CMP Global Properties

The following table lists the global properties (variables) that can be defined for CMPClosed Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. when manually configuring the inventory file.

When using the Installation Configuration tool described in Installation Configuration Tool, some properties are either hidden or their range of permitted values is restricted to avoid misconfiguration of the system.

Some values are hardcoded to facilitate configuration:

The name of the database used by the CMP components = MDSCMP

The database type = postgres

CMP Global Properties

Property

Default Value

Description

Mandatory?

company_name

MODEL

Company name

Optional

branding_code

MODEL

Branding code

Optional
installation_id N/A An installation identifier displayed within individual applications to identify the instance of CMP being accessed Mandatory

jdbc_server

N/A

Database server name or IP address

Mandatory

jdbc_server_port

5432

Database server port

Optional

jdbc_schema_name

N/A

The name of the database schema used by the CMP components

Mandatory

delivery_state

alpha

YUM repository delivery state suffix. This property is used for internal CMP deployments only.

Optional

yum_repository_url

N/A

The URL of the CMP YUM repository

Mandatory

yum_repository_username

N/A

The CMP repository username.

Optional

yum_repository_password

N/A

The CMP repository password.

Optional

third_party_yum_repository_url

N/A

The URL of the YUM repository with the third party components.

Mandatory

maven_repository_url

N/A

Maven repository URL

Mandatory

should_deploy_db

true

Flag indicating if the database should be deployed using Liquibase or just current properties applied to it

Optional

verify_ssl_certificates

true

If set to false, YUM won't check the validity of the SSL certificate

Optional
ssl_certificates N/A This property is a dictionary of three elements: "private_key", "certificate" and "ca". Each element is the path to the corresponding PEM file. If specified at the global level and <service>_should_use_ssl is true, the deployment playbook will use the specified files to enable the HTTPS listener. If the property is omitted while <service>_should_use_ssl is still set to true, the self-signed certificate will be generated for the hostname where the specific service is deployed. The property can be overridden at the group/host level. Optional

ansible_connection

ssh

Type of connection that Ansible will use to access the remote system

Optional

ansible_ssh_user

ansible

Ansible SSH username

Optional

http_proxy

 

The address of the HTTP proxy

Optional

https_proxy

 

The address of the HTTPS proxy

Optional

no_proxy

 

The comma separated list of hosts for which a proxy should not be used

Optional
use_redhat_subscription true If set to true, the playbooks will try to enable JBoss and JWS repositories using Red Hat Subscription Manager. In this case, the playbooks expect that all target hosts are registered with Red Hat and have the correct subscriptions enabled. If set to false, the target hosts must be manually configured by the customer to access the customer managed YUM repository(-ies), which provide the EAP7 and JWS5 rpm packages. Optional
SMTP Mail Server Settings This email server will be used by various modules to send emails such as password resets and notifications from Sabre
smtp_host   Email server SMTP hostname. This email server will be used by various modules to send emails such as password resets and notifications from Administration Console. Optional
smtp_port 25 The port number of the email server Optional
smtp_username   The username for authentication Optional
smtp_password   The password for authentication Optional
smtp_auth false Do your server settings support SMTP authentication? Optional
smtp_starttls false Do your server setting support the STARTTLS command? Optional
smtp_from   The "from" email address Optional
Common Application Properties These are properties that are not specific to a single application.
sam_name  

Defines the Synchronous Allowance Management implementation that will be deployed for this CMP installation.

The options are: none, offline, lifecycle, or openet (None, Offline SAM, Lifecycle SAM or Openet SAM in the Installation Configuration Tool).

Depending on what is selected, the appropriate modules for that OCS will be installed along with SABRE Server, REST, AgentView Interfaces Layer and Business Configuration (Configuration Centre).

Mandatory
internal_webservice_password   The password of the user used when calling SOAP and REST web services from other applications within the CMP product suite (only used internally within CMP) Mandatory
log_collector_sftp_password   The password of the "logcollector" user that the CMP Administration Console will use to retrieve log files for display. Mandatory
Health Check Service Properties These are properties which relate to the health check service that is deployed alongside each web application for use by an external load balancer if required.
use_ssl true Should SSL be used for the Health Check Service? Optional
jdbc_password N/A The password for the user that the Health Check Service will use to connect to the database (only used internally within CMP) Mandatory
http_port 21215 The port that the Health Check Service will listen for HTTP(S) connections on. This will be common across all hosts to which the health check service is deployed. Optional