Augmenting profiles using the Profile wizard

You can augment a WebSphere Application Server or WebSphere Application Server Network Deployment stand-alone server profile, deployment manager profile, or custom profile into a WebSphere Process Server profile of the same type using the Profile wizard graphical user interface (GUI).

Before you begin

Before using this procedure, ensure that:
  • You have reviewed the list of prerequisites for creating or augmenting a profile at Prerequisites for creating or augmenting profiles.
  • If you plan to augment a stand-alone server or custom profile, you determine if it has already been federated to a deployment manager:
    • If the profile you want to augment has already been federated to a deployment manager, you cannot augment it to a WebSphere Process Server profile using the Profile wizard. You must augment it manually by following the procedure in Augmenting a federated profile manually.
    • If the profile you want to augment has not already been federated to a deployment manager, when you do federate it via the addNode command later, the following must be true of the deployment manager with which it is federated in order for the augmentation to complete successfully:
      • It must be running.
      • It must use the default SOAP JMX connector type and the connector must be enabled.
      • It must have already been augmented into a WebSphere Process Server profile.
  • You shut down any servers associated with the profile you plan to augment.
Important: You cannot have two instances of the WebSphere Process Server Profile wizard or WebSphere Application Server or WebSphere Application Server Network Deployment Profile creation wizard running concurrently on one set of core product files. Attempts to create profiles concurrently result in a warning. If a warning panel is displayed, determine if there is another profile creation or augmentation action occurring.
  • If there is, you must wait until it completes.
  • If there is not, delete the file profileRegistry.xml_LOCK in the directory install_root/properties if it exists. You can then run the Profile wizard.
Important: The language of the Profile wizard is determined by the default language on the system. If the default language is not one of the supported languages, then English is used. You can override the system’s default language by starting the Profile wizard from the command line and using the java user.language setting to replace the default language, as follows:
  • Icon indicating Linux platforms Icon indicating UNIX platforms On Linux and UNIX platforms: install_root/java/bin/java -Duser.language=locale -cp install_root/bin/ProfileCreator_wbi/pcat.jar run
  • Icon indicating Windows platforms On Windows platforms: install_root\java\bin\java -Duser.language=locale -cp install_root\bin\ProfileCreator_wbi\pcat.jar run
For instance, to start the Profile wizard in the German language on a Linux system, type the following:
install_root/java/bin/java -Duser.language=de -cp install_root/  \
bin/ProfileCreator_wbi/pcat.jar run

Why and when to perform this task

Complete the following steps to augment a profile.

Steps for this task

  1. Start the WebSphere Process Server Profile wizard. You can start the wizard in several ways:
    • On all platforms, from the First Steps console. See Starting the First Steps console for how to start the First Steps console.
    • Icon indicating Windows platforms On Windows platforms: From the Windows Start menu, or by executing the command install_root\bin\ProfileCreator_wbi\pcatWindows.exe.
    • Icon indicating Linux platforms Icon indicating UNIX platforms On Linux and UNIX platforms: By executing the appropriate command in the install_root/bin/ProfileCreator_wbi directory. The name of the command varies by platform:
      • Icon indicating AIX platforms On AIX platforms: ./pcatAIX.bin
      • Icon indicating HP-UX platforms On HP-UX platforms: ./pcatHPUX.bin
      • Icon indicating Linux platforms On Linux x86 32-bit platforms: ./pcatLinux.bin
      • Icon indicating Linux platforms On Linux x86 64-bit platforms: ./pcat.bin
      • Icon indicating Linux platforms On Linux zSeries 31-bit and 64-bit platforms: ./pcatLinux390.bin
      • Icon indicating Linux platforms On Linux Power platforms: ./pcatLinuxPPC.bin
      • Icon indicating Solaris platforms On Solaris SPARC platforms: ./pcatSolaris.bin
      • Icon indicating Solaris platforms On Solaris x86 64-bit platforms: ./pcatSolarisx86_64.bin
    Important: Do not execute the similar pct command found in install_root/bin/ProfileCreator on Linux and UNIX platforms and install_root\bin\ProfileCreator on Windows platforms. This command creates WebSphere Application Server profiles -- not WebSphere Process Server profiles.
    The Welcome panel is displayed.
  2. In the Welcome panel, select Next.
    If an unfederated WebSphere Application Server or WebSphere Application Server Network Deployment profile exists for augmentation, one of two Existing profile detection panels is displayed. Do one of the following, depending on whether WebSphere Application Server or WebSphere Application Server Network Deployment is installed:
    • If WebSphere Application Server is installed, select Augment an existing WebSphere Application Server profile, highlight the profile to augment from the drop-down list, and select Next. Only unfederated stand-alone server profiles are displayed as selections. The profile you select to augment must be from the version of WebSphere Application Server on which WebSphere Process Server is installed. The Service Component Architecture configuration panel is displayed. Proceed to Configuring a stand-alone server profile to configure your stand-alone server profile.
    • If WebSphere Application Server Network Deployment is installed, select Augment an existing WebSphere Application Server profile and select Next. You must then choose which type of profile you want to augment from the Profile type selection panel. Proceed to step 3.
    Important: If an Existing profile detection panel is not displayed, no profile exists for augmentation. In this case, do not follow this procedure. Use the procedure described in Creating profiles using the Profile wizard.
  3. Select the radio button corresponding to the type of profile you want to augment. Select Next. The list of profile types includes only those types which have valid WebSphere Application Server Network Deployment profiles that can be augmented into WebSphere Process Server profiles. One of the following panels is displayed:
    • If you selected to augment a stand-alone server or deployment manager profile, the Profile augmentation selection panel is displayed. Proceed to step 5.
    • If you selected to augment a custom profile, the Custom profile augmentation considerations panel is displayed. Proceed to step 4.
  4. Review the conditions that the deployment manager associated with the custom node must meet for a successful augmentation of the custom node. Then select Next.
  5. Choose the profile you want to augment from the drop-down list. Select Next. One of the following panels is displayed:
    • If you are augmenting a stand-alone server or deployment manager profile, the Service Component Architecture configuration panel is displayed.
    • If you are augmenting a custom profile, the Database configuration panel is displayed.
  6. Proceed to one of the following topics to configure and complete augmentation of your profile.

Result

You are ready to configure your profile, which will define a new operating environment of the type you specified (stand-alone server, deployment manager, or managed node).


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)