Calling new services from a WebSphere Adapters request node without changing existing deployed resources

If your message flow acts as a gateway to an Enterprise Information System (EIS), you can use it to call new services that did not exist when you developed the flow. Therefore, if a new service 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 use iterative deployment, you can configure an SAPRequest, SiebelRequest, PeopleSoftRequest, or JDEdwardsRequest node to look for a specified operation in all relevant .outadapter components that are deployed to the integration server.

1. Run the Adapter Connection wizard to create an .outadapter component and a library for the new EIS services.

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

2. Ensure that method names are unique across all primary and secondary adapters that are used by the request node. If they are not unique, edit them by clicking Edit Operations on the Service Generation and Deployment Configuration panel of the Adapter Connection wizard.

   The method names correspond to the Service Operation names, which are configured by the Adapter Connection wizard. In most cases, the names are based on the name of the service that is being discovered (for example, the BAPI name in SAP, or the business object and operation name in Siebel). However, in some cases, you must edit them to avoid a clash.

   You can set the method name dynamically in the message flow by setting the local environment field $LocalEnvironment/Adapter/MethodName.

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.

   Alternatively, you can identify the methods that are defined by the adapter by looking at the Default method property of the request node. If you have a .outadapter component in your workspace, you can drop it onto a message flow to create a request node for the .outadapter component. The request node has that adapter set as its primary adapter, and the list of methods that are defined by that adapter are visible in the Default method property of the request node.

4. Ensure that the library that is created does not contain any types that share the same name and namespace of existing libraries. 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 libraries. 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.