Sap HANA Training doc

1
2012
SAP HANA 1.0 Online
Training
Trainer/Author: Param
SAP HIGH PERFORMANCE
ANALYTICAL APPLIANCE
(SAP HANA 1.0)

SAP HIGH PERFORMANCE ANALYTICAL APPLIANCE (SAP HANA 1.0)
January
2012
Page | 2
PART – ONE
Fundamental Manual
SAP HANA is that technology which allows the
processing of
huge quantities of real time data
in the ‘main memory’ of a server
to provide near time results
from transactions..

January
2012
Page | 3
LESSON 1: OVERVIEW
SAP In-Memory Appliance (SAP HANA)
SAP HANA is a hardware and software combination that integrates a number of SAP
components including the SAP In-memory database, Sybase Replication technology and SAP®
LT (Landscape Transformation) Replicator.
The SAP in-memory database is a hybrid in-memory database that combines row-based,
column-based, and object-based database technology. It is optimized to exploit parallel
processing capabilities of modern multi core/CPU architectures. With this architecture, SAP
applications can benefit from current hardware technologies.
SAP HANA contains the following components and tools:
• SAP® In-Memory Computing Engine (IMCE) Server 1.0
• SAP® IMCE Clients 1.0 – The IMCE clients are the interfaces by which the IMCE can
communicate with other components. The following subcomponents are included:
o IMCE ODBO 1.0 (OLE DB for OLAP)
o IMCE ODBC 1.0 (Open Database Connectivity)
o IMCE JDBC 1.0 (Java Database Connectivity)
o IMCE SQLDBC 1.0 (SQL Database Connectivity)
• SAP® IMCE Studio1.0 (includes SAP HANA Modeler)
• Sybase Replication Server 15 + Sybase Enterprise Connect Data Access (ECDA)
• Sybase Replication Agent
• SAP® HANA Load Controller 1.0 (includes R3Load, RepServer De-cluster Add-On)
• SAP® Host Agent 7.20
SAP HANA software is available in 3 different editions:
1. SAP HANA appliance software PLATFORM EDITION
2. SAP HANA appliance software ENTERPRISE EDITION
3. SAP HANA appliance software ENTERPRISE EXTENDED EDITION

January
2012
1. PLATFORM EDITION is for customers who already have a license for SAP Business
Page | 4
Objects - Data Services. Following are the sub-components:
 SAP HANA database
 SAP HANA studio
 SAP HANA client
 SAP Host Agent 7.20
 SAP HANA information composer
2. ENTERPRISE EDITION is for customers who do not already have all necessary licenses
for SAP Business Objects - Data Services. Following are the sub-components:
 SAP HANA studio
 SAP HANA client
 LT Replication AddOn
 LT Replication Server
 SAP Business Objects Data Services 4.0
3. ENTERPRISE EXTENDED EDITION is for customers who want to use the full potential
of all available features. Following are the sub-components:
 SAP HANA studio
 SAP HANA client
 LT Replication AddOn
 LT Replication Server
 SAP Business Objects Data Services 4.0
 Sybase Adaptive Server Enterprise (ASE) 15.5
 Sybase Replication Server 15 (incl. ECDA)
 Sybase Replication Server Agent 15
 SAP HANA load controller

January
2012
Page | 5
Background:
Technological Innovations driving the In-Memory Computing
RESULT: Transferring ONLY the results onto the Application Layer (Faster Response Time!!!)

January
2012
Page | 6

January
2012
LESSON 2. PRODUCT AVAILABILITY MATRIX (SUPPORTED H/W
VENDORS PLATFORM)
Page | 7
Below are the supported Hardware platforms- Vendors’ technical config. available.

January
2012
Page | 8
LESSON 3. ARCHITECTURE
3.1 SAP HANA Appliance Architecture View

January
2012
Page | 9
3.2 SAP HANA Database Engine View

January
2012
Page | 10
3.3 SAP HANA Data-Loading View
3.4 SAP HANA Data-Modeling
View

January
2012
Page | 11
3.5 SAP HANA Reporting View
3.6 SAP HANA Administrator View

January
2012
Page | 12
LESSON 4. SAP HANA SYSTEM LANDSCAPING
*** Implementing SAP HANA can be performed by using the following 3 options ***
Choice 1 (For customers with SAP ERP 4.6c or SAP ECC 6.0 on a NW release below NW
ABAP 7.02)
 For any customers on SAP ERP 4.6c, utilizing SLT will require setting up an intermediary system
with at least NW ABAP 7.02 load controller for replication into HANA
 For example, a SOLMAN system could be used for the SLT Add-on
 Supports Non-Unicode or MDMP systems for SAP ERP as long as SLT is installed on a NW 7.02
Unicode system
Choice 2 (For customers with SAP ECC 6.0+, running on at least NW ABAP 7.02)
 For any customers on SAP ECC 6.0+ running on NW ABAP 7.02 (must be fully Unicode), utilizing
SLT can be done directly for replication into HANA

January
2012
Page | 13
Landscape Transformation (LT) Replication Concept
Or, Choice 3 ( Any source, SAP or Non-SAP) Using SAP BO Data Services jobs.

January
2012
Page | 14
** What is installed on the SAP HANA Server? **
 Operating System: SuSE Linux Enterprise Server 11
 SAP HANA Database Software
 Additional SAP software, e.g. SAP Host Control
 3rd party programs/agents, e.g. monitoring agents, backup agents, …
HANA Appliance Server Configurations:-
A. Scale Up Config.
B. Scale Out Config.
A. Scale Up Config.
B. Scale Out Config.

January
2012
Page | 15
LESSON 5. SAP HANA SYSTEM SIZING GUIDELINES
HANA Appliance T-Shirt Sizes
Larger Organizations (T-Shirt Sizes):

January
2012
Page | 16
LESSON 6. DATA PROVISIONING
SAP HANA data provisioning can be performed using the following ways:-
1. SAP Business Objects- Data Services
2. SAP LT Replication Server
6.1 VIA DATA SERVICES
We know,
SAP BO Data Services can connect HANA to either/any SAP or Non-SAP systems.
Connectivity options already available in SAP BO Data Services 3.x
 ABAP Dataflow
o Generates and executes an ABAP program on the SAP Application Server that
reads data from an SAP table and outputs that data to a staging file. This file
must be accessible to Data Services, which requires the configuration of an
access/transfer mechanism (shared directory/FTP)
o For all datasets
 Remote Function Call (RFC) Read Table
o An RFC is made to read the contents of an SAP table
o For very small datasets only (<1000 records)
 RFC/BAPI function calls
o For lookups, not for mass data transfer
o For very small datasets only
 IDOCs

January
2012
Page | 17
What’s new in SAP BO Data Services 4.0
 Business Content Extractors (Data Sources)
o Originally designed for SAP BW to consume SAP Business Suite data
 Covers transactional (TRAN) and master data (ATTR, TEXT) extractors
 Table, view or function module based
 Function Module based extractors have logic/transformations to
produce “logical” records that can be used for reporting purposes
 Some extractors have delta recognition
So, with the new SAP BO DS 4.0 we now can utilize Business Content Extractors to acquire data
into HANA.
There are two ways:-
1. Without the Operational Data Provisioning(ODP) Data Replication API
 Works with all SAP ERP versions
 Only works with TRAN (transactional data) and ATTR (master data attributes) – TEXT
(master data text) and HIER (master data hierarchies) aren’t supported
 Must be used in an ABAP Dataflow
o An ABAP Dataflow generates and executes an ABAP program on the SAP
Application Server that reads data from any SAP table and outputs that data to a
file. This file is then consumed by Data Services, which requires the configuration
of an access/transfer mechanism (shared directory/FTP)
 No delta recognition – FULL LOAD only

January
2012
Page | 18
2. With the Operational Data Provisioning (ODP) Data Replication API
 Can be used directly in a Dataflow, no ABAP Dataflow required
o Data from ODP enabled extractors is streamed directly to Data Services
 Delta recognition for those Business Content Extractors that support it
 HIER (master data hierarchies) extractors aren’t supported
 Works with SAP ERP Central Component (ECC) 6.0. Additional SAP Notes reqd.
o https://service.sap.com/sap/support/notes/1521883
 Access to a limited number of officially released extractors
o https://service.sap.com/sap/support/notes/1558737
o All released extractors are fully supported by SAP
Hence, from practical point of view for HANA System Integrators, it’s advisable to use ‘With
OPD’ method in favorable scenarios.
With the Operational Data Provisioning (ODP) Contd…
Let’s see the Customer Benefits as follows.
Non-SAP NetWeaver Business Warehouse (BW) customers
 Get access to the Business Suite Extractors without having to go through SAP
NetWeaver BW
 There is no need for an ABAP Dataflow and therefore no ABAP program, no staging file,
and no configuration to access the staging file
SAP NetWeaver BW customers
 Can easily apply transformations when loading SAP NetWeaver BW
 Can now use one single tool to define all extraction, validation, and cleansing rules to
load all data (SAP and non-SAP) into SAP NetWeaver BW

January
2012
Page | 19
***Important Note***
The ODP Data Replication API is delivered via the SAP NetWeaver platform on which the SAP ECC
system runs. Please note that you can’t just upgrade the SAP NetWeaver platform, you MUST upgrade
the SAP ECC instance to a Support Pack (SP) level that corresponds to the required SAP NetWeaver SP
level.
At present Approx. 200 extractors has been released for Data Services by the SAP.
Please check https://service.sap.com/sap/support/notes/1558737
Also, please advice Data services team to check ROOSATTR table to check Extractors list.
PROCESS FLOW DIAGRAM : SAP HANA & SAP BO DATA SERVICES

January
2012
Page | 20
1. Create a connection to an SAP Target System in Data services.
2. Import SAP Metadata into Data Services.

January
2012
Page | 21
3. Import SAP Metadata into HANA via Data Services
4. Import HANA Metadata back into Data Services

January
2012
Page | 22
5. Create Data Services job to Load HANA

January
2012
Page | 23
6. Execute Data Services job to Load HANA
7. Preview uploaded data in HANA

January
2012
Page | 24
6.2 VIA LT (LANDSCAPE TRANSFORMATION) REPLICATION
We remember, LT Replication is for customers with SAP ERP 4.6c or SAP ECC 6.0 on a NW release
below NW ABAP 7.02)
Configuration for LT Replication :
A Schema defines the Config. of data replication parameters for a source system.

January
2012
Page | 25
Next,
Setting up of Data Replication in SAP HANA System
Finally, Loading of data
N.B For customers/system integrators opting for LT REPLICATION, kindly undergo a Specialized Step-By-Step guide course for just 5 Hrs !
Topics viz., Installation & Configuration, Architectures & Building blocks, Trigger based approach, Declustering tables, Performance
aspects, Data processing & Transformation, Implementation Rules, Tables & Table structures, Fields, Event based rules, Filter & Conditions,
Multi system support, Modeler & finally Replication from Non-SAP systems. Contact: param.th.2009@gmail.com

January
2012
Page | 26
LESSON 7. SAP HANA STUDIO VIEW
HANA Studio- Administrator View:

January
2012
Page | 27
HANA Studio- Features:
 Modeling
o Information Models
 Information models are used to create multiple views of transactional data that
can be used for analytical purposes.
o Attribute View, Analytic View, Calculation View , Calculation View enhanced with
Analytical View
 Data Preview
o Physical tables
o Information Models
 Import/Export
o Models
o Data Source schemas (metadata) – mass and selective load
o Landscapes
 Data Provisioning (both initial load and replication)
 Analytic Privileges / Security
 Troubleshooting / Trace / Logs
Important HANA Studio Terminologies:
 Data
o Attributes – descriptive data (known as Characteristics SAP BW terminology)
 Calculated Attributes
o Measures – data that can be quantified and calculated (known as key figures in SAP BW)
 Calculated Measures & Restricted Measures
 Views
o Attribute Views – i.e. DIMENSIONS
o Analytic Views – i.e. CUBES
o Calculation Views – similar to virtual provider with services concept in BW
 Graphical
 Script (SQL Script, CE Functions)
 Procedures
o Functions – re-usable functionality
 Analytic Privilege – security object
o Analytic Privileges

January
2012
Page | 28
LESSON 8. SAP HANA MODELING
Levels/Steps of Modeling:
1. Attribute View
2. Analytic View
3. Calculation View
We know,
Attribute View is equivalent to Dimensions & Analytic View is equivalent to Cubes
1st Step: Attribute View (Dimensions)
– Build the needed master data objects as ‘Attribute Views’
– Join text tables to master data tables

January
2012
Page | 29
2nd Step: Analytical View (Cubes)
– Create Cube-like view by joining attributes view to Fact data
– Build a ‘Data Foundation’ based on transactional table
– Selection of ‘Measures’ (key figures) ...
– Add attributes
– Join attribute views to data foundation
3rd Step: Calculation View
(These are used when the Joins are NOT sufficient.)
(They look like a View & has SQL Script inside.)
– Composite view of other views (tables, re-use join)
– Consists of a Graphical & Script based editor

January
2012
Page | 30
Extra Info.:
Analytic Privileges
– Analysis authorizations based on attributes in analytic views are used here.
Ok, now lets discuss each Modeling View in detail as follows !

January
2012
Page | 31
8.1 Attribute View
They are reusable dimensions used for analysis. (Time, Account, Product)…
– Can be regarded as Master Data tables/Dimensions
– Can be linked to Fact tables in Analytical Views
Process flow within Attribute View:

January
2012
Page | 32
1. Table Selection: An Attribute View is a JOIN of several tables.
2. Table joins & Properties: Defining the JOIN properties.

January
2012
Page | 33
JOINS Definitions/Meaning:
3. Selecting Attributes:

January
2012
Page | 34
4. Create/Select Hierarchy
Set output-field property “Hierarchy active” to “true”
Next, you can define a Hierarchy level.

January
2012
Page | 35
5. Save & Activate
6. Data Preview

January
2012
Page | 36
8.2 ANALYTIC VIEW
Analytic View can be regarded as a “Cube” / “Data Foundation”
Process flow within Analytical View:

January
2012
Page | 37
1. Set Parameters
2. Table Selection

January
2012
Page | 38
3. Table joins & Properties:
Analytical View Editor:
4. Select Attributes & Measures :

January
2012
Page | 39
5. Defining Calculated Measures
Note: Remember Calculated Key-Figures (CKFs), its renamed here as Calculated Measures !

January
2012
Page | 40
6. Defining Restricted Measures
Note: Remember Restricted Key-Figures (RKFs), its renamed here as Restricted Measures !

January
2012
Page | 41
7. Save & Activate View

January
2012
Page | 42
8. Data Preview

January
2012
Page | 43
8.3 CALCULATION VIEW
They are used to create your own data foundation using database tables, attribute views,
analytic views and calculation views to address a complex business requirement.
It is the View visible to Reporting tools.
There are 2 types of Calculation Views:
Let’s dive little deeper into these 2 types of Calculation Views.

January
2012
Page | 44
A. Graphical Calculation View:
We can Select Fields/ or use Filters, Add Attributes/Measures to Output.

January
2012
Page | 45
We can Combine data from Tables/Projections & define the UNION.
This UNION modeling concept is very much similar to Multiproviders. There you go BW guys!

January
2012
Page | 46
B. Script Calculation View:
Used for more customizing requirements.
SQL or SQL Script required to write the code.
The SELECT statements support the full range of SELECT statements
To use the content of a variable as input, the variable name is pre-fixed and post-fixed by ‘@’

January
2012
Page | 47
Side-effect free re-usable code sections.
Allows the creation of new Table types dynamically.

January
2012
Page | 48
Script Calculation View Contd./-
Build-in Functions:
Familiarizing some Build-in functions

January
2012
Page | 49
8.4 EXPORT & IMPORT
We can export & import Information Models between systems, if required.
Let’s know understand the Process Flow for Exporting & Importing Information Models.
But, first we need to create Delivery Unit.
We use a delivery unit to create a group of transportable objects for content delivery and to
export information models from source system to target server.
Steps:
Step 1: From Quick Launch -> Click ‘Delivery Units’ under ‘Setup’.

January
2012
Page | 50
Step 2: Click ‘Create’ from ‘Manage Delivery Units’
Step 3: Provide your Delivery Unit details & click ‘OK’.

January
2012
Page | 51
Step 4: Assign Package to Delivery unit.
Now, the Delivery Unit is create, we can start with the Process flow of Export & Import Info.
Models.
There are the following modes of Export & Import:
A. Exporting Models(Server)- Export models that use content delivered by SAP
B. Importing Models(Server)- Import models that use content delivered by SAP
C. Exporting Models(Client)- Export models that use user-defined content
D. Importing Models(Client)- Import models that use user-defined content.

January
2012
Page | 52
 Export Information Model:
After creating the Information model, we can click on Menu-> File->Export.

January
2012
Page | 53
1. EXPORTING MODELS (CLIENT)
Select Export type

January
2012
Page | 54
2. EXPORTING MODELS (SERVER)
Select Export type

January
2012
Page | 55
Verify SAP Content export script
Choose your Source System
Select Delivery unit, verify the Export XML File & click on ‘Finish’
**You will require this file path to Import in target system

January
2012
Page | 56
Next, let’s study the Import Info. Model Process flow:
3. IMPORTING MODELS (CLIENT)

January
2012
Page | 57

January
2012
Page | 58
4. IMPORTING MODELS (SERVER)
Choose the import type Server
Select target system

January
2012
Select the File to Import (Generated from Export Model-Server source system) & Click ‘Finish’
Now, your Information model is imported & ready for use in your Production Environment.
Page | 59

January
2012
This brings to the end of PART ONE of SAP HANA training where we tried to explore
the following topics & understood the fundamentals.
Page | 60
Lesson 1. Overview SAP HANA 1.0
Lesson 2. Product Availability Matrix(Supported H/w Vendors Platform)
Lesson 3. Architecture
3.1 SAP HANA Appliance Architecture View
3.2 SAP HANA Database Engine View
3.3 SAP HANA Data-Loading View
3.4 SAP HANA Data-Modeling View
3.5 SAP HANA Reporting View
3.6 SAP HANA Administrator View
Lesson 4. SAP HANA System Landscapes
Lesson 5. SAP HANA System Sizing Guidelines
Lesson 6. Data Provisioning
6.1 Via Data Services
6.2 Via Replication (Landscape Transformation)
Lesson 7. SAP HANA Studio view
Lesson 8. SAP HANA Modeling
8.1 Attribute View
8.2 Analytic View
8.3 Calculation View
8.4 Export & Import Info. Models.

January
2012
Page | 61
PART TWO
Topics:
Lesson 9 SAP HANA Reporting
9.1 Client connectivity options
9.2 SAP BO BI 4.0
9.3 MS-Excel
9.4 SAP BO Analysis
9.5 SAP BO Explorer
9.6 Semantic Layer (Universe)
9.7 SAP Crystal Reports ( Enterprise, Dashboards & WebI)
9.8 SAP Crystal Reports 2011
Lesson 10 User Management (SAP BI 4.0 Integration)
Lesson 11 User Management (Single-Sign-on SSO)

January
2012
Page | 62
LESSON 9 SAP HANA REPORTING
9.1 CLIENT CONNECTIVITY OPTIONS
HANA 1.0 provides various interface reporting options:
 ODBO – OLE DB for OLAP
 ODBC – Open DataBase Connectivity
 JDBC – Java DataBase Connectivity
 BICS – BI Consumer Services

January
2012
9.2 SAP BO BI 4.0
The common BI Suite to Put Together Information in User’s required Format are as follows:
Page | 63
 SAP Business Object Explorer
 WebI (Interactive Analysis)
 Xcelsius (Dashboard Design)
 Crystal Reports
*** Reporting using HANA is performed through the above tools, hence there’s nothing new in HANA
reporting. If you have experienced working with SAP BOBJ Explorer or any of the above tools, then it’s just a
piece of cake for you!!

January
2012
Page | 64
SAP BOBJ Xcelsius (Dashboard Design)
Consume attractive, personalized dashboards online or offline
 Access to personalized, Flash-based dashboards
 Secure visualizations anywhere –portal, reports, PDF, MS Office documents
Empower business users with interactive information
 Powerful “what-if” analysis with sliders and other controls
 Ability to drill-down into details
 Pre-built components, skins, maps, charts, gauges, and selectors

January
2012
Page | 65
SAP Crystal Reports
Next generation Report Designer experience
 Common query design experience across all data sources with new semantic layer
 Automated report translate on for global deployments

January
2012
Page | 66
SAP BOBJ WebI
 Intuitive, Web-based interface with offline capabilities
 Multi-source access
 Interactivity with filtering, ranking, sorting, calculations, etc
 Intuitive, business-centric view of information

January
2012
Page | 67
SAP BOBJ Explorer
 Simplicity and speed of search
 Intuitive data exploration and visualization
 Fast response across mountains of data anywhere in the organization
 Accelerated version with in-memory technologies
 Support for heterogeneous data sources

January
2012
Page | 68
9.3 MS-EXCEL
Multidimensional reporting is available via Excel Pivot Tables

January
2012
Page | 69
Analytic Calculation views (Cubes) are available per your authorizations:
After selecting your “Cube”, save the Data Connection & click on ‘Finish’.
That’s it, you can then start analyzing your information over the MS-Excel.

January
2012
Page | 70
9.4 SAP BO ANALYSIS
Did you know, MS-Excel 2010 or MS-Powerpoint 2010 can be enhanced with HANA Information models
by using ODBC Connection ?
Let’s do it !
Just insert HANA datasource.
And, you’ll see new Menu called ‘Analysis’ as below:
There you go, you can view your information using MS-Excel 2010.

January
2012
Page | 71
9.5 SAP BO Explorer
 Search Engine ‘on-the-fly’
 Searches across all data sources
 Any universe accessible source
 And of course any accessible HANA system

January
2012
Page | 72
9.6 SEMANTIC LAYER (UNIVERSE)
Enables the business users to freely and securely access, analyze, enrich and share information
using familiar business terms.
Common semantic layer = one unified approach for meta-data support

January
2012
Page | 73
***Advanced topic ( Extra Know-How)
Reporting off HANA 1.0 from a Relational Universe !
Information Design Tool
Steps to create a Universe:
Step 1: Create a local Project

January
2012
Page | 74
Step 2: Create a Connection
Step 3: Select your Driver (JDBC or ODBC ?)

January
2012
Page | 75
Step 4: Define Parameters
Step 5: Provide additional connection details
Note: recommended to select the “Disconnect after each transaction”

January
2012
Page | 76
Step 6: Create Data Foundation
We know,
Data Foundations can be single or multi-source , maps tables and views the universe,
defines joins, reporting contexts.
Next,
 Select “Single Source” if HANA is the unique data source for the reporting needs
 Select “Multisource-Enabled” if data from HANA must be combined with other sources
Then,
Once Data Foundation is built, we can start HANA reporting from the relational universe.
Hence, we can have a Semantic Layer (Universe) for HANA reporting requirements.

January
2012
9.7 SAP CRYSTAL REPORTS ( ENTERPRISE, DASHBOARDS & WEBI)
Page | 77
Pre-requites: Semantic Layer (Relational Universe)
Quick view screenshots as follows for Universe queries, WebI etc.
Universe queries

January
2012
Page | 78
Crystal reports for Enterprise 4.0
WebI

January
2012
Page | 79
9.8 SAP CRYSTAL REPORTS 2011
Crystal Reports 2011 (CR2011) can used in IMCE through (SQL) via the ODBC or JDBC driver
Client drivers must be installed on the machine where CR2011 is running
 CR2011 is a 32-bit application, therefore uses the 32-bit ODBC driver for IMCE
 A DSN entry must be entered from the ODBC 32-bit Administrator tool
Then, create the Connection by clicking on ‘Database Expert’ icon in CR 2011

January
2012
Page | 80
IMCE appears as a Catalog like any other relational database
Tables and Views can then selected from the Catalog for reporting
Then, begin you report design in CR 2011
That’s all folks !
We had finished PART TWO, where in we have discovered that reporting off HANA is through
SAP BOBJ reporting tools & a few tips on creating Semantic Layer (Universe).

January
2012
ADDITIONAL LESSONS (HANA training freebies)
LESSON 10 USER MANAGEMENT (SAP BI 4.0 INTEGRATION)
Page | 81
IMCE User Credentials Mapping in BI 4
Each individual BI 4 user can be assigned IMCE credentials from the CMC
*** I’m sure SAP BO Dataservices 4.0 guys must be aware of CMC (Central Management Console) operations.***
Please make sure the option “Synchronization of Credentials” is UNCHECKED to avoid the credentials
mapping being overwritten.

January
2012
Once, the connection is configured, Test your connection after providing the correct Authentication
Mode.
Page | 82
When, the Test Connection is successful, then IMCE User Management is connected with BI 4.0

January
2012
Page | 83
LESSON 11 USER MANAGEMENT (SINGLE-SIGN-ON SSO)
Configuring the SSO
Step 1: Create the Service User in Active Directory/Domain Controller
Step 2: Provide login credential

January
2012
Page | 84
Step 3: Create Externally Identified User in SAP HANA Studio

January
2012
Page | 85
Step 4: Add system in HANA Studio

January
2012
Page | 86
Step 5: Set connection properties
User should now be able to log on to Studio (and DB) without further authentication
Hence, the SSO is been successful setup for IMCE User Management environment.
Finally, we have explored the additional topics on User Management BI 4.0 Integration & SSO!
This, brings me to the end of my SAP HANA Online
training !
Thank you for your patience !
And, thank you once again for your esteem interest in
learning sap hana. All the best my friends !!!

Sap HANA Training doc

Recommended

More Related Content

What's hot (20)

Viewers also liked (19)

Similar to Sap HANA Training doc (20)

Recently uploaded (20)

Sap HANA Training doc