Hmm... Also, just realized that the article is talking about Adobe CF. Well,
I think the principle is probably very similar. It's probably a matter what
what DLL you point it to...

Sorry if I wasn't much help after all... :o/

Chris

On Tue, Dec 16, 2008 at 1:37 PM, Chris Jordan <[email protected]>wrote:

> What you need to do to get IIS to handle all your .cfm files is add a Web
> Service Extension in the IIS admin (this was true for IIS6 and I think
> probably for IIS7).
>
> Check out this article:
> http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_18689
>
> Again, it's talking about IIS6, but it's a starting point. Maybe this bit
> didn't change between IIS6 and IIS7, who knows?
>
> Hope that helps,
> Chfis
>
>
> On Tue, Dec 16, 2008 at 1:13 PM, Rob <[email protected]> wrote:
>
>>
>> Aloha All,
>>
>> I have been very happy with migrating everything from BlueDragon to
>> openBD and now OpenBD 1.0
>>
>> I currently use the Jetty bundled release, and have it running on
>> Windows XP Pro and VISTA home.  I need to install my main application
>> on a 2003 server, running IIS 7.0.
>>
>> I cannot figure out how to get the IIS to point cfm extensions to
>> openBD.  For Blue Dragon, I had the BlueDragon Adapter dll.  Is there
>> something comperable?   I see the BlueDragonAdapter.jar file, but
>> don't know if that works with IIS (initial tests say no).
>>
>> Any ideas?
>>
>> I will be one of many apps on this 2003 server, and port 80 will be
>> for the IIS 7.0.  I would prefer to not have to use a different port
>> for my application.  I can get Jetty and IIS running side by side by
>> using different ports, but that is my least attractive solution.
>>
>> Thanks in advance for your help.
>>
>> Rob
>> >>
>>
>
>
> --
> http://cjordan.us
>



-- 
http://cjordan.us

--~--~---------~--~----~------------~-------~--~----~
Open BlueDragon Public Mailing List
 http://groups.google.com/group/openbd?hl=en
 official blog @ http://blog.openbluedragon.org/
!! save a network - trim replies before posting !!
-~----------~----~----~----~------~----~------~--~---

Reply via email to