Thank you for being a valued client of CM First Group. If you have any technical issues or concerns, please open a ticket on support.cmfirstgroup.com, email CM First technical support at support@cmfirstgroup.com or call us on our 24/7 customer hotline at +1 (512) 623-7586.

Follow

Configuration

Verifying the initial configuration

After the installation has completed, navigate to the following URL in a web browser:

http://localhost:8082/

It may take a few moments for the server component to initialize. Once the page has loaded, you will see the CM Meta Analytics dashboard.

Click on the Configuration button in the left-hand side pane to view the default configuration parameters.

back to top

Scanner Setup

Path to scanner run command (run.exe)

This path should point to the run.exe that is present within the DMS subdirectory tree.

Path to scanner root directory (DMS)

This path should point to the DMS subdirectory tree.

Path of directory where source files will be placed

This path should point to a directory on the scanning server where source code will be placed to be scanned.

Path of directory where output XML files will be place.

This path should point to a directory on the scanning server where the output XML and control files will be placed after the code has been scanned.

Maximum number of processes that will run simultaneously during execution of a job

This numeric value that specifies the desired number of simultaneous scanning processes that will be run on the scanning server. An appropriate value is typically the number of CPU's that are present in the scanning server.

Maximum number of source files that will be sent to a process for scanning

This is the number of source files that will be given to each scanner process. In most cases, this should be 1.

Path to CA import tool (xmlexchange.exe)

This path should point to the xmlexchange.exe program provided by CA to import the metadata into the repository.

Name of the ODBC data source to use to import the data into the work tables

This parameter should be the name of a system-wide 32-bit ODBC DSN that will be used by the CA import tool to write the data to the repository work tables.

Name of the ODBC user

This should be set to the name of the ODBC user that will load the work tables.

Password for the ODBC user

This should be set to the password of the ODBC user that will load the work tables.

Database prefix to import into (DBXRELXX)

This should be the name of the database that the work tables reside in.

System-wide CopyBook directory

This is the location where system wide copybooks are stored. If this location is not a valid directory, the scan will fail.

Scanner Process timeout (in Minutes)

This allows a user to set the timeout for a file to be scanned.

back to top

Arzos Resolver

Repository status for objects to be resolved:

This contains status of an object that is queued to be resolved

JDBC Connection String to ARZOS Repository:

The connection string to use to connect to the ARZOS Repository

Classpath for JDBC Driver (Semicolon delimited):

The absolute path for the JDBC Driver(s) location on the machine

Class of JDBC Driver (fully qualified)

The fully qualified path within the driver for the database component

SQL Statement to resolve Column

The statement that polls the database for the information for the resolve column

If any changes are made to any section, click the Save button for each changed section, then go to the Windows Services control panel. Right-click on the CM Meta Analytics service, and choose restart, to restart the service with the new settings.

back to top

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk