environment.mode=provision|migration
When applying a template in provision or migration mode, Command Central executes the following steps. Some steps are only executed in migration mode.
Step 1
Validates the composite template, as described in the
Validating a Composite Template topic.
Step 2
Processes the layers in the source environment. This step applies only when the environment.mode argument of the apply composite template command is set to environment.mode=migration. Command Central prepares the source environment for migration.
The layers are processed one at a time, starting from the first layer defined in the template and going down the list of layers. For example if the layers section defines um, is, and mws layers, the processing starts with the um layer. Command Central goes through the following processing steps for each layer in turn:
1. Identifies the target set of nodes from the provision/environment.type/layerAlias section of the template definition.
2. Identifies the source nodes from the migration/source/environment.type section. If the source nodes are not defined in this section, by default Command Central uses the same set of nodes as both source and target nodes.
Note:
When the template included a migration/source/default section, but does not have migration/source/environment.type sections, if evironment.type sections exist for the target nodes, the template will again use the properties defined for the target nodes, instead of the migration/source/default properties.
3. Identifies the host, port, and installation directory of the source nodes from the migration/nodes/environment.type/node.alias section. If no properties are specified in the node.alias section, Command Central uses the values for host, port, and installation directory specified for the target nodes in the top level nodes section.
4. Prepares each source node for migration. By default, the following processing steps are executed in parallel for all source nodes:
Tip:
You can customize the migration settings in the migration/options section.
a. Create a template with products, fixes, configuration, and files from each source node.
b. PAUSE all run-time components:
If the PAUSE operation is not supported, the run-time component returns an error, which is ignored.
If the PAUSE operation is successful,
Command Central waits for the run-time component to report PAUSED status.
c. Shut down all run-time components, including Platform Manager.
Note that you can set the shutdown option to false only when migrating to a different host on a Unix operating system. For all other types of migration, this option is set to true.
d. Rename the source installation directory to migration_source_installDir when migrating on the same host and installation directory.
At the end of the source environment processing step, each layer has a template.
Step 3
Bootstraps Platform Manager on the target nodes.
The bootstrap operation is executed for all layers and runs in parallel on all target nodes. The target set of nodes is identified from the provisioning/environment.type sections.
At the end of the bootstrap processing step, Platform Manager is installed on all target nodes.
Step 4
Provisions or migrates all layers to the target nodes. Command Central identifies the nodes, on which to provision or migrate a layer, from the provision/environment.type section.
The layers are processed one at a time, starting from the first layer defined in the template and going down the list of layers. For example if the layers section defines is, mws, and um layers, the processing starts with the is layer. Command Central goes through the following processing sub-steps for each layer in turn:
1. Applies each layer on the target nodes to which the layer maps in the provision section. The nodes get processed one node at a time. Command Central maps the source nodes to the target nodes using the node alias.
2. Applies the inline templates listed for each layer.
At the end of the layers processing step, each layer is applied on the specified target nodes.
Step 5
Installs products and fixes from the inline templates defined in the composite template as follows:
1. Install products, including the Platform Manager product plug-ins.
2. Install all current fixes for the installed products and plug-ins.
At the end of the product and fixes provisioning step, the products and fixes included in the templates are installed on the target nodes.
Step 6
Creates, updates, or migrates the product instances from the templates defined in the composite template. Command Central migrates each product instance using the migration utility of the product. For details about the product instance properties that you can migrate with a template and how they map to the migration settings of the product migration utilities, see "Migrating a Product Instance".
After creating or migrating a product instance, Command Central updates the product instance with the required fixes.
Step 7
Processes files that are defined inline and applies configuration settings.
To configure the products, Command Central goes through the following sub-processing steps for each layer in turn:
1. Apply the configuration properties defined for each run-time component.
2. If a configuration property requires a restart of the run-time component, the component reports PENDING_RESTART status.
3. Platform Manager restarts only the run-time components that report PENDING_RESTART.
4. Start all run-time components created from all inline templates in a layer and wait for the components to start running with ONLINE status.
Command Central repeats the same steps for the next layer defined in the template. For example, if the layers section defines um and is layers, Command Central applies the configuration properties for the products in the um layer and waits for all run-time components in the um layer to start, before moving on to apply configuration on the run-time components in the is layer.