OpManager MSSQL Configuration

Install the required OpManager version in the Linux server. After the installation is complete, the following changes should be made before starting OpManager:

Open the Linux terminal to move the database_params.conf from OpManager/conf directory and DatabaseSchema.conf from OpManager/conf/OpManager directory to a different location, using the following command,
```
mv <OpManager_Home>/conf/database_params.conf <OpManager_Home>/conf/OpManager/DatabaseSchema.conf /opt/ManageEngine/
```
Open the Linux terminal copy the database_params.conf from the OpManager/conf/OpManager/MicrosoftSQL directory and paste it in the OpManager/conf directory using the following command,
```
cp <OpManager_Home>/conf/OpManager/MicrosoftSQL/database_params.conf <OpManager_Home>/conf/
```
The following changes should be made in database_params.conf: Under OpManager/conf, change the following properties (url, username, and password) as follows,
```
Original:
URL- jdbc:jtds:sqlserver://localhost:1433/OpManagerDB   
Username- dbuser       
Password- dbpasswd
    Change to:
URL- jdbc:jtds:sqlserver://<MSSQL_Server_Host>:<MSSQL_Server_Port>/<MSSQL_Database_Name>
Username- <MSSQL_Username>     
Password- <MSSQL_Password>
    
```
注意: Open SQL Server Management studio and create a new DB with the name MSSQL_Database_Name. While creating the database, go to options and select the Recovery model as "Simple".

Now, edit the customer-config.xml under OpManager/conf/ directory with the below changes:

Original:
<configuration name="DBName" value="postgres"/>
<configuration name="StartDBServer" value="true"/>
<configuration name="DSAdapter" value="postgres"/>
<property name="masterkey.password" value="Password123"/>
Change to:
<configuration name="DBName" value="mssql"/>
<configuration name="StartDBServer" value="false"/>
<configuration name="DSAdapter" value="mssql"/>
<property name="masterkey.password" value="<MSSQL_Password>"/>

注意: The MSSQL_Password should be the same as the password configured in point 3.

Copy the DatabaseSchema.conf from the OpManager/conf/OpManager/MicrosoftSQL directory and paste it into OpManager/conf/OpManager directory by executing the below commands,
```
cp <OpManager_Home>/conf/OpManager/MicrosoftSQL/DatabaseSchema.conf <OpManager_Home>/conf/OpManager
```

Execute the following commands to rename some files which are required for the MSSQL data population,

mv <OpManager_Home>/server/conf/wrapper.conf <OpManager_Home>/server/conf/wrapper_postgres.conf
mv <OpManager_Home>/server/conf/wrapper_mssql.conf <OpManager_Home>/server/conf/wrapper.conf

Note: The above two commands are for builds with version below 12.7.000. From version 12.7.000 and above, the wrapper file under <OpManager_Home>/server/conf is not applicable.

mv <OpManager_Home>/conf/LogAnalyzer/report-configuration.xml <OpManager_Home>/conf/LogAnalyzer/report-configuration_postgres.xml
mv <OpManager_Home>/conf/LogAnalyzer/report-configuration_mssql.xml <OpManager_Home>/conf/LogAnalyzer/report-configuration.xml

mv <OpManager_Home>/conf/FirewallAnalyzer/AdvancedSearch.xml <OpManager_Home>/conf/FirewallAnalyzer/AdvancedSearch_postgres.xml
mv <OpManager_Home>/conf/FirewallAnalyzer/AdvancedSearch_mssql.xml <OpManager_Home>/conf/FirewallAnalyzer/AdvancedSearch.xml

mv <OpManager_Home>/conf/FirewallAnalyzer/reportconfigurations.xml <OpManager_Home>/conf/FirewallAnalyzer/reportconfigurations_postgres.xml
mv <OpManager_Home>/conf/FirewallAnalyzer/reportconfigurations_mssql.xml <OpManager_Home>/conf/FirewallAnalyzer/reportconfigurations.xml

mv <OpManager_Home>/conf/FirewallAnalyzer/SearchGroups.xml <OpManager_Home>/conf/FirewallAnalyzer/SearchGroups_postgres.xml
mv <OpManager_Home>/conf/FirewallAnalyzer/SearchGroups_mssql.xml <OpManager_Home>/conf/FirewallAnalyzer/SearchGroups.xml

mv <OpManager_Home>/conf/FirewallAnalyzer/SearchViews.xml <OpManager_Home>/conf/FirewallAnalyzer/SearchViews_postgres.xml
mv <OpManager_Home>/conf/FirewallAnalyzer/SearchViews_mssql.xml <OpManager_Home>/conf/FirewallAnalyzer/SearchViews.xml

After making the changes, start the product using 'sh StartOpManagerServer.sh'.

Note:

This is applicable only for the OpManager essential edition.
OpManager has an inbuilt backup and restoration support. Please use the SQL native Backup/Restore option.
The initial startup might take some time to complete since all the XMLs (with a large amount of data) will be populated into the database. So, do not interrupt the initial startup.
Enterprise edition is not supported due to BCP.exe dependency. Because, in the Central, BCP is mandatory and if the probe is configured with MSSQL then Central should also be configured with MSSQL.