As part of the configuration process, you must define input transports for each runtime instance. Any number of transports can be designated as input transports for a runtime instance. These transports are pooled for each instance. From its input transport pool, the engine pulls each message and routes it to the business process instance that uses the appropriate notification service.
Note: Input transport definitions can be exported as part of the runtime configuration and subsequently used for command line agent server management using the clagent utility. For additional information, see Working with Agent Server Instances from the Command Line and Exporting Runtime Instance Configurations.
There are several procedures for defining or modifying input transports. Choose the procedure that applies to the business process implementation on which you are working:
Defining input transports for a runtime instance during the Design phase
Defining input transports for a runtime instance during the Configure phase
Modifying input transports for a runtime instance after a package has been delivered
To define input transports for a runtime instance during the Design phase:
When a messaging service is defined to use a Notification (Receive) operation mode, the port defined for the service is associated with a transport. At the time the business process is packaged, this transport is automatically defined to be the input transport for the runtime instance.
Create a Messaging Service, adding an operation with Notification (Receive) mode.
Double-click on the service's wsdl node in the Orchestration Navigator to open the wsdl.
Expand the service's PortType node in the tree structure panel of the editor.
Add a port to the service. In the Endpoint pane of the wizard, select the transport to be the input transport for the notification messaging service.
After the package has been delivered to the runtime instance, you can view the defined input transports. If you want to modify the defined input transports, see Modifying input transports for a runtime instance after a package has been delivered.
In the Server Explorer, verify that the runtime instance is connected.
The host machine should indicate (connected). If it does not, click the expand symbol to connect to it.
Use one of the following methods in the Server Explorer view to open the properties editor:
Right-click on the runtime instance and select Properties.
Select a runtime instance to display the properties in the Properties view.
Expand the Resources > Input Transport nodes in the tree structure panel of the editor.
To define input transports for a runtime instance during the Configure phase:
Package and deliver the business process to the runtime instance.
In the Server Explorer, verify that the runtime instance is connected.
The host machine should indicate (connected). If it does not, click the expand symbol to connect to it.
Use one of the following methods in the Server Explorer view to open the properties editor:
Right-click on the runtime instance and select Properties.
Select a runtime instance to display the properties in the Properties view.
Expand the Resources > Input Transport nodes in the tree structure panel of the editor.
Right-click on Input Transport and choose Select from the context menu. The Select Input Transports dialog displays showing all of the defined Messaging Endpoints. If any transports are already defined for the runtime instance, those are highlighted in the Select Input Transports dialog.
Click to select the transports from which messages can be retrieved by the engine and routed to the runtime instance.
Use the Select All or Deselect All buttons as needed.
Hold down the SHIFT key to select multiple adjacent transports.
Hold down the CTRL key to select multiple non-adjacent transports.
Click on a selected transport to de-select that transport. De-selecting a transport removes the transport from the defined input transports for the runtime instance.
Warning: If you select a transport as a input transport and later decide to delete the transport, you must remove a transport from the defined input transports for the runtime instance before deleting the transport definition from the Endpoint Manager. Deployment problems occur when transports are defined as input transports and the transport definition has been deleted from the Endpoint Manager. See the description in Deployment Problems for resolving this issue.
Click OK to save and close the dialog. The selected messaging endpoints are imported as Input Transports for the runtime instance.
The Resources > Input Transports node of the instance properties dialog shows a separate node for each of the input transports defined. Input transport properties can be further edited for the runtime instance.
To modify input transports for a runtime instance after a package has been delivered:
There are special considerations when modifying the defined input transports for a runtime instance.
If you want to remove an transport from the list of defined input transports for the runtime instance, you must remove, or de-select, a transport from the defined input transports for a runtime instance in the Server Explorer before deleting the transport definition from the Endpoint Manager.
Deployment problems occur when transports are defined as input transports and the transport definition has been deleted from the Endpoint Manager. See the description in Deployment Problems for resolving this issue.
If you edit a port for a notification messaging service from the Design perspective, then regenerate, package, and deliver the package to the same runtime instance, both the previously defined input transport and the updated transport display as input transport.
To update this list in the Server Explorer, do the following:
Use one of the following methods in the Server Explorer view to open the properties editor:
Right-click on the runtime instance and select Properties.
Select a runtime instance to display the properties in the Properties view.
Expand the Resources > Input Transport nodes in the tree structure panel of the editor.
Click to select/edit the transports defined as input transports.
Use the Select All or Deselect All buttons as needed.
Hold down the SHIFT key to select multiple adjacent transports.
Hold down the CTRL key to select multiple non-adjacent transports.
Click on a selected transport to de-select that transport. De-selecting a transport removes the transport from the defined input transports for the runtime instance.
Click OK to save and close the dialog. The selected messaging endpoints are imported as Input Transports for the runtime instance.
Reviewing and Editing Configuration Properties
Runtime Instance Configuration Properties
Configuring a Runtime Instance