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.

Before you begin

Before completing this task, you must complete the following tasks:

• Verified that all hardware and software prerequisites have been met
• Installed IBM Business Monitor
• Logged in to the system as a user with appropriate permissions (read, write, and execute) on the profiles directory of WebSphere® Application Server
• Installed the database

Important: To install or run the Profile Management Tool on Windows 7, Windows Vista, or Windows Server 2008, you must elevate your Microsoft Windows user account privileges. Whether you are an administrative user or a non-administrative user, right-click the pmt.bat file and select Run as administrator. Alternatively, use the runas command at the command line. For example:

runas /user:ADMINNAME /env pmt.bat

Non-administrative users are prompted for the administrator password.

Complete the following steps to augment an existing deployment manager profile using the Profile Management Tool:

1. Open the Profile Management Tool using one of the following methods:
   • From the IBM Business Monitor First Steps console, click Profile Management Tool.
   • Click Start > Programs > IBM > Business Monitor 8.0 > Profile Management Tool.
   • Run pmt.bat, which is in the following directory: app_server_root\bin\ProfileManagement
   • Change to the app_server_root/bin/ProfileManagement directory and type ./pmt.sh in a terminal window.
2. On the Welcome to the Profile Management Tool panel, review the information, and click Launch Profile Management Tool.
3. On the Profiles panel, select a profile from the list and click Augment to augment an existing profile. (You can expand a profile to see the augmentations that have already been done.) You must select an existing deployment manager profile to augment to be the IBM Business Monitor deployment manager profile.
   Restriction: If you cannot see the IBM Business Monitor option, it might indicate that you are using Solaris in 64-bit mode. In that case, you cannot use the Profile Management Tool and must use the manageprofiles command.
4. On the Augment Selection panel, click Monitor server deployment manager from the list, and click Next.
5. On the Profile Augmentation Options panel, click Advanced profile augmentation, and click Next. If you click Typical, some of the panels are not shown.
6. Optional: If the profile you are augmenting has security enabled, complete the following steps on the Administrative Security panel:
   1. Type user_name for the User name.
   2. Type password for the Password.
   3. Type password in the Confirm password field.
   4. Click Next.
7. Optional: Advanced: Configure the databases using a design file.
   1. Select Use a database design file for database configuration if you would like to use a design file instead of specifying the database parameters in the following panels.
   2. Click Browse.
   3. Specify the fully qualified path name for the design file.
   4. Click Next.
   5. Select Delay execution of database scripts (must select if using a remote database) if you do not want to create and configure local databases automatically or create tables in existing databases during profile creation. Local databases are created if this check box is not selected. If you select this option, you or the database administrator must manually run the scripts that are stored in the location specified in the database script output directory field on this page. If you create the scripts for Oracle, you must replace @DB_PASSWORD@ with the password for the schema name before running them.
      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 choose to specify a design file, the database configuration panels in the Profile Management Tool are skipped. Instead, the design file location is passed to the command line to complete the database configuration. For more information on using a design file for database configuration, see "Creating or configuring database scripts using the database design tool."
8. On the Database Configuration panel, verify your MONITOR database configuration information:
   1. Select your database product from the list.
   2. Select Delay execution of database scripts (must select if using a remote database) if you do not want to create and configure a local database automatically or create tables in an existing one during profile creation or augmentation. A local database will be created if this check box is not selected. If you select this option, you or the database administrator must manually run the scripts that are stored in the location specified in the database script output directory field on this page. If you create the scripts for Oracle, you must replace @DB_PASSWORD@ with the password for the schema name before running them.
      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.
   3. In the Database name field, enter the database name or accept the default (MONITOR).
   4. In the Schema name field, enter the schema name or accept the default (MONITOR). If you are using DB2 on z/OS®, the IBM Business Monitor database schema name must be different from the Process Server common database schema name to prevent collisions between database objects.
   5. Click Next.
9. Complete the following steps for the MONITOR database on the Database Configuration (Part 2) panel. The options will vary depending on what database product you selected on the previous panel:
   1. Type user_name for the User name to authenticate with the database. This value represents an existing user ID with read and write permissions to MONITOR tables.
      Note: If you are using an Oracle database, this field is not editable.
   2. Type password for the Password for database authentication. This value represents the password for the specified database user ID.
   3. Type password in the Confirm password field. This value must match the value for Password.
   4. Browse to or enter a path for the JDBC driver classpath files. The JDBC drivers for DB2, Oracle, and SQL Server are in monitor_root/jdbcdrivers.The default JDBC driver classpath is set to use the product-specific files within this directory based on the database type that you selected on the Database Configuration panel. Alternatively, click Browse to enter a path to the JDBC driver classpath files.
      • DB2 database: The following directory is created by default:

        monitor_root/jdbcdrivers/DB2

      • Oracle database: The following directory is created by default:

        monitor_root/jdbcdrivers/Oracle

        The ojdbc6.jar JDBC driver file is the Oracle-supported JDBC driver for use with WebSphere Application Server version 7. 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.
      • SQL Server database: The following directory is created by default:

        monitor_root/jdbcdrivers/SQLServer

        The sqljdbc4.jar JDBC driver file is the Microsoft SQL Server 2.0 JDBC driver. For information about minimum required settings for SQL Server, see the related link.
   5. Select one of the following options for the JDBC driver type:
      • For Oracle databases:
        • OCI: The OCI driver requires a local Oracle client installation.
        • Thin: The Thin driver uses Java™ to communicate with the database and does not require a client on the local system.
      • For DB2 databases, profiles of IBM Business Monitor on operating systems other than z/OS are created with type 4 drivers, and profiles on z/OS are created with type 2 drivers. You can change the type after profile creation by editing the data source properties in the administrative console. A type 2 driver is a native-API driver and requires the installation of database software or a database client on the local system. A type 4 driver is a pure-Java implementation and typically provides the best performance. For the MONITOR database, no database software or clients are required on the local system.
   6. Type host_name for the Database server host name or IP address. The default value is localhost or the fully qualified local host name if defined, and you should use this value for a single-server installation. If your database is on a remote server, you must type the fully qualified host name or IP address.
      Note: Except for a single-server installation, do not use the value localhost since the cluster members depend on the actual host name or IP address.
   7. Type port_number for the Database TCP/IP service port or listener port. This value represents the port where the TCP/IP service is assigned or the port on which the database is listening.
   8. Optional: If you are using a DB2 on z/OS database, type subsystem_name for the Subsystem name. This value is the location of the DB2 for z/OS database. No spaces are allowed in the name.
   9. If you are using Oracle or SQL Server and you chose to create the database automatically, enter the following information:
      • system_user_name for the Database administrator user name. This value is the name of the database administrator for Oracle or SQL Server. This user must have access to create and drop databases and users.
      • password for the Password. This value is the password for the system administrator that is specified in the previous field.
      • password in the Confirm password field.
   10. Click Next. If the MONITOR database has not yet been created, you will see a warning message. Click Yes to continue. You can create the database at a later time.
10. On the Cognos Content Store Database panel, if you do not already have an existing IBM Cognos® Business Intelligence installation that you plan to use, enter the information to create the IBM Cognos BI content store database for multidimensional data analysis from your dashboards.
    1. Click Create a new Cognos content store database.
    2. Provide the name of a database to be used for the IBM Cognos BI content store. The default name is COGNOSCS. On Oracle, the database name is the Oracle service name. On Microsoft SQL Server, the database name must be different from the MONITOR database name.
    3. Provide a user name and password for the database, and confirm the password. If you use the same user name for the content store as for the MONITOR database, you must use the same password. Because this user requires full access rights, it is a good idea to create a new database user for the content store database only.
       Note: The user name and password for the IBM Cognos BI content store database are kept in the Cognos_JDBC_Alias, which allows all database credentials to be maintained in one place. Whenever you start the IBM Business Monitor IBM Cognos BI server, the current values are passed to the IBM Cognos BI configuration to allow IBM Cognos BI access to the content store. Because of this integration, you cannot change the content store user name and password using the IBM Cognos BI Configuration application.
11. On the Profile Augmentation Summary panel, review the information. If you need to make any modifications, click Back and make changes as necessary.
12. Click Augment to augment the profile.
13. On the Profile Augmentation Complete panel, review the information about the completed profile augmentation.
14. Optional: Access First Steps.
    • Select the Launch the IBM Business Monitor first steps option.
    • Go to profile_root/firststeps.wbm and run the firststeps.sh command.
15. Click Finish to exit the Profile Management Tool.