configuration archive file(CAR File) for IBM MDM

configuration archive file(CAR File)

A configuration archive (CAR) file captures the configuration of astandalone application server profile for later restoration on another application server node. The CAR can help clone the original profile to another machine or system.

A configuration archive file is an exported configuration file from an existing standalone application server profile and contains all application server configuration data including security settings, resources, defined ports, and so on. The advantage of using a CAR is that all of this configuration, including any enterprise archive (EAR) files, can be reliably restored to many application server nodes. Importing a configuration archive also offers some performance advantages over creating a standalone application server in the normal way.


The WebSphere Configuration Archive is new features in WebSphere Application Server v6.0.
This feature allows a set of complete or subset of WebSphere configuration archive. WebSphere
Application Server V6 provides a mechanism that allows you to export certain profiles, or server
objects from a profile, to an archive. The archive can be distributed and imported to other
installations. An exported archive is a zip file of the config directory with host-specific information
removed. The recommended extension of the zip file is .car. The exported archive can be the
complete configuration or a subset. Importing the archive creates the configurations defined in the
archive. The target configuration of an archive export / import can be a specific server or an entire
profile.
To use an archive you would:
1. Export a WebSphere configuration. This creates a zip file with the configuration.
2. Unzip the files for browsing or update for use on other systems. For example, you might need
to update resource references.
3. Send the configuration to the new system. An import can work with the zip file or with the
expanded format.
4. Import the archive. The import process requires that you identify the object in the configuration
you want to import and the target object in the existing configuration. The target can be the
same object type as the archive or its parent:
– If you import a server archive to a server configuration the configurations are merged.
– If you import a server archive to a node, the server is added to the node.
A tutorial on creating and using archives can be found in the Information Center. See
ftp://ftp.software.ibm.com/software/eod/was/6.0/SystemManagement/WASv6_SM_Configuration_
Archives/playershell.swf
Prof ile archives
The following command can be used to create an archive of a profile:
$AdminTask expor tWasprof ile {-archive }
You can only create an archive of an unfederated profile (standalone application server).
$AdminTask impor tWasprof ile {-archive }
exportWasprofile:
Use the exportWasprofile command to export the entire cell configuration to a configuration
archive. (myArchive.car)
• Using Jacl:
22 5/15/2006
$AdminTask exportWasprofile {-archive c:\myCell.ear}
• Using Jython string:
AdminTask.exportWasprofile('[-archive c:\myCell.ear]')
Interactive mode example usage:
• Using Jacl:
$AdminTask exportWasprofile {-interactive}
• Using Jython string:
AdminTask.exportWasprofile ('[-interactive]')
importWasprofile:
Use the importWasprofile command to import a cell configuration in the configuration archive to
the system. Only a base single server configuration is supported for this command.
• Using Jacl:
$AdminTask importWasprofile {-archive c:\myCell.ear}
• Using Jython string:
AdminTask.importWasprofile('[-archive c:\myCell.ear]')
Interactive mode example usage:
• Using Jacl:
$AdminTask importWasprofile {-interactive}
• Using Jython string:
AdminTask.importWasprofile ('[-interactive]')

ref: http://publib.boulder.ibm.com/infocenter/wasinfo