bb installation guidesapidp/... · web viewjune 2015august 2000 englishenglish semantic...

SAP HANA 1.0

June 2015English

Semantic Intelligence Configuration(EZ2)

SAP SEDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices Semantic Intelligence Configuration (EZ2): Configuration Guide

Copyright

© 2015 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.

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. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

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 SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE 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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© SAP SE Public of 33

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark


Revision Change Date Description

0 June 6, 2015 Initial



Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



ContentSemantic Intelligence configuration for SAP HANA Big Data Intelligence rapid-deployment solution..................................................................................................................................... 71 Purpose............................................................................................................................. 72 Preparation........................................................................................................................ 7

2.1 Prerequisites............................................................................................................72.2 Assumptions............................................................................................................7

3 Configuring Semantic Intelligence.....................................................................................83.1.1 Deploy the semantic Intelligence foundation delivery unit...................................83.1.2 Execute the seeding process (SQLScript)...........................................................83.1.3 Deploy the Semantic Intelligence business layer delivery unit............................9

4 Creating Operational and Administrative Users...............................................................114.1 Creating a Solution Admin User............................................................................114.2 Creating a Solution Business User........................................................................12

5 Configuring SAP Data Services.......................................................................................135.1 Configuring Data Service Server...........................................................................13

5.1.1 Install Python patch...........................................................................................135.1.2 Create Datastore Users to Connect to SAP HANA...........................................135.1.3 Create Local Repository and Configure Job Server..........................................145.1.4 Register Local Repository in SAP BusinessObjects BI platform Central Management Console......................................................................................................16

5.2 Apply for Authorization to Social Media Channels.................................................165.2.1 Edit Request URL for Channels........................................................................175.2.2 Apply Authorization for Twitter API 1.1..............................................................185.2.3 Apply Authorization for SAP Jam......................................................................185.2.4 Apply Authorization for Google Plus..................................................................195.2.5 Apply Authorization for YouTube.......................................................................205.2.6 Apply Authorization for Klout.............................................................................205.2.7 Apply Authorization for Facebook (New v2.2 version).......................................215.2.8 Apply Authorization for GNIP.............................................................................21

5.3 Import and Configure Data Services ATL File.......................................................225.3.1 Import Data Services ATL File...........................................................................225.3.2 Configure Datastore to SAP HANA Target Database........................................22

5.4 Executing Data Service Jobs to Retrieve Social Media Data.................................245.4.1 Executing Data Service Jobs to Retrieve Data..................................................245.4.2 Scheduling Data Service Jobs to Retrieve Data................................................25

5.5 Configuring Notifications........................................................................................266 Appendix.......................................................................................................................... 28

6.1 SAP HANA Models................................................................................................286.1.1 Configuration UI................................................................................................286.1.2 Attribute Views..................................................................................................296.1.3 The underlying SAP HANA Catalog objects......................................................306.1.4 Calculation Views (Optional).............................................................................326.1.5 Troubleshooting.................................................................................................32

6.2 Additional Resources.............................................................................................326.2.1 SAP HANA Guides............................................................................................326.2.2 Important SAP HANA Security Notes................................................................33



6.2.3 SAP Data Services............................................................................................33



Semantic Intelligence configuration for SAP HANA Big Data Intelligence rapid-deployment solution

1 PurposeThe purpose of this document is to describe the general configuration steps required to manually set up the semantic intelligence scope item for SAP HANA® Big Data Intelligence rapid-deployment solution. The configuration steps are within the system landscape you have already installed using the corresponding installation or configuration guides for installation.

2 Preparation2.1 PrerequisitesBefore you start installing this scenario, your system landscape must meet the prerequisites for the scope item. For more information about prerequisites, see the SAP Note 1956985 and the Quick Guide attached to that note.The SAP Note and the Latest Information and Configuration Guide: Getting Started document are available on the SAP Service Marketplace for rapid-deployment solutions, http://service.sap.com/rds-bdi

2.2 AssumptionsThe following assumptions are made about the configuration of the technical components for this solution:

1. SAP HANA platform is installed and configured.The installation and configuration of SAP HANA is not in scope for this solution. An installed and configured SAP HANA environment is a prerequisite for this rapid-deployment solution. For more information about the installation and configuration of the SAP HANA platform, see the SAP Help Portal http://help.sap.com/hana_platform

2. Ensure that SAP HANA® Info Access mobile app is installed and configured. Contact your system administrator in case it is not installed. For more information about SAP HANA Info Access, see the SAP Store http://store.sap.com

3. Ensure InformationAccess and libxsauthenticator entries are included in the xsengine.ini configuration.

4. Ensure automatic_language_detection is set to value of Yes in the preprocessor.ini area of the SAP HANA instance configuration.

5. SAP Data Services is installed and configured.The installation and configuration of SAP Data Services is not in scope for this solution. The rapid-deployment solution was designed with the assumption that data integration and delivery is performed by SAP Data Services. For more information about the installation and administration of SAP Data Services, see the SAP Help Portal, http://help.sap.com/bods

All other technical installation and configuration prescribed in preceding configuration guides is completed.


http://help.sap.com/bods

http://store.sap.com/

http://help.sap.com/hana_platform

http://service.sap.com/rds-bdi


3 Configuring Semantic Intelligence To implement the semantic intelligence scope item available with this rapid-deployment solution, you must configure the solution following the steps:

1. Deploy the semantic foundation delivery unit2. Execute the seeding process.3. Deploy the semantic business layer delivery unit

The steps are described in detail in the following sections.

3.1.1 Deploy the semantic Intelligence foundation delivery unit

The following steps are used to load the semantic intelligence foundation delivery unit.

The semantic intelligence foundation delivery unit can be imported using either Server or Client as source of delivery unit file location. If an import from the server is required, contact your system administrator for the server path. This step must be executed using the SAP HANA Deployment User that you created previously.

Procedure1. Ensure the semantic intelligence foundation delivery unit (HCO_RDS_BDI_SEM_SE_FND)

is downloaded into desired location. If it is not available, contact your system administrator.For more information about acquiring and downloading the delivery units, see the Getting Started Implementing Sentiment Intelligence for the SAP HANA Big Data Intelligence rapid-deployment solution guide attached to the SAP Note 1956985.

2. Choose the Quick Launch window 3. Select the SAP HANA deployment instance 4. Select Import Option.5. Choose Delivery Unit 6. Select Next.7. In the Select file section, choose the import location (Server or Client) and specify the

location of HCO_RDS_BDI_SEM_SE_FND.tgz8. Choose Finish to import the content of the delivery unit.

ResultThe HCO_RDS_BDI_SEM_SE_FND is successfully deployed. The Job Log shows the status of the package as it loads. If the load is successful, then the status displays Success. Navigate in the SAP HANA studio to the Catalog section and ensure SAP_RDS_BDI_SEMANTIC schema is visible.

3.1.2 Execute the seeding process (SQLScript)UseThe following process must be executed to ensure that the solution is configured properly and establishes references required to complete deployment:

ProcedureExecute the following SQL in the SQL Console:



CREATE FULLTEXT INDEX "INDEXLOCATION_POST" ON "SAP_RDS_BDI_SEMANTIC"."sap.rds-bdi.semantic.model::tables.SOCIALDATA_POST" ("LOCATIONNAME") CONFIGURATION 'EXTRACTION_CORE' ASYNC LANGUAGE DETECTION ('EN') PHRASE INDEX RATIO 0.200000 FUZZY SEARCH INDEX OFF SEARCH ONLY ON FAST PREPROCESS OFF TEXT MINING OFF TEXT ANALYSIS ON TOKEN SEPARATORS '\/;,.:-_()[]<>!?*@+{}="&';CREATE FULLTEXT INDEX "XIDX_SOCIALDATA_5_POST" ON "SAP_RDS_BDI_SEMANTIC"."sap.rds-bdi.semantic.model::tables.SOCIALDATA_POST" ("CREATIONUSERNAME") ASYNC PHRASE INDEX RATIO 0.200000 FUZZY SEARCH INDEX OFF SEARCH ONLY ON FAST PREPROCESS ON TEXT MINING OFF TEXT ANALYSIS OFF TOKEN SEPARATORS '\/;,.:-_()[]<>!?*@+{}="&';CREATE FULLTEXT INDEX "INDEXVOICEOFCUST_POST" ON "SAP_RDS_BDI_SEMANTIC"."sap.rds-bdi.semantic.model::tables.SOCIALDATA_POST" ("SOCIALPOSTTEXT") CONFIGURATION 'EXTRACTION_CORE_VOICEOFCUSTOMER' ASYNC FLUSH EVERY 1 MINUTES LANGUAGE DETECTION ('EN', 'FR', 'DE', 'IT', 'PT', 'ZH', 'ES', 'ZF') PHRASE INDEX RATIO 0.000000 FUZZY SEARCH INDEX OFF SEARCH ONLY ON FAST PREPROCESS OFF TEXT MINING OFF TEXT ANALYSIS ON TOKEN SEPARATORS '\/;,.:-_()[]<>!?*@+{}="&#$~|';

CREATE FULLTEXT INDEX INDEX_PRODUCT_1 ON "SAP_RDS_BDI_SEMANTIC"."sap.rds-bdi.semantic.model::tables.PRODUCT"("SHORT_TEXT"); CREATE FULLTEXT INDEX INDEX_CAMPTEXT_1 ON "SAP_RDS_BDI_SEMANTIC"."sap.rds-bdi.semantic.model::tables.CAMP_TEXT"("TEXT1");CREATE FULLTEXT INDEX INDEX_SERVICE_TICKET_1 ON "SAP_RDS_BDI_SEMANTIC"."sap.rds-bdi.semantic.model::tables.SERVICE_TICKET"("DESCRIPTION");

ResultThe FULLTEXT index of fields in SOCIALDATA_POST table is created successfully.

3.1.3 Deploy the Semantic Intelligence business layer delivery unit

UseThe semantic intelligence business layer delivery unit deploys the SAP HANA views, procedures, and roles. Perform the following steps to load the semantic intelligence business layer delivery unit for the solution.



The semantic intelligence configuration delivery unit can be imported using either Server or Client as source of delivery unit file location. If an import from the server is required, contact your system administrator for the server path. This step must be executed using the SAP HANA Deployment User that you created.

Procedure1. Ensure that the semantic intelligence business layer delivery unit

(HCO_RDS_BDI_SEM_SE) is downloaded into desired location. If it is not available, contact your system administrator.For more information about acquiring and downloading the delivery units, see the Getting Started Implementing Sentiment Intelligence for the SAP HANA Big Data Intelligence rapid-deployment solution Quick Guide attached to the SAP Note 1956985.

2. Choose the Quick Launch window 3. Select the SAP HANA deployment instance (for SYSTEM user) 4. Select Import Option.5. Choose Delivery Unit 6. Select next.7. In the Select file section, choose the import location (Server or Client) and specify the

location of HCO_RDS_BDI_SEM_SE.tgz8. Choose Finish to import the content of the delivery unit.

ResultThe semantic intelligence business layer delivery unit (HCO_RDS_BDI_SEM_SE) is successfully deployed as indicated by the status in the status window for this job.

Your deployment of semantic intelligence delivery units is now complete. To use the solution, you must create the required administrative and operational users. You also must modify the configuration settings as required for your business needs.



4 Creating Operational and Administrative Users

In this section, you create operational and administrative roles for users of this solution. The functional roles must be created for specific operational purposes. The designated roles are assigned different operational and access permissions that we recommend.Functional Roles required for operating and administering this solution:

1. Business User for access and operations of the solution.2. Solution Admin User for full administrative control in managing the solution.3. Integration Admin User manages SAP HANA content development and deployment.

The SYSTEM user does not have permission to perform all operations for this solution. The following role accounts described must be created for performing specific operations.

Semantic Intelligence is part of a larger domain for SAP HANA Big Data called Semantic Intelligence. Note that the following users that you are creating use SEMANTIC in the naming

The following steps must be performed with the SQL Editor window opened under SYSTEM account. Ensure that the appropriate Client session is set to the following user accounts you create.

4.1 Creating a Solution Admin User

This section must be performed using SYSTEM user account.

UseThe Solution Admin user has permission to manage this solution, and can perform all administrative tasks for this solution within SAP HANA. The following roles are required to perform all administrative tasks for this solution:

sap.rds-bdi.semantic.roles::RDS_BDI_MFG_SEMANTIC_ADMIN

Procedure1. Open the SAP HANA studio and logon to your SAP HANA system with SYSTEM user or

other user who has sufficient privileges to create new user2. Expand Security folder3. Right-click the User node, and choose New User4. Enter User Name and Password. For example, user name is SEMANTIC_ADMIN5. Assign following privileges to your administrator user.

Objects Details

Granted Roles Public (SYS)

sap.rds-bdi.semantic.roles::RDS_BDI_SEMANTIC_ADMIN

sap.bc.ina.service.v2.userRole::INA_USER



6. Save and activate the user.7. Change the initial password

You must change the initial password at first logon.

8. Verify the creation by logon with your semantic admin account created previously. SAP_RDS_BDI_SEMANTIC schema is visible in the catalog area of the

SEMANTIC_ADMIN user name

ResultThe semantic administrator is created and administrative roles are associated with this user.

4.2 Creating a Solution Business UserThis section must be performed using SYSTEM user account.

UseThe Business User is a consumer of information provided by this solution. For some scenarios, the Business User has permission to use the SAP HANA Big Data Intelligence application. The following roles are required by business users to use this solution:

sap.rds-bdi.semantic.roles::RDS_BDI_SEMANTIC_VIEWER


other user who has sufficient privileges to create new user2. Expand Security folder3. Right-click the User node, and choose New User4. Enter User Name and Password. For example, user name is SEMANTIC_VIEWER5. Assign following privileges to your administrator user.

Objects Details

Granted Roles Public (SYS)

sap.rds-bdi.semantic.roles::RDS_BDI_SEMANTIC_VIEWER

sap.bc.ina.service.v2.userRole::INA_USER

6. Save and activate the user.7. Change the initial password

You must change the initial password at first logon.

8. Verify the creation by logon with your SEMANTIC_VIEWER created previously. SAP_RDS_BDI_SEMANTIC schema is visible in the catalog area of the semantic

business user name

ResultThe semantic business user is created and viewer roles are associated with this user.



5 Configuring SAP Data Services The Semantic intelligence scope item uses SAP Data Services. To configure the solution for SAP Data Services, use the following the steps:

1. Configuring Data Service Server2. Applying Authorization for Social Media Channels3. Import Data Service ATL Code File.4. Executing Data Service Jobs to Retrieve Social Media Data

The steps are described in detail in the following sections.

5.1 Configuring Data Service Server5.1.1 Install Python patch

UseThis step is only relevant for python version 2.6.2 to enable the proxy over https.

Procedure1. Acquire the patch files issue1424152-py26.diff from the Web page

http://bugs.python.org/issue1424152 2. Follow the instruction to modify the python files

a. httplib.py b. urllib2.py

In your SAP Data Services Server folder: <install dir>\SAP BusinessObjects\Data Services\DataQuality\python\Lib

5.1.2 Create Datastore Users to Connect to SAP HANA

PrerequisitesYou must install the SAP HANA CLIENT first. The SAP HANA CLIENT version must match your SAP HANA SERVER version.

UseIn this activity, you create a user to connect the SAP Data Services Datastores with the SAP HANA database. You assign necessary roles and privileges to the user.


other user who has sufficient privileges to create new user2. Expand Security folder3. Right-click the User node, and choose New User4. Enter User Name and Password. For example, user name is DS_SEMANTIC_REPO5. Save and activate the user.6. Assign following privileges to your user for deployment.

Objects Details

Granted Roles

Public (SYS)

MODELING


http://bugs.python.org/issue1424152


Proposed User-ID SQL Objects Details UseDS_SEMANTIC_REPO DS_SEMANTIC_REPO is the

SAP HANA schema/catalog that is created when you create User.

AlterDropSelectUpdateInsertDeleteIndex

The schema is used to create data service repository for ATL file deployment

SAP_RDS_BDI_SEMANTIC schema

Create AnyAlterDropSelectUpdateInsertDeleteIndexTriggerDebugReferences

The schema is used to create the SAP HANA repository for target datastore

9. Save and activate the user again.10. Change the initial password

You must change the initial password after user creation.

5.1.3 Create Local Repository and Configure Job Server

PrerequisitesYou must have completed the previous section before performing the tasks in this section.Ensure that there is an empty database schema and user for use as the SAP Data Services Repository.

Procedure1. Logon to the server with the SAP Data Services installation.2. From the Windows menu, choose Start → Programs → SAP Data Services 4.x → Data

Services Repository Manager. 3. In the SAP Data Services Repository Manager dialog box, enter the following:

Repository DB type

Field User Action or Values Comments

SAP HANA Repository type Local

Database type SAP HANA

Database version HANA 1.x

Database server name

<SAP HANA Database server name>



Port <server port number>

User Name DS_SEMANTIC_REPO SAP HANA repository is created in the schema DS_SEMANTIC_REPO, the user name is the same

Password <password>

4. Choose the Create button.

Successful Message: The local repository was successfully created. (BODI-300055)

5. Close the Repository Manager application6. Choose the Close button.7. From the Windows menu, choose Start → Programs → SAP Data Services 4.x → Data

Services Server Manager.8. In the SAP Data Services Server Manager dialog box, choose the Configuration Editor

button.9. In the Job Server Configuration Editor dialog box, choose the Add button.10. In the Job Server Properties dialog box, enter the following:


Job Server name <job server name> For example, SEMANTIC_JS

Job Server port <port number> For example, 3500

11. Under Associated Repositories, choose the Add button section of the screen.12. In the Repository Information area, enter the following information:

Repository DB type


SAP HANA Database type

SAP HANA

Database version

HANA 1.x

Database Server Name



User Name DS_SEMANTIC_REPO

Password <password>

Default Repository

Selected

13. Choose the Apply button.14. On the Job Server Properties dialog box, choose the OK button.15. On the Job Server Configuration Editor Dialogue box, choose the OK button.16. On the SAP Data Services Server Manager dialog box, choose the Close and Restart

button.17. Choose OK to restart the Job Server service.



5.1.4 Register Local Repository in SAP BusinessObjects BI platform Central Management Console

Prerequisites Ensure that the local repository is created. You must be logged on to the server that installed with SAP BusinessObjects

business intelligence (BI) platform

Procedure1. From the Windows menu, choose Start → All Programs → SAP Business Intelligence →

SAP BusinessObjects BI platform 4 → SAP BusinessObjects BI platform Central Management Console.

2. In the Log On screen, enter the following and choose the Log On button:

Field User Action or Values

System <System-host>

User Name <User Name>

Password <Password>

Authentication Enterprise

3. On the Central Management Console screen, choose Data Services → Manage → Configure repository.

4. On Add Data Service Repository screen, enter the following:

Repository DB type


SAP HANA Repository Name

<repository name> For example, DS_SEMANTIC_REPO

Description <description>

Database type SAP HANA

Hostname <SAP HANA Database server name>


User name DS_SEMANTIC_REPO

Password <password>

5. Choose the Test Connection button.6. If the message box prompts that the connection was successful, choose OK.7. Choose Save

5.2 Apply for Authorization to Social Media Channels

Third-party data suppliers may require licensing or other requirements to be able to access social media feeds. Ensure that agreements are in place with these suppliers before proceeding with the following steps.



UseThe following provides the general steps required to request the key or token required by authorization of social media channel APIs. For more information, and any additional requirements, see the official Web page of the related social media channel.

Social media networks have different limits and threshold rates. Some limit requests to a fixed number while other networks provide a recommended range of settings based on different threshold levels. Your configuration must align with thresholds and restrictions for each social media network.

5.2.1 Edit Request URL for Channels

Procedure1. Open the configuration UI:

http://<hanahost>:80<instance#>/sap/rds-bdi/semantic/configuration/index.html

2. Logon with Solution Admin User that you created, refer to section 4.1

3. Choose Channel tab.

4. Choose Twitter and Select Edit.

5. In Proxy field, enter http://proxy:8080

6. In Request URL field, enter https://api.twitter.com/1.1/search/tweets.json

7. In Icon(only .png files), download and upload twitter logo

8. Choose the Update button

9. Repeat previous steps and maintain following information to each channel.

Name Proxy Request URL Comments

Twitter http://proxy:8080 https://api.twitter.com/1.1/search/tweets.json

Google+ http://proxy:8080 https://www.googleapis.com/plus/v1/activities

GNIP http://proxy:8080 https://search.gnip.com/accounts/SAPTrial/search/prod.json

Klout http://proxy:8080 http://api.klout.com/v2

SAP JAM http://proxy:8080 https://developer.sapjam.com

Facebook http://proxy:8080 https://graph.facebook.com/v2.2/

YouTube http://proxy:8080 <none> The URL is maintained under CONTENT tab of Configuration UI

RSS http://proxy:8080 <none> The URL is maintained under CONTENT tab of Configuration UI



5.2.2 Apply Authorization for Twitter API 1.1

Procedure1. Logon to the Twitter developer site, for example, https://dev.twitter.com/.

2. Logon with your Twitter account or create a new account.

3. Choose Manage Your Apps link under TOOLs group (at bottom of the page).

4. Choose Create New App.

5. Fill out the form. For Semantic Intelligence all fields are only needed internally for administration purposes.

6. Submit the form, an application is created and registered.

7. Select Keys and Access Tokens tab, your Consumer Key and Consumer Secret are created; copy them for following step.

8. In Your Access Token section, choose Create my access token button.

9. Your Access Token and Access Token Secret are created, copy them for step 13 use.

10. Open the configuration UI:




13. Choose Twitter and Select Authorization.

14. Paste or enter the value of Key in Consumer Key/Secret and Access Token Key/Secret.

15. Choose Save.

5.2.3 Apply Authorization for SAP JamThe SAP Jam API uses for the authentication the OAuth standard. A registered OAuth application and user are required to access the SAP Jam API. Identify the SAP Jam administrator for your company in the Admin menu by reviewing the user dropdown list in SAP Jam. For the data acquisition from SAP Jam, it is possible to use any user account. However, we recommend using a dedicated user for the data acquisition for security reasons. Your company administrator can help you to create a new, dedicated user account.

You must use the authentication key and secret of OAuth version 1.0. If you cannot create Key and Secret of OAuth version 1.0 with following procedure, contact your system administrator to generate it from the backend.

Procedure1. Logon to your company’s Jam account as an administrator.

2. At the top of the page, select the settings icon near account name, and then select Admin from dropdown list.

3. On the left side of the page, choose OAuth Clients.

4. At the bottom of the page, choose Add OAuth Client.

5. Make the following entries:



a. Company Name: Enter a name that identifies this application, for example: Corporation

b. Integration URL: Identify the link to Semantic Intelligence, for example

http://<hanahost>:80<instance#>/sap/rds-bdi/semantic/desktopUI5/index.html

c. Callback URL:

http://<hanahost>:80<instance#>/sap/rds-bdi/semantic/desktopUI5/index.html

d. There should be no entries to the other fields

6. Choose Save

7. Choose View from your created Application and the Key and Secret are generated.

8. Copy the value of Key and Secret for a following step.

9. Open the configuration UI, for example: http://<hanahost>:80<instance#>/sap/rds-bdi/semantic/configuration/index.html.



12. Choose SAP Jam

13. Select Authorization.

14. Paste or enter the value of Key and Secret in Consumer Key and Consumer Secret.

15. Choose Save.

16. The application will redirect you to SAP Jam.

17. Execute the logon with the designated user for the integration of SAP Jam. If SAP Jam does not ask you for a logon, check if the currently active user is correct.

18. Check the Authorize access box, and SAP Jam will redirect you back to the Configuration UI.

5.2.4 Apply Authorization for Google Plus

Procedure1. Logon to the Google APIs console, for example, https://code.google.com/apis/console.

2. Logon with your Google Credentials or create a new account.

3. Choose Create project.

4. In your project detail page, expand APIs & Auth folder, select APIs.

5. Choose the Google+ API from Browser APIs list and activate it by turning ON.

6. The Google+ API is displayed under the Enabled APIs list.

7. Choose Credentials under APIs & Auth folder.

8. Choose Create new key button and select Browser key in prompt window.

9. Choose Create button, your API KEY is generated.

10. Copy the API key for a following step.







14. Choose Google+


16. Paste or enter the value of Key in API Key.

17. Choose Save

5.2.5 Apply Authorization for YouTube

Procedure1. YouTube authorization is also accessed from the Google APIs console, for example,

https://code.google.com/apis/console.

2. Logon with your Google Credentials or create a new account.

3. Choose Create project.

4. In your project detail page, expand APIs & Auth folder, select APIs.

5. Choose the YouTube Data API v3 from Browser APIs list and activate it by turning ON.

6. The YouTube Data API v3 is displayed under Enabled APIs list.

7. Choose Credentials under APIs & Auth folder.

8. Choose Create new key button and select Browser key in prompt window.

9. Choose Create button, your API KEY is generated.

10. Copy the API key for a following step.





14. Choose YouTube



17. Choose Save

5.2.6 Apply Authorization for Klout

Procedure1. Logon to the Klout developer site, for example, http://developer.klout.com/.

2. Choose Register to build your awesome app.

3. Make the required entries and Register the App.

Result: Klout sends a confirmation e-mail

4. Choose the confirmation link that has been sent to you by e-mail.


https://code.google.com/apis/console


5. Copy the key of the Partner API v2 for a following step.


7. http://<hanahost>:80<instance#>/sap/rds-bdi/semantic/configuration/index.html



10. Choose Klout



13. Choose Save.

5.2.7 Apply Authorization for Facebook (New v2.2 version)

Procedure1. Logon to the Facebook Developer’s site, for example, https://developers.facebook.com

2. Logon with your Facebook Credentials or create a new account.

3. Choose Create My Apps and choose Add a New App from drop down list.

4. In the dialog box, choose Web site

5. Enter project name, create new project, and create App ID.

6. Return to the main page and select Tool & Support, choose Access Token Tool from dropdown list.

7. In your project detail page, Copy App Token.





11. Choose Facebook



14. Choose Save

5.2.8 Apply Authorization for GNIP

Gnip provides access to variant data sources, such as Twitter, Foursquare, WordPress, and others. Gnip require licensing to access those social media data sources. Ensure that agreements are in place and acquire the required consumer key and consumer secret from Gnip.



5.3 Import and Configure Data Services ATL File5.3.1 Import Data Services ATL File

PrerequisitesYou must have SAP Data Services repository for installing. We recommend importing the ATL file into an empty SAP Data Services repository.

UseThis activity imports the ATL File.

Procedure1. From the Windows menu, choose Start → Programs → SAP BusinessObjects Data

Services 4.x → Data Services Designer

For more information on importing files. See the Data Services Designer Guide at http://help.sap.com/bods in the Installation, Upgrade, and Deployment section.

2. In the Log On screen, enter the following:

Field Value Comment

System - host <System - host>


Password <Password>


3. Choose the Log On button4. Select the local repository you have created in the previous section Create Local

Repository and Configure Job Server for the location.5. Choose menu option Tools → Import From File.6. In the Open Import File dialog box, browse to the location and open the ATL file. 7. Ensure that following entries are visible:

Field Value

File name DS_RDS_BDI_SEMANTIC.atl

8. Enter Passphrase Welcome19. Choose Import.10. Ignore the warning message and choose OK

ResultAll repository objects required to run jobs are created in SAP Data Services.

5.3.2 Configure Datastore to SAP HANA Target DatabaseUseThe purpose of this activity is to adjust the datastore SAP_RDS_BDI_SEMANTIC to connect to the target SAP HANA database.

Procedure




1. From the Windows menu, choose Start → All Programs →SAP BusinessObjects Data Services 4.x → Data Services Designer. The Designer prompts you for logon information associated with your repository database.

Based on the of dependencies with SAP Data Services versions, the path to access SAP Data Services may be different.

2. In the BusinessObjects Data Services Repository Login dialog box, enter the following:

In System - Host, choose <BOE Server Name: BOE Server Port> using default value <your computer name>:6400.

In User name and Password

Authentication, select Enterprise.

3. Choose Log on button and then select the repository DS_SEMANTIC_REPO.

4. Choose OK and your BusinessObjects Data Service Designer screen appears.

5. In the Local Object Library (bottom-left section of the screen), choose the Datastores tab.

6. Open the context menu on the Datastore SAP_RDS_BDI_SEMANTIC and choose Edit.

7. On the Edit Datastore SAP_RDS_BDI_SEMANTIC dialog box, choose Advanced and choose Edit, you can modify the values for Data Source name, User name, and Password.

Parameter Value Comments

Datastore Name SAP_RDS_BDI_SEMANTIC Read-only

Datastore Type Database Read-only

Database type SAP HANA Read-only

Database Version HANA 1.x Based on your SAP HANA version

Use data source name (DSN)

Deselected

Data Source Server Name



User Name DS_SEMANTIC_REPO Input the User Name to access the SAP HANA Staging Database.

Password <password> Input the Password of the User Name given by your System administrator

Enable automatic data transfer

Selected

8. Choose Apply and then OK.9. Choose Apply and then OK again; ensure that no warning message appears.



ResultThe Datastore SAP_RDS_BDI_SEMANTIC is pointing to SAP HANA schema SAP_RDS_BDI_SEMANTIC.

5.4 Executing Data Service Jobs to Retrieve Social Media Data

5.4.1 Executing Data Service Jobs to Retrieve Data

UseIn this activity, you execute data service jobs to retrieve social media data. Before you can retrieve social media data, the system must be previously configured with the parameters and authorizations to access the data from the social media channels from the previous sections.

Procedure

Before executing data service jobs, CHANNEL, GROUP, CONTENT, TERM, and TASK must be previously configured. For more information, Administration: Data Services Settings, section 6, in the Semantic Intelligence for SAP HANA Big Data Intelligence rapid-deployment solution (EZ3) test script document.

1. Open the SAP Data Services Designer.2. Open the context menu of the Job_BDI_Semantic_Wrapper and choose Execute (F8).

3. In the Execution Properties dialog box, choose OK.

4. Execute Job_BDI_Semantic_Wrapper

5.

There are 11 jobs in total in our standard delivery that are executed as part of the wrapper job:

No Job Name Sequence

1 Job_BDI_Calc_Semantic After a data acquisition from one or more channels, always run this job

2 Job_BDI_Gender_Generation After a data acquisition from one or more channels, always run this job

3 Job_BDI_Geo_Detection_VOC After a data acquisition from one or more channels, always run this job

4 Job_BDI_Geo_Detection_Maintain This job should be run once a day

5 Job_BDI_Get_Twitter_Data Individual job for social data acquisition

6 Job_BDI_Get_Googleplus_Data Individual job for social data acquisition

7 Job_BDI_Get_YouTube_All_Data Individual job for social data acquisition



8 Job_BDI_Get_RSS_Data Individual job for social data acquisition

9 Job_BDI_Get_Klout_All_Data Individual job for social data acquisition

10 Job_BDI_Get_SAPJam_Data Individual job for social data acquisition

11 Job_BDI_Get_Gnip_Data Individual job for social data acquisition

You can also run the data retrieval job from the Semantic Web Application. For more information, see Administration Configuration Settings, section 7, in the Semantic Intelligence for SAP HANA Big Data Intelligence rapid-deployment solution (EZ3) test script document.

ResultThe search parameter related social media data is retrieved and loaded in the SAP HANA database

5.4.2 Scheduling Data Service Jobs to Retrieve DataUseMaintain the schedule to execute the SAP Data Services jobs automatically.

Procedure1. From the Windows menu, choose Start → Programs → SAP BusinessObjects Data

Services 4.x → Data Services Management Console.

2. In the User name and Password fields, enter your logon credentials.

Field Value Comment

System - host <System - host>


Password <Password>


3. Choose Log on.

4. Choose Administrator → Batch → DS_SEMANTIC_REPO

Select the Batch Job Configuration tab to display the jobs in the repository DS_SEMANTIC_REPO repository, for example the Job_BDI_Semantic_Wrapper 5. Choose Action “Add Schedule” of the selected job

6. On the Schedule Batch Job page

a. Enter a Schedule name and

b. Set the job to Active

c. Choose the Date Services scheduler as Scheduler

d. Select the scheduled days and time.

7. Check that the Job Server or Server Group are maintained. When they are not maintained, review the previous steps in the sections Create Local Repository and Configure Job Server.



8. Choose Apply to save the schedule.

You can also schedule the Data retrieval jobs individually for each social media channel. For more information, see Administration Configuration Settings, section 7, in the Semantic Intelligence for SAP HANA Big Data Intelligence rapid-deployment solution (EZ3) test script document.

ResultThe job can be scheduled to run repeatedly during a day.

5.5 Configuring NotificationsUseAutomatic emails can be sent to notify users when certain threshold values are exceeded. In order to configure email service, the following steps need to be performed.

Before proceeding with this task, an email service provider is needed to send emails. Use the System Administrator account in HANA to perform the following tasks.

Procedure

1. Open the XS HTTP Destination configuration file notification_smtp.xshttpdestMake changes to the configuration parameters as necessary. For example, replace the host and pathPrefix with the email service provider supplied values. If you have a proxy configured, enter the proxy details in proxyHost and proxyPort

host = <email service provider hostname>;port = 443;pathPrefix = <email service provider path>;proxyType = http;proxyHost = "proxy";proxyPort = 8080;authType = basic;useSSL = true;timeout = 30000;

Save and activate the file.

2. Start the SAP HANA XS Administration Tool. The SAP HANA XS Administration Tool is available on the SAP HANA XS Web server at the following URL: http://<hana server>:<port>/sap/hana/xs/admin/.

Click on Trust Manager and add a Trust Store for the email service provider, if it is not already configured. Import the server certificate from the emails service provider and add it to the Trust Store and save the details. Refer to the HANA Developer Guide for more details.



3. Go back to the home page of the SAP HANA XS Administration Tool by using the same URL: http://<hana server>:<port>/sap/hana/xs/admin/.

Navigate to the folder where the HTTP Destination Configuration file notification_smtp.xshttpdest file resides by choosing the following package structure sap->rds-bdi->semantic->logic. Choose the HTP Destination Configuration file.

Assign the Trust Store to the HTTP Destination File, and set the user credentials provided by the email service provider Save the configuration.The email service is now configured.

4. Choose XS Job Dashboard from the Home Page of the SAP HANA XS Administration Tool. Click on checkNotifications Job, and click on Add Schedule to add a schedule. You will be required to enter the credentials of the user to execute the job. Save the schedule.

For further details on configuring the Trust Store, HTTP Destination Configuration File and scheduling XS Job, refer to the HANA Developer Guide.



6 Appendix6.1 SAP HANA ModelsThe SAP HANA content package provides the prerequisites for reports used for the following analysis data:

Model overview Attribute views Calculation views Reports

PrerequisitesTo view the contents, you must install SAP HANA studio and have previously imported the SAP HANA Big Data Intelligence SAP HANA model into your SAP HANA server.For more information, see the Configuration Guide: Getting Started, attached to the SAP Note 1956985.

6.1.1 Configuration UIHTML Name Descriptionsap/rds-bdi/semantic/configuration Configuration UI for social media search

The underlying SAP HANA catalog object Table

Name Descriptionsap.rds-bdi.semantic.model::tables.SEARCH_LANGUAGE Search

Language

sap.rds-bdi.semantic.model::tables.SEARCH_CHANNEL Search Channel

sap.rds-bdi.semantic.model::tables.SEARCH_TERM Search Term

sap.rds-bdi.semantic.model::tables.SEARCH_INFO Search Terms with Max_ID

sap.rds-bdi.semantic.model::tables.SEARCH_TASK_NEW Search Task

sap.rds-bdi.semantic.model::tables.SEARCH_TASK_DETAIL Search Task Details

sap.rds-bdi.semantic.model::tables.CHANNEL_AUTHORIZATION Key and Token for API Authorization

sap.rds-bdi.semantic.model::tables.EXCLUDED_USER Excluded Social User for Data Privacy

sap.rds-bdi.semantic.model::tables.CRM_URL CRM Portal Information

sap.rds-bdi.semantic.model::tables.INCLUDED_USER Included



Social User for Data Privacy

sap.rds-bdi.semantic.model::tables.NOTIFICATION_MAIN Notification List

sap.rds-bdi.semantic.model::tables.NOTIFICATION_USER User for Notification

sap.rds-bdi.semantic.model::tables.NOTIFICATION_USER_GROUP Group of User for Notification

sap.rds-bdi.semantic.model::tables.NOTIFICATION_USER_GROUP_MAPPING

Mapping table for User and Group

sap.rds-bdi.semantic.model::tables.SI_PROPERTIES Settings

sap.rds-bdi.semantic.model::tables.CONTENT Content

sap.rds-bdi.semantic.model::tables.SEARCH_GROUP Group for Term

sap.rds-bdi.semantic.model::tables.SEARCH_GROUP_DETAIL Group Detail

sap.rds-bdi.semantic.model::tables.DS_CREDENTIALS Data Service Credentials

Sequence

Name Descriptionsap.rds-bdi.semantic.sequences::SEQ_EXCLUDED_USER Sequence for

Excluded User

sap.rds-bdi.semantic.sequences::SEQ_SEARCH_TASK_NEW Sequence for Tasks

sap.rds-bdi.semantic.sequences::SEQ_CONTENT Sequence for Content

sap.rds-bdi.semantic.sequences::SEQ_SEARCH_TERM Sequence for Search Terms

sap.rds-bdi.semantic.sequences::SEQ_NOTIFICATION_MAIN Sequence for Notifications

sap.rds-bdi.semantic.sequences::SEQ_NOTIFICATION_USER Sequence for User

sap.rds-bdi.semantic.sequences::SEQ_NOTIFICATION_USER_GROUP Sequence for User-Groups

sap.rds-bdi.semantic.sequences::SEQ_NOTIFICATION_USER_GROUP_MAPPING

Sequence for Mapping User and Group



6.1.2 Attribute ViewsThe attribute views support flexible UI reporting for Semantic intelligence of social media data.

Attribute View Name Descriptionsap.rds-bdi.semantic/AT_VOC Attribute View for

Voice of Customer

sap.rds-bdi.semantic/AT_VOC_CAMP Attribute View for Voice of Customer with Campaign

sap.rds-bdi.semantic/AT_VOC_SERV Attribute View for Voice of Customer with Service Ticket

sap.rds-bdi.semantic/AT_CAMP Attribute View for Campaign

sap.rds-bdi.semantic/AT_GEO_DETECTION Attribute View for Go Detection

sap.rds-bdi.semantic/AT_ACTIVE_SEARCH_TASK Attribute View for active Tasks

sap.rds-bdi.semantic/AT_INACTIVE_SEARCH_TASK Attribute View for inactive Tasks

sap.rds-bdi.semantic/AT_NOTIFICATION_FOR_SENDING Attribute View for Notification

sap.rds-bdi.semantic/AT_NOTIFICATION_FOR_SENDING2 Attribute View for Notification

sap.rds-bdi.semantic/AT_NOTIFICATION_OVERVIEW_FOR_DISPLAY

Attribute View for display Notification

sap.rds-bdi.semantic/AT_NOTIFICATION_RAW_DISPLAY Attribute View for Notification

sap.rds-bdi.semantic/AT_NOTIFICATION_USER_FOR_DISPLAY

Attribute View for Notification User

sap.rds-bdi.semantic/AT_SEARCH_TASK Attribute View for Tasks

sap.rds-bdi.semantic/AT_SERV

sap.rds-bdi.semantic/AT_TA_TYPE_FULL

sap.rds-bdi.semantic/AT_SOCIALDATA

sap.rds-bdi.semantic/AT_SERV

6.1.3 The underlying SAP HANA Catalog objects Table

Name Descriptionsap.rds-bdi.semantic.model::tables.SOCIALDATA Social Data

SOCIALDATA_POST

sap.rds-bdi.semantic.model::tables.SOCIALUSERINFO Information Of the user of the



Social Media Channel

$TA_INDEXVOICEOFCUST

$TA_INDEXLOCATION

sap.rds-bdi.semantic.model::tables.VOICEOFCUSTOMER Voice of Customer with average sentiment

sap.rds-bdi.semantic.model::tables.VOICEOFCUSTOMERDETAIL

Voice of Customer with Sentiment Detail

sap.rds-bdi.semantic.model::tables.VOICEOFCUSTCAMP Voice of Customer joined with Campaign

sap.rds-bdi.semantic.model::tables.VOICEOFCUSTSERV Voice of Customer joined with Service Ticket

sap.rds-bdi.semantic.model::tables.PRODUCT Product

sap.rds-bdi.semantic.model::tables.CAMP_HEADER Campaign Header Information

sap.rds-bdi.semantic.model::tables.CAMP_ITEM Campaign Item Information

sap.rds-bdi.semantic.model::tables.CAMP_TEXT Campaign Text

sap.rds-bdi.semantic.model::tables.CAMP_CHANNEL Campaign channel

sap.rds-bdi.semantic.model::tables.CAMP_TYPE Campaign Type

sap.rds-bdi.semantic.model::tables.SERVICE_TICKET Service Ticket

sap.rds-bdi.semantic.model::tables.SERVICE_PROCESS_TYPE

Service Ticket Process Type

sap.rds-bdi.semantic.model::tables.KLOUT_SCORE Klout Score Information

sap.rds-bdi.semantic.model::tables.FILTER_SETTING Filter Setting

sap.rds-bdi.semantic.model::tables.PROCEDURE_TIME Last Process Time

sap.rds-bdi.semantic.model::tables.CHANNEL_AUTO

sap.rds-bdi.semantic.model::tables.CRM_URL

sap.rds-bdi.semantic.model::tables.STARTPAGE Startpage and KPI Terms settings per User

sap.rds-bdi.semantic.model::tables.VIP_USER VIP SocialUsers

sap.rds-bdi.semantic.model::tables.WORKBENCHVIEW User Report Settings

Procedure



Name Descriptionsap.rds-bdi.semantic.procedures::PROC_SENT

6.1.4 Calculation Views (Optional)The calculation views provide data for SAP BusinessObjects Explorer® and SAP Lumira® reporting for Semantic intelligence of social media data.

Calculation View Name Descriptionsap.rds-bdi.semantic/CA_VOC Calculation View for Voice of

Customer

sap.rds-bdi.semantic/CA_VOC_CAMP Calculation View for Voice of Customer with Campaign

sap.rds-bdi.semantic/CA_VOC_SERV Calculation View for Voice of Customer with Service Ticket

sap.rds-bdi.semantic/CA_NOTIFICATION_FOR_SENDING

Calculation View for Notification

sap.rds-bdi.semantic/CA_TA_TYPE

6.1.5 Troubleshooting

6.1.5.1 Data Services Error while validating jobsIssue: The following error message occurs when validating the SAP Data Service jobs (BDI_ALL_*)Empty JOIN CONDITION clause for INNER JOIN or LEFT OUTER JOIN. (BODI-1116148)

Solution:1. Double-click the error message and navigate to detail data flow, which highlights the issue.2. Choose the From Tab

3. Choose Validate All from the Menu bar by choosing Validate → Validate All.4. A message displays - Validate: No Errors Found. 5. Save the Data Services flow. The error will not reoccur.

6.2 Additional ResourcesThe following reference manuals support the core products and are available on the SAP Help Portal http://help.sap.com

6.2.1 SAP HANA GuidesFor information about SAP HANA landscape, deployment, installation, administration, and security, see the resources listed in the table:Topic Guide/Tool Quick LinkSAP HANA Landscape, Deployment & Installation

SAP Help Portal

http://help.sap.com/hanaSAP HANA Master Guide SAP HANA Overall Installation Guide SAP HANA Automated Update Guide

SAP HANA SAP Help http://help.sap.com/hana_platform



http://help.sap.com/hana

http://help.sap.com/


Topic Guide/Tool Quick LinkSecurity Portal SAP HANA Security Guide

SAP HANA Installation and Administration

SAP Help Portal

http://help.sap.com/hana_platformSAP HANA Technical Operations ManualSAP HANA database Studio InstallationSAP HANA Trigger-based Replication (SLT) Installation GuideSAP HANA Developer Guide

SAP HANA Sizing SAP Service Marketplace

http://service.sap.com/quicksizer

6.2.2 Important SAP HANA Security NotesThe most important SAP Notes that apply to SAP HANA appliance software and SAP HANA database security are shown in the table:

SAP Note Title1598623 SAP HANA appliance - Security

1514967 SAP HANA appliance – Central Note

6.2.3 SAP Data ServicesFor information about SAP Data Services installation, administration, and security, see the resources listed in the table:Topic Guide/Tool Quick LinkSAP Data Services

SAP Help Portal

http://help.sap.com/bodsInstallation, Upgrade, Deployment Security Information System Administration and Maintenance



https://service.sap.com/sap/support/notes/1514967

https://service.sap.com/sap/support/notes/1598623

http://service.sap.com/quicksizer


bb installation guidesapidp/... · web viewjune 2015august 2000 englishenglish semantic...

Documents