Store dynamic data files in a second location

The Central Governance file structure contains files, such as log files and database data files, that continue to grow. You can opt to store this dynamic data on a separate file location, and to modify this location if you run out of space on the disk. You can set this up at installation or post-installation. If this is an initial installation, refer to the Complete the initial configuration section in the Central Governance Installation Guide.

Configure after installation

With Central Governance installed and running, perform the following steps:

1. Stop Central Governance.
2. Copy the existing log and data files from the current location to the new location as shown in the Copy log and data files tables.

3. Run the cgcmd configure command.
4. For the option File location:
• Set Change location for dynamic files to YES.
• In the Dynamic data file location field, enter the path to the second file system, which is used for dynamic data storage.
5. Click Save and Start.

Note

Simply changing the file location parameters does not migrate data from the existing location to the new location. You must copy the existing log and data directories to the new location prior to clicking Save and Start. Central Governance cannot start without the MySQL data in the new location.

Note

If you copied the MySQL data to the new location, but not the Mongo data, you can start Central Governance with no data as if it were the initial product start. To migrate the Mongo data at a later date, copy the data and repeat the cgcmd configure command.

File location

The following parameters in the configuration page determine the use of a second location to store dynamic system files.

Change location for dynamic files

No: The static and dynamic files are stored in the Central Governance installation directory. (default)

Yes: Allows you to specify a new location for the database data and the log files. The Dynamic data file location field displays.

Dynamic data file location 

The dynamic data can be stored on a file system or a Windows path other than the Central Governance installation directory. The value of this field is checked for operating system compliance, and that it is reachable when Central Governance is started. If the path indicated in Dynamic data file location does not exist, it is created when you start Central Governance as follows:

• The MongoDB (internal storage) and MySQL (application database) data are stored in the <custom_location>/data directory.
• The log files are stored in the <custom_location>/logs directory.

Copy log and data files

Move the existing dynamic data to the new location prior to starting Central Governance. Central Governance checks, when starting, if the database data exists in the new location.

Populate the Central Governance log and data directories manually as follows, though moving the log file content is optional.

UMA

File	Current location	New location
uma.log	<cg_root>/logs	<custom_location>/logs/uma

Core services log files and directories

Files	Current location	New location
errout.txt provider.log.0 stdout.txt stoperrout.txt stopstdout.txt	<cg_root>/runtime/ com.axway.nodes.ume_xxx/uma/logs	<custom_location>/logs/ com.axway.nodes.ume_xxx/uma/logs
kernel.log opnode.log Peformance.log	<cg_root>/runtime/ com.axway.nodes.ume_xxx/logs	<custom_location>/logs/ com.axway.nodes.ume_xxx/logs

Access and security log files and directories

If you are using the log files to troubleshoot Access and Security, be advised that Access and Security functionality may be stopped or altered if the external database user password has been changed. Please see the Note on database passwords.

Files	Current location	New location
provider.log.0	<cg_root>/runtime/ com.axway.nodes.passport_xxx/uma/logs	<custom_location>/logs/ com.axway.nodes.passport_xxx/ uma/logs
backup.log backupAM.log certs_report.log expiredcerts.log <hostname_value>_ex.log PSImportTool.log server.log	<cg_root>/runtime/ com.axway.nodes.passport_xxx/passport/logs	<custom_location>/logs/com.axway.nodes. passport_xxx/passport/logs

Internal storage files and directories

Files	Current location	New location
Logs
Errout.txt Provider.log.0 Stdout.txt Stoperrout.txt Stopstdout.txt	<cg_root>/runtime/ com.axway.nodes.mongodb_xxx/uma/logs	<custom_location>/logs/ com.axway.nodes.mongodb_xxx/uma/logs
mongo.log	<cg_root>/runtime/ com.axway.nodes.mongodb_xxx	<custom_location>/logs/ com.axway.nodes.mongodb_xxx
Data
data	<cg_root>/runtime/ com.axway.nodes.mongodb_xxx/mongo/data	<custom_location>/data/ com.axway.nodes.mongodb_xxx/mongo/data

Transfer CFT connector log files and directories

Files	Current location	New location
provider.log.0	<cg_root>/runtime/ com.axway.nodes.cftconnector_xxx/uma/logs	<custom_location>/logs/ com.axway.nodes.ume_xxx/uma/logs

Application database files and directories

The following information is only of interest if you upgraded from an older version of Central Governance with an embedded MySQL.

Files	Current location	New location
Logs
Errout.txt Provider.log.0 Stout.txt Stoperrout.txt Stopstdout.txt	<cg_root>/runtime/ com.axway.nodes.mysql_xxx/uma/logs	<custom_location>/logs/ com.axway.nodes.mysql_xxx/uma/logs
log	<cg_root>/runtime/ com.axway.nodes.mysql_xxx/log	<custom_location>/logs/ com.axway.nodes.mysql_xxx/log
Data
data folder "*"	<cg_root>/runtime/ com.axway.nodes.mysql_xxx/data	<custom_location>/data/ com.axway.nodes.mysql_xxx/data

Troubleshoot

When clicking Save and Start, if creating the directory path [mkdir] fails, for example the user has no rights in the new location, an error occurs in the configuration phase.