Configuring › Configuration Tool Settings

Configuration Tool Settings

The configuration tool lets you configure the following settings:

• CCI (Common Communications Interface) server information
• DRAS (Distributed Repository Access System) server information
• Authentication Configuration
• External Security (Customer Supplied Authentication Exits)
• LDAP (Lightweight Directory Access Protocol) Host Information
• Default Administrator Mainframe ID
• Database Connection Settings

CCI (Common Communications Interface) Server Information

CA CCI connects to the host CA Output Management product (CA View®, CA Dispatch™, or CA Bundl®) repositories. CA CCI instances install as the servers and configure to communicate with other CA CCI servers that run on the network. CA OM Web Viewer uses a CA CCI client that you must configure to allow communications with a single CA CCI server.

CCI Server

Specifies the name or IP address of the mainframe where the CA CCI server task executes.

Example: mainframe.company.com

CCI Port

Specifies the port number that the CCI server uses.

Example: 1202

CCI Client System ID

Specifies a unique value that identifies the product instance to the CA CCI server. You can use the computer name where you deployed the product, except if you deployed the product on the same system where the CA CCI server executes. This situation can happen with USS systems.

Important! Never define a system ID that matches the computer name of the CCI server. This match can cause CCI failures. If you are using Application Level External Configuration, be sure to select a different CCI (Common Communications Interface) Client System ID for each CA OM Web Viewer on your network.

Note: By default, the Client System ID will be a modified version of your computer name. However, if you have two instances of CA OM Web Viewer on the same computer they must each have a different Client System IDs.

Limit: 8 characters

Example: system1

DRAS (Distributed Repository Access System) Server Information

CA Distributed Repository Access System (CA DRAS) acts as the License Management Program (LMP) license check server and the mainframe external security interface for web login.

DRAS Server

Specifies the domain of the DRAS server. The configuration tool discovers the available DRAS servers. Select the server by its listed number.

Example: 1 - ENFID1:DRASSVR1

Authentication Configuration

You can select one of the following security configurations:

• Mainframe Security then LDAP Security
• LDAP Security then Mainframe Security
• External Security (Customer Supplied Authentication Exits)

Important! Selecting external security causes all users, except System Admins, to be validated through external security only. The System Admin group members can only be authenticated through mainframe security.

External Security EXIT

If you select to use an External Security Exit, provide a path to a folder that has the files that comprise your External Security EXIT and needed libraries. The files will then be copied for CA OM Web Viewer to be used by the configuration tool.

Fully qualified directory where External Security Exit files are located:

The location of your exit jars.

Example: C:\WV_Exit\dist

The files in the supplied folder are copied to either of two locations depending on your configuration type:

• If using Application Level Internal configuration.

  The deployable (WAR or EAR)

• If using Application Level External Configuration or System Level External Configuration.

  Your external configuration location.

Notes:

• All files are copied, but subfolders and folder structure is removed. The file hierarchy is flattened.
• Only jar files are automatically loaded by the CA OM Web Viewer classloader, for more information on referencing other non-jar files, see the CA Output Management Web Viewer Programmer Guide.
• Jars that are listed in the CLASSPATH do not need to be included in this folder. In this instance, CLASSPATH can refer to the system CLASSPATH variable on the system where you run CA OM Web Viewer or a CLASSPATH defined within your Java EE Application Server. Whether applications on your Java EE Application Server use your system’s CLASSPATH or one defined within the Java EE Application Server is determined by your Java EE Application Server. WebSphere Application Server for example, does not pass the system CLASSPATH to the application.

LDAP (Lightweight Directory Access Protocol) Host Information

If you have mainframe security first, these settings are not required.

LDAP Host

Specifies the host name of the LDAP system.

Example: ldap.company.com

LDAP Port

Specifies the port number of the LDAP system.

Example: 389

LDAP Login Attribute

Specifies the attribute in your LDAP directory that represents the user ID of your users. Common examples include cn (common name) and uid.

Example: sAMAccountName

LDAP Base DN

You must add these attributes to the login attribute of a user to provide that distinguished name that you desire.

Example: OU=Users,OU=North America,DC=company,DC=com

Bind DN

(Optional) Specifies the user login and base distinguished name of an account that can bind to the LDAP server and authentic other users.

Example: cn=Jim,ou=west,ou=admin,dc=company,dc=com

Bind Password

(Optional) Specifies the password for the Bind DN account.

Default Administrator Mainframe ID

The product requires the userid for its primary administrator.

Important! This userid must be a mainframe user.

Database Connection Settings

The product uses an external database to store administrative and user settings. Multiple database applications are supported in addition to generic JDBC-compliant database applications.

Database type

Lists the supported database types. Select the number matching your database application.

Example: 1

Full path name of an IBM DB2 license file

DB2 Only.

Full path name of the JAR file containing the JDBC driver

Local JDBC driver Only.

Host name

Specifies the name of the computer where the database server executes.

Example: dbserver.company.com

Port number

Specifies the port number that the database server uses.

Example: 1433

Database name

Specifies the name of the database that CA OM Web Viewer uses.

Important! You must create the database prior to testing or starting the product successfully.

Example: dvweb_adminDB

User name

Specifies the database user name with access to the CA OM Web Viewer database.

Example: sa

Password

Specifies the password of the database user name.

Does this account have CREATE TABLE privileges?

If no, create the tables before you start CA OM Web Viewer using the DDL SQL provided with the installation media.

Example: Enter 1 for Yes, 0 for No

Maximum number of connections for Read

Example: 100

Maximum number of connections for Write

Example: 100

JDBC URL

Specifies the JDBC URL based on the values provided. If additional parameters or changes are required, enter the correct URL.

Example: jdbc:sqlserver://dbserver.company.com:1433;databaseName=dvweb_adminDB

Note: If you do not have this information, consult your Database Administrator.