Hello EDQ Experts ,
I have a technical question regarding the creation of data store in EDQ . Our client has several cluster data bases which should act as the sources to the EDQ process. Generally they connect to the cluster database using the servicename which can point to any one of the three database servers. Given below is an example of the TNS file entry to connect to the cluster database.
(ADDRESS = (PROTOCOL = TCP)(HOST = xxxxprd01-vip.main.xxxxx.com)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = xxxxprd02-vip.main.xxxxx.com)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = xxxxprd03-vip.main.xxxxx.com)(PORT = 1521))
(LOAD_BALANCE = yes)
(SERVER = DEDICATED)
(SERVICE_NAME = BIPRD)
While creating the EDQ datastore, it ask for a host name and SID. In this case, there is no one host name and SID. Client do not want to pin point the connection to any one server since the load balancing will not work in that case.
Can you please suggest any possible option to handle this scenario.
There are three ways to do this.
1. Use a JNDI data store connection that is configured on the app server and just specify the JNDI name in EDQ. This is fine as long as the app server can handle complex connect strings like the one you specified.
2. Use an Oracle TNS data store connection. This option will appear in the Data Store setup wizard if you set the oracle.net.tns_admin Java system property to the directory containing tnsnames.ora. Note that there is no need for Oracle client software to be installed - just the tnsnames.ora file. This is normally done by creating a file called jvm.properties in your EDQ config directory, or you can set the property in the app server when setting up EDQ (for example -d oracle.net.tns_admin = c:\temp)
3. Use an Oracle LDAP data store connection. This also requires setting Java system properties, such as these:
dn.oracle.directory.servers = ldap://servername:port
dn.oracle.default.admin.context = dc=datanomic,dc=local
The first property gives the location of the LDAP server(s), the second sets the context within the LDAP tree. These properties are used to construct an Oracle/LDAP JDBC connection string, which looks something like:
Edited by: MikeMatthews on Nov 12, 2012 4:37 AM