Commands for the ConfigArchiveOperations group of the AdminTask object
Use the Jython or Jacl scripting languages to configure servers in your environment. The commands and parameters in the ConfigArchiveOperations group can be used to export or import server configurations and entire cell configurations.
For more information about the AdminTask object, see the Commands for the AdminTask object article.
The following commands are available for the ConfigArchiveOperations group of the AdminTask object:
Command name: Description: Target object: Parameters and return values: Examples: exportServer Use the exportServer command to export the server configuration to a node that is defined in the configuration archive.
The exportServer command virtualizes the server configuration and exports a server to a configuration archive. This process breaks any existing associations between the server configurations in the configuration archive and the configurations in the system. This process also removes applications from the server that you specify, breaks the relationship between the server that you specify and the core group of the server, cluster, or service integration bus member.
The exportServer command exports the metadata file of the node where the server resides. Use this information later when you import the configuration archive to verify that the target node is compatible to the node from which you are exporting the server.ship.
None
- Parameters:
- -archive
- The fully qualified path of the exported configuration archive. (String, required)
- -nodeName
- The node name of the server. This parameter is only required when the server name is not unique across the cell. (String, optional)
- -serverName
- The server name. (String, required)
- Returns: None
Batch mode example usage:
Using Jacl
$AdminTask exportServer {-archive c:\myServer.ear -nodeName node1 -serverName server1}Using Jython string
AdminTask.exportServer('[-archive c:\myServer.ear -nodeName node1 -serverName server1]')
Interactive mode example usage:
Using Jacl
$AdminTask exportServer {-interactive}Using Jython string
AdminTask.exportServer ('[-interactive]')
importServer Use the importServer command to import a server that resides in a configuration archive to the system. This command imports all the server scope configurations defined in the configuration archive to system configuration.
None
- Parameters:
- -archive
- The fully qualified path of the configuration archive. (String, required)
- -nodeInArchive
- The node name of the server defined in the configuration archive. (String, optional if there is only one node defined in the configuration archive, required if there are multiple nodes defined in the configuration archive)
- -serverInArchive
- The name of the server defined in the configuration archive. (String, optional if there is only one server defined on the specified nodeInConfiguration archive, required if there are multiple servers defined under the specified nodeInConfiguration archive)
- -nodeName
- The node name where the server is imported. (String, optional if there is only one node)
- -serverName
- The server name where the server is imported. If the server name that you specify matches an existing server name under the node, an exception is created. (String, optional, default:serverInArchive)
- -coreGroup
- The core group name to which the server should belong. (String, optional)
- Returns: None
Batch mode example usage:
Using Jacl
$AdminTask importServer {-archive c:\myServer.ear -nodeInArchive node1 -serverInArchive server1}Using Jython string
AdminTask.importServer('[-archive c:\myServer.ear -nodeInArchive node1 -serverInArchive server1]')
Interactive mode example usage:
Using Jacl
$AdminTask importServer {-interactive}Using Jython string
AdminTask.importServer ('[-interactive]')
Related tasks
Using the AdminTask object for scripted administration Related reference
Commands for the AdminTask object