Oracle9iAS Wireless Release Notes Release 2 (9.0.2) Part Number A97614_01 |
|
May, 2002
Part No. A97614-01
This document summarizes the differences between Oracle9iAS Wireless and its documented functionality.
The following topics are addressed:
This section details vital issues and their solutions that must be accomplished to enable the proper functioning of Oracle9iAS Wireless.
Accomplish this step on the middle tier. To specify a complete domain in the list of Proxy "Exception Addresses", prepend the domain name with a dot ("."). Here are the steps:
http://<hostname>:1810
Here's an example:
To specify the domain "oracle.com" and the localhost in the Exception Addresses, enter "localhost|127.0.0.1|.oracle.com
" in the Exception Address input box. For more information, see Section 4.4.1: "Configuring the Proxy Server" in Oracle9iAS Wireless Getting Started and System Guide.
You may omit this step if you are completing a fresh installation.
The subscriber name argument to the ptgUpgradeRepository.sh
(for UNIX) or ptgUpgradeRepository.bat
(for Windows) script must be the DNS subdomain that the machine is registered under (that is, if the machine has a fully-qualified DNS name mymachine.foo.bar.com, then the subscriber name argument is foo
.). If for example, it is mymachine.bar.com
, then the subscriber name argument would be bar
.
You may disregard this issue if you are not running against an upgraded OID.
This version of Oracle9iAS Wireless requires a user with the dn:
cn=orcladmin, cn=Users, <default subscriber dn>
to exist in the upgraded OID. If you are using wireless functionality (for example, Self Registration), with user-related model APIs against this OID instance, then this user should be granted CREATE/ DELETE/EDIT privileges for all the users in the default subscriber.
Before installing Oracle9iAS Wireless against an upgraded OID, the above-mentioned entity must be created with appropriate privileges. For details on creating such an entity with appropriate privileges refer to Chapter 12 - "Managing Oracle Internet Directory" in Oracle 9iAS Administrator's Guide, and Chapter 13 - "Directory Access Control" in Oracle Internet Directory Administrator's Guide.
If both the Infrastructure and Middle tiers are installed on the same machine, and the Enterprise Manager daemon running on that computer is referring to the Infrastructure home, then the "Register Oracle Portal Provider for Wireless System Manager" and "Register Oracle Portal Provider for Wireless Customization" from the Wireless site will throw "java.lang.NoClassDefFoundError" errors.
In the orion-web.xml
file of the Infrastructure install, the Portal jars (pdkjava.jar
and ptlshare.jar
) should refer to the location of the middle-tier installation.
For example, if the Infrastructure is installed in:
/private/ias20_infra/
and the Middle Tier is installed in:
/private/ias20_midtier/
then the following entries in the Enterprise Manager daemon orion-web.xml
:
<classpath path="/private/
ias20_infra/portal/jlib/pdkjava.jar"/>
<classpath path="/private/
ias20_infra/portal/jlib/ptlshare.jar"/>
should be replaced with:
<classpath path="/private/
ias20_midtier/portal/jlib/pdkjava.jar"/>
<classpath path="/private/
ias20_midtier/portal/jlib/ptlshare.jar"/>
Restart the opmn process for the changes to take effect.
After accessing a large number of different module services or HTTP adapter-based services (with JSP-based content sources hosted on the same Java VM), some of the services fail with a 'service error'. Accessing the target JSPs results in a 'NoClassDefFound' exception. Restarting the server corrects the problem.
When an application is loaded for the first time, the OC4J classloaders read the class bytes in the library jars into memory; it does so without the classes being referenced (because the application instantiates classes from an in-memory array).
Class files resulting from compiling JSP files are loaded dynamically. In time, the heap gets filled up and newer classes from compiled JSPs cannot be read into the memory array(s), nor instantiated on the heap. Hence the top-level classloaders fail with a 'NoClassDefFound' exception. In subsequent lookups, the 'OutOfMemoryError' is not thrown since the JDK classloader loadClass( )
implementation semantics prescribe NOT reloading classes that could not deterministically be loaded earlier.
To determine if this is the case, check the number of OutOfMemoryErrors in sys_panama.log
. That number should be the same as the number of times the server has been restarted.
If it is the case, increase the heap-size for the VM in opmn.xml
by modifying the Java option subelement of the OC4J element corresponding to the instanceName OC4J_Wireless.
http://hostname:1810
ias_admin/<password supplied at install time>
For more information, see: "Setting the JVM Heap Size for OC4J Processes" in Chapter 6 of Oracle9i Application Server Performance Guide.
Accomplish this step on the infrastructure. This version of Oracle9iAS Wireless relies on the Provisioning Integration Service provided by the Directory Integration Platform to be notified of user and/or group changes in OID. These changes are stored in the OID change log and are appropriately filtered by the Provisioning Integration Service before being delivered as change events to this application.
Even if you are not deploying the OID server in replication mode, ensure that the directory administrator starts up the replication server in order to periodically purge unnecessary change log entries.
This can be done by starting the replication server using the following command:
$ORACLE_HOME/bin/oidctl connect=<net_service_name> server=oidrepld
instance=1
flags="-p <ldapserver_port_number>" start
For more information on starting and stopping the replication server, see Chapter 3: Preliminary Tasks and Information in the OID Administrator Guide.
Without this periodic cleanup, the OID change log can grow to occupy the entire file system causing the OID service to become unavailable. The need to start the replication server to purge the change log is only a temporary measure; it will be automatically addressed in a future release.
Accomplish this step on the middle tier and infrastructure. Clocks on all machines that are part of an Oracle9iAS instance must be synchronized. This can be done by running NTP (Network Time Protocol) daemons on all machines running the various components of an Oracle9iAS deployment. Run xntpd
(or similar daemon processes) on most UNIX-like architectures and abouttime
or similar software for Microsoft Windows platforms.
This is a requirement because several interdependent components require that clocks be synchronized for them to work coherently. All platforms are affected by this requirement.
Can we document the "date mismatch issue" in the Release Notes for NT.
Accomplish this step on the middle tier (UNIX only). Due to a JDK bug, HTML screens may have broken image tabs. To work around this issue, modify opmn.xml
in: [Oracle Home]/opmn/conf
Modify the value of the DISPLAY property to point to a machine with an X server running. Also, be sure to allow other X-windows clients to connect to that machine. To achieve this, run the xhost
command on the machine running the X-server.
Here is an opmn.xml
example:
<prop name="DISPLAY" value="xmachine.us.oracle.com:0.0"/>
This affects all UNIX platforms.
The Modules included in this production release are complete and functional. There are, however, important updates to the modules that will soon be released as a patch.
You can use the Modules as they are, but be advised that the patch will make significant database and other changes, requiring you to discard previous end-user personalization information. You will not be able to migrate your previous information when you install the patch.
Accomplish this step on the middle tier. Due to a bug, none of the applications will be auto-started (that is, an application is started only when the first request for that application arrives). To change this behavior to auto-start applications (especially for push and async applications), edit the file config/default-web-site.xml
to add a load-on-startup attribute to the web-app tag, setting the value of the attribute to True.
For instance, to auto-start the async application which resides in the
OC4J_Wireless product group, edit the file[Oracle Home]/j2ee/OC4J_Wireless/config/default-web-site.xml
and change the web-app tag for the async application such that it looks like the entry below:
<web-app application="async" name="async-web" root="/async" load-on-startup="true"/>
In this release, there can be only one Async server taking requests. Configuring and starting multiple ASK is not supported.
Accomplish this step on the middle tier. Due to a bug, HTML pages (such as System Manager, customization, etc.) may not work with NetScape 4.7. The workaround for this problem is to re-register the mod_osso
partner app to use the WebCache port number, rather than the Oracle HTTP Server port number. For the details and the exact steps as to how to perform this, please refer to the Oracle HTTP Server Release Notes.
All platforms are affected by this.
Pre-built demonstrations have been provided to preview some of the Oracle9iAS Wireless functionality available to you. These demonstrations are located at: <hostname>:port/ptg/rm (<hostname>:port/ptg/rm
is the Wireless view of the Oracle9i Application Server.). Follow these steps to view demonstrations included in Oracle9iAS Wireless:
<hostname>:port/ptg/rm
http://<hostname>:1810
This section contains information that enables you to ensure that you've correctly set up Oracle9iAS Wireless for use.
After installation and configuration, ensure that you are using the correct URLs, port numbers, and login information.
To ensure that you are using the correct port number, check the port number for Oracle9iAS Wireless stored in:
[Oracle home]/install/portlist.ini
For more information on port usage, see Oracle9i Application Server Installation Guide and Oracle9i Application Server Administrator's Guide.
To access Oracle9iAS Wireless, use the following URLs and other information:
Management of Oracle9iAS Wireless Server is accomplished through Oracle Enterprise Manager. To access the System Manager for Oracle9iAS Wireless through the Oracle Enterprise Manager (OEM) console:
For more information, see Oracle9iAS Wireless Getting Started and System Guide.
You can find additional and updated documentation and other information on Oracle9iAS Wireless through the Oracle Technology Network (OTN). OTN provides developers with the latest information on Oracle's products and technologies. To access OTN, visit:
http://otn.oracle.com/products
You may disregard this issue if your Infrastructure and Middle tiers are installed on separate machines.
There is a generic error that affects some Oracle9iAS components, including Oracle9iAS Wireless. This errors occur when you use Microsoft Internet Explorer to access the System Manager on a machine that has both infrastructure and a middle tier installed on it. You may encounter the following errors:
Following are notes on the Messaging System for this release.
If you do not remove the Push driver, then Wireless cannot send an SMS message. The SMS driver does not receive the delivery request because the system still considers the Push driver capable of delivering SMS. The delivery request remains in the system until a future instance of the Push driver becomes available.
Due to a bug, Message IDs returned from the Send methods of Push or Pushlite may not match the order of Recipients' addresses as they were input.
The first time you attempt Repository Upload before Single Sign-On, you will be redirected to the Single Sign-On page. After you type in your username and password, the browser shows an empty page, with the URL pointing to http://<hostname>/webtool/provisioning/upload.jsp. Click the Back button three times, then you will see the Repository Object Upload page again. Click the Upload button, and the upload process will be finish successfully. This behavior does not reoccur in subsequent download/upload attempts.
The first time you attempt Repository Download, you will be redirected to the Single Sign-On login page (since you have not previously logged on). After login, a dialog box appears asking where to save the file. Specify the file location and click OK. The page remains at the SSO URL and does not return to the Site tab of Wireless page. This behavior does not reoccur in subsequent download/upload attempts.
The password policy in OID can be configured by Oracle9iAS administrators to specify user password life, and how soon before password expiration users are prompted to change their passwords. Users must apply the rdbms 9.0.1.3 patchset to use this functionality. See "Password Policies" in Chapter 3, "Directory Enabled Single Sign-On" in "Oracle9iAS Single Sign-On Administrator's Guide" for more details on Change Password Functionality.
Caching of forms in WebCache is not supported because session variables cannot be substituted (as they are hidden fields) in forms. Currently this is true only for TINY_HTML, so technically one should still be able to cache forms for other devices. But, as other transformers are modified to use hidden fields for other devices (in order to support POST requests), this limitation will also apply to them.
When Oracle Web Cache sends requests to Oracle9iAS Wireless, Oracle Web Cache allows the Oracle9iAS Wireless server 30 seconds to generate a response. In some extreme conditions, such as when Oracle9iAS Wireless is under a heavy load, it may not be able to respond within the stipulated 30 seconds, in which case Oracle Web Cache sends a network apology page to the browser.
If 30 seconds is not sufficient, then you can change the default settings of the OSSEND_TIMEOUT
and OSRECV_TIMEOUT
attributes in the Oracle Web Cache configuration file internal.xml
(this is in the Oracle Web Cache installation directory):
OSSEND_TIMEOUT
--Network round-trip time (latency) between Oracle Web Cache and the application Web server. The 20 second default of the OSSEND_TIMEOUT
attribute is usually sufficient for most operating systems.
You can determine the latency to the application Web server by issuing the following command from the Oracle Web Cache computer:
ping -s application_Web_server
This command provides output similar to the following:
PING sales.us.acme.com: 56 data bytes
64 bytes from sales.us.acme.com (130.35.45.34): icmp_ seq=0. time=20. ms
64 bytes from sales.us.acme.com (130.35.45.34): icmp_ seq=0. time=21. ms
If the time value is over 20 seconds, then increase the OSSEND_TIMEOUT
attribute value.
OSRECV_TIMEOUT
--Latency and application Web server processing time. The default is 30 seconds.
You can determine the processing time by sending a sample request to the application Web server, then monitor the time to process the request. If the processing time is over 30 seconds, then increase the OSRECV_TIMEOUT
attribute value.
To change these default settings:
internal.xml
file: <CALYPSONETINFO/>
<CALYPSONETINFO/>
line as follows:
OSSEND_TIMEOUT
attribute as follows: <CALYPSONETINFO OSSEND_TIMEOUT="seconds"/>
OSSRECV_TIMEOUT
attribute as follows: <CALYPSONETINFO OSSRECV_TIMEOUT="seconds"/>
OSSEND_TIMEOUT
and OSSRECV_TIMEOUT
attributes as follows: <CALYPSONETINFO OSSEND_TIMEOUT="time" OSRECV_TIMEOUT="time"/>
There have been some recent changes to the XML Tag Glossary:
SimpleImage supports an alt
attribute which provides alternate text for display devices, and an alternate .wav file for the voice deviceclass devices. Here is an example:
<SimpleBind> <SimpleMatch> </SimpleMatch> <SimpleTask> </SimpleTask> <SimpleDisplay> <SimpleTextItem deviceclass="voice"> <SimpleAudio src="http://somehost/audio.wav"/> </SimpleTextItem> <SimpleTextItem deviceclass="pda, microbrowser"> Hello welcome </SimpleTextItem> </SimpleDisplay> </SimpleBind>
In this release, it is not possible to create a quicklink for a module.
When using the pre-built Oracle9iAS Wireless Messaging/Push applications and when developing your own applications with messenger.oracle.com, the required format for SMS, voice (telephone) and fax numbers is:
1-aaa-nnnnnnn
Where aaa
is the area code, and nnnnnnn
is the telephone number.
The Calendar and Tasks Modules require configuration. In Oracle9iAS Wireless Developer's Guide, you are instructed to install the Lotus Domino Toolkit for Java/CORBA, add NCSO.jar to the classpath for Oracle9iAS Wireless 2.0. Installing the toolkit creates "DTJava" directory on the file system.
Please note the following cautions:
ServerTasks=<other tasks>,http,diiop
A list of known bugs and their workarounds for Oracle Mobile Studio follows.
Generic to all platforms.
If, for some reason, the Wireless schema (that is, the database connect string and/or password have been modified to point to a different schema, the targets.xml
file on the middle tier must be modified to reflect this change. Edit targets.xml
in Oracle9iAS Wireless Release 9.0.2 OracleHome/sysman/emd
, to make the following changes (in bold) to the target entry corresponding to oracle_wireless.
<Property NAME="ConfigDBPort" VALUE="port number of new database"/>
<Property NAME="ConfigDBpassword" VALUE="schema password of new database" ENCRYPTED="FALSE"/>
<Property NAME="MachineName" VALUE="machine name of new database"/>
<Property NAME="ConfigDBSID" VALUE="SID of new database"/>
<Property NAME="ConfigDBMachineName" VALUE="machine name of new database"/>
<Property NAME="UserName" VALUE="schema name of new database" ENCRYPTED="FALSE"/>
<Property NAME="Port" VALUE="port number of new database"/>
<Property NAME="SID" VALUE="SID of new database"/>
<Property NAME="ConfigDBUserName" VALUE="schema name of new database" ENCRYPTED="FALSE"/>
<Property NAME="ORACLE_HOME" VALUE="/private/ias/OraHome1"/>
<Property NAME="password" VALUE="schema password of new database" ENCRYPTED="FALSE"/>
Web Integration Server and Developer are not included in this release.
Web Component Developer is a Java-based GUI tool that enables you to create Web components that can be delivered by Web Component Developer. There is a know issue in Web Component Developer when generating Web Component Definition files. The problem renders development of composite Web Components not possible. This known bug is scheduled to be fixed and delivered to customers via Automated Release Updates (ARU).
Generic to all platforms.
A condition has been discovered that will cause the Oracle9iAS Wireless status to be displayed (in Oracle Enterprise Manager) as Down, even though it is in fact Up. This occurs when more than one Oracle home directory exists on a single machine.
If you have more than one Oracle Home directory on a single machine, make the following changes to the Oracle9iAS Middle Tier (including Oracle9iAS Wireless) installation:
(UNIX only) Add the following line to the start of ORACLE_HOME/Wireless/sample/runpanamaserver.sh, just after the first line ("#!/bin/sh"):
ORACLE_HOME=${1}
(Windows only) Add the following line to the beginning of ORACLE_HOME\Wireless\samplerunpanamaserver.bat:
set ORACLE_HOME=%1
Oracle is a registered trademark, and Oracle9i, OracleMobile, PL/SQL, SQL*Net, and SQL*Plus are trademarks or registered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners.
Copyright © 2002 Oracle Corporation.
All Rights Reserved.
|
![]() Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|