SAP Analytics Cloud Agent Simple Deployment Kit

The SAP Analytics Cloud Agent Simple Deployment Kit allows you to quickly get your import data connections working.

The SAP Analytics Cloud Agent Simple Deployment Kit is ideal if you do not already have a Tomcat Server deployment running, or an existing SAP Business Technology Platform (BTP) Cloud Connector configured.

Note
The simple deployment kit is only supported on Windows 64-bit operating systems. If you have a different server, such as Linux, you'll need to install and configure the agent manually. See Installing SAP Analytics Cloud Agent.
Note

The SAP Analytics Cloud agent deployment kit prior to version 1.0.269 has the Apache Tomcat memory allocation set to 1GB out of the box. For better handling of large data volumes, ensure that Apache Tomcat has at least 4GB of memory. Refer to SAP Note 2732879 Information published on SAP site for information on how to increase Tomcat memory allocation.

The deployment kit has limited configuration options. If you would like all available options, perform a full manual installation of all required components. If you have already installed the deployment kit, and require more options, uninstall the kit before performing a full manual installation. For more information, see Import Data Connection Overview Diagram.

When you run the deployment kit, a Tomcat server, the Cloud Connector, and the SAP Analytics Cloud agent will be installed. Environment variables and folders for JDBC and File Server will also be created or configured. If your connection type requires the SAP Java Connector (JCo) or JDBC drivers, you must manually deploy them following the Post-Setup Guide included in the deployment folder. All components will be installed on the same machine.

The deployment kit is available at SAP Software Downloads. Go to Support Packages and Patches, and search for the CLOUD KIT. Follow the instructions in the README.txt included in the .zip and the Post-Setup Guide available in the deployment folder.

Setting Custom User Parameters

The file parameters-example.ini is included in the deployment kit .ZIP file. To overwrite the preset user settings used by the deployment kit, rename this file to parameters.ini and provide the following custom parameters:
  • tomcatuser: Provide a user name for your Tomcat user.
  • tomcatpassword: Provide a password for your Tomcat user.
  • sccpassword: Provide a Cloud Connector password.
  • tomcatMaxHeap: Provide the memory allocation in MB for Tomcat.

Script Behaviors

Option

Behavior

Clean Install

Default installation: Performs the installation using a Tomcat heap size of 4096 MB.

Custom installation: Choose one of the options for Tomcat heap size, or type a custom value between 256 MB and 32768 MB.

  • Installs required software components unless you already have the Cloud Connector installed on your machine.
  • Depending on what types of import data connections you plan to use, you may need to add the SAP Java Connector or JDBC drivers. Instructions are available in the Post-Setup Guide included in the deployment folder.
  • If an existing parameters.ini file is found, choose whether to import the custom parameters from that file, or proceed with the clean installation, overwriting the parameters.ini file.
Modify SAP Analytics Cloud agent settings Choose one of the options for Tomcat heap size, or type a custom value between 256 MB and 32768 MB.
Repair/Upgrade
  • Performs a repair on the existing setup or an upgrade to a newer version of the deployment kit. All user settings are preserved.
Remove Everything
  • Removes all software components installed with the kit, and user settings will not be preserved.
  • If you choose to reinstall the deployment kit at a later time, user settings from the previous installation will not be available.

Post-Installation and Apache Tomcat Configuration

For better handling of large data volumes, ensure that Apache Tomcat has at least 4GB of memory. Refer to SAP Note 2732879 Information published on SAP site for information on how to increase Tomcat memory allocation.