Use configuration archive files in customized CIP profiles

Use configuration archive files in customized CIP profiles

A configuration archive (CAR) file captures the configuration of a stand-alone appserver profile for later restoration. The CAR can help clone the original profile to another machine or system.
The Installation Factory allows for a previously exported configuration archive of an existing stand-alone appserver profile to be bundled with an installation image, maintenance packages, user files, and scripts. The resulting bundle is a customized installation package, or CIP.
A configuration archive file is an exported configuration file from an existing stand-alone appserver profile. Use the AdminTask command scripting interface to create the configuration archive. The configuration archive contains all of the configuration data for a stand-alone application server, including security settings, resources, and defined ports. Configuration archives allow one to restore a pre-configured, working, and tested stand-alone appserver configuration from a source machine to one or more target machines.
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, 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.

Related information

Developing and installing customized installation packages Creating customized CIP profiles
Creating customized CIP profiles from the command line
Commands for the AdminTask object
ConfigArchiveOperations command group for the AdminTask object