Kbase 22126: SonicXQ: Does a process have to be deployed to a container?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/20/2003 |
|
SUMMARY:
This applies to SonicXQ 1.5. You might find that a process is running though it has not been deployed to your container. This Kbase explains how to track down why the process is running.
EXPLANATION:
A process, like a service, has an Entry Endpoint. In the case of a service, the service must be deployed in an active container to start running. A process can be deployed in an active container, which will activate it, but it can also start running if it is called by a service. The service would need to be deployed in the container. For instance, a service might include code like this:
if (isPO())
{
Java.lang.System.out.println(" <Message is a Purchase Order. Sending to Demo Process>");
return XQ_getProcess("SCDemoProcess");
}
This would trigger the SCDemoProcess. Assuming that all services in the Process Itinerary had been deployed in the container, the process would run through to completion.
SOLUTION:
If you find that a process is running that you don't want or expect to be running in the container, use the container logging to double check the services you've deployed and find where the process is called.
References to Written Documentation
SonicXQ 1.5 Developer's Guide, Chapter 9, Process Flows, Process Flow Concepts.