Application integration with WebSphere Cast Iron Cloud Integration, Part 3: Publishing a project into the Integration Appliance

Part 1 and Part 2 of this series demonstrated how to create and configure an orchestration using WebSphere® Cast Iron Studio. In this last part of the series, you will learn to test an orchestration in Studio, publish a Cast Iron project, and run the project from the Integration Appliance.

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

Part 1 and Part 2 of this series demonstrated how to create a project and configure an orchestration using WebSphere Cast Iron Studio (hereafter called Studio). Here in Part 3 as the final step, you will deploy the Cast Iron project into the Integration Appliance and test the orchestration. If the Cast Iron project is valid, then it is ready for deployment. Before deployment, you can test the orchestration in Studio. The deployment is basically publishing the project from the orchestration to runtime (for example, the Integration Appliance).

If Studio and the Integration Appliance are on the same network, then you can directly publish the project to the Integration Appliance. However, if Studio and the Integration Appliance are in separate networks, you need to export the project from Studio. You can import the project into the Integration Appliance by using the Web Management Console (WMC). In this article, we assume that Studio and the Integration appliance are in the same network.

Testing the Cast Iron orchestration

You can test the orchestration within Studio itself. Click the Verify tab as shown in Figure 1. The XML message is put into the input local queue. Press the green Play button.

Figure 1. Verifying the orchestration
Verifying the orchestration

The orchestration is executed in Studio as shown in Figure 2.

Figure 2. Execution result in Studio
Execution result in Studio

As a result, the EMPDTL Oracle® table is loaded as shown in Figure 3.

Figure 3. Execution result in the Oracle table
Execution result in the Oracle table

Publishing and deploying the project using WMC

Once the project is validated in the studio, you can publish and deploy the project in the Integration Appliance using the Web Management Console (WMC).

  1. From the studio menu bar, select File> Publish Project. The Integration Appliance details are:
    • Host Name: managementIP, shown as x.xx.xxx.x
    • User Name: management user ID, shown as admin
    • Password: management password
    Figure 4. Publishing the project in the Integration Appliance
    Publishing the project in the Integration Appliance
  2. Press the OK button. If the project is successfully published, then the following message is displayed as shown in Figure 5.
    Figure 5. Success message after publishing the project in Integration Appliance
    Success message after publishing the project in Integration Appliance

    Now the WMC is opened in a supported browser (such as https://managementIP/login), as shown in Figure 6.

    Figure 6. Cast Iron WMC login page
    Cast Iron WMC login page
  3. Once logged in with the management user ID and management password, you can locate your project (see Figure 7) that was published in the previous step.
    Figure 7. Cast Iron WMC - Home
    Cast Iron WMC - Home

    In Figure 7, your project is still undeployed. You can access configuration details of the project (see Figure 8) by clicking on the project name, as highlighted in Figure 7.

    Figure 8. Configuration details of the project
    Configuration details of the project
  4. Click the Edit button to edit the orchestration as shown in Figure 8 and make the following changes (also see Figure 9):
    • Logging Level: All
    • Max Simultaneous Jobs: 1
    Figure 9. Editing the orchestration
    Editing the orchestration
  5. After this change, press the Save button at the bottom.
  6. Press the green arrow to deploy the project as shown in Figure 10.
    Figure 10. The project is in undeployed state
    The project is in undeployed state

    Once deployed, the status changes as shown in Figure 11.

    Figure 11. The project is in running state
    The project is in running state
  7. To test the project, the XML input message is put in the input local queue. Click the databaseOperation orchestration as highlighted in Figure 11. The orchestration details appear as shown in Figure 12.
    Figure 12. Orchestration details in WMC
    Orchestration details in WMC
  8. Now click Details as highlighted in Figure 12 to see the activities of the orchestration, which is shown in Figure 13. As a result, the EMPDTL Oracle table is now loaded.
    Figure 13. Activity summary of the orchestration in WMC
    Activity summary of the orchestration in WMC

Conclusion

This article series described how to:

  • Build an orchestration.
  • Configure the activities.
  • Validate and test the orchestration in Cast Iron Studio.
  • Publish and deploy the project into the Integration Appliance using the Web Management Console.
  • Run the project from the Integration Appliance.

Without any programming knowledge, you developed the integration solution using WebSphere Cast Iron. You configured the required activities, learned how application integration happens through Cast Iron, and learned how communication occurs between two different external systems. By performing the above activities, you can build an integration solution in days. This process may reduce the integration development cost significantly because the development approach is based on a simple configuration, not coding.

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=946254
ArticleTitle=Application integration with WebSphere Cast Iron Cloud Integration, Part 3: Publishing a project into the Integration Appliance
publish-date=09252013