6 Configuring the Oracle Business Activity Monitoring Domain

After you have installed Oracle Business Activity Monitoring (as part of Oracle SOA Suite and Oracle Business Process Management installation), you can configure the domain, which you can also extend for high availability.

The configuration steps presented here assume that you have completed the installation steps covered in:

Refer to the following sections to configure a WebLogic domain and test the configuration:

  • Configuring the Domain
    Use the Configuration Wizard to create and configure a domain.
  • Starting the Servers
    After configuration is complete, start Node Manager, then the WebLogic Administration Server and Managed Servers.
  • Verifying the Configuration
    After completing all configuration steps, you can perform additional steps to verify that your domain is properly configured.

6.1 Configuring the Domain

Use the Configuration Wizard to create and configure a domain.

Note:

BAM uses the Oracle SOA Suite schema. Therefore, you will not create a database schema during BAM domain configuration.

For more information on other methods to create domains, see Additional Tools for Creating, Extending, and Managing WebLogic Domains in Creating WebLogic Domains Using the Configuration Wizard.

6.1.1 Starting the Configuration Wizard

Start the Configuration Wizard to begin configuring a domain.

To start the Configuration Wizard:

  1. Go to the /oracle_common/common/bin directory:

    (UNIX) ORACLE_HOME/oracle_common/common/bin

    (Windows) ORACLE_HOME\oracle_common\common\bin

    where ORACLE_HOME is your 12c (12.2.1.1) Oracle home.

  2. Enter the following command:

    (UNIX) ./config.sh

    (Windows) config.cmd

6.1.2 Navigating the Configuration Wizard Screens to Create and Configure the Domain

Enter required information in the Configuration Wizard screens to create and configure the domain for the topology.

Note:

You can use this procedure to extend an existing domain. If your needs do not match the instructions in the procedure, be sure to make your selections accordingly, or see the supporting documentation for more details.

6.1.2.1 Selecting the Domain Type and Domain Home Location

Use the Configuration Type screen to select a Domain home directory location, optimally outside the Oracle home directory.

Oracle recommends that you locate your Domain home in accordance with the directory structure in What Are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware, where the Domain home is located outside the Oracle home directory. This directory structure helps avoid issues when you need to upgrade or reinstall software.

To specify the Domain type and Domain home directory:

  1. On the Configuration Type screen, select Create a new domain.

    Note:

    You can also extend your existing Oracle SOA Suite domain to include BAM by selecting Update an existing domain. For more information, see Extending the Domain with Business Activity Monitoring in Enterprise Deployment Guide for Oracle SOA Suite.
  2. In the Domain Location field, specify your Domain home directory.

Tip:

For more information about this screen, see Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.

6.1.2.2 Selecting the Configuration Templates for Oracle Business Activity Monitoring

Use the Templates screen to select the templates you require.

On the Templates screen, make sure Create Domain Using Product Templates is selected, then select the following template(s):

  • Business Activity Monitoring - 12.2.1.1.0 [soa]

  • If you are installing BAM in a SOA domain (for example, if you plan to use BAM for monitoring SOA using the built-in BAM dashboards), also select: 

    Oracle SOA Suite - 12.2.1.1.0 [soa]

    Selecting this template automatically selects the following as dependencies:

    • Oracle Enterprise Manager

    • Oracle WSM Policy Manager

    • Oracle JRF

    • WebLogic Coherence Cluster Extension

Tip:

For more information about this screen, see Templates in Creating WebLogic Domains Using the Configuration Wizard.

6.1.2.3 Selecting the Application Home Location

Use the Application Location screen to select the location to store applications associated with your domain, also known as the Application home directory.

Oracle recommends that you locate your Application home in accordance with the directory structure in What Are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware, where the Application home is located outside the Oracle home directory. This directory structure helps avoid issues when you need to upgrade or re-install your software.

Tip:

For more about the Application home directory, see About the Application Home Directory.

For more information about this screen, see Application Location in Creating WebLogic Domains Using the Configuration Wizard.

6.1.2.4 Configuring the Administrator Account

Use the Administrator Account screen to specify the user name and password for the default WebLogic Administrator account for the domain.

Oracle recommends that you make a note of the user name and password that you enter on this screen; you need these credentials later to boot and connect to the domain's Administration Server.

6.1.2.5 Specifying the Domain Mode and JDK

Use the Domain Mode and JDK screen to specify the domain mode and Java Development Kit (JDK).

On the Domain Mode and JDK screen:

  • Select Production in the Domain Mode field.

  • Select the Oracle HotSpot JDK in the JDK field.

Tip:

For more information about this screen, see Domain Mode and JDK in Creating WebLogic Domains Using the Configuration Wizard.

6.1.2.6 Specifying the Database Configuration Type

Use the Database Configuration type screen to specify details about the database and database schema.

On the Database Configuration type screen, select RCU Data. This option instructs the Configuration Wizard to connect to the database and Service Table (STB) schema to automatically retrieve schema information for schemas needed to configure the domain.

Note:

If you select Manual Configuration on this screen, you must manually fill in parameters for your schema on the next screen.

After selecting RCU Data, fill in the following fields:

Field Description

DBMS/Service

Enter the database DBMS name, or service name if you selected a service type driver.

Example: orcl.exampledomain.com

Host Name

Enter the name of the server hosting the database.

Example: examplehost.exampledomain.com

Port

Enter the port number on which the database listens.

Example: 1521

Schema Owner

Schema Password

Enter the username and password for connecting to the database's Service Table schema. This is the schema username and password entered for the Service Table component on the Schema Passwords screen in the RCU (see Specifying Schema Passwords).

The default username is prefix_STB, where prefix is the custom prefix that you defined in the RCU.

Click Get RCU Configuration when you finish specifying the database connection information. The following output in the Connection Result Log indicates that the operation succeeded:

Connecting to the database server...OK
Retrieving schema data from database server...OK
Binding local schema components with retrieved data...OK

Successfully Done.

Tip:

For more information about the schema installed when the RCU is run, see About the Service Table Schema in Creating Schemas with the Repository Creation Utility.

For more information about this screen, see Database Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.

6.1.2.7 Specifying JDBC Component Schema Information

Use the JDBC Component Schema screen to verify or specify details about the database schemas.

Verify that the values populated on the JDBC Component Schema screen are correct for all schemas. If you selected RCU Data on the previous screen, the schema table should already be populated appropriately.

Tip:

For high availability environments, see the following sections in High Availability Guide for additional information on configuring data sources for Oracle RAC databases:

For more information about this screen, see JDBC Component Schema in Creating WebLogic Domains Using the Configuration Wizard.

6.1.2.8 Testing the JDBC Connections

Use the JDBC Component Schema Test screen to test the data source connections.

A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.

By default, the schema password for each schema component is the password you specified while creating your schemas. If you want different passwords for different schema components, manually edit them in the previous screen (JDBC Component Schema) by entering the password you want in the Schema Password column, against each row. After specifying the passwords, select the check box corresponding to the schemas that you changed the password in and test the connection again.

Tip:

For more information about this screen, see JDBC Component Schema Test in Creating WebLogic Domains Using the Configuration Wizard .

6.1.2.9 Selecting Advanced Configuration

Use the Advanced Configuration screen to complete the domain configuration.

On the Advanced Configuration screen, select:

  • Administration Server

    Required to properly configure the listen address of the Administration Server.

  • Node Manager

    Required to configure Node Manager.

  • Topology

    Required to configure the Oracle Business Activity Monitoring (BAM) Managed Server.

6.1.2.10 Configuring the Administration Server Listen Address

Use the Administration Server screen to select the IP address of the host.

Select the drop-down list next to Listen Address and select the IP address of the host where the Administration Server will reside, or use the system name or DNS name that maps to a single IP address. Do not use All Local Addresses.

Do not specify any server groups for the Administration Server.

6.1.2.11 Configuring Node Manager

Use the Node Manager screen to select the type of Node Manager you want to configure, along with the Node Manager credentials.

Select Per Domain Default Location as the Node Manager type, then specify Node Manager credentials.

Tip:

For more information about this screen, see Node Manager in Creating WebLogic Domains Using the Configuration Wizard.

For more about Node Manager types, see Node Manager Overview in Administering Node Manager for Oracle WebLogic Server.

6.1.2.12 Configuring Managed Servers for Oracle Business Activity Monitoring

Use the Managed Servers screen to configure Managed Servers.

The selections described here reflect the standard installation topology shown in Using the Standard Installation Topology as a Starting Point. The standard installation topology represents a sample topology for this product, installing BAM in a SOA domain. It is not the only topology this product supports. For example, if you are creating a BAM-only domain, you will not see the SOA selections.

On the Managed Servers screen, two Managed Servers named soa_server1 and bam_server1 are already created by default.

To configure Managed Servers for Oracle Business Activity Monitoring:
  1. In the Listen Address drop-down list, select the IP address of the host on which the Managed Servers will reside. Do not use All Local Addresses.
  2. In the Server Groups drop-down list, select SOA-MGD-SVRS for soa_server1 and BAM-MGD-SVRS-ONLY for bam_server1.

    There is another server group called SOA-MGD-SVRS-ONLY that targets only SOA but not Oracle Web Services Manager (OWSM) to the server. This is typically used if you want to have Oracle Web Services Manager (OWSM) in a different server rather than with the SOA server.

    Server groups target Fusion Middleware applications and services to one or more servers by mapping defined application service groups to each defined server group. A given application service group may be mapped to multiple server groups if needed. Any application services that are mapped to a given server group are automatically targeted to all servers that are assigned to that group. For more information, see Application Service Groups, Server Groups, and Application Service Mappings in Domain Template Reference.

  3. Configuring second Managed Servers is one of the steps needed to configure the standard topology for high availability. If you are not creating a highly available environment, then this step is optional.

    Repeat these steps to create two more Managed Servers named soa_server2 and bam_server2.

    For more information about the high availability standard topology, see Understanding the Fusion Middleware Standard HA Topology in High Availability Guide.

    For more information about the next steps to prepare for high availability after your domain is configured, see Preparing Your Environment for High Availability.

These server names are referenced in examples throughout this document.

Tip:

For more information about this screen, see Managed Servers in Creating WebLogic Domains Using the Configuration Wizard.

6.1.2.13 Configuring a Cluster for Oracle Business Activity Monitoring

Use the Clusters screen to create a new cluster.

On the Clusters screen:

  1. Click Add.
  2. Specify bam_cluster1 in the Cluster Name field.
  3. Leave the Cluster Address field blank.

By default, server instances in a cluster use unicast to communicate with one another. If you want to change your cluster communications to use multicast, see Considerations for Choosing Unicast or Multicast in Administering Clusters for Oracle WebLogic Server.

You can also use Oracle Fusion Middleware Control to create clusters. In this case, you can configure cluster communication (unicast or multicast) as you go through cluster creation steps. For more information, see Create and configure clusters in Oracle WebLogic Server Administration Console Online Help.

Tip:

For more information about this screen, see Clusters in Creating WebLogic Domains Using the Configuration Wizard.

6.1.2.14 Assigning Oracle Business Activity Monitoring Managed Servers to the Cluster

Use the Assign Servers to Clusters screen to assign Managed Servers to a new configured cluster. A configured cluster is a cluster you configure manually. You do not use this screen if you are configuring a dynamic cluster, a cluster that contains one or more generated server instances that are based on a server template.

See About Dynamic Clusters for more on configured cluster and dynamic cluster terms.

On the Assign Servers to Clusters screen:

  1. In the Clusters pane, select the cluster to which you want to assign the Managed Servers; in this case, bam_cluster1.
  2. In the Servers pane, assign bam_server1 to bam_cluster1 by doing one of the following:

    • Click once on bam_server1 to select it, then click the right arrow to move it beneath the selected cluster (bam_cluster1) in the Clusters pane.

    • Double-click on bam_server1 to move it beneath the selected cluster (bam_cluster1) in the Clusters pane.

  3. Repeat to assign bam_server2 to bam_cluster1.
  4. If you are configuring BAM in a SOA domain, repeat these steps to assign soa_server1 and soa_server2 to soa_cluster1.
The following image shows a generic example of the Clusters pane after Managed Servers are assigned to clusters.

Figure 6-1 Managed Servers Assigned to Clusters

Description of Figure 6-1 follows
Description of "Figure 6-1 Managed Servers Assigned to Clusters"

Tip:

For more information about this screen, see Assign Servers to Clusters in Creating WebLogic Domains Using the Configuration Wizard.

6.1.2.15 Configuring Coherence Clusters

Use the Coherence Clusters screen to configure the Coherence cluster.

Leave the default port number as the Coherence cluster listen port. After configuration, the Coherence cluster is automatically added to the domain.

Note:

Setting the unicast listen port to 0 creates an offset for the Managed Server port numbers. The offset is 5000, meaning the maximum allowed value that you can assign to a Managed Server port number is 60535, instead of 65535.

See Table 8-2 for more information and next steps for configuring Coherence.

Note:

For Coherence licensing information, see Oracle Coherence Products in Licensing Information.

6.1.2.16 Creating New Oracle Business Activity Monitoring Machines

Use the Machines screen to create new machines in the domain. A machine is required so that Node Manager can start and stop servers.

Tip:

If you plan to create a high availability environment and know the list of machines your target topology requires, you can follow the directions in this section to create all of the machines at this time. For more information, see Optional Scale Out Procedure in High Availability Guide.

  1. Select the Machine tab (for Windows) or the UNIX Machine tab (for UNIX), then click Add to create a new machine.
  2. In the Name field, specify a machine name, such as bam_machine1.
  3. In the Node Manager Listen Address field, select the IP address of the machine in which the Managed Servers are being configured.

    You must select a specific interface and not localhost. This allows Coherence cluster addresses to be dynamically calculated.

  4. Verify the port in the Node Manager Listen Port field.
  5. Repeat these steps to add more machines, if required. For example, if you are configuring BAM in a SOA domain, repeat these steps for a second machine named soa_machine2.

Note:

If you are extending an existing domain, you can assign servers to any existing machine; you don’t need to create a new machine unless your situation requires it.

Tip:

For more information about this screen, see Machines in Creating WebLogic Domains Using the Configuration Wizard.

6.1.2.17 Assigning Servers to Oracle Business Activity Monitoring Machines

Use the Assign Servers to Machines screen to assign the Administration Server and Managed Servers to a new machine.

On the Assign Servers to Machines screen:

  1. In the Machines pane, select the machine to which you want to assign the servers; in this case, bam_machine1.
  2. In the Servers pane, assign AdminServer to bam_machine1 by doing one of the following:

    • Click once on AdminServer to select it, then click the right arrow to move it beneath the selected machine (bam_machine1) in the Machines pane.

    • Double-click on AdminServer to move it beneath the selected machine (bam_machine1) in the Machines pane.

  3. Repeat these steps to assign both bam_server1 and bam_server2 to bam_machine1.
  4. If you are configuring BAM in a SOA domain, repeat these steps to assign both soa_server1 and soa_server2 to soa_machine1.
The following figure shows a generic example of the Machines pane after Managed Servers are assigned to machines.

Figure 6-2 Assign Managed Servers to Machines

Description of Figure 6-2 follows
Description of "Figure 6-2 Assign Managed Servers to Machines"

Tip:

For more information about this screen, see Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard.

6.1.2.18 Virtual Targets

If you have a WebLogic Server Multitenant (MT) environment, you use the Virtual Targets screen to add or delete virtual targets. For this installation (not a WebLogic Server MT environment), you do not enter any values; just select Next.

Tip:

For more information about this screen, see Virtual Targets in Creating WebLogic Domains Using the Configuration Wizard.

6.1.2.19 Partitions

The Partitions screen is used to configure partitions for virtual targets in WebLogic Server Multitenant (MT) environments. Select Next without selecting any options.

Tip:

For more information about this screen, see Partitions in Creating WebLogic Domains Using the Configuration Wizard.

6.1.2.20 Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen shows detailed configuration information for the domain you are about to create.

Review each item on the screen and verify that the information is correct. To make any changes, go back to a screen by clicking the Back button or selecting the screen in the navigation pane. Domain creation does not start until you click Create.

Tip:

For more information about this screen, see Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.

6.1.2.21 Writing Down Your Domain Home and Administration Server URL

The End of Configuration screen shows information about the domain you just configured.

Make a note of the following items because you need them later:

  • Domain Location

  • Administration Server URL

You need the domain location to access scripts that start Node Manager and Administration Server, and you need the URL to access the Administration Server.

Click Finish to dismiss the Configuration Wizard.

6.2 Starting the Servers

After configuration is complete, start Node Manager, then the WebLogic Administration Server and Managed Servers.

Note:

For more information on additional tools you can use to manage your domain, see Overview of Oracle Fusion Middleware Administration Tools in Administering Oracle Fusion Middleware.

6.2.1 Starting Node Manager

To start the per-domain Node Manager:

  1. Go to the DOMAIN_HOME/bin directory.

  2. Enter the following command:

    • (UNIX) Using nohup and nm.out as an example output file:

      nohup ./startNodeManager.sh > LOG_DIR/nm.out&

      where LOG_DIR is the location of directory in which you want to store the log files.

    • (Windows) startNodeManager.cmd

      Note:

      On Windows operating systems, Oracle recommends that you configure Node Manager to run as a startup service. This allows Node Manager to start up automatically each time the system is restarted.

      See Running Node Manager as a Startup Service in Administering Node Manager for Oracle WebLogic Server.

6.2.2 Starting the Administration Server

To start the Administration Server:

  1. Go to the DOMAIN_HOME/bin directory.

  2. Enter the following command:

    • (UNIX)

      ./startWebLogic.sh

    • (Windows)

      startWebLogic.cmd

If you selected Production Mode on the Domain Mode and JDK screen when you created the domain, you see a prompt for the Administrator user login credentials as provided on the Administrator Account screen.

Tip:

For more information about starting the Administration Server, see Starting and Stopping Administration Server in Administering Oracle Fusion Middleware.

In production mode, a boot identity file can be created to bypass the need to provide a user name and password when starting the Administration Server. For more information, see Creating a Boot Identity File for an Administration Server in Administering Server Startup and Shutdown for Oracle WebLogic Server.

You can verify that the Administration Server is up and running by accessing the Administration Server Console. The URL is provided on the End of Configuration screen (http://administration_server_host:administration_server_port/console). The default Administration Server port number is 7001.

Note:

Make sure that the database hosting your product schemas is up and running and accessible by the Administration Server.

For more information about how to use the Administration Console, see Getting Started Using Oracle WebLogic Server Administration Console in Administering Oracle Fusion Middleware.

6.2.3 Starting the Managed Servers

To start the Managed Servers:

  1. Log in to Oracle Fusion Middleware Control: 
    http://administration_server_host:administration_server_port/em

    The Administration Server host and port number were in the URL on the End of Configuration screen (Writing Down Your Domain Home and Administration Server URL). The default Administration Server port number is 7001.

    The login credentials were provided on the Administrator Account screen (Configuring the Administrator Account).

  2. The Enterprise Manager landing page lists the servers configured for this domain and displays their status (such as Running or Shutdown). For a newly configured domain, only the AdminServer(admin) will be running.

    Select the first Managed Server.

  3. Next to the WebLogic Server menu, select Start Up.
  4. Repeat Steps 3 and 4 to start all Managed Servers.
  5. On the main landing page, verify that all the Managed Servers are up and running.

6.3 Verifying the Configuration

After completing all configuration steps, you can perform additional steps to verify that your domain is properly configured.

To verify that the domain is configured properly, see Performing Additional Domain Configuration Tasks.