Name of the web service. The Web Services Hub publishes this name when you check in the workflow and the service is visible. The default name is a concatenation of the repository name, folder name, and workflow name. This name must be unique.

Maximum amount of time the Web Services Hub can take to process a request and generate a SOAP response before the request times out. If the Web Services Hub is unable to generate a response within the timeout period, it sends a fault message to the web service client and drops the connection.

Default is 60 seconds. Set to 0 to disable the timeout period.

Maximum amount of time the Web Services Hub can take to process requests before it starts another instance to process the next request. The service time period starts from the time the Web Services Hub receives a SOAP request to the time it generates a SOAP response. If the average time it takes the Web Services Hub to process a request exceeds the service time, the Web Services Hub starts a new instance of the web service to process new requests.

For example, the service time is set to 1000 milliseconds. If the Web Services Hub cannot process requests within 1000 milliseconds, the Web Services Hub starts another instance of the web service to process the next SOAP request.

Default is 1000.

Note: To avoid a decline in performance, do not set the service time threshold to lower than 100 milliseconds.

Web Services Hub Service to run the workflow. Click the Browse button to select one or more Web Services Hub Service to run the web service workflow. By default, the web service workflow can run on any Web Services Hub Service associated with the repository.

Maximum number of web service instances that can be started by a Web Services Hub. All instances of the web service workflow running on the Web Services Hub are included in the count, whether the instance is started dynamically or manually. The Web Services Hub cannot start another web service instance after the maximum is reached.

Requires authentication before the web service can be run. The Web Services Hub authenticates the request based on the user name token. You can choose to protect the service or make it public.

Any PowerCenter user who can run a workflow can run a protected web service workflow using the Workflow Manager,

pmcmd

, or LMAPI. If a web service is not protected, any web service client can start the service without authentication.

For more information, see Adding Security to a Client Request.

Makes the web service visible in the Web Services Hub Console. When you make the service visible, the Web Services Hub publishes the web service and the WSDL on the Web Services Hub Console. You can test the web service and view and download the WSDL from the Web Services Hub Console.

If the service is not visible, the Web Services Hub does not publish the web service WSDL.

Allows a web service client to start the workflow by sending a request to the Web Services Hub. If the web service workflow is runnable, a web service client request can start the workflow or run the web service while the workflow is running. If you want a web service client to start the workflow, schedule the workflow to run on demand. If the web service workflow is not runnable, a web service client can invoke the web service while the workflow is running, but cannot start the workflow. If disabled, you can start the workflow through the Workflow Manager, LMAPI, or

pmcmd

.