Creating and augmenting profiles using the Profile Management Tool

The Profile Management Tool in the WebSphere® Customization Toolbox lets you create or augment profiles to manage your runtime environment.

About this task

Restriction: If you are using Solaris, the Profile Management Tool user interface is not available. You must use the manageprofiles command.

For a single-server environment, create a stand-alone profile.

For a network deployment environment, complete the following steps:
  1. Create the deployment manager profile before creating the other profiles. If you created a deployment manager profile before installing IBM® Business Monitor (for example, for WebSphere Application Server) and you plan to use the same deployment manager profile to manage IBM Business Monitor nodes, augment the profile using the template that IBM Business Monitor provides.
  2. Create a custom profile for each node that you plan to add to the server cluster. Alternatively, augment an existing custom profile for each node that you plan to add.
    Note: If the database server contains multiple versions of DB2® installed, or multiple DB2 instances, the server's default DB2 version or instance is used for profile creation. To control which DB2 version or instance is used, use the "Installing databases manually" procedure so that the database administrator can ensure that the proper version or instance is used.

If you are using an Oracle database, JDBC support is provided by the Oracle JDBC drivers for JVM 1.6. The ojdbc6.jar JDBC driver file is the Oracle-supported JDBC driver for use with WebSphere Application Server. The ojdbc6.jar file can be used for both Oracle 10g and Oracle 11g. For information about minimum required settings for Oracle, see the related link.

By default, the Profile Management Tool points to the ojdbc6.jar file supplied in app_server_root\jdbcdrivers\Oracle. Alternatively, you can download another Oracle ojdbc6.jar JDBC driver file and point to it when you run the Profile Management Tool or the manageprofiles command.

If you are using an SQL Server database, the SQL Server JDBC drivers for JVM 1.6 provide JDBC support. IBM Business Monitor uses the Microsoft JDBC 2.0 driver sqljdbc4.jar file. By default, the Profile Management Tool points to the sqljdbc4.jar file supplied in app_server_root\jdbcdrivers\SQLServer. Alternatively, you can download another Microsoft sqljdbc4.jar JDBC driver file and point to it when you run the Profile Management Tool or the manageprofiles command. For information about minimum required settings for SQL Server, see the related link.

  • Creating stand-alone profiles
    If you require a stand-alone profile and did not choose to create one at the end of the IBM Business Monitor installation, you can run the Profile Management Tool to create the profile. The profile is created in the WebSphere Application Server profiles directory.
  • Augmenting stand-alone profiles
    You can use the Profile Management Tool to augment stand-alone profiles for IBM Business Monitor. If you plan to use the server to develop, test, and debug monitor models, you must install the monitor model debugger.
  • Creating deployment manager profiles
    You must have a deployment manager profile to manage all federated servers in a cell. If you are setting up a network deployment environment, create this profile first.
  • Augmenting deployment manager profiles
    In a network deployment environment, you must have a deployment manager profile. Rather than create a new one, you can optionally augment an existing deployment manager profile to be the deployment manager profile for IBM Business Monitor.
  • Creating custom profiles for nodes
    For a network deployment, you must create a custom profile for each node that you plan to add to the IBM Business Monitor server cluster. The profile is created in the WebSphere Application Server profiles directory.
  • Augmenting custom profiles for nodes
    For a network deployment, you need a custom profile for each node that you plan to add to the IBM Business Monitor server cluster. Rather than create a new one, you can optionally augment an existing custom profile for each node.
Parent topic: Creating and augmenting profiles
Related information:
Data source minimum required settings for Oracle
Data source minimum required settings for Microsoft SQL Server
Oracle-related troubleshooting