Oracle Application Server UMS Portlet - Release Notes
OracleAS Portal Integration Solutions
Oracle Application Server
UMS Portlet - Release Notes
| Last Update: |
May 2005 |
| Status: |
Beta |
Contents
System Requirements
What's New
Installation
Known Issues
System Requirements
The following are the recommended and minimum requirements to use and
install the Oracle Application Server (OracleAS) Unified
Messaging Service (UMS) Portlet:
| Application Server |
OracleAS Containers for J2EE (OC4J) v9.0.2 or
later |
| OracleAS Portal Version |
3.0.9.8.2 (and later), 9.0.2.x or later, 9.0.4.x
or later, 10.1.2.x or later |
| Browsers |
Netscape 4.0.8 and above,
Microsoft Internet Explorer 4.0.1 with Service Pack 1 and above |
What's New
- Certified against Oracle Application Server Portal Developer Kit
(PDK) version 9.0.4.1.
Installation
Follow the instructions within the Oracle
Application Server UMS Portlet - Installation Instructions
document.
After installation, please review the Oracle Application Server UMS
Portlet - User Guide which explains
how this portlet works.
Known Issues
- The OracleAS UMS Portlet will throw a
javascript error when deployed on Oracle
Portal 3.0.9 and viewed using Microsoft Internet Explorer. This is due
to the use of
fully qualified parameter names for the HTML form elements that are
used to allow for multiple instances of the same portlet to be added to
the same page. Microsoft Internet Explorer does
not handle the javascript call to window.document.formName.elements["elementName"]
when the "elemenName" is fully qualified. However this does work when
viewed in the Netscape Browser when deployed on Oracle Portal 3.0.9.
There are no issues when the provider is deployed on OracleAS Portal
release 9.0.2 or later. The portlet is best viewed in Microsoft
Internet Explorer.
- The portlet has been tested only
with a select set of telecom
providers. So not all transport types will work across all the
geographical
regions.
- The sender and recipient phone numbers should be in the
specified
format mentioned in the User
Guide.
- After sending a message and receiving the status message "Message
sent
from xxxx, please check the message log for status", you
should
not refresh the compose page. Refreshing the page will send the
same message
again, because the browser will POST the cached data back to the JPDK
framework
resulting in a duplicate message being sent.
- Currently the portlet only permits sending plain text
messages.
Future releases may have support for other content types.
- The portlet screens are not NLS compliant.
Trademarks
Oracle and the Oracle logo are
trademarks or registered
trademarks of Oracle Corporation in the United States and other
countries.
All other names are trademarks and/or registered
trademarks of their respective owners.
|