SAP Business Intelligence Suite Patch 10.x Update Guide

Transcription

1 SAP BusinessObjects Business Intelligence Suite Document Version: 4.0 Support Package SAP Business Intelligence Suite Patch 10.x Update Guide

2 Table of Contents 1 Introduction About this Document Purpose Constraints Variables Planning SAP BusinessObjects Patches Patch platform support Patch language support Patch installation limitations and restrictions Planning your Patch installation Downloading Patches Installation scenarios Applying Patches to a system with multiple SAP BusinessObjects products Parallel update Updating web application components Saving web.xml file modifications Patch installation on Windows To install SAP BusinessObjects Patches for server components on Windows To install SAP BusinessObjects Patches for client components on Windows Silent installation on Windows To run a silent installation using a response file on Windows Silent installation parameters on Windows Uninstalling SAP BusinessObjects Patches on Windows To uninstall SAP BusinessObjects Patches on Windows Patch installation on UNIX To install the SAP BusinessObjects patch on UNIX Silent installation on UNIX To run a silent installation using a response file on UNIX Silent installation parameters on UNIX To uninstall SAP BusinessObjects Patches on UNIX SAP SE or an SAP affiliate company. All rights reserved. Table of Contents

3 1 Introduction 1.1 About this Document This guide is intended for the system administrator or IT professional who is responsible for the installation, deployment, and maintenance of SAP BusinessObjects Business Intelligence suite. Topics covered in this guide include: Patch installation on Windows Patch installation on UNIX Silent Patch installation Uninstalling Patches It is recommended that this guide be used in conjunction with the following Patch documentation: The Patch Release s and Fixed issues document which contains information about important issues, limitations, and work-arounds for the Patch release, as well as information about the defects addressed by the Patch Purpose This document is intended as a reference for use by system administrators when updating the BI suite with the most recent Patch. For the latest information, updates, and other information, visit the support site at service.sap.com/bosap-support Constraints This guide does not describe how to set up a host operating system, supported database, web application server, or web server. If you are planning to use a dedicated database, web application server, or web server, it must be installed and functioning before SAP BusinessObjects Business Intelligence platform can be installed. Refer to the vendor documentation for more information on installing or upgrading these components Variables The following variables are used throughout this guide. Variable <INSTALLDIR> Description The directory where the BI platform is installed. Introduction 2014 SAP SE or an SAP affiliate company. All rights reserved. 3

4 Variable Description On a Windows machine, the default directory is C: \Program Files (x86)\sap BusinessObjects\ SAP SE or an SAP affiliate company. All rights reserved. Introduction

5 2 Planning 2.1 SAP BusinessObjects Patches A separate Patch is available for each SAP BusinessObjects package, as outlined in the following table. Patch SAP BusinessObjects Business Intelligence platform Patch Description Use this Patch to update the BI platform installations. This Patch is also intended for SAP BusinessObjects Edge Business Intelligence (BI) SAP BusinessObjects Business Intelligence platform Client Tools Patch Use this Patch to update the BI platform Client Tools installations. Client tools include: Web Intelligence Rich Client Business View management tool Report Conversion tool Web services query tool Universe design tool Information design tool Translation management tool Data Federation administration tool Widgets for SAP BusinessObjects Business Intelligence platform Translation management tool Developer Components SAP BusinessObjects Business Intelligence platform Java SDK SAP BusinessObjects Business Intelligence platform.net SDK SAP BusinessObjects Business Intelligence platform Web Services Consumer SDK SAP Crystal Reports Java SDK SAP Crystal Reports 2011 Patch Use this Patch to update SAP Crystal Reports 2011 installations. If you are running SAP Crystal Reports 2011, see Patch installation limitations and restrictions. SAP Crystal Reports for Enterprise Patch Use this Patch to update SAP Crystal Reports for Enterprise installations. SAP Crystal Server 2011 Patch Use this Patch to update SAP Crystal Server 2011 installations. Planning 2014 SAP SE or an SAP affiliate company. All rights reserved. 5

6 Patch SAP Crystal Server 2011 Client Patch SAP BusinessObjects Live Office Patch SAP Crystal Presentation Design Patch SAP BusinessObjects Dashboard Design Patch SAP BusinessObjects Explorer Patch SAP BusinessObjects Integration Option for Microsoft SharePoint Patch Description Use this Patch to update SAP Crystal Server 2011 Client installations. Use this Patch to update SAP BusinessObjects Live Office installations. Use this Patch to update SAP Crystal Presentation Design installations. Use this Patch to update SAP BusinessObjects Dashboard Design installations. Use this Patch to update SAP BusinessObjects Explorer installations. Use this Patch to update SAP BusinessObjects Integration Option for Microsoft SharePoint installations. 2.2 Patch platform support The following table shows the platform support for each Patch. Support Package Windows AIX Solaris Linux SAP BusinessObjects Business Intelligence platform SAP BusinessObjects Business Intelligence platform Client Tools SAP Crystal Reports 2011 SAP Crystal Server 2011 SAP Crystal Server 2011 Client Patch SAP Crystal Reports for Enterprise SAP BusinessObjects Live Office SAP Crystal Presentation Design SAP BusinessObjects Dashboard Design SAP BusinessObjects Explorer SAP SE or an SAP affiliate company. All rights reserved. Planning

7 Support Package Windows AIX Solaris Linux SAP BusinessObjects Integration Option for Microsoft SharePoint Patch 2.3 Patch language support A Patch only contains string resources for English, and any string fix resolutions contained in the Patch will be displayed in English. Translations for string fixes are added to the next available Support Package containing the fix. 2.4 Patch installation limitations and restrictions The following limitations and restrictions apply to Patch installation: Patches are maintenance installations, not complete product installations. An SAP BusinessObjects product must be installed in order to install a Patch. A Patch only updates files that are already installed. For example, if you previously performed a custom installation, the Patch will only update the subset of files that were installed during the original, custom installation. Patches can only be installed in their entirety. You cannot install a subset of Patch updates. It is required that all components in a SAP BusinessObjects system be at the same maintenance level. For example, SAP BusinessObjects server, client, and web components must be at the same maintenance level. If you update one component of your SAP BusinessObjects system, you must also update the other components. If you uninstall a Patch for one component in your system, you must uninstall the same Patch for the other components. If you install a new SAP BusinessObjects product or component to your system after Patch installation, you must re-apply the Patch to the machine where you installed the new product or component to ensure that all SAP BusinessObjects products and components are at the same Patch level. Patches are designed for a specific maintenance package level. For example, a Patch designed for Support Package 5 cannot be installed if your system is at only the Support Package 4 level. You must upgrade to the Support Package 5 level before installing that Patch. Patches designed for the same Support Package level are cumulative. Therefore, it is unnecessary to install an earlier Patch from a particular Support Package level on top of a later Patch at that same level. The Patch installation program can automatically redeploy web application components to the web application server only if the bundled Tomcat web server was used, and those components were deployed automatically at initial installation time. If the web application components were initially deployed using the WDeploy tool, you must use WDeploy to redeploy those components after installing the Patch. For more information see Updating web application components. If you are performing a silent installation using a response file, you must create the response file with the setup.exe or install.sh file from the target Patch installation package. Response files generated for a Planning 2014 SAP SE or an SAP affiliate company. All rights reserved. 7

8 Patch installation are specific to that Patch, and cannot be shared between full installations and update installations, or between Support Package installations and Patch installations. 2.5 Planning your Patch installation Before applying a Patch to your system the following planning steps are recommended: Back up your existing BI suite deployment. For details on backing up your system see the SAP BusinessObjects Business Intelligence Platform Administrator Guide. We recommend that you back up the BOE140 and BOE140_Audit databases, as well as the contents of the dfo folder. The default location of this folder is <install dir>\sap BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\dfo. Review the Patch Release s and Fixed Issues document to determine if defects addressed by the Patch are relevant to your SAP BusinessObjects installation, and for important issues, limitations, and work-arounds for the Patch release. Identify all SAP BusinessObjects products and components that require updates. For the SAP BusinessObjects 4.0 release, Patches are provided for each product that has its own installer. Refer to SAP BusinessObjects Patches to identify the Patches required for your upgrade. On windows, installed patches can be determined from the Windows Add/Remove Programs list. On Unix, installed patches can be determined by running <install path> \modifyorremoveproduct.sh It is required that all SAP BusinessObjects products and components be at the same support package and patch level. If you have a distributed installation or you are running multiple SAP BusinessObjects products, ensure that all products and distributed components are updated. This includes BI platform servers, client tools, web components, and other SAP BusinessObjects products such as SAP Crystal Reports and Live Office. If you have SAP BusinessObjects web application components installed, ensure that you have defined an update path for these components. The update path depends on how you initially deployed the web application components. For more information, see Updating web application components. Before you begin, review Patch installation limitations and restrictions. Review Patch installation scenarios. The scenarios may help you plan your upgrade. Before you begin, gather all required documentation. Depending on your upgrade, additional documentation such as the SAP BusinessObjects Business Intelligence Platform Installation Guide may be required. 2.6 Downloading Patches SAP BusinessObjects Patches are available for download from the SAP Support Portal: patches SAP SE or an SAP affiliate company. All rights reserved. Planning

9 3 Installation scenarios This topic describes common Patch installation scenarios that may help you plan your Patch installation. 3.1 Applying Patches to a system with multiple SAP BusinessObjects products Due to product interdependencies, it is required that all SAP BusinessObjects products be at the same maintenance level. For example, if you want to apply a patch to SAP Crystal Reports on a system where you run SAP Crystal Reports, Live Office, and the BI platform, you must apply patches for all three products so that all products are running at the same patch level. In this scenario, you must apply a SAP Crystal Reports patch, a Live Office patch, and an BI platform patch. 3.2 Parallel update If you are installing an update in a distributed BI platform deployment, where servers and components are installed across multiple machines, you need to apply the update to those machines in a specific order for the system to update properly. You must wait for all machines updating in parallel to finish before proceeding to the next step. Do not restart a machine until all machines updating in parallel have finished updating, even if a restart is requested by the installation program. There must be at least one CMS machine available to the non-cms machines that are updating. All CMS machines that are running when you begin updating, and any additional CMS machines that start during the update, must be available for the entire duration of the update. You should not be running any additional installation, maintenance, or server administration workflows that could cause the CMS machines to restart while the update is taking place. Update the machines in your deployment in the following order: 1. Update, in parallel, all CMS host machines. 2. Update, in parallel, all non-cms host machines. 3. Once all the updates have finished running, restart all CMS machines in your cluster. Installation scenarios 2014 SAP SE or an SAP affiliate company. All rights reserved. 9

10 This process needs to be repeated for every product that is installed on the machines in the deployment. For example, BI platform, Explorer and Client Tools. If a product is only installed on non-cms machines, step 1 can be skipped. 3.3 Updating web application components How you apply an update to the BI platform web applications depends on whether you are using the bundled Tomcat web application server: If you are using the bundled Tomcat web application server, the BI platform WAR files are automatically updated when you run the update installation program. No additional steps are required. If you are not using the bundled Tomcat web application server, use the update installation program to install the new WAR files to <INSTALLDIR>/enterprise_xi40/warfiles/webapps, then use WDeploy to deploy the WAR files to your web application server. If you are applying multiple updates, install all updates first to obtain a final set of WAR files that can be redeployed at the same time. See SAP BusinessObjects Business Intelligence Platform Web Application Deployment Guide for instructions on using WDeploy. You must update all BI platform WAR files when you are updating your deployment. All BI suite components, including web applications, must have the same version number. 3.4 Saving web.xml file modifications When a patch is installed, the web.xml files for SAP BusinessObjects web applications that have been deployed to a web application server are overwritten. This means that any customizations that you've made by changing the web.xml files on the web application server are lost after applying a Patch update. If you modified a web.xml file for a web application and do not want to lose your modifications, you must make the modifications in the BI platform installation directory. Changes made to the configuration files in the BI platform installation directory will be retained when patching. On Windows systems, this directory is <INSTALLDIR>\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps. On UNIX systems, this directory is <INSTALLDIR>/sap_bobj/enterprise_xi40/ warfiles/webapps. Then, after you've applied the patch, rebuild the affected.war files and redeploy the.war files to the web application server SAP SE or an SAP affiliate company. All rights reserved. Installation scenarios

11 4 Patch installation on Windows You must have Administrator privileges on your Windows system to run a SAP BusinessObjects Patch installation. In order to free resources on the machine on which you are installing this patch, it is recommended that you use the Central Management Console (CMC) to stop all of the BI platform servers on the machine before installing the patch, with the following exceptions: Server Intelligence Agent (SIA) Central Management Server (CMS) Input and Output File Repository Servers (FRS) CMS system database These services and servers must be running for the installation to proceed. If you have modified web.xml files for web applications, see Saving web.xml file modifications before you apply a patch. If you are updating a product that contains server components, the installation program prompts you for information for your deployment's Central Management Server (CMS). This is required to update content that is stored in the CMS database, such as localized strings for server properties. 4.1 To install SAP BusinessObjects Patches for server components on Windows Context This procedure is used to install patches that update the SAP BusinessObjects Business Intelligence platform server package running on Windows. This package updates BI platform server components. Procedure 1. Launch the installation by running setup.exe 2. Choose a language for the installation program to use during the installation process, and click OK. The installation program checks your system to ensure the proper prerequisites are in place 3. Click Next. 4. In the Welcome dialog box, click Next to proceed. Patch installation on Windows 2014 SAP SE or an SAP affiliate company. All rights reserved. 11

12 5. In the License Agreement dialog box, review the contents of the End User License Agreement, and click Next to proceed if you agree to the terms. If the patch includes server components, the CMS dialog box is displayed. 6. Type the Hostname, Port Number, and Administrator Password for your deployment's CMS, and click Next to continue. 7. In the Start Installation dialog box, click Next to begin the installation. The update will install. If web applications are updated as part of the patch, depending on the options you chose when you originally installed SAP BusinessObjects BI Platform a post installation dialog box may appear with additional instructions for redeploying your.war files. 8. Click Finish. 4.2 To install SAP BusinessObjects Patches for client components on Windows Context This procedure is used to install Patches for SAP BusinessObjects client applications. This includes the following packages: SAP BusinessObjects Business Intelligence platform Client SAP BusinessObjects Business Intelligence platform Live Office SAP Crystal Reports for Enterprise SAP Crystal Reports 2011 SAP Crystal Server 2011 Client SAP Crystal Presentation Design SAP BusinessObjects Dashboard Design SAP BusinessObjects Integration Option for Microsoft SharePoint Procedure 1. Launch the installation by running setup.exe 2. Choose a language for the installation program to use during the installation process, and click OK. The installation program will perform a check to ensure the required prerequisites are in place. 3. Click Next. 4. In the Welcome dialog box, click Next. 5. In the License Agreement dialog box, review the contents of the End User License Agreement, and click Next to proceed if you agree to the terms SAP SE or an SAP affiliate company. All rights reserved. Patch installation on Windows

13 6. In the Start Installation dialog box, click Next to begin the installation. The Installation Progress dialog box appears. 4.3 Silent installation on Windows To run a silent installation using a response file on Windows Context Patches can be installed silently using a response file. Silent installation is particularly useful when you need to perform multiple installations or automate installations. To run a silent installation using a response file you must first create an.ini file using the installation program. Once you have created the.ini file, you can run a silent installation by running the setup.exe command and specifying the path to the.ini file. You must create the response file using the same installation program that will run it. You cannot re-use a response file from a previous release or from a Support Package. When creating a response file with the GUI installation program, passwords entered via the GUI are not written to the response file: Replace the starred entries (********) with your passwords before performing a silent installation. Procedure 1. Create an installation.ini file (a response file). a) Open a command line console. b) From the directory that contains the SAP BusinessObjects setup.exe file, run the setup.exe command with the write option (-w) specified: setup.exe -w <responsefilepath\filename.ini > where <filename.ini> is the name you have given to the response file and <responsefilepath> is the location where you want the file created. Patch installation on Windows 2014 SAP SE or an SAP affiliate company. All rights reserved. 13

14 If a file path is not specified, the file is stored in the directory that setup.exe is run from. The installation program must have write permissions on this directory. c) Press Enter to launch the installation program. d) Follow the on-screen instructions to enter your preferred installation settings until you reach the Start installation dialog box. e) Click Cancel to abort the installation setup. All parameters from the installation program, both user defined and default, are recorded in the.ini file which is saved to the directory you specified. 2. After editing the response file to replace any starred entries, you can run a silent installation using the.ini file by running setup.exe with the read option (-r). Results Log files for the install are stored at <install dir>\installdata\logs Silent installation parameters on Windows The following table lists parameters that are used for response file silent installation on Windows. It is recommended that you create response files using the SAP BusinessObjects setup program (setup.exe) as described in To run a silent installation using a response file on Windows. Parameter RemoteCMSname Description Specifies the name of the Central Management Server (CMS) remotecmsname="<servername>" remotecmsport Specifies the port used by the CMS remotecmsport="6400" remotecmsadminname remotecmspassword Must specifie the "administrator" account for the CMS. Specifies the password for the Administrator account for the CMS. remotecmspassword="<mypassword>" SAP SE or an SAP affiliate company. All rights reserved. Patch installation on Windows

15 4.4 Uninstalling SAP BusinessObjects Patches on Windows Patches can only be uninstalled one at a time, in the reverse order of installation. When uninstalling Patches, ensure that all of the products in your deployment are at the same version before using the system To uninstall SAP BusinessObjects Patches on Windows Procedure 1. In Windows, click Start, point to Settings, and then select Control Panel. 2. Double-click Add or Remove Programs. 3. Highlight the Patch entry in the list of programs and click Change/Remove. The Application Maintenance dialog box appears. 4. Select Remove and click Yes. 5. Wait while the appropriate files are removed and the necessary configuration is carried out. Click Finish. Next Steps If you have Dashboards installed on your system, you will need to take the following additional steps: 1. Modify the BI platform install to re-add "BI Workspace Services (Control Panel -> Add\Remove Programs -> SAP BusinessObjects BI platform 4.0 -> Uninstall/Change). 2. Using the Central Configuration Manager, shut down the Server Intelligence Agent. 3. Restore the following backups: BOE140 and BOE140_Audit databases The contents of the dfo folder. 4. Restart the host system. Patch installation on Windows 2014 SAP SE or an SAP affiliate company. All rights reserved. 15

16 5 Patch installation on UNIX In order to free resources on the machine on which you are installing this patch, it is recommended that you use the Central Management Console (CMC) to stop all of the BI platform servers on the machine before installing the patch, with the following exceptions: Server Intelligence Agent (SIA) Central Management Server (CMS) Input and Output File Repository Servers (FRS) CMS system database These services and servers must be running for the installation to proceed. If you have modified web.xml files for web applications, see Saving web.xml file modifications before you apply a Patch. If you are updating server components, the installation program prompts you for information for your deployment's Central Management Server (CMS). This is required to update content that is stored in the CMS database, such as localized strings for server properties. 5.1 To install the SAP BusinessObjects patch on UNIX Procedure 1. Launch the installation by running the following command from the patch installation source file location: setup.sh InstallDir=<INSTALLDIR> where <INSTALLDIR> is the installation directory of your SAP BusinessObjects product. 2. Verify the installation directory and press Enter to start the installation. The installation program will check to ensure the required prerequisites are in place. 3. Press Enter to continue. A Welcome screen will be displayed. 4. Press Enter to continue. The license agreement will be displayed. 5. Review the content of the License agreement and press Enter to agree and proceed. If the patch includes server components, you will be prompted for your CMS credentials. 6. Enter your CMS credentials and press Enter to start the installation. The progress indicator displays the status of the installation SAP SE or an SAP affiliate company. All rights reserved. Patch installation on UNIX

17 If web applications are updated as part of the patch, depending on the options you chose when you originally installed SAP BusinessObjects BI Platform a post installation screen may appear with additional instructions for redeploying your.war files. 7. Press Enter to complete the installation. To review details of the installation, you can view the contents of the installation log file located in INSTALLDIR/InstallData/logs/ 5.2 Silent installation on UNIX To run a silent installation using a response file on UNIX Context Patches can be installed silently using a response file. Silent installation is particularly useful when you need to quickly perform multiple installations or automate installations. To run a silent installation using a response file you must first create a response file. The following steps describe how to create a response file using the SAP BusinessObjects installation program. Once you have created the response file, you can run a silent installation by running the./setup.sh command and specifying the path to the response file. If you are performing a silent installation using a response file, you must create the response file with the setup.exe or setup.sh file from the target support package or patch installation package. Response files cannot be shared between support package installations and patch installations. When creating a response file with the GUI installation program, passwords entered via the GUI are not written to the response file: Replace the starred entries (********) with your passwords before performing a silent installation. Procedure 1. Create a response file. Patch installation on UNIX 2014 SAP SE or an SAP affiliate company. All rights reserved. 17

18 a) From the patch installation source file location, run the.setup.sh command with the write option (-w) specified:./setup.sh installdir=<installdir> -w <responsefilepath/filename.ini> where <INSTALLDIR> is the SAP BusinessObjects installation directory and <responsefilepath/ filename.ini> is the path and file name for the response file you are creating. b) Press Enter to launch the installation program. c) Follow the on-screen instructions to enter your preferred installation settings until you reach the Start installation dialog box of the setup program, the press Enter. The settings are recorded in the response file. 2. You can now run a response file installation by issuing./setup.sh command with the -r option specified:./setup.sh InstallDir=<INSTALLDIR> -r <responsefilepath/filename.ini > where <responsefilepath/filename.ini> is the path and name of the response file you created. 3. Press Enter to launch the installation Silent installation parameters on UNIX The following table lists parameters that are commonly used for response file silent installation on UNIX. It is recommended that you create a response files using./setup.sh and the -w parameter, as described in To run a silent installation using a response file on UNIX. Parameter RemoteCMSname Description Specifies the name of the Central Management Server (CMS) remotecmsname="<servername>" remotecmsport Specifies the port used by the CMS remotecmsport="6400" remotecmsadminname remotecmspassword Specifies the administrator account for the CMS. Specifies the password for the Administrator account for the CMS. remotecmspassword="<mypassword>" SAP SE or an SAP affiliate company. All rights reserved. Patch installation on UNIX

19 5.3 To uninstall SAP BusinessObjects Patches on UNIX Procedure 1. To uninstall a patch, execute the following command from the root directory of your SAP BusinessObjects installation:./modfiyorremoveproducts.sh The Add or Remove Programs dialog box is displayed. 2. Select the SAP BusinessObjects patch you want to remove and press Enter. You will be prompted for your Central Management Server credentials. 3. Enter your CMS credentials and press Enter. 4. Select Uninstall Product and press Enter. A confirmation dialog box is displayed. 5. Select Yes and press Enter. The uninstallation process begins. Patch installation on UNIX 2014 SAP SE or an SAP affiliate company. All rights reserved. 19

20 Important Disclaimers on Legal Aspects This document is for informational purposes only. Its content is subject to change without notice, and SAP does not warrant that it is error-free. SAP MAKES NO WARRANTIES, EXPRESS OR IMPLIED, OR OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. 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 specifically disclaims any liability with respect to this document and no contractual obligations or commitments are formed either directly or indirectly by this document. 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. Regarding link classification, see: help.sap.com/disclaimer SAP SE or an SAP affiliate company. All rights reserved. Important Disclaimers on Legal Aspects

21 Important Disclaimers on Legal Aspects 2014 SAP SE or an SAP affiliate company. All rights reserved. 21

22 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 index.epx for additional trademark information and notices.