Powered by Zoomin Software. For more details please contactZoomin

DataDirect OpenAccess SDK Help

Specifying Primary and Alternate Servers

  • Last Updated: May 12, 2026
  • 1 minute read
    • OpenAccess SDK
    • Version 9.0
    • Documentation

Connection information for primary and alternate servers can be specified using either a connection URL through the JDBC Driver Manager or a JDBC data source. For example, the following connection URL for the JDBC Client specifies connection information for the primary and alternate servers using a connection URL:

jdbc:openaccess://server1:20092;serverDataSource=SDSN1;User=test; Password=secret;AlternateServers=(server2:20092;serverDataSource=SDSN2,server3:20092;serverDataSource=SDSN3)

In this example:

...server1:20092;serverDataSource=SDSN1...

is the part of the connection URL that specifies connection information for the primary server. Alternate servers are specified using the AlternateServers property. For example:

...;AlternateServers=(server2:20092;serverDataSource=SDSN2,
server3:20092;serverDataSource=SDSN 3)

Similarly, the same connection information for the primary and alternate servers specified using a JDBC data source would look like this:

OpenAccessDataSource mds = new OpenAccessDataSource();
mds.setDescription("My OpenAccessDataSource");
mds.setServerName("server1");
mds.setPortNumber(20092);
mds.setServerDataSource("SDSN1");
mds.setUser("test");
mds.setPassword("secret");
mds.setAlternateServers(server2:20092;serverDataSource=SDSN2, server3:20092;ServerDataSource=SDSN3)

In this example, connection information for the primary server is specified using the ServerName, PortNumber, and serverDataSource properties. Connection information for the alternate servers is specified using the AlternateServers property.

TitleResults for “How to create a CRG?”Also Available inAlert