Use the CORBA Connectors page to register, edit, and delete CORBA connectors. You must register CORBA connectors before you use them in ColdFusion applications. You must also restart the server when you finish configuring the CORBA connector.
ColdFusion loads object request broker (ORB) libraries dynamically by using a connector, which does not restrict ColdFusion developers to a specific ORB vendor. The connectors depend on the ORB runtime libraries provided by the vendor. A connector for Borland Visibroker is embedded within ColdFusion. Make sure that the ORB runtime libraries are in cf_root/runtime/lib (server configuration) or cf_webapp_root/WEB-INF/cfusion/lib (multiserver and J2EE configurations).
The following table contains information about the libraries and connectors:
Operating System |
Vendor |
ORB |
ColdFusion connector |
ORB library |
---|---|---|---|---|
Windows NT and later |
Borland |
VisiBroker 4.5 |
coldfusion.runtime.corba.VisibrokerConnector (embedded) |
vbjorb.jar |
Solaris |
Borland |
VisiBroker 4.5 |
coldfusion.runtime.corba.VisibrokerConnector (embedded) |
vbjorb.jar |
The following lines are an example of a CORBA connector configuration for VisiBroker:
ORB Name visibroker ORB Class Name coldfusion.runtime.corba.VisibrokerConnector ORB Property File c:\ColdFusion8\runtime\cfusion\lib\vbjorb.properties Classpath [blank]
ColdFusion includes the vbjorb.properties file, which contains the following properties that configure the ORB:
org.omg.CORBA.ORBClass=com.inprise.vbroker.orb.ORB org.omg.CORBA.ORBSingletonClass=com.inprise.vbroker.orb.ORB SVCnameroot=namingroot