Configuration
Click here to see this page in full context
  1. Home >>
  2. CM4D Configuration (Plugin) >>
  3. Configure - Site Connection and Service Endpoints

Configuration

Topic Contents [Hide]Topic Contents [Show]
  1.   award Licensing
  2.   list Service Endpoints
  3.   site-database Site Database

  bookmark Home > CM4D Configuration

zap The Configuration tab contains settings for connecting to the CM4D Site database, configuring service endpoints and minor licensing settings.

  award Licensing

The Licensing tab relates to how CM4D applications interact with the licensing server. This section does not manage the licenses themselves. Licenses for CM4D applications are managed using the ATS Licensing Server plugin. The CM4D Configuration plugin only contains settings pertaining to the frequency with which the Licensing Server is pinged by CM4D applications attempting to obtain concurrent user licenses.

See the topic Configuration - Licensing for details.

  list Service Endpoints

The Service Endpoints tab contains the connection details for the services which support CM4D applications. The endpoint services must be added and/or connect successfully in order to access any information obtained from those endpoints.

See the topic Configuration - Service Endpoints for details.

  site-database Site Database

The Site Database tab contains the connection information for the CM4D Site Database. The Site database connection must be configured before the Sites, Managed DataSources and Results Database in the Site Management tab.

What is a CM4D Site Database?What is a CM4D Site Database?The Site database is used primarily for the internal enterprise management of the CM4D software applications on a server. Some additional functions of the database include user management, user privilege management, CM4D Scheduler settings, and CM4D Managed DataSource configurations. A CM4D Site database may manage a single or multiple Sites with one or more CM4D datasources per Site. Each of these Managed Datasources could contain many routines which share the same identifying information. For example, a separate datasource could be created for each development phases of a product.

See the topic Configuration - Site Database for details.

Can we improve this topic?