WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Creating customized profiles

The Installation Factory captures the configuration of an existing application server profile and bundles it with an installation image, maintenance packages, and user files and scripts. The resulting bundled model enivronment is a customized installation package, or CIP. An installer can use a CIP to install an exact replica of the model application serving environment, with identically installed maintenance packages, configured profiles, and deployed applications.

Before you begin

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

If you cannot use the Profile Creation wizard, use the wasprofile 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.

Configuration archives are available for use in a CIP only when WebSphere Application Server Network Deployment is bundled with maintenance at the V6.0.2.5 level or higher. As you might expect, the configuration archive file must export from a system that has maintenance applied at a maintenance level of V6.0.2.5 or higher.

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.

Why and when to perform this task

The series of configuration events for using a configuration archive and other CIP customizations is shown in the following V6.0.2.5 example:
  1. An expert installs Version 6.0.
  2. The expert installs Refresh Pack 2 (or higher) for V6.0 to raise the model system to the V6.0.2 maintenance level.
  3. The expert installs Fix Pack 5 or a later fix pack for V6.0.2 to raise the model system to the required V6.0.2.5 or later maintenance level.
  4. The expert creates a default (stand-alone application server) profile, deploys applications, and makes other configuration changes.
  5. The expert creates a configuration archive of the default profile using the AdminTask exportWasprofile command.
  6. The expert uses the Installation Factory to create a CIP that includes the 6.0 product image, the refresh pack, and the fix pack.
  7. The expert includes the configuration archive in the CIP when defining profile customizations for a stand-alone application server profile type.
  8. The expert creates the CIP.
  9. The expert distributes the CIP or copies of the CIP to any number of licensed installers who require the customized system for their users.
  10. An installer installs the CIP.
  11. An installer uses the enhanced Profile Creation wizard in the CIP to create an application server profile, which automatically restores the configuration archive. An installer can also use the wasprofile command to create the profile and restore any customizations manually.
Table 1. Profile Creation wizard locations and functions
Profile Creation wizard Location Creates Customized Profiles? Creates Normal Profiles?
Enhanced IF version Launch the Profile Creation wizard check box at the end of the CIP installation. (cip_app_server_root/ProfileCreator/) Yes No*
Enhanced IF version cip_app_server_root/ProfileCreator/ Yes No*
Product version cip_app_server_root/bin/ProfileCreator/ No Yes
Profile version cip_app_server_root/profiles/profile_name/bin/ProfileCreator/ No Yes
* The enhanced Profile Creation wizard exists only when there is a customization for a profile. If no customization exists, this enhanced Profile Creation wizard is not present in the CIP. In such a case, the checkbox at the end of the CIP installation wizard opens the normal Profile Creation wizard.

A configuration archive is available for an application server CIP profile only. A special profile template in V6.0.2.5 and later versions enables the importation of a configuration archive file into the application server profile.

Use the enhanced Profile Creation wizard to create profiles that accept configuration actions that are included in the CIP. Use the minimal default profile template to create an application server when you are restoring a configuration archive file. If the customizations do not restore a CAR, the normal application server template creates the application server profile. Either type of application server profile accepts other configuration actions in the CIP that might deploy EAR files and run scripts.

Table 2. Allowed customizations
CIP Profile Type Include and Run Scripts Include and Deploy an Enterprise Archive (EAR) Include and Restore a Configuration Archive (CAR)
Stand-alone application server

(default profile)

Yes Yes Yes
Deployment manager

(dmgr profile)

Yes No No
Custom

(managed profile)

Yes No No

Steps for this task

Result

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 for a profile template apply to any profiles that you create with the enhanced Profile Creation wizard.

To create a profile without the exact same customizations, in other words, a normal profile, use the normal product Profile Creation wizard in the cip_app_server_root\profiles\profile_name\bin\ProfileCreator directory.

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
Developing and installing customized installation packages
Profile customization
Configuration archive files
Creating customized CIP profiles from the command line
startNode command
startManager command
startServer command

Task topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_if_restore_car_gui.html

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