Transcription
SAS Marketing Operations Management Architecture and SecurityWHITE PAPER
SAS White PaperTable of ContentsIntroduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1High-Level Architecture Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 SAS Marketing Operations Management Foundation. . . . . . . . . . . . 3Marketing Information Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Marketing Process Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Applications Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 SAS Marketing Operations Management Modules . . . . . . . . . . . . . . 5Architectural Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Cataloger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Media Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Media Processor for FLV Generator. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Media Processor for Illustrator and InDesign. . . . . . . . . . . . . . . . . . . . . 7Office Processor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Platform and Technology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Internet Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Adobe Acrobat and Microsoft Office 2010 . . . . . . . . . . . . . . . . . . . . . . 8.NET Framework, ASP.NET, MTOM, AJAX and Flex . . . . . . . . . . . . . . . 8Versions of Platform Technology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Third-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
SAS Marketing Operations ManagementSoftware and Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . 10Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10User Machine Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Typical Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13DAM and Media Processing-Centric Deployment. . . . . . . . . . . . . . . . 14Deployment on a Virtual Machine Environment. . . . . . . . . . . . . . . . . . 15Deployment with SAS Digital Marketing . . . . . . . . . . . . . . . . . . . . . . 17Multitenant Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Application Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Account and Password Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18URL and Password Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Secure Communication Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Termination of Abandoned Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . 19Masquerading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Module Access Policy and Security Policy. . . . . . . . . . . . . . . . . . . . . 19Auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19iii
SAS White PaperIntroductionThis white paper describes the architecture of SAS Marketing Operations Managementand various aspects of its deployment and security. The information in this paper is validfor versions 6.0 R14, R14 Update 1 and R14 Update 2 (which is the current version).The following areas are covered: High-level architecture overview. Architectural components. Ecosystem. Virtualization. Deployment options. Deployment best practices. Security.This paper is intended for those involved in purchasing, selling and implementing SASMarketing Operations Management, including system administrators and anyoneseeking an understanding of the solution’s architecture and security.High-Level Architecture OverviewSAS Marketing Operations Management’s architecture includes the following highlights: A Web-based multitiered marketing solution. An intuitive and interactive AJAX-based user interface that can be extended easily. Use of common user-interface (UI) widgets, application services, marketingprocesses and marketing information models. Extensible and configurable information and process models. An XPDL-standard-compliant marketing process engine. A star schema-based rich marketing information model. An SOA that facilitates integration with existing enterprise applications.SAS Marketing Operations Management is an efficient and effective enterprise marketingsolution that uses advanced software and networking technologies. As a Web-basedsolution, SAS Marketing Operations Management enables marketing professionals toautomate and streamline their marketing operations and processes.SAS Marketing Operations Management has an n-tier architecture. Its well-defined,comprehensive Web-service interface implements the business logic necessary fora robust and scalable marketing operations management solution. It constitutesa service-oriented architecture (SOA) that allows integration with other enterpriseapplications and systems.1
SAS Marketing Operations Management. . . . . . . . . . . . . . .P ong &agrknaianwo rat Ma ardArt nfigu sset shbo dge MCo ital A g Da owle nchnDig rketi g Kn rkbe tonMa rketi g W mennMa rketi nage nernMa er Ma e PlaOff ourc der nersRe Buil c PlaneSit ategi eetsStr e ShTim.sesicendpxAu thent ationszs, EAu thori ctice castAu t Pra , Fore ssBe gets RuledsBu ines rssBu enda ieslCa rrenc rsnteesCu stom onte tivitiCu ital C g AcnDig rketi ionstMa tificarsNo tners OfferPa duct esPro ourcsRe rseUs dorsnVe sions wsrVe rkfloWosuct er inistration tsdPro roduc & Adm er Repor er.esciverSbWeit Trails ation. . . . . .eginEn gersna ingticaly MaAn cess Cach inet Eng erPro enss Cont hics anag enepiinMsGra tion g EngBuaniorm agInf MessngitrkeMa. . . . . . . .sgieolohnTec. . . . . . . . . . .Figure 1: SAS Marketing Operations Management modules, Web servicesand technology ecosystem.2
SAS White PaperSAS Marketing Operations Management has a rich user interface framework thatincludes a comprehensive library of forms, custom controls and widgets to help quicklydevelop customer need-based user interface screens. All modules are built using thisframework to ensure a consistent user experience. The framework-based approachgives users the flexibility to customize the existing user interface according to theirspecific needs.At its core, SAS Marketing Operations Management offers powerful information andprocess management capabilities. Its unique data model represents marketing datain terms of entity and facet objects. It has a unique way of retrieving, adding andupdating marketing data to and from the database, which enhances its performanceand scalability.Process modeling is based on the Workflow Management Coalition (WfMC) approvedXPDL standards (wfmc.org/xpdl-implementations.html) for representing processes,and it allows integration with various business process modeling or business processexecution language tools or software.The solution’s process designer enables users to define marketing workflow processesbased on business process modeling notation (BPMN). Users can also define processesusing any software based on BPMN modeling and then import those processes intoSAS Marketing Operations Management via the process designer.SAS Marketing Operations Management components have been separated intoappropriate n-tier architecture to provide maximum flexibility in terms of configurationand scalability. The solution’s components use industry-standard platforms andInternet technologies.SAS Marketing Operations Management FoundationSAS Marketing Operations Management Foundation provides the commoninfrastructure, application services and configuration tools for all modules within SASMarketing Operations Management.SAS Marketing Operations Management Foundation includes: Marketing information management. Marketing process management. Web services. Applications framework. Modules.3
SAS Marketing Operations l nagementArtworkProducerSiteBuilderSAS Marketing Operations ManagementSchema DesignerProcess DesignerUser Interface DesignerMOM Widgets & UI ControlApplications ntWeb ServicesMarketing Information ManagementMarketing Process ManagementSAS Marketing Operations Management FoundationFigure 2: SAS Marketing Operations Management Foundation.Marketing Information ManagementThe marketing information object model includes more than 150 predefined marketingentities (plans, activities, budgets, resources, estimates, vendors, digital assets, etc.). Itskey features are: A highly scalable and flexible star schema database. Configurable relationships between marketing entities without requiring anydevelopment effort. Configurable extension of the schema by association of customer-specificmetadata, called facets. Support for hierarchical lookup values. An operational data store for ad hoc reporting functionalities.Marketing Process ManagementThe marketing process management engine includes predefined representation ofalmost every marketing workflow task (plan approval, project execution and multipleproject type configurations, such as product launch, packaging and promotions design,etc.). Its key features are: Compliance with WfMC standard XPDL format for defining marketing processes. Based on industry standard BPMN graphical process notation. Support for hierarchical process definition and process dependencies. Support for manual and automated process initiations.4
SAS White Paper Support for predefined task types based on standard marketing processes. Support for human resource management. Support for integration with other systems through Web services.Web ServicesThe SAS Marketing Operations Management Web services implement all the businesslogic required by marketing operations management solutions. Its key features are: A highly modular, service-oriented architecture. Easy integration with ERP, CRM and other enterprise applications.Applications FrameworkThe SAS Marketing Operations Management applications framework includesthe following: Schema designer – Enables client-specific extensions to the SAS MarketingOperations Management database schema. Process designer – Enables client-specific configuration of marketing processes. User interface designer – Enables easy creation and extension of user interfacesand provides consistent user interactions for all marketing solutions. Widgets – Includes commonly used UI objects required for implementing complexmarketing functionality for consistent usage across all modules within SASMarketing Operations Management (e.g., approvals, discussion forums, search,navigation into the digital library.) User interface controls – Includes UI objects that incorporate common userinteractions (e.g., search, hierarchical lists, task panes, forms) used by all SASMarketing Operations Management modules.SAS Marketing Operations Management ModulesSAS Marketing Operations Management is built on SAS Marketing OperationsManagement Foundation and includes several modules, each focused on a well-definedmarketing operation. The following modules are included: Marketing Dashboards. Claims Management. Calendars. Artwork Producer. Strategic Planner. Approvals. Marketing Workbench. Marketing Knowledge Manager. Capacity Planner. Site Builder. Timesheets. Offer Management. Digital Asset Manager. Reports.5
SAS Marketing Operations ManagementArchitectural MediaProcessor forIllustratorAdobeIllustratorMediaProcessor forFLV GeneratorMediaProcessor forInDesignAdobeInDesignFigure 3: Architectural components of SAS Marketing Operations Management.CatalogerThe cataloger is responsible for importing digital assets into the SAS MarketingOperations Management system. Multiple catalogers can be deployed to manageuploading large volumes of digital assets. The cataloger distinguishes between singleand batch file uploads and reduces upload waiting time for users.Web ServerThe Web server hosts the SAS Marketing Operations Management suite. Users haveaccess to the Web server via Internet or intranet, depending on the deployment.Application ServerThe application server hosts the Web services belonging to SAS Marketing OperationsManagement Foundation.Media ServerThe media server is an optional component for a standard SAS Marketing OperationsManagement installation. It is an essential component for a digital asset managementcentric deployment. If more than 500 assets or assets greater than 5GB are uploadedor downloaded per month, the deployment could be defined as digital assetmanagement-centric.The media server hosts the digital asset repository to store digital content. It facilitatesfaster downloads due to fewer machine hops. It also facilitates the downloading oflarge files without hampering system usage.6
SAS White PaperMedia GeneratorThe media generator is an advanced and dedicated component responsible for highvolume processing of assets. It is responsible for generating previews, thumbnails andvarious renditions of the digital assets.Media Processor for FLV GeneratorThis media processor is responsible for FLV preview generation for video files to allowannotation on them.Media Processor for Illustrator and InDesignThis media processor is responsible for artwork generation using Adobe Illustratorand InDesign.Office ProcessorThe office processor is installed on a Microsoft Office server and is essential forgenerating previews and thumbnails of Microsoft Office files. It also helps with theprocessing required to consolidate comments made on Microsoft Office files routedfor approval.Platform and TechnologySAS Marketing Operations Management is based on the following industry-standardplatforms and technologies.Operating SystemSAS Marketing Operations Management is supported on Microsoft Windows Server2008 R2 Standard (64-bit). Microsoft Internet Information Server (IIS) is used as theapplication server.DatabaseSAS Marketing Operations Management stores all structured data and metadata relatedto digital content and collaborative workflows in a relational database managementsystem (RDBMS). Currently, Microsoft SQL Server 2008 R2 is the only supporteddatabase. The database can be accessed using the .NET data providers.7
SAS Marketing Operations ManagementInternet TechnologyThis layer contains software that enables users to interact with SAS MarketingOperations Management components across the Internet or intranet. This includes:1. SMTP servers for email notifications.2. FTP servers for file transfers for cataloging or remote downloads.3. Microsoft IIS for communicating with users via HTTP or HTTPS.Adobe Acrobat and Microsoft Office 2010Adobe PDF (versions 8.0/9.0/9.3.2/X) and Microsoft Office 2010 (64-bit version) files canbe routed, reviewed and approved using the Web browser.NET Framework, ASP.NET, MTOM, AJAX and FlexThe multiuser and transaction-oriented data access and business logic componentsof SAS Marketing Operations Management are implemented on .NET Framework andASP.NET. The UI is developed using ASP.NET and AJAX. A rich graphical UI has beendeveloped using Flex.SAS Marketing Operations Management uses the standard message transmissionoptimization mechanism (MTOM) protocol to transfer files across the application serverand Web server tiers.Use of a limited number of proven, industry-standard platforms and technologiesprovides a controlled environment for the application framework, which simplifiesimplementation and maintenance while enhancing robustness.8
SAS White PaperSAS MarketingOperations ManagementSoftware IntegrationWeb ServerAcrobatMedia ServerMS WordCatalogerMS ExcelIllustratorExternal Web ServiceMedia ProcessorApplication ServicesInDesignSQL ServerFile SystemPlatformASP.NET.NET FrameworkWindows Server OSFigure 4: SAS Marketing Operations Management platform and technology.Versions of Platform TechnologySAS Marketing Operations Management is based on Microsoft technologies. Pleasenote, however, that the software and hardware versions listed in the tablebelow are subject to change with newer versions of SAS Marketing OperationsManagement. To ensure that you have the most current list, please refer to theSAS Marketing Operations Management installation document that matches theversion of the software that you installed from the SAS Support site.9PlatformPlatform VersionServer Operating SystemWindows Server 2008 R2 (64-bit).NET Framework3.51ASP.NET3.51
SAS Marketing Operations ManagementDatabaseSAS Marketing Operations Management currently supports SQL Server Database 2008R2. The architecture allows the system to be ported to a new database by adding adatabase-specific query processor in the data access layer.Third-Party SoftwareSAS Marketing Operations Management requires certain third-party software for theDashboards, Desktop, Artwork Producer and Approvals related functionality. A detailedlist of software and hardware requirements is provided below in the next section.Software and Hardware RequirementsSoftware RequirementsPlease note: The architecture described in this paper is valid for versions SAS MarketingOptimization Management 6.0 R14 , R14 Update 1 and R14 Update 2 (the currentversion at the time of publication).10
ApplicationSWeervebSrerverCatalogerMediaSDa ervetabrasMe e Sdia erverPMe rocdia essorPrforocMSesso IllusOftrfficor ratoMe e SInD rdia ervesigGe ernneratorSoftwareLdo icenwn seloa reqda uirble ed/R /Fed reeist lyributedSAS White PaperUsageWindows Server 2008 R2 standard(64-bit) EN-US LocaleLicense requiredto be purchased bycustomerWindows 7 Standard (64-bit)EN-US LocaleLicense requiredto be purchased bycustomerIIS 7.0 on Windows 2008 R2(7.5.7600.16385)Comes with WindowsserverYYYYYYYWeb serverMSMQ v. 5.0Comes with WindowsserverYYYYYYYUsed for sending messages via queues by allmodules in MOM.NET Framework 3.51Freely downloadableYYYYYYY.NET required by applicationMSXML 4.0Freely downloadableYYYYMicrosoft SQLXML 4.0 SP1 (sqlxml.msi)Redistributed viaMOM PackageYUsed by SQL Server / Express. Used for XML queryoutput by Object Manager of MOM.Microsoft SQL Server System CLRTypes (SQLSysClrTypes.msi)Redistributed viaMOM PackageYExecuting DB script filesShared Management Objects(SharedManagementObjects.msi)Redistributed viaMOM PackageYExecuting DB script filesAccess Database Engine x64(AccessDatabaseEngine x64.exe)Redistributed viaMOM PackageYMicrosoft SQL Server 2008 R2Standard versionLicense requiredto be purchased bycustomerMedia Streaming Server(windows Media Services 2008Windows6.1-KB963697-x64.msu)Comes with WindowsserverAdobe Acrobat IX or Adobe Acrobat X(10.0.0) - Standard versionCustomer to buyMicrosoft Visual C 2008Redistributable Package (vcredistx64.exe)Redistributed viaMOM PackageYYCrystal Reports Basic for Visual Studio2012 x64 RedistributablePackageRedistributed viaMOM PackageYYMicrosoft Office Professional Plus2010 x-64 (14.0.4763.1000)License requiredto be purchased bycustomerImageMagick ributed viaMOM PackageASP.NET State ServiceComes with .NetFrameworkAdobe Illustrator CS3/CS4(Requiredonly if Artwork Producer is beingdeployed for the customer)License requiredto be purchased bycustomerAdobe InDesign CS 5.5 (Required onlyif Artwork Producer is being deployedfor the customer)License requiredto be purchased bycustomerGhostscript ly downloadable11YYYYYYYYYYRequired to host Illustrator processor - only ifArtwork Producer is being deployed and thecustomer is using Illustrator templatesRequired for XML processing. Used by all modules.YReading Excel using OLE DBYDatabase for MOMYRequired for streaming mediaY (ifWebDAVis beingused)YYOperating systemYYYYAcrobat is required on the MS Office Processor. It isoptional on the Web server, required only if WebDAVis used. (Note: If MOM Media annotations is notbeing used for approvals, a per user Adobe Licensefor all users of approvals needs to be purchased)YExecuting C COM DLLsRequired for Report generationYUsed for Consolidation of comments by approvalstasks and jobs and for import and export of Excel byall modules.YYUsed to generate previews and thumbnails fordigital assets in dam.Required along with .NETYUsed by Artwork Producer (Required only if ArtworkProducer is being deployed for the customer andcustomer is using Illustrator templates)YUsed by Artwork Producer (Required only if ArtworkProducer is being deployed for the customer andcustomer is using InDesign templates)YUsed for media file processing by DAM along withImageMagick
SAS Marketing Operations ManagementUser Machine RequirementsUsers interact with SAS Marketing Operations Management through Web browsers,mail clients and FTP clients. Users do not have to install any proprietary or “fat client”software on their desktops. Browsers – Internet Explorer 8.0/9.0 (32-bit) (Windows), Safari 5.1.5 onOS Lion, Firefox 12.0 (Windows). Microsoft Office 2010 (64-bit version). Adobe Acrobat 8.0/9.0/9.3.2 Standard or Professional or AdobeAcrobat X Reader. Adobe Flash player 10.3.183.11 (for Flex-Based Dashboard channels). SAS Marketing Operations Management desktop utility (created using Adobe Air)for desktop cataloging of digital assets into the Marketing Operations ManagementDigital Library. Additional requirements: Microsoft Terminal Server (for remote connectivity andmanagement of servers, mainly for administrators – optional).Hardware RequirementsArchitectural ComponentMinimum StorageRequirementMinimum HardwareRecommendationApplication Server150GB scalableDual-core or quad-core processor8GB of RAMWeb Server100GBDual-core or quad-core processor8GB of RAMMedia Server500GB scalable to 1TBDual-core or quad-core processor8GB of RAMMedia Generator100GBDual-core or quad-core processor8GB of RAMCataloger100GBDual-core or quad-core processor8GB of RAMMedia Processor100GBDual-core or quad-core processor8GB of RAM12
SAS White PaperHere are some recommendations to consider while determining the configuration fora specific deployment:1) The requirements mentioned above are generic product requirements. Forspecific customer requirements, please contact the SAS Marketing OperationsManagement Sizing Team (EEC department).2) The above table gives the minimum hardware requirements for each of the servers.If multiple components are being deployed on the same machine, a more robusthardware configuration is recommended.3) A database server (for SQL Server on Windows) is required. However, SAS doesnot have specific recommendations for this server or the database size.4) The server where the file system resides needs to have a higher storage capacity.In the above table, the media server is shown as a high-storage configuration. Inthe case where a media server is not set up, the application server needs a highstorage configuration and must be scalable.5) An improved hardware configuration is recommended for servers where largemedia processing happens, such as the cataloger, media processor andmedia generator.DeploymentThe SAS Marketing Operations Management architecture facilitates the deployment ofeach architectural component on a separate or on the same machine. The deploymentchoice depends on many factors, including: Is it is a DAM-centric deployment – i.e., is the system primarily being used toupload and download large numbers of digital assets? Is the amount of media processing large – i.e., is the system being used togenerate large volumes of artwork? Is usage in terms of number of users too high – i.e., will the number of usersworking concurrently on the system be high? Is the system going to be accessed by users outside the network – i.e., areusers geographically distributed and working remotely over the Web to accessthe system?The following section explains some of the typical deployment scenariosand recommendations.Typical DeploymentA typical deployment of SAS Marketing Operations Management comprises: A cataloger on one machine. A Web server on a separate machine. An application server on a separate machine. A database server hosting the database. A media processor on one machine.13
SAS Marketing Operations ManagementNote: This scenario could vary based on your specific environment, preferred securitysettings and firewall setups, etc.For example, in some hosted environments, it is preferred that the Web server, mediaserver and catalog server be located on the internal network segment as well. AnApache Server Reverse Web Proxy Farm sits in the DMZ, and a second firewall is setin between the DMZ and the internal network segment.FirewallDMZFile SystemWeb ServerCatalogerInternal Network SegmentApplicationServicesFile SystemMarketingDataMediaProcessorFigure 5: Typical SAS Marketing Operations Management deployment.DAM and Media Processing-Centric DeploymentIf DAM is being used extensively, and the system is primarily being used to uploadand download large numbers of digital assets, the deployment would comprise: A media server and cataloger on one machine. A Web server on one machine. An application server on one machine. A media processor and media generator on one machine.Note: This scenario could also vary based on your specific environment and preferredsecurity settings and firewall setups, etc., as mentioned in the previous scenario.14
SAS White PaperFirewallDMZFile SystemMedia Server CatalogerWeb ServerInternal Network SegmentApplicationServicesFile SystemMarketingDataMediaProcessorFigure 6: DAM-centric deployment.Deployment on a Virtual Machine EnvironmentSAS Marketing Operations Management can be deployed on an industry-standardvirtualization platform, such as VMWare. SAS Marketing Operations Management workson such a virtualization environment with almost no performance degradation, subject toaccurate configuration.15
SAS Marketing Operations ManagementCommonStorage Area(SAN / NAS)Web verSQLServerVMWare ESX ServerHardwareWindowsServerFigure 7: A sample virtual machine environment setup.The above deployment is done on VMWare ESX Server, where two virtual machineshave been created, and specific architectural components are deployed on each virtualmachine. The capacity planning for each machine is done as per the requirement ofthe component. SAN or NAS can be used as a common storage area. SAS MarketingOperations Management is completely compatible with VMWare enabled virtualizationtechnology with almost no degradation in performance.16
SAS White PaperDeployment with SAS Digital MarketingIf SAS Digital Marketing is set up along with SAS Marketing Operations Management,there are two potential scenarios to consider: Both SAS Marketi
and various aspects of its deployment and security . The information in this paper is valid for versions 6 .0 R14, R14 Update 1 and R14 Update 2 (which is the current version) . . Metrics Strategic Planning Marketing Work ows Digital Assets Financial Management Offer Management Authentication Authorization User Management Marketing Analytics .
