Handling new event types from a Websphere Adapters input node without changing existing deployed resources

You can create an event handler to an Enterprise Information System (EIS) to handle new event types that did not exist when you first developed your message flow. Therefore, if a new event is provided by the EIS, you do not have to modify and retest the message flow.

Before you begin

• Read the concept topic WebSphere Adapters resources.
• Ensure that you have created and deployed a message flow that is configured to use secondary adapters, as described in Configuring WebSphere Adapters nodes for secondary adapters.

About this task

To implement an event handler that you can enhance iteratively with new event types (that is, deploy new event types to the event handler), configure an SAPInput node to use secondary adapters. The set of secondary adapters can be extended at operational time without affecting any existing adapters.

1. Run the Adapter Connection wizard to create a new .inadapter component and a new message set for the new EIS events.

   You do not need to rediscover existing events. For more information about running the Adapter Connection wizard, see Connecting to an EIS by using the Adapter Connection wizard.

2. Ensure that the method names are unique.

   The method names correspond to the Service Operation names. Therefore, when you are choosing or editing the Service Operation names, make sure that they do not clash with those names defined in other adapters that are being used by that node.

3. Avoid duplicate method names by using user trace in the following way.
   1. Start user trace by following the instructions in User trace example.
   2. Stop and restart the message flow.
   3. Read user trace. Message BIP3432 identifies which methods are already defined by currently deployed adapters.
4. Ensure that the message set that is created does not contain any types that share the same name and namespace of existing message sets. You can change the namespaces of the types on the Adapter Connection wizard by using the Business Object Namespace control.

   Use different namespaces for different message sets. The use of different namespaces is important when working with BAPIs because the BAPI return field typically has the same name for all BAPIs, and its type definition can change depending on the age of the BAPI.