|Oracle Voice and Wireless Release Notes
Release 1 Version 9.0.3
Part Number B10089_01
Part No. B10089-01
This document summarizes the differences between Oracle Voice and 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 Oracle Voice and 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:
Domain names specified in the exception addresses should be prepended with a ".". For example, to specify the domain "oracle.com" in the Exception Addresses use ".oracle.com" instead of "*.oracle.com" or "oracle.com".
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 Oracle Voice and 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
You may disregard this issue if you are not running against an upgraded OID.
This version of Oracle Voice and 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 Oracle Voice and 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 Voice and Wireless site will throw "java.lang.NoClassDefFoundError" errors.
orion-web.xml file of the Infrastructure install, the Portal jars (
ptlshare.jar) should refer to the location of the middle-tier installation.
For example, if the Infrastructure is installed in:
and the Middle Tier is installed in:
then the following entries in the Enterprise Manager daemon
should be replaced with:
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; these do 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.
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 Oracle Voice and 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
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.
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
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
<prop name="DISPLAY" value="xmachine.us.oracle.com:0.0"/>
This affects all UNIX platforms.
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
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"/>
Accomplish this step on the middle tier. Due to a bug, HTML pages (such as System Manager, 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.
This section contains information that enables you to ensure that you've correctly set up Oracle Voice and Wireless for use.
Ensure you perform a full offline backup before installing Oracle Collaboration Suite into an existing Oracle9iAS 220.127.116.11 installation. If you later want to rollback to your old infrastructure, you will need to restore your previous database.
This note is applicable only to deployments in which an Oracle Collaboration Suite middle-tier is installed against an existing Oracle9iAS 18.104.22.168 infrastructure (or an infrastructure upgraded to Oracle9iAS Wireless 22.214.171.124). In such cases, installing Oracle Collaboration Suite middle-tiers will cause the Wireless schema to be upgraded to the Oracle Collaboration Suite schema. The Voice and Wireless component installed in the Oracle9iAS 126.96.36.199 Oracle_Home will not function.
The workaround for this situation is to upgrade all existing Oracle9iAS 188.8.131.52 middle-tiers to Wireless 184.108.40.206. The Wireless 220.127.116.11 patch is distributed via Oracle Technology Network (http://otn.oracle.com).
Furthermore, the configuration parameters for the Mobile PIM applications will be overwritten with Oracle Collaboration Suite settings. The Mobile PIM applications installed in the Oracle 9iAS 18.104.22.168 Oracle_Home will not function.
This note applies to all platforms.
Before you upgrade Oracle9iAS version 9.0.2 to Oracle Collaboration Suite, backup your repository first (the Oracle9iAS version 9.0.2 infrastructure wireless schema is upgraded when you install Oracle Collaboration Suite).
If you downgrade to Oracle9iAS version 9.0.2 in the future, you can restore the backup repository. No middle-tier downgrade is needed because the Oracle Collaboration Suite middle-tier is installed in a different ORACLE_HOME than the Oracle9iAS version 9.0.2 middle-tier.
Oracle9i Recovery Manager User's Guide
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 Oracle Voice and Wireless stored in:
For more information on port usage, see Oracle9i Application Server Installation Guide and Oracle9i Application Server Administrator's Guide.
To access Oracle Voice and Wireless, use the following URLs and other information:
|Component||URL||Port number and login|
Oracle Voice and Wireless Device Portal
Enter your user name and then enter your password. If you are an administrator, enter orcladmin as your user name. The password for orcladmin is what you supplied at installation time for ias_admin.
Oracle Voice and Wireless System Manager Portal
Management of Oracle Voice and Wireless Server is accomplished through Oracle Enterprise Manager. To access the System Manager for Oracle Voice and Wireless through the Oracle Enterprise Manager (OEM) console:
|Component||URL||Port number and login|
Oracle Enterprise Manager
Enter your OEM user name (ias_admin is the default) and the password you supplied at installation.
For more information, see Oracle9iAS Wireless Getting Started and System Guide.
You can find additional and updated documentation and other information on Oracle Voice and Wireless through the Oracle Technology Network (OTN). OTN provides developers with the latest information on Oracle's products and technologies. To access OTN, visit:
The Oracle telephone number for accessing Voice and Wireless is contained in the
welcome.uix file, and is displayed on the right-hand side of the interface. This telephone number is only for Oracle-hosted instances. Administrators must change the access number to their own corporate numbers to customize the information for their own instances.
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.
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 Oracle Voice and 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
<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
<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
<Property NAME="ORACLE_HOME" VALUE="/private/ias/OraHome1
<Property NAME="password" VALUE="schema password of new database
In Oracle9iAS 902, wireless applications cannot be clustered using the Oracle9iAS clustering mechanism. However, it is still possible to configure Oracle9iAS 902 such that a high-availability deployment can be achieved. Complete the following steps for high-availability deployment.
[oracle home]/dcm/bin/dcmctl stop
[oracle home]/bin/emctl stop
[oracle home]/opmn/conf/ons.confon each of the mid-tiers and on the infrastructure tier contains IP-address entries for all the other tiers. If not, file and add missing IP-address entries.
opmn.xml, a typical entry to start 4 OC4J processes in the default island would be of the form:
<oc4j maxRetry="3" instanceName="OC4J_Wireless" gid="OC4J_Wireless" numProcs="4">
[oracle home]/Apache/Apache/conf/mod_oc4j.conf), modify the mount-point entries for the Wireless runtime. If two mid-tiers [M1 and M2] are used, the entries should be of the form:
Oc4jMount /ptg instance://m1.c1.mysite.com:OC4J_Wireless,m2.c2.se4637-u-sr006.us.oracle.com:OC4J_Wireless
Oc4jMount /ptg/* instance://m1.c1.mysite.com:OC4J_Wireless,m2.c2.se4637-u-sr006.us.oracle.com:OC4J_Wireless
c2are the respective Oracle9iAS 902 instance names and can be determined by running the command:
[oracle home]/dcm/bin/dcmctl whichInstance.
[oracle home]/dcm/bin/dcmctl updateConfigto update the DCM repository with the configuration file changes.
[oracle home]/dcm/bin/dcmctl getReturnStatusand wait until the command exits. This confirms that the changes have been propagated to the DCM repository.
<orion-web-app>tag in the file
[oracle home]/dcm/bin/dcmctl start.
[oracle home]/bin/emctl start
Currently, high-availability support is only available for the core server runtime (by default mapped to the URI
For more information, refer to the OC4J documentation.
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.