21 Extending the Domain with Oracle Real-Time Integration Business Insight
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 by using web-based dashboards, and reports.
This chapter includes the following sections:
- Variables Used When Configuring Business Insight
As you perform the tasks in this chapter, refer to the directory variables that are listed in this section. - Prerequisites for Adding Oracle Insight to the Domain
Before you add Oracle Insight to your existing Oracle SOA Suite domain, you must ensure that the prerequisites are met. - Roadmap for Adding Oracle Insight to the Domain
Before you extend an SOA domain for Oracle Real-Time Integration Business Insight, familiarize yourself with the high-level steps that you must perform to extend the domain. - Extending the SOA Domain to Include Oracle Real-Time Integration Business Insight
This section provides instructions for extending the existing enterprise deployment SOA domain with the Oracle Real-Time Integration Business Insight. - Propagating the Extended Domain to the Domain Directories and Machines
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. - Starting and Validating Managed Servers after Adding Insight
After you extend the domain with Insight, you must restart the servers, add the InsightAdmin Role to the administrators group, and then validate the access to Insight and the BAM URLs. - 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 the Access to Oracle Insight Through the Hardware Load Balancer
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. - Adjusting JTA Values for Insight Models
- Backing Up the Configuration
As a best practice, Oracle recommends you to create a backup after you successfully extended a domain or at another logical point. Create a backup after you verify 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.
Parent topic: Configuring the Enterprise Deployment
Variables Used When Configuring Business Insight
As you perform the tasks in this chapter, refer to 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
-
WEB_DOMAIN_HOME
In addition, refer to 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
Prerequisites for Adding Oracle Insight to the Domain
Before you add Oracle Insight to your existing Oracle SOA Suite domain, you must ensure that the prerequisites are met.
About Installation Requirements for Adding Oracle Insight to the Domain
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.
See the following sections:
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 is installed in the Oracle home directories when you install Oracle SOA Suite as illustrated in Understanding the SOA Enterprise Deployment Topology.
Parent topic: Prerequisites for Adding Oracle Insight to the Domain
About Database Schema Requirements for Oracle Insight
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 and SOA schemas. As a result, there is no need to run RCU specifically for Oracle Insight.
Parent topic: Prerequisites for Adding Oracle Insight 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 for an Enterprise Deployment.
Parent topic: Prerequisites for Adding Oracle Insight to the Domain
Roadmap for Adding Oracle Insight to the Domain
Before you extend an 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 by using the |
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 |
Extending the SOA Domain to Include Oracle Real-Time Integration Business Insight
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:
Starting the Configuration Wizard
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 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 the remote servers when you use the Pack
and Unpack
commands.
To begin domain configuration:
Navigating the Configuration Wizard Screens for Oracle Insight
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:
- 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 have 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:
For more information about the other options on this screen, see Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.
- Task 2 Selecting the Configuration Template
-
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.3.0 [soa]
-
Insight Service Bus Agent - 12.2.1.3.0 [osb]
-
Insight - 12.2.1.3.0 [soa]
Click Next.
-
- Task 3 Providing the GridLink Oracle RAC Database Connection Details
-
All fields are pre-populated, because you already configured the domain to reference the Fusion Middleware schemas that are required for the domain. Insight uses the existing Datasources for SOA and no new Datasources need to be added to the domain.
Note:
Any custom datasources that were created before the extension (like LEASING datasources) will show up before this screen. Check the Datasources row and click Next. The test datasource screen will verify its validity. Click Next.
- Task 4 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 5 Selecting Advanced Configuration
-
Click Next to continue.
- Task 6 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 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.
Tip:
More information about the options on this screen can be found in Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.
- Task 7 Writing Down Your Domain Home and Administration Server URL
-
The Configuration Success screen will show the following items about the domain you just configured:
-
Domain Location
-
Administration Server URL
You must make a note of both items as you will need them later; the domain location is needed to access the scripts used to start the Administration Server, and the URL is needed to access the Administration Server.
Click Finish to dismiss the configuration wizard.
-
- Task 8 Starting the Administration Server
-
Start the Administration Server to ensure the changes you have made to the domain have been applied.
Propagating the Extended Domain to the Domain Directories and Machines
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 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.
Starting and Validating Managed Servers after Adding Insight
After you extend the domain with Insight, you must restart the servers, add the InsightAdmin Role to the administrators group, and then validate the access to Insight and the BAM URLs.
- Starting the Managed Servers
After extending the domain, restarting the Administration Server, and propagating the domain to the other hosts, start the configured SOA, OSB, and BAM servers. - Adding the InsightAdmin Role to the Administrators Group
When the startup operation is complete and before you validate the Oracle Insight configuration on the Managed Server, add theInsightAdmin
administration role to the enterprise deployment administration group (SOA Administrators
). - Validating the Managed Servers After Adding Insight
Starting the Managed Servers
After extending the domain, restarting the Administration Server, and propagating the domain to the other hosts, start the configured SOA, OSB, and BAM servers.
Adding the InsightAdmin Role to the Administrators Group
When the startup operation is complete and 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, see Configuring Roles for Administration of Oracle SOA Suite Products.
Validating the Managed Servers After Adding Insight
When the managed servers are started and the InsightAdmin Role is added to the Administrators Group, validate the access to Insight and BAM URLs.
Note:
If a front-end address was configured for the clusters, ensure that you have defined the required URLs in the Web Tier (OHS or OTD) for a successful Insight verification.
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 routes Oracle Insight requests correctly to the Oracle Insight software on the Oracle SOA, OSB, and BAM clusters.
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 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 use separate hosts for Oracle BAM and 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:
Parent topic: Configuring the Web Tier for the Extended Domain
Validating the Access to Oracle Insight Through the Hardware Load Balancer
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:
Adjusting JTA Values for Insight Models
To increase the JTA timeout periods, follow these steps:
- Log in to Weblogic Console.
- Click the Data Sources link.
- Select
BamDataSource
from the Data Sources shown in the table. - Navigate to the Transaction tab.
- Enable Set XA Transaction Timeout.
- Set XA Transaction Timeout to zero (0).
This procedure sets the BamDataSource JTA
timeout to the same value as the domain timeout, which is 30 seconds by default. However, you may need to adjust the global domain and Distributed_Lock_Timeout
in the database for appropriate behavior. As a generic rule, the database's Distributed_Lock_Timeout
must be larger than the XA DS Timeout which in turn much be equal or larger than the domain's Global Transaction Timeout
. For more details about processing transactions and manage transaction timeouts, see Introducing Transactions in Developing JTA Applications
for Oracle WebLogic Server.
Backing Up the Configuration
As a best practice, Oracle recommends you to create a backup after you successfully extended a domain or at another logical point. Create a backup after you verify 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.