A configuration archive (CAR) file captures the configuration of a stand-alone application server profile for later restoration. The CAR can help clone the original profile to another machine or system.
One particularly useful application of configuration archives occurs with the Installation Factory, which is available as of V6.0.2.5.
The Installation Factory allows for a previously exported configuration archive of an existing stand-alone application server profile to be bundled with an installation image, maintenance packages, and user files and scripts. The resulting bundle is a customized installation package, or CIP.
An installer can use an existing CIP to install an exact replica of a model application serving environment, with installed maintenance packages, configured profiles, and deployed applications. Configuration archive files are one of the key customizations that make CIPs so easy to use.
Configuration archives are available for use in a CIP only when WebSphere Application Server is at a maintenance level of V6.0.2.5 or higher. As you might expect, the configuration archive file must export from a system that is also at a maintenance level of V6.0.2.5 or higher.
See Creating customized CIP profiles from the command line for more information about restoring a configuration archive while creating a stand-alone application server profile.
The Profile Creation wizard augments the new stand-alone profile with the configuration archive and other customizations that are included in the CIP.
Related information
Developing and installing customized installation packages
Profile customization
Creating customized CIP profiles from the command line
Creating customized profiles
Commands for the AdminTask object