SAP Crystal Server Document Version: 2011 Support Package SAP Crystal Server Installation Guide for Linux

Transcription

1 SAP Crystal Server Document Version: 2011 Support Package SAP Crystal Server Installation Guide for Linux

2 Content 1 Document History Introduction About this Document Purpose Integration Constraints Planning Upgrade support....8 Object types and feature requirements....8 Product co-existence Web application servers Web servers Database servers Preparation System requirements Account permissions Network permissions Preparing the CMS system or Auditing Data Store database Extra requirements for IBM DB Extra requirements for Sybase Set ulimit to unlimited Final checklist Installation To download the installation program To run an interactive installation To select an install type While the installation program runs When installation is complete To run a silent installation Command-line switch parameters Installation option parameters Post-Installation Launching the CMC SAP SE or an SAP affiliate company. All rights reserved. Content

3 6.2 Troubleshooting login issues Creating additional Adaptive Processing Servers Deploying web applications Post-install diagnostic checks Making changes to SAP Crystal Server To modify SAP Crystal Server...51 To repair SAP Crystal Server To remove SAP Crystal Server When the administrator account password is lost Content 2015 SAP SE or an SAP affiliate company. All rights reserved. 3

4 1 Document History Table 1: Version Date Description SAP Crystal Server 2011 Nov First release of this document SAP Crystal Server 2011 Feature Pack 3 SAP Crystal Server 2011 Support Package 12 May 2012 Updated information on supported Web application servers Updated information on supported Web servers New instructions on downloading the installation program New instructions on adding additional Adaptive Processing Servers (post installation) November 2015 Updated information about Tomcat SAP SE or an SAP affiliate company. All rights reserved. Document History

5 2 Introduction This document guides you through the installation of SAP Crystal Server. 2.1 About this Document The following documentation provides administrators with information, procedures, and options for the installation, removal, and modification of an SAP Crystal Server. Two versions of this guide exist: SAP Crystal Server Installation Guide for Unix: for use with Unix or Linux operating systems (this document). SAP Crystal Server Installation Guide for Windows: for use with Microsoft Windows operating systems (this document). SAP Crystal Server Installation Guide for Windows: for use with Microsoft Windows operating systems. SAP Crystal Server Installation Guide for Unix: for use with Unix or Linux operating systems. 2.2 Purpose This document is intended for system administrators installing SAP Crystal Server. For the latest information, patches, and other information, visit the SAP BusinessObjects support site: Integration SAP Crystal Server is a suite of enterprise-level business intelligence analysis and reporting systems. The suite will integrate into your existing network, database, authentication, security, and operating systems. For an overview of the technologies and architecture used in SAP Crystal Server, and how they can fit into your organization's existing infrastructure, read the SAP BusinessObjects Business Intelligence Platform Planning Guide. SAP Crystal Server is a variant of the BI platform so the recommendations here are applicable to both products. Introduction 2015 SAP SE or an SAP affiliate company. All rights reserved. 5

6 2.4 Constraints This guide does not describe how to set up a supported host operating system, database, web application, or web server. If you are planning to use a dedicated database, web application, or web server, it must be installed and functioning before attempting to install SAP Crystal Server SAP SE or an SAP affiliate company. All rights reserved. Introduction

7 3 Planning SAP Crystal Server can be installed on Windows or Linux platforms, with a combination of supported web servers, web application servers, database servers, and web technologies. You decide how the components that make up SAP Crystal Server will be deployed. A small development deployment might use the setup program's default options to install SAP Crystal Server, a database, and a web application server on a single computer system. A larger scale deployment might install individual server components on dedicated systems to host individual server functions over a network. For example: a dedicated host for a web application server; a dedicated host for the SAP Crystal Server core system; and a dedicated host for the database. Before installing: Review your systems to ensure they meet the basic requirements. For a detailed list of supported environments and hardware requirements, consult the Supported Platforms Guide available on the SAP Crystal Server support site at service.sap.com/bosap-support. This document includes specific version and patch-level requirements for web application servers, web browsers, databases, and operating systems. When setting up a deployment comprised of two or more hosts, ensure that the hosts can communicate with each other across the network. Decide whether to use the included DB2 database server. If you do not have a database server in place for use with SAP Crystal Server, the installation program can install and configure one for you. It is recommended that you evaluate your requirements against information from your database server vendor to determine which supported database would best suit your organization's requirements. An existing database must have database user accounts with the appropriate database privileges ready, and the appropriate drivers must be installed and verified as working. The setup program attempts to connect to, and initialize, the database as a part of the installation process. The installation program will only install a database on the local host. It cannot install across a network. Decide whether to use the included Tomcat web application server. If you do not have a web application server system to serve SAP Crystal Server web applications, the installation program can install and configure one for you. It is recommended that you evaluate your requirements against information from your web application server vendor to determine which supported web application server would best suit your organization's requirements. To use any other supported web application server, it must be installed, configured, enabled, and accessible before you install SAP Crystal Server. The installation program will only install Tomcat to the local machine. It cannot install to remote systems across a network. Decide which installation option to use. The installation program offers three installation options: 1. Full: install all available components, including a bundled web application server and database server. 2. Custom / Expand: select and install all or any of the available components. Planning 2015 SAP SE or an SAP affiliate company. All rights reserved. 7

8 3. Web Tier: install web applications on a dedicated web application server. You can use an previously installed web application server, or the bundled Tomcat web application server. Determine the location of the components to be installed. This includes the specific subnet, machines, database, security, or cluster systems to be used. For instructions on installing the Mobile BI add-on, see the SAP BusinessObjects Mobile Installation and Deployment Guide. 3.1 Upgrade support To upgrade to SAP Crystal Server 2011 Support Package 12, you must install the program, then migrate settings and content using the Upgrade management tool. For information on how to upgrade from a previous version, see the SAP Crystal Server Upgrade Guide. When the installation program detects a previously installed version of SAP Crystal Server, it presents the option to perform a side-by-side installation, which installs the new version, leaving the previously installed version intact. A system can host more than one version of SAP Crystal Server, although system performance may be degraded if both are running at once. New Features Tomcat 7.0 is now the default, bundled web application server. If you are updating a you existing setup that uses the bundled Tomcat 6.0 web application server to SAP Crystal Server 2011 with the update installation program, your system is automatically updated to Tomcat Object types and feature requirements Ensure that the machine on which you run the upgrade management tool has the SAP Crystal Server features that correspond to the object types that you want to upgrade. The following table lists the available object types and the features associated with them. Remember If a feature is not installed on the machine, the corresponding object type will not be upgraded. Table 2: Object type BI workspaces (Dashboards) Crystal reports Required feature BI workspace Services none SAP SE or an SAP affiliate company. All rights reserved. Planning

9 Object type Explorer Lifecycle management console (LifeCycle Manager) data Universes, connections Mobile Required feature none Platform Processing Services or Platform Scheduling Services Connectivity Processing Services CMS plugin for Moible Product co-existence Several SAP Crystal Server products can exist on the same host. For example, the Client Tools can be installed on a host running SAP Crystal Server server products, although it is recommended that SAP Crystal Server is installed before Client Tools. All SAP Crystal Server products installed at your organization must have the same patch level. For example, if your organization upgrades SAP Crystal Server products to a service pack or fix pack, all add-ons, Client Tools, and stand-alone products must also be upgraded. Similarly, if one product is downgraded, all other products should also be downgraded. To install add-on products, ensure that any required server components are present. A dependency check that identifies missing or outdated components is run by SAP BusinessObjects installation programs. If a dependency requirement is not met, the installation program identifies and suggests ways to meet the requirement. An add-on product which requires server components will not install until the appropriate server components are available. If a product included with Client Tools also comes with a dedicated stand-alone installation program, both can be installed on the same host. SAP Crystal Server cannot be installed on the same host as SAP BusinessObjects Business Intelligence platform. When installing SAP Crystal Server products, the user has the option to select a custom destination parent folder, into which the software is installed. Subsequent installations of other SAP Crystal Server products uses the same folder given for the original installation, and cannot be changed. If an SAP Crystal Server product is removed from a host, any remaining SAP Crystal Server product installation will be unaffected. Any component shared by the both installations will remain, and will only be removed when the last product that requires the shared component is removed. Add-on products with dependencies on other products should be removed before the product on which they depend. 3.2 Web application servers You can integrate SAP Crystal Server with a Java web application server. If you do not have a web application server in place for use with SAP Crystal Server, the installation program can install and configure a Tomcat 7.0 web application server for you. It is recommended that you evaluate your Planning 2015 SAP SE or an SAP affiliate company. All rights reserved. 9

10 requirements against information from your web application server vendor to determine which supported web application server would best suit your organization's requirements. When configuring a production environment, it is recommended that the web application server is hosted on a separate system. Running SAP Crystal Server and a web application server on the same host in a production environment may decrease performance. If Tomcat 7.0 does not meet your organization's requirements, the following web application servers are supported: JBoss SAP NetWeaver Application Server WebLogic WebSphere For a detailed list of supported web application servers, versions, and patch levels, consult the Supported Platforms Guide available at To use a supported web application server other than the bundled version of Tomcat 6.0, it must be running and accessible before you attempt to install. The Web Tier option installs only web applications to a supported Java web application server. This is useful for deploying web applications to nodes in a web application server cluster. 3.3 Web servers You can use a dedicated web server to host static web content, such as images, HTML, or multimedia files. This is known as a split deployment. Split deployments increase the performance of the web application server as it no longer needs to serve static content, and returns dynamic content only when required. The WDeploy tool is able to separate static dynamic content for deployment to separate web and web application servers. For more information on split deployments, see the SAP BusinessObjects Business Intelligence Platform Web Application Deployment Guide. The web and web application servers can run on the same machine, or on separate machines across a network. SAP Crystal Server supports the following combinations of web servers and web application servers: Apache 2.2 web server with Tomcat 7 Apache web server with WebLogic 10.x IBM IHS web server 6 with WebSphere 6.1 ( or newer) IBM IHS web server 7 with WebSphere 7.0 ( or newer) For a detailed list of supported web servers, versions, and patch levels, consult the Supported Platforms Guide available at SAP SE or an SAP affiliate company. All rights reserved. Planning

11 3.4 Database servers If you do not have a database server in place for use with SAP Crystal Server, the installation program can install and configure one for you. It is recommended that you evaluate your requirements against information from your database server vendor to determine which supported database would best suit your organization's requirements. IBM DB2 is the default database server. Any other database server must be running and accessible when you run the installation program. SAP Crystal Server also supports the following database servers: MySQL Oracle MaxDB Sybase The database client and server must use the Unicode character set. For a list of supported database versions, revision levels, and requirements, consult the Supported Platforms Guide, available at Planning 2015 SAP SE or an SAP affiliate company. All rights reserved. 11

12 4 Preparation This section details how to prepare for the installation of SAP Crystal Server. Process Flow 1. Ensure that sufficient disk space is available. Allow for both the operating system and the software to grow over time as patches or new components become available. 2. Gather the installation media or download the latest release and any patches or service packs from the support portal at To download SAPCAR, go to Software Downloads Support Packages and Patches Browse our Download Catalog SAP Technology Components SAPCAR. To download SAP HOST AGENT, go to Software Downloads Support Packages and Patches Browse our Download Catalog SAP Technology Components SAP HOST AGENT 3. Decide which options you will want to change during the installation process. In most cases, you can accept the default values. More advanced installations require that you plan the installation process. The installation program prompts for the following information: License information (the name of the user and company associated with your SAP Crystal Server license). Web application server configuration, including type, connection, and authentication details. Database server configuration, including type, connection, and authentication details. CMS system and Auditing Data Store configuration information, including type, connection, and authentication details. Folder where SAP Crystal Server will be installed. Central Management Console (CMC) administrator account password and cluster key. CMS port number to receive incoming connections. Server Intelligence Agent (SIA) name. Server Intelligence Agent (SIA) port number for incoming connections. SAP Solution Manager Diagnostics (SMD) configuration. CA Wily Introscope Enterprise Manager configuration. Subversion or ClearCase version control system configuration to store configuration files. Lifecycle management (LCM) configuration. Installation type and components (Full, Custom / Expand, Web Tier). 4.1 System requirements Use the following guidelines when you install SAP Crystal Server: SAP SE or an SAP affiliate company. All rights reserved. Preparation

13 Ensure that the operating system is supported. Only 64-bit operating systems are supported. Windows.NET Framework 3.5 Service Pack 1 and Windows installation program 4.5 are required. Before you run the installation program, ensure that the destination partition has enough room for the deployment to expand (when updates and new features are added in the future). If you install the deployment on the operating system partition, ensure that there is enough room for the deployment and the operating system. It is recommended that you have at least 2 gigabytes available for temporary files and web applications. If you have previously installed any SAP BusinessObjects products, the installation program uses the existing directory. For a detailed list of supported operating systems and hardware requirements, consult the Supported Platforms documentation available at Account permissions To install SAP Crystal Server on a Windows host, a user must have the following permissions: Category Operating system Required access Local administrative privileges. Network Network connectivity through appropriate ports to all machines in the deployment. Access to shared file system directories for users of the deployment. Appropriate network authentication privileges. Database Permission for the SAP BusinessObjects user account to create, edit, and drop tables. Permission for the SAP BusinessObjects user account to create stored procedures (required by the Central Management Server (CMS) system database). You cannot install the deployment on a domain controller, or on a Windows host where the default local Administrator group security settings have been modified. To install SAP Crystal Server on a Unix or Linux host, a user must have the following permissions: Category Required access Operating system Permission to read, write, and execute scripts in the destination directory. For a system install, root access is required (the installation program creates start-up run control scripts in /etc/rc that start or stop the servers when the host machine is started or stopped). Network Network connectivity through appropriate ports to all machines in the deployment. Preparation 2015 SAP SE or an SAP affiliate company. All rights reserved. 13

14 Category Required access Access to shared file system directories. Appropriate network authentication privileges. Database Permission for the SAP BusinessObjects user account to create, edit, and drop tables. Permission for the SAP BusinessObjects user account to create stored procedures (required by the Central Management Server (CMS) system database) Additional Unix and Linux requirements User account Create a user account and group under which the software's background processes can run. Use this account to perform the installation and run the software. The account does not require root privileges. Locale Before you install, set the installing account's environment to use a supported UTF-8 locale and ensure that your console software supports UTF-8 character sets. To ensure that your operating system uses the correct locale, set the LC_ALL and LANG environment variables to your preferred locale in your login environment. For example, the following bash shell commands set the locale to the United States English UTF-8 locale: export LANG=en_US.utf8 export LC_ALL=en_US.utf8 Tip Type locale to check that all of the related locale environment variables (such as LC_MONETARY, LC_NUMERIC) were properly set by LC_ALL. For a detailed list of supported Unix and Linux environments, see the Supported Platforms guide available on the SAP Crystal Server support site Commands In order for the installation program to run correctly, the following utilities must be installed on your system and available on the path: SAP SE or an SAP affiliate company. All rights reserved. Preparation

15 Table 3: /bin/sh pwd read touch uname expr hostname sed awk chown grep tail tar id dirname gzip stty ulimit which ping If one of them is not available on your system, install a version from your operating system vendor rather than a third-party vendor (such as the GNU project). The output from a GNU version of a utility can differ significantly from the version provided by your operating system vendor. To prevent the installation program from encountering output in an unexpected format, ensure that no GNU utilities are used in the installing user account's environment. Installations A new installation can be one of two different types. User installation The installed software is owned by the account that was used to run the installation program. This account must be used to start and stop the servers. Access to the root user account is not required to perform a user installation, and installation program will exit if it detects that it is being run as root. System installation A system installation is a finished user installation with system startup and shutdown run control scripts added. These scripts automatically start and stop SAP Crystal Server server functions as the operating system starts up or shuts down. The script to install the run control scripts must be run with root privileges after a user installation has completed Network permissions When you install SAP Crystal Server across multiple machines, use the following guidelines to ensure your network functions properly: Servers running on all hosts must be able to communicate with each other. Each machine must be able to communicate with the web application server, the Central Management Server (CMS) host, all SIA hosts, and clients. On any host with more than one network interface card (NIC), ensure that the primary NIC is routable before running the installation program. If the primary NIC is not routable, you will have to re-configure the networking settings after the installation. For information on how to bind to routable NICs, see the Managing and Configuring Servers chapter of the SAP BusinessObjects Business Intelligence Platform Administrator Guide. Preparation 2015 SAP SE or an SAP affiliate company. All rights reserved. 15

16 Each machine must use a fixed hostname. Fully-qualified hostnames are supported. Ensure that deployment hostnames do not include any of the following characters: underscore (_), period (.), backslash (\), or forward-slash (/). If you run the installation program behind a firewall, see the Securing SAP BusinessObjects business intelligence platform chapter of the SAP BusinessObjects Business Intelligence Platform Administrator Guide Choosing a server location When planning a distributed installation, consider the latency between servers. To maintain high CMS performance, place your CMS on the same subnet as the CMS system and Auditing Data Store database servers. The CMS can also be clustered, so that CMS server processes run on different host systems in the cluster. When creating a CMS cluster, ensure that each machine experiences the same network latency to the CMS system or Auditing Data Store. Consult the Managing and Configuring Servers section of the SAP BusinessObjects Business Intelligence Platform Administrator Guide for more information on clustering CMS server processes. 4.2 Preparing the CMS system or Auditing Data Store database To use a database server other than the database bundled with SAP Crystal Server, the following tasks must be completed before installing SAP Crystal Server. Create a database (or tablespace or schema, if applicable to your database), and account to store CMS configuration and system information. A second tablespace or scheme is required to hold auditing information. Record the database, tablespace, and account information so you can enter the details when prompted by the SAP Crystal Server installation program. Caution If you have an existing SAP Crystal Server installation, you must create a fresh database and migrate existing content after the install is complete. Ensure that your database server is configured to use Unicode character encoding (such as UTF-8). Ensure that the database accounts have privileges to create, modify, and delete tables, and to create stored procedures. When using a database server on a network, the appropriate database client drivers must be installed and verified as working before installing SAP Crystal Server. Contact your database administrator to establish which drivers are required for your database. During your installation, you will be prompted for the connection and authentication credentials so that the installation program can initialize the database. The table below shows which information is required for supported databases: SAP SE or an SAP affiliate company. All rights reserved. Preparation

17 Table 4: Database Information required by installation program MySQL MySQL database name Server hostname Port number (default is 3306) Account username Account password Reset existing database checkbox (recommended setting) IBM DB2 DB2 Alias name Account username Account password Reset existing database checkbox (recommended setting) Oracle Oracle TNSNAME connection identifier Account username Account password Reset existing database checkbox (recommended setting) MaxDB Database name Server hostname Port number (default is 7210) Account username Account password Reset existing database checkbox (recommended setting) Sybase Service name The Sybase service name is a combination of the hostname and the port number, set by your database administrator in the sql.ini and interfaces files. SAP Crystal Server will connect to the default database for the user you specify. The default is set by the database administrator. Account username Account password Reset existing database checkbox (recommended setting) Table 5: Database Information required by installation program Microsoft SQL Server using ODBC ODBC DSN name (selected from the Windows System DSN list) Account username Account password Database name Use trusted connection checkbox Show system database checkbox Reset existing database checkbox (recommended setting) Preparation 2015 SAP SE or an SAP affiliate company. All rights reserved. 17

18 Database Information required by installation program MySQL MySQL database name Server hostname Port number (default is 3306) Account username Account password Reset existing database checkbox (recommended setting) IBM DB2 DB2 Alias name Account username Account password Reset existing database checkbox (recommended setting) Oracle Oracle TNSNAME connection identifier Account username Account password Reset existing database checkbox (recommended setting) MaxDB Database name Server hostname Port number (default is 7210) Account username Account password Reset existing database checkbox (recommended setting) Sybase Service name The Sybase service name is a combination of the hostname and the port number, set by your database administrator in the sql.ini and interfaces files. SAP Crystal Server will connect to the default database for the user you specify. The default is set by the database administrator. Account username Account password Reset existing database checkbox (recommended setting) Extra requirements for IBM DB2 IBM DB2 has requirements that must be met before installing either SAP Crystal Server with the integrated IBM DB2 database, or your own IBM DB2 database. If you plan to use the integrated IBM DB2 database bundled with SAP Crystal Server, or you plan to install and use your own IBM DB2 database server for use with SAP Crystal Server: Ensure that the ID of the user account used to host the DB2 database meets the following requirements from IBM. For more information an IBM's requirements for Unix or Linux systems hosting DB2, see DB2 users and groups (Linux and UNIX) in the Database Fundamentals section of the DB2 Solution Information Center at SAP SE or an SAP affiliate company. All rights reserved. Preparation

19 Must have a primary group other than guests, admins, users, or local Can include only lowercase letters (a-z), numbers (0-9), or the underscore character (_) Cannot be longer than eight characters Cannot begin with IBM, SYS, SQL, or a number Cannot be a DB2 reserved word (USERS, ADMINS, GUESTS, PUBLIC, or LOCAL), or an SQL reserved word Cannot use any user IDs with root privilege for the DB2 instance ID, DAS ID, or fenced ID. Cannot include accented characters If existing user IDs are specified instead of creating new user IDs, ensure that the user IDs: Are not locked Do not have expired passwords The primary group of the user must meet the following requirements: Cannot be one of guests, admins, users, or local Cannot start with sql or ibm Cannot start with a number Must contain only lowercase letters (a-z), or numbers (0-9). If you plan to install and use an IBM DB2 database server for use with SAP Crystal Server: Ensure that the DB2 database is created with the following settings: Collating Sequence = "Identity" Codeset = "UTF-8" Territory = "<XX>" Replace <XX> with the code that is appropriate for your location. Consult your DB2 documentation for more information. If your DB2 database does not have the Collating Sequence = "Identity" setting, the user and user group objects may not sort as expected in the CMC. Create a user temporary table space before installing SAP Crystal Server. If you do not create a user temporary table space, the SAP Crystal Server installation program will not be able to configure the DB2 database. For more information on user temporary table spaces in IBM DB2, see DB2 Basics: Table spaces and buffer pools in the IBM technical library: wieser/0212wieser.html. When using IBM DB2 to host an Auditing Data Store database, ensure that the page size for the auditing table space is set to a minimum of 8192 (8 KB). Ensure that the CMS system database is not partitioned. The Auditing Data Store database may be partitioned Interprocess Communications (IPC) settings when using the bundled DB2 9.7 FP1 database The database bundled with SAP Crystal Server is IBM DB2 9.7 FP1. If using the bundled database, prior to installation, ensure the following IPC parameters have been set with a value equal to or greater than the following minimum values: Preparation 2015 SAP SE or an SAP affiliate company. All rights reserved. 19

20 IPC kernel parameter kernel.shmmax (SHMMAX) Enforce minimum setting (64-bit kernel) kernel.sem (SEMMNI) kernel.msgmni (MSGMNI) kernel.msgmax (MSGMAX) kernel.msgmnb Extra requirements for Sybase If you are using Sybase for the CMS or auditing database: Create a database with a page size of 8 KB. The Sybase database default page size is 2KB, which is too small for the CMS system database to run efficiently. The page size is set up during the database creation and cannot be changed after the database is created. Use a Unicode character set, such as UTF Set ulimit to unlimited To successfully build and deploy SAP Crystal Server web applications, the host operating system or user account ulimit setting must be configured as unlimited. Set the ulimit configuration with the ulimit command, or modify the system configuration file /etc/ security/limits.conf. For more information about the ulimit setting, see the documentation included with your operating system. 4.4 Final checklist Prior to installing SAP Crystal Server, review the following checklist. Have you decided on the installation destination folder? The use of Unicode characters in the destination folder is not supported. Ensure that the installation destination folder is not the same folder in which the installation program has been extracted (do not install to the current working directory when running the installation program from the current working directory). Have you verified appropriate network connectivity between all machines that will be part of your deployment? SAP SE or an SAP affiliate company. All rights reserved. Preparation

21 If you are using your own database server: Have you created a database, tablespace (if required), and accounts for the CMS system and Auditing Data Store databases? Have you made sure you can log onto the database from the SAP Crystal Server host? If you are using DB2 or Sybase, have you verified that your database was created with the correct settings? (Some settings can't be modified after the database has been created.) Has the database client software been properly configured? If you are using your own web application server: Have you decided on which web application server to use? Has the server already been installed and configured? Have you ensured that your existing web application server has the required JDK installed? Installation on Microsoft Windows requires a minimum screen solution of The SAP Crystal Server setup program no longer installs Client Tools. Client Tools can only be installed with the dedicated Client Tools installation program. Preparation 2015 SAP SE or an SAP affiliate company. All rights reserved. 21

22 5 Installation There are two different methods of running the installation program for SAP Crystal Server: Interactive installation An interactive wizard prompts for all information related to the installation. Use this option to select individual installation options from a series of screens. This is the default installation method. Silent installation Installation options are given on the command-line, which override the installation program's default values. The command-line can be used to give some or all installation options. When an installation option is not given on the command-line, the installation program uses a default value. Installation options can be given in a response file rather than directly on the command-line. This type of silent installation uses the -r command-line parameter to read installation options from the response file. Use this option if you want to install multiple machines with the same configuration. Installation options stored in a response file can be overridden by giving them on the command-line. When the -q (quiet mode) switch is used, the installation program does not prompt for any user input during the installation. If the installation program encounters an unexpected condition, and is unable to continue, it will undo any work completed up to that point, and return the system to the state that it was in before the installation started. When the installation program detects an identical previously-installed version, it will enter maintenance mode, allowing you to remove, repair, or modify the software. 5.1 To download the installation program 1. Go to > Software Downloads. 2. Select Installations and Upgrades>A Z Index. 3. Select C Crystal Server Crystal Server Select Installation and Upgrade and then select your platform. 5. Select all of the objects titled SBOP BI PLATFORM <version> SERVER plus any additional add-on products you require, then follow the instructions on the website to download and extract the objects. The software may take a long time to download, and you may need to contact the system administrator to ensure your company's firewall will not terminate the download process. Support Packages and Patches are installation programs that contain updates to BI platform software. You can download them from > Software Downloads Support Packages and Patches A Z Index. For more information on installing Support Packages and Patches, see the SAP BusinessObjects Business Intelligence Platform Upgrade Master Guide SAP SE or an SAP affiliate company. All rights reserved. Installation

23 5.2 To run an interactive installation Load, mount, or download the SAP Crystal Server installation media. Ensure that LC_ALL has been set to a supported UTF-8 character set, such as en_us.utf8. For example: export LANG=en_US.utf8 export LC_ALL=en_US.utf8 The installation log file will be saved to <<BOE_INSTALL_DIR>>/InstallData/logs/<<DATE>>/ InstallDU<<COMPONENT>>.log. 1. Change directory to the folder containing the setup.sh installation program. Use the InstallDir=<<DESTINATION_DIR>> parameter to set the destination folder from the command line. For example, to install SAP Crystal Server into the folder /opt/sap, use the command./setup.sh InstallDir=/opt/sap. 2. Choose a language for the setup program to use during the installation process. The language setting is used by the installation program to display information to you in the language of your choice. If you select a non- English language, the corresponding language pack is automatically installed on the server. The installation program will automatically run in the same language as your operating system. The language used by the installation program will determine the names used for components configured by the installation program. These names cannot be changed later and are not affected by language settings once the installation is complete. 3. Review the destination folder shown. This is the folder into which the installation program will install SAP Crystal Server. If the folder does not exist, the installation program creates it. The use of Unicode characters in the destination folder is not supported. Ensure that the destination folder is not the same folder in which the installation program has been extracted (do not install to the current working directory when running the installation program from the current working directory). 4. The installation program checks for required components and conditions. Review the results and decide whether to continue with the installation, or abort and correct any unmet requirements. If a dependency prerequisite condition is critical, the installation program will not allow the installation to proceed. If the missing or unsupported component is optional, you have the option to either continue with the installation or stop and correct the condition. 5. Review the installation welcome screen. 6. Review and accept the license agreement. 7. Enter the product keycode. The product keycode was given to you when you purchased SAP Crystal Server. Store the keycode and registration information in a safe place in case you need to re-install. 8. To install support for a language, select it from the list. Installation 2015 SAP SE or an SAP affiliate company. All rights reserved. 23

24 Carefully consider which languages need to be installed for your organization. To add or remove language support later requires that you remove and re-install SAP Crystal Server. The language currently being used by the operating system is selected automatically. English language support cannot be deselected because SAP Crystal Server falls back to using English if a problem is detected with an individual language. 9. Select one of the following install type options: User install A user installation causes the installation program to install the software as a self-contained package within a directory, where the software must be started and stopped manually from the command-line. System install A system installation causes the installation program to install start-up and shutdown scripts in the run control (rc) folder of the operating system (/etc/rc or similar) so that the software will start and stop automatically with the operating system. A system installation requires root user privileges. The Choose Install Type screen appears To select an install type SAP Crystal Server requires a database server and web application server to function. If you do not have an existing database, the installation program can automatically install and configure a Microsoft SQL Server database. If you do not have an existing web application server, the installation program can automatically install and configure a Tomcat web application server. SAP Crystal Server requires a database server and web application server to function. If you do not have an existing database, the installation program can automatically install and configure an IBM DB2 database. If you do not have an existing web application server, the installation program can automatically install and configure a Tomcat web application server. The Choose Install Type screen is used to select the installation component options. 1. Select one of the following install type options: Full Installs all required server components onto a single machine. Use this option to create a single-host deployment, such as a pre-production development or test environment. Custom / Expand Install Allows experienced users to select individual components. Use this option: When distributing server components between more than one host, such as creating a CMS cluster. When you want full control over which components are deployed to a host. Web Tier The web tier hosts web applications and serves content to users over the web. Use the Web Tier installation option to install Java web applications onto a dedicated Java web application server SAP SE or an SAP affiliate company. All rights reserved. Installation

25 If you do not have a web application server in place for use with SAP Crystal Server, the installation program can install and configure a Tomcat web application server for you. It is recommended that you evaluate your requirements against information from your web application server vendor to determine which supported web application server would best suit your organization's needs. If you already have a supported web application server installed, you can deselect the option to install Tomcat, and only install the Java web applications 2. Proceed to the next screen to start configuring the selected installation. You may return to the install type options screen at any time later. Review the Destination Folder shown. This is the folder into which the installation program will install SAP Crystal Server. If the folder does not exist, the installation program creates it. The use of Unicode characters in the destination folder is not supported. Ensure that the destination folder is not set to the same folder in which the installation program has been extracted. If you have already installed SAP BusinessObjects products, the Destination Folder field is not editable, and the path to the existing folder is displayed. 3. If you selected a Full installation, proceed to the following Full section. 4. If you selected a Custom / Expand installation, proceed to the following Custom / Expand section. 5. If you selected a Web Tier installation, proceed to the following Web Tier section Full Installation of Crystal Server The following steps are performed for full installations of SAP Crystal Reports Server. 1. A database is required to store Central Management Server (CMS) configuration and run-time information. A second database is required for Auditing Data Store (ADS) information. If you do not have a database server in place for use with SAP Crystal Server, the installation program can install and configure one for you. It is recommended that you evaluate your requirements against information from your database server vendor to determine which supported database would best suit your organization's needs. To install the bundled database server, select Install and use the default database. IBM DB2 will be installed and configured to store Central Management Server (CMS) and auditing data. To use an existing supported database server, select Use an existing database server. The installation program prompts for information on the database type and connection credentials for both the CMS system and Auditing Data Store databases. An existing database must have user accounts with the appropriate privileges ready, and the appropriate drivers must be installed and verified as working. The installation program attempts to connect to, and initialize, the database as a part of the installation process. Installation 2015 SAP SE or an SAP affiliate company. All rights reserved. 25

26 2. If you selected Use an existing database server: a. Select the database type to use for the CMS database. b. Select the database type to use for the Auditing database (Auditing Data Store). If you do not want to use the auditing feature, select No Auditing Database. 3. A Java web application server is required to host SAP Crystal Reports Server 2011 Support Package 12 web applications. If you do not have a web application server in place for use with SAP Crystal Reports Server 2011 Support Package 12, the installation program can install and configure a Tomcat web application server for you. It is recommended that you evaluate your requirements against information from your web application server vendor to determine which supported web application server would best suit your organization's needs. When configuring a production environment, it is recommended that the web application server is hosted on a separate system. Running SAP Crystal Reports Server 2011 Support Package 12 and a web application server on the same host in a production environment may decrease performance. This release of SAP Crystal Server does not support the automatic deployment of web applications to any web application server other than the bundled Tomcat web application server. To deploy web applications to a different supported web application server, use the WDeploy tool. For more information, see the SAP BusinessObjects Business Intelligence platform Web Application Deployment Guide. To use the bundled Tomcat Java web application server, select Install Tomcat application server and automatically web applications and services to it. To manually deploy web applications to an existing supported Java web application server later, using the WDeploy tool, select Manually deploy to a preinstalled web application server. If you have already set up a Java web application server, or you only require support for the Central Management Server (CMS) or BI launch pad applications, select Install Web Application Container Server and automatically deploy web applications and services to it. 4. Decide whether to install and use the Subversion version control system to keep track of configuration versions with the SAP Lifecycle Manager. To use an existing version control system, you must manually configure the Lifecycle Manager after the installation is complete. Lifecycle Manager stores each configuration change in a version control system, making it easier to revert to a previous configuration when needed. 5. Enter a name and port number for the System Intelligence Agent (SIA) node. The name must consist of English alphanumeric characters (A-Z, a-z, and 0-9) and contain no spaces or other punctuation. The SIA name cannot start with a number. This is the name that you will see in the Central Configuration Manager (CCM). Many CMS servers can be managed by a single SIA. The port is used for the SIA to listen for incoming connections from the CMS. The SIA must be able to receive incoming connections on this port, so ensure that your firewall is configured appropriately. Port 6410 is a standard TCP/IP port number reserved for use with an SAP Crystal Server SIA. 6. Review the default value for the Central Management Server (CMS) port number. This is the port on which the CMS listens for incoming connections from the web application server, web server (if applicable), other CMS SAP SE or an SAP affiliate company. All rights reserved. Installation

27 nodes (if applicable) and servers. The CMS must be able to receive incoming connections on this port, so ensure that your firewall is configured appropriately. Port 6400 is a standard TCP/IP port number reserved for use with SAP Crystal Server CMS systems. 7. Enter and confirm the CMS Administrator account password and the CMS cluster key. The CMS Administrator is a super-user account in the SAP Crystal Reports Server 2011 Support Package 12 authentication system, used only to administer your SAP BusinessObjects server configuration. It is not part of any operating system or single sign-on authentication system. Communication between some CMS components is encrypted to provide a higher level of security when using clusters. 8. Configure the CMS system database. a. If you chose to install the bundled database, the installation program uses your choices to install and configure the database for use with SAP Crystal Server. Enter the port number for DB2 to listen for incoming database queries. The DB2 database must be able to receive incoming connections on this port, so ensure that your firewall is configured appropriately. b. If you deselected the Integrated Database option in the feature list, enter the connection information for an existing database to use for the CMS system database. c. If you deselected the Integrated Database option in the feature list, and you plan to use auditing, enter the connection information for the Auditing Data Store (ADS) database. 9. Decide whether to start the servers as soon as the installation is complete. If you do not start the servers after the installation process is complete, the servers must be started manually with the Central Configuration Manager (CCM). 10. Configure the web application server. If you selected Tomcat 7.0 in the feature list, review the default values for the web application server connection port number, the shutdown port number, and the redirect port number. The Connection port is the port on which the web application server listens for incoming connections from web clients. The Shutdown port allows the web application to be shut down remotely. The Redirect port enables redirects to secure web connections. 11. If you chose to install the bundled Subversion version control system for use with Lifecycle Manager, confirm the port number and enter and confirm a password for SAP Crystal Server to use when accessing the Subversion repository. 12. SAP Crystal Server can integrate with your organization's deployment of SAP Solution Manager Diagnostics (SMD). If your organization uses SAP SMD, select Configure connectivity to SAP SMD Agent. You will be prompted for information. If you chose not to configure SMD at this time, you can configure SMD Agent in the Central Management Console (CMC) Placeholders screen later. To use SAP Solution Manager Diagnostics (SMD), SAP Host Agent and SMD Agent must be installed: For information on installing the SAP Host Agent before SAP Crystal Reports Server 2011 Support Package 12, see To enable SAP System Landscape Directory (SLD) support. For information on installing the SAP Host Agent after SAP Crystal Reports Server 2011 Support Package 12, see To configure System Landscape Directory (SLD) Data Supplier (DS) post installation. Installation 2015 SAP SE or an SAP affiliate company. All rights reserved. 27

28 For information on installing SMD Agent before SAP Crystal Server, see SAP Solution Manager Diagnostics (SMD). For information on installing SMD Agent after SAP Crystal Server, see To configure SMD Agent post installation. a. If you chose to integrate with SMD, enter the SMD Agent hostname and port number. 13. SAP Crystal Server can integrate with your organization's deployment of CA Wily Introscope Enterprise Manager. If your organization uses Introscope Enterprise Manager, select Integrate connectivity to Introscope Enterprise Manager. You will be prompted for information. To use CA Wily Introscope Enterprise Manager, SMD Agent must be installed: For information on installing SMD Agent before SAP Crystal Server, see SAP Solution Manager Diagnostics (SMD). For information on installing SMD Agent after SAP Crystal Server, see To configure SMD Agent post installation. a. If you chose to integrate with Introscope Enterprise Manager, enter the hostname and port number for the Introscope Enterprise Manager server. The Start Installation screen appears. Click Next to install. Proceed to While the installation program runs Custom / Expand installation The following steps are performed for Custom / Expand installations of SAP Crystal Server. The Select Features screen displays selectable components that can be installed. 1. Review the list of features to install. Only features with a selected checkbox are installed. Features are grouped under the following headings: Web Tier The web tier components serve content to web browsers. If you do not have a web application server in place for use with SAP Crystal Server, the installation program can install and configure a Tomcat web application server for you. It is recommended that you evaluate your requirements against information from your web application server vendor to determine which supported web application server would best suit your organization's needs. If you already have a supported web application server installed, you can deselect the option to install Tomcat, and only install the Java web applications Servers Server features include the Business Intelligence platform servers (such as processing and scheduling servers), major system components (such as the CMS, Event Server, bundled database, and a version control system). Administrator Tools The Administrator Tools features help administrators maintain an installation SAP SE or an SAP affiliate company. All rights reserved. Installation

29 If you plan to use the upgrade management tool to upgrade objects from an older version of SAP Crystal Server, see Object types and feature requirements. Database Access To access, analyze, and report on the data in your organization's existing databases, select the appropriate Database Access features. If your organization does not use a particular database, you can deselect it. Samples The samples features installs sample reports, templates, and reporting databases. If you do not need samples, you can deselect it. 2. Select the type of installation being performed. If you are installing a stand-alone server, or the first server in a cluster, select Start a new SAP Crystal Server deployment. If you already have a CMS and want to create a new server as part of a cluster, select Expand an existing SAP Crystal Server deployment. If you selected Start a new SAP Crystal Server deployment on the last screen, proceed to Custom (New) installation. If you selected Expand an existing SAP Crystal Server deployment on the last screen, proceed to Custom (Expand) installation Custom (New) installation If you chose the Start a new SAP Crystal Server deployment option for a Custom / Expand installation: 1. If you deselected the Integrated Database option in the feature selection screen: a. Select the type of database to use for the CMS system database. b. Select the type of database to use for the Auditing Data Store (ADS) database. If you do not want to use auditing, select No Auditing Database. An existing database must have database user accounts with the appropriate database privileges ready, and the appropriate drivers must be installed and verified as working. The installation program attempts to connect to, and initialize, the database as a part of the installation process. 2. Enter a name and port number for the System Intelligence Agent (SIA) node. The name must consist of English alphanumeric characters (A-Z, a-z, and 0-9) and contain no spaces or other punctuation. The SIA name cannot start with a number. This is the name that you will see in the Central Configuration Manager (CCM). Many CMS servers can be managed by a single SIA. The port is used for the SIA to listen for incoming connections from the CMS. The SIA must be able to receive incoming connections on this port, so ensure that your firewall is configured appropriately. Port 6410 is a standard TCP/IP port number reserved for use with an SAP Crystal Server SIA. 3. Review the default value for the Central Management Server (CMS) port number. This is the port on which the CMS listens for incoming connections from the web application server, web server (if applicable), other CMS Installation 2015 SAP SE or an SAP affiliate company. All rights reserved. 29

30 nodes (if applicable) and servers. The CMS must be able to receive incoming connections on this port, so ensure that your firewall is configured appropriately. Port 6400 is a standard TCP/IP port number reserved for use with SAP Crystal Server CMS systems. 4. Enter and confirm the CMS Administrator account password and the CMS cluster key. The CMS Administrator is a super-user account in the SAP Crystal Server authentication system, used only to administer your server. It is not part of any operating system or single sign-on authentication system. Communication between some CMS components is encrypted, to provide a higher level of security when using clusters. 5. Configure the CMS system database. a. If you chose to install the bundled database, the installation program uses your choices to install and configure the database for use with SAP Crystal Server. Enter the port number for DB2 to listen for incoming database queries. The DB2 database must be able to receive incoming connections on this port, so ensure that your firewall is configured appropriately. b. If you deselected the Integrated Database option in the feature list, enter the connection information for an existing database to use for the CMS system database. c. If you deselected the Integrated Database option in the feature list, and you plan to use auditing, enter the connection information for the Auditing Data Store (ADS) database. 6. Decide whether to start the servers as soon as the installation is complete. If you do not start the servers after the installation process is complete, the servers must be started manually with the Central Configuration Manager (CCM). 7. Configure the web application server. If you selected Tomcat 7.0 in the feature list, review the default values for the web application server connection port number, the shutdown port number, and the redirect port number. The Connection port is the port on which the web application server listens for incoming connections from web clients. The Shutdown port allows the web application to be shut down remotely. The Redirect port enables redirects to secure web connections. 8. If you chose to install the bundled Subversion version control system for use with Lifecycle Manager, confirm the port number and enter and confirm a password for SAP Crystal Server to use when accessing the Subversion repository. 9. SAP Crystal Server can integrate with your organization's deployment of SAP Solution Manager Diagnostics (SMD). If your organization uses SAP SMD, select Configure connectivity to SAP SMD Agent. You are prompted for information. If you chose not to configure SMD at this time, you can configure SMD Agent in the Central Management Console (CMC) Placeholders screen later. To use SAP Solution Manager Diagnostics (SMD), SAP Host Agent and SMD Agent must be installed: For information on installing the SAP Host Agent before SAP Crystal Server, see To enable SAP System Landscape Directory (SLD) support. For information on installing the SAP Host Agent after SAP Crystal Server, see To configure System Landscape Directory (SLD) Data Supplier (DS) post installation SAP SE or an SAP affiliate company. All rights reserved. Installation

31 For information on installing SMD Agent before SAP Crystal Server, see SAP Solution Manager Diagnostics (SMD). For information on installing SMD Agent after SAP Crystal Server, see To configure SMD Agent post installation. a. If you chose to integrate with SAP Solution Manager Diagnostics (SMD), enter the SMD Agent hostname and port number. 10. SAP Crystal Server can integrate with your organization's deployment of CA Wily Introscope Enterprise Manager. If your organization uses Introscope Enterprise Manager, select Integrate connectivity to Introscope Enterprise Manager. You are prompted for information. To use CA Wily Introscope Enterprise Manager, SMD Agent must be installed: For information on installing SMD Agent before SAP Crystal Server, see SAP Solution Manager Diagnostics (SMD). For information on installing SMD Agent after SAP Crystal Server, see To configure SMD Agent post installation. a. If you chose to integrate with Introscope Enterprise Manager, enter the hostname and port number for the Introscope Enterprise Manager server. The Start Installation screen appears. Click Next to install. Proceed to While the installation program runs Custom (Expand) installation If you chose the Expand an existing SAP Crystal Server deployment option for a Custom / Expand installation: 1. The expand host must be able to connect to the CMS database. Select the type of server used for the CMS system database. The installation program prompts for information on the CMS database type and connection credentials. The appropriate drivers must be installed and verified as working on the expand host. 2. Enter a name and review the port number for the System Intelligence Agent (SIA) node. The name must consist of English alphanumeric characters (A-Z, a-z, and 0-9) and contain no spaces or punctuation. The SIA name cannot start with a number. This is the name that you will see in the Central Configuration Manager (CCM). Many CMS servers can be managed by a single SIA. The port is used for the SIA to listen for incoming connections from the CMS. The SIA must be able to receive incoming connections on this port, so ensure that your firewall is configured appropriately. Port 6410 is a standard TCP/IP port number reserved for use with a SAP Crystal Server SIA. 3. Enter connection information for the existing CMS. This includes the hostname and port number of the primary CMS. Fully qualified domain names are supported. Installation 2015 SAP SE or an SAP affiliate company. All rights reserved. 31

32 4. Enter and confirm a value for the CMS cluster key. Communication between some CMS components is encrypted to provide a higher level of security. 5. Review the default value for the new Central Management Server (CMS) port number. This is the port on which the new CMS listens for incoming connections from the web application server, web server (if applicable), other CMS nodes (if applicable) and servers. The CMS must be able to receive incoming connections on this port, so ensure that your firewall is configured appropriately. Port 6400 is a standard TCP/IP port number reserved for use with SAP Crystal Server CMS systems. 6. If you are installing the bundled database, enter a database administrator account password and an Enterprise user account name and password. If you are using a previously installed database, enter connection credentials for the CMS to connect to the database. The installation program uses your choices to install, configure the database for use with SAP Crystal Server. 7. Decide whether to start the servers as soon as the installation is complete. If you do not start the servers after the installation process is complete, the servers must be started manually with the Central Configuration Manager (CCM). 8. Review the default values for the web application server connection port number, the shutdown port number, and the redirect port number. The web application server must be able to receive incoming connections on these ports, so ensure that your firewall is configured appropriately. The Connection port is the port on which the web application server listens for incoming connections from web clients. The Shutdown port allows the web application to be shut down remotely. The Redirect port enables redirects to secure web connections. 9. Review the port number and provide a password for SAP Crystal Server to use when accessing the Subversion repository. 10. SAP Crystal Server can integrate with your organization's deployment of SAP Solution Manager Diagnostics (SMD). If your organization uses SAP SMD, select Configure connectivity to SAP SMD Agent. You are prompted for information. If you chose not to configure SMD at this time, you can configure SMD Agent in the Central Management Console (CMC) Placeholders screen later. To use SAP Solution Manager Diagnostics (SMD), SAP Host Agent and SMD Agent must be installed: For information on installing the SAP Host Agent before SAP Crystal Server, see To enable SAP System Landscape Directory (SLD) support. For information on installing the SAP Host Agent after SAP Crystal Server, see To configure System Landscape Directory (SLD) Data Supplier (DS) post installation. For information on installing SMD Agent before SAP Crystal Server, see SAP Solution Manager Diagnostics (SMD). For information on installing SMD Agent after SAP Crystal Server, see To configure SMD Agent post installation. a. If you chose to integrate with SAP Solution Manager Diagnostics (SMD), enter the SMD Agent hostname and port number. 11. SAP Crystal Server can integrate with your organization's deployment of CA Wily Introscope Enterprise Manager. If your organization does not use Introscope Enterprise Manager, select Do not integrate connectivity to Introscope Enterprise Manager SAP SE or an SAP affiliate company. All rights reserved. Installation

33 To use CA Wily Introscope Enterprise Manager, SMD Agent must be installed: For information on installing SMD Agent before SAP Crystal Server, see SAP Solution Manager Diagnostics (SMD). For information on installing SMD Agent after SAP Crystal Server, see To configure SMD Agent post installation. a. If you chose to integrate with Introscope Enterprise Manager, enter the hostname and port number for the Introscope Enterprise Manager server. The Start Installation screen appears. Select Next to install. Proceed to While the installation program runs Web Tier installation The web tier hosts web applications and serves content to users over the web. Use the Web Tier installation option to install Java web applications onto a dedicated Java web application server. A web tier installation does not deploy web applications to the web application server. To deploy web applications to a web application server after a web tier installation, use the WDeploy tool. For more information on using the WDeploy tool, see the SAP BusinessObjects Business Intelligence Platform Web Application Deployment Guide. If you do not have a web application server in place for use with SAP Crystal Server, the installation program can install and configure a Tomcat web application server for you. It is recommended that you evaluate your requirements against information from your web application server vendor to determine which supported web application server would best suit your organization's needs. If you already have a supported web application server installed, you can deselect the option to install Tomcat, and only install the Java web applications The following steps are performed for Web Tier installations of SAP Crystal Server. 1. Review the list of features to install. Only features with a selected checkbox are installed. Web Tier components: Java Web Applications: Central Management Console (CMC), BI launch pad, and other web applications Tomcat 7: the Apache Tomcat web application server. 2. If you chose to install the Tomcat 7 web application server, review the default values for the web application server connection port number, the shutdown port number, and the redirect port number. The web application server must be able to receive incoming connections on these ports, so ensure that your firewall is configured appropriately. The Connection port is the port on which the web application server listens for incoming connections from web clients. The Shutdown port allows the web application to be shut down remotely. The Redirect port enables redirects to secure web connections. Installation 2015 SAP SE or an SAP affiliate company. All rights reserved. 33

34 3. SAP Crystal Server can integrate with your organization's deployment of CA Wily Introscope Enterprise Manager. If your organization uses Introscope Enterprise Manager, select Integrate connectivity to Introscope Enterprise Manager. You will be prompted for information. To use CA Wily Introscope Enterprise Manager, SMD Agent must be installed: For information on installing SMD Agent before SAP Crystal Server, see SAP Solution Manager Diagnostics (SMD). For information on installing SMD Agent after SAP Crystal Server, see To configure SMD Agent post installation. a. If you chose to integrate with Introscope Enterprise Manager, enter the hostname and port number for the Introscope Enterprise Manager server. The Start Installation screen appears. Click Next to install. Proceed to While the installation program runs While the installation program runs The progress bar illustrates the progress of the installation as a whole. When performing an Expand installation, the existing CMS may be restarted automatically as a part of the installation process. The installation program installs SAP activity and resource monitoring tools. These tools enable you to provide detailed technical information about your installation in the event of a problem When installation is complete When the installation is complete, review the information in the Post Installation Steps screen. If you are not using the bundled Tomcat web application server, you must deploy web applications with the WDeploy web application deployment tool Reboot suppression If a file is locked during the installation, you may be prompted to restart the server after the installation. You can choose to reboot immediately, or later. However, if you choose to suppress the reboot, the system may be in an unsupported state until the system is rebooted. The installation log will record whether the system is rebooted at the end of the installation process SAP SE or an SAP affiliate company. All rights reserved. Installation

35 5.3 To run a silent installation Every option in the installation wizard can be given from the command-line. This type of installation is known as a silent install. Installation options can be given directly on the command-line as a parameter, or can be stored in a response file. Giving installation options on the command-line Installation options can be passed directly to the setup program from the command-line as a parameter. For example, the installation option CMSPort=6401 can be given on the command-line as a parameter when running the installation program to set the CMS port number to 6401, instead of the default value of In the following example of giving the CMSPort parameter on the command-line, ellipses ([...]) are shown to indicate where other installation options would normally be present: setup.exe [...] CMSPort=6401 [...]./setup.sh [...] CMSPort=6401 [...] Giving installation options in a response file Installation options can be stored in a response file, which is a text file containing installation option parameters in key-value format. When using a response file to give installation options, the installation program is run from the command-line with the -r <<RESPONSE_FILE>> parameter, where <<RESPONSE_FILE>> is the name of the response file. The response file contains multiple installation options, with one installation option per line. In the following example, the response file is given as a parameter: setup.exe [...] -r C:\response.ini [...]./setup.sh [...] -r $HOME/response.ini [...] For example, the installation option CMSPort=6401 can be given on a line in the response file to set the CMS port number to 6401, instead of the default value of In the following example of giving the CMSPort parameter in a response file, ellipses ([...]) are shown to indicate where other installation options would normally be present: [...] CMSPort=6401 [...] The installation program returns the cursor to the command-line prompt when it starts. To run the installation program from a script, or to force the installation program to wait to complete before returning to the command-line, use the Windows Command Interpreter start /wait command to invoke setup.exe. For example: start /wait setup.exe [<<COMMAND_LINE_OPTIONS>>] For a complete list of installation options, see Installation option parameters [page 38]. For an example of a response file, see Response file example [page 45]. Installation 2015 SAP SE or an SAP affiliate company. All rights reserved. 35

36 5.3.1 Command-line switch parameters The following table lists the switch parameters that can be given to the installation program on the command-line to perform a silent installation. Table 6: Installation program command-line switch parameters Switch parameter Description Example -w <<FILENAME>> Writes a response file to <<FILENAME>>, containing the options selected from the installation wizard. -r <<FILENAME>> Reads installation options from a response file named <<FILENAME>>. setup.exe -w "C: \response.ini"./setup.sh -w "$HOME/ response.ini" setup.exe -r "C: \response.ini"./setup.sh -r "$HOME/ response.ini" -q When performing a silent installation, this switch causes the installation program to install with no console output or prompting. If a problem is encountered, the installation program will write a message to the installation log file and exit. This switch must always be used in combination with the -r <<FILENAME>> switch parameter. setup.exe -q -r "C: \response.ini"./setup.sh -q -r "$HOME/ response.ini" To use a response file To use a response file, run the installation program with the -r <<RESPONSE_FILE>> parameter. The installation program reads all installation options from the response file, and no further input is required. For example, the following command reads installation options from the response file C:\response.ini: setup.exe -r C:\response.ini For example, the following command reads installation options from the response file $HOME/response.ini:./setup.sh -r $HOME/response.ini To override an installation option in a response file, give that option on the command-line. Installation options given on the command-line take precedence over the options in the response file. For a complete list of installation options, see Installation option parameters below. If an unexpected condition is encountered, an error message is written to the installation log file and the installation program exits. Installation activity, warnings, and errors are written to the installation log file in the folder: <<BOE_INSTALL_DIR>>\InstallData\logs\<<DATE>>\InstallDU<<COMPONENT>>.log SAP SE or an SAP affiliate company. All rights reserved. Installation

37 <<BOE_INSTALL_DIR>>/InstallData/logs/<<DATE>>/InstallDU<<COMPONENT>>.log If the <<BOE_INSTALL_DIR>> folder has not been created by the time the installation program exits, look for install.log in the temporary folder specified by the system <TEMP> environment variable To write a response file To create a response file, run the installation program with the -w <<RESPONSE_FILE>> parameter and select the desired installation options with the installation wizard. When the wizard completes, the installation program exits and the response file is created. The response file can then be used for future installations. For example, the following command creates the response file C:\response.ini: setup.exe -w C:\response.ini For example, the following command creates the response file $HOME/response.ini:./setup.sh -w $HOME/response.ini Once created, the response file can be updated with a text editor. When creating a response file with the GUI installation program, passwords entered via the GUI will be written to the response file in plain text format To read a response file A response file installation is started on the command-line, but installation options are read from a ASCII text file with the options stored in key-value format. This is useful when setting up a cluster, or for creating development or test environments with standardized options. When an option is given both on the command-line and in a response file, the command-line options take precedence over the response file options. This allows an administrator to override an option in a response file when required. This provides three levels precedence for installation options: 1. Installation options given on the command-line take highest precedence, and will always override response file and default values. 2. Installation options given in a response file are used when not given on the command-line, and override default values. 3. Installation option default values are used when not given on the command-line or in a response file. For example, the following command reads installation options from the response file C:\response.ini, but overrides the response file's setting for the installation destination folder: setup.exe -r C:\response.ini InstallDir="C:\SAP\SAP BusinessObjects Enterprise XI 4.0\" Installation 2015 SAP SE or an SAP affiliate company. All rights reserved. 37

38 For example, the following command reads installation options from the response file $HOME/response.ini, but overrides the response file's setting for the installation destination folder:./setup.sh -r $HOME/response.ini InstallDir=/opt/sap/sap_bobj/ Quiet mode installations A quiet mode installation is a command-line installation that does not prompt for installation options. Installation options must be provided on the command-line or in a response file. Any installation options not provided on the command-line or in a response file are left at their default values. The -q switch bypasses the installation program's installation wizard, and allows an installation to be performed with no human input and no console output. For example, the following command uses the default values for all installation options, except for the installation destination folder (set to C:\SAP\SAP BusinessObjects Enterprise XI 4.0\ instead of the default folder C:\Program Files (x86)\sap BusinessObjects Enterprise XI 4.0). setup.exe -q InstallDir="C:\SAP\SAP BusinessObjects Enterprise XI 4.0\" For example, the following command uses the default values for all installation options, except for the installation destination folder (set to /opt/sap/sap_bobj instead of the current working folder). setup.exe -q InstallDir=/opt/sap/sap_bobj/ If an unexpected condition is encountered, an error message is written to the installation log file and the installation program exits. Installation activity, warnings, and errors are written to the installation log file in the folder: <<BOE_INSTALL_DIR>>\InstallData\logs\<<DATE>>\InstallDU<<COMPONENT>>.log <<BOE_INSTALL_DIR>>/InstallData/logs/<<DATE>>/InstallDU<<COMPONENT>>.log If the <<BOE_INSTALL_DIR>> folder has not been created by the time the installation program exits, look for a file named setupengine.log in a timestamp folder in the temporary folder specified by the system <TEMP> environment variable Installation option parameters The following table lists the parameters that can be used to select installation options on both the command-line and in response files. See the table Installation option parameters specific to Windows for parameters specific to Windows operating systems. See the table Installation option parameters specific to Unix or Linux for parameters specific to Unix or Linux operating systems SAP SE or an SAP affiliate company. All rights reserved. Installation

39 Table 7: Installation option parameters Parameter SetupUILanguage=<<CODE>> Description Determines which language for the installation program to use during the installation. Substitute the language code where <<CODE>> is: Czech: CS Danish: DA Dutch: NL English: EN Finnish: FI French: FR German: DE Hungarian: HU Italian: IT Japanese: JA Korean: KO Norwegian Bokmal: NB Polish: PL Portuguese: PT Russian: RU Simplified Chinese: zh_cn Slovak: SK Spanish: ES Swedish: SV Thai: TH Traditional Chinese: zh_tw Turkish: TR InstallDir=<<PATH>> Destination folder into which the setup program will install. When installing to a host that already has an installation of SAP Crystal Server, the value of InstallDir will be automatically set to the same path as the existing installation. The use of Unicode characters in the destination folder is not supported. The use of Unicode characters in the destination folder is not supported. Ensure that the destination folder is not the same folder in which the installation program has been extracted (do not install to the current working directory when running the installation program from the current working directory). Installation 2015 SAP SE or an SAP affiliate company. All rights reserved. 39

40 Parameter SelectedLanguagePacks=<<CODE>> Description Installs language support for users and administrators to interact with SAP Crystal Server in a supported language. If more than one language pack is to be installed, use a semi-colon delimited list without spaces, within quotes, to separate each code. In the following example, language support for English, Japanese, Simplified Chinese, and Thai will be installed: SelectedLanguagePacks="en;ja;zh_CN;th" Substitute the following language codes where <<CODE>> is: Czech: CS Danish: DA Dutch: NL English: EN Finnish: FI French: FR German: DE Hungarian: HU Italian: IT Japanese: JA Korean: KO Norwegian Bokmal: NB Polish: PL Portuguese: PT Russian: RU Simplified Chinese: zh_cn Slovak: SK Spanish: ES Swedish: SV Thai: TH Traditional Chinese: zh_tw Turkish: TR ChooseIntroscopeIntegration=<<V ALUE>> CMSPassword=<<PASSWORD>> CMSPasswordConfirm=<<PASSWORD>> Introscope_ent_host=<<HOSTNAME> > Introscope_ent_port=<<PORT>> Determines whether Introscope support will be enabled or not. To enable Introscope integration, set <<VALUE>> to integrate. To disable Introscope integration, set <<VALUE>> to nointegrate. Password to use for the CMS Administrator account. Substitute <<PASSWORD>> with the password. Password confirmation for the CMS Administrator account. Substitute <<PASSWORD>> with the password. Hostname of the Introscope server. Substitute <<HOSTNAME>> with the Introscope server hostname. Network TCP listening port number used by the Introscope server. Substitute <<PORT>> with the Introscope server port number SAP SE or an SAP affiliate company. All rights reserved. Installation

41 Parameter ChooseSMDIntegration=<<VALUE>> SMDAgent_host=<<HOSTNAME>> SMDAgent_port=<<PORT>> RegisteredUser=<<NAME>> RegisteredCompany=<<NAME>> ProductKey=<<KEY>> CMSPort=<<PORT>> ClusterKey=<<KEY>> ClusterKeyConfirm=<<KEY>> EnableServers=<<SWITCH>> LCMName=LCM_Repository Description Determines whether SAP Solution Manager Diagnostics (SMD) Agent support will be enabled or not. To enable SMD integration, set <<VALUE>> to integrate. To disable SMD integration, set <<VALUE>> to nointegrate. Hostname of the SMD Agent. Substitute <<HOSTNAME>> with the agent hostname. Network TCP listening port number used by the SMD Agent. Substitute <<PORT>> with the agent port number. Name of the user to whom the software is registered. Substitute <<NAME>> with the name. Name of the company to whom the software is registered. Substitute <<NAME>> with the name. Product license key issued when you purchased the software. Substitute <<KEY>> with the product key in the format XXXXX-XXXXXX-XXXXXX- XXXX. Network TCP listening port number used by the CMS for incoming connections. Substitute <<PORT>> with the port number. The default value is Cryptographic key used to encrypt secure CMS cluster communications. Substitute <<KEY>> with the key string. Cryptographic key conformation. Substitute <<KEY>> with the key string. Determines whether or not the CMS servers will be started automatically after the installation is complete. To enable servers automatically after the installation, set <<SWITCH>> to 1. To not enable the servers, so that they must be started manually at a later time, set <<SWITCH>> to 0. Hostname of the SAP Lifecycle management server. Do not change this value. LCMPort=<<PORT>> LCMUsername=LCM Network TCP listening port number used by the SAP Lifecycle management server. Substitute <<PORT>> with the port number. Username to access SAP Lifecycle management server. Do not change this value. LCMPassword=<<PASSWORD>> LCMPasswordConfirm=<<PASSWORD>> NewOrExpandLCM=<<VALUE>> User password to access SAP Lifecycle management server. Substitute <<PASSWORD>> with the password. User password confirmation. Substitute <<PASSWORD>> with the password. Determines whether or not the installation is a new LCM on a fresh server, or an expand installation used to create a CMS cluster. To perform a new installation, set <<VALUE>> to new. To perform an expand installation, set <<VALUE>> to expand. Installation 2015 SAP SE or an SAP affiliate company. All rights reserved. 41

42 Parameter SelectIntegratedDatabase=<<VALU E>> Description Determines whether or not the bundled database will be installed. To install the bundled database, set <<VALUE>> to 1. The bundled database is Microsoft SQL Server 2008 Express. The bundled database is IBM DB2. SIAName=<<NAME>> SIAPort=<<PORT>> TomcatConnectionPort=<<PORT>> TomcatShutdownPort=<<PORT>> TomcatRedirectPort=<<PORT>> InstallType=<<VALUE>> WebAppServerType=<<VALUE>> Features=<<CODE>> Name of the Server Intelligence Agent (SIA) node create for this installation. The name must be alphanumeric and cannot start with a number. Substitute <<NAME>> with the SIA name. Network TCP listening port number used by the SIA. Substitute <<PORT>> with the port number. Network TCP listening port number used by the Tomcat web application server for inbound connections. Substitute <<PORT>> with the port number. Network TCP listening port number used by the Tomcat web application server to trigger a server shutdown. Substitute <<PORT>> with the port number. Network TCP listening port number used by the Tomcat web application server for server request redirection. Substitute <<PORT>> with the port number. Determines whether or not the installation program should select installable components based upon the default settings, custom settings (allows you to select components), or settings used for installing web tier components (when installing to a web application server). To install the default components, set <<VALUE>> to default. To install a custom selection of components, set <<VALUE>> to custom. To install a web tier components, set <<VALUE>> to webtier. Sets the web application server to use for web application deployment. The default value is tomcat. Before deploying web applications with the WDeploy tool, you must still manually update the WDeploy configuration files. For more information, see the SAP BusinessObjects Business Intelligence platform Web Application Deployment Guide. List of components to install. Used in combination with the InstallType=custom or InstallType=webtier parameter. This parameter should not be modified manually. Features must be selected through the installation program user interface when creating a response file. For a complete list of feature codes, see Feature codes [page 43]. Table 8: Installation option parameters specific to Windows Parameter SQLExpressAdminPassword=<<PASSW ORD>> SQLExpressBOEUserName=<<USERNAM E>> SQLExpressBOEUserPassword=<<PAS SWORD>> Description Admin password to assign to the Microsoft SQL Server sa administrative user account. Substitute <<PASSWORD>> with the password. Username to assign to the Microsoft SQL Server user account used by the CMS. Substitute <<USERNAME>> with the username. Admin password to assign to the Microsoft SQL Server user account used by the CMS. Substitute <<PASSWORD>> with the password SAP SE or an SAP affiliate company. All rights reserved. Installation

43 Table 9: Installation option parameters specific to Unix for Linux Parameter DB2PortNumber=<<PORT>> Description Network TCP listening port number used by the DB2 database server bundled with SAP Crystal Server. Substitute <<PORT>> with the database server port number Feature codes The following feature codes to select features for installation. Multiple features are separated with commas. root: install all features WebTier: install all web tier components JavaWebApps1 Java Web Applications tomcat70 Tomcat 7.0 Servers: install all server components PlatformServers: install all platform servers CMS (Central Management Server) FRS (File Repository Servers) PlatformServers.IntegratedDB.DB2 (installs bundled IBM DB2 server) DashboardAnalyticsServer (BI Workspace) PlatformServers.EventServer PlatformServers.SystemLandscapeSupplier (SLD) PlatformServers.WebAppContainerService (WACS) AdaptiveProcessingServer (platform processing) AdaptiveJobServer (scheduling) Subversion (Subversion version control system) ConnectionServices: install connectivity components ConnectionProcService DataFederatorServices: install all data federation components DataFederatorQueryService CrystalReportsServers: install all SAP Crystal Reports components CrystalReportsProcServices (SAP Crystal Reports Processing) CrystalReportSchedulingServices CrystalReport2011ProcServices (SAP Crystal Reports 2011 Processing) CrystalReport2011SchedulingServices (SAP Crystal Reports 2011 Scheduling) XcelsiusServers (Dashboard Design) AdministratorTools: install all administrator tools UpgradeManager (Upgrade management tool) If you plan to use the upgrade management tool to upgrade objects from an older version of SAP BusinessObjects Business Intelligence platform, see Object types and feature requirements [page 8]. Installation 2015 SAP SE or an SAP affiliate company. All rights reserved. 43

44 DataAccess install all database access components DataAccess.DataFederator DataAccess.HPNeoView DataAccess.MySQL DataAccess.GenericJDBC DataAccess.GenericODBC DataAccess.GenericOLEDB DataAccess.OptionalDataDirectODBC DataAccess.MaxDB DataAccess.Salesforce (Salesforce.com) DataAccess.Netezza DataAccess.Microsoft_AnalyticalServices DataAccess.MicrosoftExchange DataAccess.MicrosoftOutlook DataAccess.Microsoft_SQLServer DataAccess.Microsoft_Access DataAccess.Ingres DataAccess.Greenplum DataAccess.IBMDB2 DataAccess.Informix DataAccess.ProgressOpenEdge DataAccess.Oracle DataAccess.Sybase DataAccess.Teradata DataAccess.SAPBW DataAccess.SAP (security and data access for SAP BW and R/3 systems) DataAccess.PersonalFiles DataAccess.JavaBean DataAccess.OpenConnectivity DataAccess.HSQLDB DataAccess.Derby DataAccess.Essbase DataAccess.MyCube (OLAP Cube) DataAccess.XML DataAccess.ADO.NET DataAccess.COMData DataAccess.DataSet (Dataset Consumer) DataAccess.SymantecACT DataAccess.BDE (IDAPI Database DLL) DataAccess.CDO (Crystal Data Objects) DataAccess.FieldDefinitions DataAccess.FileSystem DataAccess.NTEventLog SAP SE or an SAP affiliate company. All rights reserved. Installation

45 DataAccess.WebActivityLog DataAccess.Btrieve (Pervasive Database Driver) DataAccess.dBase DataAccess.UWSC (Universal Web Services Connector (UWSC)) Samples: install sample reports and data sources Response file example The following example response file contains options for installing SAP Crystal Server. Example In this example, the response file is named $HOME/response.ini. ### Choose to Integrate Introscope Enterprise Manager: integrate or nointegrate chooseintroscopeintegration=nointegrate ### Choose to Integrate Solution Manager Diagnostics (SMD) Agent: integrate or nointegrate choosesmdintegration=nointegrate ### CMS administrator password cmspassword=password1 ### #property.cmspasswordconfirm.description# cmspasswordconfirm=password1 ### CMS connection port cmsport=6400 ### CMS cluster key ClusterKey=Crypto1 ### #property.clusterkeyconfirm.description# ClusterKeyconfirm=Crypto1 ### Choose to start servers after install: 0 or 1 enableservers=1 ### Installation directory installdir=/opt/sap/sap_bobj/ ### Choose install type: default, custom, webtier installtype=custom ### Introscope Enterprise Manager Hostname introscope_ent_host=$introscopeagententerprisemanagerhost ### Introscope Enterprise Manager Port number introscope_ent_port=$introscopeagententerprisemanagerport ### LCM server name lcmname=lcm_repository ### LCM password lcmpassword=password1 ### #property.lcmpasswordconfirm.description# lcmpasswordconfirm=password1 ### LCM port lcmport=3690 ### LCM user name lcmusername=lcm ### Choose install mode: new, expand neworexpandinstall=new ### Product keycode productkey=xxxxx-xxxxxxx-xxxxxxx-xxxxxxx-xx ### Registered Company registeredcompany=default_company ### Registered User registereduser=default_user ### Language Packs Selected to Install selectedlanguagepacks=en ### Setup UI language Installation 2015 SAP SE or an SAP affiliate company. All rights reserved. 45

46 setupuilanguage=en ### SIA node name sianame=sia1 ### SIA connector port siaport=6410 ### SMD Agent Hostname smdagent_host=$smdagenthost ### SMD Agent Port Number smdagent_port=$smdagentport ### #propertydeclaration.sqlexpressadminpassword.description# sqlexpressadminpassword=password1 ### #propertydeclaration.sqlexpressboeusername.description# sqlexpressboeusername=boeuser ### #propertydeclaration.sqlexpressboeuserpassword.description# sqlexpressboeuserpassword=password1 ### #propertydeclaration.tomcatconnectionport.description# tomcatconnectionport=8080 ### #propertydeclaration.tomcatredirectport.description# tomcatredirectport=8443 ### #propertydeclaration.tomcatshutdownport.description# tomcatshutdownport=8005 ### #propertydeclaration.wacsport.description# wacsport=6405 ### Available features ### ### root ### WebTier ### JavaWebApps1 ### tomcat70 ### Servers ### PlatformServers ### CMS ### FRS ### PlatformServers.IntegratedDB ### DashboardAnalyticsServer ### PlatformServers.EventServer ### PlatformServers.SystemLandscapeSupplier ### PlatformServers.WebAppContainerService ### AdaptiveProcessingServer ### AdaptiveJobServer ### Subversion ### ConnectionServices ### ConnectionProcService ### DataFederatorServices ### DataFederatorQueryService ### AdvancedAnalysisServices ### MultidimensionalAnalysisServices ### BExWebApplicationsService ### CrystalReportsServers ### CrystalReportsProcServices ### CrystalReportSchedulingServices ### CrystalReport2011ProcServices ### CrystalReport2011SchedulingServices ### ExportSupport ### Export.MicrosoftMail ### Export.LotussMail ### Export.Lotuss ### Export.ExchangeFolders ### Export.Application ### Export.HTML ### Export.ODBC ### Export.Record ### Export.ReportDefinition ### WebIServers ### WebIProcServer ### WebISchedulingServices ### XcelsiusServers ### MobileServers SAP SE or an SAP affiliate company. All rights reserved. Installation

47 ### IntegrationServers ### SiebelSignOnServer ### BWPublisherServer ### AdministratorTools ### UpgradeManager ### DeveloperTools ### BOE64bitNETSDK ### DataAccess ### DataAccess.DataFederator ### DataAccess.HPNeoView ### DataAccess.MySQL ### DataAccess.GenericJDBC ### DataAccess.GenericODBC ### DataAccess.GenericOLEDB ### DataAccess.OptionalDataDirectODBC ### DataAccess.MaxDB ### DataAccess.Salesforce ### DataAccess.Netezza ### DataAccess.Microsoft_AnalyticalServices ### DataAccess.MicrosoftExchange ### DataAccess.MicrosoftOutlook ### DataAccess.Microsoft_SQLServer ### DataAccess.Microsoft_Access ### DataAccess.Ingres ### DataAccess.Greenplum ### DataAccess.IBMDB2 ### DataAccess.Informix ### DataAccess.ProgressOpenEdge ### DataAccess.Oracle ### DataAccess.Sybase ### DataAccess.Teradata ### DataAccess.SAPBW ### DataAccess.SAP ### DataAccess.PersonalFiles ### DataAccess.JavaBean ### DataAccess.OpenConnectivity ### DataAccess.HSQLDB ### DataAccess.Derby ### DataAccess.Essbase ### DataAccess.Peoplesoft ### DataAccess.JDEdwards ### DataAccess.Siebel ### DataAccess.OracleEBS ### DataAccess.Universe ### DataAccess.MyCube ### DataAccess.XML ### DataAccess.ADO.NET ### DataAccess.COMData ### DataAccess.DataSet ### DataAccess.SymantecACT ### DataAccess.BDE ### DataAccess.CDO ### DataAccess.FieldDefinitions ### DataAccess.FileSystem ### DataAccess.NTEventLog ### DataAccess.WebActivityLog ### DataAccess.Btrieve ### DataAccess.dBase ### DataAccess.UWSC ### Samples ### Help features=javawebapps1,tomcat70,webtier,cms,frs,platformservers.integrateddb,dashbo ardanalyticsserver,platformservers.eventserver,platformservers.systemlandscapesupp lier,platformservers.webappcontainerservice,adaptiveprocessingserver,adaptivejobse rver,subversion,platformservers,connectionprocservice,connectionservices,datafeder atorqueryservice,datafederatorservices,multidimensionalanalysisservices,bexwebappl icationsservice,advancedanalysisservices,crystalreportsprocservices,crystalreports chedulingservices,crystalreport2011procservices,crystalreport2011schedulingservice Installation 2015 SAP SE or an SAP affiliate company. All rights reserved. 47

48 s,export.microsoftmail,export.lotussmail,export.lotuss,export.exchangefold ers,export.application,export.html,export.odbc,export.record,export.reportdefiniti on,exportsupport,crystalreportsservers,webiprocserver,webischedulingservices,webis ervers,xcelsiusservers,mobileservers,siebelsignonserver,bwpublisherserver,integrat ionservers,servers,upgrademanager,administratortools,boe64bitnetsdk,developertools,dataaccess.datafederator,dataaccess.hpneoview,dataaccess.mysql,dataaccess.generic JDBC,DataAccess.GenericODBC,DataAccess.GenericOLEDB,DataAccess.MaxDB,DataAccess.Sa lesforce,dataaccess.netezza,dataaccess.microsoft_analyticalservices,dataaccess.mic rosoftexchange,dataaccess.microsoftoutlook,dataaccess.microsoft_sqlserver,dataacce ss.microsoft_access,dataaccess.ingres,dataaccess.greenplum,dataaccess.ibmdb2,dataa ccess.informix,dataaccess.progressopenedge,dataaccess.oracle,dataaccess.sybase,dat aaccess.teradata,dataaccess.sapbw,dataaccess.sap,dataaccess.personalfiles,dataacce ss.javabean,dataaccess.openconnectivity,dataaccess.hsqldb,dataaccess.derby,dataacc ess.essbase,dataaccess.peoplesoft,dataaccess.jdedwards,dataaccess.siebel,dataacces s.oracleebs,dataaccess.universe,dataaccess.mycube,dataaccess.xml,dataaccess.ado.ne T,DataAccess.COMData,DataAccess.DataSet,DataAccess.SymantecACT,DataAccess.BDE,Data Access.CDO,DataAccess.FieldDefinitions,DataAccess.FileSystem,DataAccess.NTEventLog,DataAccess.WebActivityLog,DataAccess.Btrieve,DataAccess.dBase,DataAccess.UWSC,Sam ples,help SAP SE or an SAP affiliate company. All rights reserved. Installation

49 6 Post-Installation This section describes the activities that should be performed after the installation program has finished, to test that the installation was successful. 6.1 Launching the CMC Verify that the installation was successful by logging on to the Central Management Console (CMC). The CMC is used to administer servers, users and groups, rights, and security policies. For more information on using the CMC, see the SAP BusinessObjects Business Intelligence Platform Administrator Guide. Launch the CMC by going to: Start Programs SAP Crystal Server 2011 SAP BusinessObjects Enterprise SAP BusinessObjects Enterprise Central Management Console. If you have installed a dedicated web application server, you can enter the web application server's URL to access the CMC. Use the following URL: Substitute <<WEB_APP_SERVER>> for the hostname of the web application server and <<PORT>> for the web application server's listening port. If you are using a custom web application server root context or BOE.war web application context, the URL will be different. If you are using Internet Explorer, you may receive several Internet Explorer Enhanced Security Configuration warnings because the new server is not yet added to the list of trusted sites. Click Add to add the local web server to the list of trusted web sites. If your server is not using SSL encryption, deselect Require server verification ( for all sites in this zone. Log on as the Administrator user by typing Administrator into the User Name field and entering the administrative password that you entered into the installation program. 6.2 Troubleshooting login issues If you are unable to log on to the CMC, evaluate the following possible causes: 1. Is a firewall blocking the CMS port number (default 6400) or the web application server port? 2. Is the URL correct?? The default URL to access the CMC is: Post-Installation 2015 SAP SE or an SAP affiliate company. All rights reserved. 49

50 Substitute <<WEB_APP_SERVER>> for the hostname of the web application server and <<PORT>> for the web application server's listening port. If you are using a custom web application server root context or BOE.war web application context, the URL will be different. 3. Is the correct method specified in the Authentication field? The default authentication type is Enterprise, referring to native SAP Crystal Server authentication system. If you are using an LDAP single sign-on authentication system, select the system instead. 4. Did you provide the correct user credentials in the User Name and Password fields on the CMC login screen? The name of the administrative account is Administrator. The password configured when SAP BusinessObjects Business Intelligence platform was installed. 5. Is the Server Intelligence Agent (SIA) is running. Start the CCM with the ccm.sh script. If the SIA is not running, start it. 6. Ensure that the database server(s) used for the CMS system and Auditing Data Store databases are running, and that the network connection from the CMS to the database is working. 7. If you are attempting to connect to a CMS cluster using format, and this is your first attempt to connect to the cluster, the CMC will not know which CMS servers belong to the cluster. In this case, you need to specify a list of CMS servers in the web.xml, found in the WEB-INF folder of the CMC web application WAR file. Follow the instructions in the cms.clusters section of web.xml for more details. It is also possible to specify CMS cluster information for the BI launch pad by modifying its corresponding web.xml file. If none of these solutions work, consider repairing or reinstalling the software or contacting SAP BusinessObjects support at Creating additional Adaptive Processing Servers The installation program installs one Adaptive Processing Server (APS) per host system. Depending on the features that you've installed, this APS may host a large number of services, such as the Monitoring Service, Lifecycle Management Service, Multi-Dimensional Analysis Service (MDAS), Publishing Service, and others. If you are installing a production environment, do not use the default APS. Instead, it is highly recommended that once the installation process is complete, you perform a system sizing to determine: The type and number of APS services. The distribution of services across multiple APS servers. The optimal number of APS servers. Multiple APS servers provide redundancy, better performance, and higher reliability. The distribution of APS servers across multiple nodes. Create new APS server instances as determined by the sizing process. For example, if the outcome of your sizing happens to suggest the creation of one APS for each service category, then may end up creating eight APS servers. One for each service category: Advanced Analysis Services, Connectivity Services, Core Services, Crystal Reports Services, Dashboard Design Services, Data Federation Services, Lifecycle Management Services, and Interactive Analysis Services SAP SE or an SAP affiliate company. All rights reserved. Post-Installation

51 6.4 Deploying web applications The installation only installs web applications to Tomcat 7. If the installation program did not automatically deploy web applications to your web application server, you must deploy the web applications manually with the WDeploy tool, or with the web application server administrative console. The WDeploy tool automates the deployment of web applications to supported web application servers. For more information on using WDeploy, see the SAP BusinessObjects Business Intelligence Platform Web Application Deployment Guide. 6.5 Post-install diagnostic checks You can run the Monitoring Tool at any time to run a diagnostics check and look for problems. To access the Monitoring Tool in order to run diagnostic tests, log on to the Central Management Console (CMC), select the Monitoring screen, and click the Probes tab. 6.6 Making changes to SAP Crystal Server To modify SAP Crystal Server These instructions describe the process to modify your SAP Crystal Server installation by adding or removing installed features. It is recommended that you back up the CMS system database before modifying SAP Crystal Server. The CMS must be running in order to modify an SAP Crystal Server installation. 1. Change directory to the <<BOE_INSTALL_DIR>> folder. 2. Run the command:./modifyorremoveproducts.sh Log files, configuration files for web applications, and web applications will not be removed by the removal program. Folders left after removing a corresponding feature can be removed manually later with the rm command. 3. Select the installation to be modified. Post-Installation 2015 SAP SE or an SAP affiliate company. All rights reserved. 51

52 4. Select the Modify option. 5. Ensure that all features you want available are selected. Ensure that features you do not want installed are deselected. Expand the highlighted feature in the selection tree by pressing the keyboard spacebar. Use the arrow keys to navigate up or down. Toggle feature selections with the X key. When you are satisfied with the selected features, press Enter. 6. If you are modifying a server with a CMS installed, press Enter to apply the changes. If you are modifying a server that uses a remotely installed CMS, enter the hostname, port, and an administrative account username and password. 7. When the changes have been made, press Enter to return to the command-line. The installation has been updated To repair SAP Crystal Server These instructions describe the process to repair an SAP Crystal Server installation. This process restores the files and settings originally configured by the setup program. It is recommended that you back up the CMS system database before repairing SAP Crystal Server. The CMS must be running in order to modify an installation. 1. Change directory to the <<BOE_INSTALL_DIR>> folder. 2. Run the command:./modifyorremoveproducts.sh Log files, configuration files for web applications, and web applications will not be removed by the removal program. Any remaining folders can be removed manually with the rm command. 3. Select the installation to be repaired. 4. Select the Repair option. 5. Enter the hostname, port, and an administrative account username and password. 6. When the repair is finished, press Enter to return to the command-line. The installation has been repaired, restoring your system to its original configuration To remove SAP Crystal Server These instructions describe the process to permanently uninstall SAP Crystal Server from a system. It is recommended that you back up the CMS database before removing SAP Crystal Server SAP SE or an SAP affiliate company. All rights reserved. Post-Installation

53 Add-on products that with dependencies on other products should be removed before the product on which they depend. For example, for servers with SAP Crystal Server Explorer installed, SAP Crystal Server Explorer should be removed first, as it will not function without SAP Crystal Server. Removing SAP Crystal Server removes the core product plus any installed maintenance packages. To remove maintenance packages individually, see the installation guides for those maintenance packages. The following items will remain: The repository database, as it may be shared with other programs The file repository folder, as it may contain user data Web applications deployed to a web application server will not be undeployed. Use the WDeploy command or the web application server administrative console to undeploy web applications. Web application files customized to an individual web application server Configuration files These items can be manually removed later by an administrator, if required. 1. Stop all server processes. Change directory to the <<BOE_INSTALL_DIR>>/sap_bobj folder and run the command:./ccm.sh stop all Alternatively, run the command:./stopservers 2. If you are using the DB2 database bundled with SAP Crystal Server, stop DB2. For example, run the command:./db2shutdown.sh 3. If you are using the Tomcat web application server bundled with SAP Crystal Server, stop Tomcat. For example, run the command:./tomcatshutdown.sh 4. Change directory to the <<BOE_INSTALL_DIR>> folder. For example, run the following command: cd.. 5. Run the command:./modifyorremoveproducts.sh Post-Installation 2015 SAP SE or an SAP affiliate company. All rights reserved. 53

54 Log files, configuration files for web applications, and web applications will not be removed by the removal program. Any remaining folders can be removed manually with the rm command. 6. Select the installation to remove. 7. Select the Remove option. The software has been removed from the system. 6.7 When the administrator account password is lost If the credentials for the SAP Crystal Server administrator account are lost, consider the following potential resolutions: If another administrative account is available, use it to change the password for the SAP Crystal Server administrator account SAP SE or an SAP affiliate company. All rights reserved. Post-Installation

55 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 wilful 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: Important Disclaimers and Legal Information 2015 SAP SE or an SAP affiliate company. All rights reserved. 55

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