Germain UX Init Configuration

⚙️ Initialize the GermainUX Configuration

After installing the GermainUX datastore, Germain Enterprise, GermainUX Services, and all required infrastructure components, initialize the platform by importing the configuration supplied with the GermainUX Service distribution.

You can import the configuration using:

📋 Prerequisites

Before importing the configuration, confirm that:

🔍 Locate the configuration files

Extract the GermainAPMService-<version> archive if this has not already been done.

In this guide, SERVICE_HOME refers to the extracted directory.

The configuration files are located under:

SERVICE_HOME/install/configuration

The distribution typically contains:

Always import the core configuration first.

Before importing

Configuration imports can modify or replace existing settings. Before importing into an existing environment:

Do not import configuration intended for another environment without reviewing it first.

💻 Option 1: Import with the Germain Config Tool

This is the recommended method for importing a complete configuration directory.

The Germain Config Tool is located under:

SERVICE_HOME/bin

🪟 Windows

Run:

bin\gct.bat -c imp <configuration-directory>

Example:

bin\gct.bat -c imp C:\germainapm\install\configuration\core

🐧 Linux

Run:

bin/gct.sh -c imp <configuration-directory>

Example:

bin/gct.sh -c imp /opt/germainapm/install/configuration/core

🔁 Import order

Import the directories in the following order:

1. Import core.

2. Confirm that the core import completed successfully.

3. Import ux and any required technology-specific directories.

4. Import customer-specific or environment-specific configuration last.

When files have parent-child relationships, import the parent first.

For example:

germain.apm.monitoringConfig.json

must be imported before:

germain.apm.monitoringConfig.*.json

📖 Review the import log

If the tool reports an error, review:

SERVICE_HOME/var/logs/config-tool.log

Additional instructions for the Germain Config Tool are available in:

SERVICE_HOME/install/configuration/gct.txt

Do not continue with dependent configuration files until errors in the base configuration have been resolved.

🌐 Option 2: Import through the Configuration Console

Use the Configuration Console when configuration files must be imported individually or when the command-line tool is unavailable.

1️⃣ 1. Open the console

Open the Germain Configuration Console.

Example:

http://<germain-host>:8080/germainapm/config

Sign in using an account authorized to manage the platform configuration.

🔧 2. Open the REST Client

In the upper-right corner, select REST Client, located below the logout option.

📁 3. Import the base configuration

Start with:

germain.apm.json

Open the file and copy its entire JSON content.

In the REST Client:

1. Paste the JSON into Request Body.

2. Set Qualified Name to:

   germain.apm
   

3. Select the PUT HTTP method.

4. Select Execute.

5. Confirm that the request completes successfully.

6. Refresh the Configuration Console.

The newly imported configuration structure should now be visible.

🗂️ 4. Import the remaining core files

Import the other files from the core directory.

For each file:

1. Copy its JSON content into Request Body.

2. Set the correct Qualified Name.

3. Select PUT.

4. Execute the request.

5. Confirm that it succeeds before continuing.

The qualified name normally matches the filename without the .json extension.

For example:

Import base files before their related child files.

For example, import:

germain.apm.monitoringConfig.json

before importing:

germain.apm.monitoringConfig.<component>.json

📦 Import optional configuration

After importing all files from core, import the required files from directories such as:

ux
siebel

and any other feature, technology, or customer-specific directory.

Review each file before importing it to ensure it applies to the environment.

🔄 Restart affected services

Some imported settings take effect immediately, while others require one or more GermainUX components to restart.

After completing the import:

For a new installation, restarting all GermainUX components provides the clearest validation that the imported configuration can be loaded.

✅ Validate the configuration

After the import, verify that:

Review the following log if the command-line import fails:

SERVICE_HOME/var/logs/config-tool.log

Also review the Germain Enterprise and individual service logs for configuration-loading or dependency errors.

🐛 Troubleshooting

❌ The Config Tool reports an import error

Verify:

Use config-tool.log to identify the first file that failed.

❓ A qualified name is rejected

Confirm that:

⏪ Previously imported settings disappear

This usually occurs when an optional configuration was imported without selecting Merge.

Restore the last configuration backup or reimport the required configuration in the correct order:

1. Core configuration

2. Optional configurations with Merge enabled

3. Environment-specific customizations

⚙️ Configuration exists but is not applied

Confirm that:

▶️ Next step

After validating the initial configuration, configure the required monitoring components, applications, users, dashboards, rules, and SLAs through the GermainUX Workspace.

Source: GermainUX Initial Configuration.