Deployment concepts

Use Studio to create integration projects, which you deploy to the Cloud using the Management Console or deploy to the Integration Appliance using the Web Management Console. A deployment of a project contains all runtime components necessary to run the processing defined in the orchestrations of the project.

With respect to deployment, there are two important concepts to keep in mind as you develop a project:
  • Publishing and Deploying are two distinct steps. Publishing is the act of promoting a project from Studio to an integration environment (cloud or Integration Appliance) or to another intermediate location. A project does not run in the integration environment until you deploy it.
  • Projects can have multiple configurations that support completely different environments (development, test, production). Using Studio to create configuration properties for projects offers greater flexibility at deployment time, because you can bind the properties to different environments.
The Integration Appliance provides the following two options for getting your projects from Studio to the Integration Appliance:
  • Projects can be published directly to an Integration Appliance.
  • Projects can be exported from Studio to a staging location and then uploaded to an Integration Appliance.

Whether you export from Studio and later upload to the Integration Appliance or publish directly to the Integration Appliance from Studio, the project does not run on the Integration Appliance until you deploy.




Feedback | Notices


Timestamp icon Last updated: Thursday, December 17, 2015


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.gettingstarted.doc/getstart_deploymentconcepts.html