sas social network analysis server 2...• jboss application server • ibm websphere application...

SAS® Social NetworkAnalysis Server 2.2Installation and Configuration Guide

SAS® Documentation

The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2010. SAS® Social Network Analysis Server 2.2: Installation andConfiguration Guide. Cary, NC: SAS Institute Inc.

SAS® Social Network Analysis Server 2.2: Installation and Configuration Guide

Copyright © 2010, SAS Institute Inc., Cary, NC, USA

All rights reserved. Produced in the United States of America.

For a hardcopy book: No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means,electronic, mechanical, photocopying, or otherwise, without the prior written permission of the publisher, SAS Institute Inc.

For a Web download or e-book:Your use of this publication shall be governed by the terms established by the vendor at the time you acquire thispublication.

U.S. Government Restricted Rights Notice: Use, duplication, or disclosure of this software and related documentation by the U.S. government issubject to the Agreement with SAS Institute and the restrictions set forth in FAR 52.227–19 Commercial Computer Software-Restricted Rights (June1987).

SAS Institute Inc., SAS Campus Drive, Cary, North Carolina 27513.

1st electronic book, December 2010

SAS® Publishing provides a complete selection of books and electronic products to help customers use SAS software to its fullest potential. For moreinformation about our e-books, e-learning products, CDs, and hard-copy books, visit the SAS Publishing Web site at support.sas.com/publishing or call 1-800-727-3228.

SAS® and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and othercountries. ® indicates USA registration.

Other brand and product names are registered trademarks or trademarks of their respective companies.

http://support.sas.com/publishing

http://support.sas.com/publishing

Contents

PART 1 Introduction 1

Chapter 1 • Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Purpose of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3SAS Administrator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Database Administrator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3System Administrator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2 • Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

PART 2 Pre-Installation 7

Chapter 3 • Preparing for SAS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Pre-Installation Requirements for SAS 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Create SAS Social Network Analysis Server Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Java Development Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Web Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Junit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Verify the Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11SAS Intelligence Platform Pre-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 4 • Preparing the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Oracle Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13MySQL Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14IBM DB2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Microsoft SQL Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Create Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Modifications to Database Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Database Client and JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

PART 3 Running the SAS Deployment Wizard 31

Chapter 5 • Running the SAS Deployment Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Install and Configure Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Run the SAS Deployment Wizard in Install Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Apply Hot Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Run the SAS Deployment Wizard in Configure Mode . . . . . . . . . . . . . . . . . . . . . . . . . 35

PART 4 Post-Installation and Configuration 39

Chapter 6 • Post-Installation Steps for SAS 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Post-Installation Steps for SAS 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 7 • Post-Installation Database Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43MySQL Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 8 • Register Database Identities and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Register Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 9 • Register Database Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63MySQL Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Chapter 10 • Register Data Mart Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Create the SAS Data Mart Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Register a SAS Library for Alert Detail Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Register a SAS Library for Alert Summary Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Register a SAS Library for Data Mart Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Register a SAS Library for Network Link Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Register a SAS Library for Network Node Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Register a SAS Library for Alert Generation Process Input Tables . . . . . . . . . . . . . . . . 99

Chapter 11 • Configure the Autoexec and Verify Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Modify SAS to Load the SAS Social Network Analysis Server Autoexec File . . . . . 101Verify Access to the Libraries and Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

PART 5 Configure Core Entity Tables, Job Calendar, andStored Processes 105

Chapter 12 • Configure Core Entity Tables, Job Calendar, and Stored Processes . . . . . . . . . 107Load the Entity Tables and Job Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Import SAS Stored Processes and Deploy Web Services . . . . . . . . . . . . . . . . . . . . . . 110Modify SAS Stored Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

PART 6 Register Investigators and ETL Developers 115

Chapter 13 • Register Investigators and ETL Developers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Initialize Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Synchronize Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Register ETL Developers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

PART 7 Optional Features 121

Chapter 14 • Optional Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

iv Contents

Comments Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Integrating with a Geographic Map Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Integrating with SAS Enterprise Case Management . . . . . . . . . . . . . . . . . . . . . . . . . . 125Extract EAR File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Recreate the EAR File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Contents v

vi Contents

Part 1

Introduction

Chapter 1Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1

Chapter 1

Introduction

Purpose of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

SAS Administrator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Database Administrator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

System Administrator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Purpose of this DocumentThis document provides installation and configuration information for the SAS SocialNetwork Analysis Server.

Target AudienceThe target audience members for this document are SAS administrators, databaseadministrators, and system administrators using the SAS Social Network Analysis Server.

SAS Administrator TasksUsing the information in this document, SAS administrators are able to assign investigatorroles to investigators for the SAS Social Network Analysis Server.

Database Administrator TasksUsing the information in this document, database administrators are able to configureschema and database user IDs for use with SAS Social Network Analysis Server.

3

System Administrator TasksUsing the information in this document, system administrators are able to perform thefollowing tasks:

• configure data sources and data stores

• configure investigation paths

Technical SupportSAS Technical Support is the first group to contact regarding installation and configurationproblems that installers encounter in the field. To contact SAS Technical Support, performthe following steps:

1. Go to www.sas.com.

2. Select Contact Us.

3. Select the appropriate Web page or telephone number from the Support Contactssection of the page.

4 Chapter 1 • Introduction

Chapter 2

Installation Overview

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Installation OverviewThe following are the high-level steps for installing and configuring the SAS SocialNetwork Analysis Server:

1. Check the pre-installation requirements for SAS 9.2, the system requirements for SAS9.2, and the system requirements for the SAS Social Network Analysis Server 2.2.

2. Create operating system accounts. For deployments that need to make requests for userIDs, making the request early can avoid delays to installing and configuring SASsoftware.

3. Install third-party software:

a. Install and configure one of the following databases:

• Oracle Database

• MySQL Server

• IBM DB2

• Microsoft SQL Server

b. Install one of the following Web application servers:

• JBoss Application Server

• IBM WebSphere Application Server

• Oracle WebLogic Server

4. Use the SAS Deployment Wizard to install, but not configure, the following:

a. SAS Foundation

b. SAS Social Network Analysis Server

c. SAS Social Network Analysis middle tier (can be installed on the same machineas the SAS Social Network Analysis Server)

5. Contact SAS Technical Support for hot fix information and software.

6. Run the SAS Deployment Wizard in configure mode to configure the installed SASsoftware.

5

7. Perform post-installation and configuration tasks:

a. Configure SAS/ACCESS.

b. Seed the database configuration tables with data that is needed by the SAS SocialNetwork Analysis Server.

c. Register the database and SAS libraries.

d. Modify the SAS Social Network Analysis Server autoexec file.

e. Load the entity configuration tables and job calendar.

f. Import SAS stored processes and deploy Web services.

Note: If you are performing a multiple-machine deployment, you cannot performthis step until the SAS Deployment Wizard completes the configuration of themiddle-tier machine.

g. Initialize users and groups.

h. Synchronize users and groups.

6 Chapter 2 • Installation Overview

Part 2

Pre-Installation

Chapter 3Preparing for SAS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 4Preparing the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

7

Chapter 3

Preparing for SAS Installation

Pre-Installation Requirements for SAS 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Create SAS Social Network Analysis Server Users . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Java Development Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Web Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Junit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Verify the Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

SAS Intelligence Platform Pre-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Pre-Installation Requirements for SAS 9.2The following table contains URLs to reference documentation for installing SAS 9.2Foundation on UNIX and Microsoft Windows environments. Go to the URL thatcorresponds to the appropriate operating system and follow all the applicable steps on thosepages.

Table 3.1 SAS 9.2 Installation References

OperatingSystem Title URL

UNIX Installation Note 36467:Documentation for a SAS® 9.2installation on UNIX

http://support.sas.com/kb/36/467.html

Windows Installation Note 36553:Documentation for installing SAS®9.2 Phase 2 (TS2M3) in Windows32-bit, x64, and 64-bit Itanium (IPF)operating environments


9



Create SAS Social Network Analysis Server UsersThe SAS Social Network Analysis Server uses an alert generation process to analyze data,perform rule-based and analytic processing, and then generate alerts from the analyzeddata. In order to run the alert generation process, the SAS Social Network Analysis Serverrequires an operating system user ID. Throughout this document, the sample user ID issassna, though an existing user ID can be used. As a post-installation task, SASManagement Console is used to create a user ID in metadata and associate this user ID withit. If you do not already have an operating system account to use for running the alertgeneration process, then create one, or request one from your system administrator.

If you are using IBM DB2 and the database uses operating system user IDs forauthentication, then you need to create two additional user IDs, snauser and snaread.

Java Development KitUse the following URL to identify the version required for the specific hardware andoperating environment:

http://support.sas.com/resources/thirdpartysupport/v92m3/index.html.

Refer to the Java Development Kits (JDK) section at the URL. Be sure to get the JDK thatmatches your Web application server.

Note: It is not necessary to download a JDK if the IBM WebSphere Application Server isused in the deployment. The IBM WebSphere Application Server includes a specificversion of the IBM JDK that is automatically installed and used by the WebSphereApplication Server.

Web Application ServerThe SAS Social Network Analysis Server supports the JBoss Application Server, IBMWebSphere Application Server, and Oracle WebLogic Server. For more information aboutthese Web application servers, see the SAS 9.2 Support for Web Application Servers andHTTP Servers page at the following URL: http://support.sas.com/resources/thirdpartysupport/v92m3/index.html.

JunitIf the SAS Deployment Tester is installed in addition to the SAS Social Network AnalysisServer, then Junit 4.0 is recommended. See the Junit information that is provided on theSAS 9.2 Support for Additional Software Products page at the following URL:

http://support.sas.com/resources/thirdpartysupport/v92m3/othersw.html#tab_junit

10 Chapter 3 • Preparing for SAS Installation

http://support.sas.com/resources/thirdpartysupport/v92m3/index.html






Verify the Operating System RequirementsBefore you install the SAS Social Network Analysis Server, make sure that you meet theminimum system requirements that are described in the system requirementsdocumentation. System requirements are unique for each operating system. Items that areaddressed as system requirements include software requirements, hardware requirements,space requirements, specific product requirements, and graphics hardware and softwarecompatibility.

Access the SAS System Requirements page at http://support.sas.com/resources/sysreq/index.html. Select the SAS 9.2 (TS2Mx) SystemRequirements link. From the Product menu on that Web page, select SAS SocialNetwork Analysis Mid-Tier to view the requirements for the middle tier. Reset the filterand then select SAS Social Network Analysis Server from the Product menu to view therequirements for the server tier.

SAS Intelligence Platform Pre-Installation TasksFor information about pre-installation tasks that are required to install the SAS IntelligencePlatform, see the SAS Intelligence Platform: Installation and Configuration Guide athttp://support.sas.com/92administration.

SAS Intelligence Platform Pre-Installation Tasks 11

http://support.sas.com/resources/sysreq/index.html

http://support.sas.com/resources/sysreq/index.html

http://support.sas.com/92administration

12 Chapter 3 • Preparing for SAS Installation

Chapter 4

Preparing the Database

Oracle Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

MySQL Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

IBM DB2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Microsoft SQL Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Create Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17MySQL Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Modifications to Database Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Database Client and JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Oracle Database Configuration

Product DocumentationOracle Database 10g Release 2 Documentation Library: http://www.oracle.com/pls/db102/homepage

Oracle Database 11g Release 2 Documentation Library: http://www.oracle.com/pls/db112/homepage

Instructions1. Install Oracle Database. Record the location of the Oracle JDBC drivers. The location

is typically $ORACLE_HOME/jdbc/lib. The location must be provided to the SAS

13

http://www.oracle.com/pls/db102/homepage




Deployment Wizard. If the SAS middle-tier software will be installed on a differentmachine, then copy the drivers to the machine that will be used for the SAS middle tier.

2. Create and configure a database and schema within Oracle Database. During thisprocess, the hardware sizing, hardware configuration, global database settings,tablespace creation, and data files specification are performed.

Note: The SAS Deployment Wizard defaults to a database that is named SNAALERT,but the name referenced by the SAS Deployment Wizard can be changed duringthe installation. The creation of the database is usually performed with the OracleDatabase Configuration Assistant (DBCA).

MySQL Database Configuration

Product DocumentationMySQL 5.0 Reference Manual: http://dev.mysql.com/doc/refman/5.0/en/

Chapter 2. Installing and Upgrading MySQL: http://dev.mysql.com/doc/refman/5.0/en/installing.html

Section 2.18. Post-Installation Setup and Testing: http://dev.mysql.com/doc/refman/5.0/en/post-installation.html

PrerequisitesIf the JDBC driver has not already been installed on the middle-tier machine, then downloadConnector/J from the following link:

http://dev.mysql.com/downloads/connector/j/5.0.html

Record the location of the JDBC drivers. The location must be provided to the SASDeployment Wizard.

Instructions1. Install MySQL. Install version 5.0 (specifically 5.0.77 or higher, but not a 5.1 version

on Microsoft Windows systems).

2. Create and configure a database within MySQL. In the my.ini file, configure thedatabase so that the default engine type is InnoDB. SAS also suggests settinginnodb_flush_log_at_trx_commit to 1 so that the transaction logs are flushed to diskafter each transaction is committed.

Note: The SAS Deployment Wizard defaults to a database that is named SNAALERT,but the name referenced by the SAS Deployment Wizard can be changed duringthe installation.

14 Chapter 4 • Preparing the Database

http://dev.mysql.com/doc/refman/5.0/en/

http://dev.mysql.com/doc/refman/5.0/en/installing.html

http://dev.mysql.com/doc/refman/5.0/en/installing.html

http://dev.mysql.com/doc/refman/5.0/en/post-installation.html

http://dev.mysql.com/doc/refman/5.0/en/post-installation.html

http://dev.mysql.com/downloads/connector/j/5.0.html

IBM DB2 Configuration

Product DocumentationIBM Support Portal - DB2 for Linux, UNIX and Windows: http://www-947.ibm.com/support/entry/portal/Documentation/Software/Information_Management/DB2_for_Linux,_UNIX_and_Windows

IBM DB2 Database for Linux, UNIX, and Windows Information Center: http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp

Instructions1. Install DB2. Record the location of the JDBC drivers. The location is typically in the

DB2 installation directory, in a directory that is named java. Identify which JDBCdriver JAR file applies to the JDK that is used by the Web application server, and thencopy that JAR file to a separate directory. The directory name must be provided to theSAS Deployment Wizard.

If the SAS middle-tier software will be installed on a different machine, then copy theJDBC driver JAR file to that machine.

2. Create and configure a database. SAS requires that the table space for the database usesa 32-kilobyte page size. The following command is a sample SQL statement for creatingthe database instance:

create database snaalert pagesize 32 k user tablespace managed by database using (file '/data01/snaalert/snaalert.dbf' 16184) autoresize yes temporary tablespace managed by system using ('/data01/snaalert/user_tmp') extentsize 32


Microsoft SQL Server Configuration

Product DocumentationMicrosoft SQL Server Library: http://technet.microsoft.com/en-us/library/bb545450.aspx

Microsoft SQL Server 2008 R2 Getting Started: http://technet.microsoft.com/en-us/library/bb500434.aspx

Microsoft SQL Server Configuration 15

http://www-947.ibm.com/support/entry/portal/Documentation/Software/Information_Management/DB2_for_Linux,_UNIX_and_Windows



http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp

http://technet.microsoft.com/en-us/library/bb545450.aspx




Instructions1. Install SQL Server.

2. Create and configure a database. The following command is a sample SQL statementfor creating the database instance:

create database snaalerton( name = snadat, filename = 'c:\sqlserver\datafiles\snadat.mdf', size = 5120, maxsize = 8192, filegrowth = 50 )log on( name = snalog, filename = 'c:\sqlserver\transaction_logs\snalog.ldf', size = 5120MB, maxsize = 8192MB, filegrowth = 50MB );


Create Database UsersCreating database user IDs before running the SAS Deployment Wizard is an optional task.The SAS Deployment Wizard requires information about how to connect to the databasewith JDBC, including user credentials, but it installs and configures SAS Social NetworkAnalysis without connecting to the database. As a result, you can create database user IDsbefore running the SAS Deployment Wizard if it is more convenient or you prefer to doso. If you choose to wait until after running the SAS Deployment Wizard, then SASprovides sample scripts that can be modified to create users.


Oracle DatabaseThe following figure shows the database user IDs and schemas that are used by the SASSocial Network Analysis Server:

Figure 4.1 Oracle Database User IDs and Schemas

SNAALERT

SNAREAD

SNADBREADSNADBUSERS

SNAUSERSNACORE

SNACOREUSERS

Read-Write

Read-only

Database user ID

Metadata group

Metadata user

Schema: SNACORE

Library: DB_CORE

Schema: SNAUSER

Library: DB_KC

sassna Investigator A

Investigator B

Investigator C

ETL Developer A

ETL Developer B

ETL Developer C

Three database user IDs need to be created:

Table 4.1 Oracle Database User IDs

User ID Description

SNACORE Has Read and Write access to the schema where core entity data is loaded.Further details about entity levels and loading core entity data appear inthe SAS Social Network Analysis Server: Administration Guide. This userID is used to execute extract, transform, and load processes to load thecore entity data into the database, specifically the SNACORE schema.

Create Database Users 17

User ID Description

SNAUSER Has Read and Write access to the schema where alert generation processconfiguration tables are loaded.

SNAREAD Has Read access to the schema where the alert generation processconfiguration tables and the core entity data are loaded.

SAS supplies the following sample script after the SAS Deployment Wizard is run:

CREATE USER "SNAUSER" PROFILE "DEFAULT" IDENTIFIED BY "<read/write dbuser password>"DEFAULT TABLESPACE "<tablespace>"TEMPORARY TABLESPACE "<temporary tablespace>"ACCOUNT UNLOCK;

GRANT "CONNECT" TO "SNAUSER";GRANT "RESOURCE" TO "SNAUSER";GRANT CREATE VIEW TO "SNAUSER";GRANT CREATE ANY SYNONYM TO "SNAUSER";GRANT DROP ANY SYNONYM TO "SNAUSER";GRANT SELECT ANY SEQUENCE TO "SNAUSER";

CREATE USER "SNAREAD" PROFILE "DEFAULT" IDENTIFIED BY "<read only dbuser password>"DEFAULT TABLESPACE "<tablespace>"TEMPORARY TABLESPACE "<temporary tablespace>"ACCOUNT UNLOCK;

GRANT "CONNECT" TO "SNAREAD";GRANT "RESOURCE" TO "SNAREAD";

CREATE USER "SNACORE" PROFILE "DEFAULT" IDENTIFIED BY "<read/write dbcoreuser password>"DEFAULT TABLESPACE "<core tablespace>"TEMPORARY TABLESPACE "<core temporary tablespace>"ACCOUNT UNLOCK;

GRANT "CONNECT" TO "SNACORE";GRANT "RESOURCE" TO "SNACORE";GRANT CREATE VIEW TO "SNACORE";GRANT CREATE ANY SYNONYM TO "SNACORE";GRANT DROP ANY SYNONYM TO "SNACORE";GRANT SELECT ANY SEQUENCE TO "SNACORE";

If you prefer to create users after the SAS Deployment Wizard runs, the sample scripts areavailable in the following locations:

Windows Specifics!SASROOT\snamva\sasmisc\dbmsc\util\create_app_user_orcl.sql

UNIX Specifics!SASROOT/misc/snamva/dbmsc/util/create_app_user_orcl.sql

The necessary modifications appear in the following table.


Table 4.2 Script Modification for Oracle Database

Tag to be Modified Replacement Value for Tag

<read/write dbuser password> Password for the SNAUSER database user ID.

<tablespace> Name of the permanent tablespace used to store the SAS SocialNetwork Analysis Server application objects.

<temporary tablespace> Name of the temporary tablespace used to store the SAS SocialNetwork Analysis Server application objects.

<read only dbuser password> Password for the SNAUSER database user ID.

<read/write dbcoreuserpassword>

Password for the SNACORE database user ID.

<core tablespace> Name of the permanent tablespace used to store core entitydata.

<core temporary tablespace> Name of the temporary tablespace used to store core entitydata.


MySQL DatabaseThe following figure shows the database user IDs that are used by the SAS Social NetworkAnalysis Server.

Figure 4.2 MySQL Database User IDs and Database

SNAREAD

SNADBREADSNADBUSERS

SNAUSER


Investigator B

Investigator C

ETL Developer A

ETL Developer B

ETL Developer C

Read-Write

Read-only

Database user ID

Metadata group

Metadata user

Database: SNAALERT

Library: DB_CORE and DB_KC

Two database user IDs need to be created:


Table 4.3 MySQL Database User IDs

User ID Description

SNAUSER Has Read and Write access to the schema where alert generation processconfiguration tables and core entity data is loaded.


SAS supplies the following sample script after the SAS Deployment Wizard is run:

CREATE USER 'SNAUSER'@'<hostname>' IDENTIFIED BY '<read/write dbuser password>';SET PASSWORD FOR 'SNAUSER'@'<hostname>' = OLD_PASSWORD('<read/write dbuser password>');

GRANT SELECT, ALTER, CREATE, CREATE TEMPORARY TABLES, CREATE VIEW, DELETE, DROP, INDEX, INSERT, UPDATE, LOCK TABLES, SHOW VIEW ON <database>.* TO 'SNAUSER'@'<hostname>';

CREATE USER 'SNAREAD'@'<hostname>' IDENTIFIED BY '<read only dbuser password>';SET PASSWORD FOR 'SNAREAD'@'<hostname>' = OLD_PASSWORD('<read only dbuser password>');

GRANT SELECT ON <database>.* TO 'SNAREAD'@'<hostname>'


Windows Specifics!SASROOT\snamva\sasmisc\dbmsc\util\create_app_user_mysql.sql

UNIX Specifics!SASROOT/misc/snamva/dbmsc/util/create_app_user_mysql.sql



Table 4.4 Script Modification for MySQL Database


<hostname> Host from which the user can access thedatabase. If the user needs to connect frommultiple hosts, repeat the CREATE USER andSET PASSWORD statements.

<read/write dbuser password> Password that the SNAUSER database user IDspecifies to authenticate to the database.

<database> Name of the database that was created andconfigured.

<read only dbuser password> Password that the SNAREAD database user IDspecifies to authenticate to the database.


IBM DB2The following figure shows the database user IDs and schemas that are used by the SASSocial Network Analysis Server:

Figure 4.3 IBM DB2 Database User IDs and Schemas

Read-Write

Read-only

Database user ID

Metadata group

Metadata user

SNAREAD

SNADBREADSNADBUSERS

SNAUSER


Investigator B

Investigator C

ETL Developer A

ETL Developer B

ETL Developer C

SNAALERT

DBADM

Schema: SNACORE

Library: DB_CORE

Schema: SNAUSER

Library: DB_KC



Table 4.5 IBM DB2 Database User IDs

User ID Description

SNAUSER Has DBADM privilege, which provides Read and Write access to alltables.


SAS does not provide sample scripts for creating these accounts, but does provide scriptsfor setting the privileges. SAS provides the following sample script for setting DBADMprivilege for SNAUSER:

grant dbadm on database to user snauser

If you prefer to perform the grant after the SAS Deployment Wizard runs, the sample scriptsare available in the following locations:

Windows Specifics!SASROOT\snamva\sasmisc\dbmsc\util\sfs_util_grant_access_to_snauser_db2.bat

UNIX Specifics!SASROOT/misc/snamva/dbmsc/util/sfs_util_grant_access_to_snauser_db2.sh


Microsoft SQL ServerThe following figure shows the database user IDs and schemas that are used by the SASSocial Network Analysis Server:

Figure 4.4 Microsoft SQL Server Database User IDs and Schemas

SNAREAD

SNADBREADSNADBUSERS

SNAUSER


Investigator B

Investigator C

ETL Developer A

ETL Developer B

ETL Developer C

Read-Write

Read-only

Database user ID

Metadata group

Metadata user

SNAALERT

Schema: SNACORE

Library: DB_CORE

Schema: SNAUSER

Library: DB_KC



Table 4.6 Microsoft SQL Server Database User IDs

User ID Description

SNAUSER Has Read and Write access to the schema where alert generation processconfiguration tables are loaded. Has Read and Write access to the schemawith the core entity tables.


SAS provides the following sample script after the SAS Deployment Wizard is run:

USE [master]GO

CREATE LOGIN [SNAUSER] WITH PASSWORD=N'<read/write dbuser password>', DEFAULT_DATABASE=[master], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFFGO

USE [master]GOEXEC master..sp_addsrvrolemember @loginame = N'SNAUSER', @rolename = N'bulkadmin'GOUSE [SNAALERT]GOCREATE USER [SNAUSER] FOR LOGIN [SNAUSER]GOUSE [SNAALERT]GOEXEC sp_addrolemember N'db_datareader', N'SNAUSER'GOUSE [SNAALERT]GOEXEC sp_addrolemember N'db_datawriter', N'SNAUSER'GOUSE [SNAALERT]GOEXEC sp_addrolemember N'db_ddladmin', N'SNAUSER'GOuse [master]GOGRANT ADMINISTER BULK OPERATIONS TO [SNAUSER]GOUSE [SNAALERT]GOCREATE SCHEMA [SNACORE] AUTHORIZATION [SNAUSER]GOUSE [SNAALERT]GOCREATE SCHEMA [SNAUSER] AUTHORIZATION [SNAUSER]GOUSE [SNAALERT]


GOALTER USER SNAUSER WITH DEFAULT_SCHEMA=SNAUSERGO

USE [master]GO

CREATE LOGIN [SNAREAD] WITH PASSWORD=N'<read only dbuser password>', DEFAULT_DATABASE=[master], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFFGO

USE [SNAALERT]GO

CREATE USER [SNAREAD] FOR LOGIN [SNAREAD]GO

USE [SNAALERT]GO

EXEC sp_addrolemember N'db_datareader', N'SNAREAD'GO


Windows Specifics!SASROOT\snamva\sasmisc\dbmsc\util\create_app_user_sqlserver.sql

UNIX Specifics!SASROOT/misc/snamva/dbmsc/util/create_app_user_sqlserver.sql


Table 4.7 Script Modification for Microsoft SQL Server




Modifications to Database AccessThe database access strategies that are provided by SAS in the previous sections describeusing a database user ID named SNAREAD for read-only access to the database. Througha metadata group that is named SNADBREAD, investigators receive read-only access

Modifications to Database Access 27

through the SNAREAD database user ID. (Detailed instructions for creating theSNADBREAD metadata group and investigators are provided later in this document.)

Investigators might need Read and Write access to some of the tables in the DB_KC library.Part of an investigator's work is to view alerts, determine whether further investigation isrequired, and then dispose of the alert. Many choices for alert disposition are possible. Asimple example is one state to indicate that further investigation is required, and anotherstate to indicate that no action is required. If you choose to record the alert dispositionactions in the DB_KC.FSK_ALERT table, then the SNAREAD database user ID requiresRead and Write access.

Database Client and JDBC DriversAs a post-installation task, you must run several database scripts provided with the SASSocial Network Analysis Server to prepare and initialize your database. These databasescripts assume that a database client application is installed and available on the PATH. Ifthe database is not installed on the same machine as the SAS Social Network AnalysisServer server-tier, then install the database client on the server-tier machine.

The SAS Social Network Analysis Server middle-tier Web application requires access tothe database through JDBC. If the database is installed on a different machine than themiddle tier, then install the JDBC driver for the database on the middle-tier machine.

The following table identifies the JDBC drivers for the databases that the SAS SocialNetwork Analysis Server supports.

Table 4.8 JDBC Driver and Java Version Support

Database Driver Java Version Description

Oracle Database ojdbc14.jar Java 5 Use with Oracle Database version 10and a Web application server thatuses Java 5. This includes JBoss 4.2,Oracle WebLogic Server 9.2, andIBM WebSphere Application Server6.1.

ojdbc5.jar Java 5 Use with Oracle Database version 10or 11 and a Web application serverthat uses Java 5. This includes JBoss4.2, Oracle WebLogic Server 9.2, andIBM WebSphere Application Server6.1.

odjbc6.jar Java 6 Use with Oracle Database version 10or 11 and a Web application serverthat uses Java 6. This includes JBoss4.3 and Oracle WebLogic Server 11g.

MySQLDatabase

mysql-connector-java-5.0.8-bin.jar

Java 5 or Java 6 Use with any Web application server.


Database Driver Java Version Description

IBM DB2 db2jcc.jar Java 5 Use with a Web application serverthat uses Java 5. This includes JBoss4.2, Oracle WebLogic Server 9.2, andIBM WebSphere Application Server6.1.

db2jcc4.jar Java 6 Use with a Web application serverthat uses Java 6. This includes JBoss4.3 and Oracle WebLogic Server 11g.

Microsoft SQLServer

sqljdbc.jar Java 5 Provides support for JDBC 3.0.Using sqljdbc.jar with Java 6 isincompatible and throws anexception when connecting to adatabase.

sqljdbc4.jar Java 6 Provides support for JDBC 4.0.Using sqljdbc4.jar with Java 5 isincompatible and throws anexception.

Database Client and JDBC Drivers 29

Part 3

Running the SAS DeploymentWizard

Chapter 5Running the SAS Deployment Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

31

Chapter 5

Running the SAS DeploymentWizard

Install and Configure Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Run the SAS Deployment Wizard in Install Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Apply Hot Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Run the SAS Deployment Wizard in Configure Mode . . . . . . . . . . . . . . . . . . . . . . . 35Start the SAS Deployment Wizard in Configure Mode . . . . . . . . . . . . . . . . . . . . . . 35Anonymous Web Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35JDBC Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Install and Configure SequenceThe SAS Deployment Wizard has two modes: install and configure. It is very important torun the wizard in install mode first, add hot fixes to the software, and then run the wizarda second time in configure mode. The following steps describe the sequence:

1. Run the SAS Deployment Wizard in install mode.

2. Contact SAS Technical Support for hot fix software and instructions.

3. Run the SAS Deployment Wizard in configure mode.

In a multiple-machine deployment, start with the server-tier machine and follow the sameorder of install, hot fix, and configure:

1. Run the SAS Deployment Wizard in install mode:

a. on the server-tier machine

b. on the middle-tier machine

2. Contact SAS Technical Support for hot fix software and instructions. Apply the hot fixin the following sequence:



3. Run the SAS Deployment Wizard in configure mode:



33

Run the SAS Deployment Wizard in Install ModeAs described in the previous section, it is important to run the SAS Deployment Wizard ininstall mode, and to specifically disable the configure mode. The following figure showsthe wizard with only the install mode enabled.

Display 5.1 SAS Deployment Wizard: Install SAS Software

Apply Hot FixesContact SAS Technical Support for hot fix software and instructions for applying the hotfix.

34 Chapter 5 • Running the SAS Deployment Wizard

Run the SAS Deployment Wizard in ConfigureMode

Start the SAS Deployment Wizard in Configure ModeAfter hot fix software is applied, run the SAS Deployment Wizard in configure mode. Thefollowing figure shows the wizard with only the configure mode enabled.

Display 5.2 SAS Deployment Wizard: Configure SAS Software

The following sections describe the wizard pages that are used for configuring SAS SocialNetwork Analysis Server.

Anonymous Web AccessThe SAS Deployment Wizard offers an option to enable anonymous Web access. Theconsequence of enabling this option is that the Web services and stored processes that areused in the SAS Social Network Analysis Server will not require authenticated credentialsto be used. If this option is not selected, then all requests for the Web services and storedprocesses require credentials. This second option results in a more secure deployment.

The SAS Social Network Analysis Server does not require anonymous Web access, sounless some other SAS software is deployed on the machine and requires it, do not enablethis option.

JDBC PropertiesWithin the SAS Deployment Wizard, users are asked a series of questions regarding theJDBC database connection information required by the Social Network Analysis middletier. Complete the following instructions:

Run the SAS Deployment Wizard in Configure Mode 35

1. Select the database product from the Database Type menu.

Display 5.3 JDBC Database Type

Click Next.

2. Provide the host name, port number, database name, and the directory that contains theJDBC driver JAR files for the database. The following figure shows sample values forMySQL.


Display 5.4 JDBC Properties

When you provide the directory that contains the JDBC driver JAR files, you need tobrowse to the directory that contains the JAR file. You do not need to select the JARfile, and the JAR filename does not appear in the text field on the wizard page. Also,make sure that the directory contains only the JAR file that is appropriate for the JDKversion that is used by the Web application server. For more information about theJDBC driver JAR files, see “Database Client and JDBC Drivers” on page 28.

Click Next.

3. Enter the User ID and Password for the JDBC connection to the database.

Run the SAS Deployment Wizard in Configure Mode 37

Display 5.5 JDBC Database User

At this point in the process, follow the instructions in the operating system-specific SAS9.2 Foundation Configuration Guide.


Part 4

Post-Installation andConfiguration

Chapter 6Post-Installation Steps for SAS 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 7Post-Installation Database Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 8Register Database Identities and Groups . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 9Register Database Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Chapter 10Register Data Mart Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Chapter 11Configure the Autoexec and Verify Libraries . . . . . . . . . . . . . . . . . . . . 101

39

Chapter 6

Post-Installation Steps for SAS9.2

Post-Installation Steps for SAS 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Post-Installation Steps for SAS 9.2Table 6.1 SAS 9.2 Configuration References

OperatingSystem Document URL

UNIX Configuration Guide for SAS 9.2Foundation

http://support.sas.com/documentation/installcenter/en/ikfdtnunxcg/61994/PDF/default/config.pdf

Windows Configuration Guide for SAS 9.2Foundation

http://support.sas.com/documentation/installcenter/en/ikfdtnwincg/62175/PDF/default/config.pdf

Windows (x64) Configuration Guide for SAS 9.2Foundation

http://support.sas.com/documentation/installcenter/en/ikfdtnwx6cg/62192/PDF/default/config.pdf

Note: The post-installation and configuration for the SAS/ACCESS software must becompleted after the installation of SAS 9.2 Foundation.

41










42 Chapter 6 • Post-Installation Steps for SAS 9.2

Chapter 7

Post-Installation Database Tasks

Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Confirm or Create Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Apply DDL and Seed the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

MySQL Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Confirm or Create Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Apply DDL and Seed the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Confirm or Create Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Apply DDL and Seed the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Create or Confirm Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Apply DDL and Seed the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Oracle Database

Confirm or Create UsersIf database users were not created before running the SAS Deployment Wizard, then createthem now. SAS provides sample scripts in the following locations:

Windows Specifics!SASROOT\snamva\sasmisc\dbmsc\util\create_app_user_orcl.sql

UNIX Specifics!SASROOT/misc/snamva/dbmsc/util/create_app_user_orcl.sql


43

Table 7.1 Script Modification for Oracle Database


<read/write dbuser password> Password for the SNAUSER database user ID.

<tablespace> Name of the permanent tablespace used to store the SAS SocialNetwork Analysis Server application objects.

<temporary tablespace> Name of the temporary tablespace used to store the SAS SocialNetwork Analysis Server application objects.

<read only dbuser password> Password for the SNAREAD database user ID.

<read/write dbcoreuserpassword>

Password for the SNACORE database user ID.

<core tablespace> Name of the permanent tablespace used to store core entitydata.

<core temporary tablespace> Name of the temporary tablespace used to store core entitydata.

Apply DDL and Seed the DatabasePreviously, the database users were created. When the SAS Deployment Wizard was run,it required the JDBC driver location and database connection parameters. The SASDeployment Wizard installed scripts and data definition language statements (DDL) inSQL files. The scripts apply the DDL to create and seed the database. Choose the correctprocedure based on the operating system of the SAS Social Network Analysis Server.

UNIXThe scripts that are identified in this section invoke sqlplus to communicate with Oracle.If the current user ID does not have access to sqlplus, the database administrator mightneed to ask the system administrator to add the sqlplus executable path to the PATHenvironment variable. Make sure that sqlplus is available before proceeding.

1. Copy !SASROOT/misc/snamva/dbmsc/util/sfs_util_load_orcl_template.sh to a new file, such assfs_util_load_orcl_SNAALERT.sh.

2. Edit the copied file and replace the <path to SNA RDBMS utility directory> tag withthe fully qualified path to !SASROOT/misc/snamva/dbmsc/util/. Replace thetags with values for the parameters shown in the following table.

3. Make the script executable by entering the following command:

chmod 775 sfs_util_load_orcl_SNAALERT.sh

4. Execute the script by entering the following command:

./sfs_util_load_orcl_SNAALERT.sh

44 Chapter 7 • Post-Installation Database Tasks

Table 7.2 Oracle Script Parameters for UNIX

Parameter Value

<ORACLE SID> System ID of the Oracle database.

<ORACLE home directory> Oracle database home directory.

<ORACLE base directory> Oracle database base directory.

<database> Use the ORACLE_SID value.

<database user> Database user ID that has Read and Writeprivileges. Previous sections of this documentsuggest the SNAUSER database user ID.

<database user password> Password for the database user ID.

<path to SNA dbmsc directory> Fully qualified path to !SASROOT/misc/snamva/dbmsc.

<fully qualified path to seed file> Fully qualified path to !SASROOT/misc/snamva/dbmsc/seed/seed_rdbms_orcl.sql.

Microsoft WindowsFor the scripts in this section to execute successfully from a DOS command line, paths todirectories that contain spaces need to be converted to shortened DOS directory names.Convert a Windows path with spaces by taking the first six (6) characters of the directoryname and then appending a tilde (~) and a number. If there is only one directory whosefirst characters are unique, the number will be 1. For example, take the following Windowspath:

C:\Program Files\SAS\SASFoundation\9.2\snamva\sasmisc\dbmsc\util

This path needs to be converted to the following:

C:\Progra~1\SAS\SASFoundation\9.2\snamva\sasmisc\dbmsc\util

To apply the DDL and seed the database, perform the following steps:

1. Copy !SASROOT\snamva\sasmisc\dbmsc\util\sfs_util_load_orcl_template.bat to a new file, such assfs_util_load_orcl_SNAALERT.bat.

2. Edit the copied file and replace the <path to SNA RDBMS utility directory> tag withthe fully qualified path to !SASROOT\snamva\sasmisc\dbmsc\util\. Replacethe tags with values for the parameters shown in the following table.

3. Execute the script from the DOS command prompt. For example, at the DOS prompt,enter the following command:

sfs_util_load_orcl_SNAALERT.bat

Oracle Database 45

Table 7.3 Oracle Script Parameters for Windows

Parameter Value

<database> Use the ORACLE_SID.



<path to SNA dbmsc directory> Fully qualified path to !SASROOT\snamva\sasmisc\dbmsc.

<fully qualified path to seed file> Fully qualified path to !SASROOT\snamva\sasmisc\dbmsc\seed\seed_rdbms_orcl.sql.

MySQL Database

Confirm or Create UsersIf database users were not created before running the SAS Deployment Wizard, then createthem now. SAS provides sample scripts in the following locations:

Windows Specifics!SASROOT\snamva\sasmisc\dbmsc\util\create_app_user_mysql.sql

UNIX Specifics!SASROOT/misc/snamva/dbmsc/util/create_app_user_mysql.sql


Table 7.4 Script Modification for MySQL Database


<hostname> Host from which the user can access thedatabase. If the user needs to connect frommultiple hosts, repeat the CREATE USER andSET PASSWORD statements.


<database> Name of the database that was created andconfigured.



Apply DDL and Seed the DatabasePreviously, the database users were created. When the SAS Deployment Wizard was run,it required the JDBC driver location and database connection parameters. The SASDeployment Wizard installed scripts and data definition language statements (DDL) inSQL files. The scripts apply the DDL to create and seed the database. Choose the correctprocedure based on the operating system of the SAS Social Network Analysis Server.

UNIXThe scripts that are identified in this section invoke the mysql client to communicate withMySQL. If the current user ID does not have access to the mysql client, the databaseadministrator might need to ask the system administrator to add the executable path to thePATH environment variable. Make sure that the mysql client is available beforeproceeding.

1. Copy !SASROOT/misc/snamva/dbmsc/util/sfs_util_load_mysql_template.sh to a new file such assfs_util_load_mysql_SNAALERT.sh.



chmod 775 sfs_util_load_mysql_SNAALERT.sh


./sfs_util_load_mysql_SNAALERT.sh

Table 7.5 MySQL Script Parameters for UNIX

Parameter Value

<database server> The host name of the machine with MySQLserver.

<database server port> The port that MySQL is listening on. Thedefault value is 3306.

<database> The name of the database. The default valuementioned previously is SNAALERT.




MySQL Database 47

Parameter Value

<fully qualified path to seed file> Fully qualified path to !SASROOT/misc/snamva/dbmsc/seed/seed_rdbms_mysql.sql.






1. Copy !SASROOT\snamva\sasmisc\dbmsc\util\sfs_util_load_mysql_template.bat to a new file such assfs_util_load_mysql_SNAALERT.bat.


3. Execute the script from the DOS command prompt by entering the following command:

sfs_util_load_mysql_SNAALERT.bat

Table 7.6 MySQL Script Parameters for Windows

Parameter Value

<database server> Host name of the machine with MySQL server.

<database server port> Port that MySQL is listening on. The defaultvalue is 3306.

<database> The name of the database. The default valuementioned previously is SNAALERT.





Parameter Value

<fully qualified path to seed file> Fully qualified path to !SASROOT\snamva\sasmisc\dbmsc\seed\seed_rdbms_mysql.sql.

IBM DB2

Confirm or Create UsersSAS does not provide sample scripts for creating database user IDs. Two users are neededfor the SAS Social Network Analysis Server, SNAUSER and SNAREAD. The SNAUSERdatabase user ID is given DBADM privileges, and sample statements for granting thatprivilege are available in the following locations:

Windows Specifics!SASROOT\snamva\sasmisc\dbmsc\util\sfs_util_grant_access_to_snauser_db2.bat

UNIX Specifics!SASROOT/misc/snamva/dbmsc/util/sfs_util_grant_access_to_snauser_db2.sh

Apply DDL and Seed the DatabasePreviously, the database and database user were created. When the SAS DeploymentWizard was run, it required the JDBC driver location and database connection parameters.The SAS Deployment Wizard installed scripts and data definition language statements(DDL) in SQL files. The scripts apply the DDL to create and seed the database. Choosethe correct procedure based on the operating system of the SAS Social Network AnalysisServer.

UNIXTo apply the DDL and seed the database, perform the following steps:

1. Copy !SASROOT/misc/snamva/dbmsc/util/sfs_util_load_db2_template.sh to a new file such assfs_util_load_db2_SNAALERT.sh.



chmod 775 sfs_util_load_db2_SNAALERT.sh


./sfs_util_load_db2_SNAALERT.sh

IBM DB2 49

Table 7.7 DB2 Script Parameters for UNIX

Parameter Value

<database> The name of the database.




<fully qualified path to seed file> Fully qualified path to !SASROOT/misc/snamva/dbmsc/seed/seed_rdbms_db2.sql.






1. Copy !SASROOT\snamva\sasmisc\dbmsc\util\sfs_load_db2_template.bat to a new file such assfs_util_load_db2_SNAALERT.bat.



sfs_util_load_db2_SNAALERT.bat

Table 7.8 DB2 Script Parameters for Windows

Parameter Value



Parameter Value




<fully qualified path to seed file> Fully qualified path to !SASROOT\snamva\sasmisc\dbmsc\seed\seed_rdbms_db2.sql.

Microsoft SQL Server

Create or Confirm UsersIf database users were not created before running the SAS Deployment Wizard, then createthem now. SAS provides sample scripts in the following locations:

Windows Specifics!SASROOT\snamva\sasmisc\dbmsc\util\create_app_user_sqlserver.sql

UNIX Specifics!SASROOT/misc/snamva/dbmsc/util/create_app_user_sqlserver.sql


Table 7.9 Script Modification for Microsoft SQL Server




Apply DDL and Seed the DatabasePreviously, the database and database user were created. When the SAS DeploymentWizard was run, it required the JDBC driver location and database connection parameters.The SAS Deployment Wizard installed scripts and data definition language statements(DDL) in SQL files. The scripts apply the DDL to create and seed the database.

Microsoft SQL Server 51

For the scripts in this section to execute successfully from a DOS command line, paths todirectories that contain spaces need to be converted to shortened DOS directory names.Convert a Windows path with spaces by taking the first six (6) characters of the directoryname and then appending a tilde (~) and a number. If there is only one directory whosefirst characters are unique, the number will be 1. For example, take the following Windowspath:





1. Copy !SASROOT\snamva\sasmisc\dbmsc\util\sfs_util_load_sqlserver_template.bat to a new file such assfs_util_load_sqlserver_SNAALERT.bat.



sfs_util_load_sqlserver_SNAALERT.bat

Table 7.10 Microsoft SQL Server Script Parameters

Parameter Value

<database server> Host name of the machine with the database.


<database user Database user ID that has Read and Writeprivileges. Previous sections of this documentsuggest the SNAUSER database user ID.



<fully qualified path to seed file> Fully qualified path to !SASROOT\snamva\sasmisc\dbmsc\seed\seed_rdbms_sqlserver.sql.


Chapter 8

Register Database Identities andGroups

Register Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Register an Authentication Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Register Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Important Information About Metadata Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Register an SNADBUSERS Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Register an SNADBREAD Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Register an SNACOREUSERS Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Register Users and Groups

Register an Authentication DomainThe steps in this section register a new authentication domain in SAS metadata for thedatabase authentication credentials. Authentication domains are added using SASManagement Console. An authentication domain is a name that facilitates the matching ofuser credentials with the servers for which they are valid.

To register the authentication domain, perform the following steps with SAS ManagementConsole:

1. Right-click User Manager and select Authentication Domains.

2. Click New and enter snaDbAuth in the Name field.

3. Click OK.

53

Display 8.1 Authentication Domains Display

Register UsersThe steps in this section register the users who execute the alert generation process. Theexample shown here registers a single application user with the user ID sassna. This userID is used throughout the rest of this document. If another user ID is used for a customerimplementation, assume that the user ID can substitute for sassna.

To register a user, perform the following steps:

1. Right-click User Manager and select New ð User.

2. Select the General tab, and provide a value for the Name, Display Name, and Job Titlefields.

54 Chapter 8 • Register Database Identities and Groups

Display 8.2 New User: General

3. Select Accounts, and then click New.

4. Add the operating system login information in the User ID field. Do not provide apassword for this account in the Password field. Select DefaultAuth for theAuthentication Domain field.

Register Users and Groups 55

Display 8.3 New User: Accounts

5. Click OK to close the New Login Properties dialog box, and then OK to close the NewUser Properties dialog box.

Important Information About Metadata GroupsThe following sections describe how to create groups in SAS metadata and then associateone database user account with each group in the snaDbAuth authentication domain.Metadata users, such as investigators, can be a member of one of the groups only.

CAUTION:Users can belong to only one of the metadata groups described in this document.If a user is accidentally added to more than one of the groups identified in this document,then SAS cannot determine the database user account to use for access to the database.The results are unpredictable.

Register an SNADBUSERS Group

PurposeThe SNADBUSERS group is for users that execute the alert generation process. TheSNAUSER database user ID is associated with this group so that members have Read and


Write privileges to the configuration tables for the alert generation process in theSNAUSER database schema. Members also have at least Read privilege to the SNACOREdatabase schema.

InstructionsTo register the SNADBUSERS group, perform the following steps:

1. Right-click User Manager.

2. Select New ð Group.

3. In the General tab, enter SNADBUSERS in the Name and Display Name fields.

Display 8.4 SNADBUSERS Group: General

4. Select Members, and then select sassna.


Display 8.5 SNADBUSERS Group: Members


6. Add the database credentials for the SNAUSER database user ID in the User ID fieldand the password in the Password field. Select snaDbAuth from the AuthenticationDomain menu.


Display 8.6 SNADBUSERS Group: Accounts

Register an SNADBREAD Group

PurposeThe SNADBREAD group is for users who need read-only access to the alert, configuration,and core entity data. The SNAREAD database user ID is associated with this group.Investigator groups are associated with this group later in this document.

InstructionsTo register the SNADBREAD group, perform the following steps:

1. Right-click User Manager and select New ð Group.

2. Select General and enter SNADBREAD for the Name and Display Name fields.


Display 8.7 SNADBREAD Group: General


4. Add the database credentials for the SNAREAD database user ID in the User ID fieldand the password in the Password field. Select snaDbAuth from the AuthenticationDomain menu.


Display 8.8 SNADBREAD Group: New Login Properties

Register an SNACOREUSERS Group

PurposeNote: This step applies to deployments that use Oracle Database only.

The SNACOREUSERS group is for users who execute extract, transform, and loadprocesses to load the core entity data into the SNACORE schema. The SNACORE databaseuser ID is associated with this group.

InstructionsTo register the SNACOREUSERS group, perform the following steps:

1. Right-click User Manager and select New ð Group.

2. Select General and then enter SNACOREUSERS for the Name and Display Namefields.

3. Skip the Groups and Roles tab.


5. Add the database credentials for the SNACORE database user ID in the User ID fieldand the password in the Password field. Select snaDbAuth from the AuthenticationDomain menu.


Chapter 9

Register Database Libraries

Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Register the Oracle Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Register an Oracle Library for Metadata Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Register an Oracle Library for Core Entity Tables . . . . . . . . . . . . . . . . . . . . . . . . . . 68

MySQL Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Register the MySQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Add Attributes to MySQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Register a MySQL Library for Metadata Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Register the IBM DB2 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Register an IBM DB2 Library for Metadata Tables . . . . . . . . . . . . . . . . . . . . . . . . . 79Register an IBM DB2 Library for Core Entity Tables . . . . . . . . . . . . . . . . . . . . . . . 81

Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Create a Data Source Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Register the SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Register an ODBC Library for Metadata Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Register an ODBC Library for Core Entity Tables . . . . . . . . . . . . . . . . . . . . . . . . . 90

Oracle Database

Register the Oracle ServerTo register the database, perform the following steps:

1. Right-click Server Manager and select New Server.

2. Select Oracle Server and click Next.

3. Provide a value in the Name field, such as Oracle Server. Record the value becauseit is used later in a SAS autoexec file.

63

Display 9.1 Oracle Server: Specify Server Name

Click Next.

4. Provide the following server properties:

Major version number: 10

Minor version number: 2

Appropriate Software version number (for example, if 10.2.0.4 is installed, then theSoftware Version Number is 4)

Vendor and Associated Machine should be already provided in the dialog box.

64 Chapter 9 • Register Database Libraries

Display 9.2 Oracle Server: Enter Server Properties

Click Next.

5. Provide the following connection properties:

Table 9.1 Oracle Database Connection Properties

Field Value

Path ORACLE SID or Database name thatcontains the alert, configuration, and coreentity database.

Authentication type User/Password

Authentication domain snaDbAuth

Oracle Database 65

Display 9.3 Define Oracle Server: Enter Connection Properties

Click Next.

6. Review the summary information and then click Finish.

Register an Oracle Library for Metadata TablesThe steps in this section register a library named DB_KC for the metadata tables:

1. Right-click Libraries and select New Library. The New Library Wizard appears.

2. Select Oracle Library from the list of libraries.

Click Next.

3. Enter DB_KC in the Name field.

4. Click Browse and, using the folder navigation window, create /Products/SASSocial Network Analysis/DB_KC. Set this value in the Location field.


Display 9.4 Metadata Tables: Specify Library Details

Click Next.

5. From the list of Available servers, select SASApp and click the right-arrow button.

Click Next.

6. Ener DB_KC in the Libref field.

Display 9.5 Metadata Tables: Enter Library Properties

Click Next.

7. Provide the following server and connection information:

Oracle Database 67

Table 9.2 Oracle Metadata Tables Server and Connection Properties

Field Value

Database Server Use the default value.

Database Schema Name SNAUSER

Connection Use the default value.

Default Login Use the default value of (None).

Display 9.6 Metadata Tables: Specify Server and Connection Information

Click Next.


Register an Oracle Library for Core Entity TablesThe steps in this section register the DB_CORE library for the core entity tables. The coreentity tables are loaded by a custom ETL process. For more information pertaining toentities and core entity data, see the SAS Social Network Analysis Server: AdministrationGuide.

To register the DB_CORE library for the core entity tables, perform the following steps:


2. From the list of libraries, select Oracle Library.

Click Next

3. Enter DB_CORE in the Name field.


4. Click Browse and, using the folder navigation window, create /Products/SASSocial Network Analysis/DB_CORE. Set this value in the Location field.

Display 9.7 Core Entity Tables: Specify Oracle Library Details

Click Next.

5. From the list of Available servers, select SASApp and click the right-arrow button.

Display 9.8 Configuration Metadata Tables: Select SAS Servers

Click Next.

6. Enter DB_CORE in the Libref field.

Oracle Database 69

Display 9.9 Core Entity Tables: Enter Library Properties

Click Next.


Table 9.3 Oracle Core Entity Tables Server and Connection Information

Field Value


Database Schema Name SNACORE




Display 9.10 Core Entity Tables: Data Server

Click Next.


MySQL Database

Register the MySQL ServerTo register the MySQL server, perform the following steps:


2. Select MySQL Server and click Next.

3. Provide a value in the Name field, such as MySQL Server. Record the value becauseit is used later in a SAS autoexec file.

MySQL Database 71

Display 9.11 Register MySQL Server: Specify Server Name

Click Next.




Software version number (if version 5.1.49 was installed, then enter 49).

The Vendor and Associated Machine should already appear in the dialog box.


Display 9.12 Register MySQL Server: Enter Server Properties

Click Next.


Table 9.4 MySQL Server Connection Properties

Field Value

Database SNAALERT (in this example)

MySQL Server hostname.example.com (do not enclose thehost name in quotation remarks even if thehost name includes periods)

Port 3306



MySQL Database 73

Display 9.13 Register MySQL Server: Enter Connection Properties

Click Next.


Add Attributes to MySQL ServerTo add attributes to the MySQL server, perform the following steps:

1. Select the MySQL server that was just registered.

2. Right-click the icon and select Properties.

3. Click Extended Attributes.

4. Click New.

5. Provide the following properties:

Table 9.5 Extended Attributes

Field Value

Field Name MYSQL_PORT

Value 3306

Description MySQL Server Port


Display 9.14 MySQL Server: Extended Attributes

Register a MySQL Library for Metadata TablesTo register a MySQL library for the metadata tables, perform the following steps:

1. Right-click Libraries and select New Library.

2. Select MySQL Library and click Next.

3. Enter DB_KC in the Name field. Click Browse and create the /Products/SASSocial Network Analysis/DB_KC path. Click Next.

MySQL Database 75


4. From the list of Available servers, select SASApp and then click Next.

5. Enter DB_KC in the Libref field. Click Next.

6. If SAS will use any encoding other than Latin1, such as EUC-CN (Chinese), thenperform the following steps to set a connection option to avoid transcoding errors:

a. Click Advanced Options and select the Connection tab.

b. In the User-defined connection initialization command field, provide valuessimilar to the following example:

"set names 'gbk', session sql_mode='';"

7. Review the summary information and click Finish.

IBM DB2

Register the IBM DB2 ServerTo register the IBM DB2 server, perform the following steps:


2. Select DB2 Server for UNIX and PC Hosts and click Next.

3. Provide a value in the Name field, such as DB2 Server. Record the value because itis used later in a SAS autoexec file.


Display 9.16 Register IBM DB2 Server: Specify Server Name

Click Next.




Software version number: blank

The Vendor and Associated Machine should already appear in the dialog box.

IBM DB2 77

Display 9.17 Register IBM DB2 Server: Enter Server Properties

Click Next.


Table 9.6 IBM DB2 Connection Properties

Field Value

Datasrc SNAALERT




Display 9.18 Register IBM DB2 Server: Enter Connection Properties

Click Next.


Register an IBM DB2 Library for Metadata TablesTo register an IBM DB2 library for the metadata tables, perform the following steps:


2. Select DB2 Library for UNIX and PC Hosts and click Next.


IBM DB2 79





Table 9.7 IBM DB2 Server and Connection Properties

Field Value







Click Next.


Register an IBM DB2 Library for Core Entity TablesThe steps in this section register the DB_CORE library for the core entity tables. The coreentity tables are loaded by a custom ETL process. For more information pertaining toentities and core entity data, see the SAS Social Network Analysis Server: AdministrationGuide.



2. Select DB2 Library for UNIX and PC Hosts and click Next.

3. Enter DB_CORE in the Name field. Click Browse and create the /Products/SASSocial Network Analysis/DB_CORE path. Click Next.

IBM DB2 81

Display 9.21 Core Entity Tables: Specify Library Details


5. Enter DB_CORE in the Libref field. Click Next.


Table 9.8 IBM DB2 Server and Connection Properties

Field Value






Display 9.22 Core Entity Tables: Specify Server and Connection Information

Click Next.


Microsoft SQL Server

Create a Data Source NameUse the ODBC Data Source Administrator to create a System DSN for access to SQLServer. Your settings might need to be different from the settings shown in the displays.Follow these steps to add the DSN:

1. Log on to the server-tier machine.

2. Start the ODBC Data Source Administrator.

3. Select the System DSN tab and then click Add.

4. Select the driver, such as SQL Server Native Client, and click Finish.

5. Enter SNAALERT in the Name field and use the Server menu to select the SQL Serverto use.


Click Next.

6. Select the radio button for the correct form of authentication. The following displayshows an example of using SQL Server authentication.

Click Next.

7. Select the Change the default database to check box and then select SNAALERTfrom the menu.


Click Next.

8. Select the defaults on the following pages of the wizard, and then confirm that the DSNis configured correctly by using the Test Data Source button.

Register the SQL ServerTo register the Microsoft SQL Server as an ODBC server, perform the following steps:


2. Select ODBC Server and click Next.

3. Provide a value in the Name field, such as SQL Server. Record the value because itis used later in a SAS autoexec file.


Display 9.23 Register SQL Server: Specify Server Name

Click Next.




Software version number: blank

Vendor: Microsoft Corporation

The Associated Machine should already appear in the dialog box.


Display 9.24 Register SQL Server: Enter Server Properties

Click Next.


Table 9.9 SQL Server Connection Properties

Field Value

Datasrc SNAALERT




Display 9.25 Register SQL Server: Enter Connection Properties

Click Next.


Register an ODBC Library for Metadata TablesTo register an ODBC library for the metadata tables, perform the following steps:


2. Select ODBC Library and click Next.







Table 9.10 SQL Server Server and Connection Properties

Field Value







Click Next.


Register an ODBC Library for Core Entity TablesThe steps in this section register the DB_CORE library for the core entity tables. The coreentity tables are loaded by a custom ETL process. For more information pertaining toentities and core entity data, see the SAS Social Network Analysis Server: AdministrationGuide.



2. Select ODBC Library and click Next.

3. Enter DB_CORE in the Name field. Click Browse and create the /Products/SASSocial Network Analysis/DB_CORE path. Click Next.


Display 9.28 Core Entity Tables: Specify Library Details


5. Enter DB_CORE in the Libref field. Click Next.


Table 9.11 SQL Server Server and Connection Properties

Field Value






Display 9.29 Core Entity Tables: Specify Server and Connection Information

Click Next.



Chapter 10

Register Data Mart Libraries

Create the SAS Data Mart Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Register a SAS Library for Alert Detail Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Register a SAS Library for Alert Summary Tables . . . . . . . . . . . . . . . . . . . . . . . . . 97

Register a SAS Library for Data Mart Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Register a SAS Library for Network Link Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Register a SAS Library for Network Node Tables . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Register a SAS Library for Alert Generation Process Input Tables . . . . . . . . . . . . 99

Create the SAS Data Mart Directories

PurposeThe SAS Social Network Analysis Server requires a series of directories to store thefollowing types of information:

• configuration files for the alert generation process

• location for autocall macros

• SAS libraries for a data mart

To keep the directory structure consistent and organized, SAS provides a script with theSAS installation to create the required directory structure.

UNIXTo create the SAS data mart directories on a UNIX server, perform the following steps:

1. Log on with the user ID that is used to execute the alert generation processes. In previoussections of this document, the suggested user ID is sassna.

2. Change directory to !SASROOT/misc/snamva/dbmsc/util/.

3. Create the data mart directories with the sfs_create_project_dirs.sh script:

93

./sfs_create_project_dirs.sh conf-dir sas-dir mart-dir

Note: Ensure that the user who executes the alert generation processes has Writepermission on all of the directory paths.

Example Code 10.1 Data Mart Directory Creation

./sfs_create_project_dirs.sh /data/sna/conf /data/sna/sas /data/sna/mart

The arguments in the previous example create the following directory structure:

/data/sna/conf/agp

/data/sna/mart/alert_detail

/data/sna/mart/alert_summary

/data/sna/mart/network_links

/data/sna/mart/network_nodes

/data/sna/mart/prep_data

/data/sna/mart/project_alert_detail_code

/data/sna/mart/project_alert_detail_codegen

/data/sna/mart/scenario_archive

/data/sna/mart/scenario_code

/data/sna/mart/scenario_codegen

/data/sna/mart/scenario_header_code

/data/sna/mart/scenario_prep_code

/data/sna/mart/scenario_prep_codegen

/data/sna/mart/scoring_parameters

/data/sna/sas/sasautos

Microsoft WindowsTo create the SAS data mart directories on a Microsoft Windows server, do the following:

1. Log on and open a command prompt.

2. Change directory to !SASROOT\snamva\sasmisc\dbmsc\util\.

3. Create the data mart directories with the sfs_create_project_dirs.bat script:

sfs_create_project_dirs.bat conf-dir sas-dir mart-dir

Example Code 10.2 Data Mart Directory Creation

sfs_create_project_dirs.batE:\data\sna\conf E:\data\sna\sas E:\data\sna\mart

The arguments specified in the example create the following directory structure:

E:\data\sna\conf\agp

E:\data\sna\mart\alert_detail

E:\data\sna\mart\alert_summary

E:\data\sna\mart\network_links

94 Chapter 10 • Register Data Mart Libraries

E:\data\sna\mart\network_nodes

E:\data\sna\mart\prep_data

E:\data\sna\mart\project_alert_detail_code

E:\data\sna\mart\project_alert_detail_codegen

E:\data\sna\mart\scenario_archive

E:\data\sna\mart\scenario_code

E:\data\sna\mart\scenario_codegen

E:\data\sna\mart\scenario_header_code

E:\data\sna\mart\scenario_prep_code

E:\data\sna\mart\scenario_prep_codegen

E:\data\sna\mart\scoring_parameters

E:\data\sna\sas\sasautos

Register a SAS Library for Alert Detail TablesThe steps in this section describe how to register the SAS library for the alert detail tables.The following table identifies the information that is necessary for registering this library.

Table 10.1 Alert Detail Tables Library Properties

Field Description

Name SNA_ALDT

Location /Products/SAS Social NetworkAnalysis/SNA_ALDT

SAS server SASApp

Libref SNA_ALDT

Path Specification mart-dir/alert_detail

To register the SNA_ALDT library, perform the following steps:

1. Provide the following information on the wizard pages:

Note: If prompted for a logon ID and password, enter sassrv.


3. From the list of libraries, select SAS BASE Library and click Next.

4. Enter SNA_ALDT in the Name field. Click Browse and create the /Products/SASSocial Network Analysis/SNA_ALDT path.

Register a SAS Library for Alert Detail Tables 95


Click Next.

5. From the list of Available servers, select SASApp.

Click Next.

6. Enter SNA_ALDT in the Libref field. Click New and use the file browser to navigateto the location of the alert_details directory that was created with thesfs_create_project_dirs script.


Click Next.


Register a SAS Library for Alert Summary TablesA SAS library for the alert summary tables must be created. The steps are similar to creatingthe alert detail table library. Use the values in the following table:

Table 10.2 Alert Summary Tables Library Properties

Field Description

Name SNA_ALSM

Location /Products/SAS Social NetworkAnalysis/SNA_ALSM

SAS server SASApp

Libref SNA_ALSM

Path Specification mart-dir/alert_summary

Register a SAS Library for Alert Summary Tables 97

Register a SAS Library for Data Mart TablesA SAS library for data mart tables must be created. The steps are similar to creating thealert detail table library. Use the values in the following table:

Table 10.3 Data Mart Tables Library Properties

Field Description

Name SNA_DM

Location /Products/SAS Social NetworkAnalysis/SNA_DM

SAS server SASApp

Libref SNA_DM

Path Specification mart-dir

Register a SAS Library for Network Link TablesA SAS library for the network link tables must be created. The steps are similar to creatingthe alert detail table library. Use the values in the following table:

Table 10.4 Network Link Tables Library Properties

Field Description

Name SNA_LINK

Location /Products/SAS Social NetworkAnalysis/SNA_LINK

SAS server SASApp

Libref SNA_LINK

Path Specification mart-dir/network_links


Register a SAS Library for Network Node TablesA SAS library for the network node tables must be created. The steps are similar to creatingthe alert detail table library. Use the values in the following table:

Table 10.5 Network Node Tables Library Properties

Field Description

Name SNA_NODE

Location /Products/SAS Social NetworkAnalysis/SNA_NODE

SAS server SASApp

Libref SNA_NODE

Path Specification mart-dir/network_nodes

Register a SAS Library for Alert GenerationProcess Input Tables

A SAS library for the input tables that are used in the alert generation process must becreated. The steps are similar to creating the alert detail table library. Use the values in thefollowing table:

Table 10.6 Input Tables Library Properties

Field Description

Name SNA_PD

Location /Products/SAS Social NetworkAnalysis/SNA_PD

SAS server SASApp

Libref SNA_PD

Path Specification mart-dir/prep_data

Register a SAS Library for Alert Generation Process Input Tables 99

Chapter 11

Configure the Autoexec and VerifyLibraries

Modify SAS to Load the SAS Social Network Analysis Server Autoexec File . . . 101

Verify Access to the Libraries and Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Modify SAS to Load the SAS Social NetworkAnalysis Server Autoexec File

The SAS Social Network Analysis Server uses several macros and macro variables. Thesteps in this section describe the location of, and how to modify, the autoexec file that SASprovides with the SAS Social Network Analysis Server.

1. Locate the autoexec.sas file:

SAS-config-dir/Levn/SASApp/SASEnvironment/SASSocialNetwork/autoexec.sas

2. Within the autoexec file, edit the parameters shown in the following table.

Table 11.1 Autoexec File Parameters

Parameter Value

DB_SERVER_NAME

Provides the metadata name of the database server. Previous sections ofthis document used sample values, such as Oracle Server. Enclosethe value in the %STR function. For example, if the name of the databaseserver in the SAS Management Console is Oracle Server, theDB_SERVER_NAME parameter should be specified as follows:

%STR(Oracle Server)

DB_TRANS_LIB

Provides the metadata library name for the library that is used forconfiguration and alerts. Previous sections of this document identified theDB_KC library for this purpose.

DB_CORE_LIB

For deployments that use MySQL, remove this parameter. Fordeployments that use Oracle, SQL Server, or DB2, provide the metadatalibrary name for the library that is used to store core entity data. Thisdocument provided a sample name of DB_CORE.

SAS_DM_LIB Provides the metadata library name for the SAS data mart library. Previoussections of this document provided a sample name of SNA_DM.

101

Parameter Value

SAS_PATH Provide the fully qualified path that was created with the sas-dir parameterto the sfs_create_project_dirs script. Enclose the value in a %STR()function—for example, %STR(C:\Data\sna\sas).

CONF_PATH Provide the fully qualified path that was created with the conf-dirparameter to the sfs_create_project_dirs script. Enclose the value in a%STR() function—for example, %STR(C:\Data\sna\conf).

3. Add a DATA step to the file. Without this entry, SAS starts and then becomesunresponsive:

data _null_; run;

The following code is an example:

data _null_; run;%sfs_util_autoexec(use_omr=YES ,db_server_name=%str(Oracle Server) ,db_trans_lib=DB_KC ,db_core_lib=DB_CORE ,sas_dm_lib=SNA_DM ,sas_path=%str(C:\Data\sna\sas) ,conf_path=%str(C:\Data\sna\conf));

Verify Access to the Libraries and TablesAt this point in the installation and configuration process, the database server has beenconfigured with the tables that are needed by the SAS Social Network Analysis Server.Libraries are also registered in metadata to access the tables. The next step is to start SASand verify access to the tables. Verifying access to the tables confirms that SAS/ACCESSis configured correctly, the database server and tables are configured correctly in metadata,and the SAS Social Network Analysis Server autoexec can be loaded correctly.

To verify table access, perform the following steps:

1. Log on to the machine that is hosting the SAS Social Network Analysis Server. In amulti-machine deployment, log on to the server-tier machine.

2. Change directory to the SAS configuration directory:

cd SAS-config-dir/Levn/SASApp

3. Start SAS with the -metauser and -metapass options:

UNIX Specifics./sas.sh -metauser sassna -metapass password

Windows Specificssas.bat -metauser sassna -metapass password

4. Review the SAS log and confirm that the following libraries are assigned:

• SNA_SDM

• SNA_NODE

102 Chapter 11 • Configure the Autoexec and Verify Libraries

• SNA_LINK

• SNA_ALDT

• SNA_ALSM

• SNA_PD

• SNA_SP

• DB_KC

• DB_CORE

• SNA_DM

5. Confirm that the macro variables are available to the SAS session by issuing thefollowing %PUT statement:

%put SFS_TRANS_DATABASE=&SFS_TRANS_DATABASE

If the autoexec is configured correctly, the SAS log indicates a value such asSNAALERT.

Verify Access to the Libraries and Tables 103

104 Chapter 11 • Configure the Autoexec and Verify Libraries

Part 5

Configure Core Entity Tables, JobCalendar, and Stored Processes

Chapter 12Configure Core Entity Tables, Job Calendar, and Stored Processes . 107

105

Chapter 12

Configure Core Entity Tables, JobCalendar, and Stored Processes

Load the Entity Tables and Job Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Fields in FSK_JOB_CALENDAR Updated by

%SFS_UTIL_SEED_AGP_METADATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Calendar Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Create Templates Used by the Alert Generation Process . . . . . . . . . . . . . . . . . . . . 110

Import SAS Stored Processes and Deploy Web Services . . . . . . . . . . . . . . . . . . . . 110Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Import SAS Stored Processes from a SAS Package . . . . . . . . . . . . . . . . . . . . . . . . 110Deploy the Imported SAS Stored Processes as a Web Service . . . . . . . . . . . . . . . 112

Modify SAS Stored Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Load the Entity Tables and Job Calendar

OverviewEntities are used in the alert generation process for aggregating alerts. Therefore, they mustbe loaded into database tables before projects and scenarios can be added to the system forthe alert generation process. Entities are loaded to the database through the%SFS_UTIL_SEED_AGP_METADATA macro. This macro reads comma-separated-value (CSV) files to load the FSK_ENTITY_LEVEL_INFO andFSK_ENTITY_RELATION tables. The same macro seeds the FSK_JOB_CALENDARtable.

Note: The names of CSV files must be of the same case, either upper case or lower case,but not mixed case. By default, the SAS macro looks for the CSV files in the conf/agpdirectory that was created with the sfs_create_project_dirs script.

1. Create the two CSV files in the conf/agp directory:

• fsk_entity_level_info_import.csv

• fsk_entity_relation_import.csv

Examples of these files exist in the following locations:

UNIX Specifics!SASROOT/misc/snamva/dbmsc/seed/fsk_entity_level_info_import.csv

107

!SASROOT/misc/snamva/dbmsc/seed/fsk_entity_relation_import.csv

Windows Specifics!SASROOT\snamva\sasmisc\dbmsc\seed\fsk_entity_level_info_import.csv

!SASROOT\snamva\sasmisc\dbmsc\seed\fsk_entity_relation_import.csv

2. Start SAS with the user ID that is used to run the alert generation process. For example,if the user ID is sassna, start SAS with the following command:

sas -metauser sassna -metapass password

3. Run the %SFS_UTIL_SEED_AGP_METADATA macro.

Note: The SAS log will contain an error message stating that the macro was unable totruncate FSK_JOB_CALENDAR. This error occurs because the data set is empty,but it causes no problems. If the macro is run a second time, the error does notappear because the data set is no longer empty.

4. Review the SAS log and use the Explorer window to confirm that the data was loadedfrom the CSV files into the tables FSK_ENTITY_LEVEL_INFO andFSK_ENTITY_RELATION.

5. Confirm that FSK_JOB_CALENDAR is populated with data.

Fields in FSK_JOB_CALENDAR Updated by%SFS_UTIL_SEED_AGP_METADATA

The fields in FSK_JOB_CALENDAR that require updates appear in the following table.

Table 12.1 FSK_JOB_CALENDAR Fields

Field Value Description

RUNDATE_IND Y or N Indicates whether the alert generation process should executefor a given calendar date. A value of Y indicates that the alertgeneration process should be executed on the given calendardate. Since the alert generation process must be scheduled inorder for any scenario to be executed, it is required to set theRUNDATE_IND for each available run date.

DAILY_RUNDATE_IND Y or N Indicates whether the alert generation process and dailyscenario(s) should execute for a given calendar date. A valueof Y indicates that the alert generation process should beexecuted on the given calendar date and the daily scenario(s)should be executed for the same date. Since the alertgeneration process must be scheduled in order for anyscenario to be executed, it is required to set theDAILY_RUNDATE_IND to Y for each available run date.

WEEKLY_RUNDATE_IND Y or N If for a given run date (calendar date), weekly scenarios needto be executed, then WEEKLY_RUNDATE_IND must alsobe set to Y.

108 Chapter 12 • Configure Core Entity Tables, Job Calendar, and Stored Processes

Field Value Description

MONTHLY_RUNDATE_IND Y or N If for a given run date (calendar date), monthly scenariosneed to be executed, then MONTHLY_RUNDATE_INDmust also be set to Y.

STATUS_IND Y or N Indicates whether that particular date has completelyexecuted (Y).

BUSINESS_DAY_COUNT Numeric, -1 =do not include

A BUSINESS_DAY_COUNT of ( 1) indicates that the alertgeneration process should not run on this date and is used todifferentiate between business and physical calendar days.This relationship is used to create the SAS formatsNUM_TO_DATE and DATE_TO_NUM and is used in mostscenarios as well as in the replication process.

Note: The combination of RUNDATE_IND=Y and STATUS_IND=N controls the nextvalid run date.

Regularly scheduled monthly and weekly jobs (such as weekly jobs scheduled every secondMonday) can be updated programmatically for FSK_JOB_CALENDAR by running aprogram modeled after the job control code in install.sas.

Non-recurring updates can be made via FSEDIT, VIEWTABLE, SQL, and the DATA step.

Calendar LayoutThe alert generation calendar consists of a sequence of days and additional attributes thatenable users to specify when the alert generation process should execute. The followingexplains each field.

Table 12.2 Descriptions of Fields in the Alert Generation Calendar

Field Description

JOB_CALENDAR_ID Integer surrogate key value.

CALENDAR_DATE SAS DATETIME Value representing the date and time. Time is specified as 00:00:00.

RUNDATE_IND Indicates whether the day is a valid run date. Valid values are Y and N.

DAILY_RUNDATE_IND Indicates whether the day is a daily run date and is used for scenario codegeneration. Valid values are Y and N.

WEEKLY_RUNDATE_IND Indicates whether the day is a weekly run date and is used for scenario codegeneration. Valid values are Y and N.

MONTHLY_RUNDATE_IND Indicates whether the day is a monthly run date and is used for scenario codegeneration. Valid values are Y and N.

STATUS_IND Indicates the status of the alert generation process for that day. Y indicates thatthe day has been processed. N indicates that it has not.

BUSINESS_DAY_COUNT Numeric indicator that distinguishes between business and physical days. Validvalues are -1 or any sequentially increasing positive integer

Load the Entity Tables and Job Calendar 109

Create Templates Used by the Alert Generation ProcessStart SAS with a user ID that is a member of the SNADBUSERS metadata group. The userID that is used to run the alert generation process was added to this group in previousinstructions in this document and can be used for this step. Use a command that is similarto the following example:

sas -metauser userID -metapass password

1. Load the following SAS program into the program editor and submit it:

UNIX Specifics!SASROOT/misc/snamva/dbmsc/ddl/create_templates_sas.sas

Windows Specifics!SASROOT\snamva\sasmisc\dbmsc\ddl\create_templates_sas.sas

2. For Oracle installations only, load the following SAS program into the program editorand submit it:

UNIX Specifics!SASROOT/misc/snamva/dbmsc/ddl/create_templates_orcl.sas

Windows Specifics!SASROOT\snamva\sasmisc\dbmsc\ddl\create_templates_orcl.sas

Import SAS Stored Processes and Deploy WebServices

OverviewThe investigator user interface shows alerts that are generated by the alert generationprocess. For alert viewing, SAS Stored Processes are deployed as Web Services, and theinvestigator user interface displays the alerts that are read by the SAS Stored Processes.

Import SAS Stored Processes from a SAS PackageSAS provides template SAS Stored Process metadata in a SAS package file. To import atemplate SAS package, perform the following steps:

1. Using SAS Management Console, select the Folders tab and navigate to /System/Applications/SAS Social Network Analysis/Social NetworkAnalysis 2.2.

2. Right-click the Social Network Analysis 2.2 folder and select Import SAS Package.


Display 12.1 Import SAS Package

3. Select the Browse button and navigate to the location of the template SAS packagefile:

UNIX Specifics!SASROOT/misc/snamva/Template.spk

Windows Specifics!SASROOT\snamva\sasmisc\Template.spk

a. Ensure that the Include access controls check box is not selected.

b. Select Next.

4. For each of the stored process icons, such as getActionableEntities, select the icon anddeselect the Include source code check box. The stored process code is not importedwith the package because it is already installed in the SAS installation directory. Thelocation is identified later in this procedure.

Import SAS Stored Processes and Deploy Web Services 111

Display 12.2 Import SAS Package: Select Objects to Import

5. Select Next.

6. Select Next on the About Metadata Connections page.

7. Select SASApp as the target application server on the SAS Application Servers page,and then click Next.

8. Select Add on the Source Code Repositories page, and provide the directory name:

UNIX Specifics!SASROOT/sasstp/snamva/

Windows Specifics!SASROOT\snamva\sasstp

9. Use the Target menu to select the directory that was just added, and then click Next.

10. Review the Summary page, and then click Next.

11. Confirm that the import process completed successfully, and then click Finish.

Deploy the Imported SAS Stored Processes as a Web ServiceAfter the SAS package file is imported, metadata is associated with the SAS program codefor the stored processes in the SAS installation directory. The code for the stored processescan be modified at any time to configure the display of alerts and social networks on theinvestigator user interface. However, they are deployed as a Web service now, even thoughthe SAS program code can be customized later.

1. Use the Folders tab of SAS Management Console to navigate to the folder that wasjust imported to the /System/Applications/SAS Social NetworkAnalysis/Social Network Analysis 2.2 folder.


2. Select the Template folder, unless it has been renamed. If the folder has been renamed,select the renamed folder. The stored process icons appear in the right pane.

3. Deploy the alerts-related Web service. Hold down the CTRL key and click to selectthe following stored process icons:

• getActionableEntities

• getAlertTransactions

• getChartSeries

• getSubAlerts

• processAlertResponse

4. Right-click one of the selected icons and select Deploy As Web Service. The DeployAs Web Service wizard starts.

5. On the Web Service Information page, confirm or set the following values:

• Select the default value for Web Service Maker URL from the menu.

• Make sure that New Web Service Name is set to the value ofTemplateAlerts. However, if the folder was renamed to a value likeHealthcare, then the New Web Service Name must be HealthcareAlerts.

• The choice of credentials to use does not matter.

Click Next.

6. On the Web Service Keywords and Namespace page, provide the following value forthe Namespace field:

http://sas.com/sso/fraud/alerts

Click Next.

7. Confirm the settings and then click Finish.

8. Deploy the social network-related Web service using a method that is similar todeploying the alerts-related Web service. Hold down the CTRL key and click to selectthe following stored process icons:

• getSocialNetwork

• getSocialNetworkNodeDetails

• growSocialNetworkNode

9. Right-click one of the selected icons and select Deploy As Web Service. The DeployAs Web Service Wizard starts.

10. On the Web Service Information page, confirm or set the following values:

• Use the default value for Web Service Maker URL.

• Make sure that New Web Service Name is set to the value ofTemplateSocialNetworkAnalysis. However, if the folder was renamed to a valuelike Healthcare, then the New Web Service Name must beHealthcareSocialNetworkAnalysis.

• The choice of credentials to use does not matter.

Click Next.

11. On the Web Service Keywords and Namespace page, provide the following value forthe Namespace field:

http://sas.com/sso/fraud/sna

Import SAS Stored Processes and Deploy Web Services 113

Click Next.

12. Confirm the settings and then click Finish.

If the deployment completes successfully, two new Web services (TemplateAlerts andTemplateSocialNetworkAnalysis) are listed at the following URL:

http://WebApplicationServerHostName:port/SASBIWS

Modify SAS Stored ProcessesEach of the SAS Stored Process files that are delivered with the SAS Social NetworkAnalysis Server are typically modified to provide a customer-specific experience. Onecommon modification is used to ensure that investigators access the database tables withappropriate privileges. By executing the SAS Social Network Analysis Server autoexec atthe start of each stored process invocation, the credentials for the investigator are checkedwith the SAS Metadata Server, and then associated with the assigned database credentials.

The following code is an example of the modification to the getActionableEntities storedprocess.

/* modified getActionableEntities stored process */%let syscc=0;%let trans_rc=0;%let rc_actionable_entity_query=0;

%sfs_util_autoexec(use_omr=YES ,db_server_name=%str(Oracle Server) ,db_trans_lib=DB_KC ,db_core_lib=DB_CORE ,sas_dm_lib=SNA_DM ,sas_path=%str(C:\Data\sna\sas) ,conf_path=%str(C:\Data\sna\conf));

%sfs_dm_query_actionable_entities(_rc=rc_actionable_entity_query);

Perform the modification to each of the stored process files. Without this modification, thedatabase libraries and the SAS libraries are not assigned when each stored process isinvoked.


Part 6

Register Investigators and ETLDevelopers

Chapter 13Register Investigators and ETL Developers . . . . . . . . . . . . . . . . . . . . . 117

115

Chapter 13

Register Investigators and ETLDevelopers

Initialize Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Add an Administrator Group and Administrators . . . . . . . . . . . . . . . . . . . . . . . . . 117Add an Investigator Group and Investigators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Synchronize Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Register ETL Developers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Initialize Users and Groups

Add an Administrator Group and AdministratorsAdministrators for the SAS Social Network Analysis Server use an administrative userinterface to manage projects, scenarios, and routing and suppression groups. Access to theadministrative user interface is controlled by metadata permissions on a metadata folder.SAS recommends creating a group, giving the group WriteMetadata privilege on the folder,and then assigning administrators to the group.

1. Use the User Manager plug-in to SAS Management Console to create a group namedSNA Administrators.

When creating the group, select the Groups and Roles tab and add the SNADBUSERSgroup as a member of this group so that administrators have Read and Write access tothe database.

2. Select the Folders tab and then navigate to /System/Applications/SASSocial Network Analysis/Social Network Analysis 2.2.

3. Right-click the folder icon and select Properties.

4. Select the Authorization tab and then click Add. The Add Users and Groups dialogbox appears.

5. Select SNA Administrators from the list, select the right-arrow icon, and click OK.The Add Users and Groups dialog box closes.

6. Select the SNA Administrators group that you just added to the Users and Groupslist.

7. In the Effective Permissions area, grant WriteMetadata permission. The indirectWriteMemberMetadata grant is automatically added with a gray background. ClickOK.

117

8. Select the Plug-ins tab and use the User Manager plug-in to add administrative users.As each user is added, use the Groups and Roles tab to make the user a member ofthe SNA Administrators group.

Add an Investigator Group and InvestigatorsInvestigators have access to the investigator user interface to view alerts. Access to theinvestigator user interface is controlled with explicit ReadMetadata permission on ametadata folder. A metadata folder is created when a SAS package file (SPK file) isimported into metadata. The metadata folder contains metadata for the SAS StoredProcesses that read the alerts generated by the alert generation process and display them inthe investigator user interface. Users can be added and removed from an investigator groupat any time.

1. Use the User Manager plug-in to SAS Management Console to create a group for theinvestigators. The group can be named according to the type of activity that the groupinvestigates, or perhaps by geographical location. As an example, create a group namedSNA Investigators.

When creating the group, select the Groups and Roles tab and add the SNADBREADgroup as a member of this group so that investigators have Read access to the database.

2. Click the Folders tab and navigate to /System/Applications/SAS SocialNetwork Analysis/Social Network Analysis 2.2/Template. If thefolder was renamed when the Template.spk file was imported, then the folder namewill be different.

3. Right-click the folder icon and select Properties.

4. Select the Authorization tab and click Add. The Add Users and Groups dialog boxappears.

5. Select the group name, such as SNA Investigators, from the list, select the right-arrowicon, and click OK. The Add Users and Groups dialog box closes.

6. Select the group that you just added to the Users and Groups list.

7. In the Effective Permissions area, confirm that the ReadMetadata permission isgranted and has a white background. Click OK.

8. Select the Plug-ins tab and use the User Manager plug-in to add investigative users.As each user is added, use the Groups and Roles tab to make the user a member ofthe investigative group.

Investigative users can belong to more than one investigative group, but they cannot belongto the administrator group. For example, an investigator can be a member of a group thatinvestigates check fraud and a member of a group that investigates wire fraud. However,do not nest groups.

Synchronize Users and GroupsAfter users, administrators, and groups are added to metadata, the information must bepropagated to tables in the database. SAS provides the %SFS_UTIL_SYNCH_USERSmacro to perform this function. Whenever users, administrators, group membership, orgroup privilege on a metadata folder are changed, run this macro by performing thefollowing steps:

118 Chapter 13 • Register Investigators and ETL Developers

1. Log on to the SAS Social Network Analysis Server machine.

2. Start SAS with a user ID that is a member of the SNADBUSERS metadata group. Theuser ID that is used to run the alert generation process was added to this group inprevious instructions in this document and can be used for this step. Use a commandthat is similar to the following example:

sas -metauser userID -metapass password

3. Run the macro. The following code is an example:

%let rc = 0;%sfs_util_synch_users(testing='N', rc=&rc);

4. Review the SAS log and then confirm that the return code is zero:

%put rc=&rc

Register ETL DevelopersThe DB_CORE library represents core-entity data that can contain security-sensitiveinformation such as account numbers. The data is added to the DB_CORE library byextract, transform, and load (ETL) users and jobs. These users require Write access to theDB_CORE library, and that access is provided by being a member of theSNACOREUSERS group for deployments that use Oracle, and a member of theSNADBUSERS group for deployments that use MySQL, DB2, or SQL Server.

Register ETL Developers 119

120 Chapter 13 • Register Investigators and ETL Developers

Part 7

Optional Features

Chapter 14Optional Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

121

Chapter 14

Optional Features

Comments Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Integrating with a Geographic Map Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Integrating with SAS Enterprise Case Management . . . . . . . . . . . . . . . . . . . . . . . 125Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Sample DDL for User-Defined Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Extract EAR File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Recreate the EAR File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Comments FeatureFor deployments that include SAS Enterprise Business Intelligence Server, a commentingfeature can be enabled. Enabling this feature results in providing investigators with anopportunity to associate comments with the actionable entity for an alert and with nodesin a social network diagram. The comments are stored in the database that is used for SASShared Services.

123

The following display shows an example of the commenting feature and highlights theNew Topic button that is used to add comments.

To enable the commenting feature, perform the following steps:

1. Extract the sas.socialnetworkanalysis2.2.ear file to a temporary location. For moreinformation, see “Extract EAR File Contents” on page 130.

2. Edit the WEB-INF/classes/config.properties file and add the followingproperty:

use.commentservices=true

3. Recreate the sas.socialnetworkanalysis2.2.ear file. For more information, see “Recreatethe EAR File” on page 131.

Note: Do not use DEBUG-level logging for the SAS Social Network Analysis Webapplication when the commenting feature is enabled. If DEBUG-level logging is set,then attempting to add a comment results in an exception for the investigator in the userinterface, and the comment is not stored.

Integrating with a Geographic Map ServiceThe SAS Social Network Analysis Server can integrate with a geographic map service.When this feature is enabled, a social network can be displayed with a background that isprovided by the map service. The social network diagram can integrate with either EsriArcGIS Online Map Service or a MAPNIK Open Street Map layer for OpenScales.

The following list identifies the requirements for integrating a geographic map service:

• You must provide a URL to the map service for deployments that use Esri ArcGISOnline Map Service.

• Latitude and longitude variables with coordinate values must be present in the data setthat represents the social network diagram nodes.

124 Chapter 14 • Optional Features

To enable the geographic map service feature, perform the following steps:


2. Edit the config.xml file to add information about the map service. The following codeshows sample values:

<mapService>   <type>ESRI</type> <url>http://hostname.example.com/urlForMapService</url></mapService>

Note: Do not use a URL element for an OpenScales deployment.


When this feature is enabled and investigators view social network diagrams that use data

sets with latitude and longitude variables, the Map icon ( ) is visible. Clicking the Mapicon changes the social network diagram background to the map that is provided by themap service.

Integrating with SAS Enterprise Case Management

Feature DescriptionSAS Enterprise Case Management complements the SAS Social Network Analysis Serverby providing a way to investigate an alert and then open a case against the alerted actionableentity. When this feature is enabled, an investigator has two ways to create a case:

• use the Update Alert menu to create a case against the actionable entity, and none,some, or all of the related alerts as incidents

• use the node icon menu from the network diagram to create a case against the actionableentity, without adding any incidents

Prerequisites• SAS Enterprise Case Management must be installed and configured to the point that it

is ready for customizations.

• User-defined fields for cases and incidents must be added to the SAS Enterprise CaseManagement database. The user-defined fields for incidents must be created, even ifyou do not plan to use them all. If you do not want to use them all, exclude the columnsfrom the user interface definition files.

Integrating with SAS Enterprise Case Management 125

InstructionsThe following high-level steps describe how to perform the integration. Refer to the SASEnterprise Case Management: Administrator's Guide for details about customizing SASEnterprise Case Management.

Customize SAS Enterprise Case Management

1. When an investigator creates a case with the SAS Social Network Analysis Server,case-related fields are populated with information about the actionable entity.Customize SAS Enterprise Case Management to accept the case-related fields:

Table 14.1 Required User-Defined Fields for Creating Cases

Column NameStandard or User-Defined Field Data Type Description

CASE.CASE_TYPE_CD Standard VARCHAR(10) Cases are created as"Generic."

CASE.CASE_DESC Standard VARCHAR(100) Set to the descriptionof the actionableentity. This field islimited to 99characters.

CASE.X_ACTIONABLEENTITYID User-Defined Field VARCHAR(50) Set to the entity IDfor the actionableentity.

CASE.X_ACTIONABLEENTITYTYPE User-Defined Field VARCHAR(50) Set to the entity typefor the actionableentity.

CASE.X_ACTIONABLEENTITYNAME User-Defined Field VARCHAR(100) Set to the entity namefor the actionableentity.

CASE.X_ACTIONABLEENTITYVERTICAL User-Defined Field VARCHAR(1000) Set to the alert seriesname. The alertseries name iscontrolled by thefolder name that isdescribed in step 2 of“Import SAS StoredProcesses andDeploy WebServices” on page110.

CASE.X_ALERTCOMMENTS User-Defined Field VARCHAR(1000) Set to the commentsadded by theinvestigator.



CASE.X_ALERTSUGGESTEDASSIGNEE User-Defined Field VARCHAR(1000) Set to the personsuggested by theinvestigator. Thisaction does notactually assign thecase to the suggestedassignee.

2. Customize SAS Enterprise Case Management to accept the incident-related fields:

Table 14.2 Required User-Defined Fields for Creating Incidents


INCIDENT.INCIDENT_TYPE_CD Standard VARCHAR(10) Cases are created as"Generic."

INCIDENT.INCIDENT_DESC Standard VARCHAR(100) Set to the descriptionof the related alert.This field is limitedto 99 characters.

INCIDENT.X_ACTIONABLEENTITYID User-Defined Field VARCHAR(50) Set to the entity IDfor the actionableentity.

INCIDENT.X_ACTIONABLEENTITYTYPE User-Defined Field VARCHAR(50) Set to the entity typefor the actionableentity.

INCIDENT.X_ACTIONABLEENTITYNAME User-Defined Field VARCHAR(100) Set to the entity namefor the actionableentity.

INCIDENT.X_ACTIONABLEENTITYVERTICAL

User-Defined Field VARCHAR(1000) Set to the alert seriesname. The alertseries name iscontrolled by thefolder name that isdescribed in step 2 of“Import SAS StoredProcesses andDeploy WebServices” on page110.

3. Design a custom user interface definition:

a. Include the user-defined fields from the previous tables. The following code is anexample of including the suggested assignee:


<field name="CASE.X_ALERTSUGGESTEDASSIGNEE" type="string" readonly="true"> <label>Suggested Assignee</label></field>

b. Include a link back to SAS Social Network Analysis. The following code is anexample of adding a button that displays the network diagram for the actionableentity:

<field type="component" component-name="LinkToDirective" name="LinkToDirective"> <label>View Network Diagram</label> <param name="directive" value="'viewSNANetwork'"/> <param name="actionableEntityID" value="CASE.X_ACTIONABLEENTITYID"/> <param name="actionableEntityType" value="CASE.X_ACTIONABLEENTITYTYPE"/> <param name="analyticContext" value="CASE.X_ACTIONABLEENTITYVERTICAL"/> <param name="render-as" value="'button'"/> <param name="window-features" value="'location=no,toolbar=no'"/></field>

Note: The 'viewSNANetwork' directive is case-sensitive. Also note that the valuesfor directive, render-as, and window-features are enclosed in single quotationmarks and double quotation marks.

Customize the SAS Social Network Analysis Server


5. Edit the config.xml file to set the <referToCase> value to true:

<referToCase>true</referToCase>


Configure Investigators in SAS Metadata

7. Use SAS Management Console to make each investigator a member of the EnterpriseCase Management Users group.

T I P Do not attempt to make the investigators group a member of the Enterprise CaseManagement Users group. The membership will not be detected and attempts tocreate cases will fail.

8. Also with SAS Management Console, give each investigator a role that is related toSAS Enterprise Case Management. The Case Management: Advanced role isavailable by default.

Sample DDL for User-Defined FieldsInformation about how to customize SAS Enterprise Case Management is available in theSAS Enterprise Case Management: Administrator's Guide. The following code exampledemonstrates one way to configure the case and incident-related fields.

%inc 'SAS-config-dir\Lev1\Applications\SASCaseManagementServerCfg\2.3\Source\control/ecm_autoexec.sas';

/*******************************************************************************


LOAD INCIDENT USER DEFINED FIELD DEFINITIONS

The structure for all five tables (CASE_UDF_DEF, INCIDENT_UDF_DEF, PARTY_UDF_DEF, FINANCIAL_ITEM_UDF_DEF, and GENERIC_DATA_UDF_DEF) is identical and each contains the following columns:

- UDF_TABLE_NM - UDF_NM - UDF_TYPE_NM - UDF_DESC - MAX_CHAR_CNT

*******************************************************************************/

proc sql;

/* Actionable Entity Definitions */ insert into ecm_db.incident_udf_def values ('INCIDENT', 'X_ACTIONABLEENTITYID', 'VARCHAR', 'Id', 50) values ('INCIDENT', 'X_ACTIONABLEENTITYTYPE', 'VARCHAR', 'Type', 50) values ('INCIDENT', 'X_ACTIONABLEENTITYNAME', 'VARCHAR', 'Name', 100) values ('INCIDENT', 'X_ACTIONABLEENTITYRANK', 'DOUBLE', 'Rank', null) values ('INCIDENT', 'X_ACTIONABLEENTITYVERTICAL', 'VARCHAR', 'Analytic Domain', 1000) values ('INCIDENT', 'X_ALERTAGGREGATIONDESCRIPTION', 'VARCHAR', 'Description', 1000);

insert into ecm_db.incident_udf_def values ('INCIDENT', 'X_ALERTID', 'VARCHAR', 'Date Submitted', 50) values ('INCIDENT', 'X_ALERTTYPE', 'VARCHAR', 'Completed By', 50) values ('INCIDENT', 'X_ALERTRANK', 'DOUBLE', 'Type of Incident', null) values ('INCIDENT', 'X_ALERTSTATUS', 'VARCHAR', 'Job Title', 32) values ('INCIDENT', 'X_ALERTTRIGGER', 'VARCHAR', 'Video surveillance?', 100) values ('INCIDENT', 'X_ALERTTRIGGERDTTM', 'DATE', 'Amount of Suspicious Activity', null) values ('INCIDENT', 'X_ALERTDESCRIPTION', 'VARCHAR', 'Location of Incident', 1000);

insert into ecm_db.incident_udf_def values ('INCIDENT', 'X_ENTITYID', 'VARCHAR', 'Account Number', 50) values ('INCIDENT', 'X_ENTITYTYPE', 'VARCHAR', 'Account Owner', 50) values ('INCIDENT', 'X_ENTITYNAME', 'VARCHAR', 'Account Owner', 100) values ('INCIDENT', 'X_ENTITYVALIDFROMDTTM', 'TIMESTAMP', 'Account Owner', null) values ('INCIDENT', 'X_ENTITYVALIDTODTTM', 'TIMESTAMP', 'Account Owner', null);quit;

/******************************************************************************* LOAD FINANCIAL_ITEM SUMMARY FIELD DEFINITIONS IN CASE AND INCIDENT*******************************************************************************/

proc sql;

/* Actionable Entity Definitions */ insert into ecm_db.case_udf_def values ('CASE', 'X_ACTIONABLEENTITYID', 'VARCHAR', 'Id', 50)


values ('CASE', 'X_ACTIONABLEENTITYTYPE', 'VARCHAR', 'Type', 50) values ('CASE', 'X_ACTIONABLEENTITYNAME', 'VARCHAR', 'Name', 100) values ('CASE', 'X_ACTIONABLEENTITYRANK', 'DOUBLE', 'Rank', null) values ('CASE', 'X_ACTIONABLEENTITYVERTICAL', 'VARCHAR', 'Analytic Domain', 1000) values ('CASE', 'X_ALERTAGGREGATIONDESCRIPTION', 'VARCHAR', 'Description', 1000);

insert into ecm_db.case_udf_def values ('CASE', 'X_ALERTID', 'VARCHAR', 'Date Submitted', 50) values ('CASE', 'X_ALERTTYPE', 'VARCHAR', 'Completed By', 50) values ('CASE', 'X_ALERTRANK', 'DOUBLE', 'Type of Incident', null) values ('CASE', 'X_ALERTSTATUS', 'VARCHAR', 'Job Title', 32) values ('CASE', 'X_ALERTTRIGGER', 'VARCHAR', 'Video surveillance?', 100) values ('CASE', 'X_ALERTTRIGGERDTTM', 'DATE', 'Amount of Suspicious Activity', null) values ('CASE', 'X_ALERTDESCRIPTION', 'VARCHAR', 'Location of Incident', 1000) values ('CASE', 'X_ALERTCOMMENTS', 'VARCHAR', 'Comment', 1000) values ('CASE', 'X_ALERTSUGGESTEDASSIGNEE', 'VARCHAR', 'Comment', 1000);

insert into ecm_db.case_udf_def values ('CASE', 'X_ENTITYID', 'VARCHAR', 'Account Number', 50) values ('CASE', 'X_ENTITYTYPE', 'VARCHAR', 'Account Owner', 50) values ('CASE', 'X_ENTITYNAME', 'VARCHAR', 'Account Owner', 100) values ('CASE', 'X_ENTITYVALIDFROMDTTM', 'TIMESTAMP', 'Account Owner', null) values ('CASE', 'X_ENTITYVALIDTODTTM', 'TIMESTAMP', 'Account Owner', null);quit;

Extract EAR File ContentsThis section does not describe a required task. The information in this section describeshow to extract the contents of the sas.socialnetworkanalysis2.2.ear file to a temporarylocation so that the contents can be modified. This task is a common task in severalconfiguration tasks. Follow these steps to extract the contents of the EAR file to a temporarylocation:

1. Stop the SAS Social Network Analysis Server Web application.

2. Make a backup copy of the sas.socialnetworkanalysis2.2.ear file that is in SAS-config-dir/Web/Staging/.

3. Make a temporary directory and extract the EAR file:

mkdir /tmp/earcd /tmp/earjar xf /path/to/sas.socialnetworkanalysis2.2.ear

4. Make another temporary directory and extract the WAR file:

mkdir /tmp/warcd /tmp/war/jar xf /tmp/ear/sas.sso.snaserver.war


Recreate the EAR FileThis section does not describe a required task. The information in this section describeshow to recreate the sas.socialnetworkanalysis2.2.ear file from a temporary location. Thistask is a common task after extracting the EAR file to a temporary location and performinga configuration task. Follow these steps to recreate the EAR file:

1. Recreate the WAR file:

cd /tmp/warjar cf /tmp/ear/sas.sso.snaserver.war .

2. Recreate the EAR file:

cd /tmp/earjar cf /tmp/sas.socialnetworkanalysis2.2.ear .

3. Copy the EAR file to SAS-config-dir/Web/Staging/ and then redeploy the Webapplication.

Recreate the EAR File 131

Your Turn

We welcome your feedback.

• If you have comments about this book, please send them to [email protected] the full title and page numbers (if applicable).

• If you have comments about the software, please send them to [email protected].

sas social network analysis server 2...• jboss application server • ibm websphere application...

Documents