Bill,

Thanks so much for the detailed instructions. However, nothing came through attached. Would you mind e-mailing the files to dcarabetta (at) gmail.com? Also, I assume that I'll be able to deploy directly to a J2EE ColdFusion instance using the exe installer in a subsequent beta? I used the WAR deployment option for CFMX, as I've always found that setup much easier than the EAR deployment option. My directory setup for CFMX 7.01 is:

D:\JRun4\servers\cfmx7\cfusion

(again, note that it's not at the default C:\ location)

And that's the only instance (other than the JRun admin instance) that I have right now. I only point all this out because I want to make sure that my setup (which is pretty vanilla as far as the J2EE CFMX setup process goes) will eventually be covered by the one-click installer you provided on the Labs site.

Regards,
Dave.



On 3/14/06, Bill Sahlas <[EMAIL PROTECTED]> wrote:
Hi Dave -
 
The current beta installer  is designed to only update the initial CF instance in your multi-instance CFMX install - not a JRun 4 deployment. 
 
Currently the beta 1 version has a bug and doesn't make the correct modification to the web.xml file on the "multi-server installer" (that's option #2 of the CFMX 7.01 installer)  but all the needed files are deployed to the correct location.  The one scenario that the installer isn't designed to handle is when the installer is a pure J2EE app server installer like JRun 4 install where you've also (appserver/jrun/lib/jrun-comp.ear) installed CF using the J2EE option (appserver/jrun/servers/cfmx/cfusion/)  The instructions should be sufficient to get you going for the J2EE app servers like JRun 4 and CF J2EE.
 
Below find the instructions on what you need to add to the web.xml file and instructions for both Flex Builder 2 and FES2 messaging/cf flex event gateway.
 

For Flex Builder 2 connectivity

 

1) modify /WEB-INF/web.xml for you're deployed server

Add this to the Servlet section

 

   <!-- start flex2 Servlet -->
    <servlet>
        <servlet-name>MessageBrokerServlet</servlet-name>

 

        <servlet-class>coldfusion.bootstrap.BootstrapServlet</servlet-class>

 

        <init-param>
            <param-name>servlet.class</param-name>
            <param-value>flex.messaging.MessageBrokerServlet</param-value>
            <param-name>services.configuration.file</param-name>
            <param-value>/WEB-INF/flex/flex-enterprise-services.xml</param-value>
        </init-param>
        <load-on-startup>1</load-on-startup>
    </servlet>
    <!-- end flex2 Servlets -->

 

 

Add this down near the bottom of the file in the servlet-mapping section

    <!-- start flex 2 -->
  <servlet-mapping  id="macromedia_mapping_0">
        <servlet-name>MessageBrokerServlet</servlet-name>
        <url-pattern>/flex2gateway/*</url-pattern>
    </servlet-mapping>
     <!-- end flex 2 -->

2) Make this dir C:\JRun4\servers\cfusion\cfusion-ear\cfusion-war\WEB-INF\flex and add the attached flex-enterprise-services.xml .

3) Modify flex-enterprise-services.xml - find the channel-definition id="my-cfamf" and make the endpoint uri= match your environment.  It defaults to

 <endpoint uri="http://localhost:8500{context.root}/flex2gateway/ " class="flex.messaging.endpoints.AMFEndpoint"/> so if you're got cf running off http://localhost:8300/cfusion then you'd have

 <endpoint uri="http://localhost:8300/cfusion/flex2gateway/ " class="flex.messaging.endpoints.AMFEndpoint"/>

4) copy the attached flashremoting_update.jar and flex-messaging.jar and put these under C:\JRun4\servers\cfusion\cfusion-ear\cfusion-war\WEB-INF\cfusion\lib

 

For the FlexMessaging Gateway all you'll need to do is

 

1) put the attached flex-messaging-gateway.jar file under C:\JRun4\servers\cfusion\cfusion-ear\cfusion-war\WEB-INF\cfusion\gateway\lib (flex-messaging-gateway.cfg is only a sample and isn't needed)

2) in the unzip the eventgateway.zip file under your C:\JRun4\servers\cfusion\cfusion-ear\cfusion-war\CFIDE\administrator\ which will replace the ones that you've got with the updated version that includes the FlexMessaging Gateway. 

3) Download the instructions and docs from the Mystic downloads page on the mmbeta site to familiarize yourself with both of these implementations.  There's tutorials on how to setup samples of both of these implementations  Using ColdFusion MX with Flex 2 (PDF) .

 

 

NOTE: if you've got FES Beta I installed it includes both /flex and /samples applcations and maybe more than that.  If you want to you can restrict what Flex loads by modifying the C:\fes2\jrun4\servers\default\SERVER-INF\jrun.xml

 

Replace the <service class="..."></service> section that says This Service handles application deployment with this one.

  <!-- ================================================================== -->
  <!-- This Service handles application deployment                        -->
  <!-- ================================================================== -->
  <service class="jrun.deployment.DeployerService" name="DeployerService">
    <attribute name="bindToJNDI">true</attribute>
    <!-- <attribute name="deployDirectory">{jrun.server.rootdir}</attribute> -->
    <attribute name="temporaryDirectory">{jrun.server.rootdir}/SERVER-INF/temp</attribute>
    <attribute name="persistXML">false</attribute>
    <attribute name="validateXML">false</attribute>
    <attribute name="file">{jrun.home}/lib/jrun-comp.ear</attribute>
    <!-- <attribute name="file">{jrun.server.rootdir}/samples/</attribute> -->
     <attribute name="file">{jrun.server.rootdir}/flex/</attribute>
    <attribute name="hotDeploy">true</attribute>
    <service name="Flex Web Application Factory" class="jrun.servlet.WebApplicationFactory">
      <attribute name="mandatoryFingerPrint">WEB-INF/flex/flex-config.xml</attribute>
    </service>
  </service>

 
 
For the J2EE appserver + CFMX J2EE deploys you may need to copy the flex-messaging-logins.jar and backport-util-concurrent.jar files from your FES2 install.


From: [email protected] [mailto:[email protected]] On Behalf Of Dave Carabetta
Sent: Tuesday, March 14, 2006 9:55 AM
To: Flex Coders
Subject: [flexcoders] Flex 2: ColdFusion Updater Install Issues with FES

I've been trying to avoid using this list for install support, but
I've tried the Labs Forums, two blogs, and another flex2dev mailing
list that I don't think works anymore, so I'm out of options...

I'm trying to get the Flex/ColdFusion Connectivity installer available
on the Labs site (cf_flexconnect_b1_0123_en.exe) to run, and I'm
constantly hung up on the first step after selecting the "Multiserver"
option where it asks where ColdFusion MX 7 is located. The default
path listed is C:\JRun4. My install is at D:\JRun4. I changed it to
that but I got this: "The specified directory D:\JRun4 does not
contain a valid JRun root directory." and I cannot continue. I then
add one directory at a time all the way down to my ColdFusion MX 7
instance (through the /WEB-INF/cfusion directory, and through my
/CFIDE directory) and I get the same exact error, except with the
added directories listed.

Does the installer not work with a path other than C:\JRun4 or
something? The forums are getting next to no traffic in the relevant
categories, and even fewer responses at that. I really want to dig
into FES with ColdFusion, but it won't work if I can't get this
installed.

Anybody have any thoughts? I'm desperate.

Regards,
Dave.


--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS






--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




Reply via email to