This section contains a list of the known issues with Communications Express 6.3. The following product areas are covered:
Communications Express Login Screen Does Not Honor CSS Definition in themes.properties
The login.jsp file in Communications Express has hard-coded style— sheet information. As a result of this, new skin-definitions cannot be applied for the style-sheets used with the login page.
Western European Characters Garbled in Subject when Internet Explorer is Used
This occurs when the default mail client is Microsoft Outlook and the browser used is Internet Explorer. When you are invited to an event with a multi-byte name, and you click on the link of the name of the person who invited you, the subject field of the Outlook client displays garbled characters.
Need Some Documentation on Webmail Pop-ups
The online help for Communications Express does not contain information on how to enable pop-up windows for various supported browsers. Communications Express uses pop-up windows to perform various tasks like composing emails, creating new tasks, and so on. The browser must allow pop-up windows to appear for the site from where Communications Express is accessed.
UWCAuth Servlet Throws a NullPointer Exception
In a deployment scenario where the dependent components of Communications Express (deployed on Sun Java System Application Server) are deployed across multiple nodes, the Communications Express UWCAuth Servlet throws a NullPointer Exception.
Workaround: Restart the Application Server.
UWC Forward Function Should use Sieve Redirect, not Notify
Communications Express allows users to create mail filters by setting a forwarding address in the Options page. This forwarding functionality uses the sieve notify function instead of redirect. Notify is intended to send a short message (possibly via pager) to let the recipient know he has new mail. Messages should actually be forwarded using the redirect functionality instead of notify (which is a nonstandard option).
From this release onwards, all new forward mail filters will by default use the forward rule instead of the notify rule. This fix is also backward compatible. If you upgrade Communications Express from an earlier release, you can preserve your old settings for forwarding mail filters (that is, using the notify rule) by setting the mailfilter.preservenotify property to true in the uwcconfig.properties file. This property is set to false by default.
Communications Suite Installer Does Not Permit Installation in a Local Zone
An attempt to install Communications Express with and Access Manager using the Communications Installer 14a into a sparse zone results in the following message regarding shared components:
Unsupported componets in zone.
Following components required by the selected components, are not supported in local zone and they can not be installed directly into the local zone. Please install these components from the global zone before proceeding this installation.
Workaround: Install the shared components in the global zone using the pkgadd command. This allows the installation to proceed without any problems.
login_type=proxy Doesn't Seem to Have any Effect.
The login_type parameter in the db_config.properties file specifies the method through which the connection to the LDAP store is maintained. You can assign the following three values to this parameter:
anon - Enables the user to connect to the LDAP as an anonymous user
restricted - Enables the user to connect as a user who has the rights to perform operations on the Address Book Store.
proxy - Enables the user to masquerade as a user who can perform operations on the Address Book Store. Assigning this value enhances performance as it bypasses the LDAP bind on each operation.
According to this bug, when users try to specify a method for connecting to the LDAP store by setting this parameter to any of the values listed above, the connection to the LDAP is made with the directory manager credentials irrespective of the method specified. This prevents the administrator from setting some ACLs in the directory and users can have access to parts of the LDAP store when they should not.
JES5-B14a: Linux RH4.0: Unable to load Communications Express Login Page in a Multi-tiered Deployment
The login page fails to load even if the user logs in with valid credentials in a Multi-tired deployment topology. This issue is seen in the following scenario:
Communications Express and webmail host are installed on one node
Directory Server, Calendar Server on separate nodes
Calendar Server, Messaging Server, and Communications Express configured with SSO
Access Manager is enabled in the uwcauth.properties by setting the property auth.identity.enabled to true
The web container logs a series of exceptions indicating a problem with Access Manager when Communications Express tries to execute code that makes calls to Access Manager SDK. This happens when a user tries to log on to Communications Express.
This section contains a list of known issues in the Configurator tool for Communications Express.
The Communications Express Patch Configuration Program Prompts Users for the Webmail SSL Port Number Even if SSL is Not Enabled
When the patch-config program is executed on a Communications Express installation, it first checks if webmail is deployed. If it is deployed, the users are prompted to enter the SSL port number. Users can choose to install webmail with or without SSL. The patch-config program prompts the users to enter the SSL port number for webmail even if webmail is not enabled with SSL.
Workaround: If webmail is not configured in SSL mode, ignore this message by pressing the Enter key and proceed with the patch configuration.
Communications Express Does Not Allow Users to Log in After a Patch is Backed Out
Communications Express brings back the login page when users try to log on to Communications Express with valid credentials, after a patch is backed out. This issue is seen when users upgrade Communications Express by installing a patch using the patch-config and install-newconfig commands but later run the backout-newconfig to back out of a patch. The backout-newconfig utility does not warn users that some of the JSP files may have been cached by the web container.
Workaround: Remove the ClassCache directory for your web container and restart the web container on which Communications Express is deployed. The ClassCache directories for Web Server and Application Server are:
Web Server: /opt/SUNWwbsvr/https- <servername>/ClassCache/https- <servername>, where <servername> is the domain on which Communications Express is deployed.
Application Server: /var/opt/SUNWappserver/domains/domain1/generated/jsp/j2ee-modules/ <uwc_module_name>, where <uwc_module_name> is the name of the module deployed on the Application Server.
JSESSIONID Does Not Get Destroyed when Access Manager SSO is Configured With Communications Express
When Communications Express and Access Manager are installed on different machines, a user can view the calendar of a previously logged in user. This is because the JSESIONID cookie does not get destroyed.
Workaround: The following settings in the IS-SDK-BASEDIR/SUNWam/lib/AMConfig.properties file should be changed on the Access Manager machine that Communications Express runs on:
com.iplanet.am.session.client.polling.enable=false com.iplanet.am.notification.url= <url-to-access-web-container-of-CommunicationsExpress> /servlet/com.iplanet.services.comm.server.PLLRequestServlet
Configurator Tool for Communications Express Does Not Support the `Unconfigure' Option
The Communications Express Configurator does not allow you to undeploy, remove files at the time of configuration, and remove files created during runtime.
Workaround: To Unconfigure Communications Express:
Remove the Communications Express package. For example on Solaris type:
Remove the deploy directories.
Remove the WEBAPP entry from Web Server or Application Server server.xml file.
Silent Configuration Does Not Work.
Communications Express allows configuration to be executed only interactively, and does not allow silent configuration. When you try to configure in a silent mode, the following error is displayed, “The Directory name cannot be left blank. This is a mandatory field. Please enter again.”
Communications Express Configurator: devinstall Dumps Core for Unresolved Host Aliases
Communications Express configuration wizard fails to complete the configuration process if your system is not configured for host name aliases.
Workaround: Ensure that you have configured one or more host name aliases for your system.
To configure one or more host name aliases on UNIX systems:
Provide the configuration for the hosts in /etc/nsswitch.conf file:
hosts: files dns nis
This configuration indicates to the name service the lookup order it should use to resolve host names and host aliases. The name service lookup order is: files, dns, and nis.
Ensure that the /etc/hosts file contains two or more host names defined against your machine’s IP address.
For example, if your system IP address is 126.96.36.199, then in /etc/hosts file, you can configure the IP address as:
188.8.131.52 budgie.siroe.varrius.com budgie
184.108.40.206 budgie.siroe.varrius.com budgie loghost
Example of an incorrect IP address:
GUI Configuration Input Fields are Truncated because Input Fields are Right Aligned
The field names and browser buttons are truncated or not visible when the configuration wizard is invoked in a language other than English.
Workaround: Resize the configuration panels to view its contents properly.
The Components for Communications Express are Shown to be Zero Bytes
The configurator tool for Communications Express shows the component size as 0 bytes while displaying the Mail and Calendar components for Communications Express.
Java Exception on Web Server Startup after Configuration of Communications Express
In an installation scenario where Communications Express and Access Manager are installed and configured on separate nodes, the Web Server installed on the node containing Communications Express throws a Java exception on restart. This is due to the incorrect settings in the Web Server's classpath (on the node where Communications Express is installed).
Workaround: Edit the web-svr-base /config/server.xml file on the Web Server instance of the node where Communications Express is installed, and ensure that the following entries are available in the Web Server's classpath:
opt/SUNWam/lib:/opt/SUNWam/locale:/etc/opt/SUNWam/config: /opt/SUNWam/lib/am_sdk.jar:/opt/SUNWam/lib/am_services.jar: /opt/SUNWam/lib/am_logging.jar
Unable to Configure Communications Express on Linux due to Self Referencing Symbolic Links
The Communications Express configurator creates a self referencing symbolic link on Linux under the /var/opt/sun/uwc/staging directory.
Workaround: Remove all self referencing symbolic links from the /var/opt/sun/uwc/staging directory and redeploy Communications Express.
Communications Express Configurator Fails to Validate Application Server Port and as a Result the Configuration Hangs
The Communications Express configurator does not validate the Application Server port during configuration and thus the configuration hangs if a wrong Application Server port number is specified.
Configuration of Communications Express Hangs if Web Server is Running
The configuration of Communications Express hangs when the Web Server is running. This is due to an UnsatisfiedLinkError error.
Workaround: Gracefully shutdown the Web Server by executing the command /web-svr-base/web-svr-domain_name /stop. This will allow the Communications Express configuration to proceed.
Cannot Configure Communications Express in a Multiplexor Environment.
This problem occurs when Messaging Server is configured in a locale other than English. When users try to configure Communications Express using the configuration tool, on the Messaging Server panel when users provide the credentials, the configuration tool passes this on to the Messaging Server and waits for the response. If you configured Messaging Server in Japanese, on authenticating the user correctly, Messaging Server returns a string ja/mail.html to Communications Express. Communications Express on the other hand checks for the response and then proceeds further. However, there is a problem on the Communications Express configuration end which expects a string en/mail.html. Since the response received from Messaging Server is different from what the configuration wizard expects, the following error is displayed:
The Webmail Server credentials are wrong or Server misconfigured
Cannot Go Back in Command line Mode Configuration.
The configuration wizard for Communications Express provides a functionality for users to go back by typing the < symbol. This does not work as desired. As a result of this users cannot go to a previous page or screen by typing the < symbol.
After Patch Upgrade in a Virtual Domain Setup, the Invitations Tab is Disabled.
When Communications Express is upgraded from JES4 non-virtual domain set up to Communications Suite version 5, virtual domain setup by applying a patch, the invitation tab is disabled in the calendar user interface.
Workaround: Clearing the calendar LDAP entries for the user enables the invitation tab.
The View and Edit Tasks Show Notes and Reminder Messages That Span Multiple Lines in a Single Line.
While adding Task notes and Remainder messages in a calendar, the notes or messages are displayed in a single line even if the user intends to have them in multiple lines.
Communications Express Displays Server Error While Importing a Large Calendar Import File
Communications Express displays a server error if a large calendar file is imported. Communications Express allows uploading of files that are within a defined limit. If the size of the file exceeds the defined value, the server displays an error. By default, Communications Express allows 4MB of data to be imported. This error is displayed in the calendar Import/Export window. Communications Express does not handle the server error or display an appropriate message.
Owner Cannot Edit or Delete Event/Task if Existing User is Migrated from Non-virtual Domain to Virtual Domain
Communications Express does not allow owners of the default calendar to edit or delete events, tasks, or invitations that they create when migrated from a non-virtual domain setup to a virtual domain setup. As a result, if an existing user in JES 4 non-hosted domain setup is migrated to hosted domain in Communications Suite version 5, the user cannot edit or delete events created.
Workaround: Explicitly assign read and write permissions by using the Manage Calendar option. For more information on Managing Calendars, refer to the Sun Java System Communications Express 6.3 Online Help.
The Calendar Component for Communications Express Behaves Incorrectly When Monthly Recurring Events are Scheduled
The calendar component for Communications Express behaves incorrectly when monthly recurring events are scheduled. For example, when you schedule a monthly recurring event on every second Thursday of a month, the first instance of the recurrence displays the event on a third Thursday.
Event Search Field in Calendar Does Not Recognize Wild Cards
Communications Express does not recognize wild cards for searching Events or Tasks.
Cannot Edit Imported Events and Tasks in Calendar
Communications Express does not allow editing of Events and Tasks that are imported from one calendar to the other (with allow... permissions set on both), for the same calendar owner.
Default Calendar View Changed to Day View in Calendar Express After Login to Communications Express
When new user is created using Delegated Administrator, after logging in to Calendar Express, the default view is displayed as overview view. However, after logging on to Communications Express, the icsextendeduserprefs are created in LDAP (the user is provisioned in the LDAP), and default view in Calendar is created as day view (ceDefaultView=dayview) so when user logs in back to Calendar Express the day view is displayed.
Communications Express does not provide an overview view. The only supported views are day view, week view, month view, and year view, When user logs in to Communications Express the user is provisioned in the LDAP (by initializing various properties like, ceDefaultView). These default values are picked from uwcdomainconfig.properties. So when user logs in back to Calendar Express, it uses this value from LDAP to find out the display view.
Users may find that the default view for Calendar Express and Communications Express are different when switching from Calendar Express to Communications Express.
MiniCalendar is not opening for "Start Date", if we Select "No Due Date" in the New/Edit Task Window for Internet Explorer
When users create or edit a task from the Calendar tab in Communications Express, the miniature calendar icon is disabled in the row containing the Start Date. This happens when the No Due Date check box is selected for the task. This bug has is seen only when the browser used is Internet Explorer 6.
Communications Express Calendar Web Exception When Searching Calendar Groups for an Event
The Communications Express calendar client displays an exception if a user searches a calendar group consisting of owned and subscribed calendars for events of interest. If a user creates a calendar group and wants to search this group for a particular event, the Communications Express client returns with an error that the page cannot be displayed. As a result, a user cannot search the calendar group for an event and will need to search each calendar individually.
This problem depends on the alphabetical ordering of the event names. If the event in the owner's calendar is alphabetically before the event in the subscribed calendar, the problem may not occur. This problem occurs when the event in the subscribed calendar begins with a letter that is alphabetically before the event in the owner's calendar.
Direct Delivery of Mails to a Multi-byte Shared Folder Corrupts the Recipients Email Address
When mails are sent to a multi-byte shared folder, the recipient's email address is corrupted and the mail is not delivered to the multi-byte shared folder, instead it is delivered to the inbox of the user where the multi-byte shared folder is created. It only works if the recipient's shared folder is created using IMAP-MUTF 7
Workaround: Disable the popup blocker for this URL in your browser.
Communications Express Does Not Behave as Desired when Popup Blockers are Enabled in Browsers
When users enable the pop-up blocker feature in their browsers, the Compose, Reply, Reply All, Forward, and Forward Inline windows of Communications Express are not displayed even though they are valid pop-ups with respect to the application. Communications Express does not let the browsers know that this is a valid pop—up.
The Quota Bar in the Mail Component of Communications Express is not Refreshed With the Size Limit Unless Users View Other Pages that Cause the Page to Refresh Itself.
Communications Express does not refresh and display the status of the quota in the Mail component when mails are sent or received. The updated size is refreshed when users view other pages like Manage Folder, or open an email that causes the page to refresh. The mail quota bar is displayed correctly in cases where the action of the user causes the page to refresh itself.
When User Logs in Through a Domain Specific URL Without Providing @virtualdomain.com, the Mail Tab is Missing
This bug is seen when users log on to Communications Express that is configured with hosted domain support. In a hosted domain scenario, users should log on using the uid along with the virtual domain name. For example firstname.lastname@example.org. If the user logs on to Communications Express without specifying the hosted domain, the Mail tab does not appear.
Workaround:While logging on to the virtual domain, provide the virtual host URL on the browser, for example <virtualdomain>.siroe.com, and then log on to the virtual domain using email@example.com the mail tab is shown. Here:
<virtualdomain> is the configured virtual domain name under the default domain (siroe.com in the example)
uid is the user id of the user on the virtual domain
Saving Draft with Multiple Copies of Same Attachment Removes all Duplicate Name Attachments
This bug is seen when users save drafts of email that have multiple attachments with the same name, regardless of the size of the attachment. At the time of saving the draft, duplicate copies of the attachments are lost and only one copy is retained in the draft. The email is correctly sent along with multiple copies of the same attachment if sent without saving the draft.
In another scenario, if users try to save email drafts that have vCard attachments, the vCard attachments are lost at the time of saving the draft. This works fine if the users sends the mail without saving the draft.
The Address Book Component of Communications Express Does Not Validate the Format of the File That is Being Imported
Communications Express does not validate the file formats when trying to import already exported address book contacts. As a result of this, if a file exported in one file format is imported as another file format, inappropriate error messages are displayed, and in certain cases incorrect contact data is imported.
For example, if users try to import an LDIF file by selecting the Import Format as Microsoft CSV or Address book CSV type from the Import and Export Address Book window of the Address Book component, the following error message is displayed:
The file selected for import is empty or does not exist
The Address Book component does not validate the file format that is being imported.
If an LDIF format type file is imported as a Thunderbird CSV format, Address book creates 10 contacts for the one contact exported.
If a Microsoft CSV format type file is imported as a Thunderbird CSV format, Address book creates multiple contacts.
Communications Express Displays a Configuration Error When Users Try to Search in the Corporate Directory With a Valid Keyword
Communications Express displays the following error message when users try to search the corporate directory with a valid keyword:
Your server is not configured properly or your search query has exceeded the limit. Please check server configuration
Compose Window is Not Displayed to the User When Popup Blocker is Enabled in the Browsers
This issue is seen when users enable the popup blocker feature in their browser. On enabling popup blockers, when users click on the email address of their contacts in the Address Books, Communications Express does not open the mail compose window even when this is a valid pop up window.
Workaround: Disable the pop-up blocker feature for the domain.
The Address Book Name Cannot be Localized by defaultps/dictionary-<lang\>.xml for Every Session
The address book name cannot be localized because the localized value which is based on the resolved session language and the domain specific defaultps/dictionary-<lang\>.xml is assigned when the address book is accessed for the first time.
The “Name” and “Description” entered in the Address Book Options page are also not displayed in the current Address Book drop-down list that appears on the Address Book tab page.
Importing Data from Outlook CSV Format Creates Invalid Birthday and Anniversary.
When users try to import Microsoft Outlook data in CSV format into Communications Express, the entries for Birthday and Anniversary are incorrectly set to 00/00/00.
LDAP Connection Pool does not get Refreshed
The problem occurs when the values specified for the LDAP pool refresh parameter in the uwcconfig.properties (ldapusersession.ldappoolrefresh ) and db_config.properties (defaultserver .ldappoolrefresh) file are greater than the configured firewall time-out value. An error is displayed on the browser complaining of a misconfiguration. Consider the following scenario where the LDAP pool refresh is configured as 30 seconds:
Configure a firewall between Communications Express and the Directory Server host that stores all the LDAP user entries.
Add a firewall rule that closes the TCP connection if there are no connection requests for 15 seconds.
Leave Communications Express idle for more than 30 seconds.
Try to login, or if already logged in, try to search for a user in the address book. An error is displayed at the client's browser complaining of a misconfiguration.
Workaround: The ldappoolrefresh parameters in the uwcauth.properties and db_config.properties files should be lesser than the firewall time-out value.
User's Sieve Scripts May Stop Working After the Upgrade
This is relevant for sites running JES Messaging Server 6.2p2 or later, upgrading to initial JES Messaging Server 6.3. Users who make any use of date-based filtering via the mail filters from Communications Express.
For Sieve filters, the undocumented, unsupported setdateaction, implemented for JES Messaging Server 6.2p2 (Change Request Number: 6236243), has been removed for JES Messaging Server 6.3. setdate was proposed in early versions of a sieve draft for variables, but then removed from later drafts, and in particular is not present in the latest variables draft, now in final call stage. In place of that now-obsolete approach, the more recently proposed date Sieve extension and in particular its currentdate test has been implemented.
End users are quite unlikely to have attempted to explicitly, knowingly used setdate, given its experimental, quickly obsoleted, undocumented, status.
However, the Communications Express mail filter generator in JES Messaging Server 6.2p2 did use setdate when users requested any filtering of their messages by date. Therefore, many users likely have, without knowing it, personal Sieve filters making use of the now-obsolete setdate action. If users edits their Sieve filter in any way, any such obsolete usages will be corrected to use the newer currentdate approach. But in the meantime, their Sieve filter will be considered syntactically incorrect and generate an error; each message to the user with such an incorrect Sieve filter will simply be delivered without filtering, plus the MTA will send a notification message to the user owning the Sieve filter warning of the syntax problem in his/her Sieve filter.
Mail Sent Using Large Japanese/French Data Appears Garbled.
When a large email message is received, users must click an attachment link (text/html or text/plain) within the message. If the content of this attachment includes non-ASCII characters, users may see corrupted data in the newly opened browser pane.
Workaround: Manually select the appropriate encoding from the browser menu.
Users Unable to Localize Date Format in Event View and Check Availability View
Communications Express allows users to define localized date and time formats. The localized date and time formats can be defined in the i18n.properties files. However, the localized date and time cannot be displayed for the following views and pages: There is no corresponding properties for these pages in the i18n.properties file.
Check Availability View
Importing CSV from Localized Microsoft Outlook Express Version 6.00.2800.1123 Does Not Work
Communications Express cannot import CSV data from a localized Microsoft Outlook Express.
Localization Bug When Creating a Sieve Filter on Inbox
This bug is seen when a filter is created by a user for locales other than English. For example, when a user changes the preferred language in Communications Express to a locale other than the default language English, and sets a filter to move emails satisfying a condition, the filter does not move emails to the equivalent folder but tries to move the emails into the folder with the localized name.
Communications Express Calendar, Multi-byte Attachment Filename will be Garbled when it is Opened in Internet Explorer 6.0.
This bug is seen when users try to create a task or event in Communications Express using Internet Explorer 6.0. When users try to attach a file with a multi-byte name and save the attachment, the file name in the save dialog box is gets garbled.
When Adding Localized Email Address Name to Address Book, the Name gets Garbled.
When trying to add email address to address book by clicking 'Add Address' button from a received message that has a localized sender name, the sender's name is garbled in the address book entry.
Importing Localized CSV to Japanese Outlook Does Not Work.
This is an interoperability issue with localized address book contacts in CSV and Outlook Express. Users cannot import address book entries exported as CSV in Outlook for Japanese locale. Address book only supports UTF-8 character encoding. However Outlook Express uses native encoding character sets for other locales. For example, for Japanese locale Outlook supports Shift-JIS. As a result of this interoperability, the contacts in Japanese locale cannot be imported.
Opposite First Name and Last Name Entry when Adding a Contact in Japanese
Communications Express does not add contacts in Address book based on the locale. When users try to add a Japanese contact in Japanese locale, the contact is added as per the rules of English. The contacts are added in the order of First Name and Last Name. Japanese locale requires that the user's last name appears before the first name.
Cannot Add Proper Name to Address Book from 'Add Address' Button.
When users try to add email address to address book using the 'Add Address' button from a received message, the view name is duplicated the contact does not get added properly.
Communications Express does not Handle Password Policies as Desired
Communications Express has the following issues when setting up password policies:
When a password lock is set on entering a wrong password, say for three consecutive tries, on the next correct entry, Communications Express displays a Server Error (500) Page instead of displaying an appropriate message.
When users try to log in with an expired password, the following error is displayed.
Authentication Failed Reenter your username and password.
This message is ambiguous and is not correct.
When users try to login to Communications Express with a policy 'Need to reset the password at the first login', the user is not prompted to reset his password.
Certification Revocation List Not Working
Communications Express does not display any error message when encrypted messages are sent to users whose certificates have been revoked.
S/MIME Draft Added Junk Attachment Smime.p7m to the Message After Saving Draft Message
Communications Express supports the S/MIME specification. You can use S/MIME to encrypt and sign your messages. According to this bug, when users try to sign and encrypt a message and save the draft, the draft that gets saved contains an attachment with the name smime.p7m. Users cannot remove this attachment. Also, all attachments for the saved message are also lost and only the smime.p7m attachment remains in the draft.
Edit Existing Mail Filter by Adding a Forward to Email Address Does not Work
When users edit an already created mail filter by adding a condition for forwarding mails to an email address from the Options page of Communications Express, on clicking the Save button, the filter does not get applied. The conditions added after saving it for the first time do not get executed.
Workaround: This bug has the following workarounds:
Logout and login again as the same and select the mail filter just created and click on the Save button once again. The filter along with the changes gets applied this time.
Edit the Messaging Server configuration file by adding the following option in the options.dat file in the Messaging Server installation directory. The default location of the options.dat file is opt/SUNWmsgsr/config/:
Domain Specific Users Cannot Access Communications Express After Upgrade from JES4 to Communications Suite version 5
Consider a scenario where a JES4 installation of Communications Express that has been configured to support multiple domains and is later upgraded to JES5 by applying the appropriate patches. After the upgrade, the users for the configured domain cannot log on. Here is an example:
Install the JES4 version of Communications Express
Create a virtual domain siroe.com on this set up.
Customize siroe.com by changing a few images and editing the skin properties of siroe.com.
Upgrade to JES5 by applying the appropriate patches.
Restart the web container on which Communications Express is deployed.
Try to log on to the siroe.com virtual domain that is set up in the previous steps using a valid user for siroe.com .
An error page is displayed and the user cannot log on to this domain.
This section describes known issues in the Communications Express— specific documentation.
Description of Upgrading Communications Express L10n Patch Contains Errors
This bug is in the Communications Suite 5 Upgrade Guide which has three parts to it. These three parts are described as follows:
Incorrect patch ID mentioned in Table 6–5: The patch id mentioned for x86 Solaris 9 and 10 in Table 6–5 is 118042–18, which is incorrect. The correct patch ID is 118042-19. Patch ID number 118043 has been obsoleted for Solaris X86. You need to apply patch ID number 118042-19 to upgrade Communications Express localization for both SPARCand X86 Solaris.
Incorrect RPM name mentioned in Table 6–7: The correct RPM names for Communications Express localization are as follows:
Incorrect prepatch script in Linux upgrade procedure: Step 5 in the Linux upgrade procedure displays incorrect prepatch script as follows:
# sh 118-044-19.prepatch
The correct prepatch script is as follows:
# sh 118044-19.prepatch