SBM 10.1.3.1 is the version that immediately follows SBM 10.1.3. All of the features, changes, and fixes that were made in SBM 10.1.3 can be found in SBM 10.1.3.1.
SBM 10.1.3.1 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 10.1.3.1 from http://www.serena.com/support and then follow the instructions in the SBM Installation and Configuration Guide.
SBM 10.1.3.1 is available in U.S. English only.
The following terminology and component name changes have been made since the release of SBM 2009 R4.
|Old Term||New Term|
SBM Application Administrator
|SBM Application Repository|
|SBM Application Administrator|
|Auxiliary Data (in SBM Application Administrator)|
Notification Server (in the SBM installer)
|SBM Mail Services|
- For changes made in SBM 2009 R4, refer to the readme.
- For terminology changes made since TeamTrack 6.6.1, refer to the Moving to Serena® Business Manager guide.
The sections below discuss changes in supported software 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).
- Server Operating Systems
- Microsoft Windows 2012 SP1 and SP2 (64-bit)
- Tablet Support
Serena Work Center is only supported in the Chrome Web browser for tablets that run iOS7.
The latest application Web service calls can be found in the sbmappservices72 WSDL. The latest administrative Web service calls can be found in the sbmadminservices72 WSDL. All TeamTrack Web services and earlier SBM Web services (including 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 SBM Web services version 7.2. For new Web service implementations, use SBM Web services version 7.2.
The following component build numbers apply to this version:
- SBM: Build 10.01.03.01.103
- SBM Composer : Build 013
- User Workspace, SBM System Administrator and SBM Application Administrator: Build 85
- Application Repository: Build 24
- SBM Configurator: 10.01.03.01.16
- Database version: 1013010105
- English – 10.1.3.1
- Japanese – 2009 R4.01 (the translated content applies to version 2009 R4.01)
To read the security bulletin for SBM 10.1.3.1, visit http://www.serena.com/support, click "My Downloads", and then open the Windows product page for SBM 10.1.3.1.
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.
Please refer to prior readmes for a list of features and changes that were added in another version before this release.
- TeamTrack 6.6.1.x
- Serena Business Mashups 2009 R1.0x
- Serena Business Mashups 2009 R2.0x
- Serena Business Mashups 2009 R3.0x
- Serena Business Manager 2009 R4.0x
- Serena Business Manager 10.1
- Serena Business Manager 10.1.1.X
- Serena Business Manager 10.1.2
- Serena Business Manager 10.1.2.1
- Serena Business Manager 10.1.2.2
- Serena Business Manager 10.1.3
If this is a new installation, download version 10.1.3.1 from http://www.serena.com/support and then follow the instructions in the SBM Installation and Configuration Guide to install Serena Business Manager.
There are two methods for migrating from Tracker to SBM. For more information on migrating your Tracker data to SBM, refer to the "Migrating Tracker Data to SBM" solution (S138468).
If you have TeamTrack 6.6.1.x installed, download version 10.1.3.1 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.
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, SBM 10.1.3.1 must be installed on each server and client machine.
- Major upgrades are upgrades from any version prior to 2009 R3. If you are upgrading from a version prior to 2009 R3, review the Important Notes for Major and Minor Upgrades below and then follow the steps in solution S138037 to upgrade to 10.1.3.1.
- Minor upgrades are upgrades from version 2009 R3 and later. If you are upgrading from version 2009 R3 or later, review the Important Notes for Major and Minor Upgrades below and then follow the steps in Minor Upgrades to upgrade to 10.1.3.1.
- If you are using NT Challenge Response prior to the upgrade, you must ensure that the new workcenter virtual directory in IIS uses the same authentication settings that are currently set on the tmtrack virtual directory. (The virtual directory authentication settings must match.) This means that you must change the workcenter virtual directory to use Integrated Windows Authentication and disable Anonymous Access (and select Basic authentication as well if you have selected it on the tmtrack virtual directory). You can perform this change any time after the installer is finished.
- 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.
- Smart Search is now enabled by default as part of the upgrade for
Smart Search provides sophisticated search capabilities by automatically
indexing the content of items and notes that have been added to items. The
default Smart Search polling interval is 3 minutes; this means that by default,
searches will return related items three minutes after the items have been
Smart Search operates on pre-built indices. For SBM upgrades, the index building begins once JBoss is started for the first time after you upgrade your installation. The complete indexing operation can take ample time to finish for very large databases; however, some search results in Work Center begin to appear immediately and the number of results continues to grow while the initial indexing operation works toward completion.
You can view the overall progress of the indexing operation in the ssf.log file located on the server that hosts SBM Common Services. The log file is located here:
- As of
the upgrade process drops the current Common Log database tables and then
recreates them. This means your existing Common Log data is deleted as part of
the upgrade. Common Log data is typically only used to troubleshoot issues with
Important: If you need to preserve the data in your Common Log database tables, ensure that you back up the Common Log database before you upgrade.
- As 10.1.2, the
Login Application (Federation Server) has been merged with the
Security Token Service (STS) into a single
Security Server (also known as the Identity Provider (IDP)). This means that
TokenService.war directories have been merged
and replaced with a new
idp.war directory on the
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/loginFor the STS, it will be:
- You must have one instance of SSO installed in order to have a functional instance of SBM, regardless if you plan to enable SSO or not. The SBM upgrade does not install missing components; therefore, if SSO is not currently installed, you must run the installer, perform an uninstall, and then reinstall SBM with SSO included. In a distributed installation, choose a server to host SSO, and then perform the uninstall and reinstall on that machine.
- For Oracle systems, the required roles and privileges for the SBM schema user have changed. Please visit S133641 for details.
- You must ensure that all of the SBM components are installed on one or more servers prior to upgrading. This includes SSO and SBM Common Services. You can choose to enable or disable SSO once it is installed; however, you still must install the SSO component for SBM to function properly.
- You must disable the
User Access Control (UAC) setting before you
on Windows 2008 or 2008 R2. To disable this setting, perform the following
- From the Windows Start menu, open the Control Panel and select User Accounts.
- Turn off UAC:
- On Windows 2008, open the User Accounts window, click Turn User Account Control on or off and clear the Use User Account Control (UAC) to help protect your computer check box.
- On Windows 2008 R2, click Change User Account Control settings, and move the slider to the Never notify position.
- Click OK.
- 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 4.0 or higher must be installed on all Windows machines. If it is not detected, the .Net Framework is installed by SBM. To save download and installation time, you may want to install version 4.0 or higher prior to running the SBM installer. Also, if you will not have Internet access during the installation, you should download and install version 4.0 or higher beforehand.
- On Windows 2003 systems, the
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
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
determine if version 4.5 is already installed, open the command line and enter
- If you are connecting to a Microsoft SQL Server 2008 database, you must select the 2008 SQL Server Native Client driver. The SQL Server ODBC driver is not compatible with Microsoft SQL Server 2008.
- If you upgrade to Windows 2008 in addition to upgrading
you must enable the Web Server (IIS) role before you install
SBM Application Engine.
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
SBM Installation and Configuration
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.
- 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
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 SBM Configurator 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
SBM DSN that is installed with
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.
- 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 (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.
- States, transitions, and projects now have unique internal names
that make it possible to unambiguously refer to them in a Web service,
AppScript, or API call. (This enables you to change the display name of the
state or transition and not interfere with any of these references). Note the
- The internal state and transition names are derived from the internal name of their defining workflows. These internal values are set when you open a process app in SBM Composer for the first time after upgrading to SBM 10.1 or later versions.
- You can change the new default internal names for states and transitions at any time before the process app is published for the first time in SBM 10.1 or later versions. Once the process app is published, the internal names cannot be changed.
- The internal names for existing projects are automatically
created upon upgrade to
SBM 10.1 or
later versions. When you create new projects in the
in versions after 10.1,
automatically creates the internal project name for you.
Note: During promotion, if the internal project name clashes with an existing internal project name, the internal name in the target database is affected in one of two ways:
- For new projects that are added during promotion, when a conflict occurs, the project name in the target database will be a blank or empty string.
- For existing projects that are updated during promotion, when a conflict occurs, the project name in the target database remains unchanged. If the internal name in the incoming XML does not conflict with the internal name in the target database, then the promoted project's internal name is used.
- The Java Notification Server does not support the
MAPI standard. For upgrading customers formerly using MAPI with the
Notification Server, you can now connect to your Microsoft Exchange server
Exchange e-mail server type in
Exchange option enables
communicate with your Microsoft Exchange server using the MS Exchange Web
For customers currently using MAPI, perform the following steps to configure the Notification Server to connect using MS Exchange:
- Run the SBM Configurator on each server where the Notification Server is installed.
- In the Mail Services tab, select the Notification Server tab.
- In the E-Mail Server Type drop-down list, select Exchange.
- Enter your current Exchange server version, connection URL, and system user credentials.
You might use the Exchange option if your company does not allow connection through SMTP. The Exchange protocol is also available for use with the Mail Client in the event your company does not allow connection through POP3 or IMAP. If no such restrictions exists, consider choosing SMTP for the Notification Server and POP3 for the Mail Client because they enable faster connection speeds than MS Exchange.
2009 R4, application icons were introduced. You could specify an icon in the
application editor in
and the icon appeared on the application tabs in the
SBM User Workspace.
If you did not specify an icon, a default red icon was automatically used. As
10.1, the red icon is no longer the default; instead no icon is used if you do
not specify one.
- If you are upgrading from a release earlier than SBM 2009 R4, you will see no change; no icon will appear on the application tab.
- If you are upgrading from SBM 2009 R4 or later, and changed the default red icon to something else, you will see no change; your icon will still appear on the application tab.
- If you are upgrading from SBM 2009 R4 or later, and kept the default red icon, you will no longer see the icon; the application tab will be blank. If you want to restore the red icon, you can select it from the list that opens when you select "New image..." from the drop-down list in the application editor in SBM Composer. Redeploy your process app after making this change.
- Security Tokens are now generated for authenticated users
regardless of the log in method you choose in
Note the following behavior for upgrades from releases prior to 10.1:
- If SSO was enabled in a prior release, after the upgrade to 10.1.3.1, deployed apps will use Security Tokens automatically without having to be redeployed.
- If SSO was disabled in a prior release, after the upgrade to 10.1.3.1, deployed apps will not use Security Token authentication unless they are redeployed (even if SSO is enabled after the upgrade).
- The following information only applies to
SBM systems in
which external events were used with orchestration workflows and
was not used:
- With the use of security tokens for all communication with SBM components regardless of authentication method, it is now necessary to provide credentials in the User element of external events that are processed by the Event Manager. Credentials must be supplied in order to receive a security token.
releases allowed anonymous events if
was disabled. As of
10.1, security tokens are used in all underlying communication. As part of the
upgrade process, in order to still accept external events without credentials,
the Event Manager is automatically configured to continue to accept external
events without authentication credentials. If
was enabled prior to upgrade, then it is assumed that external events always
included credentials and will continue to do so in your environment.
Important: If you are currently using external events without SSO, it is strongly recommended that you adjust the source of those external events to now include credentials. Once you adjust the external source to include a credential, you can then manually override the Event Manager settings by setting the no_authentication parameter to “false” in the alf.properties file. For configuration instructions, see solution S138463.
- After upgrading, the no_authentication setting is independent of the SSO setting. If you are performing a new installation, you can override the default behavior for the Event Manager and enable it to accept external events without credentials. For configuration instructions, see solution S138463.
- For SBM Application Engine Web services, the SBM Application Engine auth still overrides the security token auth. In some cases, this is useful in day-to-day operations and may be useful if you are upgrading from versions prior to 10.1. For example, orchestration workflows that contain coded auth for the SBM Application Engine service calls will continue to work if the external event is changed to send a credential; the coded auth will override the security token and continue work as it did prior to upgrade.
- 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
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 System Administrator,
otherwise the domain that the IIS server machine is installed on is used for
As part of the upgrade, SBM Configurator should perform the following steps for you automatically to accommodate this new requirement. However, for systems that use NT Challenge Response authentication that have an authentication override set in SBM System Administrator, you must perform the following steps manually:
- In IIS, copy or take note of the current domain that you have set for Basic Authentication on the GSOAP directory.
- Clear Basic Authentication from the GSOAP directory and only specify Anonymous Access or Anonymous Authentication. (In previous versions of SBM, you had to specify Basic Authentication on the IIS GSOAP directory and provide the domain there).
- From the Options menu in the SBM System Administrator, select Settings or click the Settings icon on the toolbar. The Settings – Server tab opens.
- Paste or enter the correct Windows domain in the Default domain for web services field.
- 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.3.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.
- If you installed 10.1, which had the Transition Group Restrictions and User Field Selections check boxes selected by default in promotion profiles, and then upgrade to 10.1.2, the check boxes could become unchecked.
- Prior to 10.1.2, renaming an orchestration in
and then redeploying the process app would leave the originally deployed
orchestration event map in place while also deploying a new event map with the
new name. The original event map was still associated with its events, so
events associated with the orchestration would cause both the original event
map to run the orchestration workflows and the new event map to run the
orchestration workflows. This problem could reoccur on each new deployment.
Generally, the behavior was that an orchestration workflow would appear to run
twice or more simultaneously, where it was only expected to run once (although
other unexpected behavior was also possible).
This problem is fixed as of 10.1.2 for deployments of new process apps, and an upgrade is provided that as far as is possible, fixes existing deployments by removing any duplicates. For systems installed prior to SBM 10.1, certain cases of existing deployments cannot be automatically upgraded and will still be prone to this renaming issue. Mostly, these cases can be addressed by redeploying the currently deployed process apps.Note: If you suspect duplicated event dispatches after upgrade, contact Serena Customer Support for assistance.
- 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.
This section provides important notes and upgrade instructions for upgrades to SBM 10.1.3.1 from version 2009 R3 and later.
Before you upgrade, review the information above in addition to the following topics:
Follow these steps before beginning the upgrade:
- Verify that SBM 2009 R3 or later is installed on your system by opening the "About" box in the Web interface. You can also view the current version of each component in the System Information tab of the SBM Configurator.
- Back up your existing database before installing this version.
- Back up the SBM installation directory structure on your Application Engine Web server machine.
- Download the release from support.serena.com.
- Close SBM Configurator on all servers if it is open.
- Extract the server installation files.
- 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.
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 of SBM 10.1, the Notification Server and Mail Client are powered by Serena Common JBoss and installed independently from the SBM Application Engine component. For upgrades from versions prior to 10.1, the option to install the new SBM Mail Services (which contains the Notification Server and Mail Client) is selected by default (except on servers that host only the SBM Application Engine and no other components; in that scenario, you must manually select the SBM Mail Services check box to install the Notification Server and Mail Client because the installation of these components now includes the Serena Common JBoss service, which consumes additional resources on the server).
Before you install the SBM Mail Services, review the following installation considerations:
- For your production environment, if you have a high volume of Notification Server and Mail Client activity, you can now add additional instances of the SBM Mail Services. Installing multiple instances not only provides failover in case one of the servers shuts down; it also improves the overall performance of notification handling because the processing load is distributed across multiple servers.
- For installations with over 1000 users or heavy orchestration usage, consider installing the SBM Mail Services on a dedicated server without any other SBM components. If you install the SBM Mail Services separately, you must enter the SBM Application Engine host name and port in SBM Configurator after the installation. This enables the Notification Server and Mail Client to communicate with SBM Application Engine.
- For multi-environment installations that include separate SBM Application Engine installations for test, staging, and production environments, install the SBM Mail Services at least once in each environment.
After you have reviewed the components that are currently installed and decided whether or not to install the SBM Mail Services, click Upgrade Now to proceed.Note: For minor upgrades, if you want to uninstall existing components or install new components other than the SBM Mail Services, 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.
- At the end of the installation process, click
Configure to launch
SBM Configurator detects the current upgrade process, and upgrades the file system by merging existing configurations from your previous installation into the new installation files. You must click Apply to save these changes. Once the file system is upgraded, you can run SBM Configurator again anytime thereafter to verify or modify your configuration settings as needed.Note: If you are prompted to restart your server after the installer is finished, 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.To complete the upgrade process, you must use SBM Configurator to upgrade the Application Engine database. Note the following important information:
- Click Upgrade Database on the Database Servers tab (before or after you click Apply) to begin the database upgrade. In the event that you want to verify your configuration and save the installation upgrade changes that have occurred before you upgrade the database, you can click Apply and perform the database upgrade later at an appropriate time; however, you must complete the Application Engine database upgrade before users can access SBM.
- Plan ample time for the database upgrade to complete. When the upgrade finishes successfully, a message appears that directs you to the upgrade log.
- For distributed installations, you perform the database upgrade in SBM Configurator on the server that hosts SBM Application Engine.
- For multi-environment installations, you must upgrade each Application Engine database in each environment.
- Review the database upgrade log file in the Log folder of the 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.
- 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
If you previously used a custom HTML template for your reports, the reports might not display properly after upgrade. Therefore, consider using the default template or modifying it as needed. For example, as of SBM 10.1.2, several changes were made to Summary Reports that might not display properly using a custom template from a prior release. Instead, either use the new default template or merge your customizations into the default template to create a new custom template.Important: If you installed the TT4ZMF integration prior to upgrading, you must follow the instructions in the TT4ZMF readme to reinstall the integration after the SBM upgrade is complete.
- 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.
- If you are using Windows Domain (NTCR) authentication for SBM, edit the workcenter virtual directory authentication settings in IIS, select Integrated Windows Authentication, disable Anonymous Access, and select Basic authentication if you have selected it on the tmtrack virtual directory. The workcenter virtual directory settings must match the tmtrack virtual directory settings.
- In SBM Configurator, verify that these services are started in the Manage Services tab: SBM Application Engine Web server (Internet Information Services - IIS), Serena Common JBoss, Notification Server, and Mail Client.
- Instruct all SBM Composer users to install the client tools using the instructions in the following section (Client Installation).
- Instruct SBM User Workspace and SBM Application Repository users to clear the cache in their Web browsers.
The client executable contains SBM Composer and is intended to be run only on client machines.
Previous versions of SBM System Administrator are automatically uninstalled as part of the upgrade (administrative duties are now performed using SBM Application Administrator). Previous versions of SBM Composer are upgraded automatically and do not need to be uninstalled prior to upgrading. The new versions are installed in the same location as the old versions.
To upgrade SBM Composer:
- Download the client installer from support.serena.com.
- Launch the installer by double-clicking the file.
- Click Next on the Welcome dialog box.
- Click Install to upgrade the current client installation.
A list of defects fixed in this version can be found in the Knowledge Base. 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.
Beginning in SBM 10.1, user accounts are managed in SBM Application Administrator rather than in SBM System Administrator. SBM Application Administrator, which requires a connection to the SBM Web server, is not available if the number of users in your system exceeds the number of installed seat licenses.
If you receive a seat license error in a version earlier than SBM 10.1.1.4, contact Customer Support for assistance is resolving the issue. If you have SBM 10.1.1.4 or later installed, the Users tab in the SBM System Administrator is enabled automatically if you encounter this problem. Open SBM System Administrator and delete or modify user accounts so that they are in compliance with their seat licenses. (If you encounter this problem and the SBM System Administrator is already open, you need to close it and reopen it for the Users tab to appear.) Once you resolve user accounts, the Users tab is not visible the next time you open the SBM System Administrator.
For a complete list of known issues and potential workarounds, refer to the Knowledge Base. You must have a Serena.com user account to view items in the Knowledge Base. Register for a free account if you do not already have one.
Note: The following issue is only applicable if you had previously upgraded to 10.1 or 10.1.1.1. If you did not use either version prior to upgrading, 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. Starting with 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.
- After you install SBM on Windows 2012 SP1 or SP2 (64-bit), SBM Configurator does not launch automatically when you click Configure at the end of the install process. To work around this problem, launch SBM Configurator manually from the install location.