Oracle® Application Server Release Notes
10g (9.0.4) for Solaris Operating System (SPARC) Part No. B10629-15 |
|
![]() Previous |
![]() Next |
This chapter describes issues with Oracle Application Server Wireless (OracleAS Wireless). It includes the following topics:
This section includes information and workarounds for general issues in OracleAS Wireless. It includes the following topics:
Section 15.1.2, "Performance Optimization and JSP Files Modification"
Section 15.1.4, "Multi-byte Usernames in Jabber Not Supported"
Section 15.1.10, "Errors with Localized Voice Message for Device Validation in Customization Portal"
Section 15.1.11, "Unavailable Functionality for Re-Created SSO Users"
Section 15.1.12, "Working with Signature Capture Form Control"
Section 15.1.13, "Integrating Oracle Application Server Wireless with Web Cache"
Section 15.1.14, "Integrating Oracle Application Server Wireless with Oracle Portal"
Section 15.1.15, "Oracle Application Server Wireless log.xml File does not Support NLS"
Section 15.1.16, "POST Method is Not Supported by All Markup Languages"
Section 15.1.17, "Model Object Changes Not Propagated Across Applications"
Section 15.1.20, "Webclipping Output May be Displayed in Different Language"
Section 15.1.21, "Avoid Sending Short Message with Japanese Language Strings"
Section 15.1.22, "Do not Store Messages with Korean Characters"
Note: For more information about Performance issues and strategies, see the OracleAS Wireless section of Oracle Technology Network. |
To use Multi-Channel Gateway, you must create and deploy your web application. You can use any web technology to develop your application. You can use either static or dynamic pages. Also, you can use either Mobile XML or XHTML markup language. The only requirement is that the application is accessible through HTTP(S) protocol. You application may or may not run on the same machine as the Multi-Channel Gateway.
For simplicity, we assume that the application is a simple JSP (Hello.jsp
). The URL to access this JSP directly is: http://myhost:8080/jsp/Hello.jsp
.
The Multi-Channel Gateway is another web application that can be accessed using the following URL: http://hostname:7777/mcs/remote/
(7777
is the default port for Oracle9iAS Wireless). But by accessing the Multi-Channel Gateway URL, you will not get any content because the Multi-Channel Gateway does not produce content. In order to access your own application (the content source) from your device through the Multi-Channel Gateway you must specify a special URL. To illustrate how that URL is created, consider the sample URL:
http://myhost:8080/jsp/Hello.jsp
The URL that you must enter in your device is:
http://hostname:7777/mcs/remote/http/myhost/8080/jsp/Hello.jsp
Here is how the above URL was created:
Get the basic Multi-Channel Gateway URL. That is, http://hostname:7777/mcs/remote/
Create the absolute URL (including the port number even if you use the default port number: 80
for HTTP and 443
for HTTPS) to your application.
Replace the://
and:
in your application original URL with /
(That is, change from http://myhost:8080/jsp/Hello.jsp
to http/myhost/8080/jsp/Hello.jsp
Append the modified URL to the Multi-Channel Gateway URL.
Passing parameters to your web application is very simple. Just use the standard URL syntax and append the query string at the end of the URL.
For example: If you want to pass fname
and lname
parameters to your Hello.jsp
then use the following syntax:
http://hostname:7777/mcs/remote/http/myhost/8080/jsp/Hello.jsp?fname=John&lname=Doe
When a request is received from the user device to the Multi-Channel Gateway, it recreates the original application URL, that is:
http://myhost:8080/jsp/Hello.jsp
and sends a request to that URL. The Multi-Channel Gateway uses the same HTTP method that the user device used to send the request (If the user device used GET
, then the Multi-Channel Gateway will use GET
to access the back end application. Currently only GET
and POST
are supported.)
In general, Oracle Application Server Containers for J2EE (OC4J) examines JavaServer Pages (JSP) files to detect changes, then recompiles. However, this OC4J behavior was changed in regards to the JSP files that are deployed inside the ptg web application.
If you make changes to these included, precompiled JSP files, OC4J will not detect and compile the changes in those JSP files.
See: For more information on OC4J Configuration, see "JSP Configuration Parameters" in Oracle Application Server Containers for J2EE Support for JavaServer Pages Developer's Guide. |
For example, all JSP files that are deployed inside the ptg web application are precompiled. If for some reason you want to modify those JSP files, then you can no longer use the precompiled class files; you must change the OC4J settings to enable JSP compilation. To do that, modify the web.xml
file for the ptg application, located in:
[ORACLE_HOME]/OC4J_Wireless/applications/ptg/ptg-web/WEB-INF/web.xml
.
In order to avoid this problem (in which modifications to JSP files do not take effect), and to optimize the performance of some of the JSP files included in Oracle Application Server Wireless, you must modify the web.xml
file, as detailed below:
Delete the following from the file:
<!-- WARNING!!! Overridden JSP engine settings With this configuration the JSP files in this application will NOT be recompiled. Any changes to the JSP source files will NOT take effect. If you want to switch back to the default JSP engine settings simply comment out the servlet declaration and mapping for the jsp servlet below. --> <servlet> <servlet-name>jsp</servlet-name> <servlet-class>oracle.jsp.runtimev2.JspServlet</servlet-class> <!-- you can disable page scope listener if you don't need this function. --> <init-param> <param-name>check_page_scope</param-name> <param-value>true</param-value> </init-param> <!-- you can set main_mode to "justrun" to speed up JSP dispatching, if you don't need to recompile your JSP anymore. You can always switch your main_mode. Please see our doc for details --> <init-param> <param-name>main_mode</param-name> <param-value>justrun</param-value> </init-param> <load-on-startup>0</load-on-startup> </servlet> <servlet-mapping> <servlet-name>jsp</servlet-name> <url-pattern>/*.jsp</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>jsp</servlet-name> <url-pattern>/*.JSP</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>jsp</servlet-name> <url-pattern>/*.jspx</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>jsp</servlet-name> <url-pattern>/*.sqljsp</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>jsp</servlet-name> <url-pattern>/*.SQLJSP</url-pattern> </servlet-mapping>
You must also delete the ORACLE_HOME/j2ee/OC4J_Wireless/applications/ptg/ptg-web/WEB-INF/classes/_modules directory, and all class files in the ORACLE_HOME/j2ee/OC4J_Wireless/applications/ptg/ptg-web/WEB-INF/classes directory whose names start with an underscore ( _ ).
Restart the OC4J_Wireless application.
The following Messaging issues exist:
Due to a bug in the device, sending MMS messages with the Subject containing non-ASCII characters to the Nokia 3650 is not supported.
Sending SyncML server settings to the Nokia 3650 is not supported.
All pre-seeded site-level drivers are enabled by default. You can disable unwanted drivers for better performance.
Messaging Transport supports sending messages in English only over Enhanced Messaging Services (EMS). Other languages are supported on SMS and MMS.
Jabber, the backend used with Instant Messaging, does not support multi-byte usernames; the Instant Messaging module consequently does not support multi-byte usernames.
In the User Interface and documentation, all references to XMSDriver should read PushDriver.
The Push SOAP URL has changed in this release. If you are using the XMS client against a newly installed instance of Oracle Application Server Wireless, the client must be updated to use the new URL. By default, the new URL will be /xms/webservices
(rather than /push/webservices
) as in earlier releases.
If the instance has been upgraded from the 9.0.2 to the 9.0.4 release, the old URL (/push/webservices
) will still be valid, though the application will in fact be running the 9.0.2 code base. As such, this URL is intended for backward compatibility only; you should update the clients of the SOAP API to use the new URL (/xms/webservices
).
MXML messages containing an image reference with the attribute addImageExtension=true
, when sent using XMS to an email recipient, may appear with broken in-line images on certain email clients. The workaround for this problem is to:
Go to the Foundation tab in Oracle Application Server Wireless Tools.
Select the ASYNC device.
Click Edit.
Go to the Browser section and navigate to the Image File MIME types table.
Move the following MIME types from the left pane to the right pane:
image/bmp bmp
image/png png
image/tiff tif
image/gif gif
image/jpeg jpg
Click Apply to save the changes.
Notification messages sent through email to users that have a sending window specified in their contact rules may be delivered prematurely. That is, if a notification is generated at 9:00AM, and the user has specified in his contact rules that he does not want any emails until 10:00AM, the message will be sent immediately, rather than delayed for 60 minutes.
There is no workaround for this issue.
This section describes issues with XHTML and XForms. It includes the following topics:
To develop Async services using XForms, item element, instead of itemset, should be used to represent the option list for the elements select
and select1
.
The browser Back button cannot be (reliably) used with XForms web applications. Oracle Application Server caches the state of a form on the server to support multiple round trips between the browser and the Application Server. When using the browser Back button, the browser (cache) does not fetch the current state from the server; this may result in a conflict. Also on certain actions (such as XForms submit
) the Application Server (after the submit) clears the state (on the server), and the server throws an error if resubmit is tried (using the browser Back button).
XForms uses the select1
and select
controls to show the intent that one or more may be selected from a list of values. To show radio buttons, checkboxes or select lists, use these controls. Also use the appearance attribute to control the type of select1
or select
the UI will display. Use appearance="full"
to display a radio button (in the case of select1
) or checkbox (in the case of select
).
When XForms documents use the post submission method, the XForms processor does not submit the xmlns
namespace attributes (default namespace and namespace prefixes used) in the submitted XML (instance) data. This is a known bug, and authors can work around this problem by defining the namespace prefixes in the instance data's root element.
The device validation message through the voice channel will only work when the user's locale is set to English, and the message is rendered by a voice gateway with an English Automatic Speech Recognition (ASR) engine. Any other settings for the user locale or the gateway ASR engine are unsupported and will likely cause errors in message delivery.
Re-created SSO users of the Oracle Application Server Wireless Tools cannot access some of the tools' functionality. If a user is deleted and then re-created, then that user cannot use all of the functionality of the Wireless Tools. This problem occurs because of the way the SSO server caches GUID information for the users. To solve this problem, restart the SSO server.
Some browsers (such as the Spectrum24® WebClient for Palm Computing Platform) support the ability to capture signatures. Applications developed using OracleAS Wireless XML can generate the target markup required to support signature capture. In this release, the following browsers are supported for signature capture:
Symbol Spectrum24® WebClient for Palm Computing Platform Version 2.8-10 for Palm OS 4.1
Microsoft Pocket Internet Explorer 4.1 on Microsoft Pocket PC
Microsoft Pocket Internet Explorer on Microsoft CE3 or later
On supported Microsoft Pocket PC and Windows Mobile platforms, the Oracle Signature Capture Plug-in for Pocket Internet Explorer must be installed. The Oracle Signature Capture Plug-in is available for download from Oracle MetaLink at http://metalink.oracle.com
or contact Oracle Support.
WebCache supports MobileXML documents, but does not support documents that are written in XHTML+XForms or XHTML-MP.
In order for devices to use this function, they (devices) must send the appropriate HTTP Accept header.
In this release, the Oracle Application Server Wireless log.xml
file does not support NLS.
The XForms transformer sometimes outputs markup language that includes the POST
method. Therefore devices that do not support the POST
method, such as old J-Phone Type C2 devices in Japan, are not supported with XForms.
If you use the Wireless model API, and make changes in the Wireless persistent objects, include the following in your web application web.xml file to ensure that the changes are propagated across all web applications:
<?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd"><web-app><!-- ... --><filter-mapping>...</filter-mapping><listener><listener-class>oracle.panama.servlet.CacheManagerListener</listener-class></listener><servlet>...</servlet><!-- ... --></web-app>
When you access the webclipping functionality of the OracleAS Wireless Webtool, and you use the Netscape Web browser and Japanese is your browser language , you will not be able to correctly view the Webclipping help pages .
When you access the OracleAS Wireless portal by an HDML simulator and try to login with an invalid user account , the non-ascii data in the username is displayed as corrupted data or changed to another string .
When you use OracleAS Wireless Webclipping, the output may display in a language dissimilar to the language of your user profile; that is the language you use to loging in to Webtool. The Webclipping manager uses your Web browser language as the default.If you want the output of OracleAS Wireless Webclipping to appear in a specific language please refer to the Help of your Web browser for how to set the browser language .
If you use UP.SDK 3.3.1 simulator to connect to OracleAS Wireless portal , specifically ptg/rm, and then go to SMS and send a short message with Japanese strings and save it, the saved Japanese message will be garbled.
If you login into OracleAS Wireless portal, select PIM > Shortmessage, and create a predefined Short Message using Korean characters and then save it, you will find the SMS saved. However, if you select Pick Message and try to select the saved message, you will find that the saved message is not present.
Oracle recommends not storing a short message in Korean characters when accessing the OracleAS Wireless portal .
This section describes OracleAS Wireless configuration issues and workarounds. It includes the following topics:
Section 15.2.1, "Configuration Assistant Hanging for Wireless on 10g 64-bit Database"
Section 15.2.3, "Potential Conflicts in Application Entities Based on OID"
Section 15.2.5, "Updating Oracle Application Server Wireless Hostname"
Section 15.2.6, "Oracle Application Server Workflow Integration"
Section 15.2.8, "Discovering New Devices or Simulators Using the Openwave Plug-in"
Section 15.2.9, "Integrating Oracle Application Server Wireless with Oracle Internet Directory"
Section 15.2.10, "Unable to Log Into Studio and Customization Tools"
Before recreating a 10g database on the same machine as the original database, using the same Service Name and SQL*Net port as the original database, then you should shut down any middle tiers that are trying to connect to the database. This is done so that the database does not receive many incorrect username/password requests (If it does, the account will be locked out).
If you must keep the middle tier running while creating the new database, then set failed_login attempts to UNLIMITED as a workaround.
Oracle Application Server Wireless standalone instance names can only contain single-byte alphanumeric characters. This includes the instance names for messaging gateway, notification engine, data feed engine, notification event collector, performance logger and location event server.
Oracle Application Server Wireless middle tiers installed against the common meta data repository (Oracle Application Server Wireless schema) share a common application entity in OID. The application entity is created as part of the first Oracle Application Server Wireless middle tier installation, and is owned by the OID user who installs that middle tier. Subsequent Oracle Application Server Wireless middle tiers installed against the same meta data repository use the application entity that was created as part of the first middle tier installation.
Subsequent Oracle Application Server Wireless middle tier installations against a meta data repository should be done by the same OID user who installed the first Oracle Application Server Wireless middle tier.
If you want to use a different OID user to install subsequent Oracle Application Server Wireless middle tiers, then you must add the OID user as a shared owner of the application entity before starting any subsequent Oracle Application Server Wireless middle tier installations.
To add a shared owner for a Oracle Application Server Wireless application entity:
Find the name of the Oracle Application Server Wireless application entity by executing
$ORACLE_HOME/wireless/bin/getAppEntityName.sh[bat]
from the first middle tier. This script prints the name of the Oracle Application Server Wireless application entity.
Use the OID Deployment Delegation Console or OID Directory Manager to add the new OID user as a Component Owner for the Oracle Application Server Wireless application entity name returned in the previous step.
See: For more details, see "Using Deployment Delegation Console to Add Users to Groups" in Oracle Application Server 10g Installation Guide. |
If your OC4J_Wireless server must support a large number of concurrent users, increase the maximum memory size to 1 GB (or more) using the following JVM options:
-Xms512m -Xmx1024m
You can increase the MaxClients
parameter in httpd.conf
to support higher hit rates. For example, by setting MaxClients
to 1024 in httpd.conf
, you can allow up to 1024 concurrent HTTP requests. Consequently, you can expect an increased number of Application Server threads in the OC4J_Wireless instance. Ensure you reduce the thread stack size to 256k in order to support large numbers of Application Server threads in OC4J_Wireless. The default stack size in the Solaris environment is 512k. The stack size is set by the following JVM option:
-Xss256k
If you are running OC4J_Wireless instances on multi-CPU machines, you can set the JVM options to enable the Parallel GC algorithm in JDK 1.4. You may set the ParallelGCThreads parameter to the number of CPUs in your host. For 4-CPU Solaris machines, the following JDK 1.4 JVM options have been found to increase the performance of the OC4J_Wireless instances:
-XX:+UseParallelGC -XX:ParallelGCThreads=4
The following GC tuning parameters provide better performance for the OC4J_Wireless:
-XX:NewRatio=2 -XX:SurvivorRatio=16
Instructions for updating the Oracle Application Server Wireless port and hostname are detailed in OracleAS 10g Administrator's Guide. If you want to update the hostname only, without updating the port:
Re-register Wireless with SSO by running the following command on the middle-tier host:
ORACLE_HOME
/wireless/bin/reRegisterSSO.sh new_wireless_url oracle_home administrator_dn
where:
new_wireless_url
: Wireless HTTP URL with the new Web Cache listener port.
oracle_home
: Middle-tier Oracle home whose Web Cache port you are changing.
administrator_dn
: OID administrator.
For example, if you have changed the Web Cache listener port to 7779 on the middle-tier installation in /home/oracle
on host myhost:
ORACLE_HOME/wireless/bin/reRegisterSSO.sh http://myhost:7779/ptg/rm /home/oracle cn=orcladmin
For a user to be able to receive Workflow notifications properly, ensure the following settings in the customization portal are set properly:
A device should be created and validated.
The option, Allow other applications to access my user profile, in the User Profile section should be checked.
The Contact Rules section should not have Unavailable checked.
Also, a setting must be set properly on the Workflow home page.
To do so:
Log on to your Workflow home page.
Click User Preferences. The value for Send me electronic mail notifications cannot be Do not send me mail. If it is, the user must change it by clicking Update. Choose any option except for Do not send me mail or Plain text summary mail.
To confirm your change, click OK.
To enable the Workflow worklist application, the Workflow folder must be made visible. To do this:
Log on to the Oracle Application Server Wireless tool.
Click the Content tab on the top right to go to the Publish Content page.
Select the Workflow folder and click Edit.
Check the Visible box and click Apply.
During 9.0.4 middle tier installation, WebCache must be configured with the HTTPS Port number. If WebCache is not configured with the HTTPS Port number, then Oracle Application Server Wireless will by default set its HTTPS Port to zero.
After you configure WebCache with the correct HTTPS Port, you must use Oracle Enterprise Manager to reconfigure all of the HTTPS-related URL parameters.
If you use the plug-in interface that is provided by Openwave, change the user agent of the HDML_EZweb logical device to:
UP.Browser/3.0*UP.Link/3*, UP.Browser/3.2.9.1-*UP.Link/3*"
Run Oracle Directory Integration Server (odisrv
) when you want to synchronize data between Oracle Application Server Wireless and OID.
A problem has been reported regarding logging into Customization and Studio Tools. This was caused by configuring JServ before configuring Wireless. You should configure Wireless before you configure JServ. If you have problems running JServ and OC4J together, see "Using JServ and OC4J Together" in the Oracle HTTP Server Administrator's Guide.
This section describes documentation errata for OracleAS Wireless. It includes the following topics:
Section 15.3.3, "Account Numbers in Oracle Application Server Wireless Tool"
Section 15.3.5, "Configuring Oracle Application Server Wireless for Voice Applications"
Section 15.3.14, "Unable to Change User Password in Customization"
Section 15.3.15, "No Error Given When Adding an Already Existing User"
Section 15.3.18, "Location Search Does Not Return Location Name"
Section 15.2.2.1 of the Oracle Application Server Wireless Administrator's Guide should read as follows:
The Oracle Application Server Wireless Web Server (ptg/rm
) determines the locale of a user in the following order:
Use PAlocale
(if present).
Use the Accept_Language HTTP header (if present).
Use the site default locale.
Throughout the documentation, you can substitute UNIX for Solaris in all instances except for the Oracle Application Server Wireless tuning described in Chapter 13 of the Oracle Application Server Wireless Administrator's Guide ("Optimizing Oracle Application Server Wireless"). The tuning knobs described in this chapter are Solaris-specific.
When you create or modify a device using the Oracle Application Server Wireless Tool, you enter the Primary Phone Number for the device. This number becomes the Account Number for the device. The online Help sometimes refers to the Primary Phone Number in places where the user interface displays the label Account Number. The correct usage is Account Number.
The online MXML tag glossary omits the dtmf
attribute <SimpleMenu>
.
This attribute controls whether or not DTMF keys are assigned to the first 9 <SimpleMenuItem>
s automatically.
Values for the dtmf
attribute are true or false; the default is false.
The following changes to the documentation in Oracle Application Server Wireless Administrator's Guide have occurred since the book was released:
Section 9.2.2, "Configuring and Testing Voice-Enabled Applications" should be removed as the information is no longer necessary.
Section 9.2.3.1, "Provisioning Mobile Studio for Voice Access": in addition to the existing step, you must set the PAlogin
parameter (PAlogin=true
).
The ORACLE_SERVICES_PIM_MAIL_AUDIO_TMP_DIR
and ORACLE_SERVICES_PIM_MAIL_AUDIO_TMP_URL
parameters are in the Mail application, not the Voice Main Menu application as stated in Section 9.2.3.2.5, "Configuring the Voice Main Menu to Prefetch the Mail Application" in Oracle Application Server Wireless Administrator's Guide.
The following notes apply to Section 9.2.4.1, "Testing the General Commands" in Oracle Application Server Wireless Administrator's Guide:
The path to grammer.jsp is incorrect. The path to globalGrammar.jsp
on the integrated instance is: <IAS-HOME>/j2ee/OC4J_Wireless/applications/modules/modules-web/common/jsp/globalGrammar.jsp
.
The following text is no longer valid:
"Modify the following file for the My Oracle main menu, or another .JSP for a personalized menu: <iasw-root>/iaswv20/wireless/j2ee/applications/voice/voice-web/mainmenu/MOCGrammar.jsp
"
The following changes to driver attributes (in Section 10.6.1, "Pre-Built Drivers" of Oracle Application Server Developer's Guide) have been made:
For the UCP Driver, the sms.server.default.encoding
attribute:
The default encoding of the text message. The default value is IA5. For multi-byte languages (such as Chinese), the attribute must be set to UCS-2. The attribute sms.message.chunksize
should be set accordingly (that is, the chunksize should be no more than 160 if the encoding is IA5; no more than 70 if the encoding is UCS-2).
For the SMPP Driver, the sms.server.default.encoding
attribute:
The default encoding of the text message. The default value is IA5. For multi-byte languages (such as Chinese), the attribute must be set to UCS-2. The attribute sms.message.chunksize
should be set accordingly (that is, the chunksize should be no more than 160 if the encoding is IA5; no more than 70 if the encoding is UCS-2).
In Section 10.6.1.9.1, "About Jabber" in Oracle Application Server Wireless Developer's Guide, a figure is mistakenly referenced. Instead, this paragraph is appropriate:
Consider a scenario in which an Oracle Application Server Wireless instance is connected to MSN through Jabber's MSN transport gateway using the ID oracleagent@msn.com. End users on MSN can then access applications on the Oracle Application Server Wireless instance by sending messages to this ID (oracleagent@msn.com) from their client.
Tuning information has changed and has been enhanced since publication of the Oracle Application Server Wireless books. See Oracle Technology Network for the latest information about tuning Oracle Application Server Wireless.
Some URLs have changed since publication of the OracleAS Wireless books. Table 15-1 details the changes.
Table 15-1 OracleAS Wireless Changed URL
Existing URL | Should Be... |
---|---|
|
|
|
|
webservices |
webservices |
product/devices/certified/ certified_gateways_wap.jsp |
Go to the Mobile Tech Center. |
|
Go to the Mobile Tech Center. |
|
|
|
|
products/oracle9i/doc_library/ 901_%20doc/nav/docindex.htm |
|
|
|
|
|
Section 14.2.3, "Using Web Services" did not include mention of mobile positioning support. The correct paragraph should read:
Oracle Application Server location services support the use of Web services with wireless applications that use the capabilities of the Geocoder
, Mapper
, Router
, or YPFinder
interfaces. Application developers do not need to add special coding if the application runs within OracleAS Wireless. Rather, Web services are integrated as service proxies for geocoding, mapping, routing, and business directory (YP), and mobile positioning support.
This section replaces the information about the CMG MMS Driver included in OracleAS Wireless Developer's Guide.
This driver provides the ability to send and receive MMS messages to and from a CMG MMSC (Multimedia Messaging Service Center). The driver has been updated to work with the CMG MMSC API for VAS v1.1.1 library. Since the earlier versions are no longer available from CMG and v1.1.1 is not backward compatible with any earlier versions, you must upgrade to this version.
This driver requires the CMG MMSC API for VAS v1.1.1 (mmscapi.jar and mmscapi.war), available from CMG (http://www.cmgwds.com). You must add the mmscapi.jar library to the CLASSPATH in $ORACLE_HOME/opmn/conf/opmn.xml (in UNIX) or $ORACLE_HOME\opmn\conf\opmn.xml (in Windows).
mms.cmg.account.id—The MSISDN of the VAS application, or the short identification number as registered with the CMG MMSC. This is required.
mms.cmg.account.alias—The application alias configured in the CMG U-power web interface. This is required.
mms.cmg.account.password—The password to authenticate the VAS application as registered with the CMG MMSC. This is required.
mms.cmg.config.file—The path to the core configuration file for the CMG MMSC API. This is required. For details regarding the contents of this file, refer to the User Manual that is packaged with the CMG MMSC API distribution. A sample configuration file is included: ($ORACLE_HOME\wireless\messaging\drivers\cmg\CMGMMSDriver.cfg) with this driver.
mms.cmg.debug—Enable logging extra debug information to the file. Options: true (debug enabled), false, or leave blank (debug disabled).
mms.cmg.billing.category—MMSC Billing Category (optional). This value is used to send custom billing category information to the MMSC. For details and examples of the billing category, refer to the User Manual that is packaged with the CMG MMSC API distribution.
mms.cmg.billing.price—MMSC Billing Price Value (optional). This value is used to send custom billing price information to the MMSC. For details and examples of the billing price, refer to the User Manual that is packaged with the CMG MMSC API distribution.
To configure the driver to receive MMS messages, you must perform these steps:
Package the mmscapi.war file into a cmgmmsc.ear file as follows:
Unzip $ORACLE_HOME\wireless\messaging\drivers\cmg\cmgmmsc.ear.zip into an empty directory. This creates the following directory structure: \META-INF\application.xml, \META-INF\MANIFEST.MF
Copy mmscapi.war into this directory and rename this file to cmgmmsc.war. This creates the final directory structure: \META-INF\application.xml, \META-INF\MANIFEST.MF, \cmgmmsc.war
Zip this directory structure and rename the zip file to cmgmmsc.ear.
Copy cmgmmsc.ear to $ORACLE_HOME\wireless\j2ee\applications\
In $ORACLE_HOME\wireless\j2ee\config\wireless-web-site.xml, add: <web-app application="cmgmmsc" name="cmgmmsc" root=/"cmgmmsc" load-on-startup="true"/>
In $ORACLE_HOME\wireless\j2ee\config\wireless-server.xml, add: <application name="cmgmmsc" path="../applications/cmgmmsc.ear" auto-start="true" />
Start the OracleAS Wireless instance, which will auto-deploy the cmgmmsc.ear file.
After the auto-deploying is complete, in $ORACLE_HOME\wireless\j2ee\applications\cmgmmsc\cmgmmsc\WEB-INF\web.xml:
Edit the trace directory and filename.
Add the following section: <servlet-mapping> <servlet-name> HttpReceive </servlet-name> <url-pattern> /HR </url-pattern></servlet-mapping>
Back up (rename the file's extension to anything except .jar) $ORACLE_HOME\wireless\lib\log4j-core.jar and $ORACLE_HOME\wireless\lib\log4j.jar. Copy $ORACLE_HOME\wireless\j2ee\applications\cmgmmsc\cmgmmsc\WEB-INF\lib\log4j-1.2.5.jar to $ORACLE_HOME\wireless\lib\log4j-core.jar.
Restart the OracleAS Wireless instance.
The servlet HttpReceive runs within the OracleAS Wireless instance, and requires RMI to communicate with the CMGMMSDriver. Further details are provided in the User Manual that is packaged with the CMG MMSC API distribution.
End users only have permission to change their passwords if that permission has been granted by the Administrators. If permission is not granted, then the Change Password field will be greyed-out (disabled).
For more information on enabling password resets, see OracleAS Wireless Administrator's Guide.
If you attempt to add a user or group using an existing user name or group name, the existing user/group data is updated. The expected behavior would be for an error to be generated, but instead, the existing information is silently updated.
When editing a user group's data with faulty information (such as a name that already exists), an error is displayed. When you alter the details and click Finish, a new entity is created.
When a search is performed for Devices on one tab of the Webtool (such as Foundation), the search results persist, even when a search for devices is done on another tab of the webtool (such as Services).