Scribd
Upload
127 views

OSM Multi-Data Source Config Using N-RAC Nodes - Updated

Oracle Communications Order and Service Management (OSM) can be configured to use an active-active Oracle Real Application Cluster (RAC) with multiple database nodes for high availability and scalability. The document describes how to configure OSM to connect to additional RAC nodes beyond the two nodes supported by the OSM installer. It involves manually creating JDBC data sources for each RAC node and configuring a multi data source to balance connections across the RAC nodes. WebLogic server nodes are partitioned among the RAC nodes to ensure order affinity and even load distribution.

Uploaded by

manualph
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
127 views

OSM Multi-Data Source Config Using N-RAC Nodes - Updated

Oracle Communications Order and Service Management (OSM) can be configured to use an active-active Oracle Real Application Cluster (RAC) with multiple database nodes for high availability and scalability. The document describes how to configure OSM to connect to additional RAC nodes beyond the two nodes supported by the OSM installer. It involves manually creating JDBC data sources for each RAC node and configuring a multi data source to balance connections across the RAC nodes. WebLogic server nodes are partitioned among the RAC nodes to ensure order affinity and even load distribution.

Uploaded by

manualph
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Oracle Communications Order and Service

Management (OSM)
Configuring OSM with multiple database nodes in an Oracle
Real Application Cluster (RAC)

Multi data source configuration using N-RAC nodes:


Since Oracle Communications Order and Service Management 7.2.0 GA, OSM has had the
capability to use Oracles Real Application Cluster in an active-active configuration for
availability and scalability at the database tier. The OSM installer supports the ability to set up a
two-node active-active Oracle RAC cluster, however the OSM application is able to support
additional RAC nodes beyond two, which can be manually added as a post installation activity.
This document describes how OSM is configured to support multiple RAC nodes from the
managed server nodes in a WebLogic cluster, and how to configure additional RAC nodes if you
wish to have an OSM cluster that utilizes an active-active RAC cluster of more than two nodes.
During installation, the OSM installer prompts for the database parameters of the Oracle RAC
instances and automatically creates the appropriate configuration in a JDBC multi data source. If
you decide to manually configure your JDBC data source, you must understand the following
discussion.
At the application layer, OSM maintains an affinity between WebLogic Servers and orders this
is called order affinity. That is, all processing of an order is performed exclusively by one
WebLogic Server instance at a time to minimize synchronization between WebLogic cluster
nodes. Similarly, at the database layer to ensure efficiency and scalability of a RAC cluster, the
OSM application needs to ensure all database operations for a particular order maintained by a
WebLogic Server instance are directed to the same Oracle RAC instance. Thus, the approach to
preserve Database Server order affinity is to have each WebLogic Server instance connect to
only one Oracle RAC instance at a time.
OSM uses a multi data source consisting of two data sources, each of which connects to an
Oracle RAC database instance. Using the failover algorithm, the first data source is the primary
data source and the other data source is the secondary data source. Under normal operation, only
the primary data source is connected and used. When the primary data source fails, the multi data
source chooses the next available data source as the primary data source.
In an active-active Oracle RAC, WebLogic Server nodes are partitioned. In a two-node activeactive Oracle RAC, half of the WebLogic Server nodes are configured to one Oracle RAC
database instance as their primary data source, and to the other Oracle RAC database instance as
the secondary data source. The other half of the WebLogic Server nodes are configured with the
sequence of the Oracle RAC database instances swapped. As a result, if one of the Oracle RAC
database instances fails, half the WebLogic Server nodes fails over to the remaining Oracle RAC
database instance, which is already handling the database operations of the other half of the
WebLogic Server nodes in the WebLogic cluster.
Extending this to a three node active-active Oracle RAC, the WebLogic server cluster would be
divided into three groups of equal size. The first group of WebLogic servers would need to be
configured to the first Oracle RAC database instance as their primary data source, the next group
would be configured to use the second Oracle RAC database instance as their primary data
source, and the last group of WebLogic servers would use the third Oracle RAC database

instance as their primary data source. The same logic is used for a 4 node Oracle RAC
configuration (divide WebLogic servers into 4 groups), and a 5 node (divide WebLogic servers
into 5 groups), and so on.

Data Source Configuration for Oracle RAC Active


Active-Active

Manually Creating and Configuring the Data Source


This section describes the steps required to manually create and configure additional data sources
for an Oracle RAC instance. Inn an active
active-active configuration you create data sources equal to
the number of nodes.
To create and configure an additional data source for an Oracle RAC instance:
1. Log in to the WebLogic Administration Server Console.
2. In the Domain Structure tree, expand Services, JDBC, then select Data Sources.
Sources
3. On the Summary of JDBC Data Sources page, click New.
4. On the JDBC Data Sources Properties page, do the following:
o Enter a name for the JDBC data source.
 If you have an active
active-active configuration, name the data
sources osm_pool_rac<<ID>>
osm_pool_rac<<ID>>_group_<<ID>> and osm_pool_rac<<ID

>>_group_<<ID>>. Example:
osm_pool_rac2_group_a and osm_pool_rac2_group_b.
o Enter a unique JNDI name for the data source. For
example, oracle/communications/osm/internal/jdbc/pool_2.
o Select Oracle as the database type.
o Click Next.
5. Select one of the following non-XA thin drivers:
o If your Oracle RAC database is configured with local listeners, select *Oracle's
Driver (Thin) for Instance connections; Versions: 9.0.1 and later.
o If your Oracle RAC database is configured with a remote listener (the default),
select *Oracle's Driver (Thin) for RAC Service-Instance connections;
Versions: 10 and later.
o Click Next.
6. On the Transaction Options page, do the following:
o Ensure the default option Supports Global Transactions is selected.
o Select the option Logging Last Resource.
o Click Next.
7. On the Connection Properties page, specify the service name, database name, host, and
port of the additional Oracle RAC instance based on one of the following scenarios:
o If your Oracle RAC database is configured with a remote listener and server-side
load balancing (the default), the host and port of the new data source must be the
same as the host and port of the existing data source. Additionally, if the existing
data source specifies a service name and the instance name of the Oracle RAC
instance, the new data source must also specify the service name and instance
name of the Oracle RAC instance. (The instance name is required in order to
override server-side load balancing. See "Listener Considerations for Oracle
RAC" for a full discussion of listener functionality.)
For example, if the existing data source URL is:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HO
ST=host5.us.oracle.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=orcl)(INST
ANCE_NAME=orcl1)))
The new data source URL is:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HO
ST=host5.us.oracle.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=orcl)(INST
ANCE_NAME=orcl2)))
o If your Oracle RAC database is configured with local listeners, the host and port
of the new data source must be different than the host and port of the existing data
source. If the existing data source specifies a service name, the new data source
must specify the same service name.
o Enter the OSM database schema user name and password, and then confirm the
password.
o Click Next.
8. On the Test Database Connection page, review the connection parameters and click Test
Configuration.

WebLogic attempts to create a connection from the administration server to the database. Results
are displayed at the top of the page. If the test is unsuccessful, you should correct any
configuration errors and retry the test.
If the JDBC driver you selected is not installed on the administration server, you should
click Next to skip this step.
Click Next.
9. On the Select Targets page, do the following:
o Target the data source to part of the cluster. For example,
target osm_pool_rac2_group_a to osm1 and osm_pool_rac2_group_b to osm2.
10. Click Finish.
Your configuration is saved and the data source is deployed to the cluster.
11. Configure the connection properties for the newly created data source.
12. Add the data source to the preconfigured multi data source.
Configuring Connection Pool Properties
In addition to the properties you defined in the previous section, you must configure the data
source's connection pool properties.
To configure the connection pool properties, do the following:
1. Select the data source and navigate to the Connection Pool tab.
2. In the Properties list, enter oracle.net.CONNECT_TIMEOUT=10000.
3. In the Initial Capacity field, enter 0.
4. Click Advanced options.
5. Select the Test Connections on Reserve check box.
6. In the Test Frequency field, enter 300.
7. In the Test Table Name field, enter SQL SELECT 1 FROM DUAL.
8. In the Seconds to Trust an Idle Pool Connection, enter 10.
9. In the Shrink Frequency field, enter 900.
10. Save your changes.
Adding the Data Source to the Multi Data Source
You can make all data source and multi data source changes in a single edit session. You do not
have to save your changes between steps.
To add the new data source to the multi data source:
1. In the Domain Structure tree, expand Services, then select Data Sources.
2. On the Summary of Data Sources page, click the multi data source name.
3. Click the Configuration Data Sources tab, and the following:
o Add the data sources to the multi data sources in the order specified for 2 RAC
nodes as example:
 Multi data source oms_pool_group_a must contain the two data
sources osm_pool_rac1_group_a and osm_pool_rac2_group_a, in this
order.
 Multi data source oms_pool_group_b must contain the two data
sources osm_pool_rac2_group_b and osm_pool_rac1_group_b, in this
order.

Note:
Oracle recommends that you shut down all managed servers before changing the order of the
data sources in the list because the first data source in the list is used to compose the name of
the Oracle Coherence cluster when OSM starts.
4. Save your changes.

Sample configuration for 4 Active RAC nodes:


For using more than 2 active RAC nodes, we have to change the configuration manually after the
installer setup; to support n active RAC nodes. The following diagram illustrates the
configuration for 4 Active RAC nodes.
With this architecture, starting up WebLogic managed servers 1 through 4 would interact with
separate db instances.

Here is the configuration files attached for this setup:

jdbc.7z

You might also like