![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Good Day, Could you provide an example for using Java Code in order to connect to ASA 11 + High Availability..? The docs do not include a guides for this environment.. just for a regular java app connecting t a single node Thank you JMT |
#3
| |||
| |||
|
|
Good Day, Could you provide an example for using Java Code in order to connect to ASA 11 + High Availability..? The docs do not include a guides for this environment.. just for a regular java app connecting t a single node Thank you JMT |
#4
| |||
| |||
|
|
First things first you must be using the iAnywhere JDBC driver and *not* JConnect [JConn does not use the correct protocol to do this]. After that it should just be a matter of using the correct connection string [same as ODBC, E/SQL, OLEDB . . . .] If your client software is 10.0.x+ you simply need to specify the alternate-server-name in your ENG= or ServerName= connection parameter and the client libraries and servers will figure it out after that point. [Note: the alternate-server-name is defined at the mirror/primary servers via the -sn switch.] "Jose-Miguel Torres" wrote in message news:4ae86345.1f62.1681692777 (AT) sybase (DOT) com... Good Day, Could you provide an example for using Java Code in order to connect to ASA 11 + High Availability..? The docs do not include a guides for this environment.. just for a regular java app connecting t a single node Thank you JMT |
#5
| |||
| |||
|
|
Nick is right. There is no ALTERNATIVE_SERVER_NAME connection property available in the jConnect driver at this time. The jConnect team is working on providing support for SQL Anywhere HA in the next release. There is no set date for this release at this time. -- Joshua Savill Sybase Inc. - Product Manager Nick Elson [Sybase iAnywhere] wrote: First things first you must be using the iAnywhere JDBC driver and *not* JConnect [JConn does not use the correct protocol to do this]. After that it should just be a matter of using the correct connection string [same as ODBC, E/SQL, OLEDB . . . .] If your client software is 10.0.x+ you simply need to specify the alternate-server-name in your ENG= or ServerName= connection parameter and the client libraries and servers will figure it out after that point. [Note: the alternate-server-name is defined at the mirror/primary servers via the -sn switch.] "Jose-Miguel Torres" wrote in message news:4ae86345.1f62.1681692777 (AT) sybase (DOT) com... Good Day, Could you provide an example for using Java Code in order >> to connect to ASA 11 + High Availability..? The docs do not include a guides for this environment.. >> just for a regular java app connecting t a single node Thank you JMT |
#6
| |||
| |||
|
|
Nick /Joshua Thanks a lot ! I'll try that JMT Nick is right. There is no ALTERNATIVE_SERVER_NAME connection property available in the jConnect driver at this time. The jConnect team is working on providing support for SQL Anywhere HA in the next release. There is no set date for this release at this time. -- Joshua Savill Sybase Inc. - Product Manager Nick Elson [Sybase iAnywhere] wrote: First things first you must be using the iAnywhere JDBC driver and *not* JConnect [JConn does not use the correct protocol to do this]. After that it should just be a matter of using the correct connection string [same as ODBC, E/SQL, OLEDB . . . .] If your client software is 10.0.x+ you simply need to specify the alternate-server-name in your ENG= or ServerName= connection parameter and the client libraries and servers will figure it out after that point. [Note: the alternate-server-name is defined at the mirror/primary servers via the -sn switch.] "Jose-Miguel Torres" wrote in message news:4ae86345.1f62.1681692777 (AT) sybase (DOT) com... Good Day, Could you provide an example for using Java Code in order >> to connect to ASA 11 + High Availability..? The docs do not include a guides for this environment.. >> just for a regular java app connecting t a single node Thank you JMT |
#7
| |||
| |||
|
|
JMT, If you want to use jConnect, then you'll need to download EBF 16508 or higher of 6.05 for HA support with SQL Anywhere. You can find the jConnect download at downloads.sybase.com. The current EBF is the following: jConnect for JDBC - EBF 16903: 6.05 ESD #16 6.0.5 11 Jun 2009 EBF/Patch -- Joshua Savill Sybase Inc. - Product Manager Jose-Miguel Torres wrote: Nick /Joshua Thanks a lot ! I'll try that JMT Nick is right. There is no ALTERNATIVE_SERVER_NAME connection property available in the jConnect driver at >> this time. The jConnect team is working on providing support for SQL Anywhere HA in the next release. There is >> no set date for this release at this time. -- Joshua Savill Sybase Inc. - Product Manager Nick Elson [Sybase iAnywhere] wrote: First things first you must be using the iAnywhere JDBC >>> driver and *not* JConnect [JConn does not use the correct protocol to do this]. After that it should just be a matter of using the correct connection string [same as ODBC, E/SQL, OLEDB . . .] If your client software is 10.0.x+ you simply need to specify the alternate-server-name in your ENG= or ServerName= connection parameter and the client libraries and servers will figure it out after that point. [Note: the alternate-server-name is defined at the mirror/primary servers via the -sn switch.] "Jose-Miguel Torres" wrote in message news:4ae86345.1f62.1681692777 (AT) sybase (DOT) com... Good Day, Could you provide an example for using Java Code in order >> to connect to ASA 11 + High Availability..? The docs do not include a guides for this environment.. >> just for a regular java app connecting t >> a single node Thank you JMT |
#8
| |||
| |||
|
|
Joshua, Thanks again.! We'll try the ianywhere driver first and see how it goes from there. Anyway , i'll let you know. Regards Jose-Miguel JMT, If you want to use jConnect, then you'll need to download EBF 16508 or higher of 6.05 for HA support with SQL Anywhere. You can find the jConnect download at downloads.sybase.com. The current EBF is the following: jConnect for JDBC - EBF 16903: 6.05 ESD #16 6.0.5 11 Jun 2009 EBF/Patch -- Joshua Savill Sybase Inc. - Product Manager Jose-Miguel Torres wrote: Nick /Joshua Thanks a lot ! I'll try that JMT Nick is right. There is no ALTERNATIVE_SERVER_NAME connection property available in the jConnect driver at >> this time. The jConnect team is working on providing support for SQL Anywhere HA in the next release. There is >> no set date for this release at this time. -- Joshua Savill Sybase Inc. - Product Manager Nick Elson [Sybase iAnywhere] wrote: First things first you must be using the iAnywhere JDBC >>> driver and *not* JConnect [JConn does not use the correct protocol to do this]. After that it should just be a matter of using the correct connection string [same as ODBC, E/SQL, OLEDB . . .] If your client software is 10.0.x+ you simply need to specify the alternate-server-name in your ENG= or ServerName= connection parameter and the client libraries and servers will figure it out after that point. [Note: the alternate-server-name is defined at the mirror/primary servers via the -sn switch.] "Jose-Miguel Torres" wrote in message news:4ae86345.1f62.1681692777 (AT) sybase (DOT) com... Good Day, Could you provide an example for using Java Code in order >> to connect to ASA 11 + High Availability..? The docs do not include a guides for this environment.. >> just for a regular java app connecting t >> a single node Thank you JMT |
![]() |
| Thread Tools | |
| Display Modes | |
| |