IBM E02HMLL-I Implementation Guide - Page 47
Con connectors, business, object, support, associated, Create, con collaboration,
View all IBM E02HMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 47 highlights
Configure connectors for business object support and associated maps Before you can test all of the developed components together, you must reconfigure the connector definitions to add support for the application-specific and generic objects they require to participate in the interface. The system associates any maps that it can automatically, but in situations where there are multiple maps that could transform objects you must explicitly associate a map. For more information, see Chapter 7, "Configuring connectors," on page 121. Create and configure collaboration objects Once you have added support for the required business object definitions to the connectors you can create a collaboration object based on the template and bind its ports to the proper components. For more information on working with collaboration objects, see Chapter 9, "Configuring collaboration objects," on page 155. Deploy the interface After you have created all of the required components for the interface you must deploy it to your local InterChange Server Express instance to test the interface. For more information on deployment, see "Exporting components to a package using System Manager" on page 68. Test the interface After you have deployed the interface to your local InterChange Server Express instance you should test the interface as a whole to ensure that the components satisfy the business requirements when working together. Do the following to test the interface: 1. Ensure that all of the required components are active. 2. Trigger an event in the source system. 3. Examine the logging output of InterChange Server Express to ensure that the components in the interface execute properly. 4. Examine the destination system to ensure that the entity was processed successfully and that the data appears as it should. Chapter 3. Developing business process interfaces 35