Create customized CIP profiles

 

+

Search Tips   |   Advanced Search

 

 

Overview

The Installation Factory allows for customized installation packages to be created that bundle...

• Installation image
• Maintenance packages
• Stand-alone appserver configuration archives
• EARs
• User files
• Scripts

The resulting bundle is a customized installation package (CIP).

The installer can use the Profile Management or manageprofiles tools to automatically restore profile customizations included in the CIP

If you cannot use the Profile Management tool, use the manageprofiles command to restore the customized profiles

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 SIB. The original SIB configuration is not portable and, therefore, is not included in the CIP.

 

Procedure

1. Install WAS V6.x.

2. Creates a default stand-alone appserver profile

3. Deploy applications

4. Make other configuration changes.

5. Create a configuration archive (CAR) of the default profile...

   wsadmin -conntype NONE -c "$AdminTask exportWasprofile {-archive myarchive.car}

6. Use the Installation Factory to create a CIP that includes the 6.x product image, refresh packs, and fix packs.

7. Include scripts to run during install time or uninstall time.

8. Include the CAR in the CIP

9. Include EARs for any of the four types of profile customization...
   • cell
   • stand-alone
   • deployment manager
   • managed

10. 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
    • federated appserver

11. Includes any additional files to be installed on the system.

12. Distribute the CIP to installers

13. Installers install the CIP.

14. 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.

15. 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 WAS 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 CAR is present, it will be automatically restored.

A CAR is available for an appserver CIP profile only. A special profile template enables the importation of a CAR file into the appserver profile. Use the Profile Management tool to create CIP profiles that accept configuration actions that are included in the CIP. Use the appserver CIP profile when you are restoring a CAR 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 CAR, 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.

 

Allowed customizations

CIP profile type	Run scripts	Deploy EAR	Restore CAR
Cell (dmgr and managed node)	Yes	No	No
dmgr	Yes	No	No
Stand-alone appserver	Yes	Yes	Yes
Custom (managed profile)	Yes	No	No

 

Options

• Create and augment an appserver profile that includes a CAR file.

  The Profile Management tool automatically augments the profile with any customizations that exist for the default appserver profile.

• Create and augment an appserver profile that does not include a CAR file.

  Choose the appserver profile in the enhanced Profile Management tool. The Profile Management tool uses the appropriate profile to create an appserver 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 appserver to test your applications.

---

 

Related information

Developing customized installation packages
Profile customization
Use CAR files in customized CIP profiles
Creating customized CIP profiles from the command line
startNode command
startManager command
startServer command