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.
This section describes using the Toolkit component of Process Center with an Outbound Adapter module.
- Switch to the Business Integration perspective of Integration Designer and import WebSphere Adapter.
- Run the External Service discovery for the Outbound adapter and configure the module for the outbound operation.
- 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
- 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
- Once the Outbound module is ready, switch to the Process Center perspective in Integration Designer.
- In the Toolkits tab, click on Create New
Toolkit, as shown in Figure 15.
Figure 15. Creating the Toolkit in the Process Center perspective
- Provide a name, such as
Test01TK, for the Toolkit as shown in Figure 16.
Figure 16. Name for the Toolkit
- 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
- Select the implementation and library of the Toolkit as shown in
Figure 18. Implementation and library of the Toolkit in the workspace
- Right-click on the created outbound module name and select
Associate with Process Center, as shown in
Figure 19. Association of the module and adapter with the Toolkit
- 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
- 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
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.
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.
- You can download the REST client from Firefox®.
- Install the REST Client Add-on for the Mozilla Firefox browser.
Then click Tools > RESTClient, as shown in Figure
Figure 22. RESTClient in Mozilla
- 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
- Select the Method as POST.
- 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
- 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:
Figure 25. 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:
- Login to the admin console of the Process Center server or external Process Server.
- Go to WebSphere enterprise applications > Deployed module > Manage Modules.
- 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
- 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. Getting the message body
- Select XML editor, select all the content, and
select Copy as shown in Figure 28.
Figure 28. Copying all the XML content
- 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
- 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.
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
For the snapshot of Toolkits to be deployed in the external Process Server, follow these steps:
- 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.
- Right-click on the Dependent Toolkits of the
newly created process application NewPA, then select
Change Toolkit Dependencies as shown in
Figure 31. Change the Toolkit Dependencies
- Select SnapTest01TK, which is the snapshot of
Test01TK toolkit as shown in Figure 32.
Figure 32. Select the snapshot of the Toolkit
- 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
- 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
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.
To delete an existing Toolkit, follow these steps:
- Click on the Toolkit to be deleted.
- Go to the Manage tab and Archive the selected Toolkit.
- If the Toolkit has dependency with any process application, then delete that Process App first.
- Go to the Snapshots tab and select Delete Toolkit.