Oracle Web Application Server™ Installation Guide Release 3.0.1 for Windows NT Part No.
Oracle Web Application Server™ Installation Guide Release 3.0.1 Copyright © Oracle Corporation 1996, 1997, 1998 All rights reserved. Printed in the U.S.A. This software was not developed for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It is the customer’s responsibility to take all appropriate measures to ensure the safe use of such applications if the programs are used for such purposes.
Oracle Government Purchasing, Oracle Government Receivables, Oracle Government Revenue Accounting, Oracle Graphical Schema Editor, Oracle Graphics, Oracle Human Resource Management Systems, Oracle Human Resources, Oracle Illustrated, Oracle Illustrated Series, Oracle Imaging, Oracle Incident, Oracle Industries, Oracle Installer, Oracle InstantSQL, Oracle Integrator, Oracle Internet Commerce, Oracle Internet Server, Oracle InterOffice, Oracle InterOffice Client, Oracle InterOffice Manager, Oracle InterOffice
Contents Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Chapter 1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of the Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Web Application Server Control Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Configuration for Multi-node Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Setting Up a Secure Oracle Web Application Server . . . . . . . . . . . . . . . . . . . 4-4 Chapter 5 Configuration of Third-party HTTP Servers . . . . . . . . . . . . . . . . . . . . . . . . . .5-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface This Installation Guide is the primary source of introduction, installation, and configuration information for Oracle Web Application Server for Windows NT. Audience This Installation Guide is necessary for installing, configuring, or administering Oracle Web Application Server 3.0.1 for Windows NT.
Listener Administrator Home page, and follow the online documentation link icon. The PDF documentation can be found by clicking the online documentation icon in the Oracle for Windows NT program group. Note: To read the PDF online documentation, install the Adobe Acrobat Reader by double-clicking the file ACROREAD.EXE in the ACROBAT directory on the product CD. The Web Application Server 3.0.
Conventions Used in This Manual This table lists the typographical conventions used in this manual. Convention Meaning Monospace text Indicates text that must be typed exactly as shown. set echo off All uppercase plain Indicates command names, SQL reserved words and keywords as in ALTER DATABASE. All uppercase plain is also used for directory names and file names. ORANT\DATABASE\INITORCL.ORA Bold Used for filenames, directories, and utilities such as: owsctl.
Convention Meaning C:\> Represents the Windows NT command prompt of the current hard disk drive. Your prompt may differ and may, at times, reflect the subdirectory in which you are working. Symbols Symbols other than brackets and vertical bars must be entered in commands exactly as shown.
Web Application Server Documentation Manager Oracle Corporation 500 Oracle Parkway Redwood Shores, CA 94065 Preface xi
xii Oracle Web Application Server™ Installation Guide
CHAPTER 1 Introduction Overview of the Product As the World Wide Web matures, a new generation of Internet and Intranet business applications is emerging. These new applications will incorporate real business transactions, data-driven multimedia content, and interactive information.
Oracle Web Application Server 3.0.1 operates across a wide range of operating systems, from PCs to workstations, and through its open cartridge API, supports a diverse class of languages and applications. Oracle Web Application Server 3.0.1 is the first Web server to support real transactions and it does so using X/ Open DTP standards. Note: A cartridge is a program, run on the server by the Web Request Broker (WRB), that interfaces to a Web server (Oracle or otherwise) through the WRB API.
Security With all the potential of real business applications, but no face-to-face contact, the Web presents new security challenges. Oracle Web Application Server 3.0.1 supports full end-to-end security at the client, at every level within the Web server architecture, and through the firewall to an Oracle database. This unprecedented degree of granularity supports not only username-password protection, but also custom security schemes.
Fully portable WRB API • CORBA-compliant ORB-based Web Request Broker • unifying API for Netscape, Microsoft, and Oracle HTTP servers • native Java environment • auto-generated wrapper classes for PL/SQL • native access to Oracle • HTML presentation classes • National Language Support (NLS) • support for persistent database connections • HTML 3.
VRML Cartridge • VRML 2.
• dedicated process per request • automatic cleanup • native imagemap support • multiple imagemap extensions • configurable DNS resolution • Common Log Format • OCI cartridge (Oracle Call Level Interface) • Rdb cartridge • Oracle Security Server • Oracle Internet Commerce Server (cartridge-based solution for electronic commerce) • third-party cartridges available through the Cartridge Solutions Network Miscellaneous Optional Extensibility Oracle Web Application Server 3.0.
• transactional support across multiple cartridges Persistent Storage Services • APIs for storing and retrieving content or managing content from a SQL database • schema attributes include content-type, author, creation date, etc.
1-8 Oracle Web Application Server™ Installation Guide
CHAPTER 2 Installation Requirements System Requirements Hardware Requirements Hardware Item Required CPU An Intel compatible 486 or higher processor Memory 64 MB (32 MB for a listener only machine) Disk Space 150 MB Swap Space 64 MB CD-ROM Device RockRidge format
Software Requirements Software Item Version Operating System Windows NT Server v. 4.0 Web Browser Any browser that supports tables and forms Listener Oracle 40-bit Oracle 128-bit Netscape FastTrack V2.0, V2.0.1 Netscape Enterprise Server V2.0, V2.0.1 Microsoft Internet Information Server V2.0, V3.0 Oracle RDBMS 7.1.6 7.2.2x 7.2.3x 7.3.2.x 7.3.3.x 8.0.3* 8.0.4* JAVA Developer Kit (JDK) 1.0.
Oracle products and minimum release levels for using the Web Application Server with an Oracle database. Products Minimum Release Oracle Server 7.1.6 PL/SQL 2.1.6 SQL*Net 2.1.6 TCP/IP Protocol Adaptor 2.1.6 Note: The Oracle Server and PL/SQL are not installed automatically with Web Application Server. Remote Database Installation If you wish to access an Oracle database on a remote machine, install the products listed above on the remote machine.
the architecture of the Web Application Server is based on CORBA (common object request broker architecture), which is a standard for distributed objects. One advantage of distributing the processes on different machines is performance and scalability. You can handle more requests without using up too much resources from one machine. See Appendix C, “Multi-node Configuration” on page 1 for additional information.
Multi-Node Remote - Listener Only Installation This installation shows an example of a remote-node in a multi-node configuration. • Listener (Oracle, Microsoft, or Netscape) Multi-Node Remote - Cartridge and Listener Installation This installation shows an example of a remote-node in a multi-node configuration.
2-6 Oracle Web Application Server™ Installation Guide
CHAPTER 3 Installation Procedure Supported Installation Activities The following installation activities are described in this chapter: • Pre-installation Information • First-time Web Application Server Installation • Installing over an Existing Web Application Server • Uninstalling Oracle Web Application Server You may also use the Installer to configure third-party Web servers for use with Oracle Web Application Server.
Installing a Primary Node in a Multi-node Configuration The following activities are supported when installing a primary node in a multi-node setup. • first time 3.0.1 installation • 3.0.1 reinstallation (configuration of third-party HTTP products saved automatically on partial install) • 3.0.
2. Install Oracle Web Application Server. During installation, make sure that you check the “Remote Oracle RDBMS Connection (SQL*Net V2.3)” option in the optional cartridge installation section. If during installation “Remote Oracle RDBMS Connection” was not selected, then make sure that SQL*Net V2.3 on the Oracle Web Application Server CD is installed. 3. Use the SQL*Net Easy Configuration tool to create a database alias for the database instance. 4. Ensure that TRACE_CLIENT_LEVEL = ON in the sqlnet.
Administrator Listener Settings This information is required for a single node or primary node (in a multi-node) installation. • Port Number - Defaults to 8888. • User Name - Defaults to “admin”. • User Password - The password you will use for the node. Web Listener Settings The following information is needed for the general usage Web listener. You may use the Oracle listener or a third-party HTTP listener such as Netscape FastTrack or Microsoft IIS.
Then launch the SETUP.EXE program, which starts the Oracle Installer. 2. Choose the language you want to use during installation. 3. Enter the following Oracle Installation Settings: Company Name Enter the name of your company. Oracle Home Enter the directory for the ORACLE_HOME environment variable. This will be the directory under which the Web Application Server directory tree will be placed. ORACLE_HOME can be any alphanumeric value up to 256 characters. The default is C:\ORANT.
If you install Oracle Application Server in a multi-node configuration, you must install one primary node and at least one remote node. • Primary multi-node installation - The primary node is where your WRB and configuration files are installed. • Remote multi-node installation - Related remote nodes are nodes that share the same WRB. Remote node installation allows you to specify which components of the Oracle Web Application Server you want for a specific node.
• ODBC Cartridge • Oracle JDBC Drivers (Beta) • Remote Oracle RDBMS Connection (SQL*Net V 2.3) • VRML Cartridge If you use Oracle8, you must install SQL*Net regardless of whether your Oracle8 installation is local or remote. Note: 7. Site Installation Enter the following information about the installation site. Site Name - Defaults to “WEBSITE30”. Oracle Web Application Server allows you to have multiple server sites running in a single installation environment.
The shared key can vary from 0 to 255 bytes. The string is made up of only hexadecimal characters; for example, 0-9 and a-f. Larger shared keys have higher security. Shared key size has minimal impact on performance. This field should be left blank if you do not wish to use encryption. 8. Administration Listener Information This screen only displays on a single- or primary-node installation when the Web Request Broker is installed.
Note: The Microsoft Internet Information Server does not use a listener name. Port Number - Defaults to 80. Do not change this number. Note: For Microsoft, you need to follow the Post-Install steps in Post-Installation and Administration on page 4-1. 11. Copy Files This dialog allows you to confirm your configuration parameters. When you click OK, the installation is performed. 12. If you chose to install SQL*Net V 2.3 products, you are now asked to specify which SQL*Net V2.
information. An upgrade copies library and message files only based on component choices and skips configuration questions. - New Install - This option installs Web Application Server Release 3.0.1 and overwrites your existing Web Application Server configuration information. A new install backs up old files before overwriting them. In a new install, the configuration files for the administration listener and the default listener (for example SVADMIN.CFG, WRB.APP, and SVWWW.
Uninstalling Oracle Web Application Server To uninstall the Oracle Web Application Server for Windows NT, follow these steps: 1. Shutdown all the listeners (including the Administration listener, Netscape, and Microsoft IIS listeners). Warning: Do not shut down services using the Control Panel Services window. Use the following command at the DOS prompt: owsctl stop Where is the name of the listener you want to shut down. 2.
Home, the Software Asset Manager is displayed. Figure 3-1: Software Asset Manager The right side of the window displays products installed on your system. Select the products you wish to remove. Use Shift + click, or click and drag to select multiple items. c. 3-12 Click Remove. The Installer will remove the selected products from your system.
CHAPTER 4 Post-Installation and Administration Starting Web Application Server Start the Web Request Broker (WRB) and the Administration Listener by using the owsctl command. At the DOS prompt, type: owsctl start wrb This starts the WRB. To start the Administration Listener, type the following at the DOS prompt: owsctl start admin To start your listener, type the following at the DOS prompt: owsctl start where is the name of your listener.
To verify that a listener is running, at the DOS prompt, type: owsctl status Listeners The installation process creates two listeners using the values input at install time, the Administration Listener and the Default Web Listener. If the defaults are chosen, the values are as listed below. If other values were input, please note them. Administration Listener The Administration Listener is used for Web Application Server configuration and administration tasks. • Host Name: hostname.
Web-based Administration Use the Oracle Web-based administration pages to configure and administer Web Application Server. 1. Use your Web browser to navigate to the Web Application Server Administrator Welcome Page at: http:/// where localhost is the hostname of the machine on which Oracle Web Application Server is installed, and port is the port number you have assigned to the administration web listener (8888 by default). A dialog box appears, requesting you to authenticate. 2.
1. Add the remote node names to the wrb.app file on the primary node. a. In the primary node’s wrb.app file, add the fully qualified name(s) of any remote hosts. Your entries should be of the form: . b. Restart the WRB on the primary node by entering: owsctl stop wrb owsctl start wrb 2. Start up the listener processes by typing: owsctl start where listenerName specifies the name of the listener. 3. Install the correct components on the remote nodes.
CHAPTER 5 Configuration of Thirdparty HTTP Servers Overview A feature of Oracle Web Application Server Version 3.0.1 is the HTTP daemon adapter which enables the Web Request Broker (WRB) to run seamlessly using third-party HTTP servers (listeners) instead of the Oracle Web Listener shipped with Oracle Web Application Server. Oracle Web Application Server supports: • Netscape FastTrack 2.0 and 2.01 • Netscape Enterprise Server 2.0 and 2.01 • Microsoft Internet Information Server (IIS) 2.0 and 3.
Oracle Installer automatically creates registry entries under HKZY_LOCAL_MACHINE\Software\Oracle when you upgrade a Netscape HTTP server to use the Oracle WRB: OWS30:\OWS30 OWS_ADdPCFG30:\ADMIN\ADPSPY.CFG The installation automatically backs up original Netscape FastTrack and Enterprise HTTP server settings during the migration. The new settings filename is OBJ.CONF.SAV, and it is saved to the same directory as the original OBJ.CONF file.
owsctl start fnsl To stop the server: owsctl stop servername To check the status of the server: owsctl status servername Note: If you use owsctl to start the Netscape server, you must register the Netscape server with the Oracle Web Application Server. Changes Made During Configuration The wlmigrat program does the following: • Configures the Netscape server configuration file obj.
NameTrans fn=pfx2dir from=/tr-img \ dir=”%ORAWEB_HOME%/demo/img” \ NameTrans fn=pfx2dir from=/sample/bin \ dir=”%ORAWEB_HOME%/sample/bin”name=”cgi” NameTrans fn=pfx2dir from=/sample \ dir=”%ORAWEB_HOME%/sample” \ NameTrans fn=pfx2dir from=/oracle \ dir=”%ORAWEB_HOME%/doc” The following functions are added to the obj.
browsers that support NTLM (Microsoft Internet Explorer) can configure the server. 3. Enable anonymous access to IIS. 4. Configure the Web Request Broker for IIS by going to the Web Request Broker Administration page at http://localhost:port/ows-doc/Intro.html where localhost is the name of the host machine and port is the port on which your administration server is running (default is 8888). 5. Confirm that the following files exist: • %ORAWEB_HOME%\BIN\NDWFIS30.DLL • %ORAWEB_HOME%\ADMIN\ADPIIS.
5-6 Oracle Web Application Server™ Installation Guide
CHAPTER 6 Migrating to Oracle Web Listener This chapter describes how to migrate from a Netscape server to Oracle Web Application Server. Requirements Before migrating a Netscape FastTrack or Enterprise server to Oracle Web Application Server, make sure the system meets the following requirements: • The Oracle Web Application Server 3.0.1 is installed on the same machine as the Netscape server. The Oracle Web Application Server Administration Server must be running.
Introduction During Migration of the Netscape server to Oracle Web Application Server, the Netscape configuration files obj.conf, magnus.conf, and mime.types are read and parsed, then translated into the Oracle Web Application Server listener and WRB configuration files such as svserver.cfg and svserver.app. However, some of the Netscape server features are not converted to the Oracle Web Application Server listener.
determine if and how it should service the request. This file contains information like directory mappings and security restrictions. • mime.types - This file provides the server with a mapping from file extensions to the MIME types. Both migration choices (configuring the Netscape server to use the Oracle WRB, and migrating the Netscape server to Oracle Web Application Server) use these configuration files extensively. Migrating a Netscape Server to Oracle Web Application Server 1.
• reads and parses the Netscape obj.conf, magnus.conf, and mime.types files and translates the migratable items into the Oracle Web Application Server configuration • writes the translated configuration and the default Oracle Web Application Server configuration to the Oracle Web Listener svserver.cfg file • registers the newly migrated Oracle Web Application Server with the owl.cfg file Migrating the magnus.conf File The ServerName directive defines the server host name.
Migrating the obj.conf and mime.types Files The obj.conf file defines how the server should handle the incoming requests for documents and programs. An object contains a name or a pattern match which defines the resources it applies to. For example: Object also contains a series of directives.
[DirMaps] /Netscape/cgibin/ CR /cgibin/ • NameTrans fn=document-root root=/Netscape/docs The value of root= is the document root. This directive is mapped into the svserver.cfg [DirMaps] section as: [DirMaps] /Netscape/docs/ NR / • NameTrans fn=unix-home from=/~subdir=”public_html,home.html” The value of subdir= is the user directory if the URL specifies ~user. It is mapped into the svserver.
[Server] UseDirIndexing = true • PathCheck index-names=index.html,home.html fn=find-index The value of index-names= is the initial file to be searched if a URL does not specify the file name. It is mapped into the svserver.cfg [Server] section as: [Server] InitialFile = index.html Note: Oracle Web Application Server only allows one file to be specified in the InitialFile parameter, while Netscape allows multiple files to be specified in a comma-separated list.
Server Side Includes (parse-html) On Netscape, the parse-html option means it will parse the HTML files with any SSI before sending them to the client. The parse-html option is associated with the optional opts=no-exec (which prevents the client from executing anything on the server machine), and can be applied to any files and directories on the server machines, whether the files and directories appear on its directory mapping or not. For example: # # dirmap # ... NameTrans from=”/ows/3.
parsed-html or SSI files into the Oracle Application Server’s virtual directory to be processed with SSI. The SSI parameters ParseHTMLExtn, EnableExecTag, and ExtensionList can be configured as the user requires. The wlmigrat tool lists all files and directories with the parse-html option set to on at the end of migration. The user is encouraged to move them into a directory where they can be processed by the Oracle Web Application Server SSI.
6-10 Oracle Web Application Server™ Installation Guide
CHAPTER 7 Upgrading from Previous Releases Upgrade from WebServer 2.x to Web Application Server 3.0.1 To upgrade from WebServer 2.x to Web Application Server 3.0.1: 1. Install Oracle Web Application Server 3.0.1 on the same machine as Oracle WebServer 2.x. Make sure you do not use the same listener name and DCD name as used in WebServer 2.x. Warning: Windows NT does not support multiple Oracle Homes. If you already have an existing Oracle Home, changing it during installation of Release 3.0.
• %ORAWEB_HOME%/admdoc/OWS2xto30.html • %ORAWEB_HOME%/admbin/wlupgrade Access the Upgrade Page Make sure that the Oracle Administration Server 3.0.1 is running. 1. Access the upgrade page from the Web Application Server 3.0.1 Administration Server by entering the following location in your Web browser: http://hostname.domain:port/ows-adoc/Migrat.html You may also access this page by clicking on the following links: a.
• If conflicts are found, it lists the conflicts and prompts you to ‘keep 2.x parameters’ or ‘use 3.0.1 parameters’. If there is no conflict, you are prompted with ‘ok to upgrade’. • Merges the Oracle WebServer 2.x svserver_name.app information into Web Application Server 3.0.1 wrb.app file. • Merges the Oracle WebServer 2.x svserver_name.cfg security information such as user, group, and realms into the wrb.app file. • Updates the svserver_name.cfg for Web Application Server 3.0.1.
Entry Description owa_connect_string SQL*Net v2 connect string if using remote database owa_valid_ports ports allow access to database owa_log_dir directory that stores database errors owa_nls_lang database language type owa_error_page html page that shows errors There are two built-in DCDs, owa_dba and owa_default_service, in the owa.cfg. These DCDs are not upgraded because they are created during installation. Upgrade and merge the entries into wrb.app.
username=www_dba password=manager oracle_home=private/home/wchan/work/ows-home connect_string=DOHC nls_lang=AMERICAN_AMERICA.US7ASCII [PLSQL_DOHC_WEB] owa_valid_ports=8818 3368 owa_log_dir=/private/home/wchan/work/ows-home/log/ owa_dad_name=DOHC_WEB You can refer to the DCD by using DOHC_WEB. The following table shows the parameter mappings between WebServer 2.x DCD, Web Application Server 3.0.1 DAD, and Web Application Server 3.0.1 PL/ SQL. OWS2.x DCD OWS3.0.1 DAD_xx OWS3.0.
1. The upgrade tool updates the [DynApps] section to Web Application Server 3.0.1. In WebServer 2.0, the section is: [DynApps] %ORACLE_HOME%/ows2/lib/libndwll.so ndwlld_DynamicInit %ORACLE_HOME%/ows2/lib/ndwrd.so sndwrdini_init %ORACLE_HOME%/ows2/lib/ndwp.so ndwp_dinit In WebServer 2.1, the section is: [DynApps] %ORACLE_HOME%/ows21/lib/ndwfss.so oracle_adp_init The upgrade tool will update the entry to: [DynApps] %ORAWEB_HOME%/lib/libwrl.so oracle_adp_init 2. The upgrade tool updates the svserver_name.
Conflicts occur when cartridges, application directory mapping, section parameters, and application protection defined in Web Application Server 3.0.1 wrb.app are already defined in WebServer 2.x svserver.app with different values. For example: In WebServer 2.x svserver.app: [Apps] .. MYAPP1 /private/oracle/ows21/myapp1/libmyapp1.so myapp1entry 0 100 [AppDirs] /usr/myapp1 MYAPP1 /private/oracle/ows21/myapp1 [MYAPP1] MyApp1Param1 = True MyApp1Param2 = False In Web Application Server 3.0.1, wrb.app: [Apps] .
example shown above, the cartridge MYAPP1 is in conflict, thus the definition for MYAPP1 in WebServer 2.x svserver.app is not merged into Web Application Server 3.0.1 wrb.app. Its related parameters such as application directory mapping /usr/myapp1, and the cartridge section [MYAPP1] are not merged into Web Application Server 3.0.1 wrb.app either. Parameters without conflict are upgraded with the tool and merged into the Web Application Server 3.0.1 wrb.app file.
APPENDIX A Starting and Stopping the Listener owsctl Utility Commands The owsctl utility starts, stops, reloads, and displays the status of the Oracle Web Listener, Oracle Web Status Monitor, WRB, ORB and Cartridge processes. You can also use it to display the version number of the cartridge.
• If listener_name is supplied, it starts the named Oracle Web Listener. • If the Netscape server is registered with Oracle Web Application Server, owsctl starts up the Netscape server based on the registration information. • The ORB processes are mnaddrsrv, mnrpcnmsrv, and mnorbsrv. Use NCX or ncx to run these processes. Make sure you run the NCX processes before exclusively starting the WRB process.
• If CARTRIDGE or cartridge is supplied, it shows the current status of cartridge processes, such as wrbfac. -e This option exclusively starts/stops the WRB processes. When you use this option to start/stop the WRB, the NCX (ORB) processes are not started/stopped. Environment To use owsctl, you must have the following environment variables set: • ORAWEB_HOME - Absolute path where Oracle Web Application Server is installed. • ORAWEB_SITE - This is the site name for the Oracle Web Application Server.
The following examples show how to run the processes: Example 1: Starting the WRB Process Start the WRB processes on the primary machine by entering: owsctl start wrb Example 2: Displaying the WRB Status Show the status of WRB processes on the primary node by entering: owsctl status wrb Example 3: Starting the Listener (Optional) Start the Oracle Web Listener Admin by entering: owsctl start admin Example 4: Displaying the Listener Status (Optional) Show the status of the Oracle Web Listener Admin by ente
owsctl start ncx Example 10: Starting the WRB Processes without the ORB processes: To exclusively start the WRB processes use: owsctl start -e wrb Files WRB/Cartridge pid: %ORAWEB_ADMIN%/ows/%ORAWEB_SITE%/wrb/config/ .ows_machine_name.pid WRB/Cartridge address: %ORAWEB_ADMIN%/ows/%ORAWEB_SITE%/wrb/config/.omnaddr Web Listener registration file: %ORAWEB_ADMIN%/ows/%ORAWEB_SITE%/httpd_machine_name/ owl.cfg WRB process files: %ORAWEB_HOME%/bin/mnaddrsrv.exe %ORAWEB_HOME%/bin/mnrpcnmsrv.
A-6 Oracle Web Application Server™ Installation Guide
APPENDIX B Multi-node Configuration The Oracle Web Application Server is made up of several processes — most of which are defined as services on Windows NT. You can run these processes on different machines on the network. You can do this because the architecture of the Web Application Server is based on CORBA (common object request broker architecture), which is a standard for distributed objects. Two advantages of distributing the processes on different machines are performance and scalability.
Type Process Services Runs on Description WRB Processes wrbcfg OraWeb_wrbcfg Primary The WRB configuration provider wrblog OraWeb_wrblog Primary The WRB logger wrbasrv wrbahsrv OraWeb_wrbsrv OraWeb_wrbahsrv Primary and Remote The WRB authentication servers wrbroker OraWeb_wrbroker Primary The Web Request Broker wrbvpm OraWeb_wrbvpm Primary The WRB virtual path manager wrbfac OraWeb_wrbfac Primary and Remote The cartridge factory Primary and Remote Cartridge processes Primary
instances for its node. 6. The cartridge instances are then registered with the Dispatcher, so that the Dispatcher can direct requests to them. When subsequent requests for the cartridge come in, the Dispatcher sends the requests to unoccupied cartridge instances.
Distributing the Authentication Server Processes You can run the Authentication Server on machines other than the primary node, and you can run multiple copies of the Authentication Server. The main reasons for doing this are performance and reliability. • If the primary node is running many processes and resources on the node are scarce, you might get better performance if you move the Authentication Server to a less busy machine.
To stop the processes for the Authentication Server: owsctl stop -p wrbasrv owsctl stop -p wrbahsrv Troubleshooting and Tips If requests are not being sent to the remote nodes, consider the following: Multi-node Configuration • You have to use the same UDP port number on all nodes. This number is saved in the registry entry HKZY_LOCAL_MACHINE\Software\Oracle\Medianet\OMNADD R.
Index A E Administration Listener, default settings, 4-2 Adobe Acrobat Reader, installation, viii External Listener Registration utility, 5-2 C cartridges remote installation, 3-6 running on remote nodes, B-1 certificate, requesting, 4-4 common gateway interface, 1-5 configuration files Netscape Server, 6-2 configuring Microsoft IIS to use WRB, 5-4 CORBA-compliant ORB, 1-3 customer support, x D database connection descriptors (DCD), 4-2 database installation local, 2-3 remote, 2-3 Default Web Listener,
L Listener remote installation, 3-6 LiveHTML Cartridge, 1-4 local database installation, 2-3 localhost, definition, 4-3 logging, 1-5 M Microsoft IIS, configuring to use WRB, 5-4 migrating changes made during, 5-3, 6-3 from Netscape Server, 6-2 tools, 6-2 migration utility, using with Netscape servers, 5-2 multi-node configuration, 2-4 N Netscape Server configuration information, 6-2 migrating from, 6-2 O ODBC cartridge, 1-6 open architecture, 1-1 Oracle WebServer 2.
V VRML Cartridge, 1-5 W Web Application Server starting, 4-1 Web Request Broker, 1-3 administration page location, 5-5 Web Request Broker (WRB), 3-6 remote installation, 3-6 WebServer 2.
