Queue and directory validation
If you explicitly specify a request queue name, you might accidentally
use an existing queue name. If you use generated queue names, a truncated
queue name might not be unique. To protect against these problems, the deploy
utility looks for the presence of an existing start up script in the generated/server
subdirectory of the deployment directory. It then checks the URI specified
to the listener in that script. It also checks whether the request queue
already exists. Having made these checks, the deployment utility then takes
one of the following six actions as appropriate:
- Request queue does not already exist
- The listener start up script is not found in the generated/server directory.
This is the case where no previous service has been deployed from this directory.
Deployment continues with no warnings or errors.
- The listener start up script is found but the request queue in the URI
does not match that being used by the deployment utility. This is the case
where a previously deployed service in this directory was deployed with a
different queue.
The deployment utility displays an error message and exits.
- The listener start up script is found and the request queue matches that
being used by the deploy utility This might indicate an incomplete or corrupted,
but compatible, previous deployment.
The deployment utility displays
a warning message because the start up file was valid but the queue did not
exist. Deployment continues and the request queue is created.
- Request Queue does already exist
- The listener start up script is not found in the generated/server directory.
This might indicate the queue is already in use for services deployed in another
directory, or for some other application.
The deployment utility displays
an error message and exits.
- The listener start up script is found but the request queue in the URI
does not match that being used by the deployment utility. This is the case
when a service has already been deployed in this directory, but using a different
queue.
The deployment utility displays an error message and exits.
- The listener start up script is found and the request queue matches that
being used by the deploy utility. This occurs when a service has already been
deployed in this directory using the same queue.
Deployment continues
with no warnings or errors.