You can extend your domain to include Oracle Real-Time Integration Business Insight, an application designed for business users. The application enables users to model, collect, and monitor business-level metrics using web-based dashboards, and reports.
This chapter includes the following sections:
InsightAdmin
administration role to the enterprise deployment administration group (SOA Administrators
).Parent topic: Configuring the Enterprise Deployment
As you perform the tasks in this chapter, refer 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
OHS_DOMAIN_HOME
In addition, refer the virtual IP (VIP) addresses that are defined in Physical and Virtual IP Addresses Required by the Enterprise Topology:
ADMINVHN
The actions that are described in this chapter are performed on the following host computers:
SOAHOST1
SOAHOST2
WEBHOST1
WEBHOST2
BAMHOST1
BAMHOST2
Before you add Oracle Insight to your existing Oracle SOA Suite domain, you must ensure that the prerequisites are met.
This chapter assumes that you are configuring Oracle Real-Time Integration Business Insight in a domain that is already running Oracle SOA Suite (SOA, OSB, BPM, and BAM), as shown in Figure 3-2.
In the default topology, there is no need to install Oracle Insight because Oracle Insight is included in the Oracle SOA Suite and Oracle Business Process Management distribution. Oracle Insight installed into the Oracle home directories when you install Oracle SOA Suite as illustrated in Understanding the SOA Enterprise Deployment Topology .
The schemas required for Oracle Insight are created in the database when you run the Repository Creation Utility (RCU) to create the required Oracle BAM/SOA schemas. As a result, there is no need to run RCU specifically for Oracle Insight.
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 for an Enterprise Deployment.
Before extending a SOA domain for Oracle Real-Time Integration Business Insight, familiarize yourself with the high-level steps that you must perform to extend the domain.
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 Insight components |
Extending the SOA Domain to Include Oracle Real-Time Integration Business Insight |
Propagate the Domain Configuration to the Managed Server domain directories |
Oracle Insight requires some updates to the WebLogic Server start scripts. Propagate these changes using the Pack and Unpack commands. |
Propagating the Extended Domain to the Domain Directories and Machines |
Add the SOA Administrator role to the Oracle Insight 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 Insight Administration Group |
Start the involved Servers |
Oracle Insight servers extend an existing domain. As a result, the Administration Server and the respective Node Managers are already running in SOAHOST1 and SOAHOST2. |
|
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. |
|
Update the Oracle HTTP Server for the WLS_BAM Managed Servers |
To enable Oracle HTTP Server to route to Oracle Insight, add the required directives to the Oracle HTTP Server configuration files, and then 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 Insight |
|
Validate the Access Through Oracle HTTP Server |
Verify that the server status is reported as Running. |
Validating the Access to Oracle Insight Through the Hardware Load Balancer |
This section provides instructions for extending the existing enterprise deployment SOA domain with the Oracle Real-Time Integration Business Insight.
Extending the domain involves the following tasks:
Note:
If you have added any customizations directly to the start scripts in the domain, those customizations are overwritten by the configuration wizard. To customize server startup parameters that apply to all servers in a domain, create a file called setUserOverrides.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 the remote servers when you use the Pack
and Unpack
commands.
To begin domain configuration:
Follow the instructions in these sections to create and configure the domain for the topology, with static clusters.
In this step, you extend the domain created in Extending the Domain with Business Activity Monitoring to contain Oracle Real-Time Integration Business Insight components.
Domain creation and configuration include the following tasks:
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 have created in Creating the Initial Infrastructure Domain for an Enterprise Deployment.
Tip:
For more information about the other options on this screen, see Configuration Type in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.
On the Templates screen, make sure that Update Domain Using Product Templates is selected, then select the following templates:
Insight SOA Agent - 12.2.1.2.0[soa]
Insight Service Bus Agent - 12.2.1.2.0[osb]
Insight - 12.2.1.2.0[soa]
Click Next.
On the GridLink Oracle RAC Component Schema screen, provide the information required to connect to the RAC database and component schemas, as shown in the following table.
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, |
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, |
Enable Fan |
Verify that the Enable Fan check box is selected, so the database can receive and process FAN events. |
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.
Click Next to continue.
The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. Review the details of each item on the screen and verify that the information is correct.
Click Update.
In the Extending Domain screen, click Done.
Start the Administration Server to ensure the changes you have made to the domain have been applied.
After you have extended the domain with the Insight components, 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 |
---|---|---|
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 |
|
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. |
*If you are configuring Oracle BAM on separate hosts, then you would unpack the domain on all nodes: BAMHOST1, BAMHOST2, SOAHOST1 and SOAHOST2.
Before you validate the Oracle Insight configuration on the Managed Server, add the InsightAdmin
administration role to the enterprise deployment administration group (SOA Administrators
).
To perform this task, refer to Configuring Roles for Administration of Oracle SOA Suite Products.
After extending the domain, restarting the Administration Server, and propagating the domain to the other hosts, start the configured SOA, OSB, and BAM servers.
If you have not already started the managed servers, follow the instructions in this section to start and validate WLS_BAM1 and WLS_BAM2.
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.
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.
Make the following modifications to the Oracle HTTP Server instance configuration files to ensure that the Oracle HTTP Server instances in the Web tier routes Oracle Insight requests correctly to the Oracle Insight software on the Oracle SOA, OSB, and BAM clusters.
These instructions assume that you are configuring Oracle BAM/Insight on the same host as Oracle SOA Suite. If you are using separate hosts for Oracle BAM/Insight, 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 Insight:
Verify that Oracle Insight URLs are successfully routing requests from the hardware load balancer to the Oracle HTTP Server instances to the Oracle Insight software in the middle tier.
You can also use this procedure test the failover of the Managed Servers where Oracle Insight is configured.
To verify the URLs:
As a best practice, Oracle recommends you to create a backup after successfully extending a domain or at another logical point. Create a backup after verifying that the installation done until the point at which you decide to create the backup is successful. A quick backup is used for the express purpose of immediate restoration if problems are encountered 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.