Verifying database configuration files are current in Symantec Mobility: Suite
This topic applies to the Production Installations only.
The following steps are only required if you have modified the config files manually or if you have performed an upgrade on the primary system before installing the secondary Front End server. All steps are to be performed on the primary FE.
To verify database files are current
Obtain the Oracle information that is required to run the config file encryption scripts from the following files:
You must have the following information: Host, Port, User, Password, and Database name. The script also takes the oracleServiceName parameter, if required. mysql can also be substituted for oracle if appropriate. There is a -help option that shows you required options.
Place the Config Key file from your initial configuration into the /usr/local/nukona/appstore_cu/configurator directory.
Locate your pass phrase.
If you are uncertain whether you have the correct Config Key and pass phrase, run pull_config_cache.pyc described in step 7 to confirm the key can decrypt the file. The push command verifies that the key was decrypted properly, so running the pull command is just a test.
Issue the following command:
Use the push_config script, filling in the appropriate parameters.
Confirm that you have the correct config files in the database by using the pull_config_cache.pyc script with the --prefix option.
YOU MUST USE the --prefix option. If not, the database files write over the local copies. Never run the pull_config_cache.pyc script without the --prefix unless you have made local backups of the files in a separate directory. Local copies are assumed to be most current (at this point in the process, they should be identical).
From the /usr/local/nukona/appstore_cu/configurator directory, run the following with the correct values: