CIP profile customization

The Build definition wizard provides a way to include profile customizations that include scripts to run at profile creation or deletion, deploying one or more EAR files, adding business level applications, and restoring one configuration archive file.

EAR files are deployed with default deployment options. If you must deploy an EAR file with different options, then simply include the EAR file as a user file. Then include a script to deploy the EAR file.

Scripts can run at profile creation or deletion time in the order you specify. A script can call other scripts that we can include as user files.

A configuration archive file (CAR) is an exported configuration file from an existing profile. Use the AdminTask command scripting interface to create the configuration archive.

We cannot restore a CAR enabled with a feature pack using a customized installation package (CIP). The only configuration archives that can be restored in a CIP are unaugmented standalone application server profiles. A CAR can only be restored into the same profile type in which it was exported.

Profile types

Target profile type the customizations will be applied on.

Select Allow creation of new profiles using the customizations to allow the Profile Management tool to list all available profile types to be created using the customizations.

Select Allow augmentation of existing profiles using the customizations to allow the Profile Management tool to list all available profiles to be augmented using the customizations.

For feature pack CIPs, the only profile type which can be augmented is a standalone dmgr.

Profile creation

Specifies scripts that run or files to include during profile creation or augmentation.

Perform such actions as running scripts, including and restoring configuration archives, including EAR files, and deploying applications within an EAR file.

If we 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.

Profile deletion

Specifies scripts that run when the profile is deleted or unaugmented.

At profile deletion time, the CIP can specify additional scripts to run. Generally, these scripts are needed to reverse the customization actions that occurred at profile creation time. If there are any profile deletion time configuration actions to run, then the /if_augmentingTemplates/deleteRegistry.xml file contains the configuration actions. The manageprofiles command typically unaugments any Installation Factory customized augments when deleting a profile.

Action Type

Configuration action type.

File Name

Specifies scripts, enterprise archive files, or the configuration archive file.

Directory Path

Directory that contains scripts, enterprise archive files, or the configuration archive file.

Failure Action Specifies what action to take if a script fails or a file cannot be loaded. The following choices are valid:

Add scripts

Opens a file browsing dialog window where we can search for and select scripts to include in the CIP. Scripts can be any of the following supported script types:

  • ANT scripts (*.ant)

    Specify failonerror="true" in your profile customization ANT scripts.

  • [Windows] <p> Windows batch files (*.bat)

  • [AIX]

    [HP-UX]

    [Linux]

    [Solaris] <p> Shell scripts (*.sh)

  • JAR files (.jar)

  • JACL scripts (.jacl)

  • Jython scripts (.py)

[iSeries]

The QEJBSVR user profile must have proper authority to the files and directories involved to run any customized scripts which read or write from the file system.

[HP-UX]

If you include any customized shell scripts for the HP-UX operating system, add #!/bin/sh as the first line of the script or the script will fail to run. This applies to all UNIX-based systems.

Add enterprise archives

Opens a browse dialog where we can search for and select an enterprise EAR file to include in the CIP for a standalone profile.

An EAR file is a enhanced Java™ archive (JAR) file, defined by the J2EE standard used to deploy J2EE applications to J2EE appservers. An EAR file contains enterprise beans, a deployment descriptor, and WAR files for individual Web apps.

Add BLA packages

Opens a browse dialog where we can search for and select a business level application (BLA) file to include in the CIP for a standalone profile.

A BLA is a definition of application composition that uses physical binaries to run the application business logic. It does not represent or contain the application binaries. This provides clean separation between administration of binaries and administration of application definition. A BLA is a configuration that is stored in WAS ND configuration repository.

Add configuration archives

Opens a browse dialog where we can search for and select a configuration archive file to include in the CIP for a standalone profile.

A configuration archive file is an exported configuration file from an existing standalone appserver profile or a DMZ Secure Proxy Server for IBM WAS profile. Use the AdminTask command scripting interface to create the configuration archive.

The configuration archive contains all of the configuration data for a standalone appserver, including security settings, resources, defined ports, and so on. The advantage of using a configuration archive is that this configuration, including any enterprise archive (EAR) files, can be reliably restored to multiple nodes. Importing a configuration archive also offers some performance advantages over creating a standalone appserver in the typical way.

See Creating customized CIP profiles from the command line for information about using the command line to create and restore profiles when we cannot use the Profile Management Tool in the CIP.

See Administrative command invocation syntax for a description of using an admin command. See Commands for AdminTask for a description of the exportWasprofile and importWasprofile commands that are available for AdminTask.

Modify

Specifies an entry that changes the file path and file name or the directory path and directory name.

Remove

Removes selected scripts, enterprise archive files, or the configuration archive file from the CIP.

Move Up

Moves a script, enterprise archive file, or the configuration archive file higher in the list to make that item run earlier than lower actions in the list.

Move Down

Moves a script, enterprise archive file, or the configuration archive file lower in the list to make that item run after higher actions in the list.


Related concepts

Related tasks

Related reference



Last updated Nov 11, 2010 1:01:09 PM CST