Pre-Installation Checklist

You must successfully install, configure, and verify SBM 11.1 or higher on one or more servers according to the steps in the SBM Installation and Configuration Guide. This means you will have a fully functional SBM system and database created before you install Serena Service Manager.

Ensure that you have at least one administrative user who has sufficient privileges to import and promote the solution files in SBM Application Repository. For details on these privileges, see the SBM Application Repository Guide.

If your SBM installation is distributed among multiple servers, determine which servers host the following SBM components:

SBM Application Engine
SBM Application Repository
SBM Common Services

You will run the Service Manager installer on the server or servers that host these SBM components.

As of Serena Service Manager 5.0, you must ensure that your server has at least 4GB of RAM. If you are using a distributed installation, you must ensure that each Service Manager server has 4 GB of RAM.

CAUTION:

4GB of RAM is required to run Service Manager. You may encounter problems running the SBM Tomcat service with less RAM.

If you are using multiple environments in SBM (such as development, test, and production), you must ensure that each environment has its own instance of SBM Common Services (not a shared instance). SBM Application Repository is the only component that can be shared by multiple environments.

Procure and install licenses for the solutions that you intend to use. Note that the SLA feature is enabled with any of these solution licenses.

For Oracle systems, the Oracle schema user requires a certain set of roles and privileges to enable "Oracle Text" for use with the Social Widget control that is enabled by default in the Service Manager process apps. See solution S133641 for details.

Important: You must apply these roles and privileges to the Oracle schema user prior to promoting or deploying the apps.

For SQL Server systems, you must ensure that "Full-Text Indexing" is enabled in the DBMS. Note the following:

In SQL Server 2005, "Full-Text Indexing" is enabled automatically once you successfully deploy any process app in which the Social Widget is enabled, as long as the "Full-Text Search" feature was selected during the SQL Server DBMS installation.
In SQL Server 2008 and later, "Full-Text Indexing" is selected by default for all databases, as long as the "Full-Text Search" feature was selected during the SQL Server DBMS installation.

Note: The Full-Text Search feature in SQL Server is an optional installation component. Therefore, first verify that the feature is installed in SQL Server. To verify this, right-click the database in SQL Server, select Properties, and then select the Files page. “Use full-text indexing” should be selected.

If you are upgrading from a previous version of Service Manager, before you upgrade, log in to SBM Application Repository, and save both the original and latest versions of each process app to file. After you save both copies, follow the steps described in the Serena Service Manager On-Premise Upgrade Guide to create a comparison report that highlights the changes you have made to each process app. You will use this report to help you decide which changes you want preserve in the new version of each process app.