Extending the Domain with Business Activity Monitoring

17 Extending the Domain with Business Activity Monitoring

The procedures explained in this chapter guide you through the process of extending the enterprise deployment domain to include Oracle Business Activity Monitoring.

Variables Used When Configuring Business Activity Monitor
As you perform the tasks in this chapter, you reference the directory variables that are listed in this section.
Support for Dynamic Clusters in BAM
Business Activity Monitoring does not support dynamic clusters in this release.
About Configuring BAM in Its Own Domain
For adding BAM to the enterprise topology, you can add it to the existing SOA domain or you can create a new domain for BAM, separate from the Oracle SOA suite domain.
Prerequisites When Adding Oracle BAM to the Domain
Before you add Oracle BAM to your existing Oracle SOA Suite domain, consider the following information and prerequisites.
Special Instructions When Configuring Oracle BAM on Separate Hosts
If you choose to configure Oracle BAM on its own hardware, then you can use the instructions in this chapter, as long as you also consider the information in the following sections.
Roadmap for Adding Oracle BAM to the Domain
The table in this section lists the high-level steps to extend a SOA domain for Oracle Business Activity Monitoring.
Extending the SOA Domain to Include Oracle Business Activity Monitoring
You can use the Configuration Wizard to extend the existing enterprise deployment SOA domain with the Oracle Business Activity Monitoring.
Propagating the Extended Domain to the Domain Directories and Machines
After you have extended the domain with the BAM instances, and you have restarted the Administration Server on SOAHOST1, you must then propagate the domain changes to the domain directories and machines.
Adding the Enterprise Deployment Administration User to the Oracle BAM Administration Group
Before you validate the Oracle BAM configuration on the Managed Server, add the enterprise deployment administration user (weblogic_soa) to the BAMAdministrator group.
Starting and Validating the WLS_BAM1 Managed Server
After extending the domain, restarting the Administration Server, and propagating the domain to the other hosts, start the newly configured BAM servers.
Starting and Validating the WLS_BAM2 Managed Server
After you start the WLS_BAM2 managed server, you must verify that the server status is reported as Running in the Admin Console and access the URLs to verify the status of the servers.
Modifying the Upload and Stage Directories to an Absolute Path
Configuring the Web Tier for the Extended Domain
Configure the web server instances on the web tier so that the instances route requests for both public and internal URLs to the proper clusters in the extended domain.
Validating Access to Oracle BAM Through the Hardware Load Balancer
Verify that Oracle BAM URLs are successfully routing requests from the hardware load balancer to the Oracle HTTP Server instances to the Oracle BAM software in the middle tier.
Enabling JDBC Persistent Stores for BAM
Oracle recommends that you use JDBC stores, which leverage the consistency, data protection, and high availability features of an oracle database and makes resources available for all the servers in the cluster.
Enabling Automatic Service Migration for BAM
By default, the BAM Managed Servers are always configured with Automatic Service Migration. Specific BAM migratable targets with the appropriate migration policies are created and the cluster database leasing is configured for the BAM cluster during the Configuration Wizard session.
Backing Up the Configuration
It is an Oracle best practices recommendation to create a backup after you successfully extend a domain or at another logical point. Create a backup after you verify that the installation so far is successful. This is a quick backup for the express purpose of immediate restoration in case of problems in later steps.

Parent topic: Configuring the Enterprise Deployment

Variables Used When Configuring Business Activity Monitor

As you perform the tasks in this chapter, you reference the directory variables that are listed in this section.

The values for several directory variables are defined in File System and Directory Variables Used in This Guide.

ORACLE_HOME
ASERVER_HOME
MSERVER_HOME
ORACLE_RUNTIME
WEB_DOMAIN_HOME

In addition, you reference the following virtual IP (VIP) address that are defined in Physical and Virtual IP Addresses Required by the Enterprise Topology:

ADMINVHN

Actions in this chapter are performed on the following host computers:

SOAHOST1
SOAHOST2
WEBHOST1
WEBHOST2
BAMHOST1
BAMHOST2

Parent topic: Extending the Domain with Business Activity Monitoring

Support for Dynamic Clusters in BAM

Business Activity Monitoring does not support dynamic clusters in this release.

You can configure BAM in its own domain or in an existing SOA domain, including a domain where the rest of the clusters are dynamic. However, the BAM cluster is configured as a static cluster in all cases. The procedures explained in this chapter help you extend the domain with a static BAM cluster.

Parent topic: Extending the Domain with Business Activity Monitoring

About Configuring BAM in Its Own Domain

For adding BAM to the enterprise topology, you can add it to the existing SOA domain or you can create a new domain for BAM, separate from the Oracle SOA suite domain.

For more information about building the SOA topology, see Building Your Own Oracle SOA Suite Enterprise Topology.

If you decide to configure BAM in a separate domain, keep the following points in mind to add BAM to your topology:

Ignore any references to the SOA Managed Servers or the SOA Cluster. These elements of the domain exist only if you extend a domain that has already been extended with the Oracle SOA suite.
Run the Repository Creation Utility (RCU) to create the SOAINFRA schema for the BAM domain. This schema is required by BAM. You must use an unique SOAINFRA schema and schema prefix for the BAM domain.
When running the Configuration Wizard, the High Availability Options screen appears as described in Navigating the Configuration Wizard Screens to Extend the Domain with Oracle SOA Suite.

This screen appears for the first time when you create a cluster that uses Automatic Service Migration or JDBC stores or both. After you select HA Options for a cluster, all subsequent clusters that are added to the domain by using the Configuration Wizard, automatically apply HA options (that is, the Configuration Wizard creates the JDBC stores and configures ASM for them).

Oracle recommends that you select the following options to configure Automatic Service Migration and JDBC stores automatically:
- Select Enable Automatic Service Migration with Database Basis.
- Set JTA Transaction Log Persistence to JDBC TLog Store.
- Set JMS Server Persistence to JMS JDBC Store.

Parent topic: Extending the Domain with Business Activity Monitoring

Prerequisites When Adding Oracle BAM to the Domain

Before you add Oracle BAM to your existing Oracle SOA Suite domain, consider the following information and prerequisites.

Note:

If you choose to install Oracle BAM on a separate set of host computers, then in addition to the prerequisites listed here, see Special Instructions When Configuring Oracle BAM on Separate Hosts.

Parent topic: Extending the Domain with Business Activity Monitoring

Understanding the Installation Requirements for Adding Oracle BAM to the Domain

This chapter assumes that you are configuring Oracle Business Activity Monitoring on the same host computers as Oracle SOA Suite, as shown in Figure 3-2.

In the default Oracle SOA Suite and Oracle Business Activity Monitoring topology, you target Oracle BAM to its own Managed Servers and its own cluster, but it shares system resources with the other Oracle SOA Suite products on SOAHOST1 and SOAHOST2. Those system resources include a shared storage device where the Oracle SOA Suite software has been installed in an existing Oracle home directory.

In the default topology, there is no need to install Oracle BAM, because Oracle BAM is included in the Oracle SOA Suite and Oracle Business Process Management distribution and is installed into the Oracle home directories when you install Oracle SOA Suite in Understanding the SOA Enterprise Deployment Topology .

Parent topic: Prerequisites When Adding Oracle BAM to the Domain

Understanding the Database Schema Requirements for Oracle BAM

The schemas required for Oracle BAM are created in the database when you run the Repository Creation Utility (RCU) to create the required Oracle SOA Suite schemas.

As a result, there is no need to run RCU specifically for Oracle BAM.

Parent topic: Prerequisites When Adding Oracle BAM to the Domain

Backing Up the Existing Installation

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.

Parent topic: Prerequisites When Adding Oracle BAM to the Domain

Special Instructions When Configuring Oracle BAM on Separate Hosts

If you choose to configure Oracle BAM on its own hardware, then you can use the instructions in this chapter, as long as you also consider the information in the following sections.

For some organizations, it might make sense to install and configure Oracle BAM on separate host computers so the Oracle BAM software can use dedicated hardware resources and can be further isolated from the other Oracle SOA Suite products.

Parent topic: Extending the Domain with Business Activity Monitoring

Procuring Additional Host Computers for Oracle BAM

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.

Parent topic: Special Instructions When Configuring Oracle BAM on Separate Hosts

Installation Requirements When Configuring Oracle BAM on Separate Hosts

If you configure Oracle BAM on its own set of host computers, then you should follow the same shared storage strategy that you are following for the host computers where the other Oracle SOA Suite products are installed.

Note:

The Oracle home used by BAMHOST1 and BAMHOST2 must contain the exact set of software binaries used by the SOAHOST1 and SOAHOST2 hosts in the domain; otherwise, unpredictable behavior in the execution of the binaries may occur.

Depending on your shared storage strategy, one of the following sections apply if you are using separate host hardware for the Oracle BAM software:

Parent topic: Special Instructions When Configuring Oracle BAM on Separate Hosts

Installation Requirements When Using a Separate Volume or Partition

If BAMHOST1 and BAMHOST2 are using separate shared storage volumes or partitions, then you must install the Infrastructure and optionally Oracle SOA Suite on those hosts. For more information, see Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment.

Note that the location where you install the Oracle home (which contains the software binaries) varies, depending upon the host. To identify the proper location for you Oracle home directories, refer to the guidelines in File System and Directory Variables Used in This Guide.

To install the software on BAMHOST1 and BAMHOST2, log in to each host, and perform the following tasks:

Use the instructions in Installing the Oracle Fusion Middleware Infrastructure in Preparation for an Enterprise Deployment to create the Oracle home on the appropriate storage device and install Oracle Fusion Middleware Infrastructure.
Optionally, use the instructions in Installing Oracle SOA Suite for an Enterprise Deployment to install the Oracle SOA Suite software.

Parent topic: Installation Requirements When Configuring Oracle BAM on Separate Hosts

Installation Requirements When Using a Shared Oracle Home

If BAMHOST1 and BAMHOST2 are using an existing volume or partition where the Oracle Fusion Middleware Infrastructure or Oracle SOA Suite are already installed, then you must mount the volumes appropriately to BAMHOST1 and BAMHOST2. For more information, see Mounting the Required Shared File Systems on Each Host. Ensure that BAMHOST1 and BAMHOST2 have access to this Oracle home, similar to the rest of the hosts in the domain.

This is the preferred method of using shared storage for the enterprise deployment. For more information, see Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment.

After you have mounted an existing volume or partition that contains an existing Oracle home, then you should attach the Oracle home to the local Oracle Inventory on BAMHOST1 or BAMHOST2.

To attach an Oracle home in shared storage to the local Oracle Inventory, use the following command on the BAMHOSTs:

cd ORACLE_HOME/oui/bin/attachHome.sh

./attachHome.sh -jreLoc JAVA_HOME

The pack and unpack utilities is used to bootstrap the domain configuration for the WLS_BAM1 and WLS_BAM2 servers. As a result, if you have mounted an existing Oracle home with the required software already installed, then you do not need to install any software in these two hosts.

Parent topic: Installation Requirements When Configuring Oracle BAM on Separate Hosts

Configuration Wizard Instructions When Configuring Oracle BAM on Separate Hosts

If you configure Oracle BAM on separate host computers, then the instructions in this chapter for configuring the domain with the Configuration Wizard are slightly different.

Specifically, be sure to create additional Oracle WebLogic Server machines for BAMHOST1 and BAMHOST2, and then target the WLS_BAM1 and WLS_BAM2 Managed Servers to those machines, rather than to SOAHOST1 and SOAHOST2. See Task 14, "Verifying the Existing Machines" and Task 15, "Assigning Servers to Machines".

Parent topic: Special Instructions When Configuring Oracle BAM on Separate Hosts

Propagating the Domain Configuration When Configuring Oracle BAM on Separate Hosts

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.

Parent topic: Special Instructions When Configuring Oracle BAM on Separate Hosts

Roadmap for Adding Oracle BAM to the Domain

The table in this section lists the high-level steps to extend a SOA domain for Oracle Business Activity Monitoring.

Step	Description	More Information
Run the Configuration Wizard to Extend the Domain in the Administration Server domain home	Extend the SOA domain to contain Oracle BAM components.	Extending the SOA Domain to Include Oracle Business Activity Monitoring
Propagate the Domain Configuration to the Managed Server domain directories	Oracle BAM requires some updates to the WebLogic Server start scripts. Propagate these changes by using the `pack` and `unpack` commands.	Propagating the Extended Domain to the Domain Directories and Machines
Add the SOA Administrator role to the Oracle BAM Administration Group	This step allows you to use one set of credentials to access the various product-specific management utilities.	Adding the Enterprise Deployment Administration User to the Oracle BAM Administration Group
Start the Oracle BAM Servers	Oracle BAM servers extend an already existing domain. As a result, the Administration Server and respective Node Managers are already running in SOAHOST1 and SOAHOST2.	Starting and Validating the WLS_BAM1 Managed Server
Validate the WLS_BAM Managed Servers	Verify that the server status is reported as Running in the Admin Console and access URLs to verify status of servers.	Starting and Validating the WLS_BAM2 Managed Server
Configuring Oracle HTTP Server for the WLS_BAMn Managed Servers	To enable Oracle HTTP Server to route to Oracle BAM, add the required directives to the Oracle HTTP Server configuration files, and set the WebLogicCluster parameter to the list of nodes in the cluster.	Configuring Oracle HTTP Server for the WLS_BAM Managed Servers
Configure the WebLogic Server Proxy Plugin	Enable the WebLogic Server Proxy Plugin for Oracle BAM.	Configuring the WebLogic Proxy Plug-In
Validating Access Through Oracle HTTP Server	Verify that the server status is reported as Running.	Validating Access to Oracle BAM Through the Hardware Load Balancer
Configure Automatic Service Migration for the Oracle BAM Servers	Service migration ensures that key pinned services can be migrated automatically to another Managed Server in the cluster if one of the Managed Servers or host computers fails. For more information about service migration, see Using Whole Server Migration and Service Migration in an Enterprise Deployment.	Enabling Automatic Service Migration for BAM
Backing up the Oracle BAM Configuration	To back up the domain configuration for immediate restoration in case of failures in future procedures.	Backing Up the Oracle BAM Configuration

Parent topic: Extending the Domain with Business Activity Monitoring

Extending the SOA Domain to Include Oracle Business Activity Monitoring

You can use the Configuration Wizard to extend the existing enterprise deployment SOA domain with the Oracle Business Activity Monitoring.

Extending the domain involves the following tasks.

Parent topic: Extending the Domain with Business Activity Monitoring

Starting the Configuration Wizard

Note:

If you added any customizations directly to the start scripts in the domain, those are overwritten by the configuration wizard. To customize server startup parameters that apply to all servers in a domain, you can create a file called setUserOverridesLate.sh and configure it, for example, add custom libraries to the WebLogic Server classpath, specify additional JAVA command-line options for running the servers, or specify additional environment variables. Any customizations you add to this file are preserved during domain upgrade operations, and are carried over to remote servers when you use the pack and unpack commands.

To begin domain configuration:

Shut down the Administration Server to prevent any configuration locks, saves, or activations from occurring during the configuration of the domain.
Navigate to the following directory and start the WebLogic Server Configuration Wizard.
```
ORACLE_HOME/oracle_common/common/bin
./config.sh
```

Parent topic: Extending the SOA Domain to Include Oracle Business Activity Monitoring

Navigating the Configuration Wizard Screens for Oracle BAM

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

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- 12.2.1.3.0 [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.

Element Description and Recommended Value

Element	Description and Recommended Value
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	In the ONS Host field, enter the SCAN address for the Oracle RAC database. In the Port field, enter the ONS Remote port (typically, `6200`). These values are required when connecting to Oracle 11g databases but optional when connecting to Oracle database 12c and higher. If you are using an Oracle 12c database, 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.

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

In the ONS Host field, enter the SCAN address for the Oracle RAC database.

In the Port field, enter the ONS Remote port (typically, 6200).

These values are required when connecting to Oracle 11g databases but optional when connecting to Oracle database 12c and higher. If you are using an Oracle 12c database, 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	Listen Port	SSL Listen Port	SSL Enabled	Server Groups
WLS_SOA1*	SOAHOST1	8001	n/a	No	SOA-MGD-SVRS-ONLY
WLS_SOA2*	SOAHOST2	8001	n/a	No	SOA-MGD-SVRS-ONLY
WLS_WSM1	SOAHOST1	7010	n/a	No	JRF-MAN-SVR WSMPM-MAN-SVR
WLS_WSM2	SOAHOST2	7010	n/a	No	JRF-MAN-SVR WSMPM-MAN-SVR
WLS_BAM1	SOAHOST1	9001	n/a	No	BAM12-MGD-SVRS-ONLY
WLS_BAM2	SOAHOST2	9001	n/a	No	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 17-1 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	80	443
WSM-PM_Cluster	Leave it empty	Leave it empty	Leave it empty	Leave it empty
BAM_Cluster	Leave it empty	soa.example.com	80	443

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

Note:

BAM supports only static servers. Retain the default value (Unspecified) in the Dynamic Server Group field.

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:

Select the Unix Machine tab.
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.
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 Configuring Virtual Targets

Do not specify any values. Click Next.

Task 17 Configuring Partitions

Do not specify any values. Click Next.

Task 18 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 19 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 Server Administration Console and Oracle Enterprise Manager Fusion Middleware Control.

Click Finish to dismiss the Configuration Wizard.

Task 20 Start the Administration Server

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

Parent topic: Extending the SOA Domain to Include Oracle Business Activity Monitoring

Propagating the Extended Domain to the Domain Directories and Machines

After you have extended the domain with the BAM instances, and you have restarted the Administration Server on SOAHOST1, you must then propagate the domain changes to the domain directories and machines.

The following table summarizes the steps required to propagate the changes to all the domain directories and machines.

Task Description More Information

Task	Description	More Information
Pack up the Extended Domain on SOAHOST1	Use the `pack` command to create a new template jar file that contains the new BAM Servers configuration. When you pack up the domain, create a template jar file called soadomaintemplateExtBAM.jar.	Packing Up the Extended Domain on SOAHOST1
Unpack the Domain in the Managed Servers Directory on SOAHOST1*	Unpack the template jar file in the Managed Servers directory on SOAHOST1 local storage.	Unpacking the Domain in the Managed Servers Domain Directory on SOAHOST1
Unpack the Domain on SOAHOST2	Unpack the template jar file in the Managed Servers directory on the SOAHOST2 local storage.	Unpacking the Domain on SOAHOST2

Pack up the Extended Domain on SOAHOST1

Use the pack command to create a new template jar file that contains the new BAM Servers configuration.

When you pack up the domain, create a template jar file called soadomaintemplateExtBAM.jar.

Packing Up the Extended Domain on SOAHOST1

Unpack the Domain in the Managed Servers Directory on SOAHOST1*

Unpack the template jar file in the Managed Servers directory on SOAHOST1 local storage.

Unpacking the Domain in the Managed Servers Domain Directory on SOAHOST1

Unpack the Domain on SOAHOST2

Unpack the template jar file in the Managed Servers directory on the SOAHOST2 local storage.

Unpacking the Domain on SOAHOST2

*If you are configuring Oracle BAM on separate hosts, then you would unpack the domain on BAMHOST1 and BAMHOST2, rather than on SOAHOST1 and SOAHOST2.

Parent topic: Extending the Domain with Business Activity Monitoring

Adding the Enterprise Deployment Administration User to the Oracle BAM Administration Group

Before you validate the Oracle BAM configuration on the Managed Server, add the enterprise deployment administration user (weblogic_soa) to the BAMAdministrator group.

To perform this task, refer to Configuring Roles for Administration of an Enterprise Deployment.

Parent topic: Extending the Domain with Business Activity Monitoring

Starting and Validating the WLS_BAM1 Managed Server

After extending the domain, restarting the Administration Server, and propagating the domain to the other hosts, start the newly configured BAM servers.

Enter the following URL into a browser to display the Fusion Middleware Control login screen:
```
http://ADMINVHN:7001/em
```
Log in to Fusion Middleware Control by using the Administration Server credentials.
In the Target Navigation pane, expand the domain to view the Managed Servers in the domain.
Select only the WLS_BAM1 Managed Server, and click Start Up on the Oracle WebLogic Server toolbar.

Note:

BAM Servers depend on the policy access service to be functional, so the WSM-PM Managed Servers in the domain need to be up and running and reachable before the BAM servers are started.
When the startup operation is complete, navigate to the Domain home page and verify that the WLS_BAM1 Managed Server is up and running.
To verify that the BAM software is configured properly:
1. Enter the following URL in the browser:
```
http://SOAHOST1:9001/bam/composer
```
  The login screen for BAM's composer appears.
  
  If you configured Oracle BAM on separate host computers, enter BAMHOST1 in the URL, rather than SOAHOST1.
2. Enter the weblogic_soa login credentials.
  
  The BAM Composer screen appears.
Note:

To validate the server URLs, disable (set to blank) the front-end host until you have completed the configuration for the web tier. If you do not disable the front-end host, all requests fail because they are redirected to the front-end address.
Enter the following URL:
```
http://SOAHOST1:9001/inspection.wsil/
```
If you configured Oracle BAM on separate host computers, enter BAMHOST1 in the URL, rather than SOAHOST1.

You should see a response with the following list of links.

Description of the illustration bam_links.jpg
Enter the following URL in the browser:
```
http://SOAHOST1:9001/bam/cqservice/
```
If you configured Oracle BAM on separate host computers, enter BAMHOST1 in the URL, rather than SOAHOST1.

You should get a message in the browser indicating BAM CQService is running.

Parent topic: Extending the Domain with Business Activity Monitoring

Starting and Validating the WLS_BAM2 Managed Server

After you start the WLS_BAM2 managed server, you must verify that the server status is reported as Running in the Admin Console and access the URLs to verify the status of the servers.

Log in to Fusion Middleware Control by using the Administration Server credentials.
In the Target Navigation pane, expand the domain to view the Managed Servers in the domain.
Select only the WLS_BAM2 Managed Server, and click Start Up on the Oracle WebLogic Server tool bar.
When the startup operation is complete, navigate to the Domain home page and verify that the WLS_BAM2 Managed Server is up and running. Access the equivalent URLs for the WLS_BAM2:
```
http://SOAHOST2:9001/bam/composer
```
The login screen for BAM's composer appears. Enter the login credentials. The BAM composer's menu is displayed.
Enter the following URL:
```
http://SOAHOST2:9001/inspection.wsil/
```
You should see a response with a list of links.
Enter the following URL in the browser:
```
http://SOAHOST2:9001/bam/cqservice/
```
You should get a message in the browser indicating BAM CQService is running.

Note:

If you configured Oracle BAM on separate host computers, enter BAMHOST2 in the URL, rather than SOAHOST2.

Parent topic: Extending the Domain with Business Activity Monitoring

Modifying the Upload and Stage Directories to an Absolute Path

After you configure the domain and unpack it to the Managed Server domain directories on all the hosts, verify and update the upload and stage directories for Managed Servers in the new clusters. See Modifying the Upload and Stage Directories to an Absolute Path in an Enterprise Deployment.

Parent topic: Extending the Domain with Business Activity Monitoring

Configuring the Web Tier for the Extended Domain

Configure the web server instances on the web tier so that the instances route requests for both public and internal URLs to the proper clusters in the extended domain.

For additional steps in preparation for possible scale-out scenarios, see Updating Cross Component Wiring Information.

Configuring Oracle Traffic Director for the Extended Domain
Configuring Oracle HTTP Server for the WLS_BAM Managed Servers
Make the following modifications to the Oracle HTTP Server instance configuration files to ensure that the Oracle HTTP Server instances in the web tier can route Oracle BAM requests correctly to the Oracle BAM software on the Oracle SOA Suite cluster.
Configuring the WebLogic Proxy Plug-In
Set the WebLogic Plug-In Enabled parameter for the BAM cluster.

Parent topic: Extending the Domain with Business Activity Monitoring

Configuring Oracle Traffic Director for the Extended Domain

If you have configured Oracle Traffic Director for this domain, you might be required to add additional origin server pools, virtual servers, or routes to the Oracle Traffic Director configuration. To understand the Oracle Traffic Director requirements for each Oracle Fusion Middleware product and for instructions on adding origin server pools, virtual servers, and routes, see Defining Oracle Traffic Director Virtual Servers for an Enterprise Deployment.

Parent topic: Configuring the Web Tier for the Extended Domain

Configuring Oracle HTTP Server for the WLS_BAM Managed Servers

Make the following modifications to the Oracle HTTP Server instance configuration files to ensure that the Oracle HTTP Server instances in the web tier can route Oracle BAM requests correctly to the Oracle BAM software on the Oracle SOA Suite cluster.

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:

Log in to WEBHOST1 and change directory to the configuration directory for the first Oracle HTTP Server instance (ohs1):
```
cd WEB_DOMAIN_HOME/config/fmwconfig/components/OHS/ohs1/moduleconf
```

Add the following directives inside the <VirtualHost> tag in the soa_vh.conf file:

<Location /bam/composer >
  WLSRequest ON
  WebLogicCluster SOAHOST1:9001,SOAHOST2:9001
  WLProxySSL ON
  WLProxySSLPassThrough ON
</Location>

<Location /OracleBAMWS>
  WLSRequest ON
  WebLogicCluster SOAHOST1:9001,SOAHOST2:9001
  WLProxySSL ON
  WLProxySSLPassThrough ON
</Location>

<Location /oracle/bam/>
  WLSRequest ON
  WebLogicCluster SOAHOST1:9001,SOAHOST2:9001
  WLProxySSL ON
  WLProxySSLPassThrough ON
</Location>

Log in to WEBHOST2 and change directory to the following location so that you can update the configuration file for the second Oracle HTTP Server instance (ohs2):
```
cd WEB_DOMAIN_HOME/config/fmwconfig/components/OHS/ohs2/moduleconf
```
Open the soa_vh.conf file and add the BAM directives to the <VirtualHost> tag.
Restart the Oracle HTTP Server instances on WEBHOST1 and WEBHOST2.

Parent topic: Configuring the Web Tier for the Extended Domain

Configuring the WebLogic Proxy Plug-In

Set the WebLogic Plug-In Enabled parameter for the BAM cluster.

Log in to the Oracle WebLogic Server Administration Console.
In the Domain Structure pane, expand the Environment node.
Click on Clusters.
Select the BAM_Cluster cluster to which you want to proxy requests from Oracle HTTP Server.

The Configuration: General tab is displayed.
Scroll down to the Advanced section and expand it.
Click Lock and Edit.
Set the WebLogic Plug-In Enabled to yes.
Click Save, and then click Activate Changes. Restart the BAM servers for the changes to be effective.

Parent topic: Configuring the Web Tier for the Extended Domain

Validating Access to Oracle BAM Through the Hardware Load Balancer

Verify that Oracle BAM URLs are successfully routing requests from the hardware load balancer to the Oracle HTTP Server instances to the Oracle BAM software in the middle tier.

You can also use this procedure to test the failover of the Managed Servers where Oracle BAM is configured.

To verify the URLs:

While the WLS_BAM1 Managed Server is running, stop the WLS_BAM2 Managed Server by using the Oracle WebLogic Server Administration console.
Access the following URL and verify the HTTP response as indicated in Starting WLS_BAM1 Managed Server:
```
https://soa.example.com/bam/composer
```
Access the following URL to be sure the software is running as expected:
https://soa.example.com/oracle/bam/server
Start WLS_BAM2 from the Oracle WebLogic Server Administration console.
Stop WLS_BAM1 from the Oracle WebLogic Server Administration console.
Access the URL again, and verify that the HTTP response is still valid, as indicated in Starting and Validating the WLS_BAM2 Managed Server.

Parent topic: Extending the Domain with Business Activity Monitoring

Enabling JDBC Persistent Stores for BAM

Oracle recommends that you use JDBC stores, which leverage the consistency, data protection, and high availability features of an oracle database and makes resources available for all the servers in the cluster.

If you have made the following selections in the High Availability Options screen, as recommended in this guide for static clusters, then JDBC persistent stores are already configured for both JMS and TLOGS:

Set JTA Transaction Log Persistence to JDBC TLog Store.
Set JMS Server Persistence to JMS JDBC Store.

In case you did not select JDBC for JMS and TLOGS persistent in the High Availability Options screen, you can still configure JDBC stores manually in a post step. For specific instructions to configure them manually, see Using JDBC Persistent Stores for TLOGs and JMS in an Enterprise Deployment.

Parent topic: Extending the Domain with Business Activity Monitoring

Enabling Automatic Service Migration for BAM

By default, the BAM Managed Servers are always configured with Automatic Service Migration. Specific BAM migratable targets with the appropriate migration policies are created and the cluster database leasing is configured for the BAM cluster during the Configuration Wizard session.

You can validate the configuration as described in Validating Automatic Service Migration in Static Clusters.

Note:

BAM is configured for automatic service migration regardless of whether or not you select Enable Automatic Service Migration in the High Availability Options screen during domain configuration. Automatic Service Migration is a requirement for BAM because it uses singleton services.

If you configure Oracle BAM in its own domain, then you can use the BAM leasing data source (BamLeasingDatasource). However, in a more typical environment, where you are configuring both Oracle BAM with Oracle SOA suite or Oracle Service Bus, then Oracle recommends that you use a central automatic service migration data source, such as WLSSchemaDataSource that is used by the rest of the components.

Parent topic: Extending the Domain with Business Activity Monitoring

Backing Up the Configuration

It is an Oracle best practices recommendation to create a backup after you successfully extend a domain or at another logical point. Create a backup after you verify that the installation so far is successful. This is a quick backup for the express purpose of immediate restoration in case of problems in later steps.

The backup destination is the local disk. You can discard this backup when the enterprise deployment setup is complete. After the enterprise deployment setup is complete, you can initiate the regular deployment-specific Backup and Recovery process.

For information about backing up your configuration, see Performing Backups and Recoveries in the SOA Enterprise Deployments.

Parent topic: Extending the Domain with Business Activity Monitoring