Skip to main content

Introduction

CSP Mobile makes it possible to connect a wide variety of mobile devices such as smartphones and tablets.

The native interface controls of the relevant mobile platform (iOS-based and Windows-based devices) are supported, thus providing the associated benefits.

The application itself runs on the Web server as CSP Mobile and communicates, as does CSP Cockpit, directly with CSP Server and the OLAP databases.

This document provides installation, configuration and administration instructions for CSP Mobile.

Supported Web Servers

CSP Mobile supports the following Web servers:

The principles of the architecture are the same for each Web server used. See Architecture for details.

Supported Operating System Versions

The following mobile operating system versions are supported:

iOS

8.x/9.x/10.x/11.x

Windows

10.x

Supported Messaging Services

  • Skype for Business
  • Telegram

Note: Please refer to the technical information of Skype for Business or Telegram which version is supported by your operating system.

Architecture

An installation of an environment with CSP Mobile always has the following fundamental structure:

Architecture diagram

The Cubeware Mobile Service Architecture provides a Web-based service API for report components such as DataViews, filters, charts, maps and analytical visualizations. CSP Web has been extended to include this service API. This means that the powerful, highly scalable, tried and tested Web Engine is also available for CSP Mobile. Existing repositories can be used on mobile devices. The repositories are administered by the CSP Server.

Benefits:

  • Open Web service architecture
  • Connection of a wide variety of mobile devices such as smartphones and tablets
  • Support for the native interface controls of the relevant mobile platform

Planning the Hardware

Planning the hardware is a very important aspect of a successful installation.

Note: Since the exact requirements cannot be calculated to cover all cases, the information given here can only be regarded as a recommendation. The actual requirement will depend heavily on the databases used, the data models and the reports generated.

Hard Drive Capacity

The installation of the CSP Mobile components requires a total of approx. 200 MB of hard drive space. Each user who is logged in requires an additional 2 MB of space in the temporary folder. If the Export function is used for reports, additional space for the temporary storage of the generated export files will be needed.

Memory Requirements

Main memory (RAM) is an important element of planning an installation. Since each session runs in a Worker process in the MobileEngine, the computer on which it is installed (application layer) must have sufficient main memory.

The following values apply for each user logged in concurrently.

  • OLAP data model: The larger the model, the more memory is required for caching data. It can always be assumed that 60 MB is required for each user.
  • Reports: If very large reports are available, or reports which contain a very large number of null lines or which have a large nesting depth, the memory requirements increase accordingly. For an open report containing more than 1000 lines (lines which occur in a query, not just the visible lines), an additional 10 MB must be added on.

Examples:

  • Medium-sized data model, simple reports, 20 concurrent users: 20 users x 60 MB = approx. 1.2 GB memory requirements.
  • Large data model, simple reports, 20 concurrent users: 20 users x 85 MB = 1.7 GB memory requirements.
  • Large data model, complex reports, 100 concurrent users: 100 users x 85 MB = 8.5 GB memory requirements.

Memory Requirements When Using the Map Layout Component

If you are using the Map layout component, you can assume an additional 100 MB + 60 MB per concurrent user.

Examples:

  • Medium-sized data model, simple reports, 20 concurrent users:
    • 20 users * 60 MB +
    • 20 users * 60 MB +
    • 100 MB = 2.5 GB memory required.
  • Large data model, simple reports, 20 concurrent users:
    • 20 users * 85 MB +
    • 20 users * 60 MB +
    • 100 MB = 3 GB memory required.
  • Large data model, complex reports, 100 concurrent users:
    • 100 users * 85 MB +
    • 100 users * 60 MB +
    • 100 MB = 14.6 GB memory required.

Note: In order to use maps in a report, you need to have an edition of CSP Server (Standard or Professional) installed, which supports Interactive Maps, and you also need appropriate shape files.

CSP Mobile is a 32-bit application. The traditional 2 GB memory limit for each application does not apply here, as each Web Worker process can use 2 GB. Note the configuration settings in the file mobileenabler.cfg in this respect.

Processor

The machine on which the application layer is installed serves all logged-in users concurrently. Depending on how many users are using the system simultaneously and the intensity of use, it may make sense to deploy a multi-processor machine.

You should be aware that alongside the application layer, the database itself must also be able to serve several users, which means that both machines should be equipped with the same number of processors. Using processors that do not provide equal capacity means that the application can only reach the performance afforded by the machine with the lowest number of processors.

It is important to note that doubling the number of processors does not mean that performance of the application is also doubled. A database query or a processing step in the application is only ever carried out by one processor, which means that the performance for a given user remains the same despite multiple processors; the overall performance, on the other hand, is almost doubled.

Data Transfer Rate

We recommend LTE for communication between the mobile device and the Web server.

Operating System

For information on the operating systems supported, refer to General Requirements (Microsoft IIS) and General Requirements (JSP Web Server).

Licensing

No licenses are required in order to install the application layer and the Web layer. The application layer can be installed on as many servers as are required.

In the case of CSP Server, the Web Access feature must be licensed. This feature enables access to the repositories of the CSP Server from an Internet browser (CSP Web) or a mobile device (CSP Mobile) or Microsoft Store (Windows).

You will find information on licensing in the online Help system for CSP Cockpit and in the section entitled Licensing and activation.

Security Concept for CSP Mobile

CSP Mobile is fully integrated into the security concept of Web servers. You can download the app from the Apple AppStore (iOS).

There are three parts to the security concept:

  • Security settings on the Web server
  • Permissions concept of CSP Cockpit / database permissions
  • Passcode lock, PIN lock or Pattern lock on the mobile device

Security Settings on the Web Server

The connection between the mobile device and the Web server (and hence CSP Mobile) is established over the Internet. It must therefore be possible to connect to the Web server over the Internet.

Important: It is not necessary for the CSP Server to be reachable over the Internet.

Encryption Is Possible

Communication between the app and the server can be handled over HTTPS, i.e. it can be encrypted. You will find a description of how to set up HTTPS when using IIS here.

VPN

It is also possible to establish a connection via a VPN. In order to do this, you must enable VPN on the mobile device before you start the app. You will find a description of how to set up a VPN in the User Manual for your mobile device.

Permissions Concept of CSP Cockpit

The permissions set in Cockpit and the permissions stored in the database govern authorization for editing reports and accessing data. Although it is possible to change reports in the app (by means of filter selection), these changes are not saved.

Passcode Lock on the Mobile Device

Mobile devices allow you to set up a passcode that has to be entered when the mobile device is switched on or when sleep mode is terminated.

Recommendations

  • Enable the passcode lock and do not store any screenshots of reports that contain sensitive data.
  • Use the PDF in app in order to distribute reports. The PDF documents are created temporarily and are not stored.

    Caution: Clear the outbox of your email client after you have sent an email if the distributed reports contain sensitive data.

  • Do not jailbreak your iPhone, as this enables remote access to the iOS file system.

Functionality of the App

  • The Navigator is available for selecting reports (as in Cockpit) and can be called from the toolbar at any time.
  • All filters (including multiple selection) are available (exception: MDX container).
  • The selection bar, action bar and filter bar are represented by means of a native control element.
  • Actions for jumping between reports and for calling URLs are available, but all other actions, which cannot be run on the mobile device (program call actions, export actions, etc.), are automatically hidden.
  • Reports can be printed or sent by email as PDF files.
  • Output on a projector is supported. Both iOS and Windows support mirrored reproduction on an external monitor/projector.

You can call up a description in the app from the login dialog box by tapping the Mountain icon.

Was this article helpful?

We're sorry to hear that.