Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Andy Casey (AndyC853) Quad Graphics Inc
Quad Graphics Inc
US
AndyC853 Member since 2017 4 posts
Quad Graphics Inc
Posted: Nov 1, 2017
Last activity: Nov 24, 2017
Posted: 1 Nov 2017 10:00 EDT
Last activity: 24 Nov 2017 7:37 EST
Closed
Solved

Using TNS names Pega 7.2 and Tomcat 8.5.16

Hi,

We're currently in the process of migrating our Pega implementation from the cloud to an on premise server. We currently have Tomcat setup to point to Oracle with the entries like the one below in our context.xml. This works fine but we'd prefer to have Tomcat pull the url info from the TNSNAMES.ORA file that is managed by our database team so we don't have to worry about manually updating the Tomcat config if addresses are added/removed to the address list. Is it possible to reference a server in Tomcat just by the address name in the TNS names file?

<Resource name="jdbc/PegaDATA"
auth="Container"
type="javax.sql.DataSource"
driverClassName="oracle.jdbc.OracleDriver"
url="jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=xxxxx)(PORT = yyyy)))(CONNECT_DATA=(SERVICE_NAME=zzzzz)))"
username="user"
password="pw"
maxTotal="100"
maxIdle="30"
maxWaitMillis="10000"
/>

To see attachments, please log in.
System Administration Installation and Deployment Data Integration

Posted: 6 years ago
Posted: 1 Nov 2017 12:35 EDT
Ankur Das (@nkur.das_GCS) Principal Software Solutions Engineer
Pegasystems Inc.
US

Hi Andy, 

I see that your JDBC URL uses a TNS keyword-value pair connection string to connect to your database. This is primarily used / recommended from connecting from thick client applications like (Java SWINGs/ Applet/ Java). 

However, Oracle recommends the following URL connection string for Datasources while connecting from Application server. This is for the same reason / problem you are trying to address. 

jdbc:oracle:thin:@HOST_NAME:PORT_NUMBER:SERVICE_NAME

As you can see from the format above, the connection String in the Tomcat's DataSource config simply refers to the Oracle database SERVICE_NAME. The connection resolution happens at based on the ADDRESSES defined on tnsnames.ora and there is no hard coupling of the TNS ADDRESS in the Datasource connection string.

Discuss internally to see if you can use/test the above recommended connection string style to solve your problem.

To see attachments, please log in.
Posted: 6 years ago
Posted: 1 Nov 2017 14:57 EDT
Andy Casey (AndyC853) Quad Graphics Inc
Quad Graphics Inc
US
Thanks for the response.  The problem is our production server will be on one of 3 clusters.  I'm assuming that format wouldn't work since we'd have 3 different host names.  The entry for our production server in the tns names file looks something like this:
  (DESCRIPTION = 
    (ADDRESS_LIST = 
       (ADDRESS = (PROTOCOL = TCP)(HOST = cluster1)(PORT = 1234))
  (ADDRESS = (PROTOCOL = TCP)(HOST = cluster2)(PORT = 1234)) 
  (ADDRESS = (PROTOCOL = TCP)(HOST = cluster3)(PORT = 1234))
) 
(CONNECT_DATA = (SERVICE_NAME = xxxx) )
To see attachments, please log in.

Accepted Solution

Posted: 6 years ago
Posted: 24 Nov 2017 7:37 EST
Andy Casey (AndyC853) Quad Graphics Inc
Quad Graphics Inc
US

The DBA's ended up creating a gateway that we could use as a host name which allowed us to go with the simple syntax.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice