Create customized CIP profiles

Operating Systems: i5/OS
Personalize the table of contents and search results

Create customized CIP profiles

The Installation Factory allows for acustomized installation package (CIP) to be created that bundles an installation image, maintenance packages, previously exported standalone application server configuration archives, EARs, user files, and scripts. 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.

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

If you cannot use the Profile Management tool, use the manageprofiles command to restore the customized profiles as described in Creating customized CIP profiles from the command line.

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

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.

Overview

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

An expert installs V6.x.
The expert creates a default (stand-alone application server) profile, deploys applications, and makes other configuration changes.
The expert creates a configuration archive of the default profile using the wsadmin tool:
```
wsadmin -conntype NONE -c "$AdminTask exportWasprofile {-archive myarchive.car}
```
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.
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. You can only include EARs for any of the four types of profile customization (cell, stand-alone, deployment manager, managed).
4. You can include scripts for all profile types. For V6.1, you can also perform customization on the "cell" profile set, which includes two profiles: deployment manager and federated application server.
5. The expert optionally includes additional files to be installed on the system.
The expert distributes the CIP to installers who require the pre-configured system for their users.
The installers install the CIP.
The installers create any of the following profile types: cell, stand-alone application server, deployment manager, managed. If you are an installer, you can use one of the following methods to create the profile:
- After the CIP installation, run the Profile management tool.
- After the CIP installation, run the manageprofiles command once to do a create and augment.
- After the CIP installation, run the manageprofiles command twice sequentially to do a create and then an augment.
  Alternatively, you can run the manageprofiles command once to augment an existing profile.
- In a scratch installation, do the following within the CIP installation wizard:
  1. On the Install Sample Applications panel, select the Install profile customizations checkbox.
  2. On the WebSphere Application Server environments panel, select a profile that has profile customization defined.
    If the profile that you select has profile customization defined, then the installation wizard will effectively run the manageprofiles command once to do a create and augment. If there is no profile customization defined, you get a regular profile.
If 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 Profile Management tool to create CIP profiles that accept configuration actions that are included in the CIP. Use the application server CIP profile when you are restoring a configuration archive file or other customizations. The Profile Management tool can also create normal profiles that do not accept customizations.

When you run the Profile Management tool with CIP customized profiles installed, the Environment Selection panel will show environments with -- cip_uid at the end. These are the customized profiles, and each of them will create a regular profile and then apply the customizations through a profile augmentation. If the customized profile that you select contains a configuration archive, then it will be imported.
The first four environments listed on the Environment Selection panel, which do not have a -- cip_uid at the end, are the regular profile types. If you want a regular profile without customizations, select one of these.

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)

Cell
(deployment manager and a managed node)
Yes No No
Deployment manager
(dmgr profile)
Yes No No
Stand-alone application server
(default profile)
Yes Yes Yes
Custom
(managed profile)
Yes No No

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)
Cell (deployment manager and a managed node)	Yes	No	No
Deployment manager (dmgr profile)	Yes	No	No
Stand-alone application server (default profile)	Yes	Yes	Yes
Custom (managed profile)	Yes	No	No

Procedure

Create and augment an application server profile that includes a CAR file.
The Profile Management tool automatically augments the profile with any customizations that exist for the default application server profile.
Create and augment an application server profile that does not include a CAR file.
Choose the application server profile in the enhanced Profile Management tool. The Profile Management tool uses the appropriate profile to create an application server that does not require the CAR, but that still accepts other customizations.
The Profile Management tool automatically augments a CIP profile with any customizations that exist for the profile type.
Create and augment a deployment manager profile.
Choose the deployment manager CIP profile in the Profile Management tool.
The Profile Management tool automatically augments the CIP profile with any customizations that exist for the deployment manager.
Create and augment a custom profile.
Choose the custom CIP profile in the Profile Management tool.
The Profile Management tool automatically augments the CIP profile with any customizations that exist for the custom profile.

Results

After creating the profile and restoring the customizations, the installation should have a profile that is configured like the profile in the model product installation that was the pattern for the CIP. Existing customizations are used only when you create a CIP profile with the Profile Management tool.

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.

}

Related information

Creating customized CIP profiles CIP profile customization
Using configuration archive files in customized CIP profiles
Creating customized CIP profiles from the command line
startNode command
startManager command
startServer command