Install and Set Up → Getting Started → Pre-Installation Checklist
The following checklist describes the tasks that you need to perform
- Install and configure
SBM 11.2 or
higher according to the steps in the
SBM Installation and Configuration
You must have a fully functional
and database created before you install
- If you are using a single server to host all the
components, ensure the server has at least 4GB of RAM. For a distributed
installation, ensure that each
server has 4 GB of RAM. You may encounter problems running the
service with less RAM.
- Ensure that you have at least one administrative user who has
sufficient privileges to import and promote the solution files in
For details on these privileges, see the
SBM Application Repository
- If you are using multiple environments in
as development, test, and production), ensure that each environment has its own
SBM Common Services
(not a shared instance).
is the only
component that can be shared by multiple environments.
- Procure and install licenses for the solutions that you intend to
- 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
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. 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
- If you are upgrading from a previous version of
before you upgrade, log in to
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
SSM On-Premise Upgrade
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.
Copyright © 2012–2017 Serena Software, Inc., a Micro Focus company. All rights reserved.