WebSphere WebSphere Enterprise Service Bus, Version 6.0.1 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Augmenting an existing WebSphere Application Server Network Deployment deployment manager profile into a WebSphere ESB deployment manager profile

A deployment manager provides a single administrative interface to a logical group of servers on one or more machines. This logical group of servers is known as a cell. A deployment manager manages the configuration for all of the managed nodes in its cell and deploys applications to any managed node in the cell. All of the profiles in the cell share command files and other product binaries that are created during the installation. You can augment a deployment manager profile using the Profile wizard graphical user interface (GUI).

Before you begin

Before using this procedure:
  • Ensure you have an existing installation of WebSphere ESB.
  • Ensure you want to augment a deployment manager profile and that you want to do so interactively. If your plan does not meet these criteria, see Creating and augmenting profiles using the Profile wizard for descriptions of other documented profile creation or augmentation procedures.
  • Ensure you have enough disk and temporary space to augment the profile.
    Profile Required disk space Required temp space
    Deployment manager profile 30 MB 40 MB
    Custom profile 10 MB 40 MB
    Application server profile 200 MB 40 MB
  • If you have enabled global security on your installation of WebSphere ESB or WebSphere Application Server Network Deployment ensure you disable it before creating the profile. For information on enabling and disabling global security, see Setting up WebSphere ESB security.

Why and when to perform this task

Use the following procedure to augment an existing WebSphere Application Server Network Deployment deployment manager profile into a WebSphere ESB deployment manager profile.

Steps for this task

  1. Log on as root on a Linux or UNIX system, or as a member of the Administrator group on a Windows system.
  2. Start the WebSphere ESB Profile wizard to create a new runtime environment.

    See Starting the Profile Wizard for ways to start the Profile wizard on various platforms.

    The system starts InstallShield Multiplatform to run the Profile wizard and the Welcome panel is displayed.

  3. Click Next.

    If an WebSphere Application Server Network Deployment profile exists for augmentation, the Existing Profile Detection panel is displayed. Select Augment an existing WebSphere Application Server profile and click Next.

    The Profile Type Selection panel is displayed.
    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 using the Profile wizard.
  4. From the Profile Type Selection panel, select Deployment manager profile, then click 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 ESB profiles.

    The Profile Augmentation Selection panel is displayed.
  5. Choose the profile you want to augment from the drop-down list and click Next. The Service Component Architecture Configuration panel is displayed.
  6. Choose whether to configure the service integration bus in a secured mode. To configure the service integration bus in a secured mode, perform the following steps:
    1. Select the check box next to Configure the service integration bus in a secured mode.
    2. Enter the user ID and password, and confirm the password, used to authenticate with a secured service integration bus.
    3. Click Next.

    To not configure the service integration bus in a secured mode, leave the check box clear and click Next.

    The Profile Summary panel is displayed.

  7. Review the profile characteristics and click Next to augment the profile or 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 which contains more details to help you resolve the errors.
  8. Ensure the check box to launch the First steps console is selected and click Finish to close the Profile wizard and start the First steps console.

Result

A WebSphere Application Server Network Deployment deployment manager profile is now successfully augmented into a WebSphere ESB deployment manager profile.

What to do next

Check server operation by selecting Start the deployment manager from the First steps console. An output window opens. If you see a message similar to the following, your deployment manager is operating properly:
ADMU3000I: Server dmgr open for e-business; process id is 3072

You can also check server operation by running the Installation Verification Test (IVT) from the First steps console to verify that your installation is operating properly.


Task topic

Terms of Use | Rate this page

Timestamp iconLast updated: 13 Dec 2005
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.wesb.doc\tasks\twesb_profile_augment_dmgr.html

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