WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Configuring custom profiles (managed nodes) using default values

Learn how to use the Profile Management Tool to create and configure a custom profile using default configuration values.

Before you begin

This topic assumes that you are using the Profile Management Tool to create or augment profiles and are following the procedure in either Creating profiles using the Profile Management Tool or Augmenting profiles using the Profile Management Tool. As a result, it is assumed that you have started the Profile Management Tool, have chosen to create or augment a custom profile, and have selected the Typical profile creation or augmentation option.

About this task

In this type of configuration, the Profile Management Tool assigns default values to ports, to the location of the profile, and to the names of the profile, node, and host. You can choose to federate the node to an existing deployment manager during the creation or augmentation process, or federate it later using the addNode command. If you decide to federate the profile during the creation or augmentation process, the tool sets the Common database configuration to the same database as the deployment manager. If you decide not to federate, the database configuration is left unconfigured.

As a result of following the procedure in either Creating profiles using the Profile Management Tool or Augmenting profiles using the Profile Management Tool, the Federation panel is displayed. Complete the following steps to configure a new custom profile using default values.

Procedure
  1. In the Federation panel, choose to federate the node into the deployment manager now as part of the profile creation or augmentation, or at a later time and apart from profile creation or augmentation.
    • If you choose to federate the node as part of the profile creation or augmentation, specify the host name or IP address and SOAP port of the deployment manager, and an authentication user ID and password if administrative security is enabled on the deployment manager. Leave the Federate this node later check box unselected. Then click Next.

      The Profile Management Tool verifies that the deployment manager exists and can be contacted, and that the authentication user ID and password are valid for that deployment manager (if it is secured).

      Attention: Federate the custom node during profile creation or augmentation only if all of the following conditions are true:
      • You do not plan to use this custom node as a migration target.
      • No other node is being federated. (Node federation must be serialized.)
      • The deployment manager is running.
      • The deployment manager is a WebSphere ESB deployment manager.
      • The deployment manager is at a release level the same or higher than that of the custom profile you are creating or augmenting.
      • The deployment manager has a JMX administrative port enabled. The default protocol is SOAP.
      Do not federate the custom node during profile creation or augmentation if any one of the following conditions are true:
      • You plan to use this custom node as a migration target.
      • Another profile is being federated. (Node federation must be serialized.)
      • The deployment manager is not running or you are not sure if it is running.
      • The deployment manager has not yet been augmented into a WebSphere ESB deployment manager.
      • The deployment manager is not at a release level the same or higher than that of the custom profile you are creating or augmenting.
      • The deployment manager does not have a JMX administrative port enabled.
      • The deployment manager is reconfigured to use the non-default remote method invocation (RMI) as the preferred Java™ Management Extensions (JMX) connector. (Click System administration > Deployment manager > Administration services in the administrative console of the deployment manager to verify the preferred connector type.)

      If you attempt to federate a custom node when the deployment manager is not running or is not available for other reasons, a warning panel prevents you from continuing. If this warning panel appears, click OK to exit from it, and then make different selections on the Federation panel.

    • If you choose to federate the node at a later time and apart from profile creation or augmentation, select the Federate this node later check box and click Next.

      See Federating custom nodes to a deployment manager for more information on how to federate a node by using the addNode command. Read more about this command in the addNode command topic in the WebSphere Application Server Network Deployment, version 6.1, information center.

    The Profile summary panel is displayed.

  2. In the Profile summary panel, click Create or Augment to create or augment the profile or Back to change the characteristics of the profile.

    When the profile creation or augmentation is complete, the Profile complete panel is displayed with the message The Profile Management tool created the profile successfully or The Profile Management tool augmented the profile successfully.

  3. In the Profile complete panel, select Launch the First steps console, Create another profile, or both; click Finish to exit. Use the First steps console access the product documentation. Use the Create another profile option to restart the Profile Management Tool to create additional profiles.

Results

You have completed one of the following tasks:
  • Created a WebSphere ESB profile.
  • Augmented a WebSphere Application Server Network Deployment profile into a WebSphere Enterprise Service Bus profile.

What to do next

If you did not federate the profile during profile creation or augmentation, federate it now. The node within the profile is empty until you federate the node and use the deployment manager to customize the node.


task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/tins_config_mannode_typ.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).