How to install Crystal Server 2013 step by step?

Version 27

    Verified Product Versions

    Service Desk 7.6Service Desk 7.7.xService Desk 7.8.xService Desk 2016.xAsset Manager 2016.xService Desk 2017.x




    The purpose of this document is to provide step-by-step instructions to install Crystal Server 2013. The scenario described here is a basic new installation of the product using SQL Server to host the Crystal Server database. There are different ways to install and configure Crystal Server and this document does NOT explain all the different possibilities. The official installation documentation provided by SAP is available in the Official SAP installation guides section and should be consulted to understand all the possibilities offered for the installation of Crystal Server.



    Why should I install Crystal Server?


    Crystal Server is a solution that allows you to host, manage and run reports created with the Crystal Reports editor. It is a server-based platform edited by SAP and it is also known as BusinessObjects BI Platform 4.1. It is not directly integrated with any LANDESK programs, but you can use it to host reports based on your Service Desk database and access these reports via hyperlinks from the Service Desk interface.


    You should install Crystal Server if you plan to regularly use reports from the Service Desk web interface, or if you want to schedule reports on a regular basis. If you only use the Service Desk console, you can run reports directly from the Crystal Reports menu - in this case the reports are generated via the Crystal Reports runtime shipped with Service Desk and you don't need to install Crystal Server.




    You are also entitled to install and use Crystal Reports and Crystal Server when you purchase LANDESK Service Desk. Download links and license keys for both products can be obtained from your account manager, or from your usual LANDESK licensing team if you are a LANDESK partner.



    Official SAP installation guides


    This article explains how to perform a basic installation of Crystal Server with a SQL Server database. For more details about the different options available please refer to the official installation guide of Crystal Server 2013 on the SAP website:




    Supported platforms


    The list of supported platforms for Crystal Server 2013 is available on the SAP website from the link below:


    SAP BusinessObjects BI Platform 4.1 Supported Platforms



    Step 1 - Creating the Central Management Server database and user


    The Central Management Server (CMS) database stores all the configuration information of your Crystal Server system. It needs to be created manually before starting the installation of Crystal Server. You also need to create a login that Crystal Server uses to access the CMS database.


    In this scenario we create a basic database using an existing SQL Server installation. There are other database systems supported (Oracle, MySQL, SQL Anywhere...). See the official installation guide for more details.


    In SQL Server Management Studio, create a new database:

    Enter the database name. You can configure the other database options if needed, but in this scenario we use the default database settings:

    Once the database is created, you need to create a user that will be used by Crystal Server to access the database. Go to the Security > Logins section of your SQL Server instance and create a new login:

    Enter a login name, select SQL Server Authentication, enter a password and adjust the password policy options as needed (in the example above the password never expires). Select the CMS database that you have created as the default database for this user:

    In the User Mapping section, select the CMS database, select the db_owner role for this database and click OK:

    The database user needs to have privileges to create, modify and delete tables, and to create stored procedures. In this scenario we give the db_owner role to the user, but you may want to configure the permissions in a different way.




    Once the database and the user have been created, we need to create an ODBC link on the server where Crystal Server will be installed


    In this scenario we are using a CMS database created with SQL Server. If you use a different database system you need to configure the ODBC link accordingly or use another connection method (see the official installation guide for more details).


    In Windows Server, open Administrative Tools > ODBC Data Sources (64-bit) and click the System DSN tab:

    Click Add, select the SQL Server driver and click Finish:

    Enter a data source name, select the SQL Server where the CMS database has been created and click Next:

    Select With SQL Server authentication, enter the login ID and the password of the user created in SQL Server and click Next:

    Select the CMS database as the default database and click Next:

    Leave the default options and click Finish:

    Click the Test Data Source button in the summary and ensure that the connection works correctly, then click OK to create the ODBC connection:



    Step 3 - Installing Crystal Server 2013


    Extract the Crystal Server installation zip file on the server where you want to install the application, and launch setup.exe located under \DATA_UNITS\CRServer_win.


    Go through the initial installation steps as below:


    When you reach the "Select Install Type" step, you can choose the type of installation:

    • Full installs all the features and uses more disk space and system resources.
    • Custom / Expand allows you to select only the features you want to install.


    In this scenario we are doing a basic installation of Crystal Server without all the features and we select Custom / Expand:


    Select the destination folder (default: C:\Program Files (x86)\SAP BusinessObjects):


    You can now select the features that you want to install (if you have chosen the Full installation type you won't see the screen below). For a basic installation, unselect all the components (untick the Instances checkbox) and select only the items below:


    • WebTier > Java Web Applications
    • WebTier > Tomcat 7.0
    • Servers > Platform Services > Central Management Server
    • Servers > Platform Services > File Repository Services (FRS)
    • Servers > SAP Crystal Reports Services > SAP Crystal Reports 2013 Processing Services
    • Servers > SAP Crystal Reports Services > SAP Crystal Reports 2013 Scheduling Services
    • Database Access > Generic OLEDB
    • Database Access > Microsoft SQL Server
    • Database Access > [any other data source you may want to use with your reports, e.g. Oracle, MySQL, etc]
    • Samples (can be useful for testing / troubleshooting)

    Select Start a new SAP Crystal Server deployment:

    Select Microsoft SQL Server using ODBC for the CMS database type:

    You have the possibility to configure an auditing database. If you want to use a dedicated auditing database, you will need to create the database first and create an ODBC link on it (same procedure as for the CMS database). In this scenario we select No auditing database (you can configure it later if needed):

    The Server Intelligence Agent name is used to identify the process that manages the Crystal Server system. A service will be created on the server with this name. By default it is the computer name but you can rename it with a more meaningful title. The default port used by the SIA is 6410:

    The default port used for the Central Management Server (CMS) is 6400:

    Enter a password for the administrator account and a cluster key. The administrator account is the one that you will use to login to the Central Management Console and to manage the system. The cluster key is used for installations with multiple CMS servers or to reconfigure your existing CMS database. Make sure you remember both passwords as they are then encrypted in the database:

    In the Central Management Server configuration screen, select the ODBC link that you have created earlier. If the link doesn't appear in the list then you need to reconfigure correctly first (see the section Step 2 - Creating the System Data Source link. Make sure your create the link as a System data source and not a User DSN). Enter the password for the database user (created in the section "Creating the database user" above). Select only "Show system database" and "Reset existing database":


    If you want to use another database connection method, see the Crystal Server installation guide for the recommended settings.

    Leave the default ports used for Tomcat. Tomcat is the web server that hosts the Crystal Server web applications (default connection port: 8080; default shutdown port: 8005; default redirect port: 8443):


    Select Do not configure connectivity to SMD agent (you can configure it later if needed):


    Select Do not configure connectivity to Introscope Enterprise Manager (you can configure it later if needed):


    Once you are ready to start the installation, click Next:

    The installation can take up to several hours depending on the system resources. You can check the installation logs located under [installation path]\InstallData\logs\YYYY.MM.DD.HH.MM.SS\ (e.g. "C:\Program Files (x86)\SAP BusinessObjects\InstallData\logs\2015."). The main log file is setupengine.log.

    Review the post installation screens to ensure that the installation is complete and without errors:


    Once the program is installed, it is recommended to install the service pack for Crystal Server that should have been provided to you with the download links and license keys. The installation of the service pack is very straightforward and does not require any specific configuration. The service pack installation program will ask for the administrator password (that you have entered during the Crystal Server installation) and requires the Server Intelligence Agent to be running (see the section below to check that the SIA runs correctly).



    After the installation


    New shortcuts have been created in the Start menu:


    You can use the Central Configuration Manager to manage the Crystal Server components (Server Intelligence Agent and Tomcat). You need to ensure that both services are running to be able to use Crystal Server:


    You can launch the Central Management Console (CMC) from the shortcut menu or via the URL http://localhost:8080/BOE/CMC (8080 is the default Tomcat connection port). To connect to the CMC, enter the following details:


    • System: <server_name>:<CMS_port> (the default CMS port is 6400)
    • User Name: administrator (the administrator login is always "administrator", even if you have installed Crystal Server in a different language)
    • Password: the password for the administrator account entered during the installation
    • Authentication: Enterprise


    The System Configuration Wizard appears. In this scenario we have only installed the basic components and there is no advanced configuration required, so you can just close it:


    To add reports and make them available for your Web Access users, see this article: How to share a Crystal Server report with your Web Access Users