Binding associates the logical design of an external service to a preconfigured physical service and port. This enables communication with each messaging, database, and Web service required by the business process during runtime.
Prerequisite:
Port types and ports must be defined for each service. Port types must be defined during the design of the business process. Ports can be defined during design. Ports can also be defined during configuration, or prior to binding the endpoints. See Adding a Port for additional information.
To bind the endpoints:
In the Server Explorer, verify that the runtime instance is connected and expanded.
The service machine should show a "connected" status. If it does not, click the expand symbol next to the runtime instance to connect to it and expand its contents.
Right-click on the instance or package in the Server Explorer view and select Properties.
The configuration properties for the selected package appear:
The Processes folder contains the identification of each business process included in the package.
The Endpoints folder contains the identification of all service interaction objects included in the package and the configuration for each. Identification of the configuration information binds the logical use of the service to a physical resource.
Expand each Endpoints and Services folder and select the Configuration item for each endpoint.
Select the following:
wsdl location: The wsdl column identifies the location of the information defining the service interaction. ‘Local’ refers to the definition within the package.
Service operation: The service includes the operations that are performed on the external service.
Port: for each physical binding. Click Add Port to add a port. Note: Adding a port is optional if ports required by the service were added to the service during design and are available for selection under Port.
WARNING! Make sure the service is defined and that the endpoint specified in the package and the port identifying a physical resource are the same.
Click OK to save the bindings and close the window.
Before deploying the package to the runtime instance, verify that the properties for the runtime instance are sufficiently configured. For example, verify that all transports are specified and that threads are set to the performance level that will accommodate activity on the instance. Refer to Runtime Instance Creation and Configuration for additional information.
After completing the binding and configuration, continue to the next step: Deploying the configured package.
Note: Endpoint binding definitions can be exported 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 Package Bindings.