In EAServer 6.0, each connection manager that supports C/C++ and PowerBuilder components has its own connection library. In earlier versions of EAServer, a single connection library libjcm.dll (Windows) or libjcm.so (Solaris) handled all connection management for native connections. Separating the connection managers allows for smaller client or server footprints, and simplifies connection management.
C/C++ and PowerBuilder components require connections that are created using C/C++ code. To support C/C++ connections, EAServer 6.0 provides the new database types listed in Table 1. To manage each C/C++ connection, EAServer creates a Java object, which supports the JDBC API.
Database type |
Java connection library |
C/C++ connection library |
---|---|---|
JCM_Sybase |
libjcm_sybase.dll |
libct.dll |
JCM_Odbc |
libjcm_odbc.dll |
odbcad32.dll |
JCM_Odbc_Unicode |
libjcm_odbcu.dll |
odbcad32.dll |
JCM_Oracle |
libjcm_oracle.dll |
oci.dll |
JCM_Oracle_Unicode |
libjcm_oracleu.dll |
oci.dll |
See the EAServer CORBA Components Guide.