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


Configuring stand-alone server profiles using default values

Learn how to use the Profile Management Tool to create and configure a WebSphere® ESB stand-alone server profile with default configuration settings.

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 stand-alone server profile, and have selected the Typical profile creation or augmentation option.

About this task

Selecting the Typical profile creation or augmentation option creates or augments a profile with default configuration settings. 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, host, and cell. The administrative console is installed. You can optionally enable administrative security (unless you are augmenting a profile that has security enabled – then you must re-enter the administrative user ID and password of that profile to augment it to a WebSphere ESB profile). If your operating system and the privileges of your user account permit, the tool creates a system service to run the server. The Common Event Infrastructure and Common database configurations are set to Derby Embedded.

It also configures Business Space powered by WebSphere using Derby Embedded.

Restriction: If you plan to federate this stand-alone server profile to a deployment manager, do not use the Typical option to create it. The default values for messaging engine storage and database type provided in a Typical profile creation or augmentation are not suitable deployment environment installations. Use the Advanced option to create or augment the profile instead. See Configuring stand-alone server profiles using customized values for instructions.

As a result of following the procedure in either Augmenting profiles using the Profile Management Tool or Creating profiles using the Profile Management Tool, you are viewing either the Administrative security panel or the Profile summary panel. Complete the following steps to configure a new stand-alone server profile with default configuration values.

Procedure
  1. The panel you see displayed in the Profile Management Tool depends on whether you are creating or augmenting a profile. If you are augmenting a profile, it also depends on whether security is enabled on that profile.
    If you are performing First step
    Typical profile augmentation and administrative security is enabled on the profile you are augmenting. The Administrative security panel is displayed. Proceed to step 2.
    Typical profile augmentation and administrative security is not enabled on the profile you are augmenting. The Profile summary panel is displayed. Proceed to step 3.
    Typical profile creation The Administrative security panel is displayed. Proceed to step 2.
  2. Enable administrative security.

    This screen differs depending on whether you are creating or augmenting a profile.

    If you are creating a profile, you can enable administrative security now, or later from the administrative console. To enable administrative security now, leave the Enable administrative security check box selected, supply a user name and password to log onto the administrative console, and click Next. To disable administrative security, clear the check box. To enable administrative security later from the administrative console, open the console and select Security > Business Integration Security.

    If you are augmenting a profile and see this panel, the profile you are augmenting has security enabled. You must re-enter the administrative user ID and password for that profile.

    The Profile summary panel is displayed.

  3. 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.

    Attention: If errors are detected during profile creation or augmentation, other messages might appear in place of the success message, for example:
    • The Profile Management tool created the profile but errors occurred, which indicates that profile creation completed but errors were generated.
    • The Profile Management tool cannot create the profile, which indicates that profile creation failed completely.
    • The Profile Management tool augmented the profile but errors occurred, which indicates that profile augmentation completed but errors were generated.
    • The Profile Management tool cannot augment the profile, which indicates that profile augmentation failed completely.
    The Profile complete panel identifies the log file to reference in order to troubleshoot the problems. See the descriptions of relevant log files listed in Installation and profile creation log files.
  4. 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 to start the server. 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 or WebSphere Application Server Network Deployment profile into a WebSphere Enterprise Service Bus profile.
The node within the profile has a server named server1 for Linux, UNIX®, and Windows platforms or servername for i5/OS platforms and the number is incremented if there is more than one WebSphere ESB installation.

What to do next

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

You can also check server operation by running the Installation Verification Test (IVT) from the First steps console or running the wbi_ivt command. This test is to verify that your deployment manager or stand-alone server installation is operating properly. For a stand-alone server profile, it also runs a Health Monitor check and generates a report.


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_saserver_typ.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).