dm101 Install en

PUBLIC
SAP Disclosure Management

Document Version: 10.1 SP08 – 2016-11-24
Installation and Upgrade Guide

Content
1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 Hardware and Software Requirements in SAP Disclosure Management. . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 SAP Notes for the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3 Downloading SAP Disclosure Management Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2 Installation of SAP Disclosure Management Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

2.1 Preparation of SAP Disclosure Management Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Software and Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Configuration of Microsoft IIS 7.0 Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 How to Perform an Initial Installation of SAP Disclosure Management Application Server . . . . . . . . . . . . 11
How to Use the Repair Function During Installation of the SAP Disclosure Management Server
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Configuration After Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3 How to Upgrade SAP Disclosure Management 10.0 to SAP Disclosure Management 10.1. . . . . . . . . . . . 20
How to Uninstall SAP Disclosure Management Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.4 How to Set Up the SAP Disclosure Management Task Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Installing Arelle for Validation of your U.S. SEC Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.5 SAP Disclosure Management XBRL Service Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.6 Post-Installation of SAP Disclosure Management Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Hypertext Transfer Protocol Secure (HTTPS) for SAP Disclosure Management. . . . . . . . . . . . . . . . 28
Enabling Single Sign-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Testing Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Testing the Task Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Activating Detailed Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Configuring Virtual SMTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Configuring the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Uploading Configuration File for Data Source Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Using WebDAV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3 Installation of SAP Disclosure Management 10.1 Application Server with Silent Parameters
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.1 Installation of SAP Disclosure Management 10.1 Office Client with Silent Parameters. . . . . . . . . . . . . . 43
4 Installation of SAP Disclosure Management Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.1 Preparation of SAP Disclosure Management Client Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Software and Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Configuration Requirements for SAP NetWeaver BW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Authorization Requirements and Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

2 PUBLIC Content
Upgrading Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.2 Installing SAP Disclosure Management Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.3 How to Install the SAP Disclosure Management XBRL Mapper. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.4 Post-Installation of SAP Disclosure Management Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Configuring Data Source Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Testing the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.5 Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Uninstalling SAP Disclosure Management from Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5 Installation of SAP Disclosure Management BW Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

5.1 Preparation of SAP Disclosure Management BW Connector Installation. . . . . . . . . . . . . . . . . . . . . . . . 51
Software and Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Enabling Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.2 Installing SAP Disclosure Management BW Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.3 Post-Installation of SAP Disclosure Management BW Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Assigning Web Service Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Assigning Authorizations for Briefing Book Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Administration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6 Business Content Packages for SAP Disclosure Management (SAP DM). . . . . . . . . . . . . . . . . . . .58

Content PUBLIC 3
1 Introduction
SAP Disclosure Management comprises a server and client component as well as a BW connector. This guide
provides information about the installation of the components.
The SAP Disclosure Management client is a COM add-in in Microsoft Excel, Microsoft Word, and Microsoft
PowerPoint. After successful installation, 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 and the dependencies between the components:
The target groups for this guide are the following:
● Consultants
● Technical consultants
● IT administrators
SAP Disclosure Management has two product versions, which include more than 25 component versions:
● 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)

4 PUBLIC Introduction
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.
1.1 Hardware and Software Requirements in SAP Disclosure

Management
When compiling a list of the software component versions you want to use, it is important to understand the
hardware and software requirements that need to be met to run this combination of software component
versions.
You can find this information in the Product Availability Matrices of SAP Disclosure Management 10.1 and SAP
Disclosure Management, XBRL reporting add-ons 1.0, supplemented by the Product Availability - Essentials
presentation, in the sections Software Requirements and Hardware Requirements.
Note
In addition to the requirements set out in PAM and the Product Availability - Essentials presentation, Java SE
1.7x Runtime Environment has to be executed in 64-bit mode.
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, which are described in more detail in the Product Availability - Essentials
presentation, in the 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.
1.2 SAP Notes for the Installation
Read the following SAP Notes before you start the installation. These SAP Notes contain the most recent
information on the installation, as well as corrections to the installation documentation.
Make sure that you have the up-to-date version of each SAP Note, which you can find at https://
support.sap.com/notes .

Introduction PUBLIC 5
SAP Note Number Title Description
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
1566421 Installing DISCMLG on SAP NetWeaver Description for installing add-on for SAP
7.0 (BI 7.1) NetWeaver
984200 You cannot change DEVICE_CLASS Using REQUEST_DEVICE_CLASS

parameter in existing session
1318499 Transportability of Web Service Transport of Web service configurations

no longer supported due to security and
connectivity issues
2043397 SAP Disclosure Management 10.1 Description for installing SAP Disclosure
Installation Note Management
2052707 Migration of SQL server 2005 database Upgrading SAP Disclosure Management
to SQL server 2008 with subsequent 10.0 SP08 or higher running with SQL
continuation of SAP Disclosure Server 2005 to SAP Disclosure
Management 10.1 setup Management 10.1
Service Pack 05 Management 10.1 SP05
Service Pack 06 Installation Note Management 10.1 SP06
2316228 SAP Disclosure Manaegement 10.1 Description for installing SAP Disclosure
2250295 Installation of the US SEC Web Preview With SAP Disclosure Management 10.1
Plugin with SAP Disclosure SP05 PL2 the US SEC Preview Plugin
Management 10.1 SP05 PL2 uses the Arelle Edgar Renderer
component for generating preview
results of an XBRL instance. The usage
of the plugin requires some Arelle-
specific software to be installed on each
SAP Disclosure Management Task
Engine server instance.
2365878 Insufficient read access to certificates' After an update to or new installation of

private keys SAP Disclosure Management 10.1
Service Pack 07 or higher the login does
not work.
2394506 Planned Discontinuation of WebDAV WebDAV functionality is switched off by

functionality default

1.3 Downloading SAP Disclosure Management Software
To download SAP Disclosure Management software, go to https://support.sap.com and find the required SAP
Disclosure Management software under Software Downloads Installations and Upgrades or Support
Packages and Patches .
Installations and Upgrades contains one download object for each product version:
● This includes all software component versions available at a certain point in time (for example, the initial
release of a product version).
● It does not necessarily include the latest support packages and patches.
● Certain software component versions may be missing if they were initially released at a later point in time.
● The following are required to start from certain components, namely the ABAP-based software component
versions:
○ DM CONNECTOR FOR NW BI 7.0
○ DM CONNECTOR FOR NW BI 7.30
○ DM CONNECTOR FOR NW BI 7.31 / 7.4
Support Packages and Patches includes several download objects, which contain the following:
● Each individual software component version

● The available support packages for each software component version
● The available patches for each support package
To understand which software component versions can be installed at which release, support package, or patch
level and which updates can be applied in which sequence, see the example below:
Example
You are planning to implement SAP Disclosure Management 10.1. You require basic information about which
software component versions can be installed at which release/support package/patch level and which
updates can be applied in which sequence. SAP Disclosure Management consists of two product versions –
SAP Disclosure Management 10.1 and SAP Disclosure Management, XBRL reporting add-ons 1.0 – which
include more than 25 software component versions. The allowed base installation and update paths differ
between different software component versions, so it is important to understand which software component
version can be installed and updated in which way.
Go to https://www.support.sap.com and make sure you choose the right downloads by doing the following:
● Get information about initial installation and update options.

● Find out which software component versions you need to run for your scenario(s) in the Product
Availability Essentials presentation in PAM .
● Find out which software component version download to use by checking the sections below. You can find
the different types of downloads for the two different product versions by following the links in the table:
Table 1:
SAP DISCLOSURE MGMT. 10.1 Support Packages and Patches

Installations and Upgrades
DISCLOSURE MGM XBRL ADD-IN 1.0 Support Packages and Patches

Installations and Upgrades

Introduction PUBLIC 7
Information about the following areas is available at https://support.sap.com .
Documentation
Description Internet Address Title
Application Help help.sap.com User help for SAP Disclosure

Management
General Quick Links
Description Internet Address
SAP Notes https://support.sap.com/notes
Released platforms https://support.sap.com/platforms
Security https://support.sap.com/security

2 Installation of SAP Disclosure
Management Server
2.1 Preparation of SAP Disclosure Management Server

Installation
To install the server correctly, check if the following prerequisites are met:
Configuration of Microsoft IIS 7.0 Web Server [page 9]
2.1.1 Software and Hardware Requirements
(PAM). The Product Availability Essentials presentation also contains information for getting started, and can be
found under General Information Details and Dates Essentials .
2.1.2 Configuration of Microsoft IIS 7.0 Web Server
Context
To configure Microsoft IIS 7.0 web server, carry out the following steps described in the subchapters.:
Related Information
Enabling Static Content [page 10]

Switching IIS 7.0 to 32 bit [page 11]

Installation of SAP Disclosure Management Server PUBLIC 9
2.1.2.1 Enabling Static Content
Procedure
1. Start the Server Manager.

2. In the Roles folder, right-click Web Server (IIS) to display the context menu.
3. Select Add Roles Services.
4. In the Add Role Services dialog box, select the following items:
○ Static Content (Installed)

○ ASP.NET (Installed)
○ .NET Extensibility (Installed)
○ ISAPI Extensions (Installed)
○ ISAPI Filters (Installed)
5. Click Install to activate the role services.
2.1.2.2 Enabling HTTP Activation
Context
To enable HTTP activation, follow the steps below.
Procedure
1. In the server manager, in the navigation pane, choose Features Add Features .
2. In the feature selection window, 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 that 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.

10 PUBLIC Installation of SAP Disclosure Management Server
2.1.2.3 Switching IIS 7.0 to 32 bit
Procedure
1. Start the Microsoft IIS Manager.

2. Change the following Advanced Settings of the Application Pools:
○ Select True for Enable 32-Bit Applications.
○ Select Integrated for Managed Pipeline Mode.
3. Close the dialog box.
2.2 How to Perform an Initial Installation of SAP Disclosure

Management Application Server
Prerequisites
The hardware and software prerequisites for installing SAP Disclosure Management Application Server must be
fulfilled. Depending on which software component version you want to use, one or more of the following three
methods for installing a software component version from scratch are supported:
1. Start with the version of the software component version that is provided by the initial version (always
supported)
2. Start with the latest support package (supported by some software component versions)
3. Start with the latest patch (supported by some software component versions)
Context
Make sure that there is no previous installation of SAP Disclosure Management Application Server on the
machine. To install SAP Disclosure Management 10.1 from scratch, you must have administrative rights. A wizard
leads you through the following installation steps:
Procedure
1. The system checks whether your computer fulfills the prerequisites. The requirements that are met are
marked with a green checkmark; any that are not met are marked with a red cross. If all prerequisites are
fulfilled and marked with a green checkmark, choose Next.

2. In this step the system connects with the database. SAP Disclosure Management Application Server 10.1 only
supports SQL Server 2008, 2008 R2, and 2012. If a lower version of the database server is selected, the setup
will not proceed and an appropriate message is displayed. Enter or select the database server, correct the
credentials for database connection, and, if required, change the name of the database and choose Next.

3. SAP Disclosure Management Application Server now uses the database credentials to connect to the
database. Select the correct authentication mode and, if required, enter the correct credentials and choose
Next. The authentication mode and credentials are saved to a configuration file for further use by the
application.
4. Here, the IIS website is configured for the SAP Disclosure Management Application Server website. For more
information about the IIS website, see http://support.microsoft.com/kb/323972 .

a. Change the TCP port, name, and installation location of the website, if required.
b. Select whether to run SAP Disclosure Management Application Server as a 32-bit or 64-bit application.
This option will set the property Enable 32 bit Applications to true or false for the application pool selected
to run for SAP Disclosure Management Application Server.
5. You have the option to configure SAP Disclosure Management Application Server to use basic authentication
or basic and active directory authentication. For more information about active directory authentication, see
the Creating Users chapter in the User Administration section of the administration guide. If active directory
authentication is selected, you must enter a valid domain user and password. This user will be used as the
“Identity” user to run the application pool used for the SAP Disclosure Management website. For more
information, see also the Single Sign-On chapter in the security guide and Enabling Single Sign-On in the

installation and upgrade guide.
6. Define the default admin user name and password for SAP Disclosure Management Application Server. This
user can be used to log in for the first time after the installation.

7. The system starts installing SAP Disclosure Management Application Server. This includes copying files,
making registry entries, and executing SQL scripts against the database.

8. In the last step the system completes the installation. To open the release note or the log file, select the
relevant checkbox and choose Finish.
Results
The installation wizard applies the following changes to the system during the installation process:
● Creates and updates the following:
Database tables
roleER database role
Schemes linked to the roleER role
Database user (if defined) linked to the roleER role
SAP Disclosure Management user (if defined)
Default contents for SAP Disclosure Management in the database
IIS web site
● Copies the runtime information to the physical directory of the IIS website
● Registers the aspnet_isap.dll for the website in order to activate ASP.NET MVC
Next Steps
Update of Server Installations

After the initial installation, update to the latest available support package and patch level according to the
supported update paths described in the PAM. Follow the steps described in the setup wizard of each software
component version.
2.2.1 How to Use the Repair Function During Installation of the

SAP Disclosure Management Server
The Repair action in the installation wizard executes a process to repair missing or corrupt files or registry entries.
The database and config files cannot be repaired with this process. To repair the installation, proceed as follows:
1. Start the setup if you have administrative rights.

2. A screen is displayed with an introduction to the maintenance screen for repairing your installation or
uninstallation. It displays the version you are trying to repair. Choose Next to continue.
3. Select whether you want to repair or remove the installation and choose Continue.
4. If you choose to repair the installation, the next screen takes you straight to the installation. Choose Install to
repair the installation.
5. After repair, the final screen to view the log and release note is displayed, with the success or failure of the
repair action.
2.2.2 Configuration After Server Installation
Context
To complete the configuration of the SAP Disclosure Management server installation, proceed as follows:
Procedure
1. On DM SERVER – XBRL SERVICE 10.1, the configuration in the file <installation folder>
\corepService.ValidationService.dll.config (default installation folder is C:\Program Files
\SAP\SAP Disclosure Management XBRL Service) must be edited as follows:
○ The path to the server’s Java SE 1.7x Runtime Environment (>>key=”PathToJavaVM”<<) as shown in
line 5 of the example below.

○ The allocated memory for Java SE 1.7x Runtime Environment (>>-Xmx8G<<). The default value of 8 GB
can be increased to 20 GB to improve performance depending on the demands of the particular scenario
(number of parallel tasks, size of data involved, and so on) as displayed in line 7 of the example below.
2. To enable quick access to all log files created by each installed DM SERVER – APPL SERVER 10.1, DM SERVER
– XBRL SERVICE 10.1, and DM SERVER – TASK ENGINE 10.1, enter the system landscape information
required in SAP Disclosure Management web administration, in System Configuration, then Landscape.
Create an entry for each server component installed.
Note
All entries are meant to reflect the existing configuration – you cannot change the configuration here.
○ Component protocol can be http or https depending on your configuration.

○ Component IP / FQDN depending on your configuration.
○ Component port depending on your configuration. If unchanged, ports for application servers are as
chosen during setup or manually in the Microsoft IIS configuration. For task engines: 2605 and for XBRL
services: 2981.
○ Component type: Application Server, Task Engine, or XBRL Service.
Note
Entries cannot be changed. If settings need adjustment, delete an entry then create it anew.
3. Once the application server installation is complete, deploy plugins as follows. Upload the support package or
patch level corresponding to your application server required for your scenario(s) following the steps
described under Configuring the Server [page 37] paragraph 3.
Transport
To transport your customizing, master data, and content to another system (for example, from a
development system to a test system and later to a productive system), see under Import and Export of
Content in SAP Disclosure Management in the SAP Disclosure Management User Help.
Note
Import and export limitations can be found in SAP note 2104952 .

2.3 How to Upgrade SAP Disclosure Management 10.0 to
SAP Disclosure Management 10.1
You can upgrade SAP Disclosure Management 10.0 SP08 or higher to SAP Disclosure Management 10.1. As the
10.1 setup is a major update from the old releases SP08 or higher, it is necessary to uninstall the existing version
found on the system and delete all the files, and install the latest files and database changes. The database is not
deleted during uninstallation of the old version, so that it can be referenced again during the upgrade. Therefore.
we strongly recommend that you back up your database and config files such as web.config, log.config,
config20.xml, and other data sources. The installation wizard overwrites these files with the latest changes. The
steps described below show the upgrade screens in detail.
1. Start the setup and ensure that you have administrative rights. The screen displays an introduction and the
note that we recommend you read before starting the installation process. Once you have read the note,
choose Next to continue.
2. In the next step, the system checks whether you have installed the required software. The prerequisites that
are met are displayed with a green checkmark; those that are not are displayed with a red cross. The setup
will only continue if all the prerequisites are met. The setup process also verifies the upgrade path and notifies
you accordingly.
3. Choose Next. The system displays the database connection screen. SAP Disclosure Management Application
Server 10.1 only supports SQL Server 2008 or higher. If you select a lower version of the database server, the
setup will not proceed and displays an appropriate message. Enter or select the database server, and the
correct credentials for database connection.

Note
If you want to continue using the same database, it is very important that you enter the correct name of the
database currently in use with SAP Disclosure Management. Otherwise, the database will not be updated
correctly with the new updates.
Note
If you are currently using SQL Server 2005, you have to manually back up the database and restore it on an
SQL server 2008,2008 R2, or 2012 database server to proceed.
4. In the next step, the database credentials that will be used by the SAP Disclosure Management application
server to connect to the database are shown. Select the correct authentication mode and, if required, enter
the correct credentials and choose Next. The authentication mode and credentials are saved to a config file
for further use by the application.
5. The IIS website for the SAP Disclosure Management application server website is now configured.. For more
information about the IIS website, see http://support.microsoft.com/kb/323972 . Define the following
fields:
Table 2:
Name The friendly name appears in the tree of IIS Manager. You
can change it later if you want to rename the site.
IP address Enter the IP address that users can use to access this site.

Port Enter the port at which HTTP.sys must listen for requests
made to this website. The default port is 80. If you specify a
port other than the default port, clients must specify the
port number in requests to the server, otherwise they will
not be able to connect to the website.
Host Name Enter a host name if you want to assign one or more host
names. The host name is also known as the domain name
to one computer that uses a single IP address. If you spec
ify a host name, clients must use the host name instead of
the IP address to access the website.
By default, the installation wizard detects the old installation location and enters it as the new location. If
required, you can change the installation directory. Change the TCP port, name, and installation location of
the website, if required. Select whether to run the SAP Disclosure Management application server as a 32 bit
or 64 bit application. This option will set the property <Enable 32 bit Applications> to true or false
under the application pool selected to run for the SAP Disclosure Management application server.
6. In the next step, you configure whether SAP Disclosure Management is to use basic authentication or basic &
active directory authentication. For more information about active directory authentication, see . If you select
active directory authentication, enter a valid domain user and password. This user is used as the Identity user
to run the application pool used for the SAP Disclosure Management website. Once you have completed the
screen, choose Next. For more information on active directiony authentication see How to Enable Single Sign-
On [page 33] and the subchapters.

7. The system starts to install SAP Disclosure Management. This includes copying files, making registry entries,
and executing SQL scripts against the database.

8. Once the system has finished the installation a completion message is displayed. To open the release note
and log file, select the checkboxes and choose Finish.
2.3.1 How to Uninstall SAP Disclosure Management Server
Uninstallation will remove SAP Disclosure Management Application Server from the system. It will remove all the
files, registry entries, and config files, but will not remove the database. The files that have been manually installed
or uploaded to the server, such as config20.xml, plugins, and so on, will not be deleted. Uninstallation can be
performed in two ways.
Uninstallation using the setup wizard
Follow the steps below to uninstall SAP Disclosure Management Server:
1. Start the setup (you must have administrative rights).

2. The next screen displays an introduction to the maintenance screen for repairing and uninstalling SAP
Disclosure Management Server. It displays the version you are trying to uninstall. Choose Next to continue.
3. Select whether you want to repair or remove the installation. To uninstall, select Remove and choose Next.
4. Choose Remove to start the uninstallation.
5. Once uninstallation is complete, you get a message confirming the successful deletion of SAP Disclosure
Management Application Server.
Uninstallation from control panel
1. Go to the control panel.

2. Search for and select SAP Disclosure Management Application Server in the list of installed programs.

3. Choose Uninstall to start the process.
4. The status of the uninstallation is shown in the progress bar; upon successful removal of SAP Disclosure
Management Application Server, the progress bar completes and disappears.
2.4 How to Set Up the SAP Disclosure Management Task

Engine
Prerequisites
Before you start installing the task engine, make sure that the following prerequisites are met on the destination
machine:
● Microsoft Windows Server 2008 or higher

● Microsoft .NET Framework 4.0 Full Package or higher
The setup routine must be executed by a user with administrative rights on the destination machine where the
task engine instance or instances will be installed.
Context
The SAP Disclosure Management task engine is part of the SAP Disclosure Management (DM) server, but it is
delivered separately. This enables the administrator to separate the task engine installation from the SAP DM
application server installation. This enables the administrator to install the task engine on a different machine.
Another advantage is that the administrator can install more than one instance of the task engine. This enables
several task engine instances to be used in a horizontally scaled system architecture, controlled by an attached
load balancer.
Procedure
1. Start the task engine installation wizard and read the SAP Note displayed on the screen.
2. Check whether all prerequisites are fulfilled for the installation. If not, install the required software before you
start the installation process. The system displays a green checkmark next to every fulfilled prerequisite, a
red cross for prerequisites that are not met.
3. Select the destination path for the task engine instance. The task engine can be installed on any possible
destination path on a physical hard drive. Installing the task engine on a mapped network drive is not
supported. During the setup process, you can change the default destination path by selecting the path where
the current task engine instance needs to be installed.
4. Select the SAP Disclosure Management database instance. You have to select an existing SAP Disclosure
Management database instance with an existing database catalog that is already used by a running SAP

Disclosure Management application server. This database must be attached to the task engine instance
during the setup process to connect the application server and the task engine instance. Therefore, you must
have a technical database user with administrative permissions that allows you to connect to the SAP
Disclosure Management database during the installation. Alternatively, you can use your own current
administrative Windows authentication to establish a database connection.
a. The first step during the installation is to prepare the database connection on a technical basis to enable
the task engine setup to establish a database connection for validation of the database connection string
used in the task engine configuration file.
b. The second step is to select the authentication method (Windows Integrated Authentication or Technical
User) and, if you have selected the Technical User authentication method, to insert a technical SAP DM
user with its valid credentials. This SAP DM user will be used for the task engine itself to establish a
database connection when the SAP Disclosure Management application server and task engine are
running in productive mode.
2.4.1 Installing Arelle for Validation of your U.S. SEC Scenario
Procedure
1. Download Arelle version 2016-11-22 or the latest version from http://arelle.org/ and install it in the default
directory on your Task Engine server. SAP Disclosure Management uses the executable file C:\Program
Files\Arelle\arelleCmdLine.exe and requires this file to be found exactly in this location.
2. Start Arelle from the start menu. If this does not work, you will need to additionally download and install Visual
C++ Redistributable for Visual Studio 2015.
3. Edit the Arelle configuration file C:\Program Files\Arelle\config\disclosuresystems.xml. In the
default installation everything in this file is commented out. You will need to comment in the following section
<DisclosureSystem names="US SEC (Edgar Filing Manual, Strict)|efm|efm-strict"
[…] />. Within this section, find the row which reads standardTaxonomiesUrl="edgartaxonomies.xml.
Since this file does not exist in your Arelle installation, you need to change this row to
standardTaxonomiesUrl="edgartaxonomies-2016.xml.
Results
You have installed Arelle.
Next Steps
In order to use Arelle for U.S. SEC Validation you have to configure it. For more information, see Using Arelle for
U.S. SEC Validation in the user guide.

2.5 SAP Disclosure Management XBRL Service Setup
Context
The SAP Disclosure Management XBRL service is part of the SAP Disclosure Management Server, but is delivered
separately. This enables the administrator to separate the XBRL service installation from the SAP DM Server
installation, which means that an administrator can install the XBRL Service on a different machine.
Prerequisites for Installing the XBRL Service
Before you start the XBRL service installation, make sure that the following prerequisites are met on the
destination machine: 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 presentation also contains information for getting
started, and can be found under General Information Details&Dates Essential Information .
Before you start the XBRL service installation, make sure that the following prerequisites are met on the
destination machine:
● Microsoft Windows Server 2008 or higher is installed

● Microsoft .NET Framework 4.5.1 Full Package or higher is installed
● Java Runtime Environment (JRE) Version 1.8 (64-Bit) is installed
Procedure
1. Start the SAP Disclosure Management XBRL service wizard.

2. The system checks whether the prerequisites are fulfilled and displays the result of the check: If everything is
correct the individual software components have a green checkmark to the right of the description. If not,
they are marked with a red cross. If software components are missing, install them and start the installation
again.
3. Select the destination path where you want the XBRL service to be installed.
The XBRL service can be installed on any destination path on a physical hard drive. Installing the XBRL service
on a mapped network drive is not supported. During the setup process, you can change the default
destination path by selecting a different path where the XBRL service needs to be installed.
4. The system informs you once the installation is completed successfully.
2.6 Post-Installation of SAP Disclosure Management Server
The post-installation for the server comprises the following issues:

● Testing Server Installation [page 35]
● Activating Detailed Error Messages [page 36]
● Configuring Virtual SMTP Server [page 36]
● Configuring the Server [page 37]
● Uploading Configuration File for Data Source Connections [page 38]
● Using WebDAV [page 38]
2.6.1 Hypertext Transfer Protocol Secure (HTTPS) for SAP

Disclosure Management
HTTPS protocol is used to encrypt and authenticate the communication between Web server and client in the
World Wide Web (WWW). To secure your communication in SAP Disclosure Management (SAP DM), you have to
perform the following steps:
● Securing connection between SQL Server and SAP DM

1. Enable SQL Server for encrypted connections.
For information, see the Microsoft help at Encrypting Connections to SQL.

2. Enable SAP DM for encrypted connections.
To enable SAP DM for encrypted connections, you have to modify the related connection strings:
○ Application Server:
○ Use Windows Internet Explorer to navigate to the installation folder of SAP DM Application
Server, which is generally c:\inetpub\wwwroot\SAP\Disclosure Management.
○ Navigate to the bin folder and open the file
cundus.enterpriseReporting.Services.dll.Config.
○ Find the connection string with the name enterpriseReporting and add Encrypt=True; to
the connection string.
Example
connectionString="Data Source=[SQL-Server];Initial Catalog=[DM
Database];Integrated Security=False; User Id=CDMUser;
Password=Initial1; Encrypt=True;"
○ TaskEngine:
○ UsieWindows Internet Explorer to navigate to the installation folder of SAP DM TaskEngine C:
\Program Files (x86)\SAP\SAP Disclosure Management TaskEngine.
○ Open the file SAP.DM.TaskEngine.WinService.exe.Config.
○ Find the connection string with the name taskEngine and add Encrypt=True; to the
connection string.
Example
connectionString="Data Source=[SQL-Server];Initial Catalog=[DM
Database];Integrated Security=False; User Id=CDMUser;
Password=Initial1; Encrypt=True;"

○ Troubleshooting:
○ Error: Certificate chain was issued by an authority that is not trusted
Solution 1: Check if the root certificate (Root CA) is installed on the server that is running MS SQL
Server.
Solution 2: Add TrustServerCertificate=True; to the connection strings.

● Database Encrypting with Transparent Data Encryption (TDE)
TDE encryption is a mechanism provided by Microsoft that allows you to encrypt the entire MS SQL Server
database.
○ Encrypt the database.
The required steps are described in Microsoft MSDN at Transparent Data Encryption (TDE).
Note
Supported MS SQL Server editions are listed below:
○ SQL Server 2012 Enterprise, Developer, and Evaluation editions
○ SQL Server 2008 R2 Datacenter, Enterprise, Developer, and Evaluation editions
○ SQL Server 2008 Enterprise, Developer, and Evaluation editions
● Validation Service
The validation service uses NetTcpBinding. HTTPS is part of the HTTP protocol. NetTcpBinding uses a binary
protocol, which is not HTTP. Therefore, you cannot use HTTPS with
NetTcp. SAP extends the service so that you can use NetTcpBinding with a certificate for transport security.
To enable security, you have to extend the configuration for the validation service on the server and
clients (Task Engine and SAP DM server). To do so, add the following entry to csfServices:
<serviceCertificatefindValue="d714fdded29a4b58c5ed30f26642d7112af9f8d6"
x509FindType="FindByThumbprint" storeLocation="LocalMachine" storeName="My" />
Table 3: Parameters
Parameter Description Mandatory Default Setting Reference to Values
storeName Specifies the name of No My http://msdn.micro

the X.509 certificate soft.com/en-us/
store to open library/system.secur
qð/?€d%˚−rõ°þÙG¥p¢Q¨´Êf†Ü…=
qð/&€x%˚−rõ
°¹Ù¥9¢F¨¾ßf⁄Ü‰˛x]˝1ý
cates.storename.aspx
StoreName Enu
meration
storeLocation The location of the No Local Machine http://msdn.micro

certificate store the soft.com/en-us/
client uses to obtain library/system.secur
qð/?€d%˚−rõ°þÙG¥p¢Q¨´Êf†Ü…=
the client certificate
qð/&€x%˚−rõ
°¹Ù¥9¢F¨¾ßf⁄Ü‰˛x]˝1ý
qð/5€q%−9õ°¢ÙM¥t¢J¨©Èf�Ü“˛}]1ý
tion.aspx StoreLo
cation Enumeration

Parameter Description Mandatory Default Setting Reference to Values
x509FindTypeDef Defines the type of X. No FindBySubjectDistin http://msdn.micro

in 509 search to be exe guishedName soft.com/de-de/
cuted library/system.secur
ò\öÒUì8…³‚8:Ñ.±y:
+Ë·KB5ó®³ê
ò\öËUð8…³‚8!Ñi±0s
<Ë½KW5õ¦ﬁœ&gx©
cates.x509findtype
%28v=vs.85%29.aspx
X509FindType-
Enumeration
findValue The value to search for Yes Depends on

in the X.509 certificate X509FindType. Look
store at same reference.
● Task Engine Service

Follow the steps described in the section How to Configure the TaskEngine Service for HTTPS [page 30].
● Configuring WebDAV for HTTPS support on 64-Bit systems

To enable WebDAV for HTTPS support, you need to change the Web.config file as shown below:
2.6.1.1 How to Configure the TaskEngine Service for HTTPS
Context
To configure the task engine to work with HTTPS, you have to install a certificate on the server and client machine.
Official certificates are issued by the Certificate Authority (CA).
1. To verify if the certificates are available, enter Start Run and enter MMC. This opens the management
console.
2. Choose File Add/Remove Snap-in Add...
3. Double-click Certificates
4. Select Computer Account.
5. Choose Next Finish Close OK .

Register the task engine URL to the SSL. To do this, you need to copy the thumbprint of the certificate.
1. Select the certificate you want to use, open the details tab, and scroll down to the Thumbprint option.
2. Select the thumbprint and copy it.
3. Paste it into the Notepad function, or any other text editor, and remove the spaces between the characters.
Example
Once the spaces between the characters have been removed, it should look like this:
d714fdded29a4b58c5ed30f26642d7112af9f8d6
4. To link the certificate to the task engine URL, run the following command in the Visual Studio command
prompt:
netsh http add sslcert ipport=Taskenginehostip:port number certhash=Thumbprint of
the certificate appid= New GUID clientcertnegotiation=enable
Example
The task engine URL is http://127.0.0.1:2605/TaskEngineService. The command is as follows:
netsh http add select ipport=127.0.0.1:2605

certhash=d714fdded29a4b58c5ed30f26642d7112af9f8d6 appid=
{ 1e421d4a-1b30-4fc5-98fd-19349b2d828c} clientcertnegotiation=enable
5. Configure the configuration file of the task engine service.exe.config as shown below:

6. Configure the server file web.config as shown below:

Results
You have configured the task engine to use SSL with HTTP.
Related Information
http://msdn.microsoft.com/en-us/library/ms733791.aspx
http://www.codeproject.com/Articles/24027/SSL-with-Self-hosted-WCF-Service
2.6.2 Enabling Single Sign-On
Context
To use single sign-on in connection with Microsoft Active Directory, SAP Disclosure Management requires a
Windows domain account with read access to Active Directory. This Windows domain account has to be
configured on the Internet Information Server (IIS). To enable single sign-on you have two options:
1. Run the IIS service under this Windows domain account.

2. Run the IIS Application Pool under this Windows domain account.
Note
Single sign-on is not available for WebDAV and public Web services.

2.6.2.1 How to Configure a Windows Domain Account on IIS
Procedure
1. Connect to the server, choose Start, and enter services.msc in the Search field.
2. On the next screen, double-click the service World Wide Web Publishing Service.
3. On the next screen, select the Log On tab and enter a valid Windows domain account with read access to
Active Directory.
4. Double-click World Wide Web Publishing Service.
Results
You have enabled single sign-on for a Windows domain account.
2.6.2.2 How to Configure a Windows Domain Account for an

Application Pool
Procedure
1. Connect to the server, choose Start, and enter inetmgr in the Search field.
2. In IIS Manager , in the left pane, select Application Pool and choose the relevant IIS application pool.
3. Choose Advanced Settings… in the right pane.
4. On the Advanced Settings screen, select and edit the property Identity in the Process Model section.
5. Choose OK.
6. On the Application Pool Identity screen, select Custom account and choose Set.
7. Enter a valid domain account with read access to Active Directory.

2.6.2.3 Modifying the web.config File
Procedure
1. On the server, navigate to the installation folder of SAP Disclosure Management and open the web.config
file.
2. Search for the setting <forms loginUrl="/Account/LogOn" defaultUrl="/Report/Index"/>.
3. Change the setting to <forms loginUrl="/Account/LogOnAD" defaultUrl="/Report/Index"/>.
4. Save the web.config file.
2.6.3 Testing Server Installation
Context
To test the SAP Disclosure Management server connection, proceed as follows:
Procedure
1. Open an internet browser and enter URL: http://<host>:<port>/ using the host name and port settings
you entered for the setup of the IIS web site.
The system displays the login form for SAP Disclosure Management.
2. Enter the administrator name and the password defined during the installation process.
3. Click Login.
2.6.4 Testing the Task Engine
Prerequisites
You have installed SAP Disclosure Management 10.1.
Context
Test the task engine service. If the service is not running, start the service as follows:

Procedure
1. To open the Window Service Console, choose Start Run then Type services.msc .
2. Select the service SAP Disclosure Management TaskEngine.
3. Choose Start in the context menu.
Results
You have started the task engine service.
2.6.5 Activating Detailed Error Messages
Context
If the setup has been successfully completed, but the web site 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.
2.6.6 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.
2.6.7 Configuring the Server
Context
After installing the server, configure it as follows:
Procedure
1. Set the system configuration:
a. In SAP Disclosure Management, go to Administration System Configuration .

b. On the Misc tab, in the Root folder for the Web-service box, enter the server name and the port number.
c. Update the following information on every tab: e-mail, misc, license, upload, plugins, content refresh.
2. Set the content refresh files:
a. Navigate to Administration Content Refresh Configuration .

b. Configure and upload the config20.xml file. For more information, see Uploading Configuration File for
Data Source Connections [page 38].
c. Upload the BIP_WordTableDef.doc file.
d. Upload the BIP_WordTableTagging.xml file.
3. Upload and register the plugins:
a. Navigate to Administration Plugins .

b. Upload the required plugins to the system, one after the other.
c. Register all plugins needed to create reports.
4. Assign global permissions to the administration user.
You can also create a new superuser including the following roles:
Standard-Admin
Standard-Readonly
Standard-Editor

Standard-Manager
Standard-Transporter
2.6.8 Uploading Configuration File for Data Source

Connections
Context
The configuration of data source connections is stored in the file config20.xml. You can use this file both on the
client and on the server.
If you want to make data sources available to all users, we recommend that you create a configuration for these
data source connections on a client and then upload the config20.xml file to the server. For information on
setting up data source connections on the client, see Configuring Data Source Connections [page 48].
To make it easier for the users, create a config20.xml file, which only includes the connection to the SAP
Disclosure Management server, and copy the file to the application folder of each user.
If you upload a config20.xml file to the system, the existing file will be overwritten. To keep the existing file as an
offline backup, you can download it.
Procedure
1. In Disclosure Management, on the Administration tab, click the Content refresh link.
2. On the Configuration tab, in the section for the config20.xml file, click Browse ...
3. Navigate to the config20.xml file, then click Open.
4. Click Add file.
2.6.9 Using WebDAV
SAP Disclosure Management uses Web-based distributed authoring and versioning (WebDAV) for accessing the
server database and enabling distributed Web authoring.
Note
Please note that, as of SAP Disclosure Management 10.1 SP08, the support of the WebDAV function will be
discontinued for security reasons. For more information, see 2394506 and 2391729
This means that there are the following restrictions in the naming of some objects in SAP Disclosure
Management:
1. The following characters are not allowed in chapter, report, or period names: / \ < > * " ? | § ' ² ³ % : + & ° ,

2. You cannot create a chapter, report, or period name that ends with a space.
3. You cannot create a chapter, report, or period name with two or more consecutive spaces in the name (for
example, period..1).
2.6.9.1 Accessing Web Documents via WebDAV in Read-Only

Mode
Procedure
1. Open a Microsoft Office application and click File Open .

2. In the Open dialog box, enter http://<host>:<port>/Webdav in the File name box.
3. Click Open.
Results
A read-only version of your selected file appears.
Tip
You can connect your frequently used WebDAV folders as a network drive in Windows Explorer. When
connecting the WebDAV folder, make sure that the "W" is written in upper case. The directory is ordered by the
folders for the respective periods. Each period folder contains the following subfolders:
● DataCache
● Document
● XBRL Taxonomy
Each subfolder contains subfolders for the report and its chapters.
2.6.9.2 Accessing Web Documents Using WebDAV by

Mapping the Network Drive
Context

Procedure
1. In Windows Explorer, choose Tools Map network drive .

2. In the open dialog box, enter \\<host>:<port>\Webdav in the Folder field.
3. Log in using your SAP Disclosure Management user name and password.
2.6.9.3 Disabling WebDAV
Context
Access to SAP Disclosure Management using WebDAV is enabled by default. If you do not require WebDAV
access, we recommend that you disable it. Disabling WebDAV means shutting down a potential source of security
leaks.
Procedure
1. Open the web.config file in the root folder of the application server.
2. In the snippet below replace allow with deny:
Source Code
<location path="Webdav">
<system.web>
<authorization>
<allow users="*" />
</authorization>
</system.web>
</location>
<location path="Webdav/Api">
<system.web>
<authorization>
<allow users="*" />
</authorization>
</system.web>
</location>
3. Restart the application.
Note
For more information, see SAP Note 2206377 .

Management 10.1 Application Server with
Silent Parameters
The SAP Disclosure Management application server can be installed in silent mode. It is very important to note
that in silent mode it is assumed that all the prerequisites for SAP Disclosure Management application server are
fulfilled and that the parameters are provided with the correct values. It is very important to make a backup of
your existing config files web.config, cundus.enterpriseReporting.Services.dll.config, log.config, as they may be
overwritten by the setup. 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 Install shield parameters, see
Setup.exe /s /w /v"/qn CUSTOMERPARAMETERS under http://helpnet.flexerasoftware.com/
installshield19helplib/helplibrary/IHelpSetup_EXECmdLine.htm .
The following CUSTOMERPARAMETERS can be used in a silent installation:
Table 4: Parameters
Parameter Definition
IS_SQLSERVER_DO_NOT_USE_REG
IS_SQLSERVER_SERVER This parameter informs the setup of the name of the database
server to be used by the SAP Disclosure Management Appli
cation Server. For upgrades, this parameter should only be
used if the existing database has been moved manually to an
other server.
IS_SQLSERVER_DATABASE This parameter informs the setup of the name of the database
to be used by the SAP Disclosure Management Application
Server. For upgrades, this parameter should only be used if
the existing database has been moved manually to another
server.
IS_SQLSERVER_AUTHENTICATION This parameter identifies the type of authentication that you

want to use to connect to the database server. The following
numbers are valid values:
0—Windows authentication credential of the current user.

This parameter tells the setup to use the SQL connection pro
vided in the silent installation parameters. For upgrades, only
use this parameter if the existing database was moved man
ually to another server.
1—Server authentication
This parameter can only be used for a fresh installation. For

upgrades, this parameter should only be used if the existing
database has been moved manually to another server.

Installation of SAP Disclosure Management 10.1 Application Server with Silent
Parameters PUBLIC 41
SILENT_IS_SQLSERVER_USERNAME In the event of server authentication, this parameter contains

the SQL server user name to use to connect to the SQL
server. This parameter can only be used for a fresh installa
tion.
SILENT_IS_SQLSERVER_PASSWORD This parameter tells the setup to use the SQL connection. In
the event of server authentication, this parameter contains
the SQL server user password to use to connect to the SQL
server. This parameter can only be used for a fresh installa
tion.
SILENT_FSF_SQLSERVER_USERNAME This parameter contains the user name that SAP Disclosure
Management Application Server is to use to connect to the
database after installation. This information is saved to the
config file for future use. This parameter can only be used for
a fresh installation.
SILENT_FSF_SQLSERVER_PASSWORD This parameter contains the user password that SAP Disclo
sure Management Application Server is to use to connect to
the database after installation. This information is saved to
the config file for future use. This parameter can only be used
for a fresh installation.
INSTALLDIR This parameter defines the physical installation directory for

SAP Disclosure Management Application Server. This param
eter can only be used for a fresh installation.
FSF_IISWEBSITEPORT This parameter defines the TCP port number to be used for
SAP Disclosure Management Application Server. This param
eter can only be used for a fresh installation.
APPPOOL_IDENTITY (8 or 1) This parameter tells the setup to configure SAP Disclosure

Management Application Server to use Basic Authentication
or Basic & Active Directory Authentication.
● 1 = Basic Authentication
● 8 = Basic & Active Directory Authentication
This parameter can only be used for a fresh installation.
Important: You need an active DOMAINUSER.
SILENT_APPPOOL_ACC This parameter tells the setup which domain user to use if the
Basic & Active Directory Authentication method is selected.
SILENT_APPPOOL_PWD This parameter tells the setup which domain user password to
use if the Basic & Active Directory Authentication method is
selected. This parameter can only be used for a fresh installa
tion.

42 PUBLIC Parameters
LOGINSITE=LogOnAD This parameter tells the installation to configure the start site
of SAP Disclosure Management to use the selected authenti
cation mode. The following values are allowed:
● LogOnAD = If the Basic & Active Directory Authentication

mode is selected
● LogOn = If the Basic Authentication mode is selected
The example below shows an installation from scratch:
Sample Code
Setup.exe /s /w /v"/qn IS_SQLSERVER_DO_NOT_USE_REG=1

IS_SQLSERVER_SERVER=SQLEXPRESS2008R2
IS_SQLSERVER_DATABASE=DisclosureManagementDB
IS_SQLSERVER_AUTHENTICATION=1
SILENT_IS_SQLSERVER_USERNAME=sa
SILENT_IS_SQLSERVER_PASSWORD=123456
SILENT_FSF_SQLSERVER_USERNAME=CDMUser
SILENT_FSF_SQLSERVER_PASSWORD=Initial1
INSTALLDIR=\"C:\inetpub\wwwroot\"
FSF_IISWEBSITEPORT=8080
APPPOOL_IDENTITY=8
SILENT_APPPOOL_ACC=\"MyDOMAIN\DOMAINUSER\"
SILENT_APPPOOL_PWD=DOMAINUSER
LOGINSITE=LogOnAD"
If you want to update an existing SAP Disclosure Management 10.1 Application server without any parameter
changes, use the command update_setup.exe /s /v/qn. This means the values of the parameters will be
taken from the last successful installation.
3.1 Installation of SAP Disclosure Management 10.1 Office

Client with Silent Parameters
You can install the SAP Disclosure Management 10.1 Office Client in silent mode.
Please define the parameters with the correct values.
Note
In silent mode, it is assumed that all the prerequisites for SAP Disclosure Management client are fulfilled and
that 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 client installation process use the following syntax:

Parameters PUBLIC 43
Example
ClientSetup.exe /s /w /v"/qn INSTALLDIR=\"C:\MyDMClient\"
In this example, the client will be installed into the C:\MyDMClient\ program directory.

44 PUBLIC Parameters
Management Client
4.1 Preparation of SAP Disclosure Management Client

Installation
This section provides information on preparing the installation. The following topics are affected:
● Soft- and Hardware Requirements [page 9]

● Configuration Requirements for SAP NetWeaver BW [page 45]
● Authorization Requirements and Security Settings [page 45]
● Upgrading Client [page 46]
4.1.2 Configuration Requirements for SAP NetWeaver BW
The client must support an HTTP or HTTPS connection to the SAP NetWeaver BW server.
The corresponding proxy and firewall settings may need adjustment.
4.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.
Check the following security settings on the client:
The .NET framework security level must be set to high (default) to allow the registration of the DLL files.
● Select the Trust access to the VBA project object model checkbox in the Developer Macro Settings area.

Installation of SAP Disclosure Management Client PUBLIC 45
4.1.4 Upgrading Client
Context
SAP Disclosure Management 10.0 SP01 uses a different client installer software to that in the previous version.
If SAP Disclosure Management 10.0 SP01 is installed, you can update the client without uninstalling the client
component.
If you upgrade from SAP Disclosure Management 10.0 (client version 10.0.0.24) to SAP Disclosure Management
10.0 SP01 or higher, proceed as follows:
Procedure
1. Uninstall and remove the application completely from your machine.

For more information, see Uninstalling SAP Disclosure Management from Client [page 50]Uninstalling SAP
Disclosure Management from Client [page 50].
2. Restart your machine.
3. Install the new version of the client component.
For more information, see Installing SAP Disclosure Management Client [page 46]Installing SAP Disclosure
Management Client [page 46].
4.2 Installing SAP Disclosure Management Client
Prerequisites
To install the SAP Disclosure Management client, proceed as follows:
Procedure
1. Download the installation zip file from the SAP AG customer site.
2. Unzip the file and double-click the *.exe file to start the installation wizard.
3. To run the installer with administrator privileges, right-click the *.exe file, click Run as ..., and enter the user
name and password of a user who has administration rights on the client machine.
4. Confirm the welcome message and the installed components.
5. Select the program language and click Next.
6. If you want to change the destination folder, click Browse and select another folder.
7. Click Next to install the application and start updating the system.

46 PUBLIC Installation of SAP Disclosure Management Client
8. When the SAP Disclosure Management client has been successfully installed, click Finish.
Results
The installation wizard SAP Disclosure Management inserts the COM-add-ins into the Microsoft Excel, Word and
Powerpoint applications.
The wizard stores program and configuration files in the following standard directories:
● Program files: <program files folder>\SAP\Disclosure Management

● Configuration file: <user folder>\Application Data\cundus AG\cundusBIPublisher
4.3 How to Install the SAP Disclosure Management XBRL

Mapper
The SAP Disclosure Management XBRL Mapper is part of the Disclosure Management Client, but it is delivered
separately. This enables the user to use the XBRL Mapper separately from the SAP Disclosure Management Client
and to update the software entities independently. The setup routine must be executed by a user with
administrative permissions on the destination machine where the SAP Disclosure Management XBRL Mapper is
installed.
Before you start the SAP Disclosure Management XBRL Mapper installation, make sure that the following are
installed on the destination machine:
● Microsoft Office 32-bit

● Microsoft Word 2007 or higher
● Microsoft Excel 2007 or higher
● Microsoft .NET Framework 4.5.1 full package or higher
1. Start the wizard for installing the SAP Disclosure Management XBRL Mapper and choose Next.
2. The system checks whether the prerequisites mentioned above are fulfilled. If so, the system puts a green
checkmark next to the prerequisite. If not, it shows a red cross.
3. Select the destination path for the SAP Disclosure Management XBRL Mapper.
The XBRL Mapper can be installed on any destination path on a physical hard drive. Installing the XBRL
Mapper on a mapped network drive is not supported. During the setup process, you can change the default
destination path by selecting a different one.
4. You are notified once the installation has finished successfully.
4.4 Post-Installation of SAP Disclosure Management Client
The post-installation of the client comprises the following tasks:

● Configuring Data Source Connections [page 48]
● Testing the Installation [page 48]
4.4.1 Configuring Data Source Connections
The installation wizard of SAP Disclosure Management deploys the configuration file config20.xml to the local
user application data directory. This file contains the complete configuration of SAP Disclosure Management on
the client machine, including the connected data sources.
To enable quick access to data sources for all users, the IT administrator can preconfigure config20.xml with
the required data sources and copy it to each individual machine or store it on a file server. The latter solution is
useful in a centralized environment.
The maintenance of access authorization to data sources is restricted.
Data sources can be locked so that users cannot edit or delete data sources. For more information, see
Configuring File for Data Source Lock [page 48].
4.4.1.1 Configuring File for Data Source Lock
Prerequisites
You enter the lock directly into the configuration file.
Procedure
1. Navigate to [user folder]\cundus AG\cundusBIPublisher.

2. Open the config20.xml file.
3. Locate the data source you want to lock and then locate the following conding within it: <Locked>0</
Locked>.
4. To lock the datat source, change 0 to 1.
5. Repeat step 3 and 4 for each data source you want to lock.
6. Click File Save to save your changes.
4.4.2 Testing the Installation
When SAP Disclosure Management is successfully installed, test the COM-add-ins in the Microsoft Office
applications.

Note
For validation purposes, it is sufficient to test one application only. It may be necessary to change the same
settings in every application.
This section comprises the following tasks:
● Starting Disclosure Management in a Microsoft Office Application [page 49]

● Activating COM-Add-Ins in Microsoft Office Applications [page 49]
4.4.2.1 Starting Disclosure Management in a Microsoft

Office Application
Procedure
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 a ribbon or menu item does not appear, activate the COM-add-in in the application. For more information,
see Activating COM-Add-Ins in Microsoft Office Applications [page 49].
2. On the Disclosure Management ribbon or menu, click Start.
The system adds additional options to the ribbon or menu.
4.4.2.2 Activating COM-Add-Ins in Microsoft Office

Applications
Prerequisites
Execute the following steps for for Microsoft Word, Microsoft Excel and Microsoft Powerpoint.
Procedure
1. Start the Microsoft Office application.
2. Click File Options .

3. In the Options dialog box, click Add-Ins.
4. Click COM-Add-Ins from the list and click Go.
5. In the COM-add-ins dialog box, select DisclosureManagementConnector and click OK to apply your changes.

Next Steps
Note
Ensure that the macro security settings are configured correctly. For more information, see Authorization
Requirements and Security Settings [page 45].
4.5 Additional Information
4.5.1 Uninstalling SAP Disclosure Management from Client
Procedure
1. To remove SAP Disclosure Management from the client, use one of the following procedures:
○ In the Windows control panel, use the Remove Program function to uninstall SAP Disclosure
Management.
○ Uninstall the application by using Setup.exe:
1. Open the SAP Disclosure Management installation folder.
2. Double-click the setup.exe file.
3. Click Remove and then OK.
4. Click OK again.
2. The wizard uninstalls the application.
Results
When uninstalling the program, the file is not deleted, and can be reused for subsequent installations.

Management BW Connector
5.1 Preparation of SAP Disclosure Management BW

Connector Installation
This section provides information about the following tasks:
● Configuration [page 51]

● Authorizations [page 55]
5.1.2 Configuration
On the SAP BW server, you can use transaction SICF to deactivate the following objects:
● /sap/bc/soap/rfc
● /sap/bc/soap/wsdl11
Note
You have to create and configure every single Web service manually using transaction SOAMANAGER, so do
not activate ICF node /sap/bc/soap/rfc or /sap/bc/soap/wsdl11. Activating this node 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 52]

Installation of SAP Disclosure Management BW Connector PUBLIC 51
5.1.3 Enabling Web Services
Note
To prevent disconnection from SAP BW, follow the instructions in SAP Note 1811818. Before you start the
configuration steps, apply all available ABAP support packages for the SAP Disclosure Management BW
connector. To ensure error-free operation, apply all available ABAP support packages as soon as you have
applied the installation package or upgraded the exchange package.
SAP Disclosure Management supports the following procedure for enabling Web services:
Establishing and Connecting Single Web Services Manually [page 52]
Note
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 .
5.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.

52 PUBLIC Installation of SAP Disclosure Management BW Connector
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 53].
For more information about SOA Manager, see SAP Help Portal at 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 53].
Results
In transaction SICF, the Web services are displayed under /sap/bc/srt/rfc/cundus/* .
5.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
5.1.4 Authorizations
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 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:
5.2 Installing SAP Disclosure Management BW Connector

The software is delivered as an ABAP add-on installation file. For a description on how to install add-ons, see
Installing and Upgrading Add-Ons and SAP Note 1566421.

5.3 Post-Installation of SAP Disclosure Management BW
Connector
The post-installation of the SAP Disclosure Management BW connector includes the following topics:
● Assigning Web Service Authorizations [page 56]

● Assigning Authorizations for Briefing Book Administrator [page 56]
● Administration Tasks [page 57]
5.3.1 Assigning Web Service Authorizations

To use SAP Disclosure Management, you need authorization 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 at help.sap.com.
5.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, have to be assigned to the authorization object DCUBIPAUH in the SAP Disclosure Management BW
connector.

5.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 57]
5.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.

6 Business Content Packages for SAP
Disclosure Management (SAP DM)
SAP DM business content packages are usually installed by uploading a list of chapter content documents to the
SAP Disclosure Management server. In addition, follow the steps described in the respective individual scenario,
business content, or starter kit guide.
Where business content packages consist mainly of Excel or Word templates, you can simplify the update to a
new business content version by replacing not the whole list of templates throughout the system but only those
that actually change. Where applicable, SAP provides information about which templates have been changed as
part of the respective legal change or release note. An example regarding the business content for Solvency II
taxonomy 1.5.2.b can be found in SAP note 2131972 .

58 PUBLIC Business Content Packages for SAP Disclosure Management (SAP DM)
Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does
not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency
(see: http://help.sap.com/disclaimer).

Important Disclaimers and Legal Information PUBLIC 59
go.sap.com/registration/
contact.html
© 2016 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 http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.

dm101 Install en

Uploaded by

Copyright:

Available Formats

dm101 Install en

Uploaded by

Document Information

Original Title

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

dm101 Install en

Uploaded by

Copyright:

Available Formats

PUBLIC

SAP Disclosure Management

Installation and Upgrade Guide

2 Installation of SAP Disclosure Management Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

4 Installation of SAP Disclosure Management Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Installation and Upgrade Guide

5 Installation of SAP Disclosure Management BW Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Installation and Upgrade Guide

The target groups for this guide are the following:

Installation and Upgrade Guide

1.1 Hardware and Software Requirements in SAP Disclosure

Support Package Stacks

1.2 SAP Notes for the Installation

Installation and Upgrade Guide

984200 You cannot change DEVICE_CLASS Using REQUEST_DEVICE_CLASS

1318499 Transportability of Web Service Transport of Web service configurations

2365878 Insufficient read access to certificates' After an update to or new installation of

2394506 Planned Discontinuation of WebDAV WebDAV functionality is switched off by

Installation and Upgrade Guide

● Each individual software component version

● Get information about initial installation and update options.

SAP DISCLOSURE MGMT. 10.1 Support Packages and Patches

DISCLOSURE MGM XBRL ADD-IN 1.0 Support Packages and Patches

Installation and Upgrade Guide

Description Internet Address Title

Application Help help.sap.com User help for SAP Disclosure

General Quick Links

Description Internet Address

SAP Notes https://support.sap.com/notes

Released platforms https://support.sap.com/platforms

Installation and Upgrade Guide

2.1 Preparation of SAP Disclosure Management Server

Configuration of Microsoft IIS 7.0 Web Server [page 9]

2.1.1 Software and Hardware Requirements

2.1.2 Configuration of Microsoft IIS 7.0 Web Server

Enabling Static Content [page 10]

Installation and Upgrade Guide

1. Start the Server Manager.

○ Static Content (Installed)

2.1.2.2 Enabling HTTP Activation

To enable HTTP activation, follow the steps below.

Installation and Upgrade Guide

1. Start the Microsoft IIS Manager.

2.2 How to Perform an Initial Installation of SAP Disclosure

Installation and Upgrade Guide

Installation and Upgrade Guide

Installation and Upgrade Guide

Installation and Upgrade Guide

Installation and Upgrade Guide

Installation and Upgrade Guide

● Creates and updates the following:

Update of Server Installations

Installation and Upgrade Guide

2.2.1 How to Use the Repair Function During Installation of the

1. Start the setup if you have administrative rights.

2.2.2 Configuration After Server Installation

Installation and Upgrade Guide

○ Component protocol can be http or https depending on your configuration.

Installation and Upgrade Guide

storeName Specifies the name of No My http://msdn.micro

storeLocation The location of the No Local Machine http://msdn.micro

x509FindTypeDef Defines the type of X. No FindBySubjectDistin http://msdn.micro