Moving BMC Helix Multi-Cloud Broker data between environments
As an administrator, you can move BMC Helix Multi-Cloud Broker data from one environment to another environment. You can move the following types of data:
- Configuration data; for example, organization details, vendor metadata, BMC Helix Multi-Cloud Broker provider configuration in BMC Helix Multi-Cloud Broker
- Records and definitions from Ticket Brokering Library
- Processes from Ticket Brokering Library
For a quick overview of the different environments between which you can move data, see Moving-data-and-integration-projects-between-environments.
Example of moving data
Allen, an administrator in Apex Global, wants to integrate BMC Helix Multi-Cloud Broker with Jira to synchronize incidents and issues between the two applications. Allen and other users perform the following tasks in the development, QA, and production environments:
Development
- Allen adds the organization details.
- He adds the Jira metadata.
- He defines the following filter criteria to broker BMC Helix Multi-Cloud Broker incidents to Jira:
Priority=High - He moves the data from the development environment to the QA environment.
QA
- Allen adds the URL and credentials of the QA environment for BMC Helix Multi-Cloud Broker in the relevant project variables in the integration template.
This action ensures that when the integration is run, the variables use the QA environments to pass the data. - The QA team verifies the data.
After successful verification, they provide a sign-off to move the data to the production environment.
Production
- Allen moves the data to a production environment, and adds the host URL and credentials of the production environment in the integration template variables.
Process of moving data
The following image shows the process of moving BMC Helix Multi-Cloud Broker data between environments:
Before you begin
Make sure you have appropriate permissions to access Remedy Deployment Application.
To learn about the roles and permissions, see Deployment Application roles and permissions in the online Action Request System documentation.
To move data between environments
The following table lists the steps you need to perform in different environments and the associated information references in the online AR System documentation:
Step | Action | Reference |
|---|---|---|
Development environment | ||
1 | Define a package with data and processes that you want to move across environments. | |
2 | Specify rules to validate a package while it is being built. | |
3 | Export the validated package to your local machine and share the package with the deployment manager. | |
QA or Test environment | ||
4 | Import the package, load it in your test environment, and verify the package. | |
5 | Validate the package in your test environment to identify issues, if any. | |
6 | Deploy the package on your test environment. | |
7 | Test the package and when it is verified, export the package. | |
Production environment | ||
8 | Import the package from your local machine on the production environment. | |
9 | Validate the package in the production environment to identify issues, if any. | |
10 | When the package is validated successfully, deploy it on your production environment. | |
Alternatively, you can use a command-line interface (CLI) to move data between environments.
To learn about using a CLI, see Building and deploying packages by using the CLI.
Task to perform after moving the data
After you move the data, make sure you perform the following task:
Task | Where to perform | Example |
|---|---|---|
Add the host URL and credentials of the BMC Helix Multi-Cloud Broker environment in which you have moved the data. This ensures that when you run an integration template, it passes the data to the correct environment and the integration is successful. | Project variables in an integration template |
|
To verify that the data has moved
After you move the data to the target environment, make sure that all the data has moved successfully. To do this, review the data across the target environment; for example, verify the ServiceNow metadata by reviewing the Configure Vendor Metadata section and verify the Apex Global organization details by reviewing the Manage primary organizations section.
Manage Vendor Metadata section
Manage Primary Org section
Troubleshooting
After you complete the process of moving data, if you are unable to view certain data in the target environment, perform any of the following actions:
Action | UI |
|---|---|
Check if you have completed the task list while setting up an integration in Quick Configuration Guide. |
|
Check the Error Management console to view any errors that occurred while moving the data. |
|
Move the data again by using the Deployment Management Console. |
|
