User manual MACROMEDIA COLDFUSION MX 61 CONFIGURING AND ADMINISTERING COLDFUSION MX

[. . . ] Configuring and Administering ColdFusion MX Trademarks Afterburner, AppletAce, Attain, Attain Enterprise Learning System, Attain Essentials, Attain Objects for Dreamweaver, Authorware, Authorware Attain, Authorware Interactive Studio, Authorware Star, Authorware Synergy, Backstage, Backstage Designer, Backstage Desktop Studio, Backstage Enterprise Studio, Backstage Internet Studio, ColdFusion, Design in Motion, Director, Director Multimedia Studio, Doc Around the Clock, Dreamweaver, Dreamweaver Attain, Drumbeat, Drumbeat 2000, Extreme 3D, Fireworks, Flash, Fontographer, FreeHand, FreeHand Graphics Studio, Generator, Generator Developer's Studio, Generator Dynamic Graphics Server, JRun, Knowledge Objects, Knowledge Stream, Knowledge Track, Lingo, Live Effects, Macromedia, Macromedia M Logo & Design, Macromedia Flash, Macromedia Xres, Macromind, Macromind Action, MAGIC, Mediamaker, Object Authoring, Power Applets, Priority Access, Roundtrip HTML, Scriptlets, SoundEdit, ShockRave, Shockmachine, Shockwave, Shockwave Remote, Shockwave Internet Studio, Showcase, Tools to Power Your Ideas, Universal Media, Virtuoso, Web Design 101, Whirlwind and Xtra are trademarks of Macromedia, Inc. and may be registered in the United States or in other jurisdictions including internationally. Other product names, logos, designs, titles, words or phrases mentioned within this publication may be trademarks, servicemarks, or tradenames of Macromedia, Inc. or other entities and may be registered in certain jurisdictions including internationally. [. . . ] You can use the subdirectory created by the Web Server Configuration Tool for one of your virtual hosts but you must create additional subdirectories for all other virtual hosts. For example, the first time you run the Web Server Configuration Tool, it creates jrun_root/lib/wsconfig/1; if you have two other virtual hosts, you must manually create two other directories, jrun_root/lib/wsconfig/mystore and jrun_root/lib/wsconfig/myemp directories. 3 Open the jrun_root/servers/servername/SERVER-INF/jrun. xml file for each of your server instances, ensure that the deactivated element is set to false, and note the value of the port element for the ProxyService service. <service class="jrun. servlet. jrpp. JRunProxyService" name="ProxyService"> <attribute name="activeHandlerThreads">25</attribute> <attribute name="backlog">500</attribute> <attribute name="deactivated">false</attribute> <attribute name="interface">*</attribute> <attribute name="maxHandlerThreads">1000</attribute> <attribute name="minHandlerThreads">1</attribute> <attribute name="port">51002</attribute> . . . 4 Open the apache_root/conf/httpd. conf file in a text edit and find the VirtualHost directives. The settings added by the Web Server Configuration Tool are after the last </IfModule> directive, as the following example shows: . . . # JRun Settings LoadModule jrun_module "C:/JRun4/lib/wsconfig/1/mod_jrun20. so" <IfModule mod_jrun20. c> JRunConfig Verbose false JRunConfig Apialloc false JRunConfig Ssl false JRunConfig Ignoresuffixmap false JRunConfig Serverstore "C:/JRun4/lib/wsconfig/1/jrunserver. store" JRunConfig Bootstrap 127. 0. 0. 1:51020 #JRunConfig Errorurl <optionally redirect to this URL on errors> AddHandler jrun-handler . jsp . jws . cfm . cfml . cfc </IfModule> NameVirtualHost 127. 0. 0. 1 <VirtualHost 127. 0. 0. 1> ServerAdmin admin@mysite. com DocumentRoot "C:/Program Files/Apache Group/Apache2/htdocs" ServerName SERVER02 ErrorLog logs/error. log </VirtualHost> <VirtualHost 127. 0. 0. 1> ServerAdmin admin@mysite. com DocumentRoot "C:/Program Files/Apache Group/Apache2/htdocs2" ServerName mystore ErrorLog logs/error-store. log </VirtualHost> <VirtualHost 127. 0. 0. 1> ServerAdmin admin@mysite. com DocumentRoot "C:/Program Files/Apache Group/Apache2/htdocs3" Enabling application isolation 79 ServerName myemployee ErrorLog logs/error-employee. log </VirtualHost> . . . 5 For each VirtualHost directive, copy the IfModule directive from its default location outside the VirtualHost directive to the last element in the VirtualHost directive. 6 Delete the Apialloc, Ssl, and Ignoresuffixmap elements in the IfModule directive for each virtual host. Modify the Serverstore and Bootstrap elements to point to the appropriate proxy port (from the jrun. xml file) and jrun_root/lib/wsconfig/subdirectory/jrunserver. store file, which the web server connector creates automatically. 7 In the original IfModule directive, remove the Serverstore and Bootstrap lines. The following example shows three virtual hosts, two of which are configured for ColdFusion MX: . . . # JRun Settings LoadModule jrun_module "C:/JRun4/lib/wsconfig/1/mod_jrun20. so" <IfModule mod_jrun20. c> JRunConfig Verbose false JRunConfig Apialloc false JRunConfig Ssl false JRunConfig Ignoresuffixmap false #JRunConfig Serverstore "C:/JRun4/lib/wsconfig/1/jrunserver. store" #JRunConfig Bootstrap 127. 0. 0. 1:51020 AddHandler jrun-handler . jsp . jws . cfm . cfml . cfc </IfModule> NameVirtualHost 127. 0. 0. 1 <VirtualHost 127. 0. 0. 1> ServerAdmin admin@mysite. com DocumentRoot "C:/Program Files/Apache Group/Apache2/htdocs" ServerName RNIELSEN02 ErrorLog logs/error. log </VirtualHost> <VirtualHost 127. 0. 0. 1> ServerAdmin admin@mysite. com DocumentRoot "C:/Program Files/Apache Group/Apache2/htdocs2" ServerName rnielsenstore ErrorLog logs/error-store. log <IfModule mod_jrun20. c> JRunConfig Verbose true JRunConfig Serverstore "C:/JRun4/lib/wsconfig/mystore/jrunserver. store" JRunConfig Bootstrap 127. 0. 0. 1:51002 AddHandler jrun-handler . jsp . jws . cfm . cfml . cfc </IfModule> </VirtualHost> <VirtualHost 127. 0. 0. 1> ServerAdmin admin@mysite. com DocumentRoot "C:/Program Files/Apache Group/Apache2/htdocs3" ServerName rnielsenemployee ErrorLog logs/error-employee. log <IfModule mod_jrun20. c> JRunConfig Verbose true JRunConfig Serverstore "C:/JRun4/lib/wsconfig/myemp/jrunserver. store" JRunConfig Bootstrap 127. 0. 0. 1:51003 AddHandler jrun-handler . jsp . jws . cfm . cfml . cfc </IfModule> </VirtualHost> . . . 8 Restart Apache. 80 Chapter 6: Using Multiple Server Instances Configuring application isolation in SunONE Web Server When using multiple virtual hosts with multiple server instances under SunONE Web Server, you create multiple SunONE Web Server instances, one for each ColdFusion server instance. This discussion assumes that you have already created server instances, as described in "Enabling application isolation" on page 77. To configure multiple server instances for application isolation when using SunONE Web Server: · Run the Web Server Configuration Tool multiple times, once for each SunONE Web Server server instance, specifying a different configuration directory and ColdFusion server instance each time. Enabling load balancing and failover Load balancing is an enterprise-level feature in which the application server automatically alternates requests among the server instances in a cluster. Clustering also enables application servers to route requests to a running server instance when the original server instance goes down. Note: These instructions apply only when running ColdFusion MX on JRun. When deploying ColdFusion MX on other J2EE application servers, consult the application server documentation for information on enabling session replication. You can get load balancing and failover by deploying the ColdFusion application to multiple server instances and adding the instances to a cluster. The web server connector optimizes performance and stability by automatically balancing load and by switching requests to another server instance when a server instance stops running. However, you must purchase a separate ColdFusion MX license for each computer. Note: If you set up and test multiple server instances while running the 30-day Trial version, the cluster may not continue to function appropriately when the Trial version reverts to Developer version after 30 days. To implement failover for the server instances in a cluster, you must enable session replication. Session replication coordinates session information in real-time among the server instances in a cluster. Enabling session replication lets a request be automatically routed to a running server if the current server is unavailable. To configure a cluster of server instances for load balancing and failover: 1 Create server instances for the cluster as described in "Defining additional server instances" on page 76. 2 Deploy ColdFusion on each server instance as described in "Deploying ColdFusion MX" on page 76. 3 Start each server instance. 4 Open the ColdFusion MX Administrator on each server instance using the built-in web server. Define the resources (such as data sources and Verity collections) required for the application. If using failover, go to the Memory Variables pages, and enable J2EE sessions. You must do this for all server instances in the cluster. Note: Session variables are the only memory variables that support failover. In particular, ColdFusion components do not support failover. Enabling load balancing and failover 81 5 Open the jrun_root/lib/security. properties file and add the IP addresses of the other JRun servers in the cluster to jrun. trusted. hosts. 6 Open the JMC and create a cluster that contains your server instances. Note: Do not add the admin JRun server to a cluster. 7 If using failover, perform the following steps in the JMC: a Open the cluster by clicking the cluster name in the left panel. f In the New Replication Buddy field, enter the names of the other servers in the cluster one- by-one, and click Add. g Click Apply. Choose your website, but instead of choosing a single server instance, select the cluster. [. . . ] (-144) (-145) Description Error occurred during filter initialization. File could not be opened. Dispatch error codes Error code VdkError_CouldntLoadDLL VdkError_NoSuchFunction No. (-201) Function not available. Warning error codes Error code VdkWarning_CollectionDown VdkWarning_QueryComplex VdkWarning_LowMemory No. (10) (11) (12) Description The collection was down when it was opened. [. . . ]