If you have not yet backed up the existing Fusion Middleware Home and domain, back it up now.

To back up the existing Fusion Middleware Home and domain, see Performing Backups and Recoveries in the SOA Enterprise Deployments.

If you are configuring Oracle BAM on its own set of host computers, you must procure the additional hardware and be sure that it meets the system requirements described in Host Computer Hardware Requirements and Operating System Requirements for the Enterprise Deployment Topology.

You should also add the required entries to the Enterprise Deployment Workbook, as described in Using the Enterprise Deployment Workbook . For the purposes of this guide, you can refer to these host computers as BAMHOST1 and BAMHOST2.

If you configure Oracle BAM on separate host computers, then the instructions in this chapter for propagating the domain to the other domain directories must be modified.

Specifically, in addition to propagating the domain to the Managed Server domain directories on SOAHOST1 and SOAHOST2, you must also unpack the domain in the local Managed Server directories for BAMHOST1 and BAMHOST2.

Note that this means you must start the Node Manager software on each BAMHOST computer before you can remotely start the WLS_BAM Managed Servers on these hosts.

To begin domain configuration:

In this step, you extend the domain created in Extending the Domain with Oracle SOA Suite , to contain Oracle Business Activity Monitoring components.

The steps reflected in this section would be very similar if Oracle Business Activity Monitoring was extending a domain containing only an Administration Server and a WSM-PM Cluster, but some of the options, libraries and components shown in the screens could vary.

Domain creation and configuration includes the following tasks:

• Task 1, "Selecting the Domain Type and Domain Home Location"

• Task 2, "Selecting the Configuration Template"

• Task 3, "Specifying the Database Configuration Type"

• Task 4, "Specifying JDBC Component Schema Information"

• Task 5, "Providing the GridLink Oracle RAC Database Connection Details"

• Task 6, "Testing the JDBC Connections"

• Task 7, "Selecting Advanced Configuration"

• Task 8, "Configuring Managed Servers"

• Task 9, "Configuring a Cluster"

• Task 10, "Assigning Server Templates"

• Task 11, "Configuring Dynamic Servers"

• Task 12, "Assigning Managed Servers to the Cluster"

• Task 13, "Configuring Coherence Clusters"

• Task 14, "Verifying the Existing Machines"

• Task 15, "Assigning Servers to Machines"

• Task 16, "Reviewing Your Configuration Specifications and Configuring the Domain"

• Task 17, "Writing Down Your Domain Home and Administration Server URL"

• Task 18, "Start the Administration Server"

Task 1   Selecting the Domain Type and Domain Home Location

On the Configuration Type screen, select Update an existing domain.

In the Domain Location field, select the value of the ASERVER_HOME variable, which represents the complete path to the Administration Server domain home that you created in Creating the Initial Infrastructure Domain for an Enterprise Deployment.

For more information about the directory location variables, see File System and Directory Variables Used in This Guide.

Tip:

More information about the other options on this screen can be found in Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.

Task 2   Selecting the Configuration Template

On the Templates screen, make sure Update Domain Using Product Templates is selected, then select the following template:

• Oracle Business Activity Monitoring [soa]

Click Next.

Task 3   Specifying the Database Configuration Type

On the Database Configuration Type screen, select RCU Data.

All fields are pre-populated, because you already configured the domain to reference the Fusion Middleware schemas that are required for the Infrastructure domain.

• Verify that the Vendor is Oracle and the Driver is *Oracle's Driver (Thin) for Service Connections; Versions: Any.

• Verify that Connection Parameters is selected.

• Verify and ensure that credentials in all the fields are the same as those provided during the configuration of Oracle Fusion Middleware Infrastructure.

Note:

Any custom data sources that were created before the extension (such as LEASING datasources) shows up before this screen. Check the Datasources row and click Next. The test data source screen verifies its validity. Click Next.

Click Get RCU Configuration after you finish verifying 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.

Task 4   Specifying JDBC Component Schema Information

On the JDBC Component Schema page, select the following schemas:

• BAM Schema

• BAM Job Sched Schema

• BAM Leasing Schema

• BAM Non JTA Schema

• BAM MDS Schema

Select Convert to Gridlink, and then click Next.

Task 5   Providing the GridLink Oracle RAC Database Connection Details

On the GridLink Oracle RAC Component Schema screen, provide the information that is required to connect to the RAC database and component schemas, as shown in the following table.

Table 16-1 Providing the GridLink Oracle RAC Database Connection Details

Element	Description and Recommended Value
Service Name	Verify that the service name for the Oracle RAC database is appropriate. For example, soaedg.example.com.
SCAN, Host Name, and Port	Select the SCAN check box. In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database. In the Port field, enter the SCAN listening port for the database (for example, 1521).
ONS Host and Port	These values are not required when you are using an Oracle 12c database or higher versions because the ONS list is automatically provided from the database to the driver.
Enable Fan	Verify that the Enable Fan check box is selected, so the database can receive and process FAN events.

Task 6   Testing the JDBC Connections

On the Test JDBC Data Sources screen, confirm that all connections were successful.

The connections are tested automatically. The Status column displays the results. If all connections are not successful, click Previous to return to the previous screen and correct your entries.

Click Next when all the connections are successful.

Task 7   Selecting Advanced Configuration

To complete domain configuration for the topology, select Topology on the Advanced Configuration screen.

Note:

JDBC stores are recommended and selected in Task 3, "Configuring High Availability Options" so there is no need to configure File Stores.

If you choose File Stores in Task 3, "Configuring High Availability Options", you have to select the File Stores option here to configure them in a shared location in ORACLE_RUNTIME/domain_name/BAM_Cluster/jms. Shared location is required to resume JMS and JTA in a failover scenario.

Click Next.

Task 8   Configuring Managed Servers

On the Managed Servers screen, add the required managed servers for Oracle BAM:

• Select the automatically created server and rename it to WLS_BAM1.

• Click Add to add another new server and enter WLS_BAM2 as the server name.

• Select BAM12-MGD-SVRS-ONLY as the server group for the BAM Servers. Deselect BAM12-MGD-SVRS from the list.

The configuration for the added servers should match those shown in the following table.

Name	Listen Address	Enable Listen Port	Listen Port	Enable SSL Port	SSL Listen Port	Administration Port	Server Groups
WLS_SOA1*	SOAHOST1	Unchecked	Disabled	Checked	7004	9004	SOA-MGD-SVRS-ONLY
WLS_SOA2*	SOAHOST2	Unchecked	Disabled	Checked	7004	9004	SOA-MGD-SVRS-ONLY
WLS_WSM1	SOAHOST1	Unchecked	Disabled	Checked	7010	9003	JRF-MAN-SVR WSMPM-MAN-SVR
WLS_WSM2	SOAHOST2	Unchecked	Disabled	Checked	7010	9003	JRF-MAN-SVR WSMPM-MAN-SVR
WLS_BAM1	SOAHOST1	Unchecked	Disabled	Checked	7006	9005	BAM12-MGD-SVRS-ONLY
WLS_BAM2	SOAHOST2	Unchecked	Disabled	Checked	7006	9005	BAM12-MGD-SVRS-ONLY

*The WLS_SOA1 and WLS_SOA2 Managed Servers are shown if you extend a domain where Oracle SOA Suite has already been configured.

*When you specify the listen address for WLS_BAM1 and WLS_BAM2, enter SOAHOST1 and SOAHOST2, respectively, unless you configure Oracle BAM on separate host computers (BAMHOST1 and BAMHOST2). If you configure Oracle BAM on separate hosts, enter BAMHOST1 and BAMHOST2.

Task 9   Configuring a Cluster

On the Configure Clusters screen, click Add to add the BAM_Cluster (leave the present cluster as they are):

Table 16-2 List of Clusters When Extending the Domain for Oracle BAM

Name	Cluster Address	Frontend Host	Frontend HTTP Port	Frontend HTTPS Port
SOA_Cluster*	Leave it empty	soa.example.com	0	443
WSM-PM_Cluster	Leave it empty	internal.example.com	0	444
BAM_Cluster	Leave it empty	soa.example.com	0	443

*The SOA cluster appears only if you have already configured Oracle SOA Suite in the domain.

Click Next.

Task 10   Assigning Server Templates

Click Next.

Task 11   Configuring Dynamic Servers

Click Next.

Task 12   Assigning Managed Servers to the Cluster

On the Assign Servers to Clusters screen, assign servers to clusters as follows:

• BAM_Cluster:

  • WLS_BAM1

  • WLS_BAM2

Click Next.

Task 13   Configuring Coherence Clusters

Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain. Leave the port number value at 9991, as it was defined during the initial Infrastructure domain creation.

Task 14   Verifying the Existing Machines

Verify the machines that have already been created in the domain. By default, you are targeting the new Oracle BAM Managed Servers to the SOAHOST1 and SOAHOST2 machines, respectively.

However, if you configure Oracle BAM on separate host computers, then you must create two new machines for the corresponding BAMHOST1 and BAMHOST2 host computers:

1. Select the Unix Machine tab.

2. Use the Add button to create two new Unix machines for BAMHOST1 and BAMHOST2.

   Node Manager Listen Address to the physical IP address for BAMHOST1 and BAMHOST2.

3. Verify the port in the Node Manager Listen Port field.

   The port number 5556, shown in this example, may be referenced by other examples in the documentation. Replace this port number with your own port number as needed.

Leave all other fields to their default values.

Click Next.

Task 15   Assigning Servers to Machines

On the Assign Servers to Machines screen, assign the new WLS_BAM1 and WLS_BAM2 servers to the SOAHOST1 and SOAHOST2 machines, respectively.

However, if you are configuring Oracle BAM on separate host computers, assign the new Oracle BAM servers to the newly created BAMHOST1 and BAMHOST2 machines, respectively.

Click Next.

Task 16   Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen contains the detailed configuration information for the domain you are about to extend. Review the details of each item on the screen and verify that the information is correct.

If you need to make any changes, you can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.

Click Update to execute the domain extension.

In the Configuration Progress screen, click Next when it finishes.

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

Task 17   Writing Down Your Domain Home and Administration Server URL

The Configuration Success screen shows the following items about the domain that you just configured, including:

• Domain Location

• Administration Server URL

Make a note of both these items, because you need them later; you need the domain location to access the scripts used to start the Administration Server, and you need the Administration Server URL to access the WebLogic Remote Console and Oracle Enterprise Manager Fusion Middleware Control.

Click Finish to dismiss the Configuration Wizard.

Task 18   Start the Administration Server

Start the Administration Server to ensure the changes that you have made to the domain have been applied.

Note that these instructions assume that you are configuring Oracle BAM on the same host as Oracle SOA Suite. If you use separate hosts for Oracle BAM, you must modify the WebLogicCluster parameter in the Oracle HTTP Server configuration files to reference the BAMHOST computers, rather than the SOAHOST computers.

To enable Oracle HTTP Server to route requests to Oracle BAM: