user manual

Chapter 27: Using VisiConnect 325
Other Considerations
com.borland.enterprise.visiconnect.DataSource or the
com.borland.enterprise.visiconnect.cci.ConnectionFactory interfaces.
3 Update the classes in the ra.xml standard deployment descriptor file. For
example, before extending the interfaces, the ra.xml may look something
like this:
<managedconnectionfactory-
class>com.borland.enterprise.connector.serial.
LocalTxManagedConnectionFactory</managedconnectionfactory-class>
<connectionfactory-interface>javax.sql.DataSource</connectionfactory-
interface>
<connectionfactory-impl-
class>com.borland.enterprise.connector.serial.JdbcDataSource</
connectionfactory-impl-class>
<connection-interface>java.sql.Connection</connection-interface>
<connection-impl-
class>com.borland.enterprise.connector.serial.JdbcConnection</
connection-impl-class>
4 After extending the interfaces, the ra.xml may look something like this:
<managedconnectionfactory-
class>com.borland.enterprise.connector.serial.LocalTxManagedConnectionFa
ctory</managedconnectionfactory-class>
<connectionfactory-
interface>com.borland.enterprise.visiconnect.DataSource</
connectionfactory-interface>
<connectionfactory-impl-
class>com.borland.enterprise.connector.serial.RemoteJdbcDataSource</
connectionfactory-impl-class>
<connection-interface>java.sql.Connection</connection-interface>
<connection-impl-
class>com.borland.enterprise.connector.serial.JdbcConnection</
connection-impl-class>
As this illustrates, this conversion impacts the connection factory only. No
other Resource Adapter classes are affected by this conversion.
1 Compile the Java code for the extended interface and implementation into
class files.
2 Package these into the Resource Adapter's Java Archive (.jar) file.
3 Update the Resource Adapter Archive (.rar) file with this extended .jar.
4 Deploy the Resource Adapter Archive, or include it in a Enterprise
Application Archive (.ear) file to be deployed as part of a J2EE application,
to VisiConnect running standalone or as a partition service in the Borland
Enterprise Server.
You now have a Remote Connector. The Resource Adapter's connection
factory will be registered in JNDI via CosNaming. You can browse this using
the JNDI Browser in the Console. Any CORBA client can now use this
Connector. The client can be written in any language which has an IDL