SAP Disclosure Management 10.0 - Installation and Upgrade Guide

SAP Disclosure ManagementDocument Version: 10.0 SP07 - 2013-11-14

Installation and Upgrade Guide

Table of Contents1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1 SAP Notes for the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 Information Available in SAP Service Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Installation of SAP Disclosure Management Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1 Preparation of SAP Disclosure Management Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.1.1 Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1.2 Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1.3 Configuring IIS 6.0 on 64-bit Windows Server OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.1.4 Configuration of Microsoft IIS 7.0 Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.2 Installing SAP Disclosure Management Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.3 Post-Installation of SAP Disclosure Management Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.3.1 Hypertext Transfer Protocol Secure (HTTPS) for SAP Disclosure Management. . . . . . . . . . . . 112.3.2 Testing Server Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3.3 Starting the Task Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3.4 Activating Detailed Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.3.5 Configuring Virtual SMTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.3.6 Configuring Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.3.7 Uploading Configuration File for Data Source Connections. . . . . . . . . . . . . . . . . . . . . . . . . . 182.3.8 Using WebDAV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3 Installation of SAP Disclosure Management Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.1 Preparation of SAP Disclosure Management Client Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.1.1 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.1.2 Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.1.3 Configuration Requirements for SAP NetWeaver BW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.1.4 Authorization Requirements and Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213.1.5 Upgrading Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.2 Installing SAP Disclosure Management Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223.3 Post-Installation of SAP Disclosure Management Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.3.1 Configuring Data Source Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.3.2 Testing the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

3.4 Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.4.1 Uninstalling SAP Disclosure Management from Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

4 Installation of SAP Disclosure Management BW Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.1 Preparation of SAP Disclosure Management BW Connector Installation. . . . . . . . . . . . . . . . . . . . . . . . 25

4.1.1 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254.1.2 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.1.3 Enable Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2 2013 SAP AG or an SAP affiliate company. All rights reserved.Installation and Upgrade Guide

Table of Contents

4.1.4 Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294.2 Installing SAP Disclosure Management BW Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294.3 Post-Installation of SAP Disclosure Management BW Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

4.3.1 Activating ICF Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.3.2 Assigning Web Service Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .304.3.3 Assigning Authorizations for Briefing Book Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . 304.3.4 Administration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Installation and Upgrade GuideTable of Contents 2013 SAP AG or an SAP affiliate company. All rights reserved. 3

1 IntroductionSAP Disclosure Management comprises a server and client component as well a BW connector. This guide provides information on 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 which allows easy access to SAP Disclosure Management features.The SAP Disclosure Management BW connector is used to extract data from a SAP BW system.

NoteThe BW connector uses standard SAP NetWeaver BW applications. The applications use the SAP ABAP environment and objects, Business Server Pages (BSP), JavaScript, HTML and Cascading Style Sheets (CSS).

The following figure displays the system landscape and the dependencies between the components:

The target groups for this guide are the following: Consultants Technical consultants IT administrators


Introduction

1.1 SAP Notes for the InstallationYou must 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 in the SAP Service Marketplace at the Internet address:service.sap.com/notes

SAP Note Number Title Description1615026 Installation SAP Disclosure

Management 10.0 SP1Information needed before executing the installation

1566421 Installing DISCMLG on SAP NetWeaver 7.0 (BI 7.1)

Description for installing add-on for SAP NetWeaver

1594335 DM 10.0 SP00 Patch Installation Procedures

Description on how to install the SAP Disclosure Management patch

984200 You cannot change DEVICE_CLASS Using REQUEST_DEVICE_CLASS parameter in existing session

1633768 Advice for Installation of SAP Disclosure Management 10.1

Preventing problems with text and formular variables of BW queries

1318499 Transportability of Web Service Transport of web service configurations no longer supported due to security and connectivity issues

1.2 Information Available in SAP Service MarketplaceInformation on the following areas is available in the SAP Service Marketplace.

Documentation

Description Internet Adress TitleApplication Help help.sap.com User help for SAP Disclosure

Management

Installation and Upgrade GuideIntroduction 2013 SAP AG or an SAP affiliate company. All rights reserved. 5

General Quick Links

Description Internet Address TitleSAP Notes service.sap.com/notes -Released platforms service.sap.com/platforms -Security service.sap.com/security -


Introduction

2 Installation of SAP Disclosure Management Server

2.1 Preparation of SAP Disclosure Management Server InstallationTo install the server correctly, check if the following prerequisites are met:

Software Requirements [page 7]Configuration of Microsoft IIS 7.0 Web Server [page 8]

2.1.1 Hardware Requirements

The hardware requirements for the server component are the following: CPU: quad core processor (32-/64-bit) with 2 GHz+ 4 GB random-access memory 20 GB hard disk drive (HDD) (excluding data base)The hardware requirements for the server component when using the COREP scenario are the following:

CPU: quad core processor (32-/64-bit) with 2 GHz+ 32 GB random-access memory 20 GB hard disk drive (HDD) (excluding data base)

2.1.2 Software RequirementsThe following components are required for installing and running the SAP Disclosure Management server: Microsoft Windows Server 2003, 2008 or 2008 R2 Microsoft .NET framework 4.0 Microsoft IIS 6 or higher

NoteIf you use Microsoft IIS 7, you have to carry out additional configuration tasks. For more information, see Configuration of Microsoft IIS 7.0 Web Server [page 8].

SAP Disclosure Management supports the following relational database management systems (RDBMS): Microsoft SQL Server 2005 Microsoft SQL Server 2008 Microsoft SQL Server 2008 R2

Installation and Upgrade GuideInstallation of SAP Disclosure Management Server 2013 SAP AG or an SAP affiliate company. All rights reserved. 7

NoteYou need administrator rights to carry out the installation. Windows and web server configuration may be necessary. The prerequisites are documented in the Microsoft guides.

2.1.3 Configuring IIS 6.0 on 64-bit Windows Server OSTo run IIS 6.0 on a 64-bit Windows Server 2003, carry out the following steps:1. Enable IIS 6.0 to run 32-bit application on 64-bit Windows. Proceed as follows:

a. Open a command prompt and navigate to the following directory: %systemdrive%\Inetpub\AdminScripts.

b. Enter the following command: cscript.exe.adsutil.vbs set W3SVC/AppPools/Enable32BitApOnWin64 true.

c. Choose ENTER.2. Register ASP.NET 2.0 32-bit.

a. Open a command prompt and navigate to the following directory: %sysemroot%\Microsoft.NET\Framework\v2.0.50727\.

b. Enter the following command: aspnet_regiis -i.c. Choose ENTER.

3. Enable ASP.NET 32-bit.a. Open the IIS Manager Console.b. Navigate to Web Service Extensions.c. Set status for the ASP.NET v2.0.50727 (32-bit) entry to Allowed.

2.1.4 Configuration of Microsoft IIS 7.0 Web ServerTo configure Microsoft IIS 7.0 web server, carry out the following steps: Enabling Static Content [page 8] Switching IIS 7.0 to 32 bit [page 9]

2.1.4.1 Enabling Static Content1. 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:


Installation of SAP Disclosure Management Server

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.4.2 Switching IIS 7.0 to 32 bit1. 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 Installing SAP Disclosure Management ServerMake sure that the port you use is not owned by another web application. If the port is used by the default web application, stop this application.With SQL server version 2008 and earlier, you need to verify that the database authentication to be used in the setup is the same as the one in the security settings of the SQL server.

NoteIf you update SAP Disclosure Management from a previous version, create a backup of the database before starting the installation process. Use the standard tools from Microsoft SQL server to create the backup.

To install the server, proceed as follows:1. Download the installation file from the SAP AG customer site.2. Unzip the file.3. Double-click the installer package to start the installation wizard.4. In the InstallShield Wizard dialog box, click Next.5. Enter the database server and click Browse to navigate to the required server.6. Select one of the following options for connecting to the database:

Windows authentication to connect to the server with the same username and password used for access to the Windows system.

Server authentication to enter an existing login ID and the related password.7. Enter the name of the database catalog in which the metadata of the database objects is to be stored or click

Browse to navigate to the required catalog.8. Click Next.


9. Select one of the following connection types for the SQL server and SAP Disclosure Management server: Windows authentication

The technical user to be created is identical to the NT user. Server authentication

The technical user to be created can be different from the SQL user.Enter an existing Login ID and Password.

10. Enter the administrator username and password.11. Re-enter the password for password confirmation purposes.12. Click Next and confirm the information on the web resources displayed in the dialog box.13. Enter the following information:

Name of the SAP Disclosure Management web site TCP-IP address of the web site TCP Port Description Physical directory of the web site. Click Browse to navigate to the directory in which the SAP Disclosure

Management web site is to be stored.14. Click Next, then Install to start the installation process.15. Click Finish when the SAP Disclosure Management server has been successfully installed.The installation wizard applies the following changes to the system during the installation process: Creates and updates the following:

Database tablesroleER database roleSchemes linked to the roleER roleDatabase user (if defined) linked to the roleER roleSAP Disclosure Management user (if defined)Default contents for SAP Disclosure Management within the databaseIIS web site

Copies the runtime information to the physical directory of the IIS web site. Registers the aspnet_isap.dll for the web site in order to activate ASP.NET MVC.

2.3 Post-Installation of SAP Disclosure Management Server

The post-installation for the server comprises the following issues: Testing Server Installation [page 16] Activating Detailed Error Messages [page 17] Configuring Virtual SMTP Server [page 17] Configuring Server [page 17] Uploading Configuration File for Data Source Connections [page 18] Using WebDAV [page 18]



2.3.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.

ExampleconnectionString="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.

ExampleconnectionString="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).

NoteSupported 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 ServiceThe 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 withNetTcp. 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 andclients (Task Engine and SAP DM server). To do so, add the following entry to csfServices:

Table 1: ParametersParameter Description Mandatory Default Setting Reference to

Values

storeName Specifies the name of the X.509 certificate store to open

No My http://msdn.microsoft.com/en-us/library/system.security.cryptography.x509certificates.storename.aspx StoreName Enumeration

storeLocation The location of the certificate store the client uses to obtain the client certificate

No Local Machine http://msdn.microsoft.com/en-us/library/system.security.cryptography.x509certificates.storelocation.aspxStoreLocation Enumeration



Parameter Description Mandatory Default Setting Reference to Values

x509FindTypeDefin

Defines the type of X.509 search to be executed

No FindBySubjectDistinguishedName

http://msdn.microsoft.com/de-de/library/system.security.cryptography.x509certificates.x509findtype%28v=vs.85%29.aspxX509FindType-Enumeration

findValue The value to search for in the X.509 certificate store

Yes Depends on X509FindType. Look at same reference.

Task Engine ServiceFollow the steps described in the section How to Configure the TaskEngine Service for HTTPS.

Configuring WebDAV for HTTPS support on 64-Bit systemsTo enable WebDAV for HTTPS support, you need to change the Web.config file as shown below:

2.3.1.1 How to Configure the TaskEngine Service for HTTPS

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 Certificates4. 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.

ExampleOnce 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

ExampleThe 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.



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


You have configured the task engine to use SSL with HTTP.Related InformationHow to: Configure a Port with an SSL CertificateSSL with Self-hosted WCF Service

2.3.2 Testing Server InstallationTo test the SAP Disclosure Management server connection, proceed as follows:1. Open an internet browser and enter URL: http://:/ 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.3.3 Starting the Task Engine You have installed SAP Disclosure Management 10 SP5.To start the service follow the steps below:1. Open Window Service Console Start Run Type services.msc .2. Select the service SAP Disclosure Management TaskEngine.



3. Choose Start in the context menu.You have started the task engine service.

2.3.4 Activating Detailed Error MessagesIf 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.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.3.5 Configuring Virtual SMTP ServerIf no SMTP server is installed, install and configure this server manually.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.3.6 Configuring ServerAfter installing the server, configure the server as follows: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, fill in the server name and the port number.c) Update the following information on every tab: e-mail, misc, licence, 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 18].

c) Upload the BIP_WordTableDef.doc file.d) Upload the BIP_WordTableTagging.xml file.

3. Register the render plug-ins:a) Navigate to Administration Plugins .b) Register all plug-ins needed to create reports.

4. Assign global permissions to the administration user.You can also create a new superuser including the following roles:

Standard-AdminStandard-ReadonlyStandard-EditorStandard-Manager

5. If you are working with XBRL reports, start validation service:a) On the server, go to the [InstallDir] directory.b) In the ValidationService folder, run the Install.bat file.c) Enter your domain user as the login ID and your password.

2.3.7 Uploading Configuration File for Data Source ConnectionsThe 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 22].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.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.3.8 Using WebDAVSAP Disclosure Management uses web-based distributed authoring and versioning (WebDAV) for accessing the server database and enabling distributed web authoring.



If you use WebDAV: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 in a dot; for example, chapter.3. You cannot create a chapter, report or period name with two or more consecutive dots in the name; for

example, period..1

2.3.8.1 Accessing Web Documents via WebDAV in Read-Only Mode1. Open a Microsoft Office application and click File Open .2. In the Open dialog box, enter http://:/Webdav in the File name box.3. Click Open.A read-only version of your selected file appears.

TipYou 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 TaxonomyEach subfolder contains subfolders for the report and its chapters.


3 Installation of SAP Disclosure Management Client

3.1 Preparation of SAP Disclosure Management Client InstallationThis section provides information on preparing the installation. The following topics are affected: Hardware Requirements [page 20] Software Requirements [page 20] Configuration Requirements for SAP NetWeaver BW [page 21] Authorization Requirements and Security Settings [page 21] Upgrading Client [page 21]

3.1.1 Hardware Requirements The hardware requirements for the client component are the following: Network-compatible machine Approximately 250 MB of disk space Monitor display resolution of at least 1024 x 768 pixel 1 GB random-access memory

3.1.2 Software RequirementsSAP Disclosure Management requires the installation of the following software: Windows 2000, Windows XP with service pack 2, Windows Vista or Windows 7 Microsoft .NET Framework 3.5 with service pack 1 for SAP Disclosure Management Client and Microsoft .NET

Framework 4.0 for SAP Disclosure Management Server Microsoft XML Parser (Windows XP standard component) One of the following Microsoft Office versions:

Microsoft Office 2003 (service pack 1 or higher, especially on Windows 2000) Microsoft Office 2007 (service pack 1 is necessary) Microsoft Office 2010 (32bit)

NoteOnly the 32-bit version of Microsoft Office 2010 is supported.

Microsoft Internet Explorer 8 and 9


Installation of SAP Disclosure Management Client

NoteMicrosoft Internet Explorer 7 is only supported for English and German.

3.1.3 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.

3.1.4 Authorization Requirements and Security Settings It is recommended to install the software for the local user rather than for all users. To do so, the person who executes the installation needs authorization to write registry entries and 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. The macro security settings for each Microsoft Office application must be changed in the trust center:

Click the Enable all macros radio button in the Macro Setting area. Select the Trust access to the VBA project object model checkbox in the Developer Macro Settings area.

To access the Microsoft Office application macro settings:1. Open the application and click File Options ,then click Trust Center in the navigation area.2. Click Trust Center Settings.3. In the navigation area, click Macro Settings.

3.1.5 Upgrading ClientSAP 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:1. Uninstall and remove the application completely from your machine.

For more information, see Uninstalling SAP Disclosure Management from Client [page 24]Uninstalling SAP Disclosure Management from Client [page 24].

2. Restart your machine.3. Install the new version of the client component.

Installation and Upgrade GuideInstallation of SAP Disclosure Management Client 2013 SAP AG or an SAP affiliate company. All rights reserved. 21

For more information, see Installing SAP Disclosure Management Client [page 22]Installing SAP Disclosure Management Client [page 22].

3.2 Installing SAP Disclosure Management ClientTo install the SAP Disclosure Management client, proceed as follows: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.8. When the SAP Disclosure Management client has been successfully installed, click Finish.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: \SAP\Disclosure Management Configuration file: \Application Data\cundus AG\cundusBIPublisher

3.3 Post-Installation of SAP Disclosure Management ClientThe post-installation of the client comprises the following tasks: Configuring Data Source Connections [page 22] Testing the Installation [page 23]

3.3.1 Configuring Data Source ConnectionsThe 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 23].

3.3.1.1 Configuring File for Data Source LockYou enter the lock directly into the configuration file.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: 0.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.

3.3.2 Testing the InstallationWhen SAP Disclosure Management is successfully installed, test the COM-add-ins in the Microsoft Office applications.

NoteFor 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 23] Activating COM-Add-Ins in Microsoft Office Applications [page 24]

3.3.2.1 Starting Disclosure Management in a Microsoft Office Application1. 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 24].

2. On the Disclosure Management ribbon or menu, click Start.The system adds additional options to the ribbon or menu.

Installation and Upgrade GuideInstallation of SAP Disclosure Management Client 2013 SAP AG or an SAP affiliate company. All rights reserved. 23

3.3.2.2 Activating COM-Add-Ins in Microsoft Office ApplicationsExecute the following steps for for Microsoft Word, Microsoft Excel and Microsoft Powerpoint.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.

NoteEnsure that the macro security settings are configured correctly. For more information, see Authorization Requirements and Security Settings [page 21].

3.4 Additional Information

3.4.1 Uninstalling SAP Disclosure Management from Client1. 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.When uninstalling the program, the file is not deleted, and can be reused for subsequent installations.



4 Installation of SAP Disclosure Management BW Connector4.1 Preparation of SAP Disclosure Management BW Connector InstallationThis section provides information about the following tasks: Software Requirements [page 25] Configuration [page 25] Authorizations [page 29]

4.1.1 Software Requirements The SAP Disclosure Management BW connector is compatible with the following SAP NetWeaver BW releases: SAP NetWeaver BW 7.0 SAP NetWeaver BW 7.3The BW connector is compatible with all existing SAP support packages after SAP NetWeaver BW 7.0 SP 19.

4.1.2 ConfigurationOn SAP BW server, use transaction SICF to activate the following objects:/sap/bw/sap/bw/mime/sap/bc/sap/bc/bsp//sap/bc/bsp/sap//sap/bc/bsp/sap/icm/sap/bc/bsp/sap/public/sap/bc/bsp/sap/public/bc/sap/bc/bsp/sap/public/graphics/sap/bc/bsp/sap/system/sap/public/sap/public/bc/sap/public/bc/ur

Installation and Upgrade GuideInstallation of SAP Disclosure Management BW Connector 2013 SAP AG or an SAP affiliate company. All rights reserved. 25

/sap/public/bsp/sap/htmlb/sap/public/bsp/sap/system/sap/public/bsp/sap/system_public/sap/public/bsp/sap/public/sap/public/bsp/sap/public/bc/sap/bc/soap/rfc

NoteIf you want to create and configure every web service manually using transaction SOAMANAGER, do not activate ICF node /sap/bc/soap/rfc. Activation of this node might result in a security issue. For further information see SAP Note 1394100.

Related InformationEnable Web Services [page 26]

4.1.3 Enable Web Services

NoteTo prevent disconnecting from SAP BW, follow the instructions in SAP Note 1811818. Before starting the configuration steps, apply all available ABAP support packages for SAP Disclosure Management BW connector. For an error-free operation, apply all available ABAP Support Packages immediately after applying the installation package or upgrade exchange package.

To enable web services, the following alternative procedures are technically enabled: Establishing and Connecting Web Services Manually [page 26]

You can create and connect each web service separately. This procedure is recommended by SAP. Activating ICF Node for RFC Calls [page 29]

You can activate the ICF node /sap/bc/soap/rfc. You can then use every RFC-enabled object as a web service.

CautionFor securtiy reasons, SAP does not recommend this procedure. It is recommended to establish the web services manually.

4.1.3.1 Establishing and Connecting Web Services ManuallyYou have administration rights on your machine.You establish web services and connect them to the virtual endpoints manually.


Installation of SAP Disclosure Management BW Connector

NoteYou have to establish the web services separately on every BW system which you want to communicate with a SAP Disclosure Management client. For more information, see SAPNote 1318499.

1. Go to transaction SOAMANAGER and establish the web services.For a table of all web services, see Web Services and Virtual Endpoints [page 27].For more information on SOA Manager, refer to the SAP Help Portal at the following site: help.sap.com.

2. Establish the binding between each web service and the corresponding virtual endpoint in package /CUNDUS/BIPUBLISHER.For a table of all web services and the virtual endpoints, see Web Services and Virtual Endpoints [page 27].

In transaction SICF the web services are displayed under //default_host/sap/bc/srt/rfc/cundus/* .

4.1.3.2 Web Services and Virtual Endpoints

Web Service Virtual Endpoint

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

4.1.3.3 Activating ICF Node for RFC CallsTo enable all RFC objects as web services, proceed as follows:1. On the BW server, use transaction SICF.2. Activate the /default_host/sap/bc/soap/rfc object .

This procedure is technically enabled but for security reasons SAP recommends that the web services are established manually. For more information, see Establishing and Connecting Web Services Manually [page 26].

4.1.4 AuthorizationsYou need administration rights on both the SAP BW server and the client machine that is used for validation purposes.

4.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.

4.3 Post-Installation of SAP Disclosure Management BW Connector The post-installation of the SAP Disclosure Management BW connector includes the following topics: Activating ICF Node [page 30] Assigning Web Service Authorizations [page 30] Assigning Authorizations for Briefing Book Administrator [page 30] Administration Tasks [page 30]


4.3.1 Activating ICF Node When the transport files have been installed, activate the following ICF node:/default_host/sa/bc/bsp/cundus/BODM

4.3.2 Assigning Web Service AuthorizationsTo use SAP Disclosure Management, you need the authorization for Remote Function Call (RFC) destinations.To enable RFC, choose one of the following options: Assign the corresponding access right directly to the user. In case the situation requires a more detailed authorization situation, assign the user to the function group /

CUNDUS/*

NoteMake sure, that every user has the appropriate rights to execute the function modules.

For more information on RFC Authorization, refer to the SAP Help Portal at the following site: help.sap.com.

4.3.3 Assigning Authorizations for Briefing Book AdministratorUsers 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.

4.3.4 Administration TasksThis section provides information on administration tasks you execute after the SAP Disclosure Management BW connector has been activated: Determining Default Host and Port [page 30] Displaying List of Web Services [page 31]

4.3.4.1 Determining Default Host and PortTo find the default host name and port number of the SAP Disclosure Management BW connector, proceed as follows:



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.

4.3.4.2 Displaying List of Web Services1. Open an internet browser.2. Enter the following URL:

http://defaulthost:port/sap/bc/bsp/sap/WebServiceBrowser/search.html

A list of web services is displayed.


www.sap.com/contactsap

2013 SAP AG 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 AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group 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 AG in Germany and other countries.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

Installation and Upgrade GuideTable of Contents1 Introduction1.1 SAP Notes for the Installation1.2 Information Available in SAP Service Marketplace

2 Installation of SAP Disclosure Management Server2.1 Preparation of SAP Disclosure Management Server Installation2.1.1 Hardware Requirements2.1.2 Software Requirements2.1.3 Configuring IIS 6.0 on 64-bit Windows Server OS2.1.4 Configuration of Microsoft IIS 7.0 Web Server2.1.4.1 Enabling Static Content2.1.4.2 Switching IIS 7.0 to 32 bit

2.2 Installing SAP Disclosure Management Server2.3 Post-Installation of SAP Disclosure Management Server2.3.1 Hypertext Transfer Protocol Secure (HTTPS) for SAP Disclosure Management2.3.1.1 How to Configure the TaskEngine Service for HTTPS

2.3.2 Testing Server Installation2.3.3 Starting the Task Engine2.3.4 Activating Detailed Error Messages2.3.5 Configuring Virtual SMTP Server2.3.6 Configuring Server2.3.7 Uploading Configuration File for Data Source Connections2.3.8 Using WebDAV2.3.8.1 Accessing Web Documents via WebDAV in Read-Only Mode

3 Installation of SAP Disclosure Management Client3.1 Preparation of SAP Disclosure Management Client Installation3.1.1 Hardware Requirements3.1.2 Software Requirements3.1.3 Configuration Requirements for SAP NetWeaver BW3.1.4 Authorization Requirements and Security Settings3.1.5 Upgrading Client

3.2 Installing SAP Disclosure Management Client3.3 Post-Installation of SAP Disclosure Management Client3.3.1 Configuring Data Source Connections3.3.1.1 Configuring File for Data Source Lock

3.3.2 Testing the Installation3.3.2.1 Starting Disclosure Management in a Microsoft Office Application3.3.2.2 Activating COM-Add-Ins in Microsoft Office Applications

3.4 Additional Information3.4.1 Uninstalling SAP Disclosure Management from Client

4 Installation of SAP Disclosure Management BW Connector4.1 Preparation of SAP Disclosure Management BW Connector Installation4.1.1 Software Requirements4.1.2 Configuration4.1.3 Enable Web Services4.1.3.1 Establishing and Connecting Web Services Manually4.1.3.2 Web Services and Virtual Endpoints4.1.3.3 Activating ICF Node for RFC Calls

4.1.4 Authorizations

4.2 Installing SAP Disclosure Management BW Connector4.3 Post-Installation of SAP Disclosure Management BW Connector4.3.1 Activating ICF Node4.3.2 Assigning Web Service Authorizations4.3.3 Assigning Authorizations for Briefing Book Administrator4.3.4 Administration Tasks4.3.4.1 Determining Default Host and Port4.3.4.2 Displaying List of Web Services

Copyright and Trademarks

SAP Disclosure Management 10.0 - Installation and Upgrade Guide

Documents

sap disclosure management112

sap ag

sap notes

sap bw system

sap affiliate company

sap netweaver bw213

sap abap environment

testing server installation