TM BlueDragon 6.2.1 Server and Server JX Installation Guide BlueDragon 6.2.
NEW ATLANTA COMMUNICATIONS, LLC BlueDragon™ 6.2.1 Server and Server JX Installation Guide December 16, 2005 Version 6.2.1 Copyright © 1997-2005 New Atlanta Communications, LLC. All rights reserved. 100 Prospect Place • Alpharetta, Georgia 30005-5445 Phone 678.256.3011 • Fax 678.256.3012 http://www.newatlanta.com BlueDragon is a trademark of New Atlanta Communications, LLC. ServletExec and JTurbo are registered trademarks of New Atlanta Communications, LLC in the United States.
Contents 1. INTRODUCTION .............................................................................................................1 1.1 ABOUT THIS MANUAL ....................................................................................................1 1.2 TECHNICAL SUPPORT ....................................................................................................1 1.2.1 Additional Information in FAQs .............................................................................2 1.
6.2.2 Enabling SSH Tunneling.....................................................................................27 6.3 DATASOURCE CONFIGURATION ....................................................................................28 6.3.1 Automatic Configuration of ODBC Datasources (Windows) ..............................28 6.3.2 Configuring Access, SQL Server, and Others as ODBC Datasources ..............28 6.3.3 Support for MySQL .............................................................................
1 1. Introduction B lueDragon is family of server-based products for the deployment of ColdFusion® Markup Language (CFML) for dynamic web publishing—with native technology platform integration on the operating system, web server, and database of your choice. CFML is a popular server-side, template-based markup language that boasts a rich feature set and renowned ease-of-use.
Besides offering all the documentation, a FAQ, and feature request options, perhaps the most useful aspect of our self-help support is our active BlueDragon-Interest discussion list. New Atlanta engineers and customers are available to help solve both common and challenging problems. There’s also a searchable archive of past discussion list topics. Details regarding paid support options, including online-, telephone-, and pager-based support are available from the New Atlanta web site: http://www.
2 2. BlueDragon Product Configurations BlueDragon is currently available in three product configurations: BlueDragon Server, BlueDragon Server JX, BlueDragon for J2EE and BlueDragon for the Microsoft .NET Framework. 2.
your application across multiple servers, load balancing and failover, support for J2EE sessions and J2EE datasources, and more. BlueDragon/J2EE is available for Windows, Mac OS X, SPARC Solaris, IBM AIX, HPUX and Linux (and indeed, on any operating system which supports a J2EE server). 2.3 BlueDragon for the Microsoft .NET Framework BlueDragon for the Microsoft .NET Framework allows you to deploy CFML applications as native .NET components on .NET servers.
3 3. Preparing For Installation Before proceeding with installation of BlueDragon, there are a few concepts you should understand and in some cases preliminary steps that you should take first. 3.1 System Requirements BlueDragon Server and Server JX is supported on the following operating systems, and provides web server adapters for the following web servers (Both BlueDragon Server and Server JX are not supported on Windows 95/98/Me): OS Web Server Windows 2003 Microsoft IIS 4.0, 5.0, 5.1, and 6.
As for other flavors of Linux, while we have not tested and do not support them officially, we have had customers run on Slackware, Debian, Gentoo and others. The key requirement is to be running the 2.4 kernel on an x86 32-bit platform. If you need to deploy BlueDragon on combinations of OS platform and/or web servers not listed here, consider using BlueDragon/J2EE. It allows you to deploy CFML applications on any standard J2EE web server (or Servlets 2.
individual virtual hosts. See section 3.7 for additional information on configuring web server adapters. Yet another solution is to configure the web server to identify different virtual directories to serve CFML out of a single physical directory but directed against either of multiple CFML servers installed on the machine.
3.5 BlueDragon Servers Account Privileges Be aware that BlueDragon Server and Server JX editions run by default as root on Linux and OS X systems, and as the Local System Account on Windows systems. This is something we may change in the future. 3.6 Built-in Web Server BlueDragon Server contains a built-in web (HTTP) server that can be used for development and testing, and is also used to access the BlueDragon administration console.
ColdFusion MX presumes that the different virtual hosts have the same content (such as when the different hosts on the same web server are clustered), and you must change their “cacherealpath” setting if the hosts each have different content, as discussed in Macromedia TechNote 18258. BlueDragon instead presumes that the different hosts will have different content, and therefore you need only change this setting when that’s not the case (as in a clustering situation).
3.7.2.1 Microsoft IIS Adapter uses Extension Mappings If you install a web server adapter on Microsoft IIS, be aware that the adapter runs using extension mappings rather than as an ISAPI filter. Generally, the adapter configuration is handled entirely by BlueDragon, but this clarification is useful should you need to perform any manual configuration. 3.7.2.
http://www.microsoft.com/windows2000/downloads/recommended/urlscan/ 3.7.2.6 Restarting Microsoft IIS If you install a web server adapter on Microsoft IIS, follow these instructions to restart Microsoft IIS and make sure the BlueDragon web server adapter is initialized properly. For Microsoft IIS 5.0/5.1/6.0 on Windows 2000/XP/2003: 1. Using the Internet Services Manager, right click on the computer name and select the Restart IIS menu option as illustrated in Figure 1, below. 2.
Figure 2. Restarting IIS 5.0 on Windows 2000 (Step 2) 3.7.3 Apache Web Server Issues Following are Apache web server issues. 3.7.3.1 Apache Support on Red Hat 9 Red Hat 9 comes with Apache 2.0.40. As discussed in the requirements section above, BlueDragon supports only 2.0.42 through 2.0.53. Please upgrade to one of these later versions of Apache. A solution for this problem is under consideration. Please contact bluedragon-support@newatlanta.
Server itself or before starting the BlueDragon Server when attempting to use the Admin console to add the web server adapter. For more clarity, the following table describes the directory and file differences between the Apache Group standard and that for Gentoo and Mac OS X default configurations. From this information it should be straightforward to derive the required information for other configurations, such as Debian or Slackware.
ln -s /usr/sbin/httpd /usr/local/apache/bin/httpd ln –s /etc/apache/conf/apache.conf /usr/local/apache/conf/httpd.conf Note that this example for Gentoo includes a link for the Apache configuration specification file (httpd.conf) since its name is different than that for an Apache Group installation. Please note that additional functionality has been included into the BlueDragon Server 6.2.1 release allowing it to recognize the pre-installed Apache web server for RedHat & CentOS distributions.
1. activating the Sun JDK 1.4 Headless mode 2. installing a virtual X11 frame buffer 3. using a pure Java version of the AWT However, none of these have yet been incorporated into the BlueDragon release. Each solution presents complications because of the need to install 3rd-party software and some do not provide a complete solution for all cases of headless graphic rendering. Additionally, New Atlanta Communications has not certified any of these solutions through our typical testing process.
4 4. Running the Installer There are separate BlueDragon installers for Windows, Linux, and Mac OS X. Be sure to download the appropriate installer for your operating system. Also, there are separate installers for BlueDragon Server and BlueDragon Server JX. Again, installation of BlueDragon/J2EE is covered separately in Deploying CFML on J2EE Application Servers. The BlueDragon installers are Java-based and include a built-in Java VM (JVM).
More detailed installer debug information can be found in the following files found in the root directory of the drive where BlueDragon installation was attempted: BlueDragon_Server_installation_error.log BlueDragon_Server_installation_output.log 4.2 Installing on Linux The BlueDragon Server and Server JX installers for Linux have the following file names (the entry-level BlueDragon Server is only available on Linux): BlueDragon_Server_62-Linux.sh BlueDragon_Server_JX_62-Linux.sh 4.2.
sequence of UNIX systems. This script is named based upon the BlueDragon edition and installed into the /etc/rc.d/init.d directory. For example, for BlueDragon Server JX, the file /etc/rc.d/init.d/BlueDragon_Server_JX will be created. Currently, BlueDragon Server installers only create the script, but do not assume configuration into any specific run-level. Therefore, in order to have BlueDragon Server controlled at system startup and shutdown, it must be manually installed into appropriate rc.
4.3.1 Resolving Installation Problems on OS X Basic installer status information can be found in the installer log file, which is named BlueDragon_Server_JX_6.2_InstallLog.log (or without “_JX” version) located in the BlueDragon installation directory (if the installer is aborted before completing, the log file will be placed on the Windows desktop). More detailed installer debug information can be found in the following files found in the root directory: BlueDragon_Server_installation_error.
The default installation directory for Linux is: /usr/local/NewAtlanta/BlueDragon Table 1, below, describes the contents of the BlueDragon installation directory. Item Description bin This directory contains various binary executable files used by BlueDragon Server. Do not modify or delete the contents of this directory. classes This directory exists in BlueDragon Server JX only and is automatically added to the classpath. See the READ ME in this directory for more information.
Table 1. BlueDragon Server Installation Directory Content 4.4.1 How the BlueDragon Server Has Been Installed On Windows, BlueDragon Server is installed as a service that is configured for automatic startup, and is started by the installer. On Linux and Mac OS X, BlueDragon Server is installed as a daemon and is started by the installer. See Sections 4.2.3 and 4.3.2 for more information. BlueDragon 6.2.
5 5. Verifying Your Installation With BlueDragon installed, you should now verify that the installation was successful by running some tests against the BlueDragon server as described in this section. 5.1 Built-in Web Server To verify that the BlueDragon built-in web server is running, enter the following URL in a web browser (if you specified a port other than 8080 during installation, use that port number in the URL): http://localhost:8080/index.
Figure 3. BlueDragon CFML Test Page BlueDragon 6.2.
6 6. BlueDragon Administration Console The BlueDragon administration console is used primarily to configure the BlueDragon environment. It also provides status information about the BlueDragon runtime state. The console offers online help on each page to assist in understanding how its features work. There is information in the online help that is not in the BlueDragon documentation. Additional discussion of the online help is found in the BlueDragon 6.2.1 User Guide.
Figure 4. Administration Console Login After logging in, the BlueDragon administration console will appear similar to Figure 5, below. Click the menu items in the left frame to access the various BlueDragon administration functions. Refer to the BlueDragon 6.2.1 User Guide, which can be found in the docs directory of the BlueDragon installation directory, for more information about using the administration console. BlueDragon 6.2.
Figure 5. BlueDragon Administration Console 6.2 Accessing the Administration Console Remotely As mentioned in the previous section, the BlueDragon administration console can only be accessed using the built-in web server. The built-in web server is configured by default to be accessible only from the server on which BlueDragon is installed. This means that the BlueDragon administration console, by default, cannot be accessed remotely.
• If you’re able to access the administration console and want to modify it to allow other IP addresses to access it, note that the "License & Security" link (under "General") has a field called "Allowed IP addresses". • If you can't access the administration console, you can instead modify the bluedragon-server.properties file in the config directory where BlueDragon is installed. It has an entry of the same name.
Forward local port 8080 (or wherever you have BlueDragon’s internal server set) via SSH to the remote server port 8080. This will also allow you to leave the remote server configured to accept requests only from localhost/127.0.0.1, as that is where the incoming SSH tunnel will appear to come from.
databases like Oracle), the free Server edition does not. Does this mean you can’t use an Access datasource in BlueDragon? Or a SQL Server database in the free Server edition? No. It’s just that you must instead create the datasource outside of BlueDragon as described in the previous section and then use the ODBC Refresh option also described there to see the datasource. 6.3.
7 7. Executing Your CFML Applications With BlueDragon installed and verified, the next step will be to execute your existing CFML applications. How you do this will depend on whether you’re using the built-in web server or have implemented a web server adapter. 7.1 Working with a Web Server Adapter If you’re using a web server adapter, the location of your CFML files will be driven by your web server and/or virtual directory mappings for that web server.
9 8. Updating BlueDragon If you already have BlueDragon installed and want to install another edition or version, there are some concerns you should be aware of. This section highlights those. It also presents information that may be useful when uninstalling BlueDragon, which is discussed further in section 9. In the discussions to follow, the term “edition” is used to refer to the different BlueDragon products, as in BlueDragon Server of BlueDragon Server JX.
that they must each be configured to use different ports for the built-in web server and any web server adapter. Be aware, however, that there is no mechanism to carry your current configuration settings, custom tags, logs, and wwwroot documents (if you used the built-in web server) from the current installation to another. Section 8.4 offers information to help preserve current settings and implement them in the new installation. 8.
• wwwroot holds any CFML and other web documents you created if you used the built-in web server for development • classes and lib hold CFX custom tags, database drivers, servlets, or other java classes (note that each will contain files and subdirectories even if you don’t place any there) • customtags holds any CFML custom tags you may have placed there for server-wide access (again, there are some sample files already placed there at installation) • servlets (found in Server JX only) holds any jav
BlueDragon 6.2 uninstaller attempts to preserve many of the files discussed above. The information remains for your consideration to further protect your work. 8.5 Obtaining Updates and Patches Patches for BlueDragon are made available whenever New Atlanta deems it appropriate.
10 9. Uninstalling BlueDragon The following sections describe uninstalling BlueDragon on Windows, Linux, and Mac OS X. 9.1 Protecting Previous Work, Settings, and Logs Before uninstalling, be cautioned that the BlueDragon uninstall process attempts to remove all directories and files where BlueDragon was installed, which may include useful work and information that you may want to protect (especially if you’re planning to then install a new release). As of the 6.
9.3 Uninstalling on Linux At a command prompt enter the following from the uninstall sub-directory of the BlueDragon installation directory to launch the uninstaller: sh ./Uninstall_BlueDragon_Server_JX_6.2 For the Server edition, remove the _JX portion of that command. The uninstaller will be launched in console or GUI mode based on the mode used when the installer was run. The GUI mode uninstaller requires a minimum of 8-bit color depth (256 colors) and a minimum 640 x 480 screen resolution. 9.
11 10. Appendix: Disabling NES/iWS Servlets Section 3.7.4 indicated that if you plan to install a BlueDragon web server adapter with Netscape® Enterprise Server/iPlanet™ Web Server, you must first disable the web server’s built-in servlet support. Follow the instructions, below, based on which version of the NES/iWS web server you have installed. 10.1 iPlanet Web Server 6.0 For iWS 6.0, the built-in servlet/JSP engine is enabled by default.
Figure 6. Disable iWS 6.0 Servlets/JSP Figure 7. Deactivate the iWS 4.0/4.1 Servlet Engine BlueDragon 6.2.
10.3 Netscape Enterprise Server 3.5.1 and 3.6 For NES 3.5.1 and 3.6, the built-in Java interpreter is deactivated by default. If, however, it has been activated on your server you must deactivate it before installing the BlueDragon web server adapter. 1. From the Netscape Administration Server home page, click the appropriate server. 2. Click Programs from the menu bar in the upper frame of the server administration page. 3. In the menu in the left frame of the Programs page, click Java. 4.
