AMXBPM 4.2 - Update JDBC Resource Templates to reference Oracle tnsnames.ora file

AMXBPM 4.2 - Update JDBC Resource Templates to reference Oracle tnsnames.ora file

book

Article ID: KB0079472

calendar_today

Updated On:

Products Versions
TIBCO BPM Enterprise (formerly TIBCO ActiveMatrix BPM) 4.2.0

Description

In general when we change the database details we have to update the AMXBPM JDBC Resource Templates.

Is there a way to reference the Oracle tnsnames.ora file path an hold the database details in the TNS Name entry?

If the database is migrated then only the entry in the tnsnames.ora file will be changed.

 

Issue/Introduction

In general when we change the database details we have to update the AMXBPM JDBC Resource Templates. Is there a way to reference the Oracle tnsnames.ora file path an hold the database details in the TNS Name entry? If the database is migrated then only the entry in the tnsnames.ora file will be changed.

Environment

TIBCO ActiveMatrix BPM (Oracle) 4.2.0

Resolution

An existing AMXBPM installation can be updated to use a TNS Names entry.
 
The JDBC URL can be modified to use a tnsnames.ora entry rather than specify the database server, port and service names.
 
The tnsnames.ora file must be accessible in the same path on all AMXBPM servers e.g. /opt/tnsadmin
 
The Unix user that runs AMXBMPM on each server must have permission to open this file.
 
The Java option oracle.net.tns_admin must be set on the all System and BPM Nodes to provide the directory containing the tnsnames.ora file.
 
1 Add the java option to the existing System and BPM Nodes – this includes SystemNodeReplica and BPM Nodes on all servers e.g.
    In the AMX Admin UI go to each node in turn (Infrastructure -> Nodes)
    Select the node
    Select the “Configuration” tab and select “JVM Configuration”
    Under “Properties” click the “Add” icon
    For the property name enter ->       oracle.net.tns_admin
    For the property value enter ->      /opt/tnsadmin
    When the property is added the node will go out-of-sync
    With the node highlighted select “Install or Sync” on the menu under “Nodes”
    Wait for the node to synchronise with the new setting.
    Repeat the above for each System and BPM Node.
 
2 Stop and start all nodes associated with the System and BPM applications
    The nodes will start with the oracle.net.tns_admin property
 
3 After the restart check that:
    a The oracle.net.tns_admin property is set on each node (System and BPM)
    b The  amx.bpm.ap is fully started and in the “Running” state
 
4 Update the BPM JDBC Resource templates with the new JDBC URL to reference the tnsnames.ora file
    In our example test environment this means changing the JDBC URL from:
        jdbc:oracle:thin:@db1srv:1521:ora12
    to:
        jdbc:oracle:thin:@ORA12
 
   BPM 4.2.0 has three JDBC resource templates – update each one in turn and set the URL to one that uses the tnsnames.ora file.  Save each template as modifications are made and apply the changes to the runtime environment.
 
   The JDBC resource templates names are:
       1 DataSource
       2 DataSourceBDS
       3 DataSourceDirect
 
   For 1 & 2 the URL is set in the General page in the “Database URL” property
   For 3 the URL is set in the “Advanced” tab in the connection property “URL”
 
   Update each resource template in turn in the AMX Admin User Interface under:
  Shared Objects -> Resource Templates
 
   As you save each JDBC resource template a dialogue box will be displayed “Apply changes in resource template to runtime”
 
   Click on “Save” to apply the changes to the runtime environment – this will re-install the Resource Instances on BPM Nodes.
 
   (Make sure that the resource template and BPM Environment is selected – they should be by default).
 
   After updating each resource template make sure that the Resource Instance in the “Running” and “In Sync” on each BPM Node. This can take a while depending on the performance of the AMXBPM servers and nodes.
 
5 Stop all BPM Nodes
 
6 Start all BPM Nodes

 
The above add the oracle.net.tns_admin property to existing nodes only – it does not change the default values for new nodes. 
Any new nodes will not have the oracle.net.tns_admin property configured –these must be configured manually using the above steps.