Application integration with WebSphere Cast Iron Cloud Integration, Part 2: Configuring the orchestration

Part 2 of this series explains how to configure a WebSphere® Cast Iron orchestration, along with detailed procedures on configuring an MQ Poll Message activity, a Read XML activity, and a Database Insert Rows activity.

Share:

Shouvik Mitra (shomitra@in.ibm.com), IT Specialist, IBM

Photo of Shouvik MitraShouvik Mitra is a Senior IT Specialist at IBM India. He has more than 10 years of experience in Enterprise Integration. He is experienced with several EAI technologies, such as WebSphere Message Broker, WebSphere Cast Iron, and SeeBeyond e*Gate. Shouvik is an IBM certified Message Broker professional. He holds a degree in Power Engineering from Jadavpur University, Kolkata, India.



25 September 2013

Introduction

Part 1 of this article series presented an overview of creating projects in WebSphere Cast Iron Studio (hereafter called Studio), creating an orchestration, and configuring the configuration properties and endpoints. Here, Part 2 demonstrates the procedure of configuring the Cast Iron orchestration along with configuring an MQ Poll Message activity, a Read XML activity, and a Database Insert Rows activity.


Configuring the orchestration

This section describes how to configure different activities in an orchestration to perform specific tasks.

Configuring the MQ Poll Message activity

  1. From the Activity tab, drag the MQ Poll Message activity into the orchestration as shown in Figure 1.
    Figure 1. MQ Poll Message activity
    MQ Poll Message activity
  2. Now you need to configure this Poll Message activity. Click the Poll Message activity on the orchestration as shown in Figure 2. At the bottom, the configuration checklist appears, which you have to configure one by one.
    Figure 2. Configuring MQ Poll Message activity
    Configuring MQ Poll Message activity
  3. Click Pick Endpoint and select MQEndpoint as shown in Figure 3. Then save the project by pressing CTRL+s.
    Figure 3. Selecting the endpoint in the MQ Poll Message activity
    Selecting the endpoint in the MQ Poll Message activity
  4. 4. Next, select Configure in the checklist as shown in Figure 4.
    Figure 4. Setting the queue name in the MQ Poll Message activity
    Setting the queue name in the MQ Poll Message activity
  5. The input queue name is provided here as shown in Figure 4. Also the Payload Data type is selected as String. Instead of hard coding the "Queue Name", you can set the configuration property here by clicking the "T" drop-down icon next to the "Queue Name" field.
    Figure 5. Setting the queue name in the MQ Poll Message activity from the configuration parameter
    Setting the queue name in the MQ Poll Message activity from the configuration parameter
  6. Leave "Delivery Rules" and "Retry" as they are. Now click on Map Outputs. Initially, Map Outputs looks like Figure 6.
    Figure 6. Map Outputs of the MQ Poll Message activity
    Map Outputs of the MQ Poll Message activity
  7. Here, copy the input payload (as shown by the arrow in Figure 6) to an orchestration variable. To do that, click on payload and then click Copy as shown in the blue box. After you click Copy, a new window appears as shown in Figure 7.
    Figure 7. Copying payload in Map Outputs of the MQ Poll Message activity
    Copying payload in Map Outputs of the MQ Poll Message activity
  8. Next, click on payload as shown in Figure 7, and then click on the Create button.

    A new orchestration variable called "payload"is created that needs to be renamed later, as shown in Figure 9. The input payload is mapped to this newly created "payload" variable, as shown in the blue box in Figure 8.

    Figure 8. Mapping payload in Map Outputs of MQ Poll Message activity
    Mapping payload in Map Outputs of MQ Poll Message activity
  9. Now rename this newly created payload variable. Click the Variables tab. The blue arrow shows that there is a new "payload" variable created as shown in Figure 9.
    Figure 9. Renaming the new variable
    Renaming the new variable
  10. Click the payload variable name as shown by the arrow in Figure 9. Change the variable name to Input_Payload as shown in Figure 10. Press the Enter key.
    Figure 10. Renamed new variable
    Renamed new variable

    Note that the variable name is also automatically changed in "Map Outputs" on the checklist of the MQ Poll Message Activity, as shown in Figure 11.

    Figure 11. Renamed new variable in Map Outputs of the MQ Poll Message activity
    Renamed new variable in Map Outputs of the MQ Poll Message activity

Configuring the Read XML activity

  1. Drag the Read XML activity in the orchestration, as shown in Figure 12.
    Figure 12. Read XML activity
    Read XML activity
  2. In the orchestration, click the Read XML activity. The checklist appears at the bottom. Click Configure as shown in Figure 13.
    Figure 13. Configuring the Read XML activity
    Configuring the Read XML activity
  3. Here, you need to get the appropriate XML schema, which needs to be parsed. Click the Browse button as shown in Figure 13 to display the list of orchestration variables, which is displayed in Figure 14.
    Figure 14. Orchestration variables
    Orchestration variables
  4. Click the New button. The following window appears as shown in Figure 15.
    Figure 15. Data types for the variables
    Data types for the variables
  5. Click the Add button. The appropriate schema location is provided. Click the OK button as shown in Figure 16.
    Figure 16. Loading the XML schema
    Loading the XML schema
  6. The CompanyDetails appear in the XML Schemas section as shown in Figure 17. Click CompanyDetails as shown by the blue arrow in Figure 17 and click Next.
    Figure 17. Selecting the root node of the XML schema
    Selecting the root node of the XML schema
  7. The variable name is left as it is as shown in Figure 18. Click Finish.
    Figure 18. Naming the newly created variable
    Naming the newly created variable
  8. The "CompanyDetails" appear as shown in Figure 19. Click OK and save the project by pressing Ctrl+s.
    Figure 19. Newly created variable in list of orchestration variables
    Newly created variable in list of orchestration variables
  9. Click Map Inputs as shown in Figure 20.
    Figure 20. Configuring Map Inputs of the Read XML activity
    Configuring Map Inputs of the Read XML activity
  10. Click Select Inputs. The following window appears as shown in Figure 21.
    Figure 21. Setting the variables in Map Inputs of the Read XML activity
    Setting the variables in Map Inputs of the Read XML activity
  11. Select Input_Payload and click OK. Input_Payload is mapped to XmlText as shown in Figure 22.
    Figure 22. Mapping variables in Map Inputs of the Read XML activity
    Mapping variables in Map Inputs of the Read XML activity
  12. Click Map Outputs as shown in Figure 23.
    Figure 23. Map Outputs of the Read XML activity
    Map Outputs of the Read XML activity
  13. Now create a copy of "OutputXml". Click CompanyDetails as shown by the arrow in Figure 23, and then click the Copy button. The following window appears as shown in Figure 24.
    Figure 24. Copying parameters for Map Outputs of the Read XML activity
    Copying parameters for Map Outputs of the Read XML activity
  14. Click OutputXml and then click the Create button to create a new variable as shown in Figure 25.
    Figure 25. Mapping for Map Outputs of the Read XML activity
    Mapping for Map Outputs of the Read XML activity
  15. Rename the newly created OutputXml to CompanyDetailsXML. Select the Variables tab and click OutputXml as shown by the arrow in Figure 26.
    Figure 26. Renaming the new variable
    Renaming the new variable
  16. Enter the new name, CompanyDetailsXML, at the position shown by the blue arrow as shown in Figure 26. After entering the new name, press the Enter key, and press Ctrl+s to save the project. The renamed variable name is shown in Figure 27.
    Figure 27. Renamed new variable name in Map Outputs of the Read XML activity
    Renamed new variable name in Map Outputs of the Read XML activity

Configuring the Insert Rows activity

  1. Drag the Insert Rows activity into the orchestration as shown in Figure 28.
    Figure 28. Database Insert Rows activity
    Database Insert Rows activity
  2. In the orchestration, click the Insert Rows activity. The checklist appears at the bottom. Click Pick Endpoint and select DBEndpoint as shown in Figure 29.
    Figure 29. Selecting the Endpoint for the Insert Rows activity
    Selecting the Endpoint for the Insert Rows activity
  3. Now click Pick Table as shown in Figure 30.
    Figure 30. Configuring Pick Table of the Insert Rows activity
    Configuring Pick Table of the Insert Rows activity
  4. Click the Browse button. The following window appears as shown in Figure 31.
    Figure 31. Browsing the database table
    Browsing the database table
  5. Select the user schema as CIRON. Press the Search button. The list of tables under the CIRON schema appears as shown in Figure 32.
    Figure 32. Selecting the database table
    Selecting the database table
  6. Select the EMPDTL table and click OK. The database table columns appear in the Pick Table checklist as shown in Figure 33.
    Figure 33. Selecting columns of the database table
    Selecting columns of the database table
  7. Select Delivery Rules as shown in Figure 34.
    Figure 34. Setting the Delivery Rules
    Setting the Delivery Rules
  8. Select the Map Inputs checklist and then click the Select Inputs button as shown in Figure 35.
    Figure 35. Configuring Map Inputs of the Insert Rows activity
    Configuring Map Inputs of the Insert Rows activity
  9. Select the appropriate variable, CompanyDetailsXML, and click OK as shown in Figure 36.
    Figure 36. Input variable for Map Inputs of the Insert Rows activity
    Input variable for Map Inputs of the Insert Rows activity
  10. The CompanyDetailsXML appears on the input side. The mapping is done as shown in Figure 37. Save the project by pressing Ctrl+s.
    Figure 37. Mapping for Map Inputs of the Insert Rows activity
    Mapping for Map Inputs of the Insert Rows activity

Validating the Cast Iron project

After the configuration is completed, the complete orchestration looks like Figure 38. To validate the project, click the yellow "Validate Project" check mark button as shown in the box in Figure 38.

Figure 38. Completing the orchestration
Completing the orchestration

The following success message appears as shown in Figure 39. The project is now ready for deployment.

Figure 39. Validation of the Studio project
Validation of the Studio project

Conclusion

In Part 2 of this series, you configured a Cast Iron orchestration, the MQ Poll Message activity, the Read XML activity, and the Database Insert Rows activity. As a final step, you validated the orchestration in Cast Iron Studio. In the next part, Part 3, you will learn to test an orchestration in Studio, publish a Cast Iron project, and run the project from the Integration Appliance.

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=946240
ArticleTitle=Application integration with WebSphere Cast Iron Cloud Integration, Part 2: Configuring the orchestration
publish-date=09252013