ServletExec 5.
NEW ATLANTA COMMUNICATIONS, LLC ServletExec 5.0 Installation Guide TM October 24, 2003 Version 5.0 Copyright © 1997-2002 New Atlanta Communications, LLC 100 Prospect Place • Alpharetta, Georgia 30005-5445 Phone 678.256.3011 • Fax 678.256.3012 http://www.newatlanta.com ServletExec is a trademark of New Atlanta Communications, LLC. Registration pending. All other trademarks and registered trademarks herein are the property of their respective owners.
Contents 1. INTRODUCTION .............................................................................................................1 1.1 SERVLETEXEC PRODUCTS.............................................................................................1 1.2 TECHNICAL SUPPORT ....................................................................................................2 2. SERVLETEXEC/ISAPI: MICROSOFT IIS PLUGIN (WINDOWS) .................................3 2.1 UPGRADING FROM A PREVIOUS VERSION .......
.2.4 Disable the Built-In Servlet Engine (iWS 4.0 and higher)...................................33 4.2.5 Disable the Built-In Servlet Engine (Sun ONE Web Server 6.1) ........................34 4.3 INSTALLING SERVLETEXEC/NSAPI FOR MULTIPLE SERVERS .........................................34 4.4 RUNNING THE SERVLETEXEC/NSAPI INSTALLER ..........................................................34 4.5 WHAT WAS INSTALLED AND/OR MODIFIED? ..................................................................35 4.5.
6.4 RUNNING THE SERVLETEXEC/AS INSTALLER ................................................................72 6.5 WHAT WAS INSTALLED AND/OR MODIFIED? ..................................................................72 6.5.1 The ServletExecAS Directory .............................................................................73 6.5.2 NES / iWS / Sun ONE.........................................................................................74 6.5.2.1 Server Configuration Files .............................
1 1. Introduction Installing ServletExec 5.0 (all product configurations) N ew Atlanta ServletExec 5.0 is a high-performance, reliable, and cost-effective web application server that implements the JavaTM Servlet API 2.4, JavaServer Pages™ (JSP) 2.0, and JSP Standard Tag Library (JSTL) 1.1 standards defined by Sun Microsystems, Inc. as component technologies of the Java 2 Platform, Enterprise Edition (J2EETM).
1. INTRODUCTION - ServletExec/AS is available for Windows NT/2000/XP/2003 and various UNIX platforms, including SPARC Solaris, Linux, HP-UX, and AIX. If you’re using Microsoft IIS or NES/iWS/Sun ONE and you aren’t sure whether the Servlet Engine or Application Server configuration is best for you, we recommend starting with the Servlet Engine version of ServletExec (ServletExec/ISAPI or ServletExec/NSAPI). If you’re using Apache, only the ServletExec/AS version is currently available.
2 2. ServletExec/ISAPI: Microsoft IIS Plugin (Windows) Installing the plugin servlet engine for Microsoft Internet Information Server S ervletExec/ISAPI is a plugin servlet engine for Microsoft Internet Information Server (IIS) on Microsoft Windows NT/2000/XP/2003. ServletExec/ISAPI enables you to deploy Java Servlets and JavaServer Pages (JSP) on Microsoft IIS in a standard, robust, high-performance environment. The ServletExec/ISAPI installer is named ServletExec_ISAPI_50.exe.
2. MICROSOFT IIS PLUGIN (WINDOWS) stop_iis.bat command file or, (c) click Restart IIS in the Internet Services Manager administrative tool. 2. Close all open applications, making sure to include DBMON. 3. Make backup copies of the ServletExec Data, Servlets, classes (if you’ve added an additional one), and webapps (versions 3.1 and above only) subdirectories of the ServletExec ISAPI directory. The location of this directory varies depending upon your version of ServletExec. For ServletExec/ISAPI 2.
2. MICROSOFT IIS PLUGIN (WINDOWS) OS Web Server Windows 2003 Internet Information Server (IIS) 6.0 Windows 2003 64-bit Edition Internet Information Server (IIS) 6.0 Windows XP Professional Internet Information Server (IIS) 5.1 Windows 2000 Internet Information Server (IIS) 5.0 Windows NT 4.0 Server Internet Information Server (IIS) 4.0 Windows NT 4.0 Workstation Peer Web Services (PWS) 4.0 Table 2. Supported Operating Systems and Web Servers 2.2.2 JDK or JRE ServletExec/ISAPI 5.
2. MICROSOFT IIS PLUGIN (WINDOWS) 2.2.3.1 Multiple JDK/JRE Versions Installed You may have multiple versions of the JDK/JRE installed on your system. ServletExec/ISAPI (including the installer) uses registry entries to determine which installed JDK/JRE to use. It will look for an installed JDK first and if it doesn’t find one it will look for a JRE. It will look for JDK/JREs from vendors in the following order: Sun Microsystems, and then IBM. Here’s the complete algorithm: 1.
2. MICROSOFT IIS PLUGIN (WINDOWS) See Section 2.5.4 for more information. 2.4 Running the ServletExec/ISAPI Installer Double-click the ServletExec/ISAPI installer icon to launch Setup. Please review the ServletExec License Agreement carefully and check the READ ME displayed by the setup program for any last minute notices before continuing. 2.
2. MICROSOFT IIS PLUGIN (WINDOWS) Guide for instructions on running these examples. lib The lib subdirectory contains the Java archive (.jar) files required by ServletExec/ISAPI. Important Do not modify the contents of the lib directory! Servlet Logs This subdirectory contains the Servlet.log files that capture the output from the servlet log() method. In some cases, this directory isn’t created until the first ServletExec initialization.
2. MICROSOFT IIS PLUGIN (WINDOWS) The following User should be granted Full Control to the ServletExec ISAPI directory and its subdirectories: IUSR_ (the user created by IIS for processing requests for anonymous users). Figure 1. ISAPI NTFS Permission Settings (Windows 2000) With IIS 6.0, the Application Pool Identity used for the ServletExec worker process should also be granted Full Control to the ServletExec ISAPI directory and its subdirectories. 2.5.3 ServletExec_ISAPI.
2. MICROSOFT IIS PLUGIN (WINDOWS) To confirm your settings for IIS 1. In Internet Service Manager, open the Properties dialog for the virtual directory that maps to the physical directory in which ServletExec_ISAPI.dll resides. (By default, this is the SCRIPTS virtual directory). 2. Verify that the Name parameter under Application Settings is available and that execute permission is enabled. If it is not available, click Create (IIS 4.0 only). 3. Click Apply, and click OK. 2.5.
2. MICROSOFT IIS PLUGIN (WINDOWS) 5. Right-click the server icon, and then click Properties. You should see a dialog similar to Figure 2. Make sure you’ve opened the Properties dialog for the server as illustrated in Figure 2, and not for the Default Web Site (or any other web site you may have configured). 6. In Properties, check to make sure WWW Service is selected in the Master Properties list (see Figure 2), and then click Edit. 7. In Master Properties, click the ISAPI Filters tab (see Figure 3).
2. MICROSOFT IIS PLUGIN (WINDOWS) Figure 3. ISAPI Filters (IIS 5.0) 8. Click any previously installed servlet engines, and then click Remove. 9. Click ServletExec, and then click Edit to examine or modify it (if you wish). If you do not see ServletExec, click Add and follow the instructions to add the ServletExec/ISAPI entry, making sure to point to ServletExec_ISAPI.dll. To examine or manually modify the metabase ISAPI Filter under IIS 4.0 1.
2. MICROSOFT IIS PLUGIN (WINDOWS) Figure 4. Server Properties (IIS 4.0) 4. In Master Properties, click the ISAPI Filters tab (see Figure 5). 5. Click any previously installed servlet engines, and then click Remove. 6. Click ServletExec, and then click Edit to examine or modify it (if you wish). If you do not see ServletExec, click Add and follow the instructions to add the ServletExec/ISAPI entry, making sure to point to ServletExec_ISAPI.dll. ServletExec 5.
2. MICROSOFT IIS PLUGIN (WINDOWS) Figure 5. ISAPI Filters 2.6 ServletExec Admin Username & Password 2.6.1 Windows NT 4.0 and Windows 2000/XP/2003 If the ServletExec admin web application is protected using Basic authentication then the username and password used to access the ServletExec admin pages must match those of an existing Windows user as defined in the User Manager. 2.6.2 IIS 4.0 (Windows NT 4.0) and IIS 5.0/5.1/6.
2. MICROSOFT IIS PLUGIN (WINDOWS) 4. Expand the Internet Services Manager entry until you can see the icon for your server. 5. Right-click the server icon, and then click Properties. Make sure you’ve opened the Properties dialog for the server as illustrated in Figure 4, and not for the Default Web Site (or any other web site you may have configured). 6. In Properties, check to make sure WWW Service is selected in the Master Properties list, and then click Edit. 7.
2. MICROSOFT IIS PLUGIN (WINDOWS) to read and write to the file system because access to the NT File System (NTFS) is based on the user account of the process. Rules Governing IIS User Accounts 1. During normal request processing in your servlet’s service(), doGet(), or doPost() method, your servlet will be running under the user account of the authenticated user, if the user had to enter a username and password to access your servlet.
2. MICROSOFT IIS PLUGIN (WINDOWS) Using the Services control panel… 1. In Control Panel, click Services. 2. Click IIS Admin Service, and then click Stop. 3. Restart IIS. Using the command line… • Execute the batch file stop_iis.bat (found in the ServletExec ISAPI directory). 2.9 Uninstalling ServletExec/ISAPI To completely uninstall ServletExec/ISAPI 1. Stop IIS as described in Section 2.8. 2. Close any open DBMON windows. 3. Open Control Panel and click Add/Remove Programs. 4.
3 3. ServletExec/NSAPI: NES/iWS/Sun ONE Plugin (Windows) Installing the Windows NT/2000/XP/2003 plugin servlet engine for Netscape Enterprise Server, iPlanet Web Server, and Sun ONE Web Server S ervletExec/NSAPI is a plugin servlet engine for Netscape Enterprise Server (NES) and iPlanet Web Server (iWS). ServletExec/NSAPI enables you to deploy Java Servlets and JavaServer Pages (JSP) on NES/iWS/Sun ONE in a standard, robust, high-performance environment. The ServletExec/NSAPI 5.
3. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (WINDOWS) To upgrade to a new version of ServletExec/NSAPI and maintain your old configuration settings 1. Stop your web server. If you’ve installed ServletExec/NSAPI for multiple NES/iWS/Sun ONE server instances, stop each one that is running. 2. Close all open applications, making sure to include DBMON. 3. Make backup copies of the ServletExec Data, Servlets, classes (if you’ve added an additional one), and webapps (versions 3.
3. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (WINDOWS) 3.2 System Requirements 3.2.1 Operating System and Web Server • • ServletExec/NSAPI 5.0 is not supported on Windows 95, Windows 98 or Windows ME. ServletExec/NSAPI 5.0 supports the following operating systems and web servers: OS Windows 2003, Windows XP Professional, Windows 2000, Windows NT 4.0 Server, and Windows NT 4.0 Workstation Web Server Netscape Enterprise Server (NES) 3.5.1 and higher iPlanet Web Server (iWS) 4.
3. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (WINDOWS) Important The JDK or JRE must be installed on a local drive and not on a mapped network drive. If the JDK/JRE has been installed on a mapped network drive, ServletExec/NSAPI will not be able to load and initialize the Java VM. 3.2.3.1 Multiple JDK/JRE Versions Installed You may have multiple versions of the JDK/JRE installed on your system. ServletExec/NSAPI (including the installer) uses registry entries to determine which installed JDK/JRE to use.
3. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (WINDOWS) 3.3 Uninstalling Other Servlet Engines Very Important You must uninstall any other servlet engines previously installed for use with NES/iWS/Sun ONE before installing and using ServletExec/NSAPI. In particular, modifications to the obj.conf and magnus.conf configuration files for other servlet engines must be removed.
3. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (WINDOWS) 2. On the Server Manager page, click the Java tab. 3. On the Enable/Disable Servlets/JSP page, disable Java globally and for all virtual servers, and click OK. 4. On the resulting page, click Save and Apply 3.4 Installing ServletExec/NSAPI for Multiple Servers If you’ve created multiple NES/iWS/Sun ONE server instances, you must run the ServletExec/NSAPI installer separately for each server instance for which you want to install ServletExec/NSAPI.
3. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (WINDOWS) • • Registry entries for ServletExec/NSAPI were created or modified The obj.conf and magnus.conf configuration files were updated (if you chose to let the ServletExec/NSAPI installer modify these files; otherwise, you must manually edit these files to support ServletExec/NSAPI) The following sections describe each of these changes. 3.6.
3. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (WINDOWS) used by the installer. lib The lib sub-directory contains the Java archive (.jar) files required by ServletExec/NSAPI. Important Do not modify the contents of this directory! The https- subdirectories of the ServletExec NSAPI directory each contain the following subdirectories. classes The classes subdirectory is automatically added to the ServletExec VM classpath.
3. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (WINDOWS) 3.6.2 Registry Entries The ServletExec/NSAPI installer creates a new registry entry for each web server instance for which it is installed with the following key: HKEY_LOCAL_MACHINE\SOFTWARE\New Atlanta Communications\ServletExec NSAPI\https- This key contains a single parameter named Home, that contains the path to the web server’s subdirectory within the ServletExec NSAPI directory.
3. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (WINDOWS) You must either: (a) make sure the ServletExec/NSAPI Init directives appear before these two Java Interpreter directives; or, (b) remove the Java Interpreter directives. Important— NES and iWS 4.1 or earlier Users If you're using NES or iWS 4.1 or earlier, you must add the Init directives to the obj.conf file rather than the magnus.conf file. 2. The following lines must be added to obj.
3. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (WINDOWS) Completely Uninstall ServletExec to uninstall ServletExec/NSAPI for all NES/iWS/Sun ONE web server instances 4. The uninstaller may not be able to remove all installed files. Check for the https- directory from within the ServletExec NSAPI directory, and delete it if it remains. The default location of the ServletExec NSAPI directory is within the C:\Program Files\New Atlanta directory. 5. Edit the obj.conf and magnus.
3. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (WINDOWS) # You can edit this file, but comments and formatting changes # might be lost when the admin server makes changes. # Use only forward slashes in pathnames--backslashes can cause # problems. See the documentation for more information.
4 4. ServletExec/NSAPI: NES/iWS/Sun ONE Plugin (SPARC Solaris) Installing the SPARC Solaris plugin servlet engine for Netscape Enterprise Server, iPlanet Web Server, and Sun ONE Web Server ervletExec/NSAPI 5.0 is a plugin servlet engine for Netscape Enterprise Server (NES) and iPlanet Web Server (iWS). ServletExec/NSAPI enables you to deploy Java Servlets and JavaServer Pages (JSP) on NES/iWS/Sun ONE in a standard, robust, high-performance environment. S The ServletExec/NSAPI 5.
4. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (SPARC SOLARIS) To upgrade to a new version of ServletExec/NSAPI and maintain your old configuration settings 1. Stop your web server. If you’ve installed ServletExec/NSAPI for multiple NES/iWS/Sun ONE server instances, stop each one that is running. 2. Make backup copies of the ServletExecData, Servlets, classes (if you’ve added an additional one), and webapps (versions 3.
4. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (SPARC SOLARIS) ServletExec/NSAPI 5.0 installed in the default location, the following lines should appear in the server start script: ServletExecHome=/usr/local/NewAtlanta export ServletExecHome 9. Restart your web server. After restarting your web server, the new version of ServletExec/NSAPI will run using your old configuration settings. Tip If you have any problems, you can restore the subdirectories from the backups you made in Step 3. 4.
4. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (SPARC SOLARIS) You can download the Sun JDKs for SPARC Solaris from: http://java.sun.com/j2se/ 4.2.2.1 Multiple JDK/JRE Versions Installed You may have multiple versions of the JDK/JRE installed on your system. If the installation script detects multiple versions, it will ask you to select which one to use.
4. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (SPARC SOLARIS) 4.2.5 Disable the Built-In Servlet Engine (Sun ONE Web Server 6.1) For Sun ONE Web Server 6.1, the built-in servlet engine is enabled by default. You must disable the built-in servlet engine before installing ServletExec/NSAPI. To disable the Servlet Engine 1. From the Sun ONE Administration Server home page, click the appropriate server. 2. On the Server Manager page, click the Java tab. 3.
4. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (SPARC SOLARIS) # ./ServletExec_NSAPI_50.sh 3. Review the ServletExec License Agreement carefully and check the README displayed by the installer for any last minute notices before continuing. 4. Continue following the prompts and instructions until you see confirmation of a successful installation. You will be able to see a record of the completed installation steps and errors in the log file /tmp/SEinstall.log. Note The SEinstall.
4. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (SPARC SOLARIS) https- There is one https- subdirectory for each NES/iWS/Sun ONE server instance on which ServletExec/NSAPI is installed. See further discussion of this directory directly below. installerFiles The installerFiles subdirectory contains files use by the ServletExec/NSAPI setup program for installing ServletExec/NSAPI on multiple NES/iWS/Sun ONE server instances.
4. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (SPARC SOLARIS) or open directory structure. See the READ ME in the webapps directory and the ServletExec User Guide for more information. 4.5.2 Server start Script The server start script must be modified to set the ServletExecHome, LD_LIBRARY_PATH, and LD_PRELOAD environment variables, and possibly export the SERVER_ROOT environment variable. This script resides in the https- subdirectory of the web server's installation directory.
4. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (SPARC SOLARIS) 4.5.2.3 LD_PRELOAD The LD_PRELOAD environment variable must be set to explicitly load libjava.so before any other shared objects: LD_PRELOAD=libjava.so export LD_PRELOAD 4.5.2.4 SERVER_ROOT Because the server installation directory may vary, the SERVER_ROOT environment variable may need to be exported to the start script to direct ServletExec/NSAPI to that location.
4. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (SPARC SOLARIS) Init classpath=".." ldpath=".." fn="SJavaBootInit" You must either: (a) make sure the ServletExec/NSAPI Init directives appear before these two Java Interpreter directives; or, (b) remove the Java Interpreter directives. Important— NES and iWS 4.1 or earlier Users If you're using NES or iWS 4.1 or earlier, you must add the Init directives to the obj.conf file rather than the magnus.conf file.
4. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (SPARC SOLARIS) Completely Uninstall ServletExec to uninstall ServletExec/NSAPI for all NES/iWS/Sun ONE web server instances If you choose to remove ServletExec/NSAPI from an NES/iWS/Sun ONE server instance, or to remove ServletExec/NSAPI completely, the uninstaller will not remove the modifications made to either the obj.conf, magnus.conf or the server start script. Important The installer will not automatically remove these lines.
4. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (SPARC SOLARIS) # You can edit this file, but comments and formatting changes # might be lost when the admin server makes changes.
5 5. ServletExec/AS: Application Server (Windows) Installing the Windows NT/2000/XP/2003 web server adapters for Microsoft IIS, Netscape Enterprise Server, iPlanet Web Server, Sun ONE Web Server, and Apache HTTP Server T he ServletExec Application Server (ServletExec/AS) is a standalone web application server that hosts Java Servlets and JavaServer Pages (JSP).
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) To upgrade to ServletExec/AS 5.0 from 3.0 or 3.1 and maintain your old configuration settings 1. Stop your web server. If you’ve installed ServletExec/AS adapters for multiple web servers, stop each one that is running. 2. Make backup copies of the ServletExec Data, Servlets, classes (if you’ve added an additional one), and webapps (versions 3.1 and above only) subdirectories for all ServletExec/AS instances. For ServletExec/AS 3.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) OS Windows 2003 Web Server Windows XP Professional Windows 2000 Windows NT 4.0 Server and Workstation Service Pack 4 or higher Microsoft IIS 6.0 iPlanet Web Server (iWS) 4.0 and higher Sun ONE Web Server 6.1 Apache HTTP Server 1.3.9 through 1.3.28 and 2.0.43 through 2.0.47 Microsoft IIS 5.1 Netscape Enterprise Server (NES) 3.5.1 and higher iPlanet Web Server (iWS) 4.0 and higher Sun ONE Web Server 6.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) • JDK/JRE for Windows 1.3 from IBM Important The JRE does not contain a Java compiler, which is required by ServletExec to support JavaServer Pages (JSP). Be sure to install the JDK, and not the JRE, if you plan to use JSP. You can download the Sun JDKs for Windows from: http://java.sun.com/j2se/ You can download the IBM JDKs for Windows from: http://www.ibm.com/developerworks/java/ 5.2.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) 2. Read the CurrentVersion variable from the key found in Step 1. Currently, the only valid values for this variable start with “1.3” or “1.4” (including, for example “1.4.2”). 3. Append the value of the CurrentVersion variable from Step 2 to the key from Step 1 to create a new key. For example: HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit\1.4 or… HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\1.4 4.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Important You must install at least one web server adapter whenever you install a ServletExec/AS instance. The only time you would choose Install a web server adapter is after you have previously installed a ServletExec/AS instance on a different physical machine from the web server, and now wish to install a ServletExec/AS adapter to allow the web server to communicate with the ServletExec/AS instance running on the remote machine.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Important Do NOT move or rename the folder you choose after ServletExec/AS is installed. 5. Enter an Instance Name. After selecting a destination folder, the ServletExec/AS installer prompts you for the ServletExec/AS instance name. This name is used to uniquely identify the ServletExec/AS instance for administration, and is especially important if you install more than one instance on your server.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) 7. Before making any change to your computer, the ServletExec/AS installer displays a confirmation dialog, as represented in Figure 13. Click Back to modify any of your selections, or Cancel to abort the installation. After clicking Next, the ServletExec/AS installer will begin copying files to your computer. 8. Install ServletExec as an NT Service? The installer will prompt you to install the ServletExec/AS instance as an NT service.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) 9. Update the server configuration file. If you’re installing a web server adapter for Netscape Enterprise Server, iPlanet Web Server, or Apache HTTP Server, the ServletExec/AS installer will prompt you to update the server configuration file. The web server configuration file must be updated for the ServletExec/AS web server adapter to work properly, so it is recommended that you allow the installer to do so.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Documentation Contains the ServletExec User Guide, and the Servlet 2.4 and JSP 2.0 API documentation from Sun Microsystems. Examples This subdirectory contains examples of a web application and a JSP page with an embedded bean. See the appropriate chapters of the ServletExec User Guide for instructions on running these examples.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Servlets This subdirectory contains the class files for legacy servlets hosted by ServletExec/ISAPI. These servlets run under the context of the default web application. See the READ ME in the Servlets directory and the ServletExec User Guide for more information. webapps This directory contains a subdirectory for each configured virtual server.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) To examine or manually modify the metabase ISAPI Filter under IIS 5.0/5.1/6.0 1. 2. 3. 4. 5. 6. 7. 8. 9. Click Start, point to Settings and click Control Panel. In Control Panel, double-click Administrative Tools. In Administrative Tools, double-click Internet Services Manager. Expand the Internet Services Manager entry until you can see the icon for your server. Right-click the server icon, and then click Properties.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Figure 15. ISAPI Filters (IIS 5.0) To examine or manually modify the metabase ISAPI Filter under IIS 4.0 1. Open Internet Service Manager (Microsoft Management Console) and expand the Internet Information Server entry until you can see the icon for your server. 2. Right-click the server icon, and then click Properties. You should see a dialog similar to Figure 16.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Figure 16. Server Properties (IIS 4.0) 4. In Master Properties, click the ISAPI Filters tab (see Figure 17). 5. Click any previously installed servlet engines, and then click Remove. 6. Click ServletExec, and then click Edit to examine or modify it (if you wish). If you do not see ServletExec, click Add and follow the instructions to add the ServletExec/AS entry, making sure to point to ServletExec_Adapter.dll. ServletExec 5.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Figure 17. ISAPI Filters 5.5.3.3 The webadapter.properties Configuration File The webadapter.properties file was created in the config subdirectory of your ServletExec AS 5.0 installation. This file contains the configuration properties used by the ServletExec adapter for the Microsoft IIS/PWS web server. These properties are used by the adapter for routing HTTP requests from the web server to a ServletExec Application Server (AS) instance.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) 5.5.4.1 Server Configuration Files To install a ServletExec/AS web server adapter for NES/iWS/Sun ONE, modifications must be made to the web server's obj.conf and magnus.conf files. This section describes the modifications to these files made by the ServletExec/AS installer. Important If you chose not to allow the installer to make these modifications, you must make them manually.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Service method=(GET|HEAD|POST) type=magnus-internal/nac fn="ServletExecService" Figure 18 and Figure 19 show complete magnus.conf and obj.conf files for the Sun ONE Web Server 6.1 with the ServletExec/AS directives highlighted. Important You must stop and restart the NES/iWS/Sun ONE web server after modifying the configuration files. # # The NetsiteRoot, ServerName, and ServerID directives are DEPRECATED.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) # You can edit this file, but comments and formatting changes # might be lost when the admin server makes changes. # Use only forward slashes in pathnames--backslashes can cause # problems. See the documentation for more information.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Important If you chose not to allow the installer to make these modifications, you must make them manually. The following directive was added to httpd.conf with the other LoadModule directives (near the top of the file): LoadModule servletexec_module modules/ApacheModuleServletExec.dll If the httpd.conf file contains a ClearModuleList directive followed by AddModule directives, then the following directive was added for ServletExec/AS: AddModule mod_servletexec.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) when the pool is empty and another request is received… default setting is 5). Once the pool max idle limit is reached, freed connections will be disconnected. A good guideline for changing these parameters from their default settings would be to set the pool max idle to your average number of connections, and to set the pool increment to the average spike number of connections.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) 5.7.1 Starting ServletExec/AS A ServletExec/AS instance is a standalone Java application that communicates with the web server (through the ServletExec/AS web server adapter) using network sockets. You start a ServletExec/AS instance using the java command on the command line. In addition to java command arguments, ServletExec/AS accepts several required and optional arguments. You can also start a ServletExec/AS instance using the StartServletExec.bat file.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Argument -backlog -name -home -log -root Explanation which the ServletExec/AS instance communicates with the web server adapter(s). If you modify this value, you must also modify the web server configuration file(s) as described above. Optional. The default value is 50.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Argument -addl Explanation Optional. This can be used to specify additional document directories (other than the root) and is specified in two forms: -addl = -addl = For example: -addl /test=C:\Test -addl www.abc.com/support=C:\Support -addl -mimetypes See previous explanation. Optional.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) 5.7.2 Stopping ServletExec/AS You must stop a ServletExec/AS instance using the StopServletExec.bat file. If a ServletExec/AS instance is not shut down properly, servlet destroy() methods are not invoked, sessions are not saved, and buffered log messages are lost. See the ServletExec User Guide for more information about the ServletExec Admin UI. 5.7.2.1 StopServletExec.bat The batch file StopServletExec.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) web server adapters running on the local machine. It is possible to install and configure web server adapters to run on a different machine (a “remote” machine) than the ServletExec/AS instance. To run a web server adapter on a different machine 1. Edit the StartServletExec.
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) See either the Virtual Servers chapter or the Servlet Alias section in the ServletExec User Guide for detailed instructions. You can use the ServletExec/AS installer to automatically update a web server configuration file to force requests that specify a web application URL context path to be forwarded to a particular ServletExec/AS instance. To have requests that specify a web application URL context path forwarded to a particular instance 1.
6 6. ServletExec/AS: Application Server (UNIX/Linux) Installing the UNIX web server adapters for Netscape Enterprise Server, iPlanet Web Server, Sun ONE Web Server, and Apache HTTP Server T he ServletExec Application Server (ServletExec/AS) is a standalone web application server that hosts Java Servlets and JavaServer Pages (JSP).
6. SERVLETEXEC/AS: APPLICATION SERVER (UNIX/LINUX) To upgrade to ServletExec/AS 5.0 from 3.0 or 3.1 and maintain your old configuration settings 1. Stop your web server. If you’ve installed ServletExec/AS adapters for multiple web servers, stop them all. 2. Make backup copies of the ServletExecData, Servlets, classes (if you’ve added an additional one), and webapps (versions 3.1 and above only) directories for all ServletExec/AS instances. For ServletExec/AS 3.
6. SERVLETEXEC/AS: APPLICATION SERVER (UNIX/LINUX) OS SPARC Solaris 2.6, 7, 8 and 9 Web Server HP-UX 11.0 and 11i v1.0 (11.11) AIX 5.1, and 5.2 Red Hat Linux 7.x, 8.x and 9.x and Red Hat Enterprise Linux 2.1 Netscape Enterprise Server (NES) 3.5.1 and higher iPlanet Web Server (iWS) 4.0 and higher Sun ONE Web Server 6.1 Apache HTTP Server 1.3.4 and higher Apache HTTP Server 2.0.43 and higher iPlanet Web Server (iWS) 4.0 and higher Sun ONE Web Server 6.0.
6. SERVLETEXEC/AS: APPLICATION SERVER (UNIX/LINUX) fail, ServletExec is not fully supported in these environments. Correcting these types of problems come with issues that are both technical and/or business-related and therefore are not officially supported. If you do have any problems, first contact ServletExec Tech Support at support@newatlanta.com. Be sure to include the installation log with your email so that the problems may be accurately analyzed. In addition to a JDK 1.3-, or 1.
6. SERVLETEXEC/AS: APPLICATION SERVER (UNIX/LINUX) 6.3 Uninstalling Other Servlet Engines Very Important You must uninstall any other servlet engines previously installed before installing and using ServletExec/AS. In particular, modifications to the obj.conf, magnus.conf, and httpd.conf configuration files for other servlet engines must be removed. For Netscape Enterprise Server, iPlanet Web Server, and Sun ONE Web Server, make sure the internal servlet and JSP support is disabled. See Section 3.
6. SERVLETEXEC/AS: APPLICATION SERVER (UNIX/LINUX) 6.5.1 The ServletExecAS Directory The ServletExecAS directory was created within the /usr/local/NewAtlanta directory, or the directory you specified during the installation. Important Do not move the ServletExecAS directory after installation. If you move this directory, ServletExec/AS will be unable to find its configuration files. There are no restrictions on the location of the ServletExecAS directory.
6. SERVLETEXEC/AS: APPLICATION SERVER (UNIX/LINUX) The se- subdirectories of the ServletExecAS directory each contain the following subdirectories. classes The classes subdirectory is automatically added to the ServletExec VM classpath. Place class files that will be shared by multiple web applications in this directory. See the READ ME file within the classes subdirectory for more information. ServletLogs This subdirectory contains the Servlet.
6. SERVLETEXEC/AS: APPLICATION SERVER (UNIX/LINUX) Important If you chose not to allow the installer to make these modifications, you must make them manually. Several lines must be added to these configuration files for each server for which ServletExec/AS is installed (the location of these lines within these files is very important): 1. Add the following lines to the beginning of magnus.conf before the other Init directives: Init Init fn=”load-modules” shlib="/bin/nsapi/ServletExec_Adapter.
6. SERVLETEXEC/AS: APPLICATION SERVER (UNIX/LINUX) Important You must stop and restart the NES/iWS/Sun ONE web server after modifying the configuration files. # # The NetsiteRoot, ServerName, and ServerID directives are DEPRECATED. # They will not be supported in future releases of the Web Server.
6. SERVLETEXEC/AS: APPLICATION SERVER (UNIX/LINUX) # You can edit this file, but comments and formatting changes # might be lost when the admin server makes changes. # Use only forward slashes in pathnames--backslashes can cause # problems. See the documentation for more information.
6. SERVLETEXEC/AS: APPLICATION SERVER (UNIX/LINUX) Important If you chose not to allow the installer to make these modifications, you must make them manually. The following directive was added to httpd.conf with the other LoadModule directives (near the top of the file): LoadModule servletexec_module modules/mod_servletexec.so If the httpd.conf file contains a ClearModuleList directive followed by AddModule directives, then the following directive was added for ServletExec/AS: AddModule mod_servletexec.
6. SERVLETEXEC/AS: APPLICATION SERVER (UNIX/LINUX) when the pool is empty and another request is received… default setting is 5). Once the pool max idle limit is reached, freed connections will be disconnected. A good guideline for changing these parameters from their default settings would be to set the pool max idle to your average number of connections, and to set the pool increment to the average spike number of connections.
6. SERVLETEXEC/AS: APPLICATION SERVER (UNIX/LINUX) 6.7.1 Starting ServletExec/AS A ServletExec/AS instance is a standalone Java application that communicates with the web server (through the ServletExec/AS web server adapter) using network sockets. You start a ServletExec/AS instance using the java command on the command line. In addition to java command arguments, ServletExec/AS accepts several required and optional arguments. You can also start a ServletExec/AS instance using the StartServletExec script.
6. SERVLETEXEC/AS: APPLICATION SERVER (UNIX/LINUX) Argument -backlog -name -home -log -root Explanation the ServletExec/AS instance communicates with the web server adapter(s). If you modify this value, you must also modify the web server configuration file(s) as described above. Optional. The default value is 50.
6. SERVLETEXEC/AS: APPLICATION SERVER (UNIX/LINUX) Argument directory> -addl Explanation Optional. This can be used to specify additional document directories (other than the root) and is specified in two forms: -addl = -addl = For example: -addl /test=usr/local/test -addl www.abc.com/support=usr/local/support -addl -mimetypes
6. SERVLETEXEC/AS: APPLICATION SERVER (UNIX/LINUX) arguments. A complete list of StopServletExec command line arguments is provided below. 6.7.2.2 Using the java Command We recommend that you use the StopServletExec script to stop a ServletExec/AS instance. However, it is possible to stop a ServletExec/AS instance by invoking the StopServletExec program using the java command from a command line.
6. SERVLETEXEC/AS: APPLICATION SERVER (UNIX/LINUX) See Section 6.4 for more information. 3. Enter the name, IP address, and port number of the ServletExec/AS instance when prompted. Note You can install multiple web server adapters on multiple machines or on a single machine to forward requests to a single ServletExec/AS instance. 6.7.4 Multiple ServletExec/AS Instances (Multiple Java VMs) It is possible to configure a web server adapter to forward HTTP requests to more than one ServletExec/AS instance.
6. SERVLETEXEC/AS: APPLICATION SERVER (UNIX/LINUX) 6.8 Uninstalling ServletExec/AS To uninstall ServletExec/AS or a web server adapter 1. Re-run the ServletExec/AS installation script. 2. Click the appropriate option from the following choices: uninstall a ServletExec/AS instance, uninstall a web server adapter, or completely uninstall ServletExec/AS. 3. If you are uninstalling a web server adapter or completely uninstalling ServletExec/AS, you must manually edit the web server configuration file (obj.
