User manual BUSINESS OBJECTS BUSINESSOBJECTS 6 FOR WINDOWS CONFIGURING THE TOMCAT 4.1-IIS 5 CONNECTOR

[. . . ] A Microsoft Internet Information Services (IIS) plugin (filter and extension), the connector's job is to identify requests for URL that are actually JSPs or servlets, and then forward those requests to the Tomcat server for processing. The connector is actually a filter that examines every request reaching the HTTP server. Any requests that are not Java-related are ignored; those that are Java-related are passed to the Tomcat server. IIS loads the redirector plugin then calls its filter function for each incoming request. [. . . ] Launch the IIS management console by clicking Start > Programs > Administrative Tools > Internet Services Manager. Add a new virtual directory for your IIS/PWS (Personal Web Server) web site by right-clicking Default Web Site, then clicking New > Virtual Dir. Its physical path should be the directory where you placed isapi_redirect. dll (in our example it is c:\jakartatomcat\bin\win32\i386). Assign this directory execute access. Business Objects Documentation Supplement 6 Configuring the Tomcat 4. 1/IIS 5 Connector 7. Now add isapi_redirect. dll as a filter for your IIS/PWS web site by rightclicking Default Web Site, clicking the ISAPI Filters tab, then clicking Add. The name of the filter should reflect its task (for example, jakarta), its executable must be c:\jakarta-tomcat\bin\win32\i386\isapi_redirect. dll. If you're using PWS, use regedit to add/edit the Filter DLLs key under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W3SVC\ Parameters. This key contains a list of DLLs with their full paths, separated by commas. The redirector is now configured. Making sure the redirector works Start Tomcat, then make sure the redirector is working. You can do this by typing http://localhost/examples/jsp/index. html as the URL in a web browser, then running some of the JSP examples. If this doesn't work correctly, see Troubleshooting on page 10 Configuring the ISAPI redirector Configuring the Tomcat 4. 1/IIS 5 Connector 7 Adding additional contexts The examples context is useful for verifying your installation, but you also need to add the contexts that you will need in your specific deployment. Adding the context to Tomcat (for instructions, see the Tomcat documentation) 2. Adding the context to the ISAPI redirector Adding contexts to the ISAPI redirector Adding a context to the ISAPI redirector is simple. Just open the uriworkermap. properties file in a text editor, and then add a line that looks like: /context/*=<worker_name> where <worker_name> is the name of one of the Tomcat workers Workers and their names are defined in the worker. properties file, which by default comes with a single pre-configured worker called defworker that you can use. For example, if you want to add a context called shop, add the following line to uriworkermap. properties: /shop/*=defworker Up through Tomcat version 3. 2, a uriworkermap. properties-auto is automatically written each time Tomcat is started. This file includes settings for each of the contexts that Tomcat will serve during its run. Each context has settings to have Tomcat handle servlet and JSP requests, but by default, static content is left to be served by IIS. Each context also has a commented out setting to have Tomcat handle all requests to the context. You can rename this file (so it won't be overwritten the next time Tomcat is started) and uncomment this setting or make other customizations. You can also use this file as is in your worker_mount_file setting. Business Objects Documentation Supplement 8 Configuring the Tomcat 4. 1/IIS 5 Connector Advanced context configuration Sometimes it's better to have IIS serve the static pages (HTML, GIF, JPEG, etc. ), even if these files are part of a context served by Tomcat. For example, in the examples context, there is no need to serve the HTML and GIF files from the Tomcat process. To make IIS serve static files that are part of the Tomcat, you must: 1. [. . . ] # Note: # ----> lbfactor must be > 0 # ----> Low lbfactor means less work done by the worker. worker. ajp13. lbfactor=1 # # Specify the size of the open connection cache. #worker. ajp13. cachesize # #------ DEFAULT LOAD BALANCER WORKER DEFINITION ------------#-----------------------------------------------------------# # # The loadbalancer (type lb) worker perform weighted round-robin # load balancing with sticky sessions. # Note: # ----> If a worker dies, the load balancer will check its state # once in a while. [. . . ]