SAP Crystal Server Installation Guide for Windows SAP Crystal Server 2011 Feature Pack 3

SAP Crystal Server Installation Guide for Windows ■ SAP Crystal Server 2011 Feature Pack 3 2012-08-13 Copyright © 2012 SAP AG. All rights reserved...
Author: Anabel Russell
4 downloads 4 Views 821KB Size
SAP Crystal Server Installation Guide for Windows ■ SAP Crystal Server 2011 Feature Pack 3

2012-08-13

Copyright

© 2012 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360°, B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. 2012-08-13

Contents

3

Chapter 1

Document History...................................................................................................................5

Chapter 2

Introduction.............................................................................................................................7

2.1 2.2 2.3 2.4

About this Document...............................................................................................................7

Chapter 3

Planning..................................................................................................................................9

3.1 3.1.1 3.1.2 3.2 3.3 3.4

Upgrade support....................................................................................................................10

Chapter 4

Preparation............................................................................................................................15

4.1 4.1.1 4.1.2 4.2 4.2.1 4.2.2 4.3

System requirements.............................................................................................................16

Chapter 5

Installation.............................................................................................................................23

5.1 5.2 5.2.1 5.2.2 5.2.3

To download the installation program.....................................................................................23

Purpose...................................................................................................................................7 Integration................................................................................................................................7 Constraints..............................................................................................................................8

Object types and feature requirements..................................................................................11 Product co-existence.............................................................................................................11 Web application servers.........................................................................................................12 Web servers..........................................................................................................................13 Database servers...................................................................................................................13

Account permissions..............................................................................................................16 Network permissions.............................................................................................................17 Preparing the CMS system or Auditing Data Store database.................................................17 Extra requirements for IBM DB2............................................................................................19 Extra requirements for Sybase...............................................................................................20 Final checklist.........................................................................................................................20

To run an interactive installation.............................................................................................24 To select an install type..........................................................................................................25 While the installation program runs.........................................................................................36 When installation is complete.................................................................................................37

2012-08-13

Contents

5.3 5.3.1 5.3.2

To run a silent installation.......................................................................................................37

Chapter 6

Post-Installation....................................................................................................................53

6.1 6.2 6.3 6.4 6.5 6.6 6.6.1 6.6.2 6.6.3 6.7

Launching the CMC...............................................................................................................53

Chapter 7

Installing SAP Crystal Server 2011 Client Tools...................................................................61

7.1 7.1.1 7.1.2 7.1.3 7.1.4 7.2 7.3 7.3.1 7.3.2 7.4 7.4.1 7.4.2 7.4.3 7.5

Desktop client applications.....................................................................................................62

Appendix A

More Information...................................................................................................................77

Index

4

Command-line switch parameters..........................................................................................38 Installation option parameters ................................................................................................41

Troubleshooting login issues..................................................................................................53 Creating additional Adaptive Processing Servers...................................................................54 Deploying web applications....................................................................................................55 Post-install diagnostic checks.................................................................................................55 Making changes to SAP Crystal Server.................................................................................55 To modify SAP Crystal Server................................................................................................56 To repair SAP Crystal Server.................................................................................................57 To remove SAP Crystal Server..............................................................................................58 When the administrator account password is lost..................................................................58

Business View Manager.........................................................................................................62 Information design tool...........................................................................................................62 Translation Management Tool................................................................................................63 Data Federation Administration Tool.......................................................................................63 To run an interactive installation of Client Tools......................................................................64 To run a silent installation of Client Tools...............................................................................65 Command-line silent install of Client Tools.............................................................................66 Installation option parameters for Client Tools........................................................................69 Making changes to Client Tools.............................................................................................74 To modify Client Tools...........................................................................................................74 To repair a Client Tools installation.........................................................................................75 To remove Client Tools..........................................................................................................75 Upgrading Client Tools...........................................................................................................76

79

2012-08-13

Document History

Document History

Version

Date

Description

SAP Crystal Server 2011

Nov. 2011

First release of this document

SAP Crystal Server 2011 Feature Pack 3

5

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)

2012-08-13

Document History

6

2012-08-13

Introduction

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 Windows: for use with Microsoft Windows operating systems (this document). •

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: ser vice.sap.com/bosap-support.

2.3 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. Note: SAP Crystal Server is a variant of the BI platform so the recommendations here are applicable to both products.

7

2012-08-13

Introduction

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.

8

2012-08-13

Planning

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 Microsoft SQL Server 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. Note: 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

9

2012-08-13

Planning

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. 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 Feature Pack 3 , 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 Features new to this release include: • Lifecycle Management • Mobile Support • Dashboards Server support • Language Support • WDeploy support

10

2012-08-13

Planning

3.1.1 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. Object type

Required feature

BI workspaces (Dashboards)

BI workspace Services

Crystal reports

none

Explorer

none

Lifecycle management console (LifeCycle Manager) data

Platform Processing Services or Platform Scheduling Services

Universes, connections

Connectivity Processing Services

Mobile

CMS plugin for Moible

3.1.2 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. Note: 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.

11

2012-08-13

Planning

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 6.0 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 requirements. Note: 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 6.0 does not meet your organization's requirements, the following web application servers are supported: • • • • •

JBoss SAP NetWeaver Application Server Tomcat 7.0 WebLogic WebSphere

For a detailed list of supported web application servers, versions, and patch levels, consult the Supported Platforms Guide available at http://service.sap.com/bosap-support. Note: •

12

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.

2012-08-13

Planning



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: For a detailed list of supported web servers, versions, and patch levels, consult the Supported Platforms Guide available at http://service.sap.com/bosap-support.

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. Microsoft SQL Server 2008 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 • IBM DB2 • Oracle • MaxDB • Sybase • Microsoft SQL Server using ODBC Note: If you intend to use Microsoft SQL Server, ensure that the account being used to install has the appropriate privileges. Microsoft SQL Server installation requires that the account being used is a member of the Windows Administrators group, and that the default privileges assigned to the

13

2012-08-13

Planning

Administrators group have not been modified. For more information, see Microsoft SQL Server 2008 knowledge base article number 2000257: SQL Server 2008 installation will fail if the setup account does not have certain user rights. Note: 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 http://service.sap.com/bosap-support.

14

2012-08-13

Preparation

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 http://service.sap.com/bosap-support. • To download SAPCAR, go to http://service.sap.corp/bosap-support > Software Downloads > Support Packages and Patches > Browse our Download Catalog > SAP Technology Components > SAPCAR. • To download SAP HOST AGENT, go to http://service.sap.corp/bosap-support > 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").

15

2012-08-13

Preparation

4.1 System requirements Use the following guidelines when you install SAP Crystal Server: • 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 http://service.sap.com/bosap-support.

4.1.1 Account permissions To install SAP Crystal Server on a Windows host, a user must have the following permissions: Category

Required access

Operating system

Local administrative privileges.

Network

• • •

Database

• •

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

Note: 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.

16

2012-08-13

Preparation

4.1.2 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. • Each machine must use a fixed hostname. Fully-qualified hostnames are supported. Note: 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.

4.1.2.1 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

17

2012-08-13

Preparation

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:

18

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)

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)

2012-08-13

Preparation

Database

Information required by installation program

MaxDB

• • • • • •

Database name Server hostname Port number (default is 7210) Account username Account password "Reset existing database" checkbox (recommended setting)



Service name Note: •

Sybase

• • • •

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)

4.2.1 Extra requirements for IBM DB2 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: http://www.ibm.com/developerworks/data/library/techar ticle/0212wieser/0212wieser.html.



19

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

2012-08-13

Preparation



Ensure that the CMS system database is not partitioned. The Auditing Data Store database may be partitioned.

4.2.2 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-8.

4.3 Final checklist Prior to installing SAP Crystal Server, review the following checklist. • Have you decided on the installation destination folder? Note: • •

• • •



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? 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 1024 × 768.

20

2012-08-13

Preparation

Note: The SAP Crystal Server setup program no longer installs Client Tools. Client Tools can only be installed with the dedicated Client Tools installation program.

21

2012-08-13

Preparation

22

2012-08-13

Installation

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 https://service.sap.com/bosap-support > Software Downloads. 2. On the "Find your software" tab, under the "A–Z Index", select Installations and Upgrades. 3. Select C > Crystal Server > Crystal Server 2011. 4. Select Installation and Upgrade and then select your platform. 5. Select all of the objects titled "SBOP BI PLATFORM SERVER" plus any additional add-on products you require, then follow the instructions on the website to download and extract the objects.

23

2012-08-13

Installation

Note: 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 https://service.sap.com/bosap-support > Software Downloads. On the "Find your software" tab, under the "A–Z Index", click Support Packages and Patches. For more information on installing Support Packages and Patches, see the SAP BusinessObjects Business Intelligence Platform Upgrade Master Guide.

5.2 To run an interactive installation Before installing, ensure that the account being used has Administrator privileges. The installation requires that the account being used is a member of the Windows Administrators group, and that the default privileges assigned to the Administrators group have not been modified. When the installation program starts, a series of prerequisite checks are performed. The result of this test is displayed for your information. If your system does not meet the minimum requirements, the installation program will not install SAP Crystal Server. Microsoft C++ redistributable components will be installed automatically if they are not found. 1. Log in at the console or use Microsoft Remote Desktop connection with a minimum screen resolution of 1024 × 768. 2. Locate the installation program. If you are installing from a physical media, look for setup.exe in the top-level folder. If you are installing from a compressed download, extract it and locate set up.exe. 3. Run setup.exe by double-clicking it in Windows Explorer or calling it from the command-line. Note: If your operating system is Windows Server 2008, verify with your IT administrator whether UAC (User Account Control) is enabled. If UAC is enabled, then right-click setup.exe and select Run as administrator. From the command-line, open a command prompt and enter: runas /user: setup.exe. 4. 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. Note: 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 Windows components configured by the installation program, such as Windows service names and Start menu shortcuts. These names cannot be changed later and are not affected by language settings once the installation is complete. 5. The installation program checks for required components. Review the results and decide whether to continue with the installation, or abort and correct any unmet requirements.

24

2012-08-13

Installation

If a dependency prerequisite condition is critical, the installation program will not allow the installation to proceed. If a missing or unsupported component is optional, you have the option to either continue with the installation or stop and correct the condition. The installation program will provide information on how to correct the condition. 6. Review the recommendations made by the installation program welcome screen. 7. Review the agreement and select I accept the License Agreement. 8. Enter the name, company, and the product keycode you purchased. Keep the keycode safe in case you need to re-install the product. 9. To install support for a language, select it from the list. Note: Carefully consider which languages need to be installed for your organization before installing them. 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 it is used if a problem is detected with an individual language. The "Choose Install Type" screen appears.

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

25

2012-08-13

Installation

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. 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. Note: • •

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.

5.2.1.1 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. Microsoft SQL Server 2008 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.

26

2012-08-13

Installation

Note: 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. 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 Feature Pack 3 web applications. If you do not have a web application server in place for use with SAP Crystal Reports Server 2011 Feature Pack 3, 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. Note: 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 Feature Pack 3 and a web application server on the same host in a production environment may decrease performance. Note: 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.

27

2012-08-13

Installation

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 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. Note: The CMS Administrator is a super-user account in the SAP Crystal Reports Server 2011 Feature Pack 3 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 and confirm the database administrator account password, and an Enterprise user account password. The Enterprise user name may be changed if you do not want to use the default. 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. If you're using an ODBC database driver, you must configure an ODBC data source. On older Windows operating system, such as Windows 2003 Server, a system ODBC DSN connection can be configured from: Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC). If you're using a newer Windows operating system, such as Windows 2008 Server or Windows 7, a system ODBC DSN can be configured from: Start > Control Panel > Administrative Tools > Data Sources (ODBC). 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 6.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.

28

2012-08-13

Installation

If you selected Web Application Container Server (WACS) in the feature list, review the "HTTP Listening Port" number for the Web Application Container Server to listen for incoming connections from web clients. The web application server and WACS must be able to receive incoming connections on the given port numbers, so ensure that your firewall is configured appropriately. 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. Note: 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 Feature Pack 3, see "To enable SAP System Landscape Directory (SLD) support". • For information on installing the SAP Host Agent after SAP Crystal Reports Server 2011 Feature Pack 3 , 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 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. Note: 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”.

29

2012-08-13

Installation

5.2.1.2 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. Note: 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".



Developer Tools If you plan to develop your own applications with an SAP Crystal Server Software Development Kit (SDK), install the Developer Tools feature.



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.

30

2012-08-13

Installation

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.

5.2.1.2.1 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. Note: 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 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. Note: 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.

31

2012-08-13

Installation

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 and confirm the datase administrator account password, and an Enterprise user account password. The Enterprise user name may be changed if you do not want to use the default. 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. If you're using an ODBC database driver, you must configure an ODBC data source. On older Windows operating system, such as Windows 2003 Server, a system ODBC DSN connection can be configured from: Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC). If you're using a newer Windows operating system, such as Windows 2008 Server or Windows 7, a system ODBC DSN can be configured from: Start > Control Panel > Administrative Tools > Data Sources (ODBC). 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 6.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. If you selected Web Application Container Server (WACS) in the feature list, review the "HTTP Listening Port" number for the Web Application Container Server to listen for incoming connections from web clients. The web application server and WACS must be able to receive incoming connections on the given port numbers, so ensure that your firewall is configured appropriately. 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. Note: 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".

32

2012-08-13

Installation

• • •

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. 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. Note: 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.

5.2.1.2.2 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. Note: The appropriate database drivers must be installed and verified as working on the expand host. 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 a SAP Crystal Server SIA. 3. Enter connection information for the existing CMS.

33

2012-08-13

Installation

This includes the hostname and port number of the primary CMS, as well as the Administrator account password. Fully qualified domain names are supported. 4. Enter the CMS cluster key for the existing CMS host. Communication between some CMS components is encrypted to provide a higher level of security. The cluster key must match the key entered on the existing CMS host, to which you are attempting to connect. 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 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. Enter connection details for the CMS system database. If you are using the Microsoft SQL Server 2008 database bundled with SAP Crystal Server on the existing CMS, to which you are attempting to connect, you must configure a system ODBC DSN connection for the existing CMS system database. If you are using a different previously installed database, enter connection credentials for the CMS to connect to the database. 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. Configure the web application server. a. If you chose Install Tomcat application server and automatically deploy web applications and services to it above, 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. b. If you chose Install Web Application Container Server and automatically deploy web applications and services to it above, review the "HTTP Listening Port" number for the Web Application Container Server to listen for incoming connections from web clients. The web application server and WACS must be able to receive incoming connections on the given port numbers, so ensure that your firewall is configured appropriately. 9. 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. 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. Note: To use SAP Solution Manager Diagnostics (SMD), SAP Host Agent and SMD Agent must be installed:

34

2012-08-13

Installation

• • • •

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. Note: 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.

5.2.1.3 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. Note: •

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.

35

2012-08-13

Installation

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 6: the Apache Tomcat web application server. 2. If you chose to install the Tomcat 6 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. 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. Note: 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.

5.2.2 While the installation program runs The progress bar illustrates the progress of the installation as a whole. Note: 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.

36

2012-08-13

Installation

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

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

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 6400. 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 [...] •

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 parameter, where is the name of the response file.

37

2012-08-13

Installation

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 [...] 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 6400. 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 [...]

Note: 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 []

For a complete list of installation options, see Installation option parameters . For an example of a response file, see Response file example.

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 5-1: Installation program command-line switch parameters Switch parameter

Description

Example

-w

Writes a response file to , containing the options selected from the installation wizard.

setup.exe -w "C:\re sponse.ini"

-r

Reads installation options from a response file named .

38

setup.exe -r "C:\re sponse.ini"

2012-08-13

Installation

Switch parameter

Description

-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 switch parameter.

Example

setup.exe -q -r "C:\re sponse.ini"

5.3.1.1 To use a response file To use a response file, run the installation program with the -r 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:\re sponse.ini: setup.exe -r C:\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: \InstallData\logs\\InstallDU.log If the 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.

5.3.1.1.1 To write a response file To create a response file, run the installation program with the -w 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

39

2012-08-13

Installation

Once created, the response file can be updated with a text editor. Note: 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.

5.3.1.1.2 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:\re sponse.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\"

5.3.1.2 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\"

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:

40

2012-08-13

Installation

\InstallData\logs\\InstallDU.log If the 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.

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

41

2012-08-13

Installation

Table 5-2: Installation option parameters Parameter

SetupUILanguage=

Description

Determines which language for the installation program to use during the installation. Substitute the language code where is: • • • • • • • • • • • • • • • • • • • • • •

InstallDir=

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

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. Note: The use of Unicode characters in the destination folder is not supported. • •

42

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

2012-08-13

Installation

Parameter

Description

SelectedLanguagePacks=

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 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 ChooseIntroscopeIntegra tion=

Determines whether Introscope support will be enabled or not. To enable Introscope integration, set to integrate. To disable Introscope integration, set to nointegrate.

CMSPassword=

Password to use for the CMS Administrator account. Substitute with the password.

CMSPasswordConfirm=

Password confirmation for the CMS Administrator account. Substitute with the password.

Introscope_ent_host=

Hostname of the Introscope server. Substitute with the Introscope server hostname.

43

2012-08-13

Installation

Parameter

Description

Introscope_ent_port=

Network TCP listening port number used by the Introscope server. Substitute with the Introscope server port number.

ChooseSMDIntegration=

Determines whether SAP Solution Manager Diagnostics (SMD) Agent support will be enabled or not. To enable SMD integration, set to integrate. To disable SMD integration, set to nointegrate.

SMDAgent_host=

Hostname of the SMD Agent. Substitute with the agent hostname.

SMDAgent_port=

Network TCP listening port number used by the SMD Agent. Substitute with the agent port number.

RegisteredUser=

Name of the user to whom the software is registered. Substitute with the name.

RegisteredCompany=

Name of the company to whom the software is registered. Substitute with the name.

ProductKey=

Product license key issued when you purchased the software. Substitute with the product key in the format XXXXXXXXXXX-XXXXXX-XXXX.

CMSPort=

Network TCP listening port number used by the CMS for incoming connections. Substitute with the port number. The default value is 6400.

ClusterKey=

Cryptographic key used to encrypt secure CMS cluster communications. Substitute with the key string.

ClusterKeyConfirm=

Cryptographic key conformation. Substitute with the key string.

EnableServers=

Determines whether or not the CMS servers will be started automatically after the installation is complete. To enable servers automatically after the installation, set to 1. To not enable the servers, so that they must be started manually at a later time, set to 0.

LCMName=LCM_Repository

Hostname of the SAP Lifecycle management server. Note: Do not change this value.

LCMPort=

44

Network TCP listening port number used by the SAP Lifecycle management server. Substitute with the port number.

2012-08-13

Installation

Parameter

Description

LCMUsername=LCM

Username to access SAP Lifecycle management server. Note: Do not change this value.

LCMPassword=

User password to access SAP Lifecycle management server. Substitute with the password.

LCMPasswordConfirm=

User password confirmation. Substitute with the password.

NewOrExpandLCM=

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 to new. To perform an expand installation, set to expand.

SelectIntegratedDatabase=

Determines whether or not the bundled database will be installed. To install the bundled database, set to 1. The bundled database is Microsoft SQL Server 2008 Express.

SIAName=

Name of the Server Intelligence Agent (SIA) node create for this installation. The name must be alphanumeric and cannot start with a number. Substitute with the SIA name.

SIAPort=

Network TCP listening port number used by the SIA. Substitute with the port number.

TomcatConnectionPort=

Network TCP listening port number used by the Tomcat web application server for inbound connections. Substitute with the port number.

TomcatShutdownPort=

Network TCP listening port number used by the Tomcat web application server to trigger a server shutdown. Substitute with the port number.

TomcatRedirectPort=

Network TCP listening port number used by the Tomcat web application server for server request redirection. Substitute with the port number.

InstallType=

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 to default. To install a custom selection of components, set to cus tom. To install a web tier components, set to webtier.

45

2012-08-13

Installation

Parameter

Description

WebAppServerType=

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.

Features=

List of components to install. Used in combination with the Install Type=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.

Table 5-3: Installation option parameters specific to Windows Parameter

Description

SQLExpressAdminPassword=

Admin password to assign to the Microsoft SQL Server sa administrative user account. Substitute with the password.

SQLExpressBOEUserName=

Username to assign to the Microsoft SQL Server user account used by the CMS. Substitute with the username.

SQLExpressBOEUserPass word=

Admin password to assign to the Microsoft SQL Server user account used by the CMS. Substitute with the password.

5.3.2.1 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 • •



Servers: install all server components •

46

JavaWebApps1 Java Web Applications tomcat60 Tomcat 6.0 PlatformServers: install all platform servers

2012-08-13

Installation



• • •

CMS (Central Management Server) FRS (File Repository Servers) PlatformServers.IntegratedDB (installs bundled Microsoft SQL Server 2008 Express)

• • • • • • •

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 •



DataFederatorServices: install all data federation components •





DataFederatorQueryService

CrystalReportsServers: install all SAP Crystal Reports components • • • •



ConnectionProcService

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) Note: 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".



DeveloperTools: install all developer tool components •



DataAccess install all database access components • • • • • • • •

47

BOE64bitNETSDK (64-bit SAP BusinessObjects Business Intelligence platform .NET SDK)

DataAccess.DataFederator DataAccess.HPNeoView DataAccess.MySQL DataAccess.GenericJDBC DataAccess.GenericODBC DataAccess.GenericOLEDB DataAccess.OptionalDataDirectODBC DataAccess.MaxDB

2012-08-13

Installation

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •

48

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 DataAccess.WebActivityLog DataAccess.Btrieve (Pervasive Database Driver) DataAccess.dBase DataAccess.UWSC (Universal Web Services Connector (UWSC))

Samples: install sample reports and data sources

2012-08-13

Installation

5.3.2.2 Response file example The following example response file contains options for installing SAP Crystal Server. Example: In this example, the response file is named C:\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=C:\Program Files (x86)\SAP BusinessObjects\ ### 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

49

2012-08-13

Installation

### Registered User registereduser=default_user ### Language Packs Selected to Install selectedlanguagepacks=en ### Setup UI language 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 ### tomcat60 ### 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.LotusNotesMail ### Export.LotusNotes ### Export.ExchangeFolders ### Export.Application

50

2012-08-13

Installation

### Export.HTML ### Export.ODBC ### Export.Record ### Export.ReportDefinition ### WebIServers ### WebIProcServer ### WebISchedulingServices ### XcelsiusServers ### MobileServers ### 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,tomcat60,WebTier,CMS,FRS,PlatformServers.IntegratedDB,DashboardAnalyticsServer,Plat formServers.EventServer,PlatformServers.SystemLandscapeSupplier,PlatformServers.WebAppContainerService,Adap tiveProcessingServer,AdaptiveJobServer,Subversion,PlatformServers,ConnectionProcService,ConnectionSer vices,DataFederatorQueryService,DataFederatorServices,MultidimensionalAnalysisServices,BExWebApplication sService,AdvancedAnalysisServices,CrystalReportsProcServices,CrystalReportSchedulingServices,CrystalRe port2011ProcServices,CrystalReport2011SchedulingServices,Export.MicrosoftMail,Export.LotusNotesMail,Ex port.LotusNotes,Export.ExchangeFolders,Export.Application,Export.HTML,Export.ODBC,Export.Record,Export.Re portDefinition,ExportSupport,CrystalReportsServers,WebIProcServer,WebISchedulingServices,WebIServers,Xcel

51

2012-08-13

Installation

siusServers,MobileServers,SiebelSignOnServer,BWPublisherServer,IntegrationServers,Servers,UpgradeManager,Ad ministratorTools,BOE64bitNETSDK,DeveloperTools,DataAccess.DataFederator,DataAccess.HPNeoView,DataAc cess.MySQL,DataAccess.GenericJDBC,DataAccess.GenericODBC,DataAccess.GenericOLEDB,DataAccess.MaxDB,DataAc cess.Salesforce,DataAccess.Netezza,DataAccess.Microsoft_AnalyticalServices,DataAccess.MicrosoftExchange,DataAc cess.MicrosoftOutlook,DataAccess.Microsoft_SQLServer,DataAccess.Microsoft_Access,DataAccess.Ingres,DataAc cess.Greenplum,DataAccess.IBMDB2,DataAccess.Informix,DataAccess.ProgressOpenEdge,DataAccess.Oracle,DataAc cess.Sybase,DataAccess.Teradata,DataAccess.SAPBW,DataAccess.SAP,DataAccess.PersonalFiles,DataAccess.Jav aBean,DataAccess.OpenConnectivity,DataAccess.HSQLDB,DataAccess.Derby,DataAccess.Essbase,DataAccess.People soft,DataAccess.JDEdwards,DataAccess.Siebel,DataAccess.OracleEBS,DataAccess.Universe,DataAccess.MyCube,DataAc cess.XML,DataAccess.ADO.NET,DataAccess.COMData,DataAccess.DataSet,DataAccess.SymantecACT,DataAccess.BDE,DataAc cess.CDO,DataAccess.FieldDefinitions,DataAccess.FileSystem,DataAccess.NTEventLog,DataAccess.WebActivity Log,DataAccess.Btrieve,DataAccess.dBase,DataAccess.UWSC,Samples,Help

52

2012-08-13

Post-Installation

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: http://:/BOE/CMC

Substitute for the hostname of the web application server and 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 (https:) 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?

53

2012-08-13

Post-Installation

Check the Windows Firewall settings by going to: Start > Settings > Control Panel > Windows Firewall. 2. Is the URL correct?? The default URL to access the CMC is: http://:/BOE/CMC

Substitute for the hostname of the web application server and 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 or Windows AD 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. Go to Start > SAP SAP Crystal Server 2011 > SAP BusinessObjects Enterprise > Central Configuration Manager. 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 the @ 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 service.sap.com/bosap-support.

6.3 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

54

2012-08-13

Post-Installation

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.

6.4 Deploying web applications The installation only installs web applications to Tomcat 6. 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

55

2012-08-13

Post-Installation

6.6.1 To modify SAP Crystal Server These instructions describe the process to modify your SAP Crystal Server installation by adding or removing installed components though the Windows Control Panel. It is recommended that you back up the CMS system database before modifying SAP Crystal Server. 1. Run the Central Configuration Manager (CCM) by selecting Start > Programs > SAP BusinessObjects Enterprise > BusinessObjects Enterprise > Central Configuration Manager. The CCM screen appears. 2. Select all listed servers and click the Stop button. 3. When all of the servers are stopped, close the CCM console. 4. If you're using a newer Windows operating system, such as Windows Server 2008, go to: Start > Control Panel > Programs and Features. If you're using an older Windows operating system, such as Windows Server 2003, go to: Start > Control Panel > Add or Remove Programs. 5. Select SAP Crystal Server 2011 and click the Change/Remove button. The "Application Maintenance" screen appears. 6. Select any features you want to install; unselect any features you want to remove. Features are grouped under the following headings: • "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. 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, version control system), and servers that integrate SAP Crystal Server into your organization's existing network infrastructure (such as PeopleSoft, Siebel, and SAP BW). Install servers if you plan to use the installed system for SAP Crystal Server BI processing, such as a stand-alone Central Management Server (CMS) or as part of a CMS cluster.



Administrator Tools The Administrator Tools features help administrators maintain an installation.



56

Developer Tools

2012-08-13

Post-Installation

If you plan to develop your own applications with an SAP Crystal Server Software Development Kit (SDK), install the Developer Tools feature. •

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 the option to install it.



Samples The samples features installs sample reports, templates, and reporting databases. If you do not need samples, you can deselect it.



Help To install help files, select this feature. If you do not need help files installed on your system, you can deselect it.

7. Select Next to apply your changes. The setup program applies your changes and returns to the Control Panel applet. The installation has been updated.

6.6.2 To repair SAP Crystal Server These instructions describe the process to repair an SAP Crystal Server installation from the Microsoft Windows Add or Remove Control Panel applet. 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. 1. Run the Central Configuration Manager (CCM) by selecting Start > Programs > SAP BusinessObjects Enterprise > BusinessObjects Enterprise > Central Configuration Manager. The CCM screen appears. 2. Select all listed servers and click the Stop button. 3. When all of the servers are stopped, close the CCM console. 4. If you're using a newer Windows operating system, such as Windows Server 2008, go to: Start > Control Panel > Programs and Features. If you're using an older Windows operating system, such as Windows Server 2003, go to: Start > Control Panel > Add or Remove Programs. 5. Select SAP Crystal Server and click the Change/Remove button. The "Application Maintenance" screen appears. 6. Select Repair. The "Application Maintenance" screen disappears and the software is restored to its original configuration. This may take a long time. When complete, the Control Panel appears. The installation has been repaired, restoring your system to its original configuration.

57

2012-08-13

Post-Installation

6.6.3 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. Note: 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. 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 Note: These items can be removed manually by an administrator if required. 1. Go to: Start > All Programs > SAP Crystal Server 2011 > SAP BusinessObjects Enterprise > Central Configuration Manager. 2. Change the status of all servers to stopped. 3. When all of the servers are stopped, close the CCM. 4. If you're using a newer Windows operating system, such as Windows Server 2008, go to: Start > Control Panel > Programs and Features. If you're using an older Windows operating system, such as Windows Server 2003, go to: Start > Control Panel > Add or Remove Programs. 5. Select SAP Crystal Server 2011. 6. On newer Windows operating systems, select Uninstall. On older Windows operating systems, select Change/Remove. 7. Click through to confirm the removal. 8. Select Finish to close the "System Setup" screen. The software has been removed from the system.

6.7 When the administrator account password is lost

58

2012-08-13

Post-Installation

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.

59

2012-08-13

Post-Installation

60

2012-08-13

Installing SAP Crystal Server 2011 Client Tools

Installing SAP Crystal Server 2011 Client Tools

The SAP Crystal Server 2011 Client Tools can only be installed by a dedicated installation program, and are no longer bundled with the installation of SAP Crystal Server servers. The dedicated SAP Crystal Server Client Tools installation program installs a suite of desktop clients on supported Windows operating systems only. Client Tools are not available for Unix or Linux operating systems. Note: • • •

Although the Client Tools are supported on 64-bit operating systems, the Client Tools themselves are only available as 32-bit applications. When installing a database driver for Client Tools on 64-bit operating systems, ensure that you install the 32-bit version. A 32-bit application cannot use a 64-bit driver. If you install both the Client Tools and BI platform servers on the same 64-bit Windows operating system, you must install both 32-bit and 64-bit database drivers on the machine. You must also ensure that both 32-bit and 64-bit database connector middleware is installed and that their data source configurations are identical since Client Tools requests in this scenario may be handled by either of the two 32-bit or 64-bit Native Connectivity Services.

Some of the client applications that make up the Client Tools suite are also available with their own stand-alone installation program. This allows you to install the client application by itself, without having to install the Client Tools suite's "Custom" installation option. Client Tools can co-exist on a system that also runs SAP Crystal Server server software. When installing both SAP Crystal Server servers and Client Tools on the same system, it is recommended that the SAP Crystal Server server components (including add-ons and language packs) are installed before Client Tools. This allows the Client Tools to same the same components as the server. No keycode is required to install Client Tools, but you require administrative privileges for the account being used to run the installation program. If a file is in use during the installation, the installation program recommends a system reboot when the install is complete. Although the reboot can be postponed, and you can continue to use the system after the installation, the system may be in an unsupported state until it is rebooted. It is recommended that you restart the system prompted at the end of an installation if a reboot is recommended. The installation program requires a minimum screen resolution of 1,024 × 768 pixels. Using Microsoft Remote Desktop Connection to run the installation program is fully supported, as long as a minimum screen resolution of 1,024 × 768 pixels is used.

61

2012-08-13

Installing SAP Crystal Server 2011 Client Tools

7.1 Desktop client applications The following desktop client applications are installed by the SAP Crystal Server Platform Client Tools installation program: • Business View Manager • Report Conversion Tool • Information design tool • Translation Management Tool • Data Federation Administration Tool • Widgets • Developer Components For integrating BusinessObjects functionality into interactive web applications. Includes SAP BusinessObjects Business Intelligence platform Java SDK, Web Services SDK, and .NET SDK. •

Data Access and Security

7.1.1 Business View Manager Business View Manager allows users to build semantic layer objects that simplify underlying database complexity. Business View Manager can create data connections, dynamic data connections, data foundations, business elements, business views, and relational views. It also allows detailed column and row-level security to be set for the objects in a report. Designers can build connections to multiple data sources, join tables, alias field names, create calculated fields, and then use the simplified structure as a Business View. Report designers and users can then use the business view as the basis for their reports, rather than and building their own queries from the data directly.

7.1.2 Information design tool Information design tool (formerly Information Designer) is an SAP BusinessObjects metadata design environment that enables a designer to extract, define, and manipulate metadata from relational and OLAP sources to create and deploy SAP BusinessObjects universes.

62

2012-08-13

Installing SAP Crystal Server 2011 Client Tools

7.1.3 Translation Management Tool SAP BusinessObjects Business Intelligence platform provides support for multilingual documents and universes. A multilingual document contains localized versions of universe metadata and document prompts. A user can create reports, for example, from the same universe in their chosen languages. Translation Management Tool (formerly Translation Manager) defines the multilingual universes and manages translation of universes and other report and analytic resources in the CMS repository. Translation Management Tool: • Translates universe or documents for a multilingual audience. • Defines the metadata language parts of a document, and the appropriate translation. It generates external XLIFF format and imports XLIFF files to get translated information. • Lists the universe or document structure to be translated. • Lets you translate the metadata through the user interface, or though an external translation tool by importing and exporting XLIFF files. • Creates multilingual documents.

7.1.4 Data Federation Administration Tool The Data Federation Administration Tool (formerly Data Federator) is a rich client application that offers easy-to-use features to manage your data federation service. Tightly integrated in the SAP BusinessObjects Business Intelligence platform, the data federation service enables multi-source universes by distributing queries across disparate data sources, and lets you federate data through a single data foundation. The data federation administration tool lets you optimize data federation queries and fine-tune the data federation query engine for the best possible performance. You use the data federation administration tool to do the following: • Test SQL queries.

63



Visualize optimization plans which detail how federated queries are distributed to each source.



Compute “statistics” and set system parameters to fine-tune the data federation services and get the best possible performance.



Manage properties to control how queries are executed in each data source at the connector level.



Monitor running SQL queries.



Browse the history of executed queries.

2012-08-13

Installing SAP Crystal Server 2011 Client Tools

7.2 To run an interactive installation of Client Tools When the installation program starts, a series of prerequisite checks are performed. The result of this test is displayed for your information. If your system does not meet the minimum requirements, the installation program will not install SAP Crystal Server. If the installation program detects a previously installed version, a message is displayed to inform you of the options available for side-by-side installations. The installation program creates a human-readable log file. To read detailed information about the installation program's activities, see the installation log file after the installation is complete. 1. Log in at the console or use Microsoft Remote Desktop connection with a minimum screen resolution of 1024 × 768. 2. Locate the installation program. If you are installing from a physical media, look for setup.exe in the top-level folder. If you are installing from a compressed download, extract it and locate set up.exe. 3. Run setup.exe by double-clicking it in Windows Explorer or calling it from the command-line. A log file containing information on the installation process is saved to \In stallData\logs\\InstallDU.log. 4. Select a language for the installation 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 support is automatically installed on your system. Note: 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 Windows components configured by the installation program, such as Start menu shortcuts. These named cannot be changed later and are not affected by language settings once the installation is complete. 5. The installation program checks for required components. 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 a missing or unsupported component is optional, you have the option to either continue with the installation or stop and correct the condition. The installation program will provide information on how to correct the condition. During a silent installation, the installation program does not display the results of dependency prerequisites. If a critical component or supported version is not found, the writes an error to the installation log file and aborts. If an optional component of a supported version is not found, the missing or unsupported component is noted in the installation log file. 6. Review the recommendations made by the installation program welcome screen. 7. Review the agreement and select I accept the License Agreement. 8. Select any language for which you want language support to be installed. A language pack allows SAP Crystal Server Client Tools to interact with users in a specific language.

64

2012-08-13

Installing SAP Crystal Server 2011 Client Tools

Users can select their preferred language in the preference settings for each language tool. 9. Review and confirm the destination folder setting. If you have already installed SAP BusinessObjects products, the Destination Folder field is not editable, and the path to the existing folder is displayed. Note: • •

The use of Unicode characters in the destination folder path is not supported. Ensure that the destination folder is not set to the same folder in which the installation program has been extracted.

10. Review the list of features to install. Only features with a selected checkbox is installed. The following components can be selected: • Client components Desktop client applications: • Business View Manager • Web service query tool • Information design tool • Translation Management Tool • Data Federation Administration Tool •

Developer components Software Development Kits (SDK) for developing your own applications that integrate into SAP Crystal Server: • SAP Crystal Server Java SDK • SAP Crystal Server Web Services SDK • SAP Crystal Server .NET SDK • SAP Crystal Reports Java SDK

11. Review the confirmation screen and start the installation when ready. The "Start Installation" screen appears. Click "Next" to install.

7.3 To run a silent installation of Client Tools 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

65

2012-08-13

Installing SAP Crystal Server 2011 Client Tools

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 6400. 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 [...] •

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 parameter, where 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 [...] 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 6400. 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 [...]

Note: 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 []

For a complete list of installation options, see Installation option parameters for Client Tools. For an example of a response file, see Response file example for Client Tools.

7.3.1 Command-line silent install of Client Tools

66

2012-08-13

Installing SAP Crystal Server 2011 Client Tools

You can install Client Tools with one command by specifying parameters on the command-line. This is referred to as a “silent” installation. When parameters are supplied on the command-line, the installation will not prompt for information.

7.3.1.1 To use a response file To use a response file, run the installation program with the -r 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:\re sponse.ini: setup.exe -r C:\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: \InstallData\logs\\InstallDU.log If the 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.

7.3.1.1.1 To write a response file To create a response file, run the installation program with the -w 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

Once created, the response file can be updated with a text editor. Note: 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.

67

2012-08-13

Installing SAP Crystal Server 2011 Client Tools

7.3.1.1.2 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:\re sponse.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\"

7.3.1.2 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\"

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: \InstallData\logs\\InstallDU.log If the 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.

68

2012-08-13

Installing SAP Crystal Server 2011 Client Tools

7.3.2 Installation option parameters for Client Tools The following table lists the parameters that can be used to select installation options on both the command-line and in response files.

Table 7-1: Installation option parameters Parameter

Description

InstallDir=

Destination folder into which the setup program will install. When installing to a host that already has an installation of SAP BusinessObjects Business Intelligence platform, the value of In stallDir will be automatically set to the same path as the existing installation. Note: • •

69

The use of Unicode characters in the destination folder path is not supported. Ensure that the destination folder is not set to the same folder in which the installation program has been extracted.

2012-08-13

Installing SAP Crystal Server 2011 Client Tools

Parameter

Description

SelectedLanguagePacks=

Installs language support for users and administrators to interact with SAP BusinessObjects Business Intelligence platform 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 is: • • • • • • • • • • • • • • • • • • • • • •

70

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

2012-08-13

Installing SAP Crystal Server 2011 Client Tools

Parameter

SetupUILanguage=

Description

Determines which language for the installation program to use during the installation. Substitute the language code where is: • • • • • • • • • • • • • • • • • • • • • •

Features=

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

List of components to install. To select multiple features, use a comma-delimited list without spaces to give each code. In the fol lowing example, Business View Manager and Information Design Tool are selected for install: Features=Business_View_Manager,InformationDesignTool,[...]

For a complete list of feature codes, see Feature codes.

7.3.2.1 Feature codes for Client Tools

71

2012-08-13

Installing SAP Crystal Server 2011 Client Tools

Use the following feature codes to select features for installation. To select multiple features, separate each feature code with a comma, without spaces. For example, the following feature list selects Business View Manager and Information Design Tool clients for installation: features=Business_View_Manager,InformationDesignTool,[...]



root: install all features •

ClientComponents: install all client components • • • •



DevComponents: install all developer tool components • • • •



JavaSDK (SAP BusinessObjects Business Intelligence platform Java SDK) WebSDK (SAP BusinessObjects Business Intelligence platform Java Web Services SDK) DotNetSDK (SAP BusinessObjects Business Intelligence platform .NET SDK) CRJavaSDK (SAP Crystal Reports Java SDK)

DataAccess install all database access components • • • • • • • • • • • • • • • • • • • • • • • •

72

Business_View_Manager InformationDesignTool Translation_Manager (Translation management tool) DataFederationAdministrationTool

DataFed_DataAccess (Data Federator) HPNeoView_DataAccess MySQL_DataAccess GenericODBC_DataAccess GenericOLEDB_DataAccess GenericJDBC_DataAccess MaxDB_DataAccess SalesForce_DataAccess (Salesforce.com) Netezza_DataAccess Microsoft_DataAccess Ingres_DataAccess Greenplum_DataAccess IBMDB2 Informix_DataAccess Progress_Open_Edge_DataAccess Oracle_DataAccess Sybase_DataAccess TeraData_DataAccess PersonalFiles_DataAccess JavaBean_DataAccess OpenConnectivity_DataAccess HSQLDB_DataAccess Derby_DataAccess Essbase_DataAccess

2012-08-13

Installing SAP Crystal Server 2011 Client Tools

7.3.2.2 Response file example for Client Tools The following example response file contains options for installing SAP Crystal Server Client Tools. Example: In this example, the response file is named C:\response.ini. ### Installation directory installdir=C:\Program Files (x86)\SAP BusinessObjects\ ### #property.SelectedLanguagePack.description# selectedlanguagepacks=cs;da;nl;en;fi;fr;de;hu;it;ja;ko;nb;pl;pt;ru;zh_cn;sk;es;sv;th;zh_tw;tr ### Setup UI language setupuilanguage=en ### Available features ### -----------------### root ### ClientComponents ### WebI_Rich_Client ### Business_View_Manager ### QAAWS ### InformationDesignTool ### Translation_Manager ### DataFederationAdministrationTool ### biwidgets ### DevComponents ### JavaSDK ### WebSDK ### DotNetSDK ### CRJavaSDK ### DataAccess ### DataFed_DataAccess ### HPNeoView_DataAccess ### MySQL_DataAccess ### GenericODBC_DataAccess ### GenericOLEDB_DataAccess ### GenericJDBC_DataAccess ### MaxDB_DataAccess ### SalesForce_DataAccess ### Netezza_DataAccess ### Microsoft_DataAccess ### Ingres_DataAccess ### Greenplum_DataAccess ### IBMDB2 ### Informix_DataAccess ### Progress_Open_Edge_DataAccess ### Oracle_DataAccess ### Sybase_DataAccess ### TeraData_DataAccess ### SAPBW_DataAccess ### SAP_DataAccess ### PersonalFiles_DataAccess ### JavaBean_DataAccess ### OpenConnectivity_DataAccess ### HSQLDB_DataAccess ### Derby_DataAccess ### Essbase_DataAccess ### PSFT_DataAccess ### JDE_DataAccess ### Siebel_DataAccess ### EBS_DataAccess features=WebI_Rich_Client,Business_View_Manager,QAAWS,InformationDesignTool,Translation_Manager,DataFeder ationAdministrationTool,biwidgets,ClientComponents,JavaSDK,WebSDK,DotNetSDK,CRJavaSDK,DevCompo nents,DataFed_DataAccess,HPNeoView_DataAccess,MySQL_DataAccess,GenericODBC_DataAccess,GenericOLEDB_DataAc cess,GenericJDBC_DataAccess,MaxDB_DataAccess,SalesForce_DataAccess,Netezza_DataAccess,Microsoft_DataAc

73

2012-08-13

Installing SAP Crystal Server 2011 Client Tools

cess,Ingres_DataAccess,Greenplum_DataAccess,IBMDB2,Informix_DataAccess,Progress_Open_Edge_DataAccess,Ora cle_DataAccess,Sybase_DataAccess,TeraData_DataAccess,SAPBW_DataAccess,SAP_DataAccess,PersonalFiles_DataAc cess,JavaBean_DataAccess,OpenConnectivity_DataAccess,HSQLDB_DataAccess,Derby_DataAccess,Essbase_DataAc cess,PSFT_DataAccess,JDE_DataAccess,Siebel_DataAccess,EBS_DataAccess,DataAccess,root

7.4 Making changes to Client Tools

7.4.1 To modify Client Tools These instructions describe the process to modify your Client Tools installation by adding or removing installed components though the Windows Control Panel. 1. If you're using a newer Windows operating system, such as Windows Server 2008, Vista, or Windows 7, go to: Start > Control Panel > Programs and Features. If you're using an older Windows operating system, such as Windows Server 2003 or Windows XP, go to: Start > Control Panel > Add or Remove Programs. 2. Select SAP Crystal Server Client Tools and click the Change button. The "Application Maintenance" screen appears. 3. Select any features you want to install; unselect any features you want to remove. The following components can be selected: • Client components Desktop client applications: • Business View Manager • Information design tool • Translation Management Tool • Data Federation Administration Tool •

Developer components Software Development Kits (SDK) for developing your own applications that integrate into SAP Crystal Server: • SAP Crystal Server Java SDK • SAP Crystal Server Web Services SDK • SAP Crystal Server .NET SDK • SAP Crystal Reports Java SDK



Data access Drivers that allow client tools to access supported databases.

74

2012-08-13

Installing SAP Crystal Server 2011 Client Tools

4. Select Next to apply your changes. The setup program applies your changes and returns to the Control Panel applet. The installation has been updated.

7.4.2 To repair a Client Tools installation These instructions describe the process to repair a Client Tools installation from the Microsoft Windows Add or Remove Control Panel applet. This process restores the files originally installed by the setup program. It is recommended that you back up your system before running a repair. 1. If you're using a newer Windows operating system, such as Windows Server 2008, Vista, or Windows 7, go to: Start > Control Panel > Programs and Features. If you're using an older Windows operating system, such as Windows Server 2003 or Windows XP, go to: Start > Control Panel > Add or Remove Programs. 2. Select "SAP BusinessObjects Enterprise Client Tools XI 4.0" and click the Change button. The "Application Maintenance" screen appears. 3. Select Repair. The "Application Maintenance" screen disappears and the software is restored to its original configuration. This may take a long time. When complete, the Control Panel appears. The installation has been repaired, restoring your system to its original configuration.

7.4.3 To remove Client Tools The following steps remove SAP Crystal Server Client Tools from a system. Note: Add-on products that with dependencies on other products should be removed before the product on which they depend. For example, for SAP Crystal Server servers with SAP Crystal Server Explorer installed, SAP Crystal Server Explorer should be removed first, as it will not function without SAP Crystal Server. 1. If you're using a newer Windows operating system, such as Windows Server 2008, Vista, or Windows 7 go to: Start > Control Panel > Programs and Features. If you're using an older Windows operating system, such as Windows Server 2003 or Windows XP, go to: Start > Control Panel > Add or Remove Programs. 2. Select the SAP BusinessObjects Enterprise Client Tools XI 4.0 to remove and click Remove.

75

2012-08-13

Installing SAP Crystal Server 2011 Client Tools

Note: If you have installed a Client Tools component more than once, each instance will appear in the separately. 3. Confirm that you want to remove the selected components. The appropriate files are removed and the necessary configuration is completed. 4. Click Finish. The Client Tools have been uninstalled and you are returned to the Control Panel. The SAP Crystal Server Client Tools have now been removed from the system. Files that were not installed by the installation program, such as those created or modified post-install, will not be removed.

7.5 Upgrading Client Tools The Client Tools installation program will not modify existing previous versions of SAP Crystal Server Client Tools. SAP Crystal Server Client Tools are supported when installed on systems that also contain the following previous Client Tool versions: • SAP BusinessObjects Business Intelligence platform XI 3.1 (any version) • BusinessObjects Enterprise XI 3.0 • BusinessObjects Enterprise XI R 2.0 The installation of SAP Crystal Server Client Tools with Client Tools form BusinessObjects Enterprise 10 or BusinessObjects Enterprise XI is not supported and you may encounter compatibility issues.

76

2012-08-13

More Information

More Information

Information Resource

Location

SAP product information

http://www.sap.com http://help.sap.com/analytics

SAP Help Portal

Access the most up-to-date English documentation covering all SAP Analytics products at the SAP Help Portal: • http://help.sap.com/bobi (BusinessObjects Business Intelligence) • http://help.sap.com/boepm (Enterprise Performance Management) • http://help.sap.com/boeim (Enterprise Information Management) Certain guides linked to from the SAP Help Portal are stored on the SAP Service Marketplace. Customers with a maintenance agreement have an authorized user ID to access this site. To obtain an ID, contact your customer support representative. To find a comprehensive list of product documentation in all supported languages, visit:http://help.sap.com/boall. http://service.sap.com/bosap-support

SAP Support Portal

The SAP Support Portal contains information about Customer Support programs and services. It also has links to a wide range of technical information and downloads. Customers with a maintenance agreement have an authorized user ID to access this site. To obtain an ID, contact your customer support representative. http://www.sdn.sap.com/irj/sdn/bi-sdk-dev

Developer resources http://scn.sap.com/docs/DOC-27465 (BI SDK Developer Library)

Articles and eLearning on the SAP Community Network

77

http://scn.sap.com/docs/DOC-19311 These articles were formerly known as technical papers.

2012-08-13

More Information

Information Resource

Location

https://service.sap.com/notes Notes These notes were formerly known as Knowledge Base articles. Forums on the SAP Community Network

https://www.sdn.sap.com/irj/scn/forums http://www.sap.com/services/education

Training

From traditional classroom learning to targeted e-learning seminars, we can offer a training package to suit your learning needs and preferred learning style. http://www.sap.com/services/bysubject/businessobjectsconsulting

Consulting

78

Consultants can accompany you from the initial analysis stage to the delivery of your deployment project. Expertise is available in topics such as relational and multidimensional databases, connectivity, database design tools, and customized embedding technology.

2012-08-13

Index 64-bit client tools 61 platform 16

A account permissions 16 administrator password 58 Auditing Data Store preparing for 17

B Business View Manager 62 BusinessObjects Enterprise upgrade from 10

C check-list installation 20 Client Tools 64-bit vs. 32-bit 61 installation 61, 64 languages 61 repair 75 response file 73 silent install 66 uninstallation 75 upgrade from previous versions 76 clients Business View Manager 62 Data Federation Administration Tool 63 Data Federator. See Data Federation Administration Tool 63 Information design tool 62 Information Designer. See Information design tool 62 Translation Management Tool 63 CMC launching 53 troubleshooting 53 CMS system database preparing for 17 co-existence, product 11 command-line installation 37 installation program parameters 38

79

D Data Federation Administration Tool 63 database choosing 13 DB2 extra requirements 19 deployment web applications 55 diagnostic tests 55 disaster mitigation reset administrator password 58

E Enterprise Resource Planning (ERP) 20

F feature codes client 71 Enterprise 46

I Information design tool 62 installation account permissions 16 check-list 20 client tools 61 Client Tools 64 Client Tools feature codes 71 Client Tools silent install 66 command-line 37, 38 custom 30, 31 Enterprise feature codes 46 expand 30 full 26 installation program 24 methods 23 parameters 41 planning 9 post-install 53 preparation for 15 requirements 16 response file 37, 39, 40, 67, 68 response file example 49 screen resolution 61

installation (continued) silent 40, 68, 69 software removal 58 type 25 web tier 35 installation program to run 24

M Monitoring Tool 55

N network permissions 17

O object types requirements 11

P password reset 58 permissions for installation account 16 network 17 planning installation 9 post-installation 53 diagnostic tests 55 modification 56, 74 repair 57

R reboot suppression 37 remove software 58 Client Tools 75 repair 57, 75 requirements 16 response file 39, 40, 67, 68 Client Tools feature codes 71 Enterprise feature codes 46 example 49 example for Client Tools 73 parameters 41

2012-08-13

Index

S

T

SAP Host Agent 15 screen resolution installation 61 silent installation 65 parameters 69 Sybase extra requirements 20

Translation Management Tool 63

80

U uninstallation 58 Client Tools 75 upgrade Client Tools 76

upgrade support 10 upgrades requirements object types 11

W web application server, choosing 12 web applications 55 web server, choosing 13

2012-08-13

Suggest Documents