Oracle9i Application Server Wireless Edition Configuration Guide Release 1.1 May 2001 Part No.
Oracle9i Application Server Wireless Edition Configuration Guide, Release 1.1 Part No. A86701-02 Copyright © 2001 Oracle Corporation. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information of Oracle Corporation; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws.
Contents List of Tables Send Us Your Comments ................................................................................................................... xi Preface........................................................................................................................................................... xiii Audience ................................................................................................................................................ xiii Organization.......
1.9 1.10 2 Geocoding Setup.................................................................................................................. 1-12 JDBC Connection Pooling .................................................................................................. 1-12 FastForward 2.1 Introduction............................................................................................................................ 2.1.1 Features....................................................................
4 Logging 4.1 4.2 4.2.1 4.2.2 4.3 4.4 4.5 4.6 5 4-1 4-1 4-2 4-3 4-5 4-5 4-5 4-6 Multiple JVM Support and Load Balancing 5.1 5.2 5.3 5.4 5.5 5.5.1 5.5.2 5.6 5.6.1 5.6.2 5.6.3 6 Overview ................................................................................................................................ Database Logging.................................................................................................................. Configuring the Database Logger..............................
.4 6.5 6.6 6.7 6.8 7 System Password Encryption/Decryption........................................................................ Extensibility..................................................................................................................... LoadXml.................................................................................................................................. Upload and Download Utilities ...............................................................................
10.3 10.4 10.5 10.6 10.7 10.8 10.9 10.10 10.11 10.12 10.13 10.14 10.15 10.16 10.17 10.18 10.19 10.20 10.21 10.22 10.23 10.24 10.25 10.26 Notification.properties ..................................................................................................... Rmi.properties ................................................................................................................... oemevent.properties .................................................................................................
viii
List of Tables 2–1 2–2 2–3 2–4 2–5 4–1 4–2 4–3 5–1 6–1 6–2 7–1 8–1 8–2 8–3 8–4 9–1 9–2 9–3 10–1 10–2 10–3 10–4 10–5 10–6 10–7 10–8 10–9 10–10 10–11 10–12 10–13 10–14 10–15 10–16 10–17 10–18 10–19 10–20 Mail parameters..................................................................................................................... 2-5 Directory parameters ............................................................................................................
–21 10–22 10–23 10–24 10–25 10–26 x Parameters of the mappers.xml File ............................................................................... Parameters of the routers.xml File .................................................................................. Parameters of the Strip.properties File........................................................................... Strip Processing Classes....................................................................................................
Send Us Your Comments Oracle9i Application Server Wireless Edition Configuration Guide, Release 1.1 Part No. A86701-02 Oracle Corporation welcomes your comments and suggestions on the quality and usefulness of this document. Your input is an important part of the information used for revision.
xii
Preface The Oracle9i Application Server Wireless Edition Configuration Guide discusses how to configure Wireless Edition. This Preface contains these topics: Audience Organization Related Documentation Documentation Accessibility Audience Oracle9i Application Server Wireless Edition Configuration Guide is for users who are setting up their environments to administer and/or develop applications for wireless users.
Organization This document contains: Chapter 1, "Overview" Overview of post-installation configuration procedures. Chapter 2, "FastForward" Configure Mail and LDAP applications. Chapter 3, "Alerts and SMS Request Listener" Configuring the SMS Listener to process time-based, scheduled services known as Alerts. Chapter 4, "Logging" Configuring the logging capabilities of Wireless Edition.
Additionally, Oracle9i Application Server, Database, Networking, Application Development, and other documentation is available on your Documentation CD, and at docs.oracle.com. Documentation Accessibility Oracle’s goal is to make our products, services, and supporting documentation accessible to the disabled community with good usability. To that end, our documentation includes features that make information available to users of assistive technology.
xvi
1 Overview This document describes the post-installation configuration of Wireless Edition. Each section of this document presents a different topic. These sections include: ■ Section 1.1, "Installation Overview" ■ Section 1.2, "Manual Configuration" ■ Section 1.3, "Upgrade" ■ Section 1.4, "Samples" ■ Section 1.5, "Web Integration Server" ■ Section 1.6, "Wireless Edition Client" ■ Section 1.7, "OCI8 JDBC Driver" ■ Section 1.8, "User Provisioning" ■ Section 1.
Installation Overview Important: ■ In this document: WE_HOME is the directory in which Wireless Edition is installed followed by the "panama" sub-directory. For example: c:\ias10210\panama (Windows) /private/ias10210/panama (UNIX) Replace "WE_HOME" with the fully-qualified directory path. ■ ORACLE_HOME is the directory in which Oracle9i Application Server is installed. 1.
Manual Configuration 1.2 Manual Configuration After installation, perform the manual configuration steps described in this section: ■ Section 1.2.1, "Configure Oracle HTTP Server and JServ" ■ Section 1.2.2, "Configure ProxyFirewall.properties" ■ Section 1.2.3, "Start the Oracle HTTP Server" ■ Section 1.2.4, "Wireless Edition Configuration Verification" 1.2.1 Configure Oracle HTTP Server and JServ This section describes the configuration of the Oracle HTTP Server and JServ. 1. Configure the httpd.
Manual Configuration a. Verify that the Java Virtual Machine is version 1.2.2. For example: wrapper.bin= /Apache/jdk/bin/java.exe b. After the other "wrapper.classpath" entries, add all the required Wireless Edition files after the "tools.jar" entry in the classpath. For Windows (for UNIX replace "\" with "/"): wrapper.classpath=\server\classes wrapper.classpath=\lib\panama.zip wrapper.classpath=\lib\panama_core.zip wrapper.classpath=\lib\panama_portal.
Manual Configuration 4. For UNIX only, to display the images from the Personalization Portal properly, set the DISPLAY environment variable in the jserv.properties file to configure access to the host on which the server runs: a. If the X server runs on the same machine as the Wireless Edition server, set the DISPLAY environment variable in the jserv.properties file as follows: wrapper.env=DISPLAY=:0.
Manual Configuration b. In the Startup Servlets section, add the Wireless Edition specific servlets: servlets.startup=oracle.panama.ParmImpl c. In the Servlet Aliases section, add the Wireless Edition specific servlets: servlet.rm.code=oracle.panama.ParmImpl 1.2.2 Configure ProxyFirewall.properties If a proxy server is used to access an external web site from Wireless Edition, configure the ProxyFirewall.properties file: 1. Set http.use.proxy to true. For example: http.use.proxy=true 2.
Upgrade The login page should appear. The Personalization Portal prompts you to enter a user name and a password. You can log in using “Administrator” as the user name and “manager” as the password. 2. Run the Wireless Edition Request Manager by accessing the following URL: http://host_name.domain:7777/ptg/rm The login page should appear. The page prompts you to enter a user name and a password. You can log in using “Administrator” as the user name and “manager” as the password.
Samples 1.4 Samples You can install the sample services and adapters into the repository after completing the steps in Section 1.2 and/or Section 1.3. 1. Change to the sample directory: WE_HOME\sample (Windows) WE_HOME/sample (UNIX) 2. Modify the upload.bat or upload.sh file using the -l option to specify the Wireless Edition user and password for which the data is loaded. For example: -l Administrator/manager 3. Run the following: upload.bat samples.xml (Windows) upload.sh samples.xml (UNIX) 4.
Web Integration Server 1.5 Web Integration Server The Wireless Edition Web Integration Server hosts services that applications can use to exchange data and information sources via the Web. The Web Integration Server is installed with Wireless Edition. The following steps guide you through the configuration process of the Web Integration Server: 1. Run the Web Integration Server. From the WE_ HOME/panama/WebIntegration/Server/bin directory, typing the following: a. For Windows: server.bat b.
Wireless Edition Client 1.6 Wireless Edition Client The Wireless Edition client runs only on the Windows platform. The client installation consists of the following: ■ Service Designer ■ Web Integration Developer 1.6.1 Service Designer The Service Designer is a visual interface for implementing and managing services in Wireless Edition. It creates and modifies Wireless Edition objects, including adapters, transformers, and services.
OCI8 JDBC Driver 2. From the Edit menu, select Preferences, and then Configuration. 3. Enter the Proxy (HTTP) and the Secure Proxy (HTTPS) settings appropriate for your environment. 4. Click OK. 1.7 OCI8 JDBC Driver The default configuration of Wireless Edition uses the Oracle THIN JDBC driver. For a production environment, the Oracle OCI8 JDBC driver is required, as it provides improved performance, concurrency, scalability, and multi-byte support.
User Provisioning 1.8 User Provisioning You can integrate your repository with an existing provisioning system using one of the following: 1. You can manage users by creating a service with the Wireless Edition provisioning adapter. The provisioning adapter supports the Wireless Edition services that create, search for, update, and delete users at runtime. 2. Use the LoadXml utility to import users from a flat XML file that conforms to the Repository DTD.
JDBC Connection Pooling Connection pooling under Wireless Edition session management supports server environments that include short-lived threads, long-lived threads (thread pool model), or a combination of short-lived and long-lived threads. The following system properties apply to the connection pooling mechanism: #Minimum number of connections for the connection pool db.connect.minConnections=5 #Maximum number of connections for the connection pool db.connect.
JDBC Connection Pooling 1-14 Oracle9i Application Server Wireless Edition Configuration Guide
2 FastForward This document describes the FastForward Email and Directory applications, their installation, and configuration. Each section of this document presents a different topic.
Introduction 2.1 Introduction The FastForward Email and Directory applications enables you to provide your end users with access to their corporate email and directory lookup on any mobile device. Mobile email will drive productivity within your enterprise, allowing employees to stay in touch while away from the office. 2.1.
Installation Mail ■ JavaMail API 1.2 from Sun Microsystems ■ JavaBeans Activation Framework extension (JAF) from Sun Microsystems Directory ■ JNDI 1.2 from Sun Microsystems 2.2.2 Installation 2.2.2.1 On Your Own Web Server and JSP Engine Ensure you have a working web server and a JSP engine configured to run on that web server. Refer to your web server and JSP engine documentation for more information. Put all the jar files from the lib directory into the JSP engine’s classpath. Ensure that
Configuration 2.3 Configuration The OracleMobile Mail and Directory applications provide mobile access for industry standard electronic mail systems and Directory servers. Supported backends include: Mail ■ IMAP ■ POP3 ■ MS Exchange 5.5 and 2000 ■ Lotus 4.6 and Release 5 Directory ■ LDAP servers supporting JNDI 1.2 Mail and Directory applications can be two separate applications, or they can be configured separately in such a way that they can interact with each other.
Configuration An example of the files is in the doc directory. IMPORTANT: The root "oracle" directory containing the properties files must be in the classpath of the JSP engine. There is a properties directory in the install; modify the properties files there, and put the /properties directories in the classpath of the JSP engine. Note: Parameters and values in properties file is case sensitive. Ensure you are using the proper format for your UNIX or Windows platforms.
Configuration mail.folder.sent The name of the Sent folder on the mail server. Default is "Sent". This property is optional. mail.default.emaildomain Default email domain for sending emails. When sending emails, if the email domain is not specified, the default email domain will be appended to the username. mail.log Determines whether log in is enabled or not. Value is either "true" or "false". Default is "true". mail.logger Full path of the log file. mail.msgfetch.
Configuration mail.designer.path Path to the application specified in ServiceDesigner Service Trees. Check the "studio" parameter. For example, if Mail is the service defined for the Mail application, and it is put in a folder called Apps under Service Trees, then the path should be /Apps/Mail. For the Directory application, you must configure the following parameters: Table 2–2 Directory parameters ldap.host LDAP server hostname. ldap.port LDAP server port number. The default is 389. ldap.
Configuration ldap.username ldap.password If an LDAP login is required, a default username and password can be specified. Ensure the ldap.enableLogin property is true. ldap.emailEnabled Enables/disables email access from a directory. If enabled, when a person from LDAP is displayed, users can send an email directly from the email address. ldap.emailAttribute Name of the email attribute of a person in the LDAP schema. ldap.
Configuration 2.3.0.3.2 Configuring Mail and Directory Parameters through request Parameters defined this way will override the values defined in the properties file. The following Mail parameters can be passed through request: Table 2–3 Mail parameters passed through request CONFIG_FILE Specifies the properties file that defines all the other Mail properties. This allows multiple properties files for different configurations. By default, the file OracleMobileEmail.properties will be used.
Configuration DOMAIN Definition, possible values, and default values are the same as the "mail.default.emaildomain" in the properties file. LOG Definition, possible values, and default values are the same as the "mail.log" in the properties file. LOGFILE Definition, possible values, and default values are the same as the "mail.logger" in the properties file. MAIL_FETCH_ SIZE Definition, possible values, and default values are the same as the "mail.msgfetch.setsize" in the properties file.
Configuration PTG_VERSION Definition, possible values, and default values are the same as the "oracle.panama.version" in the properties file. STUDIO Definition, possible values, and default values are the same as the "studio" in the properties file All the other parameters will be read from the properties file, or the default values will be used. If other parameters are defined property, you can bypass the login. Note that all parameters values are string.
Configuration String getXMLVersion (Object o) Returns the PTG XML version. Ensure it is consistent with the "studio" parameters. Currently, studio is running PTG 1.0. boolean isStudio(Object o) Indicates whether it is running in studio or not. Ensure it is consistent with the "oracle.panama.version" parameters. Currently, studio is running PTG 1.0. String getInboxFolderName (Object o) Returns the Inbox folder name. String getSentFolderName (Object o) Returns the Sent folder name.
Configuration 2.3.0.3.4 Configuration of URL Adapter in PTG 1.1 ServiceDesigner Mail and Directory applications can be run through the URL Adapter in PTG 1.1. To do so, you must create a Master Service and a Service Alias. Here are the steps (for details, refer to the PTG documentation): 1. Open Service Designer and connect to a PTG 1.1 instance. 2. Open the Master Services folder at the top level.
Configuration Figure 2–1 Service Designer Window Now you can use e-mail.
3 Alerts and SMS Request Listener Alerts and SMS Request Listener discusses alerts and the SMS Request Listener in Wireless Edition. Each section of this document presents a different topic. These sections include: ■ Section 3.1, "Overview" ■ Section 3.2, "Alerts" ■ Section 3.3, "SMS Request Listener" ■ Section 3.4, "Request and Notification Queue Pool" In this document WE_HOME is the directory in which Wireless Edition is installed followed by the "panama" sub-directory.
Alerts and alert address can be created by end users through Wireless Edition personalization from the desktop computer or the device. Services in Wireless Edition can be invoked through the HTTP protocol and through SMS. Users can invoke the services through SMS with the corresponding service name. However, currently only services without input arguments can be invoked through SMS. The result of the service execution is returned as another SMS. The capability is provided through the SMS Request Listener.
Alerts 3.2.2 Notification Queue The result of an alert execution, if any, together with the alert creator’s default alert address, is placed in the notification queue. The Wireless Edition dequeues notification messages out of the notification queue. If the alert address is an email address, the result is sent out as an email message. If the alert address is a phone number, the result is sent out as SMS to the specified phone number. 3.2.
Alerts Edition can also use the URL connection to the SMS-C server when sending the SMS message. In this case, provide the correct URL to the SMS-C server: sms.server.url= 3.2.4.2 SMPP Protocol If the SMPP protocol is used to communicate between the Wireless Edition and SMS-C when sending the notification message, set: sms.driver.class=oracle.panama.util.sms.SmsSMPPDriver Set the following entries with the appropriate values: # The SMPP system id # sms.smpp.system.
SMS Request Listener 3.2.4.5 Flow-Control Configure the following entries for the SMS-control: # The max number of SMS chunks per message. # sms.message.maxchunks= # # The maximum number of bytes per message. # sms.message.maxsize= 3.2.4.6 Wireless Edition SMS System Account for SMS-C If there is a dedicated SMS system account created at SMS-C for the Wireless Edition to send the SMS to, configure the following entries appropriately: # Wireless Edition SMS System Account Id sms.account.
Request and Notification Queue Pool To configure the SMS Request Listener: 1. Include oracle.panama.util.sms.SmsServer as another daemon thread in the locator.request.daemon.classes entry in the System.properties file in the WE_ HOME/server/classes/oracle/panama/core/admin directory. 2. Configure the SMS protocol. See Section 3.2.4.3. 3. If the UCP protocol is used when configuring the SMS protocol, set: sms.receiver.listener.mode=true 4.
Request and Notification Queue Pool # init.pool.size= # # Minimum Thread pool size # minimum.pool.
Request and Notification Queue Pool 3-8 Oracle9i Application Server Wireless Edition Configuration Guide
4 Logging The document describes the logging capability of Wireless Edition. Each section of this document presents a different topic. These sections include: ■ Section 4.1, "Overview" ■ Section 4.2, "Database Logging" ■ Section 4.3, "Service Designer Logging" ■ Section 4.4, "Server Logging" ■ Section 4.5, "Transaction Logging" ■ Section 4.6, "Configuring the Runtime Monitor and Management" 4.
Database Logging 4.2.1 Configuring the Database Logger The database logger of a Wireless Edition instance must point to a database schema to log the information. This configuration is done in the System.properties file of each Wireless Edition instance. # #System Logger related parameters # # Number of minutes after which the logger thread wakes up to flush # the log entries to the database. This parameter is optional. SystemLog.logger.
Database Logging select access to the V$ tables. # Usage example: log in as system and say "grant select any table to %PANAMA_ USERNAME%" #SystemLog.db.connect.string=%PANAMA_USERNAME%/%PANAMA_USER_PW%@%PANAMA_ HOST%:%PANAMA_PORT%:%PANAMA_SID% If the SystemLog.db.connect.string parameter is set, logged information is stored in a separate database. This parameter should not be set if the logged information is to be stored in the same repository.
Database Logging Table 4–2 Contents of the ptg_service_log Table 4-4 Column Name Description service_id Object Identifier (OID) for the invoked service. service_name Name of the invoked service. ptg_instance_id Unique identifier, for the database instance. final_service_id OID of the final service, for example the master service or folder. final_service_name Name of the final service. session_id Session identifier for which the service was invoked.
Transaction Logging 4.3 Service Designer Logging By default, the Service Designer writes error information to the log directory of the Service Designer home directory. You can modify this setting, and the log naming pattern, in the preferences.xml file. The file is in the WE_ HOME/tools/ServiceDesigner/resources directory. 4.4 Server Logging The Wireless Edition writes server error information to the files and directory specified in the System.properties file.
Configuring the Runtime Monitor and Management You can use the System.properties file to set the directory to which the Wireless Edition writes transaction logs, and to specify a file name pattern for the log files. You can also configure the transaction record pattern. If you enable transaction logging when a user accesses a service that has a cost value set, the transaction log generates data. You can set a cost for a master service using the Wireless Edition Service Designer.
Configuring the Runtime Monitor and Management You can configure the probe component by editing the www-server.properties file in the WE_HOME/server/classes/oracle/panama/core/probe directory. The following daemon manages the implementation: oracle.panama.core.probe.
Configuring the Runtime Monitor and Management 4-8 Oracle9i Application Server Wireless Edition Configuration Guide
5 Multiple JVM Support and Load Balancing Multiple JVM Support and Load Balancing describes multiple Java Virtual Machine (JVM) support in Wireless Edition. Each section of this document presents a different topic. These sections include: ■ Section 5.1, "Overview" ■ Section 5.2, "Multiple Instances on Same Machine as Oracle HTTP Server" ■ ■ Section 5.3, "Multiple Instances on the Same Machine/Oracle HTTP Server on Different Machine" Section 5.
Overview Important: ■ In this document: WE_HOME is the directory in which Wireless Edition is installed followed by the "panama" sub-directory. For example: c:\ias10210\panama (Windows) /private/ias10210/panama (UNIX) Replace "WE_HOME" with the fully-qualified directory path. ■ ORACLE_HOME is the directory in which Oracle9i Application Server is installed. 5.
Multiple Instances on Same Machine as Oracle HTTP Server 5.2 Multiple Instances on Same Machine as Oracle HTTP Server To configure multiple JVM instances on the same machine: 1. Modify the jserv.conf file so the Oracle HTTP Server is aware of the multiple JServ instances that are running. Start each of these JServ instances manually. Insert the following statements after any existing statements in the section that begins with and ends with in the jserv.conf file. The jserv.
Multiple Instances on Same Machine as Oracle HTTP Server ApJServRoute JS2 PC2 . . ApJServRoute JSN PCN f. This file is used internally by Apache for implementing fault tolerance: ApJServShmFile ORACLE_HOME\Apache\Jserv\jserv_shm g. Close the section using: 2. Start the Oracle HTTP Server. ORACLE_HOME\Apache\Apache\Apache.exe -k start -d ORACLE_HOME\Apache\Apache 3. Create and modify the jserv.properties files for each of the instances. Make copies of the default jserv.
Multiple Instances on Same Machine as Oracle HTTP Server structure and modify the structure so that each of the JServ instances have unique port numbers and other resources. For example, these directories should appear as \server\classesx, where x corresponds to each of the JServ instances 1...N. Modify the System.properties file in the \server\classesx\oracle\panama\core\admin directory: a. Set the unique identifier for the instance. x corresponds to each of the JServ instances 1...N.
Multiple Instances on Same Machine as Oracle HTTP Server Table 5–1 Property File Settings Property File Setting \admin\AsynchNotification.properties server.listen.port=5500x \core\admin\AsynchRequest.properties server.listen.port=6500x \core\admin\Ftp.properties ftp.server.port=910x \core\admin\Notification.properties sms.server.port=5000x \core\admin\Rmi.properties rmi.server.port=201x The port number on which the RMI server runs. \probe\www-server.properties port=809x \magent\config\MAgent.
Multiple Instances and Oracle HTTP Server All on Different Machines jserv.properties file to Java as part of the classpath. See Section 5.6.3 for a sample batch script. 5.3 Multiple Instances on the Same Machine/Oracle HTTP Server on Different Machine The steps are the same as in Section 5.2 except for the following: 1. While configuring jserv.conf change the ApJServHost directive so that the Oracle HTTP Server points to the machine running the JServ instances, by specifying its IP address.
Multiple Instances and Oracle HTTP Server All on Different Machines 2. Start the Oracle HTTP Server. 3. On each machine running the JServ instances, modify the jserv.properties file: bindaddress=ip_address_of_machine_running_jserv_instance security.allowedAddresses=oraclehttpserver_ip_address 4. On the machine running the Master Instance, modify the Master.properties file. See Table 5–1 for more information. 5. Modify the system.
Configuring the Personalization Portal for Load-Balancing 5.5 Load Balancing When multiple instances are running, load balancing can be performed by a separate machine. For example, there could be several Oracle HTTP Server instances, each with a set of JServ instances balanced on a one-to-many basis by this machine. The Oracle HTTP Server instances can perform load balancing by using a hardware load balancer in front of the Oracle HTTP Server instances.
Configuring the Personalization Portal for Load-Balancing ■ Section 5.6.1, "Clients/Gateways Support Cookies" ■ Section 5.6.2, "Clients/Gateways Do Not Support Cookies" 5.6.1 Clients/Gateways Support Cookies To set up the Personalization Portal when clients and/or intermediate gateways support cookies, enable one of the load-balanced Wireless Edition instances to service Personalization Portal requests. Modify the jserv.
Configuring the Personalization Portal for Load-Balancing 3. Copy the default zone.properties file in ORACLE_HOME\Apache\Jserv\conf to zone_pp.properties. In this file, ensure that the session.useCookies parameter has a value of true. root.properties= ORACLE_HOME\Apache\Jserv\conf\zone_pp.properties 4. Modify the various Wireless Edition specific properties files. The default location for these files is in the \server\classes directory.
Configuring the Personalization Portal for Load-Balancing h. Set the following in the Notification.properties file in the \server\classes\oracle\panama\core\admin\ directory to: sms.server.port=5000 i. Set the following in the Rmi.properties file in the \server\classes\oracle\panama\core\admin\ directory. This is the port number on which the RMI server runs: rmi.server.port=201 j. Set the following in the www-server.
Configuring the Personalization Portal for Load-Balancing set classpath=%classpath%;ORACLE_HOME\jsp\lib\ojsp.jar set classpath=%classpath%;ORACLE_HOME\lib\servlet.jar set classpath=%classpath%;ORACLE_HOME\Apache\BC4J\lib\jndi.jar set classpath=%classpath%;ORACLE_HOME\lib\xmlparserv2.jar set classpath=%classpath%;\lib\client.zip set classpath=%classpath%;\lib\server.zip set classpath=%classpath%;\lib\caboshare-opt-1_0_0.zip set classpath=%classpath%;\lib\marlin-opt-1_0_0.
Configuring the Personalization Portal for Load-Balancing 5-14 Oracle9i Application Server Wireless Edition Configuration Guide
6 Oracle Enterprise Manager Oracle Enterprise Manager describes the use of Oracle Enterprise Manager with Wireless Edition. Each section of this document presents a different topic. These sections include: ■ Section 6.1, "Overview" ■ Section 6.2, "Prerequisites" ■ Section 6.3, "Configuring the Server, Client, and Middle-tier" ■ Section 6.4, "Setting up the ptg_services.tcl File" ■ Section 6.5, "Configuration for Another Wireless Edition Instance" ■ Section 6.
Overview 6.1 Overview The use of Oracle Enterprise Manager with Wireless Edition provides: ■ Performance monitoring ■ Fault management ■ Configuration management Performance Monitoring The Oracle Enterprise Manager Diagnostic Pack includes Performance Manager and Capacity Planner. The Performance Manager is a Windows NT client side tool for viewing performance data collected by the Wireless Edition Cartridge.
Configuring the Server, Client, and Middle-tier 6.3 Configuring the Server, Client, and Middle-tier The Oracle Enterprise Manager configuration includes server side, client side, and middle tier configuration instructions: ■ ■ ■ The Oracle Enterprise Manager server side configuration involves the Oracle Intelligent Agent and Data Gatherer. See Section 6.3.1.
Configuring the Server, Client, and Middle-tier 4. Append the ptg_services.tcl file name to the nmiconf.1st file found in the ORACLE_HOME/network/agent/config directory. The agent discovers the Wireless Edition service using these files. 5. Edit the ptg_services.tcl file to configure the instance(s) information. See Section 6.4 for instructions on setting up the ptg_services.tcl file. Configuration for a default instance name (PTG1) is provided as an example.
Configuring the Server, Client, and Middle-tier 5. Append the following entry to the svppcart.dat file in the ORACLE_ HOME/odg directory. PTG ALL libvpxptg vpxptg This completes the server side configuration. Restart the Oracle Intelligent Agent. Restart the Data Gatherer.
Configuring the Server, Client, and Middle-tier 1. Un-zip the ptgwincartridge.zip file in WE_ HOME/oem/agent/cartridge/win32 to a directory (referred to as CART_DIR in this document). 2. Copy the file vpxptg.dll in CART_DIR\odg\bin to the ORACLE_HOME\bin directory. 3. Copy the file vpxptgUS.htm in CART_DIR\odg\html to the ORACLE_ HOME\odg\html directory. 4. Copy the file vpxptgus.msb in CART_DIR\odg\mesg to the ORACLE_ HOME\odg\mesg directory. 5. Append the following entry to the svppcart.
Configuring the Server, Client, and Middle-tier 3. Extract this file in the copied directory. This extracts the console integration classes, Performance Manager integration classes, events integration classes, and RMI client and stub for the Console interaction with the server. For example: jar -xvf oemptg.jar 4. The entries in WE_HOME/oem/client/OEMClient.properties.append must be appended to ORACLE_HOME/sysman/config/OEMCLient.properties. The following shows the entries.
Configuring the Server, Client, and Middle-tier 5. The entries in WE_HOME/oem/client/vtdclient.properties.append must be appended to ORACLE_HOME/sysman/config/vtdclient.properties. The following shows the entries: /target/oracle_sysman_diagpack/oracle_sysman_ ptg=oracle.sysman.vtd.VtdPtgCredentials /options/standalone=TRUE 6. Edit the ORACLE_ HOME/classes/oracle/panama/magent/MAgent.properties file to reflect the values of the installed Wireless Edition server name.
Configuring the Server, Client, and Middle-tier $ORACLE_HOME/jlib/ewtcompat-opt-3_3_6.zip $ORACLE_HOME/jlib/ewt-swingaccess-1_1_1.jar $ORACLE_HOME/jlib/share-1_0_8.jar $ORACLE_HOME/jlib/jssl-1_2.jar $ORACLE_HOME/jlib/javax-ssl-1_2.jar $ORACLE_HOME/jlib/netcfg.jar:/ For Windows: %ORACLE_HOME%\classes %ORACLE_HOME%\jdbc\lib\classes111.zip %ORACLE_HOME%\lib\vbjorb.jar %ORACLE_HOME%\lib\vbjapp.jar %ORACLE_HOME%\lib\vbjtools.jar %ORACLE_HOME%\classes\classesFromIDLVisi %ORACLE_HOME%\jlib\ewt-3_3_6.
Setting up the ptg_services.tcl File # Wireless Edition events integration # /com/oracle/sysman/em/tests_datasource/ptg/datasource = oracle.sysman.ptg.PTGTestsDatasource Note: After updating the OMSRegistry.registry file, recreate the Oracle Management Server repository using the Oracle Enterprise Manager configuration assistant. See the Oracle Enterprise Manager Configuration Guide for more information. This completes the middle-tier configuration.
Setting up the ptg_services.tcl File set HostName($NEW_PARAMETER_NAME) $Host; set tnsaddress($NEW_PARAMETER_NAME) "(DESCRIPTION=(ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = TRACE_DB_HOSTNAME)(PORT = TRACE_DB_ PORT)))(CONNECT_DATA=(SID=TRACE_DB_SID)(ORACLE_HOME=TRACE_DB_ORACLE_ HOME)(SERVER=DEDICATED)))" In the following example a new parameter (ServiceName2) is added and the values for the PTG_INSTANCE_NAME, TRACE_DB... are set.
Configuration for Another Wireless Edition Instance set HostName($ServiceName2) $Host; set tnsaddress($ServiceName2) "(DESCRIPTION=(ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = ptgserver-sun.us.oracle.com)(PORT = 1521)))(CONNECT_ DATA=(SID=ptgdev)(ORACLE_HOME=/private/oracle/8.1.7)(SERVER=DEDICATED)))" Note: Place this file in ORACLE_HOME/network/agent/config. Add this file name to nmiconf.lst. To reflect any change to either file restart the Oracle Intelligent Agent and rediscover the node. 6.
Asynchronous Notification of Error Information 6.6 Configuring the Database Logger The database logger of a Wireless Edition instance must point to a database schema to log the information. This configuration is done in the System.properties file of each Wireless Edition instance. See Chapter 4 for more information on the database logger. 6.
Launching the Oracle Enterprise Manager Tools 6.8 Launching the Oracle Enterprise Manager Tools Performance Monitoring is accomplished through the Oracle Enterprise Manager Performance Manager and Capacity Planner tools (provided only for Windows NT). Once the installation is complete: 1. Launch the necessary performance monitoring tool. See the Oracle Enterprise Manager documentation for instructions on how to launch it. 2. At the login screen select Stand-alone and no repository connection. Click OK.
7 Multi-byte Character Support Multi-byte Character Support describes multi-byte character support in Wireless Edition. Each section of this document presents a different topic. These sections include: ■ Section 7.1, "Overview" ■ Section 7.2, "Multi-byte Encoding Schemes" ■ Section 7.3, "Setting the Multi-Byte Encoding for the Personalization Portal" ■ Section 7.4, "Setting up a Netscape Browser to Display Multi-byte Data" ■ Section 7.5, "LocalStrings.
Overview 7.1 Overview This release of Wireless Edition supports single-byte, multi-byte, and fixed-width encoding schemes which are based on national, international, and vendor-specific standards. If the character set is single byte, and that character set includes only composite characters, the number of characters and the number of bytes are the same. If the character set is multi-byte, there is generally no such correspondence between the number of characters and the number of bytes.
LocalStrings.properties Files and Localization 7.3 Setting the Multi-Byte Encoding for the Personalization Portal The Personalization Portal receives the encoding for the text of the site from the setting in the PAPZ logical device, which is in the repository. The default encoding is VTF-8, which can be used for both Western European and Asian languages. The portal sets the content for each page with the encoding specified by the logical device.
LocalStrings.properties Files and Localization 7.5.3 Localization for LDAP, Mail Adapter, and Personalization from a Device Localization text for these adapters can be found in LocalStrings.properties files in the WE_HOME/server/classes/oracle/panama/adapter directory. The sub-directories are specified. Table 7–1 LocalStrings.properties Files Details 7-4 Location Contents /ldap/LocalStrings.properties Text labels used by the LDAP adapter. /mail/LocalStrings.
8 Utilities Utilities describes the XML utilities used for management and deployment. Each section of this document presents a different topic. These sections include: ■ Section 8.1, "System Password Encryption/Decryption" ■ Section 8.2, "LoadXml" ■ Section 8.3, "Upload and Download Utilities" ■ Section 8.4, "Xslt" ■ Section 8.
System Password Encryption/Decryption 8.1 System Password Encryption/Decryption The Wireless Edition database password for the repository is stored in clear text in the System.properties file by default. The password can be encrypted by running the following tool to modify the db.connect.string: encryptPassword.sh WE_HOME/server/classes/oracle/panama/core/admin Then set the following property in the System.properties file: passwordEncrypted=true 8.1.1 Extensibility The SystemPasswordEncryptionHook.
LoadXml 8.2 LoadXml The LoadXML utility allows you to download and upload Wireless Edition repository objects as XML files. LoadXml reads from stdin and writes to stdout. All logging and error messages are written to stderr. The XML in the file you import with LoadXml must conform to the Repository XML. The upload function performs the following: 1. Checks for the objects in the repository by logical unique name. 2. Loads all dependencies. 3.
LoadXml Table 8–1 LoadXml Utility 8-4 Option Description -l usr/pwd Log on to Wireless Edition using a user name and password. If no administrator is defined in the system, the program allows any user to log on. Otherwise, the user must be an administrator to log on. -x Unload all repository data to stdout. The data can be filtered by adding these options to the -x option. -a Adapter filter. -d Logical device filter. -g Group filter. -n Agent filter. -s Service filter.
Upload and Download Utilities Option -r Description This option ensures that the repository and object cache for a running instance of Wireless Edition are current. The following is sample syntax: -r rmi://stpc250.us.oracle.com:2008/PanamaServer -c0 < bootstrap.xml rmi-host is the machine on which the RMI registry is running. port is the port at which the registry is listening. server-name is the name of the Wireless Edition instance. port and server-name can be found in the Rmi.properties file.
Xslt Note: Please make sure the -l option has been properly specified in either the upload.bat or upload.sh script file. The xmlloader.properties file specifies the mapping between the object names and their handler Java classes. The objects are specified as fully-qualified from the root, as dot-separated names. For example, the PanamaObjects property file is specified as oracle.panama.util.XMLLoader.PGRPHandler. The System.properties file has the following entries to determine behavior.
CopyObjects Xslt, which is a command-line utility, reads from standard input and writes its results to standard output. Synopsis oracle.panama.util.Xslt [stylesheet] Options The Xslt utility takes the following option: Table 8–3 Options for the Xslt Utility Option Description stylesheet The XSL stylesheet that the utility applies to the XML document. Xslt Example java oracle.panama.util.Xslt mystylesheet.xsl < myxml.xml 8.
CopyObjects Options The CopyObjects utility takes the following options: Table 8–4 Options for the CopyObjects Utility Option Description -f folder The name of an existing folder in the source system. -s source The source Wireless Edition server. Specify the source in the format: username/password@//hostname:port/servername targets The target Wireless Edition servers.
9 Recommended Settings Recommended Settings defines recommended parameters for Wireless Edition. Each section of this document presents a different topic. These sections include: ■ Section 9.1, "Mod_JServ Configuration" ■ Section 9.2, "Recommended Unix Kernel Parameters" ■ Section 9.
Mod_JServ Configuration 9.1 Mod_JServ Configuration To adjust the maximum number of socket connections that Mod_ JServ can handle simultaneously, modify the following parameter in the jserv.properties file. Table 9–1 Mod_JServ Configuration Name Value security.maxConnections 200 9.
Recommended Unix TCP Parameters Parameter Value tcp_ip_abort_interval 60000 tcp_ip_abort_cinterval 60000 tcp_keepalive_interval 120000 tcp_fin_wait_2_flush_interval 16000 tcp_conn_req_max_q 10240 tcp_conn_req_max_q0 10240 tcp_xmit_hiwat 65536 tcp_xmit_lowat 32768 tcp_recv_hiwat 65536 tcp_slow_start_initial 2 tcp_time_wait_interval 32767 Recommended Settings 9-3
Recommended Unix TCP Parameters 9-4 Oracle9i Application Server Wireless Edition Configuration Guide
10 Property Files The Wireless Edition supports system-wide extensibility using property files. Each property file stores runtime parameters and processing information for a Wireless Edition component. The Wireless Edition property files are named with the extension .properties or .xml. Each section of this document presents a different topic. These sections include: ■ Section 10.1, "Overview" ■ Section 10.2, "System.Properties" ■ Section 10.3, "Notification.properties" ■ Section 10.4, "Rmi.
Overview ■ Section 10.17, "MailAdapter.properties" ■ Section 10.18, "Master.Properties" ■ Section 10.19, "positioner.xml" ■ Section 10.20, "Geocoders.xml" ■ Section 10.21, "Mappers.xml" ■ Section 10.22, "Routers.xml" ■ Section 10.23, "Strip.properties" ■ Section 10.24, "MAgent.properties" ■ Section 10.25, "MInstances.properties" ■ Section 10.26, "Cookies.
Overview Table 10–1 Wireless Edition Properties Files Property File Description System.Properties Configuration settings for the entire Wireless Edition system. Notification.properties Email and SMS server configuration properties. Rmi.properties Identifies the server name and listening port of the Wireless Edition RMI server. oemevent.properties Properties for event logging using oemevent. Ftp.
System.Properties Property File Description Mappers.xml Specifies the possible mapper capability providers’ preferences, in descending order. Routers.xml Specifies the routing capability provider’s preference in descending order. Strip.properties Acquires and converts arbitrary Web content; reads configuration settings from the Strip.properties file. Uses the settings in the file to locate classes that process the markup tags in content.
System.Properties Key Type Editable Description instance.identifier String Y Wireless Edition server instance identifier. Must be unique among Wireless Edition server instances and should be modified if multiple instances are running. The default is instance1. locator.boot.check Boolean N If set to true, the Wireless Edition performs a bootstrap check procedure during system boot. The default is true.
System.Properties 10-6 Key Type Editable Description db.session.min Integer Y The minimum or optimal number of open database sessions. This parameter is used to tune the session pool. It can increase when necessary, but always attempts to return to the specified number of concurrent open database sessions. db.connect.minConnections Integer Y The minimum number of connections for the connection pool. The default is 5. db.connect.
System.Properties Key Type Editable Description locator.objectcache.class Class Name N The object cache implementation class. The default is oracle.panam.core.util.ObjectC acheHardWeakImpl. objectcache.check.timetolive Seconds Y The time-to-live, in seconds, of a persistent object. After this time, the Wireless Edition reconstructs the object. The default is 600. objectcache.check.interval Seconds Y The time required for the cache monitor to check the cache.
System.Properties 10-8 Key Type Editable Description log.level String list Y Log level. Can contain any of the following: error, warning, notify, or transaction. The default is "warning, error, notify". log.directory Path Y Log file directory. log.file.name File name Y Log file name pattern. The default is sys_panama.log. log.file.maxsize Integer Y Maximum number of log records in the same file. The default is 1000. log.tx.directory Path Y Transaction log file directory.
System.Properties Key Type Editable Description locator.external.hook.class Class name Y Default implementation of UserAuthenticationHook. The default is oracle.panama.core.PanamaExt ernalHookDefImpl. locator.useragent.class Class name Y Default implementation of the device recognition class. The default is oracle.panama.core.xform.User AgentImpl. locator.request.daemon .classes Class name list Y System daemons to start. See System.properties file for options. locator.request.queue.
System.Properties Key Type Editable Description locator.home.folder.sorter.hook. class String Y Value used by the oracle.panama.rt.common.Ho meFolderSorter class to sort the services in a user’s home folder. The default is USER_ SERVICES_FIRST. locator.service.visibility.hook.class Class Name Y Declares a hook to show or hide a service when Wireless Edition is started. The default is oracle.panama.rt.common.Serv iceVisibility. locator.location.service.visibility. hook.
System.Properties Key Type Editable Description locator.session.id.hook.class Class Name Y Declares the hook for generating the session ID. The default is oracle.panama.rt.common.Sessi onIdGenerator. locator.listener.registration.hook. class Class Name Y Declares the hook for the event registration listener. The default is oracle.panama.rt.common.Liste nerRegistration. locator.caller.location.hook.class Class Name Y Declares the hook which acquires the user’s current location.
System.Properties Key Type Editable Description locator.request.listener.classes Class Name Y Declares a class to implement the RequestListener interface, or oracle.panama.core.admin.Syst emLogger to perform database session logging. The event.request.begin and event.request.end, and event.after.request properties must be set to 1 to enable them locator.response.listener.classes Class Name Y Declares a class to implement the ResponseListener interface. event.before.
System.Properties Key Type Editable Description event.request.error Boolean Y Declares a request event to be "error occurs during request processing". The default is false, or disabled. Set to true to enable. event.after.request Boolean Y Declares a request event to be "request object has been released". The default is false, or disabled. Set to true to enable. event.response.error Boolean Y Declares a response event to be "error in response object. The default is false, or disabled.
System.Properties Key Type Editable Description order.services String Y The sorting order for the Wireless Edition services, folders, and bookmarks on the output devices. The default is ORDER_SEQNO_ASC, ORDER_NAME_ASC. SystemLog.enableServiceLogging Boolean Y Specifies whether Service Logging should be enabled. The default is false. SystemLog.enableSessionLogging Boolean Y Specifies whether Session Logging should be enabled. The default is false. SystemLog.logger.
Notification.properties 10.3 Notification.properties This file provides basic configuration for the notification engine. This file is in the WE_HOME/server/classes/oracle/panama/core/admin directory. Table 10–3 Parameters of the Notification.properties File Key Type Editable Description dispatcher.logical.device. String email.name N Repository name of the logical device for email. The default is EMAIL. dispatcher.logical.device. String sms.
Rmi.properties Key Type Editable Description mail.server.name String Y Send Mail Transport Protocol (SMTP) server host name if email is used as the means of notification. mail.domain String Y Optional property. The mail domain name used if required by the SMTP server. mail.from String Y Mandatory property. The "From" mail address. mail.organization String Y Optional property. The organization. mail.subject String Y Mandatory property. The mail subject. mail.content.transfer.
oemevent.properties Key Type Editable Description rmi.server.name String Y Name of the RMI server. The default is PanamaServer. The implementation is managed by the daemon: oracle.panama.core.rmi.server.ServerImpl 10.5 oemevent.properties Asynchronous notification of error information is provided using the event framework provided by Oracle Enterprise Manager.
Ftp.properties Note: You must be connected to the spatial database to use the spatial adapters. In addition, data stored in the spatial database (images and geometry) must be purchased from a third-party provider. 10.6 Ftp.properties The FTP server is a daemon that publishes the repository as an FTP file system. The repository folder is represented as an FTP directory, and repository objects are represented as FTP files.
Spatial.Properties The Ftp.properties file has the following parameters: Table 10–6 Parameters of the Ftp.properties File Key Type Editable Description ftp.server.port Integer Y TCP listening port. The default is 9100. ftp.connection.timeout Seconds Y Client connection timeout in seconds, a value of 0 is equal to "no timeout." The default is 30. ftp.charset String Y Character set used to send "Object" names, it must be a valid Java character set. The default is ISO8859_1. 10.7 Spatial.
www-server.properties 10.8 www-server.properties The probe is a daemon that displays runtime information about: ■ Log files ■ Active objects ■ Active sessions ■ Active threads The probe performs simple runtime management including: ■ Shutting down an active object instance. ■ Refreshing persistent attributes on an active object. ■ Setting the global debug flag to on or off. ■ Reloading properties for device recognition when adding a new device to a running system.
Provisioning.properties oracle.panama.core.probe.WebServer 10.9 Provisioning.properties This property file is used by the Provisioning adapter and the Personalization Portal. This file is in the WE_HOME/server/classes/oracle/panama/core/admin directory. Table 10–9 Parameters of the Provisoning.properties File Key Type Editable Description common.root Folder Name Y Common root folder for the user’s home folders. A new subfolder is created for every new user. The default is /Users Home. common.
useragent.properties 10.10 useragent.properties This property file lists the mapping from the HTTP user agent to the Wireless Edition logical device. This file is in the WE_HOME/server/classes/oracle/panama/core/admin directory. Table 10–10 Parameters of the UserAgents.properties File Key Type Editable Description default.logicaldevice Device Y Default logical device if no mapping is found. The default is WML11. [ID].useragent String Y UserAgent starting string from HTTPRequest. [ID].
EncodingSets.properties Table 10–12 Parameters of the AsynchNotification.properties File Key Type Editable Description worker.classname Class Name N Implementation class for the asynchronous notification Dequeuer. The default is oracle.panama.core.parm.asynch.AsynchNotifica tionImpl. init.pool.size Integer Y Thread pool size at startup. The default is 1. minimum.pool.size Integer Y Minimum thread pool size. The default is 1. server.listen.
LocationMark.properties This file is in the WE_HOME/server/classes/oracle/panama/core/admin directory. The IANA standard is available on the Information Sciences Institute web site. The Java encoding set names are published on the Javasoft web site. Table 10–14 Parameters of the EncodingSets.properties File Key Description [ID].iananame IANA name for the encoding set. [ID].javaname Corresponding Java name for the encoding set. 10.15 LocationMark.properties The LocationMark.
ProxyFirewall.properties Key Type Editable Description display.County String Y County of the location mark. display.State String Y State of the location mark. display.Country String Y Country of the location mark. display.PostalCodeExt String Y Postal extension code of the location mark. display.PostalCostCode String Y Postal code of the location mark. 10.16 ProxyFirewall.
MailAdapter.properties Key Type Editable Description authentication.set Boolean Y Declares whether the proxy server requires authentication. The default is false. authentication.username String Y User name if authentication is required. authentication.password String Y Password if authentication is required. 10.17 MailAdapter.properties This is the properties file for the email adapter. It is in the WE_ HOME/server/classes/oracle/panama/adapter/mail directory.
Geocoders.xml Key Type Editable Description rmiThreadPool.minThreads Integer Y Maximum number of threads in the RMI thread pool. The default is 20. rmiThreadPool.idleTimeout Integer Y Idle timeout, in minutes, for the thread. The default is 10. remoteObjects.length Integer Y Default is 1. remote.Object1.name String N Default is CacheSynchServer. remoteObject1.implementation String N Default is oracle.panama.master.CacheSyncS erver. ptginstances.
Mappers.xml Table 10–20 Parameters of the Geocoders.xml File Key Description ProviderName Provider name. ProviderImpl Class that implements the provider. the rest Additional arguments read by the provider. 10.21 Mappers.xml This XML file specifies all the possible mapper capability providers. The sequence in the XML file determines the mapper provider’s preference in descending order. It is in the WE_HOME/server/classes/oracle/panama/spatial/mapper directory.
Strip.properties with a translation table to convert a target entity into an appropriate string. It in the WE_HOME/server/classes/oracle/panama/adapter/stripper directory. Table 10–23 Parameters of the Strip.properties File Key Type Editable Description stripper.useProxy Boolean Y Enables the use of a proxy server. The default is true. stripper.proxyServe Host Name Y Name of the proxy server. The default is proxy.domain.com. stripper.proxyPort Integer Y Port number of the proxy server.
MAgent.properties oracle.panama.adapter.stripper.Strip1.targets.aring = å oracle.panama.adapter.stripper.Strip1.targets.Aring = Å oracle.panama.adapter.stripper.Strip1.targets.ouml = ö oracle.panama.adapter.stripper.Strip1.targets.Ouml = Ö oracle.panama.adapter.stripper.Strip1.targets.amp = & oracle.panama.adapter.stripper.Strip1.targets.Amp = & oracle.panama.adapter.stripper.Strip1.targets.AMP = & oracle.panama.adapter.stripper.Strip1.targets.nbsp = oracle.panama.adapter.stripper.Strip1.targets.
Cookies.properties instance name to the corresponding Magent.properties file. For example, for two instances: PTG1=oracle.panama.magent.config.Magent1 PTG2=oracle.panama.magent.config.Magent2 10.26 Cookies.properties This property file enables Wireless Edition to use cookies and sets the duration of the login session. This file is in the WE_HOME/server/classes/oracle/panama/core/admin directory. Table 10–26 Parameters of the Cookies.properties File Key Type Editable Description cookie.use.
Cookies.
Index device recognition class, 10-9 Directory application application parameters, configuring, 2-4 servers, 2-4 download utility, 8-5 A alerts, 3-2 asynchronous notification, 6-13 properties, 10-22 asynchronous request properties, 10-23 2-7 C cache implementation, 10-7 client, Wireless Edition, 1-10 configuration management using Oracle Enterprise Manager, 6-2 manual, 1-3 multiple JVM instances, 5-3 through properties files, E-mail & Directory, verification, 1-6 configuration files, 10-1 connect string
deployment scenarios, 5-2 support, 5-1 I IMAP, 2-4 installation overview, 1-2 N J notification properties, 10-15 queue, 3-3 JDBC Connection Pooling, 1-12 driver setting, 10-5 JNDI 1.2, 2-4 JVM support, multiple, 5-1 O L LDAP properties, 10-22 load balancing, 5-9 LoadXML, 1-12 utility, 8-3 location mark properties, 10-24 log listeners, creating, 10-7 logging, 4-1 levels, 10-8 server, 4-5 Service Designer, 4-5 specifying the implementing class, transaction, 4-5, 4-6, 10-8 Lotus 4.
positioner.xml, 10-27 preferences.
provisioning adapter, 1-12 upgrading, 1-7 www-server properties, 10-20 X XML, 8-1 Xslt utility, Index-4 8-6
