Installation and Upgrade Guide

PUBLIC
Document Version: DM Stack 20xx – 2022-11-26
Installation and Upgrade Guide

© 2023 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Release-Specific Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1 Hardware and Software Requirements in SAP Disclosure Management. . . . . . . . . . . . . . . . . . . . . . . 8
2.2 SAP Notes for the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3 Initial Installation of SAP Disclosure Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3.1 Selection of Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Collection of Required Installation Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Preparation of SAP Disclosure Management Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2 Installation of DM SERVER - APPL SERVER 10.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.3 Installation of DM SERVER - APPL SERVER 10.1 with Silent Parameters. . . . . . . . . . . . . . . . . . . . . . 28
3.4 Installation of DM SERVER - TASK ENGINE 10.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Running the Setup Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Selecting an Installation Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Configuring Database Details for Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Configuring Database Authentication for DM Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Adding Location of Application Server for Cryptographic Key. . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Installing Arelle for Preview and Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Checking the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Performing a Health Check of Installed Task Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.5 Installation of DM SERVER- TASK ENGINE 10.1 With Silent Parameters. . . . . . . . . . . . . . . . . . . . . . 46
3.6 Configuration of DM SERVER - APPL SERVER 10.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Configuring the Main Task Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Configuring the Component Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Checking the Component Landscape Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Configuring Document Web Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.7 Installation of DM CLIENT 10.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Preparation of SAP Disclosure Management Client Installation. . . . . . . . . . . . . . . . . . . . . . . . . .53
Installing SAP Disclosure Management Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
SAP Disclosure Management Client Registry Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
3.8 Installation of Fujitsu Interstage XWand. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Installing Fujitsu Interstage XWand. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.9 Installation of DM CLIENT 10.1 with Silent Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.10 Installation of DM XBRL MAPPER 10.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

2 PUBLIC Content
Installing DM XBRL Mapper. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
3.11 Installation of DM XBRL MAPPER 10.1 with Silent Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.12 Installation of BW Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Preparation of SAP Disclosure Management BW Connector Installation. . . . . . . . . . . . . . . . . . . 66
Installing BW Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Post-Installation of BW Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
3.13 Enabling Data Connections to SAP S4/HANA or SAP BW4/HANA. . . . . . . . . . . . . . . . . . . . . . . . . . 77
3.14 Post-Installation of SAP Disclosure Management Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Activating Detailed Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Configuring Virtual SMTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Configuring Data Sources on Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4 Upgrade of SAP Disclosure Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
5 Uninstalling DM SERVER - APPL SERVER 10.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6 Update of SAP Disclosure Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

6.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.2 Choosing the Right DM Target Stack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
6.3 Collection of Required Update Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Choosing the Right DM Stack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Checking the Components To Be Updated. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Understanding Update Paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Downloading Files for Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
6.4 Update of DM SERVER – APPL SERVER 10.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Checking Logon to DM Website. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Making a Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Enabling Database Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Stopping Microsoft Internet Information Services (Relevant for DM Stacks Lower Than 1200)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Running the Setup Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Configuring Database for Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Choosing an Update Option for Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Checking the Rest of the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Checking the Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Update Paths for DM Stacks Lower than 1000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6.5 Update of DM SERVER – TASK ENGINE 10.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Making a Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
6.6 Update of DM SERVER – XBRL SERVICE 10.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Making a Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Uninstalling DM SERVER – XBRL SERVICE 10.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Restore the Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Content PUBLIC 3
6.7 Update of DM CLIENT 10.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Uninstalling DM CLIENT 10.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Installing DM CLIENT 10.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
6.8 Update of DM XBRL MAPPER 10.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
Uninstalling DM XBRL MAPPER 10.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
Installing DM XBRL MAPPER 10.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
6.9 Updating Fujitsu Interstage XWand. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
7 DM Fiori Launchpad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

7.1 Assigning Business Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
7.2 Configuring Database Authentication for DM Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
8 Technical Post-Installation and Post-Update Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
9 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
9.1 Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
9.2 Usage of the Install Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
9.3 Database Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
9.4 SAP Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

4 PUBLIC Content
1 Release-Specific Information
This chapter contains information about release-specific deviations from the standard installation. In case of
update and installation issues, see Known Issues [page 113]. For general information about DM stacks, see
Choosing the Right DM Stack [page 10].
DM Stack 1100
Correct Link to Custom Help If Applicable

If you use a local custom help, the following applies:
With DM Stack 1100, the default link to the online help has changed. The setting Root folder for the webhelp in
Administration System configuration Misc is overwritten with the new URL as part of an update of DM
SERVER – APPL SERVER 10.1 to DM Stack 1100.You must reajust the URL after completing all other update
steps.
DM Stack 900R / DM Stack 900
Use DM Stack 900R instead of DM Stack 900

To simplify update efforts and reduce the number of manual steps, DM Stack 900 has been replaced with DM
Stack 900R, which covers built-in solutions for a list of issues that could occur with DM Stack 900.
Hence, it is highly recommended that you skip DM Stack 900 and update via DM Stack 900R instead.
Implement Mandatory SAP Notes

If you have already or accidentally updated to DM Stack 900 (instead of DM Stack 900R), implement the
following SAP Notes as part of the update of DM SERVER – APPL SERVER 10.1 right after the step Enabling
Database Access [page 15]:
1. SAP Note 2473211

2. SAP Note 2473157
3. SAP Note 2472900
4. SAP Note 2553129
5. SAP Note 2536768
6. SAP Note 2552409
Consider Deviating Update Path

DM Stack 900(R) can be updated from one of the following stacks:
• DM Stack 802
• DM Stack 803

Release-Specific Information PUBLIC 5
• DM Stack 804
• DM Stack 805
You cannot update from DM Stack 800. If you are on DM Stack 800, update to DM Stack 802 first, then to DM
Stack 900R.
Adjust Transport Packages With Date Fields

Transport packages exported with earlier versions of DM can contain date fields in several different formats.
With DM Stack 900(R), the date fields have been harmonized to follow the ODBC timestamp format, for
example, 1998-12-31 01:23:56, without second fractions.
When you import transport packages from earlier releases, DM Stack 900(R) expects dates to be expressed
in this format. Hence, transport packages created earlier have to be adjusted manually to match the ODBC
timestamp format if they contain date fields.
Allow HTTP Verbs

From DM Stack 900(R), some HTTP verbs are used by DM so you have to allow them for this application. If you
denied certain HTTP verbs before an update to DM Stack 900(R), follow the steps described in Configuring the
Web Server [page 24], under … for Microsoft Internet Information Services <version> item “Allow required
HTTP verbs” .
DM Stack 800
Grant Access to API Certificate

Once you've completed the update to DM Stack 800, follow the steps described in Enabling Database Access
[page 15].
DM Stack 600
Repair Data Links

Once you've completed the update to DM Stack 600, you must implement SAP Note 2385972 . This applies
even if plan to update to a higher DM Stack.

6 PUBLIC Release-Specific Information
2 Introduction
This guide provides information about the installation of the SAP Disclosure Management components, that is,
the server component, the client component, and BW connector.
The SAP Disclosure Management client is a COM add-in in Microsoft Excel, Microsoft Word, and Microsoft
PowerPoint. After the installation of the SAP Disclosure Management componets, the Microsoft Office
applications display a ribbon that allows easy access to SAP Disclosure Management features.
The SAP Disclosure Management BW connector is used to extract data from an SAP BW system.
 Note
The BW connector uses standard SAP BW and SAP NetWeaver functionality. The application uses the SAP
ABAP environment and the ABAP-based Web Service Infrastructure of SAP NetWeaver.
The following figure shows the system landscape:
This guide addresses the following target groups:
• Consultants
• Technical consultants
• IT administrators
SAP Disclosure Management has two product versions, which include a large number of component versions:

Introduction PUBLIC 7
• SAP Disclosure Management 10.1 (technical name: SAP DISCLOSURE MGMT. 10.1)
• SAP Disclosure Management, XBRL reporting add-ons 1.0 (technical name: DISCLOSURE MGM XBRL
ADD-IN 1.0)
 Note
For a list of the software and hardware requirements for SAP Disclosure Management 10.1 and SAP
Disclosure Management XBRL reporting add-ons 1.0, see the SAP Disclosure Management 10.1 Product
Availability Matrix (PAM). The Product Availability - Essentials PowerPoint presentation also contains
information for getting started and can be found under General Information Details and Dates
Essential Information in the section Introducing SAP Disclosure Management.
2.1 Hardware and Software Requirements in SAP

Disclosure Management
When you prepare the list of the software component versions you want to use, it is important to understand
the hardware and software requirements to run this combination of software component versions.
You can find more information in the Product Availability Matrices of SAP Disclosure Management and
SAP Disclosure Management, XBRL reporting add-ons, supplemented by the Product Availability - Essentials
presentation, in the sections Software Requirements and Hardware Requirements.
Support Package Stacks
Both product versions, SAP DISCLOSURE MGMT. 10.1 and DISCLOSURE MGM XBRL ADD-IN 1.0,
are maintained via various types of deliveries that are described in the Product Availability - Essentials
presentation, section Product Versions and Releases. One of the main delivery types is the support package,
which is a planned subrelease of a software component version. Support packages for the different software
component versions of a product version that, according to SAP’s testing results, work together on one
system are called support package stacks. All available support package stacks are documented in SAP Note
2138656 . Choose a support package stack that meets your requirements. Unless indicated otherwise, we
recommend that you use the latest available support package stack.
2.2 SAP Notes for the Installation
Plese read the following SAP Notes carefully before you start the installation. These SAP Notes contain the
most recent information on the installation, as well as corrections to the installation documentation.
Please make sure that you have an up-to-date version of all SAP Notes, which you can find at https://
support.sap.com/notes .
Installation and Upgrade

8 PUBLIC Introduction
SAP Note Number Title Description
2672792 DM Stack 1300 Release Note Information about new and changed
features
2423859 DM Installation and Update Information about the installation and

update of SAP Disclosure Management
2316228 SAP Disclosure Management Stacks Information about SAP Disclosure

Management stacks
2052707 Migration of SQL server 2005 database Upgrading SAP Disclosure

to SQL server 2008 with subsequent Management 10.0 SP08 or higher
continuation of SAP Disclosure running with SQL Server 2005 to SAP
Management 10.1 setup Disclosure Management 10.1
1566421 Installing DISCMLG on SAP NetWeaver Description for installing add-on for
7.0 (BI 7.1) SAP NetWeaver
Troubleshooting
984200 You cannot change DEVICE_CLASS Using REQUEST_DEVICE_CLASS

parameter in existing session
2365878 Insufficient read access to certificates' After an update to or new installation

private keys of SAP Disclosure Management 10.1
Service Pack 07 or higher the login
does not work.
Miscellaneous Notes
2084486 EBA and EIOPA supervisory reporting Information on product versions and
overview licensing, taxonomy support, support
of individual national requirements,
and information on supervisory
reporting according to EBA and EIOPA

Introduction PUBLIC 9
3 Initial Installation of SAP Disclosure
Management
3.1 Selection of Components
SAP Disclosure Management consist of two product versions containing a large number of components:
• SAP Disclosure Management 10.1 (technical name: SAP DISCLOSURE MGMT. 10.1)
• SAP Disclosure Management, XBRL reporting add-ons 1.0 (technical name: DISCLOSURE MGM XBRL
ADD-IN 1.0)
Depending on the scenario(s) you want to cover with SAP Disclosure Management, you need to make a
decision about the required components. The product availability matrix can help you make such decision.
Please read the presentation under Essential Information.
3.1.1 Collection of Required Installation Objects
3.1.1.1 Choosing the Right DM Stack
DM Stacks are working combinations of versions for all DM Components. The DM stacks note 2138656 lists
all DM stacks and provides basic information about this.
The same note refers to release notes for each DM stack. They provide information about enhancements,
corrections, legal change support, and bug fixes.
Please check if the latest DM stack meets your requirements. Unless otherwise indicated, it is strongly
recommended that you use the latest available DM stack.
 Note
If you opt for a different DM stack than the one covered by this guide, search for the guide that covers your
target DM stack on the SAP Help Portal at https://help.sap.com.

10 PUBLIC Initial Installation of SAP Disclosure Management
3.1.1.2 Choosing the Right Versions
To install your target DM stack, it is important to understand which components allow you to start with which
version. Depending on the component, one or more of the following installation paths are supported:
1. Starting with the initial version of the software component

2. Starting with the version from any DM stack ending with 00, for example DM stack 800
3. Starting with the version from any DM stack
The following table shows which components supports which installations from scratch:
Start with any DM Stack

Component Start with Initial Version Ending with 00 Start with any DM Stack
Mandatory You must install all DM stacks You must install all DM stacks
DM Application Server*
ending with 00 between your ending with 00 between your
lower than stack 1000
current version and the tar current version and the tar
get version. ** get version. **
Mandatory You must only install the tar You must only install the tar
DM Application Server*
get version. get version.
as of stack 1000
• DM Client Mandatory (must match the You must install previous ver You must install previous ver
Application Server version) sions. sions.
• DM Task Engine
• DM XBRL Engine
• DM XBRL Mapper
DM CONNECTOR FOR NW BI Mandatory

7.0x
 Recommenda
tion
Apply all patches and all
correction notes valid for
the latest patch
DM CONNECTOR FOR NW BI Mandatory

7.30
 Recommenda
tion
the latest patch

Initial Installation of SAP Disclosure Management PUBLIC 11
Start with any DM Stack
Component Start with Initial Version Ending with 00 Start with any DM Stack
DM CONNECTOR NW BI Mandatory
7.31 - 7.50
 Recommenda
tion
the latest patch
DM CONNECTOR S/4HANA Mandatory Possible Possible
* Enable Database Access:
If you want to update DM SERVER – APPL SERVER 10.1 on a Microsoft Windows Server machine without
Microsoft SQL Server Management Studio, install the following software components:
• Microsoft ODBC Driver 11 for SQL Server

• Microsoft Command Line Utilities 11 for SQL Server
** DM Stack 900R / DM Stack 900
DM Stack 900R Replaces DM Stack 900
To simplify update efforts and avoid manual steps, DM stack 900 has been replaced with DM stack 900R,
which covers built-in solutions for a list of issues that could occur with DM stack 900. Hence, it is highly
recommended to skip DM stack 900 and update to DM stack 900R instead.
SAP Notes to Be Implemented
Only in case you have already or accidentally updated to DM stack 900 instead of DM stack 900R: implement
the following SAP Notes as part of the update of DM SERVER – APPL SERVER 10.1 right after the step
Enable Database Access:
• 2473211
• 2473157
• 2472900
• 2553129
• 2536768
• 2552409
The following update paths apply to DM stack 900R:
• From DM Stack 802

 Caution
You can't update from DM stack 800. If you are on DM stack 800, update to DM stack 802 first, then to DM
stack 900R.

 Example
1. If you want to update from stack 403 to stack 1202, you must install the following stacks in this order:
• Stack 500
• Stack 600
• Stack 700
• Stack 800
• Stack 802
• Stack 900R
• Stack 1000
• Stack 1202
2. Uninstall previous versions of DM Client, DM Task Engine, DM XBRL Engine, DM XBRL Mapper and
install the latest available version between stack 1200 and stack 1202.
3.1.1.3 Downloading Files For Installation
As of DM Stack 902, you can use DM Stacks table (from SAP Note 2138656 ) to find all new downloads of
a DM Stack in SAP Software Downloads (https://launchpad.support.sap.com/#/softwarecenter ). Click the
link at the top of the column listing the target DM Stack.
 Note
• A blue background denotes recently released software.

• A yellow background indicates that this version of the component has been published as part of an
earlier DM Stack. For the related downloads, search SAP Software Downloads for the DM Stack that
first included this version.

For downloads from DM Stacks lower than 902 or if you want to find your downloads manually, navigate in SAP
Software Downloads as described below.
SAP Software Downloads provides files in two general areas, Installations and Upgrades and Support Packages
and Patches:
1. Installations and Upgrades contains the following download packages:

1. A virtual installation medium containing SAP BW Connector for SAP S/4 HANA
2. A download package containing all other installation packages for other SAP NetWeaver releases.
 Recommendation
Please do not use this download package!
2. Support Packages and Patches includes all other download objects
SAP DISCLOSURE MGMT. 10.1 Installations and Upgrades Support Packages and Patches
DISCLOSURE MGM XBRL ADD-IN Installations and Upgrades Support Packages and Patches
1.0
 Note
For the following components, select WINDOWS ON X64 64BIT from the dropdown list once you have
reached the list of downloads:
• DM SERVER - APPL SERVER 10.1

• DM SERVER - TASK ENGINE 10.1
• DM SERVER - XBRL SERVICE 10.1

3.1.1.4 Downloading Third-Party Components
Download the following components:
1. Arelle
Download Arelle version 2016-11-22 or the latest version from http://arelle.org/download/ .
 Caution
Ensure that you download the Windows 64-bit version.
2. Fujitsu Interstage Xwand

Download Fujitsu Interstage Xwand from https://launchpad.support.sap.com/#/softwarecenter .
You can find the download package under D SAP DISCLOSURE MANAGEMENT SAP DISCLOSURE
MGMT. 10.1 INTERST. XWAND TAX ED&IN CR 13 .
 Caution
Do not download the installation files from the Fujitsue Web site, as these are part of a demo version
without license key.
3.1.2 Preparation of SAP Disclosure Management Server

Installation
3.1.2.1 Enabling Database Access
If you want to install DM SERVER – APPL SERVER 10.1 on a Microsoft Windows Server machine without
Microsoft SQL Server Management Studio, you must download the following software components from the
Microsoft website and install them on the server:
1. Microsoft ODBC Driver 11 for SQL Server

2. Microsoft Command Line Utilities 11 for SQL Server
 Note
Even with Microsoft SQL Server Management Studio installed, the above components may have not been
installed.
3.1.2.2 Running the Setup Wizard
1. Copy the setup executable to the desktop of the destination server and run it with administrative Microsoft
Windows permissions.
2. The setup wizard checks the following software requirements:

 Note
If the result is negative, see Hardware and Software Requirements in SAP Disclosure Management [page 8]
and solve any remaining issues.
3.1.2.3 Configuring Database for Setup
You enable the DM setup wizard to connect to the target database with a working authentication.
1. In Microsoft SQL Server Management Studio, log on to the target database with a user with administrative
permissions. The user credentials and the hostname of the database server are required for the next step.
In the Server Properties, ensure that in server authentication "SQL Server and Windows Authentication
mode" is selected.
2. In the DM setup wizard, select the Microsoft SQL Server as the database server to be used by DM.
3. Enter the authentication information to be used during the setup process. Make sure to enter the user with
administrative database permissions.
4. Select the database catalog (the database name) to be updated for DM and continue.

3.1.2.4 Configuring Database Authentication for DM Usage
Configure the authentication for a technical database user DM uses to access the database during usage of the
product.
The authentication type is a basic authentication, that is user and password. The default credentials are:
• User: CDMUser
• Password: Initial1
The credentials are encrypted and saved to the file

cundus.enterpriseReporting.Services.dll.config in the \bin folder below the installation folder
of DM SERVER – APPL SERVER 10.1.

3.1.2.5 Configuring Website Settings
Configure the Microsoft Internet Information Services (IIS) settings for SAP Disclosure Management:
The Wizard checks whether:
• The name of the IIS website is already in use.

• The TCP port is already in use.
• A file already exists in the system that is in use by another instance.
You can change the installation folder of DM SERVER – APPL SERVER 10.1. In most cases, it is sufficient
to change the TCP port to your needs. As the default configuration of the used protocol for Disclosure
Management is HTTPS, the default TCP port is set to 443. Additionally, an SSL certificate is required to
install DM SERVER – APPL SERVER 10.1 with HTTPS configuration. You can select this certificate from the

Certificate dropdown list. The dropdown list of the setup wizard shows all available SSL Server certificates that
are currently installed with IIS:
You can also switch the protocol configuration to HTTP using the Protocol dropdown list. Once it is set to HTTP,
the TCP port is automatically set to 80 , and no SSL certificate is required to continue with the installation:
The application is installed to the named directory of your Microsoft Windows Server system.
A website and an application pool with the entered name is created and the website is added to the application
pool.

3.1.2.6 Configuring Website Security Settings
Configure one of the following authentication methods:
• Basic Authentication
• Active Directory Authentication, including basic authentication as a fallback
In both cases, a user for basic authentication with the following credentials will be created:
• User: Admin
• Password: Initial1
If you choose Active Directory Authentication, a technical user with the credentials you enter is created. This
user is not available in the application itself. It is used for the sole purpose of authentication requests to
Microsoft Windows AD. The user name and domain must match a user in your existing Microsoft Windows
Active Directory.
3.1.2.7 Granting Access to API Certificate
If you install DM Stack 800 or higher, the following steps are required. API calls authenticated via Microsoft
Windows Active Directory use a certificate that needs to be prepared by granting read permissions to it for
ISS_IUSRS.

Proceed as follows:
1. As an administrator, run Microsoft Management Console.

2. Choose File Add/Remove Snap-in… Certificates and click the Add button.
3. Select Computer Account and click Next.
4. Choose File Add/Remove Snap-in… Certificates and click Add.
5. Select Computer Account and click Next.
6. Confirm by clicking Finish.
7. Close the Add or remove Snap-ins dialog box by clicking OK. From the Snap-in tree view, choose
Certificates ) Local Computer) Personal Certificates .
8. Right-click the ApiDisclosureManagementV2 certificate and choose All Tasks Manage Private Keys… .

9. Add IIS_IUSRS to the permission group.
10. Click OK to close all dialog boxes.
 Note
Use the application pool user with read authorizations for the certificate.
The following error message occurs if you don't set this up correctly:
The private keys of the certificate with the issuer

'System.Security.Cryptography.X509Certificates.X500DistinguishedName' could not
read.
 Note
The Application Pool user needs read access to the private keys of the certificates. For more information,
see SAP Note 2365878 .
3.1.2.8 Checking the Installation
Check that the SAP Disclosure Management website is available by using Internet Explorer to open http://
localhost:<Port Number>/ from the server machine itself and http://<Server Host Name or IP
Address>:<Port Number>/.
from any computer in the network
Verify if you are able to log on with the default credentials:
• user: Admin
• password: Initial1
 Note
You are requested to change the default password once you have logged in.

After logon and password change, you should see a screen similar to this one:
3.1.2.9 Configuring the Web Server
To configure the Web server, follow the steps for the IIS version you run.
Microsoft Internet Information Services 7
If you run DM SERVER – APPLICATION SERVER 10.1 on Microsoft Server 2008 or 2008 R2, configure IIS
7.0/7.5 as follows:
1. Enable Static Content:

1. Start the Server Manager.
2. In the Roles folder, right-click Web Server (IIS), then click Add Roles Services.
3. In the Add Roles Services dialog, select the following items:
• Static Content (Installed)
• ASP.NET (Installed)
• .NET Extensibility (Installed)
• ISAPI Extensions (Installed)
• ISAPI Filters (Installed)
4. Click Install to activate the role services.
2. Enable HTTP Activation:
1. In the navigation pane of the server manager, choose Features Add Features .

2. In the feature selection dialog box, expand .NET Framework 4.5 Advanced Services WCF Services.
3. Select HTTP Activation. Any other features that are selected by default can remain selected. If a dialog
box is displayed and prompts you to add features required for HTTP activation, choose Add Required
Features.
4. Choose Next.
5. Confirm your selections.
6. Choose Install to complete the installation.
3. Switch IIS to 64 bit:
1. Start the .
2. Change the following Advanced Settings of the Application Pool(s):
• Select False for “Enable 32-Bit Applications”.
• Select Integrated for “Managed Pipeline Mode”.
3. Close the dialog box.
4. Allow required HTTP verbs (from DM Stack 900(R)):
2. In the Connections pane, go to the Disclosure Management application.
3. In the Home pane, double-click Request Filtering.
4. In the Request Filtering pane, click the HTTP verbs tab.
5. Make sure that the following actions are not denied. If they are, remove them from the list:
• POST
• GET
• PUT
• DELETE
Microsoft Internet Information Services 8.0
If you run DM SERVER – APPLICATION SERVER 10.1 on Microsoft Server 2012 or 2012 R2, configure IIS 8.0
as follows:

2. On Dashboard, click on Add roles and features.
3. On the Before You Begin wizard page, click Next >.
4. On the Installation Type wizard page, make sure that Role-based or feature-based installation is
selected and click Next >.
5. On Server Selection wizard page, make sure that Select a server from the server pool option is selected
and your local server is marked in the list. Then click Next >.
6. On the Server Roles wizard page, go to the Web Server (IIS) checkbox in the toles list and expand the
Web Server (IIS) node. Expand the subnode Web Server, then the subnode Application Development.
Then select the .NET Extensibility 4.5 and ASP.NET 4.5 roles. Confirm that ISAPI Filters and ISAPI
Extensions are also selected automatically as dependent required roles to be installed. Finally, click
Next >.
7. On the Features wizard page, do not make any changes and click Next > to continue.

8. On the Confirmation wizard page, check that following roles are ready to be installed:
• Web Server (IIS)
• Web Server
• Application Development
1. ASP.NET 4.5
2. ISAPI Extensions
3. ISAPI Filters
4. .NET Extensibility 4.5
10. Click Close to hide the wizard when the installation has been completed.
2. Configure Default Delegation State for Features at Lower Levels:
2. Select the top node of the local server instance in the Connections tree view.
3. In Features View, double-click the Feature Delegation icon.
4. In the next view, make sure that Authentication – Anonymous and Authentication – Windows are set to
Read/Write.
5. When you've finished the configuration, close the Server Manager.
2. Change the following Advanced Settings of the application pool(s):
• Select False for Enable 32-Bit Applications.
• Select Integrated for Managed Pipeline Mode.
4. Clean-Up Handler Mapping of IIS Website:
2. Select the website SAP Disclosure Management.
3. Click Handler Mappings.
4. Select the row with the Name “*”.
5. Right-click and click Remove.
5. Allow required HTTP verbs (as of DM Stack 900(R)):
• POST
• GET
• PUT
• DELETE
6. Close the dialog.

Microsoft Internet Information Services 10.0
If you run DM SERVER – APPLICATION SERVER 10.1 on Microsoft Server 2012, 2012 R2 or 2016 configure
IIS 10.0 as follows:

2. On the Dashboard, click on Add roles and features.
3. On the Before You Begin wizard page, click Next >.
4. On the Installation Type wizard page, make sure that „Role-based or feature-based installation” is
selected and click Next >.
5. On Server Selection wizard page, make sure that Select a server from the server pool is selected and
your local server is marked in the list. Then click Next >.
6. On the Server Roles wizard page, navigate to Web Server (IIS) checkbox in the roles list and expand the
Web Server (IIS) node. Expand the subnode Web Server, then the subnode Application Development.
Confirm that .NET Extensibility 4.6, ASP.NET 4.6, ISAPI Extensions and ISAPI Filters are selected
automatically as dependent required roles to be installed. If not, select the .NET Extensibility 4.6 and
ASP.NET 4.6 roles. Finally, click Next .
 Note
For more information, see SAP Note 2753498 .
7. On the Features wizard page, do not change anything and click Cancel if all features are installed on the
selected server, otherwise click Next > to continue.
8. On the Confirmation wizard page, verify that the roles are ready to be installed.
10. Click Close to hide the wizard, when the installation has been completed.
2. Configure Default Delegation State for Features at Lower Levels:
2. Select the top node of the local server instance in the Connections tree view.
3. In the Features View, double-click the Feature Delegation icon.
4. In the next view, make sure that Authentication – Anonymous and Authentication – Windows are set to
Read/Write.
5. When you've finished the configuration, close the Server Manager.
2. Make sure that the following Advanced Settings of the application pool(s) are set to:
1. False for Enable 32-Bit Applications.
2. Integrated for Managed Pipeline Mode.
4. Clean-Up Handler Mapping of IIS Website:
2. Select the website SAP Disclosure Management.
3. Click Handler Mappings.
4. Select the row with the Name “*”.
5. Right-click and click Remove.

5. Allow required HTTP verbs (as of DM Stack 900(R)):
1. POST
2. GET
3. PUT
4. DELETE
3.2 Installation of DM SERVER - APPL SERVER 10.1
Once you have met the software and hardware requirements, found out which components are required to run
your scenario(s) and downloaded the right version of each component from one single DM Stack, you are ready
to install SAP Disclosure Management.
It is recommended that you start with the installation of the most complex component, DM SERVER – APPL
SERVER 10.1.
3.3 Installation of DM SERVER - APPL SERVER 10.1 with

Silent Parameters
You can install the DM SERVER - APPL SERVER 10.1 in silent mode. Please note that you must meet
all prerequisites for the SAP Disclosure Management Application Server and make sure that the parameters
have correct values. It is strongly recommended that you make a backup of your existing configuration files
web.config, cundus.enterpriseReporting.Services.dll.config, and log.config, because they
might be overwritten by the setup. You must execute the command line or batch file that is used for executing
the setup in silent mode as an administrator. The default command for a silent installation is <setup.exe>
-s <silent installation parameters>.
You can use the following command line parameters with the setup:
Parameter Definition
help Show parameter help
uninstall Uninstall the SAP Disclosure Management Application

Server

s Use silent installation. This parameter requires the custom

parameters listed in the table below.
You can use the following CUSTOMERPARAMETERS in a silent installation:
Parameters
SQLSERVER_HOST This parameter specifies the name of

the database server to be used by the
SAP Disclosure Management Applica
tion Server.
SQLSERVER_DATABASE This parameter specifies the name

of the database to be used by the
tion Server.
SETUP_SQLSERVER_AUTHENTICA This parameter identifies the type of

TION authentication that you want to use to
connect to the database server during
the installation. The following numbers
are valid values:
• 0—Windows Authentication.
This parameter tells the setup to
use the SQL connection provided
in the silent installation parameters
• 1—Database Authentication
This parameter can only be used
for a new installation. For up
grades, this parameter should only
be used if the existing database
has been moved manually to an
other server.
SETUP_SQLSERVER_USERNAME During server authentication, this pa

rameter contains the SQL server user
name used to connect to the SQL
server.
 Note
The user must have the necessary
authorizations to create or modify
tables.

DM_SQLSERVER_AUTHENTICATIO This parameter identifies the type of

N authentication you want to use to con
nect to the database server at runtime.
The following values are permitted:
• 0 — Windows Authentication
This parameter tells the setup pro
gram to use the SQL connection
provided in the silent installation
parameters.
• 1—Database Authentication
This parameter can only be used
for a new installation. For up
grades, this parameter should only
be used if the existing database
has been moved manually to an
other server.
SETUP_SQLSERVER_PASSWORD This parameter tells the setup to use

the SQL connection. During server au
thentication, this parameter contains
the SQL server user password used to
connect to the SQL server.
DM_SQLSERVER_USERNAME This parameter contains the user name

that the SAP Disclosure Management
Application Server uses to connect to
the database after installation. This in
formation is saved to the configuration
file for future use. This parameter can
only be used for a new installation.
 Note
The user has only read/write per
mission on DM tables.
DM_SQLSERVER_PASSWORD This parameter contains the user pass

word that the SAP Disclosure Manage
ment Application Server uses to con
nect to the database after installation.
This information is saved to the config-
uration file for future use. This parame
ter can only be used for a new installa
tion.
WEBSITENAME This parameter contains the name of

the IIS Application Pool and IIS Website
that is created on the IIS Web server.

IPADDRESS This parameter defines the IP address

to be used for the SAP Disclosure Man
agement Application Server. This pa
rameter can only be used for a new in
stallation.
WEBSITEPORT This parameter defines the TCP port

number to be used for the SAP Disclo
sure Management Application Server.
This parameter can only be used for a
new installation.
AUTHMETHOD This parameter tells the setup to con

figure the SAP Disclosure Management
Application Server to use basic authen
tication or Active Directory authentica
tion:
• 0 = Basic Authentication
• 1 = Active Directory Authentication

new installation.
 Note
An active DOMAINUSER is required.
AUTHUSER This parameter tells the setup which

domain user to use if the Active Direc
tory authentication method is selected.
new installation.
This parameter tells the setup which

AUTHPASSWORD
domain user password to use if the Ac
tive Directory authentication method is
selected. This parameter can only be
used for a new installation.
DB_BACKUP_DONE This parameter tells the setup that you

confirm that you have made a manual
database backup before updating the
tion Server:
• Yes = You confirm that a database

backup exists.
• No = You do not confirm that a da
tabase backup exists.
Switch for setting the used proto

BINDING_PROTOCOL
col, which can be either "HTTP" or
"HTTPS".

BINDING_CERTIFICATE This parameter is used for setting the

hash value of the SSL certificate that is
used by the DM Application Server for a
secure HTTPS connection.
This parameter is used for defining the

-INSTANCE_NUMBER="<instanc
number of the DM SERVER - APPL
e number>" SERVER 10.1 instance to be updated
or uninstalled.
-CONFIG_UPDATE="<0|1>" This parameter is used to specify the

update option for configuration files:
• 0 = Default Update
• 1 = Custom Update
 Note
This parameter is optional. If this
parameter is left out in the com
mand string, the default update op
tion ("0") is applied by default.
The example below shows an installation from scratch using the basic authentication method:
 Sample Code
<setup.exe> -s -SQLSERVER_HOST="WIN-ANFL4JRDDR2\SQLEXPRESS2008R2"
-SQLSERVER_DATABASE="DisclosureManagementDB"
-SETUP_SQLSERVER_AUTHENTICATION="1"
-SETUP_SQLSERVER_USERNAME="sa" -SETUP_SQLSERVER_PASSWORD="MyPassword1"
-DM_SQLSERVER_USERNAME="CDMUser" -DM_SQLSERVER_PASSWORD="EnterNewPassword"
-WEBSITENAME="SAP Disclosure Management" -IPADDRESS="*" -WEBSITEPORT="8080"
-AUTHMETHOD="0" -BINDING_PROTOCOL="http"
-INSTALLDIR="C:\inetpub\wwwroot\SAP\SAP Disclosure Management"
The example below shows an installation from scratch using the Active Directory authentication method:
 Sample Code
-DM_SQLSERVER_USERNAME="CDMUser" -DM_SQLSERVER_PASSWORD="EnterNewPassword"
-WEBSITENAME="SAP Disclosure Management" -IPADDRESS="*" -WEBSITEPORT="8080"
-AUTHUSER="MyDomain\MyDomainUserName" -AUTHPASSWORD="MyDomainUserPassword1"
-BINDING_PROTOCOL="http"
-AUTHMETHOD="1" -INSTALLDIR="C:\inetpub\wwwroot\SAP\SAP Disclosure Management"
The example below shows an update installation using the authentication method using the authentication
method of the existing instance #1::

 Sample Code
-DB_BACKUP_DONE="Yes" -INSTANCE_NUMBER="1"
Additional Information About Authentication Methods
SETUP_SQLSERVER_AUTHENTICATION If you set this parameter to 1, you must enter valid database
credentials for the SETUP_SQLSERVER_USERNAME and
SETUP_SQLSERVER_PASSWORD parameters.
If you set this parameter to

0, the SETUP_SQLSERVER_USERNAME and
SETUP_SQLSERVER_PASSWORD parameters are not re
quired.
AUTHMETHOD If you set this parameter to 1, it must enter Active Direc

tory authentication credentials for the AUTHUSER and
AUTHPASSWORD parameters.
If you set this parameter 0, the AUTHUSER and

AUTHPASSWORD parameters are not required.
INSTALLDIR This parameter defines the physical installation directory for

the SAP Disclosure Management Application Server. This
parameter can only be used for a new installation and must
be last one in the command string.
3.4 Installation of DM SERVER - TASK ENGINE 10.1
3.4.1 Running the Setup Wizard
Copy the setup file to the desktop of the destination server and run it with administrative Microsoft Windows
permissions.
The setup wizard checks the following software requirements:

 Note
If the result is negative, see Hardware and Software Requirements [page 8] and solve any remaining issues.
To handle instances, follow the instructions described below.
Installing a New Instance from Scratch
1. Run the setup wizard. In the following step, the currently installed instances of DM SERVER - TASK
ENGINE 10.0 on the current system are displayed:

2. The Current Mode field informs you that you're currently in installation mode. It also means that a new
instance of DM SERVER - TASK ENGINE 10.0 will be installed from scratch additionally. The above
screen shows two instances that are already installed on the server machine. Once you continue the
installation from scratch, the new instance will be added to the already existing ones.
3. Click Next: a prerequisites check is performed by the setup wizard. If the prerequisites check is successful,
you can define the name of the DM SERVER - TASK ENGINE 10.1 instance, the associated technical
name of the Windows Service to be created, the TCP port to be used for the TaskEngineService Web
service URL, the protocol (HTTP or HTTPS), and finally the SSL certificate that must be selected once the
instance has been configured for HTTPS usage.

4. If you're in installation mode, the setup wizard checks the values defined in tis step. It checks whether the
instance name, service Name and TCP port are already in use. If the validity check fails, an appropriate
error message is issued and the installation process can't be completed until all values are valid.
 Note
This validity check isn't performed in update mode.
Updating an Already Existing Instance
1. Run the setup wizard. In the same step described under Installing a New Instance from Scratch, you
can update an already existing installation of DM SERVER - TASK ENGINE 10.0, more specifically, what
instance should be updated:

2. In the above screen, Update selected instance is selected, which means that the setup switches to update
mode. The Current Mode field informs you about this. The instance affected by the update is the selected
one listed in the relevant table. In other words, instance #2 will be updated as it is selected in the list.
3. Click Next to perform the update.
 Note
You can update every single existing instance on the current server machine. You can also update DM
Stacks earlier than DM Stack 17xx. Please note that in this case, the DM Stack to be updated must at
least DM Stack 1000 or higher.
 Caution
If you already have a Task Engine instance installed with HTTP, you cannot switch to HTTPS by
updating the instance. If you want to switch this instance to HTTPS, you must first uninstall it, then
reinstall it with HTTPS.
Registering a Manually Created Instance
1. The setup wizard doesn't automatically detect existing instances of DM SERVER – TASK ENGINE 10.1
on your server machine that were created manually, as such instances aren't available as instances in

Windows Registry. To make them available for the setup wizard, click Register existing instance. The
following dialog is displayed:
2. The drop-down list displays all existing DM SERVER - TASK ENGINE 10.1 Windows services available
on the system where you run the setup wizard. If you select Show all, all available Windows services are
displayed. If you deselect Show all, all Windows services with the SAPDM prefix are listed. Once you've
selected a valid service item that is associated with a DM SERVER – TASK ENGINE 10.1 installation
on the same system, you can select this service item to be registered as an instance of DM SERVER –
TASK ENGINE 10.1 in Windows Registry. If you have selected a valid service item that is associated with DM
SERVER – TASK ENGINE 10.1, the relevant version number and the installation directory of the relevant file
system that is connected to the selected service item are displayed.
Uninstalling an Existing Instance
You can't uninstall instances of DM SERVER – TASK ENGINE 10.1 using the Microsoft Windows Control
Panel. Instead, you must use the setup executable file in the Command Prompt or from a batch file providing
the relevant uninstall command. As a prerequisite, you must have the instance number and the service name of
the affected instance at hand.
 Example
If the instance to be uninstalled is #2, the command line is as follows:
<setup.exe> -uninstall -INSTANCE_NUMBER="2" -SERVICE_NAME="SAPDMTaskEngine_2"
If you want to uninstall an instance silently, the command line is as follows:
<setup.exe> -s -uninstall -INSTANCE_NUMBER="2" -SERVICE_NAME="SAPDMTaskEngine_2"

 Note
The value for the SERVICE_NAME parameter is the technical name of the Windows Service item. Make sure
that you run the above-mentioned commands as an administrator in the Command Prompt or use a batch
file.
Installing a New Instance from Scratch Silently
If you want to install a new instance of DM SERVER – TASK ENGINE 10.1 from scratch silently, the
procedure remains identical. You must, however, add the following new parameters to the silent installation
command:
• INSTANCE_NAME="<Display Name of the DM Task Engine Instance/Service>"

• INSTANCE_PORT="<TCP Port for the DM Task Engine Instance>
If you leave out the above parameters, the default values for the installation from scratch are used:
• INSTANCE_NAME="SAP Disclosure Management TaskEngine"

• INSTANCE_PORT="2605"
You can run a silent installation from scratch using following command, assuming that database authentication
is done using the Windows authentication method:
<setup.exe> -s -SQLSERVER_HOST="WIN-G4H4P1I7AI5\SQLSRV2016EXPR"
-SQLSERVER_DATABASE="DMDB2" -SETUP_SQLSERVER_AUTHENTICATION="0"
-DM_SQLSERVER_USERNAME="CDMUser" -DM_SQLSERVER_PASSWORD="Initial1"
-INSTALLDIR="C:\Program Files\SAP\SAPDMTaskEngine2"
-PATH_TO_JRE="C:\jdk-13.0.1\bin\java.exe" -JRE_SETTINGS="-XX:-UseGCOverheadLimit
-XX:+DisableExplicitGC -XX:+UseParallelGC -Xms2G -Xmx20G -jar"
-DISABLE_CRYPTO_KEY_TRANSFER="Yes" -INSTANCE_NAME="SAP DM Task Engine Instance 2"
-INSTANCE_PORT="2606" -BINDING_PROTOCOL="http"
Updating an Existing Instance Silently
If you want to update an already existing instance of DM SERVER – TASK ENGINE 10.1, you must make
sure that the affected instance is already registered in Windows Registry. Once this is done, you must have the
instance number, service name, and service port of the instance at hand, whereafter you can run the silent
update.
You can run a silent installation from scratch using following command, assuming that database authentication
is done using the Windows authentication method:
<setup.exe> -s -SQLSERVER_HOST="WIN-G4H4P1I7AI5\SQLSRV2016EXPR"
-SQLSERVER_DATABASE="DMDB2" -SETUP_SQLSERVER_AUTHENTICATION="0"
-DM_SQLSERVER_USERNAME="CDMUser" -DM_SQLSERVER_PASSWORD="Initial1"
-INSTALLDIR="C:\Program Files\SAP\SAPDMTaskEngine2"
-PATH_TO_JRE="C:\jdk-13.0.1\bin\java.exe" -JRE_SETTINGS="-XX:-UseGCOverheadLimit
-XX:+DisableExplicitGC -XX:+UseParallelGC -Xms2G -Xmx20G -jar"

-DISABLE_CRYPTO_KEY_TRANSFER="Yes" -INSTANCE_NUMBER="2" -INSTANCE_NAME="SAP DM Task
Engine Instance 2" -INSTANCE_PORT="2606"
3.4.2 Selecting an Installation Folder
Choose an installation folder and configure Java Runtime Environment.
You can also configure the path of Java Runtime Environment and the memory settings.

 Caution
The memory size significantly impacts the duration of the validation.
For any server running DM SERVER - TASK ENGINE 10.1 and/or DM SERVER - XBRL SERVICE 10.1,
the following prerequisites must be met:
• Operating system and DM SERVER - TASK ENGINE 10.1 and DM SERVER - XBRL SERVICE 10.1
running in 64-bit mode
• Quad-core 64-bit CPU at 2 GHz or more
• 32 GB RAM and 20 GB free disk space (excluding database)
3.4.3 Configuring Database Details for Setup
The setup wizard is enabled to connect to the target database with a working authenticatio.
Proceed as follows:
1. Select the Microsoft SQL Server already in use by DM.

2. Specify the authentication to be used during the setup process. By default, the standard Microsoft SQL
Server admin user “sa” is used.
3. Enter the database catalog, that is, the database name, already in use by DM and click Next.

3.4.4 Configuring Database Authentication for DM Usage
product. The authentication type is the basic authentication, that is, user and password.
 Caution
Do not use the option Windows authentication of current user, as it is deprecated. For more information, see
SAP Note 2744381 .
The default credentials are:
• User: CDMUser
• Password: <Password entered during Application Server Installation>
 Note
It is required that you enter the same user that is used for DM SERVER – APPL SERVER 10.1.
The credentials are encrypted and saved to the file SAP.DM.TaskEngine.WinService.exe.config in the
installation folder of DM SERVER – TASK ENGINE 10.1.
3.4.5 Adding Location of Application Server for

Cryptographic Key
By default, you can transfer the cryptographic key from the DM SERVER – APPL SERVER 10.1 configuration
to the DM SERVER – TASK ENGINE 10.1 configuration. You can disable this functionality by selecting

Disable Cryptographic Key Transfer. Changes will be manually done later. In this case, you must copy
the cryptographic key entry from the Application Server application installation directory web.config →
appsettings section to the Task Engine installation directory winservice.config → appsettings
section.
If you do not disable the feature, you must provide a valid root URL to the already installed DM SERVER –
APPL SERVER 10.1 and additionally the credentials of an administrative application user.
Once you've selected Register Task Engine in Landscape Configuration of DM Application Server, the current
instance of DM SERVER – TASK ENGINE 10.1 is added in the according landscape configuration of DM
SERVER – APPL SERVER 10.1 administration during the installation. This feature is optional and is disabled
by default.
3.4.6 Installing Arelle for Preview and Validation
Prerequisites
Visual C++ Redistributable for Visual Studio 2017
Procedure
1. Run arelle-win-x64-2018-03-16.exe or any higher version of Arelle.

 Note
Do not change the default installation location (C:\Program Files\Arelle). The file
C:\ProgramFiles\Arelle\arelleCmdLine.exe is required to be found on exactly this location
by SAP Disclosure Management. For more information, see also .
2. You can check the installation by starting the application C:\Program Files\Arelle\arelleGUI.exe.
3.4.7 Checking the Installation
1. To check the installation of DM SERVER – TASK ENGINE 10.1, start Internet Explorer on the destination
server machine and open http://localhost:2605/TaskEngineService/.
2. Check the webpage. It should look like this:

3.

3.4.8 Performing a Health Check of Installed Task Engine
Once you've installed or updated a DM SERVER - TASK ENGINE 10.1 instance, a wizard step for checking
the status of the currently installed or updated instance is displayed:
This wizard step summarizes the status of the installed or updated instance of DM SERVER - TASK ENGINE
10.1. It checks if the TaskEngineService endpoint is up and running. In case or errors, the status is updated
accordingly, along with a recommendation to check the installation log for more information about the issues
that occurred.
3.5 Installation of DM SERVER- TASK ENGINE 10.1 With

Silent Parameters
As an alternative to the standard installation process, you can install the Task Engine in silent mode. In other
words, the setup is executed in the background. This type of setup is suitable for remote installations and
allows you to change default parameters like destination path, database server, or database catalog. It also
allows you to change the database user that is used to establish the database connection, when Disclosure
Management is in production mode.
The syntax for the setup command is as follows: setup.exe -s <parameters>. To display the general setup
parameter help, run the setup program with following command: setup.exe -help.
To uninstall the TaskEngine silently, run the following command:setup.exe -s -uninstall.

The following parameters are available for silent installation:
Command Line Parameter Description
SQLSERVER_HOST="<Database Server>" Database server name (FQDN) or IP address.
Name of the database instance on the selected database

SQLSERVER_DATABASE="<Database Name>"
server.
SETUP_SQLSERVER_AUTHENTICATION="<0|1>" This parameter identifies the type of authentication that you

want to use to connect to the database server:
• 0 = Windows authentication
• 1 = Database authentication
SETUP_SQLSERVER_USERNAME="<Administrative Name of the technical DM user for database authentication

Database User>" of the setup program. This parameter must be defined if the
SETUP_SQLSERVER_AUTHENTICATION parameter is set to
"0".
SETUP_SQLSERVER_PASSWORD="<Administrative Password of the technical DM user for database authentica

User Password>" tion of the setup program. This parameter must be defined if
the SETUP_SQLSERVER_AUTHENTICATION parameter is set
to "0".
INSTALLDIR="<Installation Directory>" Destination path.
Name of the technical DM user to be used in the database

DM_SQLSERVER_USERNAME="<DM Database User>"
connection string in the TaskEngine configuration file.
DM_SQLSERVER_AUTHENTICATION This parameter identifies the type of authentication you

want to use to connect to the database server at runtime.
The following values are permitted:
• 0 — Windows Authentication
This parameter tells the setup program to use the SQL
connection provided in the silent installation parame
ters.
• 1 — Database Authentication
This parameter can only be used for a new installation.
For upgrades, this parameter should only be used if the
existing database has been moved manually to another
server.
DM_SQLSERVER_PASSWORD="<DM Database User Password of the technical DM user to be used in the data
Password>" base connection string in the TaskEngine configuration file.
PATH_TO_JRE="<Physical path to 'java.exe' Path to java.exe file of 64-bit Java Runtime Environment.
file>"
JRE_SETTINGS="<Memory Settings for JRE>" Memory settings for Java Runtime Environment.
Add Task Engine machine to DM landscape.

REGISTER_TASK_ENGINE_SERVICE="<Yes|No>"

Command Line Parameter Description
INSTANCE_NUMBER="<Number of the DM Task Number of the DM Task Engine instance.

Engine Instance>"
INSTANCE_NAME="<Display Name of the DM Task Name of the DM Task Engine instance or service.
Engine Instance/Service>"
INSTANCE_PORT="<TCP Port for the DM Task TCP port for the DM Task Engine instance.
Engine Instance>"
-BINDING_CERTIFICATE This parameter is used for setting the hash value of the SSL
certificate that is used by the DM Application Server for a
secure HTTPS connection.
-BINDING_PROTOCOL Switch for setting the used protocol, which can be either
HTTP or HTTPS.
To uninstall DM SERVER- TASK ENGINE 10.1 in UI mode, run the following command: setup.exe
-uninstall.
3.6 Configuration of DM SERVER - APPL SERVER 10.1
3.6.1 Configuring the Main Task Engine
To enable the installed DM SERVER – APPL SERVER 10.1 instance to communicate with one of the installed DM
SERVER – TASK ENGINE 10.1 instances as the main Task Engine, you must enter the URL of the Task Engine in
the system administration of DM SERVER – APPL SERVER 10.1.
To do so, proceed as follows>
1. On the DM website, navigate to Administration System Configuration Misc .

2. Replace the URL placeholder in Task engine web service URL with the URL of the Task Engine used for its
installation verification earlier, for example, http://localhost:2605/TaskEngineService/.
3. Click Save.

3.6.2 Configuring the Component Landscape
1. On the DM website, go to Administration System Configuration Landscape .

2. Click New Component and maintain the following for the DM SERVER – APPLICATION SERVER 10.1, DM
SERVER – TASK ENGINE 10.1, and DM SERVER – XBRL SERVICE 10.1:
• Protocol
• IP / FQDN
• Port
• Type
The following is an example of minimum setup using three instances – one per component – using the default
ports and HTTP:

3.6.3 Checking the Component Landscape Configuration
Once the landscape is configured, the logs of all components are available via the DM website.
1. To check the configuration for correctness, go to Administration Log Files Log Files Application
Sever on the DM website. Select the configured URLs one after another and check the respective log
entries. At this point in time, it is sufficient if the message “No data available” is displayed.

2. Repeat the check for the log files of all task engines. As a result, you should see at least one log file entry
per task engine.
3. Repeat the check for the log files of all XBRL services. As a result, you should see at least one log file entry
per XBRL service.

3.6.4 Configuring Document Web Service
To configure the installed DM SERVER – APPL SERVER 10.1 instance for using the DM Document Web
Service, enter the root folder of the service in the system administration of DM SERVER – APPL SERVER
10.1.
To do so, proceed as follows>
1. On the DM website, go to Administration System Configuration Misc .

2. Replace the URL placeholder in Root folder for the Web services with the URL of the service entered as
follows: http://[host]:[port]/WebServices/WDocumentService.asmx
3. Click Save.

3.7 Installation of DM CLIENT 10.1
3.7.1 Preparation of SAP Disclosure Management Client

Installation
3.7.1.1 Software and Hardware Requirements
The SAP Disclosure Management BW connector desktop application is used to extract data from an SAP BW
system. It should primarily be installed on the end user workstation.
Disclosure Management XBRL reporting add-ons 1.0, see the SAP Disclosure Management 10.1
Product Availability Matrix (PAM). The Product Availability Essentials presentation also contains information for
getting started, and can be found under General Information Details and Dates Essentials .

3.7.1.2 Configuration Requirements for SAP NetWeaver
Business Warehouse
An HTTP or HTTPS connection to the SAP NetWeaver BW server is required and the corresponding proxy and
firewall settings may have to be adjusted.
3.7.1.3 Authorization Requirements and Security Settings

We recommend that you install the software for the local user rather than for all users. To do so, you need
authorization to write registry entries and you must have read/write access to the installation directory.
On the clinet, make sure that the .NET framework security level is set to high (default) to allow the registration
of the DLL files. To do so, select the Trust access to the VBA project object model checkbox in the Developer
Macro Settings area.
3.7.2 Installing SAP Disclosure Management Client
Running the Setup Wizard
Copy the setup file to the desktop of the destination computer and run it with administrative Microsoft
The setup wizard checks the following software requirements. If the result is negative, see Hardware and
Software Requirements in SAP Disclosure Management [page 8] to solve any remaining issues.

Selecting an Installation Folder
If required, change the installation folder of DM Client 10.1.
Checking the Rest of the Installation
Click Install to start the installation.

Proceed as follows:
1. Start a Microsoft Office application directly or open a document on the SAP Disclosure Management server
for editing.
The Disclosure Management ribbon or menu item appears. If no ribbon or menu item appears, activate the
COM-add-in in the application.

2. On the Disclosure Management ribbon or menu, click Start.
The system adds additional options to the ribbon or menu.
3.7.4 SAP Disclosure Management Client Registry Keys
Registry Path
Managable by Name in UI in HKEY_CUR More Informa
UI Configuration RENT_USER Registry Key Values Purpose tion
Yes Language Software\cun Language Language co

dus des
AG\cundusBIP
ublisher
Yes Enable parallel Software\cun AsynCallAllo True/False

connections dus wed
AG\cundusBIP
ublisher
Yes Unify variables Software\cun UnifyVariabl True/False For more infor

dus e mation, see the
AG\cundusBIP detailed de
ublisher scription of the
registry key in
the SAP Disclo
sure Manage
ment client
component. To
view the de
scription,
choose
Configuratio
Common .

Registry Path
Yes Autosize tables Software\cun AutosizeNoTe For more infor

with no tem dus mplateTables mation, see the
plate after data AG\cundusBIP detailed de
link ublisher scription of the
registry key in
the SAP Disclo
sure Manage
ment client
component. To
view the de
scription,
choose
Configuratio
Common .
Yes Display preview Software\cun ShowPreviewR True/False For more infor

data right-to- dus TL mation, see the
left AG\cundusBIP detailed de
registry key in
the SAP Disclo
sure Manage
ment client
component. To
view the de
scription,
choose
Configuratio
Common .

Registry Path
Yes Enable change Software\cun TrackChanges True/False For more infor

tracking for cell dus mation, see the
values in Micro AG\cundusBIP detailed de
soft Word ublisher scription of the
registry key in
the SAP Disclo
sure Manage
ment client
component. To
view the de
scription,
choose
Configuratio
Common .
Yes Enable SSL cer Software\cun EnableSSLCer True/False For more infor
tificate checks dus tificateChec mation, see the
for SOAP AG\cundusBIP ksForSOAP detailed de
registry key in
the SAP Disclo
sure Manage
ment client
component. To
view the de
scription,
choose
Configuratio
Common .

Registry Path
Yes Microsoft Word Software\cun WordTableFor Path to local For local use of For more infor
template dus matPath folder Microsoft Word mation, see the
AG\cundusBIP templates detailed de
registry key in
the SAP Disclo
sure Manage
ment client
component. To
view the de
scription,
choose
Configuratio
Common .
No Software\cun CSFSERVERNAM DataSource Last connected

dus E name DM server
AG\cundusBIP
ublisher
No Software\SAP EmbedTrueTyp True/false Saves TrueType

\Disclosure eFontsPP fonts in docu
Management ment (only for
Microsoft Pow
erPoint).
Registry keys
No Software\SAP WordProcessI Set automati
increase per
\Disclosure d cally if key is
formance when
Management created
you start Micro
soft Word and
No Software\SAP OfficePath Path to sub Microsoft Excel
\Disclosure folder in Micro applications.
Management soft Office in
stallation folder
containing the
Microsoft Word
and Microsoft
Excel executa
ble files
No Software\SAP ExcelProcess Set automati

\Disclosure Id cally if key is
Management created

Registry Path
No
Software\SAP ShowNotifica • 0 = Disa Disables notifi- Some operating
\Disclosure tions bled cations or systems don't
Management • 1 = Show forces bubble support toast
Bubbles notification. If notifications
not available, with Citrix.
the notification
type depends
on the operat
ing system:
• Windows
versions
lower than
Windows
8: bubbles
• Windows 8
and higher:
toasts
3.8 Installation of Fujitsu Interstage XWand
If your XBRL scenario uses an open taxonomy, you may need to edit the taxonomy files. For this purpose, the
Fujitsu Interstage XWand tool is used.
 Note
For more information, see: http://www.fujitsu.com/global/products/software/middleware/application-

infrastructure/interstage/solutions/xbrl/ .
3.8.1 Installing Fujitsu Interstage XWand
Proceed as follows:
1. Extract the archive XWANDTOOLKITxxxx.zip.

2. Execute autorun.exe.
3. Click Installation.
4. Confirm the execution with administrator rights.
5. Click Next.

6. Enter the license key provided in the zip file and continue.
7. Click Complete, then Next.

8. Click Install.

Start the application from the Windows Start menu Interstage XWand Toolkit Taxonomy Editor & Instance
Creator :
Alternatively, you can directly execute C:\Program Files (x86)\ISXWand\XWand-

tk\tools\xbrl21\run.bat.
3.9 Installation of DM CLIENT 10.1 with Silent Parameters
Installing DM CLIENT 10.1
You can install DM CLIENT 10.1 in silent mode.
 Note
All prerequisites for DM CLIENT 10.1 are met and the parameters are defined with the correct values.

The command prompt or batch file that is used for executing the setup in silent mode must be started as the
administrator.
For the default DM CLIENT 10.1 installation process, use the following syntax:
 Example
setup.exe -s -INSTALLDIR="C:\MyDMClient"
In this example, the client files are installed to the C:\MyDMClient\ program directory.
Additionally, you can use the following command line parameter to display a general parameter help:
setup.exe -help
Uninstalling DM CLIENT 10.1
To uninstall DM CLIENT 10.1, enter the command setup.exe -s -uninstall.
3.10 Installation of DM XBRL MAPPER 10.1
 Note
The DM XBRL MAPPER 10.1 component is only required for XBRL scenarios that require data tagging.
3.10.1 Installing DM XBRL Mapper
Prerequisites
You have installed DM CLIENT 10.1.
Installation
Run the installer (DMXBRLMAPPERxxxx.exe).

Proceed as follows:
1. Start a Microsoft Office application directly or open a document on DM SERVER - APPL SERVER 10.1
for editing.
2. On the SAP Disclosure Management ribbon or menu, an additional option (SAP DM XBRL Mapper) is
displayed.
3. Click Start (SAP DM XBRL Mapper).

4. A new ribbon (DM XBRL) appears.
3.11 Installation of DM XBRL MAPPER 10.1 with Silent

Parameters
Installing DM XBRL MAPPER 10.1
You can install DM XBRL MAPPER 10.1 in silent mode.
 Note
All prerequisites for DM XBRL MAPPER 10.1 are met and the parameters are defined with the correct
values.
The command prompt or batch file that is used for executing the setup in silent mode must be started as the
administrator.
For the default installation process, use the following syntax:
 Example
setup.exe -s -INSTALLDIR="C:\<name of directory>"
In this example, DM XBRL MAPPER 10.1 is installed to the C:\<name of directory>\ program directory.
Additionally, you can use the following command line parameter to display a general parameter help:
setup.exe -help

Uninstalling DM XBRL MAPPER 10.1
To uninstall DM XBRL MAPPER 10.1, enter setup.exe -s -uninstall.
3.12 Installation of BW Connector
3.12.1 Preparation of SAP Disclosure Management BW

Connector Installation
This section provides information about the following tasks:
• Configuration [page 66]

• Authorizations [page 70]
3.12.1.1 Software and Hardware Requirements
The SAP Disclosure Management BW connector desktop application is used to extract data from an SAP BW
system. It should primarily be installed on the end user workstation.
Disclosure Management XBRL reporting add-ons 1.0, see the SAP Disclosure Management 10.1
Product Availability Matrix (PAM). The Product Availability Essentials presentation also contains information for
getting started, and can be found under General Information Details and Dates Essentials .
3.12.1.2 Configuration
On the SAP BW server, run transaction SICF to deactivate the following objects:
• /sap/bc/soap/rfc
• /sap/bc/soap/wsdl11
 Note
You must create and configure all Web services manually in transaction SOAMANAGER. Do not activate
the ICF nodes /sap/bc/soap/rfc or /sap/bc/soap/wsdl11. Activating these nodes might result in security
issues and could prevent the BW connector for SAP NetWeaver from working properly. For more
information, see SAP Note 1394100 .

Related Information
Enabling Web Services [page 67]
3.12.1.3 Enabling Web Services
To prevent disconnection from SAP Business Warehouse, see SAP Note 1811818 . Before you start the
configuration steps, apply all available ABAP support packages for the SAP Disclosure Management BW
connector. More specifically, apply all available ABAP support packages as soon as you have applied the
installation package or upgraded the exchange package.
To enable Web services, see Establishing and Connecting Single Web Services Manually [page 67].
 Caution
For security reasons SAP Disclosure Management no longer supports SOAP Processor 6.20. Deactivate ICF
node /sap/bc/soap/rfc and /sap/bc/soap/wsdl11. It is mandatory to deactivate these ICF nodes and to
establish the single Web services manually. For more information, see SAP Note 1998413 .
3.12.1.3.1 Establishing and Connecting Single Web Services

Manually
Prerequisites
You have administration rights on your machine.
Context
You must establish Web services and connect them to the Web service definition manually.
 Note
You have to establish the Web services separately on each BW system that you want to communicate with
an SAP Disclosure Management client. For more information, see SAP Note 1318499 .
Procedure
1. Call transaction SOAMANAGER and establish single Web services. Make sure that the bindings have exactly
the same spelling as the Web service definitions, including the “/” (slash) characters.

For a table of all Web services, see Web Services and Web Service Definitions [page 68].
For more information about SOA Manager, see SAP Help Portal at https://help.sap.com.
2. Establish the binding between each Web service and the corresponding Web service definition in package /
CUNDUS/BIPUBLISHER.
For a table of all Web services and the Web service definitions, see Web Services and Web Service
Definitions [page 68].
Results
In transaction SICF, the Web services are displayed under /sap/bc/srt/rfc/cundus/* .
3.12.1.3.2 Web Services and Web Service Definitions
Web Service Web Service Definition
CUNDUS_YCU_API_CHAN_BBOOK_RFC /CUNDUS/YCU_API_CHAN_BBOOK_RFC
CUNDUS_YCU_API_DEL_BBOOK_RFC /CUNDUS/YCU_API_DEL_BBOOK_RFC
CUNDUS_YCU_API_DEL_CHILD_RFC /CUNDUS/YCU_API_DEL_CHILD_RFC
CUNDUS_YCU_API_GET_BBOOK_RFC /CUNDUS/YCU_API_GET_BBOOK_RFC
CUNDUS_YCU_API_HAS_ROLE /CUNDUS/YCU_API_HAS_ROLE
CUNDUS_YCU_API_INFO_CHILD_RFC /CUNDUS/YCU_API_INFO_CHILD_RFC
CUNDUS_YCU_API_NEW_BBOOK_RFC /CUNDUS/YCU_API_NEW_BBOOK_RFC
CUNDUS_YCU_API_NEW_CHILD_RFC /CUNDUS/YCU_API_NEW_CHILD_RFC
CUNDUS_YCU_API_NOTE_BBOOK_RFC /CUNDUS/YCU_API_NOTE_BBOOK_RFC

CUNDUS_YCU_API_PUB_BBOOK_RFC /CUNDUS/YCU_API_PUB_BBOOK_RFC
CUNDUS_YCU_API_SEEK_BBOOK_RFC /CUNDUS/YCU_API_SEEK_BBOOK_RFC
CUNDUS_YCU_CHECK_AUTH /CUNDUS/YCU_CHECK_AUTH
CUNDUS_YCU_CHECK_STYLES /CUNDUS/YCU_CHECK_STYLES
CUNDUS_YCU_CHECK_LOGON /CUNDUS/YCU_CHECK_LOGON
CUNDUS_YCU_CHECK_VAR /CUNDUS/YCU_CHECK_VAR
CUNDUS_YCU_CHECK_VERSION /CUNDUS/YCU_CHECK_VERSION
CUNDUS_YCU_GET_BBOOKS /CUNDUS/YCU_GET_BBOOKS
CUNDUS_YCU_GET_BBOOKS_VARS /CUNDUS/YCU_GET_BBOOKS_VARS
CUNDUS_YCU_GET_BBOOKS_XML /CUNDUS/YCU_GET_BBOOKS_XML
CUNDUS_YCU_GET_F4_HIERARCHY /CUNDUS/YCU_GET_F4_HIERARCHY
CUNDUS_YCU_GET_LICENSE_RFC /CUNDUS/YCU_GET_LICENSE_RFC
CUNDUS_YCU_GET_VARIABLE_F4 /CUNDUS/YCU_GET_VARIABLE_F4
CUNDUS_YCU_GET_VAR_DEP /CUNDUS/YCU_GET_VAR_DEP
CUNDUS_YCU_GET_VAR_DEP_SINGLE /CUNDUS/YCU_GET_VAR_DEP_SINGLE

CUNDUS_YCU_SET_LICENSE_RFC /CUNDUS/YCU_SET_LICENSE_RFC
3.12.1.4 Authorizations
Administration rights are required on both the SAP BW server and the client machine that is used for validation.
SAP Disclosure Management users also need authorization for SAP BW queries.
 Note
These authorizations are customer-specific. An example role for SAP BW query users is
SAP_BW_WP_QUERY_USER.
 Note
There are cases where queries are not available in SAP Disclosure Management. If this is the case, allow
external access as shown below:
3.12.2 Installing BW Connector
The software is delivered as an ABAP add-on installation file. For a description on how to
install add-ons, see https://help.sap.com/viewer/3b5766180ec240949501f4b1897a74a0/LATEST/en-US/
493e90fb29002221e10000000a42189d.html and SAP Note 1566421 .

 Caution
Before you install BW Connector, you must download and install the relevant Attribute Change Package
to make BW Connector compatible with SAP S/4HANA On Premise 1809. To do so, go to https://
launchpad.support.sap.com/#/softwarecenter and search for DISCLMG.
3.12.3 Post-Installation of BW Connector
Installation
The installed function modules and Webservice definitions must be bound into single Web Services.
 Note
You need administration rights on your machine to perform these steps.
Configuration
You must create and configure all Web services manually in transaction SOAMANAGER. In other words, do not
activate the ICF node /sap/bc/soap/rfc or /sap/bc/soap/wsdl11, as this may result in security issues
and could prevent the BW connector for SAP NetWeaver from working properly. For more information, see SAP
Note 1394100 .
On the SAP BW server, you can deactivate the above objects in transaction SICF.
Enabling Web Services
You must establish Web services and connect them to the Web service definition manually.
 Note
To prevent disconnection from SAP BW, follow the instructions in SAP Note 1811818 . Before you
start configuration, apply all available ABAP support packages for the SAP Disclosure Management BW
connector. To ensure an error-free operation, apply all available ABAP support packages as soon as you
have applied the installation package or upgraded the exchange package.
 Note
For security reasons, SAP Disclosure Management no longer supports SOAP Processor 6.20. Deactivate
the ICF node /sap/bc/soap/rfc and /sap/bc/soap/wsdl11. It is mandatory to deactivate these ICF
nodes and to establish the single Web services manually. For more information, see SAP Note 1998413 .

 Note
You must establish the Web services separately on each BW system that you want to connect to an SAP
Disclosure Management client. For more information, see SAP Note 1318499 .
Proceed as follows:
1. Run transaction SOAMANAGER and establish single Web services.

For more information about SOA Manager, see SAP Help Portal (http://help.sap.com) and search for the
relevant product and release.
2. The following is a recommended naming convention (please adhere to this convention): if, for example, the
service name is CUNDUS_YCU_CHECK_VERSION, the binding name is /CUNDUS/YCU_CHECK_VERSION.
 Note
Make sure that the bindings have exactly the same spelling as the Web service definitions, for example,
the service uses an underscore (_), while the binding has a slash (/).
3. Establish the binding between the Web service and the corresponding Web service definition in package /
CUNDUS/BIPUBLISHER.
The following objects need to be bound (Please note that four delivered objects are obsolete.):
Define: Web Service Bind to: Web Service Definition
CUNDUS_YCU_API_CHAN_BBOOK_RFC /CUNDUS/YCU_API_CHAN_BBOOK_RFC
CUNDUS_YCU_API_DEL_BBOOK_RFC /CUNDUS/YCU_API_DEL_BBOOK_RFC
CUNDUS_YCU_API_DEL_CHILD_RFC /CUNDUS/YCU_API_DEL_CHILD_RFC
CUNDUS_YCU_API_GET_BBOOK_RFC /CUNDUS/YCU_API_GET_BBOOK_RFC
CUNDUS_YCU_API_HAS_ROLE /CUNDUS/YCU_API_HAS_ROLE
CUNDUS_YCU_API_INFO_CHILD_RFC /CUNDUS/YCU_API_INFO_CHILD_RFC
CUNDUS_YCU_API_NEW_BBOOK_RFC /CUNDUS/YCU_API_NEW_BBOOK_RFC
CUNDUS_YCU_API_NEW_CHILD_RFC /CUNDUS/YCU_API_NEW_CHILD_RFC
CUNDUS_YCU_API_NOTE_BBOOK_RFC /CUNDUS/YCU_API_NOTE_BBOOK_RFC
CUNDUS_YCU_API_PUB_BBOOK_RFC /CUNDUS/YCU_API_PUB_BBOOK_RFC
CUNDUS_YCU_API_SEEK_BBOOK_RFC /CUNDUS/YCU_API_SEEK_BBOOK_RFC
CUNDUS_YCU_CHECK_AUTH /CUNDUS/YCU_CHECK_AUTH
CUNDUS_YCU_CHECK_LOGON /CUNDUS/YCU_CHECK_LOGON
CUNDUS_YCU_CHECK_STYLES /CUNDUS/YCU_CHECK_STYLES

Define: Web Service Bind to: Web Service Definition
CUNDUS_YCU_CHECK_VAR /CUNDUS/YCU_CHECK_VAR
CUNDUS_YCU_CHECK_VERSION /CUNDUS/YCU_CHECK_VERSION
CUNDUS_YCU_GET_BBOOKS /CUNDUS/YCU_GET_BBOOKS
CUNDUS_YCU_GET_BBOOKS_VARS /CUNDUS/YCU_GET_BBOOKS_VARS
CUNDUS_YCU_GET_BBOOKS_XML /CUNDUS/YCU_GET_BBOOKS_XML
CUNDUS_YCU_GET_F4_HIERARCHY /CUNDUS/YCU_GET_F4_HIERARCHY
CUNDUS_YCU_GET_LICENSE_RFC /CUNDUS/YCU_GET_LICENSE_RFC
CUNDUS_YCU_GET_VARIABLE_F4 /CUNDUS/YCU_GET_VARIABLE_F4
CUNDUS_YCU_GET_VAR_DEP /CUNDUS/YCU_GET_VAR_DEP
CUNDUS_YCU_GET_VAR_DEP_SINGLE /CUNDUS/YCU_GET_VAR_DEP_SINGLE
CUNDUS_YCU_SET_LICENSE_RFC /CUNDUS/YCU_SET_LICENSE_RFC
 Note
On protocol security
Enable SSL if needed, for example, if you want to use HTTPS.
Set transport channel authentication to: User ID/Password.
Verify the configuration
In transaction SICF, the Web services are displayed under /sap/bc/srt/rfc/cundus/*.
If you expand each web service, it should look like this:
 Note
The ‘001’ is the client number, so this may vary on your system.

Authorizations
1. BW Queries
You need administration rights on both the SAP BW server and the client machine that is used for
validation.
SAP Disclosure Management users also need authorizations for SAP BW queries.
 Note
These authorizations are customer-specific. An sample role for SAP BW query users is
SAP_BW_WP_QUERY_USER.
 Note
There are cases where queries are not available in SAP Disclosure Management. If this is the case,
allow external access as shown below:
2. RFC Authorization
To use SAP Disclosure Management, you need authorizations for Remote Function Call (RFC) destinations.
To enable RFC, choose one of the following options:
• Assign the corresponding access rights directly to the user.
SAP Disclosure Management users must have RFC (S_RFC) authorizations for the three function
groups, which are available under /CUNDUS/* and Web Service Authorizations (S_SERVICE).
• If a more detailed authorization situation is required, assign the user to the function group:
 Note
Make sure that every user has the appropriate rights to execute the function modules.

For more information on RFC Authorization, see SAP Help Portal (http://help.sap.com).
3. Briefing Book Authorization

Users who need to access and publish briefing books without restrictions, even if they do not own
the briefing book, should be assigned to the authorization object “DCUBIPAUH” in the SAP Disclosure
Management BW connector.
3.12.3.1 Assigning Web Service Authorizations
To use SAP Disclosure Management, you need authorizations for Remote Function Call (RFC) destinations.
To enable RFC, choose one of the following options:
• Assign the corresponding access rights directly to the user.

SAP Disclosure Management users must have RFC (S_RFC) authorizations for the three function groups
available under /CUNDUS/* and Web Service Authorizations (S_SERVICE).
• If zou need more authorizations, assign the user to the function group:
 Note
Make sure that every user has the appropriate authorizations to execute the function modules.
For more information, see SAP Help Portal at https://help.sap.com.
3.12.3.2 Assigning Authorizations for Briefing Book

Administrator
Users who need to access and publish briefing books without restrictions, even if they do not own the briefing
book, must be be assigned to the authorization object DCUBIPAUH in the SAP Disclosure Management BW
connector.

3.12.3.3 Administration Tasks
This section provides information on administration tasks you execute after the SAP Disclosure Management
BW connector has been activated:
• Determining Default Host and Port [page 76]
3.12.3.3.1 Determining Default Host and Port
Context
To find the default host name and port number of the SAP Disclosure Management BW connector, proceed as
follows:
Procedure
1. On SAP BW server, enter transaction SMICM to start the Internet Communication Manager.
2. Click Go to Services .
The system displays a list of the configured services.
3.12.3.4 Using Initial or Reset Passwords for Establishing

Connections
You can use initial passwords or passwords reset by your system administrator to establish a connection with
an SAP ERP or an SAP BW DataSource.
For more information, see 2601512 and 2607418 .

3.13 Enabling Data Connections to SAP S4/HANA or SAP
BW4/HANA
Prerequisites
• Check that you are using a supported version of SAP Business Warehouse (SAP BW). For more
information, see .
• Additional correction notes must be applied for some versions of SAP BW. For more information, see SAP
Note 2541557 .
• Configure SSL on your SAP NetWeaver ABAP Application Server. For more information, see and SAP Note
510007 .
Context
Set up cross-origin resource sharing (CORS) between your SAP S/4HANA or SAP BW/4HANA system and SAP
SAP Disclosure Management to establish a connection.
 Note
Setting up a connection requires working with your system administrator and different IT and application
stakeholders in your organization. Most configuration steps are done on your SAP NetWeaver ABAP
Application Server (AS) before the connection from your client is established.
Affected users:
• Users with Create, Read, Update, Delete, and Maintain permissions for Connections
• Users with Execute permission for Other Data Sources.
• Admin, Application Creator, BI Content Creator, BI Admin, and Planner Reporter standard application roles.
Procedure
1. Enable SAP Information Access on your ABAP Application Server
SAP Information Access (InA) is a REST HTTP-based protocol used by SAP Disclosure Management to
access your data sources in real time. You must confirm that your InA package is enabled and services are
running on the ABAP Application Server (ABAP AX) for your data source.
a. Check that your InA package is enabled. To do so, open the following URL in your browser: https://
<Your_ABAP_Server>/sap/bw/ina/GetServerInfo?sap-client=<Your_Client_ID>.

b. Make sure that you are prompted for user credentials and that after login you receive a JSON
response. Replace <Your_ABAP_Server> with your ABAP system host, and <Your_Client_ID> with your
SAP BW client ID.
c. Check that the required Information Access Services are active in your SAP BW/4HANA or SAP BW
system.
d. Access your system using SAP Logon.
e. Execute transaction HTTP Service Hierarchy Maintenance (SICF).
f. Enter the service path /sap/bw/ina and then click Execute. The following dialog box is
displayed:
g. Under Virtual Hosts/Services, go to default_host sap bw ina .
h. Make sure that the following services are active: BatchProcessing, GetCatalog, GetResponse,
GetServerInfo, Logoff, and ValueHelp.
i. Check again if the INA protocol is installed. To do so, open the following
URL in your browser: https://<Your_ABAP_Server>/sap/bw/ina/GetServerInfo?sap-
client=<Your_Client_ID>. Make sure you're redirected to your IdP login page (if configured) and
that no 404 page is displayed after login.
2. Logon Cookie Check
a. The expected result in the browser is a JSON response, starting with ‘{"ServerInfo":..’.
b. Use the Browser Development Tool to check whether the authentication cookies are available.
Additional correction notes must be applied if the logon cookie check failed, please see SAP Note
2594129 .
3. SAP S/4 HANA Server Settings
a. The connection for the client and for the server is established through the client installation. This
means that the client is also required for the server content refresh but only for the initial connection.
Otherwise, the server takes over further processing. The Microsoft Office Applications (Microsoft

Word, Microsoft Excel, and Microsoft PowerPoint) call up the connection to the data source. The Fre
client does this for the server. If necessary, the user must confirm this.
4. S/4 HANA Connect in Hidden Mode
a. In both cases – either client-side connection or server-side connection – the initial call to the
SAP S/4 HANA data source is delegated to an internal browser component. This means that SAP
Disclosure Management 10.1 does not handle the sign-on process. This is done by the internal browser
component.
b. The initial connection call is made in hidden mode. This means neither a browser-based dialog nor a
browser window is visible when an initial call is made. There is also no interaction with the user. If a
user certificate is required and the user has stored more than one certificate in the personal certificate
store, the first certificate is selected by default.
c. Technically, the first internal call starts the URL https://<Your_ABAP_Server>:<Your-SSL-
Portnumber>/sap/bw/ina/GetServerInfo?sap-client=<Your_ABAP_Client_ID>. You must
configure Single Sign-On on <Your_ABAP_Server>. Neither a browser based standard dialog to
handle basic authentication nor a selection page for different authentication methods, nor any other
user interaction can be handled in hidden mode.
5. After the successful initial call, SAP Disclosure Management 10.1 extracts the metadata to initiate more
HTTPS requests without using the internal browser components. In case of client-side content refresh, the
HTTPS requests are started by the DM Client. In case of server-side content refresh, the HTTPS requests
are started by the DM Server. This means that in case of client-side content refresh, the SAP S/4HANA
data source must be reachable by the computer with the DM Client only. In case of server-side content
refresh the S/4HANA data source must be reachable by the computer with the DM Client AND by the DM
Server host.
3.14 Post-Installation of SAP Disclosure Management Server
3.14.1 Activating Detailed Error Messages
Context
If the setup has been successfully completed but the website cannot be loaded, you can modify the
web.config file to gerenate a detailed error message that you can send to the IT support team.
Procedure
1. Navigate to the directory in which you have installed SAP Disclosure Management.
2. Open the web.config file.
3. Change the value in the customerrors-tag from On to Off.
4. Save your changes.

3.14.2 Configuring Virtual SMTP Server
Context
If no SMTP server is installed, install and configure this server manually.
Procedure
1. Open the Microsoft IIS manager.

2. Right-click the link for the virtual SMTP server.
3. Select Properties.
4. In the Default SMTP Virtual Server Properties dialog box, click the Access tab.
5. Click Authentication.
6. Select Anonymous access and click OK.
7. Click Connection.
8. Select All except this list below and click OK.
9. Click Relay.
10. Select All except this list below and click OK.
11. Click Apply to save your changes.
3.14.3 Configuring Data Sources on Server
Context
As of DM Stack 15xx, data source configuration is written to the database. The local configurations are still
located in an xml file (config20.xml).
If you want to make data sources available to all users, we recommend that you create only the connection to
the DM server locally and create all other DM Servers including the DM Server data source on the server.
Create a config20.xml file that only includes the connection to the SAP Disclosure Management
server, and copy the file to the application folder of each user ((%appdata%\cundus AG\cundus
AG\cundusBIPublisher).
 Note
You need the permission Administration - Configure content refresh to add, edit, or delete data sources on
the server.

Procedure
1. In Disclosure Management client, choose the data source to your server and click Connect.
2. Click Connect to switch to server mode.
3. Add all data sources.

4 Upgrade of SAP Disclosure Management
If you are running SAP Disclosure Management 10.0, it is strongly recommended that you upgrade to SAP
Disclosure Management 10.1, as SAP Disclosure Management 10.0 is not supported anymore. For more
information, see SAP Note 2085953 .
To familiarize yourself with the upgrade process, please read SAP Note 2043397 .
Changing to a DM Stack not including a change of the major (DM 10.1) or minor (DM 10.1) version number of
the product is referred to as an “update”.

82 PUBLIC Upgrade of SAP Disclosure Management
5 Uninstalling DM SERVER - APPL SERVER
10.1
Uninstalling DM SERVER - APPL SERVER 10.1 removes the software from the system. All files and
configuration files are removed, as well as the IIS application pool, the IIS website, and the API certificate.
 Note
The database is not removed.
You can uninstall DM SERVER - APPL SERVER 10.1 as follows:
1. Open the Command Line as administrator and enter following command at the command line prompt:
<setup.exe> -uninstall -INSTANCE_NUMBER="<instance number>
 Note
To uninstall DM SERVER - APPL SERVER 10.1 silently, enter the following command:
<setup.exe> -s -uninstall -INSTANCE_NUMBER="<instance number>"
2. Press <Enter> to run the command. A progress bar is displayed during the uninstallation process. When
the process is complete, a success message is displayed. If errors occur during the uninstallation process,
error messages are displayed upon completion of the process.

Uninstalling DM SERVER - APPL SERVER 10.1 PUBLIC 83
6 Update of SAP Disclosure Management
6.1 Prerequisites
• You know which software components are required for the scenario you run
• You know the basic software and hardware requirements
• You know the basics of DM Stacks
• You're familiar with SAP software downloads and know where to find yours
6.2 Choosing the Right DM Target Stack
The DM Stacks Note 2138656 lists the Release Notes for all DM Stacks. These Release Notes inform you
about enhancements, improvements, legal change support, and bug fixes provided with each DM Stack. Find
the DM Stack that fits to your requirements. If there is no other indication, it is recommended that you use the
latest available DM Stack.
6.3 Collection of Required Update Objects
6.3.1 Choosing the Right DM Stack
DM Stacks are working combinations of versions for all DM Components. The DM stacks note 2138656 lists
all DM stacks and provides basic information about this.
The same note refers to release notes for each DM stack. They provide information about enhancements,
corrections, legal change support, and bug fixes.
Please check if the latest DM stack meets your requirements. Unless otherwise indicated, it is strongly
recommended that you use the latest available DM stack.

84 PUBLIC Update of SAP Disclosure Management
6.3.2 Checking the Components To Be Updated
To understand, which Software Components are required to update to the target DM Stack, have a closer look
at DM Stacks Note. The attached table indicates which components have received an update with a certain DM
Stack by showing the cells with a blue background.
The set of all blue entries between the DM Stack you are starting with (excluding) and the target DM Stack
(including) tells which components need to be updated to reach the target DM Stack: If there is at least one
blue cell for a Component, the Component needs to be updated.
6.3.3 Understanding Update Paths
Since the update paths differ between components, it is important to understand which component can be
updated from which version to which version.
Depending on the component, one of the following paths for updating to the latest available DM Stack is
supported:
• Single-step update
From DM Stack 1000, you can directly update DM SERVER – APPL SERVER 10.1 to any higher DM Stack.
• Update via the following sequence (for DM Stacks lower than 1000)
If the start version is not a DM Stack ending “…00”, for example "DM Stack 804", proceed as follows:
• Update via all following DM Stacks until the next DM Stack ending “…00” is reached.
• From the reached DM Stack “...00” update via all following DM Stack “...00” until the latest DM Stack
“...00” is reached.
• From the reached DM Stack “...00” update via all following DM Stacks to the latest DM Stack.
For components that must be updated via an update sequence, the exact sequence of required updates to
reach from a given DM Stack to another is described in DM Stacks Note 2138656 .
The following update path is mandatory for the DM SERVER – APPL SERVER 10.1 component only. If your
current version is part of DM Stack 400 or earlier, you must update every Stack ‘00’ one by one until you
you’ve reached Stack 500.

Update of SAP Disclosure Management PUBLIC 85
As you can see from the graph shown above, from DM Stack 1000, you can directly update DM SERVER –
APPL SERVER 10.1 to any higher DM Stack without following the mandatory update path before reaching DM
Stack 1000.
 Example
Single-step update
A single-step update means that you must uninstall the current component first. Only then you can install
the new component from scratch. This is relevant for all components provided by a setup executable file,
except for the DM SERVER – APPL SERVER 10.1 component (see example for update path b).
If you have installed an earlier version of DM CLIENT 10.1 and you want to perform an update to the latest
available DM Stack, you must download the latest available download object from SAP Software Downloads,
then uninstall the earlier version of DM CLIENT 10.1, and install the new component version.
 Example
Update via Sequence
From DM Stack 1000, you can directly update DM SERVER – APPL SERVER 10.1 to any higher DM Stack
without following the above-mentioned update path. The following example is only required for updates
from earlier DM Stacks.
 Example
Not applicable if you have already reached DM Stack 1000)
You have installed DM SERVER - APPL SERVER 10.1 from DM Stack 511 and you want to update to DM
Stack 902. To do so, download and install in the specified order:
1. All objects following the currently installed DM Stack (see DM Stacks table of DM Stacks Note
2138656 , that is, all blue cells between the version you are starting from and the next DM Stack
“...00”.
2. All objects from DM Stacks “...00” between the start and the target DM Stack.
3. All objects following the DM Stack “...00” until the target DM Stack is reached.
Suppose you want to update from DM Stack 703 to DM Stack 802 and you would like to understand the exact
update sequence for DM SERVER – APPL SERVER 10.1.
Proceed as follows:
1. Open DM Stacks Note 2138656

2. Find the DM Stack you start from and the rows for DM SERVER – APPL SERVER 10.1.
3. Move to the right until you reach your target DM Stack.
4. Every entry with a new build version entry (the ones with blue cell background) marks a DM Stack that
included a new version for this software component.
5. Based on the above explanations, we know that we can:
• Update via a sequence of DM Stacks until we reach a DM Stack “...00”.
• Update to a later DM Stack “...00”.
• Update via the sequence of following DM Stacks.

In our example, these are:
Start Update Step 1 Update Step 2
DM Stack 703 800 802
Service Pack No Yes No
Build Version 10.1.7.253 10.1.8.134 10.1.8.136
The following table shows which components support which of the update paths described above:
Component Update in one single step Update via a sequence
DM CLIENT 10.1 possible* -
DM CONNECTOR FOR NW BI 7.0x - possible
DM CONNECTOR FOR NW BI 7.30 - possible
DM CONNECTOR NW BI 7.31 - 7.50 - possible
DM SERVER - APPL SERVER 10.1 recommended** possible
DM SERVER - TASK ENGINE 10.1 possible* -
DM SERVER - XBRL SERVICE 10.1 possible* -
DM XBRL MAPPER 10.1 possible* -
All other components possible -
* Update in one single step is executed via manual deinstallation of the old version followed by an installation of
a new version
** From DM Stack 1000. If you plan an update from an earlier DM Stack, update via a sequence like described
above.
6.3.4 Downloading Files for Updates
As of DM Stack 902, you can use the DM Stacks table in SAP Note 2138656 ) to find all new downloads of
a DM Stack in the SAP Software Downloads (https://launchpad.support.sap.com/#/softwarecenter ). Click
the link at the top of the column listing the target DM Stack.
 Note
• Table cells with a blue background have been recently released as part of the named DM Stack.
• A yellow background indicates that this version of the component has already been published as part
of an earlier DM Stack. For the downloads, search in SAP Software Downloads for the DM Stack that
first included this version.

For downloads from DM Stacks lower than 902 or if you want to find your downloads manually, navigate as
described below.
SAP Software Downloads provides files in the Installations and Upgrades and Support Packages and Patches
areas:
1. Installations and Upgrades contains a comprehensive download package per product version that is
required only to perform an initial installation of the ABAP-based Components DM CONNECTOR FOR NW
BI.
2. Support Packages and Patches includes all other download objects:
SAP DISCLOSURE MGMT. 10.1 Installations and Upgrades Support Packages and Patches
DISCLOSURE MGM XBRL ADD-IN 1.0 Installations and Upgrades Support Packages and Patches

6.4 Update of DM SERVER – APPL SERVER 10.1
6.4.1 Checking Logon to DM Website
Make sure that the technical user and connection details DM uses to connect to its database are working.
To do so, proceed as follows:
1. Check that the SAP Disclosure Management website is available through http://<Server Host Name
or IP Address>:<Port Number>/ from any computer in the network.
2. Check that you can log on using your previously existing credentials.
3. After logon, your screen should look like this:
4. In case of errors, see Known Issues [page 113].
6.4.2 Making a Backup
If you are updating a system that has been in use before, it is mandatory to back up the following:
• The existing DM database using Microsoft SQL Server Management Studio

• The following configuration files (to be restored later):
• <Installation Location>\web.config
• <Installation Location>\log.config

• <Installation Location>\bin\cundus.enterpriseReporting.Services.dll.config
• The whole folder <Installation Location>\bin as a fallback in case of errors
6.4.3 Enabling Database Access
If you want to update DM SERVER – APPL SERVER 10.1 on a Microsoft Windows Server machine without
Microsoft SQL Server Management Studio, download the following software components from the Microsoft
website and install them on the server:
• Microsoft ODBC Driver 11 for SQL Server

• Microsoft Command Line Utilities 11 for SQL Server
6.4.4 Stopping Microsoft Internet Information Services

(Relevant for DM Stacks Lower Than 1200)
Relevant for Microsoft Internet Information Services 7.0
If you run DM SERVER – APPL SERVER 10.1 on Microsoft Server 2008 or 2008 R2, stop Microsoft
Internet Information Services by following the steps described on https://technet.microsoft.com/en-us/
library/b9339773-7eff-4313-a14b-00f2b9f94ead .
Relevant for Microsoft Internet Information Services 8.0
If you run DM SERVER – APPL SERVER 10.1 on Microsoft Server 2012 or 2012 R2, stop Microsoft
Internet Information Services by following the steps described on https://technet.microsoft.com/en-US/
library/jj635851(v=ws.11).aspx .
6.4.5 Running the Setup Wizard
Copy the executable file to the desktop of the destination server and run it with administrative Microsoft
Manage Instances
You can install several instances of DM SERVER – APPL SERVER 10.1 on a single server machine and have
several instances of different DM Stacks on the same server.

Installing a New Instance from Scratch
You can install a new instance of DM SERVER – APPL SERVER 10.1 from scratch. The following sequence of
the setup wizard shows the list of available instances:
The Current Mode label tells you that you're currently in installation mode and that you're about to install an
instance from scratch.
Updating an Already Existing Instance

You can update an existing instance of DM SERVER – APPL SERVER 10.1 by selecting it and by selecting the
Update selected instance checkbox.

The Current Mode label tells you that you're currently in installation mode and that you're about to update an
existing instance.
 Note
You can update lower stacks as of SAP Disclosure Management Stack 1000.
Registering a Manually Created Instance
Manually created instances of DM SERVER – APPL SERVER 10.1 on your server machine aren't
automatically detected by the setup wizard, as there are no entries for these instances in Windows Registry. To
make them available for the setup wizard, click Register existing instance:

Unregistering an Existing Instance
You can remove existing instances of DM SERVER – APPL SERVER 10.1 and the corresponding entries from
Windows Registry by selecting the instances in the list and clicking Unregister selected instance.
You must confirm the removal of the selected instance. Once you have chosen Yes, the selected instance is
removed from Windows Registry and from the instance list displayed in the setup wizard.
 Note
With the setup wizard, you can't update or uninstall unregistered instances of DM SERVER – APPL
SERVER 10.1.
Uninstalling an Existing Instance
As of DM Stack 1600, you can't uninstall an instance of DM SERVER – APPL SERVER 10.1 in the Control
Panel of Microsoft Windows any longer. Instead, you must uninstall a specific instance using the setup
executable from the Command Line or from a batch file providing the appropriate uninstall command. To
perform the uninstallation, you must have administrator permissions and know the instance number of the
affected instance, for example:
<setup.exe> -uninstall -INSTANCE_NUMBER="2"
You can also perform the installation silently, for example:
<setup.exe> -s -uninstall -INSTANCE_NUMBER="2"
Installing a New Instance from Scratch Silently
Follow the procedure used for lower DM Stacks.
Updating an Existing Instance Silently
You can update an existing instance of DM SERVER – APPL SERVER 10.1 Before doing so, make sure that
the affected instance is already registered in Windows Registry. Once this is done, you must know the instance
number before you can run the silent update using the command string from earlier DM Stacks and by adding
the parameter -INSTANCE_NUMBER=”<instance number>” to the command string.
Prerequisites Checks
The setup wizard checks some software requirements. If the result is negative, see Hardware and Software
Requirements [page 8] and solve any remaining issues.

Database Backup Confirmation
As of DM Stack 802, you must confirm that you have manually created a backup of the existing DM database.

 Note
If you are updating a fresh installation initially performed from scratch, no database backup is required.
Nevertheless, you must confirm that you can continue with the update. In this case only, you can skip the
backup activity by selecting Yes, I created a manual backup and continue with the update by clicking Next.
 Note
It is strongly recommended that you do not uninstall DM SERVER – APPL SERVER 10.1 to resolve
issues. For more information, see Troubleshooting [page 113], otherwise contact SAP Support.
6.4.6 Configuring Database for Setup
You enable the DM setup wizard to connect to the target database with a working authentication..
1. In Microsoft SQL Server Management Studio, log on to the target database with a user with administrative
permissions. The user credentials and the hostname of the database server are required for the next step.
2. In the DM setup wizard, select the Microsoft SQL Server as the database server to be used by DM.
3. Enter the authentication information to be used during the setup process. Make sure to enter the user with
administrative database permissions.
4. Select the database catalog (the database name) to be updated for DM and continue.

6.4.7 Choosing an Update Option for Configuration Files
You can update configuration files for DM SERVER - APPL SERVER 10.1 during the update of an already
installed instance choosing one of the following options:
• Default update
• Custom update
Choosing an Update Option
When you update an already installed instance of DM SERVER - APPL SERVER 10.1, you can choose to also
update your web.config file. By default, the web.config file is automatically copied to a back-up file and
the current configuration file is overwritten by the default delivery state. You can also choose to take over the
current web.config file and extend with changes relevant for a specific stack.
In this setup wizard step, you can select the option you want to apply to your configuration file back up
and continue updating your DM SERVER - APPL SERVER 10.1 instance as already known from earlier DM
Stacks.

Choosing an Update Option for Silent Updates
You can also use the update option when you update DM SERVER - APPL SERVER 10.1 in silent mode. For
this purpose, a new command line parameter CONFIG_UPDATE is available, which you can use as follows:
• Default Update
<setup.exe> -s -... -CONFIG_UPDATE="0"
• Custom Update
<setup.exe> -s -... -CONFIG_UPDATE="1"
 Note
If you leave out this parameter during a silent update, the Default Update option is applied by default.
6.4.8 Checking the Rest of the Installation
1. Click Next to perform the actual update. For installations/updates prior to DM Stack 900(R), some steps
are executed in a command prompt.

2. Check the log files for error messages.
• For updates prior to DM Stack 900(R), check the log files in the folder <installation
folder>\Logs\Install Log\.
• For updates as of DM Stack 900(R), the log files are displayed by the setup wizard as part of the
Installation Details. You can open the content with Microsoft Notepad.
•
3. For updates as of DM Stack 1000, errors are listed in a separate window displayed at the end of the
installation procedure. The list includes installable names and the part of the installable that caused the
error. For more information, see Troubleshooting [page 113].
4. If there are no errors, continue with the update.
6.4.9 Checking the Update
Check if the SAP Disclosure Management website is available through http://localhost:<Port

Number>/ from this computer and through http://<Server Host Name or IP Address>:<Port
Number>/ from any computer in the network.
Check if you are able to logon using your previously existing credentials.

After logon, you should see a screen similar to this one:
6.4.10 Update Paths for DM Stacks Lower than 1000
As of DM Stack 1000, you can directly update DM SERVER – APPL SERVER 10.1 to any higher DM Stack.
The following information is only required for updates from earlier DM Stacks:
• Repeat the steps described in Update of DM SERVER – APPL SERVER 10.1 [page 89] until you reach the
target DM Stack.
• Follow the update path described in Understanding Update Paths [page 85] in combination with DM Stacks
Note 2138656 .
 Example
To update from DM Stack 703 to DM Stack 802, go through the updates from DM Stack 703 to DM
Stack 800 and from DM Stack 800 to DM Stack 802 by executing the steps described above for the two
updates.

6.5 Update of DM SERVER – TASK ENGINE 10.1
When you update an existing installation of DM SERVER – TASK ENGINE 10.1, you can decide in the same
setup step which instance should be fully updated:
The checkbox Update selected instance is checked, meaning that the setup switches to update mode. This is
specified by the Current Mode label. The instance affected by the update is the selected one listed in the list of
found instances. In example, instance 2 will be updated.
When you continue the installation process by clicking Next, the update will be performed as already known
from earlier DM Stacks.
By doing so, you can update every single instance existing on the current server machine. Also, you can update
DM Stacks earlier than DM Stack 1700. The only prerequisite for performing an update is that the DM Stack to
be updated is at least DM Stack 1000 or higher.
If you are updating a system that has been in use before, you must make a backup of the following
configuration files, as you will have to restore them later:
• <Installation Location>\SAP.DM.TaskEngine.Console.exe.config
• <Installation Location>\SAP.DM.TaskEngine.WinService.exe.config
• <Installation Location>\Log.config

6.6 Update of DM SERVER – XBRL SERVICE 10.1
You can update DM SERVER – XBRL SERVICE 10.1 in one step from the current DM Stack to the target DM
Stack. To do so, you have to back up some configuration files, uninstall the current version, install the target
version and then restore the configuration files.
If you are updating a system that has been in use before, you must make a backup of the following
configuration files, as you will have to restore them later:
• <Installation Location>\corepService.ValidationService.dll.config
• <Installation Location>\csfService_ValidationServiceHost.exe.config
• <Installation Location>\Log.config
6.6.2 Uninstalling DM SERVER – XBRL SERVICE 10.1
To uninstall DM SERVER – XBRL SERVICE 10.1, go to Microsoft Windows Control Panel Programs and
Features Uninstall a Program .
6.6.3 Restore the Configuration
Copy the configuration files from your backup
• corepService.ValidationService.dll.config
• csfService_ValidationServiceHost.exe.config
• Log.config
to the installation folder by overwriting the existing files.
6.7 Update of DM CLIENT 10.1
You can update DM CLIENT 10.1 in one step from the current DM Stack to the target DM Stack. To do so,
you have to back up some configuration files, uninstall the current version, install the target version and then
restore the configuration files.

6.7.1 Uninstalling DM CLIENT 10.1
To uninstall DM CLIENT 10.1, go to Microsoft Windows Control Panel Programs and Features Uninstall
a Program .
6.7.2 Installing DM CLIENT 10.1
To update DM CLIENT 10.1, install the target version of DM CLIENT 10.1 as described in Installation of DM
CLIENT 10.1 [page 53].
6.8 Update of DM XBRL MAPPER 10.1
You can update DM XBRL MAPPER 10.1 in one step from the current DM stack to the target DM stack.
To do so, uninstall the current version, and install the target version.
6.8.1 Uninstalling DM XBRL MAPPER 10.1
To uninstall DM XBRL MAPPER 10.1, go to Microsoft Windows Control Panel Programs and Features
Uninstall a Program .
6.8.2 Installing DM XBRL MAPPER 10.1
To update DM XBRL MAPPER 10.1, install the target version of DM XBRL MAPPER 10.1 as described in
Installation of DM XBRL MAPPER 10.1 [page 64].
6.9 Updating Fujitsu Interstage XWand
You can update the Fujitsu Interstage XWand tool by running the installation of a new version. This
automatically updates/replaces the existing version.

Install and verify the target version of DM XBRL MAPPER 10.1 as described in Installation of Fujitsu Interstage
XWand [page 61].

7 DM Fiori Launchpad
During the installation of or update to DM Stack 900(R) or later, the user Admin is authorized to assign
business roles to users. A business role is required to access Fiori apps on the SAP DM Fiori Launchpad.
Proceed as follows:
1. Log on to the SAP DM Fiori Launchpad (http://[DM Server host name]:[DM Server port]/
Areas/FLP/Content/login.aspx.) with the Admin user.
2. Assign the required business roles using the Business Role Assignment app.
7.1 Assigning Business Roles
During the installation of or update to DM Stack 900(R) or later, the user Admin is authorized to assign
business roles to users. A business role is required to access Fiori apps on the SAP DM Fiori Launchpad.
Proceed as follows:
1. Log on to the SAP DM Fiori Launchpad (http://[DM Server host name]:[DM Server port]/
Areas/FLP/Content/login.aspx.) with the Admin user.
2. Assign the required business roles using the Business Role Assignment app.
7.2 Configuring Database Authentication for DM Usage
product. The authentication type is the basic authentication, that is, user and password.
 Caution
Do not use the option Windows authentication of current user, as it is deprecated. For more information, see
SAP Note 2744381 .
The default credentials are:
• User: CDMUser
• Password: <Password entered during Application Server Installation>

104 PUBLIC DM Fiori Launchpad
 Note
It is required that you enter the same user that is used for DM SERVER – APPL SERVER 10.1.
The credentials are encrypted and saved to the file SAP.DM.TaskEngine.WinService.exe.config in the
installation folder of DM SERVER – TASK ENGINE 10.1.

DM Fiori Launchpad PUBLIC 105
8 Technical Post-Installation and Post-
Update Tests
You can perform functional and tests after you have installed or updated SAP Disclosure Management
components.
Prerequisites:
• You must have a test user with the following permissions:

• Period - manage
• Report – view
• Chapter – edit
• Chapter – view
• Administration – Configure system
• A test period with a limited number of chapters and the following types of content:
• Microsoft Excel data cache chapters
• Microsoft Word chapters
 Note
You can use an existing period that has few chapters or few data or in a copy an existing period
delete related Excel and Word chapters/data. This is particularly important for any XBRL scenario
where processing times can be important and data consistency impacts validation.
• A name for a target test period created by roll forward.

• A chapter file extracted from the test chapter
• A Microsoft Excel file properly configured for PDF preview

106 PUBLIC Technical Post-Installation and Post-Update Tests
Tested Software Com
ID ponent Version Tested Feature Actions to Perform Expected Result
1
DM SERVER – APPL DM website write ac In SAP Disclosure A success message is
SERVER 10.1 cess to the database Management, proceed displayed.
as follows:
Optionally,you can
1. Choose check the content of
Settings the roll forwarded pe
riod in Reports. To do
Periods .
so, select the period
2. Select a test pe
and a report. On the
riod and choose
Cockpit tab, you can
Roll forward.
view the chapters with
3. Enter a period
the associated files.
name, select
dates, and click
Roll Forward.
2
DM SERVER – APPL DM security view In SAP Disclosure You can see a list of
SERVER 10.1 Management, choose permissions and a list
Security Global of users, roles, and en

tities or periods.
permissions or
Security Local  Note

permissions . Depending on
your configuration,
global and/or local
permissions apply.

Technical Post-Installation and Post-Update Tests PUBLIC 107
Tested Software Com
3 • DM CLIENT 10.1 DM Microsoft Office 1. On the Report A success message is

tab, select a test
• DM CLIENT add-on displayed.
period and a re
10.1, DM
port containing
SERVER – APPL
Microsoft Word
SERVER 10.1
chapters with da
talinks.
2. On the Cockpit
tab, select a chap
ter containing a
datalink to the
data cache and
click Edit.
3. In Microsoft
Word, choose
SAP Disclosure
Management
Start .
4. In SAP Disclosure
Management,
choose Refresh
Refresh
Document .
5. In the refresh wiz
ard, click Next
several times. You
may need to en
ter DM user cre
dentials.
6. Click Apply
changes and OK.
4
DM SERVER – APPL DM web refresh In SAP Disclosure A success message is
SERVER 10.1 Management, proceed displayed.
as follows:
1. On the Report
tab, select a test
period and a re
port containing
Microsoft Word
chapters with da
talinks.
2. Select a test chap
ter.
3. On the Content
Refresh tab, click
Start Refresh.

Tested Software Com
5 • DM REPORTING DM web preview plug- In SAP Disclosure A Microsoft Word file,

PLUGINS 10.1 in for Microsoft Word Management, proceed which you can open, is
• DM SERVER – as follows: downloaded.
APPL SERVER
1. On the Report tab,
10.1
select a test pe
riod and a report
containing Micro
soft Word chap
ters.
2. On the Cockpit
tab, select a chap
ter, then click the
General tab.
3. Under Available
Preview Types,
click Word.
6
• DM EXCEL TO DM web preview plug- In SAP Disclosure A PDF file opens. You
PDF PLUGIN in for Microsoft Excel Management, proceed can only see data if
10.1 as follows: the chapter was con
• DM SERVER – 1. On the Report tab, figured for PDF pre

select a test pe view.
APPL SERVER
riod and a report
10.1
containing Micro
soft Excel chap
ters.
2. On the Cockpit
tab, select a chap
ter, then click the
General tab.
3. Under Available
Preview Types,
click Excel-to-PDF.

Tested Software Com
7 • DM SERVER – DM landscape and log In SAP Disclosure For each installed

APPL SERVER files Management, proceed server/feature, you
10.1 as follows: should be able to open
• DM SERVER - 1. Choose a log file.
TASK ENGINE
Administration
10.1  Note
Log Files .
• DM SERVER -
2. On each of the Not all features
XBRL SERVICE following tabs, se may be required in
10.1 lect all servers your landscape.
and download the
corresponding log
files:
• Log files
application
server
• Log files tasks
engine
• • Log files
XBRL service
8
• DM SERVER – FC-DM push In SAP Financial Close, A success message is
APPL SERVER proceed as follows: displayed.
10.1 1. Choose
• DM SERVER -
General
TASK ENGINE
Options
10.1
External Links .
2.
In the SAP Disclosure

Management area,
click Check URL.
SAP Disclosure Man

9 DM SERVER – APPL In SAP Disclosure The Fiori Launchpad is
agement Fiori web in
SERVER 10.1 Management, click displayed. Depending
terface
Fiori Launchpad and on your authorizations,
log on with your DM it can either be empty
account. or display apps.
 Note
Valid as of SAP
Disclosure Man
agement SP06.

Tested Software Com
10
DM SERVER – APPL Batch tool From the SAP Dis The upload of the
SERVER 10.1 closure Management chapter file is success
server installation ful.
folder and with the test
chapter file, adapt and
execute the following
command line:
DMBatchTool.exe
/u:user /
p:password /
h:http://[DM-
Server]:
[Port]/ /
upload /s:"C:\
\Import\\DM\
\20-F\Chapter
1.xlsx" /t:"/
2012 Q4/20-F/
Chapter 1
 Example
C:\inet
pub\wwwroot\SA
P\SAP Disclosure
Manage
ment\BatchTool,
run DMBatch
Tool.exe /
u:editor1 /
p:super /h:http://
localhost:1080/ /
upload /s:"Signa
tures_V1.docx" /t:"
/US GAAP 2014/
Form 10-Q/Signa
tures"

Tested Software Com
11
• DM SERVER – XBRL In SAP Disclosure A success message is
APPL SERVER Management, proceed displayed.
10.1 as follows:
• DM SERVER - 1. On the Report tab,
TASK ENGINE select a test pe
10.1 riod and an XBRL
report.
• DM SERVER -
2. On the General
XBRL SERVICE
tab, select the
10.1 root and click
• EU XBRL CONS. Create.
VAL. PLUGIN 3. .Keep all check
10.1 boxes selected
and click OK.
• EU XBRL EXCEL
4. After several mi
PREV PLUGIN
nutes, when a new
10.1
message is dis
• EU XBRL played, click New
VALIDATION messages 1.
PLUGIN 10.1
• EU XBRL WEB
PREV PLUGIN
10.1
12 • DM SERVER – e-Bilanz In SAP Disclosure A success message is

APPL SERVER Management, proceed displayed.
10.1 as follows:
• DM E-BILANZ 1. On the XBRL
PLUG-IN 10.1 Factory tab, select
a period and an e-
Bilanz report.
2. Click the following
buttons one after
another:
• Refresh
Content
• Create
• Validation
• Create
Preview

9 Troubleshooting
If you run into issues during an installation or update, see Known Issues [page 113]. In some cases, you must
run the Install Tool, which is described in Usage of the Install Tool [page 115].
If the issue you experience is not mentioned explicitly, run the Install Tool.
If none of the above helps you solve the issues, please contact SAP Support, as described in SAP Support
[page 117].
 Caution
It is strongly recommended that you do not uninstall DM SERVER – APPL SERVER 10.1 to solve issues.
9.1 Known Issues
The following issues may occur during an update to a specific DM Stack under certain circumstances. For more
information, see the related SAP Notes.
Several of the listed notes refer to the Install Tool. Knowledge about the Install Tool is only required if issues
occur. For more information, see Usage of the Install Tool [page 115].
Issue / Error Message Applicable for Update to DM Stack(s) Resolution
Installation Log contains error mes 1000 2536968

sage concerning "SP10PL00_Create
TempRoleToInstallFioriContent" Instal
lable Part: Cannot insert the value
NULL into column 'AuthorizationOb
jectId', table '<...>.Security.RolePermis
sions'; column does not allow nulls. IN
SERT fails.
Installation Log Contains 'AddIndi 1000 2553129

cesSP10' Error "The CREATE UNIQUE
INDEX statement terminated because a
duplicate key was found for the object
name 'Parameter.Parameters2' and the
index name 'UX_Parameter'."

Troubleshooting PUBLIC 113
Violation of PRIMARY KEY constraint 900 2472900

'PK_<name>'. Cannot insert duplicate
key in object '<table>'. The duplicate
key value is (x, y, z)
Cannot resolve the collation conflict 900 2473157
System.Data.SqlTypes.SqlNullValueEx 900 2473211

ception
Installation of earlier DM Stacks not 900 2468230

possible after previous update and sub
sequent uninstallation
Setup logs "The INSERT statement 900 2552409

conflicted with the FOREIGN KEY con
straint "FK_Parameters2_Plugins" " er
ror
Installation Log contains error: "Execut 900 2536768

ing legacy SQL scripts... The system
cannot find the file specified"
Logon fails with a message All DM Stacks from DM Stack 800 2506938
“The provided credentials are not asso

ciated with an active user. Repeated
wrong password entry will lead to de
activation of the user account. Contact
your administrator.”
Logon fails with a Microsoft Internet In All DM Stacks from DM Stack 800 2506938
formation Services page telling “Machi
neSecret is missing in web.config”
Logon fails with a message “You're not All DM Stacks from DM Stack 800 2474986
connected to a network”
Users are not able to login to the 800 Raise a customer message.
DM website via basic authentication al
though the affected users are active
and the credentials used for login are
correct.
Update not responding due to high 800 2470641

memory usage and MS SQL Server
Shows Memory Peaks of 8+ GB

114 PUBLIC Troubleshooting
Error YesNoParameter InsertSystem 703 Ignore messages like this

ParameterUseLegacyExcelTemplate:
Object already exists
Logon to DM website blocked using 700 If you can run your post-installation test
SSO for DM Stack 700 with a non-SSO user
AND you plan to update to a higher DM
Stack in the next step:
ignore this.
If any of these 2 conditions are not met:
Apply SAP Note 2369568
Installation or Update Protocol Shows 600, 800 2467646

Errors
Database connection or technical user All DM Stacks See chapter Database Connection
not working [page 117]
9.2 Usage of the Install Tool
Basic Information
The Install Tool is a part of the setup provided with DM SERVER – APPL SERVER 10.1 and is usually run
automatically as a part of the execution of the setup wizard. Technically speaking, the DM Install Tool is an
executable file ("install.exe") that you can find in the \bin folder of the installation directory of DM SERVER
- APPL SERVER 10.1.
If issues occur, you may have to run the Install Tool separately. SAP Notes for solving issues like the ones
described in Known Issues [page 113] often include SQL scripts and/or DLLs that modify the DM database
and/or the files in the DM installation folder. These SQL scripts and/or DLLs replace invalid SQL scripts / DLLs
from the standard version they refer to. The related SAP Notes include detailed information about which files to
replace.
The Install Tool always executes one installable at a time.
Before DM Stack 1000: run the Install Tool for the installable named in the error log.
As of DM Stack 1000: run the Install Tool for the installable named in the Failed Installable Parts dialog.

Prerequisites
Before you run the Install tool, you must create a “dbconnect.temp” file to provide a database connection
string that can be used by the Install Tool. This file must be saved within the \bin folder of the installation
location.
Example connection string provided in the dbconnect.temp file:
Data Source=WIN-ANFL4JRDDR2\SQLEXPRESS2008R2;Initial
Catalog=DisclosureManagementDB;User Id=sa;Password=MyPassword#1;Integrated
Security=False;MultipleActiveResultSets=True
Execution
1. Run a command prompt as Administrator.

2. Navigate to the \bin folder in the installation directory of DM SERVER - APPL SERVER 10.1
3. Execute the Install Tool using the following command:
• install.exe /i:<installable> /p:"..\Logs\Install Log" /
conStrFileName:"..\bin\dbconnect.temp" /update
• The installable is a set of DLLs executed to update to one particular DM Stack, for example,
DM101SP09PL00 to update to DM Stack 900.
As of DM Stack 1000: if parts of the installable you named for execution have been executed before without
errors, these parts will not be executed again. The Install Tool will still run the installable to execute the parts
that have not been run without errors before.
Verification
If errors are displayed in the console output of the Install Tool, see Known Issues [page 113] and search for
further SAP Notes to correct the remaining issue(s). Repeat the execution of the Install Tool applying all files/
descriptions provided by the different SAP Notes.
 Note
If you can't access the console output of the Install Tool, for example, because you closed the command
prompt after execution, you can access the same information in the log files in <installation
folder>\Logs\Install Log\.
Next Steps
If all messages shown in the Install Tool’s console output have the Success or Info level, continue with the
verification of the installation described in Checking the Installation [page 23] or Checking the Update [page
98].

116 PUBLIC Troubleshooting
9.3 Database Connection
If the DM website issues errors when you try to access it via http://<Server Host Name or IP
Address>:<Port Number>/ from any computer in the network, the technical user and/or connection details
DM uses to connect to its database are not working.
One of the following applies:
1. The SQL Server name has been changed.

2. The DM database name has been changed.
3. The credentials of the technical user have been changed
4. The technical user does not have access rights to the SQL server and/or database anymore.
To resolve the cases 1, 2 or 3, see Security Guide, chapter “Changing Connection Strings After Encryption”.
To resolve case 4, change the access rights of the technical user to the SQL server and/or database. The
database user needs at least read and write permissions to the database tables but no administrative
permissions.
9.4 SAP Support
If you encounter errors not described in Known Issues [page 113], if you can't find any SAP Note mentioning
the issue, or if an additional manual execution of the installation tool as described in Usage of the Install Tool
[page 115] did not help either, please open a customer message under component EPM-DSM-INS and enter the
following information:
• The error message and/or behavior you experience

• The DM Stack you started with, for example, DM Stack 703
• The DM Stack you plan to update to, for example DM Stack 900R
• The exact component and update/installation step during which the issue occurred, for example, while
updating DM SERVER APPL SERVER 10.1 from DM Stack 703 to DM Stack 800
• Any individual DLL file versions you've received from SAP
Example
”Deviating from the standard, we started with the file
cundus.enterpriseReporting.Services.Interfaces.dll in file version 10.1.7.254.”
• Your procedure
Example
“After running the setup wizard I applied SAP Note 123 including a manual execution of the Install Tool. The
error described kept occurring from the initial setup wizard execution until now.”
• Your complete system configuration including the following:
• OS version
• Microsoft Office version
• Web browser and web browser version
• Available RAM

Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

118 PUBLIC Important Disclaimers and Legal Information
Important Disclaimers and Legal Information PUBLIC 119
www.sap.com/contactsap
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

Installation and Upgrade Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installation and Upgrade Guide

Uploaded by

Copyright:

Available Formats

PUBLIC

Document Version: DM Stack 20xx – 2022-11-26