Turn Off Tabs
Serena Business Manager 2009 R4.01 Readme
This readme file contains information about this release. Last updated on 2011-06-23.

Contents

About this Release

Serena Business Manager 2009 R4.01 supports new installations—you do not need to install a previous version of SBM before installing this version. If this is a new installation, download version 2009 R4.01 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.

Serena Business Manager 2009 R4.01 supports two different upgrade paths. If you have installed SBM 2009 R3, follow the steps in Minor Upgrades to upgrade to 2009 R4.01. If you have not already upgraded to version 2009 R3 or later, you can upgrade directly to 2009 R4.01 from most previous versions. If you have not yet upgraded to at least 2009 R3, follow the steps in solution S138037 to perform the upgrade to 2009 R4.01.

The 2009 R4 release notes are available here. You can view the 2009 R4 readme here.

Terminology Changes

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

Note: If you are upgrading from TeamTrack, refer to the Moving to Serena® Business Manager guide for terminology changes from TeamTrack to SBM.
Old Term New Term
Serena Business Mashups Serena® Business Manager or SBM
mashup process app
Mashup Server SBM Server
Configuration Utility SBM Configurator
Mashup Composer SBM Composer
Mashup Manager SBM Application Administrator
Mashup Administrator SBM System Administrator
Web interface SBM User Workspace
Mashup Repository SBM Application Repository
Mashup Script SBM AppScript
Mashup Registry AppCentral™
Mashups API SBM API
mashup tool event definition
mashup event event
Note: Systems created beginning with 2009 R4 include a Global Process App. In systems created before 2009 R4, the Global Process App is referred to as the Global Mashup.

Supported Configurations

The supported configurations for 2009 R4.01 are identical to those published for 2009 R4. Detailed information about supported platforms and software configuration is available in the Supported Platform Matrix.

Web Services

The latest Web service calls can be found in the sbmappservices72 and sbmadminservices72 WSDLs. All TeamTrack Web services and earlier SBM Web services (ttwebservices, aewebservices70, and aewebservices71) are still compatible with this release. However, these WSDLs have been deprecated and will not contain any of the new calls or parameters found in sbmappservices72 and rel. For new Web service implementations, use these new WSDLs.

Build Numbers

The following component build numbers apply to 2009 R4.01:

  • SBM User Workspace: 2009R4.01 Build 22
  • SBM Composer: 2009R4.01 Build 012
  • SBM System Administrator: 2009R4.01 Build 22
  • Application Administrator: 2009R4.01 Build 13
  • Database version: 904010102
Note: For each release, the component build number is changed only when a code change has been made to a particular component. If no changes have been made, the component build number is the same build number that was used in the last release.

What's New

Serena Service Manager 1.1

Serena Service Manager 1.1 is a flexible process-based IT service manager offered by Serena. It contains all of the functionality of SBM and additional functionality specific to the solution. The new version of Serena Service Manager includes the following enhancements:

  1. The new Relationship Explorer displays the relationships between configuration items using a graphical layout. It allows you to see the relationships between various CIs and lets you navigate the relationship tree to view connections to additional items.

    Note: If you install Serena Service Manager from a DVD, the Relationship Explorer is found in manager/Extension directory. Copy these files to your SBM installation directory as described under Installing Relationship Explorer in the Serena Service Manager Guide.
  2. Process workflows have been updated to use conditional routing. Conditional routing automatically routes an item to a particular state based on visually-designed rules that evaluate item data.
  3. All process workflows now contain swimlanes. Swimlanes group states within the workflow, which lets you see the groups or users responsible for the items at each step of the process.
  4. Additional minor enhancements to improve ITIL compliance and usability.

Upgrades

This section provides general upgrade information and important notes for all upgrades to 2009 R4.01. Before you upgrade, review the following sections and proceed with the upgrade according to the version that you currently have installed.

Supported configurations, new features, and changes in behavior are listed in the Release Notes. Please refer to prior readmes for a list of features and changes that were added in another version before this release.

Upgrades from the following products and versions are supported in this release. Upgrades are supported from specified base releases and patches on those base releases.
  • TeamTrack 6.6.1.x
  • Serena Business Mashups 2008 R1.05 (Japanese version only)
  • Serena Business Mashups 2008 R2.0x
  • Serena Business Mashups 2009 R1.0x
  • Serena Business Mashups 2009 R2.0x
  • Serena Business Mashups 2009 R3.0x
  • Serena Business Manager 2009 R4.0x

New Installations of Serena Business Manager

If this is a new installation, download version 2009 R4.01 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.01 from http://www.serena.com/support, and then follow the instructions in Moving to Serena® Business Manager. This guide only covers upgrades from TeamTrack.

Note: This version requires a database upgrade. Back up your existing database before installing this version.

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.01 must be installed on each server machine and on each machine on which SBM Composer and SBM System Administrator are installed.

SBM 2009 R4.01 supports both major and minor upgrades:

Important Notes for Major and Minor Upgrades

The following notes apply to both major and minor upgrades:
  • You must disable the User Access Control setting before you install SBM on a Windows 2008 or 2008 R2. To disable this setting, perform the following steps:
    1. From the Windows Start menu, open the Control Panel and select User Accounts.
    2. On Windows 2008, open the User Accounts window and click Turn User Account Control on or off. On Windows 2008 R2, click Change User Account Control settings.
    3. On Windows 2008, clear the Use User Account Control (UAC) to help protect your computer check box. On Windows 2008 R2, move the slider to the Never notify position.
    4. Click OK.
    5. Reboot the server and perform the install.

    After the installation is finished, you can enable UAC; however, you must disable it again if you attempt to uninstall SBM.

  • Microsoft .NET Framework 3.5.1 must be installed on all Windows machines. If it is not detected, .Net Framework 3.5.1 is installed by SBM. To save download and installation time, you may want to install version 3.5.1 prior to running the SBM installer. Also, if you will not have Internet access during the installation, you should download and install 3.5.1 beforehand.
  • On Windows 2003 systems, the SBM installer requires Windows Installer 4.5 in order to install SQL Express without a system restart. (This is not a requirement if you are not installing SQL Express). If you do not pre-install Windows Installer 4.5, the SBM installer performs the install for you and prompts you to restart the system after you select the option to install SQL Express. When the system restart is finished, you must begin the installation again starting from the Welcome dialog. Therefore, to avoid an unscheduled system restart, download and install Windows Installer 4.5 from Microsoft, restart your server, and then install SBM. To determine if version 4.5 is already installed, open the command line and enter the following: 
    msiexec -?
  • If you are connecting to a Microsoft SQL Server database, you must select the SQL Server Native Client driver. The SQL Server ODBC driver is not compatible with SBM.
  • If you upgrade to Windows 2008 in addition to upgrading SBM, you must enable the Web Server (IIS) role before you install the SBM Application Engine on a Windows 2008 server. If the Web Server (IIS) role is not already configured on your Windows 2008 server, see the "Enabling the Web Server (IIS) Role in Windows 2008 Server" section in the Serena® Business Manager Installation and Configuration Guide for steps to enable the role.
    Note: SBM requires Internet Protocol Version 4 (IPv4) on Windows 2008 systems (IPv6 alone will not work). Both IPv4 and IPv6 protocols can be enabled simultaneously on Windows 2008; however, SBM requires at least IPv4 on each Windows 2008 server in your SBM environment. If users experience log in problems while IPv6 is enabled, see D10608 for a workaround.
  • If you decide to enable or disable Single Sign-On (SSO) in your installation as part of the upgrade, you must also redeploy all of your deployed process apps.
  • Upgrade support for migrating to a 64-bit version of SBM is handled through a new suite installation on one or more 64-bit Windows 2008 R2 servers. You can either perform a Custom install that installs one or more SBM components on multiple 64-bit operating systems or you can perform a Complete install, which installs every component on a single 64-bit server. You can still perform Remote Administration tasks or connect directly to the database via ODBC using 32-bit clients.

    You can use the SBM System Administrator that is installed by the suite installer on a 64-bit Windows 2008 R2 server to upgrade the database. As part of the upgrade, review and upgrade any scripts and APIs that were originally created on a 32-bit operating system to ensure that they also run on a 64-bit system. For example, if you have any scripts that load .dll files, those dll files must be upgraded to run on a 64-bit machine.

    The hardware requirements for SBM running on a Windows 2008 R2 64-bit operating system are as follows. The memory requirements are greater than those for a 32-bit operating system.

    • Recommended Requirements – 2 GHz or higher multi-processors; 16 GB memory; 10 GB operational disk space.
    • Minimum Requirements – 800 MHz or higher single processor; 8 GB memory; 2.5 GB operational disk space.
  • For Oracle systems, you must perform the database upgrade using either the Mashup2009 DSN that is installed with SBM or a system DSN that uses the "Oracle for SBM" driver that is installed with SBM. As part of the 2009 R4.01 upgrade, the existing Mashup2009 DSN is automatically converted to use the new "Oracle for SBM" driver. If you attempt to use a DSN other than the Mashup2009 DSN provided by SBM, the SBM System Administrator prompts you to either use the Mashup2009 DSN or to modify or create a DSN that uses the "Oracle for SBM" driver.
  • 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.

Minor Upgrades

This section provides important notes and upgrade instructions for upgrades to 2009 R4.01 from version 2009 R3 and later.

Before you upgrade, review the information above in addition to the following topics:

Pre-upgrade Steps

Follow these steps before beginning the upgrade:

  1. Verify that 2009 R3 or later is installed on your system by opening the "About" box in the Web interface or Mashup Administrator. You can also view the current version of each component in the System Information tab of the SBM Configurator.
  2. Back up your existing database before installing this version.
  3. Back up the installation directory structure SBM on your Application Engine Web server machine.
  4. Download the release from support.serena.com.
  5. Stop the following services on the Application Engine Web server: Internet Information Services – IIS, Serena Common JBoss, and the Notification Server and Mail Client.
    Note: You can stop IIS and the Serena Common JBoss Service on the Manage Services tab of SBM Configurator.

Server Installation

Note that you must replace all client and server components for all environments. To upgrade to this release on all server machines:
  1. Extract the server installation files.
  2. On the server machine for each server component, launch the suite executable. An installer message prompts you to confirm that you are upgrading your system. Click Next to continue.
  3. The Upgrade Summary dialog box appears and summarizes the components that are currently installed on the server and ready for upgrade. The current installation directory that will be upgraded is noted as well. Click Upgrade Now to proceed.
    Note: For minor upgrades, if you want to uninstall existing components or install new components, you must use the Windows Add/Remove Programs utility to completely uninstall SBM and then perform a Custom install using the suite installer again (which performs a clean install). This process does not upgrade the current installation. It is recommended that you back up your existing SBM installation directory before you uninstall and reinstall with different component selections. Once the desired components are installed, continue to the next step and reconfigure your installation using SBM Configurator.
  4. At the end of the installation process, click Configure to launch SBM Configurator. You must complete the SBM Configurator wizard before you can access SBM.
    Note: If you are prompted to restart your server, SBM Configurator launches automatically once the server has restarted. (On Windows 2008 systems, you must launch SBM Configurator manually once the server has restarted). If you decline to restart the server at this time, you will not be able to run SBM Configurator until the server has restarted.
    When you launch SBM Configurator, it detects that you are upgrading your system and it upgrades the file system by merging existing configurations from your previous installation into the new installation files. After SBM Configurator is finished upgrading your file system, you can run it anytime thereafter to verify or modify your configuration settings as needed. Guidance is available by clicking the Help buttons throughout the wizard.
  5. Launch the SBM System Administrator and upgrade the SBM Application Engine database. You must use the SBM System Administrator installed with the suite installation package to upgrade the database. If you use multiple environments, you must perform this step for each database in each environment.
  6. Review the database upgrade log file in the Log folder of installationDirectory\Serena\SBM\Application Engine directory and correct any problems that occurred during the upgrade. If the log file is empty, no errors or warnings occurred during upgrade.
  7. Merge custom modifications to HTML templates, e-mail templates, and Web interface online help files made to your upgraded files. Backup templates are stored in a backup folder in the installationDirectory\Serena\SBM\Application Engine\Backup<version>-<date>-<time> directory.
    Note: Visit the knowledge base at support.serena.com and search for solution S137984 for a list of configuration files, template files, JavaScript files and strings that have changed in this release. You must manually merge some of your existing SSO customizations into the newly installed files after you upgrade your software and database.
  8. If you performed the previous step, open SBM System Administrator, select File, and then select Put Files in Database. ALL templates and images in the database are replaced by files on your local machine.
  9. Verify that these services are started: SBM Application Engine Web server (Internet Information Services - IIS), the Serena Common JBoss, and the Serena Broker Service.
    Note: You can start IIS and the Serena Common JBoss Service on the Manage Services tab of SBM Configurator.
  10. Instruct all SBM Composer users to install the client tools using the instructions in the following section (Client Installation). SBM System Administrator users who will use the Remote Administrator should also upgrade using the client installer.
  11. Instruct SBM User Workspace and SBM Application Administrator users to clear the cache in their Web browsers.

Client Installation

The client executable contains full versions of SBM Composer and SBM System Administrator and is intended to be run on client machines.

Previous versions of SBM Composer and SBM System Administrator do not need to be uninstalled before upgrading. The new versions are installed in the same location as the old versions.

To install SBM Composer and SBM System Administrator:

  1. Download the client installer from support.serena.com.
  2. Launch the installer by double-clicking the file.
  3. Click Next on the Welcome dialog box.
  4. Click Install to upgrade the current client installation.

Fixed Issues

A list of defects fixed in this version can be found in the Knowledge Base.

Note: You must have a Serena.com user account to view items in the Knowledge Base. Register for a free account if you do not have already have one.

Known Issues

This section describes known issues and contains the following categories:

Serena Service Manager Issues

  • The Installing Relationship Explorer topic (pp. 14-15) in the Serena Service Manager Guide should contain the following details of where to find the extensions zip file:

    • If you have downloaded the Business Manager Installer zip file from the Serena Support site, extract the contents of the zip, the extension zip file will be in the Extension folder. Extract the extensions zip file into the SBM Installation directory: installationDirectory\Serena\SBM.

      The compressed file includes a defined path that begins with Application Engine and extends to nested directories named graph.

    • If you install Serena Service Manager from a DVD, the Relationship Explorer is found in manager/Extension directory. Copy these files to your SBM installation directory: installationDirectory\Serena\SBM.

Copyright © 2007–2010 Serena Software, Inc. All rights reserved.