Connect string won't change when using Configuration Manager
search cancel

Connect string won't change when using Configuration Manager

book

Article ID: 90335

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Connect string won't change when using Configuration Manager

Environment

Release: AOATAM99000-9.0-Automic-One Automation Tools-Application Manager
Component:

Resolution

Detailed Description and Symptoms

?I want to change the DB connection  string for one of my Decision DBs.  I have made the changes in the Configuration Manager but when I apply them, the old values are being passed according to the log files


Investigation

?This should work fine but could be a bug.  However there is a workaround.


Solution

?The file that retains ConfigurationManager's data is UC4ICM.ini in the ConfiguraitonManager directory. The file that AdminNode uses to read configurations from is

 Runtime\AdminNode\UC4.Decision.AdminNode.Modules.xml, where you can modify the connection string in AdminDataSource and SimulationDataSource. If the worker can't start because the EventBase database wasn't changed too, you must change it manually via
 UC4.Decision.EventBaseUtil c|changedb [-adminnode <ip[:<port>]>] -eventbase
     <uri> -connectionstring <String> [-dbtype <String>] [-dbuser <String>]
     [-dbpassword <String>] -authentication <windows|uc4decision|uc4integrated>
     [-user <String>] [-password <String>] [-uc4system <String>] [-client
     <Int32>] [-department <String>]
 (in the Tools\CommandLine\EventBaseUtil).

You can manually adjust this file to your new values.