WebSphere Application Server Network Deployment, Version 6.0.x   Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
             [TIP: Focusing the table of contents and search results]

Profile customization

The Build definition wizard provides a way to include profile customizations which include scripts to run at profile creation or deletion, deploying one or more enterprise archive (EAR) files, and restoring one configuration archive (CAR) file.

EAR files are deployed with default deployment options. If you must deploy an EAR file with different options, 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 you can include as user files.

A configuration archive file is an exported configuration file from an existing stand-alone application server profile. Use the AdminTask command scripting interface to create the configuration archive.

Profile creation

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

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

If you are restoring a customized profile that uses messaging, you must 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

Identify 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 “undo” the customization actions that occurred at profile creation time. If there are any profile deletion time configuration actions to run, the cip_app_server_root/if_augmentingTemplates/deleteRegistry.xml file contains the configuration actions. The wasprofile command should normally unaugment any IF customized augments when deleting a profile.

Action Type

Identify the type of configuration action:
  • Run a script
  • Import a configuration archive
  • Deploy an enterprise archive

File Name

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

Directory Path

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

Failure Action

Identify what action to take if a script fails or a file fails to load. Valid choices include:
  • 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)
  • [Windows] Windows batch files (*.bat)
  • Shell scripts (*.sh)
  • JAR files (.jar)
  • JACL scripts (.jacl)
  • Jython scripts (.py)
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 an application server 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.

Add configuration archives

Opens a browse dialog where you can search for and select a configuration archive file to include in the CIP for an application server profile.

A configuration archive file is an exported configuration file from an existing stand-alone application server profile. Use the AdminTask command scripting interface to create the configuration archive.

Creating a profile using the enhanced Profile Creation wizard in the CIP automatically restores the configuration archive. Each stand-alone application server profile that you create with the CIP tool creates a profile with the restored configuration archive. Use the Profile Creation wizard under the under app_server_root/bin/ProfileCreator directory to create a stand-alone Application Server without the configuration archive.

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

See Creating customized CIP profiles from the command line for information about using the command line to create and restore profiles when you cannot use the enhanced Profile Creation wizard in the CIP.

See Administrative command invocation syntax for a description of using an administrative command. See Commands for the AdminTask object for a description of the exportServer, exportWasprofile, importServer, and importWasprofile commands that are available for the AdminTask object.

Modify

Select an entry and click Modify to change 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

Move a script, enterprise archive file, or the configuration archive file up in the list to make it run earlier than other actions below it.

Move Down

Move a script, enterprise archive file, or the configuration archive file down in the list to make it run after other actions above it.




Related information
Build Definition wizard panels
Install and uninstall scripts
Additional files
Using configuration archive files in customized CIP profiles
Creating customized CIP profiles from the command line
Developing and installing customized installation packages
Reference topic    

Terms of Use | Feedback

Last updated: Mar 8, 2007 8:14:28 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/uins_ifactory12.html

© Copyright IBM Corporation 2005, 2006. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)