Skip Headers

Oracle® Collaboration Suite Release Notes
Release 2 (9.0.4) for AIX Based Systems

Part Number B12116-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Feedback

Go to previous page
Previous
View PDF

9
Oracle9iAS Wireless

This chapter provides information about issues associated with Oracle9iAS Wireless release. It includes the following sections:

9.1 Return-to-Portal URL Configuration

If you plan to have your users access the Oracle Wireless & Voice setup wizard directly, without going through the Oracle Collaboration Suite Portal home page first, you must explicitly specify where users should navigate once they have completed the Oracle Wireless & Voice wizard. By default, if users access the wizard from Portal, they will be returned to the Portal home page. If users do not access the wizard from Portal, you must specify the return-to URL of your choice in the OracleHome/webclient/classes/oracle/collabsuite/webclient/resources/webclient.properties file.

For example: portal=http://my.company.com/homepage

The default value is set to:

portal=http://<portal_host>:<portal_port>/pls/portal/PORTAL.wwsec_app_priv.login

9.2 Oracle Calendar

The following sections provide information on Oracle Calendar.

9.2.1 Calendar Server

This paragraph replaces the information in section 4.3 of Oracle9iAS Wireless Administrator's Guide concerning valid values. In Oracle Collaboration Suite mode, enter the name and port of the Oracle Collaboration Suite Calendar server. Separate both these entries with a colon (:). To determine the port for Calendar server access, view the $ORACLE_HOME/ocal/misc/unison.ini file in the Oracle Collaboration Suite middle-tier. Look for the "port" entry in the "[ENG]" section.

9.2.2 Creating New Calendar Entries through Voice

In this release, users cannot create new Oracle Calendar entries through the voice interface.

9.3 Wireless Status Displayed as Down

Oracle Enterprise Manager displays all of the processes that can be managed for a middle-tier system. When accessing the EM page and clicking on a middle-tier system, Wireless shows a red down arrow. The reason for this is that the Wireless Server has not been started. To start the Wireless Server, from your browser, point to:

@ http://machine_name:port/ptg/rm. This automatically starts the Wireless Server.

9.4 Multi-Byte Characters and Wireless Notifications

You can receive a wireless notification for a message received by Oracle Email. If either the subject or the sender's ID in the original message contains multi-byte characters, then these multi-byte characters are not displayed correctly in the notification.

9.5 Registering Oracle Portal Provider for Wireless Web Tool and Wireless Customization Fails

If both the infrastructure and middle-tiers are installed on the same system, and the Enterprise Manager daemon running on that system is referring to the infrastructure home, then the Register Oracle Portal Provider for Wireless Webtool 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, pdkjava.jar and ptlshare.jar should refer the middle-tier installation location. The orion-web.xml file is located at:

$ORACLE_HOME/sysman/j2ee/application-deployments/em/emd/orion-web.xml

For example, if the infrastructure is installed in:

/private/ias20_infra/

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.

9.6 Generic Single Sign-On Errors Encountered When Using Microsoft Internet Explorer

There is a generic error that affects some Oracle9iAS components, including Oracle Wireless. This errors occur when you use Microsoft Internet Explorer to access the Web tool on a system that has both infrastructure and a middle-tier installed on it. You might encounter the following errors:

9.7 SimpleImage and Alternate Text Display

SimpleImage supports an alt attribute which provides alternate text for display devices, and an alternate.wav file for the voice deviceclass devices. For 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>

9.8 Web Component Developer Breaks for Composite Web Component

The Web Component Developer is a java-based GUI tool that allows you to create Web Components that can be delivered by the Web Component Provider, as Wireless Services. There is a known issue of the Web Component Developer in the generation of Web Component Definition files. This renders the developing of composite Web Components not possible. This known bug is scheduled to be fixed and delivered to customers via the Automated Release Updates.

9.9 High Availability for Oracle Wireless

In Oracle Wireless, applications cannot be clustered using the Oracle9iAS clustering mechanism. However, it is still possible to configure Oracle9iAS such that a high availability deployment can be achieved. Complete the following steps for high availability deployment.


Note:

Remember to back up all files before you modify them


  1. Install the Oracle9iAS infrastructure on a system and install multiple middle- tiers on separate systems. Ensure that each of these middle-tier installations point to the infrastructure.
  2. Shut down DCM and all process in all middle-tier instances by running the following command from each middle-tier installation:
    $ORACLE_HOME/dcm/bin/dcmctl stop
    
    
  3. Shut down Oracle Enterprise Manager on each machine by running following the command from the Oracle home directory of the active EM installation:
    $ORACLE_HOME/bin/emctl stop
    
    
  4. Verify that the $ORACLE_HOME/opmn/conf/ons.conf file on each of the middle-tiers and on the infrastructure contains IP address entries for all the other tiers. If not, file and add missing IP-address entries.
  5. On each middle-tier, increase the number of processes that need to participate in the default island for the OC4J_Wireless OC4J instance to the desired number. This can be done from the EM console or by modifying the file ORACLE_HOME/opmn/conf/opmn.xml.

    See Also:

    Oracle9iAS Containers for J2EE documentation for details and concepts of OC4J instance and islands.

    For instance, if you modify opmn.xml, a typical entry to start four OC4J processes in the default island would be of the form:

    <oc4j maxRetry="3" instanceName="OC4J_Wireless" gid="OC4J_Wireless" 
    numProcs="4">
    
    
  6. In the mod_oc4j configuration file for each middle-tier (that is: $ORACLE_HOME/Apache/Apache/conf/mod_oc4j.conf), modify the mount point entries for the Wireless runtime. If two middle-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
    
    and 
    Oc4jMount /ptg/*
    instance://m1.c1.mysite.com:OC4J_Wireless,m2.c2.se4637-u-sr006.us.oracle.com
    :OC 4J_Wireless
    
    

    where c1 and c2 are the respective Oracle9iAS instance names and can be determined by running the command:

    ORACLE_HOME/dcm/bin/dcmctl whichInstance
    
    

    These entries should be exactly the same for all middle-tier machines.

  7. Run $ORACLE_HOME/dcm/bin/dcmctl updateConfig to update the DCM repository with the configuration file changes.

    On slow systems, it is likely that a DCM error (timeout) of the form ADMN-906005 is displayed. If this occurs, run the
    $ORACLE_HOME/dcm/bin/dcmctl getReturnStatus command and wait until the command exits. This confirms that the changes have been propagated to the DCM repository.

  8. Add the tag <cluster-config/> under the <orion-web-app> tag in the following file:
    ORACLE_HOME/j2ee/OC4J_
    wireless/application-deployments/ptg/ptg-web/orion-web.xml
    
    
  9. Start DCM and all processes by running the following command in all middle-tier installations:
    $ORACLE_HOME/dcm/bin/dcmctl start
    
    
  10. Start EM by running the following command in the ORACLE_HOME of the active EM installation:
    $ORACLE_HOME/bin/emctl start 
    
    
  11. Configure a hardware load-balancer to point to the middle-tiers.

    Currently, high availability support is only available for the core server runtime (by default mapped to the URI /ptg/rm).

    See Also:

    The Oracle9iAS Containers for J2EE documentation for more information.

9.10 Oracle Wireless Process Status Unavailable for Multiple Oracle Homes with External Repository

When installing both middle and infrastructure tiers on the same system and changing the Wireless schema from the Enterprise Manager console to point to a schema other than the one available as part of the infrastructure install, the Wireless process status changes are not displayed on the Enterprise Manager console. This problem occurs on all platforms.

Workaround:

From the Oracle home directory of the middle-tier for which the schema has been changed, copy the following fragment from the file:

<middle-tier ORACLE_HOME>/config/iasschema.xml

and paste it over (overwrite) the corresponding entry in the infrastructure Oracle home file:

<infrastructure ORACLE_HOME>/config/iasschema.xml 
<SchemaConfigData> 
<ComponentName>Wireless</ComponentName> 
 <BaseName>WIRELESS</BaseName> 
 <Override>true</Override> 
 <SchemaName>the new schema name</SchemaName> 
 <DBConnect>the new DB connect string</DBConnect> 
  <Password>the new DB password (encrypted)</Password> 
</SchemaConfigData> 

Restart Enterprise Manager after this is done.

9.11 Access Information

Two Quick Reference Cards are available to help users with ASK/SMS and Voice Access. They are available on Oracle Technology Network at the following locations:

9.11.1 ASK/SMS Access

For information on ASK/SMS Access, refer to the following Web site:

http://otn.oracle.com/products/owireless/wv_refcard_sms.pdf

9.11.2 Voice Access

For information on Voice Access, refer to the following Web site:

http://otn.oracle.com/products/owireless/wv_refcard_voice.pdf

9.12 SMS Commands for Accessing Oracle Collaboration Suite Components

The following commands are available for accessing Oracle Collaboration Suite components.

9.12.1 Calendar

To view your appointments:

cal [day|week] [<date>]

To make an appointment:

cal new <title> <date> <start-time> <duration> [<location>] [<notes>]
 <date> in "MM/dd/yyyy" format - year can be omitted e.g. 6/29
 <start-time> in "hh:mma" format - e.g. 1:30pm, 9:20am
 <duration> in minutes - e.g. 90

9.12.2 Address Book

Note that Directory lookup will only be performed if the contact is not found in the personal Address Book.

To find contacts in your personal address book or corporate directory.

find string

string is a comma-separated list of names (for example: John, Jack, Smith)

Example:

find John,Jack,Smith

9.12.3 Mail

Mail Async supports the following commands:

send--returns help message
send help--returns help message
send <recipients> <documents>|text:<text>--sends documents or text messages to a 
list of recipients

Examples:

send jacob "text:This is a test message."
send user@oracle.com /private/documents/roadmap30.ppt

9.12.4 Fax

The following fax commands are supported:

fax /help
fax -help
fax -h
fax recipient_fax_number "text:fax message"

Examples:

fax 16505067222 "text:hello world"
fax recipient_fax_number fileURL[,filePathInFilesOnline]
fax 16505067222 http://www.yahoo.com
fax 16505067222 
http://www.yahoo.com,/private/john/mydoc/test.html,/private/john/mydoc/FunSpec.h
tml

9.12.5 Directory

To find contacts in your corporate directory:

search <string>

<string> is a comma-separated list of names (first or last), someone's global ID with no extension, e-mail address, or phone number.

9.12.6 Short Messaging Service

Use to send short messaging over any channel:

sm <channel> <recipient> <subject> <message>

Examples:

sm voice 16505551212 Meeting Let's meet at 2:00pm--Sent as voice message.
sm email john.smith@oracle.com "Simple Subject" This is my message--Sent as an 
email.
sm sms 5551212 Meeting Let's meet at 2:00pm--Sent as an SMS message. 
sm fax 16505067000 "Urgent Meeting" This is important--Sent as fax.

Supported channels are voice, email, sms, and fax.

Subjects containing multiple words must be quoted.

Usage:

im command [param1 param2 param3 ... paramN]

Example:

im send myfriend "Hi, how are you doing?"

Enclose (in double quotes) parameters containing spaces.

Available Commands:

9.12.7 Files

To browse the contents of a given directory:

files [<directory>]

Example:

files /Private

(If left empty, the home directory is assumed)

9.13 Oracle Files Module

Follow the steps below to configure Oracle Files.

9.13.1 Adding a New Dependent Jar File

In this file:

$ORACLE_HOME/j2ee/OC4J_Wireless/config/application.xml

After this line:

<library path="%ORACLE_HOME%/wireless/lib/wireless.jar"/>

Add the following line:

<library path="%ORACLE_HOME%/wireless/lib/mod_pim_webdav_httpclient.jar"/>

Replace %ORACLE_HOME% with the absolute path for the middle tier Oracle home location. Then restart the instance for this change to take effect.

9.14 Oracle Files Default Document Character Set Must be UTF8

If the wireless PIM Module of Oracle Files is used in a multi-byte character set environment, the default character set for Oracle Files must be Unicode (UTF-8). This preference is set at the subscriber level and can be overridden at the user level.

9.15 Multibyte User Names in Jabber Not Supported

Jabber, which is the backend we use with Instant Messaging does not support multibyte usernames, thus the Instant Messaging module consequently also does not support multibyte user names.