Pre-Installation Checklist

The following checklist describes the tasks that you need to perform before you perform the install.

If you do not currently have SBM installed and configured:

• 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.

Once you have successfully installed and configured SBM, review your installation as follows:

• 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 install Release Manager on the server or servers that host these SBM components.
• If you are using multiple environments in SBM (such as development, test, and production), 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 Release Manager if only one instance of SBM Common Services is used by multiple environments.

Prepare for the Release Manager install by performing the following tasks:

• Procure and install licenses for Release Manager.
• If you are using IIS 7 or higher, you must ensure that the WebDAV handler mapping and the WebDAVModule are removed from IIS on the server that hosts SBM Application Engine. WebDAV prevents Release Manager from using critical Web service DELETE and PUT operations. To remove WebDAV, select the Web site in IIS, edit the Handler Mappings and remove WebDAV. Navigate back to the Web site Home page, edit the Modules, and remove the WebDAVModule.
• Decide if you will use the native instance of Release Automation (which is installed with Release Manager) or a standalone instance of Release Automation (installed separately from Release Manager as described in the Serena Release Manager - Release Automation User's Guide).
  Important: The ZMF plugin requires a Tomcat application server, which is only available with a standalone Release Automation instance. This means that if you intend to use the ZMF plugin with Release Manager, you must use a standalone Release Automation instance (because the native instance only runs under JBoss).
• If you intend to use the native Release Automation instance that is installed with Release Manager:
  • Download one of the following applicable JDBC drivers for your DBMS (either SQL Server or Oracle):
    • sqljdbc4.jar
    • ojdbc6_g.jar
    You must specify the location of the JDBC driver in SBM Configurator if plan to use a native instance of Release Automation with Release Manager.
  • Create a new database space for Release Automation your DBMS. You will enter the database name and additional database connection information in SBM Configurator after the installer is finished.
• Release 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, 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.