You can view or edit any saved version of a configuration.
The Configs view presents a list of components. When you expand a component node, a list of all configurations associated with that component for all servers is displayed.
To select a version of the configuration to view or edit:
- Select the configuration.
- In the Config Info panel, select the version from the drop-down.
Click View/Edit in the Config Actions panel.
To view the configuration in raw format, click View/Edit (Raw).
- If TMS detects differences between the version stored in the TMS datastore and the version stored on the server, you can choose to overwrite the TMS version with the server-stored version.
- TMS retains each edited version of a configuration. To view a different version of the configuration, select the version from the Versions drop-down.
- To load a configuration that was modified outside of TMS (using one of the external configuration programs), click Reload from Server. This updates the TMS datastore with the configuration data found on the specified server (if modified).
If you added or modified configuration settings in configuration files local to the currently selected server, you might be prompted to choose to load an externally modified version:
Configuration was modified outside of TMS on the following server(s): MYSERVER Reload configuration from externally modified version?
If you choose Yes, the local configuration file becomes the latest version of the configuration file stored for the current server.
- Changes to local registry settings also result in this prompt if the settings appear in the
standard configuration in TMS. Note: Making changes to the local registry settings is not recommended.
- If the configuration loaded from the local server is to be shared among multiple servers, you must manually create a task to publish the changes to the other servers.
In the configuration edit dialog, you can see a Version Description field. If you make any changes to the configuration, you can enter a description for the new version here.
The configuration data is displayed as a list of config items that can be individually edited, as in a configuration-specific interface such as the Pipeline Editor. The method of editing is determined by the type of configuration.
To save changes made to a configuration, enter a version description and click Save. The configuration is saved as a new version in the master TMS datastore.
After saving, you can choose to add tasks to push the new version to all servers that use it. Click OK to create a new TMS job composed of one or more tasks to push the configurations to the appropriate destinations.
For tasks that push configurations, you can choose to force the affected components to restart after the new configuration has been applied.
- The Push/Restart job is automatically submitted when you click Add Tasks and Submit.
- To submit the job manually at a later time, you can click Add to Current Job.
- To submit the configured job to TMS, make any changes to the job and then click Submit.
Editing raw configurations
In TMS, the most useful configuration items are exposed in the standard format. Optionally, you can review the raw configuration, which contains all settings associated with the configured item. To edit a raw configuration, select the item in the WorldView tab and click View/Edit (Raw) in the Config Actions panel.
The raw configuration exposes all settings contained in the TMS data dictionary for the selected item. In addition to the items available in the standard configuration, the raw configuration includes:
- read-only items that cannot be changed by users
- hidden items retained for debugging purposes Note: The items in the standard version of each configuration are documented and exposed for your use. Unless directed by Experience Analytics to change them, it is recommended that you avoid making changes to hidden configuration items.
Items that are hidden and read-only may include obsolete settings, which are maintained for upgrade purposes.
A configuration is not actively in use unless it has been assigned to a server. When a server is added to TMS, all current configurations are added and assigned to that server.
You can share a single configuration, assuming there are no server-specific config values among multiple servers.
- To assign a configuration to one or more servers, select the desired configuration and then click Assign. A list of servers to which the configuration can be assigned is displayed.
- Click the checkbox next to each server name to assign or un-assign the configuration, and then click Assign to complete the assignment.
- The configuration is assigned immediately to the selected servers. Those servers are updated the next time the corresponding Push Configuration job is executed by TMS.
Un-assigning a configuration
If you have accidentally assigned a configuration to a server and wish to revert to another version, please complete the following steps.
- In the WorldView tab, select View > Configs.
- Select the component that contains the configuration you want.
- Navigate the tree to select the configuration.
- In the Config Actions pane, click Assign (share).
- Select the server or servers to which to assign the configuration, replacing the one you originally assigned.
- Click Assign.
- Submit a task to complete the change.