How to modify the configuration files after moving the Compliance Accelerator or Discovery Accelerator databases to different SQL server

Article:TECH51129  |  Created: 2007-01-15  |  Updated: 2014-08-12  |  Article URL http://www.symantec.com/docs/TECH51129
Article Type
Technical Solution


Issue



How to modify the configuration files after moving the Symantec Compliance Accelerator (tm) or Symantec Discovery Accelerator (tm) databases from a Microsoft SQL Server / Microsoft SQL Server instance to another Microsoft SQL Server / Microsoft SQL Server instance of a different name or a different TCP Port.


Solution



Overview:

When the databases for any version of Symantec Enterprise Vault (EV) Compliance Accelerator (CA) or Symantec Enterprise Vault (EV) Discovery Accelerator (DA) need to be moved from a Microsoft SQL Server 2000/2005/2008 machine / Microsoft SQL Server instance to another Microsoft SQL Server 2000/2005/2008 machine / Microsoft SQL Server instance of a different name, or the default TCP port used by the SQL Server is changed, there are either 5 or 8 files on the Accelerator server that need to be modified to replace the name of the original Microsoft SQL Server / Microsoft SQL Server instance with the name of the new Microsoft SQL Server / Microsoft SQL Server instance or to specify the new TCP Port used by the SQL Server.  These files are located in the installation folder for the Accelerator application (typical default locations can be 'C:\Program Files\KVS\Business Accelerator - Compliance', 'C:\Program Files\Enterprise Vault Business Accelerator', or 'C:\Program Files (x86)\Enterprise Vault Business Accelerator').  The names of the five files are:
  • AcceleratorManager.exe.config
  • AcceleratorManagerConsole.exe.config
  • AcceleratorService.exe.config
  • ADSynchroniser.exe.config
  • ImportExport.exe.config

If Compliance Accelerator is installed and operational, an additional file must be modified if the Compliance Accelerator Journal Connector is installed on an Enterprise Vault server that is running at least one Journal Task.  This file is located on the Enterprise Vault server that has the Journal Connector installed and is located in the Enterprise Vault installation folder (typical default location is 'C:\Program Files\Enterprise Vault' or 'C:\Program Files (x86)\Enterprise Vault').  This file name is:
  • JournalTask.exe.config (for Microsoft Exchange journal archiving)
  • EVLotusDominoJournalTask.exe.config (for Lotus Domino journal archiving)
 
In the case of DA Version 8 and above, the use of analytics causes 3 more files to need edited:
  • AnalyticsConversationAnalyserTask.exe.config
  • AnalyticsIngesterTask.exe.config
  • AnalyticsServerApp.exe.config
 
 



To configure the Accelerator application to start using its databases on the new Microsoft SQL Server / Microsoft SQL Server instance, configure the five files on the Accelerator server prior to starting the Enterprise Vault Accelerator Manager service on that server.  To configure the five files, follow these steps:
 
1. Open Windows Explorer on the server where the Accelerator application is installed.
2. Go to the Compliance Accelerator / Discovery Accelerator installation folder.
3. Open the AcceleratorManager.exe.config file for editing.
4. Find the line with the old Microsoft SQL Server name / Microsoft SQL Server instance name.
For files AcceleratorManager.exe.config, AcceleratorManagerConsole.exe.config, AcceleratorService.exe.config, ADSynchroniser.exe.config, AnalyticsConversationAnalyserTask.exe.config, AnalyticsIngesterTask.exe.config, and AnalyticsServerApp.exe.config, the line is -
<add key="DSNConfiguration" value="server='SQLServer';Integrated Security=true;Initial Catalog='EVConfigurationDatabaseName';Connection Timeout=100;Connection Lifetime=30;Max Pool Size=200" key="DSNConfiguration" />
For file ImportExport.exe.config, the line is -
<add key="DSNConfiguration" value="server='SQLServer';Integrated Security=true;Initial Catalog='EVConfigurationDatabaseName';Connection Timeout=100;Connection Lifetime=30;Max Pool Size=200" />
where 'SQLServer' is the name of the old Microsoft SQL Server and 'EVConfigurationDatabaseName' is the name of the configuration database for the Accelerator application (default name is EVAccelerator).
NOTE: If Microsoft SQL Server instances are used, the Microsoft SQL Server instance will be identified in each line as "SQLServer\InstanceName', where 'InstanceName' is the name of the Microsoft SQL Server instance.  Also, if a specific port has already been configured for the Microsoft SQL Server access, that port number will be noted with a colon followed by the port number after the SQL Server or SQL Server instance name (i.e., 'SQLServer:1600' or 'SQLServer\SQLInstance:1600').
5. If changing names, replace the old Microsoft SQL Server name / Microsoft SQL Server instance name with the new Microsoft SQL Server name / Microsoft SQL Server instance name.  If adding a TCP Port, add a colon followed by the TCP Port number after the Microsoft SQL Server name / Microsoft SQL Server instance name.  If changing the TCP Port, replace the old port number with the new port number. 
NOTE: There should only be 1 line containing the Microsoft SQL Server name / Microsoft SQL Server instance in each file.
6. Save and close the file.
7. Repeat Sub-steps 1. through 6. for the AcceleratorManagerConsole.exe.config, AcceleratorService.exe.config, ADSynchroniser.exe.config, AnalyticsConversationAnalyserTask.exe.config, AnalyticsIngesterTask.exe.config, and AnalyticsServerApp.exe.config, and ImportExport.exe.config files.
8. Modify the following in the CA or DA Configuration database. Replace the original SQL_NetBios server name with the new SQL_NetBios server name.
 
Table Name Column Value
tblCustomer Server New_SQL_NetBiosName
Open SQL Query Analyzer and run the following query separately against each Configuration database that has been moved.  Replace bold items with the correct server name values:
UPDATE tblCustomer SET Server = 'New_SQL_NetBiosName' WHERE Server = 'Old_SQL_NetBiosName'
 
If the Journal Connector is installed on an Exchange Server that is running a Journal Task, modify the JournalTask.exe.config or EVLotusDominoJournalTask.exe.config file as follows:
1. Open Windows Explorer on each Enterprise Vault server where the Journal Connector is installed.
2. Go to the Enterprise Vault installation folder.
3. Open the JournalTask.exe.config or EVLotusDominoJournalTask.exe.config file for editing.
4. Find the two lines with the old Microsoft SQL Server name / Microsoft SQL Server instance name.
The lines are -
<add key="DSNConfiguration" value="server='SQLServer';Integrated Security=true;Initial Catalog='EVConfigurationDatabaseName';Connection Timeout=500" />
<add key="DirectoryDSN" value="packet size=4096;integrated security=SSPI;data source=SQLServer;persist security info=False;initial catalog=EnterpriseVaultDirectory" />
where 'SQLServer' is the name of the old Microsoft SQL Server and 'EVConfigurationDatabaseName' is the name of the configuration database for the Accelerator application (default name is EVAccelerator).
NOTE 1: If Microsoft SQL Server instances are used, the Microsoft SQL Server instance will be identified in each line as "SQLServer\InstanceName', where 'InstanceName' is the name of the Microsoft SQL Server instance.  Also, if a specific port has already been configured for the Microsoft SQL Server access, that port number will be noted with a colon followed by the port number after the SQL Server or SQL Server instance name (i.e., 'SQLServer:1600' or 'SQLServer\SQLInstance:1600').
NOTE 2: The following line is used by Compliance Accelerator 5.x and does not need to be modified for Compliance Accelerator 6 or greater
<add key='DSN" value="server=EVServer;Integrated Security=true;Initial Catalog=evaccelerator;Connection Timeout=500" />
5. Replace the old Microsoft SQL server name / Microsoft SQL Server instance name / TCP Port number with the new Microsoft SQL server name / Microsoft SQL Server instance name / TCP Port number.
NOTE: There should only be 2 lines containing the Microsoft SQL server name or Microsoft SQL Server instance name in the file which need to be modified.
6. Save and close the file.
7. Restart all Journal Tasks on the Enterprise Vault server.

If the databases have been moved to a newer version of SQL Server, the database compatibility level should be changed to match the SQL Server version.  For example. if the databases have been moved from a SQL Server 2000 machine to a SQL Server 2005 machine, the compatibility level should be changed from "SQL Server 2000 (80)" to "SQL Server 2005 (90)".  Likewise, if the databases have been moved to a SQL Server 2008 machine, the compatibility level should be changed to "SQL Server 2008 (100)".  The compatibility level can be found and changed in the Properties of the database, on the Options page.

 




Legacy ID



287894


Article URL http://www.symantec.com/docs/TECH51129


Terms of use for this information are found in Legal Notices