Skip to content
View as markdown Ask ChatGPT Ask Claude

Cross-Version Deployment#

Estimated time to read: 7 minutes

Overview#

This scenario builds on the Same-Version Deployment flow by distributing a new Change Package from Porto - CoE, which runs MES version 12.0, to two destinations:

  • Dresden - Development, which runs MES version 12.0 and uses automatic approval and deployment.
  • Tijuana - Production, which runs MES version 11.3 and requires manual approval before automatic deployment.

You configure a Master Data Deployment Plan for multiple destinations with different MES versions and approval settings, publish the Change Package, and verify the deployment results in both destination environments.

Info

When a destination runs a different MES version, the Global Data Orchestrator automatically converts the package during deployment if needed. The package contents must be compatible with the destination version.

Before You Start#

Review the Same-Version Deployment scenario and complete the Prerequisites before starting.

Confirm the following additional conditions:

  • A destination Customer Environment with version 11.3 is registered in Customer Portal and reachable.
  • The Private Key Secret Name configured in the Master Data Deployment Plan must resolve correctly in both destination environments.
  • The Belgas [A] BOM and its dependencies are prepared in the source Customer Environment. Use them to create the new Change Package.

Destination MES Version Considerations

This tutorial uses MES version 11.3 as an example destination. It may work when the package contents are compatible, but this is not an officially supported destination version. Official support is limited to Long-Term Support (LTS) versions.

MES versions earlier than 12.0 do not support Owner Instance management or property-level Local Overrides settings. They also lack the additional Global Data Orchestrator fields in the Master Data Package entity. For more information about object ownership, see Manage Object Ownership.

When a Change Package contains Flows, destinations running MES version 11.0 or later support child Flows and Steps at the same level. MES version 10.2 can also receive Flows, but each Flow level must contain either child Flows or Steps, not both.

Step 1: Create the Master Data Deployment Plan#

Create a new Master Data Deployment Plan for this scenario.

  1. Sign in to Customer Portal, open the Global Data Orchestrator, and select Master Data Deployment Plans.

  2. Select New from the action bar. Enter the following values:

    • Name: Deployment_Plan_02.
    • Customer: CMF.
    • Error Handling Mode: Continue.

  3. Select Create.

  4. Select next to the source Customer Environment to add a Master Data Deployment Plan Item.

    Screenshot showing how to add a new Master Data Deployment Plan Item.

  5. Configure one Master Data Deployment Plan Item for Dresden - Development. Leave the default Approval Mode and Deployment Mode values as Auto.

  6. Configure the second Master Data Deployment Plan Item for Tijuana - Production. Set Approval Mode to Manual and leave the default Deployment Mode value as Auto.

    Screenshot showing the Edit Master Data Deployment Plan Item wizard.

  7. Select Save on the action bar, then select Request Approval, followed by Set Effective. The Master Data Deployment Plan must be in the Effective state before you can select it when creating the Change Package.

    Screenshot showing the Master Data Deployment Plan in the effective state.

Step 2: Create and Publish the Change Package#

Repeat the following linked steps from the Same-Version Deployment scenario. When creating the Change Package, use these values:

  1. Create a Change Package.

    • Name: Change_Package_02.
    • Type: General.
    • Master Data Deployment Plan: Deployment_Plan_02.
    • Publication Mode: Manual.
    • Release Notes: Release Notes for the second Change Package.

  2. Add Change Package Items.

    • Contents: Add the Belgas [A] BOM and its dependencies.

  3. Optionally, verify the contents.

  4. Approve and Publish the Change Package.

Screenshot showing the second Change Package ready for publication.

Step 3: Confirm Transport Package Creation#

  1. Open the Global Data Orchestrator in Customer Portal and access Transport Package.

  2. Locate the Transport Package created from Change_Package_02.

    Screenshot showing the created Transport Package in Customer Portal.

Step 4: Monitor and Approve the Deployments#

  1. Open the Global Data Orchestrator and access the Deployment Plan Instances page.
  2. Open the Instance created by the Master Data Deployment Plan in Step 1 (Deployment_Plan_02_1).
  3. Confirm that the Master Data Deployment Instance Item for Dresden - Development has reached the Completed state.
  4. Confirm that the Master Data Deployment Instance Item for Tijuana - Production is in the Waiting For Approval state.

  5. Select Approve from the action bar or from the Action column for Tijuana - Production.

    Screenshot showing the Master Data Deployment Instance Item and the Approve option in the top ribbon.

  6. Select Approve to continue with the deployment.

    Screenshot showing the Approval wizard for the Master Data Deployment Plan.

    After approval, the package is converted for MES version 11.3 and deployed automatically to Tijuana - Production.

  7. Monitor the deployment result until both instance items reach the Completed state. Use either view to review the result:

    In the Details view, review the state of each destination in the Instance Items section. To open an item's deployment log, select in its Logs column.

    Screenshot showing both destination instance items in the Completed state and their Logs actions in the Details view.

    Go to Views and select Diagram. Review the state of each destination in the diagram. Select a destination to see additional information in the Details panel.

    Screenshot showing both destinations in the Completed state and additional information for Tijuana - Production in the Diagram view.

    When both items reach the Completed state, deployment to both destinations is complete.

Step 5: Validate Both Destinations#

  1. Confirm that the generated Master Data Package appears in the destination environment.

    Screenshot showing the generated Master Data Package in the version 12.0 destination environment.

  2. Open the Master Data Package and confirm on the Execution tab that the load completed successfully without errors.

    Screenshot showing the successful execution of the Master Data Package in the version 12.0 destination environment.

  3. Optionally, check the operation result under Execution Details in the Details tab.

    Screenshot showing the operation result of the Master Data Package in version 12.0 destination environment.

  4. Optionally, open the imported object and check its Owner Instance. For more information, see Manage Object Ownership.

    Screenshot showing the Owner Instance of the BOM imported through the Global Data Orchestrator in MES version 12.0.

  1. Confirm that the generated Master Data Package appears in the destination environment.

    Screenshot showing the generated Master Data Package in the version 11.3 destination environment.

  2. Open the Master Data Package and confirm on the Execution view that the load completed successfully without errors.

    Screenshot showing the successful execution of the Master Data Package in the version 11.3 destination environment.

  3. Optionally, verify the operation result in Execution Details within the Details view.

    Screenshot showing the operation result of the Master Data Package in version 11.3 destination environment.

What You Learned#

This scenario routes a Change Package from a source running MES version 12.0 to destinations running MES versions 12.0 and 11.3. The version 12.0 destination uses automatic approval and deployment, while the version 11.3 destination requires manual approval.

Destination MES version Approval mode Deployment mode Expected result
Dresden - Development 12.0 Auto Auto The package is approved and deployed without user intervention.
Tijuana - Production 11.3 Manual Auto The package waits for approval, then deploys automatically after approval.

Table: Expected deployment behavior for each destination

Next Scenario#

Continue to Role-Based Approval and Deployment scenario to control who approves and deploys a package at a new destination.