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

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

• If your SBM installation is distributed among multiple servers, in SBM Configurator in the Component Servers tab, determine which servers host the following SBM components:
  • SBM Application Engine
  • SBM Application Repository
  • SBM Common Services
  You will install Release Control 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 points to its own instance of SBM Common Services. SBM Application Repository is the only component that can be shared by multiple environments.
  Important: You will encounter problems in Release Control if only one instance of SBM Common Services is used by multiple environments.

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

• Procure and install licenses for Release Control.
• If you are using an Oracle database, read the following and prepare your database accordingly:
  • SBM can be configured with separate Oracle 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. Release Control 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.