Creating customized CIP profiles from the command line

The Installation Factory allows for customized installation package (CIP) to be created that bundles an installation image, maintenance packages, previously exported stand-alone application server configuration archives, EARs, 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. Installers can use the specialized Profile creation wizard in the CIP to create a stand-alone application server, deployment manager, or managed profile, which automatically restores any profile customizations that are included in the CIP. If you cannot use the specialized Profile creation wizard, use the commands described in this topic to create pre-configured profiles.

 

Before you begin

The installer can use the enhanced Profile Creation wizard in the CIP to create profiles and automatically restore the profile customizations that are included in the CIP. Or, the installer can use the wasprofile command to perform the same tasks manually from the command line.

If you cannot use the enhanced Profile Creation wizard in the CIP to create and configure profiles, use the wasprofile command to perform the task, as described in this topic.

See Creating customized profiles for a description of using the enhanced Profile Creation wizard, which is a graphical user interface.

You must have previously installed a CIP to create CIP profiles and restore customizations that are included in the CIP.

Configuration archives are available for use in a CIP only when WAS Network Deployment is bundled with maintenance at the V6.0.2.5 level or higher. As you might expect, the configuration archive file must export from a system that has maintenance applied at a maintenance level of V6.0.2.5 or higher.

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.

 

About this task

The series of configuration events for using a configuration archive and other CIP customizations is shown in the following V6.x. example:

  1. An expert installs V6.x.
  2. The expert installs Refresh Pack 2 (or higher) for V6.x to raise the model system to the Version 6.x.2 maintenance level.
  3. The expert installs Fix Pack 5 or a later fix pack for V6.x.2 to raise the model system to the required V6.x.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.

    Note: The first steps above are optional and are only required if a configuration archive needs to be exported for inclusion in a CIP. If configuration archive customization is not required, then the steps above can be omitted.

  6. The expert uses the Installation Factory to create a CIP that includes the 6.x product image.

    The CIP optionally includes a refresh pack as well as a fix pack

    1. The expert optionally includes scripts to run during install time or uninstall time.
    2. The expert optionally includes the configuration archive in the CIP when configuration profile customization for the Stand Alone Application Server config.
    3. The expert optionally includes EARs for any of the three types of profile customization (stand-alone, deployment manager, managed).
    4. The expert optionally includes scripts for any of the three types of profile customization (stand-alone, deployment manager, managed) to run either at profile creation time or profile deletion time.
    5. The expert optionally includes additional files to be installed on the system.
  7. The expert distributes the CIP to installers who require the pre-configured system for their users.
  8. The installers install the CIP.
  9. The installers use the specialized Profile creation wizard in the CIP to create any of the profile types: cell, stand-alone application server, deployment manager, managed. If a the stand-alone profile is chosen and a configuration archive is present, it will be automatically restored.

A configuration archive is available for an application server CIP profile only. A special profile template enables the importation of a configuration archive file into the application server profile.

Use the enhanced Profile Creation wizard to create profiles that accept configuration actions that are included in the CIP. Use the minimal default profile template to create an application server when you are restoring a configuration archive file. If the customizations do not restore a CAR, the normal application server template creates the application server profile. Either type of application server profile accepts other configuration actions in the CIP that might deploy EAR files and run scripts.

Table 1. Allowed customizations
CIP Profile Type Include and Run Scripts Include and Deploy an Enterprise Archive (EAR) Include and Restore a Configuration Archive (CAR)
Deployment manager

(dmgr profile)

Yes No No
Stand-alone application server

(default profile)

Yes Yes Yes
Custom

(managed profile)

Yes No No

 

Procedure

 

Results

After creating a profile and applying the customizations, the target installation should have a profile that is fully configured in the manner as designed by the CIP creator. If a configuration archive was imported, then the target profile should be a fully configured clone of the source profile where the configuration archive was exported.

To create a profile without the exact same customizations, in other words, a normal profile, use the normal profile templates in the cip_app_server_root/profileTemplates directory and do not augment the profiles.

 

What to do next

After installing your customized system, install a Web server and plug-ins, if necessary, and start the deployment manager, the node agent, and the application server to test your applications.