IM Relationship Resolution Information Center, Version 4.2

HTTP transports

HTTP transports send the incoming records through a pipeline and return a response back to the sending host. If your system uses Web services or if you must have a response, use the HTTP transport Universal Resource Identifier (URI).

The format for the HTTP transport is:

http://host_name:port_number?concurrency=n

http://
Required parameter that indicates the transport method is HTTP.
host_name
Required parameter that indicates the name of the host machine that you are sending the request from.
port_number
Required parameter that indicates the port number on the indicated host for this request.
?concurrency=n
This optional parameter enables you to specify the number of incoming records (a positive integer greater than or equal to 0) that can be processed simultaneously using the parallel pipeline processing feature.
The higher the number, the more records are processed simultaneously. For example, a concurrency of 0 indicates do not process records. A concurrency of 1 indicates process records one-at-a-time. The default number of incoming records pulled for this transport is 5, unless you specify otherwise.
You should coordinate this setting with the number of pipeline process threads spawned by the concurrency setting in the pipeline configuration file or the DEFAULT_CONCURRENCY system parameter group in the Configuration Console. The pipeline concurrency setting determines the number of simultaneous pipeline processing threads that begin when a pipeline is started. If your system is set to spawn multiple pipeline processing threads for each pipeline started, you might want to increase this transport concurrency setting so that the pipeline threads are not waiting for records to process.

Example of an HTTP transport

http://localhost:8080

Using this example command, the system reads incoming records using HTTP from localhost, port number 8080.



Feedback

Last updated: 2009