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 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:
Prepare for the
Release Control
install by performing the following tasks:
- Procure and install licenses for
Release Control.
- 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.
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.
Copyright © 2012–2016 Serena Software, Inc. All rights reserved.