Overview of Configuring Deployment Management

Deployment Management can be configured using the following steps.

  • Step 1: Gather process requirements.

    You should collect specific information concerning your process, the types of objects to be deployed, source and destination environments, and so on.

    For detailed information, see Gathering Process Requirements. For worksheets to help gather the information required to build a deployment system, see Worksheets.

  • Step 2: Configure workflows.

    Configuring workflows involves setting up the required workflow steps (decision and execution), adding transitions between the steps, and configuring each workflow step for notifications, security groups, segregation of duties, and so on. For information on how to configure workflows, see Configure workflows and Configuring Workflow Components. For configuration requirements for Deployment Management’s release process, see Configuring Releases and Distributions. For worksheets to help gather the information required to configure a workflow, see Worksheets.

  • Step 3: Configure object types.

    Object types define the technical step or steps required to "copy" a change from one environment to another environment. For information on how to configure object types, see Configuring Object Types. For worksheets to help gather the information required to configure an object type, see Worksheets.

  • Step 4: Configure environments.

    Configuring environments requires defining the server and database instances identified by your business or deployment process. For details about how to configure environments, environment groups, and environment refreshes, see Configuring Environments.

  • Step 5: Configure notification templates.

    Notification templates are preconfigured notification "formats" used by other Deployment Management entities, such as workflows, object types, and environments. Configuring Notification TemplatesConfiguring Notification Templates provides information on how to configure notification templates.

  • Step 6: Configure user data fields.

    User data fields add customized data fields used by other Deployment Management entities, such as workflows, object types, and environments. Configuring User Data discusses how to configure these user data fields.

  • Step 7: Configure your security and access requirements.

    Part of any migration or deployment process are the permissions required to perform various decisions or executions. Two of the ways in which PPM controls access to perform these decisions or executions are by licenses and access grants.

    • Licenses: Provide users with access to a PPMproduct such as Deployment Management, but they do not dictate what actions the users can perform.

    • Access Grants: When used with licenses, Access Grants define the actions a user can perform within a PPM product.

    For more information concerning security and access grants, see the Security Model Guide and Reference.

  • Step 8: Educate your deployment system users.

    After your Deployment Management system is configured and tested, you should train your users on the new business process. The following offer some guidance on how to educate your Deployment Management system users:

    • Basic Deployment Management training. Ensure that each user understands how to create, process, and report on packages.

    • Process-specific training. Ensure that each user understands the new process. Consider holding a formal meeting or publishing documents on the workflow steps and packages.

    • User responsibilities. Ensure that users understand their individual roles in the process. For example, the QA team may be restricted to approving the testing phase of a package. You can use email notifications that are part of Deployment Management to communicate information about user roles. Notifications can be very detailed, informing the recipients of their responsibilities.