Purpose
This wiki is intended as a how-to guide, to step through the process of Disclosure Management database backup, or replicating the database to another system.
Overview
All the content of the data / document repository of SAP Disclosure Management is stored in one single SQL Server Database, including structures of report, templates, configuration, workflows etc. In order to replicate this environment on another server, you need to create a backup of the SQL Server database and restore the backup file on the new server. In addition, you may adapt properly the configuration files of the ASP.net application so the DB connection and the network settings are restored.
This example is based on SQL Server 2008, IIS 6 and IIS 7 configurations.
Backup database
On the source database server, start the SQL Server Management Studio:
Connect to SQL Server using Windows authentication:
Go to Databases -> (name of the database)
Usually, the database name is DisclosureManagementDB. Right-click the database name and select the menu item Tasks -> Back Up…
Use the General settings below for defining the recovery model and the location of the .BAK file:
In the destination panel, customize the path of the backup file for instance:
D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Backup\DM.BAK.
Click Options in the left tree view:
Select the radio button overwrite all existing backup sets
Then click OK to start the backup process.
The backup of the database may take several minutes and is completed once receiving this message:
Backup configuration file
Warning: This step is optional if you plan to restore the database after running the setup of Disclosure Management Server on a new environment and if you keep the default installation settings.
On the source Web server, make a copy of the following files:
(source directory of IIS)\SAP BusinessObjects\Disclosure Management\web.configThe configuration information of the ASP.NET application for the web site is stored in this XML-based text file. Generally we store Session States especially idle session timeout, Error Handling, Security configurations…You can use any standard text editor or XML parser to edit ASP.NET configuration files.
(source directory of IIS)\SAP BusinessObjects\Disclosure Management\bin\cundus.BusinessFramework.dll.config
This XML based configuration file stores the database string connection.
3. (source directory of IIS)\SAP BusinessObjects\Disclosure Management\bin\cundus.enterpriseReporting.Services.dll.Config
This XML based configuration file stores the database string connection.
By default, the source directory of IIS is C:\Inetpub\wwwroot
Restore database
Previously run the setup of SAP Disclosure Management in order to initialize the SAP DM database.
Before restoring the database you may need to stop the Web Server or restart the SQL Server services from the SQL Server Configuration Manager tool in order to reinitialize all database connections.
Then, on the target database server, start the SQL Server Management Studio. Connect to SQL Server using Windows authentication.
Go to Databases -> DisclosureManagementDB -> Tasks -> Restore -> Database…
Select the source for restore to be From device:
Then click the 
button. Add the File to be restored.
Click OK.
Click OK again.
Select the backup sets to restore by ticking the above checkbox:
Go to Options, and tick the check box Overwrite the existing database:
Possibly adapt the Original File Name and the Restore As Path.
Click OK.
After the Restore process completed successfully, then the following dialog box is displayed.
Map the correct user
When you restore backups from another server there will most likely be mismatched login and database user Security Identifiers (SID).
- In the SQL Server Management Studio, select the folder “Security” and subfolder “Logins” (outside of the databases folder)
- Locate the user “CDM User” and double click on it
- In the opened window select “User Mapping” and apply the mapping as displayed in the screen below (see next page)
- Once this is done, open the folder “Databases” and locate the DM data base
- Open the folder “Security” and subfolder “Users”, and verify if the “CDMUser” is listed.
If all the above steps are assigned, you can continue by logging into the application.
Before you logon
Copy Web.config file from the Source Environment to the Target Environment
refer to KBA 2515295 https://launchpad.support.sap.com/#/notes/2515295