Release notes for Workplace for Business Controls and Reporting, Version 2.5.1

Last updated August 30, 2005

About this document

This document describes the known defects and workarounds for IBM Workplace for Business Controls and Reporting, Version 2.5.1 and contains the following sections:

Known defects and workarounds

Creating page titles for non-English languages in a multi-tenant environment

The Version 2.5.1 Information Center provides instructions for manually creating page titles for multi-tenant installations. Those instructions do not describe how to create the page titles for the non-English languages that are supported for Version 2.5.1. This release note provides instructions for creating page titles for the other languages.

If you install the product in a multi-tenant environment, perform the following steps after you complete step 12e of the Information Center topic "Manually install Version 2.5.1 in a multi-tenant environment":

  1. Go to the computer where WebSphere Portal is installed or to another computer that has drive access to the computer.
  2. Find the files that contain the page titles for the non-English languages. You will need to use the files in a subsequent step in this procedure. The files are named wps_root\config\work\wbcrPageTitle_cc.properties, where wps_root is the root directory for the WebSphere Portal installation (such as C:\WebSphere\PortalServer) and cc is a locale (language). The supported locales are: de (German), es (Spanish), fr (French), it (Italian), ja (Japanese), ko (Korean), pt (Brazilian Portuguese), zh (Simplified Chinese), and zh_TW (Traditional Chinese).
  3. Log in to Workplace for Business Controls and Reporting.
  4. On the WebSphere Portal toolbar, click Administration.
  5. Click Portal User Interface > Manage Pages. Manage Pages displays.
  6. In the list of page titles, click My Portal.
  7. In the list of page titles for My Portal, click WBCR. The list labeled Pages in WBCR displays.
  8. Perform the following steps for each page in the list:
    1. Click the icon Edit Page Layout for the page. The Edit Layout page displays.
    2. On the Edit Layout page, click the Edit properties button.
    3. In the section Advanced options, click I want to set titles and descriptions.
    4. To create page titles for the languages listed in step 2, perform the following steps for each language:
      1. Click the Edit icon for one of the languages.
      2. In the Title field, enter the correct title for that language. To determine the correct title, perform the following steps:
        1. Use a text editor that supports Unicode (UTF-8) to open the wbcrPageTitle properties file for that language. You found the file in step 2.
        2. In the properties file, find the section for the page titles. That section is labeled wbcr 2.5 main pages.
        3. In that section, find the page title property. For example, the Home page title property is wbcr.manager.Home.title.
        4. Copy the value of the page title property and paste the value from the file into the Title field.
        5. Click OK to save the title.
      3. On Page Properties, select another language and repeat the steps to create the page title for that language.
    5. After you have created values for all of the languages for that page, click OK or Done until you return to the page that lists Pages in WBCR.
    6. Select another page in the list and repeat the steps to add language titles for that page.
  9. Log off after you have created titles for all of the pages.

(5907)

Migrating from Version 2 to Version 2.5 to Version 2.5.1

If your installation needs to migrate to Workplace for Business Controls and Reporting, Version 2.5.1 and your current installation is Version 2, you will need to migrate from Version 2 to Version 2.5 before you can migrate to Version 2.5.1. That migration sequence is discussed in the topic "Migration considerations" in the Version 2.5.1 Information Center.

When migrating from Version 2 to Version 2.5, adhere to the following requirements in addition to the ones documented in the Version 2.5 Information Center:

(6007)

Legend for COSO heat map is not included in Excel format for reports

The Reports tab enables creating reports in a variety of formats. One of the formats is the COSO heat map. You can save a report to Adobe Portable Document Format (PDF) or Microsoft Excel format. If you save a COSO heat map to Excel format, the legend for color coding will not be included in the report.

There is no workaround for this problem.

(3896)

Certain removed owners and delegates are not recorded in the audit trail

If the user deletes a process whose Documentation Complete field is set to Yes, the audit trail will not include entries indicating that the owner and delegates have been removed. That information is missing for the deleted process as well as the subprocess, control, and procedure that are child nodes of the process.

There is no workaround for this problem.

(4087)

Changes to permissions for global roles might not be visible in the current login session

A global role is a role that includes permission for at least one global type. If the administrator assigns a user to a global role while the user is logged in, the user must log off and then log in again to see the changes.

There is no workaround for this problem.

(4403)

Problem with the version task repeating

If the administrator creates a version, the task might repeat and produce multiple versions that were not requested. The following conditions can exist when this problem occurs:

6/21/05 13:56:43:830 GMT+08:00] 5734902b TimeoutManage I WTRN0006W: Transaction 57415344:0000000000006d79000000017c497e99b380b29cc3ae238b703cc9805a140d715765625370686572655f506f7274616c[] has timed out after 120 seconds. [6/21/05 14:15:24:709 GMT+08:00] 3a75d028 WSRdbDataSour I DSRA8203I: Database product name : DB2/6000 [6/21/05 14:15:24:730 GMT+08:00] 3a75d028 WSRdbDataSour I DSRA8204I: Database product version : 08.01.0006 [6/21/05 14:15:24:731 GMT+08:00] 3a75d028 WSRdbDataSour I DSRA8205I: JDBC driver name : IBM DB2 JDBC 2.0 Type 2

If you need to increase the transaction lifetime timeout, perform the following steps:

  1. Log in to the Administrative Console for the WebSphere Application Server.
  2. In the navigation, click Servers > Application Servers.
  3. In the list of application servers, click WebSphere_Portal.
  4. In the list of Additional Properties, click Transaction Service.
  5. In the field Total transaction lifetime timeout, increase the value of the timeout. When Workplace for Business Controls and Reporting is installed on the portal, the timeout value is set to 1200 seconds.

(4429)

Problem with creating the database during installation

This symptoms of this problem are:

The possible causes of the problem are:

(5330)

Problem in searching for My Procedures when user owns large number procedures

The Navigator for the tabs includes the function Display My Lists, which enables the user to filter the business elements hierarchy to display only business elements for which the user is the owner or a delegate. In the list of filter options, My Procedures displays the procedures for which the user is the explicit owner or delegate. That filtering option can be further enhanced by selecting the option Include items I own indirectly, which displays the procedures for which the user is the explicit owner or a delegate plus the procedures that are child nodes of a business element for which the user is the explicit owner or a delegate.

If a user is the explicit and indirect owner or delegate for an extremely large number of procedures (such as 10,000) and the user selects both filtering options, the system might timeout before the results are returned. To avoid this problem, the user should not select the option Include items that I own indirectly.

(5359)

Steps are missing from the instructions for creating custom reports

The Information Center contains instructions for creating custom reports. After you perform the steps documented in the topic "Creating custom reports", you will need to perform the following steps to upload the reports to Crystal Enterprise:

  1. Launch the Crystal Publishing Wizard.
  2. Click Next on the Welcome panel.
  3. Enter the CMS name and password. Click Next.
  4. On the Select a File panel, click Add Folder.
  5. Click Find Directory and specify the directory that contains the new custom report template files (the .rpt files).
  6. Click OK. The report templates should display in the list.
  7. Click Next.
  8. Select the folder that contains the default report templates for Workplace for Business Controls and Reporting. Ensure that the folder is highlighted and then click Next.
  9. On the Location Preview panel, click Next.
  10. On the Schedule Interval panel, click Next.
  11. On the Repository Refresh panel, click Next.
  12. Ensure that Publish without modifying properties is selected and click Next.
  13. When the report templates list is displayed for verification, click Next to begin publishing.
  14. Click Finish.

The missing steps will be included in the next revision of the Information Center.

(5654)

Problem with importing catalogs in a clustered environment

The page Settings > Import supports importing and re-importing catalogs. In a clustered environment, an imported catalog file is only on the node where the import task was requested. The file is not shared with the other nodes in the cluster.

The import task relies on a scheduling function in the underlying WebSphere Application Server. That scheduling function is designed so that only one instance can be active in a cluster. The other instances of that scheduling function are dormant. Import tasks on the dormant instances must be handled by the active instance. A catalog import or re-import will fail if the catalog file is not on the cluster node that will handle the import task. The file must be on the node with the active instance of the WebSphere Application Server scheduling function.

There is no workaround for this problem.

(5105)

Accessing the Version 2.5.1 Information Center

A copy of the Information Center is automatically installed with the product. The Information Center is also available on the Web. You can use the following methods to view the Information Center.

Problem adding an attachment after logging in again

An attachment is a document or a Web address that a user can add to a process, a subprocess, or a procedure. If the session expires and the user logs in again, the user cannot add an attachment after logging in. This problem will be fixed in a future release.

Use the following workaround:

  1. After the session expires, log in again.
  2. Click the appropriate tab (Documentation or Evaluation).
  3. In the Navigator, click the target business unit. The Detail portlet will refresh.
  4. Navigate to the process, subprocess, or procedure to which you want to add an attachment.
  5. Add the attachment.

(5668)

Problem with Mozilla Web browser displaying file names

Mozilla does not display certain non-English characters in the file names for catalog files or attachment files. If you enter a file name that contains one of the problem characters, Mozilla will display an underscore character (the character _ ) for the problem character. This problem will be fixed in a future release.

Use one of the following workarounds:

(5694)

Problem with displaying double-byte characters

Version 2.5.1 has difficulty displaying characters for the following double-byte character languages: Japanese, Korean, Traditional Chinese, and Simplified Chinese. This problem will be fixed in a future release.

Use the following workaround:

  1. Add an encoding parameter to the Java Virtual Machine for WebSphere Portal. Perform the following steps:
    1. Log in to the Administrative Console for WebSphere Application Server.
    2. In the navigation area, click Servers > Application Servers.
    3. In the list of application servers, click WebSphere_Portal.
    4. Scroll down to the section Additional Properties and click Process Definition. The Process Definition page displays.
    5. Scroll down to the section Additional Properties and click Java Virtual Machine. The Java Virtual Machine page displays.
    6. Scroll down to the field Generic JVM Arguments.
    7. Add the following parameter at the end of the field: -Dclient.encoding.override=UTF-8
    8. Click OK.
    9. Click Save on the console toolbar.
    10. Restart the server WebSphere_Portal.
  2. For the target languages, change the default character set used for HTML markup. Perform the following steps:
    1. Log in to Workplace for Business Controls and Reporting.
    2. On the WebSphere Portal toolbar, click Administration.
    3. Click Portal Settings > Supported Markups. The Manage Markups page displays.
    4. In the list of markup languages, select html and then click Edit selected markup.
    5. Verify that the field Default character set has the value UTF-8.
    6. Click Set locale-specific setting.
    7. Perform the following steps for the languages Japanese, Korean, Traditional Chinese, and Simplified Chinese:
      1. Select the language.
      2. Click Edit setting for selected language.
      3. In the field Character Set, type the following value: UTF-8
      4. Click OK.
    8. After you change the settings for each language, click OK until you return to the Manage Markups main page.

(5020)

Notices

AIX, IBM, and Workplace are trademarks of the IBM Corporation in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marks of others.

 

(c) Copyright IBM Corporation 2005. All Rights Reserved.

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.