Making changes to SAP Crystal Server

These instructions describe the process to modify your SAP BusinessObjects Business Intelligence (BI) platform installation by adding or removing installed features.

It is recommended that you back up the CMS system database before modifying the BI platform.

Note

The CMS must be running in order to modify an installation.

1. Change directory to the <<BOE_INSTALL_DIR>> folder.

2. Run the command:

./modifyOrRemoveProducts.sh

Note

Log files, configuration files for web applications, and web applications will not be removed by the removal program. Folders left after removing a corresponding feature can be removed manually later with the rm command.

3. Select the installation to be modified.

4. Select Modify.

5. On the Select Language Packs page, select any languages you want to install; unselect any languages you want to remove. Click Next to continue.

6. Ensure that all features you want available are selected. Ensure that features you do not want installed are deselected.

Expand the highlighted feature in the selection tree by pressing the keyboard spacebar. Use the arrow keys to navigate up or down. Toggle feature selections with the X key.

When you are satisfied with the selected features, press Enter.

7. If you are modifying a server with a CMS installed, press Enter to apply the changes. If you are modifying a server that uses a remotely installed CMS, enter the hostname, port, and an administrative account username and password.

8. When the changes have been made, press Enter to return to the command-line.

The installation has been updated.

6.7.2 To repair SAP Crystal Server

These instructions describe the process to repair an SAP Crystal Server installation. This process restores the files and settings originally configured by the setup program.

It is recommended that you back up the CMS system database before repairing SAP Crystal Server.

Note

The CMS must be running in order to modify an installation.

1. Change directory to the <<BOE_INSTALL_DIR>> folder.

2. Run the command:

./modifyOrRemoveProducts.sh

Note

Log files, configuration files for web applications, and web applications will not be removed by the removal program. Any remaining folders can be removed manually with the rm command.

3. Select the installation to be repaired.

4. Select the Repair option.

5. Enter your CMS connection and logon information and proceed through to confirm the repair.

6. When the repair is finished, press Enter to return to the command-line.

The installation has been repaired, restoring your system to its original configuration.

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

Note

Prerequisite for uninstalling or downgrading SAP Crystal Server Platform Services 2016 SP2

● When uninstalling or downgrading SAP Crystal Server from 2016 SP2 to 2016 SP1 or 2013 or 2011, ensure that you remove the new license key pertaining to SAP Crystal Server from 2016 SP2 from CMC

● If you had uninstalled SAP Crystal Server from 2016 SP2 without removing the new license key, run the script to the remove the key. For more information on removing the key through the script, see 2276413

Note

Removing SAP Crystal Server removes the core product plus any installed maintenance packages. To remove maintenance packages individually, see the installation guides for those maintenance packages.

The following items will remain:

● The CMS repository auditing databases, as they may be shared with other programs. If you are using the bundled Sybase SQL Anywhere database server, a backup of the CMS and auditing database files (.db) remain at the following location: <<BOE_INSTALL_DIR>>/sqlanywhere/database.backup.<<DATE>>/

● 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 manually removed later by an administrator, if required.

1. Stop all server processes.

Change directory to the <<BOE_INSTALL_DIR>>/sap_bobj folder and run the command:

./ccm.sh –stop all Alternatively, run the command:

./stopservers

2. Change directory to the <<BOE_INSTALL_DIR>> folder.

For example, run the following command:

cd ..

3. Run the command:

./modifyOrRemoveProducts.sh

Note

Log files, configuration files for web applications, and web applications will not be removed by the removal program. Any remaining folders can be removed manually with the rm command.

4. Select the installation to remove.

5. Select the Remove option and confirm.

6.7.4 Patching third-party solutions bundled with the BI platform

There are several third-party software solutions bundled with SAP Crystal Server 2016 installation, including:

● SAP Sybase SQL Anywhere

● Apache Tomcat 8.0

● SAP JVM

These third-party solutions are delivered as-is and without any support to patch them with vendor-delivered patches or updates. In the event of a security issues arising in those delivered products, SAP will patch them in subsequent Support Packages (SPs) or Patches as necessary.

If your business has the need to run a newer version or patch of the bundled software, consider switching to a fully featured solution providing you with a greater flexibility and support. For a list of databases, web application servers, and other systems supported by this release, see the Product Availability Matrix (Supported Platforms/

PAR), available on the SAP BusinessObjects section of the SAP Support Portal at: https://support.sap.com/

home.html

Note

The SAP JVM/JDK must not be swapped with another vendor's JVM/JDK.