Administering ColdFusion MX
Basic ColdFusion MX Administration

Extensions section

You use the Extensions section of the Administrator to configure ColdFusion MX to work with other technologies, such as Java and CORBA. This section contains the Java Applets, CFX Tags, Custom Tag Paths, and CORBA Connectors pages.

Java Applets page

The Java Applets page of the Administrator lets you register applets and edit and delete applet registrations. Before you can use Java applets in your ColdFusion applications, you must register them in the Java Applets page.

When your applet is registered with ColdFusion MX, using the cfapplet tag in your CFML code is very simple, because all parameters are predefined. Simply enter the applet source and the form variable name you want to use.

Note:   Parameters set in the cfapplet tag override parameters defined in the Java Applets page.

For more information, see the online Help.

CFX Tags page

Before you can use a CFX tag in ColdFusion applications, you must register it. You use the CFX Tags page to register and manage ColdFusion custom tags built with C++ and Java.

You can build CFX tags in the following two ways:

• Using C++ as a dynamic link library (DLL) in Windows; as shared objects (so/sl) on Solaris, Linux, and HP-UX
• Using Java interfaces defined within the cfx.jar file

For more information, see the online Help.

Custom Tag Paths page

You use the Custom Tag Paths page of the Administrator to add, edit, and delete custom tag directory paths. The default custom tag path is under the installation directory. To use custom tags in another path, register the path on this Administrator page.

For more information, see the online Help.

CORBA Connectors page

You use the CORBA Connectors page of the Administrator to register, edit, and delete CORBA connectors. You must register CORBA connectors before using them in your ColdFusion applications. You must also restart the server when you are done with the CORBA Connector configuration.

ColdFusion MX loads ORB libraries dynamically 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 cfusionmx/runtime/lib.

The following table contains information about the libraries and connectors:

Operating System	Vendor	ORB	ColdFusion connector	ORB library
Windows NT	Borland	VisiBroker 4.5	coldfusion.runtime.corba.VisibrokerConnector (embedded)	vbjorb.jar
Solaris	Borland	VisiBroker 4.5	coldfusion.runtime.corba.VisibrokerConnector (embedded)	vbjorb.jar
HP-UX	Borland	VisiBroker 4.5	coldfusion.runtime.corba.VisibrokerConnector (embedded)	vbjorb.jar

Note:   Macromedia will provide implementations of the connectors for some of the popular ORBs. For those that are not supported, Macromedia will make the source available under NDA to a select group of third-party candidates and/or ORB vendors.

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:\neo\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

Copyright © 2002, Macromedia Inc. All rights reserved.

Comments