Deploying Cartridge Projects from the Environment Perspective

You deploy Oracle Communications Design Studio cartridge projects from the Environment perspective.

Note:

Design Studio is not intended for automated deployment or production environment deployment. See Design Studio Developer's Guide for more information about deploying cartridge projects to production environments.

Before you can deploy cartridge projects from the Environment perspective, you must create at least one Environment project, which enables you to organize your environment attributes. See "Working with Environment Projects" for more information.

To deploy cartridge projects from the Environment perspective:

1. Build the cartridge project.

   Builds detect errors in cartridge projects. You must resolve all errors in a cartridge project before you can deploy the cartridge project.

2. Determine which entities, libraries, and resources to include in the cartridge project.

   See "Packaging Projects" for more information.

3. Select Studio, then select Show Environment Perspective.

   An Environment perspective is a collection of views that enable you to create and manage the attributes associated with your environment. You use the Environment perspective to deploy and undeploy cartridges to one or more environments and to control and manage all of your environments. See "Working with Perspectives" for more information.

4. Do one of the following:

   • Create a new run-time environment if no environments exist. See "Creating Run-Time Environments" for more information.

   • Select an existing run-time environment to which to connect.

   The Cartridge Management view displays the selected environment information obtained from the most recent queried state.

5. Test the run-time environment connectivity.

   See "Testing Run-Time Environment Connectivity" for more information.

6. Define any environment-specific variables for the test environment.

   When you create Cartridge projects, some of the information you provide may depend on a specific environment. Model variables are placeholders for environment-specific values that can be defined at the time of deployment. See "Working with Model Variables" for more information.

   Cartridge management variables control attributes of the deployment and attributes of the project behavior after you deploy to the target environment. See the list of application-specific topics in the note below for more information.

   Note:

   Some Design Studio applications require that you define cartridge management variables before you deploy cartridges. The following topics provide more information:

   • Design Studio for ASAP Cartridge Management Variables Tab

   • Design Studio for Inventory Cartridge Management Variables Tab

   • Design Studio for Network Integrity Cartridge Management Variables Tab

   • About OSM Cartridge Management Variables

7. In the Cartridge Management view, select the cartridge projects to be deployed.

   If you select multiple projects, they are deployed individually, based on any existing dependencies. Oracle recommends that you deploy all run-time dependent projects to the run-time environment prior to or concurrent with any project that references them.

8. Click Deploy.

   Design Studio queries the environment for the current state of the deployed cartridges, and validates dependencies before deploying the cartridge projects. If a cartridge project defined as a run-time dependency does not exist in the target environment, Design Studio displays a warning. See "Project Editor Dependency Tab" for more information about defining dependency types.

   If the deployment fails, a message describing the reason for the failure and how to correct it appears in the Console view. If an error occurs during a deployment in which you have selected multiple projects, the system stops deployment for all subsequent projects. If you cancel the deployment, the system attempts to cancel the current deployment, and then cancels all subsequent deployments.

9. (Optional) Click Query.

   You can query the environment at any time to view the current system state.