| Oracle® Application Server Release Notes 10g Release 3 (10.1.3.2) for HP-UX Itanium Part Number B32413-04 |
|
|
View PDF |
| Oracle® Application Server Release Notes 10g Release 3 (10.1.3.2) for HP-UX Itanium Part Number B32413-04 |
|
|
View PDF |
This chapter describes issues with Oracle Communication and Mobility Server. It includes the following topics:
Review the following sections for information about issues that affect installation, configuration, and upgrade:
This release of OCMS supports lowercase usernames. Only use lowercase usernames.
OutOfMemoryException may be thrown because of a bug in JDK 5, Update 6 which is bundled with Oracle Application Server 10.1.3.2.0. If you experience this error, you should update your JDK to JDK, Update 10. If you do not get the error, updating the JDK is not necessary.
An accessibility issue has been reported when installing Oracle Communication and Mobility Server on HP-UX. When installing the product using the Installation Wizard, some of the screen elements do not meet accessibility requirements. To work around this issue, run the Installer in silent mode:
setupHPUX.bin -silent -options <HOMEDIR>/ocms-<mode>-typical.txt
By default silent installer is set for StandAlone mode. To run the installer for Integrated Application Server mode, set the following:
-V OCMS_MODE_SA="false" -V OCMS_MODE_INTEGJBOSS="false" -V OCMS_MODE_INTEGOAS="true" -V OCMS_OAS_ADMINUSER="oc4jadmin" -V OCMS_OAS_ADMINPASSWD="xxxxxx"
To run SILENT Installer in Debug Mode:
$JAVA_HOME\bin\java -cp setup.jar run -silent -options <HOMEDIR>\silentinstall.txt
Some of the Preferences settings are not completely accessible. As a workaround to this bug, configuration of the preferences can be accomplished by modifying an xml file. The default xml file (on a Microsoft Windows installation) is:
c:\Documents and Settings\<windows account>\Application Data\Oracle Communicator\Accounts\<CommunicatorAccountName>.xml
where <windows account> and <CommunicatorAccountName> are your account names.
For example, if you created an account with the name "John Smith" and you log into windows with the username "jsmith" your account information will be stored in the file.
c:\Documents and Settings\jsmith\Application Data\Oracle Communicator\Accounts\John Smith.xml
There is a companion <communicator account>.dat file which contains information on your contacts, stored in VCard format.The following sections will provide documentation on which parts of the XML file can be modified by a user using the Communicator user interface. The notation provides the XML element names in a hierarchy. These elements all appear under the root "Account" element.Note that the elements are not necessarily presented in the order in which they appear in the account xml file.Changes to these files should only be made when Communicator is closed. If Communicator is open, any changes to these files may be removed.
The Account tab gives you access to the Account settings.
(string) A textual description for this account.
Unlike the other properties in the preferences dialog, the "Run this program when system starts" and "Automatically sign in with this account" modify the Accounts.xml file in the Application Data\Oracle Communicator directory (which holds a list of all of the accounts created on this instance of Oracle Communicator). Whichever account you wish to be the default should be enclosed in a DefaultAccount element. If you wish to automatically sign in with an account, the AutoLogin attribute should be set to "1". For example:
<Accounts> <DefaultAccount AutoLogin="1">John Smith</DefaultAccount> <Account>Jane Smith</Account> <Accounts>
The Presence tab give you access to the Presence settings.
(string) The textual description of the device sent to other users; by default this is "PC".
(int) 0 if disabled, 1 if enabled. Indicates whether or not the user should be shown as idle if the user waits the period of time specified by UserIdleTimeOutValue.
The Appearance tab give you access to the Appearance settings.
(string) The visual theme to use. Options included in 10.1.3.2 are Classic, Communicator, Jazz and SteelCan.
(complex) The Sounds element represents the different sounds that are played on different events. Each Sound element represents one of the sounds.
Sound/Event: can be IncomingMessage, UserOnline, UserOffline or VoiceMessageAvailable
Sound/File: the .wav file to be played when the event occurs
Sound/Mute: 1 if the sound should not be played, 0 if the sound should be played
(int) 0 if false, 1 if true. Shows the main window on top of other windows if true.
(int) 0 if false, 1 if true. When the user clicks the "X" in the upper right corner of the window, Communicator will be minimized to the system tray instead of closed if this is true.
(int) 0 if false, 1 if true. When the user presses Enter, the message will be sent if this is true. If this is false, then pressing Enter will move to a new line.
(int) 0 if false, 1 if true. Smilies (emoticons) will show as images if this is true.
(complex) Indicates which sound should be used as the ring sound. The default sound will be used if this is empty. A single RingSignals/DefaultSignal element may be defined, with the value of that element either being the full path to a .wav sound file or one of the built in filesis present, it can either point to a .wav file or one of these: Dallas, Houston, Office, News Desk, Reception, Beep Beep, Tune 1, Tune 2, Metallic, Mobile 1, Mobile 2.
The Security tab give you access to the Security settings.
(complex) There may be 0 or more Credentials/Credential elements. The contents of the Credential element will be filled automatically if the user chooses to save the username/password when logging in. The user should not edit this field directly, but the user may remove a Credentials/Credential element to remove a username/password from storage.
The Network tab give you access to the Network settings. The proxy, XDMS, LDAP and STUN settings are all configured by an administrator, and should not be changed by the end user. These are fully documented in the administrator's guide regarding customization.
The Audio tab give you access to the Audio settings. Many of the audio and video settings are stored in the system registry.
(int) 0 if disabled, 1 if enabled. Uses silence supression in the audio if enabled.
(int) 0 if disabled, 1 if enabled. Uses echo cancellation if enabled. This is typically useful if you are using a microphone and speakers. When using a headset, you may want to disable this.
(int) 0 if disabled, 1 if enabled. Causes the PC Speaker to beep when there is an incoming call if enabled. This is useful if you are using headphones and do not wear them all the time.
The Video tab give you access to the Video settings.
(string) This element is a computer representation of the video device to use for capture. The only recommended way of modifying this in the xml is to clear the text from this element, which will result in the default system video device being used.
The Other tab give you access to the Other settings. Contacts and Groups (internal note: according to Adam JAWS users are able to add contacts and IM, but they cannot delete contacts, which is why I am providing this information here).In order to delete a contact, you must edit the .dat file in the same location as the account .xml file. Each contact is represented in VCard format, such as:
BEGIN:VCARDVERSION:3.0UID:badf5dee-3848-4443-acc5-8ab0bf19069eADR;WORK:;;;;;;USEMAIL;PREF;INTERNET:john.smith@example.comFN:N:SMITH,JOHNTEL;WORK;VOICE:@w650 555 1212URL;WORK:X-ORACLE-SIPURI:sip:john.smith@example.comX-ORACLE-GROUPS:20000REV:20070205T130513ZEND:VCARD
In order to delete a contact, find the contact VCARD entry and delete everything from and including BEGIN:VCARD to END:VCARD.
The following issues have been reported:
If an OCMS server is deployed on a DHCP based machine (such as a laptop), and the IP address is changed after the initial installation, OCMS can no longer start itself because of SIP binding errors. There are two possible workarounds for this:
Edit occurrences of the IP address in the SipContainer.xml file in the sdp/conf directory.
Reinstall OCMS.
Upon first start up, you may receive an error message regarding XSLT Stylsheets. There is no performance impact connected to this error, and you may safely ignore it.
|
 Copyright © 2008, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
