Thank you for the information. Without the jrunfilter line, Flash Remoting did not work, and presumably graphing was also knocked out. However, I think I have it working reasonably well now. Magnus.conf is the file that stores the global variables and functions used for iPlanet/Sun One. The following line is what seems to define the jrunfilter function:
Init fn="jruninit" serverstore="C:/CFusionMX/runtime/lib/wsconfig/1/jrunserver.store" bootstrap="127.0.0.1:51010" verbose="false" apialloc="false" ssl="false" ignoresuffixmap="false"
Changing ignoresuffixmap="false" to "true" is the trick that fixes remoting. The jrunfilter now only applies to directory mappings, not extension mappings. So /flashservices gets trapped by the filter, while .cfm falls through to the extension handling code where the decision to use CF5 or CFMX is made.
The following link describes this process:
http://www.corfield.org/blog/past/2004_03.html
I am not sure if this is the most efficient way to handle the situation. I briefly looked into context roots, but everything I found was regarding J2EE installs of CF.
Thank you,
Mike Chabot
>> Does anyone know what the following line accomplishes in
>> obj.conf in a Sun One/iPlanet Web server?
>>
>> NameTrans fn="jrunfilter"
>> serverstore="C:/CFusionMX/runtime/lib/wsconfig/1/jrunserver.st
>> ore" bootstrap="127.0.0.1:51010"
>
>I'm no expert with iPlanet. However, I think that this enables an NSAPI
>filter. It sounds to me like NSAPI behaves a bit like IIS's ISAPI. Within
>ISAPI, you can have filters and extensions. Filters are run at the beginning
>of the HTTP request processing pipeline, while extensions are run later on.
>ISAPI extensions are mapped to specific file extensions, while filters are
>processed for every request.
>
>There's some CFMX functionality which requires this sort of filter - the
>ability to run servlets and the Flash Remoting gateway. There may be other
>functionality dependent on this, but I'm not aware of it.
>
>
>In my experience with IIS, I generally leave both the ISAPI filter and
>extension enabled. However, it seems to work well enough with the filter
>disabled and just the extension enabled, aside from the aforementioned
>servlets and Flash Remoting stuff.
>
>Honestly, I don't really know why (or whether) both are needed - the filter
>seems like it would be sufficient. Perhaps it's just set up that way for
>redundancy.
>
>> Are there any other ways to do what I am trying to do?
>
>Yes, there may be. One way you can configure CFMX is with a context root,
>which basically limits the filter to only accepting requests that map to a
>specific directory. When you install CFMX onto a J2EE server, you're asked
>for a context root during the EAR/WAR creation process. You should be able
>to specify the directory name as the context root, and CFMX should only then
>process requests within that directory. I haven't specifically set CFMX up
>this way with a CF 5 server, though, so this is conjecture on my part.
>
>Dave Watts, CTO, Fig Leaf Software
>http://www.figleaf.com/
>phone: 202-797-5496
>fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
