Macromedia colfusion mx 7 Manual

Descargar
Página de 72
Disabling Remote Development Services
59
4.
Prepare your CORBA server side, as follows: 
a
Start your Visibroker osagent service or process, if it is not already running, by entering the 
following command: 
osagent
Note: If you must connect to an osagent in another subnetwork, include the following lines in 
the vbjorb.properties file:
vbroker.agent.addr=<IP address of machine running OSAGENT>
vbroker.agent.port=<port>
b
Start the Interface Repository and load it with the IDL file that you plan to use, by entering 
an 
irep
 command, as in the following example: 
irep myir MyIDLFile.idl 
c
(Optional) Start the Naming Service by entering a command like the following: 
nameserv namingroot 
Note: The name of the Naming Service (namingroot in the previous example) must match the 
value for SVCnameroot in the vbjorb.properties file. 
d
Start Visibroker on your CORBA server.
For more information, see the Borland Visibroker documentation.
5.
Restart ColdFusion MX 7 for your changes to take effect.
For more information, see 
.
You can now make CORBA invocations from ColdFusion MX 7. For more information about 
integrating CORBA objects into ColdFusion MX 7, see ColdFusion MX Developer’s Guide.
Disabling Remote Development Services
If you use Macromedia Dreamweaver MX or Macromedia HomeSite+ to develop your 
applications, you can access a remote ColdFusion MX 7 server using HTTP. However, you must 
configure Remote Development Services (RDS) in your integrated development environment 
(IDE), and RDS must be enabled in ColdFusion MX 7. Using RDS, IDE users can securely 
access remote files and data sources, build SQL queries from these data sources, and debug CFML 
code.
Note: The ColdFusion Report Builder uses RDS for the Query Builder and for charting support.
However, for security reasons, Macromedia recommends that you disable RDS on a production 
server. To disable it, you must disable the RDSServlet mapping.
To disable the RDSServlet mapping:
1.
Back up the web.xml file.
This file is in the cf_root\wwwroot\WEB-INF directory in Windows and in the 
cf_root/wwwroot/WEB-INF directory on UNIX. In the multiserver and J2EE configurations, 
this file is under cf_webapp_root/WEB-INF.
2.
Open the original web.xml file for editing.