You can import deployment environment definitions using
the wsadmin command. You can use the wsadmin command
to perform the same definition-import task that you perform in the
administrative console. This capability allows you to use a script
to import many deployment environment definitions to a deployment
manager freeing the administrative console for other tasks and enables
you to replicate working configurations to other deployment managers.
Before you begin
- You must have a copy of the exported deployment environment definition.
- You must be at the deployment manager to which you are importing
the deployment environment definitions.
- Make sure that a deployment environment with the same name as
the deployment environment definition you are importing does not exist
on this deployment manager.
- The deployment manager importing the deployment environment definition
must at least support all the functions defined in the deployment
environment definition.
Required security role for this task: When security and role-based authorization are enabled,
you must use a userid and password with administrator or operator
authority to perform this task.
About this task
Use the command line to import deployment environment definitions
in the following situations:
- You must import multiple deployment environment definitions and
prefer to use the command line.
- You prefer to use the command line to import one deployment environment
definition as a template for multiple deployment environments.
- You must import a large number of deployment environment definitions;
using wsadmin reduces the time for performing the
task.
Procedure
- Open a command window.
The wsadmin command can be found at either the <ESB>/profiles/<dmgr
profile>/bin directory, or the <ESB>/bin directory.
- Copy the deployment environment definition file you are
importing to the system.
- Enter the wsadmin command to enter the wsadmin environment
- Use the importDeploymentEnvDef command
to import the deployment environment definition from the file you
just copied to the deployment manager. You can rename the
deployment environment when you import it.
Note: If administrative
security is on, you will be prompted for a user ID and password, if
you do not supply it in the command.
Example
This example imports the deployment environment myDepEnv
and renames it eastDepEnv on the deployment manager myDmgr with administrative
security enabled.
wsadmin -connType SOAP -host myDmgr -port 8879 -user dmgrAdmin -password -dmgrPass
> $AdminTask importDeploymentEnvDef {-filePath
c:/dmgr01/importedEnvironments/myDepEnv.xml -topologyName eastDepEnv}
The
-connType parameter specifies
the type of connection to be used; the default argument is
SOAP.
Note: As
the default is SOAP, you do not need to give explicitly
if SOAP is the connection type that is being used.
The
-host parameter specifies
the host used for the SOAP or RMI connection. The default value for
-host is
the local host.
Note: If the node is running on the local host, you
don not need to specify -host
Note: If
you disable administrative security, you do not need to specify a
user ID and password.
What to do next
Optiional: Validate
the imported deployment environments.