Your JVM configuration name is an optional setting during the init-config step of a product installation. If a configuration name was specified in the script, then the same configuration name must be used for all other scripts, such as validates and deploys.
Creating a configuration name is most commonly used when multiple products are installed off of the same installation. Generally this is in the form of one configuration per product. This provides the ability to start, deploy or stop a single product independently of other products. This helps mitigate the impact of downtime for maintenance activities.
Determining whether Default or Customized configuration is utilized
First, navigate to the following directory:
If you see just the
template directories, continue to the Default Configuration section.
If you see additional directories than just the
template directories, continue to the Customized configuration name section.
If you have just the
template directories in your
config directory, then you do not have a configuration name.
To double-check this is an active installation and not an unused/incomplete installation, open the
default directory, followed by the
ER directories (for Assure, Insight, Perceive and ER, respectively), and verify that there are files present. All installations will have the skeleton structure of the
default directory with product subdirectories. The subdirectories will be empty unless the
default configuration (no configuration name) is in use.
Customized configuration name
If you see additional directories in your
config directory than just the
template directories, such as the screenshot below, then each directory name represents each of your configurations. In the example below, there are six configurations:
To check which products a configuration correspond to, open any of your configuration directories and review which product IDs are present as subdirectories. There may be one or many products per configuration. The subdirectories will be labelled
ER for Assure, Insight, Perceive and ER, respectively.
In the example below, the configuration corresponds to an Assure installation:
By mapping the configuration names to the product subdirectories, you can determine with products rely on which configuration names. When running a script that has input for a configuration name for that product, such as validates and deploys, you must also include the configuration parameter with that product's configuration name (