WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Importing deployment environment definitions using the administrative console

You can import an existing deployment environment definition from another deployment manager to use as a base for configuring a new deployment environment.

Before you begin

Required security role for this task: When security and role-based authorization are enabled, you must log in to the administrative console as an administrator or operator to perform this task.
Important: You cannot import multiple deployment environment definitions from a compressed file at the same time. You must extract the definitions from the compressed file and then import the definitions one at a time.

About this task

Importing an existing deployment environment definition to create a new one can minimize the amount of time you spend configuring a deployment environment. If an existing environment is similar to the one you want to create, export it and then import it into the deployment manager you are configuring.
Procedure
  1. Click Import in the Deployment Environments page to launch the Deployment Environment Configuration wizard.

    The wizard starts with Load an external deployment environment definition selected.

  2. Click Browse to open a file dialog and select the deployment environment definition file to import or type the full path to it.
  3. Click Next to load the configuration and launch the Import deployment environment wizard.

    The wizard displays the Select Nodes page, unless all the node names match currently federated notes. If all nodes match, the wizard displays the Database page.

    Important: Clicking configure in any panel in the wizard configures the deployment environment with the current values.
  4. Optional: From the list of possible nodes on the Select Nodes page, select the nodes to include in the deployment environment and click Next.

    To include a node, select the check box next to the node name. Use Node Mapping to map the selected node to another node name.

    Important: Next is not be available if the nodes selected do not meet the constraints imposed by the imported deployment environment definition. For example, if there is a requirement for the deployment environment to contain a node named "Mandatory_Node" and 3 other nodes with any name, you will be unable to continue until you select "Mandatory_Node" and 3 other nodes.
  5. On the Database page, configure the databases for the deployment environment, then click Next.

    On this page, define the database information for the components that are included in this deployment environment. Where possible, the wizard supplies default information for the parameters, but change those values to match the values that you defined when you planned the environment.

  6. Verify that the information on the Summary page is correct and click Finish and Generate Environment to save and complete the configuration of the deployment environment. To exit without completing the configuration click, Finish.

Results

When the configuration completes, you can examine the configuration files to view the changes.

What to do next

Either save the changes to the master configuration or discard them.

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.zseries.doc/doc/tadm_import_top.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).