sas social network analysis server 2support.sas.com/documentation/onlinedoc/socialnetwork... ·...

SAS® Social Network Analysis Server 2.1Installation and Configuration Guide

InstallConfigGd_colortitlpg.indd 1 12/9/09 9:39:56 AM

The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2009. SAS® Social Network Analysis Server 2.1: Installation and Configuration Guide. Cary, NC: SAS Institute Inc.

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

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

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

For a hard-copy 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 this publication.

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

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

1st electronic book, December 2009 2nd electronic book, March 2010

SAS® Publishing provides a complete selection of books and electronic products to help customers use SAS software to its fullest potential. For more information 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 other countries. ® indicates USA registration.

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

SAS Social Network Analysis Server 2.1: Table of Contents Installation and Configuration Guide

Table of Contents

Terms, Definitions and Acronyms ......................................................................................................... 1

1 Introduction .................................................................................................................................. 1

1.1 Purpose of this Document ............................................................................................................... 1 1.2 Target Audience ............................................................................................................................... 1 1.2.1 SAS Administrator Tasks ............................................................................................................ 1 1.2.2 Database Administrator Tasks ................................................................................................... 1 1.2.3 System Administrator Tasks ...................................................................................................... 1

1.3 Technical Support ............................................................................................................................ 1

2 Installation Overview ..................................................................................................................... 2

3 Pre‐Installation Instructions ........................................................................................................... 4

3.1 Get Sun JDK ...................................................................................................................................... 4 3.2 Get JBoss Application Server ........................................................................................................... 4 3.3 Get Junit 3.8.1 .................................................................................................................................. 4 3.4 Get BlazeDS ...................................................................................................................................... 4 3.5 Oracle Database ............................................................................................................................... 4 3.5.1 References ................................................................................................................................. 4 3.5.2 Instructions ................................................................................................................................ 5

3.6 MySQL Database .............................................................................................................................. 6 3.6.1 References ................................................................................................................................. 6 3.6.2 Prerequisites .............................................................................................................................. 6 3.6.3 Instructions ................................................................................................................................ 6

4 Installing the SNA Server and SNA Mid‐Tier ................................................................................... 7

4.1 Pre‐Installation Requirements for SAS 9.2 ....................................................................................... 7 4.2 Anonymous Web Access .................................................................................................................. 7 4.3 SNA Server and SNA Mid‐Tier .......................................................................................................... 8 4.4 Oracle Database ............................................................................................................................... 9 4.5 MySQL Database ............................................................................................................................ 12 4.6 Post‐Installation Steps for SAS 9.2 ................................................................................................. 15

5 Post‐Installation and Configuration .............................................................................................. 17

5.1 Oracle Database ............................................................................................................................. 17 5.1.1 Database User Creation ........................................................................................................... 17 5.1.2 Apply DDL and Seed the Database .......................................................................................... 17 5.1.2.1 Sun Solaris Servers ............................................................................................................... 18 5.1.2.2 Microsoft Windows .............................................................................................................. 18

5.1.3 Define New Authentication Domains ...................................................................................... 19 5.1.4 Define Users ............................................................................................................................ 20 5.1.5 Define SNADBUSERS Group ..................................................................................................... 24 5.1.6 Define SNADBREAD Group ...................................................................................................... 28 5.1.7 Define SNACOREUSERS Group ................................................................................................ 33 5.1.8 Define Oracle Server................................................................................................................ 38 5.1.9 Modify Connection for Oracle Server ...................................................................................... 42

03/26/2010 Page iii The information contained in this document is considered confidential and covered under the terms of any SAS agreements as executed by customer and SAS Institute Inc.

SAS Social Network Analysis Server 2.1: Table of Contents Installation and Configuration Guide

03/26/2010 Page iv The information contained in this document is considered confidential and covered under the terms of any SAS agreements as executed by customer and SAS Institute Inc.

5.1.10 Define Second Connection for Oracle Server .......................................................................... 44 5.1.11 Define Oracle Library for Configuration Metadata Tables ...................................................... 48 5.1.12 Define DB_CORE Read Only Oracle Library for Core Entity Tables ......................................... 53 5.1.13 Define DBCORERW Read/Write Oracle Library for Core Entity Tables ................................... 60

5.2 MySQL Database ............................................................................................................................ 65 5.2.1 Database User Creation ........................................................................................................... 65 5.2.2 Apply DDL and Seed the Database .......................................................................................... 66 5.2.2.1 Sun Solaris Servers ............................................................................................................... 66 5.2.2.2 Microsoft Windows .............................................................................................................. 67

5.2.3 Define New Authentication Domains ...................................................................................... 68 5.2.4 Define New Users .................................................................................................................... 69 5.2.5 Define SNADBUSERS Group ..................................................................................................... 72 5.2.6 Define SNADBREAD Group ...................................................................................................... 76 5.2.7 Define MySQL Server ............................................................................................................... 80 5.2.8 Add Attributes to MySQL Server ............................................................................................. 85 5.2.9 Define MySQL Library for Metadata Tables ............................................................................ 86

5.3 Create the SAS Data Mart Directories ........................................................................................... 91 5.3.1 Purpose .................................................................................................................................... 91 5.3.2 Sun Solaris 10 Servers .............................................................................................................. 92 5.3.3 Microsoft Windows Servers .................................................................................................... 92

5.4 Define SAS Data Mart Libraries ...................................................................................................... 94 5.4.1 Define SAS Library for Alert Detail Tables ............................................................................... 94 5.4.2 Define SAS Library for Alert Summary Tables ......................................................................... 99 5.4.3 Define SAS Library for Data Mart Tables ............................................................................... 104 5.4.4 Define SAS Library for SNA Network Link Tables .................................................................. 109 5.4.5 Define SAS Library for SNA Network Node Tables ................................................................ 114 5.4.6 Define SAS Library for Alert Detection Input Tables ............................................................. 119

5.5 Modify SAS to Load the SAS Social Network Analysis Server Autoexec ...................................... 123 5.5.1 Modify the Autoexec ............................................................................................................. 124

5.6 Verify Access to the Libraries and Tables .................................................................................... 126 5.7 Load the Entity Tables and Job Calendar ..................................................................................... 126 5.7.1 Fields in FSK_JOB_CALENDAR Updated by %SFS_UTIL_SEED_AGP_METADATA .................. 127 5.7.2 Calendar Layout ..................................................................................................................... 128 5.7.3 Create Templates Used by the Alert Generation Process ..................................................... 128

5.8 Import SAS Stored Processes and Deploy Web Services ............................................................. 129 5.8.1 Import SAS Stored Processes from a SAS Package ................................................................ 129 5.8.2 Deploy the Imported SAS Stored Processes as a Web Service .............................................. 132 5.8.3 Add Stored Process Server Invocation Options ..................................................................... 135

5.9 Initialize Users and Groups .......................................................................................................... 135 5.9.1 Add an Administrator Group and Administrators ................................................................. 135 5.9.2 Add an Investigator Group and Investigators ....................................................................... 136

5.10 Synchronize Users and Groups .................................................................................................... 136

SAS Social Network Analysis Server 2.1: Lists of Figures and Tables Installation and Configuration Guide

Lists of Figures and Tables

List of Figures

Figure 1: Installation and Configuration Overview ....................................................................................... 3 Figure 2: Enable Anonymous Web Access .................................................................................................... 7 Figure 3: SAS Internal Account: Anonymous Web User ............................................................................... 8 Figure 4: Oracle Mid‐Tier Database Configuration ....................................................................................... 9 Figure 5: Oracle Database JDBC Properties ................................................................................................ 10 Figure 6: Oracle Mid‐Tier Database User .................................................................................................... 11 Figure 7: MySQL Mid‐Tier Database Configuration .................................................................................... 12 Figure 8: MySQL Database JDBC Properties ............................................................................................... 13 Figure 9: MySQL Mid‐Tier Database User ................................................................................................... 14 Figure 10: BlazeDS Driver ............................................................................................................................ 15 Figure 11: Authentication Domains Display ................................................................................................ 20 Figure 12: New User: General ..................................................................................................................... 21 Figure 13: New User: Groups and Roles ..................................................................................................... 22 Figure 14: New User: Accounts ................................................................................................................... 23 Figure 15: New User: Authorization............................................................................................................ 24 Figure 16: SNADBUSERS Group: General .................................................................................................... 25 Figure 17: SNADBUSERS Group: Members ................................................................................................. 26 Figure 18: SNADBUSERS Group: Accounts .................................................................................................. 27 Figure 19: SNADBUSERS Group: Authorization ........................................................................................... 28 Figure 20: SNADBREAD Group: General ..................................................................................................... 29 Figure 21: SNADBREAD Group: Members ................................................................................................... 30 Figure 22: SNADBREAD Group: Groups and Roles ...................................................................................... 31 Figure 23: SNADBREAD Group: New Login Properties ............................................................................... 32 Figure 24: SNADBREAD Group: Authorization ............................................................................................ 33 Figure 25: SNACOREUSERS Group: General ................................................................................................ 34 Figure 26: SNACOREUSERS Group: Members ............................................................................................. 35 Figure 27: SNACOREUSERS Group: Accounts .............................................................................................. 36 Figure 28: SNACOREUSERS Group: Authorization ...................................................................................... 37 Figure 29: Define Oracle Server: New Server Wizard ................................................................................. 38 Figure 30: Define Oracle Server: Specify Server Name ............................................................................... 39 Figure 31: Define Oracle Server: Enter Server Properties .......................................................................... 40 Figure 32: Define Oracle Server: Enter Connection Properties .................................................................. 41 Figure 33: Define Oracle Server: Server Creation ....................................................................................... 42 Figure 34: Modify Oracle Server Connection: General .............................................................................. 43 Figure 35: Modify Oracle Server Connection: Authorization ...................................................................... 44 Figure 36: Define Second Oracle Server Connection: New Connection Wizard ......................................... 45 Figure 37: Define Second Oracle Server Connection: Enter Connection Properties .................................. 46 Figure 38: Define Second Oracle Server Connection: Connection Creation ............................................... 47 Figure 39: Configuration Metadata Tables: Select Library Type ................................................................. 48 Figure 40: Configuration Metadata Tables: Specify Library Details ............................................................ 49 Figure 41: Configuration Metadata Tables: Select SAS Servers .................................................................. 50 Figure 42: Configuration Metadata Tables: Enter Library Properties ......................................................... 51 Figure 43: Configuration Metadata Tables: Specify Server and Connection Information .......................... 52 Figure 44: Configuration Metadata Tables: Library Creation ..................................................................... 53

03/26/2010 Page v The information contained in this document is considered confidential and covered under the terms of any SAS agreements as executed by customer and SAS Institute Inc.


Figure 45: Core Entity Tables: Select Library Type ...................................................................................... 54 Figure 46: Core Entity Tables: Specify Oracle Library Details ..................................................................... 55 Figure 47: Core Entity Tables: Select SAS Servers (Optional) ..................................................................... 56 Figure 48: Core Entity Tables: Enter Library Properties .............................................................................. 57 Figure 49: Core Entity Tables: Data Server ................................................................................................. 58 Figure 50: Core Entity Tables: Library Creation .......................................................................................... 59 Figure 51: Core Entity Tables: Select Library Type ...................................................................................... 60 Figure 52: Core Entity Tables: Specify Oracle Library Details ..................................................................... 61 Figure 53: Core Entity Tables: Select SAS Servers (Optional) ..................................................................... 62 Figure 54: Core Entity Tables: Enter Library Properties .............................................................................. 63 Figure 55: Core Entity Tables: Specify Server and Connection Information ............................................... 64 Figure 56: Core Entity Tables: Library Creation .......................................................................................... 65 Figure 57: Authentication Domains Display ................................................................................................ 69 Figure 58: New User: General ..................................................................................................................... 70 Figure 59: New User: Groups and Roles ..................................................................................................... 71 Figure 60: New User: Accounts ................................................................................................................... 72 Figure 61: SNADBUSERS Group: General .................................................................................................... 73 Figure 62: SNADBUSERS Group: Members ................................................................................................. 74 Figure 63: SNADBUSERS Group: Accounts .................................................................................................. 75 Figure 64: SNADBREAD Group: General ..................................................................................................... 76 Figure 65: SNADBREAD Group: Members ................................................................................................... 77 Figure 66: SNADBREAD Group: Groups and Roles ...................................................................................... 78 Figure 67: SNADBREAD Group: New Login Properties ............................................................................... 79 Figure 68: Define MySQL Server: New Server Wizard ................................................................................ 80 Figure 69: Define MySQL Server: Specify Server Name .............................................................................. 81 Figure 70: Define MySQL Server: Enter Server Properties ......................................................................... 82 Figure 71: Define MySQL Server: Enter Connection Properties ................................................................. 83 Figure 72: Define MySQL Server: Server Creation ...................................................................................... 84 Figure 73: MySQL Server: Extended Attributes .......................................................................................... 85 Figure 74: Metadata Tables: Select Library Type ........................................................................................ 86 Figure 75: Metadata Tables: Specify Library Details ................................................................................... 87 Figure 76: Metadata Tables: Select SAS Servers ......................................................................................... 88 Figure 77: Metadata Tables: Enter Library Properties ................................................................................ 89 Figure 78: Metadata Tables: Specify Server and Connection Information ................................................. 90 Figure 79: Metadata Tables: Library Creation ............................................................................................ 91 Figure 80: Data Mart Directory Creation Example ‐ Sun Solaris Server ...................................................... 92 Figure 81: Data Mart Directory Creation Example – Microsoft Windows Server ....................................... 93 Figure 82: Alert Details Tables: Select Library Type .................................................................................... 94 Figure 83: Alert Details Tables: Specify SAS BASE Library Details ............................................................... 95 Figure 84: Alert Details Tables: Select SAS Servers (Optional).................................................................... 96 Figure 85: Alert Details Tables: Enter Library Properties ............................................................................ 97 Figure 86: Alert Details Tables: Library Creation ........................................................................................ 98 Figure 87: Alert Summary Tables: Select Library Type ............................................................................... 99 Figure 88: Alert Summary Tables: Specify SAS BASE Library Details ........................................................ 100 Figure 89: Alert Summary Tables: Select SAS Servers (Optional) ............................................................. 101 Figure 90: Alert Summary Tables: Enter Library Properties ..................................................................... 102 Figure 91: Alert Summary Tables: Library Creation .................................................................................. 103 Figure 92: Data Mart Tables: Select Library Type ..................................................................................... 104

03/26/2010 Page vi The information contained in this document is considered confidential and covered under the terms of any SAS agreements as executed by customer and SAS Institute Inc.


03/26/2010 Page vii The information contained in this document is considered confidential and covered under the terms of any SAS agreements as executed by customer and SAS Institute Inc.

Figure 93: Data Mart Tables: Specify SAS BASE Library Details ................................................................ 105 Figure 94: Data Mart Tables: Select SAS Servers (Optional) ..................................................................... 106 Figure 95: Data Mart Tables: Enter Library Properties ............................................................................. 107 Figure 96: Data Mart Tables: Library Creation .......................................................................................... 108 Figure 97: SNA Network Link Tables: Select Library Type ......................................................................... 109 Figure 98: SNA Network Link Tables: Specify SAS BASE Library ............................................................... 110 Figure 99: SNA Network Link Tables: Select SAS Servers (Optional) ........................................................ 111 Figure 100: SNA Network Link Tables: Enter Library Properties ............................................................... 112 Figure 101: SNA Network Link Tables: Library Creation ........................................................................... 113 Figure 102: SNA Network Node Tables: Select Library Type .................................................................... 114 Figure 103: SNA Network Node Tables: Specify SAS BASE Library Details ............................................... 115 Figure 104: SNA Network Node Tables: Select SAS Servers (Optional) .................................................... 116 Figure 105: SNA Network Node Tables: Enter Library Properties ............................................................ 117 Figure 106: SNA Network Node Tables: Library Creation ......................................................................... 118 Figure 107: Alert Detection: Select Library Type ...................................................................................... 119 Figure 108: Alert Detection: Specify SAS BASE Library Details ................................................................. 120 Figure 109: Alert Detection: Select SAS Servers (Optional) ...................................................................... 121 Figure 110: Alert Detection: Enter Library Properties .............................................................................. 122 Figure 111: Alert Detection: Library Creation ........................................................................................... 123 Figure 112: Modified SAS Configuration File – Sun Solaris ....................................................................... 125 Figure 113: Code to Insert......................................................................................................................... 125 Figure 114: Modified SAS Configuration File ‐ Microsoft Windows ......................................................... 125 Figure 115: Import SAS Package ............................................................................................................... 129 Figure 116: Import SAS Package: Select Objects to Import ...................................................................... 131 Figure 117: Modify Data Target: Schema URI ........................................................................................... 133

List of Tables

Table 1: Oracle Installation and Configuration References .......................................................................... 4 Table 2: MySQL Installation and Configuration References ......................................................................... 6 Table 3: SAS 9.2 Installation References ....................................................................................................... 7 Table 4: SAS 9.2 Configuration References ................................................................................................. 15 Table 5: Script Modification (for Oracle Databases) ................................................................................... 17 Table 6: sfs_util_create_orcl_template.sh Parameters .............................................................................. 18 Table 7: sfs_util_load_orcl_template.bat Parameters ............................................................................... 19 Table 8: Oracle Authentication Domains .................................................................................................... 19 Table 9: Script Modification (for MySQL).................................................................................................... 66 Table 10: sfs_util_load_mysql_template.sh Parameters ............................................................................ 67 Table 11: sfs_util_load_mysql_template.bat Parameters .......................................................................... 67 Table 12: MySQL Authentication Domains ................................................................................................. 68 Table 13: Autoexec File Parameters ......................................................................................................... 124 Table 14: FSK_JOB_CALENDAR Fields ....................................................................................................... 127 Table 15: Descriptions of Fields in the Alert Generation Calendar ........................................................... 128 Table 16: Stored Processes ....................................................................................................................... 132

SAS Social Network Analysis Server 2.1: Introduction Installation and Configuration Guide

Terms, Definitions and Acronyms

Term Definition

CSV comma separated value

DDL Data Definition Language

ETL extract, transform, and load

RDBMS relational database management system

SNA social network analysis

SPK SAS Package

03/26/2010 Page 1 of 137 The information contained in this document is considered confidential and covered under the terms of any SAS agreements as executed by customer and SAS Institute Inc.

SAS Social Network Analysis Server 2.1: Introduction Installation and Configuration Guide

1 Introduction 1.1 Purpose of this Document This document is the Installation and Configuration Guide for SAS Social Network Analysis Server 2.1. This document applies to SAS Social Network Analysis Server 2.1 with hot fix B14001 already applied. If the hot fix is not already applied, contact SAS technical support.

1.2 Target Audience The target audience members for this document are SAS administrators, database administrators, and system administrators using the SAS Social Network Analysis Server 2.1.

1.2.1 SAS Administrator Tasks Using the information in this document, SAS Administrators are able to assign investigator roles to investigators (configuration) within the SAS Social Network Analysis Server 2.1.

1.2.2 Database Administrator Tasks Using the information in this document, database administrators are able to configure schema within the SAS Social Network Analysis Server 2.1.

1.2.3 System Administrator Tasks Using the information in this document, system administrators are able to perform the following tasks:

1. Configure data sources and data stores. 2. Configure investigation paths.

1.3 Technical Support SAS Technical Support is the first group to contact regarding installation and configuration problems that installers encounter in the field. To contact SAS Technical Support, do the following:

1. Go to www.sas.com. 2. Select Contact Us. 3. Select the appropriate Web page or telephone number from the Support Contacts section of

the page.


www.sas.com

SAS Social Network Analysis Server 2.1: Installation Overview Installation and Configuration Guide

2 Installation Overview The installation and configuration of the SAS Social Network Analysis Server 2.1 occurs in three distinct phases (Figure 1):

1. Pre‐installation: a. Install and configure either a MySQL or an Oracle database. b. Acquire Adobe BlazeDS.

2. SNA Server Installation: Install the SNA Server, which includes the following: a. SAS Foundation b. SAS Social Network Analysis Server 2.1 c. SAS SNA Mid‐tier (may be installed on the same machine as the SNA Server) d. Post‐Installation steps for enabling either the SAS/ACCESS® Interface to MySQL or

SAS/ACCESS® to ORACLE. 3. Post‐Installation and Configuration: Configure the environment for SNA server, which includes

the following: a. Seeding the SNA relational database management system (RDBMS) configuration tables b. Defining the RDBMS and SAS data libraries c. Modifying the SAS Social Network Analysis Server 2.1 autoexec file d. Loading the entity configuration tables and job calendar e. Importing SAS stored processes and deploying Web services f. Initializing users and groups g. Synchronizing users and groups


SAS Social Network Analysis Server 2.1: Installation Overview Installation and Configuration Guide

03/26/2010 Page 3 of 137

Figure 1: Installation and Configuration Overview

The information contained in this document is considered confidential and covered under the terms of any SAS agreements as executed by customer and SAS Institute Inc.

SAS Social Network Analysis Server 2.1: Pre‐Installation Instructions Installation and Configuration Guide

3 Pre‐Installation Instructions This section contains pre‐installation instructions for preparing the SNA Server databases. Note: Only one database needs to be prepared: Oracle (Section 3.5) or MySQL (Section 3.6).

3.1 Get Sun JDK The SAS Social Network Analysis Server user interfaces and mid‐tier require the Sun JDK version 5 update 15. Use the following link to identify the version required for the specific hardware environment:

http://support.sas.com/resources/thirdpartysupport/v92m2/jdks.html

3.2 Get JBoss Application Server The SAS Social Network Analysis Server user interfaces and mid‐tier require JBoss 4.2.3.GA. The download is available at http://labs.jboss.com/portal/jbossas/download. Select the file for 4.2.3.GA.

3.3 Get Junit 3.8.1 If the SAS Deployment Tester is installed in addition to SNA Server, the mid‐tier requires Junit 3.8.1. The download is available at the following link:

http://sourceforge.net/projects/junit/files/junit/3.8.1/junit3.8.1.zip/download

3.4 Get BlazeDS The SAS Social Network Analysis Server user interfaces require software from the Adobe BlazeDS project. SAS requires version 3.2. The binary distribution is available from http://opensource.adobe.com/wiki/display/blazeds/Release+Builds. Record the location of the blazeds.war file. The location must be provided to the SAS Deployment Wizard.

3.5 Oracle Database

3.5.1 References

Table 1: Oracle Installation and Configuration References

Reference Format URL

General

Universal Installer and OPatch User's Guide for Windows and UNIX

HTML http://www.oracle.com/pls/db102/to_toc?pathname=em.102%2Fb16227%2Ftoc.htm&remark=portal+%28Getting+Started%29

Universal Installer and OPatch User's Guide for Windows and UNIX

PDF http://www.oracle.com/pls/db102/to_pdf?pathname=em.102%2Fb16227.pdf&remark=portal+%28Getting+Started%29

Sun Solaris

Release Notes HTML http://www.oracle.com/pls/db102/to_toc?pathname=relnotes.102%2Fb15689%2Ftoc.htm&remark=portal+%28Getting+Started%29


http://support.sas.com/resources/thirdpartysupport/v92m2/jdks.html

http://labs.jboss.com/portal/jbossas/download

http://sourceforge.net/projects/junit/files/junit/3.8.1/junit3.8.1.zip/download

http://opensource.adobe.com/wiki/display/blazeds/Release+Builds

http://www.oracle.com/pls/db102/to_toc?pathname=em.102%2Fb16227%2Ftoc.htm&remark=portal+%28Getting+Started%29

http://www.oracle.com/pls/db102/to_toc?pathname=em.102%2Fb16227%2Ftoc.htm&remark=portal+%28Getting+Started%29

http://www.oracle.com/pls/db102/to_pdf?pathname=em.102%2Fb16227.pdf&remark=portal+%28Getting+Started%29

http://www.oracle.com/pls/db102/to_pdf?pathname=em.102%2Fb16227.pdf&remark=portal+%28Getting+Started%29

http://www.oracle.com/pls/db102/to_toc?pathname=relnotes.102%2Fb15689%2Ftoc.htm&remark=portal+%28Getting+Started%29





Release Notes PDF http://www.oracle.com/pls/db102/to_pdf?pathname=relnotes.102%2Fb15689.pdf&remark=portal+%28Getting+Started%29

Database Installation Guide (SPARC 64‐bit)

HTML http://www.oracle.com/pls/db102/to_toc?pathname=install.102%2Fb15690%2Ftoc.htm&remark=portal+%28Getting+Started%29

Database Installation Guide (SPARC 64‐bit)

PDF http://www.oracle.com/pls/db102/to_pdf?pathname=install.102%2Fb15690.pdf&remark=portal+%28Getting+Started%29

Microsoft Windows (32‐bit)



Database Installation Guide




Microsoft Windows (x64)







3.5.2 Instructions 1. Install Oracle on the machine where the database is going to reside. Note: Install version 10G

Release 2. Also, record the location of the Oracle JDBC drivers. The location is typically $ORACLE_HOME/jdbc/lib. The location must be provided to the SAS Deployment Wizard.

2. Create and configure a database and schema within Oracle. During this process 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 with the name of snaalert, but the name referenced by the SAS Deployment Wizard can be changed during the installation. The creation of the database is usually performed with the Oracle Database Configuration Assistant (that is, DBCA).

Note: See Section 5.1.1 for an example script to execute (and modify, if applicable).

http://www.oracle.com/pls/db102/to_pdf?pathname=relnotes.102%2Fb15689.pdf&remark=portal+%28Getting+Started%29


http://www.oracle.com/pls/db102/to_toc?pathname=install.102%2Fb15690%2Ftoc.htm&remark=portal+%28Getting+Started%29


http://www.oracle.com/pls/db102/to_pdf?pathname=install.102%2Fb15690.pdf&remark=portal+%28Getting+Started%29




















3.6 MySQL Database

3.6.1 References

Table 2: MySQL Installation and Configuration References


Sun Solaris

Installing MySQL HTML http://dev.mysql.com/doc/refman/5.0/en/solaris‐installation.html

UNIX Post‐Installation Procedures

HTML http://dev.mysql.com/doc/refman/5.0/en/unix‐post‐installation.html

Operating System Specific Notes

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

Microsoft Windows

Installing MySQL HTML http://dev.mysql.com/doc/refman/5.0/en/windows‐installation.html

Windows Post‐installation Procedures

HTML http://dev.mysql.com/doc/refman/5.0/en/windows‐post‐installation.html

3.6.2 Prerequisites The SAS Social Network Analysis Server provides Web applications that are deployed on the JBoss Application Server. To communicate with MySQL, the JBoss application server and the SAS Web applications requires JDBC access to MySQL. Download Connector/J from the following link:

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

Note: Record the location of the JDBC drivers. The location must be provided to the SAS Deployment Wizard.

3.6.3 Instructions 1. Install MySQL on the machine where the database is going to reside. Note: 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 the database so

that the default engine type is InnoDB. SAS also suggests setting innodb_flush_log_at_trx_commit to 1 so that the transaction logs are flushed to disk after each transaction is committed. For Solaris installations, the MySQL configuration file is named my.cnf, and can be added to the /etc directory for global configuration of all MySQL server installations on the machine. Note: The SAS Deployment Wizard defaults to a database with the name of SNAALERT, but the name referenced by the SAS Deployment Wizard can be changed during the installation. To create a database, the following minimal example could be used within command line of the MySQL client:

mysql>CREATE DATABASE SNAALERT

Note: See Section 5.2.1 for an example script to execute (and modify, if applicable).

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

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

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

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

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

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

SAS Social Network Analysis Server 2.1: Installing the SNA Server and SNA Mid‐Tier Installation and Configuration Guide

4 Installing the SNA Server and SNA Mid‐Tier

4.1 Pre‐Installation Requirements for SAS 9.2 Table 3 contains links to reference documentation for installing SAS 9.2 Foundation on UNIX and Microsoft Windows environments. Go to the URL that corresponds to the appropriate operating system and follow all the applicable steps on those pages.

Table 3: SAS 9.2 Installation References

Operating System Document URL

UNIX SAS 9.2 Installation http://support.sas.com/kb/36/467.html

Windows SAS 9.2 Installation http://support.sas.com/kb/36/553.html

4.2 Anonymous Web Access During the installation of the SAS SNA Mid‐Tier, select the option to set up a SAS identity for anonymous access to certain Web services and Web applications (Figure 2). Enter a user ID and password for the internal SAS account to be used to grant clients access to applicable SAS Web Infrastructure Platform applications (Figure 3).

Figure 2: Enable Anonymous Web Access


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

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


Figure 3: SAS Internal Account: Anonymous Web User

4.3 SNA Server and SNA Mid‐Tier Depending on the plan file (describing how the servers are laid out for each installation), the SAS Social Network Analysis Server 2.1 and the SAS SNA Mid‐Tier may be installed on the same machine or on different machines. Note: The figures in this section (Figure 4 through Figure 10) illustrate the installation of the SAS Social Network Analysis Server 2.1 and the SAS SNA Mid‐Tier on the same machine.

After SAS 9.2 is installed, follow the relevant operating system‐specific configuration instructions that are linked in Table 4.



4.4 Oracle Database Within the SAS Deployment Wizard, users are asked a series of questions regarding database connection information required by the SNA Mid‐tier. Complete the following instructions:

1. Specify Oracle as the Database Type (Figure 4). 2. Enter the directory that contains the JDBC driver jars for the Oracle database.

Figure 4: Oracle Mid‐Tier Database Configuration



3. Enter the Host Name, Port, and Database Name for the JDBC connection for the Oracle database (Figure 5). The host name is the fully qualified host name where the Oracle RDBMS is installed. Note: In general, the port number required in 1521.

Figure 5: Oracle Database JDBC Properties



4. Enter the User ID and Password for the JDBC connection for the Oracle database (Figure 6). Note: The password must be entered a second time for confirmation purposes.

Figure 6: Oracle Mid‐Tier Database User



4.5 MySQL Database Within the SAS Deployment Wizard, users are asked a series of questions regarding database connection information required by the SNA Server Mid‐tier. Complete the following instructions:

1. Specify MySQL as the Database Type (Figure 7). 2. Enter the directory that contains the JDBC driver jars for the MySQL database.

Figure 7: MySQL Mid‐Tier Database Configuration



3. Enter the Host Name, Port, and Database Name for the JDBC connection for the MySQL database (Figure 8). The host name is the fully qualified host name where the MySQL RDBMS is installed.

Figure 8: MySQL Database JDBC Properties



4. Enter the User ID and Password for the JDBC connection for the MySQL database (Figure 9). Note: The password must be entered a second time for confirmation purposes.

Figure 9: MySQL Mid‐Tier Database User



5. Enter the location where the blazeds.war can be found (Figure 10).

Figure 10: BlazeDS Driver

Important Reminder: At this point in the process, follow the instructions in the operating system‐specific SAS 9.2 Foundation Configuration Guide (see Table 4).

4.6 Post‐Installation Steps for SAS 9.2 Table 4: SAS 9.2 Configuration References

Operating System Document URL

UNIX Configuration Guide for SAS® 9.2 Foundation

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

Windows Configuration Guide for SAS® 9.2 Foundation

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

Windows (x64) Configuration Guide for SAS® 9.2 Foundation

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










Note: The post‐installation and configuration for the SAS/ACCESS interfaces must be completed after the installation of SAS 9.2 Foundation.

Note: Before continuing with this installation, be sure to refer to the Special Install Instructions for Social Network Analysis Server, particularly for the SAS/OR OPTGRAPH procedure, that are available at the following link:

http://smteam.sas.com/workgroups/Social‐Network‐Analysis/default.aspx

http://smteam.sas.com/workgroups/Social-Network-Analysis/default.aspx

SAS Social Network Analysis Server 2.1: Post‐Installation and Configuration Installation and Configuration Guide

5 Post‐Installation and Configuration The instructions in this section define metadata within the SAS Management Console. Follow the instructions in Section 5.1 for Oracle databases or in Section 5.2 for MySQL databases.

5.1 Oracle Database

5.1.1 Database User Creation The SNA Server application requires database users. Three users need to be created:

1. snauser: Has read and write access to the schema where alert detection configuration tables are loaded.

2. 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 in the SNA Server Administration Guide.

3. snaread: Has read access to the schema where the alert detection configuration tables and the core entity data are loaded.

There is an example script for creating users that the person creating the database users can modify, if appropriate.

• Sun Solaris: !SASROOT/misc/snamva/dbmsc/util/create_app_user_orcl.sql

• Microsoft Windows: !SASROOT\snamva\sasmisc\dbmsc\util\create_app_user_orcl.sql

The necessary modifications appear in Table 5.

Table 5: Script Modification (for Oracle Databases)

Tag to be Modified Replacement Value for Tag

read/write dbuser password Password that snauser specifies to authenticate to the database

tablespace Name of the permanent tablespace used to store the SNA Server application objects

temporary tablespace Name of the temporary tablespace used to store the SNA Server application objects

read only dbuser password Password that SNAREAD specifies to authenticate to the database

5.1.2 Apply DDL and Seed the Database Previously, the database and database users were created. When the SAS Deployment Wizard 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 either create or seed the database. If a seed file with SQL does not exist to populate the SAS Social Network Analysis Server database tables, perform one of the following two procedures. Choose the correct procedure based on the operating system of the SAS Social Network Analysis Server.



Section 5.1.2.1 contains instructions for Sun Solaris servers; Section 5.1.2.2 contains instructions for Microsoft Windows servers.

5.1.2.1 Sun Solaris Servers

1. Log on with the SAS installer user ID. 2. Copy !SASROOT/misc/snamva/dbmsc/util/sfs_util_load_orcl_template.sh to a

new file, such as sfs_util_load_orcl_SNAALERT.sh. 3. Edit the copied file and replace the path to SNA RDBMS utility directory tag with the

fully qualified path to !SASROOT/misc/snamva/dbmsc/util/. Replace the tags with values for the parameters shown in Table 6.

4. Make the script executable: chmod 775 sfs_util_load_orcl_SNAALERT.sh

5. Execute the script: ./sfs_util_load_orcl_SNAALERT.sh

Table 6: sfs_util_create_orcl_template.sh Parameters

Parameter Value

ORACLE_SID System ID of the Oracle database

ORACLE_HOME Oracle database home directory

ORACLE_BASE Oracle database base directory

database Use the ORACLE_SID value

database user Database user ID that has read and write privileges; previous sections of this document suggest snauser

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

This script invokes sfs_util_load_orcl.sh. The second script uses sqlplus to communicate with Oracle. If the current user ID does not have access to sqlplus, the database administrator may need to ask the system administrator to add the sqlplus executable path to the PATH environment variable.

5.1.2.2 Microsoft Windows

1. Log on with the SAS installer user ID. 2. Copy !SASROOT\snamva\sasmisc\dbmsc\util\sfs_util_load_orcl_template.bat

to a new file, such as sfs_util_load_orcl_SNAALERT.bat. 3. Edit the copied file and replace the path to SNA RDBMS utility directory tag with the

fully qualified path to !SASROOT\snamva\sasmisc\dbmsc\util\. 4. Replace the tags with values for the parameters shown in Table 7.



5. Execute the script from the DOS command prompt. For example, at the DOS prompt, type the following: sfs_util_load_orcl_SNAALERT.bat

Table 7: sfs_util_load_orcl_template.bat Parameters

Parameter Value

database Use the ORACLE_SID

database user Database user ID that has read and write privileges. Previous sections of this document suggest snauser

database user password

Password for the database user ID


Fully qualified path to !SASROOT/snamva/sasmisc/dbmsc


Fully qualified path to !SASROOT/snamva/sasmisc/dbmsc/seed/seed_rdbms_orcl.sql

5.1.3 Define New Authentication Domains The steps in this section define new authentication domains for the Oracle database. Authentication domains are added using the SAS Management Console. An authentication domain is a name that facilitates the matching of logins with the servers for which they are valid, which is important when users access certain secondary servers, such as an Oracle server. Each Oracle server connection has an authentication domain associated with it.

Three authentication domains are required for users who execute the batch alert detection process and extract, transform, and load (ETL) processes, because Oracle requires a separate schema for each of the Authentication Domains shown in Table 8. Each Oracle schema has a server connection associated with it; the authentication domain is used to establish the connection.

Table 8: Oracle Authentication Domains

Domain Authorization Type Login ID Users

snaDbAuth Alert and configuration data library

snauser Users who execute the batch alert detection process

snaCoreAuth Core entity data library snacore Users who execute the batch alert detection process and ETL process to load the core entity data into the ORACLE database, specifically the SNACORE schema

snaDbRead Read‐only access for specific users

snaread Users who need read‐only access to the SNA metadata, such as investigators

To create the authentication domains, do the following within the SAS Management Console:



1. Right‐click on the User Manager. 2. Select Authentication Domains…. 3. Select New. 4. Enter the Name: snaDbAuth. 5. Select OK. 6. Repeat Steps 3 through 5 for the authentication domains snaCoreAuth and snaDbRead. The final Authentication Domains display appears (Figure 11).

Figure 11: Authentication Domains Display

5.1.4 Define Users The steps in this section define the users who execute the batch alert detection process and/or ETL processes. The example shown here defines a single application user with the user name snarun. The user ID snarun is used throughout the rest of the SNA installation and configuration guide. If another user ID is used for a customer implementation, assume that this user ID can substitute for snarun.



To define users, do the following:

1. Right‐click on User Manager. 2. Select New User. 3. In the General tab, enter snarun for the Name, Display Name, and Job Title (Figure 12).

Figure 12: New User: General



4. In the Groups and Roles tab, select BI Web Services Users (Figure 13).

Figure 13: New User: Groups and Roles



5. In the Accounts tab, select New (Figure 14). 6. Add the operating system login information (User ID and Password). 7. Specify the Authentication Domain: DefaultAuth.

Figure 14: New User: Accounts



8. In the Authorization tab, select PUBLIC, SAS System Services, SAS Administrators, and SASUSERS (Figure 15).

Figure 15: New User: Authorization

5.1.5 Define SNADBUSERS Group The steps in this section define the SNADBUSERS group. SNADBUSERS is for users who execute the batch alert detection process. SNAUSER is an associated login to this group and the authentication domain is snaDbAuth.



To define the SNADBUSERS group, do the following:

1. Right‐click on User Manager. 2. Select New Group. 3. In the General tab, enter SNADBUSERS for the Name and Display Name (Figure 16).

Figure 16: SNADBUSERS Group: General



4. In the Members tab, select BI Web Services Users, SAS General Servers, snarun, and SAS Anonymous Web User (Figure 17).

Figure 17: SNADBUSERS Group: Members



5. Skip the Groups and Roles tab. 6. In the Accounts tab, select New (Figure 18). 7. Add the Oracle RDBMS login information (User ID and Password). 8. Specify the Authentication Domain: snaDbAuth.

Figure 18: SNADBUSERS Group: Accounts




Figure 19: SNADBUSERS Group: Authorization

5.1.6 Define SNADBREAD Group The steps in this section define the SNADBREAD group, which is for users who need read access to the alert, configuration, and core entity data. SNAREAD is an associated login to this group and the authentication domain is snaDbRead. All investigators need to be assigned to this group.



To define the SNADBREAD group, do the following:

1. Right‐click on User Manager. 2. Select New Group. 3. In the General tab, enter SNADBREAD for the Name and Display Name (Figure 20).

Figure 20: SNADBREAD Group: General



4. In the Members tab, select SASUSERS (Figure 21).

Figure 21: SNADBREAD Group: Members




Figure 22: SNADBREAD Group: Groups and Roles



6. In the Accounts tab, select New (Figure 23). 7. Add the Oracle RDBMS login information (User ID and Password). 8. Specify the Authentication Domain: snaDbRead.

Figure 23: SNADBREAD Group: New Login Properties




Figure 24: SNADBREAD Group: Authorization

5.1.7 Define SNACOREUSERS Group The steps in this section define the SNACOREUSERS group, which is for users who execute ETL processes to load the core entity data into the RDBMS SNACORE schema. SNACORE is an associated login to this group and the authentication domain is snaCoreAuth.



To define the SNACOREUSERS group, do the following:

1. Right‐click on User Manager. 2. Select New Group. 3. In the General tab, enter SNACOREUSERS for the Name and Display Name (Figure 25).

Figure 25: SNACOREUSERS Group: General



4. In the Members tab, select snarun (Figure 26).

Figure 26: SNACOREUSERS Group: Members



5. Skip the Groups and Roles tab. 6. In the Accounts tab, select New (Figure 27). 7. Add the Oracle RDBMS login information (User ID and Password). 8. Specify the Authentication Domain: snaCoreAuth.

Figure 27: SNACOREUSERS Group: Accounts




Figure 28: SNACOREUSERS Group: Authorization



5.1.8 Define Oracle Server The steps in this section define the Oracle server:

1. Right‐click on Server Manager. 2. Select New Server... and the New Server Wizard appears (Figure 29). 3. Select Oracle Server. 4. Select Next.

Figure 29: Define Oracle Server: New Server Wizard



5. Enter the Name of the Oracle server (Figure 30). 6. Select Next.

Figure 30: Define Oracle Server: Specify Server Name



7. Enter the following server properties (Figure 31): a. Major version number: 10 b. Minor version number: 2 c. Appropriate Software version number (for example, if 10.2.0.4 was installed on a Microsoft

Windows 2008 Server, then the Software Version Number is 4) d. Select the machine from the Associated Machine menu. Click New to register a new

machine if the machine hosting Oracle is not already registered in metadata. 8. Vendor and Associated Machine should already appear in the dialog box. 9. Select Next.

Figure 31: Define Oracle Server: Enter Server Properties



10. Enter the following connection properties (Figure 32): a. Path: ORACLE SID/Database name that contains the alert, configuration, and core entity

data b. Authentication type: User/Password c. Authentication domain: snaDbAuth (this authentication domain is associated with the

SNAUSER login) 11. Select Next.

Figure 32: Define Oracle Server: Enter Connection Properties



12. Review the summary information (Figure 33). 13. Select Finish.

Figure 33: Define Oracle Server: Server Creation

5.1.9 Modify Connection for Oracle Server The steps in this section modify the connection for the Oracle server defined in Section 5.1.8. This connection uses the snaDbAuth authentication domain.



To modify the connection for the Oracle server, do the following:

1. Select the Oracle Server defined in Section 5.1.8. 2. In the Connections tab (right pane), right‐click on the highlighted connection. 3. Select Properties and the General Properties display appears (Figure 34).

Figure 34: Modify Oracle Server Connection: General



4. Select the Authorization tab. 5. Select Add… (Figure 35). 6. Add SNACOREUSERS, SNADBREAD, and SNADBUSERS. 7. Select OK.

Figure 35: Modify Oracle Server Connection: Authorization

5.1.10 Define Second Connection for Oracle Server The steps in this section define a second connection for the Oracle server defined in Section 5.1.8. This connection uses the snaCoreAuth authentication domain and will be used to access the core entity data in the SNACORE schema.



To define a second connection for the Oracle server, do the following:

1. Right‐click on the Oracle Server defined in Section 5.1.8. 2. Select Add Connection… and the New Connection Wizard appears (Figure 36). 3. Enter the Name of the connection to the core schema. 4. Select Next.

Figure 36: Define Second Oracle Server Connection: New Connection Wizard



5. Enter the following connection properties (Figure 37): a. Path: ORACLE SID/Database name that contains the alert, configuration, and core entity

data b. Authentication type: User/Password c. Authentication domain: snaCoreAuth (this authentication domain is associated with the

SNACORE login) 6. Select Next.

Figure 37: Define Second Oracle Server Connection: Enter Connection Properties




Figure 38: Define Second Oracle Server Connection: Connection Creation



5.1.11 Define Oracle Library for Configuration Metadata Tables The steps in this section define the Oracle library for the configuration metadata tables:

1. Right‐click on Libraries (under the Data Library Manager). 2. Select New Library… and the New Library Wizard appears (Figure 39). 3. Select Oracle Library from the list of libraries. 4. Select Next.

Figure 39: Configuration Metadata Tables: Select Library Type



5. Enter the Name: DB_KC (Figure 40). 6. Select Browse…. 7. Using the folder navigation window, create the Location: /Products/SAS Social Network

Analysis/DB_KC. 8. Select Next.

Figure 40: Configuration Metadata Tables: Specify Library Details



9. From the list of Available servers, select SASApp (Figure 41). 10. Select Next.

Figure 41: Configuration Metadata Tables: Select SAS Servers



11. Enter the Libref: DB_KC (Figure 42). 12. Select Next.

Figure 42: Configuration Metadata Tables: Enter Library Properties



13. Enter the following server and connection information (Figure 43): a. Database Schema Name: SNAUSER. b. Default Login: SNAUSER.

14. Select Next.

Figure 43: Configuration Metadata Tables: Specify Server and Connection Information




Figure 44: Configuration Metadata Tables: Library Creation

5.1.12 Define DB_CORE Read Only Oracle Library for Core Entity Tables The steps in this section define the DB_CORE Oracle library for the core entity tables. The core entity tables are loaded by a custom ETL process. For more information pertaining to entities and core entity data, see the SNA Server Administration Guide.



To define the DB_CORE Oracle library for the core entity tables, do the following:

1. Right‐click on Libraries, select New Library… and the New Library Wizard appears (Figure 45). 2. From the list of libraries, select Oracle Library. 3. Select Next.

Figure 45: Core Entity Tables: Select Library Type



4. Enter the Name: DB_CORE (Figure 46). 5. Select Browse…. 6. Using the folder navigation window, create the Location: /Products/SAS Social Network

Analysis/DB_CORE. 7. Select Next.

Figure 46: Core Entity Tables: Specify Oracle Library Details




Figure 47: Core Entity Tables: Select SAS Servers (Optional)



10. Enter the Libref: DB_CORE (Figure 48). 11. Select Next.

Figure 48: Core Entity Tables: Enter Library Properties



12. Enter the following server and connection information (Figure 49): a. Database Schema Name: SNACORE b. Default Login: SNAUSER

13. Select Next.

Figure 49: Core Entity Tables: Data Server




Figure 50: Core Entity Tables: Library Creation



5.1.13 Define DBCORERW Read/Write Oracle Library for Core Entity Tables The steps in this section define the DBCORERW Oracle library for the core entity tables:

1. Right‐click on Libraries, select New Library… and the New Library Wizard appears (Figure 51). 2. From the list of libraries, select Oracle Library. 3. Select Next.

Figure 51: Core Entity Tables: Select Library Type



4. Enter the Name: DBCORERW (Figure 52). 5. Select Browse…. 6. Using the folder navigation window, create the Location: /Products/SAS Social Network

Analysis/DBCORERW. 7. Select Next.

Figure 52: Core Entity Tables: Specify Oracle Library Details




Figure 53: Core Entity Tables: Select SAS Servers (Optional)



10. Enter the Libref: DBCORERW (Figure 54). 11. Select Next.

Figure 54: Core Entity Tables: Enter Library Properties



12. Enter the following server and conncection information (Figure 55): a. Database Schema Name: SNACORE b. Default Login: SNACORE c. Connection Core: SNA Oracle RDMBS Server

13. Select Next.

Figure 55: Core Entity Tables: Specify Server and Connection Information




Figure 56: Core Entity Tables: Library Creation

5.2 MySQL Database

5.2.1 Database User Creation The SNA Server requires database users. Two users need to be created:

1. SNAUSER: Has read and write access to the database where alert detection configuration tables are loaded.

2. SNAREAD: Has read‐only access to the database where alert detection configuration tables are loaded.



There is an example script for creating users that the person creating the database users can modify, if appropriate.

• Sun Solaris: !SASROOT/misc/snamva/dbmsc/util/create_app_user_mysql.sql

• Microsoft Windows: !SASROOT\snamva\sasmisc\dbmsc\util\create_app_user_mysql.sql

The necessary modifications appear in Table 9.

Table 9: Script Modification (for MySQL)

Tag to be Modified Replacement Value for Tag

hostname Host from which the user can access the database; if the user needs to connect from multiple hosts, repeat the CREATE USER and SET PASSWORD statements

read/write dbuser password Password that SNAUSER specifies to authenticate to the database

database Name of the database that was created and configured (described in Section 3.6.3)

read only dbuser password Password that SNAREAD specifies to authenticate to the database

5.2.2 Apply DDL and Seed the Database Previously, the database and database users were created. When the SAS Deployment Wizard 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 either create or seed the database. If a seed file with SQL does not exist to populate the SAS Social Network Analysis Server database tables, perform one of the following two procedures. Choose the correct procedure based on the operating system of the SAS Social Network Analysis Server.

These procedures use the SAS installer user ID to run scripts. The scripts call the mysql command line utility. Before running any commands, make sure that the mysql command is in the path for the SAS installer user ID.

5.2.2.1 Sun Solaris Servers

1. Log on with the SAS installer user ID. 2. Copy !SASROOT/misc/snamva/dbmsc/util/sfs_util_load_mysql_template.sh to a

new file such as sfs_util_load_mysql_SNAALERT.sh. 3. Edit the copied file and replace the path to SNA RDBMS utility directory tag with the

fully qualified path to !SASROOT/misc/snamva/dbmsc/util/. 4. Replace the tags with values for the parameters shown in Table 10. 5. Make the script executable:

chmod 775 sfs_util_load_mysql_SNAALERT.sh

6. Execute the script: ./sfs_util_load_mysql_SNAALERT.sh



Table 10: sfs_util_load_mysql_template.sh Parameters

Parameter Value

database server The host name of the machine with MySQL server. The default value mentioned previously is SNAALERT.

database server port The port that MySQL is listening on. The default value is 3306.

database The name of the database.

database user The database user ID that has read and write privileges. Previous sections of this document suggest SNAUSER.

database user password Password for the database user ID.


Fully qualified path to !SASROOT/misc/snamva/dbmsc.


Fully qualified path to !SASROOT/misc/snamva/dbmsc/seed/seed_rdbms_mysql.sql

5.2.2.2 Microsoft Windows

1. Log on with the SAS installer user ID. 2. Copy !SASROOT\snamva\misc\dbmsc\util\sfs_load_mysql_template.bat to a new

file such as sfs_util_load_mysql_SNAALERT.bat. 3. Edit the copied file and replace the path to SNA RDBMS utility directory tag with the

fully qualified path to !SASROOT\snamva\misc\dbmsc\util\. Replace the tags with values for the parameters shown in Table 11.

4. Execute the script from the DOS command prompt: sfs_util_load_mysql_SNAALERT.bat

Note: For the script to execute successfully from a DOS command line, paths whose directories contain spaces need to be converted to shortened DOS directory names. Converting a Windows path with spaces requires taking the first six (6) characters of the Windows directory and then appending a tilde (~) and a number. If there is only one directory whose first characters are unique, the number will be 1. For example, the following Windows path:

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

would be converted to:

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

Table 11: sfs_util_load_mysql_template.bat Parameters

Parameter Value

database server Host name of the machine with MySQL server.

database server port Port that MySQL is listening on. The default value is 3306.




Parameter Value

database Name of the database.

database user Database user ID that has read and write privileges. Previous sections of this document suggest SNAUSER.

database user password Password for the database user ID.


Fully qualified path to !SASROOT\snamva\misc\dbmsc.


Fully qualified path to !SASROOT\snamva\misc\dbmsc\seed\seed_rdbms_mysql.sql

5.2.3 Define New Authentication Domains The steps in this section define new authentication domains for the MySQL database (Table 12). Authentication domains are added using the SAS Management Console. An authentication domain is a name that facilitates the matching of logins with the servers for which they are valid, which is important when users access certain secondary servers, such as a MySQL server.

Table 12: MySQL Authentication Domains

Domain Authorization Type Login ID Users

snaDbAuth Alert and configuration data library and core entity library

SNAUSER Users who execute the batch alert detection process

snaDbRead Read‐only access for specific users

SNAREAD Users who need read‐only access to the SNA metadata, such as investigators


To create the authentication domains, do the following within the SAS Management Console:

1. Right‐click on User Manager. 2. Select Authentication Domains…. 3. Select New. 4. Enter the Name: snaDbAuth. 5. Select OK. 6. Repeat Steps 3 through 5 for the Authentication domain snaDbRead. The final Authentication Domains display appears (Figure 57).

Figure 57: Authentication Domains Display

5.2.4 Define New Users The steps in this section define the users who execute the batch alert detection process and/or ETL processes. The example shown here defines a single application user with the user name snarun.



To define users, do the following:

1. Right‐click on User Manager. 2. Select New User (in this example, the user snarun is added). 3. In the General tab, enter snarun for the Name, Display Name, and Job Title (Figure 58).

Figure 58: New User: General




Figure 59: New User: Groups and Roles



5. In the Accounts tab, select New (Figure 60). 6. Add the operating system login information (User ID and Password). 7. Specify the Authentication Domain: DefaultAuth.

Figure 60: New User: Accounts

5.2.5 Define SNADBUSERS Group The steps in this section define the SNADBUSERS group. SNADBUSERS is for users who execute the batch alert detection process. SNAUSER is an associated login to this group and the authentication domain is snaDbAuth.



To define the SNADBUSERS group, do the following:

1. Right‐click on User Manager. 2. Select New Group. 3. In the General tab, enter SNADBUSERS for the Name and Display Name (Figure 61).

Figure 61: SNADBUSERS Group: General



4. In the Members tab, select BI Web Services Users, SAS General Servers, snarun, and SAS Anonymous Web User (Figure 62).

Figure 62: SNADBUSERS Group: Members



5. Skip the Groups and Roles tab. 6. In the Accounts tab, select New (Figure 63). 7. Add the MySQL RDBMS login information (User ID and Password). 8. Specify the Authentication Domain: snaDbAuth.

Figure 63: SNADBUSERS Group: Accounts



5.2.6 Define SNADBREAD Group The steps in this section define the SNADBREAD group, which is for users who need read access to the alert, configuration, and core entity data. SNAREAD is an associated login to this group and the authentication domain is snaDbRead. All investigators need to be assigned to this group.

To define the SNADBREAD group, do the following:

1. Right‐click on User Manager. 2. Select New Group. 3. In the General tab, enter SNADBREAD for the Name and Display Name (Figure 64).

Figure 64: SNADBREAD Group: General



4. In the Members tab, select SASUSERS (Figure 65).

Figure 65: SNADBREAD Group: Members




Figure 66: SNADBREAD Group: Groups and Roles



6. In the Accounts tab, select New (Figure 67). 7. Add the MySQL RDBMS login information (User ID and Password). 8. Specify the Authentication domain: snaDbRead.

Figure 67: SNADBREAD Group: New Login Properties



5.2.7 Define MySQL Server The steps in this section define the MySQL server:

1. Right‐click on Server Manager. 2. Select New Server... and the New Server Wizard appears (Figure 68). 3. Select MySQL Server. 4. Select Next.

Figure 68: Define MySQL Server: New Server Wizard



5. Enter the Name of the MySQL server (Figure 69). 6. Select Next.

Figure 69: Define MySQL Server: Specify Server Name



7. Enter the following server properties (Figure 70): a. Major version number: 5 b. Minor version number: 0 c. Appropriate Software version number (for example, if 5.0.84 was installed on a Microsoft

Windows 2008 Server, the Software Version Number will be 84). d. Select the machine from the Associated Machine menu. Click New to register a new

machine if the machine hosting MySQL is not already registered in metadata. 8. The Vendor and Associated Machine should already appear in the dialog box. 9. Select Next.

Figure 70: Define MySQL Server: Enter Server Properties



10. Enter the following connection properties (Figure 71): a. Name of the MySQL Database (SNAALERT in this example) b. MySQL Server: localhost c. Port: 3306 d. Authentication type: User/Password e. Authentication domain: snaDbAuth (this authentication domain is associated with the

SNAUSER login) 11. Select Next.

Figure 71: Define MySQL Server: Enter Connection Properties




Figure 72: Define MySQL Server: Server Creation



5.2.8 Add Attributes to MySQL Server The steps in this section add attributes to the MySQL server defined in Section 5.2.7:

1. Select the MySQL server defined in Section 5.2.7. 2. Right‐click on Properties. 3. Select the Extended Attributes tab (Figure 73). 4. Select New. 5. Enter the following server properties:

a. Field Name: MYSQL_PORT b. Value: 3306 c. Description: MySQL Database Port

Figure 73: MySQL Server: Extended Attributes



5.2.9 Define MySQL Library for Metadata Tables The steps in this section define the MySQL library for the metadata tables:

1. Right‐click on Libraries. 2. Select New Library… and the New Library Wizard appears (Figure 74). 3. From the list of libraries, select MySQL Library. 4. Select Next.

Figure 74: Metadata Tables: Select Library Type



5. Enter the Name: DB_KC (Figure 75). 6. Select Browse…. 7. Using the folder navigation window, create the Location: /Products/SAS Social Network

Analysis/DB_KC. 8. Select Next.

Figure 75: Metadata Tables: Specify Library Details




Figure 76: Metadata Tables: Select SAS Servers



11. Enter the Libref: DB_KC (Figure 77). 12. Select Next.

Figure 77: Metadata Tables: Enter Library Properties



13. Enter the Default Login: SNAUSER (Figure 78). 14. Select Next.

Figure 78: Metadata Tables: Specify Server and Connection Information




Figure 79: Metadata Tables: Library Creation

5.3 Create the SAS Data Mart Directories

5.3.1 Purpose SAS Social Network Analysis Server requires a series of directories to store the following types of information:

• Alert generation process configuration files

• Location for autocall macros

• SAS libraries for a data mart

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



5.3.2 Sun Solaris 10 Servers To create the SAS data mart directories on a Sun Solaris server, do the following:

1. Log on with the user ID that is used to execute the extract, transform, and load (ETL) and alert detection processes. In previous sections of this document, the suggested user ID is snarun.

2. Change directory to !SASROOT/misc/snamva/dbmsc/util/. 3. Create the data mart directories with the sfs_create_project_dirs.sh script:

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

Note: Ensure that the user who executes the ETL and alert detection processes has write permission on all of the directory paths.

-bash-3.00$ ./sfs_create_project_dirs.sh /data/sna/conf /data/sna/sas /data/sna/mart

Figure 80: Data Mart Directory Creation Example – Sun Solaris Server

The arguments specified in the 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

5.3.3 Microsoft Windows Servers To create the SAS data mart directories on a Microsoft Windows server, do the following:

1. Log on to the host where SAS Foundation and the SNA Server are installed. Enter the user ID that is used to execute the ETL and alert detection processes. In previous sections of this document, the referenced user ID is snarun.

2. Open a command prompt. 3. Change directory to !SASROOT\snamva\sasmisc\dbmsc\util\.



4. Create the data mart directories with the sfs_create_project_dirs.bat script: sfs_create_project_dirs.bat conf-dir sas-dir mart-dir

Files\SAS_9.2\SASFoundation\9.2\snamva\sasmisc\dbmsc\util>sfs_create_project_dirs.bat E:\data\sna\conf E:\data\sna\sas E:\data\sna\mart

Figure 81: Data Mart Directory Creation Example – Microsoft Windows Server

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

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



5.4 Define SAS Data Mart Libraries

5.4.1 Define SAS Library for Alert Detail Tables The steps in this section define the SAS library for the alert detail tables:

1. Right‐click on Libraries, select New Library… and the New Library Wizard appears (Figure 82). 2. From the list of libraries, select SAS BASE Library. 3. Select Next.

Figure 82: Alert Details Tables: Select Library Type



4. Enter the Name: SNA_ALDT (Figure 83). 5. Select Browse…. 6. Using the folder navigation window, create the Location: /Products/SAS Social Network

Analysis/SNA_ALDT. 7. Select Next.

Figure 83: Alert Details Tables: Specify SAS BASE Library Details




Figure 84: Alert Details Tables: Select SAS Servers (Optional)



10. Enter the Libref: SNA_ALDT (Figure 85). 11. Select the Engine: BASE. 12. Enter the correct Path Specification for the alert detail tables (Note: For the 2.1 release, this

location must be rooted off of the mart-dir directory that was created with the sfs_create_project_dirs script as mart-dir/alert_detail). Note: If prompted for a logon ID and password, enter sassrv.

13. Select Next.

Figure 85: Alert Details Tables: Enter Library Properties




Figure 86: Alert Details Tables: Library Creation



5.4.2 Define SAS Library for Alert Summary Tables The steps in this section define the SAS library for the alert summary tables:


Figure 87: Alert Summary Tables: Select Library Type



4. Enter the Name: SNA_ALSM (Figure 88). 5. Select Browse…. 6. Using the folder navigation window, create the Location: /Products/SAS Social Network

Analysis/SNA_ALSM. 7. Select Next.

Figure 88: Alert Summary Tables: Specify SAS BASE Library Details




Figure 89: Alert Summary Tables: Select SAS Servers (Optional)



10. Enter the Libref: SNA_ALSM (Figure 90). 11. Select the Engine: BASE. 12. Enter the correct Path Specification for the alert summary tables (Note: For the 2.1 release,

this location must be rooted off of the mart-dir directory that was created with the sfs_create_project_dirs script as mart-dir/alert_summary).

13. Select Next.

Figure 90: Alert Summary Tables: Enter Library Properties




Figure 91: Alert Summary Tables: Library Creation



5.4.3 Define SAS Library for Data Mart Tables The steps in this section define the SAS library for the data mart tables:


Figure 92: Data Mart Tables: Select Library Type



4. Enter the Name: SNA_DM (Figure 93). 5. Select Browse…. 6. Using the folder navigation window, create the Location: /Products/SAS Social Network

Analysis/SNA_DM. 7. Select Next.

Figure 93: Data Mart Tables: Specify SAS BASE Library Details




Figure 94: Data Mart Tables: Select SAS Servers (Optional)



10. Enter the Libref: SNA_DM (Figure 95). 11. Select the Engine: BASE. 12. Enter the correct Path Specification for the data mart tables (Note: For the 2.1 release, this

must be the mart-dir location that was specified to the sfs_create_project_dirs script. The scenario_code directory must be a subdirectory of the specified location.)

13. Select Next.

Figure 95: Data Mart Tables: Enter Library Properties




Figure 96: Data Mart Tables: Library Creation



5.4.4 Define SAS Library for SNA Network Link Tables The steps in this section define the SAS library for the SNA network link tables:


Figure 97: SNA Network Link Tables: Select Library Type



4. Enter the Name: SNA_LINK (Figure 98). 5. Select Browse…. 6. Using the folder navigation window, create the Location: /Products/SAS Social Network

Analysis/SNA_LINK. 7. Select Next.

Figure 98: SNA Network Link Tables: Specify SAS BASE Library




Figure 99: SNA Network Link Tables: Select SAS Servers (Optional)



10. Enter the Libref: SNA_LINK (Figure 100). 11. Select the Engine: BASE. 12. Enter the correct Path Specification for the SNA link tables (Note: For the 2.1 release, this

must live under the mart-dir directory that was created with the sfs_create_project_dirs script as mart-dir/network_links).

13. Select Next.

Figure 100: SNA Network Link Tables: Enter Library Properties




Figure 101: SNA Network Link Tables: Library Creation



5.4.5 Define SAS Library for SNA Network Node Tables The steps in this section define the SAS library for the SNA network node tables:

1. Right‐click on Libraries, select New Library…. The New Library Wizard appears (Figure 102). 2. From the list of libraries, select SAS BASE Library. 3. Select Next.

Figure 102: SNA Network Node Tables: Select Library Type



4. Enter the Name: SNA_NODE (Figure 103). 5. Select Browse…. 6. Using the folder navigation window, create the Location: /Products/SAS Social Network

Analysis/SNA_NODE. 7. Select Next.

Figure 103: SNA Network Node Tables: Specify SAS BASE Library Details




Figure 104: SNA Network Node Tables: Select SAS Servers (Optional)



10. Enter the Libref: SNA_NODE (Figure 105). 11. Select the Engine: BASE. 12. Enter the correct Path Specification for the SNA node tables (Note: For the 2.1 release, this

must live under the mart-dir directory that was created with the sfs_create_project_dirs script as mart-dir/network_nodes).

13. Select Next.

Figure 105: SNA Network Node Tables: Enter Library Properties




Figure 106: SNA Network Node Tables: Library Creation



5.4.6 Define SAS Library for Alert Detection Input Tables The steps in this section define the SAS library for the prep / input data tables for alert detection:

1. Right‐click on Libraries and select New Library…. The New Library Wizard appears (Figure 107). 2. From the list of libraries, select SAS BASE Library. 3. Select Next.

Figure 107: Alert Detection: Select Library Type



4. Enter the Name: SNA_PD (Figure 108). 5. Select Browse…. 6. Using the folder navigation window, create the Location: /Products/SAS Social Network

Analysis/SNA_PD. 7. Select Next.

Figure 108: Alert Detection: Specify SAS BASE Library Details




Figure 109: Alert Detection: Select SAS Servers (Optional)



10. Enter the Libref: SNA_PD (Figure 110). 11. Select the Engine: BASE. 12. Enter the correct Path Specification for the prep data tables (Note: For the 2.1 release, this

must live under the mart-dir directory that was created with the sfs_create_project_dirs script as mart-dir/prep_data).

13. Select Next.

Figure 110: Alert Detection: Enter Library Properties



14. Review the summary information (Figure 111). 15. Select Finish. 16. After this library is populated with tables, those tables need to be registered in the SAS

Metadata Repository. a. Right‐click on the library and select Register Tables. b. Add all the tables that need to appear in the administrative client.

Figure 111: Alert Detection: Library Creation

5.5 Modify SAS to Load the SAS Social Network Analysis Server Autoexec The SAS Social Network Analysis Server uses several macros and macro variables. The steps in this section describe the location of, and how to modify, the autoexec file that SAS provides with SAS Social Network Analysis server. It also describes how to reference the autoexec file so that all the SAS sessions on the machine have access to the macros and macro variables.



5.5.1 Modify the Autoexec 1. Locate the autoexec.sas file:

a. Sun Solaris: !SASROOT/misc/snamva/autoexec.sas b. Microsoft Windows: !SASROOT\snamva\sasmisc\autoexec.sas

2. Within the autoexec file, edit the parameters shown in Table 13.

Table 13: Autoexec File Parameters

Parameter Value

db_server_name Provides the metadata name of the database server. Previous sections of this document used sample values, such as SNA Oracle RDBMS Server and SNA MySQL RDBMS Server. Enclose the value in the %str() function. For example, if the name of the RDBMS server in the SAS Management Console is SNA MySQL RDBMS Server, then this parameter should be specified as %str(SNA MySQL RDBMS Server).

db_trans_lib Provides the metadata library name for the library that is used for configuration and alerts. Previous sections of this document identified the DB_KC library for this purpose.

db_core_lib For deployments that use MySQL, remove this parameter. For deployments that use Oracle, provide the metadata library name for the library that is used to store core data. The Oracle configuration section of this document provided a sample name of DB_CORE.

sas_dm_lib Provides the metadata library name for the SAS data mart library. Previous sections of this document provided a sample name of SNA_DM. The path for this location does not need to be specified in the autoexec. The path is retrieved from the SAS Metadata Server.

sas_path Identifies the path to the sasautos directory that was created with the sfs_create_project_dirs script as described in section "Create the SAS Data Mart Directories" on page 91. Specify the second parameter, such as E:\data\sna\sas.

conf_path Identifies the path to the agp directory that was created with the sfs_create_project_dirs script as described in section "Create the SAS Data Mart Directories" on page 91. Specify the first parameter, such as E:\data\sna\conf.

3. Modify the SAS configuration file to load the autoexec file.

a. Sun Solaris: Edit !SASROOT/sasv9_local.cfg and add lines shown in Figure 112. Note: For the metadata-server-host-name, specify the fully qualified host name. If the metadata server is listening on a different port than the default port, change it to the correct value. b. Microsoft Windows: Edit !SASROOT\nls\locale\sasv9.cfg and add the lines shown in

Figure 113 (insert them between the warning messages, as shown in Figure 114).



Note: For the metadata-server-host-name, specify the fully qualified host name. If the metadata server is listening on a different port than the default port, change it to the correct value.

-metaserver "metadata-server-host-name"

-metaport 8561

-metarepository "Foundation"

-insert sasautos !SASROOT/ucmacros/snamva -autoexec "!SASROOT/misc/snamva/autoexec.sas"

Figure 112: Modified SAS Configuration File – Sun Solaris


-metaport 8561


-sasautos (SASAUTOS "!SASROOT\snamva\ucmacros")

-autoexec "!SASROOT\snamva\sasmisc\autoexec.sas"

Figure 113: Code to Insert

/*---------------------------------------------------------------\

| WARNING: INSTALL Application edits below this line. User |

| options should be added above this box comment. |

| INSTALL Application maintains and modifies the |

| following options; -SASAUTOS, -SASHELP, -SASMSG, |

| -PATH, and -MAPS. It also maintains and modifies |

| the following CONFIG variables with the -SET option; |

| INSTALL, USAGE, LIBRARY, SAMPSIO, SAMPSRC, SASCBT, |

| and SASEXT01-SASEXT50. It preserves all lines above |

| the line containing 'DO NOT EDIT BELOW THIS LINE'. |

\---------------------------------------------------------------*/


-metaport 8561


-sasautos (SASAUTOS "!SASROOT\snamva\ucmacros")

-autoexec "!SASROOT\snamva\sasmisc\autoexec.sas"

/* DO NOT EDIT BELOW THIS LINE - INSTALL Application edits below */

Figure 114: Modified SAS Configuration File ‐ Microsoft Windows



5.6 Verify Access to the Libraries and Tables At this point in the installation and configuration process, the RDBMS server has been configured with the tables that are needed by SAS Social Network Analysis Server. Metadata libraries are configured to access the tables. The next step is to start SAS and verify access to the tables. Verifying access to the tables confirms that the database server and tables are configured correctly in metadata and that the SAS Social Network Analysis Server autoexec is loaded correctly.

To verify table access, do the following:

1. Log on to the machine that is hosting SAS Social Network Analysis Server. 2. Start SAS with the -metauser and -metapass options: sas -metauser snarun

-metapass password. 3. Confirm that the macro variables are available to the SAS session by issuing the following %PUT

statement: %put SFS_TRANS_DATABASE=&SFS_TRANS_DATABASE;

Note: If the autoexec is configured correctly, the SAS log indicates a value such as SNAALERT.

5.7 Load the Entity Tables and Job Calendar Entities are used in the alert generation process for aggregating alerts. Therefore, they must be loaded into database tables before projects and scenarios can be added to the system for the 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 and FSK_ENTITY_RELATION tables. The same macro seeds the FSK_JOB_CALENDAR table.

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/agp directory 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

Note: Examples of these files exist in the following locations: Sun Solaris: !SASROOT/misc/snamva/dbmsc/seed/fsk_entity_level_info_import.csv !SASROOT/misc/snamva/dbmsc/seed/fsk_entity_relation_import.csv

Microsoft Windows: !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 backend alert detection process. For example,

if the user ID is snarun, start SAS with the following command: sas -metauser snarun -metapass password

3. Run the macro: %sfs_util_seed_agp_metadata;



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

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

5. Confirm that FSK_JOB_CALENDAR is populated with data.

5.7.1 Fields in FSK_JOB_CALENDAR Updated by %SFS_UTIL_SEED_AGP_METADATA The fields in FSK_JOB_CALENDAR that require updates appear in Table 14.

Table 14: FSK_JOB_CALENDAR Fields

Field Value Description

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

DAILY_RUNDATE_IND Y or N Indicates whether the alert generation process and daily scenario(s) should execute for a given calendar date. A value of Y indicates that the alert generation process should be executed on the given calendar date and the daily scenario(s) should be executed for the same date. Since the alert generation process must be scheduled in order for any scenario to be executed, it is required to set the DAILY_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 need to be executed, then WEEKLY_RUNDATE_IND must also be set to Y.

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

STATUS_IND Y or N Indicates if that particular date has completely executed (Y).

BUSINESS_DAY_COUNT Numeric, ‐1 = do not include

A BUSINESS_DAY_COUNT of (–1) indicates that the alert generation process should not run on this date and is used to differentiate between business and physical calendar days. This relationship is used to create the SAS formats NUM_TO_DATE and DATE_TO_NUM and is used in most scenarios as well as in the replication process.

Note: The combination of RUNDATE_IND=Y and STATUS_IND=N dictates the next valid run date.



Regularly scheduled monthly and weekly jobs (such as weekly jobs scheduled every second Monday) may be updated programmatically for FSK_JOB_CALENDAR by running a program modeled after the job control code in install.sas.

Non‐recurring updates may be made via FSEDIT, VIEWTABLE, SQL, and DATA step.

5.7.2 Calendar Layout The alert generation calendar consists of a sequence of days and additional attributes that enable users to specify when the alert generation process should execute. Table 15 explains each field.

Table 15: 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 code generation; Valid values are Y and N

WEEKLY_RUNDATE_IND Indicates whether the day is a weekly run date and is used for scenario code generation; valid values are Y and N

MONTHLY_RUNDATE_IND Indicates whether the day is a monthly run date and is used for scenario code generation; valid values are Y and N

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

BUSINESS_DAY_COUNT Numeric indicator that distinguishes between business and physical days; valid values are -1 or any sequentially increasing positive integer

5.7.3 Create Templates Used by the Alert Generation Process Start SAS with the user ID that is used to run the backend alert detection process. For example, if the user ID is snarun, start SAS with the following command:

sas -metauser snarun -metapass password

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

Sun Solaris: !SASROOT/misc/snamva/dbmsc/ddl/create_templates_sas.sas

Microsoft Windows: !SASROOT/snamva/sasmisc/dbmsc/ddl/create_templates_sas.sas 2. For Oracle installations only, load the following SAS program into the program editor and

submit it: Sun Solaris: !SASROOT/misc/snamva/dbmsc/ddl/create_templates_orcl.sas



Microsoft Windows: !SASROOT/snamva/sasmisc/dbmsc/ddl/create_templates_orcl.sas

5.8 Import SAS Stored Processes and Deploy Web Services The investigator user interface shows alerts that are generated by the alert generation process. For alert viewing, SAS Stored Processes are deployed as Web Services, and the investigator user interface displays the alerts that are read by the SAS Stored Processes.

5.8.1 Import SAS Stored Processes from a SAS Package SAS provides template SAS Stored Process metadata in a SAS package file. Follow the steps below to import a template SAS package:

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

2. Right‐click on the Social Network Analysis 2.1 folder and select Import SAS Package from the resulting dropdown menu (Figure 115).

Figure 115: Import SAS Package

3. Select the Browse button and navigate to the location of the installed SPK file:

Sun Solaris: !SASROOT/misc/snamva/Template.spk Microsoft Windows: !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 getAlertTransactions, select the icon. Note: Deselect the Include source code check box for each of the stored processes (Figure 116). The stored process code is not imported with the package because it is already installed in the SAS installation directory. The location is identified later in this procedure.

Figure 116: 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 select

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

a. Sun Solaris: !SASROOT/sasstp/snamva/ b. Microsoft Windows: !SASROOT\snamva\sasstp

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



10. Review the Summary page and select Next. 11. Confirm that the import process completed successfully and then select Finish.

5.8.2 Deploy the Imported SAS Stored Processes as a Web Service After the SAS package file is imported, metadata is associated with the SAS program code for the stored process in the SAS installation directory. That code can be modified at any time to configure the display of alerts on the investigator user interface. However, they can be deployed as a Web service now, even though the SAS program code can be customized later.

1. Use the Folders tab of SAS Management Console to navigate to the folder that was just imported to the /System/Applications/SAS Social Network Analysis/Social Network Analysis 2.1 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. Some of the stored processes respond with XML streams to the investigator user interface. These stored processes must have the Schema URI set for the responses that use XML streams. The XML Schema (XSD) files are installed with the SAS software in the following location: a. Sun Solaris: !SASROOT/misc/snamva/xml/ b. Microsoft Windows: !SASROOT\snamva\sasmisc\xml\

For each of the stored processes identified in Table 16, perform the following steps:

1. Select the stored process icon, right‐click and select Properties. 2. Select the Data tab. 3. For each of the Targets listed in Table 16, perform the following steps:

a. Select the label value, such as response, and then select Edit. The Modify Data Target dialog box opens.

b. Edit the Schema URI field. Start the value with the file:// protocol, the path to the XML directory containing the XSD files, followed by the name of the XSD file. See Figure 117 for an example. Note: The Schema URI is the location of the XSD file on the machine where the mid‐tier is installed. If the mid‐tier is installed on a separate machine than the SAS Foundation, the XSD files need to be copied from the directory listed above to the machine where the mid‐tier is installed.

Table 16: Stored Processes

Stored Process Name Target Label on the Data Tab

Schema URI

getActionableEntities Response file://d:\data\...\getActionableEntities.xsd

getSocialNetwork respN file://d:\data\...\getSocialNetworkNodes.xsd

respL file://d:\data\...\getSocialNetworkLinks.xsd

respG file://d:\data\...\getSocialNetworkGroups.xsd

Cmodel file://d:\data\...\getScoringModel.xsd




Stored Process Name Target Label on the Data Tab

Schema URI

getSubAlerts Response file://d:\data\...\getActionableEntities.xsd

growSocialNetworkNode respN file://d:\data\...\getSocialNetworkNodes.xsd

respL file://d:\data\...\getSocialNetworkLinks.xsd

respG file://d:\data\...\getSocialNetworkGroups.xsd

For Solaris installations, the Schema URI is a value like file:///data/.../getActionableEntities.xsd.

Figure 117: Modify Data Target: Schema URI


4. After each of the stored processes in Table 16 has the Schema URI set, deploy the alerts‐related Web service. Hold down the CTRL key and click to select the following stored process icons: a. getActionableEntities b. getAlertTransactions c. getChartSeries d. getSubAlerts e. processAlertResponse

5. Right‐click one of the selected icons and select Deploy As Web Service. The Deploy As Web Service wizard starts.

6. On the Web Service Information page, confirm the following: a. Select the default value for Web Service Maker URL from the dropdown list. b. New Web Service Name must be set to the value of FolderNameAlerts. For example, if

the folder is named Healthcare, then the New Web Service Name must be HealthcareAlerts.

c. The choice of credentials to use does not matter. d. Select Next.

7. On the Web Service Keywords and Namespace page, provide the following value for the Namespace field: http://sas.com/sso/fraud/alerts

8. Select Next. 9. Confirm the settings and then select Finish. 10. Similar to the method for deploying the alerts‐related Web service, the Social Network‐related

Web service is deployed. Hold down the CTRL key and click to select the following stored process icons: a. getSocialNetwork b. getSocialNetworkNodeDetails c. growSocialNetworkNode

11. Right‐click one of the selected icons and select Deploy As Web Service. The Deploy As Web Service Wizard starts.

12. On the Web Service Information page, confirm the following: a. Use the default value for Web Service Maker URL. b. New Web Service Name must be set to the value of

FolderNameSocialNetworkAnalysis. For example, if the folder is named Healthcare, then the New Web Service Name must be HealthcareSocialNetworkAnalysis.

c. The choice of credentials to use does not matter. d. Select Next.

13. On the Web Service Keywords and Namespace page, provide the following value for the Namespace field: http://sas.com/sso/fraud/sna

14. Select Next. 15. Confirm the settings and then select Finish.


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

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


If the deployment completes successfully, two new Web services (FolderAlerts and FolderSocialNetworkAnalysis) are listed at:

http://WebApplicationServerHostName:8080/SASBIWS

5.8.3 Add Stored Process Server Invocation Options Stored process server invocation options need to be added to allow the stored process server to access the SNA Server SAS macros, SAS data libraries, and RDBMS libraries. To alter the Store Process Server invocation options, edit the /sasv9_usermods.cfg file underneath the StoredProcessServer directory, which is underneath the application server directory associated with Social Network Analysis SAS deployment. For example, the location of the sasv9_usermods.cfg file on a Microsoft Windows server this directory might be the following:

C:\SAS\Config\Lev1\SASApp\StoredProcessServer\sasv9_usermods.cfg file

1. Open the sasv9_usermods.cfg file in an editor. 2. Add the following invocation options to this file, based on the operating system on which SAS

Foundation is installed: a. Sun Solaris: -insert sasautos !SASROOT/ucmacros/snamva -autoexec "!SASROOT/misc/snamva/autoexec.sas"

b. Microsoft Windows: -sasautos (SASAUTOS "!SASROOT\snamva\ucmacros") -autoexec "!SASROOT\snamva\sasmisc\autoexec.sas"

5.9 Initialize Users and Groups The administrator who manages users and groups should refer to the SNA Server Administration Guide for instructions on establishing an administrator’s profile that can be used to log on and to initialize users and groups.

5.9.1 Add an Administrator Group and Administrators Access to the administrative 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 the SAS Management Console to create a group named SNA Administrators. When creating the group, select the Groups and Roles tab and add this group as a member of SNADBUSERS so that administrators have read and write access to the database.

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

3. Right‐click the folder icon and select Properties. 4. Select the Authorization tab and then select Add. The Add Users and Groups dialog box opens. 5. Select SNA Administrators from the list, select the right‐arrow icon, and select OK. The Add

Users and Groups dialog box closes. 6. Select SNA Administrators that has just been added to the Users and Groups list.


http://webapplicationserverhostname:8080/SASBIWS


7. In the Effective Permissions area, select the WriteMetadata check box and select OK. 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 of the SNA Administrators group.

5.9.2 Add an Investigator Group and Investigators Investigators have access to the investigator user interface to view alerts. Access to the investigator user interface is controlled with explicit ReadMetadata permission on a metadata folder. A metadata folder is created when a SAS package file (.SPK file) is imported into metadata. The metadata folder contains SAS Stored Processes that read the alerts generated by the alert generation process and display the alerts in the investigator user interface. Users can be added and removed from an investigator group at any time.

1. Use the User Manager plug‐in to the SAS Management Console to create a group for the investigators. The group can be named according to the type of activity that the group investigates, or perhaps by geographical location. For example, create a group named Healthcare Investigators. When creating the group, select the Groups and Roles tab and add this group as a member of SNADBREAD so that investigators have read access to the database.

2. Click the Folders tab and navigate to /System/Applications/SAS Social Network Analysis/Social Network Analysis 2.1/Folder. For example, the folder might be named Healthcare.

3. Right‐click the folder icon and select Properties. 4. Select the Authorization tab and select Add. The Add Users and Groups dialog box opens. 5. Select the group name (Healthcare Investigators) from the list, select the right‐arrow icon, and

select OK. The Add Users and Groups dialog box closes. 6. Select the group that has just been added to the Users and Groups list. 7. In the Effective Permissions area, confirm that the ReadMetadata check box is enabled with a

white background. Select 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 of the investigative group.

Investigative users can also be members of the administrative group. Investigative users can also belong to more than one investigative group. For example, an investigator can be a member of a group that investigates check fraud and a member of a group that investigates wire fraud. However, do not nest groups.

5.10 Synchronize Users and Groups After users, administrators, and groups are added to metadata, the information must be propagated to tables in the database. SAS provides the %SFS_UTIL_SYNCH_USERS macro to perform this function. Whenever users, administrators, group membership, or group privilege on a metadata folder are changed, run this macro by doing the following:

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




2. Start SAS with a metadata account that has write privileges to the database. From previous instructions in this document, this requirement is met by any account that is a member of the SNADBUSERS metadata group: sas -metauser userID -metapass password

3. Run the macro: %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;

Your Turn

We welcome your feedback.

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

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

SAS® Publishing Delivers!Whether you are new to the work force or an experienced professional, you need to distinguish yourself in this rapidly changing and competitive job market. SAS® Publishing provides you with a wide range of resources to help you set yourself apart. Visit us online at support.sas.com/bookstore.

SAS® Press Need to learn the basics? Struggling with a programming problem? You’ll find the expert answers that you need in example-rich books from SAS Press. Written by experienced SAS professionals from around the world, SAS Press books deliver real-world insights on a broad range of topics for all skill levels.

s u p p o r t . s a s . c o m / s a s p r e s sSAS® Documentation To successfully implement applications using SAS software, companies in every industry and on every continent all turn to the one source for accurate, timely, and reliable information: SAS documentation. We currently produce the following types of reference documentation to improve your work experience:

• Onlinehelpthatisbuiltintothesoftware.• Tutorialsthatareintegratedintotheproduct.• ReferencedocumentationdeliveredinHTMLandPDF– free on the Web. • Hard-copybooks.

s u p p o r t . s a s . c o m / p u b l i s h i n gSAS® Publishing News Subscribe to SAS Publishing News to receive up-to-date information about all new SAS titles, author podcasts, and new Web site features via e-mail. Complete instructions on how to subscribe, as well as access to past issues, are available at our Web site.

s u p p o r t . s a s . c o m / s p n

SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. Otherbrandandproductnamesaretrademarksoftheirrespectivecompanies.©2009SASInstituteInc.Allrightsreserved.518177_1US.0109

http://support.sas.com/saspress

http://support.sas.com/publishing

http://support.sas.com/spn

sas social network analysis server 2support.sas.com/documentation/onlinedoc/socialnetwork... ·...

Documents