Installation guide

ManualsBrandsRed Hat ManualsComputer equipmentNETSCAPE ENTERPRISE SERVER 6.1 - NSAPI PROGRAMMER GUIDE

ServletExec

4.1

Installation Guide

for Microsoft Internet Information Server

Netscape Enterprise Server

iPlanet Web Server

and Apache HTTP Server

Summary of content (91 pages)

PAGE 1
ServletExec 4.
PAGE 2
NEW ATLANTA COMMUNICATIONS, LLC ServletExec 4.1 Installation Guide TM September 13, 2001 Version 4.1 Copyright © 1997-2001 New Atlanta Communications, LLC 100 Prospect Place • Alpharetta, Georgia 30005-5445 Phone 678.366.3211 • Fax 678.366.3210 http://www.newatlanta.com ServletExec is a trademark of New Atlanta Communications, LLC All other trademarks and registered trademarks herein are the property of their respective owners.
PAGE 3
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 .......
PAGE 4
.3 INSTALLING SERVLETEXEC/NSAPI FOR MULTIPLE SERVERS ........................................32 4.4 RUNNING THE SERVLETEXEC/NSAPI INSTALLER..........................................................32 4.5 WHAT WAS INSTALLED AND/OR MODIFIED? ..................................................................33 4.5.1 The ServletExecNSAPI Directory .......................................................................33 4.5.2 Server start Script .................................................................
PAGE 5
6.2.3 Web server adapters ..........................................................................................70 6.2.3.1 Apache HTTP Server ................................................................................................ 71 6.3 UNINSTALLING OTHER SERVLET ENGINES ....................................................................71 6.4 RUNNING THE SERVLETEXEC/AS INSTALLER................................................................71 6.5 WHAT WAS INSTALLED AND/OR MODIFIED? ........
PAGE 6
1 1. Introduction Installing ServletExec 4.1 (all products) N ew Atlanta ServletExec 4.1 is a high-performance, reliable, and cost-effective web application server that implements the JavaTM Servlet API 2.3 and JavaServer Pages™ (JSP) 1.2 standards defined by Sun Microsystems, Inc. as component technologies of the Java 2 Platform, Enterprise Edition (J2EETM). Additional information about J2EE, servlets, and JSP technologies can be found on Sun’s web site: http://java.sun.
PAGE 7
1. INTRODUCTION If you’re using Microsoft IIS or NES/iWS 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. ServletExec Servlet Engine ServletExec Application Server • Runs within the web server process (loaded as a Windows DLL or UNIX .
PAGE 8
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® and Microsoft Windows 2000®. 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_41.exe.
PAGE 9
2. MICROSOFT IIS PLUGIN (WINDOWS) 2. Close all open applications, making sure to include DBMON. 3. Make backup copies of the ServletExecData, 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 and earlier: The default location for the ServletExec ISAPI directory is within the C:\InetPub directory.
PAGE 10
2. MICROSOFT IIS PLUGIN (WINDOWS) OS Web Server 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 4.1 is not supported on JDK or JRE 1.1.x or earlier. To install ServletExec/ISAPI 4.
PAGE 11
2. MICROSOFT IIS PLUGIN (WINDOWS) 1. Look for a Sun JDK using the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit If Sun JDK found, go to Step 2. Otherwise, look for a Sun JRE using the following key: HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment If Sun JRE found, go to Step 2. Otherwise, look for an IBM JDK or JRE using the following keys .
PAGE 12
2. MICROSOFT IIS PLUGIN (WINDOWS) 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.5 What Was Installed and/or Modified? When you installed ServletExec/ISAPI, three changes were made to your system: • • • The ServletExec ISAPI directory was created. The ServletExec_ISAPI.
PAGE 13
2. MICROSOFT IIS PLUGIN (WINDOWS) 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. ServletExecData This subdirectory contains the ServletExec/ISAPI configuration files.
PAGE 14
2. MICROSOFT IIS PLUGIN (WINDOWS) Figure 1. ISAPI NTFS Permission Settings (Windows 2000) 2.5.3 ServletExec_ISAPI.dll The ServletExec_ISAPI.dll dynamic link library (DLL) was installed in the directory you selected during the installation process. This directory must be mapped to a Microsoft IIS virtual directory and the virtual directory must have execute permission enabled.
PAGE 15
2. MICROSOFT IIS PLUGIN (WINDOWS) 2.5.4 Registry & Metabase Entries The ServletExec/ISAPI installer creates a new registry entry with the following key: HKEY_LOCAL_MACHINE\SOFTWARE\New Atlanta Communications\ServletExec ISAPI This key contains a single parameter named Home, that contains the path to the ServletExec ISAPI directory. Note If you move the ServletExec ISAPI directory after installation, you must modify this key to contain the new path. 2.5.4.
PAGE 16
2. MICROSOFT IIS PLUGIN (WINDOWS) Figure 2. Server Properties (IIS 5.0) Figure 3. ISAPI Filters (IIS 5.0) ServletExec 4.
PAGE 17
2. MICROSOFT IIS PLUGIN (WINDOWS) 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_AS.dll. To examine or manually modify the metabase ISAPI Filter under IIS 4.0 1.
PAGE 18
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 The username and password assigned in the ServletExec Admin User Interface must match those of an existing Windows user as defined in the User Manager. See Section 1.4.1 of the ServletExec 4.1 User Guide for information on setting the username and password for the ServletExec Admin UI. 2.6.2 IIS 4.0 (Windows NT 4.0) and IIS 5.
PAGE 19
2. MICROSOFT IIS PLUGIN (WINDOWS) 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. Click the Directory Security tab and under Anonymous Access and Authentication Control, click Edit.
PAGE 20
2. MICROSOFT IIS PLUGIN (WINDOWS) your servlet. Otherwise, your servlet will be running under the IUSR_ account (the account under which IIS runs anonymous user requests). 2. If your servlet is configured to be loaded by ServletExec/ISAPI during initialization, your init() method will be executed under the SYSTEM account. Otherwise, if your servlet is loaded when it receives its first request, the rules for item #1, above, apply. 3.
PAGE 21
2. MICROSOFT IIS PLUGIN (WINDOWS) 2.9 Uninstalling ServletExec/ISAPI To completely uninstall ServletExec/ISAPI 1. 2. 3. 4. Stop IIS as described in Section 2.8. Close any open DBMON windows. Open Control Panel and click Add/Remove Programs. In the list, click ServletExec 4.1 ISAPI, and then click Add/Remove or Change/Remove, depending on your operating system. 5. Sometimes the ServletExec/ISAPI uninstaller may not be able to remove all of the installed files.
PAGE 22
3 3. ServletExec/NSAPI: Netscape/iPlanet Plugin (Windows) Installing the Windows 2000/Windows NT plugin servlet engine for Netscape Enterprise Server and iPlanet 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 in a standard, robust, highperformance environment. The ServletExec/NSAPI 4.1 installer for Windows is named ServletExec_NSAPI_41.
PAGE 23
3. NETSCAPE/IPLANET 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 server instances, stop each one that is running. 2. Close all open applications, making sure to include DBMON. 3. Make backup copies of the ServletExecData, Servlets, classes (if you’ve added an additional one), and webapps (versions 3.
PAGE 24
3. NETSCAPE/IPLANET PLUGIN (WINDOWS) 3.2 System Requirements 3.2.1 Operating System and Web Server • • ServletExec/NSAPI 4.1 is not supported on Windows 95, Windows 98 or Windows ME. ServletExec/NSAPI 4.1 supports the following operating systems and web servers: OS 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.0 and higher Table 3. NSAPI Supported Operating Systems and Web Servers 3.2.
PAGE 25
3. NETSCAPE/IPLANET 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/ISAPI 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.
PAGE 26
3. NETSCAPE/IPLANET PLUGIN (WINDOWS) 3.3 Uninstalling Other Servlet Engines Very Important You must uninstall any other servlet engines previously installed for use with NES/iWS before installing and using ServletExec/NSAPI. In particular, modifications to the obj.conf configuration file for other servlet engines must be removed. In addition, you must disable the NES/iWS built-in servlet support as described in the following sections before installing ServletExec/NSAPI. 3.3.
PAGE 27
3. NETSCAPE/IPLANET PLUGIN (WINDOWS) • • Stop all servers before running the ServletExec/NSAPI installer. Use the same installation directory for all ServletExec/NSAPI installations. The ServletExec/NSAPI installer will create a separate subdirectory within the ServletExecNSAPI directory for each server instance See 3.6.1 for a detailed explanation of the NSAPI directory. When installed for multiple NES/iWS server instances, each instance of ServletExec/NSAPI creates its own Java VM.
PAGE 28
3. NETSCAPE/IPLANET PLUGIN (WINDOWS) There are no restrictions on the location of the ServletExecNSAPI directory. Important Do not move the ServletExecNSAPI directory after installation. There is a registry entry that allows ServletExec/NSAPI to find this directory. If you move this directory, ServletExec/NSAPI will be unable to find its configuration files. See 3.6.2 for a detailed discussion of registry entries.
PAGE 29
3. NETSCAPE/IPLANET PLUGIN (WINDOWS) shared by multiple servlets in this directory. See the READ ME file within the classes subdirectory for more information. Servlet Logs This subdirectory contains the Servlet.log files that capture the output from the servlet log() method. In some cases, this directory doesn’t get created until the first ServletExec initialization. ServletExecData This subdirectory contains the ServletExec/NSAPI configuration files.
PAGE 30
3. NETSCAPE/IPLANET PLUGIN (WINDOWS) Important If you chose not to allow the installer to make these modifications, you must make them manually. Several lines must be added to the obj.conf configuration file for each server for which ServletExec/NSAPI is installed. The location of these lines within the obj.conf file is very important. 1. Add the following lines to the beginning of obj.conf before the other Init directives: Init fn=”load-modules” shlib="/ServletExec_NSAPI.
PAGE 31
3. NETSCAPE/IPLANET PLUGIN (WINDOWS) Important The NameTrans directive for ServletExec/NSAPI must appear first in the list of NameTrans directives for the default object. The Service directive for ServletExec/NSAPI must similarly appear first in the list of Service directives for the default object. Figure 7 shows a partial obj.conf file for NES 3.6 with ServletExec/NSAPI installed. The default installation locations were used for both the server and ServletExec/NSAPI.
PAGE 32
3. NETSCAPE/IPLANET PLUGIN (WINDOWS) See the following example in Figure 7 Init fn="load-modules" shlib="C:/Program Files/New Atlanta/ServletExec NSAPI/ServletExec_NSAPI.dll" funcs="ServletExecInit,ServletExecFilter,ServletExecService" Init fn="ServletExecInit" Init fn=flex-init access="C:/Netscape/SuiteSpot/https-ntserver1/logs/access" format.access="%Ses->client.ip% %Req->vars.auth-user% [%SYSDATE%] \ "%Req->reqpb.clf-request% \ " %Req->srvhdrs.clf-status% %Req->srvhdrs.
PAGE 33
4 4. ServletExec/NSAPI: Netscape/iPlanet Plugin (SPARC Solaris) Installing the SPARC Solaris plugin servlet engine for Netscape Enterprise Server and iPlanet Web Server S ervletExec/NSAPI 4.1 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 in a standard, robust, highperformance environment. The ServletExec/NSAPI 4.
PAGE 34
4. NETSCAPE/IPLANET PLUGIN (SPARC/SOLARIS) 4.1 Upgrading from a Previous Version You can upgrade to ServletExec 4.1 from all previous versions except versions 3.0C or 3.0E. If you have either of these versions installed, you will need to completely uninstall that version and do a clean installation of ServletExec 4.1. To upgrade to a new version of ServletExec/NSAPI and maintain your old configuration settings 1. Stop your web server.
PAGE 35
4. NETSCAPE/IPLANET PLUGIN (SPARC/SOLARIS) where is the full path to the ServletExecNSAPI directory. The default path to the ServletExecNSAPI directory is different in ServletExec/NSAPI 4.x than for previous versions, so you may also need to update the . 8. The start script for each upgraded NES/iWS server instance may need to be updated to reflect the base location of the new ServletExec installation. For ServletExec/NSAPI 4.
PAGE 36
4. NETSCAPE/IPLANET PLUGIN (SPARC/SOLARIS) 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 SPARC Solaris from: http://java.sun.com/j2se/ Note Sun has created two versions of the JDK for Solaris, which it refers to as the Production and Reference implementations (or releases).
PAGE 37
4. NETSCAPE/IPLANET PLUGIN (SPARC/SOLARIS) Tip If you still have problems running ServletExec/NSAPI after deactivating the Java interpreter, check the Init directives in your obj.conf file as described in Section 3.6.3. 4.2.4 Disable the Built-In Servlet Engine (iWS 4.0 and higher) For iWS 4.0 and higher, 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.
PAGE 38
4. NETSCAPE/IPLANET PLUGIN (SPARC/SOLARIS) To use the ServletExec/NSAPI Installer 1. Give the file execute permission. # chmod +x ServletExec_NSAPI_41.sh 2. From a shell command line, run it as follows: # ./ServletExec_NSAPI_41.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.
PAGE 39
4. NETSCAPE/IPLANET PLUGIN (SPARC/SOLARIS) application and a JSP page with an embedded bean. See the appropriate chapters of the ServletExec User Guide for instructions on running these examples. https- There is one https- subdirectory for each NES/iWS server instance on which ServletExec/NSAPI is installed. See further discussion of this directory directly below.
PAGE 40
4. NETSCAPE/IPLANET PLUGIN (SPARC/SOLARIS) configured. This subdirectory contains the “default” folder for automatically deploying web applications hosted by ServletExec/NSAPI. See the README in the webapps directory and the ServletExec User Guide for more information. 4.5.2 Server start Script The Netscape 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.
PAGE 41
4. NETSCAPE/IPLANET PLUGIN (SPARC/SOLARIS) • For JDK 1.2 reference release: LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/java/jre/lib/sparc LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/java/jre/lib/sparc/native_thr eads LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/java/jre/lib/sparc/classic export LD_LIBRARY_PATH • For JRE 1.
PAGE 42
4. NETSCAPE/IPLANET PLUGIN (SPARC/SOLARIS) Note The first Init directive will normally appear on a single line within the obj.conf file. It’s shown as spanning two lines here for formatting reasons. It may span two lines within obj.conf, in which case the second line must begin with a tab or space character. Important If you had previously activated, then deactivated the Java Interpreter for NES 3.5.1 or higher, two Init directives similar to the following will still be in your obj.
PAGE 43
4. NETSCAPE/IPLANET PLUGIN (SPARC/SOLARIS) # chmod +x ServletExec_NSAPI_41.sh 2. From a shell command line, run it as follows: # ./ServletExec_NSAPI_41.sh 3.
PAGE 44
4. NETSCAPE/IPLANET PLUGIN (SPARC/SOLARIS) Init fn="load-modules" shlib="/usr/local/NewAtlanta/ServletExecNSAPI/bin/ServletExecNSAPI.so" funcs="ServletExecInit,ServletExecFilter,ServletExecService" Init fn="ServletExecInit" Init fn=flex-init access="/usr/local/netscape/suitespot/https-ntserver1/logs/access" format.access="%Ses>client.ip% - %Req->vars.auth-user% [%SYSDATE%] \ "%Req->reqpb.clf-request% \ " %Req->srvhdrs.clf-status% %Req->srvhdrs.content-length%" Init fn=load-types mime-types=mime.
PAGE 45
5 5. ServletExec/AS: Application Server (Windows) Installing the Windows 2000/Windows NT web server adapters for Microsoft IIS, Netscape Enterprise Server, iPlanet 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). ServletExec/AS does not contain a built-in HTTP (web) server.
PAGE 46
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) To upgrade to ServletExec/AS 4.1 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.
PAGE 47
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) OS Web Server Windows® 2000 Microsoft IIS 5.0 Netscape Enterprise Server (NES) 3.5.1 and higher iPlanet Web Server (iWS) 4.0 and higher Apache HTTP Server 1.3.9 through 1.3.20 Windows NT® 4.0 Service Pack 4 or higher Microsoft IIS 4.0 Netscape Enterprise Server (NES) 3.5.1 and higher iPlanet Web Server (iWS) 4.0 and higher Apache HTTP Server 1.3.9 through 1.3.20 Table 5. AS-Windows Supported Operating Systems and Web Servers 5.2.
PAGE 48
5. SERVLETEXEC APPLICATION SERVER (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/AS will not be able to load and initialize the Java VM. 5.2.3.1 Multiple JDK/JRE Versions Installed You may have multiple versions of the JDK/JRE installed on your system. The ServletExec/AS installer uses registry entries to determine which installed JDK/JRE to use.
PAGE 49
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) 5.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 and httpd.conf configuration files for other servlet engines must be removed. For Microsoft IIS, the ISAPI Filters metabase entries associated with other servlet engines must be removed. See Section 5.5.3.
PAGE 50
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Figure 9. Setup Type 3. Click Next. Review the license agreement carefully and check the READ ME for any last minute notices before continuing. 4. After accepting the license agreement and reviewing the READ ME, the ServletExec/AS installer prompts you for the destination folder for installing the ServletExec/AS files. You may choose the default or click Browse to select a different folder.
PAGE 51
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) list of configured servers (both NES and iWS support multiple servers per physical machine). Figure 10. Web Server Adapter 7. Before making any change to your computer, the ServletExec/AS installer displays a confirmation dialog, as represented in Figure 11. 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.
PAGE 52
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Figure 11. Confirm ServletExec Installation 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.
PAGE 53
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) • The web server configuration file was modified to enable Connection Pooling between the web server adapter and ServletExec The following sections describe each of these changes. 5.5.1 The ServletExec AS Directory The ServletExec AS directory was created in the location you selected during the installation process.
PAGE 54
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) its contents are only used by the installer. lib The lib subdirectory contains the Java archive (.jar) files required by ServletExec/AS. Important Do not modify the contents of this directory! The se- subdirectories of the ServletExec AS directory each contain the following subdirectories. classes The classes subdirectory is automatically added to the ServletExec VM classpath.
PAGE 55
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) 5.5.3 Microsoft IIS If you installed a web server adapter for Microsoft IIS, the installer modified your system as described in the following sections. 5.5.3.1 ServletExec_Adapter.dll The ServletExec_Adapter.dll dynamic link library (DLL) was installed in the C:\InetPub\Scripts directory, which is mapped to the SCRIPTS virtual directory in the default IIS installation; or, ServletExec_Adapter.
PAGE 56
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Figure 12. Server Properties (IIS 5.0) Figure 13. ISAPI Filters (IIS 5.0) ServletExec 4.
PAGE 57
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) 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 14.
PAGE 58
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Figure 15. ISAPI Filters 5.5.3.3 The servletexec.properties Configuration File The servletexec.properties file was created in the C:\InetPub\scripts directory (or, in the same directory as ServletExec_Adapter.dll, if the DLL was installed in some other directory). This file contains the configuration properties used by the ServletExec adapter for the Microsoft IIS/PWS web server.
PAGE 59
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) To modify Connection Pooling in IIS for ServletExec/AS • Add the following to the end of the servletexec.properties file on two separate lines: servletexec..pool-increment= servletexec..pool-max-idle= 5.5.3.4 Web Application URL Context For each web application URL context configured using the ServletExec Admin UI, you must update the applications property in the servletexec.properties file.
PAGE 60
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Several lines must be added to obj.conf for each server for which ServletExec/AS is installed (the location of these lines within the obj.conf file is very important): 1. Add the following lines to the beginning of obj.conf before the other Init directives: Init Init fn=”load-modules” shlib="/bin/nsapi/ServletExec_Adapter.dll" funcs="ServletExecInit,ServletExecService" fn=”ServletExecInit” .instances="127.0.0.
PAGE 61
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Important You must stop and restart the NES/iWS web server after modifying the obj.conf configuration file. Init fn="load-modules" shlib="C:/Program Files/New Atlanta/ServletExec AS/bin/nsapi/ServletExec_Adapter.dll" funcs="ServletExecInit,ServletExecService" Init fn="ServletExecInit" .instances="127.0.0.1:8888" Init fn=flex-init access="D:/Netscape/SuiteSpot/https-/logs/access" format.access="%Ses->client.ip% - %Req->vars.
PAGE 62
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) To modify Connection Pooling in NES/iWS for ServletExec/AS • Add the following to the beginning of the obj.conf file. Go back to Step 1 earlier in this section, copy it that line and insert a space at the end it, adding the following immediately after and on the same line (the formatting requirements of this page are wrapping the text to fit the page): .pool-max-idle= .poolincrement= 5.5.4.
PAGE 63
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) 5.5.5.2 Server Configuration File (httpd.conf) To install a ServletExec/AS web server adapter for Apache, modifications must be made to the web server’s httpd.conf file. This section describes the modifications to httpd.conf made by the ServletExec/AS installer. 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.
PAGE 64
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) To update the ServletExecApplications directive in httpd.conf • Use the following form: ServletExecApplications /URL-context1 /URL-context2 SetHandler servlet-exec SetHandler servlet-exec 5.5.5.
PAGE 65
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) web server root document directory is C:\Program Files\Apache Group\Apache\htdocs and the following subdirectories appear beneath htdocs: htdocs\subdir1 htdocs\subdir2 htdocs\subdir2\subdir3 In this example, there are two levels of subdirectories beneath htdocs, so to create a suffix alias of .jsp, you should add three Location directives to httpd.conf, one for htdocs and one for each subdirectory level: # # suffix alias for htdocs #
PAGE 66
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) 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. The following sections describe both methods. 5.6.1.1 StartServletExec.bat The batch file StartServletExec.bat is provided for your convenience in starting the ServletExec/AS instance. It is also used by Services to start the ServletExec/AS instance. StartServletExec.
PAGE 67
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Argument -name -home -log -root Explanation argument specifies the size of the ServletExec/AS incoming request queue. Requests received when the queue is full are rejected.
PAGE 68
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Argument Explanation -addl = For example: -addl /test=C:\Test -addl www.abc.com/support=C:\Support -addl -mimetypes See previous explanation. Optional. This specifies the path to the NES, iWS, or Apache mime.types file. If this argument isn’t provided, the ServletContext.getMimeType() method always returns null.
PAGE 69
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) 5.6.2.1 StopServletExec.bat The batch file StopServletExec.bat is provided for your convenience in stopping the ServletExec/AS instance. It is also used by the Services control panel to stop the ServletExec/AS instance. StopServletExec.bat invokes the StopServletExec Java program to stop the ServletExec/AS instance. StopServletExec.bat includes defaults for the java and StopServletExec command line arguments. You can edit StopServletExec.
PAGE 70
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) Argument -admin Explanation program assumes port 80. If -direct is specified without a port, then the StopServletExec program assumes port 8888. Specifies the username/password as configured by the ServletExec Admin UI. If these are not specified correctly, the stop command will be rejected by the ServletExec/AS instance. Therefore, you must edit the StopServletExec.
PAGE 71
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) 5.6.4 Multiple ServletExec/AS Instances (Multiple Java VMs) It’s possible to install and run multiple ServletExec/AS instances on a single server machine. Each ServletExec/AS instance will run independently of the others, each within its own Java Virtual Machine (VM). To install multiple ServletExec/AS instances • Run the ServletExec/AS installer again to install another instance.
PAGE 72
5. SERVLETEXEC APPLICATION SERVER (WINDOWS) 3. Click the appropriate option from the following choices: uninstall a ServletExec/AS instance, uninstall a web server adapter, or completely uninstall ServletExec/AS. 4. If you are uninstalling a web server adapter (or completely uninstalling ServletExec/AS), you must manually edit the web server configuration file(s) to remove the ServletExec/AS directives If you are completely removing ServletExec/AS from your system, delete the ServletExec AS directory.
PAGE 73
6 6. ServletExec/AS: Application Server (UNIX/Linux) Installing the UNIX web server adapters for Netscape Enterprise Server, iPlanet 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). ServletExec/AS does not contain a built-in HTTP (web) server. Therefore, it must be used in conjunction with Netscape Enterprise Server (NES), iPlanet Web Server (iWS), or Apache HTTP Server.
PAGE 74
5. SERVLETEXEC APPLICATION SERVER (UNIX) To upgrade to ServletExec/AS 4.1 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 ServletExec Data, 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.
PAGE 75
5. SERVLETEXEC APPLICATION SERVER (UNIX) OS Web Server SPARC Solaris 2.6, 7, and 8 Netscape Enterprise Server (NES) 3.5.1 and higher iPlanet Web Server (iWS) 4.0 and higher Apache HTTP Server 1.3.4 or higher HP-UX 10.20 and 11.0 Same as SPARC Solaris AIX 4.3.3 and 4.3.10 IPlanet Web Server (iWS) 4.0 and higher Apache HTTP Server 1.3.4 or higher Red Hat Linux 6.2 and 7.0 Apache HTTP Server 1.3.4 or higher Table 8.
PAGE 76
5. SERVLETEXEC APPLICATION SERVER (UNIX) • • • Apache HTTP Server 1.3.4 and higher Covalent Raven 1.4 and higher C2Net (Red Hat) Stronghold 2.3.x and 2.4.x 6.2.3.1 Apache HTTP Server Building the ServletExec/AS web server adapter for Apache requires use of the Apache apxs utility, which in turn requires that you have perl, a C compiler, and a dynamic shared linker installed prior to running the installer.
PAGE 77
5. SERVLETEXEC APPLICATION SERVER (UNIX) # ./ServletExec_AS_41.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.
PAGE 78
5. SERVLETEXEC APPLICATION SERVER (UNIX) 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. se- There is one se- subdirectory for each ServletExec/AS installed on the computer. See further discussion of this directory directly below.
PAGE 79
5. SERVLETEXEC APPLICATION SERVER (UNIX) webapps One of these subdirectories exists for each virtual server configured. This subdirectory contains the “default” folder for automatically deploying web applications hosted by ServletExec/AS. See the README in the webapps directory and the ServletExec User Guide for more information. 6.5.
PAGE 80
5. SERVLETEXEC APPLICATION SERVER (UNIX) 2. The following directives must be added after the