SBM 11.0.1 is the version that immediately follows SBM 11.0. All of the features, changes, and fixes that were made in SBM 11.0 can be found in SBM 11.0.1.
SBM 11.0.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 11.0.1 from http://www.serena.com/support and then follow the instructions in the SBM Installation and Configuration Guide.
Note the following important information about this release:
- SBM 11.0.1 requires Serena License Manager 2.2. You must upgrade to version 2.2 before you can upgrade to SBM 11.0.1.
- Solution releases prior to and including Serena Service Manager / Serena Request Center 5.2 and Serena Release Control 6.0 will not run properly on SBM 11.0.1 and these versions are not supported. You will need to upgrade each solution to newer, compatible versions before you can use them.
- SBM is now certified against Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6). Note that SBM requires that both IPv4 and IPv6 stacks are present on each server, though IPv4 can be disabled.
- SBM 11.0.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.
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).
The following component build numbers apply to this version:
- SBM User Workspace and Serena Work Center: Build 11.00.01.00.790 (Build 552)
- SBM Composer : 11.0.1 (Build 0232)
- SBM System Administrator and SBM Application Administrator: 11.00.01.00.790 (Build 552)
- Application Repository: Build 11.00.01.00.790 (Build 520)
- SBM Configurator: 11.00.01.00.358
- Database version: 1101000006
- English – 11.0.1
- Japanese – 2009 R4.01 (the translated content applies to version 2009 R4.01)
For more information regarding third-party software copyrights and license information, refer to the files under "Downloads" or "News" at http://www.serena.com/support.
The following features have been added in this release.
- New Date Format Options
- Trend Report Improvements
- Extended Out of Office Capabilities
- Support for Single Sign-On with SAML2
Users who select Use Date/Time Format from Locale as their date format can now select short, medium, or long format options. This enables users to view date values with month names instead of digits, if desired. For example, if a user selects English (United States) as the Locale and Use Date/Time Format from Locale as their Date Format, the following display options are available:
- Long – January 18, 2016 10:01:49 AM
- Medium – Jan 18, 2016 10:01:49 AM
- Short – 1/18/16 10:01:49 AM
All date/time field values in the system will appear according to the user's locale and the selected format type.
- Users can now select Query At Runtime for the Start Date and End Date when creating trend reports. This means you can potentially bind Date/Time fields on a form to the query-at-runtime start and end dates on an embedded trend report. Use of query-at-runtime parameters is currently limited to the standard trend report in SBM 11.0.1.
- Users can now use Date/Time Keywords for the Start Date and End Date when creating trend reports. This enables users to define a start and end date for a trend report without having to specify fixed dates, which requires less oversight and maintenance.
- You can now create a "global" out-of-office delegation for a user. To temporarily delegate all of a user's items to another user, create the delegation in Application Administrator, select the Base Project, and then select the option to delegate items in all sub-projects. Only users who have privileges to own items in the selected project are available as delegates.
- Fields that are used to define secondary ownership are now available for delegation. For example, the IT Technicians field may be set as the secondary owner for the "Assigned" state. SBM can now update this field based on the out-of-office delegation that you create.
You can now achieve cross-product single sign-on between an external identity provider and SBM using the SAML 2.0 protocol. SAML 2.0 is used by organizations to transmit and process user authentication and authorization credentials between security domains. This enables SBM to operate as a service provider that can be accessed by users who are already authenticated and authorized by an external SAML 2.0 infrastructure. You configure the trust relationship between SBM and an external identity provider in the Authentication tab in SBM Configurator. For details, refer to the SBM Configurator help.
The following sections describe additional features that have been changed or added to this release.
Securing Anonymous Events
You can now use SBM Configurator to specify SBM credentials in SBM Configurator that the Event Manager will use for anonymous events if your system must accept events that do not have accompanying authentication credentials. If your system was previously configured to accept anonymous events via the no_auth parameter in the alf.properties file, you must either add credentials to your events (preferred) or you must select the Allow Anonymous Events check box in SBM Configurator and enter an SBM user name and password after the upgrade to 11.0.1.
Extended GetFieldValue() Usage
Many SBM features require Web browsers that support HTML5. Some of these features are not available in older browsers, such as Internet Explorer (IE) 8.
- Serena Work Center
- Rich Text Editor for applying formatting to e-mail messages, notes, and certain Text fields.
- Updated form styling and modern themes
- Drill-down display options for Distribution, Advanced Distribution, Summary, Time to State, Elapsed Time, Trend, Backlog Trend, Entering a State, Open and Completed, and State Activity reports (if Flash components are also disabled)
- User profile card
- Group member lists for Multi-User fields on State forms
- Translated strings in the workflow diagram
- Second background colors and corner radius settings on custom forms
- Standard logout behavior when a user closes the browser or tab that hosts SBM, or when a user navigates away from SBM to another page. This means the behavior is the same whether a user formally logs out or if he or she ends the session by closing the browser or navigating to a different page. Note that the sixty-minute idle timeout remains in place if the session is left open and the user does not log out through one of these means.
- Upgrade your browser, or
- Contact your administrator and ask for HTML5 features to be disabled.
In addition, Compatibility Mode should be disabled in all versions of Internet Explorer.
This section provides upgrade information and important notes for all upgrades to SBM 11.0.1. To test the upgrade, mimic your current installation on a separate set of servers. This test installation should include all of the environments used by your system. Serena recommends that you upgrade and test this installation before upgrading your production installation. To upgrade successfully, you must upgrade each server and client machine to SBM 11.0.1.
- Supported Upgrade Paths
- Requirements and Changes
- Planning for the Upgrade
- Pre-Upgrade Steps
- Upgrading the Installation
- Upgrading the Databases
- Post-Upgrade Tasks
- Upgrading Customizations and Integrations
- Upgrading from 2009 R4 or later
If you are upgrading from 2009 R4 or any version thereafter, refer to the important notes and instructions below to upgrade to SBM 11.0.1.
- Upgrading from versions prior to 2009 R4
If you are upgrading from a version of SBM prior to 2009 R4, follow the upgrade instructions in solution S138037 to upgrade to 10.1.5.X first, and then upgrade your 10.1.5.X installation to SBM 11.0.1 using the instructions below.
- Upgrading from TeamTrack 6.6.1.X
If you are upgrading from TeamTrack 6.6.1.X, follow the instructions in the Moving to Serena Business Manager guide (available at http://www.serena.com/support) to upgrade to SBM 10.1.5.X first. In addition refer to solution S137372 to learn about the upgrade preparation utility. After you have upgraded TeamTrack to SBM 10.1.5.X, follow the instructions below to upgrade to SBM 11.0.1.
- Upgrading from Tracker
For information on migrating your Tracker data to SBM, refer to the "Migrating Tracker Data to SBM" solution (S138468).
Before you upgrade to SBM 11.0.1, read the following important information:
- SBM 11.0.1 requires Serena License Manager 2.2. You must upgrade to version 2.2 before you can upgrade to SBM 11.0.1. .
- SBM 11.0.1 requires 64-bit Windows servers. If you are using 32-bit servers prior to the upgrade, you must install SBM 11.0.1 on one or more 64-bit machines, and then upgrade the databases using the 64-bit installation. 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.
- 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.
- Work Center
search operates on pre-built indices that may change for each
search index is rebuilt when Tomcat is started for the first time after the
upgrade. The complete indexing operation can take ample time to finish for very
large databases; however, some search results in
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 part of the database upgrade and migration to
the new ODE BPEL engine, data in the CL_CONTEXT_VALUE and CL_LOG tables is
deleted. New indexes are added to the CL_CONTEXT_VALUE and CL_LOG tables on
upgrade to prevent time outs from occurring when you try to view Common Log
In order to add the new indexes, these tables will be emptied during the
Important: If you need to view Common Log data that was present prior to the upgrade, ensure that you have backed up these tables.
- For Oracle systems, note the following:
- You must ensure that the required roles and privileges for the SBM schema user are up-to-date. Refer to solution S133641 for details.
- You must perform the database upgrade using either the
SBM DSN or a system DSN that uses the "Oracle for SBM" driver. If your system used the Mashup2009
DSN prior to the upgrade, that DSN is automatically converted to use the new
"Oracle for SBM" driver.
Important: The underlying driver in the DSN that ships with SBM was changed in SBM in 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.
The upgrade process you will follow depends on the type of installation you currently have:
- Single Server Installation — All of the SBM components are
installed on a single server.
For single server installations, you will run the suite installer on your server and then upgrade the databases using SBM Configurator. The databases are upgraded in two phases—in phase one, the Application Engine database is upgraded; once it completes successfully, phase two begins. In phase two, you are prompted to enter the SBM user name and password of your primary system administrator or an SBM user that has the Remote Administration privilege to upgrade the Orchestration Engine database.
- Distributed Installation — The SBM components are installed
on multiple servers that comprise a single production environment.
For distributed installations, you will run the suite installer on each server, and then use SBM Configurator to upgrade the databases. When you begin the Orchestration Engine database upgrade on the server that hosts SBM Orchestration Engine, you are prompted to enter the SBM user name and password of your primary system administrator or an SBM user that has the Remote Administration privilege. This scenario requires that you start the SBM services and that you perform the database upgrades in a certain order. This is explained in more detail below in Upgrading the Databases.
- Multi-environment installation — The SBM components are
installed on single or multiple servers that are separated into multiple SBM
environments (such as development, test, and production).
The process for upgrading multiple environments (used in a path to production model) depends on which environment hosts SBM Application Repository and which environment you plan to upgrade first (Test/Staging first or Production first).
is part of the Test environment and you plan to upgrade Test first
In this setup, each environment uses a single instance of Application Repository that is installed in the Test environment. You will upgrade the Application Engine and Orchestration Engine databases in the Test environment first. After the upgrade in Test is finished, you will not be able to deploy to Production from Application Repository until you upgrade the Production servers and databases.
is part of the Production environment and you plan to upgrade Test first
In this setup, each environment uses a single instance of Application Repository that is installed in the Production environment. You will upgrade the Application Engine and Orchestration Engine databases in the Test environment first. After the upgrade in Test is finished, you will not be able to deploy to Test from Application Repository until you upgrade the Production servers and databases.Important: If you are upgrading from 2009R4X, in order to upgrade the Test environment first, you must install and configure a temporary 11.0.1 instance of SBM Application Repository that is connected to a backup copy of the production Application Repository database. Once the upgrade in the Test environment is finished, you can uninstall the temporary 11.0.1 SBM Application Repository instance and delete the backup copy of the database that was used for the upgrade.
is part of either Production OR Test and you plan to upgrade all environments
at the same time
If you plan to upgrade all environments at the same time (one immediately after the other), upgrade the instance that hosts Application Repository first (likely Production). This will allow you to upgrade the other environments that do not have SBM Application Repository without installing a temporary instance.
For information about warnings that may appear during a multi-environment upgrade, see Handling Warnings with Multiple Environments.
- If SBM Application Repository is part of the Test environment and you plan to upgrade Test first
If you are upgrading from the following versions, plan for hosting new server components as follows:
- If you are upgrading from 09R4, you will use SBM Configurator to designate which server or servers will host the SBM Mail Services component. By default, SBM Mail Services appears on an undefined server until you drag and drop it to the desired server or servers.
- If you are upgrading from a release prior to 10.1.2, use SBM Configurator to designate which server will host the SBM Logging Services component. By default, SBM Logging Services appears on an undefined server until you drag and drop it to the desired server. If you are upgrading from a release after 10.1.2, SBM Logging Services is enabled on the same machine as SBM Common Services by default. You can use SBM Configurator to move it to a dedicated server, if necessary (for example, if you set the logging level to TRACE for debugging purposes).
Follow these steps before you perform the upgrade.
- Verify that SBM 2009 R4 or later is installed on the System Information tab in SBM Configurator.
- Back up your existing databases.
- Back up the SBM installation directory structure on the Application Engine server.
- Back up the Smart Search index directory on the SBM Common Services server. If you need to revert the upgrade for any reason, you will restore the index from this backup (because the index is rebuilt as part of the upgrade).
- Consider consulting with your DBA to assess the current table indexes in the SBM databases. Because significant database schema changes do not necessarily coincide with each database upgrade, table indexes are not automatically rebuilt as part of the upgrade process. Over time, indexes can report excessive fragmentation, which could negatively impact performance if they are not rebuilt periodically.
- If you store SBM item attachments on the file system, open SBM System Administrator and note the location of the attachments directory. You will enter the location in SBM Configurator later as part of the upgrade.
- Create a new database space in your DBMS to host the Configuration Settings database if you did not create it in a prior release. As of SBM 10.1.5, you can use this database to store configuration settings across your entire SBM installation in one centralized location.
- Download the new suite and client installers from support.serena.com.
- Extract the server installation files, and then launch the suite installer. An installer message prompts you to confirm that you are upgrading your system. Click Next to continue.
Ready to Upgrade dialog box appears. Click
Upgrade Now to being upgrading the server installation. At the
end of the installation upgrade, click
Configure to launch
Note: If you are prompted to restart your server, SBM Configurator launches automatically once the server has restarted. (On Windows 2008 systems, you must manually launch SBM Configurator after the restart). If you decline, you will not be able to run SBM Configurator until the server has been restarted.
- Decide if you will use the
Configuration Settings database if you have not done so
already. If you have a distributed installation, it is highly recommended that
you use the
Configuration Settings database, because it enables you to
easily synchronize configuration settings between each
server without requiring you to export and import configuration snapshot files.
On the Database Servers tab, enter database connection information for the Configuration Settings database that you created as part of the pre-upgrade process.
- If you store SBM item attachments on the file system, enter the location of the attachments directory on the Common Services tab. This enables SBM Common Services to return attachments in Work Center search results. If you store attachments in the database, skip this step.
- Verify your configuration settings, and then click
detects the current upgrade process and upgrades the file system by merging
existing configurations from your previous installation into the new
Important: You must click Apply to save these changes before you upgrade the Application Engine and Orchestration Engine databases. Once the file system is upgraded, you can run SBM Configurator again anytime thereafter to verify or modify your configuration settings as needed.
- On each client machine, run the client installer. The client executable contains SBM Composer and is intended to be run only on client machines. Previous versions of SBM Composer are upgraded automatically and do not need to be uninstalled prior to upgrading. The new version is installed in the same location.
The database upgrade process has changed as of SBM 11.0. Review the following important information before you begin.
- The Orchestration Engine database upgrade is no longer automatically performed after you start the SBM services; instead, you must manually invoke the upgrade process by clicking the Upgrade Database link in SBM Configurator. This ensures that the Orchestration Engine database is not upgraded prematurely.
- If SBM Application Engine and SBM Orchestration Engine are installed on the same server, the Orchestration Engine database upgrade is performed immediately after the Application Engine database upgrade.
SBM Application Engine
SBM Orchestration Engine
are installed on separate servers:
- You must ensure that IIS is started on the SBM Application Engine server and SBM Tomcat is started on each of the other SBM servers. Both IIS and SBM Tomcat must be running and all components must be accessible from the SBM Orchestration Engine server before the Orchestration Engine database upgrade begins.
- You must upgrade the Application Engine database on the SBM Application Engine server first, and then upgrade the Orchestration Engine database on the SBM Orchestration Engine server.
- The Orchestration Engine database upgrade is performed by the renew utility using the user account that you specify when prompted. For details on this process and more information related to the Orchestration Engine database upgrade, refer to About the Orchestration Engine Database Upgrade.
When you are ready, open the Database Servers tab in SBM Configurator, and then click Upgrade Database.
If an ORA-00904 message appears in the Application Engine upgrade log after you finish upgrading the Application Engine database, refer to solution S141358 for a description of the problem and a resolution.
After the databases are upgraded successfully, verify that the services are started in the Manage Services tab. Instruct Application Repository users to clear the cache in their Web browsers before they attempt to access SBM Application Repository.
Review the following information and make any necessary changes after you have upgraded your servers and databases:
- 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 encrypted SSO passwords prior to the upgrade, you must re-encrypt the passwords using the Security tab in SBM Configurator after the upgrade is finished on the SSO server. This ensures that the SSO passwords in the gatekeeper-core-config.xml file remain encrypted.
- For systems that are configured to use client certificate authentication, you must perform additional configuration steps after the upgrade or disable the feature entirely. For details, refer to the entry about client certificate authentication in Installation and Configuration Issues.
- HTML rendering and Rich Text editing is enabled by default for all notes in your system after the upgrade. 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 upgrade from any version prior to 11.X,
reviews the existing JBoss configuration and allocates the same amount of
memory to Tomcat that was previously allocated to JBoss. After the upgrade, if
you need to adjust the amount of memory that is allocated to Tomcat, perform
the following steps:
- Stop the SBM Tomcat service.
- Navigate to installDirectory\Serena\SBM\Common\Tomcat 7.0\bin, and edit the common_config.bat file.
- Change the JVM_X_MAXMEMSIZE value as necessary.
- In the same \bin directory, execute the update_tomcat_config.bat file.
- Start the SBM Tomcat service.
- After the database upgrades are finished, use the Reset Administrative User Access wizard in SBM System Administrator if your database does not contain at least one Regular User or Managed Administrator account with Remote Administration privilege. 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.
- 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.
- 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 after the upgrade.
Review the following information for help with upgrading custom changes and integrations.
If you made custom modifications to any HTML templates, e-mail templates, or online help files, you must merge your changes into the newly-upgraded files, and then use SBM System Administrator to Put Files in Database. All templates and images in the database are replaced by files on your local machine as part of this operation. Backup templates are stored on the installationDirectory\Serena\SBM\Application Engine server here:
If you used custom HTML templates in your reports, the reports might not display properly after upgrade. Consider using the default template or modifying it as needed instead. 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 changes into the default template to create a new custom template.
- 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.
Login Application (Federation Server) was 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 were been merged
and replaced with a new
idp directory on the
If you are upgrading from a release prior to 10.1.2 and you have created custom SSO integrations, you must review all URLs and calls to ensure that they use the latest directory names. For example, if your existing integrations call the Security Token Service (STS), you must ensure that the new idp directory is used.
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.
- If you configured your system to use anonymous events prior to the upgrade, you must either add credentials to your events (preferred) or you must select the Allow Anonymous Events check box in SBM Configurator and enter an SBM user name and password to use anonymous events after the upgrade.
As of SBM 11.0, the Orchestration Engine database upgrade process has changed. This section describes changes in the process, how it affects the schema, and how to resolve failures and validation errors that might appear during the upgrade.
The Orchestration Engine database upgrade is now performed by the renew utility that is installed with SBM. (For detailed information about the renew utility, refer to the SBM Orchestration Guide.) The renew utility is responsible for restoring existing data in the JBPM tables into the new BPEL tables that are used by the Apache ODE BEPL engine. Existing data in the event manager tables is preserved to ensure that orchestrations continue to run as they did prior to the upgrade.
The JBPM and JMS tables in the database are not dropped as part of the upgrade, but they are no longer used and do not conflict the new BPEL tables that are added. If you want to remove the old JBPM tables after the orchestration database has been successfully upgraded, on the server that hosts SBM Orchestration Engine, run the clear_jbpm.bat file located here:
Retrying Orchestration Engine Upgrades and Clearing Warnings
When the renew utility is launched, all process apps that contain orchestrations are redeployed. If any failures are encountered, a message appears and presents the following options:
- View Warnings
This opens the fail_out.xml file located here:
installDirectory\Serena\SBM\Misc\renew\fail_out.xmlThis file contains a list of process apps that failed to upgrade successfully and target environments that are invalid.
- View Log
This opens the upgrade.log file located here:
installDirectory\Serena\SBM\Common\Tomcat 7.0\server\default\logsThis file contains details about the upgrade, including detailed error messages for any failures that were encountered.
Use the list in fail_out.xml in combination with the detail from the upgrade.log to investigate any failures. Depending on the failures, you have the following options:
- You can address the failures, and then click Upgrade Database again. In the prompt that appears, click Retry Upgrade. This launches the renew utility again and attempts to deploy your process apps now that the failures should be fixed.
- If the failures are expected and you do not want to change anything, click Upgrade Database again in SBM Configurator, and then click Clear Warnings in the prompt that appears. This prevents the warnings from appearing again and completes the database upgrade.
For example, if the schema version in a process app needs to be upgraded, NOT_SUPPORTED_VERSION appears as the cause in the fail_out.xml file. This means the process app schema version needs to be upgraded by redeploying from SBM Composer. You can either redeploy from SBM Composer and run the database upgrade again, or if you do not want to redeploy at this time, but you want to finish the database upgrade now, click Upgrade Database again, and then click Clear Warnings.
The database upgrade will report failures if the target server information in your environments is missing or cannot be verified. For example, if you are testing the production database upgrade by moving the database to a different environment, the upgrade process will report failures related to your environment definition in Application Repository. You can either update the endpoint and target server information and click Retry Upgrade or click Clear Warnings to proceed without making the changes to finish the upgrade.
This option redeploys the process apps that are listed in fail_out.xml.
This option recreates the fail_out.xml if it is deleted or missing.
For more examples on these options, refer to the renew command "-redeploy" in the SBM Orchestration Guide.
In multi-environment installations, the renew utility attempts to redeploy process apps that contain orchestrations to every SBM environment in Application Repository. If you have three environments defined, when you upgrade the first environment (Test, in this example), messages appear in the upgrade.log about skipping the other environments that have not been upgraded:
Redeployment will be skipped for ‘Staging Environment’ environment since it is not upgraded. AE version 10.01.05.02.115 Redeployment will be skipped for ‘Production Environment’ environment since it is not upgraded. AE version 10.01.05.02.115
You can safely ignore these messages because you will upgrade these environments in turn.
When you prepare to upgrade each subsequent environment, consider stopping the SBM Tomcat service first in your upgraded environments to prevent redundant redeploy operations from occurring. Stopping SBM Tomcat in each upgraded environment also speeds up the overall upgrade process. However, note that failures will be recorded in the fail_out.xml for these environments because the upgrade will still attempt to redeploy to them. If the only failures that appear are related to the environments that have already been upgraded, use the Clear Warnings button to discard these warnings and finish the upgrade. In this scenario, this enables SBM Configurator to consider the Test database upgrade as “complete” because the warnings do not apply to the current environment and the Test database was successfully upgraded.
Resolving WSDL Validation Errors
Validation errors appear during the SBM Orchestration Engine database upgrade if the process apps that are redeployed by the renew utility contain WSDLs that fail WS-I validation. The same validation failures appear when you attempt to deploy process apps with invalid WSDLs in 11.0.X. This is due to the change from the JBPM to Apache ODE engine in 11.0, which follows new rules to ensure that SBM does not allow execution of invalid WSDLs.
If a WSDL validation failure is encountered, you can view the WSDL in either SOAP UI or Eclipse to find the invalid portion and fix it accordingly. After you have modified the WSDL and ensured that it passes WS-I validation in either tool, modify the process app .msd file, replace the invalid WSDL file with the fixed version, and then redeploy the process app.
For more information and troubleshooting tips on resolving WSDL validation errors, refer to solution S141405.
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.
This section describes known issues and contains the following categories:
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 have already have one.
- The SBM Tomcat components in 11.0.1 run on Java 8. Due to known issues in this version, if client certificate authentication is enabled between components in SBM, all communication from Tomcat to IIS fails. Also, if SSO is used, users cannot log in to SBM when client certificate authentication is enabled. This means that you if have client certificate authentication enabled prior to the upgrade, you must disable it after the upgrade is finished. Alternatively, you can leave client certificate authentication enabled, and perform the steps described in D22099 to work around this problem.
SBM Application Repository Issues
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 this 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.