Skip Headers
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for hp-ux PA-RISC (64-bit)
B15511-05
  Go To Documentation Library
Home
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

10 Oracle Application Server Wireless

This chapter describes issues with Oracle Application Server Wireless (OracleAS Wireless). It includes the following topics:

10.1 General Issues

This section describes general issues encountered in OracleAS Wireless. It includes the following topics:

10.1.1 EDGE_CREATE Script Errors

Some users have reported receiving an error when trying to create the edge schema on an Oracle Application Server 10g installation. This is because the dbms_aq package is often locked by other sessions when one tries to create the edge user (using the create_edge_user.sql script). When trying to create the edge schema (after connecting as edge/<password>@<db name> and running edg_create_streams.sql), table and queue creation fails.

To fix this problem:

  1. Unlock the package. This is a database administrator function. The session locking the package must relinquish the lock. This may require restarting the entire database instance. It ensures that no session is holding a lock on the dbms_aq package.

  2. Explicitly give execute privilege to the edge user on the dbma_aq package:

    1. Log in as system.

    2. Execute SQL> grant execute on dbms_aq to edge;

  3. Connect as edge/<password>@<db name> and run edg_create_streams.sql, again.

10.1.2 Database Lock Hangs STREAMS Dispatcher

The STREAMS dispatcher runs as a database job. If your PL/SQL development activities require you to constantly recompile packages, a database lock can hang the STREAMS dispatcher. Generally, you can restart the dispatcher by executing:

exec edg_utl.deschedule_job;

To check whether or not the job exits gracefully, check the edg_jobs table. Run the following query:

select component_name, status from edg_jobs;

If the job has exited gracefully, this query will return no rows. If this job is in the process of exiting, the status will be Stopping. It may take up to 30-40 seconds for the job to finish completely. If this query continues to return a status of Stopping, the dispatch job has frozen. To correct this, first clear this row from the table. Execute:

delete from edg_jobs where component_name = 'EdgeDispatchJob';

Next, restart the database. Once the database is restarted, restart (or reschedule) the job. Do this by executing:

exec edg_utl.schedule_job;

The job will restart. To verify, use this query:

select component_name, status from edg_jobs;

This should return a status of Started.

10.1.3 SMS/EMS Messages Contain MobileXML or XHTML Tags, not Plain Text

XMSC is disabled, by default, during 10.1.2 installation. In this state, when messages are sent (using XMS) to a 9.0.4 instance (using PushDriver), recipients receive the original markup. This problem occurs with MobileXML and XHTML content for SMS or EMS channels.

The workaround for this situation is to enable XMSC on the local instance. For more information on XMSC, see OracleAS Wireless Administrator's Guide.

10.1.4 OracleAS Wireless Patch Required after XDK Patch is Applied

If you are using Apache Axis and the Wireless feature in Oracle AS 10.1.2, and you have already applied a Release 10.1.2 XDK patch, you must download an OracleAS Wireless one-off patch from Metalink.

The Wireless one-off patch fixes a problem introduced by the XDK fix. If you do not apply the Wireless patch, logging in from the voice channel will fail.

10.1.5 Wireless Middle Tier Deconfiguration Runs for a Long Time

Deconfiguration of the last Wireless middle tier may take a long time (about one hour); do not terminate the process while it is running.

10.1.6 Broken Icons in Wireless Device Portal Homepage

Icons on the Wireless Device Portal Home page for an upgraded instance in SSL mode are broken. This is because Mod rewrite of the icons in an SSL configuration does not work.

To fix the problem, you must enable rewrite in SSL mode by adding the following entries to the SSL Virtual Host configuration:

RewriteEngine on
RewriteOptions inherit

Here is a sample entry:

<VirtualHost _default_:4444>
# General setup for the virtual host
DocumentRoot "D:\Portal1012\Apache\Apache\htdocs"
@ ServerName iwinrea05.us.oracle.com
ServerAdmin you@your.address
ErrorLog "|D:\Portal1012\Apache\Apache\bin\rotatelogs logs/error_log 43200"
TransferLog "|D:\Portal1012\Apache\Apache\bin\rotatelogs logs/access_log 43200"
Port 443

10.1.7 HDML Error When Using Expense Demo Application

A problem has been reported by users running the Expense Demo application on HDML-enabled devices. An error may appear when one attempts to click the Approve or Reject button using an HDML-enabled device to access the built-in Expense Demo application in Device Portal. Users should avoid using the Approve/Reject functionality for this demo when using HDML-enabled devices.

10.2 Configuration Issues and Workarounds

This section describes OracleAS Wireless configuration issues and workarounds. It includes the following topic:

10.2.1 Updated Transformer Stylesheets Patch Required after Upgrade

If you are upgrading from Release 9.0.2 to Release 10g (9.0.4), and then to Release 10.1.2, you must download the updated transformer stylesheets from the Oracle Mobile Tech Center (http://www.oracle.com/technology/products/iaswe/devices/index.html) and apply the stylesheets to the instance. Detailed instructions are included as part of the transformer stylesheets bundle. If you do not apply this update, service names rendered on the devices will be prefixed with a colon and an underscore (:_).

10.3 Documentation Errata

This section describes documentation errata for OracleAS Wireless. It includes the following topics:

10.3.1 Sensor Services Configuration Change

On page 4-36 of Oracle Application Server Wireless Administrator's Guide, replace Step 2 with the following:Add the oc4j.jar and the edgeclient.jar libraries to the classpath section of opmn.xml (located in the ORACLE_HOME/opmn/conf/ directory) by adding the following lines under the process type with the ID of "edgeserver_server":

<environment>
<variable id="CLASSPATH" value="$ORACLE_HOME/j2ee/home/oc4j.jar" append="true"/>
<variable id="CLASSPATH" value="$ORACLE_HOME/wireless/lib/edgeclient.jar" append="true"/>
<environment>

10.3.2 Correction to Resetting the Password Command

In Section.5.5.2, Resetting the Password in Oracle Application Server Wireless Administrator's Guide, there is an error in the command syntax (an extra comma appears). Here is the correct command:

assignUserSecurityAdminsPrivilege.sh cn=orcladmin welcome1

10.3.3 Correction to SQL Filename

In Section 13.2.4, Setting Up Streams Support and Sensor Data Archive in Oracle Application Server Wireless Developer's Guide, there is an error in the name of a SQL file. In Example 13-7, the step detailing how to create the Edge schema should be:

C:/> cd /oracle/edge

C:/oracle/edge> sqlplus system/manager@mydb @create_edg_usr.sql

In the document, the original filename had an extra e.