About Project Configurations

Project configurations allow you to create multiple variations of the same integration project, so you can create and publish one project and deploy it to many different scenarios. Within a project configuration you can specify which orchestrations are enabled, modify configuration properties for endpoints, generate or modify assets, manage scheduled downtime rules, and control permissions for the project configuration.

Each project you publish has a Default project configuration. In the Management Console, you can create additional project configurations. The project name, project version, configuration name, and project state uniquely identify each project configuration.

You must have Administrator privileges or be the publisher of the specific project to create, edit, and delete project configurations. Administrators and publishers can grant users and groups permissions that allow them to a create, edit, and delete project configurations.

Enabling and Disabling Orchestrations

The runtime only runs orchestration jobs for enabled orchestration. Before you can deploy a project configuration, the project configuration must contain at least one enabled orchestration. By default, all orchestrations are enabled.

Specifying the orchestration logging level allows you to control the type of orchestration errors that are written to the system logs. The Management Console also allows you to limit the number of jobs that run simultaneously. The number of jobs that run simultaneously can affect performance.

You must have administrator or publisher permissions to specify orchestration properties.

Understanding Configuration Properties

You create these configuration properties for a project in Studio. For more information about creating project properties and specifying a project version, see the Studio online help.

When you publish the project, you can specify values for the configuration properties. The values you specify for the configuration properties determine how the project is deployed. For example, in a project that contains database endpoints, you can create properties for database connection parameters. This allows you to create a project configuration for a test environment connecting to a test database and then use the same project to create another project configuration for a production environment that connects to another database.

You must have administrator or publisher permissions to edit configuration properties in the Management Console.

Modifying Assets

If your project configuration contains a database or WebServices endpoint, you must generate assets before you can deploy the project configuration. If your project does not contain a database or WebServices endpoint, assets are irrelevant to your project configuration.

You must have administrator or publisher permissions to generate or modify assets.

Scheduling Downtimes

Scheduling downtime allows you to perform maintenance. You can create downtime rules for project configurations that stop or suspend all enabled orchestration jobs in that project configuration for a specified duration of time. The project configuration does not have to be undeployed to create or edit a downtime rule. Downtime rules can occur once or repeat at specific intervals.

You must have administrator or publisher permissions to create, edit, or delete a downtime rule.

Editing Project Configuration Permissions

As an administrator or project publisher, you can grant permissions for project configurations to other users and groups. When you grant users or groups permissions to a project configuration they are able to create, edit, and delete the project configuration. By default, permissions to project configurations are granted to only the Administrator Group. If you want to grant permissions to another group you must explicitly do so.

For example, you are a user with publisher rights and belong to the built-in Publisher group. You publish a project. Only the Administrator Group and you have permissions to the project configuration. Members of the Publisher group, of which you are a member, do not have permissions to the project configuration. You must edit the permission on the project configuration to include another group like Publisher. For more information, see Granting Project Configuration Permissions.




Feedback | Notices


Timestamp icon Last updated: Friday, February 5, 2016


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.live.doc/Managing_Projects/aboutProjectConfigurations.html