Managing Master Data with webMethods OneData : Administering webMethods OneData : Configuring Environments : Building Environments from Other Environments
Building Environments from Other Environments
This technical note describes the options and functionality available in OneData to build, move and/or configure one environment from another.
Typical process flow in terms of physical repository changes and the associated configuration changes in a large organization implementing OneData is depicted below.
The options available to the user depend on the specific scenario at the client site. Some common scenarios are described below.
Scenario
Solution
The destination repository is empty and no tables have been created.
1. Export all the schemas from the source environment to the target environment.
2. In the metadata schema of the target environment, configure the connection parameters to the work and release schemas.
3. In the metadata of the target environment, remove any scheduled jobs that have been copied from the source environment by executing the script Quartz_Scheduler_Deletes.sql
Tables exist in the database of the target environment, but have not been imported into OneData.
1. Using Update Schema, import the tables into OneData.
2. Copy the metadata schema from the source environment to the target environment.
3. In the metadata of the target environment, remove any scheduled jobs that have been copied from the source environment by executing the script Quartz_Scheduler_Deletes.sql
4. In OneData, using the Connection Manager, configure the connection parameters for the work and release areas, as well as the other connections for this environment.
Tables exist in the target environment and have been imported into OneData, but have not yet been configured.
1. Copy the metadata schema from the source environment to the target environment.
2. In the metadata of the target environment, remove any scheduled jobs that have been copied from the source environment by executing the script Quartz_Scheduler_Deletes.sql
3. In OneData, using the Connection Manager, configure the connection parameters for the work and release areas, as well as the other connections for this environment.
The target environment exists and requires updates to synchronize it with configuration changes made in another environment.
Transfer metadata.
The target environment is not empty and you are not using any CASE tools
1. Copy the SQL from the work and release schemas of the source environment into the target environments.
2. Using Update Schema, import the objects into OneData.
3. Using OneData transfer metadata functionality, transfer the metadata from the source environment to the target environment.
4. Remove any scheduled jobs by unscheduling the job from the job center.
Copyright © 2011-2017 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback