WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Build Definition wizard: Profile customization panel

You can use the profile customization panel to run scripts at profile creation or deletion time. You can also deploy one or more enterprise archive file (EAR) file as part of profile augmentation.

You can use the profile customization panel to create customizations for one of three types of profile:
When you install the CIP, the Profile Management Tool will prompt you for the choice of profile type. In order to use the customizations that you define here, you must select the same type of profile on the Profile Management Tool as you do on the profile customization panel.
Note: Only deployment manager and custom can be selected when installing into a network deployment environment.
Note: You can deploy EAR files only with default options using the profile customization panel. If you need to deploy the EAR file with other options, include the EAR file as a user file and use a script to deploy the EAR with the necessary options.

Profile types

Select the type of profile for which you want to create customizations:
  • Stand-alone server
  • Deployment manager
  • Custom

Profile_type Profiles

In the section entitled Profile_type Profiles (where Profile_type is the type of profile you are working with) you can specify whether the Profile Management Tool displays options to use the customizations to create new profiles or augment existing profiles.
Note: Augmenting existing profiles is not supported.

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 your customizations.

Profile_type Customizations

In the section entitled Profile_type Customizations (where Profile_type is the type of profile you are working with) you can specify the customizations that you want to make on profile creation or deletion.

Profile creation

Specifies scripts that run or files to include after successfully installing the CIP.

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

Profile deletion

Specifies scripts that run when the profile is 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 cip_app_server_root/if_augmentingTemplates/deleteRegistry.xml file contains the configuration actions. The manageprofiles command typically unaugments any Installation Factory customized augments when deleting a profile.

cip_app_server_root
The following list shows the default installation root directories for a customized installation package (CIP) produced by the Installation Factory.

For AIX operating system /usr/IBM/WebSphere/ProcServer/cip/cip_uid

For HP-UX operating system /opt/IBM/WebSphere/ProcServer/cip/cip_uid

For Linux operating system /opt/ibm/WebSphere/ProcServer/cip/cip_uid

For Solaris operating system /opt/IBM/WebSphere/ProcServer/cip/cip_uid

For Windows operating system C:\Program Files\IBM\WebSphere\ProcServer\cip\cip_uid

For i5/OS operating system /QIBM/ProdData/WebSphere/ProcServer/V61/ND/cip/cip_uid

The cip_uid variable is the CIP unique ID generated during creation of the build definition file. You can override the generated value in the Build definition wizard. Use a unique value to allow multiple CIPs to install on the system.

Action Type

Specifies one of the following types of configuration actions:
  • Run a script
  • Deploy an enterprise archive. You will only be able to deploy an EAR file to a stand-alone server.

File Name

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

Directory Path

Specifies the 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:
  • Fatal error
  • Continue

Add scripts

Opens a file browsing dialog window where you can search for and select scripts to include in the CIP. Scripts can be any of the following supported script types:
  • ANT scripts (*.ant)
  • For Windows operating system Windows® batch files (*.bat)
  • For Linux operating systemFor UNIX operating systemFor i5/OS operating system Shell scripts (*.sh)
    Note: On i5/OS® the shell script does not have the .sh extension.
  • JAR files (.jar)
  • JACL scripts (.jacl)
  • Jython scripts (.py)
Note: The script that you add becomes specifically associated with the type of profile and the action (either creation or deletion) that you have selected on this panel. Hence you should select the type and event before adding the script.

Add enterprise archives

Opens a browse dialog where you can search for and select an enterprise application archive (EAR) file to include in the CIP for aWebSphere® ESB profile.

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


concept Concept topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/cins_if_builddef_profile_cust.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).