7 RAC Support

This section describes necessary modifications of an Agile e6.2.0.0 installation, including deployed Business Services, to support a RAC database.

Note: For more information about RAC architecture, please see also the Architecture Guide for Agile e6.2.0.0

We recommend performing the RAC database setup, and Agile e6.2.0.0 adaptations with the help of an Oracle consultant.

7.1 Prerequisites

1. RAC database is running.

   Oracle consulting has reviewed and approved the RAC database installation.

2. Necessary changes in tnsnames.or and sqlnet.ora on the Oracle client side, where the EDM server is running, are carried out.

3. Oracle WebLogic server is installed and running.

4. Follow the installation instruction for Agile e6.2.0.0 as described in the Server Installation Guide on Windows and UNIX for Agile e6.2.0.0.

5. For the RAC support, the following needs to be changed:

   • In the "Reference Configuration" mask you have to provide the following entries:

     • As "SQLNet Connect" add the net alias for your RAC database in tnsnames.ora.

     • As SID select the SID of one of the instances of your RAC database.

     • As "Host Name" add the IP address/hostname where this instance is running.

   The following screenshot shows an example configuration.

   
   

6. Continue the installation instruction for Agile e6.2.0.0 as described in the Server Installation Guide on Windows and UNIX for Agile e6.2.0.0.

7. Please adapt the configuration for the data source definition to benefit from the Fast Connection Failover (FCF) feature.

   If an instance is down, the J2EE components will continue to work normally using any other available instance of the RAC database.

   
   

   Note: Please review the process described in chapter Deploying Customer Adapted Files.

   
   

8. Copy the original file from the "product" folder to the related "custom" folder:

   <ep_root>/staging/product/application/<application_name>/BusinessService/META-INF/eSeriesDataSource_<application_name>.xml
   

   To:

   <ep_root>/staging/custom/application/<application_name>/BusinessService/META-INF/eSeriesDataSource_<application_name>.xml
   

9. Change the file as shown in this example.

   <name>eSeriesDataSource_yin_app</name>
   <jdbc-driver-params>
     <url>jdbc:oracle:thin:@rac-scan.example.com:1521/plm62</url>
     <driver-name>oracle.jdbc.pool.OracleDataSource</driver-name>
     <properties>
       <property>
         <name>user</name>
         <value>plm62</value>
       </property>
       <property>
         <name>FastConnectionFailoverEnabled</name>
         <value>true</value>
       </property>
       <property>
         <name>ConnectionCachingEnabled</name>
         <value>true</value>
       </property>
     </properties>
     <password-encrypted>XXX</password-encrypted>
   </jdbc-driver-params>
   <jdbc-connection-pool-params>
     <initial-capacity>5</initial-capacity>
     <max-capacity>100</max-capacity>
     <connection-reserve-timeout-seconds>10</connection-reserve-timeout-seconds>
     <inactive-connection-timeout-seconds>1800</inactive-connection-timeout-seconds>
     <test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
   </jdbc-connection-pool-params>
   <jdbc-data-source-params>
     <jndi-name>eSeriesDataSource_yin_app</jndi-name>
     <global-transactions-protocol>OnePhaseCommit</global-transactions-protocol>
     <scope>Application</scope>
   </jdbc-data-source-params>
   <jdbc-oracle-params>
     <fan-enabled>true</fan-enabled>
     <ons-node-list>db1.example.com:6200,db2.example.com:6200
     </ons-node-list>
   </jdbc-oracle-params>
   

10. Redeploy Business Service.

7.2 Limitation

The Agile e6 Configurator application uses a special connection which connects only to the instance provided in the "Reference Configuration" mask. If this instance is down, then the Configurator will not work anymore. If you use the Configurator, you must adapt the connection information for the Configurator to connect to a running database instance.

Note: This limitation is only valid for the Agile e6 Configurator. All other applications (e.g. Workflow, Permission Manager) support the RAC database.