This topic applies only to the IBM Business Process Manager Advanced configuration.

Implementing an Advanced Integration service in a separate module

If you have defined an Advanced Integration service (AIS) in a toolkit, you can choose to separate the implementation of the AIS from the service definition by using a wizard to create the basic components that you need.

Before you begin

This procedure describes the Detailed Mode. In Simple Mode, there is an Implement link under the AIS in the Business Integration perspective. Clicking this link launches the wizard.

Implementing an AIS in a separate module is not available when an interface has multiple operations or a one-way operation. This situation occurs when the interface is created in a process application in Integration Designer and marked as business relevant instead of being generated from an AIS created in Process Designer. When an interface has multiple operations, you cannot implement each operation independently because the resulting exported WSDL file contains multiple operations. To implement them independently, you must regenerate the WSDL code into a file for each operation by using the following steps:

Import the process application into Integration Designer.
Disassociate the modules from the process application.
If there are any artifacts in the default module and library projects (process_app_name_Implementation and process_app_name_Library), save these artifacts outside of your workspace. You will merge this content back into the workspace later.
Delete the disassociated default implementation and library modules. The only artifacts left in the workspace are any disassociated modules.
Reimport the process application. This action regenerates the default projects with a WSDL file for each AIS interface.
Rename the interfaces in the library module to give them unique names. This step is necessary because the advanced integration services originally came from the same interface.
Add any artifacts that you saved in step 3 back into the default module and library projects, add those back into the projects
Publish the process application or modules.

Now you can implement each AIS independently using the steps in the procedure.

Procedure

To start the wizard and generate a basic implementation for a process application, complete the following steps:

From the Business Integration view, expand the toolkit and the Advanced Integration Services folder. Right-click the service to be implemented (it is marked unimplemented) and then click Implement. The Implement Advanced Integration Services wizard opens.
Click Separate module.
Select the module where you want the implementation to be generated. Note that if you implement an AIS in a stand-alone module, the library that contains the AIS interface is added as a dependency to the module.
Specify the version of the module that you want the AIS to reference.
Important: When you package your implementation in a separate module, all the AIS definitions that reference that module that are contained in the toolkit snapshot will reference the same version of the module that contains the implementation.
By default, the version of the toolkit in your workspace is updated to the version you specified. You can choose to keep the version of your workspace artifacts unchanged.
Select an existing export, or generate a new one.
Select the operation that you want to call.
Click Next.
Select the implementation type from the following list and click Finish.
- Microflow. Select this option if your service will start a business process that provides an immediate response. An export and a business process set to a microflow are created.
- Long-running business process. Select this option if your service will start a business process that runs for an extended time; that is, if it does not provide an immediate response. An export and a business process set to a long-running process are created.
- Java component. Select this option if your service will be implemented in Java. An export and a Java component are created.
- Empty implementation. Select this option if you have not decided on the implementation you will use. An export is created but it is not wired to a component in the assembly editor. Later you can create a mediation flow, state machine, an interaction with another system through an adapter or some other implementation.
Note: Preferred interaction style determines if a synchronous or asynchronous mode of communication is used. If your AIS is interacting with modules through imports and exports, check their preferred interaction style as it may affect your performance expectations. For example, you may select an implementation type of microflow expecting a synchronous communication mode with an immediate response. But the implementation may include modules with JMS bindings that send data asynchronously which could result in data waiting in queues.
You can now see the components in the assembly editor, and the AIS is marked implemented. You must still develop the implementations because only a skeleton has been created.
Once you have developed your implementation, you must use the Publish command to update the information of the corresponding AIS in Process Designer.

Results

When the Advanced Integration service wizard finishes, the appropriate editor opens in the implementation (an editor such as BPEL or Java). In the case where no implementation is selected, the assembly editor opens only if you are in Advanced Mode. If you are in Simple Mode, the option, Empty implementation, does not show.