$alias | String Name of the target server on which to invoke the specified service. This name and its associated connection attributes are defined on the Create Remote Server Alias screen in the Integration Server Administrator. Note: If you protect the alias using an Access Control List, the user invoking invoke must be a member of this list or the invocation will fail. |
$service | String Fully qualified name of the service to invoke on the remote server, in the format folderName.folderName:serviceName (for example: wm.server:ping). |
$scope | String Flag that specifies how the session to the remote server should be managed. Set to: ![]() Further calls by the same user to pub.remote:invoke for the same server alias reuse the existing remote session with the server. Stateful interactions with the remote server are maintained and protected inside the current user's session. When the current user disconnects, the remote session expires, or the local server is shut down, the remote session is automatically disconnected. ![]() Stateful interactions with the remote server could be destroyed by other users' invocations. When the remote session expires due to inactivity or the local server is shut down, the remote session is automatically disconnected. |
$close | String Optional. Flag to indicate whether Integration Servercloses the connection to the remote server after the service invocation or keeps the connection open until it times out. Set to: ![]() ![]() Note: If the watt.server.trigger.reuseSession server configuration parameter is set to true, Integration Server expects trigger sessions to be reused and the connection to the remote server to remain open. Hence, if watt.server.trigger.reuseSession parameter is set to true, Integration Server will ignore the value of the $close parameter when a trigger service for a webMethods messaging trigger executes the pub.remote:invoke service. |
$clusterRetry | String Optional. Flag to indicate whether Integration Servershould retry a failed connection request on other Integration Servers in the cluster. Set to: ![]() ![]() Note: Once a connection to a remote server has been established, that connection is cached and reused. The $clusterRetry setting is established when the connection is first created and used. Subsequent invokes to the same remote server will not change the $clusterRetry setting, even if a different value is passed in the pipeline. Client applications must determine whether or not they want cluster retries before establishing the connection. |