This configuration file contains the pipelineURL parameter
settings to configure Web services pipelines.
You can manually add or change parameters or values in
the webservices.properties file. However, by
doing so, it is possible to corrupt this file, create an invalid configuration,
or cause pipeline processing disruption. Before you make any changes
to the pipeline configuration file, make a copy of the file for safekeeping.
Note: Web
services will need to be stopped and re-started anytime the
webservices.properties file
or the pipeline configurations are changed. This is accomplished by
running the stopEAS and startEAS scripts.
Entries other than those
described here may be present in this file. Do not change these other
entries unless directed by IBM Support.
- pipelineURL
- Allows for the configuration of a single Web services pipeline
or pipeline load balancing with multiple Web services pipelines.
- This format of the webservices.properties configuration
file allows for the configuration of a single Web services pipeline
with the pipelineURL parameter:
# Set the pipeline URL
#
pipelineURL=http://[PIPELINE_HOST]:[PIPELINE_PORT]/?concurrency=[CONCURRENCY]
Note: If you exclude the "/" between [PIPELINE_PORT]
and ?concurrency=[CONCURRENCY when starting the
pipeline it will ignore the concurrency setting without any warning.
To avoid any errors, be sure to include the "/" between [PIPELINE_PORT]
and ?concurrency=[CONCURRENCY.
- To configure pipeline load balancing across multiple pipelines,
additional pipelineURL.N are required, where N must
be a unique name or number for that particular pipeline. The syntax
of this is:
#
# Comment text
#
pipelineURL=http://[PIPELINE_HOST]:[PIPELINE_PORT]/?concurrency=[CONCURRENCY]
pipelineURL.A=http://[PIPELINE_HOST_A]:[PIPELINE_PORT_A]/?concurrency=[CONCURRENCY_A]
pipelineURL.B=http://[PIPELINE_HOST_B]:[PIPELINE_PORT_B]/?concurrency=[CONCURRENCY_B]
…
pipelineURL.C=http://[PIPELINE_HOST_C]:[PIPELINE_PORT_C]/?concurrency=[CONCURRENCY_C]
- Where
- PIPELINE_HOST
- The name of the server or the IP address of this specific Web
services pipeline.
- If you misspell the host name or put the wrong IP address the
system will not warn you, but will assume the Web services pipeline
is not reachable at the moment and will periodically retry the pipeline.
You should check the pipeline log files to confirm that the Web services
pipeline is in fact valid and receiving requests. Optionally, when
configuring a new Web services pipeline pipeline, disable all others
by commenting-out the lines with a "#" starting character, add the
new Web services pipeline pipeline, start the system, ensure it works,
and then uncomment the existing entries. You can also check the [PRODUCT_HOME]/logs/ewas/SystemOut.log file
to ensure there are no warnings about a Web services pipeline being
down.
- PIPELINE_PORT
- The TCP/IP database port number of this specific Web services
pipeline.
- If you put the wrong port number the system may not warn you,
but will assume the Web services pipeline is not reachable at the
moment and will periodically retry the pipeline. You should check
the pipeline log files to confirm that the Web services pipeline is
in fact receiving requests on that port. Optionally, when configuring
a new Web services pipeline, disable all others by commenting-out
the lines with a "#" starting character, add the new Web services
pipeline pipeline, start the system, ensure it works, and then uncomment
the existing entries. You can also check the [PRODUCT_HOME]/logs/ewas/SystemOut.log file
to ensure there are no warnings about a Web services pipeline being
down.
- CONCURRENCY
- The number of HTTP requests that can be handled by this specific
Web services pipeline. This value should generally be one and a half
to two times the value DEFAULT_CONCURRENCY system
parameter.
- For optimal system performance, the concurrency specified in the
webservice.properties for each pipeline should match the HTTP transport
concurrency with which the respective pipeline was started. If the
concurrency in the webservice.properties is greater than that of the
actual transport concurrency for the pipeline then requests may block
or fail as individual pipeline(s) may be overloaded. If the concurrency
in the webservice.properties is less than the actual transport concurrency
of the respective pipeline(s) then the respective pipeline(s) may
be under-loaded and overall system performance will degrade.
- The "http transport concurrency" is specified in the pipeline.ini configuration
file or on the command line as part of the pipeline HTTP tranport
URL as shown above.
- If this value is not specified, the default value is 1.
Note: To accept the default value -- your pipeline URL must look like this:
http://[PIPELINE_HOST]:[PIPELINE_PORT]/
not like this:
http://[PIPELINE_HOST]:[PIPELINE_PORT]/?concurrency=
Example:#
# Uses the default “pipelineURL” setting as well as
# the new suffixed settings for specifying pipelines.
# In this case the client chose to use names to make the key for each
# pipeline URL unique. Also indicates the HTTP request transport concurrency
# for some pipelines.
#
pipelineURL=http://ibmrrhost.seattle.testsite.com:7777
pipelineURL.sanjose=http://ibmrrhost.sanjose.testsite.com:9999/?concurrency=5
pipelineURL.austin=http://ibmrrhost.austin.testsite.com:9875/?concurrency=5
pipelineURL.raleigh=http://ibmrrhost.raleigh.testsite.com:8888/?concurrency=10