About configurations

You publish a project to the Integration Appliance. The WMC then runs a configuration of the project. Once you publish a project to an Integration Appliance, the WMC creates a default project configuration. The default project configuration settings enable all orchestration in the project and allow you to quickly deploy a project.

You can create numerous configurations of the same project on your Integration Appliance. Each configuration can connect to a different endpoint, if you have used configuration properties to specify the connection information for the endpoint. For example, one configuration could connect to a test database while another configuration connects a production database. Project configurations are created using the WMC, and by default, are not deployed when they are created.

Publishing

Publishing is the process of bundling up a specific integration project (the named project in Studio) and preparing the project for deployment on an Integration Appliance. When you publish a project, Studio creates a runnable version of the project and sends it to the Integration Appliance that you specify.
Exporting
Exporting is a process very similar to publishing in that it compresses your project, but instead of pushing the result to the Integration Appliance, you give the file a name and save it for subsequent uploading to the Integration Appliance. For example, this allows for additional testing by a quality control team.
Uploading
Uploading is the process of moving a project that has been exported from Studio to the Integration Appliance. A menu selection is available for this task in the WMC.

Deploying

Deploying is the process of instantiating all the runtime components necessary so that the Integration Appliance can perform the actual integration. Deploying presumes that a project has been published or uploaded to the Integration Appliance. Use the Web Management Console to deploy a project configuration.

Understanding configuration properties

Configuration Properties simplify the deployment process in moving from a development environment to a production environment. Rather than hard-code configuration details into the endpoint properties, you can create Configuration Properties, and then use these property names in the configuration pages of your endpoints.

This is because endpoints created in Studio are configured with specific address information (hostname, IP address) and other details (user account, password). These details may need to be changed at deployment for the specifics of the actual environment in which the project will run (assuming that the development, test, and production environments use different servers and systems).

At deployment , the values associated with the properties can be changed to the appropriate hostnames, IP addresses etc.

For more information about creating configuration properties, see the Studio online help.




Feedback | Notices


Timestamp icon Last updated: Tuesday, 27 September 2016


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