2 Configuration
This chapter explains how to configure the Oracle Communications Convergent Charging Controller application.
RESTClient Configuration
RESTClient reads its configuration from the config.json file. The config.json file is located in the /IN/service_packages/REST/etc directory.
RESTClient config.json Section
- Groups of parameters are enclosed with curly brackets – { }
- Comments are prefaced with a “//” at the beginning of the line
Editing the File
Open the configuration file on your system using a standard text editor. Do not use text editors, such as Microsoft Word, that attach control characters. These can be, for example, Microsoft DOS or Windows line termination characters (for example, ^M), which are not visible to the user, at the end of each row. This causes file errors when the application tries to read the configuration file.
Always keep a backup of your file before making any changes to it. This ensures you have a working copy to which you can return.
Loading Config Changes
If you change the configuration file, you must restart the service to enable the new options to take effect.
Wallet Management for oAuth
You need to create an Oracle wallet to store and manage OAM server clientId and clientSecrets, after installing the REST client (and before triggering any Auth requests). Wallets are created using /u01/app/oracle/product/12.2.0/bin/mkstore tool.
- Create an empty Oracle wallet.
- Store the credentials of OAM server for Auth requests.
Example
mkstore -wrl /IN/service_packages/REST/etc/wallet -createCredential REST username password
mkstore -wrl /IN/service_packages/REST/etc/wallet -createCredential connect_string username password
Note:
connect_string should be different for different credentials.Configuration
- Configure location of the wallet in config.json file. For example, /IN/service_packages/REST/etc/wallet.
- Generate the base64 encoded value of the wallet password and
configure it in config.json file. For example, to generate the base64
encoded wallet password, run the following
command:
echo -n "wallet_password" | base64 - Configure the clientId in config.json file.
SSL Configuration
When endpoint contains https, SSL configuration is used for certification validation. SSL configuration is taken from default java configuration. Default truststore is present in java/bin directory.
To import the certificate, run the keytool command as an administrator or root user. For example:
keytool -importcert -alias cert_alias_name -file ./ssl_cert.pem -keystore /usr/java/jdk1.8.0_261/jre/lib/security/cacerts