Augmenting WebSphere Application Server or WebSphere Application Server Network Deployment profiles

You can augment an existing WebSphere Application Server or WebSphere Application Server Network Deployment profile into a WebSphere Process Server profile by using the Profile wizard graphical user interface (GUI) interactively, or by using the manageprofiles command.

Why and when to perform this task

If you already have WebSphere Application Server or WebSphere Application Server Network Deployment profiles on the system on which you have installed WebSphere Process Server, you might want the operating environments defined by those profiles to have WebSphere Process Server functionality.

Decide whether to use the Profile wizard interactively or the manageprofiles command. The first time you augment a profile of a specific type, you must use the Profile wizard. This wizard writes the manageprofiles command used to augment the profile to a log file. Later, you can extract this command from the log file, carefully modify it, and use it to augment other similar profiles. However, the Profile wizard performs tasks that the manageprofiles command does not. (For example, it can create a Windows service for a stand-alone server or deployment manager; assign non-conflicting ports based on previous port assignments; and federate a custom profile to a deployment manager to create a managed node.)

Neither the Profile wizard not the manageprofiles command can be used to augment federated profiles. You must federate them manually using the instructions in Augmenting a federated profile manually. Plus, you must shut down any servers associated with the profile you plan to augment.


Last updated: Wed 01 Nov 2006 07:47:12

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