Contents

New Installations of Serena Business Manager

If this is a new installation, download version 2009 R4 from http://www.serena.com/support and then follow the instructions in the Serena^® Business Manager Installation and Configuration Guide to install Serena Business Manager for the first time.

Upgrading From TeamTrack 6.6.1.x

If you have TeamTrack 6.6.1.x installed, download version 2009 R4 from http://www.serena.com/support, and then follow the instructions in Moving to Serena^® Business Manager. This guide only covers upgrades from TeamTrack.

You should also refer to solution S137372 to learn about the upgrade preparation utility.

Upgrading From Earlier Versions of SBM

To test this release, you must mimic your installation on a separate set of hardware. This test installation should include all environments used by your system. You can then upgrade and test this installation before upgrading your production installation. To upgrade successfully, 2009 R4 must be installed on each server machine and on each machine on which SBM Composer and SBM System Administrator are installed.

Important Notes for Major and Minor Upgrades

• The Application Administrator fails to launch on Oracle systems if the blocksize for the tablespace is less than 8k. To work around this problem, create a .dmp of the existing SBM Application Repository tablespace and restore it into a tablespace with a blocksize that is at least 8k.

• Some installations of SBM do not allow SBM Configurator to start the Serena Common JBoss service if HTTP Analyzer V6 is installed on the same machine. If you are unable to start JBoss from SBM Configurator, contact Support and refer to solution S138009 for further assistance. You can also use the Windows Services Manager to stop and start the Serena Common JBoss service if it will not start from SBM Configurator.
• The Amazon widget fails to run and returns a 404 error unless version 2.0 of the ASP.NET Web service extension is installed and enabled in IIS. To verify that it is enabled, open IIS, select the Web Service Extensions folder, and search for ASP.NET. If the ASP.NET 2.0 status is prohibited, click Allow to enable it. If ASP.NET 2.0 is not installed, install it using the following prompts from the command line.
  On 64-bit servers, send the following command:

  C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727>aspnet_regiis.exe -I -enable

  On 32-bit servers, send the following command:

  C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis.exe -I -enable

  Once you send the command, you should see the following:

  Start installing ASP.NET (2.0.50727).
  .........................
  Finished installing ASP.NET (2.0.50727).

  Once the installation is finished, refresh the Web Service Extensions folder in IIS. You should see that ASP.NET v2.0.50727 is now installed. Click Allow if it is not enabled.

• For new multi-environment installations (which contain development, test, and productions servers), it is recommended that you create unique databases to host the Common Log database in each environment. This ensures that the Common Log messages that you see are specific to each environment. To configure this type of installation, you must provide unique schema or database names for the Common Log database in the Database Servers tab of SBM Configurator on each SBM server installation (development, test, and production).

  For existing multi-environment installations (the development, test, and productions servers that you plan to upgrade), you can create new databases to host Common Log data for each environment. For example, you can back up your current Common Log database on your production server and restore it to a new space on your development database server. Once the data has been restored in the development database, purge the existing Common Log database space on the production database server and create a new database space for your test server and (this results in two blank databases--one for test and one for production). Run SBM Configurator on the test and development SBM servers and update the Database Servers tab with the database connection information for the two new unique Common Log databases. This ensures that you have unique databases for the Common Log in each environment and it also moves your existing Common Log data from the previous production space into the new development space.

• Microsoft .NET framework 3.5.1 is not installed by the suite installer on Windows 2008 R2 servers if version 3.5.1 is not detected on the server. To work around this issue, navigate to the Control Panel, select Programs and Features, select Turn Windows features on or off, and install .NET 3.5.1 from the Features list.
• On upgrade, SBM Configurator displays port 8243 as the SSL port for JBoss, even though you might not have configured SSL with JBoss in a older version. In prior versions, HTTPS was enabled by default because an HTTPS connector and sample certificate were provided by SBM. However, this sample configuration does not secure the SBM User Workspace. To secure end-user connections into SBM, run SBM Configurator in utility mode and select Security from the Advanced Settings menu. (The Single Sign-On (SSO) tab has been renamed to Security). In the SSL sub-tab, you can generate, import, or remove SSL certificates for the IIS and JBoss components that are installed on the server. This secures end-user connections into SBM as long as the request is sent using HTTPS.
• System DSNs that use the "Oracle for SBM" driver cannot be deleted after SBM is uninstalled. To work around this issue, delete all DSNs that use the "Oracle for SBM" driver before you uninstall SBM. If you have already uninstalled SBM and you still need to delete a DSN that uses this driver, contact Support and refer to solution number S138013 for assistance.
• The SBM Application Administrator product logo may not be visible after you upgrade to SBM 2009 R4. To workaround this problem, stop the Serena Common JBOSS service, and delete the work folder located here:

  installationDirectory\Serena\SBM\Common\jboss405\server\default

  After you remove the work folder, restart Serena Common JBOSS.

• Links to auxiliary items cannot be added to primary items. To work around this problem, find the auxiliary item and add a link to the primary item.
• In Update mode, the Rich Editable Grid uses the first found Update transition with the name "Update." Regular transitions named "Update" are not used in Update mode, but these transitions can be used when users select the "All Transitions" option for editing items in the grid.
• Commas included in values for required Numeric float fields are not accepted as valid values.
• Keyboard navigation features are not fully functional when users submit or transition items or use the Action drop down list inside the Rich Editable Grid.
• When a user submits an item that goes into a decision state and then cancels a transition that is invoked as a result of a decision step, they receive an error message that indicates an item could not be found. The error message should state that the Submit action was successfully canceled.
• Users who are granted the "View Attachments I Authored" privilege and no other "view attachments" privilege cannot see attachments they add to items when custom forms are used. To work around this problem, grant these users additional privileges to view attachments, such as the "View Attachments on Any Item," or use quick forms.
• Users who are not granted privileges to view attachments are unable to view unrestricted attachments on items when custom forms are used. To work around this problem, grant these users privileges to view attachments or use quick forms.
• The Back to Results link may be removed from the drill-down results list for Distribution reports. This typically happens when the drill-down results contain a large number of items, and users click the "All n" link at the bottom of the page to see the full list. To work around this problem, run the report again.
• Users cannot use the Accessible Interface to complete Update transitions that require authentication. To work around this problem, users can switch to the regular SBM User Workspace to complete Update transitions that require authentication.
• Database exceptions occur in Drill Through reports when a Multi-Selection or Multi-Relational field is used in the driving report to control the output of a secondary report. To work around this issue, use a field type other than Multi-Selection or Multi-Relational in the driving report.
• Users may not notice the error when they provide an invalid value for a Numeric field on the Rich Editable Grid. This and other changes cannot be saved until the user provides a valid value.
• For Editable Grid reports, when you select a value from a drop-down list, the value will not populate the field. You must immediately perform the action again on the drop-down list for the value to remain selected.

• If a field does not have the Appears in report field list check box selected in its Property Editor, the field is not included in the Rule Palette, and therefore cannot be added to the left side of a rule expression. To work around this issue, select the check box, add the field to the rule expression, and then clear the check box to restore the original properties.
• When a process app is upgraded to SBM 2009 R4, the new "application variables" design part is added, but the parent application does not get checked out. Data loss could result if a designer adds application variables and then checks out or gets the latest version of the parent application.

• An asynchronous orchestration workflow fails if the name of the application that invokes it starts with a number. To work around this issue, do not use a number as the first character of an application.
• A deadlock error could occur when running an orchestration workflow in a high-volume environment. For assistance, contact Customer Support and refer to solution S137994.
• There could be runtime failures when an orchestration workflow has nested ForEach steps, and the output of the inner ForEach step is mapped directly to the input of a subsequent Service step. There could be deployment failures if the the output of the inner ForEach step is a complex type, one of its child elements has the Boolean data type, and that child element is mapped directly to the input of a subsequent Service step. For the workaround to both of these problems, go to solution D11937 .

• Role assignments are not copied when you copy a group. To work around this problem, edit the new group after it is created and add role assignments.

• If you decide to enable or disable Single Sign-On (SSO) in your installation, you must also redeploy all of your deployed process apps.
• You may experience performance problems if you use Single Sign-On (SSO) and enable automatic session renewal in the SBM Configurator. This problem occurs when a large number of users logs into the system at the same time. To work around this problem, disable automatic session renewal. This setting is located on the Security tab n the SBM Configurator.
• The Single Sign-On (SSO) components included in the SBM 2009 R4 is incompatible with SSO components included within the released version of Dimensions CM 2009 R2 and CM 2009 R1. Users of SSO between SBM and Dimensions CM must install Dimensions CM 2009 R2.05 or later or upgrade to the major release CM 12.1 before upgrading to SBM 2009 R4. Dimensions CM 2009 R2.05 and Dimensions CM 12.1 are expected to be available inMarch 2011.

• In SBM Web services version 7.2, Multi-Relational fields no longer accept a comma-separated list of internal (tableid:internal-item-id) values on update. Instead, you must specify values individually in an array of values to update a Multi-Relational field. If you are currently using an older version of SBM Web services, please note that you may need to alter any existing calls that use comma-separated lists to update Multi-Relational field values.
• SBM fails to parse upper case Boolean values that you manually set in SBM Application Engine Web service calls that are sent from within SBM applications. SBM only accepts lower case Boolean values in addition to 0 or 1. To work around this problem, leave the value empty (accepting the default value).

• The commands that appear in the Moving to Serena^® Business Manager guide that illustrate how to execute the Unicode Upgrade Utility are incorrect. When you execute the utility, you must enter the utility name without any spaces. For example, use the following format:

  UnicodeUpgradeUtility "DSN=myDSN;UID=sa;PWD=sa"

  Instead of:

  Unicode Upgrade Utility "DSN=myDSN;UID=sa;PWD=sa"

• The documentation incorrectly refers to the Enable Database Logging check box on the Database tab of the Settings dialog box in SBM System Administrator. This check box has been removed because administrative logging is now always enabled.

• Suite and client installs are interrupted on Japanese versions of Windows 2008, Windows 7, and Windows Vista unless Web Service Enhancements (WSE) 3.0 is pre-installed. To work around this problem, download WSE 3.0 from Microsoft before running the suite or client installers.
• The Template Reply Address label is truncated on the Mailbox Configuration tab for the Mail Client in SBM System Administrator.
• SBM incorrectly appears on several tabs on the LDAP Setup and Tools dialog box in SBM System Administrator.
• Some help topics in SBM Configurator appear in English instead of Japanese when you are on a Japanese operating system. To work around this problem, refer to the same topics in the Serena^® Business Manager Installation and Configuration Guide for assistance.