Integrating business applications with IBM Process Center using WebSphere Adapters

In this tutorial, you will learn how to use IBM® Process Center with WebSphere® Adapters, such as setting up Process Center, associating an inbound or outbound module with process applications or toolkits, testing an inbound or outbound module, and configuring and testing the outbound module with other test clients.

Share:

Dillip Kumar Palai (dillipkumarpalai@in.ibm.com), Software Engineer, IBM

Photo of Dillip Kumar PalaiDillip Kumar Palai is a Software Engineer working as a test specialist in the WebSphere Adapter Quality Assurance team at the IBM India Software Labs. Prior to this, he worked for the WebSphere SIBus Quality Assurance team for multi-platforms.



Deepika Udayagiri (deepika.udayagiri@in.ibm.com), Software Engineer, IBM

Photo of Deepika UdayagiriDeepika Udayagiri is a Software Engineer working as a test specialist in the WebSphere Adapter Quality Assurance team at the IBM India Software Labs. Prior to this, she worked for the WebSphere eXtended Transaction Runtime Quality Assurance team and TXSeries for multi-platforms.



05 December 2012

About this tutorial

This tutorial provides instructions on how to integrate enterprise applications using IBM WebSphere Adapters with Process Center. WebSphere Adapters are pre-built software integration components compliant with Java™ Connector Architecture 1.5 (JCA). They provide bi-directional connectivity between Enterprise Information System (EIS) and business applications through configuration only and no coding approach. They can run on multiple runtimes such as IBM Process Center, IBM Process Server, WebSphere Message Broker, and so on.

WebSphere Technology Adapters include Adapters for Email, Enterprise Content Management (ECM), Flat Files, FTP, IBM i, JDBC, and Lotus Domino. WebSphere Application Adapters include adapters for JD Edwards® EnterpriseOne, Oracle® E-Business Suite, PeopleSoft® Enterprise, SAP® Software, and Siebel® business applications.

Objectives

In this tutorial, you will learn about:

  • Configuring Process Center, which includes the prerequisites, the procedure for creating profiles, connecting to Process Center from IBM Integration Designer, and adding the Process Center server into the Integration Designer servers view.
  • Working with Process Center, which includes integrating WebSphere Adapter inbound module with process applications, outbound module with toolkits, and snapshots, respectively.

Prerequisites

You need prior knowledge about configuring inbound and outbound modules with WebSphere Adapters and a basic knowledge of the respective Enterprise Information Systems.

System requirements

  • IBM Integration Designer V8.0 (formerly called WebSphere Integration Developer)
  • WebSphere Adapter V7.5.0.3 (any adapter)
  • IBM Business Process Manager V8.0

Duration

The estimated time to complete this tutorial is 3 hours.


Introduction

IBM Process Center is an integration server where applications developed on Process Designer and IBM Integration Designer (hereafter called Integration Designer) can be deployed to help users build business processes. Process Center integration using WebSphere Adapters has become a challenge. There are many customers who are using Process Center as a runtime.

Since this topic is new to many customers, there is a need to describe how to make Process Center work with WebSphere Adapters. This tutorial is intended to help customers who are interested in using Process Center with WebSphere Connectors, such as:

  • Setting up the Process Center
  • Associating the inbound or outbound module with process applications or toolkits in Process Center
  • Testing an inbound or outbound module of WebSphere Adapter with Process Center
  • Configuring and testing the outbound module with other test clients such as RESTClient and so on.

For more details about Process Center, refer to the IBM BPM Information Center topic, Managing the Process Center repository.

Various components of Process Center

The various components of Process Center are:

You can develop the process application and toolkit by using either the Process Designer or Process Center perspective of Integration Designer. In this tutorial, you are developing process application or toolkit using the Process Center perspective of Integration Designer.


Configuring Process Center

This section describes how to create profiles, how to connect to Process Center from Integration Designer, and how to add Process Center server into the Integration Designer servers view.

Prerequisites

You need to:

  • Install BPM with the Process Center build.
  • Create two profiles: one for Process Center and the other for the external process server for the snapshot deployment.

Creating profiles

Create a standalone server profile for the Business Process Manager Advanced Process Center, such as "ProcCtr01", with the following considerations:

  1. For the admin console, provide the username and password.
  2. For the database, provide the db_username and db_password.
  3. After the profile is created successfully, start the profile.

Then, create a standalone server profile for the Business Process Manager Advanced Process Server, such as "ProcSrv01":

  1. For the admin console, provide the username and password.
  2. For the database, provide the db_username and db_password.

During the profile creation wizard for Process Server:

  1. Use different database names (common DB, performance DB, and so on) for the Process Server and Process Center profiles.
  2. Uncheck the option use server offline.
  3. Select the server type as Test.
  4. Provide a name for the environment, then input the Process Center host name and port, such as localhost and 9080 respectively, and then click Test connection. The port number is subject to change, depending on the actual environment setting.
  5. After the profile is created successfully, start the profile.

Note: Now there are two profiles, one for Process Server and one for Process Center. You can now create an inbound or outbound module and test them on both servers.

For more details about the standalone profile creation, see Creating or augmenting standalone profiles with a DB2® database server.

Connecting to Process Center from Integration Designer

You can connect to the Process Center from Integration Designer using the Process Center perspective. Provide the URL of the Process center in the following format: http://<hostname>:<port>/ProcessCenter

The user name and password are provided during profile creation to connect to Process Center.

Adding the Process Center server into the Integration Designer servers view

You can directly add a Process Center server manually. If not, the Process Center server is automatically added into the server view when the process application or toolkit is opened in the Integration Designer workspace.


Working with Process Center: Adapter inbound configuration

The following section describes how to use Process Center with applications built using adapters. You will look at the configuration of an inbound adapter module using the Process Application component of the Process Center.

When you are developing any inbound or outbound module, you can create that module by using either the embedded mode or standalone mode. If the module is standalone, then the adapter connector must be installed in the admin console of the Process Center server or the external Process Server.

Testing the inbound module with process applications

  1. Switch to the Business Integration perspective of Integration Designer and import WebSphere Adapter.
  2. Run the External Service discovery for the Inbound adapter. Add an endpoint implementation.
  3. Once the inbound module is ready, switch to the Process Center perspective in Integration Designer.
  4. In the Process Apps tab, click on Create New Process App as shown in Figure 1.
    Figure 1. Creating a Process App in the Process Center perspective
    Creating a Process App in the Process Center perspective
  5. Provide a name for the Process App, such as Test01PA, as shown in Figure 2.
    Figure 2. Name of the Process App
    Name of the Process App
  6. Select Open in workspace to open an application in the workspace as shown in Figure 3.
    Figure 3. Open created a Process App in the workspace
    Open created a Process App in the workspace
  7. Select the implementation and library for the process application in the workspace as shown in Figure 4.
    Figure 4. Implementation and library for the Process App
    Implementation and library for the Process App
  8. Right-click on the created inbound module and select Associate with Process Center, as shown in Figure 5.
    Figure 5. Association of module and adapter with Process Center
    Association of module and adapter with Process Center
  9. Select the process application from the drop down menu, and then select the adapter and module to be associated with the process application (Figure 6). Click Finish.
    Figure 6. Association of module and adapter with Process Center
    Association of module and adapter with Process Center
  10. After this step, it will take some time to deploy the module, with "updating Process Center" shown at the bottom of the Integration Designer screen. As a result of this, the module and adapter, which were outside of the process application, will be moved into the process application as shown in Figure 7.
    Figure 7. Confirmation of successful association of module and adapter with Process Center
    Confirmation of successful association of module and adapter with Process Center

Now the inbound module has been deployed and started in Process Center, which can be observed in the Servers view.

The deployed inbound module is ready to poll events from the Enterprise Information System (EIS). In EIS, events such as create/update/delete/retrieve, which are specific to adapter, can be polled by the inbound module depending on the configuration.

Once the expected events are polled, make sure that the module is undeployed, or launch the admin console of Process Center and uninstall the respective module. For the undeployment of the inbound module, either disassociate the module, adapter, or both from Process Center.

Testing the inbound module with external Process Server via the Process Application snapshot

A snapshot is the recorded state of library items within a process application or toolkit.

You can take a snapshot of process applications (which contains modules and adapters) or toolkit (which contains modules and adapters). When the requirement is to test the inbound or outbound module with the external Process Server that is connected to Process Center, then you need to create a snapshot and deploy it.

  1. Select the process application for which you want to create a snapshot as shown in Figure 8.
    Figure 8. Creating a snapshot by selecting Process Application
    Creating a snapshot by selecting Process Application
  2. Select the Create New Snapshot option as shown in Figure 9.
    Figure 9. Creating the snapshot
    Creating the snapshot
  3. Provide a name for the Snapshot, such as SnapTest01PA, as shown in Figure 10.
    Figure 10. Name for the snapshot
    Name for the snapshot
  4. Select the Install option available with "SnapTest01PA" as shown in Figure 11. This option is available with the snapshot of the process application only and not with the toolkits.
    Figure 11. Installing snapshot into the External Process Server
    Installing snapshot into the External Process Server

    Choose the external process server as shown in Figure 12.

    Figure 12. Selecting the External Process Server from the list
    Selecting the External Process Server from the list

After this, a snapshot of the process application is deployed to the external Process Server and is started. Once the expected events are polled, make sure that the module is undeployed.

Deleting the process application

To delete an existing process application, follow these steps:

  1. Click on the Process Application to be deleted.
  2. Go to the Manage tab and Archive the selected process application.
  3. Go to the Snapshots tab and select Delete Process App.

Working with Process Center: Adapter outbound configuration

The section describes how to use Process Center with the applications built using adapters. You will look at the configuration of an outbound adapter module using the Toolkit component of the Process Center.

Testing the outbound module with the Toolkits

This section describes using the Toolkit component of Process Center with an Outbound Adapter module.

  1. Switch to the Business Integration perspective of Integration Designer and import WebSphere Adapter.
  2. Run the External Service discovery for the Outbound adapter and configure the module for the outbound operation.
  3. After the Adapter Import is generated, go to the assembly diagram, add an Export (such as Export1), and wire it to the Import. Then Generate Web Service Binding for the Export (using the default setting) as shown in Figure 13.
    Figure 13. Generate Web Service Binding for the Export component
    Generate Web Service Binding for the Export component
  4. Select the SOAP1.1/HTTP option and click Finish, as shown in Figure 14. The Outbound module is ready to be deployed on Process Center.
    Figure 14. Configure the Web Service Export
    Configure the Web Service Export
  5. Once the Outbound module is ready, switch to the Process Center perspective in Integration Designer.
  6. In the Toolkits tab, click on Create New Toolkit, as shown in Figure 15.
    Figure 15. Creating the Toolkit in the Process Center perspective
    Creating the Toolkit in the Process Center perspective
  7. Provide a name, such as Test01TK, for the Toolkit as shown in Figure 16.
    Figure 16. Name for the Toolkit
    Name for the Toolkit
  8. Select Open in workspace to open the application in the workspace as shown in Figure 17.
    Figure 17. Open the created Toolkit in the workspace
    Open the created Toolkit in the workspace
  9. Select the implementation and library of the Toolkit as shown in Figure 18.
    Figure 18. Implementation and library of the Toolkit in the workspace
    Implementation and library of the Toolkit in the workspace
  10. Right-click on the created outbound module name and select Associate with Process Center, as shown in Figure 19.
    Figure 19. Association of the module and adapter with the Toolkit
    Association of the module and adapter with the Toolkit
  11. Select the respective Toolkit from the drop down menu, select the adapter and module to be associated with the Toolkit, and then click Finish (Figure 20).
    Figure 20. Association of the module and adapter with the Toolkit
    Association of the module and adapter with the Toolkit
  12. After this step, it will take some time to deploy the module and "update Process Center" shown at the bottom of the Integration Designer screen. As a result of this, the module and adapter, which were outside of the Toolkit, will be moved to the Toolkit as shown in Figure 21.
    Figure 21. Confirmation of association of the module and adapter with the Toolkit
    Confirmation of association of the module and adapter with the Toolkit

Now that the Outbound module has been deployed and started, this module is started in Process Center, which can be observed in Servers view. You can create/update/delete/retrieve events that are specific to the adapter in EIS by using clients other than the Integration Designer test client.

Note: Do not use the Integration Designer Test Client for outbound testing, especially for the Process Application and Toolkit in Process Center because the Test Client will automatically deploy the module in the Process Server instead of through the Process Application and Toolkit.

Test clients, such as REST Client, J2C test client, and SOAP UI, can also be used for outbound module testing.

Testing the outbound module with the REST client of the Mozilla Firefox browser

The following section discusses about testing the outbound module using a REST client. After the module with Process Apps or Toolkit is deployed, you can use any HTTP client tool to send out the outbound request.

  1. You can download the REST client from Firefox®.
  2. Install the REST Client Add-on for the Mozilla Firefox browser. Then click Tools > RESTClient, as shown in Figure 22.
    Figure 22. RESTClient in Mozilla
    RESTClient in Mozilla
  3. After the installation, open the REST Client and fetch the Method, URL, and Body one by one as mentioned in the steps below.
    Figure 23. RESTClient overview
    RESTClient overview
  4. Select the Method as POST.
  5. As shown in Figure 23, fetch the URL of the Webservice binding by launching the Test Component tool from Integration Designer as shown in Figure 24.
    Figure 24. Test Component option for the Export component
    Test Component option for the Export component
  6. Select the Transport tab and get the Endpoint URL link. Change the hostname and port according to where Process Center or the external Process Server is running (see Figure 25). The URL format is:
    http://<HOST>:<PORT>/<Module_Name_after_deployment>/sca/<Export Name>
    Figure 25. Getting the URL for the REST Client
    Getting the URL for the REST Client

    From the URL format, "Module_Name_after_deployment" is the name of the module after it is deployed into Process Center Server or the external Process Server. This name can be fetched from the admin console.

    Use the following procedure to get the module name after deployment:

    1. Login to the admin console of the Process Center server or external Process Server.
    2. Go to WebSphere enterprise applications > Deployed module > Manage Modules.
    3. Copy the module name that ends with "Web". The deployed module name is "T1TK-Tip-Outbound_DominoApp" and the Module_Name_after_deployment is "T1TK-Tip-Outbound_DominoWeb", as shown in Figure 26.
      Figure 26. Getting the module name after deployment
      Getting the module name after deployment
  7. As shown in Figure 23, fetch the Body - Input Business Object data for the outbound. Provide the business object parameters in the Value editor for the business object as shown in Figure 27.
    Figure 27. Getting the message body
    Getting the message body
  8. Select XML editor, select all the content, and select Copy as shown in Figure 28.
    Figure 28. Copying all the XML content
    Copying all the XML content
  9. As shown in Figure 23 for RESTClient, all the fields are ready as shown in Figure 29.
    Figure 29. Sending request to EIS with RESTClient
    Sending request to EIS with RESTClient
  10. Send out the HTTP request. If the outbound request succeeds, you see the response status as "200 OK" and the returned BO in the response message body. If it fails, an error message is displayed.

If the outbound request is successful, you can check the created/updated/deleted event in the EIS that are specific to the adapter.

To undeploy the outbound module, either disassociate the module, adapter, or both from the Process Center, or launch the admin console of Process Center and uninstall the respective module.

Testing the outbound module with the External Process Server via the Toolkit snapshot

Follow the same steps as described in the Testing the inbound module with the external Process Server via the Process Application snapshot section to create a snapshot for the toolkit by choosing Toolkits option.

After creating the snapshot of the Toolkit, there will be no install option like the snapshot of the Process Application as shown in Figure 30.

Figure 30. Install option is not available with the Toolkit snapshot
Install option is not available with the Toolkit snapshot

For the snapshot of Toolkits to be deployed in the external Process Server, follow these steps:

  1. Create a new process application such as NewPA. You can follow the Testing the inbound module with process applications section for this. Open this in the Integration Designer workspace.
  2. Right-click on the Dependent Toolkits of the newly created process application NewPA, then select Change Toolkit Dependencies as shown in Figure 31.
    Figure 31. Change the Toolkit Dependencies
    Change the Toolkit Dependencies
  3. Select SnapTest01TK, which is the snapshot of Test01TK toolkit as shown in Figure 32.
    Figure 32. Select the snapshot of the Toolkit
    Select the snapshot of the Toolkit
  4. After the previous step, you can observe that SnapTest01TK, which is snapshot of Test01TK toolkit, is moved to Dependent Toolkits of the process application "NewPA", as shown in Figure 33.
    Figure 33. Confirmation of dependent Toolkit snapshot with Process Application
    Confirmation of dependent Toolkit snapshot with Process Application
  5. Now create a snapshot of the process application that contains the dependent toolkit. Install that snapshot into the external Process Server since the snapshot of the process application contains the install option, which has already been discussed in the Testing the inbound module with the External Process Server via the Process Application snapshot section.

After this, a snapshot of the process application is deployed to the external Process Server and is started. You can check this in the admin console of the external Process Server.

Now the outbound module is ready for testing with the external Process Server. You can follow the instructions in the Testing the outbound module with the REST client of the Mozilla Firefox browser section.

Deletion of the Toolkit

To delete an existing Toolkit, follow these steps:

  1. Click on the Toolkit to be deleted.
  2. Go to the Manage tab and Archive the selected Toolkit.
  3. If the Toolkit has dependency with any process application, then delete that Process App first.
  4. Go to the Snapshots tab and select Delete Toolkit.

Conclusion

In this tutorial, you learned about Process Center and its various components. You learned how to configure and work with Process Center and work with the external Process Servers managed by Process Center. You also learned how to integrate any inbound or outbound adapter application with Process Center. You can now manage your development environment by integrating business applications with IBM Process Center using WebSphere Adapters.

Resources

Learn

Discuss

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


All information submitted is secure.

Dig deeper into WebSphere on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=848460
ArticleTitle=Integrating business applications with IBM Process Center using WebSphere Adapters
publish-date=12052012