ii 70 requirement spec en

10
SAP InfiniteInsight® 7.0 Recommended Requirements Specifications Documentation Document Version: 1.0 – 2014-11 CUSTOMER

Upload: lcyho77

Post on 18-Jan-2016

20 views

Category:

Documents


0 download

DESCRIPTION

II 70 Requirement Spec En

TRANSCRIPT

Page 1: II 70 Requirement Spec En

SAP InfiniteInsight® 7.0 Recommended Requirements

Specifications Documentation Document Version: 1.0 – 2014-11

CUSTOMER

Page 2: II 70 Requirement Spec En

CUSTOMER SAP InfiniteInsight® 7.0 ii © 2014 SAP SE or an SAP affiliate company. All rights reserved- Technology

Table of Contents 1 Technology .................................................................................................................... 3

2 Stand-alone Version Requirements .............................................................................5

3 Server & Client Version Requirements....................................................................... 6 3.1 Server Sizing .........................................................................................................................6

3.1.1 Data Access .............................................................................................................6 3.1.2 CPU Usage ...............................................................................................................6 3.1.3 Memory Consumption ............................................................................................ 7 3.1.4 Hard Disk Space ...................................................................................................... 7

3.2 Network Requirements ........................................................................................................ 7 3.3 Java Runtime Environment for Client .................................................................................8 3.4 Java Web Start Deployment ................................................................................................8

4 Annex ............................................................................................................................. 9 4.1 List of Available Binaries ......................................................................................................9

Page 3: II 70 Requirement Spec En

SAP InfiniteInsight® 7.0 CUSTOMER Technology © 2014 SAP SE or an SAP affiliate company. All rights reserved- 3

1 Technology

SAP InfiniteInsight® is written in C++ and is provided as an API under several formats (C++ loadable library, CORBA server on all supported platforms, COM library and DCOM server for Windows).

The supported platforms to date are:

Platform OS Processors Arch. Access JNI PAM SSL

Windows Windows (2000, 2003, XP, NT 4, Vista, 7)

Intel 32-bits (IA32)

32-bits x x x

Windows Windows (Server 2003, Vista, 7, Server 2008) Intel 64-bits (X64) 64-bits x x x

Sun Sparc Solaris 2.8 and later version

Sparc v9 64-bits x x x x

Sun Intel Solaris 10 and later version

Intel 64-bits (X64) 64-bits x

x x x

IBM AIX 5.3.0 PowerPC 64-bits x x x x

IA-UX 11.23 Intel® Itanium 2 64-bits x x x

RedHat ES5 (ELSMP)

Linux-kernel 2.6 ELSMP Intel 64-bits (X64) 64-bits x x x x

The last five columns of this table indicate if the platform supports the following features:

Access InfiniteInsight® Access provides access to various external data format such as SAS® files, SPSS®, Matlab®, Microsoft Excel files and more.

JNI Java Native Interface

SAP InfiniteInsight® provides Java wrappers on top of both the C++ library (through JNI) and the CORBA server to ease integration with J2EE environment.

SAP InfiniteInsight® supports the following Java Virtual Machine:

SUN JVM 1.6 for Client/Servers installations

SUN JVM 1.6 and above for standalone installations

PAM Pluggable Authentication Module

SAP InfiniteInsight® Authenticated Server supports users authentication through PAM service. Depending on the PAM configuration for SAP InfiniteInsight®, PAM itself can then perform authentication using various mode (through UNIX passwords, Kerberos, ...)

SSL Secure Socket Layer

The communication between the Java Client and the Server can be encrypted using SSL communication instead of regular TCP networking.

Notes -

Page 4: II 70 Requirement Spec En

CUSTOMER SAP InfiniteInsight® 7.0 4 © 2014 SAP SE or an SAP affiliate company. All rights reserved- Technology

See the Annex, to know which binary corresponds to each platform.

For All Intel 32-bit processors (IA32) we recommend large L1 / L2 cache sizes For Sparc processors (Sparc v8 or v9) we recommend processors with correct Floating Point Unit

. For example, we do not recommend UltraSparc T1, as it shares one FPU for 8 Processing Units. The SAP InfiniteInsight® Connector is not available on Solaris 10 X64 platform since DataDirect is

not yet supporting this platform. SAP InfiniteInsight® is Unicode enabled, which means that data and meta-data (such as the name of columns) can be provided under native or Unicode character sets. The API is however fully Unicode based.

Page 5: II 70 Requirement Spec En

SAP InfiniteInsight® 7.0 CUSTOMER Stand-alone Version Requirements © 2014 SAP SE or an SAP affiliate company. All rights reserved- 5

2 Stand-alone Version Requirements

Before installing SAP InfiniteInsight®, please check the following on your computer (for Windows version users):

For a default installation, you will need about 260 Mbytes of free disk space:

about 215 Mbytes for SAP InfiniteInsight® (including some sample data files)

and 45 additional Mbytes if you need to install a Java Virtual Machine.

Minimum 256 Mbytes RAM (512 Mbytes if you use the HTML report feature). For using some user interfaces (using Java and CORBA technology), it is also necessary to

have a valid TCP protocol layer installed on the computer. The Microsoft Windows version requires the Microsoft ODBC component to be installed on

the computer. This component is usually installed on Microsoft Windows 2000 or Windows XP systems, or with Microsoft Office products. Microsoft ODBC can be found for download on the Microsoft website (http://www.microsoft.com/data/odbc). If it is not available on your computer, a system error message such as “a required DLL file, ODBC32.dll, was not found” can be displayed when starting the KXEN application.

By default the Data Cache is parameterized to use 500 MB on the disk for a 32-bit architecture. On a 64-bit architecture it uses 2 GB on the disk and 500 MB RAM. It can be parameterized in <KXEN_INSTALLATION_PATH>/DATACACHEMANAGER.CFG

Page 6: II 70 Requirement Spec En

CUSTOMER SAP InfiniteInsight® 7.0 6 © 2014 SAP SE or an SAP affiliate company. All rights reserved- Server & Client Version Requirements

3 Server & Client Version Requirements

IN THIS CHAPTER

Server Sizing ......................................................................................................................... 6 Network Requirements .......................................................................................................... 7 Java Runtime Environment for Client .................................................................................... 8 Java Web Start Deployment .................................................................................................. 8

3.1 Server Sizing

3.1.1 Data Access

Data access for the InfiniteInsight® is either through the ODBC layer of a relational database, or directly against files in a file system. InfiniteInsight® allows direct access to several types of files formats: SAS, SPSS, Excel, Minitab, delimited text, and fixed length text. For efficiency, InfiniteInsight® does not create a separate analytics data store. InfiniteInsight® reads data from the existing data sources, and saves output and models back into the data source.

When working in a client-server environment, all data are accessed by the server. The data source (ODBC, ...) must be installed (drivers, ...) and configured on the server.

Note - To know how to install and configure the data source, read the document Connect InfiniteInsight® to your Database Management System, that can be found in the InfiniteInsight® Documentation, in the section Support and Integration Documentation > Using SAP InfiniteInsight® with Databases.

3.1.2 CPU Usage

The training of a single model consumes the resources of a single CPU for the duration of the training. Each model being trained will spawn a separate thread, each being assigned to an available CPU. Training 2 models simultaneously on the same CPU will approximately double the training time of each model. Therefore, KXEN recommends 1 CPU (500MHz or above) per concurrent user.

Page 7: II 70 Requirement Spec En

SAP InfiniteInsight® 7.0 CUSTOMER Server & Client Version Requirements © 2014 SAP SE or an SAP affiliate company. All rights reserved- 7

3.1.3 Memory Consumption

A minimum of 512MB of RAM per concurrent user for the server is recommended. Additionally, each client should have 128MB-256MB RAM to run the User Interface. In general, a model consumes about 100KB of RAM per variable during training, or about 10MB per 100 variables. The InfiniteInsight® graphical user interface consumes about 30MB of RAM.

By default the Data Cache is parameterized to use 500 MB RAM on a 64-bit architecture. The settings can be changed in <INSTALLATION_DIR>/DATACACHEMANAGER.CFG

3.1.4 Hard Disk Space

InfiniteInsight® software requires about 100 MB for the server and about 50 MB for each client. No additional storage is required for data because, as discussed above, InfiniteInsight® does not create a separate data store. However, approximately 10MB to 100MB of disk space will be required per saved model, depending on the model type and number of variables in the model. Models may be stored in a database through ODBC, or on a file system.

By default the Data Cache is parameterized to use 500 MB on the disk on a 32-bit architecture and 2 GB on a 64-bit architecture. The settings can be changed in <INSTALLATION_DIR>/DATACACHEMANAGER.CFG

3.2 Network Requirements

Each of the three components involved in the application (the Name Server, the InfiniteInsight® Server and the Client Application) can be located on a different machine (although in most installations, both the Name Server and the InfiniteInsight® Server will be located on the same Server).

The communication protocol used under the CORBA framework is the TCP protocol. The first requirement is that the:

The InfiniteInsight® Server must be capable to access the InfiniteInsight® Name Server The Client application must be capable to access both the KXEN Name Server and the

InfiniteInsight® Server.

From a Network Administration point of view it means that:

Page 8: II 70 Requirement Spec En

CUSTOMER SAP InfiniteInsight® 7.0 8 © 2014 SAP SE or an SAP affiliate company. All rights reserved- Server & Client Version Requirements

The Name Server and the InfiniteInsight® Server will be assigned a specific TCP port. By default, the startup scripts we use fix them, and they should probably set properly depending on the network strategy.

Both of these ports must be accessible from the Client machine (for example network firewalls should allow communication on these ports between Client machine and the servers).

3.3 Java Runtime Environment for Client

Java Runtime Environment 1.6.0, which is available on the Java website.

3.4 Java Web Start Deployment

In order to provide Java Web Start deployment of InfiniteInsight® Client applications, a Web Server need to be installed, configured and started on the machine when InfiniteInsight® Server is installed. InfiniteInsight® Java Web Start has been tested on the following server configurations:

Windows IIS (Internet Information Service), on Microsoft Windows systems Apache Server (http://www.apache.org)

Page 9: II 70 Requirement Spec En

Annex List of Available Binaries

SAP InfiniteInsight® 7.0 CUSTOMER Annex © 2014 SAP SE or an SAP affiliate company. All rights reserved- 9

4 Annex

4.1 List of Available Binaries

The following table lists the binaries available for each platform.

Platform OS Binary Processors

Windows (32-bits) Windows (2000, 2003, XP, NT 4, Vista, 7) Microsoft and Visual Studio 8 Intel 32-bits (IA32)

Windows (64-bits) Windows (Server 2003, Vista, 7) Microsoft and Visual Studio 8 Intel 64-bits (X64)

Windows 2008 (64-bits) Windows 2008 Microsoft and Visual Studio 8 Intel 64-bits (X64)

Sun Sparc Solaris 2.8 and later version Sun CC 5.0 Sparc v9 (64-bits)

Sun Intel Solaris 10 and later version Sun CC 5.0 Intel 64-bits (X64)

IBM AIX 5.3.0 xlC PowerPC 64-bits

IA-UX 11.23 aCC Intel® Itanium 64-bit

RedHat ES5 (ELSMP) Linux-kernel 2.6 ELSMP g++ 4.1.2 Intel 64-bits (X64)

Page 10: II 70 Requirement Spec En

www.sap.com/contactsap

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company 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.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see

for additional trademark information and notices.