Using configuration archive files in customized CIP profiles

A Customized Installation Package (CIP) created with the Installation Factory can contain a previously exported configuration archive of an existing standalone application server profile to be bundled with an installation image, maintenance packages, user files, and scripts.

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

Note: Configuration archive import support is provided in CIPs that achieve a WebSphere Application Server maintenance level of 6.0.2.5 or higher.

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.

Use the AdminTask command scripting interface to create the configuration archive. See ConfigArchiveOperations command group for the AdminTask object for more information.

A CIP which includes a configuration archive can be used to install an exact replica of a model application serving environment with installed maintenance packages, configured profiles, and deployed applications. For this reason, the configuration archive support is one of the key customizations that make CIPs so powerful when creating large scale topologies.

If you are restoring a customized profile that uses messaging, you must also include a script to configure the service integration bus (SIB). The original SIB configuration is not portable and, therefore, is not included in the CIP.

Configuration archives are available for use in a CIP only when WebSphere Application Server is at a maintenance level of Version 6.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 Version 6.0.2.5 or higher.




Related tasks
Creating customized CIP profiles
Creating customized CIP profiles from the command line
Developing and installing customized installation packages
Related reference
Commands for the AdminTask object
ConfigArchiveOperations command group for the AdminTask object
Concept topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 9:00:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=cins_if_config_archive
File name: cins_if_config_archive.html