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

Creating a new WebSphere ESB custom profile

A custom profile is an empty node that you must federate into a deployment manager cell to make operational. In contrast to a stand-alone server profile, a custom profile does not have a default server on its node. Nor are there any default applications on the custom node. Federating the custom profile changes it into a managed node. After federation, a custom profile has a nodeagent process but does not have a server process. You must use the administrative console of the deployment manager to customize the empty node for production or other uses. After you start the nodeagent, it responds to commands from the deployment manager.

Before you begin

Before using this procedure:
  • Ensure you have an existing installation of WebSphere ESB.
  • Ensure you want to create a custom server 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 create the new 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, 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

The Full installation procedure for WebSphere ESB creates one stand-alone server profile named default with a server named server1. However, to make use of the networking advantage of the product, you can use the Profile wizard to create additional profiles.

Use the following procedure to create a new custom 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 descriptions of the many 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. One of the following panels is displayed:
    • If a WebSphere Application Server or WebSphere Application Server Network Deployment profile exists, the Existing Profile Detection panel is displayed. This procedure assumes that you want to create a new profile, rather than augment an existing one into a WebSphere ESB profile. To create a new profile, select Create a new WebSphere ESB profile and click Next. The Profile Type Selection panel is displayed.
    • If no profile exists the Profile Type Selection panel is displayed.
  4. Select Custom WebSphere ESB, then click Next. The Federation panel is displayed.
  5. Choose whether to federate the custom node into a deployment manager.
    • If you choose to federate the node, specify the host name or IP address and SOAP port of the deployment manager and click Next to continue. The Profile Name panel is displayed.

      Attention:
      Federate the custom node at this time only if all of the following are true:
      • The deployment manager is running.
      • The deployment manager is a WebSphere ESB deployment manager profile.
      • Security is not enabled on the deployment manager node.
      • The deployment manager uses the default SOAP JMX connector type and the connector is enabled.
      Do not federate the custom node at this time if any one of the following is true:
      • The deployment manager is not running or you are not sure if it is running.
      • The deployment manager is a WebSphere Application Server Network Deployment profile that has not yet been augmented into a WebSphere ESB profile.
      • Security is enabled on the deployment manager node.
      • The SOAP connector is disabled.
      • The deployment manager is reconfigured to use the non-default remote method invocation (RMI) as the preferred Java Management Extensions (JMX) connector. (Select System administration > Deployment manager > Administration services in the administrative console of the deployment manager to verify the preferred connector type.)
      If you federate a custom node when the deployment manager is not running or is not available for other reasons, the Profile Creation Failed panel is displayed. Click Finish to exit this panel.
    • If you choose not to federate the node, select the check box next to Federate this node later using the addNode command and click Next to continue. The Profile Name panel is displayed. See Federating custom nodes to a deployment manager for more information on how to federate a node from the administrative console or by using this command.

  6. Specify a unique name for the profile or accept the default name. If any other profiles exist, you have the option of making this profile the default profile by selecting the check box next to Make this profile the default. Then click Next.

    Each profile that you create must have a name. When you have more than one profile, you can tell them apart at their highest level by this name. See Naming considerations for profiles, nodes, hosts, and cells for information on issues you must consider when naming the profile.

    The Profile Directory panel is displayed.
  7. Accept the default directory location for the profile or use the Browse button to specify another location, then click Next.
    This directory will contain the files that define the runtime environment, such as commands, configuration files, and log files. By default, this directory location is:
    • LINUX platforms UNIX platforms On Linux and UNIX platforms: install_root/profiles/profile_name
    • For Windows platforms On Windows platforms: install_root\profiles\profile_name
    where profile_name is the name that you specified. This directory location can be changed to any valid directory location on the system. If the directory already exists, it must be empty or the Profile wizard will display an error.

    The Node And Host Names panel is displayed.

  8. Specify the node and host names for the custom profile, or accept the defaults, then select Next.

    Use a unique name for each node that you create. See Naming considerations for profiles, nodes, hosts, and cells for information on reserved terms and other issues you must consider when naming the node and host.

    One of the following panels is displayed, depending on whether you elected to federate the node on the Federation panel in Step 5:
    • If you chose to federate the node later, the Profile Summary panel is displayed. In this case, proceed to Step 10.
    • If you chose to federate the node now, the Port Value Assignment panel is displayed. In this case, proceed to Step 9.
  9. The Profile wizard will detect ports currently used by other WebSphere products, but if you have other applications which use specified ports, verify that the ports do not conflict. Click Next.

    When federating a custom profile, the addNode command uses non-conflicting ports. This means that you can take the default port assignments as you create the profile, and let the addNode command specify non-conflicting ports as you federate the node. Port assignments must be unique on a machine. Server processes on different machines can use the same port assignments without conflict.

    The Profile Summary panel is displayed.
  10. Review the profile characteristics, and click Next to create 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 created. If no errors are detected, the Profile Creation is Complete panel is displayed at the end of the process.

    Attention: If errors are detected during profile creation, other panels might be displayed in place of the Profile Creation is Complete panel, for example:
    • Profile Creation is Complete With Warnings panel, which indicates that a profile was created but warnings were generated.
    • Profile Creation is Incomplete panel, which indicates that a profile was created but exists in an unusable state.
    • Profile Creation Failed panel, which indicates that a profile was not created.
    Each of these panels identifies the log file which contains more details to help you to resolve the errors.
  11. 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 new custom profile exists. The node within the profile is empty until you federate the node (if you have not done so during profile creation) and use the deployment manager to customize the node.

What to do next

Federate the node into the deployment manager cell if you have not already done so as you created the custom node.
Related tasks
Federating custom nodes to a deployment manager

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_create_mn.html

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