MACROMEDIA COLDFUSION 5 - CFML Manual de usuario descargar pdf (Pagina 9)

If “Separate user name and password authentication” is selected (an option available only on 

the Enterprise and Developer editions), then both a username and password would be required

to access the server via RDS, where the usernames are dened in the Administrator page

Security > User Manager.

Discussion of the User Manager interface is beyond the scope of this article. By default there

are no congured user accounts. To enable user-based access you must rst create user

accounts and passwords, and assign roles to those accounts. To use the debugger, such

a user would need the Allow RDS Access option enabled. He does not need to be given

any Admin access. You may notice an available sandbox role that you could allow called

Debugging and Logging > Debugging, but that’s for accessing the debugging page in the

Admin console.

If you’re having any problems getting the CF8 debugger to work, rst conrm whether the

RDS setup on Eclipse is working for the connection to the server. Look at the tool in Window

>Show View > Other > ColdFusion and then use either the RDS Fileview or RDS Dataview

tools to conrm that you can connect to the server using one of them. If not, then you won’t

be able to do debugging.

In the CF8 debugger, it’s possible to enable multiple developers to debug a single server.

To do this, set the RDS conguration above, using multiple user accounts. Additionally, a

setting in the ColdFusion 8 Administrator, Debugging & Logging > Debugger Settings >

Maximum Simultaneous Debugging Sessions, which defaults to ve, also controls how

many developers can do debugging at once or how many single developers can start

multiple debugging sessions.

Conguring the Multiserver or J2EE Conguration

There are a couple of nal points to make regarding the use of ColdFusion in the Multiserver

(multiple instance) or J2EE congurations (as opposed to the perhaps more commonly used

Standalone conguration of ColdFusion).

With the Standalone edition, when you enable the debugger in the ColdFusion 8

Administrator, ColdFusion automatically modies the jvm.cong for the server. With the

Multiserver or J2EE congurations, ColdFusion requires that you make the change yourself,

adding the following string to the end of the java.args line:

-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005

Use whatever port you would have entered in the ColdFusion Admin page for enabling line

debugging. Whenever you have to modify your jvm.cong, be sure to rst make a backup of

the le, because if you make a mistake then the ColdFusion server won’t be able to start.

Second, in the Multiserver conguration, each instance (the ColdFusion instance, the admin

instance, and any new instances you create) will by default share a single jvm.cong. That’s

acceptable in simple setups, but when using the debugger you may nd that you need to

create a separate jvm.cong for each instance. Some do that anyway, perhaps to create dierent

congurations (and therefore dierent jvm.cong les) for each instance with dierent JVM

memory, or dierent garbage collection, or even dierent JVMs. You can nd a couple of blog

entries discussing how to setup dierent jvm.cong les for each instance, at:

http://mkruger.cfwebtools.com/index.cfm/2006/4/17/multiserver

http://www.alagad.com/go/blog-entry/cf7-cf8-jrun-and-the-jvm

The Fusion Authority Quarterly Update Tools 95

1 2 3 4 5 6 7 8 9 10 11

Comentarios a estos manuales

Sin comentarios

MACROMEDIA COLDFUSION 5 - CFML Manual de usuario Pagina 9

Comentarios a estos manuales

Relacionado con productos y manuales para No MACROMEDIA COLDFUSION 5 - CFML