Pre-Installation Checklist

You must successfully install and configure SBM on one or more servers according to the steps in the SBM Installation and Configuration Guide. You can either perform a complete SBM installation (in which all SBM components are installed on a single server) or you can perform a custom installation (in which the SBM components are distributed among multiple servers). If you perform a custom installation, note that you must install every SBM component in order to have a fully functional SBM system.

Follow the steps in SBM Installation and Configuration Guide to validate your SBM installation once you have successfully configured SBM and finished the Create New Database wizard using SBM System Administrator.

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 version 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 JBoss 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. SBM Application Repository is the only component that can be shared by multiple environments.

Important: The SBM environments cannot share one instance of SBM Common Services. You will encounter problems in Serena Service Manager if only one instance of SBM Common Services is used 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.

Service Manager does not currently support separate Oracle schemas for each SBM component within the same Oracle instance. This also applies to multi-environment or "path to production" installations—the same Oracle instance cannot be used for multiple SBM environments (such as development, test, and production).

Important: If you currently use multiple schemas with SBM in the same Oracle instance and you plan to use Service Manager, please contact Support for assistance.

However, SBM can be configured with separate schemas as long as the SBM Orchestration Engine and Common Log tables share the same schema. This means SBM Orchestration Engine and Common Log will share one schema, while SBM Application Engine and Application Repository have their own schemas or are shared in a separate schema. If you plan to use additional environments, you must create them in separate Oracle instances in this scenario.

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.