Distributed ColdFusion

Ask a Question related to Coldfusion Server Administration, Design and Development.

  1. #1

    Default Distributed ColdFusion

    Is it absolutely necessary to have the ColdFusion files on both the Web Server
    and the App Server? The Web Server is running IIS and the App Server is
    running ColdFusion MX 7.1 Enterprise. ColdFusion 5.0 did not require the
    ColdFusion files to be on both machines. Maybe there is some kind of registry
    hack or something.

    TFMX Guest

  2. Similar Questions and Discussions

    1. Coldfusion distributed IIS conection
      Hello, I need some help to understand what goes into the ISAPI conection from a IIS server and a ColdFusion one. The IIS machine: Windows 2003 and...
    2. ColdFusion MX 7 - Distributed Mode and Context Root
      Hey all, I'm currently using ColdFusion MX 7 (multi-server) on JRun in a distributed mode (i.e. I have 1 to N separate physical apache servers...
    3. Distributed Deployment
      Hi, I am working on a ASP.NET Web Application that uses some business logic dlls (all written in .NET). If I deploy the business logic dlls to...
    4. Distributed Transaction Error
      Hi there We have a asp page in which we are making some update calls connecting to SQL Server 2000. it's been done by...
    5. Coordinated Distributed Transactions
      > In the CLI guid it says i cannot use SQLEndTran(), but what should i use? Huh? I think you've mistyped "cannot" for "must". According to the...
  3. #2

    Default Re: Distributed ColdFusion

    Actually no. The Web server holds your static content and the web
    connector, which points back to to your J2EE app server containing
    your CFMX application, which holds your .cfm,cfc files.

    In my distributed situation I was using Apache 2; however, I doubt
    there would be any differences based on the HTTP server.

    This distributed infrastructure approach is designed to split the code
    into two places and macromedia recommends the split. Because some
    people were putting all content back to the J2EE layer for simplicity
    in deployment, performance was dragging. This, as you well know, puts
    extra burden on the CFMX application to host static content when that
    is what the HTTP layer is supposed to be optimally designed for. That
    and the needless extra communication involved with hosting static
    content from the app server layer both will drain resources and
    performance dramatically depending on usage.

    So are you having a problem? Are you sure your web connector is
    configured properly?

    LinuxInductee Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139