Adobe 38043740 - ColdFusion Standard - Mac Development Manual page 1156

DEVELOPING COLDFUSION 9 APPLICATIONS
Using Web Elements and External Objects
If the assemblies are on a remote system, you install and use the ColdFusion .NET extension software on the .NET
system to create Java proxies for the .NET classes, and then move or copy them to the ColdFusion system. Also edit
the JNBDotNetSide.exe.config file on the remote system to specify the .NET classes you use. The .NET system requires
the following .NET extension software:
• JNBDotNetSide.exe, the .NET-side agent that communicates with the ColdFusion system (normally run as the
ColdFusion .NET service).
• JNBDotNetSide.exe.config, a configuration file that identifies the .NET assemblies that ColdFusion can access.
• jnbproxy.exe and jnbproxyGui.exe are command line and GUI-based programs that generate the Java proxies that
represent the .NET assemblies.
• Additional support files, including JNBShare.dll, which invoke the .NET assembly classes.
For information on installing the ColdFusion .NET extension, see Installing ColdFusion guide.
Note: When you install a new .NET version, reinstall the ColdFusion .NET extension.
Accessing .NET assemblies
ColdFusion provides two methods for accessing .NET assemblies:
• A local access method for .NET objects that are installed on the ColdFusion system
• A remote access method for .NET objects located on other systems.
For both methods, install the ColdFusion .NET extension and run the ColdFusion .NET service on the system that
hosts the assemblies. You need not install the extension or run the service on a ColdFusion system that accesses only
remote assemblies. For information on installing the ColdFusion .NET extension, see Installing ColdFusion guide.
Accessing local assemblies
For local access, ColdFusion automatically generates and uses proxies for the required .NET assemblies when you first
use the tag or
cfobject CreateObject
assembly proxies each time.
Usually when you are accessing local .NET assemblies, you do not have to override the default communication
configuration settings. Sometimes you could have to specify these settings, however. If other software on your system
uses the default 6086 port, for example, change the port number specification in the jnbridge\DotNetSide.exe.config
file, and specify the changed port number in your
the port number specification, see
To use the local access method, use the
can use the resulting ColdFusion object to construct the .NET object, call the .NET object's methods, and access its
fields. For detailed information on using .NET classes, see
Accessing remote assemblies
The remote access technique accesses .NET assemblies by using TCP or HTTP to communicate with a .NET-side agent
on a remote system. You create proxy instances and call assembly methods as you do in the Local access method, but
first configure the remote .NET-side agent and, in most cases, the proxy classes that represent the remote .NET classes.
Configure remote .NET access
1 On the remote system, install the ColdFusion .NET integration software and run the .NET-side agent (see Installing
ColdFusion guide).
function. ColdFusion caches the proxies for future use, so it does not generate
tag or
cfobject
"Configuring the .NET-side
tag or
cfobject CreateObject
"Using .NET
Last updated 1/20/2012
tag. For information on changing
CreateObject
system" on page 1154,
function to create and access the proxy. You
classes" on page 1155.
1151