Allan: Regarding #2 below, I assume you mean create a virtual directory of /CFIDE that points to CFIDE in the system?
CF mappings on Standard are server-wide, and they're server-wide on Enterprise unless you're using Sandboxing to lock them down. If you create a virtual directory, all your servers will be able to hit http://my.url.com/cfide/administrator/index.cfm, whereas using a mapping enables just directory access without exposing CFIDE in the webroot of the application. Having the files accessible from the cfchart tag should only need the mapping because it relies on the accessibility of the files, not on being able to use them in a browser. And if you're using mappings, you only need 1 per CF instance, barring any sandboxing. Also, anything you need universally can go in {cfhome}\wwwroot because that's basically a universal mapping. If you put CFIDE in it, beware, though...by default it will be available to the browser from all sites, all URLs connected to that CF instance via a webserver connector. Now JrunScripts is a different matter, because for some reason that's always a virtual directory... when you create it (in each site that will be accessing CF), you're going to need to edit the properties and add the Jrun Server Filter in the ISAPI filters tab and in the Virtual Directory properties tab for the directory click Remove against the application attributes and uncheck Read. If you check your wwwroot/web-inf/web.xml file, you'll see that GraphData.cfm is a servlet mapping, so adding a CF template to /cfide wouldn't do much. It's the same as IDE.cfm, which is the servlet mapping for RDS... these can be executed from a browser via the URL specified, but they're trapped by Jrun and mapped out to specific servlets for special handling. It's basically Jrun spoofing a CFM template to the CF server. Matthew, you said these image files were being created correctly, right? Do they look like they should even if they're not being sent back to the browser? Have you checked (or had the host check) windows and CF error logs? There should be something. If the issue was the result of a headless Win install, chances are that the graphing subsystem would fail during CFMX bootstrap... that's how it works on Linux, and also the primary cause of CFCHART issues on linux. People fail to understand that CFMX needs the basic X libraries to get cfchart to work. If you do a view source after hitting a page that's got a CFChart in it, you should see some URL information that's used to transfer the images/movies from the Chart servlet to the browser... trying hitting that URL alone and seeing what error message you get. Go from there, paying particular attention to paths, virtual or otherwise, that are missing or incorrect. Good luck! J On 6/10/05, Allan Cliff <[EMAIL PROTECTED]> wrote: > > If I remember correctly. > What you have to do is. > > 1. Create the file CFIDE/GraphData.cfm (Put a comment only in it) > 2. Create a mapping for EACH site to CFIDE (C:\Inetpub\wwwroot\CFIDE) > and > JRunScripts (C:\CFusionMX7\runtime\lib\wsconfig\1) > 3. Restart CFMX server and Bob should be your Uncle. > > Allan > -- --------------- ------------------------------------- Buy SQLSurveyor! http://www.web-relevant.com/sqlsurveyor Never make your developers open Enterprise Manager again. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209216 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
