Augmenting an existing WebSphere Application Server Network Deployment custom profile into a WebSphere Process Server custom profile

Use this procedure to augment an existing WebSphere Application Server Network Deployment custom profile into a WebSphere Process Server custom profile using the Profile Wizard graphical user interface (GUI).

Before you begin

Before using this procedure, ensure that:
  • You have an existing installation of WebSphere Process Server with an underlying installation of WebSphere Application Server Network Deployment. If you do not, see Installing the product for installation procedures.
  • You want to augment an existing WebSphere Application Server Network Deployment custom profile to a WebSphere Process Server custom profile, and that you want to do so interactively. The existing profile must be a WebSphere Application Server Network Deployment, version 6.0.0.x or 6.0.1.x profile.

    Icon indicating 6.0.1 content only If you are using WebSphere Process Server, version 6.0.1, you can also augment WebSphere Application Server Network Deployment, version 6.0.2.x profiles.

    See Creating and augmenting profiles by using the Profile Wizard for descriptions of other profile creation or augmentation procedures.

  • You have enough disk and temporary space to augment the profile. See Required disk space for the minimum disk space required.
  • If you have enabled global security on the installation of WebSphere Application Server Network Deployment which contains the profile you want to augment, you disable it before augmenting the profile. For information on enabling and disabling global security, see the WebSphere Application Server Network Deployment, version 6.0 information center at http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp.
  • If you plan to use DB2 Universal Database for your repository, you perform the following steps before augmenting the profile:
    • If you are configuring a DB2 database on a DB2 client with the server on a remote system, make sure the client system is configured to communicate with the server and that the DB2 node is cataloged. For more information, refer to the DB2 Universal Database documentation.
    • Icon indicating Linux platforms Icon indicating UNIX platforms On Linux and UNIX platforms: If you are configuring a DB2 database on a Linux or UNIX system, source the database environment by doing the following:
      1. Modify /etc/group and make sure root is in the same group as the db2instance.
      2. Source the database environment by running the db2instance/sqllib/db2profile script (replace db2instance with the name of your database instance).
  • You determine if the custom node you want to augment has already been federated to a deployment manager:
    • If the custom node 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 custom node 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.

Why and when to perform this task

To augment an existing WebSphere Application Server Network Deployment custom profile into a WebSphere Process Server custom profile, use the following procedure.

Steps for this task

  1. Log on as the root user on a Linux or UNIX system, or as a member of the Administrator group on a Windows system.
  2. Start the WebSphere Process Server Profile Wizard.

    See Starting the Profile Wizard for descriptions of the many ways to start the Profile Wizard on various platforms.

    The wizard loads the Java 2 SDK and then displays its Welcome panel.

  3. In the Welcome panel, select Next.
    If an unfederated WebSphere Application Server Network Deployment profile exists for augmentation, the Existing profile detection panel is displayed. Select the Augment an existing WebSphere Application Server profile radio button and select Next.
    Important: If an Existing profile detection panel is not displayed, no profile exists for augmentation. In this case, do not follow this procedure. Instead, cancel the augmentation and review the profile creation procedures described in Creating and augmenting profiles by using the Profile Wizard.
  4. In the Profile type selection panel, select the Custom profile radio button, then select Next.

    The list of profile types will include only those types which have valid WebSphere Application Server Network Deployment profiles that can be augmented into WebSphere Process Server profiles.

  5. In the Custom profile augmentation considerations panel, 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.
  6. In the Profile augmentation selection panel, choose the profile you want to augment from the drop-down list and select Next.

    The list includes only those profiles of the type selected. Only unfederated profiles are displayed as selections. The profile you select to augment must be from the version of WebSphere Application Server Network Deployment on which WebSphere Process Server is installed.

  7. In the Database configuration panel, configure database authentication.

    Configure database authentication by performing the following steps.

    1. Choose the database that matches the database used on the deployment manager to which this custom profile will be federated. Select the database from the list, or accept the default value of DB2 Universal.
      You can select the following databases from this panel (each entry that can be selected from the list is shown, followed by the database it represents):
      • DB2 Universal (DB2 Universal Database)
      • DB2 Universal OS/390 V7.1 (DB2 Universal Database for OS/390 V7.1)
      • DB2 Universal OS/390 V8.1 (DB2 Universal Database for OS/390 V8.1)
      • DB2 CLI (DB2 Call Level Interface)
      • Informix (Informix Dynamic Server)
      • MSSQL Server Embedded (Microsoft SQL Server Embedded)
      • MSSQL Server Data Direct (Microsoft SQL Server DataDirect)
      • Oracle OCI (Oracle OCI client)
      • Oracle Thin (Oracle Thin)

      If your selection is other than MSSQL Server Embedded, you must also provide the location of the JDBC driver class path files for the database. If your selection is DB2 Universal, you can accept the default value of install_root/universalDriver_wbi/lib on Linux and UNIX platforms or install_root\universalDriver_wbi\lib on Windows platforms.

    2. Select Next.
      One of the following panels is displayed:
      • If you select the default value of DB2 Universal, or the databases DB2 Universal OS/390 V7.1, DB2 Universal OS/390 V8.1, or DB2 CLI, the Profile summary panel is displayed. Proceed to step 9.
      • The business rule group and selector components support only DB2 Universal, DB2 Universal OS/390 V7.1, DB2 Universal OS/390 V8.1, or DB2 CLI for their repository.

        Icon indicating 6.0.1 content only In WebSphere Process Server, version 6.0.1, these components also support Oracle OCI (Oracle OCI client) and Oracle Thin (Oracle Thin).

        If you select any database other than these, a warning panel is displayed, which explains this restriction. Proceed to step 8.

        Remember: This warning panel is displayed only the first time you select a database other than these. If you select Back, select another database other than these, and then select Next, the warning panel is not displayed.
  8. In the warning panel, if you intend to use the business rule group and selector components and you still want to use a database for the other components that the business rule group and selector components do not support, you have to configure the repository database for the business rule group and selector components manually. Select OK to keep your selections or select Back to return to the Database configuration panel to change your settings. For information on configuring the repository database for the business rule group and selector components manually, see the following topic in this information center: Administering WebSphere Process Server > Administering applications and application services > Business rules > Installing the business rules dynamic repository for network deployment. This procedure assumes you select OK.
  9. In the Profile summary panel, review the profile characteristics and select Next to augment the profile or select Back to change the characteristics of the profile.

    The Profile Wizard shows a progress panel to indicate that the profile is being augmented. If no errors are detected, the Profile augmentation is complete panel is displayed at the end of the process.

    Attention: If errors are detected during profile augmentation, other panels might be displayed in place of the Profile augmentation is complete panel. Examples include the following:
    • Profile augmentation is complete with warnings panel, which indicates that a profile was augmented but warnings were generated.
    • Profile augmentation is incomplete panel, which indicates that a profile was augmented but exists in an unusable state.
    • Profile augmentation failed panel, which indicates that a profile was unable to be augmented.
    Each of these panels identifies the log file to reference in order to troubleshoot the problems. Also refer to Recovering from profile creation or augmentation failure for troubleshooting tips.
  10. Ensure the check box to launch the First Steps console is selected, and select Finish to close the Profile Wizard and start the First Steps console.

Result

A WebSphere Application Server Network Deployment custom profile is successfully augmented into a WebSphere Process Server custom profile. The node within the profile is empty until you federate the node and use the deployment manager to customize the node.

What to do next

Federate the node into the deployment manager cell. See Federating custom nodes to a deployment manager for details.

Terms of use |

Last updated: Thu Apr 27 15:20:08 2006

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