Leveraging the SAS Open Metadata Architecture Ray Helm & Yolanda Howard, University of Kansas, Lawrence, KS
|
|
- Arline Snow
- 8 years ago
- Views:
Transcription
1 Paper AD Leveraging the SAS Open Metadata Architecture Ray Helm & Yolanda Howard, University of Kansas, Lawrence, KS Abstract In the SAS Enterprise BI and Data Integration environments, the SAS Metadata Model contains a wealth of information about system configuration, data objects, report metadata, users, groups, and security authorizations. The ability to query the metadata adds a powerful tool to the SAS inventory and can be used for a wide range of purposes including surfacing metadata related to the data delivered to end users, adding relevant information to metadata objects, and performing bulk alterations to the metadata itself. This paper will provide an overview of the key tools for leveraging the Open Metadata Architecture including: the PROC METDATA procedure, the Metadata Browser utility, and the SAS XML Mapper. We will present examples of how we have employed these tools for bulk modifications of stored processes/application server associations and for generating a Data Elements Dictionary for use by our Data Warehouse consumers. Introduction The SAS Metadata Server is a crucial component of the SAS Enterprise BI Server, Enterprise Data Integration Server, and many of the industry specific solutions offered by SAS. The SAS metadata holds virtually all of the critical information including: system architecture; user authentication and authorization; data storage locations and table structure. The SAS Open Metadata Architecture provides the capacity to extract this information into reports or other data systems, generate reports on specific aspects of the system (such as user authorizations), and integrate the metadata with data from other enterprise systems to create a comprehensive view of the relationship between the business intelligence data and ERP data. Additionally, the Open Metadata Architecture allows metadata to be updated programmatically. This can be a powerful tool for the system administrator. Routine tasks can be automated, and large, complex administrative operations can be performed in a structured manner with minimal risk of errors due to operator oversight. This paper will provide two examples that take advantage of the SAS Open Metadata Architecture. The first example demonstrates a system administration task performed programmatically as part of a system migration. The second shows how the metadata from an Enterprise Data Integration system can be combined with metadata from the source ERP systems to provide a comprehensive Data Elements Dictionary. Useful Tools There are a few useful tools for working with the SAS Open Metadata Interface. The Metadata Browser feature of the SAS Foundation software is essential for visualizing the metadata objects, identifying attributes and associations, and finding specific objects of interest. Our methods rely heavily on the PROC METADATA procedure which sends requests and receives responses using XML. The SAS XML Mapper is extremely useful in generating XML map files and SAS code for reading the XML response files into SAS data sets. It should be noted that it is also possible to perform the operations described here using SAS DATA step functions which do not require any XML knowledge or tools. Using the Open Metadata Architecture in System Administration As part of our migration from a SAS Business Intelligence Platform to SAS 9.2, we were also upgrading our hardware architecture from a two server (one mid-tier and a combined metadata/application server) to a three server design. In order to employ the SAS Migration Utility, the first step required a migration from the two server architecture to an identical two server environment. This created a 9.2 system with a single server running both the Metadata Server and Application Server (SASMain) components. The installation and configuration of the new Application Server (SASApp) was independent of the migration. Rather than manually reassign over 150 stored processes from the old SASMain Application Server to the new SASApp Application Server, the SAS Open Metadata Interface tools were used to identify the stored processes in the metadata and reassign them to the new application server. Additionally, the directory metadata objects that stored the paths of the SAS programs executed by the stored processes were also reassigned to SASApp (the actual program files were moved manually). While this saved us quite a bit of tedious work reassigning stored processes to servers using the SAS Management Console, more importantly, it retained the associations between the stored processes and their links in the Information Delivery Portal. Exporting the stored processes from one application server and importing them into the other would have broken the association between the portal content and the stored process, requiring these associations to be rebuilt manually. 1
2 For the purposes of this paper, this migration scenario was recreated on a test Enterprise BI Server installation on a Windows workstation with a metadata instance containing just a few stored processes all linked to a single application server (SASApp1). A second application server (SASApp2) was also installed on the same workstation. Figure 1 shows the Metadata Browser view of the stored processes associated with the SASApp1 Logical Stored Process Server. The Financials_STP_1 stored process has been expanded to show the ComputeLocations association and displays the attributes and associations pane for the SP Source Directory. The directory shows that the physical location of the SAS program associated with the stored process is also under the SASApp1 installation directory. Figure 1. A Metadata Browser view of the SASApp1 - Logical Stored Process Server showing the stored processes under the ComputeTasks and the Attributes and Associations of the "SP Source Directory" Directory for the Financials_STP_1 stored process Identifying Metadata to be Updated Before you can perform any updates on a metadata object, the unique identifier of the object must be obtained. In this case, the metadata identity of all stored processes associated with the SASApp1 - Logical Stored Process Server need to be determined. One method for obtaining this is to create an XML input file with the appropriate request syntax and submit this using the PROC METADATA procedure. The XML below returns the Id and Name attributes for all ClassifierMaps (stored processes are ClassifierMap metadata objects) associated with the SASApp1 Logical Stored Process Server: <GetMetadataObjects> <Reposid>$METAREPOSITORY</Reposid> <Type>LogicalServer</Type> <Objects/> <NS>SAS</NS> <!-- set Flags for OMI_XMLSELECT(128)+OMI_GET_METADATA(256)+OMI_TEMPLATE(4) --> <Flags>388</Flags> <Options> <XMLSELECT search="*[@name='sasapp1 - Logical Stored Process Server']" /> <Templates> <LogicalServer Id="" Name="" > <ComputeTasks /> </LogicalServer > <ComputeTasks > <ClassifierMap /> </ComputeTasks > <ClassifierMap Id="" Name="" /> </Templates> </Options> </GetMetadataObjects> The above XML was saved to C:\sasfiles\SASApp_STPSvr_Request.xml and sent to the metadata server as shown here: 2
3 /* Set Metadata Connectiion */ options metaserver="mymetaserver" metaport=8563 metaprotocol=bridge metauser="mrhelm" metapass="*****" metarepository="foundation"; /* GetMetadataObject request file */ filename request C:\sasfiles\SASApp_STPSvr_Request.xml lrecl=1024; /* Metadata response output file */ filename response "C:\sasfiles\SASApp_STPSvr_Response.xml" lrecl=1024; proc metadata in=request out=response; run; This generates an XML file, "C:\sasfiles\SASApp_STPSvr_Response.xml" containing the results of the GetMetadataObjects query. Loading the XML Response File into SAS The next step is to convert the XML response into a SAS data set for use in constructing a set of instructions to update the metadata. The SAS XML Mapper software makes short work of constructing the necessary SAS code to read the response XML data into SAS data sets. All that needs to be done is to open the XML response file and use the Automap using XML tool to generate an XML Map. Then save the XML Map file. Once this is complete, go to the SAS Code Example tab and uncheck all of the Show options except for Copy to WORK and either save the code as a separate SAS program or copy and paste it into the SAS Program Editor. The code generated will create SAS data sets based on the response XML in the session WORK library: /******************************************************************************** * Generated by XML Mapper, _v920 ********************************************************************************/ /* * Environment */ filename SASApp 'C:\sasfiles\SASApp_STPSvr_Response.xml'; filename SXLEMAP 'C:\sasfiles\SASApp_STPSrv.map'; libname SASApp xml xmlmap=sxlemap access=readonly; /* * Local Extraction */ DATA GetMetadataObjects; SET SASApp.GetMetadataObjects; run; DATA Objects; SET SASApp.Objects; run; DATA LogicalServer; SET SASApp.LogicalServer; run; DATA ComputeTasks; SET SASApp.ComputeTasks; run; DATA ClassifierMap; SET SASApp.ClassifierMap; run; DATA Options; SET SASApp.Options; run; DATA XMLSELECT; SET SASApp.XMLSELECT; run; DATA Templates; SET SASApp.Templates; run; DATA LogicalServer1; SET SASApp1S.LogicalServer1; run; DATA ComputeTasks1; SET SASApp1S.ComputeTasks1; run; DATA ClassifierMap1; SET SASApp1S.ClassifierMap1; run; Building and submitting the UpdateMetadata request The data set ClassifierMap contains the necessary metadata information (specifically, the metadata Id) to build metadata update statements to re-associate each stored process to the SASApp2 Logical Stored Process Server. 3
4 Figure 2. The ClassifierMap Data Set The following code uses the ClassifierMap data set to build an UpdateMetadata XML file which is then submitted using the PROC METADATA procedure. The ObjRef and Name values for the SASApp2 Logical Stored Process Server were obtained using the Copy URI to Clipboard and Copy features of the Metadata Browser tool: filename InReq "C:\sasfiles\UpdateClassifierMaps.xml" lrecl=1024; data _null_; set ClassifierMap END=OVER; file InReq; if _n_=1 then put '<Multiple_Requests>' / '<UpdateMetadata >' / ' <Metadata >'; put ' <ClassifierMap Id="' Id '" >' / ' <ComputeLocations Function="Replace"> ' / ' <LogicalServer ObjRef="A50Z1M48.AT00000B" Name="SASApp2 - Logical Stored Process Server" /> ' / ' </ComputeLocations >' / ' </ClassifierMap > '; if Over then put ' </Metadata >' / ' <Reposid >$METAREPOSITORY</Reposid >'/ ' <NS>SAS</NS>' / ' <!-- OMI_TRUSTED_CLIENT ( ) OMI_RETURN_LIST (1024) -->'/ ' <Flags> </Flags>' / ' <Options /> '/ '</UpdateMetadata >' '</Multiple_Requests >' ; run; filename result "C:\sasfiles\UpdateClassifierMaps_result.xml" lrecl=1024; proc metadata in=inreq out=result; run; Figure 3 shows the stored processes associated to the SASApp2 Logical Stored Process Server after the PROC METADATA execution. Note that the directory location of the SP Source Directory still points to the SASApp1 Application Server installation path and is still associated with the SASApp1 server. At this point, the stored processes have one foot in the SASApp2 server and one in SASApp1 and execution would be problematic. Another set of metadata queries and updates is necessary to fully disassociate the stored processes from the SASApp1 Application Server. 4
5 Figure 3. A Metadata Browser view of the SASApp2 - Logical Stored Process Server with the newly associated stored processes Updating the Stored Process Source Code Directory Metadata Updating the server and directory for each of the stored process source directories follows the same basic steps that were used in updating the server associations. An XML file is created containing a GetMetadataObjects request to retrieve the metadata Id of all Directory objects having a Name attribute of SP Source Directory. In addition to the Id, the DirectoryName attribute is also requested as this is the physical path on the application server where the SAS code resides: <GetMetadataObjects> <Reposid>$METAREPOSITORY</Reposid> <Type>Directory</Type> <Objects/> <NS>SAS</NS> <!-- OMI_XMLSELECT(128)+OMI_GET_METADATA(256)+OMI_TEMPLATE(4) --> <Flags>388</Flags> <Options> <XMLSELECT search="*[@name='sp Source Directory']" /> <Templates> <Directory Id="" Name="" DirectoryName="" /> </Templates> </Options> </GetMetadataObjects> This XML file is submitted using the PROC METADATA procedure in the same fashion as previously described to obtain an XML response file from the metadata server. The methods for converting the XML response into a SAS data set using the SAS XML Mapper are also the same as those used for identifying the stored processes and will not be described in detail here. The end result of the process is a SAS data set WORK.DIRECTORY containing the Id, Name, and DirectoryName for each of the stored process directories (Figure 4). Figure 4. The Directory Data Set Using the data contained in WORK.DIRECTORY, the following code can be submitted to build an UpdateMetadata request which changes the server association for the directories to SASApp2 and alters the physical path in the DirectoryName attribute to the appropriate path for the SASApp2 installation path: filename InReq2 C:\sasfiles\UpdateSTPDirectories.xml" lrecl=1024; 5
6 data _null_; set Directory END=OVER; /* Modify DirectoryName to point to...\ebi_appserver2\lev1\sasapp2\... */ IF INDEX(DIRECTORYNAME,'EBI_AppServer1') gt 0 THEN DO; DirectoryName=TRANWRD(DirectoryName, 'EBI_AppServer1', 'EBI_AppServer2'); DirectoryName=TRANWRD(DirectoryName, 'SASApp1', 'SASApp2'); END; file InReq2; if _n_=1 then put '<Multiple_Requests>' / '<UpdateMetadata >' / ' <Metadata >'; put '<Directory Id="' Id '" ' 'Name="' Name '" ' 'DirectoryName="' DirectoryName '" >' / ' <DeployedComponents Function="Replace"> ' / ' <ServerContext ObjRef="A50Z1M48.AQ000003" Name="SASApp2" /> ' / ' </DeployedComponents >' / ' </Directory > '; if Over then put ' </Metadata >' / ' <Reposid >$METAREPOSITORY</Reposid >'/ ' <NS>SAS</NS>' / ' <!-- OMI_TRUSTED_CLIENT ( ) OMI_RETURN_LIST (1024) -->'/ ' <Flags> </Flags>' / ' <Options /> '/ '</UpdateMetadata >' '</Multiple_Requests >' ; run; After submitting the generated file, UpdateSTPDirectories.xml, via PROC METADATA, the source directories for the stored processes are now associated with the SASApp2 application server with an appropriate physical path defined (Figure 5). The process is now complete and the stored processes are ready for executing using the new application server. Figure 5. Metadata Browser view of Stored Processes associated with SASApp2 - Logical Stored Process Server with correct "SP Source Directory" locations. 6
7 Data Elements Dictionary (DED) A Practical Example Our data warehouse is comprised of elements from various enterprise systems across campus. Primarily, the data is built from PeopleSoft/Oracle tables and documentation is sparse. Table/ field definitions and relationships between source data and data warehouse tables can be tedious to document and difficult to maintain. Our goal is to have Business Analysts/Subject Matter Experts provide business logic and definitions for source tables and fields while developers add metadata as they create new target objects. Using the SAS Open Metadata Interface we extract and combine this metadata to create a robust data dictionary. Step 1 - Create XML File: The following code creates an XML file that queries the metadata using the GetMetadataObjects method. In this step, we are returning all metadata objects with a type of PhysicalTable. We then further specify the associations we would like to see returned in the XML hierarchy by identifying the templates to use. These include: Columns, Documents, Trees, TablePackage, and ResponsibleParties. FILENAME TBLREQ 'U:\ETL 9.2\YDH_TABLEQRY.QXML'; FILENAME TBLRESP "U:\ETL 9.2\DITABLES_&SYSDATE..XML" LRECL=1024; DATA _NULL_; FILE TBLREQ; INFILE CARDS4; LENGTH LONG $256; INPUT; LONG=_INFILE_; PUT LONG ' '; CARDS4; <GETMETADATAOBJECTS> <REPOSID>$METAREPOSITORY</REPOSID> <TYPE>PHYSICALTABLE</TYPE> <OBJECTS/> <NS>SAS</NS> <FLAGS>388</FLAGS><!-OMI_XMLSELECT(128)+OMI_GET_METADATA(256)+OMI_TEMPLATE(4) --> <OPTIONS> <TEMPLATES> <PHYSICALTABLE ID="" COLUMNNAME="" DESC="" DBMSTYPE="" NUMROWS=""> <COLUMNS/> <DOCUMENTS/> <TREES/> <TABLEPACKAGE/> <RESPONSIBLEPARTIES/> </PHYSICALTABLE> <COLUMN ID="" NAME="" COLUMNLENGTH="" SASFORMAT=""SASINFORMAT=""/> <DOCUMENT ID = "" NAME="" > <NOTES/> </DOCUMENT> <NOTE NAME=""> <TEXTSTORE/> </NOTE> <TEXTSTORE NAME="" STOREDTEXT="" /> <TREE ID="" NAME=""> <PARENTTREE ID="" NAME="" /> </TREE> <DATABASESCHEMA ID="" NAME="" SCHEMANAME=""> <USEDBYPACKAGES/> </DATABASESCHEMA> <SASLIBRARY ID="" NAME=""/> <RESPONSIBLEPARTY ID="" NAME="" ROLE=""> <PERSONS/> </RESPONSIBLEPARTY> <PERSON ID="" DISPLAYNAME="" /> </TEMPLATES> </OPTIONS> </GETMETADATAOBJECTS>;;;; RUN; 7
8 PROC METADATA IN=TBLREQ OUT=TBLRESP; RUN; Step 2 - Build XML Map: Using SAS XMLMapper, we open the XML file created in the previous step and create a map to read the results into SAS datasets. Navigating through the XML hierarchy is straightforward and this tool allows us to browse the object then drag and drop to create custom data sets. Figure 6.a below illustrates how we ve mapped the PhysicalTable metadata object along with its related associations and attributes into our core tables. Figure 6.b shows the resulting XMLMap. Figure 6.a: A custom map DI_TABLES is created that will create in the following tables: PhysicalTable, TablePackage, TableNotes, Documents, Column and ResponsibleParties. 8
9 Figure 6.b: A portion of the XMLMap generated by SAS XMLMapper We then bring the XML data into SAS datasets using the XML engine in a libname statement with the following: FILENAME DI_TBL 'U:\ETL 9.2\DI_TABLE.MAP'; LIBNAME TBLRESP XML XMLMAP=DI_TBL ACCESS=READONLY; Step 3 - Create DED Tables: The following data step creates one of the core dictionary tables. DATA DITABLES; LENGTH FOLDERPATH $200; SET TBLRESP.PHYSICALTABLE; FOLDERPATH=CATX( /,TABLETREENAME1,TABLETREENAME2,TABLETREENAME3,TABLETREENAME4); DROP TABLETREENAME:; RUN; Figure 7: A sample of PhysicalTable metadata Each step above is repeated for the core sections of our data dictionary and run routinely to keep the dictionary current. 9
10 Putting It All Together Using Microsoft Access as a user interface, the Data Elements Dictionary (or DED) becomes an interactive tool for both end users and developers. Tables are organized into subject areas that have their own data steward and data warehouse manager (developer). Figure 8: Data warehouse subject areas For each target table, we maintain description, data steward, fields, table type, data library, and schema information. Each column (field) is displayed along with its source information and description. We also are able to link into our 3 rd party job scheduling tables to display information about the job that created and/or updated the table. 10
11 Figure 9: Table data elements defined At the field level, we maintain the business logic (or definition), data type and format, and the source (tablename.fieldname). We can quickly determine what the impact will be if the structure of a single field is changed in an underlying source system. An extremely useful feature of the DED is that end users are also able to mass update the business logic for fields that appear in multiple tables. Figure 10: Field definitions In Data Integration Studio 4.21, developers add standardized notes and attributes to each table and job they create. We extract that metadata and are able to produce a report of each job. Another very useful piece of information is 11
12 the Process Flow Diagram created in DI Studio. The diagram can can be saved as an image file and then brought into an Access table with an attachement field. The image can then be accessed in an Access report. This allows end users to quickly see how a particiular table in the data warehouse was created. Figure 11: Data Integration Studio Job Summary Report Using the FeatureMap metadata object we are able to document the job flow and identify the source/target tables. The FeatureMap outlines each source (FeatureSource) and target (FeatureTarget). Figure 12: FeatureMap Metdata Object Using the Metadata URI as a key in our DED allows us to map a single column to its FeatureMap and then we can determine the source. In many cases there is a work table in between so we extract the WorkTable type objects as well. This allows us to drill through to the primary source. Figure 13 below show the final source to target mapping table using the FeatureMaps. 12
13 Figure 13: Mapping of Source/Target Tables Figure 14: Data Integration Studio Detailed Table Report Keeping the Metadata in Sync The DED tables in Microsoft Access are linked to Oracle tables in our warehouse. As end users update the business logic in the DED, the Oracles tables are directly updated. This information is then pushed back into the metadata using XML and the UpdateMetadata method. This keeps the DED and the SAS metadata in sync. We use PROC SQL to determine which metadata object definitions do not match and create a work table with the object URI (in the following example, this is the field TABLEID): PROC SQL; CREATE TABLE MISSING_DESC AS ( SELECT A.FOLDERPATH, A.TABLEID, A.NAME, A.DESC, A.SCHEMANAME, B.TABLE_DESCR, HTMLENCODE(B.TABLE_DESCR,'AMP LT GT APOS QUOT') AS NEWDESCR FROM DITABLES_NEW A, DED_TABLES B WHERE (A.TABLEID = B. TABLEID AND(A.DESC <> B.TABLE_DESCR)); QUIT; Note: We use HTMLENCODE to return the encoded string in order to handle special characters correctly in the XML. The work table is then used in the following code to process the metadata update: FILENAME TDESREQ 'U:\ETL 9.2\YDH_TABLEDESCR.QXML'; FILENAME TDESRESP "U:\ETL 9.2\TABLEDESCR&SYSDATE..XML" LRECL=1024; DATA _NULL_; SET MISSING_DESC END=OVER; FILE TDESREQ; 13
14 IF _N_=1 THEN PUT '<MULTIPLE_REQUESTS>' / '<UPDATEMETADATA >' / ' <METADATA >'; PUT ' <PHYSICALTABLE ID="' TABLEID '" ' / ' DESC ="' NEWDESCR '" />' /; IF OVER THEN PUT ' </METADATA >' / ' <REPOSID >$METAREPOSITORY</REPOSID >'/ ' <NS>SAS</NS>' / ' <!-- OMI_TRUSTED_CLIENT ( ) OMI_RETURN_LIST (1024) -->'/ ' <FLAGS> </FLAGS>' / ' <OPTIONS /> '/ '</UPDATEMETADATA >' '</MULTIPLE_REQUESTS >' ; RUN; PROC METADATA IN=TDESREQ OUT=TDESRESP; RUN; Conclusion Exploring the SAS Open Metadata Architecture can be daunting but it certainly provides an abundance of useful information. Using tools like the SAS Metadata Browser, SAS XML Mapper and PROC Metadata to both read and write the metadata allows us to fully take advantage of this information. These tools will be critical as we delve further into the metadata and continue to explore ways to automate and document our work. References SAS 9.2 Open Metadata Interface Reference and Usage. SAS Institute Inc SAS Institute Inc. 2009, SAS 9.2 Metadata Model: Reference Recommended Reading SAS Institute Inc. 2010, SAS 9.2 XML LIBNAME Engine: User s Guide, Second Edition. Cary, NC: SAS Institute Inc. SAS Institute Inc. 2009, SAS 9.2 Language Interfaces to Metadata. Cary, NC: SAS Institute Inc. Contact Information Your comments and questions are valued and encouraged. Contact the authors at: Ray Helm The University of Kansas Office of Institutional Research and Planning 1246 W. Campus Rd., Room 339 (785) ray-helm@ku.edu Yolanda Howard The University of Kansas Office of Institutional Research and Planning 1246 W. Campus Rd, Room 339 (785) yolanda-howard@ku.edu 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 trademarks of their respective companies. 14
Dynamic Decision-Making Web Services Using SAS Stored Processes and SAS Business Rules Manager
Paper SAS1787-2015 Dynamic Decision-Making Web Services Using SAS Stored Processes and SAS Business Rules Manager Chris Upton and Lori Small, SAS Institute Inc. ABSTRACT With the latest release of SAS
More informationTechnical Paper. Defining an ODBC Library in SAS 9.2 Management Console Using Microsoft Windows NT Authentication
Technical Paper Defining an ODBC Library in SAS 9.2 Management Console Using Microsoft Windows NT Authentication Release Information Content Version: 1.0 October 2015. Trademarks and Patents SAS Institute
More informationAdministration & Support
Getting from SAS 9.1.3 to SAS 9.2: Migration Tools or Promotion Tools Diane Hatcher and Sandy McNeill, SAS Institute Inc., Cary, NC ABSTRACT If you are running a metadata server in your SAS 9.1.3 environment,
More informationLost in Space? Methodology for a Guided Drill-Through Analysis Out of the Wormhole
Paper BB-01 Lost in Space? Methodology for a Guided Drill-Through Analysis Out of the Wormhole ABSTRACT Stephen Overton, Overton Technologies, LLC, Raleigh, NC Business information can be consumed many
More informationAn email macro: Exploring metadata EG and user credentials in Linux to automate email notifications Jason Baucom, Ateb Inc.
SESUG 2012 Paper CT-02 An email macro: Exploring metadata EG and user credentials in Linux to automate email notifications Jason Baucom, Ateb Inc., Raleigh, NC ABSTRACT Enterprise Guide (EG) provides useful
More informationRelease 2.1 of SAS Add-In for Microsoft Office Bringing Microsoft PowerPoint into the Mix ABSTRACT INTRODUCTION Data Access
Release 2.1 of SAS Add-In for Microsoft Office Bringing Microsoft PowerPoint into the Mix Jennifer Clegg, SAS Institute Inc., Cary, NC Eric Hill, SAS Institute Inc., Cary, NC ABSTRACT Release 2.1 of SAS
More informationTU04. Best practices for implementing a BI strategy with SAS Mike Vanderlinden, COMSYS IT Partners, Portage, MI
TU04 Best practices for implementing a BI strategy with SAS Mike Vanderlinden, COMSYS IT Partners, Portage, MI ABSTRACT Implementing a Business Intelligence strategy can be a daunting and challenging task.
More informationDefine ODBC Database Library using Management Console
Define ODBC Database Library using Management Console Introduction: Open database connectivity (ODBC) standards provide a common interface to a variety of databases, including AS/400, dbase, Microsoft
More informationWhat's New in SAS Data Management
Paper SAS034-2014 What's New in SAS Data Management Nancy Rausch, SAS Institute Inc., Cary, NC; Mike Frost, SAS Institute Inc., Cary, NC, Mike Ames, SAS Institute Inc., Cary ABSTRACT The latest releases
More informationABSTRACT INTRODUCTION ACCESS VIA SAS INTEGRATION TECHNOLOGIES WHY USE SAS WITH SAS INTEGRATION TECHNOLOGIES? Paper BI10-2012
Paper BI10-2012 SAS Enterprise Guide Moving Beyond Your Initial Startup Donald L Penix Jr. (D.J.) Pinnacle Solutions, Inc., Indianapolis, IN Roger D. Muller, Ph.D., First Phase Consulting, Carmel, IN ABSTRACT
More informationJet Data Manager 2012 User Guide
Jet Data Manager 2012 User Guide Welcome This documentation provides descriptions of the concepts and features of the Jet Data Manager and how to use with them. With the Jet Data Manager you can transform
More informationReal-Time Market Monitoring using SAS BI Tools
Paper 1835-2014 Real-Time Market Monitoring using SAS BI Tools Amol Deshmukh, CA ISO Corporation, Folsom Jeff McDonald, CA ISO Corporation, Folsom Abstract The Department of Market Monitoring at California
More informationExploiting Key Answers from Your Data Warehouse Using SAS Enterprise Reporter Software
Exploiting Key Answers from Your Data Warehouse Using SAS Enterprise Reporter Software Donna Torrence, SAS Institute Inc., Cary, North Carolina Juli Staub Perry, SAS Institute Inc., Cary, North Carolina
More informationSAS Business Data Network 3.1
SAS Business Data Network 3.1 User s Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2014. SAS Business Data Network 3.1: User's Guide. Cary,
More informationThe Recipe for Sarbanes-Oxley Compliance using Microsoft s SharePoint 2010 platform
The Recipe for Sarbanes-Oxley Compliance using Microsoft s SharePoint 2010 platform Technical Discussion David Churchill CEO DraftPoint Inc. The information contained in this document represents the current
More informationManaging Qualtrics Survey Distributions and Response Data with SAS
Paper 3399-2015 Managing Qualtrics Survey Distributions and Response Data with SAS ABSTRACT Faith E Parsons, Sean J Mota and Yan Quan Center for Behavioral Cardiovascular Health, Columbia University Medical
More informationSAS 9.3 Open Metadata Interface: Reference and Usage
SAS 9.3 Open Metadata Interface: Reference and Usage SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2011. SAS 9.3 Open Metadata Interface: Reference
More informationUsing SAS BI Web Services and PROC SOAP in a Service-Oriented Architecture Dan Jahn, SAS, Cary, NC
Paper 310-2008 Using SAS BI Web Services and PROC SOAP in a Service-Oriented Architecture Dan Jahn, SAS, Cary, NC ABSTRACT Many businesses are just starting to use a service-oriented architecture (SOA).
More information9.1 SAS/ACCESS. Interface to SAP BW. User s Guide
SAS/ACCESS 9.1 Interface to SAP BW User s Guide The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2004. SAS/ACCESS 9.1 Interface to SAP BW: User s Guide. Cary, NC: SAS
More informationER/Studio 8.0 New Features Guide
ER/Studio 8.0 New Features Guide Copyright 1994-2008 Embarcadero Technologies, Inc. Embarcadero Technologies, Inc. 100 California Street, 12th Floor San Francisco, CA 94111 U.S.A. All rights reserved.
More informationOnDemand for Academics
SAS OnDemand for Academics User s Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2015. SAS OnDemand for Academics: User's Guide. Cary, NC:
More informationConfiguring Apache HTTP Server as a Reverse Proxy Server for SAS 9.3 Web Applications Deployed on Oracle WebLogic Server
Configuration Guide Configuring Apache HTTP Server as a Reverse Proxy Server for SAS 9.3 Web Applications Deployed on Oracle WebLogic Server This document describes how to configure Apache HTTP Server
More informationSAS IT Resource Management 3.2
SAS IT Resource Management 3.2 Reporting Guide Second Edition SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc 2011. SAS IT Resource Management 3.2:
More informationWHAT IS THE CONFIGURATION TROUBLESHOOTER?
Paper BI-003 Best Practices for SAS Business Intelligence Administrators: Using the Configuration Troubleshooter to Keep SAS Solutions and SAS BI Applications Running Smoothly Tanya Kalich, SAS Institute
More informationForms Printer User Guide
Forms Printer User Guide Version 10.51 for Dynamics GP 10 Forms Printer Build Version: 10.51.102 System Requirements Microsoft Dynamics GP 10 SP2 or greater Microsoft SQL Server 2005 or Higher Reporting
More informationSAS 9.3 Intelligence Platform
SAS 9.3 Intelligence Platform Application Server Administration Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc 2011. SAS SAS 9.3 Intelligence
More informationER/Studio Enterprise Portal 1.0.2 User Guide
ER/Studio Enterprise Portal 1.0.2 User Guide Copyright 1994-2008 Embarcadero Technologies, Inc. Embarcadero Technologies, Inc. 100 California Street, 12th Floor San Francisco, CA 94111 U.S.A. All rights
More informationSAS 9.4 Intelligence Platform: Migration Guide, Second Edition
SAS 9.4 Intelligence Platform: Migration Guide, Second Edition SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2015. SAS 9.4 Intelligence Platform:
More informationCross platform Migration of SAS BI Environment: Tips and Tricks
ABSTRACT Cross platform Migration of SAS BI Environment: Tips and Tricks Amol Deshmukh, California ISO Corporation, Folsom, CA As a part of organization wide initiative to replace Solaris based UNIX servers
More informationCDW DATA QUALITY INITIATIVE
Loading Metadata to the IRS Compliance Data Warehouse (CDW) Website: From Spreadsheet to Database Using SAS Macros and PROC SQL Robin Rappaport, IRS Office of Research, Washington, DC Jeff Butler, IRS
More informationSAS University Edition: Installation Guide for Windows
SAS University Edition: Installation Guide for Windows i 17 June 2014 The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2015. SAS University Edition: Installation Guide
More informationSAS 9.4 Intelligence Platform
SAS 9.4 Intelligence Platform Application Server Administration Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2013. SAS 9.4 Intelligence Platform:
More informationSecurity Development Tool for Microsoft Dynamics AX 2012 WHITEPAPER
Security Development Tool for Microsoft Dynamics AX 2012 WHITEPAPER Junction Solutions documentation 2012 All material contained in this documentation is proprietary and confidential to Junction Solutions,
More informationMigrating MSDE to Microsoft SQL 2008 R2 Express
How To Updated: 11/11/2011 2011 Shelby Systems, Inc. All Rights Reserved Other brand and product names are trademarks or registered trademarks of the respective holders. If you are still on MSDE 2000,
More informationBooks-by-Users Web Development with SAS by Example (Third Edition) Frederick E. Pratter
Books-by-Users Web Development with SAS by Example (Third Edition) Frederick E. Pratter Click Tom to Kari, edit Master Statistics subtitle style 07/06/12 Come out of the desert of ignorance to the OASUS
More informationSAS Credit Scoring for Banking 4.3
SAS Credit Scoring for Banking 4.3 Hot Fix 1 SAS Banking Intelligence Solutions ii SAS Credit Scoring for Banking 4.3: Hot Fix 1 The correct bibliographic citation for this manual is as follows: SAS Institute
More informationSOLARWINDS ORION. Patch Manager Evaluation Guide for ConfigMgr 2012
SOLARWINDS ORION Patch Manager Evaluation Guide for ConfigMgr 2012 About SolarWinds SolarWinds, Inc. develops and markets an array of network management, monitoring, and discovery tools to meet the diverse
More informationSAS 9.3 Foundation for Microsoft Windows
Software License Renewal Instructions SAS 9.3 Foundation for Microsoft Windows Note: In this document, references to Microsoft Windows or Windows include Microsoft Windows for x64. SAS software is licensed
More informationScheduling in SAS 9.3
Scheduling in SAS 9.3 SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc 2011. Scheduling in SAS 9.3. Cary, NC: SAS Institute Inc. Scheduling in SAS 9.3
More informationImplementing a SAS Metadata Server Configuration for Use with SAS Enterprise Guide
Implementing a SAS Metadata Server Configuration for Use with SAS Enterprise Guide Step 1: Setting Up Required Users and Groups o Windows Operating Systems Only Step 2: Installing Software Using the SAS
More informationAutomate Data Integration Processes for Pharmaceutical Data Warehouse
Paper AD01 Automate Data Integration Processes for Pharmaceutical Data Warehouse Sandy Lei, Johnson & Johnson Pharmaceutical Research and Development, L.L.C, Titusville, NJ Kwang-Shi Shu, Johnson & Johnson
More informationIS466 Decision Support Systems. SQL Server Business Intelligence Development Studio 2008 User Guide
IS466 Decision Support Systems Instructor: Dr. Mourad Ykhlef Lecturer: Yazeed Alabdulkarim SQL Server Business Intelligence Development Studio 2008 User Guide Yazeed Alabdulkarim Revised by: Dr. Mourad
More informationAdam Rauch Partner, LabKey Software adam@labkey.com. Extending LabKey Server Part 1: Retrieving and Presenting Data
Adam Rauch Partner, LabKey Software adam@labkey.com Extending LabKey Server Part 1: Retrieving and Presenting Data Extending LabKey Server LabKey Server is a large system that combines an extensive set
More informationConfiguring Apache HTTP Server as a Reverse Proxy Server for SAS 9.2 Web Applications Deployed on BEA WebLogic Server 9.2
Configuration Guide Configuring Apache HTTP Server as a Reverse Proxy Server for SAS 9.2 Web Applications Deployed on BEA WebLogic Server 9.2 This document describes how to configure Apache HTTP Server
More informationTake a Whirlwind Tour Around SAS 9.2 Justin Choy, SAS Institute Inc., Cary, NC
Take a Whirlwind Tour Around SAS 9.2 Justin Choy, SAS Institute Inc., Cary, NC ABSTRACT The term productivity can mean a number of different things and can be realized in a number of different ways. The
More informationSage Intelligence Financial Reporting for Sage ERP X3 Version 6.5 Installation Guide
Sage Intelligence Financial Reporting for Sage ERP X3 Version 6.5 Installation Guide Table of Contents TABLE OF CONTENTS... 3 1.0 INTRODUCTION... 1 1.1 HOW TO USE THIS GUIDE... 1 1.2 TOPIC SUMMARY...
More informationInstall SQL Server 2014 Express Edition
How To Install SQL Server 2014 Express Edition Updated: 2/4/2016 2016 Shelby Systems, Inc. All Rights Reserved Other brand and product names are trademarks or registered trademarks of the respective holders.
More informationUsing SAS Enterprise Business Intelligence to Automate a Manual Process: A Case Study Erik S. Larsen, Independent Consultant, Charleston, SC
Using SAS Enterprise Business Intelligence to Automate a Manual Process: A Case Study Erik S. Larsen, Independent Consultant, Charleston, SC Abstract: Often times while on a client site as a SAS consultant,
More informationSetting Up ALERE with Client/Server Data
Setting Up ALERE with Client/Server Data TIW Technology, Inc. November 2014 ALERE is a registered trademark of TIW Technology, Inc. The following are registered trademarks or trademarks: FoxPro, SQL Server,
More informationODBC Client Driver Help. 2015 Kepware, Inc.
2015 Kepware, Inc. 2 Table of Contents Table of Contents 2 4 Overview 4 External Dependencies 4 Driver Setup 5 Data Source Settings 5 Data Source Setup 6 Data Source Access Methods 13 Fixed Table 14 Table
More informationICE for Eclipse. Release 9.0.1
ICE for Eclipse Release 9.0.1 Disclaimer This document is for informational purposes only and is subject to change without notice. This document and its contents, including the viewpoints, dates and functional
More informationDefine an Oracle Library in SAS Management Console
Define an Oracle Library in SAS Management Console This paper describes how to define an Oracle library in SAS Management Console. By following these steps, you can access your Oracle library from Business
More informationSAS BI Course Content; Introduction to DWH / BI Concepts
SAS BI Course Content; Introduction to DWH / BI Concepts SAS Web Report Studio 4.2 SAS EG 4.2 SAS Information Delivery Portal 4.2 SAS Data Integration Studio 4.2 SAS BI Dashboard 4.2 SAS Management Console
More informationData Discovery & Documentation PROCEDURE
Data Discovery & Documentation PROCEDURE Document Version: 1.0 Date of Issue: June 28, 2013 Table of Contents 1. Introduction... 3 1.1 Purpose... 3 1.2 Scope... 3 2. Option 1: Current Process No metadata
More informationCurtis Mack Curtis.Mack@lgan.com Looking Glass Analytics www.lgan.com
Curtis Mack Curtis.Mack@lgan.com Looking Glass Analytics www.lgan.com Weather Charting Graphing Geocoding Mapping Large Selection of other sites Your SAS Applications Infinite Possibilities on your own
More informationScheduling in SAS 9.4 Second Edition
Scheduling in SAS 9.4 Second Edition SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2015. Scheduling in SAS 9.4, Second Edition. Cary, NC: SAS Institute
More informationmetaengine DataConnect For SharePoint 2007 Configuration Guide
metaengine DataConnect For SharePoint 2007 Configuration Guide metaengine DataConnect for SharePoint 2007 Configuration Guide (2.4) Page 1 Contents Introduction... 5 Installation and deployment... 6 Installation...
More informationABSTRACT THE ISSUE AT HAND THE RECIPE FOR BUILDING THE SYSTEM THE TEAM REQUIREMENTS. Paper DM09-2012
Paper DM09-2012 A Basic Recipe for Building a Campaign Management System from Scratch: How Base SAS, SQL Server and Access can Blend Together Tera Olson, Aimia Proprietary Loyalty U.S. Inc., Minneapolis,
More informationSTEP 2: UNIX FILESYSTEMS AND SECURITY
Paper RIV-04 7 Steps to a SAS EBI Proof of Concept Project Sheryl Weise, Wells Fargo Bank ABSTRACT The Purchasing Department is considering contracting with your team for a new SAS Enterprise Business
More informationTechTips. Connecting Xcelsius Dashboards to External Data Sources using: Web Services (Dynamic Web Query)
TechTips Connecting Xcelsius Dashboards to External Data Sources using: Web Services (Dynamic Web Query) A step-by-step guide to connecting Xcelsius Enterprise XE dashboards to company databases using
More informationSAS Task Manager 2.2. User s Guide. SAS Documentation
SAS Task Manager 2.2 User s Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2015. SAS Task Manager 2.2: User's Guide. Cary, NC: SAS Institute
More informationConnectivity Pack for Microsoft Guide
HP Vertica Analytic Database Software Version: 7.0.x Document Release Date: 2/20/2015 Legal Notices Warranty The only warranties for HP products and services are set forth in the express warranty statements
More informationSAS 9.1. ETL Studio: User s Guide
SAS 9.1 ETL Studio: User s Guide The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2004. SAS 9.1 ETL Studio: User s Guide. Cary, NC: SAS Institute Inc. SAS 9.1 ETL Studio:
More informationSAS 9.3 Intelligence Platform
SAS 9.3 Intelligence Platform System Administration Guide Second Edition SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2012. SAS 9.3 Intelligence
More informationibolt V3.2 Release Notes
ibolt V3.2 Release Notes Welcome to ibolt V3.2, which has been designed to deliver an easy-touse, flexible, and cost-effective business integration solution. This document highlights the new and enhanced
More informationUltimus and Microsoft Active Directory
Ultimus and Microsoft Active Directory May 2004 Ultimus, Incorporated 15200 Weston Parkway, Suite 106 Cary, North Carolina 27513 Phone: (919) 678-0900 Fax: (919) 678-0901 E-mail: documents@ultimus.com
More informationETL-03 Using SAS Enterprise ETL Server to Build a Data Warehouse: Focus on Student Enrollment Data ABSTRACT WHO WE ARE MISSION PURPOSE BACKGROUND
ETL-03 Using SAS Enterprise ETL Server to Build a Data Warehouse: Focus on Student Enrollment Data Evangeline Collado, University of Central Florida, Orlando, FL M. Paige Borden, University of Central
More informationSQL Server Integration Services with Oracle Database 10g
SQL Server Integration Services with Oracle Database 10g SQL Server Technical Article Published: May 2008 Applies To: SQL Server Summary: Microsoft SQL Server (both 32-bit and 64-bit) offers best-of breed
More informationAdministration Quick Start
www.novell.com/documentation Administration Quick Start ZENworks 11 Support Pack 3 February 2014 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of
More informationImproving Your Relationship with SAS Enterprise Guide
Paper BI06-2013 Improving Your Relationship with SAS Enterprise Guide Jennifer Bjurstrom, SAS Institute Inc. ABSTRACT SAS Enterprise Guide has proven to be a very beneficial tool for both novice and experienced
More informationHow To Take Advantage Of Active Directory Support In Groupwise 2014
White Paper Collaboration Taking Advantage of Active Directory Support in GroupWise 2014 Flexibility and interoperability have always been hallmarks for Novell. That s why it should be no surprise that
More informationAuthor: Ryan J Adams. Overview. Central Management Server. Security. Advantages
Author: Ryan J Adams Overview In this paper we will look at Central Management Server and how it can help you manage a disperse environment. We will look at the requirements for setting up a CMS, the advantages
More informationSAP 3D Visual Enterprise Rapid-Deployment Solution
SAP 3D Visual Enterprise 8.0 July 2014 English SAP 3D Visual Enterprise Rapid-Deployment Solution SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany Copyright 2014 SAP AG or an SAP affiliate company.
More informationInstallation Guide. . All right reserved. For more information about Specops Inventory and other Specops products, visit www.specopssoft.
. All right reserved. For more information about Specops Inventory and other Specops products, visit www.specopssoft.com Copyright and Trademarks Specops Inventory is a trademark owned by Specops Software.
More informationSage ERP Accpac 6.0A. Installation and System Administrator's Guide
Sage ERP Accpac 6.0A Installation and System Administrator's Guide 2010 Sage Software, Inc. All rights reserved. Sage, the Sage logos, and all Sage ERP Accpac product and service names mentioned herein
More informationSAS Marketing Automation 5.1. User s Guide
SAS Marketing Automation 5.1 User s Guide The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2007. SAS Marketing Automation 5.1: User s Guide. Cary, NC: SAS Institute
More informationFast and Easy Delivery of Data Mining Insights to Reporting Systems
Fast and Easy Delivery of Data Mining Insights to Reporting Systems Ruben Pulido, Christoph Sieb rpulido@de.ibm.com, christoph.sieb@de.ibm.com Abstract: During the last decade data mining and predictive
More informationPerceptive Intelligent Capture Solution Configration Manager
Perceptive Intelligent Capture Solution Configration Manager Installation and Setup Guide Version: 1.0.x Written by: Product Knowledge, R&D Date: February 2016 2015 Lexmark International Technology, S.A.
More informationImplementing a Data Warehouse with Microsoft SQL Server 2012 MOC 10777
Implementing a Data Warehouse with Microsoft SQL Server 2012 MOC 10777 Course Outline Module 1: Introduction to Data Warehousing This module provides an introduction to the key components of a data warehousing
More informationReporting MDM Data Attribute Inconsistencies for the Enterprise Using DataFlux
Reporting MDM Data Attribute Inconsistencies for the Enterprise Using DataFlux Ernesto Roco, Hyundai Capital America (HCA), Irvine, CA ABSTRACT The purpose of this paper is to demonstrate how we use DataFlux
More informationUser's Guide. ControlPoint. Change Manager (Advanced Copy) SharePoint Migration. v. 4.0
User's Guide ControlPoint Change Manager (Advanced Copy) SharePoint Migration v. 4.0 Last Updated 7 August 2013 i Contents Preface 3 What's New in Version 4.0... 3 Components... 3 The ControlPoint Central
More informationAvatier Identity Management Suite
Avatier Identity Management Suite Migrating AIMS Configuration and Audit Log Data To Microsoft SQL Server Version 9 2603 Camino Ramon Suite 110 San Ramon, CA 94583 Phone: 800-609-8610 925-217-5170 FAX:
More informationEssential Project Management Reports in Clinical Development Nalin Tikoo, BioMarin Pharmaceutical Inc., Novato, CA
Essential Project Management Reports in Clinical Development Nalin Tikoo, BioMarin Pharmaceutical Inc., Novato, CA ABSTRACT Throughout the course of a clinical trial the Statistical Programming group is
More informationSOLARWINDS ORION. Patch Manager Evaluation Guide
SOLARWINDS ORION Patch Manager Evaluation Guide About SolarWinds SolarWinds, Inc. develops and markets an array of network management, monitoring, and discovery tools to meet the diverse requirements of
More informationGuide to Operating SAS IT Resource Management 3.5 without a Middle Tier
Guide to Operating SAS IT Resource Management 3.5 without a Middle Tier SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2014. Guide to Operating SAS
More informationYou have got SASMAIL!
You have got SASMAIL! Rajbir Chadha, Cognizant Technology Solutions, Wilmington, DE ABSTRACT As SAS software programs become complex, processing times increase. Sitting in front of the computer, waiting
More informationStreamServe Persuasion SP4 StreamServe Connect for SAP - Business Processes
StreamServe Persuasion SP4 StreamServe Connect for SAP - Business Processes User Guide Rev A StreamServe Persuasion SP4StreamServe Connect for SAP - Business Processes User Guide Rev A SAP, mysap.com,
More informationSAS Visual Analytics 7.1 for SAS Cloud. Quick-Start Guide
SAS Visual Analytics 7.1 for SAS Cloud Quick-Start Guide The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2014. SAS Visual Analytics 7.1 for SAS Cloud: Quick-Start Guide.
More informationCHAPTER 10: WEB SERVICES
Chapter 10: Web Services CHAPTER 10: WEB SERVICES Objectives Introduction The objectives are: Provide an overview on how Microsoft Dynamics NAV supports Web services. Discuss historical integration options,
More informationSage 300 ERP 2014. Installation and Administration Guide
Sage 300 ERP 2014 Installation and Administration Guide This is a publication of Sage Software, Inc. Copyright 2013. Sage Software, Inc. All rights reserved. Sage, the Sage logos, and the Sage product
More informationImplementing a SAS 9.3 Enterprise BI Server Deployment TS-811. in Microsoft Windows Operating Environments
Implementing a SAS 9.3 Enterprise BI Server Deployment TS-811 in Microsoft Windows Operating Environments Table of Contents Introduction... 1 Step 1: Create a SAS Software Depot..... 1 Step 2: Prepare
More informationDEPLOYMENT GUIDE Version 2.1. Deploying F5 with Microsoft SharePoint 2010
DEPLOYMENT GUIDE Version 2.1 Deploying F5 with Microsoft SharePoint 2010 Table of Contents Table of Contents Introducing the F5 Deployment Guide for Microsoft SharePoint 2010 Prerequisites and configuration
More informationSeamless Dynamic Web Reporting with SAS D.J. Penix, Pinnacle Solutions, Indianapolis, IN
Seamless Dynamic Web Reporting with SAS D.J. Penix, Pinnacle Solutions, Indianapolis, IN ABSTRACT The SAS Business Intelligence platform provides a wide variety of reporting interfaces and capabilities
More informationPerceptive Intelligent Capture. Product Migration Guide. with Supervised Learning. Version 5.5 SP3
Perceptive Intelligent Capture with Supervised Learning Product Migration Guide Version 5.5 SP3 Written by: Product Documentation, QA Date: March 2014 2014 Perceptive Software, Inc.. All rights reserved
More informationCHAPTER 5: BUSINESS ANALYTICS
Chapter 5: Business Analytics CHAPTER 5: BUSINESS ANALYTICS Objectives The objectives are: Describe Business Analytics. Explain the terminology associated with Business Analytics. Describe the data warehouse
More informationSAS BI Dashboard 4.3. User's Guide. SAS Documentation
SAS BI Dashboard 4.3 User's Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2010. SAS BI Dashboard 4.3: User s Guide. Cary, NC: SAS Institute
More informationLEARNING SOLUTIONS website milner.com/learning email training@milner.com phone 800 875 5042
Course 6451B: Planning, Deploying and Managing Microsoft System Center Configuration Manager 2007 Length: 3 Days Published: June 29, 2012 Language(s): English Audience(s): IT Professionals Level: 300 Technology:
More informationIBM Campaign and IBM Silverpop Engage Version 1 Release 2 August 31, 2015. Integration Guide IBM
IBM Campaign and IBM Silverpop Engage Version 1 Release 2 August 31, 2015 Integration Guide IBM Note Before using this information and the product it supports, read the information in Notices on page 93.
More informationSAS University Edition: Installation Guide for Linux
SAS University Edition: Installation Guide for Linux i 17 June 2014 The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2014. SAS University Edition: Installation Guide
More informationUpgrading User-ID. Tech Note PAN-OS 4.1. 2011, Palo Alto Networks, Inc.
Upgrading User-ID Tech Note PAN-OS 4.1 Revision B 2011, Palo Alto Networks, Inc. Overview PAN-OS 4.1 introduces significant improvements in the User-ID feature by adding support for multiple user directories,
More information