Control Center Director PDF

Control Center Director PDF
IBM
Contents
IBM Control Center Director................................................................................... 1

Release Notes.............................................................................................................................................. 1
New Feature and Enhancements........................................................................................................... 1
Known Restrictions.................................................................................................................................2
Getting Started............................................................................................................................................. 2
IBM Control Center Director Overview........................................................................................................ 3
Control Center Director Web Services......................................................................................................... 6
IBM Control Center Director and GDPR Compliance.................................................................................. 7
Preparing to Install...................................................................................................................................... 7
System Requirements............................................................................................................................ 7
Recommended Installation and Configuration Sequence.................................................................... 9
Installing and Configuring Control Center Director...................................................................................11
Before you set up the database........................................................................................................... 11
Configuring external authentication and certificate-based connections........................................... 16
Configuring IBM Connect:Direct support for Control Center Director................................................ 19
Installing Control Center Director........................................................................................................23
Installing maintenance and fixes.........................................................................................................24
Configuring Control Center Director.................................................................................................... 25
Additional Configuration Tasks............................................................................................................ 27
Taking the first steps after installing Control Center Director.............................................................28
Command Line Utilities Reference...................................................................................................... 29
Uninstalling Control Center Director....................................................................................................31
Emergency Restore.............................................................................................................................. 31
Control Center Director Web Console....................................................................................................... 32
Dashboard............................................................................................................................................ 32
Server Management............................................................................................................................. 33
Deployment Management....................................................................................................................34
License Management........................................................................................................................... 35
Audit Logs............................................................................................................................................. 37
Users and roles Management.............................................................................................................. 37
RESTful APIs Support................................................................................................................................ 39
Accessing RESTful APIs resources..................................................................................................... 39
Troubleshooting......................................................................................................................................... 40
Troubleshooting deployment scenarios.............................................................................................. 40
Troubleshooting Web Console issues.................................................................................................. 43
Notices....................................................................................................................................................... 49
Trademarks...........................................................................................................................................51
Terms and conditions for product documentation.............................................................................. 52
Index.................................................................................................................. 53
ii
IBM Control Center Director
IBM® Control Center Director (ICC Director) is an activity management and monitoring product. The
following sections describe its features and how to install, configure, and manage it into your deployment.
Release Notes
The IBM Control Center Director Release Notes document supplements Control Center Director
documentation. Release notes are updated with each release of the product and contains product
requirements, as well as other information pertinent to installing and implementing IBM Control Center
Director.
New Feature and Enhancements

The Release Notes document supplements documentation. Release notes are updated with each release
of the product and contain last-minute changes and product requirements, as well as other information
pertinent to installing and implementing .
IBM Control Center Director and its related software have the following features and enhancements:
v1.0.0.2
New Features and Enhancements
• IBM Control Center Director now extends its web console capabilities to support the Emergency
Restore procedure. Control Center Director users can now schedule an Emergency Restore Job from
the Deployments and Servers view. For more information see, “Deployment Management” on page
34 and “Server Management” on page 33.
• Deployment view is now enhanced to enable filtered viewing of completed, held, scheduled, and in
progress jobs based on their job type (Emergency Restore/Maintenance) and OS Type.
• Server group and server are now loaded and displayed using pagination pattern. This renders an
improved UX to Control Center Director web console users.
To install this software, you should go to the Fix Central website and install the latest available iFix.
v1.0.0.1
• IBM Control Center Director now extends support and integrates with Connect:Direct® for Microsoft
Windows. For more information, see:
– Compatibility Matrix
– “Configuring IBM Connect:Direct support for Control Center Director” on page 19
– “Configuring Connect:Direct for Windows for Server and Upgrade Management” on page 22
– “Configuring Connect:Direct for Windows for License Governance” on page 23
• Control Center Director now extends it export/import capabilities to include a simple method to export
server roster data out of Control Center Director configuration database into Control Center. For more
information see, Export Server Roster data from Control Center Director into Control Center .
v1.0.0.0 iFix01
IBM Control Center Director 1

With this iFix, you can install Control Center Director maintenance and fixes in Microsoft Windows, UNIX,
zLinux, and AIX platforms. For more information see, “Installing maintenance and fixes” on page 24.
Base Release (v1.0.0.0)
IBM Control Center Director 1.0 has the following features and enhancements:
• With a new, easy-to-use Web User Interface (Control Center Director Web Console), IBM Control
Center Director offers its users ease to perform routine server operational and administrative
procedures necessary for upgrade management, server management, viewing deployment history,
aggregating, correlating, and reporting licensing usage, using a standard Web browser.
• Control Center Director integrates with the following:
– Connect:Direct for UNIX
– Connect:Direct for z/OS (License Governance only)
For details see, Compatibility Matrix.
Known Restrictions
Control Center Director and its related software have the following known restrictions:
• Connect:Direct servers can only be restored to a release from which upgrade was planned. For example,
if you upgrade from Connect:Direct for UNIX v4.3 to v6.0, then you can only restore to Connect:Direct
for UNIX v4.3 but not v4.2.
• Upgrades on target Connect:Direct nodes via Control Center Director Web Console is currently not
supported for Connect:Direct servers running on a 32-bit Solaris platform. You must upgrade to
Connect:Direct for UNIX v6.0.0 and above to support the upgrade process.
Getting Started
Maintaining Connect:Direct Servers is crucial to enterprises to support mission-critical file transfer
business processes, while satisfying policy and regulatory compliance requirements.
It involves a variety of routines that stretch between upgrade management, to server management,
viewing deployment history, aggregating, correlating, and reporting licensing usage.
Those are some key metrics that administrators rely on to understand and optimize Connect:Direct server
performance, plan upgrade, identify bottlenecks early, and resolve issues proactively before they affect
end users.
If you are a first-time user, you can get a quick introduction to using IBM Control Center Director just by
reading the following section.
IBM Control Center Director, an activity management and monitoring product, helps you meet these
critical needs with the following set of features:
• Discover resources faster
– After you have installed the required maintenance version of Connect:Direct with Agent, Control
Center Director is quick to discover all the Connect:Direct resources in your environment.
– Connect:Direct Agent is included with the Connect:Direct server when it is at the required level of
maintenance for Agent inclusion.
– With the Control Center Director URL defined during Connect:Direct installation, you can continue to
stay updated about automatic re-discoveries of new resources in your environment.
2 Control Center Director PDF

• License Governance
– Control Center Director capabilities come in handy for administrators to keep track of Connect:Direct
servers deployed in your infrastructure.
– Tracking assets is an essential capability to achieve greater visibility of your environment's inventory.
– Competencies like exporting usage reports and viewing license by environment type give greater
control to steer inventory management in an effective way.
• View managed Server's and Agent's status
– The Dashboard and Servers view on the Control Center Director Web Console displays connections
with managed Connect:Direct servers and their availability status.
– This way, you can view their status and quickly locate faulty resources, instead of having to browse
through the entire infrastructure. Once the issue is diagnosed, you can troubleshoot accordingly.
• Upgrade Management
Control Center Director options help administrators automate the upgrade process on target
Connect:Direct nodes in an organized manner.
• Server Management
– Use the Servers view on the Control Center Director Web Console to display connections and
dependencies among managed Connect:Direct servers and their relationship with the Server Group,
as a whole.
– This way, you can also associate all discovered resources to the desired Server group and perform the
following routines in an organized manner:
- viewing, modifying server and server group settings
- defining a server pool and add discovered servers/server groups
- export server group composition report to steer server management in an effective way
- remove server/server groups from the server roster
“Recommended Installation and Configuration Sequence” on page 9 describes a few brief steps that
will help you get a direct experience with installing, running, and performing management operations on
Connect:Direct server.
IBM Control Center Director Overview

The following illustration shows Control Center Director components that reside as services within a
functional environment of the Control Center Director architecture. It also illustrates relationship with
other connections such as, Connect:Direct Server and ICC.

Before you begin
• Control Center Director upgrades and applies maintenance to Connect:Direct nodes through a
Connect:Direct Agent instance which is co-packaged with Connect:Direct software.
• The compatibility matrix below provides information about IBM Connect:Direct versions compatible
with Control Center Director, by its features. To install this software, you should go to the IBM Passport
Advantage website.
Table 1. Connect:Direct and Control Center Director Compatibility Matrix

IBM Connect:Direct for License Upgrade Dashboard Server
Governance Management Management
UNIX v4.2.0.5, v4.3.0.1, Y Y Y Y
v6.0.0.1, v6.1 and above*
Windows v4.7.0.7, Y Y Y Y
v4.8.0.3, v6.0.0.3, v6.1
and above**
z/OS v6.0, v6.1 and Y N N N
above***
* Supported UNIX variant information is available through Software Product Compatibility Reports
website. Emergency Restore support over Control Center Director web console is available for
Connect:Direct for UNIX from v6.1 and above.
** Emergency Restore support over Control Center Director web console is not available for
Connect:Direct for Windows v6.1. This will be supported in an upcoming maintenance release.
*** APAR PH15805
Download IBM Control Center Director to gain access to the following key Control Center Director
components.

Component Description
Control Center Director Control Center Director Engine renders the following core functions through
Engine a set of services that:
• Secure connection by using certificate-based authentication and manage
communication with Connect:Direct Agent and Server
• Enforce scheduled upgrades on target Connect:Direct nodes where
package content is to be distributed
• Monitor Connect:Direct server and Agent status
• Control Connect:Direct Servers management with a variety of routines
that stretch between viewing, modifying server and server group settings,
to exporting server group composition report.
• Collect licensing data from managed Connect:Direct servers for greater
visibility of your environment inventory.
Control Center Director Web Services

REST API Service Control Center Director provides RESTful API interface to make HTTPS
queries and fetch data from Control Center Director. These APIs make it
easy to integrate Control Center Director with external portals and other
monitoring tools.
Install Control Center Director software package to install the REST API
Service.
Web Console Service Control Center Director provides Web Console, a browser-based interface,
to render license governance and server management capabilities for large-
scale Connect:Direct deployments.
Web Console service is a component of Control Center Director.

Component Description
Connect:Direct Agent What is Connect:Direct Agent?
Agent is a component of Connect:Direct servers that are managed using
Control Center Director.
What does an Agent do?
• It helps complete various tasks that are initiated in the Control Center
Director Web Console.
• Example, if you want to upgrade a Connect:Direct Server in your network,
you can schedule this task in Control Center Director. The agent
replicates these settings and ensures that the task is completed
effectively.
When does the Agent Contact the Connect:Direct Server?
While running silently in the background, the Connect:Direct Agent contacts
Connect:Direct Server to:
• Enforce scheduled upgrades on Connect:Direct nodes where package
content is to be distributed
• Collect licensing data
• Relay maintenance tasks initiated in the Control Center Director Web
Console
• Relay managed Connect:Direct node and Agent discovery events to
Control Center Director Engine.
When the Connect:Direct Agent is first installed and configured, it is auto-
discovered by the Control Center Director Engine within 1 minute.
Control Center Director Web Services

Control Center Director Web Services makes management of vast repository of server roster, deployment
scheduling, and license distribution information, for resources in your Connect:Direct deployment,
available through a Web-based User Interface (Web Console) and a RESTful API-based interface.
This documentation describes how to plan for, install, administer, and manage Control Center Director. To
administer and manage Control Center Director access:
• Web Console Interface
Web Services extends a light and clean web-based User Interface, Control Center Director Web
Console, or simply Control Center Director Web Console. It provides Connect:Direct administrators a
single point of access to perform operational and administrative tasks necessary for centralized license
governance and server management capabilities of your Connect:Direct deployment.
To access the Control Center Director Web console, see “Taking the first steps after installing Control
Center Director” on page 28.
• RESTful API Interface
The Representational State Transfer (REST) Application Programming Interface (API) is useful when you
want to integrate Control Center Director with other solutions or develop custom applications by using
the RESTful APIs.
What to do next:
• “Preparing to Install” on page 7
• “Installing and Configuring Control Center Director” on page 11

IBM Control Center Director and GDPR Compliance
IBM Control Center Director performs password hashing and contains GDPR data such as user names,
email addresses, phone numbers, and passwords. Control Center Director allows you to view, update,
delete user information when needed.
The following topics contain detailed information about how IBM Control Center Director complies with
General Data Protection Regulation (GDPR):
• Control Center Director offers security and privacy capabilities, including ISO certifications and
technical security capabilities, to support you in meeting the GDPR compliance obligation. For more
information see, “Certificate-based Authentication” on page 17.
• Control Center Director stores user information in native database. To manage user roles, view, update,
and delete user information see, Control Center Director Web Console > Users and Roles.
• Control Center Director stores audit log information in its native databases. The audit log information
keeps track of what changes the user makes to the system. For more information see, Control Center
Director Web Console> Records.
• Control Center Director hashes stored passwords, however does not encrypt log records, user names,
names, email addresses, phone numbers.
Preparing to Install
Taking time to plan your Control Center Director installation will help ensure a smooth process. This
section lists items to consider before you start the installation process.
System Requirements
The detailed system requirements information is available through the Software Product Compatibility
Reports web site.
The tables below describe detailed system requirements and supported software information required to
install Control Center Director on 64-bit Operating Systems.
Installation Environment Requirement

Table 2.
Hardware Software
For a UNIX and Windows operating system: Control Center Director can be installed on the
following 64-bit Operating Systems:
• RAM (recommended) - 8GB
• RedHat Enterprise Linux (RHEL) Server 7.2
• RAM (minimum) - 4GB
• zSeries RedHat 7.6
Amount of memory (storage) required to install
• MS-Windows server 2016
and operate Control Center Director depends on
several factors, such as the increased data • MS-Windows 10
volume to run. Contact IBM Support for sizing • IBM AIX 7.1
recommendation for your deployment.
• IBM AIX 7.2
• Disk Space (minimum) - 15 GB

Database
Table 3.
Database type Supported Minimum version
Microsoft SQL Server 2012 SP4 and future fix packs
2014 SP3 and future fix packs
Microsoft SQL Server Enterprise Edition 2016 and future fix packs
DB2 Enterprise Server Edition 11.1.0 and future fix packs
DB2 Workgroup Server Edition 11.1.0 and future fix packs
Oracle Database 11g Enterprise Edition Release 2 and future fix packs
Oracle Database 11g Standard Edition Release 2 and future fix packs
Oracle Database 12c Release 1 (Standard/ 12.1.0.0.0
Enterprise)
Oracle Database 12c Release 2 (Standard/ 12.2
Enterprise)
JDBC drivers for SQL • SQL Server 2012 and 2014 supports JDBC driver
4.2
• Use sqljdbc42.jar
JDBC drivers for Oracle • Oracle 11g and 12c supports JDBC driver
18.3.0.277
• Use ojdbc7.jar or ojdbc8.jar
JDBC drivers for DB2 • DB2 supports JDBC driver db2jcc4

• User db2jcc_license_cu
Supported Software
Managed Resources
Table 4.
Supported Software Version
IBM Connect:Direct for UNIX v4.2.0.5, v4.3.0.1, v6.0.0.1, v6.1 and above
IBM Connect:Direct for Windows v4.7.0.7, v4.8.0.3, v6.0.0.3, v6.1 and above
Connect:Direct for z/OS v6.0, v6.1 and above
IBM Control Center v6.0.0.2 and above
Identity Management
Table 5.
Supported Software Version
Secure External Authentication Server 6.0.0 and above
Browser Support

Table 6.
Browser Type Version
Google Chrome 71 and future fix packs
Mozilla Firefox 63.0.x and future fix packs
Microsoft Edge 13 and future fix packs
Recommended Installation and Configuration Sequence

The following steps will guide you through some of the key aspects of Control Center Director. At the
conclusion of the Installation and Configuration sequence, you’ll have reached an excellent starting point
for further, more detail-driven activities.
It is recommended that you follow this sequence to manage and monitor upgrade and maintenance
activities for Connect:Direct Servers in your environment.
Attention: It's not recommended to install Control Center Director on the same server running
IBM Control Center.
Step Action Procedure/Related resources

1 Install and Configure Control Center “Installing and Configuring Control
Director Center Director” on page 11
2 Export Server Roster from IBM Control See, “Exporting Connect:Direct Server
Center (Optional) Roster from Control Center into Control
Center Director” on page 27
Note:
• Connect:Direct servers that have been
configured for Control Center Director
will automatically be added to the
Connect:Direct Server roster.
• Even if you import IBM Control Center
data, Connect:Direct Servers will need
to be configured for IBM Control
Center.
• IBM recommends you use Control
Center Director Web Console to add
and manage Servers in your
environment or dynamically discover
Connect:Direct servers before you
monitor them.
3 Start Control Center Director Web Server 1. Execute runEngine.sh

2. Log into Web Console.

Step Action Procedure/Related resources
4 Upgrade to an appropriate Control 1. Go to Fix Central site and download
Center Director compatible required level of maintenance version
Connect:Direct for UNIX/Windows fix of Connect:Direct.
pack 2. Upgrade and Install Connect:Direct
Secure Plus for UNIX or
Connect:Direct for Windows.
3. Configure Connect:Direct Server and
Agent settings. See, “Configuring IBM
Connect:Direct support for Control
Center Director” on page 19.
Note: In some cases, after a failed
upgrade, the fastest solution is to roll
back to a previous release you were
using. For more information see,
“Emergency Restore” on page 31.
5 Start Connect:Direct Agent Invoke startAgent.sh.
This script is available at:

cdinstallation_location/
install/agent/bin For more
information see, Connect:Direct
documents.
6 Verify if Control Center Director User successfully logs into Control
Installation is complete Center Director Web Console. For more
information see, “Accessing Control
Center Director Web Console” on page
28.
7 Verify if Connect:Direct Server and Agent 1. User successfully logs into Control
discovery is successful Center Director Web Console.
2. Dashboard displays Server roster
data (status) for Connect:Direct
Servers available in your
environment.
3. Control Center Director's
Administrators can now:
a. Add Connect:Direct resources
(packages) into Control Center
Director
b. Deploy Connect:Direct resources
using over target nodes
c. Schedule upgrades for one or
more Connect:Direct Servers
d. Manage one or more
Connect:Direct Servers
e. View license usage by
environment type the following
day.

Installing and Configuring Control Center Director
The following installation work flow describes the information and actions that you must take to
implement a functional Control Center Director system.
Task Related procedure

Setting up database “Before you set up the database” on page 11
Setting up External Authentication and Certificate “Configuring external authentication and
authentication certificate-based connections” on page 16
SMTP configuration Contact your System Administrator
Installing Control Center Director “Installing Control Center Director” on page 23
Configuring Control Center Director Run the config.sh utility to configure:

• KeyStore and TrustStore settings to secure
connection between Control Center Director and
Connect:Direct Server.
• Database connection
• Engine settings
• Web Services connection
• SMTP (E-mail) server
• Package upload directory
• External Authentication (SEAS) configuration
Invoke runEngine utility “Command Line Utilities Reference” on page 29
Before you set up the database

Key Concepts
• Control Center Director supports the following database types to store statistics and other information
collected from monitored servers:
– DB2 on UNIX and Microsoft Windows
– Oracle on UNIX and Microsoft Windows
– Microsoft SQL Server on Microsoft Windows servers
For more information on supported platforms, versions, and editions, see Software Product
Compatibility Reports.
• Control Center Director uses the Java Database Connectivity (JDBC) interface to connect to database
servers.
• Ensure that you have downloaded required JDBC drivers for your databases before you start installing
Control Center Director. Contact your database provider to download the JDBC drivers. For more
information on supported version see, “System Requirements” on page 7.
Complete the following high-level tasks to create and setup databases for use with Control Center
Director:
1. Install Control Center Director
2. Download required JDBC drivers.
3. Review the following topics related to database requirements and settings.

4. After you create the required databases, provide the Database connection parameters. Control Center
Director creates the required tables, views, and indexes during the installation and configuration
process.
5. Ensure Control Center Director database users are given the required permissions to access the
created databases.
Setting up Microsoft SQL Server database and users

When you create Microsoft SQL databases and database users for use with Control Center Director,
ensure that you have installed the JDBC drivers to enable the connection with Control Center Director.
Before you begin

When you install the server, accept the following settings:
• Collation Setting as SQL_Latin1_GeneralCP1_CI_AS
• Server Authentication as SQL Server and Windows Authentication Mode
Also, ensure that you have are authorized to create the databases and database users.
If you need to determine your database and engine sizing, you must request a Server Sizing Study from
your IBM Professional Services Project Manager or an IBM Sales Executive.
About this task

Create the database with the required settings outlined in following table.
Procedure
1. Create and configure a Microsoft SQL Server database instance with the required settings. Use
SQL_Latin1_GeneralCP1_CI_AS as the Collation Setting when creating the instance.
2. Create a database.
3. Create user or users. You can use the one database user to access the two different databases.
4. Grant permissions to the user or users.
Use the following required settings to ensure Control Center Director can use the SQL databases.
Table 7. SQL database settings

Required Setting Database Schema More information
Collation Setting SQL_Latin1_GeneralCP1_ This setting should be set as
CI_AS part of the database creation.
Login Security authentication SQL Server Authentication IBM Control Center supports
only SQL Server authentication.
User Mapping:
Select database.
For Role Members, select
db_owner.
Map the user’s default schema
to
“dbo”.
Torn Page Detection Off

Configuring Control Center Director to use SQL Server databases
To specify database connection details, on Linux and UNIX operating systems run config.sh and provide
the following database connection information:
Table 8.
Database Connection Parameter Description
Database Host Name For MS SQL Server 2012, to connect to a named
instance of SQL server use the format
servername;instancename.
Example: CSGPQ2;SCCINSTANCE
Database port The port number on which database server listens

on.
Default: 1433.
To ensure that the database server is listening on
that port try to establish a “telnet”connection to
the database host and port.
telnet <<dbhost>> <<dbPort>>
Database User ID
Database password
Database Name
JDBC Drivers Use sqljdbc4.jar or sqljdbc41.jar
Download JDBC driver
Setting up Oracle database and database users (schemas)

When you are creating the Oracle database, use the required settings defined below for Control Center
Director to use the Oracle database.
Required setting Database schema More information
Character set AL32UTF8 This setting is set as part

of database instance
creation.
Database user GRANT "CONNECT" TO

permissions <<databaseSchemaUser>>
GRANT CREATE TABLE TO
<<databaseSchemaUser>>
GRANT CREATE VIEW TO
GRANT "SELECT_CATALOG_ROLE" TO
GRANT UNLIMITED TABLESPACE TO
GRANT CREATE SEQUENCE TO

For additional settings on Oracle databases see the following links:
• Additional settings for the Oracle database instance
• Configuring IBM Control Center Director to use Oracle database schemas
Configuring Control Center Director to use Oracle database schemas

Table 9.
Database Host Name In case of multimode Oracle RAC, host name of all
nodes.

on. Typically, the port is 1521.
In case of multimode Oracle RAC, enter the port
number of all the nodes.
Ensure that the database server is listening on that
port.
From the server where you are installing the IBM
Control Center engine, you can try to establish a
“telnet” connection to the db host and port.
Database User ID
Database password for the DB User
Database Name (SID for non-RAC or Service Name

for Oracle RAC)
JDBC Drivers These drivers are thin client-based, pure Java

JDBC drivers.
Copy one of these files to the server where IBM
Control Center Director will be installed
These files are located under <<oracleDBHome>>/
jdbc/lib.
To use Single Client Access Name (SCAN) feature of the Oracle RAC, provide the following settings when
you run config.sh:
Table 10.
Configuration Prompt Description
Is your database in an Oracle RAC environment? Enter Y
How many nodes are in your cluster? Enter 1

Only one node should be in the Oracle RAC if SCAN
is used.

Table 10. (continued)
Configuration Prompt Description
Provide the database host name for cluster host #1 Specify the host name of the Oracle node that
enables the SCAN feature.
The host name should be the same as the
Database Host Name specified in table above.
Provide the database port number for cluster host Specify the port number of the Oracle node that
#1 enables the SCAN feature.
The port number should be the same as the
Database port specified in table above.
Setting up DB2 databases

When you are creating DB2® databases on Linux®, UNIX, and Windows operating systems, use the
required settings defined below for Control Center Director to use the DB2 databases.
Required setting Database Schema More information
Code set UTF-8 Set this setting during database

creation.
Buffer Pools One buffer pool with the page A default buffer pool is created as
size of 32K part of the database creation.
The page size of the buffer pool
One buffer pool with the page
defaults to the page size
size of 16K
specified during database
One buffer pool with the page creation.
size of 8K
One buffer pool with the page
size of 4K
Regular Table Spaces One regular table space with the One regular default table space is
page size of 32K created as part of the database
creation. The size of the table
One regular table space with the
space defaults to the page size
page size of 16K
specified during database
One regular table space with the creation.
page size of 8K
One regular table space with the
page size of 4K
User Temporary Table Spaces One user temporary table space

with a page
size of 32K
System Temporary Table Spaces One system temporary table

space with a page
size of 32K

Required setting Database Schema More information
Table Space permissions The database user must have

access permissions to the newly
created table spaces
Database user permissions CREATETAB, BINDADD, The database user ID that will be
CONNECT, IMPLICIT_SCHEMA specified during Control Center
Director configuration must have
these permissions for the
database.
For additional settings on DB2 databases see the following links:

• Additional settings for configuration parameters on DB2 databases
• Additional settings for DB2 database features
Configuring Control Center Director to use DB2 database

Table 11.
Database Host Name For DB2, to connect to a named instance of SQL
server use the format
servername;instancename.
Example: CSGPQ2;SCCINSTANCE

on.
Default: 5000
Ensure that the database server is listening on this
database port. From the server where you are
installing IBM Control Center Director, try
establishing a “telnet” connection to the database
host and port using the following command:
Database User ID
Database password
Database Name
JDBC Drivers db2jcc4.jar and db2jcc_license_cu.jar
Copy these drivers to the server where IBM Control
Center Director will be installed. These files are
typically in <<DB2installation location>>/java
folder.
Configuring external authentication and certificate-based connections

Perform the procedures defined in the following sections to set up Control Center Director connections.

Authenticating users through external directory services
By default, Control Center Director manages its users, allowing standard username/password login.
However, you may find it useful to tie into an external authentication system like LDAP. Control Center
Director supports LDAP authentication natively by using an IBM Sterling External Authentication Server
(SEAS).
To be able to authenticate your users externally you need to complete the procedure defined in the next
section.
Setting up external authentication for users
Before you begin

1. Ensure that you have the SEAS authentication definition configured. For more information see, SEAS
product documentation.
2. Ensure that Listener Connection Settings are defined and KeyStore/TrustStore files are configured in
SEAS. For more information, see SEAS System Resources Configuration.
About this task

Follow the procedure given below to set up external authentication for users.
Procedure
1. Add either a self-signed certificate or the CA-signed certificate for SEAS in the Control Center Director
TrustStore.
2. Go to “Configuring Control Center Director” on page 25 to configure SEAS connection properties.
3. On the CCD Web Console, click Users and Roles>Create User and select Use External ID.
Certificate-based Authentication
Certificate-Based authentication is an authentication method that IBM Control Center Director can use to
authenticate itself to a Connect:Direct® server. Certificate-Based Authentication eliminates the need for
IBM Control Center Director to store passwords for authentication to Connect:Direct.
When Certificate-Based Authentication is enabled, IBM Control Center Director sends a TLS certificate to
the Connect:Direct server over a secure connection to authenticate itself to the Connect:Direct Server and
vice versa. To configure IBM Control Center Director to monitor a Connect:Direct server with Certificate-
Based Authentication, see Servers view in Web Console.
Note: If you'd like to generate KeyStore/certificate(s) see, “Setting up KeyStores” on page 18.
Setting up Connect:Direct for Certificate-based Authentication
• For a new certificate, import the certificate into Connect:Direct KeyStore:
– Open spadmin window> Go to Keytore Configuration>Personal Certificates>Import the pem file.
– Go to Signer Certificates> Import CA certificate (ca.crt)
• The certificate presented by the IBM Control Center Director must be trusted by the Connect:Direct
server and the one presented by Connect:Direct must be trusted by Control Center Director.
• Connect:Direct User Authorities must include a user whose username is the Common Name of IBM
Control Center Director's end-entity certificate. The user must be assigned the permissions required to
monitor Connect:Direct. Set client.cert_auth to Y in the Functional Authority Entry for that user.
Note: The Connect:Direct user Authority controls user access to the Connect:Direct server and controls
Connect:Direct commands and statements that users can execute.
• Enable Client Authentication in the Secure+ Client record.

For more information, see:
– Enable Client Authentication on the Connect:Direct Secure Plus for UNIX
– Local User Information Record for Connect:Direct Secure Plus for UNIX
– Enable Client Authentication on the Connect:Direct Secure Plus for Windows
Setting up KeyStores
Setting up Keystores is important to manage CA-signed or self-signed certificates, and is used by client
applications for encryption, authentication, and serving over HTTPS.
See example certificate generation procedures in the following sections for instructions to perform
certificate generation in Connect:Direct and Control Center Director.
Attention: These procedures are only required if you need help in generating KeyStore/certificates
for IBM Control Center Director and Connect:Direct.
Setting up Control Center Director Keystore
About this task

Connect:Direct Agent, Control Center Director Web Services, and Engine communicate over TLS using CA-
signed certificates.
Procedure
1. Create a Certificate Authority (CA). Skip this step, if you already have a CA certificate.
To generate Control Center Director and Connect:Direct Agent certificates, you must first have a CA.
Execute the command below to generate a CA:
keytool -genkey -alias <CA_ALIAS> -keyalg RSA -keysize 4096 -sigalg SHA512withRSA -keypass
<KEYPASS> -validity 3650 -dname <DOMAIN_NAME> -keystore <CA_KEYSTORE> -storepass
<KEYSTORE_PASSWORD>
Example domain, "CN=CA,OU=unit,O=ABC,L=loc,ST=state,C=CC"
2. Generate a certificate/KeyStore for Control Center Director:

If you've generated a CA in step 1, then execute the following command to get a CA certificate:
keytool -export -alias <CA_ALIAS> -file ca.crt -rfc -keystore <CA_KEYSTORE> -storepass
<KEYSTORE_PASSWORD>
3. Create CA-signed certificates

a. Generate a server certificate
keytool -genkey -alias <CERT_ALIAS> -keyalg RSA -keysize 4096 -sigalg SHA512withRSA
-keypass <KEYPASS> -validity 3650 -dname <DOMAIN_NAME> -keystore <KEYSTORE> -storepass
<KEYSTORE_PASSWORD>
b. Import the CA certificate as your trustedcacerts into your KeyStore.
keytool -import -trustcacerts -alias <CA_ALIAS>> -file ca.crt -keystore <KEYSTORE>

-storepass <KEYSTORE_PASSWORD>
c. Generate a signing request to get a CA-signed certificate. The following command generates signing
request file in format, server_cert.csr.

keytool -certreq -alias <CERT_ALIAS> -ext BC=ca:true -keyalg RSA -keysize 4096
-sigalg SHA512withRSA -validity 3650 -file "server_cert.csr" -keystore <KEYSTORE>
d. Secure the CA-signed server certificate. If you are using an external CA, then send the signing
request file to your CA to receive your signed server certificate. Alternatively, if you have generated
CA, then execute the command below to sign your certificate:
• Sign the certificate with the generated CA in the CA Keystore using the generated csr file
keytool -gencert -alias <CA_ALIAS> -validity 3650 -sigalg SHA512withRSA -infile

"server_cert.csr" -outfile "server_signed.crt" -rfc -keystore <CA_KEYSTORE> -storepass
<KEYSTORE_PASSWORD>
• Import the signed certificate into your KeyStore
keytool -importcert -alias <CERT_ALIAS> -file server_signed.crt -keystore <KEYSTORE>

You have successfully set up your KeyStore.

To configure the KeyStore in Control Center Director, see “Configuring Control Center Director” on page
25.
Setting up Connect:Direct Server KeyStore
About this task

• Certificate authentication requires a secure connection between Control Center Director and
Connect:Direct server with a SSL, TLS, TLS1.1, or TLS1.2 connection.
• Follow the steps defined in “Setting up Connect:Direct Server KeyStore” on page 19 step 3, to generate
a CA-signed certificate for Connect:Direct. After you have generated the key-certificate pair for
Connect:Direct such as, server_signed.p12, follow below procedure to import key-certificate pair
into Secure+.
• Connect:Direct Agent and Connect:Direct server share a common KeyStore.
Procedure
1. Extract the certificate in pem format.
keytool -importkeystore -srcalias <CERT_ALIAS> -srckeystore <KEYSTORE> -srcstorepass

<KEYSTORE_PASSWORD> -destkeystore "server_signed.p12" -deststorepass <DEST_PASS>
-deststoretype PKCS12
2. Use the following openssl commands to convert certificates into pem format.
openssl pkcs12 -clcerts -nokeys -out servercert.pem -in server_signed.p12

openssl pkcs12 -nocerts -out serverkey.pem -in server_signed.p12
cat serverkey.pem servercert.pem > server_signed.pem
Configuring IBM Connect:Direct support for Control Center Director

Control Center Director upgrades and applies maintenance to Connect:Direct through a Connect:Direct
Agent instance.

After you have upgraded IBM Connect:Direct for UNIX and IBM Connect:Direct for Windows to the
required maintenance level of complete the following procedures to ensure Connect:Direct for UNIX and
Windows servers are discovered dynamically by Control Center Director.
IBM Control Center Director uses Certificate-based authentication to authenticate itself to a
Connect:Direct® server. For more information see, “Certificate-based Authentication” on page 17.
Known Restriction
• Upgrade on target Connect:Direct nodes via Control Center Director Web Console is currently not
supported for Connect:Direct servers running on a 32-bit Solaris system. You must upgrade to
Connect:Direct for UNIX v6.0.0 and above to support the upgrade process.
• Emergency restore feature is currently not available for Control Center Director v1.0.0.1 implementation
of Connect:Direct for Windows.
• When Control Center Director upgrades or applies maintenance to Connect:Direct Windows, currently
running Connect:Direct process are shut down immediately.
For more information see the following resources:
• Connect:Direct for UNIX Release Notes
• Connect:Direct for Windows Release Notes
Configuring Connect:Direct for UNIX for Server and Upgrade Management
About this task

Control Center Director upgrades and applies maintenance to Connect:Direct through a Connect:Direct
Agent instance. Agent is included with the Connect:Direct software when it is at a required level of
maintenance for Agent inclusion.
To successfully move to a Connect:Direct version that supports a Control Center Director deployment,
there are a few scenarios to consider. Review the actions below in order to optimize your update
experience:
• Download the required maintenance version of Connect:Direct software. For more information go to Fix
Central.
• Certificate-based authentication is enabled when you install and configure Connect:Direct Secure Plus
for UNIX.
Procedure
1. Configure the Agent listening port that Control Center Director will use to communicate with the Agent.
agent.port=<port> [Default:1365]
The Agent is now set to automatically listen for incoming connections from Control Center Director.
Attention: With multiple Connect:Direct instances on the same system you’re likely to run into
port conflict issues unless you allocate a unique Agent listening port per instance.
It is also recommended that having upgraded an instance, its unique port number must be
applied before upgrading the next instance. This prevents potential errors that you could
encounter during an upgrade process due to port conflict.
2. Configure the Control Center Director Open Server Architecture (OSA) URL, the target location where
Agent posts all the events to Control Center Director.

osa.rest.url=https;//<ip/hostname;port>/osa/events/post:
[Default:<blank>]
Note: Ensure that you insert a ';' and not a ':' between hostname and port and after https.
3. Set the following property to enable Agent to post all events to Control Center Director except when
set to Y.
osa.disable=N
4. Invoke the following script for changes to take effect. This script is available
atcdinstallation_location/install/agent/bin.
startAgent.sh
Configuring Connect:Direct for UNIX for License Governance

Set the following parameters (initparms) to automate license metrics collection from Connect:Direct for
UNIX.
Table 12. Initialization Parameters

Parameter (initparm) Possible Values
license.edition • Premium
• Standard
• Solo
• Default: Blank (undefined)
license.type • Production
• Non-Production
• Default: Non-Production
license.pvu A non-negative integer

• The license.pvu parameter is only applicable
for Connect:Direct Premium licenses
• This value can be calculated using the IBM
License Metric Tool (ILMT) or it can be looked up
at the IBM Processor Value Unit licensing
website.
• Default: 0
Note: All three Initparms can be unset and a user does not have to supply a value.
Solo license edition type constraints:
• A warning message is logged if the number of Netmap entries in netmap.cfg exceeds 2.
• A warning message is logged when a transfer is initiated with third or later remote entry, in order of
appearance.
• The number of concurrent sessions is restricted to 2 or fewer

Configuring Connect:Direct for Windows for Server and Upgrade Management
To successfully move to a Connect:Direct for Microsoft Windows version that supports a Control Center
Director deployment, there are a few scenarios to consider. Review the actions below in order to optimize
your update experience:
• Download the required maintenance version of Connect:Direct for Microsoft Windows software. For
more information go to Fix Central.
• Certificate-based authentication is available when you install and configure Connect:Direct Secure Plus
for Windows.
You can supply all of the information needed to configure Connect:Direct Agent instance by setting the
following properties when you install Connect:Direct Secure Plus for Windows package:
– Agent Application Interface Port
– Control Center Directory's Agent Event Repository URL
For complete installation procedure see, Install Connect:Direct for Microsoft Windows and Optionally
Connect:Direct Secure Plus. For instructions to perform silent/unattended installation see, Silent
Installation of Connect:Direct for Windows.
Alternatively, set the following parameters (initparms) to configure Connect:Direct Agent instance for
Connect:Direct for Windows. For more information on how to change initialization parameters (intiparms)
see, Changing Initialization Parameters.

Parameter (initparm) Description
agent.port Enter port details here to configure the Agent

listening port that Control Center Director will use
to communicate with the Agent.
Default: 1365
With the port configuration complete, Agent is now
set to automatically listen for incoming
connections from Control Center Director.
Attention: With multiple Connect:Direct
instances on the same system you’re likely
to run into port conflict issues unless you
allocate a unique Agent listening port per
instance.
It is also recommended that having
upgraded an instance, its unique port
number must be applied before upgrading
the next instance. This prevents potential
errors that you could encounter during an
upgrade process due to port conflict.
osa.rest.url Provide the Event Repository URL to configure the

Control Center Director Open Server Architecture
(OSA) URL, the target location where Agent posts
all the events to Control Center Director.
osa.rest.url=https;//<ip/hostname;port>
/osa/events/post:
The default is None.

Table 13. Initialization Parameters (continued)
Parameter (initparm) Description
osa.disable Enables Agent to post all events to Control Center

Director except when set to Y.
The default is N.
Configuring Connect:Direct for Windows for License Governance

Set the following parameters (initparms) to automate license metrics collection from Connect:Direct for
Microsoft Windows.

Parameter (initparm) Possible Values
license.edition • Premium
• Standard
• Solo
• Default: Blank (undefined)
license.type • Production
• Non-Production
• Default: Non-Production
license.pvu A non-negative integer

• The license.pvu parameter is only applicable
for Connect:Direct Premium licenses
• This value can be calculated using the IBM
License Metric Tool (ILMT) or it can be looked up
at the IBM Processor Value Unit licensing
website.
• Default: 0
Note: All three initparms can be unset and a user does not have to supply a value.
Note: Ensure that you set the Statistics field to All when you define a User Authority for a Connect:Direct
for Microsoft Windows user. Setting to All enables all process access to license statistics. For more
information see, Defining User Authority. This applies to the user that Control Center Director connects as
using Certificate-Based Authentication.
Solo license edition type constraints:
• A warning message is logged if the number of Netmap entries in netmap.cfg exceeds 2.
• A warning message is logged when a transfer is initiated with third or later remote entry, in order of
appearance.
• The number of concurrent sessions is restricted to 2 or fewer
Installing Control Center Director
Before you begin

Ensure that you have installed a Database server. For more information see, “Before you set up the
database” on page 11.

About this task
The following procedure describes steps to install Control Center Director on a UNIX operating system.
Other available installer by platforms are:
• IBM_CCDirector_1.0.0.0_AIX_x64.tar.gz
• IBM_CCDirector_1.0.0.0_Win_x64.exe
• IBM_CCDirector_1.0.0.0_zLinux_x64.tar.gz
Note: Do not install as root. If you do not have sufficient privileges, use chmod u+x to execute the script.
Procedure
1. Untar the installer .tar.gz file.
% tar -zxvf IBM_CCDirector_1.0.0.0_Linux_x64.tar.gz
The following files are extracted:
ICCDirector.bin
2. Confirm that you have sufficient privileges to run the following script file.
% ./ICCDirector.bin
3. The installation menu appears. Respond to each prompt to proceed to the next step and complete
installation.
Directory Structure
The following figure illustrates directory structure after a successful installation:
|---- bin
|---- db
|---- web
|---- UninstallerData
|---- jre
|---- license
|---- log
|---- packages
|---- conf
Installing maintenance and fixes

You can install Control Center Director maintenance and fixes in Microsoft Windows, UNIX, zLinux, and
AIX platforms.
Before you begin

• Download the iFix from Fix Central website and install the latest iFix available.
• To extract the installer use the following command format on UNIX platform:

unzip IBM_CCDirector_1.0.0.0_Linux_x64_<iFix_FixPack_name>.zip
About this task

The following procedure describes how to install Control Center Director maintenance and fixes:
Procedure
1. Close Control Center Director Web Console and RESTful API interface.
2. Run the following utilities:
a) For Windows platform, invoke stopEngine.bat to stop the Control Center Director engine and
stopWebAppServer.bat to stop Control Center Director Web Services.
b) For all other platforms, invoke killProcess.sh to stop all Control Center Director services.
3. Take a snapshot of the Control Center Director database for fall back purposes.
4. Back up \conf and \web\conf subfolder in the Control Center Director installation folder.
5. Run the installer and select the existing Control Center Director installation folder as the destination
folder.
6. For all prompts, keep the same value that was defined in the previous version and click Next.
7. Run config.bat/sh.
Note: This step is optional. Do not change database configuration and keep the same value that was
defined in the previous version.
Important: Do not select Yes for reinitialization of the database for either Production or Staging.
8. Invoke runEngine.bat/sh to start the Control Center Director engine.
9. Use Web UI URL supplied at Installation Complete screen to access Control Center Director Web
Console.
Configuring Control Center Director
About this task

The Control Center Director configuration utility referred to here as the configuration script is a menu
driven command-line utility for configuring the Control Center Director.
When you run the configuration script in prompt mode, and are prompted for values, the applicable
default value is displayed in brackets at the end of the prompt. If you enter no value, the script uses the
default value. The default value also provides an example of the format of the value that is required.
The default location for the configuration setup script is: \ControlCenterDirector\bin.
You must login as a Control Center Director administrator who has permission to administer the Control
Center Director server configuration before you run the config.sh script.
Note: The following procedure describes steps to configure Control Center Director on a UNIX operating
system.
Procedure
1. Log in to the target system on which the product installation resides
2. Open a command-line shell and go to the \common\bin subdirectory of the product installation
directory. For example: cd c:\ControlCenterDirector\bin
3. Invoke the following script and respond to the prompts in each section.
./config.sh

4. The utility starts and prompts you to enter details in the KeyStore and TrustStore Configuration
section.
-------------------------------------------------------------------
Config step: Keystore / truststore configuration ...
Warning: Specify a valid keystore.(See the documentation to build one)
Otherwise the secure connectors may not start.
--------------------------------------------------------------------
Keystore and truststore configuration ...
Provide the path to your java keystore file [../conf/security/CCenter.keystore] :
/home/CCD/KEYSTORE
Please provide password to the keystore (at least 6 chars, no blanks) :
Re-enter Password
Enter Alias for Key: [CDRDEV-052] : CERT_ALIAS
Provide the path to your trust store file
[/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64/jre/lib/security/cacerts] :
/home/CCD/TRUSTSTORE
You provided the following value(s)
Keystore file path: /home/CCD/KEYSTORE
Keystore password: ********
Key Alias: CERT_ALIAS
Truststore file path (optional): /home/CCD/TRUSTSTORE
You are using the default truststore password.
Are the values that were entered correct? (Y/N) [Y]
Control Center Director uses certificate-based authentication to secure connection with

Connect:Direct Server. For more information on generating KeyStore see, “Setting up Control Center
Director Keystore” on page 18.
5. In the JDBC Driver File installation section, enter the database type and JDBC driver details
required to connect to your database server.
The following section describes the configuration prompts for a SQL server database type.
For connection parameters for other database types see, Database connection parameters for Oracle
and Database connection parameters for DB2.
6. In the Database Connection Parameters Configuration section, enter database connection details.
7. Use the Administration User configuration section to create a Control Center Director administrator
user and to set up its credentials.
8. In the Event Processor (Engine) Name Configuration section, enter Control Center Director Engine
name.
9. In the Engine Time Zone Configuration section, enter a time zone value for the Engine. If the source
installation and target installation were not in the same time zone, you must specify the time zone.
10. In the Web Services Configuration section, enter appropriate connection details. Control Center
Director uses Web Server connection details defined here to connect to Control Center Director's Web
Services.
11. In the Package path configuration section, enter the package directory properties where the
Connect:Direct packages are made available.
12. In the E-mail server (SMTP) Configuration section, enter the e-mail server connection and SMTP
server administrator e-mail details.
13. In the External Authentication Server (SEAS) Configuration section, enter the connection details
here.

14. Configuring IBM Control Center Director is complete.
What to do next
1. “Recommended Installation and Configuration Sequence” on page 9
Additional Configuration Tasks

The following sections define additional configuration tasks.
Exporting Connect:Direct Server Roster from Control Center into Control

Center Director
The exportCDServersFromICC and importServers utilities are intended to provide a simple method
for importing and exporting server roster data from the ICC (UNIX-only) configuration database using
regular text files in an XML-type format.
IBM recommends Connect:Direct servers in your deployment be configured to be dynamically discovered
by Control Center Director or add servers via. Web Console before you monitor them.
Note: If the IBM Control Center instance is a multi-EP environment, then all the nodes on that
environment must be running for the export to work.
The following steps summarize how Export/Import facility is in implemented in your Control Center
deployment:
1. Invoke the exportCDServersFromICC.sh utility to export Connect:Direct server roster data from
the source entity that is, IBM Control Center instance. The target application here is Control Center
Director that reads the server roster data.
This utility prompts the user for an IBM Control Center user ID/password and a passphrase. It outputs
all configuration data into a folder in conf folder. Example, conf/conf-exportedServers.
2. Move the IBM Control Center's output folder (conf) and its content to /conf/services/nodes
where it can be accessed by Control Center Director. Connect:Direct Server roster data is now ready to
be imported into Control Center Director.
3. Invoke the importServers utility to import the Connect:Direct server roster data into the target
entity that is, Control Center Director.
This command line utility prompts the user for the passphrase specified in step 1 and the location
where the exported server roster data is available for import (see step 2).
4. Restart Control Center Director for changes to take effect. Log in to the Web Console to view and
manage Connect:Direct servers available in your environment.
Exporting Connect:Direct Servers Roster from Control Center Director into

Control Center
About this task

The exportCDServersFromCCD and importServers utilities come packaged into the Control Center
Director installer and intend to provide a simple method for exporting server roster data from the Control
Center Director configuration database using regular text files in an XML-type format.
IBM recommends Connect:Direct servers in your deployment be configured to be dynamically discovered
by Control Center Director or add servers via. Control Center Director Web Console before you monitor
them.
Note: Export Connect:Direct server roster out of Control Center Director feature is only available for IBM
Control Center v6.1.2.1 and above users.

The following steps summarize how Export/Import facility is in implemented in your Control Center
Director deployment.
Procedure
1. Invoke the exportCDServersFromCCD utility to export Connect:Direct server roster data from the
source entity that is, Control Center Director instance. The target application here is Control Center
that reads the server roster data.
This utility prompts the user for Control Center Director user ID/password and a passphrase. It outputs
all configuration data into a folder in conf folder. Example, conf/conf-exportedICCServers.
2. Move the Control Center Director 's output folder (conf) and its content to /conf/services/nodes
where it can be accessed by Control Center. Connect:Direct Server roster data is now ready to be
imported into Control Center.
3. Copy the importServers utility from \<ICCDirectorInstallationDirectory>\bin into target
entity installation directory that is, Control Center.
4. Before you invoke the import utility in the destination directory that is, Control Center, replace any
references of the source installation directory, with ‘..’.
This ensures the import utility is executed in the destination directory which is, Control Center.
5. Invoke the importServers utility to import the Connect:Direct server roster data into the target
entity that is, Control Center.
This command line utility prompts the user for the passphrase specified in step 1 and the location
where the exported server roster data is available for import (see step 2).
Note: As of Control Center Director v1.0.0.1, importServers utility comes packaged with the Control
Center Director installer package. Support to include this utility in Control Center installer package is
planned for in a future release of IBM Control Center.
6. Invoke runEngine utility to restart Control Center for changes to take effect.
You can now view and manage Connect:Direct servers available in your Control Center environment.
Taking the first steps after installing Control Center Director

After the installation is complete, Control Center Director can be instrumented using either one of the
following interfaces:
• Web Console
• RESTful APIs
After installation and configuration is complete the screen displays Control Center Director Web Console,
RESTful API, and OSA URL in the following format:
Installation and Configuration Complete Screen Display
ControlCenterDirector-Version has been successfully installed to: $USER_INSTALL_DIR$
ControlCenterDirector Web Console is available at:

https://<hostname:port>/ccd-ui/index.html
ControlCenterDirector Swagger RESTfulAPI documentaion is available at:

https://<hostname:port>/swagger-ui.html
OSA URL for Connect:Direct Server

https://<hostname:port>/osa/events/post
Accessing Control Center Director Web Console

Before you begin

• Ensure that you have enabled Certificate authentication for Connect:Direct.
• Control Center Director Web Console can be viewed only in English language and displays Date/Time-
based information in the user local time format. Recommended Control Center Director Web Console
resolution is 1366 X 768 (min) and 1600 X 900 (max).
Procedure
To access the Control Center Director Web Console in a web browser:
1. Launch a browser and navigate to the URL https://<hostname:port>/ccd-ui/index.html,
substituting the IP of your Web server.
Note: URLs provided at the end of the installation process with the correct IP address or DNS
hostname.
You can use either login as a user with full access (admin) or the restricted access (user) role
assigned. If you are logging into the Control Center Director Web Console for the first time, login as
user with full access role.
2. You should see the Control Center Director login page. Log in with the credentials set when you
configure Control Center Director using the config.sh script.
Successful logging will get you to the Dashboard. What your Dashboard displays depends on how you
have configured your Control Center Director instance and role assigned to you. For more information
see “Dashboard” on page 32.
Accessing RESTful APIs

Launch any supported browser and enter the following URL to invoke Control Center Director RESTful
APIs.
https://<hostname:port>/swagger-ui.html
For more information see, “Accessing RESTful APIs resources” on page 39.
Command Line Utilities Reference

Control Center Director provides utilities and functionality to allow all administrative operations to be
performed via scripts.
Note: Utilities listed below require root privileges to be executed.
Control Center Director supports script-based configuration and most of its software runs as a service
after installation is complete. The utility scripts come handy and allow users to manually perform
functions like stopping the Web Server, Starting Engine etc. For example, administrators can use
config.sh utility to configure components such as SQL database by executing this script that comes
bundled with the product software.
The default location for the configuration setup script is: /<installationdirectory>/bin directory.
The following table provides a summary of the utilities (.sh and .bat) and their functions.
Table 15.
Utility Purpose
startWebServer Reads the configuration file for the Web server
process and starts the server process.
stopWebServer Reads the configuration file for the Web server
process and starts the server process.

Utility Purpose
showProcs Displays all Control Center Director processes
running in your environment.
killProcs You might want to stop the Control Center Director
components and system to carry out some system
maintenance.
Use KillProcs.sh to terminate all Control Center
Director processes running in your environment.
stopEngine.sh Reads the configuration file for the Engine/Web

Server process and stops the Control Center
Director Engine and Web Services process.
stopEngine.bat Reads the configuration file for the Engine process
and stops the Control Center Director Engine
process.
To stop Web Services invoke
stopWebServer.bat.
runEngine Reads the configuration file for the Engine/Web

Server process and starts the Control Center
Director Engine and Web Services process.
config Invoke this script to set up Control Center Director
and its components.
runDataCollector The Data Collector script extracts the current state
of your Control Center Director deployment to help
IBM Support troubleshoot an issue.
It collects logs, configurations, system metrics, and
performs backup of the database without
interrupting its operations.
A separate archive is created each time that this
utility is run, in the format CCDdataTimeStamp.zip,
multiplying the disk space requirements.
Note: Ensure that you have sufficient free disk
space (at least 1GB), as the amount of data that is
collected can be large.
createTestCA Invoke this utility to create a Certificate Authority

and use it to sign own certificates.
Administrators can invoke this script in testing
scenarios to create a CA signing certificate and use
it to sign certificates.
exportCDServersFromICC This utility exports all of your Server configuration

data from a source IBM Control Center instance.
The format of the exported data is an XML-type
format and each record in the exported data
corresponds to a configuration record in the IBM
Control Center configuration database.

Utility Purpose
importServers This utility imports the same XML type formatted
data used by exportCDServersFromICC into
exportCDServersFromCCD This utility exports all of your Server configuration
data from a source Control Center Director
instance.
The format of the exported data is an XML-type
format and each record in the exported data
corresponds to a configuration record in the
Control Center Director configuration database.
Uninstalling Control Center Director
About this task

To uninstall the Control Center Director, follow the steps given below.
Procedure
1. Change the Control Center Director installation directory:
% cd UninstallerData
2. Issue the following at command line to uninstall the software:
% ./UninstallControlCenterDirector.sh
Emergency Restore
About this task

• The first step during Control Center Director upgrade management of a Connect:Direct server is to
perform a backup of the Connect:Direct product and all its system files. When any error occurs during
upgrade, the Connect:Direct server is automatically restored from backup.
• However, it is possible that after a successful upgrade a customer might observe behavior in the product
that is undesirable. In that case, a customer may wish to perform an emergency restore.
• Emergency Restore will update the Connect:Direct product and system files to its state as it was before
upgrade processing began.
Note: Any product activity performed after the Connect:Direct servers are upgraded and before
Emergency Restore is performed, will be lost.
This procedure describes the emergency restore operation using the REST API. Note that, with v1.0.0.2,
Control Center Director extends web console support for the Emergency Restore procedure for
Connect:Direct for UNIX v6.1 and above. Support for Connect:Direct for Windows v6.1 is not available in
this Fix Pack release. This will be supported in an upcoming maintenance release.
Control Center Director users can now schedule an Emergency Restore Job from the Deployments and
Servers view. For more information see, “Deployment Management” on page 34 and “Server
Management” on page 33.

Procedure
1. Access RESTful API resources
2. Invoke /server/emergencyRestore API
3. Enter the Server names that you'd like to restore
in the following request format:
"serverNames": [
"ServerNametoRestore"
]
4. Response structure displays the event ID as follows:
{ "data": <eventID> }
5. To validate the restore status, invoke /server/get/event/status/{eventId}

6. The response structure displays the restore status:
{
"data": "SUCCESS"
}
Control Center Director Web Console

IBM Control Center Director, an activity management and monitoring product, helps you meet the
following needs via its Web Console. Log in to the ICC Director Web Console to create, list, and manage
tasks to:
• Discover resources faster
• Govern License usage
• View Connect:Direct Server and Agent status
• Mange upgrades
• Manage Servers
Note: For detailed step-by-step flows, see Step by Step User Guide.
Dashboard
Click Dashboard to get insight into the health and performance of managed Connect:Direct servers in
your environment.
Data that you view on the Dashboard depends on what your role is and how you have configured your
Control Center Director instance.
When Connect:Direct server roster is imported or servers are dynamically

discovered
The landing page displays Dashboard tab on the Control Center Director navigation panel with metrics
and message broadcast information as segments or panels.
• Job status panel that displays your overall deployment health status
• Environment Overview that displays number of Connect:Direct nodes by environment type available in
your deployment
• Broadcast panel displays brief yet important alert messages for Control Center Director Web Console
users.

Note: Your user role also determines what displays on your dashboard. For example, if you are a
restricted user, the Environment Overview displays a pie chart visualization of assets assigned to you, by
environment.
Zero State view when Server Roster is not available

• When no Server Roster data is available in your deployment, the landing page displays the zero-state
view on Dashboard. The zero-state view also displays three panels, Environment view, Job status, and
Broadcast messages.
• Since there is no data available to be monitored yet, the panels display recommended steps an
Administrator must complete to get started.
Server Management
Before you begin

• IBM strongly recommends configuring Connect:Direct servers in your deployment such that they are
dynamically discovered. However, you may find it useful to import server roster into Control Center
Director from IBM Control Center via. command line utilities. Doing so enables you to observe which
servers have been configured to be managed by Control Center Director and those which have not. For
more information see, “Exporting Connect:Direct Server Roster from Control Center into Control Center
Director” on page 27.
• Except for when Connect:Direct servers in your deployment are configured to be dynamically discovered
or server details are imported from Control Center available in your deployment, you must add a server
before you can monitor it.
Note: Support to schedule upgrades (Deployments) is not available for Servers added and grouped
through Control Center Director Web Console unless they have been upgraded to the appropriate
maintenance level and have been configured for Control Center Director support.
• Identify the number, type of servers, their connection details, and other properties for servers that need
to be monitored, managed, or both in your environment.
Key Concepts - Servers

When you work with Servers tab, there are three main approaches you can use to manage Connect:Direct
Servers in your deployment:
• Add Servers in your environment and logically group them (Server groups) depending on your
organization's needs. With server groups, user roles can be associated to specific server groups.
• List Connect:Direct Servers/Server Groups available in your environment and view related details such
as, server properties, connection details, deployment history, license usage, administrator contact
details, and server settings.
• Manage Connect:Direct Server/Server Group available in your environment such as, view server details.
Note: Your User role also determines what is displayed in Servers view. Example, if you are a restricted
user, Servers view displays only those server groups that are assigned to the user with a restricted role.
Initial Administrator work flow: Servers

The following steps shows the initial work flow for a Control Center Director Web Console Administrator:
1. Add a new server*
a. Click Add New to add a new server to your environment
2. Create a new Server Group*
a. Click Create New to create a new Server Group

b. Add existing server groups from the pool by using the Server Groups field, or add other existing
servers by using the Servers field.
3. Manage Servers
a. Click All Servers to view and manage an existing server
b. Select an entry and click edit, delete, start, stop or export details of an existing server.
c. Select an entry to display server details view. This view displays server properties such as,
connection details, settings, contact details, and deployment history.
d. To schedule an Emergency Restore procedure that restores the Connect:Direct product and system
files to its state as it was before upgrade, click Emergency Restore from the Server details view.
4. Manage Server Groups
a. Click All Groups to view and manage existing server groups.
b. Select an entry to view server group properties.
c. Select an entry and click edit, delete an existing server.
* Skip step 1 and 2 if Connect:Direct servers in your deployment are configured to be dynamically
discovered or the server details are imported from ICC available in your deployment.
For detailed step-by-step walk-through see, Control Center Director Step by Step User Guide.
Deployment Management
Click Deployment tab on the Control Center Director Web Console navigation menu to seamlessly
upgrade Connect:Direct servers in your deployment to a later version.
Before you begin

• Download the latest supported Connect:Direct fix pack on your local computer.
• Ensure that you have configured your Control Center Director instance to define where the
Connect:Direct packages will be made available for auto-discovery.
• Control Center Director Administrator must manually secure and assign privliges to the packages
directory before executing any upgrade and/or applies maintenance operations to Connect:Direct
nodes.
• Auto sense feature enables Control Center Director to detect and process the packages after they are
added into/removed from the designated directory. It can take up to 15 minutes for the packages to
show up under the Deployment view.
• In some cases after a failed upgrade, the fastest solution is to roll back to a previous release you were
using. For more information see, “Emergency Restore” on page 31
Key Concepts: Deployment

• When you work with Deployment, there are two main approaches that can be used to manage the
upgrade process in your deployment.
Click:
– Packages to list and manage all Connect:Direct packages auto-discovered by your Control Center
Director instance
– Deployments to create a job (schedule upgrade) and list a job status (upgrade state)
• Your user role also determines what is displayed in Deployments view. For example, if you are a
restricted user, clicking Create Job>Select Server Groups/Servers displays only servers/groups
assigned to the user.
• To view the upgrade status of a server, go to Deployments > All Jobs tab.
– The Type field displays Completed if all the servers and/or server group are processed successfully

– The Status field displays Partial if some servers in a server group have upgraded successfully while
some did not
After a package is displayed in the Packages view, it can be scheduled for an upgrade throughout in your
current deployment.
Initial Administrator Work flow - Deployment

1. View Packages
a. Click Packages>All Package to list all Connect:Direct packages auto-discovered by your Control
Center Director instance.
b. Select an entry to view package details.
2. Manage Packages
a. Click Packages>All Package
b. Select an entry and click Deploy to schedule an upgrade (job).
c. Select an entry and click Export to export and view package details in a .csv format. You can also
export the entire page listing in a .csv format.
3. Schedule a maintenance job (Upgrade) or an Emergency Restore job.
a. Click Jobs>Deploy Job to schedule an upgrade (job).
b. Select Maintenance Job from the Job Type drop-down menu to schedule an Upgrade and enter
the rest of the form details as required.
To schedule an Emergency Restore procedure that restores the Connect:Direct product and system
files to its state as it was before upgrade, select Emergency Restore Job from the Job Type drop-
down menu.
Note: For an Emergency Restore Job, Servers and Server Groups display servers and server
groups with valid restore points.
c. Select Start Now/Schedule for Later/Hold for Later to schedule the job.
d. Click Schedule.
Scheduled job is now listed under the All Jobs view.
4. View and manage Jobs regardless of their state
a. Click Jobs>All Jobs to view all jobs in your environment.
b. Select an entry to view job details.
c. Select an entry and click Export to export and view job details in a .csv format.
d. Select an entry and click Delete to remove a held state job if it is no longer required.
e. Select an entry and click Edit to edit job.
Note: A job that is In Progress state can be stopped but not edited.
5. View and Manage Jobs by their current or recent state.
a. Click Jobs to view all jobs in your environment by state that is, In Progress, Held, Scheduled, and
Completed.
License Management
Click Licenses tab in the Control Center Director navigation menu to view license usage metrics for
Connect:Direct servers deployed in your environment.
License Governance targets delivering clear benefits to your organization such as, compliance auditing,
resource change tracking, and troubleshooting. Following licenses are available in distribution for IBM
Connect:Direct:

• Premium Edition z/OS
• Premium Edition Distributed
• Standard Edition
• Solo Edition licenses
Before you begin

Configure your Control Center Director instance to access Connect:Direct servers license data.
Key Provisioning Concepts

Licenses provides information that helps determine your overall compliance against a license type per
environment.
Use Licenses view:
• to display licenses types and metrics available by server in your environment that is, Production, Non-
Production, or Unconfigured
• current license usage by license type in your environment
• to export usage data into a report (csv format) to ensure compliance auditing
• for a consolidate view of license details and other licensing parameters for all servers bundled under the
selected Server Group
Note: Your user role determines what is displayed in Licenses view. Example: If you are a restricted user,
clicking Distribution displays only license usage data only for servers/groups assigned to the user.
Note: The license snapshot displays data by an offset from UTC that is, UTC+2:00.
Initial Administrator work flow: Licenses

1. View server distribution by license type in a production environment
a. Click Production to display server distribution by licenses type in production environment
b. View current usage and metrics by license type for all servers in a production environment
c. Select an entry and click Export to generate license usage report in a csv format
d. Click an entry to observe licensing parameters for the selected server
2. View server distribution by license type in a non-production environment
a. Click Non Production to display server distribution by licenses type in a non-production
environment
b. View current usage and metrics by license type for all servers in a non-production environment
c. Select an entry and click Export to generate license usage report in a csv format
d. Click any entry to observe licensing parameters for the selected server
3. View server distribution and licensing properties in an unconfigured environment
a. Click Unconfigured to display server distribution in a unconfigured environment
b. View current usage and metrics by license type for all servers in a unconfigured environment
c. Select an entry and click Export to generate license details in a csv format
d. Click any entry to observe licensing parameters for the selected server
4. Consolidated view of license information for all child servers under a parent server group
a. Click Server Groups > select a Server Group and observe licensing details for all child servers.
b. Select an entry and click Export to generate license details in a csv format

For detailed step-by-step walk-through see, Control Center Director step-by-step User Guide.
Audit Logs
All Control Center Director user and administrator activity performed via the Web Console display as
listings in the Audit Logs view where you can view, sort, and filter them.
This view enables Control Center Director administrators to track and record any modification made to the
Control Center Director configuration objects, user authentication actions, or to their own accounts (e.g.,
changing a password). Audit logs can also be used to search, filter, view, and export all log entries that
Control Center Director records.
Audited events are stored for ninety (90) days from the date they occurred.
Note: While all audited events are logged, certain audit events such as 'Delete a Server/Server Group/Job'
appear in a read-only mode. Admins cannot perform any actions such as view, search or delete on such
events.
Key Provisioning Concepts

• Audit log entries record any modifications made to Control Center Director configuration objects such
as, Packages, Deployments, Users, Roles, and Servers using Control Center Director Web Console.
• Other user and administrator activity performed via the Web Console, such as adding a new user,
password change or user login actions
• Resulting from a change on another Connect:Direct Server/group in a Server Group
• Display original and changed values to compare audit log entries.
• You can filter and search content based on Object type and/or user type (changed by).
• Export your filtered and searched results into a CSV format.
Initial Administrator work flow: Audit Logs

1. View audit logs
a. Click Audit Logs to view all Control Center Director user and administrator activity performed via
the Web Console display as listings
b. Click any log entry to view extended details. This view, by default, displays all user activity
performed in the last 90 days. To display user activity to a certain period, enter Date range from the
date picker.
2. Enter a search string/filter criteria to view filtered results.
3. Click Export to export your filtered and searched results into a CSV format.
For detailed step-by-step walk-through see, Control Center Director step-by-step User Guide.
Users and roles Management

Click Users and Roles tab on the Control Center Director Web Console navigation menu to configure how
Control Center Director manages access control. Access control defines and restricts role-based user
access to view and manage all or a limited set of Server Groups.
Key Provisioning Concepts - Users and roles

• Access control enables Control Center Director administrators create custom Server group restricted
roles and assign them to specific users.
– Example 1: You might have a user, User1_Finance in your organization, assigned a role
Role_Team_Finance and Server group Finance_Group1.

User1_Finance is allowed partial access to Deployment to schedule upgrades only over
Finance_Group1.
– Example 2: AdminUser_Finance in your organization with role Role_Admin_Finance is allowed
complete access to Deployment to schedule upgrades over all Server groups in your environment.
• With limited access role assigned, a user can have unique login credentials
• With complete access role assigned, a user can track transactions performed for all user created with
limited access
• Following matrix describes how Server Group restricted roles affect availability of actions on the Control
Center Director
Web Console.
For example, a user with role Full access assigned to it can view all details for all Servers and Server
Groups available in its environment. Whereas, a user with limited access role assigned, can view details
for only those Servers or Server Groups that are assigned to the user.
Table 16. Role-based actions availability matrix

For a user with role... View... On Web Console displays...
Full access Users & Roles Complete view
Restricted access Blocked
Full access Audit Logs Complete view
Restricted access Blocked
Full access Dashboard - Broadcast Complete view
Restricted access Complete view
Full access Deployments - Jobs Complete view
Restricted access Partial view
Only jobs that are scheduled by
the user
Full access Deployments - Packages Complete view

Restricted access Complete view
Full access Servers Complete view
Only servers and groups assigned
to the user
Full access Server Groups Complete view

Only servers and groups assigned
to the user
Full access Licenses Complete view

Server and Groups the user
assigned to the user

Initial Administrator Work flow - Users and Roles
1. Create Role(s)s
a. Click Create Role to add a new role
2. Create User(s)
a. Click Create Users to create a new user and assign a role created in Step 1
3. Manage Roles
a. Click List Roles to view and manage existing roles
4. Manage Users
a. Click List Users to view and manage an existing user
5. Deleting a User
a. Click List User to delete an existing user if it is no longer in use
Caveats
While you can't edit the username associated with a user, you can change the Role, IP Address and Email
fields.
RESTful APIs Support

RESTful APIs can be used to construct, execute requests, and inspect results from within your browser so
as to seamlessly integrated with external business applications. Control Center Director RESTful API
documentation provides RESTful APIs for corresponding Control Center Director functions such as,
submitting a job, POST Job.
Web Services RESTful API documentation can be accessed over a web browser using the Swagger UI
(REST API documentation framework) that helps developers design, build, and invoke RESTful Web
services.
Accessing RESTful APIs resources
About this task

• IBM Control Center Director Web Services automatically generates REST API documentation during API
creation.
• A swagger.json file is created that can be viewed in a Swagger document editor such as Swagger UI.
• RESTful API documentation lists all RESTful API resources and operations that can be called on those
resources.
Note: Before you begin, ensure that you restart the Control Center Director web server.
Procedure
1. Explore Control Center Director RESTful API resources at:
https://<IP_Address>:<Port>/swagger-ui.html
The login page appears.

2. Enter connection details for the target Connect:Direct node.
The dashboard displays a list of all RESTful API resources bundled under a relevant category. Example,
category Jobs includes the following API resources such as, DELETE Job, GET Job, GET List, PUT
Update Job etc.

3. Before you access Control Center Director REST APIs, you must first authenticate yourself with Auth
API.
• Invoke /api/auth/login
• Enter your user name and password. A bearer string is generated with a token.
• Copy the value of bearer token and click Authorize.
• Enter the bearer token value and click close.
Troubleshooting
The following sections describe scenarios, workarounds, and solutions to troubleshoot issues and recover
from errors.
Troubleshooting deployment scenarios

Control Center Director provides tools for troubleshooting and recovering from errors, such as log files.
When you encounter an issue with your deployment log files should be the first place you look to assist
you with the troubleshooting process.
The following table describes:
• Relationship between common deployment scenarios and their associated log files
• Common deployment scenarios-related FAQs
Table 17. FAQs and Log locations

Scenario/Question Details
Gathering logging events runDataCollector should be used to extract and report the
current state of your Control Center Director deployment to help IBM
Support troubleshoot an issue.
It collects logs, configurations, system metrics, and performs backup
of the database without interrupting its operations and stores the
information in a .zip archive file. You can then send the archive file to
IBM Support to help diagnose and fix problems.
Deployment-related log files Log file is available at: ControlCenterDirector\log

Look for file name with format: Engine_YYYYMMDD_TIMESTAMP
Control Center Director Engine • Log file is available at: ControlCenterDirector\log

(Hearbeat)-related log files
• Look for [NODENAME]INFO ServiceMonitor for further details
• Alternatively, look into CC_SERVER_COMPONENT table updated
with details ServerID with status UP
License Data-related log files Look for LicenseDataCollector string in the log file for more
details.

Table 17. FAQs and Log locations (continued)
Customizing logging levels to suit Set logs levels to DEBUG to start recording logs and issue the
logging requirements stopEngine/runEngine utility for changes to come into effect.
File path:
• Control Center Director Engine logs
/Conf/enginelogger.xml
• Connect:Direct Agent logs
CDInstallationDirectory/install/agent/bin/
log4j2.xml
Agent state is down, whereas Agent polling interval is 5 min. Invoke pollAgent.sh to validate if
initial registration occurred via Agent is running on Connect:Direct Server.
Agent. To troubleshoot look for agent.log file available at following log
location:
\cdinstall_dir\install\logs
How does agent communicate At startup, agent posts an OSA to communicate that Agent is up. This
with Control Center Director? helps Control Center Director in Server auto-discovery.
During the upgrade process, agent sends OSA notifying Control
Center Director about the upgrade status.
How does Agent distinguish Agent receives a unique key, correlation-id with each upgrade and
between different upgrades it uses it to distinguish and also prefix to the log files generated with
performs? each upgrade.
Auto Discovery-related failure 1. Inspect agent.log for further diagnosis and to isolate the issue.
2. One possible reason why Control Center Director could not
discover Connect:Direct Server in your deployment is because it
was not configured correctly.
3. Other possible reason could be to do with updates made to the
osa.url field that ensures Connect:Direct is auto discovered by
Agent provides a file polling mechanism that runs at a
preconfigured polling interval (cpiPollTime) and detects any
changes in osa.url field. If the osa.url field is modified
during the polling interval the changes will only take effect at the
end of the scheduled run.
4. Another possible reason could be due to multiple Connect:Direct
instances, you’re likely to run into port conflict issues unless you
allocate a unique Agent listening port per instance. It is also
recommended that having upgraded an instance, its unique port
number must be applied before upgrading the next instance. This
prevents potential errors that you could encounter during an
upgrade process due to port conflict.
5. One possible reason could be due to incorrect certificate-based
configuration that is, either the Connect:Direct certificate is not
trusted by Control Center Director or vice versa.

Table 17. FAQs and Log locations (continued)
Will a bulk server upgrade • Control Center Director handles a bulk server upgrade process in
operation, when stopped, bear an batches. Batch upgrade groups servers together so that Control
impact on servers upgrade for all Center Director can execute upgrade operations in parallel.
including servers in the
• If an error occurs during the upgrade process Control Center
operation?
Director will continue to process remaining upgrade operations in
the batch.
• Batch size is set to 25 servers by default and can be modified by
the Administrator.
• Edit the batch-size property in DeploymentService.xml
available at: conf/services/system.
• stopEngine/runEngine utility for changes to come into effect.
Some servers under Failed • This occurs is when a server was not upgraded due to multiple
Category in Job details view failure during a bulk upgrade process
show up as Suspended by • When an error occurs during bulk upgrade process, Control Center
System. Director will continue to process remaining upgrade operations
provided it meets the failure percentage threshold set.
• For example, for a batch size of 30 servers, if 15 jobs fail (50%)
server status is displayed as Suspended by System.
• Failure percentage is set to 40% by default and can be modified by
the Administrator.
• Edit the failurePercentage property in
DeploymentService.xml available at:conf/services/
system.
Server upgrade Job scheduled • Control Center Director is set to poll Agent and wait for any
returns the following error: Job response for up to 3600 seconds (default) to verify if the upgrade
marked failed as OSA from request is being processed. When this threshold is exceeded the
Agent not received. Job is marked as failed with error: Job marked failed as OSA
from Agent not received.
• To modify the interval edit
lastOSARecivedTimeDifferenceInSecToMarkJobFailed
property in DeploymentService.xml available at:conf/
services/system.
Is Agent polling interval by ICC • Control Center Director Engine is set to make 3 attempts every 60
Director Engine configurable? seconds to poll Agent to verify Agent activity.
• To modify the polling interval and number of attempts edit the
following parameters in DeploymentService.xml available
at:conf/services/system:
– AgentRestCallMaxNumberOfTime
– timeBeforeNextRestCallInSec
Note: Configuring Agent polling interval only applies to servers that
are configured to be auto-discovered by Control Center Director.

Troubleshooting Web Console issues
The following table describes possible reasons for occurrence and troubleshooting tips for issues that
most frequently occur with the Control Center Director Web console.
The quickest way to troubleshoot broken interface elements, misbehaving blocks, and interactive
functionality issues is to check the browser console to view errors. To access developer tools right-click
anywhere on the web page and select Inspect Element from the context menu. Click Network tab to view
further details.
Alternatively, browser developer tools can also be accessed for:
• Mozilla Firefox via Menu>Web Developer >Network
• Google Chrome via Menu>More tools>Developer Tools>Network
• Microsoft Edge via F12> Developer Tools > Network tab
After opening the browser console, you can start looking for errors. Errors will be displayed differently in
each browser, but generally will be color coded, labeled, or marked with an identifying icon. If you find an
error, make sure to copy the error name, location, and line number.
Table 18. Troubleshooting Web Console issues

Issue Possible Reason Solution/Workaround
Licenses
Some Connect:Direct servers • One possible reason could be • See compatibility matrix to find
show up under Licenses view as that you have added a out IBM Connect:Direct
Unconfigured Connect:Server version that versions compatible with ICC
ICC Director does not support. Director. See, Compatibility
• Another possible reason could Matrix.
be that this Connect:Direct • Ensure that initparms that are
server is not configured to used to automate license
support ICC Director. metrics collection from
Connect:Direct for UNIX/
Windows are set.
See, “Configuring IBM
Connect:Direct support for
Control Center Director” on
page 19.
Unable to edit/delete Server Licensing view restricts users To edit or delete a Server group,
Groups from within the from editing server groups under click Servers>All Groups tab and
Licenses>Server Groups tab the Server Groups tab in the left hover over Server group.
navigation pane.
Server count displayed against an This could be possible because
environment type tab such as ICC Director records and displays
Production (left navigation pane) server entry in the listing each
does not match entries displayed time you restart a server.
in server listing by license type
displayed in the pane on the
right.
Multiple entries for the same
server in a environment type

Table 18. Troubleshooting Web Console issues (continued)
No Licenses information ICC Director collects licensing Licensing view displays data by
displayed under the Licenses metrics from a Connect:Direct an offset from UTC that is, UTC
view server which could be located on +2:00
a different server. Time
difference between the two
should be considered based on
UTC time and not local time.
Servers
No Licenses information One possible reason could be To view licensing metrics for a
displayed under licenses tab in that the licenses data is made particular server go to
Servers>All Servers>View available by an offset from UTC Licenses>Production (any
Server details that is, UTC+2:00. Also, the Environment type) and select a
licensing tab under Server details date from the date picker.
page is restricted to display
licensing data for only the last 24
hours.
Timezone setting is already This could be possibly because
applied to the Connect:Direct this Server is auto-discovered by
server provided UTC offset. ICC Director.
No value is populated in the It could be possible that the • Ensure that Connect:Direct
Platform, Agent Port, server details you are attempting servers in your deployment are
Architecture, and CD Server to view are for a Connect:Direct configured to be dynamically
Installation Location fields server: discovered by Control Center
under the General tab in • that is not configured properly Director
Servers>All Servers>View to relay Connect:Direct Server See “Configuring IBM
server details properties to ICC Director Connect:Direct support for
• that was added via Web Control Center Director” on
Console page 19.
• version that is not supported by • Install/Upgrade to a
ICC Director Connect:Direct version that
supports ICC Director. For more
information see, see
Compatibility Matrix.
Icon status next to the server This implies that either the
name is displayed in orange Connect:Direct Server or Agent is
unavailable.
Server listing view is missing the This is because you cannot Ensure that you decommission
Delete option in the overflow delete a server while the Agent is the Server and then attempt to
menu against a server entry still running. delete it from the Server listing
view.
Server listing view is missing the This is because you can start a
Start option in the overflow server only when the Agent is still
menu against a server entry running and the Connect:Direct
server is unavailable.

Bulk deploy option is missing This possibly occurred because • Ensure that Connect:Direct
when I check 'Select all' check the Connect:Direct servers: servers in your deployment are
box under Servers>All Servers configured to be dynamically
• Were added via Web Console
listing view discovered by Control Center
• Server composition is not Director
homogenous that is, they are
running on different platform or • Ensure that server/server
architecture groups selected are a
homogenous set in terms of
• Version is not supported by ICC platform and architecture
Director
• Install/Upgrade to a CD version
that supports ICC Director. For
more information see, see
Compatibility Matrix
Delete option is missing when I This is because you cannot Ensure that you decommission
check Select All check box under delete a server while the Agent is the Agent and then attempt to
Servers>All Servers listing view still running. delete it from the Server listing
view.
Deployments
No field data is populated under • One possible reason could be Go to Deployments>Deploy Job
Server Group/Servers in that upgrade is not supported and:
Deployment>Deploy Job for servers that are added via • Select a Package name with a
ICC Director Web Console higher/equal package version
• Another possible reason could • Enter an Operating Server type
be that scheduling a Job to that matches the Server and/or
upgrade a server and/or server Server Group being upgraded
group is constrained by the
Operating System and package
version.
Expected input for the
following fields:
– Operating System: Should
match the OS for servers
being upgraded.
– Package Name: Should be a
version higher than the
current Connect:Direct
server version.
Deploying a job returns the

Scheduling a Job to upgrade a Go to Deployments>Deploy
following error: server and/or server group is Job>Package Name.
constrained by the package
Package selected is not version the system encountered Select a higher/equal package
compatible with server(s) a Package mismatch. version and click Deploy.
included in the selected
server group(s)

A scheduled upgrade job did not • One possible reason could be • Ensure that the time on system
move into In-Progress state. that the system running ICC running ICC Director is in sync
Director is out of sync with the with your local time
server time. • ICC Director Engine is up
• Other possible reason could be
that because ICC Director picks
scheduling jobs every minute,
the Web Console has not
displayed refreshed data.
A scheduled Job fails • One possible reason could be • Select another compatible
that the package was possibly package/Add a compatible
deleted from the designated package to the designated
directory while the job was still directory and schedule the job
In Progress state again
• Another possible reason could • Verify your Agent settings/
be that Agent is down configuration. For more
• Another possible reason could information see, “Configuring
be that the Server for which the IBM Connect:Direct support for
upgrade job was scheduled Control Center Director” on
was deleted after the job was page 19.
scheduled.

Connect:Direct packages do not • View events related to • Administrators, note that auto
show up under the Deployments packages in the event log files sense scheduler is configured
tab. to isolate the issue. by default to run every 15
• One possible reason could be minutes. To change this value,
Web Console is not displaying modify
refreshed data. Auto sense package.folderWatchDela
feature enables ICC director to yInSecs parameter in
detect and process the application.properties
packages after they are added/ • See “Configuring Control
removed into the designated Center Director” on page 25.
directory. It can take up to 15 • Go to Fix Central
minutes for the packages to
show up under the Deployment • Remove the old package first
view. and replace it with the new
package.
• Another possible reason could
be that ICC Director was not
configured correctly to define
the directory where the
Connect:Direct packages will
be made available for auto-
discovery.
be that the package name is
not in the prescribed standard
IBM format as downloaded
from Fix Central.
be that you might have
attempted to add a package
that already exists in the
designated directory possibly
with a different name and/or
same content. Packages once
added to the designated folder
cannot be replaced.
Users and Roles

User is unable to log into Web User tried to access the ICC Contact your administrator to find
Console with correct ICC Director Director Web Console from an IP out your designated IP address
account credentials addresses other than the one as entered in Users and
that the user is designated to use Roles>Create User>TCP IP
and was configured by the address field.
Administrator.
ICC Director account is locked IP is locked out to provide Attempt login again in 15 min
after consecutive failed login protection against brute force (default). To configure the time
attempts login. duration that login attempts are
blocked for modify
authentication.lockdurati
on in
application.properties.

User is unable to log into Web One possible reason could be Attempt logging into the Web
Console using ICC Director that the user is configured to Console using SEAS credentials.
account credentials (user ID). authenticate using SEAS
credentials (Users and
Roles)>Use External
Authentication (SEAS)
Account activation/password reset link-related
User did not receive an e-mail • One possible reason could be • Attempt password reset
with password reset/Account that the user is trying to login procedure with SEAS ID.
activation link. using SEAS credentials. E-mails • Attempt password reset
with account activation/ procedure with a correct ICC
password reset link are only Director ID or contact your
sent if you login with a Control administrator.
Center Director Account ID.
• See “Configuring Control
• Other possible reason could be Center Director” on page 25.
that as a security consideration
ICC Director does not display
an error message when an
incorrect account ID is entered
by the user. The user assumes
that the ID was validated, and
an e-mail was sent.
be that your SMTP server
configuration is incorrect.

Web Console won't display • One possible reason could be • Verify Certificate-based
refreshed Connect:Direct server due to incorrect certificate- authentication configuration
upgrade and maintenance data based configuration • Verify Certificate-based
when its servers are set to be
• Make sure the OSA URL authentication configuration
auto-discovered by ICC Director
configured on Connect:Direct is • To download error logs for a
same as ICC Director instance failed upgrade job, go to:
is using to track the Deployments>All Jobs>View
Connect:Direct servers. Job details> Click entry next to
• It is recommended to not Failed field to display Failed
configure same Connect:Direct pop-up>Click download button.
Server to work with multiple
Extract the log file to view
instances of ICC Director. This
contents. The log file could
causes the Connect:Direct
either be:
Server to be registered with
multiple instances of ICC 1. A single file that implies
Director instances. failure even before the upgrade
started with details.
2. Multiple log files which
implies that upgrade started
but encountered an error.
Look for following primary log
file
_UpgradeByInstallAgent.
log that includes all OSAs sent
during the upgrade.
The last OSA records the
upgrade status giving failure
details with detailed
information on where the error
occurred and possible reasons
that caused the error to occur.
For further details on log files
specific to Agent Upgrade
issues, see
_UpgradeAgent_cdaiLog.l
og.
For Connect:Direct server
upgrade issues, see
_Upgrade_cdaiLog.log.
Notices
This information was developed for products and services offered in the US. This material might be
available from IBM in other languages. However, you may be required to own a copy of the product or
product version in that language in order to access it.
IBM may not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently available in
your area. Any reference to an IBM product, program, or service is not intended to state or imply that only
that IBM product, program, or service may be used. Any functionally equivalent product, program, or

service that does not infringe any IBM intellectual property right may be used instead. However, it is the
user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this
document. The furnishing of this document does not grant you any license to these patents. You can send
license inquiries, in writing, to:
IBM Director of Licensing

IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US
For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual
Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"

WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM websites are provided for convenience only and do not in
any manner serve as an endorsement of those websites. The materials at those websites are not part of
the materials for this IBM product and use of those websites is at your own risk.
IBM may use or distribute any of the information you provide in any way it believes appropriate without
incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this
one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Director of Licensing

IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US
Such information may be available, subject to appropriate terms and conditions, including in some cases,
payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by
IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any
equivalent agreement between us.
The performance data and client examples cited are presented for illustrative purposes only. Actual
performance results may vary depending on specific configurations and operating conditions.
Information concerning non-IBM products was obtained from the suppliers of those products, their
published announcements or other publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other claims related to non-

IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers of
those products.
Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice,
and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without
notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to change before the
products described become available.
This information contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to actual people or business enterprises is
entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs
in any form without payment to IBM, for the purposes of developing, using, marketing or distributing
application programs conforming to the application programming interface for the operating platform for
which the sample programs are written. These examples have not been thoroughly tested under all
conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these
programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.
Each copy or any portion of these sample programs or any derivative work must include a copyright notice
as shown in the next column.
© 2015.
Portions of this code are derived from IBM Corp. Sample Programs.
© Copyright IBM Corp. 2015.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at
"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or
trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications
Agency which is now part of the Office of Government Commerce.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon,
Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or
its subsidiaries in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.
ITIL is a registered trademark, and a registered community trademark of the Office of Government
Commerce, and is registered in the U.S. Patent and Trademark Office.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or
its affiliates.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other
countries, or both and is used under license therefrom.
Linear Tape-Open, LTO, the LTO Logo, Ultrium and the Ultrium Logo are trademarks of HP, IBM Corp. and
Quantum in the U.S. and other countries.
Connect Control Center®, Connect:Direct®, Connect:Enterprise®, Gentran®, Gentran®:Basic®,
Gentran:Control®, Gentran:Director®, Gentran:Plus®, Gentran:Realtime®, Gentran:Server®,
Gentran:Viewpoint®, Commerce™, Information Broker®, and Integrator® are trademarks, Inc., an IBM
Company.
Other company, product, and service names may be trademarks or service marks of others.
Terms and conditions for product documentation

Permissions for the use of these publications are granted subject to the following terms and conditions.
Applicability
These terms and conditions are in addition to any terms of use for the IBM website.
Personal use
You may reproduce these publications for your personal, noncommercial use provided that all proprietary
notices are preserved. You may not distribute, display or make derivative work of these publications, or
any portion thereof, without the express consent of IBM.
Commercial use
You may reproduce, distribute and display these publications solely within your enterprise provided that
all proprietary notices are preserved. You may not make derivative works of these publications, or
reproduce, distribute or display these publications or any portion thereof outside your enterprise, without
the express consent of IBM.
Rights
Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either
express or implied, to the publications or any information, data, software or other intellectual property
contained therein.
IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of
the publications is detrimental to its interest or, as determined by IBM, the above instructions are not
being properly followed.
You may not download, export or re-export this information except in full compliance with all applicable
laws and regulations, including all United States export laws and regulations.
IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS ARE
PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT,
AND FITNESS FOR A PARTICULAR PURPOSE.

Index
D
Definitions
security terms 29
I
install
Microsoft Windows maintenance and fixes 24
K
Known Restrictions 2
M
maintenance and fixes
install in Microsoft Windows 24
S
Security terms, defined 29
System Requirements 7
Index 53
IBM®

Control Center Director PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Control Center Director PDF

Uploaded by

Copyright:

Available Formats

Control Center Director PDF

IBM Control Center Director................................................................................... 1

New Feature and Enhancements

New Features and Enhancements

New Features and Enhancements

IBM Control Center Director 1

Base Release (v1.0.0.0)

New Features and Enhancements

2 Control Center Director PDF

IBM Control Center Director Overview

IBM Control Center Director 3

Table 1. Connect:Direct and Control Center Director Compatibility Matrix

4 Control Center Director PDF

Control Center Director Web Services

IBM Control Center Director 5

Control Center Director Web Services

6 Control Center Director PDF

Installation Environment Requirement

IBM Control Center Director 7

JDBC drivers for DB2 • DB2 supports JDBC driver db2jcc4

8 Control Center Director PDF

Recommended Installation and Configuration Sequence

Step Action Procedure/Related resources

3 Start Control Center Director Web Server 1. Execute runEngine.sh

IBM Control Center Director 9

5 Start Connect:Direct Agent Invoke startAgent.sh.

This script is available at:

10 Control Center Director PDF

Task Related procedure

Configuring Control Center Director Run the config.sh utility to configure:

Invoke runEngine utility “Command Line Utilities Reference” on page 29

Before you set up the database

IBM Control Center Director 11

Setting up Microsoft SQL Server database and users

Before you begin

About this task

Table 7. SQL database settings

Torn Page Detection Off

12 Control Center Director PDF

Database port The port number on which database server listens

Setting up Oracle database and database users (schemas)

Required setting Database schema More information

Character set AL32UTF8 This setting is set as part

Database user GRANT "CONNECT" TO

IBM Control Center Director 13

Configuring Control Center Director to use Oracle database schemas

Database port The port number on which database server listens

Database Name (SID for non-RAC or Service Name

JDBC Drivers These drivers are thin client-based, pure Java

Is your database in an Oracle RAC environment? Enter Y

How many nodes are in your cluster? Enter 1

14 Control Center Director PDF

Setting up DB2 databases

Required setting Database Schema More information

Code set UTF-8 Set this setting during database

User Temporary Table Spaces One user temporary table space

System Temporary Table Spaces One system temporary table

IBM Control Center Director 15

Table Space permissions The database user must have

For additional settings on DB2 databases see the following links:

Configuring Control Center Director to use DB2 database

Database port The port number on which database server listens

Configuring external authentication and certificate-based connections