OpenText™ System Center Manager

Administration Guide

This guide explains configuration and administration tasks for

OpenText™ System Center Manager.

SYSCM240400-AGD-EN-01
OpenText™ System Center Manager
Administration Guide
SYSCM240400-AGD-EN-01
Rev.: 2024-Sept-24
This documentation has been created for OpenText™ System Center Manager CE 24.4.
It is also valid for subsequent software releases unless OpenText has made newer documentation available with the product,
on an OpenText website, or by any other means.

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1

Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: https://support.opentext.com
For more information, visit https://www.opentext.com

© 2024 Open Text

Patents may cover this product, see https://www.opentext.com/patents.

Disclaimer

No Warranties and Limitation of Liability

Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.
 Table of Contents
1 System Center Manager ............................................................ 9
1.1 Overview: The System Center Manager Lifecycle ................................ 9
1.1.1 Add Systems and Products .............................................................. 10
1.1.2 Download and Install OpenText Software Products ........................... 11
1.1.3 Patch and Update OpenText Software Products ................................ 11

2 The System Center Manager Home Page .............................. 13

2.1 Home Page: Systems by Status ....................................................... 13
2.2 Home Page: Notifications ................................................................ 14
2.3 Home Page: Pending Systems ......................................................... 14
2.4 Home Page: Patches and Updates ................................................... 15

3 Solutions and Environments .................................................. 17

3.1 Select a Solution Environment ......................................................... 18

4 Systems .................................................................................... 19
4.1 View Systems Information ............................................................... 19
4.1.1 The Systems Overview .................................................................... 20
4.1.2 The System Details View ................................................................. 20
4.2 Add and Remove Systems .............................................................. 22
4.3 Register and Unregister Systems ..................................................... 23
4.4 Enable and Disable Systems ........................................................... 24
4.5 Discover Product Component Instances ........................................... 24
4.6 Enable and Disable Product Component Instances ........................... 25
4.6.1 Enable Content Server Product Instances ......................................... 25
4.6.1.1 Enable a Content Server Master Server ............................................ 26
4.6.1.2 Enable Additional Content Server Instances ..................................... 27
4.6.2 Disable a Product Component Instance ............................................ 29

5 Products, Components, and Instances ................................. 31

5.1 The Products Page ......................................................................... 32
5.1.1 The Products Page: Updates View ................................................... 33
5.1.1.1 The Update Details page ................................................................. 35
5.1.2 The Products Page: Product View .................................................... 37
5.1.3 The Products Page: Component View .............................................. 38
5.1.3.1 The Component Instance Details Page ............................................. 38
5.1.3.2 The Content Server Product Component View .................................. 39
5.1.3.2.1 Apply an Administration Settings file to Content Server ...................... 39
5.1.4 The Products Page: Search Patches View ........................................ 41
5.2 Logs Packages ............................................................................... 43
5.2.1 Create a Logs Package ................................................................... 45

SYSCM240400-AGD-EN-01 Administration Guide iii

Table of Contents

5.2.2 Download a Logs Package .............................................................. 45

5.2.3 Delete a Logs Package ................................................................... 46

6 Obtain and Apply Updates ...................................................... 47

6.1 Update the System Center Manager Manifest File ............................. 47
6.2 Download Updates .......................................................................... 47
6.2.1 Obtain Updates in Online Mode ....................................................... 49
6.2.2 Obtain Updates in Offline Mode ....................................................... 49
6.2.3 Download Content Server Quarterly Updates .................................... 50
6.3 Apply Updates ................................................................................ 50
6.3.1 Apply Updates to Content Server ..................................................... 52
6.3.1.1 Verify Prerequisites ......................................................................... 52
6.3.1.2 Apply Updates to Content Server ..................................................... 54
6.3.2 Roll Back a Content Server Update Deployment ............................... 56
6.4 Update Analysis (for Content Server Updates) .................................. 57
6.4.1 Running Update Analysis ................................................................. 57
6.4.2 Interpreting the Content Server Update Delta Report ......................... 57
6.5 Resynchronize a Content Server Product Component instance .......... 58

7 The Product Catalog ............................................................... 59

7.1 Browse and Search for Product Versions .......................................... 60
7.2 Obtain Product Documentation ........................................................ 61
7.3 Download Products ......................................................................... 61

8 Execution Plans, Steps, and Variables .................................. 63

8.1 Execution Plans .............................................................................. 64
8.1.1 Add an Execution Plan .................................................................... 65
8.1.2 Edit an Execution Plan .................................................................... 66
8.1.3 Run an Execution Plan .................................................................... 66
8.1.4 Copy an Execution Plan .................................................................. 67
8.1.5 Delete an Execution Plan ................................................................. 68
8.1.6 Export an Execution Plan ................................................................. 68
8.1.7 Import an Execution Plan ................................................................. 68
8.1.8 Monitor Execution Plans .................................................................. 69
8.2 Execution Plan Steps ...................................................................... 69
8.2.1 Configuring Plan Steps .................................................................... 71
8.3 Execution Plan Step Library ............................................................. 71
8.3.1 AppWorks Gateway Execution Plan Steps ........................................ 72
8.3.2 Archive Center Execution Plan Steps ............................................... 72
8.3.3 Common Execution Plan Steps ........................................................ 73
8.3.4 Content Server Execution Plan Steps ............................................... 74
8.3.5 Directory Services Execution Plan Steps .......................................... 76
8.3.6 Document Pipeline Execution Plan Steps ......................................... 76

iv OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 Table of Contents

8.3.7 Intelligent Viewing Execution Plan Steps .......................................... 77

8.3.8 PowerDocs Execution Plan Steps .................................................... 77
8.4 Execution Plan Variables ................................................................. 78
8.4.1 Step Variables ................................................................................ 78
8.4.1.1 Create a Step Variable .................................................................... 79
8.4.1.2 Apply an Existing Step Variable ....................................................... 79
8.4.1.3 View and Edit Step Variables ........................................................... 79
8.4.1.4 Remove Step Variable Assignments ................................................. 79
8.4.2 System Variables ............................................................................ 80
8.4.2.1 Add a System Variable .................................................................... 80
8.4.2.2 Apply a System Variable .................................................................. 81
8.4.2.3 View and Edit System Variables ....................................................... 81
8.4.2.4 Remove System Variables ............................................................... 81

9 Monitor System Center Manager Activities .......................... 83

9.1 The Activities Overview ................................................................... 83
9.2 The Activities Page: Execution Plans View ........................................ 84
9.3 The Activities Page: Downloads View ............................................... 85
9.4 The Activities Page: Notifications View ............................................. 86

10 Update System Center Manager ............................................ 89

10.1 Update System Center Manager in Online Mode ............................... 89
10.2 Update System Center Manager in Offline Mode ............................... 90

11 Configure System Center Manager ........................................ 91

11.1 Settings: General ............................................................................ 91
11.2 Settings: Logs ................................................................................. 92
11.3 Settings: Proxy ................................................................................ 93
11.4 Settings: Users ............................................................................... 94
11.4.1 Add Users ...................................................................................... 95
11.4.1.1 Add a Locally Authenticated User ..................................................... 95
11.4.1.2 Add an OTDS User ......................................................................... 96
11.4.2 Edit a User ..................................................................................... 97
11.4.3 Remove a User ............................................................................... 98
11.4.4 Unlock a User ................................................................................. 98
11.4.5 Reset a User’s Password ................................................................. 99
11.4.5.1 Reset a Password using a Security Token ...................................... 100
11.5 Settings: Audit .............................................................................. 101
11.6 Settings: Agents ............................................................................ 101
11.6.1 Install the System Center Agent on Windows .................................. 101
11.6.1.1 Scripted Installation of the System Center Agent ............................. 101
11.6.1.2 Interactive Installation of the System Center Agent .......................... 102
11.6.1.3 Unattended Installation of the System Center Agent ........................ 103

SYSCM240400-AGD-EN-01 Administration Guide v

Table of Contents

11.6.2 Install the System Center Agent on Linux ........................................ 104

11.6.2.1 Install the System Center Agent using the Installation Script ............ 105
11.6.2.2 Install the System Center Agent using the SystemCenter_Agent.sh
File ............................................................................................... 106
11.6.2.3 Install the System Center Agent using the
install_otsystemcenteragent.sh File ................................................ 107
11.6.2.4 Unattended Installation using the SystemCenter_Agent.sh File ........ 108
11.6.2.5 Unattended Installation using the install_otsystemcenteragent.sh
File ............................................................................................... 109
11.7 Settings: Authentication ................................................................. 109
11.7.1 Authentication Method ................................................................... 110
11.7.2 Local Account Policy ..................................................................... 111
11.8 Settings: Solutions ........................................................................ 111
11.8.1 Add, Edit and Remove Solutions .................................................... 112
11.8.1.1 Add a Solution .............................................................................. 112
11.8.1.2 Modify a Solution .......................................................................... 112
11.8.1.3 Delete a Solution ........................................................................... 112
11.8.2 Export and Import Solutions ........................................................... 113
11.8.2.1 Export a Solution ........................................................................... 113
11.8.2.2 Import a Solution ........................................................................... 114
11.8.3 Add, Edit and Remove Environments ............................................. 115
11.8.3.1 Add an Environment ...................................................................... 115
11.8.3.2 Modify an Environment .................................................................. 115
11.8.3.3 Delete an Environment .................................................................. 116
11.8.4 Synchronize Solution Environments ............................................... 116
11.8.4.1 Synchronize Two Content Server Environments .............................. 118
11.9 Settings: External Vendor Files ...................................................... 120
11.9.1 Add External Vendor Files to System Center Manager .................... 121
11.9.2 Remove External Vendor Files from System Center Manager .......... 121
11.9.3 Restrict External Vendor File Uploads ............................................ 122
11.10 Settings: Manifest ......................................................................... 122
11.10.1 Update the Manifest in Offline Mode ............................................... 123
11.10.2 Manifest Repair ............................................................................. 123
11.11 Settings: Support .......................................................................... 124
11.11.1 Create a Log Package ................................................................... 124
11.12 Settings: Notification ...................................................................... 125
11.13 Settings: Activity ........................................................................... 126
11.14 Secure Sockets Layer (SSL) .......................................................... 127
11.14.1 Run System Center Manager on SSL ............................................. 127
11.14.1.1 Enable System Center Manager to run on SSL ............................... 127
11.14.1.2 Configure each System Center Agent to Connect to the System
Center Manager SSL Address ....................................................... 128
11.14.1.3 Obfuscate the keyStore and keyManager Passwords ...................... 129

vi OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 Table of Contents

11.14.1.4 SSL Deployment Using a Self-Signed Certificate ............................. 130

11.14.1.5 Troubleshooting SSL Deployments ................................................ 131
11.14.2 Connect System Center Manager to OTDS or Content Server using
SSL .............................................................................................. 131
11.15 Java Memory Pool ........................................................................ 132
11.15.1 Java Memory Settings on Windows ................................................ 132
11.15.2 Java Memory Settings on Linux ..................................................... 133
11.16 Update System Center Manager .................................................... 133
11.16.1 Update System Center Manager in Online Mode ............................. 134
11.16.2 Update System Center Manager in Offline Mode ............................. 134

12 System Center Manager Logs .............................................. 137

12.1 System Center Manager and Agent Logging ................................... 137

SYSCM240400-AGD-EN-01 Administration Guide vii

Chapter 1
System Center Manager

OpenText™ System Center Manager simplifies the installation, configuration,

patching, and updating of OpenText software applications.

Using System Center Manager, you can:

Download OpenText software

Using the System Center Manager Product Catalog, you can view product
documentation, review software requirements and dependencies, and download
installers for OpenText software applications.
Install OpenText software
You can use standardized System Center Manager Execution Plans to install
OpenText software Products on the Systems that you manage. System Center
Manager Execution Plans are re-usable and can be tailored for use in differing
Environments.
Patch and Update OpenText software
System Center Manager allows you to patch and update multiple OpenText
software applications installed on multiple computers, in simple steps, from a
single desktop.
You can use System Center Manager to discover, download, and apply software
patches and updates to supported software applications in your Environments.
System Center Manager ensures that updates are applied in a manner that is
safe, consistent, and reliable. By decreasing the manual intervention involved in
patching your OpenText systems, it makes patching easier and less error-prone.
Automate Routine File System Operations
You can develop System Center Manager Execution Plans to perform routine file
system operations, like copying, deleting, moving and renaming files, and
creating standard folder trees.

1.1 Overview: The System Center Manager Lifecycle

System Center Manager manages the installation and configuration of supported
OpenText software products, from the download of the product installers to the
ongoing maintenance of the functioning software. This online help explains how to
use it to perform each step of the System Center Manager lifecycle.

System Center Manager is used to manage remote computers, or Systems. You start
by installing the System Center Agent on a System, and then registering the System
in System Center Manager, making it a managed System. You can then use System
Center Manager Execution Plans to perform a variety of preset tasks on the System,
including installing supported OpenText software products on it.

SYSCM240400-AGD-EN-01 Administration Guide 9

Chapter 1 System Center Manager

You can also use System Center Manager to keep your supported OpenText
software products up to date, using its built-in patching and updating capabilities.
System Center Manager has a manifest that is updated daily, making it aware of
software patches and updates as soon as they become available. System Center
Manager handles the entire patching process. It downloads patches and updates and
applies them automatically and systematically.

The System Center Manager manifest also contains information on OpenText

product releases, so it can inform you of any new OpenText software that becomes
available. You can obtain product information and download product installers
automatically from the System Center Manager Catalog. Once you have
downloaded a product installer to System Center Manager, you can use it in an
Execution Plan to install software on your managed Systems.

Each of the main steps in the System Center Manager lifecycle is briefly described in
this section, and in greater detail later in this online help.

1.1.1 Add Systems and Products

Systems are computers that are managed by System Center Manager. Under normal
circumstances, you use System Center Manager to install software on a System and
to keep that software up to date.

Add and Register a System

To add a System, install the System Center Agent on a computer that you want to
manage using System Center Manager. The Agent software is available on the
Settings page: Agents view.

Tip: For more information, see “Install the System Center Agent on Windows”
on page 101 or “Install the System Center Agent on Linux” on page 104.

After you install the Agent software, the System becomes visible in System Center
Manager. Register the System on the Systems overview.

Tip: For more information, see “Register and Unregister Systems”

on page 23.

Discover and Enable Product Component Instances

Product Component Instances in System Center Manager are specific installations of
supported OpenText software.

On a registered System, run Product discovery and enable any Product Component
Instances that you want to manage using System Center Manager.

Tip: For more information, see “Discover Product Component Instances”

on page 24 and “Enable and Disable Product Component Instances”
on page 25.

10 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 1.1. Overview: The System Center Manager Lifecycle

After you have registered a System and discovered any software on it, the state of
the System determines your next step:

• If the registered System does not currently run supported OpenText software,
you can use System Center Manager to install a software product. See
“Download and Install OpenText Software Products” on page 11.
• If the registered System is already running supported OpenText software, you
can use System Center Manager to keep it up to date. See “Patch and Update
OpenText Software Products” on page 11.

1.1.2 Download and Install OpenText Software Products

You can use System Center Manager to download supported OpenText software
products and install them on managed Systems using Execution Plans.

Note: Software download and Execution Plans are not available in all versions
of System Center Manager.

Download Product Installers and Product Documentation

To download OpenText software products, use the functions available in the System
Center Manager Catalog.

Tip: For more information, see “The Product Catalog“ on page 59.

Install Supported OpenText Products Using Execution Plans

You can use System Center Manager Execution Plans to perform a wide variety of
repeatable tasks. An Execution Plan can perform a very simple single-step action,
such as copying a file to a managed System, or it can perform a complex multi-step
action, such as installing and configuring Content Server and OpenText Directory
Services on multiple managed Systems.

Tip: For more information, see “Execution Plans, Steps, and Variables“
on page 63.

1.1.3 Patch and Update OpenText Software Products

System Center Manager automates each step of the software patching process.

Check for Updates

System Center Manager needs up-to-date information to provide you with all of the
available updates for your applications. The information is contained in a manifest
file. If you operate in online mode, the manifest file is updated automatically, but in
offline mode, you must update the manifest file manually.

Tip: For more information, see “The Products Page: Updates View”
on page 33

SYSCM240400-AGD-EN-01 Administration Guide 11

Chapter 1 System Center Manager

Download Updates
When System Center Manager informs you that a patch or update is available, you
can download it automatically if you operate in online mode. In offline mode, the
process is similar to updating the manifest: you download any updates to a
computer that can connect to the Internet and then upload them to System Center
Manager.

Tip: For more information, see “Download Updates” on page 47.

Apply Updates to Product Component Instances on Systems

Any updates that you have downloaded appear on the Products page: Product view
on the Downloaded tab. To install them on one or more managed Systems, select the
updates and click Install Selected.

Tip: For more information, see “Apply Updates” on page 50.

12 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

Chapter 2
The System Center Manager Home Page

The System Center Manager Home page provides you with an at-a-glance view of
the state of your current Solution Environment. It informs you of operations that you
may need to perform and of messages that you may need to view.

You can access the Home page any time by clicking Home on the Navigation

menu or by clicking OpenText System Center Manager beside the Navigation

menu.

2.1 Home Page: Systems by Status

The Systems by status tile displays the Systems that are under the control of System
Center Manager in your current Environment.

The Systems by status tile has a pie chart with segments that show the proportion of
Systems in your Environment that are online, offline, unregistered, or disabled. To
view the absolute number of Systems in any category, hover over the relevant chart
section. You can include or exclude Systems from the pie chart by clicking Online,
Offline, Unregistered, or Disabled.

SYSCM240400-AGD-EN-01 Administration Guide 13

Chapter 2 The System Center Manager Home Page

2.2 Home Page: Notifications

The Notifications tile displays notifications that may require your attention. The
newest notifications appear at the top.

Notifications may be informational only, or they may indicate that you need to
perform an action. For example, a notification may inform you that a Component
Instance was recently enabled. In that case, it confirms the successful completion of
an action that you performed. Another notification could indicate that a new System
is available to be registered. In that case, action is probably required: you need to
register the System and enable its Component Instances.

To view a complete listing of available notifications, click the Notifications tile and
then click the Open notifications button to open the Activities page: Notifications
view.

2.3 Home Page: Pending Systems

Systems that are available to be registered in System Center Manager appear in the
Pending systems tile. If a System appears in this tile, it is an indication that you
should open the Systems page, register the System, and enable any Product
Component Instances that you would like to manage using System Center Manager.

14 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 2.4. Home Page: Patches and Updates

Click any listed System to open its Details page. Click the Open Systems button

to open the Systems Overview page.

For more information see:

• “Register and Unregister Systems” on page 23

• “Enable and Disable Product Component Instances” on page 25

2.4 Home Page: Patches and Updates

The Patches and Updates tile shows you, for each Product that you manage using
System Center Manager, whether Updates are available to be downloaded from
OpenText My Support.

SYSCM240400-AGD-EN-01 Administration Guide 15

Chapter 2 The System Center Manager Home Page

Click any Product to view its Overview page, where you can view information on
the Updates that are available.

16 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

Chapter 3
Solutions and Environments

System Center Manager is designed to manage multiple software Solutions, with

each Solution having one or more Environments. When you log on to System Center
Manager, you are logged on to a specific Solution Environment. Your Solution
Environment appears in the top left corner of the System Center Manager interface.

Tip: If you have access to more than one Solution Environment, you can use
the Change Environment option on the User Menu to change the Environment
that you are working in. The User Menu appears in the top right corner of the
System Center Manager interface. Its appearance varies according to the

logged-on user. For the Admin user, it has this appearance: .

The terms Environment and Solution have special meanings within System Center
Manager.

Environment
An Environment is a group of Systems that run OpenText software Products and
third-party applications to deliver a software service. For example, a Content
Server Environment might consist of several Systems that run instances of
Content Server, with additional host computers providing the web server and
database management software that Content Server requires.
Organizations typically have multiple Environments that deliver the same
software service. For example, your organization might have QA, Dev, and UAT
Environments that support a Production Environment. In such a setup, each
Environment runs the same software, but not on similar computers or
configurations. For example, a Production Environment might run a software
service on numerous higher-powered machines, whereas a Dev Environment
might run every Product and supporting application in the software service on a
single host computer.
Environments are central to System Center Manager. Your view of System
Center Manager is determined by the Environment that you are working on.
When you are working on an Environment, you see only the Systems and
Products that belong to that Environment. Any Execution Plan that you create
applies to your current Environment. When you apply updates to Products, only
the Systems in your current Environment are updated.

Example: You are logged on to a Solution Environment named Content Server :

Production that includes six computers that run Content Server. When you click
Systems, you see the Managed Systems that belong to your current Solution
Environment. You do not see Systems that belong to other Solutions and Environments.
When you use System Center Manager to apply Content Server patches in this
environment, System Center Manager applies the patches to the six computers in the

SYSCM240400-AGD-EN-01 Administration Guide 17

Chapter 3 Solutions and Environments

Content Server : Production Environment. It does not apply patches to the Content
Server computers in any other Content Server Solution Environment.

Solution
A Solution is used to group Environments that provide a similar software
service. You can place Environments in Solutions according to the needs of your
organization.

Example: An organization could have a Content Server Solution that includes the
following Environments:

• Content Server : QA
• Content Server : Dev
• Content Server : UAT
• Content Server : Production

Alternatively, an organization might have different Environments that serve distinct

internal or external customers.

In System Center Manager, you can see any Execution Plans that are created
within your Solution. This means that you can create an Execution Plan in a
given Environment (Development, for example) and then copy that Execution
Plan into another Environment (Production, for example), where it can be re-
used. For more information, see “Execution Plans, Steps, and Variables“
on page 63.

For information on adding, modifying, and deleting Solutions and Environments,

see “Settings: Solutions” on page 111

3.1 Select a Solution Environment

When you log on to System Center Manager, you are logged on to a specific Solution
Environment: either the last Environment that you managed or your default
Solution Environment. If you have access to only one Solution Environment, you are
logged on to that one.

To change your current Environment, click the Switch environment button on

the Header Bar. You can change to a different Environment in your current Solution,
or to an Environment from a different Solution altogether. After you change to a
different Environment, you work with the Systems that belong to that Environment
and the Products that run on those Systems.

Note: If, you attempt to log on and System Center Manager displays the
message Access denied; please contact administrator, it is possible that you
are not assigned to any Environment. If so, your administrator can correct the
problem by assigning you to an Environment.

18 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

Chapter 4
Systems

In System Center Manager, Solutions and Environments are composed of Systems:

computers that run the System Center Agent software and can be managed by
System Center Manager. Systems can run OpenText software and third-party
software. For the purposes of System Center Manager, a System that runs OpenText
software runs one or more Instances of a Component of an OpenText Product. Systems
belong to a single Solution Environment. They cannot belong to more than one.

A Product is an OpenText software grouping or family. Products are typically

composed of multiple OpenText and third-party applications. A Product Component
is one of the applications that make up the Product. A Product Component Instance is
a specific installation of a Product Component. In certain cases, there could be
several Instances of a Product Component installed on a System.

Example 4-1: Systems, Products, Components, and Instances

Myserver.corporate.com is the name of a System that runs two Instances of

Content Server, which is a Component of the Content Server Product. In this
example, Content Server is both a Product and a Product Component.

Systems run the System Center Agent software. The System Center Agent connects
them to System Center Manager, and provides information on the OpenText
software that they run. System Center Manager can install software, apply Updates
and configuration changes, and perform other administrative tasks on registered
Systems.

After you install the Agent, a System appears in System Center Manager as a
pending unregistered System. To manage a System, you must first register it, and
then enable each Product Component Instance that you want to manage on the
System.

4.1 View Systems Information

Information on the Systems in System Center Manager appears on the Systems page
in two views: the Systems Overview and the System Details view.

SYSCM240400-AGD-EN-01 Administration Guide 19

Chapter 4 Systems

4.1.1 The Systems Overview

The Systems Overview shows Managed and Pending (unregistered) Systems.

Unregistered Systems are visible in every Solution Environment until they are
registered. After a System is registered, it is visible only in the Environment that it is
registered in.

Managed Systems
Managed Systems are Systems that have been registered and that can be
configured and updated using System Center Manager. They can have an Agent

Status of Idle , Running , offline , or Disabled . (A System with

a status of Disabled is not affected by any update operations that you perform
in System Center Manager.)
The No. Products column shows the number of Product Components that are
installed on the System. You can find more information about the installed
Product Components on the System Details view.
On the Systems Overview, a registered System’s Inline Action Bar offers

options to Disable or Unregister the System, and also to access the

System’s Details view .

Unregistered Systems
Unregistered (Pending) Systems are known to System Center Manager but
cannot be managed. You must register a System before you can enable and
manage the Product Component Instances that are on it. Limited information is
available for unregistered Systems.
On the Systems Overview, an unregistered System’s Inline Action Bar offers

options to Register or Remove the System, and also to access the

System’s Details view .

4.1.2 The System Details View

The System Details view provides detailed information about a System and allows
you to perform operations on it. To open the System Details view, do one of the
following:

•
On the Systems Overview page, click the Details button in a System’s
Inline Action Bar.
• Click the System in the Systems Available area of the Systems page

The System Details view presents information on four tabs:

• General

20 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 4.1. View Systems Information

• Products
• Networking
• Operating System

System Details General tab

The General tab displays the System’s Name, Host name, Status, and Description.
It shows the Log level and HTTP log level that is in effect for that System. It also
shows when it first connected to System Center Manager, when it was last
registered, who registered it, the installation path of the Agent software and the
version of the Java Runtime Environment (JRE) that it uses. Action buttons at the top
allow you to disable or unregister the system, and to edit some of the details that
appear on this page. To modify the name and description of the System, and to set
the Log level or HTTP log level, click Edit, make changes, and then click Save. For
more information on logging for System Center Manager and System Center Agents,
see “System Center Manager and Agent Logging” on page 137.

The buttons and operations that are available on the System Details view depend on
whether the System is registered or not. For information on the various operations
enabled by the available buttons, see the following topics:

• “Register and Unregister Systems” on page 23.

• “Enable and Disable Systems” on page 24.
• “Add and Remove Systems” on page 22.

System Details Products tab

After you register a System, Product Component Instances running on it appear on
the Products tab of the System Details view.

The Products tab shows information on every OpenText Product Component

Instance on a System. For each one, it shows the Product, Component, Version,
Install path and Discovery date. In addition, the Supported and Enabled columns
indicate whether the Product Component Instance is supported (in other words,
whether System Center Manager can apply Updates to it) and enabled.

Tip: Additional information about a Product Component Instance can be

viewed on the Component Instance Details page. See “The Component
Instance Details Page” on page 38.

To check if new Products have been added to the System since the last discovery
date, you can click Discover Products to update the list.

For more information on discovering and enabling Product Component Instances,

see:

• “Discover Product Component Instances” on page 24.

• “Enable and Disable Product Component Instances” on page 25

SYSCM240400-AGD-EN-01 Administration Guide 21

Chapter 4 Systems

System Details Networking tab

The Networking tab lists the physical (MAC) address of the System and its IPv4 and
IPv6 network addresses.

System Details Operating System tab

• The Operating System tab shows hardware information for the System: current
CPU load, memory (in use and available), and disk space (in use and available).

4.2 Add and Remove Systems

You do not need to perform any specific action to add a System to System Center
Manager other than to install the System Center Agent. After you install the System
Center Agent on a host computer, the System appears automatically in the
Unregistered systems section of the Systems Overview.

For instructions on installing the System Center Agent, see “Settings: Agents”
on page 101.

Tip: If you need to re-add a System, restart the Agent on the System host
machine.

Remove a System
To remove a registered System, you must first unregister it. (See “Register and
Unregister Systems” on page 23.) A registered System cannot be removed.

To remove an unregistered System, do one of the following:

• Open the System Details view of the System that you want to remove and then
click Remove.
•
On the System’s Inline Action Bar, click the Remove button .

Optionally, you can uninstall the System Center Agent from the System. If you do
not uninstall the Agent and the Agent software is restarted, the System will attempt
to register with System Center Manager again.

22 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 4.3. Register and Unregister Systems

4.3 Register and Unregister Systems

New Systems appear on the Systems Overview as Pending Systems. Before you can
manage a System, you must register it. When you register a System, it is added to
your current Solution Environment.

Tip: After you register a System, enable any Product Component Instances on
the System that you want to manage. See “Enable and Disable Product
Component Instances” on page 25.

Registering a System
You can register a System on the Systems Overview page or on the System Details
view. Before you register a System, ensure that you are logged on to the Solution
Environment that you want to add the System to.

To register a System:

1. Do one of the following:

• In the Pending tab of the Systems Overview, click the Register button
in the System’s Inline Action Bar.

• On the System Details view, click Register System.

2. Select the I agree to register this system in the current environment check box.

Unregistering a System
If you no longer want to use System Center Manager to manage a System, or if you
have assigned it to an incorrect Environment and want to assign it to the correct one,
you can unregister the System.

Tips

• To stop managing a System temporarily, disable it. See “Enable and Disable
Systems” on page 24.

• To stop managing a Product Component Instance on a System and continue

managing the other Product Component Instances on it, disable the Product
Component Instance. See “Disable a Product Component Instance”
on page 29.

To unregister a System, click the Unregister button on its Inline Action Bar or
open its System Details view, and then click Unregister system.

SYSCM240400-AGD-EN-01 Administration Guide 23

Chapter 4 Systems

4.4 Enable and Disable Systems

When you register a System, it is enabled for management by System Center
Manager. If you want to temporarily remove a System from the group of Systems
that are managed by System Center Manager, you can disable it.

Tips

• To stop managing a System permanently, unregister it. See “Unregistering

a System” on page 23.

• To stop managing a Product Component Instance on a System and continue

managing the other Product Component Instances on it, disable the Product
Component Instance. See “Disable a Product Component Instance”
on page 29.

Enable a System

You can enable a System that has a status of Disabled by clicking the Enable

button on its Inline Action Bar, or by clicking Enable on its System Details
view.

Disabling a System
If a System appears on the Systems overview with a status of anything other than
Disabled, it is enabled. You can disable it on its System Details view.

You can disable it by clicking the Disable button on its Inline Action Bar, or by
clicking Disable on its System Details view.

4.5 Discover Product Component Instances

In most cases, System Center Manager discovers the Product Component Instances
on a System when you register the System, and displays them in the Products tab of
the System Details view. However, if you add or remove OpenText software on a
System, you can update the information on the Products tab by clicking Discover
Products.

Tip: You can discover products only on a System that is registered, enabled,
and available, and that has an status of Idle or Running. If a System is
unavailable, its Discover Products button is dimmed and cannot be used.

After you click Discover Products, information on the Product discovery operation
is available on the Activities Overview.

24 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 4.6. Enable and Disable Product Component Instances

4.6 Enable and Disable Product Component

Instances
You must enable any Product Component Instance that you want to manage.

Product Component Instances are enabled on the Products tab of “The System

Details View” on page 20. To enable a Component Instance, click Enable in the
Inline Action Bar for the Component Instance, or select the check box beside the
Product Component Instance and click Enable at the top of the list of Product
Component Instances.

After you click Enable, you are prompted to analyze the Product Component
Instance. System Center Manager performs the Download, Validate, and Update
steps, and then enables the Product Component Instance. To view information on
the Enable Component Instance operation, you can look in the Other tab of the
Activities Overview.

After you enable the first Instance of a Product Component, information on that
Product and Component becomes available on the Products page. If you have not
enabled any Instances of a specific Product Component, no information about it
appears on the Products page.

4.6.1 Enable Content Server Product Instances

In a typical production deployment of Content Server, multiple instances of Content
Server are deployed in a cluster. To enable clustered Content Server instances in
System Center Manager, you first designate a Master Server and then you enable the
additional instances.

When you enable an additional Content Server instance, System Center Manager
analyzes the new instance and compares it to the Master Server. If necessary, it
brings the new instance up to date with the Master System by adding any missing
patches, Updates, and language packs. After an instance is enabled and brought up
to date, its Windows service is shut down, with its Startup Type set to Manual. This
allows you to perform any necessary work on the instance after it is brought up to
date before it is started up again.

System Center Manager requires Anonymous Authentication on

Microsoft Internet Information Services

If you deploy Content Server on Microsoft Internet Information Services, you

must enable Anonymous Authentication to allow System Center Manager to
connect using the REST API. If Anonymous Authentication is not enabled,
System Center Manager will report that An error has occurred while
attempting to authenticate.

SYSCM240400-AGD-EN-01 Administration Guide 25

Chapter 4 Systems

4.6.1.1 Enable a Content Server Master Server

The first instance of Content Server that you enable is the Master System. It serves as
the reference instance for any subsequent instances that you add from the same
Content Server cluster. To enable the Master System, you provide the Content Server
URL, and the name and password of a Content Server administrative user.

Tip: You can change the instance that is the Master Server on the Content
Server Product Component view of the Products page. Enable Master System
in the row of the Content Server Instance that you want to make the new
Master Server. You are prompted to provide the same information as you did
for the previous Master Server.

To enable a Content Server Master System:

1. In the Products tab of the System Details view, do one of the following:

• Click Enable in the Inline Action Bar the Content Server instance that
you want to enable.
• Select the check box beside the Content Server instance that you want to
enable, and click Enable above the Product Component Instance listing.

2. On the Enable component instance ‘Content Server’ page, click Analyze.

3. On the Enable component instance ‘Content Server’ dialog box, enter the
following connection parameters for the Content Server Instance and then click
Validate.

a. In the Scheme box, select http:// or https://.

b. In the Host box, enter the name of the Content Server host computer.

Note: For an https:// connection, you must enter the name of the
host as it appears on the server certificate.
c. In the Port box, enter the IP port for connecting to Content Server. You
must enter a port number even if Content Server uses the default port for
http or https.

d. In the Path box, enter the remainder of the Content Server URL. Enter the
portion of the Content Server URL that follows the web server name and
port and precedes the question mark (?) For example, if the address of your
Content Server Administration page is http://example.corporate.com/
OTCS/cs.exe?func=admin.index, enter OTCS/cs.exe

e. Enter the name of a Content Server user that has the System
administration rights user privilege in the User name box.

f. Enter the user’s password in the Password box.

4. On the Enable component Instance ‘Content Server’ page, click Next.

26 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 4.6. Enable and Disable Product Component Instances

After you click Next, System Center Manager enables the Product Component
Instance. You can view more information on the Enable Component Instance
operation on the Activities Overview page.
5. Click Finish to complete the operation and return to the Products tab of the
System Details view.

After the Master Instance is enabled, it appears in the Content Server Product
Component view on the Products page, with a check mark icon column.

4.6.1.2 Enable Additional Content Server Instances

When you enable additional instances from a Content Server cluster whose Master
Server is already enabled in System Center Manager, it is not necessary to provide
the Content Server URL, and the name and password of a Content Server
administrative user. You can simply click Enable to add the Content Server instance
to System Center Manager.

When it attempts to enable the new instance, System Center Manager first analyzes
it and then attempts to bring it up to date (if necessary) by configuring it with the
patches, Updates, and language packs that are present on the Master Server. If it
finds potential problems during its analysis of the new Content Server instance,
System Center Manager pauses the enablement and displays a warning. Several
different types of warnings may appear.

Discrepancies between the Environments

System Center Manager may display a warning that, compared with the Master
Server, the Content Server instance that it is enabling has missing or additional
modules, additional or unknown patches or Updates, or custom language packs.
This is an indication that you should stop enabling the instance, investigate why
the two instances differ, and make changes to bring them into alignment.
Missing Packages
System Center Manager may inform you that your product requires one or more
updates before it can be enabled. For example, it may report that a package has
not been downloaded, or that it encountered an error during the download of a
required package. If you see this message, click Continue. How you proceed
after this depends on whether you operate in online mode or not.
Online mode
If you operate in online mode, System Center Manager displays the
Confirm download dialog box. Log on to My Support to download the
missing package. After the download has completed, you can attempt to
enable the Content Server instance again.
Offline mode
If you operate in offline mode, System Center Manager displays the Upload
missing packages dialog box. To continue, obtain the missing package and
add it to System Center Manager. After the dialog box displays The
package(s) have been successfully uploaded, you can click Continue to
proceed with enabling the new Content Server instance. For more

SYSCM240400-AGD-EN-01 Administration Guide 27

Chapter 4 Systems

information on obtaining packages in offline mode, see OpenText System

Center Manager - Administrator Online Help (SYSCM-H-AGD).

To enable an additional Content Server instance:

1. In the Products tab of the System Details view, do one of the following:

• Click Enable in the Inline Action Bar of the Content Server instance
that you want to enable.

• Select the check box beside the Content Server Instance that you want to
enable, and click Enable above the Product Component Instance listing.

2. On the Enable component instance ‘Content Server’ page, click Analyze.

System Center Manager analyzes the Content Server instance to determine if it
needs to be brought up to date with the Master Server. Click View details for
information on the results of the analysis. If System Center Manager finds issues
that require your attention, it requests that you take action to resolve the issue.
The action that you need to take depends on the warning that is displayed.

Discrepancies between the Environments

If System Center Manager detects a discrepancy between the two instances
that could prevent it from bringing the new instance up to date, it displays a
warning. You must resolve the discrepancy before you can enable the new
instance.

Problems with Updates, Patches, or Language Packs

If System Center Manager detects problems with any Updates, patches, or
Language Packs that it needs to apply to the new Content Server instance, it
displays a warning that a package has not been downloaded, that a package
is currently downloading, or that a package encountered an error during
download. You must correct the problem before the synchronization can
complete. Once you have corrected the problem, you may be able to
proceed to enable the instance, but in most cases, you need to restart the
enablement from the beginning.

If there are no issues that require your attention, click Next to proceed to the
Download page, where you can see a list of the required packages and their
Status

3. If there are no problems with the downloaded packages, click Next to proceed
to the Validate page.

4. System Center Manager performs a number of verifications. If they are not

successful, it does not proceed. You must resolve the underlying issue before
you can enable the new Content Server instance. Click View details to see the
results of the checks. If the prerequisite checks pass successfully, click Next to
proceed.

28 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 4.6. Enable and Disable Product Component Instances

5. The Update page displays the Content Server instances that will be updated on
the Instance tab and the packages to be applied on the Packages tab. When you
are ready to apply the Updates, click Install.

Tip: Language Packs that are installed on the Master Server are added to
the new Content Server instance when it is enabled, if they are not already
present.

System Center Manager applies the updates

To view the progress of the synchronization, open the Activities Overview
page. Under Running Activities, a Bring up to date activity appears. Click the

Details button for more information on the activity’s progress.

When the Content Server instance has been enabled, the Bring up to date
activity appears in the Other activities section of the Activities Overview, with

a status of Completed . A notification is generated with the message Bring

up to date complete.

6. Perform any additional required work on the new Content Server instance.
When it is ready, start the Content Server service and (if applicable) the Content
Server Admin service. Change the Startup Type of these services to Automatic,
if desired.

4.6.2 Disable a Product Component Instance

If you have a Product Component Instance on one of your Systems that you do not
want System Center Manager to update, you can disable that Product Component
Instance while leaving other Product Component Instances enabled. System Center
Manager does not make changes to disabled Product Component Instances. When
you use System Center Manager to update a Product Component, every active
Product Component Instance is updated in a single operation, but disabled Product
Component Instances are left untouched.

Important
All Content Server Instances must be enabled. Do not disable an instance of
Content Server in a Content Server cluster. For System Center Manager to
update the Content Server instances in a cluster, each one must be enabled. If a
single Content Server instance is disabled, System Center Manager cannot
update any of the instances in a Content Server cluster.

To Disable a Product Component Instance:

1. Open the System Details page of the System that runs the Product Component
Instance that you want to disable.

2. On the Products tab, disable the Product Component Instance in one of the
following ways:

SYSCM240400-AGD-EN-01 Administration Guide 29

Chapter 4 Systems

• click the Disable button on the Inline Action Bar of the Product
Component Instance.
• Select the check box beside the Product Component Instance and then click
Disable at the top of the Product Component Instance listing.

After you disable a Product Component Instance, it appears with a status of Not

enabled on the Products tab of the System Details page.

30 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

Chapter 5
Products, Components, and Instances

In System Center Manager, the words Product, Component, and Instance have
precise meanings.

Products, in System Center Manager, are families of OpenText applications that

System Center Manager is capable of configuring. Currently, System Center
Manager can configure the following Products:

• OpenText™ AppWorks Gateway

• OpenText™ Archive Center
• OpenText™ Content Server
• OpenText™ Directory Services
• OpenText™ Document Pipeline
• OpenText™ Intelligent Viewing

Products contain Components. Components are applications that belong to a Product

family. In most cases, a Component is configured independently of the other
Components within the Product family. In other words, a patch that you apply to
one Component does not affect any other Component.

A Product and a Component may have the same name. For example, Content Server
is a Product, but it is also a Component of the Content Server Product.

A Product Component that runs on a System is an Instance of a Component. A

Component Instance has specific characteristics, such as a Version and an Install
path. A System can run one or more Instances of a Component. For example, several
Instances of the Content Server Product Component may exist at different file
locations on a System. Strictly speaking, System Center Manager does not configure
Products or Product Components, it configures Product Component Instances.

Example 5-1: Systems, Products, Components, and Instances

Myserver.corporate.com is the name of a System that runs an Instance of

Archive Cache Server, which is a Component of the Archive Center Product.

SYSCM240400-AGD-EN-01 Administration Guide 31

Chapter 5 Products, Components, and Instances

5.1 The Products Page

The Products page contains information on Products that are installed on Systems:

• the Products and Components that System Center Manager can configure
• the Systems that run these Product Components
• the Updates and patches that System Center Manager can apply to the Product
Component Instances

Tip: The Products page does not display Product Installers that you have
downloaded from the Product Catalog. To view Product Installers that you
have downloaded and that you can use to install Products on Systems using an
Execution Plan, open the Product tab on the Downloads view of the Activities
page.

Each Product is listed on the left. If you expand a Product node, System Center
Manager displays the Product Components that belong to the Product. For example,
if you have enabled Archive Center on one of your registered Systems, Archive
Cache Server and Archive Monitoring Server appear when you expand Archive
Center.

For each Product, you can choose to view the Product Details view, Component
view, or Updates view. Each view presents different information.

Tip: Products, Components, and Instances must be discovered and enabled

before they appear on the Products page. Also, the Systems that run the

Product Component Instances must be online with a status of Running . If

you do not see the Products that you are expecting on the Products page,
review the information at “Discover Product Component Instances” on page 24
and “Enable and Disable Product Component Instances” on page 25.

Example 5-2: Products on the Products Page

MyHost123.corporate.com is a System that runs Content Server and Document

Pipeline. When you first register MyHost123.corporate.com in System Center
Manager you enable Content Server, because you intend to update it using
System Center Manager but you do not enable Document Pipeline because you
intend to continue updating it manually. No other System in your System
Center Manager deployment is running Document Pipeline.

The Content Server Product and its Product Components appear on the
Products page, but Document Pipeline does not.

32 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 5.1. The Products Page

5.1.1 The Products Page: Updates View

The Updates view of the Products page shows you Updates (patches, hotfixes and
so on) for Products managed by System Center Manager. The Updates on this page
may have a status of Available for download

SYSCM240400-AGD-EN-01 Administration Guide 33

Chapter 5 Products, Components, and Instances

34 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 5.1. The Products Page

(from OpenText My Support) or Previously downloaded . Downloaded

Updates are ready for System Center Manager to install on your managed Systems.

Available Updates are listed by Product. The listing is refreshed daily. To perform
an immediate check for newly available Updates, click Check for Updates on the
Manifest view of the Settings page. (See “Update the System Center Manager
Manifest File” on page 47.)

To view additional information on any Update, open the Details view, using one of
the following methods:

•
Click the Details button on the Update’s Inline Action Bar.
• On the Patches or Languages tab, select the check box of the Update, and then
click Details at the top of the Updates list.

To download Updates, select them and click Download <#> item(s). For more
information, see “Obtain Updates in Online Mode” on page 49.

To export a list of download links for the Updates that you have selected, click
Export metadata. You can choose to obtain the list as a CSV comma-separated
values file or as a Web page. For more information, see “Obtain Updates in Offline
Mode” on page 49.

Tip: You can also perform the Export metadata operation on the Review step
of the <Product Component> Deployment page.

5.1.1.1 The Update Details page

To view information on an Update, click the Details button on the Update’s

Inline Action Bar, either on the Product Details or Updates view.

The Update Details page provides basic information on Updates that are handled by
System Center Manager. It includes some or all of the following information:

Name
The name of the Update.

Description
A brief description of the Update. The description may include the change made
by the Update, the issue resolved by the Update, and an issue number from the
OpenText issue tracking system.

File Name
The name of the Update file.

Size
The size of the Update.

SYSCM240400-AGD-EN-01 Administration Guide 35

Chapter 5 Products, Components, and Instances

Impacts
A description of the effect that the Update has on your Product Component
deployment
Requires
Prerequisites for the Update.
Deprecated update
If the listed Product version (or later) is running on the System, the Update is
deprecated. If None, the Update is suitable for use on any platform listed in the
Requires field.
Public
If Yes, the Update is publicly available.
Retired
If Yes, the Update has been retired.
Modules
The module that the Update applies to. If empty or None, the Update applies to
the base Product Component.
Supersedes
If an Update appears in this field, the current Update replaces it. If the
superseded Update is present on your System, it is automatically removed when
you install the current Update.
Superseded by
If an Update appears in this field, the current Update is replaced by it.
Normally, you should download and install the Update that appears in this field
instead of using the current Update.

Tip: If you attempt to download or install a superseded Update, System

Center Manager prompts you to download or install the superseding
Update instead.
Dependents
Updates that are required to be installed with the current Update. The current
Update is not complete unless the dependent Updates are also installed.
Release Date
The date that the Update was officially released.

36 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 5.1. The Products Page

5.1.2 The Products Page: Product View

The Details view of the Products page displays information on Pending and
Installed Updates for a given Product.

To see the Product Details view, click a Product under Installed Products on the
left.

Tip: If the There are downloaded patches to be installed icon appears

beside the Product below Installed Products, it indicates that downloaded
Updates are available to be applied for that Product.

The Product Details view presents information on two tabs:

Pending
The Pending tab shows Updates that you have downloaded. Updates in this
view are ready to install. Several operations are possible on the Pending tab:
Install Updates
To install Updates, select one or more Updates, and then click Next. For
more information, see “Apply Updates” on page 50
Remove Updates
To remove an Update from System Center Manager (if you know that you
will never want to install it, for example), do one of the following:

•
Click the Delete button in the Update’s Inline Action Bar.
• Select the check box beside the Update and then click Delete at the top of
the Update list.

View Update Details

To view information on an Update, do one of the following:

•
Click the Details button in the Update’s Inline Action Bar.
• Select the check box beside the Update and then click Details at the top
of the Update list.

Installed
The Installed tab shows Updates that you have downloaded and applied to one
or more Product instances, and the status of each Update.

SYSCM240400-AGD-EN-01 Administration Guide 37

Chapter 5 Products, Components, and Instances

5.1.3 The Products Page: Component View

The Component view of the Products page displays the Systems that run Instances
of a given Component.

To see the Component view, expand a Product under Installed Products on the left,
and then click one of its Components.

Tip: Unique icons identify Products and Components:

This icon represents Products, but if there are Updates available for the

product, you see this icon instead: .

This icon represents Product Components.

The Component view lists each System that runs the Component that you have
selected, and shows the Install path, Version, and Platform of each Instance of the
Component. It also shows the System’s Agent status and, if applicable, whether a
System is the Master System or not.

Click the Details button in the Inline Action Bar of any Component instance to
open its Component Instance Details page.

5.1.3.1 The Component Instance Details Page

The Component Instance Details page displays detailed information about an
Instance of a Product Component on a System.

The Component Instance Details page has two tabs: Overview and Modules:

• The Overview tab displays information that is required by System Center

Manager to uniquely identify a Component Instance and to apply Updates to it.
• The Modules tab provides information on the optional modules installed on a
Product Component Instance.
Module information appears only when it is applicable. Modules information
may appear for an instance of Content Server, for example, but would not for an
instance of Document Pipeline.

38 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 5.1. The Products Page

5.1.3.2 The Content Server Product Component View

The Product Component view for Content Server contains features that are unique
to that Product Component:

Update Analysis
Update analysis provides information on the changes that a Content Server
Update will make to your system. For information on running Update analysis,
see “Update Analysis (for Content Server Updates)” on page 57

Resynchronization
To ensure that the information that System Center Manager has about your
Content Server Product Component instances is up to date and accurate, click
Resynchronization. For information on resynchronizing your Content Server
instances, see “Resynchronize a Content Server Product Component instance”
on page 58

Administration Settings
Content Server allows you to export all or some of the existing Administration
Settings from one Content Server instance and apply them to a different Content
Server instance. You can use System Center Manager to apply an
Administration Settings file to the Content Server instances that it manages. See
“Apply an Administration Settings file to Content Server” on page 39.

Tip: For information on exporting and importing Content Server

Administration Settings files, see OpenText Content Management Admin Help
- System Administration (LLESWBA-H-AGD).

5.1.3.2.1 Apply an Administration Settings file to Content Server

On the Content Server Product Component View, you can apply an Administration
Settings file to the Content Server instances that are managed by System Center
Manager.

Caution
Content Server Administration Settings files can contain two types of
settings: settings that need only be applied once to affect every instance in
the cluster and settings that need to be applied to each instance separately.
System Center Manager does not distinguish between these two types of
setting. It is important that you understand which kind of settings you are
applying, so that you can apply them properly.

You can apply the Administrations Settings file to one or more instances of the
Content Server Product Component. When you select the instances, note whether a
web address appears in the URL column. If not, you will be prompted to provide the
URL. Normally, the URL appears only for the Content Server Primary system, and
you must provide it for any other instances in the cluster.

SYSCM240400-AGD-EN-01 Administration Guide 39

Chapter 5 Products, Components, and Instances

Information on any Administration Settings operations that are running or have

been run is available on the Activities page and on the Audit view of the Settings
page.

Note: The application of an Administration Settings file may require Content

Server to restart. If so, System Center Manager will restart Content Server after
it has applied the Administration Settings file.

To apply an Administration Settings file to Content Server

1. On the Product Component View of the Products page, select a Content Server
Product Component.

2. On the Content Server Product Component view, select one or more instances
of Content Server.

Note: If you select an instance that has no data in the URL column, the
Validate instance URL dialog box will appear and you will be prompted
to provide logon information for the instance. To provide this information

beforehand, click the Set instance URL button in the Inline Action
Bar of the instance.

3. Click Administration Settings on the Action Bar. (If you select a single
instance, you can click Administration Settings on the instance’s Inline Action
Bar.)

4. The Administration Settings for Content Server <##.#.#> view opens. Click
Browse on the Pre-defined administration settings file box. Browse to an
Administration Settings file and select it.

5. Click Upload. The Sign in dialog box appears. In the URL box, it displays the
address of your Content Server deployment. Enter the user name and password
of a Content Server administrator. Select I have read the statement above and
wish to proceed and then click Authenticate.

6. A message informs you that the Administration Settings activity was started.
Then a second message informs you: Administration Settings activity is
currently running, this page will be temporarily disabled until the activity is
complete. View details.
Click View details to open the Activities Overview page, where you can view
the Apply Administration Settings activity.

Tip: When the job completes successfully, the Status appears as

Completed on the Activities Overview page. Click Details in the

Inline Action Bar to view additional information on the Apply
Administration Settings activity.

40 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 5.1. The Products Page

5.1.4 The Products Page: Search Patches View

For supported Products, System Center Manager handles the replacement of
superseded patches and the removal of retired patches. To simplify patch
management, System Center Manager shows you only the patches that are relevant
for your deployment. However, at times you may wish to obtain information on a
patch that cannot be deployed on your system in its current configuration. The
Search Patches page allows you to search all of the patches that are available for
every version of your product, and view information on any of them (including
superseded and retired patches).

The information on the Search Patches page appears in a table. The Status of each

patch appears as either Retired or Available for Download

SYSCM240400-AGD-EN-01 Administration Guide 41

Chapter 5 Products, Components, and Instances

42 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 5.2. Logs Packages

. For an explanation of the information in the other columns, see “The Update
Details page” on page 35.

To show or hide the columns on the page, click the Column Settings button.

To assist you in finding patches, you can order the Name column and filter all of the
columns except the Status column.

•
To order the Name column, click the Name - click to Sort ascending button.
Click again to sort the Names in descending order.
•
To search any column, click the Search <Column_Name> button.

To save information on any patch that you select, click the Export Metadata
button on the item’s Inline Action Bar to save the information. You can export the
information as a CSV or HTML file. To save information on multiple patches, select the
patches and click Export Metadata on the Action Bar.

5.2 Logs Packages

System Center Manager is capable of generating Logs Packages for the Products that
it manages. A Logs Package is a structured collection of existing application logs that
are packaged in a ZIP file. It is obtained from Product Component Instances running
the application in question.

Note: The Logs Package feature collects existing logs. It does not manage logs
or set log levels. If you have been advised by OpenText Customer Support to
set a specific log level or repeat a certain operation, do this within the managed
application before you use System Center Manager to generate a Logs Package.

Many applications managed by System Center Manager consist of multiple Product

Component Instances in a cluster. When you generate a Logs Package for a clustered
application, you can opt to collect logs from one instance, some instances, or every
instance in the cluster. You can also specify the type of supported log files to collect.
Many applications generate a variety of log files. System Center Manager allows you
to package only those log files that are of interest to you.

Logs Packages can take up a significant amount of disk space, so it is important to

ensure that disk space is available. Before it creates a Logs Package, System Center
Manager checks the available disk space. On each System, it verifies that available
disk space is equal to at least twice the size of the logs to be collected. On the System
Center Manager host computer, it verifies that available disk space is equal to at
least twice the size of the total log files to be collected from every System.

System Center Manager keeps up to three Logs Packages for each Product Version.
If you attempt to generate a fourth Logs Package for a given Product Version,
System Center Manager will offer to delete the oldest existing Logs Package (unless

SYSCM240400-AGD-EN-01 Administration Guide 43

Chapter 5 Products, Components, and Instances

it is currently queued or running). If you prefer to delete a different Logs Package,

you can do so on the Download Logs Package page.

When a Logs Package creation request is submitted, the status of the job goes from

Queued to Running to Completed . If you have requested that System

Center Manager generate a Logs Package containing logs from multiple Systems and
Product Component Instances, the status will remain queued until every Product
Component Instance is available.

You can monitor the creation of a Logs Package on the Activities Overview. To view

details on a Package product logs job, click the Details button . General
information is available on the General and Summary tabs. Detailed information for
each selected System and Product Component Instance is available on the Systems
tab. Click View Details to see information for a specific Product Component
Instance. Events are also written to the Audit log for each Logs Package creation,
download, and deletion.

You can download and delete completed Logs Packages on the Download Logs
Packages page.

A Logs Package has a standard structure that helps anyone who examines the log
files to quickly understand what it contains:

• The name of the file is the name of the Logs Package plus the date and time that
it was generated plus logs.zip. For example, a Logs Package called Critical
Logs, generated on August 25, 2022 at 12:31:44, has the name Critical_Logs_
2022-08-25-12-31-44_logs.zip

• The Logs Package ZIP file contains a ZIP file for each System that provided logs.
• Each System ZIP file contains a ZIP file for each Component Instance that
provided logs.
• Each Component Instance ZIP file contains the logs that you requested when you
generated the Logs Package.

Two types of manifest file also aid in understanding the contents of the Logs
Package.

• A MANIFEST.json file is included with each System ZIP file. It provides

information about the System, the logs provided from that System, and the
Product whose logs are included in the Logs Package.
• A MANIFEST file is included with each Component Instance ZIP file. It lists the
name and location of each included log file.

44 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 5.2. Logs Packages

5.2.1 Create a Logs Package

To create a Logs Package for a Product managed by System Center Manager, start
on the Component page for that Product.

To create a Logs Package:

1. On the Component view of the Products page, do either of the following:

• On a Product Component’s Inline Actions Bar, click the Create a Logs

Package button .
• Select the Product Component, and click Create a Logs Package at the top of
the Component list.

2. The Create a Logs Package page opens. It displays the supported log file types
as options and lists the Instances of the Product Component. Configure your
Logs Package as follows:

a. Enter a Logs Package name in the Package name box.

b. Select the log types that you would like to include in the Logs Package.
c. Select the Instances whose logs you would like to include in the Logs
Package.

3. Click Start to initiate the Logs Package creation, and click Yes on the
confirmation dialog box.

4. A dialog box requesting additional information may appear for some Products.
Log on as an administrative user, if you are prompted to. You may also need to
verify or correct the URL of the Product. Once you have entered the required
information, click Authenticate.

5. The Download Logs Packages page opens. When the status of the Logs Package

is Completed , the Logs Package is ready to download.

5.2.2 Download a Logs Package

To download a Logs Package, start on the Product Component page for that
Product.

To download a Logs Package:

1. On the Component view of the Products page, do either of the following:

• On a Product Component’s Inline Actions Bar, click the Download Logs

Packages button .
• Select the Product Component, and click Download Logs Packages at the
top of the Component list.

SYSCM240400-AGD-EN-01 Administration Guide 45

Chapter 5 Products, Components, and Instances

2. The Download Logs Packages page opens. It lists any existing Logs Packages
that have been previously generated for the selected Product Component. To

download a Logs Package, click the Download icon . Your browser

downloads the Logs Package.

5.2.3 Delete a Logs Package

To delete a Logs Package, start on the Product Component page for that Product.

To delete a Logs Package:

1. On the Component view of the Products page, do either of the following:

• On a Product Component’s Inline Actions Bar, click the Download Logs

Packages button .
• Select the Product Component, and click Download Logs Packages at the
top of the Component list.

2. The Download Logs Packages page opens. It lists any existing Logs Packages
that have been previously generated for the selected Product Component. To
delete a Logs Package, do either of the following:

• On the Inline Actions Bar of the Logs Package that you want to delete, click

Delete .
• Select one or more Logs Packages and click Delete at the top of the Logs
Packages listing.

46 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

Chapter 6
Obtain and Apply Updates

System Center Manager automates each step of the software patching process. Using
an up-to-date copy of its manifest file, it displays the Updates that are available on
the Updates view of the Products page. It automatically downloads any Updates
that you select. When you are ready to apply the downloaded Updates, System
Center Manager deploys them on every Product Component Instance in your
Solution Environment.

6.1 Update the System Center Manager Manifest File

System Center Manager uses a manifest file that provides information on the
Updates that are available for the Product Components under its control. If you
operate in online mode, the manifest file is updated automatically. If you operate in
offline mode, you must update the manifest file manually.

Tip: If the System Center Manager manifest becomes corrupt or unusable for
any reason, you can purge it and import a fresh copy. See “Manifest Repair”
on page 123.

Update the Manifest File in Online Mode

In online mode, System Center Manager updates its manifest file once a day. On
the Settings page Manifest view, you can view the time of the last update and
click Check for updates to perform an immediate update.
Update the Manifest File in Offline Mode
In offline mode, System Center Manager cannot update its manifest file
automatically. You need to download the manifest file using a computer that is
connected to the Internet, and then upload it to System Center Manager. For
instructions, see “Settings: Manifest” on page 122.

6.2 Download Updates

Available Updates (patches, hotfixes and so on) for Products that are managed by
System Center Manager appear on the Updates view of any Product on the Products
page.

SYSCM240400-AGD-EN-01 Administration Guide 47

Chapter 6 Obtain and Apply Updates

Updates with a status of Available for download

48 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 6.2. Download Updates

are ready to download. If you operate in online mode, you can download Updates
directly from System Center Manager. In offline mode, you must download Updates
on an Internet-connected computer and then add them to System Center Manager.

A successfully downloaded Update appears on the Updates view of the Products

page with a status of Previously downloaded .

6.2.1 Obtain Updates in Online Mode

To download one or more Updates, select them in the Updates list, click Download
<#> items, and log on to My Support when the Confirm download dialog box
appears.

To view the progress of active downloads, click the Download button that
appears at the top of any System Center Manager page, or open “The Activities
Page: Downloads View” on page 85.

6.2.2 Obtain Updates in Offline Mode

In offline mode, System Center Manager cannot download Updates directly. You
need to download Updates using a computer that is connected to the Internet, and
then upload them into System Center Manager.

To download Updates in offline mode:

1. Obtain the Updates that you need in one of the following manners:

• Use System Center Manager on an Internet-connected computer

On a computer that is connected to the Internet, open the Updates view of

the Products page. Click the Download button beside any Update that
you want to obtain. Log on to OpenText My Support if you are prompted to.
Your browser downloads the Update. Repeat this step for every Update that
you want to obtain.

• Use a download list on an Internet-connected computer

On the Updates view of the Products page, select the Updates that you want
to download and click Export Metadata.
Select either CSV (comma-separated values) file to obtain a comma-
separated values file or Web page to obtain an HTML file. Both files contain
the Name, Description, File Name, and Download URL of each Update that
you have selected.
Open the exported list on a computer that is connected to the Internet, and
use the URLs to download the Updates that you need. Log on to OpenText
My Support if you are prompted to.

SYSCM240400-AGD-EN-01 Administration Guide 49

Chapter 6 Obtain and Apply Updates

2. After you have obtained the Updates, click the Upload button that appears
at the top of any of the Product page views.
3. Drag the Updates onto the Upload page or click Add files, browse to the
location of the Updates, and select them.
4. The Updates now appear on the Upload dialog box with a status of Pending. To
upload them to System Center Manager, click Continue.
5. After you have uploaded the files, click Close to exit the Upload page.

6.2.3 Download Content Server Quarterly Updates

The Content Server Updates view presents information on two tabs:

Patches
Content Server patches work with specific Content Server quarterly Updates.
On the Patches tab, you can select patches that apply to the Update that you are
downloading. The patches that you select are downloaded along with the
quarterly Update. You can install them when you install the quarterly Update,
or afterwards if you prefer.
Languages
The Languages tab allows you to select Language Packs for installation on your
Content Server deployment. If you operate a multilingual installation of Content
Server, System Center Manager automatically selects any languages that you
have already installed. You cannot disable these selections.
To install a new interface language for Content Server, select it so that it is
included with the download of the quarterly Update. Any Language Pack that
you download with a quarterly Update will be installed when System Center
Manager installs the Update.

6.3 Apply Updates

When you install an Update, System Center Manager applies it to every Instance of
the applicable Product Component. To obtain information on the Update
installation, you can view its progress on the Activities page.

Tip: The following instructions demonstrate how to apply Updates that you
select manually from the System Center Manager user interface.

You can also apply Updates by using the Synchronize button that is
available on the Solutions view of the Settings page. This function analyzes
the Updates that are present on a Product in a source Environment, compares
them to those that are present on the same Product in a target Environment,
and then applies any missing Updates to the Product in the target
Environment. The result is that the Product in the target Environment has the
same Updates as the Product in the source Environment.

50 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 6.3. Apply Updates

Use the Synchronize function to automate the selection of Updates and

decrease the possibility of human error in the Update process. For more
information on synchronizing Solution Environments, see “Synchronize
Solution Environments” on page 116.

To apply Updates to Product Components:

1. On the Details view of any Product on the Products page, Updates that are
ready to be applied appear on the Pending tab. Select the Updates that you
wish to install, and then click Next.

2. For certain Product Updates, the Release Notes page appears. It displays any
critical issues that are documented in the product Release Notes, along with a
link to information on each issue and a link to the latest product Release Notes.
If there are no critical release notes to review, the page does not display any
issues, but it does provide a link to the product Release Notes.
Review each of the critical issues to ensure that you have addressed any

potential problems. To focus on issues of interest, click the Filter button and
enter text in the Filter By box. When you have finished reviewing the critical
release notes, select the I acknowledge that I have read the critical release
notes and have executed the required actions check box. Once you do this, the
Next button becomes available. Click Next to proceed to the Review page.

3. The Review page lists the Updates that System Center Manager will apply. You
can click Export metadata to obtain a copy of this list as a comma-separated
values (CSV) file or a webpage. Click Next to proceed with the installation.

4. On the Questions page, System Center Manager prompts you to provide

information that it requires to apply the update. For example, you may be
prompted to log on to one or more Systems. Provide any required information,
and then click Next.

5. The Validate page shows the results of any prerequisite checks that System
Center Manager performs to ensure that it can apply the Updates successfully.
To view information on the prerequisite checks, click View details.

6. Click Next to apply the Updates. On the Deploy Update dialog box, click
Continue to confirm that you want to proceed.

7. You are returned to the Product Details view. A message informs you that An
activity is currently running, this page will be temporarily disabled until the
activity is complete. This message remains in place until the Update has been
installed on all of the Product Component Instances. An Activity running icon

also appears at the top of the page.

Click View details or click the Activity running icon to display information on
the progress of the Update application.

SYSCM240400-AGD-EN-01 Administration Guide 51

Chapter 6 Obtain and Apply Updates

8. When the installation of the Update finishes, the Patch installation activity
appears in the Other tab of the Activities Overview. A status of Completed

indicates that the Update application was successful.

6.3.1 Apply Updates to Content Server

System Center Manager can apply the following Updates to Content Server:

• Content Server patches

• Content Server quarterly Updates
• Content Server Language Packs

Tip: System Center Manager can also install Content Server modules, using an
Execution Plan. See “Execution Plans, Steps, and Variables“ on page 63.

In most respects, the process of applying Updates to Content Server is similar to the
process of applying Updates to other Products, but there are a few differences.

6.3.1.1 Verify Prerequisites

Before System Center Manager applies an Update to your Content Server
environment, it verifies conditions on the Content Server instances to ensure that it
can apply the Update successfully. If there are no problems, you can proceed with
the Update. If System Center Manager indicates that Prerequisite checks failed,
click View Details for information on the warnings and errors. Normally, you must
resolve the underlying problems before you can proceed.

Errors

If the Prerequisite checks dialog box displays a status of Error , correct the
underlying problem. If you correct the problem without closing the Validate
page of the Content Server Deployment, you can click Retry to have System
Center Manager run the prerequisite checks again.
For example, if the System Center Agent is unable to write to the Content Server
application folder on a Content Server instance, System Center Manager
displays an error for that instance. You will be unable to apply the Update until
you correct the underlying problem (for example, fix the permissions on the
Content Server application folder) so that the System Center Agent can write to
it.
Warnings

If the Prerequisite checks dialog box displays a status of Warning , System

Center Manager is informing you that there is a problem that requires your
attention. In the majority of cases, you should not proceed until you have
resolved the underlying problem.
For example, if you use a custom language pack for a language that is not
officially supported by OpenText in your Content Server environment, the

52 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 6.3. Apply Updates

Prerequisite checks dialog box will show a status of Warning for the
Language Pack check. To proceed despite the warning, click Continue. It will be
your responsibility to ensure that your custom language pack is applied to the
Systems in your Content Server cluster after System Center Manager applies the
Update.

Checks performed by System Center Manager can result in the following messages:

An error has occurred while attempting to authenticate. Please check the logs for
more details.
This message indicates that System Center Manager was unable to log on to
Content Server using the credentials that you have provided. If you have
provided an incorrect password, this message appears.
This message also appears if Content Server is deployed on a Microsoft IIS site
that does not have Anonymous Authentication enabled. System Center Manager
requires Anonymous Authentication to connect to Content Server using the
REST API.
The following system(s) are not managed by System Center
This message indicates that the listed instance of Content Server has not been
enabled in System Center Manager. The nature of the listed instance dictates the
step you should take.
If the listed instance is an instance in your Content Server cluster, you should
register the System (if necessary) and enable the Content Server Component
Instance. After you have done that, System Center Manager should be able to
apply an Update to your Content Server Environment.
If it is not an actual instance in your Content Server cluster, System Center
Manager may be reporting obsolete information that remains in your Content
Server database from a previous installation. If so, click Unregister Systems, and
the information will be removed.

Caution
If you mistakenly unregister a real Content Server instance from your
cluster, System Center Manager will apply Updates to your cluster, but
not to the unregistered instance. This will result in your Content Server
cluster having instances with different patches on them. To correct this
situation:
1. Stop the Content Server service on the instance, ensure that the
instance is running the same quarterly Update and patches as the
rest of the cluster by manually applying the matching quarterly
Update, copying in any missing patches, and removing any patches
that no longer belong in place. Then restart the Content Server
service.
2. Restart the Content Server service to make the System and
Component Instance re-appear in System Center Manager. Re-
register the System and re-enable the instance.

SYSCM240400-AGD-EN-01 Administration Guide 53

Chapter 6 Obtain and Apply Updates

An Admin server is unavailable or a host name is incorrect

This message indicates one of the following:

• An Admin server is unavailable. If that is the case, ensure that the Admin
server is started and take any additional steps that are necessary to make it
available. Then restart the Install Update procedure.
• An Admin server in your Content Server Environment has a Host Name of
localhost or 127.0.0.1. If that is the case, ensure that the Host Name box on
the Admin server’s General properties page has a machine name or,
preferably, a fully qualified domain name in it.

The following system(s) are not registered in the same clustered environment
This message indicates one of the following:

• System Center Manager has discovered the Component Instance, but you
have not enabled it. If it is actually part of your Content Server cluster, you
should enable it and proceed normally.
• The Component Instance is not connected to the same Content Server
database as the other instances in the Content Server Environment that you
are updating. You may need to disable the Component Instance or assign it
to a different Content Server Solution Environment.

6.3.1.2 Apply Updates to Content Server

Once you have successfully verified the update prerequisites, you can proceed to
apply updates.

To apply Updates to Content Server:

1. On the Deploy Updates view of the Content Server Products page, the Update
menu displays the current Update level of your Content Server Environment. If
you have downloaded other Updates, you can select a newer quarterly Update.
Select a quarterly Update that you wish to install from the Update menu, or
leave the Update unchanged to install patches for your current version of
Content Server.

Tip: When you select a different Current update, the list of Downloaded
patches refreshes to display the patches that are compatible with your
selected Update.

2. Select the patches that you want to install, and then click Next.

3. The Download page appears. If you are applying a quarterly Update, it lists any
patches that are currently installed and that you need to reapply when you
apply the new quarterly Update. (This may be necessary for certain patches that
are compatible with both your current Update and the Update that you are
applying.) You can skip the reapplication of the patches by selecting the I want

54 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 6.3. Apply Updates

to skip reapplying patches check box, but OpenText recommends that you do
not do this.
To obtain the patches that need to be reapplied, click Download <#> items and
log on to OpenText My Support when you are prompted to. (If you do not
operate in online mode, click the patch’s URL on an internet-connected
computer, and then use the Upload button to add it to System Center Manager.)
Once the download completes, click Next.
4. If you are applying a quarterly Update to Content Server, the Release Notes
page appears. It displays any critical issues that are documented in the product
Release Notes, along with a link to information on each issue and a link to the
latest OpenText Content Management Release Notes. If there are no critical
release notes to review, the page does not display any issues, but it does
provide a link to the OpenText Content Management Release Notes.
Review each of the critical issues to ensure that you have addressed any

potential problems. To focus on issues of interest, click the Filter button and
enter text in the Filter By box. When you have finished reviewing the critical
release notes, select the I acknowledge that I have read the critical release
notes and have executed the required actions check box. Once you do this, the
Next button becomes available. Click Next to proceed to the Review page.
5. The Review page lists the Update, patches, and language packs that System
Center Manager will apply. You can click Export metadata to obtain a copy of
this list as a commas-separated values (CSV) file or a webpage. Click Next to
proceed with the installation.

Tip: Any compatible Language Packs that you have downloaded are
installed automatically when you install a quarterly Update. You cannot
select or omit specific Language Packs when you install a quarterly
Update.
6. On the Questions page, System Center Manager prompts you to log on to
Content Server as an administrator and to provide any other information that it
requires to apply the Update. Log on as an administrator that is capable of
applying the Update. (For a Content Server quarterly Update, log on as Admin or
sys_support.) Provide any required information, and then click Next.

7. The Validate page shows the results of any prerequisite checks that System
Center Manager performs to ensure that it can apply the Updates successfully.
If any of the checks are not successful, it cannot proceed. You must resolve the
underlying issue before you can use System Center Manager to apply Updates
to your Content Server environment. To view information on the prerequisite
checks, click View details.
8. If the prerequisite check finds no problems, click Next to apply the Updates. On
the Deploy Update dialog box, click Continue to confirm that you want to
proceed.
9. You are returned to the Details view of the Content Server Products page. A
message informs you that An activity is currently running, this page will be

SYSCM240400-AGD-EN-01 Administration Guide 55

Chapter 6 Obtain and Apply Updates

temporarily disabled until the activity is complete. This message remains in

place until the Update has been installed on all of the Product Component

Instances. An Activity running icon also appears at the top of the page.
Click View details or click the Activity running icon to display information on
the progress of the Update application.

10. When the installation of the Update finishes, the Patch installation activity
appears in the Other tab of the Activities Overview. A status of Completed

indicates that the Update application was successful.

6.3.2 Roll Back a Content Server Update Deployment

If System Center Manager encounters an unrecoverable error while it is deploying a
Content Server patch, Update or language pack, the activity appears on the Other

tab of the Activities Overview with a status of Complete with Errors . To learn

more about the nature of the error, click the Details button in the Inline Action
Bar of the Activity.

In certain cases, a Software rollback button appears beside the failed update
installation. For a Content Server quarterly Update, this may occur if System Center
Manager deploys the Update files successfully, but cannot complete the database
upgrade. (If System Center Manager cannot complete the file updates on one or
more instances of Content Server, it rolls those instances back automatically.)

To roll back a deployment:

1. In the Other tab of the Activities Overview, click the Software rollback button
beside the failed update installation.

2. The Performing Software Rollback dialog box appears and advises you that a
software rollback only restores changes made by the current deployment and
does not restore your database.

Important
If the deployment made changes to your database, file store, or search
index, you must roll back these changes by restoring a backup. System
Center Manager does not do this.

To proceed with the software rollback, click Yes.

3. The Software rollback activity appears in the Running tab of the Activities
Overview. When rollback is complete, the Software rollback activity appears in

the Other tab of the Activities Overview with a status of Completed .

56 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 6.4. Update Analysis (for Content Server Updates)

Important
If you need to restore a database, file store, or search index backup, do not
start the Content Server services until the backup has been restored.

6.4 Update Analysis (for Content Server Updates)

Content Server Update Analysis gives you insight into the changes that a Content
Server Update will make to your system. By using Update Analysis, you can
determine if any of the files in your Content Server deployment need to be
preserved or removed before you apply a Content Server Update.

6.4.1 Running Update Analysis

Perform the following steps to generate an Update Analysis report.

To generate an Update Analysis report:

1. On the Content Server Product Component view, click Update Analysis.

2. Select a Target Update, and select one or more Content Server Instances.

3. Click Analyze, and in the Update analysis confirmation dialog box, click Yes to
proceed.

4. System Center Manager displays Analyzing an instance. Please wait.

5. When the analysis is complete, click View report beside any Component
instance to see the Update analysis delta report.

6.4.2 Interpreting the Content Server Update Delta Report

The Update analysis delta report provides information on the files that will be
replaced by the Content Server Update indicated in the Overview section of the
report. (It is the Update that you selected in “Running Update Analysis”
on page 57.)

The Summary section of the report provides general information on your Content
Server system. It also lists patches that you should remove before you apply the
Content Server Update.

Tip: You can run Update Analysis at any time to check whether you have
deprecated patches deployed on your Content Server system.

In the Update analysis delta report, each file is categorized as NEW, VERIFIED, or
DIFFERENT.

NEW
NEW files are files that the Update will add to Content Server. They do not
currently exist in your Content Server installation.

SYSCM240400-AGD-EN-01 Administration Guide 57

Chapter 6 Obtain and Apply Updates

VERIFIED
VERIFIED files are files that the Update will replace. They have a hash value that
matches one in your Cluster Management manifest file, which indicates that the
file has not been modified since its installation.

DIFFERENT
DIFFERENT files are files that the Update will replace, but whose hash value does
not match the one in your Cluster Management manifest file. This indicates that
the file is not the same as when it was first installed. It may have been
customized by the System Administrator, by a third-party integration, or by
some other means. A DIFFERENT file is not the file that the Update expects to
replace, and may contain modifications that you wish to preserve. OpenText
recommends that you back up DIFFERENT files before you apply an Update.

Update Analysis also provides a list of patches that you should remove from
Content Server before you apply the Update.

Important
The list provided by Update Analysis is as complete as possible, but you
should also review the list of patches to be removed that appears in the
Content Server Release Notes. If additional removable patches are identified
after the release of the Update, the Release Notes will include patches that are
not listed in the Update Analysis Delta Report.

6.5 Resynchronize a Content Server Product

Component instance
The Resynchronization button appears on the Content Server Product Component
view. You can use it to ensure that System Center Manager has up-to-date
information for the Content Server instances in your cluster.

Updates, patches, and language packs that have been applied to your Content
Server instances by System Center Manager are accurately displayed in its interface,
but Updates and modules that you have installed manually are not tracked by
System Center Manager. To update the information that System Center Manager has
for a Content Server Product Component instance, select one or more Content Server
instances and then click Resynchronization. On the Product Component
Resysnchronization page, select one or more instances and then click
Resynchronize.

You may be prompted to obtain patches during the synchronization. If you are, click
Download and log on to OpenText My Support when you are prompted to. (If you
do not operate in online mode, click the patch’s URL on an internet-connected
computer, and then use the Upload button to add it to System Center Manager.) In
some cases, you may be prompted to obtain patches that are already installed, but
need to be reapplied during the synchronization. In such cases, you can select the I
want to skip reapplying patches check box if you do not want to reapply the
patches. In general, OpenText recommends that you do not do this.

58 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

Chapter 7
The Product Catalog

The System Center Manager Product Catalog is your first stop for researching and
obtaining OpenText software. In the Product Catalog, you can view product
documentation, review software requirements and dependencies, and download
installers for OpenText software applications. You can use an Execution Plan to
install a Product Component once you have downloaded the installer.

Note: The Product Catalog is not available in all versions of System Center
Manager.

The Catalog Overview

By default, the Catalog page opens to the Catalog overview, where a tree view
shows Products on the left and the Catalog - Latest releases view shows the latest
OpenText product releases. To hide or expose the tree view, click the Show tree

button . To filter the list of products in the tree view, click the Filter button
and enter text in the Filter by box.

To open the Catalog - Product details view for any product on the Catalog - Latest
releases view, click the Details button on its Inline Actions Bar or click anywhere
on the entry for that product.

The Catalog - Product details View

The Catalog - Product details view provides detailed information on a specific
version of an OpenText Product. To open a Catalog - Product details view, expand a
Product on the tree view and click a Product Component.

The Catalog - Product details view has an Overview tab and, depending on the
release, additional tabs.

Overview

The Overview section shows the name, version, and release date for the Product
version and provides links to its documentation and release notes. It provides a
Download button that you can use to download the Product version’s installer to
System Center Manager. When you download a Product version, all of the OpenText
Components of that Product are also downloaded. (Third-party products are not
downloaded.)

Additional Tabs

Additional tabs provide information on OpenText and third-party applications that

are required for use with the Product version. It may also provide information on

SYSCM240400-AGD-EN-01 Administration Guide 59

Chapter 7 The Product Catalog

applications that are compatible with the Product version. The tabs that appear in
the tabbed interface vary by Product version, but generally include the following
tabs:

Operating System
The Operating System tab lists the name, manufacturer and version of the
operating systems that the Product version supports.
Web Server
The Web Server tab lists the name, manufacturer, and version of the web
servers that the Product version supports.
Database
The Database tab lists the name, manufacturer and version of the database
servers that the Product version supports.
Required Products
The Required Products tab lists information on additional software products
that the Product version requires for normal operation.

Example: OpenText™ Classifications 16 requires OpenText™ Content Server. Content

Server 16 appears as a required Product version on its Required Products tab.

7.1 Browse and Search for Product Versions

If the Product version that you are looking for does not appear on the Catalog

Overview, you can find it in the tree view. Use the Filter button to limit the
number of Products that appear in the listing, and then expand a Product node to
display its available Product versions.

Example: To locate OpenText™ Document Pipeline 16, type pipe in the Filter by box, and
then expand the Document Pipelines node. Click Document Pipelines 21.2 to open the
Catalog - Product details page for that Product version.

Note: Not every available version is listed for each Product. If you require an
older version of a Product, you can download it directly from OpenText My
Support.

60 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 7.2. Obtain Product Documentation

7.2 Obtain Product Documentation

The Catalog - Product details view provides links to documentation for any Product
in the System Center Manager Product Catalog. There are two buttons. Both of them
open pages on the OpenText My Support website. The Release notes button
opens the Product Release Notes. The Additional documentation button opens a
My Support page that contains published documentation for the Product version.

7.3 Download Products

Using the Catalog, you can download Product installers directly to System Center
Manager. (If you run System Center Manager in offline mode, you can download
installers using a browser, and then upload them to System Center Manager.) Once
System Center Manager has an installer, it can install the Product on your managed
Systems.

Download Products in Online Mode

If System Center Manager is connected to the Internet, you can download Products
directly.

To download a Product installer to System Center Manager in Online mode:

1. Open the Catalog - Product details page for the Product version that you
require, and then click Download.

2. On the Catalog - Product download page, select a server operating system. The
page refreshes to display the Product Components that will be downloaded.
Review the list. You can customize the download list by selecting or clearing the
check boxes for optional Product Components. When you have selected the
Product Components that you desire, click Download.

3. The Confirm Download dialog box displays the components to be

downloaded, and the size of the download. Enter your User name and
Password, and then click Sign in. System Center Manager logs on to OpenText
My Support using your credentials and starts to download the Product installer.

4. The Product download started dialog box informs you that the download of
your Product Components has started. To monitor the progress of the

download, click the Download icon , or open the Downloads view of the
Activities page, and then click the Products tab.

Download Products in Offline Mode

If System Center Manager is not operating in Online mode, open System Center
Manager using a computer that is connected to the Internet, download the Products
that you require, and then upload them to System Center Manager manually.

SYSCM240400-AGD-EN-01 Administration Guide 61

Chapter 7 The Product Catalog

To load a Product installer into System Center Manager in Offline mode:

1. Open the Catalog - Product details for the Product version that you require,
and then click Download.

2. On Catalog - Product download page, select a server operating system. The

page refreshes to display the Product Components that will be downloaded.
Review the list. You can customize the download list by selecting or clearing the
check boxes for each optional Product Component.

3. For each Product Component that you desire, click the Download button .

4. You are prompted to enter your OpenText My Support credentials. Enter your
user name and password, and then click Sign in.

5. System Center Manager logs onto OpenText My Support using your credentials
and starts the product download. Your browser downloads the Product to your
computer.

6. Click the Upload button that is available on any Catalog view to load the
Product installer into System Center Manager. Drag and drop the installer onto
the Upload page, or click Add files and browse to the installer’s file location.
When you are ready to start the upload, click Continue.

Tip: The Product upload area serves only to upload OpenText software
products. If you want to upload a third-party product to System Center
Manager, use the external vendor file upload area instead. See “Settings:
External Vendor Files” on page 120.

7. After the upload completes, click Close to exit the Upload page. The product
that you downloaded is now visible on the Products tab of the Downloads view
of the Activities page

62 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

Chapter 8
Execution Plans, Steps, and Variables

Execution plans are repeatable sets of instructions that System Center Manager can
execute to perform operations of varying complexity. An Execution Plan can do
something simple, like creating a directory and moving a file into it, or complex, like
installing and configuring multiple instances of Content Server and a deployment of
OpenText Directory Services in a single operation. Execution Plans can be
customized to suit your Environment and your requirements.

Execution Plans consist of Steps: discrete operations that install or configure an

OpenText software product, write content to a file, apply a license, install a Content
Server module, or perform another installation or configuration task. You can order
Steps within an Execution Plan and disable them if circumstances dictate.

To simplify the task of adapting Execution Plans for use in different Environments,
and on new host Systems that may use differing file paths or other configuration
settings, Execution Plans use System Variables and Step Variables.

System Variables represent registered Systems in an Execution Plan. They allow you
to assign descriptive names to the Systems that Execution Plans modify. For
example, you could have an Execution Plan that makes changes to Archive_Center_
host. You can assign a different System to the Archive_Center_host System
Variable whenever you run the Execution Plan. In this way, System Variables
facilitate re-use of Execution Plans.

Step Variables are used to refer to values in a Step’s configuration. If your Execution
Plan requires you to specify the same configuration directory numerous times, for
example, you could create a configDir Variable and assign it to each of the directory
configurations. If you need to specify a different configuration directory when you
re-use the Execution Plan, you can update the value of the configDir Variable and
the change automatically propagates throughout the Execution Plan. Using
Variables allows you to easily tailor an Execution Plan for use in differing
Environments.

Execution Plans are created for a specific Solution Environment, but they are visible
to anyone who is logged on to the same Solution. This means that it’s easy to re-use
an Execution Plan in a different Environment in the same Solution. You can create
an Execution Plan in your Development Environment, for example, and easily re-use
it in your Quality Assurance, User Acceptance Testing, and Production
Environments. You can also use an Execution Plan outside of the Solution that it was
created for, by exporting it and then importing it into an Environment from a
different Solution.

You can create, view, and edit Execution Plans on the Plans Overview. To view
Execution Plans that are queued to execute, that are currently in progress, or that
have completed, open the Execution Plans view of the Activities page.

SYSCM240400-AGD-EN-01 Administration Guide 63

Chapter 8 Execution Plans, Steps, and Variables

8.1 Execution Plans

Execution Plans consist of one or more Execution Plan Steps.

Execution Plans are managed on the Plans Overview. To access the Plans

Overview, click Plans on the Navigation menu .

The following operations are available on the Plans Overview:

Add Execution Plans

To add an Execution Plan, click the Add item button and then click New.
For more information, see “Add an Execution Plan” on page 65.
Import Execution Plans

To import an Execution Plan, click the Add item button , then click Import
and browse to the location of an exported Execution Plan. For more information,
see “Import an Execution Plan” on page 68.
Delete Execution Plans
To delete one or more Execution Plans, do one of the following:

• Select any Execution Plans that you would like to delete, and then click
Delete at the top of the list.
•
Click the Delete button in the Execution Plan’s Inline Actions Bar.

For more information, see “Delete an Execution Plan” on page 68.

Copy Execution Plans
To copy an Execution Plan, do one of the following:

• Select an Execution Plan, and then click Duplicate at the top of the list.
•
Click the Duplicate button in the Execution Plan’s Inline Actions Bar.

For more information, see “Copy an Execution Plan” on page 67.

Export Execution Plans
To export an Execution Plan, do one of the following:

• Select an Execution Plan, and then click Export at the top of the list.
•
Click the Export button in the Execution Plan’s Inline Actions Bar.

For more information, see “Export an Execution Plan” on page 68.

Edit Execution Plans
To edit an Execution Plan, do one of the following:

64 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 8.1. Execution Plans

• Select an Execution Plan, and then click Edit at the top of the list.
•
Click the Edit icon in the Execution Plan’s Inline Actions Bar.

For more information, see “Edit an Execution Plan” on page 66.

Run Execution Plans

To run an Execution Plan, do one of the following:

• Select an Execution Plan, and then click Execute at the top of the list.
• click the Execute icon on the Execution Plan’s Inline Actions Bar.

For more information, see “Run an Execution Plan” on page 66.

8.1.1 Add an Execution Plan

An Execution Plan is created for a specific Environment and is visible to all
Environments within its Solution. If you have access to multiple Environments, be
sure to select the correct Environment before you create your Plan.

To add an Execution Plan:

1. Click Plans on the Navigation menu to open the Plans Overview.

2. Click the Add item button , and then click New.

3. On the New Plan page, give the Plan a name and, optionally, a description.

4. Add steps to the plan.

a. Create a System Variable that identifies the System where the steps will be
performed. For information on System Variables, see “System Variables”
on page 80.

b. Click the Add steps button . Numerous Step types are available. For
information on adding and configuring Steps, see “Execution Plan Steps”
on page 69.

Tips

• You can combine multiple steps to enhance the usefulness of a plan.

For example, you can combine an Install Content Server step and a Set
up Content Server step
• You can copy an existing step, to run it on a different System for
example, by clicking Duplicate.

SYSCM240400-AGD-EN-01 Administration Guide 65

Chapter 8 Execution Plans, Steps, and Variables

5. Re-order the Steps, if necessary, by using the buttons on the Step’s Inline
Actions Bar or by using the Drag and drop to reorder steps drag handle
beside each step.

6. When you have finished adding and configuring steps, run the Plan
immediately or save it for later use:

• To run the Execution Plan right away, click Execute.

• To save the Plan for later use, click Save.

Tip: If the Save button is unavailable, verify that you have given the Plan
a name, assigned a System Variable to every Step in the Execution Plan,
and entered every mandatory value. If the Status icon indicates a problem
with your step, place your mouse pointer over it to see additional
information on the problem.

8.1.2 Edit an Execution Plan

When you edit an Execution Plan, you can change its name and description, and you
can add, remove, or modify Execution Plan Steps.

To edit an Execution Plan, do one of the following:

• Select an Execution Plan, and then click Edit at the top of the list.
•
Click the Edit icon in the Execution Plan’s Inline Actions Bar.

For information on adding, removing, and modifying steps, see “Execution Plan
Steps” on page 69.

8.1.3 Run an Execution Plan

You can run an Execution Plan as soon as you create it, or save it and run it later
from the Plans Overview.

• To run a plan immediately, create or modify a plan, and then, on the Plan Details
page, click Execute.
• To run a saved plan from the Plans Overview, do one of the following:

– Select an Execution Plan, and then click Execute at the top of the Plan list.
– Click the Execute icon on the Execution Plan’s Inline Actions Bar.

If the Plan that you execute requires passwords to be set or entered, you are
prompted to enter them at run time. Enter any required passwords, and then click
Next. To verify that the passwords are correctly entered, you can select Show
Passwords.

66 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 8.1. Execution Plans

Tip: System Center Manager Execution Plans do not store passwords. You
must enter them each time you run an Execution Plan.

After you start an Execution Plan, the current view changes to the Execution Plans
view of the Activities page, where you can monitor the progress of the Plan. For
more information, see “Monitor Execution Plans” on page 69.

8.1.4 Copy an Execution Plan

There are numerous reasons that you might want to copy an Execution Plan. Some
of the most common are:

• To test modifications to an Execution Plan without losing a record of the original

Execution Plan.
• To take an Execution Plan that you created for one System in your Environment
and adapt it for use on a different System in the same Environment. For example,
you could use an existing product installation Execution Plan to install a
supported OpenText Product on a new System in your Production Environment.
• To take an Execution Plan that you created for use in a specific Environment and
adapt it for use in a different Environment in your Solution. For example, you
could use an Execution Plan that you developed to set up your Content Server :
Development Environment to set up a new Content Server : User Acceptance
Testing Environment.

Before you copy an Execution Plan, verify that you are in the Environment that you
want it to apply to. For example, to copy an Execution Plan from the Development
Environment to the Production Environment, switch to the Production
Environment before you click the Duplicate icon.

To copy an Execution Plan:

1. Open the Plans Overview, and do one of the following:

• Select an Execution Plan, and then click Duplicate at the top of the Plan list.

• Click the Duplicate button on the Execution Plan’s Inline Actions Bar.

2. In the Duplicate plan dialog box, enter a Name and Description for your copied
Execution Plan and then click Duplicate.

The copied plan now appears on the Plans Overview and the Environment that it
applies to appears in the Environment column.

SYSCM240400-AGD-EN-01 Administration Guide 67

Chapter 8 Execution Plans, Steps, and Variables

8.1.5 Delete an Execution Plan

To delete one or more Execution Plans, open the Plans Overview, select any
Execution Plans that you would like to delete, and then click the Delete button at the
top of the Plans list. To delete a single Execution Plan, you can click the Delete
button on its Inline Actions Bar.

8.1.6 Export an Execution Plan

To use an Execution Plan in a Solution that it was not created in, you can export the
Execution Plan. When you export an Execution Plan, System Center Manager saves
it as a file with a PLN file extension that you can import into another Solution. The
Solution that you import it to can be on your local installation of System Center
Manager or on a different installation.

To export a Plan, do one of the following:

• Select an Execution Plan, and then click Export at the top of the Plan list.
•
Click the Export button on the Execution Plan’s Inline Actions Bar.

The Plan is downloaded by your browser as a file named <Plan_name>.pln.

Tip: It is also possible to export an entire Solution, including each of its

Environments and all of their Execution Plans. You also have the option of
exporting any Product installer files and External Vendor Files that are
referenced by the Execution Plans. For more information, see “Export and
Import Solutions” on page 113.

8.1.7 Import an Execution Plan

To use an Execution Plan that has been exported from an Environment in a different
Solution, import the saved file to your current Environment.

Tip: To use an Execution Plan from an Environment in your current Solution,

you do not need to import it. You can copy it. See “Copy an Execution Plan”
on page 67.

If you have access to multiple Environments, be sure to select the correct

Environment before you import a saved Execution Plan.

To import an Execution Plan:

1. On the Plans Overview page, click the Add item button , and then click
Import.
2. On the Import plan page:

a. Enter a Name and, optionally, a Description.

68 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 8.2. Execution Plan Steps

b. Beside the Choose plan file box, click Browse. Browse to the location of the
Execution Plan that you want to import, and select it.

Tip: By default, an exported Execution Plan has a file extension of PLN.

c. Click Import.

The imported Execution Plan now appears on the Plans Overview.

8.1.8 Monitor Execution Plans

The Execution Plans view of the Activities page provides information on the status
of Execution Plans that are in progress or that you have executed in the past. For
more information, see “The Activities Page: Execution Plans View” on page 84.

8.2 Execution Plan Steps

Steps are the building blocks of Execution Plans. An Execution Plan can consist of a
single Step or can have multiple Steps that you can order and disable as necessary.

Steps have multiple configuration settings that appear on one or more tabs. Before
you can use a Step in your Execution Plan, you need to provide suitable values for
the configuration settings.

Note: For several reasons, detailed System Center Manager online help is not
provided for specific Execution Plan Steps.

• Some Steps require no explanation because they perform a simple task, such
as copy a file, execute a Powershell command, or modify an INI file.
• Other Steps perform tasks that are documented elsewhere, such as install or
configure Content Server or Directory Services. The configurations required
in these steps are explained in their respective help and guides.

Installation and configuration documentation for various products is available

in the System Center Manager Catalog and on OpenText My Support.

Within an Execution Plan, you can do the following with Steps:

Add
To add a Step, open an Execution Plan, and select a System Variable that

represents the System that will run the Step. Click the Add steps button .

• To add one or more Steps, select the Steps and then click Add at the top of
the Step list.
•
To add a single step, click the Add button on its Inline Actions Bar.

Once you add a Step, you need to configure it. See “Configuring Plan Steps”
on page 71.

SYSCM240400-AGD-EN-01 Administration Guide 69

Chapter 8 Execution Plans, Steps, and Variables

View and Edit

To view a Step and make modifications to it, edit an Execution Plan and then
edit the Step, using one of the following methods:

• Select a Step, and then click Edit at the top of the Plan list.
•
Click the Edit button on the Execution Plan’s Inline Actions Bar.

Review its existing settings and change them, if desired. Click Save to save your
changes.
Enable/Disable
To prevent a Step from running without removing it from the Plan, disable it
using one of the following methods:

• Select a Step, and then click Disable at the top of the Step list.
•

Click the Disable button on the Step’s Inline Actions Bar.

The Execution Plan will run but will skip the disabled Step. Disabling a Step
could be useful when you want to run an existing Execution Plan that has a Step
that does not apply to the current System or Environment. A disabled Step has a

status of Step disabled and has an Enable button , instead of a Disable

button. To re-enable the Step, click the Enable button.
Remove
To remove one or more steps permanently from an Execution Plan, do one of the
following:

• To remove one or more Steps, select the Steps and then click Remove at the
top of the Step list.
•
To remove a single step, click the Remove button on its Inline Actions
Bar.

Duplicate
To make a copy of a Step, do one of the following:

• Select the Step and then click Duplicate at the top of the Step list.
•
Click the Duplicate button on its Inline Actions Bar.

The copied Step appears immediately below the current Step.

Move
To move a Step higher or lower in the order of execution, do one of the
following:

70 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 8.3. Execution Plan Step Library

• Select the Step and then click Move up or Move Down at the top of the Step
list.
• Use the arrow buttons on the Step’s Inline Actions Bar.

8.2.1 Configuring Plan Steps

Typically, a Step has configuration settings that you need to fill out before the Step
can run within its Execution Plan. The configurations vary according to the type of
Step. An installation Step requires at least an installer file and an installation
directory and typically requires additional configuration information, whereas a file
copy step needs only a source file and a destination directory. Some Step
configurations are mandatory and others are optional. You can save an Execution
Plan that does not have values for all of its mandatory step configurations. (You can
also run an Execution Plan that does not have values for all of its mandatory step
configurations, but it will probably not run successfully.)

You can obtain information on the required configurations by reading the

descriptions that appear below most of the settings. In some cases, you may need to
obtain information from the relevant documentation. For example, to obtain
complete information on the configurations in a Content Server installation step,
refer to the OpenText Content Management - Installation Guide (LLESCOR-IGD).

The required configuration settings may appear on multiple tabs. For example, the
step that installs OpenText™ Directory Services (OTDS) on a System requires you to
provide information on the Default, Apache Tomcat, LDAP, and Java tabs. Be sure
to provide information on each of the tabs.

Tip: If you are configuring a software installation step and the software that
you want to install is not available in the Installer menu of the Step you have
selected, ensure that you have downloaded it using the Product Catalog. See
“Download Products” on page 61.

8.3 Execution Plan Step Library

System Center Manager provides Execution Plan Steps that you can use to install
and configure software that you have downloaded from the Catalog. It also provides
Common Steps that interact with the operating system, which you can include in an
Execution Plan to automate basic installation and configuration tasks.

The following Execution Plan Steps are available in System Center Manager.
Combine these Execution Plan Steps in repeatable Execution Plans to automate
installation and configuration tasks.

SYSCM240400-AGD-EN-01 Administration Guide 71

Chapter 8 Execution Plans, Steps, and Variables

8.3.1 AppWorks Gateway Execution Plan Steps

AppWorks Gateway Execution Plan Steps install OpenText AppWorks Gateway.

AppWorks Gateway: Install AppWorks Gateway for Linux

Installs OpenText AppWorks Gateway on Linux.

AppWorks Gateway: Install AppWorks Gateway for Windows

Installs OpenText AppWorks Gateway on Windows.

8.3.2 Archive Center Execution Plan Steps

The Execution Plan Steps in this section are used to install Archive Center and
Archive Center components.

Tip: Document Pipelines are often used with Archive Center. For information
on Document Pipeline Execution Plan Steps, see “Document Pipeline
Execution Plan Steps” on page 76.

Administration Client: Install Administration Client for Windows

Installs Administration Client for Windows, which is used with OpenText™
Archive Center and other OpenText products. Information on the
Administration Client for Windows is available on OpenText My Support at
Administration Client (https://knowledge.opentext.com/knowledge/llisapi.dll?
func=ll&objId=13609871&objAction=browse&sort=name).

Archive Cache Server: Install Archive Cache Server for Linux

Installs Archive Cache Server on Linux. Archive Cache Server is a component of
OpenText™ Archive Center. Information on installing Archive Cache Server on
Linux is available at OpenText Archive Center - Installation Guide for Linux (AR-
IGU).

Archive Cache Server: Install Archive Cache Server for Windows

Installs Archive Cache Server on Windows. Archive Cache Server is a
component of OpenText™ Archive Center. Information on installing Archive
Cache Server on Windows is available at OpenText Archive Center - Installation
Guide for Windows (Integrated Archive Installer) (AR-IGW).

Archive Monitoring Server: Install Archive Monitoring Server for Linux

Installs Archive Monitoring Server on Linux. Archive Monitoring Server is a
component of OpenText™ Archive Center. Information on installing Archive
Monitoring Server on Linux is available at OpenText Archive Center - Installation
Guide for Linux (AR-IGU).

Archive Monitoring Server: Install Archive Monitoring Server for Windows

InstallsArchive Monitoring Server on Windows. Archive Monitoring Server is a
component of OpenText™ Archive Center. Information on installing Archive
Monitoring Server on Windows is available at OpenText Archive Center -
Installation Guide for Windows (Integrated Archive Installer) (AR-IGW).

72 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 8.3. Execution Plan Step Library

Configure Archive Server cluster on Linux

Configures two or more Archive Server instances that are deployed on Linux to
function as a cluster.
Configure Archive Server cluster on Windows
Configures two or more Archive Server instances that are deployed on
Windows to function as a cluster.
Archive Server: Install Archive Server for Linux
Installs Archive Center on Linux. Information on installing Archive Center on
Linux is available at OpenText Archive Center - Installation Guide for Linux (AR-
IGU)
Archive Server: Install Archive Server for Windows
Installs Archive Center on Windows. Information on installing Archive Center
on Windows is available at OpenText Archive Center - Installation Guide for
Windows (Integrated Archive Installer) (AR-IGW)

8.3.3 Common Execution Plan Steps

Common Execution Plan Steps perform basic operating system tasks. They can copy
files, execute scripts, write to INI files, and perform other such operations. Common
Execution Plan Steps run as the user that runs System Center Manager.

This section lists the available Common Execution Plan Steps. More detailed
information is available within the Step itself. Each Common Execution Plan Step
includes a detailed Description of what the Execution Plan Step does and the
conditions that apply to it.

Common: Clean a directory

Deletes the contents of a directory.
Common: Copy a directory
Copies a directory to the specified location.
Common: Copy a file
Copies a file, renaming it if desired, to the specified location.
Common: Copy a file to a directory
Copies a file, keeping its name, to the specified location.
Common: Copy external vendor file
Copies the specified external vendor file to the specified directory on one or
more System Center Agent host machines.

Tip: External vendor files are third-party files that you import into System
Center Manager. For more information, see “Settings: External Vendor
Files” on page 120.
Common: Copy software
Copies OpenText software to the specified directory on one or more System
Center Agent host machines.

SYSCM240400-AGD-EN-01 Administration Guide 73

Chapter 8 Execution Plans, Steps, and Variables

Common: Delete a directory

Deletes a directory and its contents, including all subdirectories.
Common: Delete a file
Deletes the specified file. Behaves in the same manner as Common: Delete a
directory if a directory name is specified.
Common: Execute command line
Executes the specified command.
Common: Execute PowerShell
Executes the specified command from within the Windows PowerShell
command-line shell.
Common: Extract archive
Extracts the contents of a ZIP, TAR, or TAR.GZ archive to the specified location.
Common: Make a directory
Creates a directory, or a chain of directories.
Common: Modify INI file
Adds, modifies, or removes a key/value pair in the specified section of an INI
file.
Common: Move a directory
Moves a directory to the specified location.
Common: Move a file
Moves a file to the specified location.
Common: Start a service
Starts a service. Works on Windows and Linux.
Common: Stop a service
Stops a service. Works on Windows and Linux.
Common: Write string to a file
Writes a string to a new or existing file. The file is created if it does not exist. You
can specify that you want to overwrite existing content in the file or append the
string to it.

8.3.4 Content Server Execution Plan Steps

Content Server Execution Plan Steps install and configure Content Server and
Content Server modules, and can apply a Content Server license or a saved Content
Server configuration.

Content Server: Apply Administration Settings

Applies an XML file that contains saved Content Server administration settings.
For more information on saving Content Server administration settings to an
XML file, see OpenText Content Management Admin Help - System Administration
(LLESWBA-H-AGD).

74 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 8.3. Execution Plan Step Library

Content Server: Apply License

Applies a Content Server license file. For more information on Content Server
license files, see OpenText Content Management Admin Help - System
Administration (LLESWBA-H-AGD).
Content Server: Install Content Server for Linux
Installs Content Server on Linux. For more information on installing Content
Server, see OpenText Content Management - Installation Guide (LLESCOR-IGD).
Content Server: Install Content Server for Windows
Installs Content Server on Windows. For more information on installing Content
Server, see OpenText Content Management - Installation Guide (LLESCOR-IGD).
Content Server: Install Language Packs for Linux
Installs one or more language packs on the specified Content Server instance
deployed on Linux. For more information on installing Content Server language
packs, see OpenText Content Management Admin Help - System Administration
(LLESWBA-H-AGD).
Content Server: Install Language Packs for Windows
Installs one or more language packs on the specified Content Server instance
deployed on Windows. For more information on installing Content Server
language packs, see OpenText Content Management Admin Help - System
Administration (LLESWBA-H-AGD).
Content Server: Install Module
Installs a Content Server module on the specified Content Server instance. For
more information on installing Content Server modules, see OpenText Content
Management - Installation Guide (LLESCOR-IGD).
Content Server: Install Monitoring Agent
Installs the OpenText Monitoring Agent. Open Text Monitoring Agent provides
Content Server Administrators with the ability to perform real-time monitoring
of Content Server systems and to gather performance data for later analysis.
Information on Open Text Monitoring Agent is available on OpenText My
Support at Monitoring Agent 20.2 Install & Configuration Guide (https://
knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=77650436&
objAction=Open&nexturl=%2Fknowledge%2Fllisapi%2Edll%3Ffunc%3Dll
%26objId%3D77650435%26objAction%3Dbrowse%26viewType%3D1)
Content Server: Set up Content Server
Performs the initial configuration of Content Server that is required after
installation of Content Server. For more information on configuring Content
Server after installation, see OpenText Content Management - Installation Guide
(LLESCOR-IGD).

SYSCM240400-AGD-EN-01 Administration Guide 75

Chapter 8 Execution Plans, Steps, and Variables

8.3.5 Directory Services Execution Plan Steps

Directory Services Execution Plan Steps install and configure OpenText Directory
Services (OTDS).

Directory Services: Install Directory Services for Linux

Installs OTDS on Linux. For more information on installing OTDS, see OpenText
Directory Services - Installation and Administration Guide (OTDS-IWC).
Directory Services: Install Directory Services for Windows
Installs OTDS on Windows. For more information on installing OTDS, see
OpenText Directory Services - Installation and Administration Guide (OTDS-IWC).
Directory Services: Set up Directory Services
Performs the initial configuration of OTDS that is required after installation . For
more information on configuring OTDS after installation, see OpenText Directory
Services - Installation and Administration Guide (OTDS-IWC).

8.3.6 Document Pipeline Execution Plan Steps

Document Pipeline Execution Plan Steps install various Document Pipeline
products. Document Pipelines are frequently used with Archive Center. For
information on installing any of the Document Pipelines mentioned below, see
OpenText Document Pipeline - Installation and Upgrade Guide (AR-IDPDP).

Document Pipeline Base: Install Document Pipeline Base for Linux

Installs Document Pipeline Base on Linux.
Document Pipeline Base: Install Document Pipeline Base for Windows
Installs Document Pipeline Base on Windows.
Document Pipeline CMIS: Install Document Pipelines CMIS for Linux
Installs Document Pipeline for Archive Center CMIS on Linux.
Document Pipeline CMIS: Install Document Pipelines CMIS for Windows
Installs Document Pipeline for Archive Center CMIS on Windows.
Document Pipeline Doculink: Install Document Pipeline Doculink for Linux
Installs Document Pipeline for DocuLink on Linux.
Document Pipeline Doculink: Install Document Pipeline Doculink for Windows
Installs Document Pipeline for DocuLink on Windows.
Document Pipeline File Archiving: Install Document Pipelines File Archiving for
Windows
Installs File System Archiving Document Pipeline on Windows.
Document Pipeline Info: Install Document Pipelines Info for Linux
Installs Document Pipeline Info on Linux.
Document Pipeline Info: Install Document Pipelines Info for Windows
Installs Document Pipeline Info on Windows.

76 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 8.3. Execution Plan Step Library

Document Pipeline Perl: Install Document Pipelines Perl for Linux

Installs Document Pipeline Perl on Linux.
Document Pipeline Perl: Install Document Pipelines Perl for Windows
Installs Document Pipeline Perl on Windows.
Document Pipeline Remote Interface: Install Document Pipelines Remote
Interface for Linux
Installs Document Pipeline Remote Interface on Linux.
Document Pipeline Remote Interface: Install Document Pipelines Remote
Interface for Windows
Installs Document Pipeline Remote Interface on Windows.
Document Pipeline SAP: Install Document Pipelines for SAP for Linux
Installs OpenText Document Pipeline for SAP Solutions on Linux.
Document Pipeline SAP: Install Document Pipelines for SAP for Windows
Install OpenText Document Pipeline for SAP Solutions on Windows.

8.3.7 Intelligent Viewing Execution Plan Steps

Intelligent Viewing Execution Plan Steps install Intelligent Viewing on Windows
and Linux, and configure Content Server for use with Intelligent Viewing.

Intelligent Viewing: Configure Content Server for Intelligent Viewing

Configures Intelligent Viewing URLs on the specified Content Server
installation.
Intelligent Viewing: Install Intelligent Viewing for Linux
Installs Intelligent Viewing on Linux.
Intelligent Viewing: Install Intelligent Viewing for Windows
Installs Intelligent Viewing on Windows.

8.3.8 PowerDocs Execution Plan Steps

PowerDocs Execution Plan Steps automate the installation of the various Powerdocs
Product Components.

Install PowerDocs Application Server on Linux

Installs PowerDocs application server on Linux.
Install PowerDocs Application Server on Windows
Installs PowerDocs Application Server on Linux.
Install PowerDocs Content Manager on Linux
Installs PowerDocs Content Manager on Linux.
Install PowerDocs Content Manager on Windows
Installs PowerDocs Content Manager on Windows.

SYSCM240400-AGD-EN-01 Administration Guide 77

Chapter 8 Execution Plans, Steps, and Variables

Install PowerDocs Document Server Linux

Installs PowerDocs Document Server on Linux.
Install PowerDocs Document Server Windows
Installs PowerDocs Document Server on Windows.
Install PowerDocs Output Server Linux
Installs PowerDocs Output Server on Linux.
Install PowerDocs Output Server Windows
Installs PowerDocs Output Server on Windows.
Install PowerDocs Server Manager Linux
Installs PowerDocs Server Manager on Linux.
Install PowerDocs Server Manager Windows
Installs PowerDocs Server Manager on Windows.

8.4 Execution Plan Variables

System Center Manager Execution Plans use two kinds of Variables: Step Variables
and System Variables. Step Variables are used for Step configuration values and
System Variables represent Systems within a given Environment.

8.4.1 Step Variables

Step Variables are placeholders that you can use in place of fixed values in your Step
configuration settings. Step Variables allow you to easily modify configuration
settings for use on different Systems, to quickly update identical settings that need
to be specified in multiple locations, and to ensure consistency in your configuration
setting values.

Example: You have an Execution Plan that references the Content Server installation
directory multiple times, so you create a Step Variable called <Content_Server_home> that
represents the Content Server installation directory. If you re-use the Execution Plan to install
Content Server to a different location, you do not need to manually update the installation
directory repeatedly. Instead you can update the value of the <Content_Server_home> Step
Variable, and System Center Manager automatically applies the change throughout the
Execution Plan.

Step Variables have effect within a specific Execution Plan. You can define a Step
Variable for use in one Step and make use of it in the other Steps in your Execution
Plan. You cannot reference a Step Variable from one Plan in a different Plan.

Tip: If you have a useful set of Step Variables that you would like to use in a
different Execution Plan, you can copy the Plan to another Environment in
your Solution, or export it and import it to an Environment in another Solution.

The Step Variables that you define appear on the Variables tab of your Execution
Plan. Use this tab to review all of the Variables and to update their values, as
required.

78 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 8.4. Execution Plan Variables

8.4.1.1 Create a Step Variable

To apply a new Step Variable to a configuration setting, place your cursor in the
Variable box beside the setting and type the name of the new Variable.

To create a Step Variable:

1. Open an Execution Plan Step.

2. Type a name in the Variable name box. As you enter the name, it appears
below the Variable box.

3. Click the <Variable_Name> to create the Variable.

The new Variable is created with the value that exists in the configuration setting
beside it.

8.4.1.2 Apply an Existing Step Variable

To apply an existing Step Variable to a configuration setting, place your cursor in the
Variable name box beside the setting. Select a Variable from the list that appears
below the box. The Variable and its value are applied to the configuration setting.

8.4.1.3 View and Edit Step Variables

You can view and edit Step Variables on the Variables tab of an Execution Plan.

To view and edit a Step Variable:

1. Open an Execution Plan and click the Variables tab.

2. To change a Variable value, replace the content in the Variables Value box with
a different value.

3. Click Save.

After you change the value of a Variable, its value is updated in any configuration
setting in the Execution Plan that has the Variable assigned to it.

8.4.1.4 Remove Step Variable Assignments

To remove a Variable that you have assigned as the value of a configuration setting,
open the Execution Plan Details page and, in the Variables tab, click the Remove

button that appears beside the Variable name. Removing the Variable does not
remove the value of the setting. You can change the value manually, if you need to.

If the same Variable is used elsewhere in an Execution Plan, it continues to appear

on the Variables tab. To completely remove it, ensure that you have removed the
Variable from every setting that it is applied to. After you remove the last instance of
the Variable, it no longer appears on the Variables tab.

SYSCM240400-AGD-EN-01 Administration Guide 79

Chapter 8 Execution Plans, Steps, and Variables

8.4.2 System Variables

System Variables are placeholders that you use in place of specific System names in
an Execution Plan. You can view and manage them on the System Variable tab of
an Execution Plan.

When you first create an Execution Plan, the System Variables tab shows every
System that is registered in your current Environment, and each System Variable has
the same name as the System that it represents. You can remove any Systems that
you do not need to use in the current Execution Plan, and you can rename the
System Variable for any registered System.

Tip: To make it simpler to re-use an Execution Plan, give your System

Variables descriptive names that make the System’s role obvious, such as CS_
Admin_server, Archive_Center_host, or OTDS server.

If there is only one registered System in the Environment, it appears in the System
Variables tab and is automatically assigned to any step in the Execution Plan.

8.4.2.1 Add a System Variable

You create and edit System Variables on the System Variables tab of an Execution
Plan. An Execution Plan must have at least one System Variable or you cannot save
it. Other than that, you can add as many System Variables as you want to an
Execution Plan.

System Variable names must be unique within an Execution Plan, but it is possible
to create multiple System Variables that point to the same registered System.

Tip: Having two System Variables that point to the same System could be
useful if your Execution Plan has two Product installation steps. If you have
System Variables named product1_host and product2_host, you could use
them to install the two Products on the same System in a QA Environment and
on two different Systems in a production Environment.

To add a System Variable:

1. Open an Execution Plan and click the System Variables tab. Name, System and
Status information appears for at least one System Variable.

2. Add a System Variable:

a. Click the Add System Variable button . A new row appears on the
System Variables tab.
b. In the Name box, enter a System Variable name.
c. Choose a System from the Select a system menu. System Center Manager
displays the status of the System.

3. Click Save.

80 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 8.4. Execution Plan Variables

8.4.2.2 Apply a System Variable

Any System Variable that exists on the System Variables tab can be applied on the
Step tab of an Execution Plan. If you create an Execution Plan for an Environment
that has only one System, the System Variable is applied automatically. Otherwise,
select a System Variable from the System Variables menu to apply it to the current
Step. You cannot save an Execution Plan if it does not have a System Variable
applied to each of its Steps.

8.4.2.3 View and Edit System Variables

To view and edit the System Variables that are used in an Execution Plan, edit the
Plan and open the System Variables tab.

Rename
To rename any System Variable, click the Name box and enter a new name.

Reassign
To reassign the System Variable to a different System, click the Select a system
menu and choose a different System.

Add

To add a new System Variable, click the Add item button (See “Add a
System Variable” on page 80.)

Remove
To remove an existing System Variable, select it on the System Variables tab
and then click Remove above the list of System Variables. (See “Remove System
Variables” on page 81.)

After you click Save, any changes that you make to System Variables on the System
Variables tab are immediately reflected on the System Variable column of the Step
tab. For example, if you change a System Variable named cs_host to cs_agent_
server and assign a different System to it, any step that was performed by cs_host
is automatically updated to be performed by cs_agent_server with its new System
value.

8.4.2.4 Remove System Variables

When you first create an Execution Plan, the System Variables tab shows every
System that is registered in your current Environment, with the System Variable
name given the same name as the System that it represents. You can remove any
System Variable that you do not need, but an Execution Plan must have at least one
System Variable, or it cannot be saved.

To remove a System Variable, select it on the System Variables tab and then click
Remove above the list of System Variables. The row representing the System
Variable is immediately removed. Click Save to save the change.

SYSCM240400-AGD-EN-01 Administration Guide 81

Chapter 9

Monitor System Center Manager Activities

The Activities page provides information on operations performed by System

Center Manager. It has four views.

• Activities Overview

• Execution Plans

• Downloads

• Notifications

Each view is explained in greater detail in this section.

9.1 The Activities Overview

The Activities Overview provides information on Running and Other operations
performed by System Center Manager.

The Status column provides information on the state of an activity that is in progress
or has finished running:

•
Activities that complete successfully appear with a status of Completed .

• Activities that complete with problems appear with a status of Complete with

errors .

•
Activities that you stop before completion appear with a status of Canceled .

Various options are available to you on the Activities Overview.

•
To cancel an activity that is running, click the Cancel button .

•
To filter the view by Activity status, click the Filter button .
•
To obtain additional information about activities, click the Details button in
the Inline Actions Bar of any activity record.

•
To remove all activity records from the current tab, click Remove all items .

SYSCM240400-AGD-EN-01 Administration Guide 83

Chapter 9 Monitor System Center Manager Activities

9.2 The Activities Page: Execution Plans View

The Execution Plans view of the Activities page provides information on the status
of Execution Plans that are in progress or that you have executed in the past.

Note: This page view is not available in all versions of System Center Manager.

The view has two tabs:

Running
Execution Plans that are in progress appear at the top of the view, under

Running execution plans. Plans in progress appear with a Running icon .

To cancel a running Execution Plan, click its Cancel button .

Tip: When you cancel an Execution Plan, the current step runs to
completion before the Plan is stopped.
Other
Execution Plans that have completed, or that are queued to be executed, appear
on the Other tab. For a completed Plan, the icon in the Status column indicates
whether it completed successfully, was cancelled, or encountered an error.

Tip: If you start an Execution Plan that runs on a System that is already
busy running a different Plan, the plan appears in the Other execution

plans area with a status of Queued .

To view detailed status information on a running Execution Plan, click the Details

button on its Inline Actions Bar. The <Execution_Plan_Name> Details page

opens and displays details on the step that is currently running and its status. To

obtain information on the step that is currently running, click the Details button
on the step’s Inline Actions Bar. The <Step_Name> Details page opens and provides
information on the currently running step, including all of its parameters and the
values assigned to them.

84 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 9.3. The Activities Page: Downloads View

9.3 The Activities Page: Downloads View

The Downloads view of the Activities page provides information on downloads
that you have initiated using System Center Manager. The downloads are presented
on separate tabs:

Products
Software installers that you have downloaded from the Catalog appear on the
Products tab.

Note: The Products tab is not available in all versions of System Center
Manager.
Updates
Downloaded Product Updates appear on the Updates tab.
Hotfixes
Downloaded patches and hotfixes appear on the Hotfixes tab.
Language Packs
Downloaded Content Server Language Packs appear on the Language Packs
tab.

To limit what is shown on any of the four tabs, click the Filter button and enter
text in the Filter By box.

Downloads have a status of Downloaded , Downloading , or Error .

Hotfixes and Language Packs can also have a status of Installed .

Various actions are available to you on the Downloads view of the Activities page:

Details
To view information on a download, do one of the following:

• Select a download and click Details at the top of the download list.
•
Click the Details button in the download’s Inline Actions Bar.

Delete
To delete one or more downloads from System Center Manager, do one of the
following:

• Select one or more downloads and click Delete at the top of the download
list.
•
Click the Delete button in a download’s Inline Actions Bar.

SYSCM240400-AGD-EN-01 Administration Guide 85

Chapter 9 Monitor System Center Manager Activities

Tip: Download information remains visible in “Settings: Audit”

on page 101 after you delete it from the Downloads view.
Download
To download a Product Installer from the Products tab to your desktop, do one
of the following:

•
Select a download and click Download at the top of the download list.
•
Click the Download button in a download’s Inline Actions Bar.

9.4 The Activities Page: Notifications View

System Center Manager Notifications inform you of events that may interest you or
require your attention. For example, if a new System is available in the Pending
systems section of the Systems Overview, a Notification informs you that there is a
System waiting for approval.

To quickly view new Notifications, click the Notifications button that

appears at the top of any System Center Manager page. (The number on the
Notifications button shows how many new Notifications are available.) The
Notifications panel appears and displays the latest Notifications.

To view all available Notifications, click More Notifications on the More Actions
menu to open the Activities page, Notifications view. To filter the view by

event type, click the Filter button and, in the side panel, select an event type
from the Type menu.

If you no longer wish to view a Notification, you can delete it using one of the
following methods:

• Select one or more Notifications and then click Remove at the top of the
Notifications list.
•
Click the Remove button in a Notification’s Inline Actions Bar.

Alternatively, you can configure Notifications to be automatically deleted once they

exceed a specified retention period. You can have this policy apply to all Notification
types or only the ones that you designate. See “Settings: Notification” on page 125

Tip: In general, Notification information remains visible in “Settings: Audit”

on page 101 even after you delete it from the Notifications view. However,
System Notifications may not always have a corresponding Audit entry. For
example, when a new System is registered, a System Waiting for Approval

86 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 9.4. The Activities Page: Notifications View

Notification is generated. There is no corresponding Audit entry for that

Notification, but once you approve the System, a System Approved event is
written to the Audit log.

SYSCM240400-AGD-EN-01 Administration Guide 87

Chapter 10

Update System Center Manager

System Center Manager is a self-updating application. From time to time, a banner

will appear below the menu bar informing you that an update for System Center
Manager is available. If you see a message stating that an update is available, click
Start update to apply the new version. Some System Center Manager functionality
may be disabled until you apply the update.

When you apply an update to System Center Manager, the System Center Agents
that connect to that instance are automatically updated the next time they connect to
System Center Manager. After you have applied a System Center Manager update,
you do not need to take any additional action to update your System Center Agents.

The procedure for updating System Center Manager varies depending if you
operate in online mode or not. Follow the instructions that apply to your System
Center Manager deployment.

Note: If the upgrade of System Center Manager does not succeed, it is

automatically rolled back, and the System Center Manager services are not
restarted. If the Update System Center dialog box does not inform you that
your system has been successfully updated, refer to the update.log and
update-error.log files for more information on the cause of the failure.

10.1 Update System Center Manager in Online Mode

To start an update in online mode, click Start update and log on to My Support.

To update System Center Manager in online mode

1. On the banner informing you that an update is available, click Start update.

2. The Confirm download dialog box appears. Enter your My Support user name
and password, and click Start download.

3. The Update System Center dialog box appears and displays messages
indicating that System Center Manager is downloading the update and
extracting it. When it has finished these operations, the dialog box informs you
that the update is ready to be applied to your system. Click Update to apply the
update.

4. The Update System Center dialog box informs you that System Center
Manager is applying the update. When it is finished, it informs you that your
system has been successfully updated. Click Refresh to refresh the System
Center Manager page that you are on and exit the update procedure.

SYSCM240400-AGD-EN-01 Administration Guide 89

Chapter 10 Update System Center Manager

10.2 Update System Center Manager in Offline Mode

In offline mode, System Center Manager cannot download an update automatically.
You need to obtain the update and upload it to System Center Manager before the
update can be applied.

The update file has a name similar to SystemCenterUpdate_16<_#_#>.zip. The same

file is used for all System Center Manager updates, regardless of whether System
Center Manager runs on Microsoft Windows or Linux. You must install the update
using System Center Manager. Do not unzip the update onto the System Center
Manager application folder.

To update System Center Manager in offline mode

1. On the banner informing you that an update is available, click Start update.

2. The Upload product update System Center dialog box appears. It has a Drag
product update file here area, where you can drop an update and a Select
product update file button that allows you to browse to the location of an
update. It also has a Download the product update file link. You can copy this
link and open it on an Internet-connected computer to download the System
Center Manager update. You will need to log on to My Support to obtain the
update.

3. After you have obtained the update, drag and drop it onto the Upload product
update System Center dialog box or click the Select product update file button
and browse to its location.

4. The Upload product update System Center dialog box displays messages
indicating that System Center Manager is uploading the update and extracting
it. When it has finished these operations, the Update System Center dialog box
appears, informing you that the update is ready to be applied to your system.
Click Update to apply the update.

5. The Update System Center dialog box informs you that System Center
Manager is applying the update. When it is finished, it informs you that your
system has been successfully updated. Click Refresh to refresh the System
Center Manager page that you are on and exit the update procedure.

90 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

Chapter 11

Configure System Center Manager

The majority of System Center Manager settings are accessed on the Settings page.
In some cases, settings are managed in the <System_Center_installation_folder>/
configuration/config.ini file

Note: When you add a Microsoft Windows® file path into a System Center
Manager configuration file, enter it in one of the following manners:

Use forward slashes

For example, C:/cert/cacerts

Use escaped backslashes

For example, C:\\cert\\cacerts

11.1 Settings: General

The General view of the Settings page allows you to enable Online mode and
configure a Session timeout.

Click Save when you make any change to the settings on this page.

Connection
System Center Manager can run in online mode (connected to the Internet) or in
Offline mode (with no Internet connection). Online mode is the default and
OpenText recommends that you operate in online mode, if you can.

Important
If you disable Online mode, special steps are required for updating the System
Center Manager manifest file and downloading Updates. See “Update the
System Center Manager Manifest File” on page 47 and “Download Updates”
on page 47.

To enable or disable Online Mode:

1. Click Settings on the Navigation menu . The General view of the Settings
page opens.

2. Under General Settings, enable or disable Online mode.

3. Click Save.

SYSCM240400-AGD-EN-01 Administration Guide 91

Chapter 11 Configure System Center Manager

Session timeout
If a user session is inactive for the number of minutes specified in the Session
timeout box, the session is invalidated. To continue working, the user must log back
on to System Center Manager.

11.2 Settings: Logs

The Logs view of the Settings page allows you to configure the System Center
Manager Log Level, the HTTP Log Level and Request Logging.

Click Save when you make any change to the settings on this page.

Log Levels
By default, System Center Manager operates with minimal logging. For
troubleshooting, you can increase the log levels.

Log Level
The Log Level menu sets the level of System Center Manager logging. By
default, it is set to Info. To monitor the behavior of System Center Manager or to
troubleshoot an issue, set Log Level to Trace, Debug or Error.
HTTP Log Level
The HTTP Log Level menu sets the level of logging of HTTP messages sent and
received by System Center Manager and the System Center Agent. By default, it
is set to Error. For troubleshooting, set the level to Debug.
Request Logging
Request logs are a record of the requests that the server has processed. By
default, request logging is not enabled, but you can enable it for troubleshooting
purposes. To enable request logging, select the Enable check box and set the
number of days to retain request log files in the Log retention period (days) box.
By default, the log retention period is set to seven days.
Request log files are written to the <System_Center_installation_folder>/
logs/ directory. Each one has a name like requests_<yyyy_mm_dd>.log, for
example requests_2022_02_22.log. A new log file is created each day. At the
end of the log retention period, the oldest request log file is removed and a new
one is started, so with the default retention period of seven days, System Center
Manager will not store more than seven request log files in the logs directory.

For more information on logging for System Center Manager and System Center
Agents, see “System Center Manager and Agent Logging” on page 137.

92 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.3. Settings: Proxy

11.3 Settings: Proxy

The Proxy view of the Settings page allows you to enable and configure a proxy
server for use with System Center Manager.

Click Save when you make any change to the settings on this page.

Proxy Settings
If System Center Manager connects to the Internet through a proxy server, enable
Use a proxy server on the Settings page Proxy view and enter your proxy server’s
address so System Center Manager can update its manifest file and download
Updates over the Internet.

Important
For System Center Manager to operate successfully in online mode, your proxy
server administrator must configure the proxy server to allow System Center
Manager to connect directly to the following external addresses:

• api.otiam.opentext.com
• api.us1.covisint.com
• mimage.opentext.com
• login.opentext.com
• www.opentext.com

Proxy Server Address

Enable Use a proxy server, and then enter the URL and port of your proxy server in
the Server and Port boxes.

Proxy Server Authentication

If your proxy server requires a logon, select Digest or NTLM from the
Authentication type menu. To have System Center Manager store your proxy server
logon credentials, select Store credentials and enter a User name and Password.

Note: If you do not store your proxy server credentials, System Center
Manager will prompt you to provide them whenever you perform an action
that requires it to connect to the Internet, such as updating its manifest,
downloading an Update, or downloading software from the Catalog.

However, when System Center Manager performs an automatic operation that

requires Internet access, it will not prompt you to provide credentials and the
operation will not succeed. For example, without cached proxy credentials,
System Center Manager is unable to automatically update its manifest. If you
operate without cached proxy credentials, you must update the System Center
Manager manifest manually, by clicking Check for updates on the Settings
page, Manifest view.

SYSCM240400-AGD-EN-01 Administration Guide 93

Chapter 11 Configure System Center Manager

Proxy Server Exceptions

If there are servers within your internal network that System Center Manager can
connect to directly, without using your proxy server, enter them in the Exceptions

box and then click the Add button . For example, you could add localhost or
the names of any Systems that run the System Center Agent to the Exceptions
section.

11.4 Settings: Users

You can add, edit, and remove System Center Manager users on the Users view of
the Settings page. You can also unlock a user account, if your deployment of System
Center Manager uses local authentication, for a user who has been locked out of
System Center Manager after exceeding the permitted number of failed logon
attempts. (See “Local Account Policy” on page 111.)

To filter the Users list, click the Filter button and enter a text string in the Search
Id, given name, or surname box that appears in the Settings sidebar.

When you install System Center Manager, it has one user: the built-in Admin user.
The Admin user has unrestricted access to all of the functionality and to every
Solution Environment in System Center Manager, and is the only user that can make
changes to authentication or the manifest URL.

Normally, you should not use System Center Manager logged on as Admin. Instead,
you should create System Center Manager logons, with appropriate access
permissions, for anyone that will use it. You can limit a user’s access permissions in
two ways: by Role and by Solution or Environment.

Role
The scope of a user’s capabilities depends on the user’s role. There are three
roles in System Center Manager:
Administrator
Administrators have unrestricted access to System Center Manager. They
can access every Solution and Environment, and can make changes to any
System Center Manager setting.

Tip: Users that are assigned the Administrator role can do anything
that the built-in Admin user can do, except for modifying settings on
the Authentication or Manifest views of the Settings page.
Solution Manager
Solution Managers can manage any Solution that they are assigned, and can
manage any Environment within the Solution. They can add, modify, and
remove Environments in the Solutions that they are assigned.
On the Settings page, Solution Managers have access to the Audit, Agents,
Solutions, External Vendor Files and Manifest views, but not the General,

94 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.4. Settings: Users

Users and Authentication tabs. They can only view data and make changes
for the Solutions that they manage.
Environment Manager
Environment Managers can manage any Environment that they are
assigned. They can view Execution Plans that are created in their
Environment’s Solution, and they can edit Execution Plans that are created
in their Environment.
On the Settings page, Environment Managers have access to the Audit,
Agents, Solutions, External Vendor Files and Manifest views, but not the
General, Users and Authentication tabs. They can only view data and make
changes for the Environments that they manage.

Permissions
Users have access only to the Environments and Solutions that they manage.
They can only access data or settings that belong to their Solutions and
Environments. For example, they can edit an Execution Plan only if they have
access to the plan’s Environment, and they can only view Audit events from the
Solutions or Environments that they manage.

Note: System Center Manager can perform all of its user management itself or
it can delegate most of its user management functions to OpenText Directory
Services. For information on integrating OpenText Directory Services, see
“Settings: Authentication” on page 109.

11.4.1 Add Users

The steps to add a user vary slightly depending on whether you use local
authentication or OTDS authentication. Use the procedure that applies to your
deployment.

11.4.1.1 Add a Locally Authenticated User

When you add a locally authenticated user, you specify all of the user settings in
System Center Manager.

To add a locally authenticated user to System Center Manager:

1. Open the Settings page: Users view.

a. Click Settings on the Navigation menu .

b. Click Users under Settings on the left.

2. Click the Add item button .

3. The information that you need to provide is entered on two tabs: General and
Permissions.
On the General tab, enter the following information.

SYSCM240400-AGD-EN-01 Administration Guide 95

Chapter 11 Configure System Center Manager

• Enter an email address in the Id box.

• In the Role box, select either Administrator, Solution Manager, or
Environment Manager.
• Enter the user’s Given Name and Surname.
• Enter and confirm a password for the user.
4. On the Permissions tab, depending on the user’s role, assign the user access to
Solutions or Environments.

Solution Manager
Select one or more of the listed Solutions. Users will be able to view and
manage any Solutions that they are assigned, and will have access to every
Environment within those Solutions.
Environment Manager
Select a Solution Environment from the listed Environments. Users will be
able to view and manage any Environments that they are assigned.

11.4.1.2 Add an OTDS User

When you add an OTDS user, most of the user’s properties are controlled by OTDS,
but you must assign the user a Role in System Center Manager and provide the user
with access to at least one Environment (for an Environment Manager) or Solution
(for a Solution Manager).

To add an OTDS user to System Center Manager:

1. Open the Settings page: Users view.

a. Click Settings on the Navigation menu .

b. Click Users under Settings on the left.

2. Click the Add item button .

3. On the General tab:

• Select a user from OTDS. You can start typing in the Directory services user
name box, which will update to show the available users, filtered by your
text string.
• In the Role box, select either Administrator, Solution Manager, or
Environment Manager.
4. On the Permissions tab, assign the user access to Solutions or Environments.

Solution Manager
Select one or more Solutions on the Assigned Solutions page. Users will be
able to view and manage any Solutions that they are assigned, and every
Environment within those Solutions.

96 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.4. Settings: Users

Environment Manager
Select a Solution Environment from the Assigned Environments page.
Users will be able to view and manage any Environments that they are
assigned.

11.4.2 Edit a User

To edit a user, open the user’s properties on the Users view of the Settings page.
When you edit users, you can change their role to Administrator or Solution
Manager, and you can assign them access to additional Environments or remove
access to Environments that they currently manage.

To edit a user:

1. Open the Settings page: Users view.

a. Click Settings on the Navigation menu .

b. Click Users under Settings on the left.

2. Access the user setup page in one of the following ways:

• Select a user and click Edit at the top of the user list.

• Click the Edit button in the user’s Inline Actions Bar.

3. The user setup page appears. Make changes on the General and Permissions
tabs, as required.

General tab
To change the user’s role, select a role from the Role menu.
To assign a new password to a user, enter the new password in the
Password and Confirm Password boxes.
Permissions tab
To assign access to a new Solution or Environment, select it on the
Permissions tab.
To remove access to an existing Solution or Environment, clear its check
box.

4. Click Save to save your changes.

SYSCM240400-AGD-EN-01 Administration Guide 97

Chapter 11 Configure System Center Manager

11.4.3 Remove a User

To remove a user, select the user on the Users view of the Settings page, and then
click Remove.

To remove a user:

1. Open the Settings page: Users view.

a. Click Settings in the global menu bar.

b. Click Users under Settings on the left.

2. Delete the user in one of the following ways:

• Select a user and click Remove at the top of the user list.

• Click the Remove button in the user’s Inline Actions Bar.

3. The Remove dialog box appears. Click Remove.

11.4.4 Unlock a User

If your System Center Manager deployment uses local authentication, an Unlock
operation is available for each user. (If you are using OTDS authentication, the link
does not appear.)

If a user account has been locked because of successive logon failures that exceeded
the Account Logon Threshold, you can unlock the account in one of the following
ways:

• Select a user and click Unlock at the top of the user list.
•
Click the Unlock button in the user’s Inline Actions Bar.

The Unlock dialog box appears. Click Unlock.

Notes

• You must be a user with the Administrator role, or be logged on as the

Admin user, to unlock a user account.
• For information on the Account Logon Threshold, see “Local Account
Policy” on page 111.

98 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.4. Settings: Users

11.4.5 Reset a User’s Password

You can reset the password of a user who has forgotten it. The exact procedure to
follow depends on your method of authentication (OTDS or local authentication)
and the kind of user whose password needs to be reset (normal System Center
Manager user or the built-in Admin user).

If you use OTDS for authentication, you can reset a user’s password in OTDS. Refer
to the OTDS online help for information on how to do this. If you need to reset the
password of the Admin user, however, you cannot do it through OTDS. For the
Admin user, follow the security token procedure described below.

For a normal System Center Manager user who has forgotten their password, you
have two ways of resetting the user’s password.

Assign a temporary password in System Center Manager

Reset the user’s password as described in “Edit a User” on page 97.
Have the user request a security token
When a user clicks Forgot Password? on the System Center Manager logon
page, the Reset your password dialog box appears, and prompts the user to
request a security token by providing their logon ID. When the user does,
System Center Manager generates a security token in the
securityTokensubfolder of the System Center Manager application directory.
You can send the security token to the user, who can use it to create a new
password. Once the user successfully creates a new password, the security token
is removed from the file system.
The security token is valid for 5 minutes. If the security token expires before the
user creates a new password, the user can request a new security token and
restart the password reset procedure. When System Center Manager generates a
new security token for a user, it overwrites any existing security token for that
user.
Important

• To retrieve a security token, you must have access to the file system on
the System Center Manager server.
• Only the Admin user can change the Admin user’s password. If the
Admin user’s password has been forgotten, the only way to reset it is
by using a security token.

SYSCM240400-AGD-EN-01 Administration Guide 99

Chapter 11 Configure System Center Manager

11.4.5.1 Reset a Password using a Security Token

The procedure to reset a password using a security token involves two parties:

• A System Center Manager user who needs to reset a password.

• A System Center Manager administrator who can retrieve the security token
from the file system on the System Center Manager server.

To reset a password using a security token.

1. As a System Center Manager user, request a security token, as follows:

a. Inform a System Center Manager administrator that you are resetting your
password and that you will need assistance. (The security token expires in
5 minutes. If you do not use it before it expires, you will need to request a
new one.)

b. On the System Center Manager logon page, click Forgot Password?.

c. You are prompted to enter your user ID (email address). Click Continue.

Note: When you click Continue, a security token is generated on the

file system of the System Center Manager server. If you are returning
to this page because you now have a security token, select the I
already requested a security token check box before you click
Continue so that you can proceed to the next page without generating
a new security token.

d. You are prompted to enter your Security Token and a new password. Once
you receive the security token from your System Center Manager
administrator, enter it in the Security Token box, then enter your new
password in the Password and Confirm password boxes. Click Reset
password to complete the operation.

2. When a user requests a security token, System Center Manager generates a file
that contains the token. As an administrator who has access to the local file
system on the System Center Manager server, retrieve the user’s security token,
as follows:

a. Browse to the securityToken folder in the System Center Manager

application directory.

b. Open the file whose name contains the user’s name. For example, for a user
named [email protected], open the file named [email protected]. The
security token is written inside this file.

c. Send the security token to the user. The user can then reset their password
as described in step 1d above.

100 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.5. Settings: Audit

11.5 Settings: Audit

The Settings page Audit view displays a record of activities performed by or within
System Center Manager.

To page through the audit records, use the controls at the bottom of the page. To
restrict the listing of audit records to a specific event of interest, click the filter button

. The Refine by area in the Settings sidebar contains menus and boxes that
allow you to filter by Event type, Solution, Environment, Description, User and
Date.

11.6 Settings: Agents

To bring a System under the control of System Center Manager, install the System
Center Agent on it. The System Center Agent communicates with System Center
Manager and updates the System under the direction of System Center Manager.
After you complete the installation of the Agent, the System appears in System
Center Manager and can be registered. (See “Register and Unregister Systems”
on page 23.)

You can download the Agent installation software from the Agents view of the
Settings page.

11.6.1 Install the System Center Agent on Windows

To install the System Center Agent on a Windows host machine, run the System
Center Agent installation file (OpenText_SystemCenter_Agent.msi). Ensure that the
Agent computer is able to connect to the System Center Manager computer during
the installation. You have the choice of running the installation as a Windows
PowerShell script, performing an interactive installation, or running a silent
installation by providing all required information in the installation command.

11.6.1.1 Scripted Installation of the System Center Agent

You can install the System Center Agent by running the PowerShell script that
appears on the Agents view of the Settings page. The script includes values that
refer to your System Center Manager host computer and settings.

Tip: If desired, you can customize the PowerShell script by modifying the
msiexec.exe command arguments that appear between double quotation
marks immediately after -ArgumentList. For information on these command
line arguments, see “Unattended Installation of the System Center Agent”
on page 103.

To install the System Center Agent using a PowerShell script:

1. Copy the installation script.

a. In System Center Manager, open the Agents view of the Settings page.

SYSCM240400-AGD-EN-01 Administration Guide 101

Chapter 11 Configure System Center Manager

i. Click Settings on the Navigation menu .

ii. Click Agents under Settings on the left.

b. Beside the PowerShell script, click the Copy to clipboard button .

2. Run the PowerShell script on the computer that you want to add to System
Center Manager as a System.

a. Run PowerShell as Administrator.

b. Paste the script that you copied from the Agents view of the Settings page
into PowerShell and execute it.

11.6.1.2 Interactive Installation of the System Center Agent

In an interactive installation of the System Center Agent, you provide required
information in the dialog boxes of the installation wizard.

To install the System Center Agent interactively:

1. Download the Agent for Windows from your installation of System Center
Manager.

a. In System Center Manager, open the Agents view of the Settings page.

i. Click Settings on the Navigation menu .

ii. Click Agents under Settings on the left.
b. In the Agent for Windows area, click OpenText_SystemCenter_Agent.msi
and save the OpenText_SystemCenter_Agent.msi file so that you can use it
to install the System Center Agent on a Windows host that runs OpenText
software..

Tip: If you open System Center Manager on the computer where you want
to install the System Center Agent, you can download the installation file
directly to the correct computer and run the installation immediately.

2. Copy the OpenText_SystemCenter_Agent.msi file to a Windows computer that

runs supported OpenText software.

3. Run the System Center Agent installation file (OpenText_SystemCenter_Agent.

msi). When the Welcome to the OpenText System Center Agent Installation
dialog box appears, click Next. When the License Agreement dialog box
appears, enable I accept the terms in the License Agreement, and then click
Next.

4. On the OpenText System Center Manager Configuration: base parameters

dialog box, enter the Http Server Name and Http Port number of the System
Center Manager host computer.

102 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.6. Settings: Agents

5. On the Destination Folder dialog box, enter the folder that will contain the
System Center Agent program files, or accept the default (C:\OpenText\
OpenText System Center Agent <##.#.#>\). Click Next.

6. On the Ready to Install dialog box, click Install. The Installing the Product
dialog box appears and shows the progress of the installation.

7. When the installation completes successfully, the Completing the OpenText

System Center Agent Installation dialog box appears. Click Finish.

11.6.1.3 Unattended Installation of the System Center Agent

In an unattended installation of the System Center Agent, you provide required
information in the options of the installation command. Open a command prompt as
Administrator and run the following command on the computer where you want to
install the System Center Agent:

MsiExec.exe /qn /l*vx <installer_log_file_name> /i <System_Center_Agent_

installer_file_name> INSTALLDIR=<Agent_installation_directory> HTTP_PORT_
NUMBER="<System_Center_Manager_port>" SERVER_NAME="<System_Center_
Manager_server>"

In the above command, replace the strings in angle brackets as follows:

<installer_log_file_name>
The path of the installer’s log file. For example, C:\AgentInstall.log.

<System_Center_Agent_installer_file_name>
The path of the System Center Agent installer. For example, C:\Installers\
OpenText_SystemCenter_Agent.msi

<Agent_installation_directory>
The directory where you want to store the System Center Agent program files.
For example, C:\SystemCenter\OpenText System Center Agent\

<System_Center_Manager_port>
The port that the System Center Manager server uses to communicate. By
default it is 8888.

<System_Center_Manager_server>
The network name of the System Center Manager host computer. For example,
scm.example.com

For example, to silently install the System Center Agent on a computer using all of
the example values from above, run the following command:

MsiExec.exe /qn /l*vx C:\AgentInstall.log /i C:\Installers\OpenText_

SystemCenter_Agent.msi INSTALLDIR="C:\SystemCenter\OpenText System Center
Agent\" HTTP_PORT_NUMBER="8888" SERVER_NAME="scm.example.com"

SYSCM240400-AGD-EN-01 Administration Guide 103

Chapter 11 Configure System Center Manager

11.6.2 Install the System Center Agent on Linux

There are several ways to install the System Center Agent interactively on a Linux
System:

• Execute an installation script on the System Center Agent host computer

• Download SystemCenter_Agent.sh and execute it on the System Center Agent
host computer to perform an interactive installation.
• Extract and run install_otsystemcenteragent.sh on the System Center Agent
host computer to perform an interactive installation.

You can use SystemCenter_Agent.sh or install_otsystemcenteragent.sh by

including required parameters in an answer file that you pass to the script.

The resulting installation is identical, whichever method you choose.

The Landscape directory

During the installation of the System Center Agent, the installer attempts to write a
solution registry file to the /etc/opentext/landscape/ directory. This solution
registry file is used by other OpenText products to obtain information about System
Center Manager. In particular, it is used by the OpenText Solution Registry Agent to
help OpenText products to integrate with SAP.

If the user running the System Center Agent installer does not have access to the /
etc/opentext/landscape/ directory, the following message appears during the
installation:
Unable to create the landscape directory '/etc/opentext/landscape'.
The solution registry file is saved in <System_Center_Agent_home> instead.
It's recommended that the solution registry file be copied to '/etc/opentext/landscape'
directory for use by other OpenText products.

This message does not indicate an installation failure, but you can prevent it from
appearing by ensuring that the user that runs the System Center Agent installer can
create the /etc/opentext/landscape/ directory and write to it. If the message does
appear, you can copy the solution registry file from your
<System_Center_Agent_home> directory to the /etc/opentext/landscape/ directory
after the installation completes. This produces the same result as having the System
Center Agent installer create the file in the /etc/opentext/landscape/ directory
during the installation.

Tip: The solution registry file has a name similar to 20181127101110-

SYSTEMCENTERAGT-Install.ini.

104 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.6. Settings: Agents

11.6.2.1 Install the System Center Agent using the Installation Script
To install the System Center Agent by running the installation script:

1. Obtain the command that runs the script file.

a. In System Center Manager, open the Agents view of the Settings page.

i. Click Settings on the Navigation menu .

ii. Click Agents under Settings on the left.

b. Beside the bash script, click the Copy to clipboard button .

2. On the System Center Agent host computer, log on as the user that will run the
System Center Agent and execute the script.

Tip: To allow the System Center Agent the greatest flexibility in

performing operations, install it logged on as root.

The following messages appear:

Downloading System Center Agent from server...
Download successful.
Install System Center agent to /usr/local/OpenText/OpenText_System_Center_Agent? y/
n:

3. To accept the default location, press y. (Otherwise, press n and specify an

alternative location.) The installation of the System Center Agent commences.
The following messages appear:

Extracting OpenText_SystemCenterAgent.tar.gz...
Starting System Center Agent ...
System Center Agent is started.
Installation completed and Agent started.
Installation location is <System_Center_Agent_installation_directory>.

4. When the console displays Install Agent as Service? y/n:, type y to to install
the System Center Agent as a service. Enter n to have the System Center Agent
installed as a program that must be started and stopped manually.

SYSCM240400-AGD-EN-01 Administration Guide 105

Chapter 11 Configure System Center Manager

11.6.2.2 Install the System Center Agent using the

SystemCenter_Agent.sh File
To install the System Center Agent using the SystemCenter_Agent.sh file:

1. Download the Agent for Linux from your installation of System Center
Manager.

a. In System Center Manager, open the Agents view of the Settings page.

i. Click Settings on the Navigation menu .

ii. Click Agents under Settings on the left.
b. In the Agent for Linux area, click the SystemCenter_Agent.sh link and
download the SystemCenter_Agent.sh file.

2. On the System Center Agent host computer, log on as the user that will run the
System Center Agent.

Tip: To allow the System Center Agent the greatest flexibility in

performing operations, install it logged on as root.

Open a terminal and copy the SystemCenter_Agent.sh file to a Linux computer

that runs supported OpenText software.

3. Make the SystemCenter_Agent.sh file executable by running the following

command: chmod 755 SystemCenter_Agent.sh

4. Start the installation by executing the installation file: ./SystemCenter_Agent.

sh. The following messages appear:
Downloading System Center Agent from server...
Download successful.
Extracting OpenText_SystemCenterAgent_Linux.tar.gz...
Starting installation of System Center Agent for Linux.
Install System Center agent to /usr/local/OpenText/OpenText_System_Center_Agent? y/
n:

5. To accept the default location, press y. (Otherwise, press n and specify an

different location.) The installation of the System Center Agent commences.
The following messages appear:
Extracting OpenText_SystemCenterAgent.tar.gz...
Starting System Center Agent ...
System Center Agent is started.
Installation completed and Agent started.
Installation location is <installation directory>
Installing Agent as Service requires elevated privileges.
Note: The agent will be running as <current user>

6. When the console displays Install Agent as Service? y/n:, type y to to install
the System Center Agent as a service. Enter n to have the System Center Agent
installed as a program that must be started and stopped manually.

106 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.6. Settings: Agents

11.6.2.3 Install the System Center Agent using the

install_otsystemcenteragent.sh File
To install the System Center Agent using install_otsystemcenteragent.sh:

1. Obtain OpenText_SystemCenterAgent_Linux.tar.gz from the OpenText_

SystemCenter_Agent subdirectory of the System Center Manager application
directory.

2. Log on to the System Center Agent host computer as the user that will run the
System Center Agent.

Tip: To allow the System Center Agent the greatest flexibility in

performing operations, install it logged on as root.

Copy OpenText_SystemCenterAgent_Linux.tar.gz to the System Center Agent

host computer.

3. Extract install_otsystemcenteragent.sh and OpenText_SystemCenterAgent.

tar.gz from OpenText_SystemCenterAgent_Linux.tar.gz.

4. Start the installation by executing the installation file: install_

otsystemcenteragent.sh. The following messages appear:
Starting installation of System Center Agent for Linux.
Install System Center agent to /usr/local/OpenText/OpenText_System_Center_Agent? y/
n:

5. To accept the default location, press y. (Otherwise, press n and specify a

different location.) The installation of the System Center Agent commences.

6. The installer prompts you to enter the hostname of the Manager. Enter the
name of the System Center Manager host computer.

7. The installer prompts you to enter the HTTP port number of the Manager. Press
ENTER to accept the default port (8888) or enter a different port number. The
following messages appear:
Extracting OpenText_SystemCenterAgent.tar.gz...
Starting System Center Agent ...
System Center Agent is started.
Installation completed and Agent started.
Installation location is <installation directory>
Installing Agent as Service requires elevated privileges.
Note: The agent will be running as <current user>

8. When the console displays Install Agent as Service? y/n:, type y to to install
the System Center Agent as a service. Enter n to have the System Center Agent
installed as a program that must be started and stopped manually.

SYSCM240400-AGD-EN-01 Administration Guide 107

Chapter 11 Configure System Center Manager

11.6.2.4 Unattended Installation using the SystemCenter_Agent.sh File

To perform an unattended installation of the System Center Agent using
SystemCenter_Agent.sh, provide the answers to the prompts in a file, and then pass
the contents of the file to the installer.

To perform an unattended installation of the System Center Agent using

SystemCenter_Agent.sh:

1. Download the Agent for Linux from your installation of System Center
Manager.

a. In System Center Manager, open the Agents view of the Settings page.

i. Click Settings on the Navigation menu .

ii. Click Agents under Settings on the left.
b. In the Agent for Linux area, click the SystemCenter_Agent.sh link and
download the SystemCenter_Agent.sh file.

2. On the System Center Agent host computer, log on as the user that will run the
System Center Agent.

Tip: To allow the System Center Agent the greatest flexibility in

performing operations, install it logged on as root.

Open a terminal and copy the SystemCenter_Agent.sh file to a Linux computer

that runs supported OpenText software.

3. Make the SystemCenter_Agent.sh file executable by running the following

command: chmod 755 SystemCenter_Agent.sh

4. Run the installation and pass required information to the installer in an answer
file. For example, run SystemCenter_Agent.sh < <answer_file>

Example: To install the System Center Agent to a non-default directory and configure it to
run as a service, the answer file should have contents similar to the following:
n
/usr/local/scm_agent
y

108 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.7. Settings: Authentication

11.6.2.5 Unattended Installation using the install_otsystemcenteragent.sh

File
To perform an unattended installation of the System Center Agent using the
install_otsystemcenteragent.sh, provide the answers to the prompts in a file, and
then pass the contents of the file to the installer. When you use this file to install the
System Center Agent, you must specify the System Center Manager host name and
port in your answer file.

To perform an unattended installation of the System Center Agent using

install_otsystemcenteragent.sh:

1. Obtain OpenText_SystemCenterAgent_Linux.tar.gz from the OpenText_

SystemCenter_Agent subdirectory of the System Center Manager application
directory.

2. Log on to the System Center Agent host computer as the user that will run the
System Center Agent.

Tip: To allow the System Center Agent the greatest flexibility in

performing operations, install it logged on as root.

Copy OpenText_SystemCenterAgent_Linux.tar.gz to the System Center Agent

host computer.

3. Extract install_otsystemcenteragent.sh and OpenText_SystemCenterAgent.

tar.gz from OpenText_SystemCenterAgent_Linux.tar.gz.

4. Run the installation and pass required information to the installer in an answer
file. For example, run install_otsystemcenteragent.sh < <answer_file>

Example: To install the System Center Agent to a non-default directory and configure it to
not run as a service, the answer file should have contents similar to the following:
n
/usr/local/OT/SC/SCagt
SCMhost.example.net
8888
n

11.7 Settings: Authentication

On the Authentication view of the Settings page, you can set the authentication
method for System Center Manager to either local authentication or OpenText
Directory Services (OTDS). You can also configure the settings for account lockouts:
how many bad password attempts cause an account lockout and how long the
account lockout lasts.

SYSCM240400-AGD-EN-01 Administration Guide 109

Chapter 11 Configure System Center Manager

11.7.1 Authentication Method

By default, System Center Manager uses local authentication. Alternatively, you can
integrate System Center Manager with OpenText Directory Services. To do so, log
on to System Center Manager as the Admin user and enable OpenText Directory
Services on the Authentication view of the Settings page.

Important
You must be logged on as the Admin user to change the authentication method
used by System Center Manager.

Note: Regardless of how you manage users in System Center Manager, you
can always log on as the Admin user, whose password is specified during the
installation of System Center Manager.

To enable integration with OTDS, provide the address of your OTDS server and the
Resource Identifier of the Resource that represents System Center Manager in OTDS.

Tip: The Resource Identifier is available in OpenText Directory Services in the

Properties of the Resource. The OTDS Resource that you use for System Center
Manager must be inactive before you enable OTDS authentication. It will be
activated when you connect to it from System Center Manager. Ensure that the
OTDS Resource for System Center Manager does not use User and group
synchronization and does not create or modify users and groups. For more
information, see OpenText Directory Services - Installation and Administration
Guide (OTDS-IWC).

When you enable OpenText Directory Services as your authentication provider, you
specify an OTDS group that contains System Center Manager administrators. You
can select an existing OTDS group for this purpose, or one that has been created
specifically to contain System Center Manager users.

To enable System Center Manager to use OpenText Directory Services

1. Logged on as the Admin user, on the Authentication view of the Settings page,
enable OpenText Directory Services.

2. Configure the OTDS settings.

a. In the Server URL box, enter the URL of your OTDS server, for example:
http://myotds.example.net:8080

b. In the Resource Identifier box, enter the Resource Identifier of your OTDS
system, for example: 7ad3ea31-9131-4f31-b7e6-ef5d7123fb09
c. Click Test Connection to verify your settings.
d. After the test connection completes successfully, click Activate resource.

3. Select a group from the Administrators group menu.

110 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.8. Settings: Solutions

After you have enabled OTDS as your authentication provider, you must still assign
OTDS users to a System Center Manager role and to one or more System Center
Manager Solutions or Environments. See “Add an OTDS User” on page 96.

11.7.2 Local Account Policy

If you have configured System Center Manager to use local authentication, you can
configure Local Account Policy settings. (Local Account Policy settings do not
appear if you use OTDS for authentication. You can set similar policies on the OTDS
server.)

Local Account Policy settings determine how many successive times a user can fail
a logon attempt before being locked out and how long an account lockout lasts. To
change Local Account Policy settings, you must be a user with the Administrator
role, or be logged on as the Admin user.

The default value of the Account lockout duration is 15 minutes. You can set it to a
number from 1 to 60. When the Account Lockout period expires, the locked-out user
account can attempt to log on again. You can also unlock an account on the Users
view of the Authentication page to allow the user to log on immediately. See
“Unlock a User” on page 98.

The default value of the Account Lockout Threshold is 3. You can set it to a number
from 1 to 10. If a user fails a logon attempt more times in a row than the value of the
Account Lockout Threshold, the user is locked out for the Account lockout
duration.

11.8 Settings: Solutions

Your view of System Center Manager, including the Products and Systems that you
can manage, is determined by your current Solution Environment. If you are an
Administrator, you can add, edit, and remove Solutions and Environments. You can
also export Solutions for use in other installations of System Center Manager.

A Solution is used to group Environments that implement a similar software service.

A typical use case is to create a Solution to group Environments that deliver a
software service consisting of similar Products and third-party applications for a
specific group of users. For example, you may create a Solution to deliver Content
Server for a specific department within your organization or OpenText Directory
Services for a specific customer. Within such Solutions, you can create various
Environments, such as QA, UAT, and Production. As an Administrator, you can then
assign Solution Managers to one or more of these environments.

For more information on Solutions and Environments, see “Solutions and

Environments“ on page 17.

SYSCM240400-AGD-EN-01 Administration Guide 111

Chapter 11 Configure System Center Manager

11.8.1 Add, Edit and Remove Solutions

Solutions are added, modified, and removed on the Solutions view of the Settings
page.

11.8.1.1 Add a Solution

To add a Solution, open the Solutions view of the Settings page, and then click the

Add item button . When the Add Solution page appears, enter a Solution name
and, optionally, a description, and then click Add.

The Solution now appears on the Solutions view, with a warning icon
indicating that the Solution does not yet have any Environments assigned to it. For
information on adding an Environment to a Solution, see “Add an Environment”
on page 115.

11.8.1.2 Modify a Solution

You can modify a Solution by changing its name or description, or by adding,
modifying, and removing the Environments that belong to the Solution.

• To edit the Name or Description of a Solution, do one of the following:

– Select a Solution and click Edit at the top of the Solution list.
–
Click the Edit button in the Solution’s Inline Actions Bar.
• To add an Environment to a Solution, see “Add an Environment” on page 115
• To modify one of the Solution’s Environments, see “Modify an Environment”
on page 115.
• To remove an Environment from a Solution, see “Delete an Environment”
on page 116.

11.8.1.3 Delete a Solution

To delete a Solution, do one of the following:

• Select a Solution and click Delete at the top of the Solution list.
•
Click the Edit button in the Solution’s Inline Actions Bar.

click the Delete button beside the Solution’s name.

The Delete dialog box appears and informs you of the number of Environments,
Systems, and users who are associated with the Solution. Click Delete to proceed to
delete the Solution.

112 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.8. Settings: Solutions

Systems that are associated with a deleted Solution are returned to unregistered
status and can be registered again on the Systems page. See “Register and
Unregister Systems” on page 23.

11.8.2 Export and Import Solutions

You can export a Solution for use in other installations of System Center Manager.
An exported Solution includes the Solution’s Environments, the Execution Plans that
belong to the Environments, and optionally the files that are used by the Execution
Plans. To use an exported Solution in another installation of System Center
Manager, you can import it.

A Solution is exported as a ZIP archive that contains:

• Execution Plans in a plans subfolder

• Product installer files in a productFiles subfolder
• External Vendor Files in an extVenFiles subfolder
• A solution.json file that describes the exported Solution, including the
Environments and Systems that are part of the Solution

1. The subfolders are present only if the Solution actually includes items of
that type. For example, if the Solution does not contain any External
Vendor Files, the extVenFiles subfolder is not included in the Solution ZIP
archive.
2. Patches are not included in an exported Solution. Only files that are
referenced in an Execution Plan are included in the Solution export.

11.8.2.1 Export a Solution

Exporting a Solution allows you to re-use a Solution from your current System
Center Manager in a different installation of System Center Manager.

Presume, for example, that you manage Content Server for a number of distinct
customers. You have developed a Content Server Solution that includes multiple
Content Server Environments and various Execution Plans that you use for
installing, configuring, and maintaining Content Server. You export this Solution
and import it into your customer’s System Center Manager installation, and then
you use the Environments and Execution Plans in it to set up and maintain the
customer’s Content Server deployment. This allows you to use the same tested and
repeatable procedures for each of your Content Server customers.

To export a Solution:

1. Open the Solutions view of the Settings page.

2. Initiate the Solution export in one of the following ways:

• Select a Solution and click Export at the top of the Solution list.

SYSCM240400-AGD-EN-01 Administration Guide 113

Chapter 11 Configure System Center Manager

• Click the Export button in the Solution’s Inline Actions Bar.

3. The Export Solution dialog box appears, informing you of the number of
Environments, Execution Plans, and files associated with the Solution. Click
Export.

4. When the Solution package is ready, the Export solution dialog box appears.
Click Download. Your browser downloads the Solution package.

11.8.2.2 Import a Solution

When you import a Solution, you add its Environments and Execution Plans to your
current System Center Manager installation. You also add any associated files
(Products and External Vendor Files) that are included with the Solution, unless
they already exist on the target System Center Manager. During the import
procedure, you can modify the Solution’s name and description and the names and
descriptions of the Solution Environments.

To import a Solution:

1. Open the Solutions view of the Settings page.

2. Click the Upload button

3. To begin the import, either:

• Click Add file, then browse to a Solution package and select it, or
• Drag the Solution package onto the Upload side panel.

4. The Import solution page appears. Click each tab in the Details area to learn
about the Environments, Systems, Execution Plans, External Vendor Files, and
Products that are included in the Solution package.
When you import a Solution, you must provide it with a Name. You can also
modify some of the Solution’s attributes:

• You can change the Solution’s Description.

• On the Environments tab, you can change the Name and Description of
each Environment included in the Solution.
Pending Systems that are available to be registered appear below the
Environment names and descriptions. To automatically register a pending
System, select an Environment from the Environment menu. To leave the
System in a pending state, leave the Environment unselected.
• On the Plans tab, you can change the Environment that an Execution Plan
belongs to by selecting it from the Environment menu.

Tip: The names in the Environment menu reflect any changes that you
make on the Environments tab.

114 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.8. Settings: Solutions

5. Click Import.

11.8.3 Add, Edit and Remove Environments

Environments are created within a Solution, and cannot exist independently of their
Solution. Environments are added, modified, and removed on the Solutions view of
the Settings page.

11.8.3.1 Add an Environment

To add an Environment, complete the steps below.

To add an Environment:

1. Open the Solutions view of the Settings page, select a Solution to modify in one
of the following ways::

• Select a Solution and click Environment at the top of the Solutions list.

• Click the Environment button in the Solution’s Inline Actions Bar.

2. In the Environments area, click the Add item button .

3. On the Add environment page, enter a name and optionally a description. Click
Add.

Tip: Environment names must be unique within a Solution, but can be re-used
in another Solution

11.8.3.2 Modify an Environment

You can modify an Environment by changing its name or description, or by
removing it from the Solution that it belongs to.

To change the name or description of an Environment:

1. Open the Solutions view of the Settings page, select a Solution to modify in one
of the following ways::

• Select a Solution and click Environment at the top of the Solutions list.

• Click the Environment button in the Solution’s Inline Actions Bar.

2. Open the Edit <Environment_Name> page in one of the following ways:

• Select an Environment and click Edit at the top of the Environments list.

• Click the Edit button in the Environment’s Inline Actions Bar.

SYSCM240400-AGD-EN-01 Administration Guide 115

Chapter 11 Configure System Center Manager

3. Change the name and description of the Environment, and then click Save.

•
To edit the name or description of an Environment, click the Edit icon .
• To remove an Environment from a Solution, see “Delete an Environment”
on page 116.

11.8.3.3 Delete an Environment

You can delete an Environment by removing it from the Solution that it belongs to.

To change the name or description of an Environment:

1. Open the Solutions view of the Settings page, select a Solution to modify in one
of the following ways::

• Select a Solution and click Environment at the top of the Solutions list.

• Click the Environment button in the Solution’s Inline Actions Bar.

2. Delete the Environment in one of the following ways:

• Select an Environment and click Delete at the top of the Environments list.

• Click the Delete button in the Environment’s Inline Actions Bar.

3. The Delete dialog box appears and informs you of the number of Systems and
users that are associated with the Environment. Click Delete to delete the
Environment.

11.8.4 Synchronize Solution Environments

In many organizations, system administrators configure and update software
products following a defined sequence. Initially, they configure and patch the
software product in a development environment. Then, when their work is done
and the software product is performing well, they promote their changes to a testing
environment, where different workers verify that the software continues to function
properly. If the testers find problems, they send the work back to the system
administrators for resolution. The system administrators resolve the problems in the
development environment, and then return the amended software product to the
testing environment for another round of testing. After multiple iterations, the work
is pronounced ready, and it is deployed in a production Environment.

System Center Manager supports this kind of workflow by allowing you to

synchronize Solution Environments. When you synchronize a Product that exists in
one Solution Environment with the same Product in another Environment, System
Center Manager analyzes the source and target Environments, and then configures
the target Product so that it has the same Updates that it has in the source
Environment. In other words, it brings the target Product up to the same “patch
level” as the source Product.

116 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.8. Settings: Solutions

Applying Updates by synchronizing a Product in two Environments is not

fundamentally different from applying Updates that you have selected manually.
(For information on applying Updates, see “Apply Updates” on page 50.) The
principal difference between the two operations is that, in a synchronization
operation, the Updates to apply are not selected by hand. They are selected
automatically by System Center Manager after analysis and comparison of the
Product configuration in the two Environments.

Tip: Currently, System Center Manager supports synchronizing the Content

Server Product using the Synchronize Patch installation synchronization type,
which synchronizes Updates, patches, and language packs. Additional
Products and synchronization types will be added in the future.

The Synchronize a product between environments function is available on the

Solutions view of the Settings page.

Before it synchronizes a Product between Environments, System Center Manager

analyzes the source and target Environments to ensure that is able to successfully
synchronize the two Environments. Depending on what it finds, System Center
Manager may display several different sorts of warnings.

Discrepancies between the Environments

System Center Manager may display a warning that, compared with the source
Environment, the Product in the target Environment has missing or additional
modules, additional or unknown patches, or custom language packs. In many
cases, this is an indication that you should stop the synchronization, investigate
why the Products in the two Environments differ, and make changes to bring
them into alignment. However, in some cases, you may be aware of the noted
difference and confident that it will not prevent the synchronization from
completing successfully. That is why the warning also includes a check box that
allows you to acknowledge the differences between the two Environments and
proceed with the synchronization.

Nothing to do
You may receive a notification that there is nothing to do because the Products
are already synchronized. This could happen if the Products are identical, but it
could also happen if, for example, the Product in the target Environment has one
more patch than the Product in the source Environment. In such a case, the
synchronization does not remove the extra patch from the target Environment.
Instead, System Center Manager informs you that there is nothing to do because
the Products are already synchronized.

Missing Packages
System Center Manager may inform you that a required package has not been
downloaded or that it encountered an error during the download of a required
package. If you see this message, click Continue. How you proceed after this
depends on whether you operate in online mode or not.
If you operate in online mode, System Center Manager displays the Confirm
download dialog box. Log on to My Support to download the missing patch.

SYSCM240400-AGD-EN-01 Administration Guide 117

Chapter 11 Configure System Center Manager

After the download has completed, restart Synchronize a product between

environments.
If you operate in offline mode, System Center Manager displays the Upload
missing packages. To continue, obtain the missing package and add it to System
Center Manager. After the dialog box displays The package(s) have been
successfully uploaded, you can click Continue to proceed with the
synchronization operation. For more information on obtaining packages in
offline mode, see OpenText System Center Manager - Administrator Online Help
(SYSCM-H-AGD).
Alternatively, System Center Manager may inform you that a required package
could not be validated because it is currently being downloaded. If you receive
this message, click Cancel and retry the synchronization after the download
completes.

11.8.4.1 Synchronize Two Content Server Environments

To synchronize the Updates, patches, and language packs that are deployed on
Content Server Product Instances in two different Environments from the same
Solution, follow the steps below.

To synchronize two Content Server Environments

1. On the Solutions tab of the Settings page, to select the Solution to synchronize
and start the synchronization process, do one of the following:

• Select a Solution and click Synchronize at the top of the Solutions list.

• Click the Synchronize button in the Solution’s Inline Actions Bar.

2. On the Source page:

a. Select a Solution Environment from the Source environment/solution

menu.

Tip: The Environment that you select must contain registered Systems
that run a Product that is supported for the synchronization
operation. Currently, the only Product that is supported for
synchronization is Content Server.
b. Select a Product name and Product version from the Environment that you
selected in the previous step. If there is only one Product and Version that
is supported for synchronization, its Product name and Product version
are presented as default options.
c. Click Next.

3. On the Source page:

a. Select a Solution Environment from the Source environment/solution

menu.

118 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.8. Settings: Solutions

Tip: The Environment that you select must contain registered Systems
that run a Product that is supported for the synchronization
operation. Currently, the only Product that is supported for
synchronization is Content Server.
b. Select a Product name and Product version from the Environment that you
selected in the previous step. If there is only one Product and Version that
is supported for synchronization, its Product name and Product version
are presented as default options.
c. Click Next.

4. On the Target page, System Center Manager performs analysis to verify that it
can perform the synchronization. If:

a. Select a different Environment from the Target environment/solution

menu. After you make your selection, System Center Manager displays the
Systems that run Product Component Instances of the Product that you are
synchronizing. The Product Component Instances that appear in the list
will be synchronized, unless they are disabled. (Disabled Product
Component Instances appear in the list, but are not selected, and will not be
synchronized.)

Tip: You cannot modify the list of Product Component Instances to be

synchronized.
b. Click Next.

5. On the Analyze page, System Center Manager validates that the Systems in the
target Environment are ready to be synchronized. If System Center Manager
finds problems, resolve them before you proceed. If System Center Manager
displays The analysis has completed successfully, click Next.

6. The Download page displays packages that System Center Manager needs for
the synchronization. To download any missing packages, click Download <#>
item(s) and log on to My Support, if necessary.

7. On the Validate page, System Center Manager validates that the Content Server
instances in the target Environment are ready to be synchronized. To view the
results of the validation, click View details.
If System Center Manager finds issues that require your attention, address the
issue before proceeding. The action that you need to take depends on the
warning that is displayed.

Discrepancies between the Environments

If System Center Manager detects a discrepancy between the two
Environments that could prevent the synchronization from completing
successfully, it displays a warning. If you are certain that the discrepancy
will not affect the synchronization, select the check box that indicates that
you acknowledge the discrepancy and choose to proceed despite it. Click
Continue.

SYSCM240400-AGD-EN-01 Administration Guide 119

Chapter 11 Configure System Center Manager

Important
Do not select the check box if you are not certain. Proceeding with the
synchronization despite the warning can have unpredictable results
on your Product Component Instance.
Problems with Updates, Patches, or Language Packs
If System Center Manager detects problems with any Updates, patches, or
Language Packs that it needs to apply to the target Environment, it displays
a warning that a package has not been downloaded, that a package is
currently downloading, or that a package encountered an error during
download. You must correct the problem before the synchronization can
complete. You may be able to proceed with the current synchronization
once you have corrected the problem, but in most cases, you need to restart
the synchronization.

8. On the Synchronize page, System Center Manager lists the Product Component
Instances that will be synchronized. Click Synchronize to proceed.
9. The synchronization begins. To view the progress of the synchronization, open
the Activities Overview page. Under Running Activities, a Synchronize Patch

Installation activity appears. Click the Details button for more information
on the activity’s progress.
10. When the synchronization completes, the Synchronize Patch Installation
activity appears in the Other activities section of the Activities Overview, with

a status of Completed . Also, a Notification is generated with the message

Synchronize Patch installation complete.

If the status displayed is Complete with Errors , it indicates that the

synchronization encountered problems during execution. To learn more about

the nature of the errors, click the Details button . If necessary, you can roll
back the Synchronize Patch Installation by following the instructions at “Roll
Back a Content Server Update Deployment” on page 56.)

11.9 Settings: External Vendor Files

You can add third-party files to System Center Manager on the External Vendor
Files view of the Settings page and then use them in your Execution Plans. For
example, you can upload a Content Server license, and then apply it on a managed
System, or you can upload an Apache Tomcat installer and then install Tomcat on a
managed System.

Note: The Settings page, External Vendor Files view is not available in all
versions of System Center Manager.

Files that have been uploaded to System Center Manager appear on the External
Vendor Files view of the Settings page. You can filter your view of this page to
make it easier to find uploaded third-party files.

120 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.9. Settings: External Vendor Files

Optionally, you can enable restrictions on External Vendor File uploads to ensure
that no single file exceeds a maximum file size, and the total number of uploaded
files does not exceed a specified file count or a total size in megabytes. You can also
limit External Vendor File uploads to files that have an allowed file extension.

11.9.1 Add External Vendor Files to System Center Manager

You can drag and drop files into System Center Manager or browse to a file and add
it.

To add External Vendor Files to System Center Manager

1. On the External Vendor Files view of the Settings page, click the Upload

button

2. On the Upload sidebar, add a file using one of the following methods:

• Drag one or more files onto the Upload sidebar.

• Click Add files, and browse to the location of the file that you want to
upload.

3. Click Continue

4. After the upload completes, click Close.

The uploaded files now appear on the External Vendor Files view of the Settings
page.

11.9.2 Remove External Vendor Files from System Center

Manager
To remove files from the Settings: External Vendor Files view, do one of the
following:and then click Remove <#> Selected.

• Select one or more files, and then click Delete at the top of the files list.
•
Click the Delete button in the file’s Inline Actions Bar.

Note: An Execution Plan that is configured to use a deleted file will generate
an error message similar to the following when you attempt to run it.

The selected external file <file_name> for the parameter <parameter_

name> could not be found.

SYSCM240400-AGD-EN-01 Administration Guide 121

Chapter 11 Configure System Center Manager

11.9.3 Restrict External Vendor File Uploads

By default, there are no restrictions on the size or number of files that you can
upload using the External Vendor Files view of the Settings page. To place limits on
External Vendor File uploads, log on to System Center Manager as an Administrator
and click Enable restrictions.

Once restrictions are enabled, the following configurations are available:

Max file count

The total number of External Vendor files must not exceed the Max file count.
System Center Manager prevents an upload if it would cause the file count to
exceed the specified maximum.
Max file size (in megabytes)
The file size of any External Vendor File must not exceed the Max file size (in
megabytes). System Center Manager prevents the upload of any file whose size
exceeds the specified maximum.
Max allowed disk space (in megabytes)
The total file size of all External Vendor Files cannot exceed the specified Max
allowed disk space (in megabytes). System Center Manager prevents the
upload of any file that would cause the total file size of all External Vendor Files
to exceed the specified maximum.
Allowed File Extensions
By default, no allowed file extensions are specified, which means that files with
any extension can be uploaded. Specify one or more file extensions to restrict
External Vendor File uploads to only files that have an allowed extension. When
you enter allowed file extensions, enter only letters. It is not necessary to enter
the dot that separates a file name and file extension. For example, enter MSI,
not .MSI.

11.10 Settings: Manifest

The System Center Manager manifest provides information about the Products in
the System Center Manager Catalog and the updates that you can apply to the
Products on your managed Systems. In online mode, System Center Manager
updates its manifest automatically every day. You can verify that you are using the
most current manifest by clicking Check for updates on the Manifest view of the
Settings page.

122 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.10. Settings: Manifest

11.10.1 Update the Manifest in Offline Mode

If you operate in offline mode, you should update the manifest manually whenever
you use System Center Manager.

To update the System Center Manager manifest in offline mode:

1. Using a computer that is connected to the Internet, download the latest System
Center Manager manifest from the Manifest URL shown on the Manifest view
of the Settings page.

2. On the Manifest view of the Settings page, click Upload manifest.

3. The Upload sidebar appears. Upload the manifest file to System Center
Manager using one of the following methods:

• Drag the manifest file onto the Upload sidebar.

• Click Add file, and browse to the location of the manifest file.

4. Click Continue.

5. After the upload completes, click Close.

11.10.2 Manifest Repair

If the System Center Manager manifest becomes corrupt or unusable for any reason,
you can purge it and import a fresh copy.

Note: Do not perform this action unless OpenText Customer Support advises
you to.

The way you repair the manifest differs in online and offline mode. Follow the
instructions that apply to your System Center Manager deployment.

Repair the System Center Manager Manifest in Online Mode

To repair the System Center Manager manifest in online mode, click Repair
manifest data on the Manifest view of the Settings page, and then click Yes on the
Repair manifest data dialog box. When the manifest repair is complete, a message at
the top of the page confirms that The system's current manifest was checked and
published on <Date_Time>..

Repair the System Center Manager Manifest in Offline Mode

To repair the System Center Manager manifest in offline mode, first obtain a
replacement copy of the System Center Manager manifest. Click Repair manifest
data on the Manifest view of the Settings page, and then click Yes on the Repair
manifest data dialog box. The Upload sidebar appears, and you can proceed in two
different ways.

SYSCM240400-AGD-EN-01 Administration Guide 123

Chapter 11 Configure System Center Manager

• Drag the System Center Manager manifest onto the Upload sidebar, and then
click Continue.
• Click Upload Manifest, browse to the location of the manifest file and then select
it. Click Start when the Upload manifest for repair dialog box appears.

When the upload completes, click Close.

When the manifest repair is complete, a message at the top of the page confirms that
The system's current manifest was checked and published on <Date_Time>.

11.11 Settings: Support

System Center Manager log files may be requested by OpenText Customer Support
if you report that System Center Manager is not behaving as you expect. The
Support view of the Settings page allows you to easily package any logs that you
have generated. It also provides access to Log Packages that you have generated in
the past.

Tip: For information on generating logs and setting log levels, see “Settings:
Logs” on page 92 and “System Center Manager Logs“ on page 137.

You can create a Log Package for any single Solution Environment. If you need to
produce Log Packages for more than one Solution Environment, generate a Log
Package separately for each Environment.

System Center Manager can retain up to five Log Packages. If you attempt to create
more than that, System Center Manager warns you that it will delete an existing Log
Package before you proceed. To delete an existing Log Package yourself, click the

Delete button in the Inline Action Bar of the Log Package, or select the Log
Package and click Delete above the list of Log Packages.

11.11.1 Create a Log Package

Generating a Log Package is a convenient way to package logs to provide to
OpenText Customer Support.

To create a Log Package:

1. On the Support view of the Settings page, click the Add item button .

2. On the Logs package page, configure your Log Package:

• Enter a Package name.

• Click Change, if necessary, to select a different Solution Environment. (By
default, your current Solution Environment is selected.)
• Enable or disable Include manager logs. If this option is not enabled, System
Center Manager logs are not included in the Log Package.

124 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.12. Settings: Notification

• Clear the check box beside any Agent whose logs you do not want to
include. By default, the logs from every System Center Agent in the Solution
Environment are included in the Log Package.

3. Click Start. You are returned to the Log Packages page. The Log Package that
you have requested appears on the page. Its status indicates whether the
package is queued, in progress or available. Note that if any Agent is busy
performing activities when the Log Package request is generated, the Log
Package job will wait for the Agent to become available before it proceeds to
add its logs to the Log Package. Information on the generation of a Log Package
is also available on the Activities Overview page.

4. Once the Log Package has a status of Completed , you can click the

Download button beside the Log Package to save a local copy that you can
provide to Customer Support.

11.12 Settings: Notification

Automatic Notification Purge configures System Center Manager to delete the
types of Notification that you specify once the specified retention period has
elapsed.

On the Notifications view of the Settings button, click the Automatic Notification
Purge toggle button to enable automatic purge of Notifications.

When you enable Automatic Notification Purge, you must also specify the
following settings:

Notification retention period (days)

Once the period that you specify elapses, Notifications of the type that you
specify will be deleted.
Notifications to purge
This section provides check boxes for the various Notification types. Select a
check box to configure Notifications of that type to be deleted once the
Notification retention period (days) elapses. Other Notifications will remain in
the Notifications view of the Activities page until you delete them.

Tip: To view examples of Notifications of various types, open the

Notifications view of the Activities page, which you can sort and filter by
Notification type.

SYSCM240400-AGD-EN-01 Administration Guide 125

Chapter 11 Configure System Center Manager

11.13 Settings: Activity

On the Activity tab of the Settings page, you can enable or disable Retry activities
with an error. (It is enabled by default.)

When this setting is enabled, System Center Manager permits you to resubmit
certain activities that ran but did not complete successfully. If you know what
prevented the activity from completing and have corrected the underlying problem,
retrying an activity can allow it to succeed. For example, if a temporary network
failure made it impossible for System Center Manager to apply an Update to a
Product Component Instance, you can retry the activity once the network is
functional again.

When you enable Retry activities with an error, you can also set a Retry error
period (hours). This is the period during which the Retry option is available for
failed activities. By default the Retry error period (hours) is 24. You can set it to a
number of hours from 1 to 72. If more hours than the Retry error period (hours)
have elapsed since an activity was originally submitted, the Retry option does not
appear for that activity.

Note that enabling Retry activities with an error affects only activities that are
started after the setting is in place. It does not affect activities that have already run,
so you will not see a Retry option for existing activities when you enable the setting.
But you will see it for eligible activities that run after the setting is in place.

Disabling Retry activities with an error, on the other hand, is effective immediately.
As soon as you disable the setting, you stop seeing the Retry option for existing
eligible activities, including ones that offered the Retry option before you disabled
the Retry activities with an error setting.

In addition, the following requirements govern whether you see a Retry option for a
failed activity:

• It is an activity that supports the Retry operation. Support for retrying activities
varies by product and by activity.

• You are the person who initiated the failed activity. Only the user that initiated a
failed activity can Retry it.

• Another activity of the same type has not been initiated in the same environment.

To retry a failed activity, locate the activity that you would like to retry on the
Activities Overview and, in its Inline Actions Bar, click Retry . After you click
Retry, a message informs you that you should determine what caused the activity to
fail by inspecting the log files and resolve that problem before you retry an activity.
It also informs you that, unlike a new activity, the Retry operation does not verify
prerequisites before it runs. (For information on the prerequisites check, see “Verify
Prerequisites” on page 52.) Click Retry to proceed.

126 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.14. Secure Sockets Layer (SSL)

11.14 Secure Sockets Layer (SSL)

This section of the online help contains information on:

• Running System Center Manager on SSL

• Connecting System Center Manager to OTDS or Content Server using SSL and a
encryption certificate that Java does not recognize by default.

11.14.1 Run System Center Manager on SSL

To run System Center Manager using SSL, configure it to reference additional
configuration files, a Java keystore file (if necessary) and an SSL port. Once you have
done that, configure each System Center Agent to connect to the updated SSL server
address.

11.14.1.1 Enable System Center Manager to run on SSL

Add parameters to the System Center Manager to enable SSL. If you are using a
certificate that is not recognized by Java, add a keystore to the System Center
Manager application directory. Specify its location and other related parameters in
the config.ini file.

Tip: Your keystore must reference a certificate in use in your Public Key
Infrastructure. For an example of using a self-signed certificate, see “SSL
Deployment Using a Self-Signed Certificate” on page 130.

To enable System Center Manager to run on SSL:

1. Stop the System Center Manager service.

2. If you are using a certificate that is not recognized by Java by default, copy your
keystore file to the <System_Center_installation_folder>\jettyhome\etc\
folder.
3. Add the following properties to the <System_Center_installation_folder>
\configuration\config.ini file:

• jetty.etc.config.urls=etc/jetty.xml,etc/jetty-deploy.xml,etc/
jetty-https.xml

• jetty.sslContext.keyStorePath=etc/<keystore_filename>
• jetty.sslContext.keyStorePassword=<keystore_password>
• jetty.sslContext.keyManagerPassword =<key_password>
• jetty.ssl.port=<ssl_port_number>
4. Start the System Center Manager service.

Note: After you complete the above steps, you can open System Center
Manager using SSL. Your managed systems will appear with an Agent status

SYSCM240400-AGD-EN-01 Administration Guide 127

Chapter 11 Configure System Center Manager

of Stopped, however, until you configure each System Center Agent to connect
to the SSL address of System Center Manager. See “Configure each System
Center Agent to Connect to the System Center Manager SSL Address”
on page 128.

11.14.1.2 Configure each System Center Agent to Connect to the System

Center Manager SSL Address
Perform the following steps for every System Center Agent.

In the following instructions, the cacerts file (the Java trust store) must trust the
security certificate used by System Center Manager. For an example of using a self-
signed certificate, see “SSL Deployment Using a Self-Signed Certificate”
on page 130.

Important
Be sure to copy the cacerts file and reference the location of the copy in the
config.ini file, as described in the following procedure. Do not reference the
<System_Center_agent_installation_folder>\jre\lib\security\cacerts
file directly in the config.ini file. The contents of the <System_Center_agent_
installation_folder>\jre\ folder may be overwritten when System Center
Manager is updated.

To configure a System Center Agent to connect to System Center Manager

using SSL:

1. Stop the System Center Agent service.

2. Copy the <System_Center_agent_installation_folder>\jre\lib\security\
cacerts file to another folder that System Center can access. For example, copy
cacerts to the <System_Center_agent_installation_folder>\localcert\
folder.
3. In the <System_Center_agent_installation_folder>\configuration\config.
ini file:

• Modify the com.opentext.sc.agent.server_uri parameter so that it points

to the updated System Center Manager SSL address, as follows:
com.opentext.sc.agent.server_uri=<System_Center_Manager_
host>:<SSL_port>/otsc-server/v1/agentwebsocket

Example: com.opentext.sc.agent.server_uri=SCMhost.example.com:8443/
otsc-server/v1/agentwebsocket

• Add the javax.net.ssl.trustStore and configure it to reference the folder

containing the copy of cacerts, as follows:
javax.net.ssl.trustStore=<System_Center_agent_installation_
folder>/<path>/cacerts

Example: javax.net.ssl.trustStore=C:\\Program Files\\OpenText\

\OpenText System Center Agent\\localcert\\cacerts

128 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.14. Secure Sockets Layer (SSL)

4. Start the System Center Agent service.

11.14.1.3 Obfuscate the keyStore and keyManager Passwords

To prevent SSL-related passwords from appearing in the config.ini file in clear
text, you can use a Jetty utility library that is included with System Center Manager
to obfuscate the passwords.

Stop the System Center Manager service before you make any changes to the
config.ini file.

To access the utility library, open a command prompt and change to the <System_
Center_Manager_home>\plugins\ directory. Using the copy of Java that is installed
with System Center Manager, execute the following command to obfuscate the
keyStore and keyManager passwords:

<System_Center_Manager_home>\jre\bin\java -cp org.eclipse.jetty.util.jar;

slf4j.api.jar org.eclipse.jetty.util.security.Password "key_password"

Example: For example, enter C:\OT\SC\SCM\jre\bin\java -cp org.eclipse.jetty.

util.jar;slf4j.api.jar org.eclipse.jetty.util.security.Password "key_
password"

Tip: The -cp org.eclipse.jetty.util.jar;slf4j.api.jar command

argument adds the two named jar files to the Java class path. Separate the two
jar files with a semi-colon (;) on Windows. On Linux, separate them with a
colon (:).

The command will generate output similar to the following:

2019-05-15 15:56:02.627:INFO::main: Logging initialized @1456ms to
org.eclipse.jetty.util.log.StdErrLog
key_password
OBF:1k8q1v251y871tvf1vun1tvn1y7r1v291k5g
MD5:ec3f9af603bbfa65eaeb21864529c154

Copy the OBF string to the config.ini file, replacing the existing clear-text
passwords, so that the keyStore and keyManager settings appear as follows:
jetty.sslContext.keyStorePassword=OBF:1k8q1v251y871tvf1vun1tvn1y7r1v291k5g
jetty.sslContext.keyManagerPassword=OBF:1k8q1v251y871tvf1vun1tvn1y7r1v291k5g

Restart the System Center Manager service.

SYSCM240400-AGD-EN-01 Administration Guide 129

Chapter 11 Configure System Center Manager

11.14.1.4 SSL Deployment Using a Self-Signed Certificate

To deploy System Center Manager on SSL using a certificate that is not recognized
by Java, such as a self-signed certificate, you can enable SSL using a keystore and
certificate that you generate using the keytool program that is included with Java.
The following sample procedure shows one way of doing this.

Note: Keytool is part of the Oracle Java Platform. Information on keytool is

available on the Oracle Help Center and elsewhere on the Internet.

To create a keystore and self-signed certificate:

1. Create a keystore file and a certificate. Execute the following command in the
<System_Center_installation_folder>\jre\bin\ folder:
keytool -keystore keystore -alias systemcenter -genkey -keyalg RSA
-sigalg SHA256withRSA

Tip: Make a note of the answers that you provide to the questions that
keytool asks.

2. Add the keystore to System Center Manager and configure System Center
Manager to use SSL by following the steps in “Enable System Center Manager
to run on SSL” on page 127.

3. Using Google Chrome™, open the https address of System Center Manager.
Because you are using a self-signed certificate, Not secure appears to the left of
the System Center Manager URL in the browser address bar.

4. Export your self-signed certificate.

a. Click Not secure, and then click Certificate (Invalid).

b. The Certificate dialog box opens. Click the Details tab. Note that the
details match the answers that you provided in step 1 above. Click Copy to
File. The Certificate Export Wizard dialog box appears.
c. On the Certificate Export Wizard dialog box, click Next. Select DER
encoded binary X.509 and click Next.
d. Specify where you would like your certificate file to be saved, and click
Next.
e. Review the information on the Completing the Certificate Export Wizard
dialog box, and then click Finish.
f. Close the Certificate dialog box.

5. Copy the exported certificate to the <System_Center_agent_installation_

folder>\localcert\ folder.

6. Make a copy of the cacerts file, as described in step 2 of “To configure a System
Center Agent to connect to System Center Manager using SSL:“ on page 128.

130 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.14. Secure Sockets Layer (SSL)

7. Configure the copy of cacerts to use your self-signed certificate by running the
following command in the <System_Center_agent_installation_folder>\jre\
bin\ folder:
keytool -import -alias systemcenter -file ..\..\localcert\<exported_
certificate_name> -keystore ..\..\localcert\cacerts -storePass
changeit

8. Update the System Center Agent config.ini file, as described in step 3 of “To
configure a System Center Agent to connect to System Center Manager using
SSL:“ on page 128.
9. Restart the System Center Agent.

11.14.1.5 Troubleshooting SSL Deployments

If you encounter either of the following Java exceptions when you attempt to
configure System Center Manager and its System Center Agents to run on SSL, it
indicates that the cacerts file, the Java trust store, does not recognize the certificate
that you are using.

• java.util.concurrent.ExecutionException: org.eclipse.jetty.websocket.
api.UpgradeException: 400 Illegal character CNTL=0x15

• javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.

security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target

11.14.2 Connect System Center Manager to OTDS or Content

Server using SSL
If your organization enables SSL using an encryption certificate that Java recognizes
by default, no additional steps are required to connect to OTDS or Content Server
over SSL. However, if your organization uses a certificate that Java does not trust by
default, additional steps are required.

Complete the below steps to add a Java truststore to System Center Manager and
add your organization’s SSL certificate to the truststore.

To add an encryption certificate to the System Center Manager Java

truststore:

1. Copy the <System_Center_installation_folder>\jre\lib\security\cacerts

file to another folder that System Center can access. For example, create a
<System_Center_installation_folder>\localcert\ folder and copy the
cacerts file to it.

2. Import your organization’s certificate into the cacerts keystore file.

3. Add the javax.net.ssl.trustStore parameter to your <System_Center_
installation_folder>\configuration\config.ini file and set its value to the
folder that you created in step 1, as follows:

SYSCM240400-AGD-EN-01 Administration Guide 131

Chapter 11 Configure System Center Manager

javax.net.ssl.trustStore=<System_Center_installation_folder/path>/
cacerts

Example: javax.net.ssl.trustStore=<System_Center_installation_folder>/
localcert/cacerts

4. Restart System Center Manager.

11.15 Java Memory Pool

By default, System Center Manager starts with 256 MB initial memory and 1536 MB
maximum memory and System Center Agents start with 256 MB initial memory and
512 MB maximum memory. These settings are appropriate for most installations of
System Center Manager, but you can modify them if you desire.

11.15.1 Java Memory Settings on Windows

On Windows, configure Java memory settings for System Center Manager in the
OpenText System Center Manager Properties dialog box. (For a System Center
Agent, open the OpenText System Center Agent Properties dialog box.)

To configure Java memory settings on Windows:

1. Open the OpenText System Center Manager Properties dialog box, using any
of the following methods:

• In the Windows Notification area, right-click the OpenText System Center

Manager icon, and then click Configure.
• If the icon is missing, start the OTSystemCenterManagerw.exe process from
the <System_Center_Manager_home> folder. If the OpenText System Center
Manager Properties dialog box still does not appear, open Windows Task
Manager and, on the Details tab, make sure that OTSystemCenterManagerw.
exe is not running, then try again.

2. On the Java tab of the OpenText System Center Manager Properties dialog
box, enter values for Initial memory pool and Maximum memory pool.

3. Click OK to save your changes.

132 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.16. Update System Center Manager

11.15.2 Java Memory Settings on Linux

On Linux, include Java memory settings in an executable shell file named setenv.sh
located in the <System_Center_Manager_home> directory or the <System_Center_
Agent_home> directory. You may need to create this file. It is not installed by default
by System Center Manager.

To configure Java memory settings on Linux:

1. Open a terminal and change directory to the <System_Center_Manager_home> or

<System_Center_Agent_home> directory.

2. Create an executable shell file called setenv.sh if it does not exist already.

3. In the setenv.sh, include the following parameters:

Initial Java Memory

JAVA_XMS="-Xms<Memory_in_megabytes>m"

For example, to set initial memory to 512 MB, include JAVA_XMS="-Xms512m"

Maximum Java Memory
JAVA_XMX="-Xmx<Memory_in_megabytes>m"

For example, to set maximum memory to 2048MB, include JAVA_XMX="-

Xmx2048m"

4. Restart System Center Manager or the System Center Agent to register your
changes.

11.16 Update System Center Manager

System Center Manager is a self-updating application. From time to time, a banner
will appear informing you that an update for System Center Manager is available. If
you see a message stating that an update is available, you should download and
apply the new version immediately. Some System Center Manager functionality
may be disabled until you apply the update.

The procedure for updating System Center Manager varies depending if you
operate in online mode or not. Follow the instructions that apply to your System
Center Manager deployment.

When you apply an update to System Center Manager, the System Center Agents
that connect to it are automatically updated the next time they connect to System
Center Manager. After you have applied a System Center Manager update, you do
not need to take any additional action to update your System Center Agents.

SYSCM240400-AGD-EN-01 Administration Guide 133

Chapter 11 Configure System Center Manager

11.16.1 Update System Center Manager in Online Mode

In online mode, System Center Manager downloads the product update file
automatically.

To update System Center Manager in online mode

1. Click Start Update on the banner message informing you that an update is
available.

2. The Update page opens. Click the My Support hyperlink. Sign in to My

Support so that System Center Manager can download the update on your
behalf.

3. The Patch download started dialog box appears informing you that System
Center Manager is downloading the update. Click Close. When the message
The required package has been provided appears and the Status icon indicates
that System Center Manager has downloaded the update, click Next.

4. Click Install to start the installation.

5. A series of messages informs you that System Center Manager is applying the
update. When it is finished, it informs you that your system has been
successfully updated. Click Close to exit the update procedure.

11.16.2 Update System Center Manager in Offline Mode

In offline mode, System Center Manager cannot download an update automatically.
You need to obtain the update and upload it to System Center Manager before the
update can be applied.

The update file has a name similar to SystemCenterUpdate_22<_#_#>.zip. The same

file is used for all System Center Manager updates, regardless of whether System
Center Manager runs on Microsoft Windows or Linux.

Important
Install the update using System Center Manager. Do not unzip the update onto
the System Center Manager application folder.

To update System Center Manager in offline mode

1. Obtain the System Center Manager update.

a. Click Start Update on the banner message informing you that an update is
available.

b. The Update page opens. To download the update, click the Download

button in the URL column. Log on to OpenText My Support if you are

prompted to. Your browser downloads the update.

134 OpenText™ System Center Manager SYSCM240400-AGD-EN-01

 11.16. Update System Center Manager

Tip: If necessary, copy the URL from the Download button and use it
to download the System Center Manager update on a computer that is
connected to the Internet.

2. Apply the System Center Manager update. Perform the following steps on any
computer that can connect to System Center Manager.

a. Click the Upload the update hyperlink. The Upload sidebar opens. Provide
the update file to System Center Manager, either by browsing to it (click
Add file) or by clicking it and dragging it onto the Upload sidebar.
b. On the Upload sidebar, click Continue. A progress bar shows that System
Center Manager is uploading and validating the update file. When the
status of the upload is Succeeded, click Close to return to the System
Center Manager Update page.
c. Click Next. On the following page, click Install to apply the update. A
series of messages informs you that System Center Manager is extracting
the update and applying it. When it has finished these operations, the
System updated dialog box informs you that the update has successfully
completed. Click Close to complete the operation and return to System
Center Manager.

SYSCM240400-AGD-EN-01 Administration Guide 135

Chapter 12
System Center Manager Logs

To help diagnose problems that you may encounter with System Center Manager or
your System Center Agents, you can enable various logging levels for the System
Center Manager and the System Center Agent.

12.1 System Center Manager and Agent Logging

There are several places that you can configure log settings in System Center
Manager:

Server logging
To set the log level for System Center Manager, open the Settings page, Logs
view, and select a value from the Log level menu. By default, Log level is set to
Info. For troubleshooting, raise the log level to Error or Debug.
Agent logging
To set the log level for a System Center Agent, open the System Details view of
a System that is registered in System Center Manager, and then click Edit. Select
a value from the Log level menu. By default, Log level is set to Info. For
troubleshooting, raise the log level to Error or Debug. You can also set the HTTP
logging level for an agent on this page.
HTTP logging
To set the log level for HTTP messages sent and received by System Center
Manager, open the Settings page, Logs view, and select a value from the HTTP
log level menu. By default, HTTP log level is set to Error. For troubleshooting,
raise the log level to Debug.
Request logging
Request logs are a record of the requests that the server has processed. To enable
request logging, open the Settings page, Logs view, click Enable request
logging check mark and specify a number of days in the Log retention period
(days) box.

Specify the System Center Log File Name and Location

By default, System Center Manager and the System Center Agent write to the
<System_Center_installation_folder>/logs/otsc.log file. To specify a different
log file, add the log.file setting to the config.ini file. The value of this setting is a
relative or absolute file path.

Important
Before you edit the config.ini file, stop System Center Manager or the System
Center Agent.

SYSCM240400-AGD-EN-01 Administration Guide 137

Chapter 12 System Center Manager Logs

• On Windows, right-click the System Center Manager or Agent application

in the Notification area and then, on the General tab, click Stop, or stop the
System Center Manager or Agent service in the Windows Services
application.
• On Linux, open a terminal as the System Center user, and run ./
otsystemcenteragent.sh stop at the <System_Center_installation_
folder> command prompt.

Example: On a default Windows installation of System Center Manager, to write logging

output to a file named mylogs.log in the logs folder, add one of the following lines to the
config.ini file:

• log.file=C:/Program Files/OpenText/OpenText System Center Manager 16.0.

0/logs/mylogs.log

• log.file=./logs/mylogs.log

138 OpenText™ System Center Manager SYSCM240400-AGD-EN-01