IBM BPM, V8.0.1, All platforms > Administer the IT infrastructure > Administer deployment environments
Importing deployment environment definitions using the command line
You can import deployment environment definitions using wsadmin.sh. You can use wsadmin.sh 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 dmgr freeing the administrative console for other tasks and enables you to replicate working configurations to other dmgrs.
- You must have a copy of the exported deployment environment definition.
- You must be at the dmgr to which you are importing the deployment environment definition.
- Verify that a deployment environment with the same name as the deployment environment definition you are importing does not exist on this dmgr.
- The dmgr from which you are importing the deployment environment definition must at least support all the functions defined in the deployment environment design.
For example, you can import a deployment environment created on aWebSphere Enterprise Service Bus dmgr into an IBM BPM deployment environment, but not the reverse.
When security and role-based authorization are enabled, use a userid and password with administrator or operator authority to perform 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 designs; using wsadmin reduces the time for performing the task.
Procedure
- Open a command window.
The wsadmin command can be found at either the <WPS>/profiles/ dmgr_profile/bin directory, or the <WPS>/bin directory.
Telnet into UNIX System Services.
- Copy the deployment environment definition XML file you are importing to the system.
Copy the deployment environment definition XML file you are importing to your chosen directory
- Enter the wsadmin command to enter the wsadmin environment. Enter the wsadmin.sh command from the WAS_HOME/profiles/ dmgr_profile/bin or the WAS_HOME/bin directory.
- Use the importDeploymentEnvDef command to import the deployment environment definition from the file you just copied to the dmgr. You can rename the deployment environment when you import it.
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 dmgr 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}
wsadmin.sh -connType SOAP -host myDmgr -port 8879 -user dmgrAdmin -password -dmgrPass > $AdminTask importDeploymentEnvDef {-filePath /dmgr01/importedEnvironments/myDepEnv.xml -topologyName eastDepEnv}The -connType parameter specifies the type of connection to be used; the default argument is SOAP.
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.
If the node is running on the local host, you do not need to specify -host
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.
Administer deployment environments
Related information:
Generate deployment environments using the command line
Manage node agents
importDeploymentEnvDef command