Patch-ID# 117752-01 Keywords: java_es communications express messaging calendar address book linux rhel2.1 Synopsis: Communications Express 6.1 RHEL2.1: core patch Date: Aug/05/2004 Install Requirements: Additional instructions may be listed below Solaris Release: Note: Redhat SunOS Release: Note: RHEL2.1 Unbundled Product: Sun Java System Communications Express Unbundled Release: 6.1 Xref: This patch available for SunOS 5.8 5.9 in patch 117287-01, and for SunOS 5.9_x86 in patch 117288-01 Topic: Communications Express 6.1 RHEL 2.1: core patch Relevant Architectures: i386 BugId's fixed with this patch: 4896244 4968400 4972547 4974164 4978485 4981705 4995018 5005512 5007786 5008401 5008457 5008458 5010296 5011515 5011634 5012352 5012443 5012489 5013242 5014055 5014131 5018340 5018478 5018487 5019021 5019588 5023634 5025016 5025506 5026361 5027129 5027138 5027152 5027233 5027234 5027318 5027989 5028111 5028787 5028832 5028836 5029968 5030548 5030757 5031469 5031525 5032016 5032143 5032275 5032336 5032818 5032928 5033663 5033671 5034017 5035551 5035889 5035893 5035906 5035910 5036480 5038181 5038908 5038909 5038964 5038981 5042331 5042332 5045982 5047435 5048811 5048818 5048921 5049086 5050108 5052361 5052444 5052494 5052534 5054877 Changes incorporated in this version: 4896244 4968400 4972547 4974164 4978485 4981705 4995018 5005512 5007786 5008401 5008457 5008458 5010296 5011515 5011634 5012352 5012443 5012489 5013242 5014055 5014131 5018340 5018478 5018487 5019021 5019588 5023634 5025016 5025506 5026361 5027129 5027138 5027152 5027233 5027234 5027318 5027989 5028111 5028787 5028832 5028836 5029968 5030548 5030757 5031469 5031525 5032016 5032143 5032275 5032336 5032818 5032928 5033663 5033671 5034017 5035551 5035889 5035893 5035906 5035910 5036480 5038181 5038908 5038909 5038964 5038981 5042331 5042332 5045982 5047435 5048811 5048818 5048921 5049086 5050108 5052361 5052444 5052494 5052534 5054877 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: Note: sun-uwc-6.1-5.1.i386.rpm Problem Description: 4896244 New Event : Recurrence : The Radio buttons and the text are alligned 4968400 Java script error when saving a new mail filter 4972547 Send Email feature removed if mail is not deployed 4974164 i18n:Export addressbook in Outlook csv and vCard format with multibyte data fail 4978485 WARNING issued by Web Server following uwc config 4981705 Clicking on Expand GROUP Icon after editing the group contact details throws err 4995018 i18n: multibyte characters become garabage at trying to search Sun Directory 5005512 l10n:general:Skiplinks & 508 compliance related strings should be localized 5007786 Week View : Grid expands to an extra timeslot for border events 5008401 Mail Filters: Folders are sometimes created, sometimes not 5008457 Events View : spacer gif not found error 5008458 Year View : css_ie5win.css (File not found) error 5010296 Accepting an invitation does not enable reminder if user has default reminder pr 5011515 Quick add Events : To temporary calendar with READ+MODIFY permissions behaves wrongly. 5011634 Modifying the Timezone for a calendar as Co-owner is not consistent across views 5012352 Mail Options : Layout : mailoptions_layout.js file missing error in WS logs uwc options_ui 5012443 Migration done wrongly in case of wrong entries 5012489 Events with zero duration should be allowed 5013242 All Views : exceptions in WS log :Cannot flush a closed output stream 5014055 "keep a copy in inbox" option is not saved in Mail Filter 5014131 JES2_b07: i18n: display name of mail address becomes garbled during add addresses 5018340 webmail: 'Date' is displaying as English viewing mail 5018478 Mail help not focussed back. 5018487 Edit Task : unchekcing No Due populates wrong date/time 5019021 Vacation text garbled sometimes 5019588 l10n-uwc-options-1: Version Information dialog in English 5023634 JES2:07a: i18n: "Save" button is English in Address Book->Options 5025016 Edit Calendar Group: Fails editing certain calendar groups created in cal_expres 5025506 JES2:07a:l10n: "Date" and "Attachment" are in English in mail headers 5026361 Tasks View : Inconsistency in Browser behaviour when hit ENTER 5027129 how to NOT allow a user to have calendar if he has mail access or vice versa 5027138 Wrong Masthead font for Mail 5027152 Search for Calendars : does not trim trailing spaces 5027233 Tasks View : Printable does not pick up the sort order 5027234 Events View : Printable does not pick up the sort 5027318 Ability to store PAB data at user specific DB locations, for Horizontal Scalability 5027989 Anonymous Views: tzid parameter is not being used 5028111 Cannot access Calendar if preferred lang is null 5028787 New Group : Cannot add EMPTY group as a member to another group. 5028832 Inconsistency in behaviour for group with no email members 5028836 Edit contact/group blows up into the entire UWC page for Select Action 5029968 New Group :Adding other group members wihtout EMAIL ID's displays wrongly. 5030548 mail filter file to folder should be a pull down not fill in box 5030757 UWC UI: Locale fallback mechanisms does NOT work for underscore characters 5031469 Clicking on NEXT in any of the Search Window Pop-ups throws Javascript Errors. 5031525 Clicking on HOME link while viewing a mail throws Javascript error. 5032016 TS-2559 : Not able to see mail tab or mail in uwc 5032143 The Edit Task dialog is not displaying the previously saved due time for the task 5032275 JES2_b09: mail filter with message forwarding - Javascript error 5032336 JES2_b09: l10n_fr: in mail tab JavaScript Error pops up 5032818 Anonymous Event view : Wrong Tool tip for Sort by Title 5032928 i18n: ' is displayed instead of appostrophe in View Event popup for FR user 5033663 euro symbol garbled in import/export of address book 5033671 Expanding existing groups in certain cases behaves wrongly. 5034017 No way to disable Vacation messages 5035551 NullPointer exception for non-l10n language settin 5035889 Enter an invitee name and hitting ENTER does not add the invitee 5035893 New Calendar : Enter a Owner/User and hitting ENTER should add the Entry. 5035906 Search for Calendars : Hit ENTER not working. 5035910 Events View: Hit for Searching events not working in netscape 7.1 5036480 Users cannot set Calendar Preferences prior to opening default calendar 5038181 Addressbook throws fullpage error when migration is enabled and migration properties were not set 5038908 Week View : WS log warning : Spacer.gif not found 5038909 Day View : WS log warning : Spacer.gif not found 5038964 Mail Options : Vacation Message : spacer.gif not f 5038981 Anonymous Day view: Displays wrong timezone. 5042331 All Day events created in Outlook are displayed incorrectly in the week view 5042332 Clicking on Check Avaliability throws spacer.gif not found 5045982 getting old autoreply 5047435 JES2_b10a : wrong UI in filter preview when begins or ends selected 5048811 uwc through gateway, editing a task brings up portal desktop 5048818 uwc through gateway, cannot delete a recurring event 5048921 Uwc through gateway,cannot add tasks by clicking on Save and Add Another. 5049086 Page not refreshed to display updated contact/group info 5050108 Week View: 'Cancel' in popup while deleting a recurring event deletes a single instance. 5052361 View/Edit Tasks : Repeating Selection : spacer.gif not found 5052444 Clicking on "Printable" throws spacer.gif not found warning 5052494 need to trim address book parameters in db_config.properties, personalstore.properties 5052534 spacer.gif not found errors for Mini Calpop ups 5054877 JES2: build 10b UWC patch1: zhtw user login and GUI are zh Patch Installation Instructions: -------------------------------- To install this patch, run the command rpm -F This will freshen your existing RPM installation. Note that if this is a relocatable binary RPM and you have installed into a non-default location using the --prefix switch, you must specify the --prefix switch with the non-default location when you install this patch. Consult the rpm(1) man page for more details. Special Install Instructions: ----------------------------- ---------------------------------------------------------------------- IMPORTANT NOTE: These instructions are applicable if you have configured Communications Express prior to the installation of this patch RPM. If you intend to configure Communications Express after installation of this patch RPM, you do not need to perform any patch configuration procedures and you can ignore all instructions provided below. ---------------------------------------------------------------------- After you finish the patch RPM installation process (using the "rpm -F ") , please perform these steps in order to apply the patch files to the Communications Express deployment. Perform the steps as mentioned in the order below: a) Run /sbin/patch-config b) Run /sbin/install-newconfig c) Restart the Web Container Instance on which the Communications Express application is deployed for the changes to take effect. Where, represents the package base directory of Communication Express. example: /opt/sun/uwc How to run the config tools "patch-config" and "install-newconfig":- The below scenario is explained by taking some example directories. * Let us Consider that the Communication Express package is installed in "/opt/sun/uwc" directory. The tools are available at: /opt/sun/uwc/sbin/patch-config and /opt/sun/uwc/sbin/install-newconfig * The Communication Express application is deployed in "/var/opt/sun/uwc" directory. * The Communication Express patch 117752-01 needs to be configured * The patch-config tool shall be invoked as: /opt/sun/uwc/sbin/patch-config -d /var/opt/sun/uwc /opt/sun/uwc/install/patch/117752-01 * The install-newconfig tool shall be invoked as: /opt/sun/uwc/sbin/install-newconfig /opt/sun/uwc/install/patch/117752-01 How the patch config process works:- To apply the patch files and patch configuration to Communications Express deployment, the patch-config tool and the install-newconfig tool should be run. a) Run the "patch-config" tool: - This tool prepares the patch files and configuration and gets these files ready to be installed. - The new patch file versions are created under /install/patch/117752-01/save 117752-01 represents the number of the patch that is configured. The save directory has the same directory structure layout as the directory, except that the files under /lib/config-templates directory are relocated to . - For each file included in this patch, this tool prepares two files under /install/patch/117752-01/save. The two files are, and .new Where, represents the file backed up from previous Communications Express deployment. .new represents the new patch file version supplied in this patch. This file will be deployed in the Communications Express deployment when you run install-newconfig program. ----------------------------------------------------------------------- IMPORTANT NOTE: Please review the changes in the new patch files before applying them by running install-newconfig program. To review the changes, please see the difference between the files and .new ----------------------------------------------------------------------- b) Run the "install-newconfig" tool: - This tool installs the new patch files prepared by patch-config tool. - This program installs all the ".new" files prepared by patch-config tool into Communications Express deployment. Patch configuration backout instructions:- * To backout the patch configuration from Communications Express deployment, please perform the following steps: i) Run /sbin/backout-newconfig For example, to backout the patch 117752-01 configuration from Communications Express deployment, run /sbin/backout-newconfig /install/patch/117752-01 - This tool reverts back the Communications Express deployment to the state where it was before the patch configuration was applied. - This tool also helps maintain a backup of any file modifications performed after the last patch configuration under the directory "/install/patch/117752-01/save" with an extension ".backup". ----------------------------------------------------------------------- IMPORTANT NOTE: Do not run backout-newconfig tool more than once. If you run the tool again, your .backup files may be overwritten by old data. ----------------------------------------------------------------------- ii) Restart the web container instance on which the Communications Express application is deployed for the changes to take effect. ----------------------------------------------------------------------------- What's New in Communications Express 6.1P1 This section describes the new features added in Communications Express 6.1P1 A. Horizontal Scalabilty of Address Book Store 1. Introduction This patch ships with a new feature that supports the Horizontal Scalabilty of Address Book Server(ABS). Before this patch, the Address Book in Communications Express allowed Personal Address Book(PAB) entries to be stored in only one LDAP location per domain. This location was the 'defaultserver' instance defined in the db_config.properties file in the directory pointed by personalstore.properties of that domain. However such kind of deployment would not scale well with large number of users and contacts per Personal Address Book. The feature of Horizontal Scalabilty provides a new attribute called 'psRoot' in the User's LDAP entry. psRoot is an ABS complaint URL that defines the LDAP location where the user's Personal Address Book entries are stored and retrieved from. It is of the form: ldap://:/DN for example: ldap://mydir.com:389/piPStoreOwner=jsmith,o=sun.com,o=PiServerDb Now users can have their own psRoot value. This allows for the administrator to provision the users whereby PAB data for all users gets spread across multiple Directory instances. Note: The Address Book Server does not provide any utility to distribute psRoot values for users per scalabity policy. Administrators need to set a specific policy suited best for the organization and use custom scripts to set the psRoot value per that policy. Need to update LDAP schema In order to use this feature, the Directory Server Schema must be updated to include the attribute 'psRoot'. To do this, include the attribute 'psRoot' in the definition of ipUser object class in /config/schema/99user.ldif. (This is similar to the way it is included in 55ims-ical.ldif). 2. Use of psRoot The use of psRoot can be switched on and off using a parameter in the domain specific personalstore.properties file. The parameter is 'db.useUserPsRoot'. If set to 'true', the user's psRoot value is used. If set to 'false', the 'defautlserver' in db_config.properties is used. Since this parameter is not included in the personalstore.properties file by default, its value is defaulted to 'false'. If the use of psRoot attribute has to be switched on, the following entry must be added in personalstore.properties file: db.useUserPsRoot = true All psRoot values used must be supplemented by extra information in db_config.properties file that is being used for Personal Address Book. The following entries need to be provided for each Directory instance used in the psRoot values. .ldappoolmin= .ldappoolmax= .ldappooltimeout= .ldaphost= .ldapport= .ldapbinddn= .ldapbindcred= where is an unique string distinguishing one instance from another. Examples can be 'db1', 'db2'. The above parameters are identical to those provided for 'defaultserver'. This also means that one of the has to be 'defaultserver'. At runtime, the 'psRoot' user attribute is resolved to a Directory instance, using .ldaphost and .ldapport. If none matches, the 'defaultserver' instance is used. 3. Autoset of psRoot attribute Whenever the User logs in, default values are set for the psRoot attribute in the User's entry, as explained by the following scenarios. a) For new users for whom psRoot attribute is not present, a psRoot value is constructed, using a psRoot pattern (defined in personalstore.properties) and the 'defaultserver' Host and Port in db_config.properties. For example, using the default psRoot pattern, the default psRoot value set will be : ldap://:/piPStoreOwner=%U,o=%D,o=PiServerDb where, %U = login ID of the user (ex: "jsmith") %D = domain of the user (ex: "sun.com") b) For existing webmail users, if PAB Migration is enabled, the psRoot is constructed using the existing pabURI attribute and a mapping table defined in /WEB-INF/config/migrate.properties. The lookup table consists of the following type of enries in the migrate.properties file: Syntax: .abhostport = : For example, if you want to migrate the pab data from the directory running at pab.example.com:389 to address book directory running at abs.example.com:389 then the entry looks like this: pab.example.com.389.abhostport = abs.example.com:389 You may have as many lookups as required. For example, if the pabURI attribute for a user uses and , the psRoot constructed using the default psRoot pattern will be: ldap://:/piPStoreOwner=%U,o=%D,o=PiServerDb Default behaviour if the above lookup is not defined for a pabURI value: If no entry is provided in the mapping table that matches the pabURI, then the values for and would be same as and respectively. In other words, in absence of the above mapping table, the PAB entries from messaging Server will be migrated to the same directory instance, as per the Comms Express Address Book Schema. Which means that, in this case, the [Target] Directory Instance will be the same as the [Source] Directory Instance. Note that the lookup table is not defined by the patch installer. Hence the lookup table needs to be defined after patch install and the webserver needs to be restarted. Please note that for the above configuration to be used, appropriate paramters would have to be defined for directory Server instance in the db_config.properties, file pointed to by the personalstore.properties of that domain. See the previous point (no. 2) on how to set this information in db_config.properties. ------------------------------------------------------------------------------ Please consult http://docs.sun.com/ for product documents. README -- Last modified date: Friday, August 27, 2004