Oracle Audio Technologies 9i User Manual

Download

Page 1

Oracle9i Application Server Wireless Edition

Configuration Guid e

Release 1.1

May 2001 Part No. A86701-02

Page 2

Oracle9i Application Server Wireless Edition Configuration Guide, Release 1.1 Part No. A86701-02 Copyright © 2001 Oracle Corpo rat ion. All rights reserved. The Programs (which includ e bo th the software and document at ion) contain proprietary inform ation 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. Reverse engineering, disassembly, or decompilation of the Programs is prohibited.

The information contai ned in this document is subject to change without notice. If you find any problems in the document at ion , please report them to us in writing. Oracle Co rporation does not wa rrant that this document is error free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the exp res s wri tt en permission of Oracle Corporation.

If the Programs are delivered to the U.S. Government or anyone licensing or using the programs on behalf of the U.S. Government, the following no tice is applicabl e:

Restricted Rights Notice Programs delivered subject to the DOD FAR Supplement are "commercial computer software" and use, duplication, and disclo su re of t he P rog rams, including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, Programs delivered subject to the Federal Acquisition Regulations are "restricted computer software" and use, duplication, and disclosure of the Programs shall be subject to the restrictions in FAR

52.227-19, Commercial Comput er S oft ware - Restricted Rights (June, 1987). Or ac le Corporation, 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle Corporation disclaims liability for any dam ages caused by such use of the Programs.

Oracle is a registered trademark, and JDev eloper, Oracle8, Oracle8i, PL/SQL, SQL*, and SQL*Pl us are trademarks or registered trademarks of Ora cle C orporation. All other company or product na me s mentioned are used for identification purposes only and may be trademarks of their respective owners.

Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries.

Page 3

Contents

List of Tables

Send Us Your Comments................................................................................................................... xi

Preface........................................................................................................................................................... xiii

Audience................................................................................................................................................ xiii

Organization......................................................................................................................................... xiv

Related Documentation ...................................................................................................................... xiv

Documentation Accessibility .............................................................................................................. xv

1 Overview

1.1 Installation Overview ........................................................................................................... 1-2

1.2

1.2.1

1.2.2

1.2.3

1.2.4

1.3

1.4

1.5

1.6

1.6.1

1.6.2

1.7

1.8

Manual Configuration.......................................................................................................... 1-3

Configure Oracle HTTP Server and JServ.................................................................. 1-3

Configure ProxyFirewall.properties............................................................................ 1-6

Start the Oracle HTTP Server....................................................................................... 1-6

Wireless Edition Configuration Verification.............................................................. 1-6

Upgrade.................................................................................................................................. 1-7

Samples................................................................................................................................... 1-8

Web Integration Server......................................................................................................... 1-9

Wireless Edition Client....................................................................................................... 1-10

Service Designer........................................................................................................... 1-10

Web Integration Developer ........................................................................................ 1-10

OCI8 JDBC Driver............................................................................................................... 1-11

User Provisioning................................................................................................................ 1-12

iii

Page 4

1.9 Geocoding Setup.................................................................................................................. 1-12

1.10

JDBC Connection Pooling .................................................................................................. 1-12

2 FastForward

2.1 Introduction............................................................................................................................ 2-2

2.1.1

2.2

2.2.1

2.2.2

2.2.2.1

2.2.2.2

2.3

2.3.0.3

2.3.0.3.1 Configuration Through Properties Files....................................................... 2-4

2.3.0.3.2

2.3.0.3.3

2.3.0.3.4 Configuration of URL Adapter in PTG 1.1 ServiceDesigner ................... 2-13

Features............................................................................................................................ 2-2

Installation.............................................................................................................................. 2-2

System Requirements .................................................................................................... 2-2

Installation....................................................................................................................... 2-3

On Your Own Web Server and JSP Engine......................................................... 2-3

On PTG 1.1 ............................................................................................................... 2-3

Configuration......................................................................................................................... 2-4

Configuration........................................................................................................... 2-4

Configuring Mail and Directory Parameters through request.............. 2-9

Mail Configuration Class.............................................................................. 2-11

3 Alerts and SMS Request Listener

3.1 Overview................................................................................................................................. 3-1

3.2

3.2.1

3.2.2 Notification Queue......................................................................................................... 3-3

3.2.3

3.2.4

3.2.4.1

3.2.4.2

3.2.4.3

3.2.4.4

3.2.4.5

3.2.4.6

3.3

3.4

3.4.1

3.4.2

Alerts ....................................................................................................................................... 3-2

Request Queue................................................................................................................ 3-2

Email-based Alert........................................................................................................... 3-3

SMS-based Alert............................................................................................................. 3-3

SMS-C Server........................................................................................................... 3-3

SMPP Protocol......................................................................................................... 3-4

SMS Protocol............................................................................................................ 3-4

UCP Protocol............................................................................................................ 3-4

Flow-Control............................................................................................................ 3-5

Wireless Edition SMS System Account for SMS-C............................................. 3-5

SMS Request Listener............................................................................................................ 3-5

Request and Notification Queue Pool................................................................................ 3-6

Request Queue Thread Pool Size................................................................................. 3-6

Notification Queue Thread Pool Size.......................................................................... 3-6

Page 5

4 Logging

4.1 Overview ................................................................................................................................ 4-1

4.2

4.2.1

4.2.2

4.3

4.4

4.5

4.6

Database Logging.............................................................................................................. .... 4-1

Configuring the Database Logger................................................................................ 4-2

Database Table Contents............................................................................................... 4-3

Service Designer Logging .................................................................................................... 4-5

Server Logging....................................................................................................................... 4-5

Transaction Logging ............................................................................................................ 4-5

Configuring the Runtime Monitor and Management...................................................... 4-6

5 Multiple JVM Support and Load Balancing

5.1 Overview ................................................................................................................................ 5-2

5.2

5.3 Multiple Instances on the Same Machine/Oracle HTTP Server on Different Machine ......

5.4

5.5

5.5.1 Load-Balancing with Cookies....................................................................................... 5-9

5.5.2

5.6

5.6.1 Clients/Gateways Support Cookies.......................................................................... 5-10

5.6.2

5.6.3

Multiple Instances on Same Machine as Oracle HTTP Server........................................ 5-3

5-7

Multiple Instances and Oracle HTTP Server All on Different Machines...................... 5-7

Load Balancing ...................................................................................................................... 5-9

Load Balancing Through URL Rewriting................................................................... 5-9

Configuring the Personalization Portal for Load-Balancing........................................... 5-9

Clients/Gateways Do Not Support Cookies............................................................ 5-10

Sample Batch File ......................................................................................................... 5-12

6 Oracle Enterprise Manager

6.1 Overview ................................................................................................................................ 6-2

6.2

6.3

6.3.1

6.3.1.1

6.3.1.2

6.3.1.3

6.3.2

6.3.3

Prerequisites........................................................................................................................... 6-2

Configuring the Server, Client, and Middle-tier............................................................... 6-3

Configuring the Server Side ......................................................................................... 6-3

Configuring the Oracle Intelligent Agent............................................................ 6-3

Wireless Edition Data Gatherer Cartridge Installation: Unix........................... 6-4

Wireless Edition Data Gatherer Cartridge Installation: Windows.................. 6-5

Configuring the Client Side.......................................................................................... 6-6

Configuring the Middle-tier......................................................................................... 6-9

Page 6

6.4 Setting up the ptg_services.tcl File.................................................................................... 6-10

6.5

6.6

6.7

6.8

Configuration for Another Wireless Edition Instance ................................................... 6-12

Configuring the Database Logger..................................................................................... 6-13

Asynchronous Notification of Error Information........................................................... 6-13

Launching the Oracle Enterprise Manager Tools........................................................... 6-14

7 Multi-byte Character Support

7.1 Overview................................................................................................................................. 7-2

7.2

7.2.1

7.2.2

7.3

7.4

7.5 LocalStrings.properties Files and Localization ................................................................. 7-3

7.5.1

7.5.2

7.5.3 Localization for LDAP, Mail Adapter, and Personalization from a Device.......... 7-4

Multi-byte Encoding Schemes............................................................................................. 7-2

Fixed-width Encoding Schemes................................................................................... 7-2

Variable-width Encoding Schemes.............................................................................. 7-2

Setting the Multi-Byte Encoding for the Personalization Portal..................................... 7-3

Setting up a Netscape Browser to Display Multi-byte Data ........................................... 7-3

Service Designer Localization....................................................................................... 7-3

Personalization Portal Localization............................................................................. 7-3

8 Utilities

8.1 System Password Encryption/Decryption ........................................................................ 8-2

8.1.1

8.2

8.3 Upload and Download Utilities.......................................................................................... 8-5

8.4

8.5

Extensibility..................................................................................................................... 8-2

LoadXml.................................................................................................................................. 8-3

Xslt ........................................................................................................................................... 8-6

CopyObjects ........................................................................................................................... 8-7

9 Recommended Settings

9.1 Mod_JServ Configuration .................................................................................................... 9-2

9.2

9.3

Recommended Unix Kernel Parameters............................................................................ 9-2

Recommended Unix TCP Parameters................................................................................ 9-2

10 Property Files

10.1 Overview............................................................................................................................... 10-2

10.2

System.Properties................................................................................................................ 10-4

Page 7

10.3 Notification.properties ..................................................................................................... 10-15

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 ProxyFirewall.properties.................................................................................................. 10-25

10.17

10.18

10.19 positioner.xml.................................................................................................................... 10-27

10.20

10.21

10.22 Routers.xml ........................................................................................................................ 10-28

10.23

10.24

10.25 MInstances.properties....................................................................................................... 10-30

10.26

Rmi.properties ................................................................................................................... 10-16

oemevent.properties ......................................................................................................... 10-17

Ftp.properties..................................................................................................................... 10-18

Spatial.Properties............................................................................................................... 10-19

www-server.properties .................................................................................................... 10-20

Provisioning.properties.................................................................................................... 10-21

useragent.properties ......................................................................................................... 10-22

LDAP.properties................................................................................................................ 10-22

AsynchNotification.properties........................................................................................ 10-22

AsynchRequest.properties............................................................................................... 10-23

EncodingSets.properties ................................................................................................... 10-23

LocationMark.properties.................................................................................................. 10-24

MailAdapter.properties.................................................................................................... 10-26

Master.Properties .............................................................................................................. 10-26

Geocoders.xml ................................................................................................................... 10-27

Mappers.xml ...................................................................................................................... 10-28

Strip.properties.................................................................................................................. 10-28

MAgent.properties............................................................................................................ 10-30

Cookies.properties............................................................................................................. 10-31

Index

vii

Page 8

viii

Page 9

List of Tables

2–1 Mail parameters..................................................................................................................... 2-5

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

Directory parameters............................................................................................................ 2-7

Mail parameters passed through request....................................................................... 2-9

Directory parameters passed through request............................................................ 2-10

Mail configuration class ..................................................................................................... 2-11

Contents of the ptg_session_log Table............................................................................... 4-3

Contents of the ptg_service_log Table ............................................................................... 4-4

Server Error Information ...................................................................................................... 4-5

Property File Settings............................................................................................................ 5-6

ptg_services.tcl Parameters................................................................................................ 6-11

Properties of the oemevents.properties File.................................................................... 6-13

LocalStrings.properties Files Details .................................................................................. 7-4

LoadXml Utility..................................................................................................................... 8-4

Behaviors for the XML Loader in the Systems.property File ......................................... 8-6

Options for the Xslt Utility................................................................................................... 8-7

Options for the CopyObjects Utility................................................................................... 8-8

Mod_JServ Configuration.................................................................................................... 9-2

Recommended Unix Kernel Parameters............................................................................ 9-2

Recommended Solaris TCP Parameters............................................................................. 9-2

Wireless Edition Properties Files ...................................................................................... 10-3

Parameters for the System.properties File....................................................................... 10-4

Parameters of the Notification.properties File.............................................................. 10-15

Parameters of the Rmi.properties File............................................................................ 10-16

Parameters of the oemevents.properties File................................................................ 10-17

Parameters of the Ftp.properties File ............................................................................. 10-19

Parameters of the spatial.properties File........................................................................ 10-19

Parameters of the www-server.properties File............................................................. 10-20

Parameters of the Provisoning.properties File.............................................................. 10-21

Parameters of the UserAgents.properties File .............................................................. 10-22

Parameters of the LDAP.properties File........................................................................ 10-22

Parameters of the AsynchNotification.properties File................................................. 10-23

Parameters of the AsynchRequest.properties File........................................................ 10-23

Parameters of the EncodingSets.properties File ........................................................... 10-24

Parameters of the LocationMark.properties File.......................................................... 10-24

Parameters of the ProxyFirewall.properties File .......................................................... 10-25

Parameters of the MailAdapter.properties File ............................................................ 10-26

Parameters of the Master.properties File....................................................................... 10-26

Parameters of the positioner.xml File............................................................................. 10-27

Parameters of the Geocoders.xml File............................................................................ 10-28

Page 10

10–21 Parameters of the mappers.xml File ............................................................................... 10-28

10–22 10–23 10–24 10–25 10–26

Parameters of the routers.xml File.................................................................................. 10-28

Parameters of the Strip.properties File........................................................................... 10-29

Strip Processing Classes.................................................................................................... 10-29

Parameters of the MAgent.properties File..................................................................... 10-30

Parameters of the Cookies.properties File..................................................................... 10-31

Page 11

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.

■ Did you find any errors?

■ Is the information clearly presented?

■ Do you need more information? If so, where?

■ Are the examples correct? Do you need more examples?

■ What features did you like most?

If you find any errors or have any other suggestions for improvement, please indicate the document title and part number, and the chapter, section, and page number (if available). You can send comments to us in the following ways:

■ Electronic mail: iasdocs_us@oracle.com

■ Postal service:

Oracle Corporation Oracle Mobile and Wireless Products 500 Oracle Parkway, Mailstop 4OP6 Redwood Shores, California 94065 USA

If you would like a reply, please give your name, address, telephone number, and (optionally) electronic mail address.

If you have problems with the software, please contact your local Oracle Support Services.

Page 12

xii

Page 13

Audience

Preface

The Oracle9i Application Server Wireless Edition Configuration Guide discusses how to configure Wireless Edition.

This Preface contains these topics:

Audience Organization Related Documenta t ion Documentation Accessibility

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. This document includes the following to pics:

Overview Setting up Wireless Edition Setting up Oracle Enterprise Manager Settings, Utilities, and Properties To use this document, you need a general knowledge of application servers, Web

servers, and database-driven Web sites, wireless technologies, and familiarity with the technologies and programming languages used in middle-tier environments.

xiii

Page 14

Organization

This document contains:

Chapter 1, "Overview" Overview of post-installation configuration

Chapter 2, "FastForward" Configure Mail and LDAP applications.

procedures.

Chapter 3, "Alerts and SMS

Request Listener"

Chapter 4, "Logging" Configuring the logging capabilities of Wireless

Chapter 5, "Multiple JVM

Support and Load Balancing"

Chapter 6, "Oracle Enterprise

Manager"

Chapter 7, "Multi-byte

Character Support"

Chapter 8, "Utilities" Utilities, such as Password

Chapter 9, "Recommended

Settings"

Chapter 10, "Property Files" Properties files and their parameters.

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.9, "Geocoding Setup"

■ Section 1.10, "JDBC Connection Pooling"

Overview 1-1

Page 18

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\pan ama (Windows) /private/ias102 10/panama (UNIX)

Replace "WE_HOME" with the fully-qualified directory path.

■ ORACLE_HOME is the directory in which Or acle9 i

Application Server is installed.

1.1 Installation Overview

The Oracle9i Application Server installation includes three options:

■ Oracle HTTP Server

■ Standard Edition

■ Enterprise Edition

Wireless Edition is installed as part of each of these options. The Oracle9i Application

Server Installation Guide discusses each option, and discusses the installation ste p s

specific to Wireless Edition. The Installation Guide defines Wireless Edition and

Oracle HTTP Server hardware and software requirements, preinstallation tasks

(setting environment variables), port numbers, starting and stopping the Oracle

HTTP Server, and the Wireless Edition client configuration.

For a new installation of Wireless Edition, follow the steps in this document starting

with the manual configuration in Section 1.2. If you have a previous release of

Wireless Edition installed see Section 1.3.

Important: Wireless Edition is not properly configured until the

manual configuration steps are completed in Section 1.2.

1-2 Oracle9i Application Server Wireless Edition Configuration Guide

Page 19

1.2 Manual Configuration

After installation, perform the manual conf iguration 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.conf file. The httpd.conf file is in the ORACLE_

HOME/Apache/Apache/conf directory.

a. Create an alias for this release of the Personalizatio n Portal. This is needed

so that the application server can find the http://hostname/portal/ L ogin.jsp URL. Include the following in the Alias section:

Alias /portal/ "WE_HOME/server/p ortal/"

Manual Configurat ion

b. To access a previous release of the Personalization Portal, in addition to this

release, create an alias. This allows the application server to find the http://hostname/papz/login.jsp URL. Include the following in the Alias section:

Alias /papz/ "W E_HOME/server/pap z/"

c. Create an alias for the Javadoc directory. Include the following in the Alias

section. This step is optional.

Alias /ptgdoc/ "WE_HOME/doc/java doc/"

2. Configure the jserv.conf file. The jserv.conf file is in the ORACLE_

HOME/Apache/Jserv/etc directory. In the ApJServMount section, add the Wireless Edition specific mount point:

ApJServMount /p tg /root

3. Configure the jserv.properties file. The jserv.properties file is in the ORACLE_

HOME/Apache/Jserv/etc directory.

Overview 1-3

Page 20

Manual Configuration

Verify that the Java Virtual Machine is version 1.2.2. For example:

wrapper.bin= <O RACLE_HOME>/Apach e/jdk/bin/java.e xe

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.classpa th=<WE_HOME>\serv er\classes wrapper.classpa th=<WE_HOME>\lib\ panama.zip wrapper.classpa th=<WE_HOME>\lib\ panama_core.zip wrapper.classpa th=<WE_HOME>\lib\ panama_portal.zi p wrapper.classpa th=<WE_HOME>\lib\ panama_papz.zip wrapper.classpa th=<WE_HOME>\lib\ client.zip wrapper.classpa th=<WE_HOME>\lib\ server.zip wrapper.classpa th=<WE_HOME>\lib\ caboshare-opt.zi p wrapper.classpa th=<WE_HOME>\lib\ marlin-opt.zip wrapper.classpa th=<WE_HOME>\lib\ ocelot-opt.zip wrapper.classpa th=<WE_HOME>\lib\ share-opt-1_1_7. zip wrapper.classpa th=<WE_HOME>\lib\ tecate-opt.zip wrapper.classpa th=<WE_HOME>\lib\ regexp.jar wrapper.classpa th=<WE_HOME>\lib\ sax2.jar wrapper.classpa th=<WE_HOME>\lib\ activation.jar wrapper.classpa th=<WE_HOME>\lib\ mail.jar wrapper.classpa th=<WE_HOME>\lib\ ldap.jar wrapper.classpa th=<WE_HOME>\lib\ ldapbp.jar wrapper.classpa th=<WE_HOME>\lib\ providerutil.jar wrapper.classpa th=<WE_HOME>\lib\ sdoapi101.jar wrapper.classpa th=<WE_HOME>\lib\ sdovis.jar wrapper.classpa th=<WE_HOME>\lib\ MapQuestX.jar wrapper.classpa th=<WE_HOME>\lib\ MQJavaCore.jar wrapper.classpa th=<WE_HOME>\lib\ RoutingJServerCl ient.jar wrapper.classpa th=<WE_HOME>\lib\ jai_codec.jar wrapper.classpa th=<WE_HOME>\lib\ jai_core.jar wrapper.classpa th=<WE_HOME>\lib\ jpeg_codec.jar wrapper.classpa th=<WE_HOME>\lib\ ordimimg.jar

Note: Perform the following step before the Oracle HTTP Server is

started. The Personalization Portal requires this step for generating the correct image.

1-4 Oracle9i Application Server Wireless Edition Configuration Guide

Page 21

Manual Configurat ion

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=DIS PLAY=:0.0

From the X server host machine (x_server_host_name in the following example) run the following command:

xhost + <x_serv er_host_name>

b. If the X server runs on a different machine (x_server_host_name in the

following example) than the Wireles s Edition server, set the DISPLAY environment variable in the jserv.properties file as follows:

wrapper.env=DIS PLAY=<x_server_ho st_name>:0.0

From the X server host machine, run the following command using the Wireless Edition host (wireless_edition_host_name in the following example):

xhost + <wirele ss_edition_host_n ame>

Note: For both cases, remain logged into the Con sole while the

xhost commands are executed. Otherwise, properties set through the xhost command may be lost and images may not be displayed properly in the Personalization Portal.

Configure the zone.properties file. The zone.properties file is in the ORACLE_ HOME/Apache/Jserv/etc directory.

a. In the List of Repositories section, add the Wireless Edition specific

repository to the existing repository line with a comma (,) separator: For Windows:

repositories=<O RACLE_HOME>\Apach e\Jserv\servlets ,<WE_ HOME>\serverpor tal,<WE_HOME>\ser ver\papz

For UNIX:

repositories=<O RACLE_HOME>/Apach e/Jserv/servlets ,<WE_ HOME>/server/po rtal,<WE_HOME>/se rver/papz

Overview 1-5

Page 22

Manual Configuration

b. In the Startup Servlets section, add the Wireless Edition specific servlets:

servlets.startu p=oracle.panama.P armImpl

In the Servlet Aliases section, add the Wireless Edition specific servlets:

servlet.rm.code =oracle.panama.Pa rmImpl

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. Specify the correct host in http.proxy.host. For example:

http.proxy.host =www-proxy.us.ora cle.com

3. Specify the correct port in http.proxy.port. For example:

http.proxy.port =80

Note: For a list of property files provided by Wireless Edition, see

Chapter 10.

1.2.3 Start the Oracle HTTP Server

To start the Oracle HTTP Server see the instructions in the Oracle9i Application Server

Installation Guide.

1.2.4 Wireless Edition Configuration Verification

After installation, you can verify that individua l Wireless Edition components are

properly configured using a desktop browser:

1. Test whether the Personalization Portal is working properly by accessing the

following URL:

http://host_nam e.domain:7777/por tal/Login.jsp

1-6 Oracle9i Application Server Wireless Edition Configuration Guide

Page 23

2. Run the Wireless Edition Request Manager by accessing the following URL:

1.3 Upgrade

To upgrade a previous release of Wireless Edition (Portal-to-Go) including release

1.0.2.1.0, 1.0.2.2.0, or 1.0.2.3.0 perform the following steps:

1. Stop the Oracle HTTP Server. See the Oracle9i Application Server Installat ion

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.

http://host_nam e.domain:7777/ptg /rm

The login page should appear. The page prompts you to enter a user name and a password.

Important: Yo u can log in using “Administrator” as the user name

and “manager” as the password. These are the default settings.

Guide for instructions.

2. Back up the entire "panama" directory. For example, copy the entire "panama"

directory to a different location.

3. Back up the repository using an Oracle backup tool.

Important: The Wireless Edition installation in the following step

upgrades the database schema and migrates the existing data.

4. Run the Oracle9i Application Server installation.

5. Follow the manual configuration steps in Section 1.2.

6. Restart the Oracle HTTP Server. See the Oracle9i Application Server Installation

Guide for instructions.

Overview 1-7

Page 24

Samples

1.4 Samples

You can in stall 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:

3. Run the following:

WE_HOME\sample (Wi ndows) WE_HOME/sample (UN IX)

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 Administrato r/manager

upload.bat samp les.xml (Windows) upload.sh samples. xml (UNIX)

Add the following entry in the jserv.properties file. This must be added before the Oracle HTTP Server is started.

wrapper.classpa th=WE_HOME\sample (Windows) wrapper.classpa th=WE_HOME/sample (UNIX)

Note: All the sample Java source and class files are stored in the

"sample" directory. Include the sample directory entry in the jserv.properties file so that JServ can locate the sample class files.

Restart the Oracle HTTP Server. See the Oracle 9i Application Serve r Installation

Guide for instructions.

You s hould see the sample adapters an d sample services in the \master\S amples

folder using the Service Designer or the Personalization Portal.

Note: Directory Service in the samples directory does not run

unless the Oracle Internet Directory is installed. Contact content providers before running any sample service in the YP and Router directories.

1-8 Oracle9i Application Server Wireless Edition Configuration Guide

Page 25

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

For UNIX

server.sh &

The Web Integration Server can also be run as a service on Windows.

2. From a browser, go to the Web Integration Server URL:

http://host_nam e.domain:5555

password manage. These are the default settings.

Web Integration Server

4. Select Settings. The server settings appear. Click Edit.

5. Enter the Proxy (HTTP) and Secure Proxy (HTTPS) settings for your

environment.

6. Click Submit.

7. Click Logout.

Note: Please make sure the max heap size has been specified for

the Web Integration Server. To increase the max heap size in the Web Integration Server startup script, add the -mx option.

The Web Integration Developer, the development environment for creating and testing Web Integration services written in Web Interface Definition Language (WIDL), is installed as part of the Wireless Edition client. For more information, see

Section 1.6.

Overview 1-9

Page 26

Wireless Edition Client

1.6 Wireless Edition Client

The Wire less Edition client runs only on the Windows platform. The client

installation consists of the following:

■ Service Designer

■ Web Integra tion 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. The Service Designer provides a tree view of

the Wireless Edition repository. This tree displays Wireless Edition objects classes,

such as adapters and transformers, as folders or branch nodes. It shows instances of

those classes as objects or leaf nodes.

The Service Designer is installed during the Wireless Edition client installation. See

the Oracle 9i Application Server Wireless Edition Implementation Guid e for information

on using this tool.

1.6.2 Web Integration Developer

Web Integra tion Developer is a development environment for creating and testing

Web Integra tion services written in We b Interface Definition Language (WIDL). The

Web Integra tion Developer includes tools for publishing WIDL services for the Web

Integration Server.

The Web Integra tion Developer is installed during the Wireless Edition client

installation. For installation instructions, see the Oracle 9i Application Server

Installation Guide.

Note: The Web Integration Developer includes its own Java

Virtual Machine (JVM). It does not require any Java setup.

To configure the Web Integration Developer:

1. Run the Web Integration Developer from the Windows Programs menu. Select

Programs, Oracle for Windows, Wireless Edition, and Web Integration Developer.

1-10 Oracle9i Application Server Wireless Edition Configuration Guide

Page 27

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. Additionally, this driver is required if the Oracle Parallel Server option is used.

To configure Wireless Edition to use the Oracle OCI8 driver:

1. Verify that ORACLE_HOME is the directory under which Wireless Edition has

been installed.

a. On Windows: Modify the jserv.properties file to include the PATH of the

directory where the OCI library (ocijdbc8.dll) is installed. The default is ORACLE_HOME\bin.

wrapper.path=<O RACLE_HOME>\bin

OCI8 JDBC Driver

On UNIX: Verify that the LD_LIBRARY_PATH environment variable

includes the directory where the OCI libraries (libocijdbc8.so and libocijdbc8_g.so) are installed. The default is ORACLE_HOME/lib.

2. Modify the System.properties file to change the driver and the connect string

settings.

db.connect.stri ng=%WE_REPOSITORY _USERNAME%/%WE_R EPOSITORY_USER_ PW%@(descriptio n=(address=(host= %WE_REPOSITORY_ HOST%)(protocol =tcp)(port=%WE_RE POSITORY_PORT%)) (connect_data=(si d=%WE_ REPOSITORY_SID% ))) db.driver=V8

Overview 1-11

Page 28

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. This utility enables you to create and update user information. For more information on the L oa dXML utility, see Section 8.2.

3. Use the Wireless Edition data model API to programmatically create users. A

model example is provided in the WE_HOME\sample\mod el di rectory. Also, see the Javadoc and Oracle9i Application Server Wireless Edition Developer’s Guide for more information on the data model API.

1.9 Geocoding Setup

Wireless Edition provides basic geocoding through the provider MapInfo . To

expand the geocoding capability to includ e other providers, see the Oracle9i

Application Server Wireless Edition Implementation Guide. Additionally , if a proxy

server is used to access an external web site (including the MapInfo provider) from

Wireless Edition, configure the ProxyFirewall.properties file:

1. Set http.use.proxy to true. For example:

http.use.proxy= true

Specify the correct host in http.proxy.host. For example:

http.proxy.host =www-proxy.us.ora cle.com

3. Specify the correct port in http.proxy.port. For example:

http.proxy.port =80

1.10 JDBC Connection Pooling

Pooling for JDBC connections im proves resource utilization and avoids connection

establishment overhead. A set of configurable parameters for this connection pool is

provided in the System.properties file. For more information see Section 10.2.

1-12 Oracle9i Application Server Wireless Edition Configuration Guide

Page 29

JDBC Connection Pooling

Connection pooling under Wireless Edition session managem en t 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 f or the connectio n pool db.connect.minC onnections=5

#Maximum number of connections f or the connectio n pool db.connect.maxC onnections=100

#Incremental al location of new c onnections to th e connection pool db.connect.incC onnections=1

#Time interval (in seconds) for the watchdog to find and release unused #connections to the connection p ool repository.sess ion.check.interva l=1

Note: To control the maximum idle time for any database

connection, configure it through the Oracle data server.

Overview 1-13

Page 30

JDBC Connection Pooling

1-14 Oracle9i Application Server Wireless Edition Configuration Guide

Page 31

FastForward

This document describes the FastForward Email and Directory applications, their

installation, and configuration

Each section of this document presents a different topic. These sections include:

■ Introduction

■ Installation

■ Configuration

FastForward 2-1

Page 32

Introducti on

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 a ny mobile

device. Mobile email will drive productivity within your enterprise, allo wing

employees to stay in touch while away from the office.

2.1.1 Features

The FastForward Email and Directory applications include implementation of the

following features:

■ General mobile device support, including: WAP phones, Palms, PocketPCs, and

RIM pagers with browser support.

■ Flexible deployment options depending on your business needs.

■ Support for IMAP and POP3 protocols (including MS Exchange 5.5 and later

and Lotus Domino 4.5 and later).

■ Integrated corporate email with LDAP employee lookup.

■ Standalone LDAP employee lookup.

2.2 Installation

2.2.1 System Requirements

This section is only applicable if the Mail and Directory applications are not run

with Oracle 9iAS Wireless Edition.

Common

■ Sun’s JDK 1.2 or JRE 1.2

■ Apache 1.3.9

■ JSP engine that supports Servlet API 2.0 and JSP 1.0. The product is tested to

run on JServ, ServletExec 2.2, and JRun 3.0.

■ Optional: HTTPS or VPN for security purposes.

■ Oracle 9iAS Wireless Edition for non-ho sting customers.

2-2 Oracle9i Application Server Wireless Edition Configuration Guide

Page 33

Mail

■ JavaMail API 1.2 from Sun Microsystems

■ JavaBeans Activation Framework extension (JAF) from Sun Microsystems

2.2.2 Installation

2.2.2.1 On Your Own Web Serve r and JSP Engi ne

Ensure you have a working web server and a JSP engine conf igured 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 <JDK 1.2>/jre/lib/rt.jar and <JDK 1.2>/lib/tools.jar is in the classpath. Configure the JSP engine to point to the JSP files in the JSP directory. Mail.jsp is the main JSP for the Mail Application, and LDAP.jsp is the main JSP for

the Directory Application.

Installation

2.2.2.2 On PTG 1.1

PTG 1.1 already includes Apache web server and JServ 1.1.1. Configure JServ so that the jar files are in its classpath. Go to <JServ1.1.1

directory>/conf/jserv.properties, then put the following lines before all other classpaths:

■ wrapper.classpath=<ompim properties directory>

■ wrapper.classpath=<ompim lib directory>/ompim.jar

Also ensure that the JavaMail and LDAP jar files are in wrapper.classpath. Configure Apache so that the JSP files are on the document root on Apache.

Mail.jsp is the main JSP for the Mail Application, and LDAP.jsp is the main JSP for the Directory Application.

Create a new service in PTG ServiceDesigner to point to the URL of the applications. See the Configuration of U RL Adapter in PTG 1.1 ServiceDesigner for more information.

FastForward 2-3

Page 34

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 Re lease 5

2.3.0.3.1 Configuration Through Properties Files

For the Mail application, configure OracleMobileEmail.properties (in the

oracle/panama/module/communicate/mail directory).

For the Directory Application, configure OracleMobileLDAP.properties (in the

oracle/panama/module/communicate/ldap directory).

2-4 Oracle9i Application Server Wireless Edition Configuration Guide

Page 35

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 <install>/properties directories in the classpath of the JSP engine.

Note: Parameters and values in properties file is case sensitive.

WARNING: Ensure you are using the proper format for your

UNIX or Windows platforms. For example: UNIX format mail.logger=/tmp/mail.log Windows format mail.logger=d:\\tmp\\mail.log

For the Mail application, you must configure the following parameters:

Configuration

Table 2–1 Mail parameters

mail.service Mail service supported by the mail server. Currently

supported services are "IMAP" or "POP3". Default is IMAP.

mail.server.name Full hostname of the mail serv er. mail.server.port Port number of the Mail server on the host. Default

for IMAP is 143. Default for POP3 is 110.

mail.smtp.server.name Full hostname of the SMTP server. mail.smtp.server.port Port number of the SMTP server on the host. Default

for IMAP is 25.

mail.smtp.server.login Returns the login name of the SMTP server. If login

for SMTP is not required, this method should return a null or empty string (""), otherwise, the value will be used for SMTP login.

mail.folder.inbox Name of the Inbox folder on the mail server. Default

is "INBOX". This property is optional.

FastForward 2-5

Page 36

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.setsize Maximum number of messages to fetch for one

request. This is the maximum number of messages returned for one request. For example, if a folder has 300 messages, only the first 200 w ill be returned at the first request.

mail.server.connect.timeout Connection timeout in milliseconds. Default is 2000.

mail.config.class The configuration class. Users can provide their own

configuration classes, allowing them to do more advanced configuration, for example, select a mail server host name based on username. Default is

oracle.panama.module.communicate.mail.util.Conf ig which is shipped with the OracleMobile Mail

application.

mail.directoryEnabled Enables/disables directory access from email. If

enabled, when users are composing emails, they can go to directories to look for email addresses. Values can be "true" or "false". Default is "false".

ldap.designer.path Used when directory is enabled. Check the

"mail.directoryEnabled" parameter. When the application is running on PTG, but not

studio, then the path to the application specified in ServiceDesigner Service Trees is needed.

For example, if LDAP is the service defined for the Directory Application, and it is put in a fold er called Apps under Service Trees, then the path should be /Apps/Ldap.

2-6 Oracle9i Application Server Wireless Edition Configuration Guide

Page 37

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.log Determines whether logging is turn on or off. Values

can be "true" or "false". Default is "true".

ldap.logger Full pathname of the log file. ldap.queries Two default queries are shipped with the

OracleMobile Directory Application:

One searches for a person on the common name LDAP attribute.

The second searches for a person on the first name and the last name LDAP attribute. For details about LDAP query syntax, see the LDAP docu mentation.

ldap.links

Hotlink is a mechanism that enable s yo u to cr ea te hyperlinks on the attribut e in the result list. For details about Hotlink, see the LDAP documentation.

ldap.labelMultipleMatch Sets the values that appear in the results list from the

query, when a query returns more than one line. Note that the values must be in the query. The default is givenname, surname, and title.

ldap.labelMultipleMatch Contains givenname, surname, and title ldap.maxResultCount Maximum results returned from a query. Default is

1000.

ldap.enableLogin Determines if LDAP login is required for a user. The

value is either "true" or "false". Default is "false".

FastForward 2-7

Page 38

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.phoneAttribute Name of the telephone number attribute of a person

in the LDAP schema.

ldap.maxRecPage Maximum results displayed on a screen. Defa ult is 9.

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.

ldap.designer.path Used when directory is enabled. Check the

"mail.directoryEnabled" parameter. When the application is running on PTG, but not

studio, then the path to the application specified in ServiceDesigner Service Trees is needed.

For example, if LDAP is the service defined for the Directory Application, and it is put in a fold er called Apps under Service Trees, then the path should be /Apps/Ldap.

2-8 Oracle9i Application Server Wireless Edition Configuration Guide

Page 39

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 pas sed 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.

For example, if you want to use the properties file myconfig.properties, put it into the request CONFIG_ FILE=myconfig, and ensure the file is on the classpath.

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.

MAIL_SERVICE Definition, possible values, and default values are the same

as the "mail.service" in the properties file.

MAILHOST Definition, possible values, and default values are the same

as the "mail.server.name" in the properties file.

MAILPORT Definition, possible values, and default values are the same

as the "mail.server.po rt" in the properties file.

SMTPHOST Definition, possible values, and default values are the same

as the "mail.smtp.server.name" in the properties file.

SMTPPORT Definition, possible values, and default values are the same

as the "mail.smtp.server.port" in the properties file.

SMTP_LOGIN Definition, possible values, and default values are the same

as the "mail.smtp.server.login" in the properties file.

SENDER_DOMAIN Definition, possible values, and default values are the same

as the "mail.smtp.domain" in the properties file.

INBOX Definition, possible values, and default values are the same

as the "mail.folder.inbox" in the properties file.

SENT Definition, possible values, and default values are the same

as the "mail.folder.sent" in the properties file.

FastForward 2-9

Page 40

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.

TIMEOUT Definition, possible values, and default values are the same

as the "mail.server.con nect.timeout" in the properties file.

CONFIG Definition, possible values, and default values are the same

as the "mail.config.class" in the properties file.

DIR_ENABLED Definition, possible values, and default values are the same

as the "mail.directoryEnabled" in the properties file. USERNAME Username of the user for transparent login. PASSWORD Password of the user for transparent login. If USERNAME is

not sent at the same time, this password will be ignored, and

the user must login. For example, if you want to bypass the

request:

http://myURL/Mail.jsp?USERNAME=myusername&PASS

WORD=mypassword

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 strings. Also, if a parameter is defined through request, it will override the corresponding parameter in the properties file.

The following Directory parameters can be passed through request:

Table 2–4 Directory parameters passed through request

LDAPHOST

LDAPPORT

2-10 Oracle9i Application Server Wireless Edition Configuration Guide

Definition, possible values, and default values are the same as the

"ldap.host" in the properties file.

Definition, possible values, and default values are the same as the

"ldap.port" in the properties file.

Page 41

Configuration

PTG_VERSION

STUDIO

Definition, possible values, and default values are the same as the

"oracle.panama.version" in th e pr opert ies file.

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. Also, if a parameter is defined through request, it will override the corresponding parameter in the properties file.

2.3.0.3.3 Mail Configuration Class

For Mail configuration, you can define your own configuration class to do more advanced configuration. For example, select mail server host name based on runtime information.

To do this, you must define a class which implements

oracle.panama.module.communicate.mail.util.IConfig, and in package oracle.panama.module.communicate.mail.util. In the class, you can define the

following methods:

Table 2–5 Mail configuration class

String getMailService(Object o) Returns the mail service. The current

supported services are IMAP and POP3. String getDomain(Object o) Returns the default mail domain. String getServerName(Object o) Returns the mail server host name. int getServerPort(Object o) Returns the mail server port number. Make

sure it is a valid number. String

Returns the SMTP server host name. getSMTPServerName(Object o)

int getSMTPServerPort(Object o) Returns the SMTP server port number. Make

sure it is a valid number. String getSMPTLogin(Object o) Returns the login name of the SMTP server.

If login for SMTP is not required, this method

should return null or empty string (""),

otherwise, the value will be used for SMTP

FastForward 2-11

Page 42

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

Returns the Inbox folder name.

(Object o) String getSentFolderName

Returns the Sent folder name.

(Object o) boolean isLogging(Object o) Indicates if logging is enabled. String getLogfile (Object o) Returns the full path of the log file. String getTimeout (Object o) Returns the con nection timeout in

milliseconds.

In the OracleMobileEmail.properties file, change the mail.config.class property to be the class you define.

The input is an object. The default behavior is not to pass anything. You can cha nge it to pass information such as a string (username for example), or a hashtable containing more information.

If you do not want to implement all of the methods, you can extend from oracle.panama.module.communicate.mail.util.Config. You can choose to override methods, but the rest will be the default implementations. The default is to ignore the username and pick up the information from the properties file.

Refer to the Javadoc IConfig.html and the Java interface in the doc directory of the install.

2-12 Oracle9i Application Server Wireless Edition Configuration Guide

Page 43

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 i n 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.

You can create a new Master Service in an existing folder or create a new folder and then create the Master Service in that folder. In the example, the Master Service "Mail" is created under the folder "Admin".

IMPORTANT: Oracle Corporation recommends that the service not

to be created at the root level directly under Master Service.

3. Choose URL Adapter for the new service.

4. In the "Input Parameters" tab, under "Value", put the URL of the application.

5. Create a service alias (for example: http://pc1.company.com/mail.jsp) for the

new service under the "Service Trees" folder. The alias should point to the Master Service created. In the example below, the service alias "Mail" is created under the "Apps" folder under "Service Trees". Oracle Corporation also recommends that the alias not be created at the level directly under Service Trees. The alias should point to /master/Admin/Mail.

6. Create an alias for users that points to the service alias created in the previous

step. In the example below, the service alias "Mail" is created under the "Administrator" folder located under "Service Trees". This means the service is available for the user "Administrator".

FastForward 2-13

Page 44

Configuration

Figure 2–1 Service Designer Window

Now you can use e-mail.

2-14 Oracle9i Application Server Wireless Edition Configuration Guide

Page 45

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"

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\pan ama (Windows) /private/ias102 10/panama (UNIX)

Replace "WE_HOME" with the fully-qualified directory path.

3.1 Overview

Alerts, in the Wireless Edition, are time-based scheduled services. Alerts are executed when the scheduled time expires. The result, if any, after the service is executed, is delivered to the end user at the default alert address . The Wireless Edition can accept either email or phone numbers as the alert address. If the default alert address is an email address , the result is delivered as an email message. If the default alert address is a phone number, the result is delivered as a SMS. The alert

Alerts and SMS Request Listener 3-1

Page 46

Alerts

3.2 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. [[Is this still true?]]

Alerts, which are time-based scheduled services, are placed in the request queue when they are created. The result of the alert execution, if any, is placed in the notification queue. The alert functionality in the Wireless Edition requir es the installation of the Oracle8i JOB and AQ options.

Important: The aq_tm_processes parameter in the init.ora file

must be set to at least "2" for the processing of asynchronous alerts in Wireless Edition.

3.2.1 Requ es t Qu eu e

The request queue stores all the alerts to be executed. The Wireless Edition processes an alert as follows:

1. An alert is created or updated with a start date and a specified interval when

the user creates a time-based scheduled service. The alert is placed in the request queue.

2. When the specified time expires, the alert is activated and executed. The result,

if any, is placed in the notification queue with the alert creator’s default alert address. The alert with an updated next execution time is placed back in the request queue.

3. If the alert fails to be executed for any reason, the alert is not placed back in the

request queue. It can only be reactivated by updating the start date through the Personalization Portal.

3-2 Oracle9i Application Server Wireless Edition Configuration Guide

Page 47

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 q ueue. 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.3 Email-based Alert

If the result of a delivered alert is an email message, set the following entries in the Notification.properties file in the WE_ HOME\server\classes\oracle\panama\core\admin directory:

# The smtp serv er hostname, mand atory <hostname> mail.server.nam e= # The mail doma in name, set if S MTP server requi res this <domainn ame> mail.domain= # The from mail address, mandato ry <email addres s> mail.from= # The organizat ion, optional <st ring> mail.organizati on= # The default m ail subject, mand atory <string> mail.subject= # The Content-T ransfer-Encoding, mandatory <stri ng> mail.content.tr ansfer.encoding=

Alerts

3.2.4 SMS-based Alert

If the result of a delivered alert is a SMS message, configure the Notification.properties file in the WE_ HOME\server\classes\oracle\panama\core\admin directory.

3.2.4.1 SMS-C Server

Configure the following entries to specify the host on w hich the SMS-C is running:

# the hostname on which the SMS- C is running sms.server.name = # the port on the sms.server.name f rom which the SMS-C i s listening the incom ing SMS-message sms.server.port =

Generally, the Wireless Edition uses direct TCP/IP communication to the SMS-C server when sending the SMS message. If the UCP protocol is selected, the Wireless

Alerts and SMS Request Listener 3-3

Page 48

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.clas s=oracle.panama.u til.sms.SmsSMPPD river

Set the following entries with the appropriate values:

# The SMPP syst em id <string> # sms.smpp.system .id= # # The SMPP syst em type <string> # sms.smpp.system .type= # # The SMPP clie nt password <stri ng> # sms.smpp.system .password=

3.2.4.3 SMS Protocol

When sending the SMS message, the Wireless Edition can use either the Universal Computer Protocol (eith er operation 01 or operation 51 command set), or the Short Message Peer-to-Peer (SMPP) protocol to communicate with the SMS-C.

3.2.4.4 UCP Protocol

If the UCP protocol is used to communicate between the Wireless Edition and SMS-C when sending the notification message, set:

sms.driver.clas s=oracle.panama.u til.sms.SmsUCPDr iver

Also, specify which command se t to use:

sms.ucptype=01 (for operation 01 command set) sms.ucptype=51 (for operation 51 command set)

3-4 Oracle9i Application Server Wireless Edition Configuration Guide

Page 49

3.2.4.5 Flow-Control

Configure the following entries for the SMS-control:

# The max numbe r of SMS chunks p er message. <int > # sms.message.max chunks= # # The maximum n umber of bytes pe r message. <int> # sms.message.max size=

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 Edit ion SMS System Ac count Id sms.account.id # The correspon ding password sms.account.pas sword

3.3 SMS Request Listener

SMS Request Listener

Note: The followin g configuration is not required if the SMS

Request Listener will not be provided to the end user.

The SMS Request Listener allows the invocation of any Wireless Edition service using a SMS message. The SMS Request Listener processes the SMS-based service invocation request and returns the result, if any, as a SMS message by performing the following:

1. Authenticate the user by finding the alert address with the actual phone

number.

2. Invoke the service.

3. Place the result, if any, after invoking the service, in the notification queue.

Alerts and SMS Request Listener 3-5

Page 50

Request and Not ifi cati on Que ue Po ol

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.li stener.mode=true

If the SMPP protocol is used when configuring the SMS protocol, set:

sms.receiver.li stener.mode=false

5. If the UCP protocol is used, set the incoming listener port appropriately:

sms.receiver.li stener.port=

3.4 Request and Notification Queue Pool

To improve the throughput for request and notification processing, configure the number of threads that process the corresponding queue.

3.4.1 Request Queue Thread Pool Size

To configure the thread pool size for the request queue, set the following appropriately in the AsynchRequest.properties file in the WE_ HOME/server/classes/oracle/panama/core/admin directory:

# Thread pool s ize at startup # init.pool.size= # # Minimum Threa d pool size # minimum.pool.si ze=

3.4.2 Notif ic at io n Queu e Th r ea d Pool Si ze

To configure the thread pool size for the notification queue, set the following appropriately in the AsynchNotification.properties file in the WE_ HOME/server/classes/oracle/panama/core/admin directory:

# Thread pool s ize at startup

3-6 Oracle9i Application Server Wireless Edition Configuration Guide

Page 51

# init.pool.size= # # Minimum Threa d pool size # minimum.pool.si ze=

Request and Notification Queue Pool

Alerts and SMS Request Listener 3-7

Page 52

Request and Not ifi cati on Que ue Po ol

3-8 Oracle9i Application Server Wireless Edition Configuration Guide

Page 53

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.1 Overview

Wireless Edition generates logging information for both the server and development client components.

Logging

4.2 Database Logging

Wireless Edition database logging records each authenticated service invocation request and each successful user session. Database logging is required for performance monitoring and measurement using Oracle Enterprise Manager. The logged information includes service access patterns, response times for services, and the number of sessions. This data can be used by remote management tools to display results such as service access patterns, throughput, and average response times. Database logging is handled asynchronously.

Logging 4-1

Page 54

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 relate d parameters #

# Number of min utes after which the logger threa d wakes up to flu sh # the log entries to the databas e. This parameter is optional. SystemLog.logge r.wakeupFrequency =10

# The maximum n umber of entries cached by the lo gger thread. # This paramete r is optional. SystemLog.logge r.maxSize=100

# Whether service loggi ng should be enabled SystemLog.enabl eServiceLogging=t rue

# Whether session loggi ng should be enabled SystemLog.enabl eSessionLogging=t rue

# The request l istener class locator.request .listener.classes =oracle.panama.c ore.admin.SystemL ogger

# The session l istener class locator.session .listener.classes =oracle.panama.c ore.admin.SystemL ogger

# Enable event request logging event.before.re quest=true event.request.e nd=true event.request.e rror=true event.after.req uest=true

# Enable event session logging event.session.b egin=true event.session.e nd=true

# System Log Da tabase connect st ring <String> # Syntax for th is property is si milar to db.conn ect.string # System Logs can be present in a sep arate database # # NOTE: For the OEM cartrige que ries, Make sure the user specifie d below has

4-2 Oracle9i Application Server Wireless Edition Configuration Guide

Page 55

select access t o the V$ tables. # Usage example: log in as system and say "grant select any table to %PANAMA_ USERNAME%" #SystemLog.db.c onnect.string=%PA NAMA_USERNAME%/% PANAMA_USER_PW%@% PANAMA_ HOST%:%PANAMA_P ORT%:%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.

Note: The database user name used here (the one replacing

%PANAMA_USERNAME%) must have select access to all tables. In this example "PANAMA" is Wireless Edition.

4.2.2 Database Table Contents

Data logged to the database is stored in two tables, ptg_service_log and ptg_ session_log.

Database Logging

Table 4–1 Contents of the ptg_session_log Table

Column Name Description

session_id The identifier of the session. user_id The Object Identifier (OID) of the user of the session. user_name The user name. ptg_instance_id A unique identifier, for the database instance. logical_device The logical device which invoked the service. login_time The timestamp when the session was created. login_hour The hour when the session was created. expiry_time The timestamp when the session expired. timestamp The time when the data is logged.

Logging 4-3

Page 56

Database Logging

Table 4–2 Contents of the ptg_service_log Table

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. service_arguments Arguments of the service, in XML format. bookmark External link, if the invoked service is a bookmark. service_type Type of service. invocation_hour Hour when the service was invoked. invocation_time Date when the service was invoked. response_time Response time for the service. request_status Status of the request, a non-zero value indicates an error

error_description Error message, if one occurred while invoking the service. user_id OID for the user. user_name Name of the user. remote_address Host IP address and name. logical_device Logical device which invoked the service. external_user_id External user ID. external_user_name External user name. adapter_type Type of adapter. adapter_home Time taken by the ad apter. transformation_ time Time taken by the transformer. timestamp Time when the data is logged.

number.

4-4 Oracle9i Application Server Wireless Edition Configuration Guide

Page 57

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 setti ng, 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 Wire less Edition writes server error information to the files and directory specified in the System.properties file. You can open the log files directly, or view them from the Wireless Edition Runtime Information and Management interface (the Probe interface) at port 8090. Click the "Files" link.

The Wireless Edition specifies these types of errors:

Table 4–3 Server Error Information

Error Value

ERR_SERVICE_UNAVAILABLE PTG-001 ERR_SERVICE_ERROR PTG-002

Transaction Logging

ERR_SERVICE_NOT_FOUND PTG-003 ERR_CONFIGURA TION_ERROR PTG-004 ERR_INTERNAL_ERROR PTG-005 ERR_DATABASE_ERROR PTG-006

In addition to error messages, the Wireless Edition provides extensive runtime exception logging. When fatal exceptions occur, the Wireless Edition logs the exceptions and stack traces in the global log file. If you need to contact Oracle Support Services, you should have the log information available.

4.5 Transaction Logging

The transaction log is a log file on the Wireless Edition server that provides information regarding user access. To enable transaction logging, you must include transaction logging as a log level in the System.properties file. For example:

log.level=Warni ng, Error, Notify , Transaction

Logging 4-5

Page 58

Configuring the Runtime Monitor and Management

You can us e 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. You can access the transaction log data programmatically, to generate billing information or to integrate th e Wireless Edition transaction information with an external billing management system.

The following sample shows the log results of four stock quote queries by a single user. The sample uses the default logging pattern, which you can modify in the System.properties file. It lists the time of access, the user name (Sample), the service, and the price per access (25):

[11/14/99 4:03:26 PM] Sample /master/OnlineQuoteO racle 25 [11/14/99 4:03:29 PM] Sample /master/OnlineQuoteO racle 25 [11/14/99 4:03:35 PM] Sample /master/OnlineQuoteO racle 25

4.6 Configuring the Runtime Monitor and Management

The probe is a daemon that displays runtime information a b out:

■ 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.

By default, installation of Wireless Edition installs and initiates the probe runtime monitor with the listening port 8090. To access the probe from a browser enter the following URL:

http://host_name:8090

4-6 Oracle9i Application Server Wireless Edition Configuration Guide

Page 59

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.c ore.probe.WebServ er

Logging 4-7

Page 60

Configuring the Runtime Monitor and Management

4-8 Oracle9i Application Server Wireless Edition Configuration Guide

Page 61

Multiple JVM Support and Load Balancing

Multiple JVM Support and Load Balancing d esc ribes 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.4, "Multiple Instances and Oracle HTTP Server All on Different

Machines"

■ Section 5.5, "Load Balancing"

■ Section 5.6, "Configuring the Personalization Portal for Load-Balancing"

Note: Oracle recommends that each Java Virtual Machine (JVM)

not support more than 200 concurrent user sessions.

Multiple JVM Support and Load Balancing 5-1

Page 62

Overview

5.1 Overview

The following sections describe three possible deploym e nt scenarios for multiple Java Virtual Machine (JVM) support in Wireless Edition:

■ 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

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\pan ama (Windows) /private/ias102 10/panama (UNIX)

Replace "WE_HOME" with the fully-qualified directory path.

■ ORACLE_HOME is the directory in which Or acle9 i

Application Server is installed.

Different Machine"

■ Section 5.4, "Multiple Instances and Oracle HTTP Server All on Different

Machines"

This document describes:

■ The Cache synchronization setup (to ensure that the object caches of each

instance are synchronous).

■ Multiple JVM environment without JServ session cookies.

■ Personalization Portal setup.

Note: The steps in this document assume an initial configuration

of single JVM support. V erify that Wireless Edition is initially set up to run as a single instance communicating with a single Oracle HTTP Server instance.

5-2 Oracle9i Application Server Wireless Edition Configuration Guide

Page 63

Multiple Instances on Sa me M ach ine as Ora cle HTTP S erve r

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 sectio n that begins with <IFModule> and ends with </IFModule> in the jserv.conf file. The jserv.conf file is in the ORACLE_HOME\Apache\JServ\conf directory.

a. Modify the following:

<IfModule mod_jser v.c> ApJServManual o n

Running multiple instances of JServ requires a manual start for each instance:

ApJServMount /p tg balance://set1 /root

W1, W2,...WN are integers that determine the load-balancing weight

assigned to each of the instances. T o balance equally among all instances; do not specify Wx; the weight value must be an integer. Weight can be decid ed on the relative load you want each JServ to handle. Requests for /ptg are load-balanced on set "set1":

ApJServBalance set1 PC1 W1 ApJServBalance set1 PC2 W2 . . ApJServBalance set1 PCN WN

Port numbers can be any valid port on the system, however they should not

conflict with any other application using the same port.

ApJServHost PC1 ajpv1 2://localhost:7771 ApJServHost PC2 ajpv1 2://localhost:7772 . . ApJServHost PCN ajpv1 1://localhost:777N

JS1 to JSN are routing cookies. These can be set to any unique string for

each entry.

ApJServRoute JS 1 PC1

Multiple JVM Support and Load Balancing 5-3

Page 64

Multiple Instances on Same Machine as Oracle HTTP Server

ApJServRoute JS 2 PC2 . . ApJServRoute JS N PCN

This file is used internally by Apache for implementing fault tolerance:

ApJServShmFile ORA CLE_HOME\Apache\Jse rv\jserv_shm

g. Close the section using:

</IfModule>

2. Start the Oracle HTTP Server.

ORACLE_HOME\Apa che\Apache\Apache.ex e -k start -d ORACLE_HOME\Apa che\Apache

Create and modify the jserv.properties files for each of the instances. Make

copies of the default jserv.properties files for each of the instances, for example, jserv1.properties, jserv2.properties. The jserv.properties f ile is in the

ORACLE_HOME\Apache\JServ\conf directory. Modify the files:

a. Port which the instance uses to communicate with Apache using the AJP

protocol. x corresponds to each of the JServ instances 1...N.

port=777x

The log file. For Unix, ensure that the JServ process owner has write permissions for this file:

log.file=ORACLE _HOME\Apache\Jser v\logs\jservx.lo g

c. This allows only clients from the local machine to access the JServ instances:

security.allowe dAddresses=127.0. 0.1

d. Change the location of class files specific to the JServ instance from:

wrapper.classpa th=<WE_HOME>\serv er\classes

to:

wrapper.classpa th=<WE_HOME>\serv er\classesx

4. To enable cache synchronization among the database instances, modify the

Wireless Edition specific properties files. The default location for these files is in the <WE_HOME>\server\classes directory. Create copies of this directory

5-4 Oracle9i Application Server Wireless Edition Configuration Guide

Page 65

Multiple Instances on Sa me M ach ine as Ora cle HTTP S erve r

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 <WE_HOME>\server\classesx, where x corresp onds to each of the JServ instances 1...N. Modify the System.properties file in the <WE_ HOME>\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.

instance.identi fier=instancex

b. Set the following parameter to true for every instance to ensure that the

instance participates in cache synchronization:

participateInCa cheSynchronizatio n=true

c. This value should point to the machine and port where the Master Instance

for Cache synchronization is running. It should have the same value for all instances. Ensure that the port number (2007 in this case) is the same as the one specified by the rmi.registry.port parame ter in the Master.properties file:

masterInstance. url=//localhost:2 007

Modify the properties files in Table 5–1. These files are in the <WE_

HOME>\serv er \c l as sesx\oracle \ p anama\core directory. The sub-directories are specified.

e. Run the following SQL scripts by connecting to the repository database as

the Wireless Edition database user. The scripts are provided in the <WE_ HOME>\server\classesx\oracle\panama\sql directory.

create_cachesyn c_schema.sql enable-cachesyn ch_triggers.sql

The master server must be started by running the script <WE_

HOME>\serv e r\c l a s s e s x \o r ac l e \ p anama\sample\ runMasterSe r v er.bat or runMasterServer.sh.

Multiple JVM Support and Load Balancing 5-5

Page 66

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.properties magent.server.port=201x

Same as rmi.server.port in Rmi.properties.

\spatial\spatial .properties Change path to cl ass files to reflect the per

\Master\Master.properties Modify the db.connect parameter in this file to be

instance classes.

the same as that in System.properties.

Modify only the Master.properties file in the

classpath of the master instance.

ptgInstances.length=N

ptgInstance1.rmi.host=localhost

ptgInstance1.rmi.port=2011 (This is the value of

rmi.server.port in the Rmi.properties file.)

ptgInstance1.rmi.objectName=CacheSyncClient

(Do not change CacheSyncClient to any other

value.)

ptgInstance2.rmi.host=localhost

ptgInstance2.rmi.port=2012

ptgInstance2.rmi.objectName=CacheSyncClient

ptgInstanceN.rmi.host=localhost

ptgInstanceN.rmi.port=201N

ptgInstanceN.rmi.objectName=CacheSyncClient

Start each of the JServ instances manually after the Oracle HTTP Server is

started. Create a batch script to supply all the classes specif ied in the

5-6 Oracle9i Application Server Wireless Edition Configuration Guide

Page 67

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. For example:

ApJServHost PC1 ajpv1 2://jserv-machine:7 771 ApJServHost PC2 ajpv1 1://jserv-machine:7 772 . . ApJServHost PCN ajpv1 1://jserv-machine:7 77N

These port numbers can be any valid port on the machine running JServ instances, only that they must not conflict with any other application using the same port.

2. In each of the jserv.propertiesx files, change the bindaddress parameter to the

IP address of the machine running the JServ instance, and the security.allowedAddresses parameter to point to the IP address of the machine running the Oracle HTTP Server. For example:

bindaddress=ip_ address_of_machin e_running_jserv_ instance security.allowe dAddresses=192.16 8.1.2

5.4 Multiple Instances and Oracle HTTP Server All on Different Machines

The steps are similar to Section 5.2, in addition:

1. Modify the jserv.conf file on the machine running the Oracle HTTP Server.

Ensure that the ApJServHost directive includes the IP addresses of each of the machines running the JServ instances. For example:

ApJServHost PC1 ajpv1 2://jserv-machine1: 8007 ApJServHost PC2 ajpv1 1://jserve-machine2 :8007 . . ApJServHost PCN ajpv1 1://jserv-machineN: 8007

Multiple JVM Support and Load Balancing 5-7

Page 68

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_machin e_running_jserv_ instance security.allowe dAddresses=oracle httpserver_ip_ad dress

On the machine running the Master Instance, modify the Master.properties file. See Table 5–1 for more information.

5. Modify the system.properties file in the <WE_

HOME>\server\classes\oracle\panama\core\admin directory on all machines:

a. Set the unique identifier for the instance:

instance.identi fier=instancex

b. Set the following parameter to true to ensure that the instance participates

in cache synchronization:

participateInCa cheSynchronizatio n=true

c. Set the following parameter to point to the machine and port where the

Master Instance for Cache synchronization is running. It should have the same value for all instances. Ensure that the port number (2007 in this case) is the same as the one specified by the rmi.registry.port parameter in the Master.properties file.

masterInstance. url=//machine_run ning_master_inst ance:2007

Run the SQL script enable_cachesync_schema.sql by connecting to the repository database as the Wireless Edition database user. The script resides, by default, in the <WE_HOME>\sql directory.

e. Start the master server on the machine running the master instance by

running the script runMasterServer.bat in the <WE_HOME>\sample directory.

6. Start each of the JServ instances manually using the batch script. See

Section 5.6.3 for a sample script.

5-8 Oracle9i Application Server Wireless Edition Configuration Guide

Page 69

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.

The main purpose of multiple JVM support in Wireless Edition is to provide scalability through load-balancin g. There are three implementation s when setting up load-balancing.

■ Load-balancing among Oracle HTTP servers through hardware load-balancing.

■ Load-balancing among Jserv instances with cookies.

■ Load-balancing among Jserv instances with URL rewritin g.

5.5.1 Load-Balancing with Cookies

When intermediate gateways or proxies and the clients support cookies, load balancing can be achieved using cookies:

1. Set the enable.http.session.binding parameter in all of the System.properties

files (on all machines, if more than one machine is invo lved) to true.

2. In the ORACLE_HOME\Apache\JServ\conf\zone.properties file set the

session.useCookies parame ter to true.

5.5.2 Load Balancing Through URL Rewriting

When intermediate gateways or proxies do not support cookies, load balancing can be achieved through URL rewriting:

1. Set the enable.http.session.binding parameter in all of the System.properties

files (on all machines, if more than one machine is invo lved) to true.

2. In the ORACLE_HOME\Apache\JServ\conf\zone.properties file set the

session.useCookies parameter to false.

5.6 Configuring the Personalization Portal for Load-Balancing

This section describes the configuration of the Personalization Portal in two environments:

Multiple JVM Support and Load Balancing 5-9

Page 70

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 interm ed iate gateways support cookies, enable one of the load-balanced Wireless Edition instances to service Personalization Portal requests. Modify th e jserv.conf file to change the value of the ApJServDefaultPort parameter to the port number of any of the load-balanc ed instances (Ap JServDefault P ort 7771).

5.6.2 Clients/Gateways Do Not Support Cookies

To set up the Personalization Portal when clients and/or intermediate gateways do not support cookies, run a separate Wireless Edition instance to service Personalization Portal requests.

1. Modify the jserv.conf file to change the value of the ApJServDefaultPort

parameter to the port number of any unoccupied port (ApJServDefaultPort

7774).

2. Create a copy of the jserv.properties file, for example, jserv4.properties

(assuming that there are three load-balanced instances running) fo r each of the instances and modify the follow ing:

a. Set the port which the instance uses to communicate with Oracle HTTP

Server using the AJP protocol. This should be the same as the value set for the ApJServDefaultPort parameter in the jserv.conf file.

port=7774

b. Set the log file. For UNIX ensure that the JServ process owner has write

permissions for this file.

log.file=ORACLE _HOME\Apache\Jser v\logs\jserv4.lo g

c. Ensure that only the Oracle HTTP Server talks to this JServ instance:

security.allowe dAddresses=oracle httpserver_ip_ad dress

d. Change wrapper.classpath=<WE_HOME>\serv e r\classes to

wrapper.classpath=<WE_HOME>\server\classesx. This is the location of class files specific to the JServ instance.

5-10 Oracle9i Application Server Wireless Edition Configuration Guide

Page 71

Configuring the Personalization Portal for Load-Balancing

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\Apa che\Jserv\conf\z one_pp.properties

4. Modify the various Wireless Edition specific properties files. The default

location for these files is in the <WE_HOME>\server\classes directory. Create a copy of this directory and modify the properties files so that each of the JServ instances has a unique port number and other resources. For example, the directory should appear as <WE_HOME>\server\classes. In the <WE_ HOME>\server\classes4\oracle\panama\core\admin\ directory, modify the System.properties file.

a. Set the unique identifier for this instance:

instance.identi fier=instance

b. Set the following parameter to true to ensure that the instance participates

in cache synchronization:

participateInCa cheSynchronizatio n=true

Set the enable.http.session.binding to false.

c. d. Set the following to point to the machine and port where the Master

Instance for Cache synchronization is running. It sho uld have the same value for all instances. Ensure that the port number (2007 in this case) is the same as the one specified by the rmi.registry.port parameter in the Master.properties file on the machine running the Master instan ce.

masterInstance. url=//localhost:2 007

Set the following in the AsynchNotification.properties file in the <WE_

HOME>\server\classes\oracle\panama\core\admin\ directory to:

server.listen.p ort=5500

f. Set the following in the AsynchRequest.properties file in the <WE_

HOME>\server\classes\oracle\panama\core\admin\ directory to:

server.listen.p ort=6500

g. Set the following in the Ftp.properties file in the <WE_

HOME>\server\classes\oracle\panama\core\admin\ directory to:

ftp.server.port =910

Multiple JVM Support and Load Balancing 5-11

Page 72

Configuring the Personalization Portal for Load-Balancing

h. Set the following in the Notification.properties file in the <WE_

HOME>\server\classes\oracle\panama\core\admin\ directory to:

sms.server.port =5000

Set the following in the Rmi.properties file in the <WE_

HOME>\server\classes\orac le\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.properties file in the <WE_

HOME>\server\classe s\oracle\panama\core directory:

port=809

Set the following in the MAgent.properties file in the <WE_ HOME>\server\classes\oracle\panama\magent\config di rectory. This is the same as the rmi.server.port setting in Rmi.properties in the <WE_ HOME>\server\classes\orac le\panama\core\admin directory.

magent.server.p ort=201

l. Set the path to the class files to reflect the per instance classes in the

Spatial.properties file in the <WE_ HOME>\server\classes\oracle\panama\spatial\ directory.

Now the instance can be started using the batch file in Section 5.6.3.

5.6.3 Sample Batch File

The following is a sample batch f ile for manually starting and stopping Oracle HTTP Server. Classes for hooks or other features should be added at the end of the file.

@ECHO OFF set classpath=%cla sspath%;ORACLE_HOME \java\lib;PORACLE_HO ME\Apache\jdk\lib set classpath=%cla sspath%;ORACLE_HOME\Ap ache\Jserv\ApacheJs erv.jar set classpath=%cla sspath%;ORACLE_HOME\Ap ache\Jsdk\lib\jsdk. jar set classpath=%cla sspath%;<WE_HOME>\serv er\classes%1 set classpath=%cla sspath%;<WE_HOME>\lib\ panama.zip set classpath=%cla sspath%;<WE_HOME>\lib\ panama_core.zip set classpath=%cla sspath%;<WE_HOME>\lib\ panama_portal.zip set classpath=%cla sspath%;<WE_HOME>\lib\ panama_papz.zip set classpath=%cla sspath%;ORACLE_HOME\jd bc\lib\classes12.zi p

5-12 Oracle9i Application Server Wireless Edition Configuration Guide

Page 73

Configuring the Personalization Portal for Load-Balancing

set classpath=%cla sspath%;ORACLE_HOME\js p\lib\ojsp.jar set classpath=%cla sspath%;ORACLE_HOME\li b\servlet.jar set classpath=%cla sspath%;ORACLE_HOME\Ap ache\BC4J\lib\jndi. jar set classpath=%cla sspath%;ORACLE_HOME\li b\xmlparserv2.jar set classpath=%cla sspath%;<WE_HOME>\lib\ client.zip set classpath=%cla sspath%;<WE_HOME>\l ib\server.zip set classpath=%cla sspath%;<WE_HOME>\l ib\caboshare-opt-1_0 _0.zip set classpath=%cla sspath%;<WE_HOME>\l ib\marlin-opt-1_0_0. zip set classpath=%cla sspath%;<WE_HOME>\l ib\ocelot-opt-1_0_0. zip set classpath=%cla sspath%;<WE_HOME>\l ib\share-opt-1_1_7.z ip set classpath=%cla sspath%;<<WE_HOME>> \lib\tecate-opt-1_0_ 0.zip set classpath=%cla sspath%;<WE_HOME>\l ib\regexp.jar set classpath=%cla sspath%;<WE_HOME>\lib\ sax2.jar set classpath=%cla sspath%;<WE_HOME>\lib\ activation.jar set classpath=%cla sspath%;<WE_HOME>\l ib\mail.jar set classpath=%cla sspath%;<WE_HOME>\lib\ ldap.jar set classpath=%cla sspath%;<WE_HOME>\lib\ ldapbp.jar set classpath=%cla sspath%;<WE_HOME>\lib\ providerutil.jar set classpath=%cla sspath%;<WE_HOME>\lib\ sdoapi.jar set classpath=%cla sspath%;<WE_HOME>\lib\ sdovis.jar set classpath=%cla sspath%;<WE_HOME>\lib\ MapQuestX.jar set classpath=%cla sspath%;<WE_HOME>\lib\ MQJavaCore.jar set classpath=%cla sspath%;<WE_HOME>\lib\ RoutingJServerClien t.jar set classpath=%cla sspath%;<WE_HOME>\lib\ jai_codec.jar set classpath=%cla sspath%;WE_HOME\lib \classes%1 REM Add other classpath entries here for specif ic features or ho oks implemented REM by the cus tomer. java -c %org.ap ache.jserv.JServ ORACLE_HOME\Apac he\JServ\conf\jse rv%1.properties

This script (in the example, jservmanual.sh) can be used in the following manner to start and stop a Jserv instance:

■ To start instance 1, use:

jservmanual.sh 1

■ To stop an instance, use:

jservmanual.sh 1 -s

Multiple JVM Support and Load Balancing 5-13

Page 74

Configuring the Personalization Portal for Load-Balancing

5-14 Oracle9i Application Server Wireless Edition Configuration Guide

Page 75

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.6, "Configuring the Database Logger"

■ Section 6.7, "Asynchronous Notification of Error Information"

■ Section 6.8, "Launching the Oracle Enterprise Manager Tools"

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\pan ama (Windows) /private/ias102 10/panama (UNIX)

Replace "WE_HOME" with the fully-qualified directory path.

■ ORACLE_HOME is the Oracle 8.1.7 Oracle home.

Oracle Enterprise Manager 6-1

Page 76

Overview

6.1 Overview

The use of Oracle Enterprise Manager with Wireless Edition provides:

■ Performance mo ni t or i ng

■ 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. The Capacity Planner allows you to archive and view performance data collected by the Wireless Edition cartridge. This cartridge is used by the Data Gatherer to collect performance data logged by the Wireless Edition runtime.

Fault Management

The event framework of Oracle Enterprise Manager enables asynchronous notification of error information. When an error occurs, Wireless Edition generates an Oracle Enterprise Manager event at the node where the error occurred. The event provides the details necessary for fault diagnosis. The Oracle Intelligent Agent running on each node picks up these events and forwards them to the Oracle Enterprise Manager Console for display. You can con f igure the Console to page or email the administrator.

Configuration Management

The configuration management framework provides a way to alter some runtime parameters.

6.2 Prerequisites

To configure Oracle Enterprise Manager for use with Wireless Edition you must first install the following com p onents:

■ Oracle Enterprise Manager 2.2 with Diagnostic Pack

■ Oracle Intelligent Agent 8.1.7

■ Oracle Management Server 2.2

6-2 Oracle9i Application Server Wireless Edition Configuration Guide

Page 77

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 c on f i gu r ation instr u c t ions:

■ The Oracle Enterprise Manager server side configuration involves the Oracle

Intelligent Agent and Data Gatherer. See Section 6.3.1.

■ The Oracle Enterprise Manager client side configuratio n involves the Console

(the navigator and events) and Diagnostic Pack (Performance Manager and Capacity Planner). See Section 6.3.2.

■ The Oracle Enterprise Manager middle-tier configurat ion involves the Oracle

Management Server, specifically the configuration to receive threshold events from the Data Gatherer Cartridge on the Console. See Section 6.3.3.

6.3.1 Configuring the Server Side

The server side configuration includes the configuration of the Oracle Intelligent Agent and the Wireless Edition Data Gatherer Cartridge.

6.3.1.1 Configuring the Oracle Intelligent Agent

To config ure the Oracle Intelligent Agent on the server:

1. Install the Oracle Intelligent Agent 8.1.7 in ORACLE_HOME. If the Ora c le

Management Server is to reside on the same host as the Oracle Intelligent Agent, ensure that the Oracle Management Server is also installed in the same ORACLE_HOME.

Note: If running Oracle 8.1.6, perform a custom installation of

Oracle 8.1.7 Enterprise Edition. Select the Oracle Intelligent Agent and its subcomponents. Insta ll it in a separate ORACLE_HOME.

2. Copy the file dgmetric.tcl from the WE_HOME/oem/agent directory to the

Oracle Intelligent Agent ORACLE_ HOME/networ k /ag e n t /e ve n t s/oracle/gen er i c /m e t ric directory. This operation replaces the existing dgmetric.tcl file.

3. Copy the file ptg_services.tcl from the WE_HOME/oem/agent directory to the

ORACLE_HOME/n etwork/agent/config d irec t or y.

Oracle Enterprise Manager 6-3

Page 78

Configuring the Server, Client, and Middle-tier

Append the ptg_services.tcl file name to the nmiconf.1st file found in the ORACLE_HOME/n etwork/agent/config d irec t or y.

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.

Note: The Oracle Intelligent Agent must be restarted whenever

any change is made to the ptg_services.tcl file or to the nmiconf.lst file.

After completing the preceding instructions, install the Wireless Edition Data Gatherer cartridge. The Oracle Intelligent Agent uses this cartridge to collect Wireless Edition performance data. The Performance Manager and Capacity Planner use the collected data to provide runtime metrics for diagnosis.

The cartridge installation steps differ according to the hardware platform.

6.3.1.2 Wireless Edition Data Gatherer Cartridge Installation: Unix

To install the data gatherer cartridge:

Important: The cartridge installation requires an Oracle Enterprise

Manager 2.2 Console and Oracle Intelligent Agent 8.1.7 on the server side.

1. Un-tar t he ptgsolariscartridge.tar file found in WE_

HOME/oem/agent/cartridge/solaris to a directory (referred to as CART_DIR in this document).

2. Copy CART_DIR/lib/libvpxptg.so to the ORACLE_HOME/odg/lib directory.

3. Copy CART_DIR/mesg/vpxptgus.msb to the ORACLE_HOME/odg/mesg

directory.

4. Copy CART_DIR/html/vpxptgUS.htm to the ORACLE_H OM E /odg/html

directory.

6-4 Oracle9i Application Server Wireless Edition Configuration Guide

Page 79

Configuring the Server, Client, and Middle-tier

Append the following entry to the svppcart.dat file in the ORACLE_ HOME/odg directory.

PTG ALL libvpxptg vpxpt g

This completes the server side configuration. Restart the Oracle Intelligent Agent. Restart the Data Gatherer.

Oracle Intelligent Agent Start and Stop

To stop the agent:

lsnrctl dbsnmp_ stop

To start the agent:

lsnrctl dbsnmp_ start

Data Gatherer Start and Stop

To stop the gatherer:

vppcntl -stop

To start the gatherer:

vppcntl -start

Note: For more informatio n on commands to restart the Oracle

Intelligent Agent, Oracle Management Server, and Data Gat herer, see the Oracle Enterprise Manager Configuration Guide.

6.3.1.3 Wireless Edition Data Gatherer Cartridge Installation: Windows

To install the data gatherer cartridge:

Important: The cartridge installation requires an Oracle Enterprise

Manager 2.2 Console and Oracle Intelligent Agent 8.1.7 on the server side.

Oracle Enterprise Manager 6-5

Page 80

Configuring the Server, Client, and Middle-tier

Un-zip the ptgwincartridge.zip file in WE_ HOME/oem/agent/cartrid ge/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.dat file in the ORACLE_

HOME\odg directory:

PTG ALL vpxptg vpxptg

This completes the server side configuration for Oracle Enterprise Manager integration. Restart the Oracle Intelligent Agent an d the Da ta Gatherer. This sta r ts the Wireless Edition cartridge along with the Oracle Intelligent Agent startup.

Select the Control Panel and then Services to restart the appropriate service.

6.3.2 Configuring the Client Side

To configure the Oracle Enterprise Manager client side:

Note: Requirement for deployment of the integration classes: JRE

1.1.8_10 f o r Unix and JRE 1.1.7.30 o for Windows.

1. Install the Oracle Enterprise Manager client, including the Console and client

tools, Oracle Management Server, and Diagnostic Pack (Performance Manager and Capacity Planner).

Note: The Oracle Enterpri se Manager Diagnostic Pack is only

available for Windows.

2. Copy the file oemptg.jar from the WE_HOME/oem/client directory to the

ORACLE_HOME/classes directory.

6-6 Oracle9i Application Server Wireless Edition Configuration Guide

Page 81

Configuring the Server, Client, and Middle-tier

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.pro perties.append must be

appended to ORACLE_HOME/sysman/config/OEMCLient.properties. The following shows the entries.

# # System defini tion of types for Wireless Editio n # /com/oracle/sys man/em/system/types/ oracle_sysman_ptg/i sa =test_service1 /com/oracle/sys man/em/system/typ es/oracle_sysman _ptg/service = tr ue /com/oracle/sys man/em/system/typ es/oracle_sysman _ptg/display_clas s = oracle.sysman.p tg.navigator.PtgD isplayDriver

# # Console defin ition of types fo r navigator tree for # Wireless Edit ion # /com/oracle/sys man/em/console/na vigator/oracle_s ysman_ptg/data_so urce = oracle.sysman.p tg.navigator.PtgS ubItemContainerS ource

/com/oracle/sys man/em/console/na vigator/oracle_s ysman_ptg/proxy =oracle.sysman. ptg.navigator.Ptg Proxy

# # Events Integr ation # # Wireless Edit ion events integr ation # /com/oracle/sys man/em/console/tests _datasource/ptg/dat asource = oracle.sysman.p tg.PTGTestsDataso urce

# PTG Console c redentials classe s for Events Int egration /com/oracle/sys man/em/system/types/ oracle_sysman_ptg/i sa = /com/oracle/sys man/em/system/typ es/oracle_sysman _ptg/service = tr ue /com/oracle/sys man/em/system/types/ oracle_sysman_ptg/c redentials_display = oracle.sysman.v tcConsole.vtcCred entials.PtgCrede ntialsDisplay /com/oracle/sys man/em/system/types/ oracle_sysman_ptg/c redentials = oracle.sysman.e mSDK.common.crede ntials.PtgCreden tials

Oracle Enterprise Manager 6-7

Page 82

Configuring the Server, Client, and Middle-tier

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/o racle_sysman_ ptg=oracle.sysm an.vtd.VtdPtgCred entials /options/standa lone=TRUE

Edit the ORACLE_

HOME/classes/oracle/panama/magent/MAgent.properties file to reflect the values of the installed Wireless Edition server name. The port number and the service name are defaulted.

Note: This property file should be in synch with the one on the

Wireless Edition server side for each instance to which the file refers.

7. For the Oracle Enterprise Manager client side installation the only pertinent

values are magent.server.host and magent.server. The remaining properties may be ignored or defaulted here.

# Server Host N ame magent.server.h ost=<Wireless Edition ser ver host name>

# The service p ort: Use the same port as the RMI server as # in Rmi.prope rties magent.server.p ort=2008

# Service Name magent.server.n ame=Magent

Verify that the classpath contains the following entries.

For UNIX:

$ORACLE_HOME/cl asses $ORACLE_HOME/jd bc/lib/classes111 .zip $ORACLE_HOME/li b/vbjorb.jar $ORACLE_HOME/li b/vbjapp.jar $ORACLE_HOME/li b/vbjtools.jar $ORACLE_HOME/cl asses/classesFrom IDLVisi $ORACLE_HOME/jl ib/ewt-3_3_6.jar

6-8 Oracle9i Application Server Wireless Edition Configuration Guide

Page 83

Configuring the Server, Client, and Middle-tier

$ORACLE_HOME/jl ib/ewtcompat-opt- 3_3_6.zip $ORACLE_HOME/jl ib/ewt-swingacces s-1_1_1.jar $ORACLE_HOME/jl ib/share-1_0_8.ja r $ORACLE_HOME/jl ib/jssl-1_2.jar $ORACLE_HOME/jl ib/javax-ssl-1_2. jar $ORACLE_HOME/jl ib/netcfg.jar:/

For Windows:

%ORACLE_HOME%\c lasses %ORACLE_HOME%\j dbc\lib\classes11 1.zip %ORACLE_HOME%\l ib\vbjorb.jar %ORACLE_HOME%\l ib\vbjapp.jar %ORACLE_HOME%\l ib\vbjtools.jar %ORACLE_HOME%\c lasses\classesFro mIDLVisi %ORACLE_HOME%\j lib\ewt-3_3_6.jar %ORACLE_HOME%\j lib\ewtcompat-opt -3_3_6.zip %ORACLE_HOME%\j lib\ewt-swingacce ss-1_1_1.jar %ORACLE_HOME%\j lib\share-1_0_8.j ar %ORACLE_HOME%\j lib\jssl-1_2.jar %ORACLE_HOME%\j lib\javax-ssl-1_2 .jar

The Oracle Enterprise Manager client side configuration is now complete.

6.3.3 Configuring the Middle-tier

The middle-tier hosts the Oracle Management Server. The following configuration is for the Events Integration.

1. Copy the file oemptg.jar in the WE_HOME/oem/oms directory to the

ORACLE_HOME/classes directory where the Oracle Management Server is installed.

2. Extract this file in the copied directory, for example:

jar -xvf oemptg.jar

This extracts the Console integration classes, Performance Manager integration classes, events integration classes, and RMI client a nd stub for the Console interaction with the server.

3. The entries in WE_HOME/oem/oms/OMSRegistry.registry.append must be

appended to the OMSRegistry.registry file in ORACLE_ HOME/sysman/admin.

# ORACLE_HOME/s ysman/admin/OMSRe gistry.registry

Oracle Enterprise Manager 6-9

Page 84

Setting up the ptg_services.tcl File

# Wireless Edit ion events integr ation # /com/oracle/sys man/em/tests_datasou rce/ptg/datasource = oracle.sysman.p tg.PTGTestsDataso urce

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 Gui de for m ore information.

This completes the middle-tier configuration. Restart the Oracle Management Server and Oracle Intelligent Agent.

6.4 Setting up the ptg_services.tcl File

To set up the ptg_services.tcl file:

1. Set the correct values of the NEW_PARAMETER_NAME, PTG_INSTANCE_

NAME, TRACE_DB_HOSTNAME, TRACE_DB_PORT, TRACE_DB_SID, and TRACE_DB_ORACLE_HOME for each instance.

2. To add anoth er instance: a. Add a new parameter to store the new ServiceName (the Wireless Edition

instance name) to the "global Parameters". See the following example.

b. Copy the lines between "BEGIN EXAMPLE" and "END EXAMPLE", and

replace the information with the new instance’s parameter name and remaining information.

global Paramete rs ServiceType Ho stName tnsaddres s argv NEW_PARAME TER_ NAME ServiceNam e2

set Parameters( oracle_sysman_ptg ) {ServiceType H ostName tnsaddres s };

set Host [linde x $argv 0];

#The Service na me is a subnode i n the navigator

set NEW_PARAMETER_ NAME PTG_INSTANCE_NAME ;

lappend Service Names $NEW_PARAME TER_NAME; set ServiceType($N EW_PARAMETER_NAME) ora cle_sysman_ptg;

6-10 Oracle9i Application Server Wireless Edition Configuration Guide

Page 85

Setting up the ptg_services.tcl File

set HostName($NEW_ PARAMETER_NAME) $Host; set tnsaddress( $NEW_PARAMETER_NA ME) "(DESCRIPTIO N=(ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP )(HOST = TRACE_DB_HOSTNAM E)(PORT = TRACE_DB_ PORT)))(CONNECT _DATA=(SID=TRACE_ DB_SID)(ORACLE_H OME=TRACE_DB_ORAC LE_ HOME)(SERVER=DE DICATED)))"

In the following example a new parameter (ServiceName2) is added and the values for the PTG_INSTANCE_NAME, TRACE_DB... are set. For this example the listed parameters are replaced with the values in the following. The values are similar to the tnsnames.ora configuration.

Table 6–1 ptg_services.tcl Parameters

Parameter Value in Examp le Description

NEW_PARAMETER_NAME ServiceName2 Parameter name declaration. PTG_INSTANCE_NAME PTG2 The Wireless Edition instance

TRACE_DB_HOSTNAME ptgserver-sun.us.oracle.com The host name of the

TRACE_DB_PORT 1521 The port of the database

TRACE_DB_SID ptgdev The SID of the log database. TRACE_DB_ORACLE_

HOME

# Example: # The Service n ame "PTG2" (Wirel ess Edition Inst ance name) is a s ubnode in the # Navigator tre e

# In the line b elow, just append the new paramet er name # i.e. Service Name2. Don’t dupl icate this line. global Paramete rs ServiceType Ho stName tnsaddres s argv ServiceNam e2

set Parameters( oracle_sysman_ptg ) {ServiceType H ostName tnsaddres s };

set Host [linde x $argv 0];

# Lines below n eed to be duplica ted every time a new instance is added set ServiceName2 PTG2 ; lappend Service Names $ServiceNam e2; set ServiceType($S erviceName2) oracle_sy sman_ptg;

/private/oracle/8.1.7 The Oracle home directory.

name.

database log database.

listener.

Oracle Enterprise Manager 6-11

Page 86

Configuration for Anothe r Wir eless Ed ition Instan ce

set HostName($Serv iceName2) $Host; set tnsaddress($S erviceName2) "(DESCRIPTION=(ADDRE SS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = p tgserver-sun.us.o racle.com)(PORT = 1521)))(CONNECT _ DATA=(SID=ptgde v)(ORACLE_HOME=/p rivate/oracle/8. 1.7)(SERVER=DEDIC ATED)))"

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.5 Configuration for Another Wireless Edition Instance

The preceding configuration is for one Wireless Edition instance. To configure another Wireless Edition instance:

1. Ptg_services.tcl: Add another entry in the ORACLE_

HOME/network/agent/config/ptg_services.tcl file. Give this instance a different service name. See Section 6.4 for in struct ions and an example.

2. Minstances.properties: Add a corresponding instance’s <instance name > =

<property file name> entry to the ORACLE_ HOME/classe s /o r acl e /p a nama/magent/c onfig/MInstanc es.propert i es file. The RMI client uses this information to communicate with the corresponding server. Each instance is monitored using a Magent.properties file which contains the Wireless Edition server host name, port, and service name. In the case of multiple instances, these are identified by these values. The

Minstances.properties file should point the instance name to the corresponding Magent.properties file. For example, for two instances:

PTG1=oracle.pan ama.magent.config .Magent1 PTG2=oracle.pan ama.magent.config .Magent2

Magent.properties: Configure the Magent.properties file on both the client and

server side to point to the new instance’s classes and port. Users can have any number of instances but each instance’s information is stored in a separate property file.

4. Ensure that an Oracle Enterprise Manager Agent is installed on the node where

the Wireless Edition instance is running. The Wireless Edition instance uses the Agent to pipe error messages to the Oracle Enterprise Manager Console.

5. The System.properties.templ file contains parameters for the system logger

and the logger schema. Ensure that these are set up appropriately.

6-12 Oracle9i Application Server Wireless Edition Configuration Guide

Page 87

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.7 Asynchronous Notification of Error Information

Asynchronous notification of error information is provided using the event framework provided by Oracle Enterprise Manager. In case of an error, the Wireless Edition server generates an Oracle Enterprise Manager event at the node where the error occurred providing all the necessary details for the fault diagnosis.

Note: An Oracle Enterprise Manager agent must be running on

the node where oemevent is invoked. The event must be defined as an unsolicited event and the node must be added as a monitored destination.

The Oracle Enterprise Manager Event properties can be configured by editing th e oemevent.properties file in the WE_HOME/server/oracle/panama/core/admin directory.

The oemevent.properties file has the following parameters:

Table 6–2 Properties of the oemevents.properties File

Key Type Customizable Description

oemevent.path string Y Complete path name for the

oemevent executable.

oemevent.event. name

oemevent.object. name

oemevent.event level

string Y Unsolicited event name as defined in

the console.

string Y Object name specified in the event

definition.

string Y Event level specified in the event

definition. The level should be defined as "2" and specified as "ale rt".

Oracle Enterprise Manager 6-13

Page 88

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 W indows 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.

3. Double-click PTG PM Targets.

4. Enter the Wireless Edition login information to the schema where the Wireless

Edition dumps the runtime log informa tion. This information is the same as the system logger configuration information that is entered in Section 6.6.

5. Enter the Data Gatherer Location. This is the host on which you installed the

Data Gatherer and Wireless Edition cartridge.

6. Click OK.

This allows you to begin using the performance monitoring and capacity planning. The Fault and Configuration Managem e nt is accomplished through the Oracle

Enterprise Manager Console.

1. Launch the Oracle Enterprise Manager Console. See the Oracle Enterprise

Manager documentation for instructions on how to launch it.

2. Log on to the repository which you created during your Oracle Enterprise

Manager installation.

3. Discover the node where the Oracle Intelligent Agent is running.

4. Configure the Console to receive unsolicited events from the Nodes

(hostnames) on which Wireless Edition is running. See the Oracle Enterprise Manager documentation for instructi ons on how to configure it.

6-14 Oracle9i Application Server Wireless Edition Configuration Guide

Page 89

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.properties Files and Localization"

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\pan ama (Windows) /private/ias102 10/panama (UNIX)

Replace "WE_HOME" with the fully-qualified directory path.

■ ORACLE_HOME is the directory in which Or acle9 i

Application Server is installed.

Multi-byte Character Support 7-1

Page 90

Overview

7.1 Overview

This release of Wireless Edition supports single-byte, multi-byte, and fixed-width encoding schemes which are based on national, inte rnational, and vendor-specific standards.

If the character set is single byte, and that character set incl ud es 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. A character can consist of one or more bytes, depending on the specific multi-byte encoding scheme.

A typical situation is when character elements are combined to form a single character. Fo r example, in the Thai language, up to three separate character elements can be combined to form one character, and one Thai character would require up to 3 bytes when TH8TISASCII or another single-byte Thai character set is used. One Thai character would require up to 9 bytes when the UTF8 character set is used.

7.2 Multi-byte Encoding Schemes

Multi-byte encoding schemes are needed to support ideographic scripts used in Asian languages like Chinese or Japanes e since these languages use thousands of characters. These schemes use either a fixed number of bytes to represent a character or a variable number of b ytes per character.

7.2.1 Fixed-width Encoding Schemes

In a fixed-width Multi-byte encoding scheme, each character is represented by a fixed number of n bytes, where n is greater than or equal to two.

7.2.2 Variable-width Encoding Schemes

A variable-width encoding scheme uses one or more bytes to represent a single character. Some Multi-byte encoding schemes use certain bits to indicate the number of bytes that represent a character. For example, if two bytes is the maximum number of bytes used to represent a character, the most significant bit can be toggled to indicate whether that byte is part of a single-byte character or the first byte of a double-byte character. In other schemes, control codes differentiate single-byte from double-byte characters. Another possibility is that a shift-out code is used to indicate that the subsequent bytes are double-byte characters until a shift-in code is encountered.

7-2 Oracle9i Application Server Wireless Edition Configuration Guide

Page 91

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, wh ich 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. To change the default encoding to multi-byte encoding click PAPZ under Logical Devices in the Service Designer and change the encoding for your particular language.

7.4 Setting up a Netscape Browser to Display Multi-byte Data

To set up a Netscape 4.6 web browser to display Multi-byte data:

1. Click Edit, Preference, Appearance, and Fonts.

2. Select Unicode in the For the Encoding field.

3. For example, for Chinese, select MS Song in the Variable Width Font field.

4. For example, for Chinese, select MS Song in the Fixed Width Font field.

5. Select the "Use my default fonts, overriding document-specified fonts" radio

button.

7.5 LocalStrings.properties Files and Localization

Localization has been simplified through the use of a property file called LocalStrings.properties. This file contains text labels used by screens within various adapters and JSP pages.

7.5.1 Service Designer Localization

Modify the LocalStrings.properties file in the panama_pasm.zip file in the ORACLE_HOME\panama\tools\ServiceDesigner\lib directory.

7.5.2 Personalization Portal Localization

Modify the LocalStrings.properties file in the WE_ HOME/server/classes/oracle/panama/adapter/webui directory.

Multi-byte Character Support 7-3

Page 92

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

Location Contents

/ldap/LocalStrings.properties Text labels used by the LDAP adapter. /mail/LocalStrings.properties Text labels used by the Mail adapter. /papzlite/LocalStrings.properties Text labels used by the device interface to the

Personalization Portal.

7-4 Oracle9i Application Server Wireless Edition Configuration Guide

Page 93

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.5, "CopyObjects"

Utilities 8-1

Page 94

System Password Encryption/Decryption

8.1 System Password Encryption/Decryption

The Wire less 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/serve r/classes/oracle /panama/core/admi n

Then set the following property in the System.properties file:

passwordEncrypt ed=true

8.1.1 Extensibility

The SystemPasswordEn cryptionHook.cla ss identifies the encryption algorithm. To provide extensibility, the class ca n be used to invoke a user ’s algorithm in place of the default algorithm.

The default setting is:

locator.SystemP asswordEncryption Hook.class= oracle.pan ama.rt.common.Sys temPasswordEncry ption

To use an alterna te encryption algorithm, implement the following interface:

public interface Syst emPasswordEncryptio nHook { /** Encrypts the text * @param te xt the text to be encrypted * @return t he encrypted text */ public String encrypt (String text);

/** Decrypts the encrypted tex t * @param en cryptedText the e ncrypted text * @return t he decrypted text */ public String dec rypt(String encry ptedText); }

This allows you to replace the default algorithm, for example:

locator.SystemP asswordEncryption Hook.class= oracle.pan ama.MyEncryption

8-2 Oracle9i Application Server Wireless Edition Configuration Guide

Page 95

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. If the objects exist in the repository, LoadXml updates the objects.

4. If the objects do not exist, LoadXml creates them.

5. After each object type is successfully loaded, LoadXml performs a commit. The

In the unload XML result, all objects have an attribute called _objectId; this is the system unique object key. You must look up objects by unique name attribute and not the object key. If you start th e program without giving an option, all options are listed.

LoadXml

commit includes all referenced objects (dependencies).

LoadXML imports and exports the repository identified by the database connect string in the System.properties file. In the development environment, this file is located in the WE_HOME/server/classes/o r acle/panama/core/admin directory.

Wireless Edition does not validate the XML file yo u import into the repository with LoadXml. To avoid errors, work in an XML file that you have exported from the repository. This gives you a “known good” Repository XML framework for adding, removing, and modifying individual elements.

Syntax

oracle.panama.c ore.util.LoadXml [-l user name/password] [-x[adg nstu] [expr]] [-c# [-p]] [-r rmi:/ /rmi-host:port/se rver_name]

Options

The LoadXml utility accepts the following options:

Utilities 8-3

Page 96

LoadXml

Table 8–1 LoadXml Utility

Option Description

-l usr/pwd

-x Unload all repository data to stdout. The data can be filtered

-a Adapter filter.

-d Logical device filter.

-g Group filter.

-n Agent filter.

-s Service filter.

-t Transformer filter.

-u User filter. expr Name expression filter. This option can include wildcards,

-c# Upload repository data read from stdin. The argument #

-p This option activates provisioning of user data when

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.

by adding these options to the -x option.

such as: [*%?_].

is a number that, if set, causes a commit after the specified number of objects are uploaded. An argument of 0 causes a commit after a comp lete load of the XML da ta.

uploading. This mode is only used with the -c option. The provisioning upload handles the provisioning DTD, and makes it possible to create, enable, disa bl e, and remove users in the repository. This mode always creates new user s. If the createUserRoot attribute is set to YES, LoadXml creates a root folder for each user. The provisioning upload uses streaming to load users, and therefore does not resolve dependencies.

8-4 Oracle9i Application Server Wireless Edition Configuration Guide

Page 97

Option Description

Upload and Download Utilities

-r 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.

Unload Example

In this example, XML data is written to standard output.

java oracle.panama .core.util.LoadXml -l adm /adm -x > outputfile.xml

Upload Example

In this example, XML data is read from standard input. It must contain all referenced o bjects.

prompt$ java or acle.panama.core. util.LoadXml -l adm/adm -c0 < inp utfile.xml

8.3 Upload and Download Utilities

You can us e the upload and download utilities to import and export the Wireless Edition repository as an XML file. These utilities invoke LoadXml. They are located in the WE_HOME/sample directory of your development environment. You invoke

upload from a command prompt as follows: upload.bat repository.xml

This loads the contents of the file repository.xml into the repository. It accesses the repository specified by the connect string in the client-side System.properties file.

To download a repository: download.bat repository.xml This places the contents of the repository in a file named repository.xml.

Utilities 8-5

Page 98

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.

Table 8–2 Behaviors for the XML Loader in the Systems.property File

Entry Behavior

xmlloader.pathExpression Specifies the regular expression which

determines the path of the objects that you intend to upload and download.

xmlloader.activityLog Specifies the location of logging activity. xmlloader.errorLog Specifies the location for logging errors. xmlloader.createUserRoot Determines whether a root folder is to be created

xmlloader.commitFrequency Frequency in seconds to commit the uploaded

xmlloader.replaceObjects Determines whether a pre-existing objects shoul d

Note: ’All the XML Loader parameters in the System.properties

for each user when uploading provisioning data.

information to the back-end repository.

be overwritten.

file are default values that are overwritten by the XML Loader API.

8.4 Xslt

The Xslt utility is a tool you can use to test stylesh e et s. Xslt uses the XML DOM parser and the XSL processor included with the Oracle XML processor. You can use Xslt to apply the stylesheets you create to any XML document.

8-6 Oracle9i Application Server Wireless Edition Configuration Guide

Page 99

Xslt, which is a command-line utility, reads from standard input and writes its results to standard output.

Synopsis

oracle.panama.u til.Xslt [stylesh eet]

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 mystyleshee t.xsl < myxml.xml

8.5 CopyObjects

The CopyObjects utility allows you to copy services from one Wireless Edition site to one or more other sites. You can use this utility, for example, to deploy services from a testing and development environment to production servers.

CopyObjects

CopyObjects sends services to target servers as XML elements. It takes a folder object as a command-line argument. To copy a service, therefore, you must first place the service in a folder. When invoked, CopyObjects copies the folder and all its contents to the target Wireless Edition sites you specify at the command line.

Requirements

All source and target Wireless Edition servers must have the Wireless Edition RMI server running.

The basic configuration of adapters and transformers must be the same on the source and target servers. CopyObjects only sends services, links, and folders. It does not send configuration data.

Syntax

oracle.panama.c ore.util.CopyObje cts [-f folder] [-s source ][targets...]

Utilities 8-7

Page 100

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 sour c e in th e

targets The tar get Wireless Edition servers . S pec ify t a r gets in the format:

format: username/password@//hostname:port/servername

username/password@//hostname:port/servername

Example

This example copies a folder and its content from a local server to production sites at m1 and m2.

java oracle.pan ama.core.util.Cop yObjects \

-f / master/finance \

-s u ser/pw@//:2008/WE Server \ u ser/pw@//m1:2008/ WEServer \ u ser/pw@//m2:2008/ WEServer

8-8 Oracle9i Application Server Wireless Edition Configuration Guide

Oracle Audio Technologies 9i User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Send Us Your Comments

Preface

Overview

Installation Overview

1.2 Manual Configuration

1.2.1 Configure Oracle HTTP Server and JServ

1.2.2 Configure ProxyFirewall.properties

1.2.3 Start the Oracle HTTP Server

1.2.4 Wireless Edition Configuration Verification

1.3 Upgrade

Samples

1.5 Web Integration Server

Wireless Edition Client

1.6.1 Service Designer

1.6.2 Web Integration Developer

1.7 OCI8 JDBC Driver

User Provisioning

1.9 Geocoding Setup

1.10 JDBC Connection Pooling

FastForward

Introducti on

2.1.1 Features

2.2 Installation

2.2.1 System Requirements

2.2.2 Installation

2.2.2.1 On Your Own Web Serve r and JSP Engi ne

2.2.2.2 On PTG 1.1

Configuration

2.3 Configuration

2.3.0.3.1 Configuration Through Properties Files

2.3.0.3.2 Configuring Mail and Directory Parameters through request

2.3.0.3.3 Mail Configuration Class

2.3.0.3.4 Configuration of URL Adapter in PTG 1.1 ServiceDesigner

Alerts and SMS Request Listener

3.1 Overview

Alerts

3.2.1 Requ es t Qu eu e

3.2.2 Notification Queue

3.2.3 Email-based Alert

3.2.4 SMS-based Alert

3.2.4.1 SMS-C Server

3.2.4.2 SMPP Protocol

3.2.4.3 SMS Protocol

3.2.4.4 UCP Protocol

3.2.4.5 Flow-Control

3.2.4.6 Wireless Edition SMS System Account for SMS-C

3.3 SMS Request Listener

Request and Not ifi cati on Que ue Po ol

3.4.1 Request Queue Thread Pool Size

3.4.2 Notif ic at io n Queu e Th r ea d Pool Si ze

4.1 Overview

Logging

4.2 Database Logging

4.2.1 Configuring the Database Logger

4.2.2 Database Table Contents

4.3 Service Designer Logging

4.4 Server Logging

Transaction Logging

Configuring the Runtime Monitor and Management

Multiple JVM Support and Load Balancing

Overview

Multiple Instances on Sa me M ach ine as Ora cle HTTP S erve r

Multiple Instances and Oracle HTTP Server All on Different Machines

Configuring the Personalization Portal for Load-Balancing

5.5 Load Balancing

5.5.1 Load-Balancing with Cookies

5.5.2 Load Balancing Through URL Rewriting

5.6.1 Clients/Gateways Support Cookies

5.6.2 Clients/Gateways Do Not Support Cookies

5.6.3 Sample Batch File

Oracle Enterprise Manager

Overview

6.2 Prerequisites

Configuring the Server, Client, and Middle-tier

6.3.1 Configuring the Server Side

6.3.1.1 Configuring the Oracle Intelligent Agent