pub.monitor.serviceControl:resubmit

contextID

String Context ID for the service to resubmit. Specify the complete, exact ID.

Note:

Whether Monitor treats contextID as case-sensitive depends on how the underlying database (for example, Oracle, DB2, or SQL server) handles the queries that Monitor issues to obtain data.

altServer

String Optional. Integration Server to which to resubmit the service, in the format Integration Server_host:Integration Server_port. By default, the service is resubmitted to the Integration Server on which the service originally ran.

Note:

Whether Monitor treats altServer as case-sensitive depends on how the underlying database (for example, Oracle, DB2, or SQL server) handles the queries that Monitor issues to obtain data.

inputPipeline

Document Optional. Input pipeline to resubmit. You can retrieve the pipeline using the pub.monitor.service:getPipeline service. If you do not provide inputPipeline, or if you do not have permission to modify the pipeline, the service retrieves the pipeline that was logged with the service in the logging database.

You can resubmit services to any Integration Server that is defined as a remote server in the Integration Server Administrator for the local Integration Server (that is, the Integration Server on which Monitor is installed). If you want to resubmit services on the local Integration Server, that Integration Server must be defined to itself as a remote server. To define an Integration Server to itself as a remote server, you must set up a remote server alias in Integration Server Administrator.

Note:

When setting up a remote server alias in Integration Server Administrator, make sure that the Host Name parameter contains the complete DNS name for the Integration Server (for example, titanium.east.webmethods.com).