WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Configuration archive files

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.

The series of configuration events for using a configuration archive and other CIP customizations is shown in the following V6.0.2.5 example:
  1. An expert installs Version 6.0.
  2. The expert installs Refresh Pack 2 (or higher) for V6.0 to raise the model system to the V6.0.2 maintenance level.
  3. The expert installs Fix Pack 5 or a later fix pack for V6.0.2 to raise the model system to the required V6.0.2.5 or later maintenance level.
  4. The expert creates a default (stand-alone application server) profile, deploys applications, and makes other configuration changes.
  5. The expert creates a configuration archive of the default profile using the AdminTask exportWasprofile command.
  6. The expert uses the Installation Factory to create a CIP that includes the 6.0 product image, the refresh pack, and the fix pack.
  7. The expert includes the configuration archive in the CIP when defining profile customizations for a stand-alone application server profile type.
  8. The expert creates the CIP.
  9. The expert distributes the CIP or copies of the CIP to any number of licensed installers who require the customized system for their users.
  10. An installer installs the CIP.
  11. An installer uses the enhanced Profile Creation wizard in the CIP to create an application server profile, which automatically restores the configuration archive. An installer can also use the wasprofile command to create the profile and restore any customizations manually.

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

Concept topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/cins_if_config_archive.html

© Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)