You must start a callout thread after a callout application
is deployed to SOAP Gateway before
the application can begin processing callout messages.
This task operates at the thread level; the start action affects only the tpipe
that is associated with this thread.
- Ensure that the SOAP Gateway server
has an active HTTP listening port.
The SOAP Gateway management utility commands
for thread management require an active HTTP listening port.
- Ensure that the callout thread pool is started with the iogmgmt
-view -workerthreads command.
Callout threads
poll messages from defined tpipes and send them to be picked up by
worker threads in the thread pool. The worker threads then invoke
external web services. If the thread pool is stopped while callout
threads are running, the work queue fills up with unprocessed messages
and callout processing halts.
-
To start the callout thread and begin processing callout requests for the application, issue
the iogmgmt -callout -startone -c connection_bundle_name -p
tpipe_name command.
connection_bundle_name is the name of the connection bundle that is specified
in the correlator XML file for the callout application. tpipe_name is the name of
each tpipe in the connection bundle that is associated with the application.
Note: You must issue the command for each tpipe associated with the application to start all of the
relevant callout threads.
- Optional:
To verify that the callout thread for the application is running, issue the iogmgmt
-view -calloutthreads command.
A callout thread might take some time to start, depending on available system
resources.
The callout thread for the connection bundle and tpipe name that you specified begins to process callout
messages.