Oracle9i Application Server Wireless Edition Configuration Guide Release 1.1 Part Number A86701-01 |
|
This document describes the post-installation configuration of Wireless Edition. Each section of this document presents a different topic. These sections include:
The Oracle9i Application Server installation includes three options:
Wireless Edition is installed as part of each of these options. The Oracle9i Application Server Installation Guide discusses each option, and discusses the installation steps 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. |
After installation, perform the manual configuration steps described in this section:
This section describes the configuration of the Oracle HTTP Server and JServ.
Alias /portal/ "WE_HOME/server/portal/"
Alias /papz/ "WE_HOME/server/papz/"
Alias /ptgdoc/ "WE_HOME/doc/javadoc/"
ApJServMount /ptg /root
wrapper.bin= ORACLE_HOME/Apache/jdk/bin/java.exe
For Windows NT (for UNIX replace "\" with "/"):
wrapper.classpath=WE_HOME\server\classes wrapper.classpath=WE_HOME\lib\panama.zip wrapper.classpath=WE_HOME\lib\panama_core.zip wrapper.classpath=WE_HOME\lib\panama_portal.zip wrapper.classpath=WE_HOME\lib\panama_papz.zip wrapper.classpath=WE_HOME\lib\client.zip wrapper.classpath=WE_HOME\lib\server.zip wrapper.classpath=WE_HOME\lib\caboshare-opt.zip wrapper.classpath=WE_HOME\lib\marlin-opt.zip wrapper.classpath=WE_HOME\lib\ocelot-opt.zip wrapper.classpath=WE_HOME\lib\share-opt-1_1_7.zip wrapper.classpath=WE_HOME\lib\tecate-opt.zip wrapper.classpath=WE_HOME\lib\regexp.jar wrapper.classpath=WE_HOME\lib\sax2.jar wrapper.classpath=WE_HOME\lib\activation.jar wrapper.classpath=WE_HOME\lib\mail.jar wrapper.classpath=WE_HOME\lib\ldap.jar wrapper.classpath=WE_HOME\lib\ldapbp.jar wrapper.classpath=WE_HOME\lib\providerutil.jar wrapper.classpath=WE_HOME\lib\sdoapi101.jar wrapper.classpath=WE_HOME\lib\sdovis.jar wrapper.classpath=WE_HOME\lib\MapQuestX.jar wrapper.classpath=WE_HOME\lib\MQJavaCore.jar wrapper.classpath=WE_HOME\lib\RoutingJServerClient.jar wrapper.classpath=WE_HOME\lib\jai_codec.jar wrapper.classpath=WE_HOME\lib\jai_core.jar wrapper.classpath=WE_HOME\lib\jpeg_codec.jar wrapper.classpath=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. |
wrapper.env=DISPLAY=:0.0
From the X server host machine (x_server_host_name in the following example) run the following command:
xhost + <x_server_host_name>
wrapper.env=DISPLAY=<x_server_host_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 + <wireless_edition_host_name>
For Windows NT:
repositories=<ORACLE_HOME>\Apache\Jserv\servlets,<WE_ HOME>\serverportal,<WE_HOME>\server\papz
For UNIX:
repositories=<ORACLE_HOME>/Apache/Jserv/servlets,<WE_ HOME>/server/portal,<WE_HOME>/server/papz
servlets.startup=oracle.panama.ParmImpl
servlet.rm.code=oracle.panama.ParmImpl
If a proxy server is used to access an external web site from Wireless Edition, configure the ProxyFirewall.properties file:
http.use.proxy=true
http.proxy.host=www-proxy.us.oracle.com
http.proxy.port=80
To start the Oracle HTTP Server see the instructions in the Oracle9i Application Server Installation Guide.
After installation, you can verify that individual Wireless Edition components are properly configured using a desktop browser:
http://host_name.domain:7777/portal/Login.jsp
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_name.domain:7777/ptg/rm
The login page should appear. The page prompts you to enter a user name and a password.
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:
Important: The Wireless Edition installation in the following step upgrades the database schema and migrates the existing data. |
You can install the sample services and adapters into the repository after completing the steps in Section 1.2 and/or Section 1.3.
WE_HOME\sample (Windows NT) WE_HOME/sample (UNIX)
-l Administrator/manager
upload.bat samples.xml (Windows NT) upload.sh samples.xml (UNIX)
wrapper.classpath=WE_HOME\sample (Windows NT) wrapper.classpath=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. |
You should see the sample adapters and sample services in the \master\Samples folder using the Service Designer or the Personalization Portal.
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:
The Web Integration Server can also be run as a service on Windows NT.
http://host_name.domain:5555
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.
The Wireless Edition client runs only on the Windows NT platform. The client installation consists of the following
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 Guide for information on using this tool.
Web Integration Developer is a development environment for creating and testing Web Integration services written in Web Interface Definition Language (WIDL). The Web Integration Developer includes tools for publishing WIDL services for the Web Integration Server.
The Web Integration 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:
The default configuration of Wireless Edition uses the Oracle THIN JDBC driver. For a production environment it is recommended that the Oracle OCI8 JDBC driver provides improved performance, concurrency, scalability, and multi-byte support. Additionally, this driver is required if the Oracle Parallel Server option is used. the OCI8 JDBC driver is required.
To configure Wireless Edition to use the Oracle OCI8 driver:
wrapper.path=[ORACLE_HOME]\bin
db.connect.string=%WE_REPOSITORY_USERNAME%/%WE_REPOSITORY_USER_ PW%@(description=(address=(host=%WE_REPOSITORY_ HOST%)(protocol=tcp)(port=%WE_REPOSITORY_PORT%))(connect_data=(sid=%WE_ REPOSITORY_SID%))) db.driver=V8
You can integrate your repository with an existing provisioning system using one of the following:
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 LoadXML utility, see Section 7.2.
Wireless Edition provides basic geocoding through the provider MapInfo. To expand the geocoding capability to include 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:
http.use.proxy=true
http.proxy.host=www-proxy.us.oracle.com
http.proxy.port=80
Pooling for JDBC connections improves 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 9.2.
Connection pooling under Wireless Edition session management supports server environments that include short-lived threads, long-lived threads (thread pool model), or a combination of short-lived and long-lived threads. The following system properties apply to the connection pooling mechanism:
#Minimum number of connections for the connection pool db.connect.minConnections=5 #Maximum number of connections for the connection pool db.connect.maxConnections=100 #Incremental allocation of new connections to the connection pool db.connect.incConnections=1 #Time interval (in seconds) for the watchdog to find and release unused #connections to the connection pool repository.session.check.interval=1
Note: To control the maximum idle time for any database connection, configure it through the Oracle data server. |
|
![]() Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|