Contents

Helpful Links

Serena Documentation Center

SBM 10.1.5 Readme

System Administrator Deprecation List

Terminology Changes

The following terminology and component name changes have been made since the release of SBM 2009 R4.

Supported Configurations

Detailed information about supported platforms and software configuration is available in the Supported Platform Matrix. (Click View to see the complete platform matrix for this release).

Build Numbers

The following component build numbers apply to this version:

• SBM User Workspace and Serena Work Center: 10.01.05.01.1127 (Build 94)
• SBM Composer : 10.1.5.1 (Build 34)
• SBM System Administrator and SBM Application Administrator: 10.01.05.01.1127 (Build 94)
• Application Repository: 10.01.05.01.1127 (Build 86)
• SBM Configurator: 10.01.05.01.14
• Database version: 1015010005

Third-Party Tools

For more information regarding third-party software copyrights and license information, refer to the files under "My Downloads" or "Product News" at http://www.serena.com/support.

Important Notes for Major and Minor Upgrades

The following notes apply to both major and minor upgrades:

• SBM 10.1.5.1 requires Serena License Manager 2.2. You must upgrade to version 2.2 before you can upgrade to SBM 10.1.5.1. .
• In order to prevent notifications from being sent for changes that have not happened recently, SBM now deletes notification events that are older than 90 days that contain a THREADID during the database upgrade. To check if you have events that will be deleted, refer to the SQL queries in solution S140945.
• SBM Configurator warns you if your installation currently uses default certificates (which should be replaced) or if your current certificates will expire soon.
  Important: To properly secure your installation, you must generate new key pairs even if you do not plan to use SSO. If you do not generate new key pairs, then the default certificates that the STS inherently trusts are used. To increase security, launch SBM Configurator and generate new unique certificate for all components. For details, see "Securing SBM" in the SBM Installation and Configuration Guide.
• If you are upgrading to any release after SBM 10.1.4 (when backlogs were first introduced) and you have configured a JBoss cluster, duplicate Backlog entries might appear when you manage views in Serena Work Center. To work around this problem, after the upgrade is finished, start JBoss on only one node, launch Work Center, and then start JBoss on the remaining nodes.
• The use of logical field names in the $FIELDVALUE base item template tag is deprecated and will not be supported in future releases. Serena recommends that you review your current e-mail templates and replace field display names with the database field name as part of the upgrade process.
• Beginning with 10.1.4, custom forms should display and perform as they did before the upgrade. The first time you redeploy process apps after the upgrade, you must redeploy from SBM Composer instead of SBM Application Repository. If you redeploy from SBM Application Repository, you may encounter problems with custom forms. To solve these problems, redeploy process apps that contain these forms from SBM Composer.
• HTML Rendering for Notes

  HTML rendering and Rich Text editing is now enabled by default for all notes in your system. To disable these features for notes, clear the Render HTML in Notes check box located on the HTML tab of the Settings dialog box in SBM System Administrator.

• As part of the database upgrade, new indexes are added to the CL_CONTEXT_VALUE and CL_LOG tables to prevent time outs from occurring when you try to view Common Log data in SBM Composer or SBM Application Repository.
  Important: In order to add the new indexes, these tables will be emptied during the upgrade process. If you need to view Common Log data that was present prior to the upgrade, ensure that you have backed up these tables.
• As of 10.1.2, the SSO Login Application (Federation Server) has been merged with the SSO Security Token Service (STS) into a single SSO Security Server (also known as the Identity Provider (IDP)). This means that the ALFSSOLogin.war and TokenService.war directories have been merged and replaced with a new idp.war directory on the SSO server.
  Important: If you have created custom SSO integrations, you must review all URLs and calls to ensure that they use the new directory names. For example, if your existing integrations call the Security Token Service (STS), you must ensure that the new idp.war directory is used (instead of ALFSSOLogin.war or TokenService.war).

  The endpoints of the SSO services must be changed accordingly. The relative URIs will stay the same, but since the application is new, the login application entry point will be:

  http(s)://host[:port]/idp/login

  For the STS, it will be:

  http(s)://host[:port]/idp/services/Trust

• For Oracle systems, the required roles and privileges for the SBM schema user have changed. Please visit S133641 for details.
• For Oracle systems, you must perform the database upgrade using either the SBM DSN that is installed with SBM or a system DSN that uses the "Oracle for SBM" driver that is installed with SBM. If your system used the Mashup2009 DSN prior to the upgrade, that DSN is automatically converted to use the new "Oracle for SBM" driver, if it was not using this driver already.
  Important: The underlying driver in the DSN that ships with SBM was changed in SBM as of version 10.1. If you currently use the Mashup2009 DSN with SBM, you do not need to do anything—the DSN will be updated automatically. If you created your own custom DSN with the "Oracle for SBM" driver prior to upgrading to SBM 10.1 or later, then you must recreate the DSN and use the new "Oracle for SBM" driver that ships with SBM after the upgrade is finished.

  If you previously designated a SID for Oracle, then that SID is automatically used in the Service name field in SBM Configurator. Verify with your DBA that the correct service name is now used in the Database Servers tab of SBM Configurator.

• User credentials in SBM Application Engine Web service calls that use Basic authentication are now handled exclusively by SBM Application Engine itself, instead of IIS. This configuration is common if your SBM system is set up with NT Challenge Response for end-user authentication. After upgrade, this means that you must now specify the Windows domain for Web service calls in SBM Configurator, otherwise the domain that the IIS server machine is installed on is used for user validation.
• If your database does not contain at least one Regular User or Managed Administrator account with Remote Administration privilege, use the Reset Administrative User Access wizard in SBM System Administrator after the database upgrade is finished. This wizard enables you to define at least one user as your primary system administrator (an account that has Regular User or Managed Administrator product access with Remote Administration privilege) who can log in to SBM Application Administrator. For details, see the SBM System Administrator Guide.
• Note: The following information is only applicable if you had previously upgraded to 10.1 or 10.1.1.1. If you did not upgrade to either version prior to upgrading to 10.1.5.1, then you can ignore the following information.
  Values in promotion profiles that were created in 10.1 or 10.1.1.1 were set to All by default. As of 10.1.1.2, entities for new items (items added to a process app since the profile was created) will be set to None by default.
  In addition:

  • Profiles created prior to 10.1 that had entities set to None may have been incorrectly using All. These entities will be set back to None.
  • Profiles created in 10.1 or 10.1.1.1 that had entities set to the default All may also be set to None. These entities must be manually corrected.

  In general, it is recommended that you review your promotion profiles and adjust the settings accordingly.
• If you have applications in SBM that use Tomcat (such as DVM), you must clear out the Tomcat work subdirectory (typically %TOMCAT_HOME%/work). Clearing the browser cache alone is insufficient. This applies to both Firefox and Internet Explorer browsers.