Admin Guide

SAS® Digital Marketing 5.1Administrator’s Guide

The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2007. SAS® Digital Marketing 5.1: Administrator’s Guide. Cary, NC: SAS Institute Inc.

SAS® Digital Marketing 5.1: Administrator’s Guide

Copyright © 2007, 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 printing, December 2007

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/pubs 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.

Contents

I Overview 1

What’s New in SAS Digital Marketing 5.1 3

Chapter 1. Introduction to SAS Digital Marketing . . . . . . . . . . . . . . 7

II Installation 19

Chapter 2. Installing SAS Digital Marketing . . . . . . . . . . . . . . . . 21

III Configuration 35

Chapter 3. Configuring SAS Digital Marketing . . . . . . . . . . . . . . . 37

Chapter 4. Customizing the Server . . . . . . . . . . . . . . . . . . . . 97

Chapter 5. Modifying Advanced Server Properties . . . . . . . . . . . . . . 133

IV Maintenance 155

Chapter 6. Managing Advanced Broadcast Tools . . . . . . . . . . . . . . . 157

Chapter 7. Managing SAS Jobs . . . . . . . . . . . . . . . . . . . . . 189

Chapter 8. Managing JDBC Connections . . . . . . . . . . . . . . . . . 221

Chapter 9. Managing Broadcast Tracking and Replies . . . . . . . . . . . . . 229

Chapter 10. Optimizing SAS Digital Marketing . . . . . . . . . . . . . . . . 255

V Appendixes 267

Appendix A. Using JMS With Broadcasts . . . . . . . . . . . . . . . . . 269

Glossary 283

Index 287

Credits

Documentation

Writing Lynne Bresler, Marie Dexter, Jennifer Jeffreys-Chen,Michael Monaco, and Jenna Moore

Editing Carolyn Sutton and Joan Knight

Production Support Tim Arnold, Monica McClain, and Stacy Suggsand Cover Design

Software

Development Jennifer Jeffreys-Chen, Michael Monaco, andSusanna Wallenberger

Installation Jennifer Jeffreys-Chen and Merri Jensenand Deployment

Testing Lynne Bresler, Jenna Moore, Keri Rehm, andShannon Smith

Support

Technical Steve Nash

Product Management Michael Monaco

i

About SAS Digital Marketing

Overview of SAS Digital Marketing

SAS Digital Marketing provides a suite of tools to plan, create, test, execute, and track your elec-tronic communication campaigns. With this comprehensive solution, you can deliver large-scalee-mail and wireless text message campaigns in-house and seamlessly coordinate your campaignswith other channels and marketing programs. You can easily customize your electronic communi-cations at the individual level and deliver effective messages to the customers that are more likelyto respond. With SAS Digital Marketing, you can achieve higher response rates and higher returnon your marketing investment.

Software Requirements

SAS Digital Marketing uses the following software:

� a POP3 or IMAP e-mail account that processes returned e-mail (bounces) and replies

� one of the following platforms or operating environments:

– Windows Server 2003 Family, Windows XP, or Windows 2000 Family– Solaris 8, Solaris 9, or Solaris 64– HPUX-IPF or HPUX-PA-RISC– AIX– Linux

� JRE 1.4.1 or 1.4.2 for the server and JRE 1.4.1 for the client

� an SMTP e-mail server for e-mail transmissions

� a JDBC provider such as a SAS/SHARE server or SAS Workspace Server

� Internet Explorer 6, Internet Explorer 7, or Mozilla Firefox

� Foundation SAS 9.1.3 SP4 on any supported platform

� a Web application server such as Apache Tomcat, BEA WebLogic, or IBM WebSphere

� an e-mail gateway to send SMS messages

� an SMS Application Service Provider, such as Clickatell Mobile Messaging(www.clickatell.com ) and PSWinCom SMS gateway (www.pswin.com), or an SMTP-SMS gateway that sends SMS, MMS, and WAP Push messages to wireless devices

NOTE: IMAP support for JavaMail API is experimental in this version of SAS Digital Marketing.

ii

Accessibility Features

SAS Digital Marketing includes the following accessibility and compatibility features that improveusability of the product for users with disabilities. These features are related to accessibility stan-dards for electronic information technology adopted by the U.S. Government under Section 508 ofthe U.S. Rehabilitation Act of 1973, as amended.

If you have questions or concerns about the accessibility of SAS products, send e-mail [email protected].

Standard Keyboard Shortcuts

SAS Digital Marketing adheres to accessibility standards for the Windows platform. SAS DigitalMarketing can be navigated by using the keyboard. The following table includes some guidelines:

Task Keyboard Control

Move forward through controls TABMove backward through controls SHIFT+TABDisplay drop-down list contents ALT+down arrowDisplay menus that have focus down arrowActivate buttons and menu selections that have focus ENTER

You can also access menu items by using the keyboard shortcuts listed in the drop-down menus orby clicking ALT + the underlined letter.

iii

Part I

Overview

What’s New in SAS Digital Marketing 5.1

Overview

SAS Digital Marketing 5.1 has the following changes and enhancements:

� improved configuration in SAS Digital Marketing

� enhanced security features

� enhanced digital data repository

� enhanced support for broadcast definitions

� improved integration with SAS Customer Intelligence software

� enhanced reporting

� enhancements to the Web Studio interface

� documentation enhancements

Improved Configuration

Configuration of SAS Digital Marketing has been improved. You can now create the WAR filesfor tracking deployment and SAS Web Studio deployment on the middle tier from the SAS DigitalMarketing Configuration wizard. No additional steps are required.

Enhanced Security Features

This version of SAS Digital Marketing provides the following security enhancements:

� Different groups of users can have access to different resources in the SAS Digital Marketingsystem.

� Fewer fire wall ports are required to be opened.

� Only approved content can be published to a digital channel.

4 F

Enhanced Digital Data Repository

You can organize images, audio files, video, and links into libraries. The ability to share these filesmakes it easier for you to browse and retrieve content for use in your campaigns. You can use Webresources to create multichannel broadcasts.

Enhanced Support for Broadcast Definitions

Support for RSS Feeds

You can now create multichannel broadcasts to support really simple syndication (RSS) feeds. RSSfeeds are interactive digital channels that are growing quickly in popularity. SAS Digital Marketingenables you to define, deploy, and track your RSS feeds.

Multichannel Broadcasts

You are now able to create a single broadcast that can be used across different digital channels.These channels include distribution via Web sites, RSS feeds, mobile devices, or e-mail. SASDigital Marketing enables you to define, test, and execute a multichannel campaign by using abroadcast wizard.

Improved E-mail Delivery

SAS Digital Marketing provides domain throttling, which limits the rate at which e-mails are sentto a specific domain, such as yahoo.com. This ensures that your e-mails are not flagged as junke-mail and filtered from recipients’ accounts.

Improved Integration with SAS Customer Intelligence

Integration between SAS Customer Intelligence and SAS Digital Marketing has been streamlinedin the following ways:

Enhanced Reporting F 5

� You can view export definitions from SAS Marketing Automation in SAS Digital Marketing.

� You can view broadcast definitions from SAS Digital Marketing in SAS Marketing Automa-tion.

� You can link multiple cells to a single communication, even when different treatments areused to personalize content.

� SAS Digital Marketing and SAS Customer Intelligence share contact and response historytables.

� SAS Enterprise Guide now is packaged with SAS Digital Marketing.

Enhanced Reporting

SAS Digital Marketing and SAS Customer Intelligence share contact and response history tables,which enables common reporting between these applications.

Enhancements to the SAS Digital Marketing Web StudioUser Interface

SAS Digital Marketing Web Studio provides additional functionality.

In the SAS Digital Marketing Web Studio interface, you can perform the following tasks:

� create, manage, and monitor e-mail broadcasts. To edit the HTML content, your site adminis-trator can download the TinyMCE Web-based Javascript editor, which is now available fromthe SAS Digital Marketing Server Configuration wizard.

� delete, rename, move, duplicate, and summarize SMS and ASP broadcasts. SMS and ASPbroadcasts are fully supported.

� change your password. If the basic security mode is used, then your default password isassigned by SAS Digital Marketing when the software is installed or configured by yoursoftware administrator. You can now change your password in SAS Digital Marketing WebStudio. After you change your password on the server, you must update your connectioninformation on your client.

� run new reports. The Visual Reports are now supported for text content in a broadcast. Youcan also run reports for RSS feeds and new multichannel broadcasts.

6 F

Documentation Enhancements

In addition to the existing SAS Digital Marketing references, a separate book, the SAS DigitalMarketing Web Studio: User’s Guide, has been created. This book contains information for allusers of Web browser clients.

Chapter 1

Introduction to SAS Digital Marketing

ContentsOverview of the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Architecture of SAS Digital Marketing . . . . . . . . . . . . . . . . . . . . . . . . 8

About the Multi-tiered Architecture . . . . . . . . . . . . . . . . . . . . . . 8Broadcast Delivery and Response Tracking . . . . . . . . . . . . . . . . . . 10

Life Cycle of the Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Life Cycle of E-mail Broadcasts . . . . . . . . . . . . . . . . . . . . . . . . 11Life Cycle of RSS Feeds . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Life Cycle of SMS Broadcasts . . . . . . . . . . . . . . . . . . . . . . . . . 14Life Cycle of ASP Broadcasts . . . . . . . . . . . . . . . . . . . . . . . . . 15

Customizing the Broadcasts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Using This Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Purpose of This Documentation . . . . . . . . . . . . . . . . . . . . . . . . 16Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Overview of the Software

SAS Digital Marketing is a client and server application that quickly delivers e-mail, RSS feeds, andSimple Message Service (SMS) broadcasts to your customers within single channel or multichannelmarketing campaigns. You can easily customize broadcast content at the individual level and deliverrelevant, personalized messages to customers who are more likely to respond. Comprehensiveresponse tracking enables you to determine the effectiveness of your broadcasts across a variety ofmarketing channels. Specifically, SAS Digital Marketing offers the following features:

� an intuitive graphical interface to create customized e-mail, SMS, and Application ServiceProvider (ASP) broadcasts as well as to define and manage RSS feeds.

� the ability to push broadcast content to the Web so that message content is shared across yourenterprise

� scalability to send millions of messages each day or several thousand messages a week

� data access to use virtually any database

8 F Chapter 1: Introduction to SAS Digital Marketing

� integration with SAS Customer Intelligence software and predictive analytics to identify thebest message for each customer or target segment

For e-mail and multichannel broadcasts, SAS Digital Marketing also supports the following:

� opt-out processing that conditionally aborts the messages to the e-mail addresses that arecontained in an opt-out table

� a global duplication policy that filters out all duplicate e-mail addresses when you send abroadcast

Architecture of SAS Digital Marketing

About the Multi-tiered Architecture

SAS Digital Marketing is designed to efficiently process large amounts of data and provide timelyfeedback on broadcast response. A multi-tier architecture enables SAS Digital Marketing to dis-tribute functionality across computer resources. A tier represents a conceptual category of softwarecomponents that perform similar computing tasks and that require similar resources. Different tiersdo not always represent separate computers or groups of computers. You scale the architecture tomeet your workload demand. For a large company, the architecture might comprise many machinesthat run different operating systems. For prototyping, demonstrations, or very small enterprises,you can install all of the tiers on a single machine.

The architecture of SAS Digital Marketing consists of the following tiers:

Client tierprovides desktop access to single channel or multichannel broadcasts, customer intelligencedata, and processing functionality. The Web browser interface provides functionality tomanage broadcasts and generate reports on broadcast response. More comprehensive func-tionality is available in an intuitive graphical user interface on individual desktop computers.

Middle tierprovides access to functionality in the Web browser interface. This tier uses Java servletsthat are deployed on a Web application server to track broadcast response, create reports, anddistribute content. This tier also passes processing and analysis requests to the server tier.

Server tieruses SAS Digital Marketing, SAS, and e-mail servers to process the workload and manage thedata sources that contain your customer intelligence. Several types of servers are available tohandle the workload. The software can distribute the processing loads to a network of serversso that large scale requests by multiple clients are handled quickly. This tier also stores thedata source tables in relational database management systems or SAS tables.

About the Multi-tiered Architecture F 9

Figure 1.1 summarizes the architecture of SAS Digital Marketing.

Figure 1.1 SAS Digital Marketing Multi-tier Architecture


Broadcast Delivery and Response Tracking

A SAS Digital Marketing broadcast includes a definition phase to create customized content, an ex-ecution phase to deliver the broadcast, and a tracking phase to record responses from recipients. Thebroadcast delivery architecture provides high-performance, customized content delivery through aMail Transport Agent (MTA). Response tracking architecture enables you to monitor message orRSS content viewing, track Web browsing, and classify recipient responses. SAS Digital Marketingprovides integrated reporting and analysis of broadcast responses, or you can use extract, transform,and load (ETL) processes for advanced analysis and visualizations.

Delivery Architecture

SAS Digital Marketing uses the following functionality:

� Java RMI technology for remote client communication.

� J2EE JavaMail technology for delivery of e-mail to the MTA.

� an ASP or SMS gateway for sending SMS, Multimedia Message Service (MMS), or WirelessApplication Protocol (WAP) Push messages.

� Extensible Stylesheet Language (XSL) for e-mail content specification.

� Java Database Connectivity (JDBC) technology for access to data tables that provide digitalmessage delivery and customization.

� SAS Digital Marketing clients that provide the graphical user interface.

� an MTA that is essentially an e-mail server. You must provide a fully configured e-mail serverfor SAS Digital Marketing to use. JavaMail supports Simple Mail Transfer Protocol (SMTP),Post Office Protocol (POP), and Internet Message Access Protocol (IMAP) communicationmethods to an MTA.

NOTE: IMAP support for the JavaMail application program interface (API) is experimental in thisversion of SAS Digital Marketing.

Tracking Architecture

The tracking architecture includes the following components:

� Java Servlet technology to track click-through and e-mail open rate. SAS Digital Marketingprovides several tracking and utility servlets for the mid-tier. You must deploy a Web appli-cation server to track e-mail broadcasts when you use these servlets. For more information,see “Configuring the Tracking and Web Publication Tier” on page 54.

� J2EE JavaMail technology to implement an e-mail client that records e-mail replies.

Life Cycle of the Broadcast F 11

Life Cycle of the Broadcast

Life Cycle of E-mail Broadcasts

The life cycle of the SAS Digital Marketing broadcast includes the definition phase to create thecontent, the execution phase to deliver the broadcast, and the tracking phase to record responsesfrom recipients.

Each e-mail message uses an address that is stored in the customer database and retrieved by usingJDBC technology. After the message content and e-mail header are created, you can edit the contentto customize the e-mail. The SAS Digital Marketing server processes the broadcast. If you createdan e-mail broadcast, then you can also use grid computing across a grid network to distribute yourbroadcasts. The MTA sends the e-mail message to the recipient. The response table records therecipient’s response to the e-mail. By using the information in the customer database, you cancorrelate the responses in the response table to customers.

Figure 1.2 shows the life cycle of an e-mail broadcast.

Life Cycle of RSS Feeds

The life cycle of SAS Digital Marketing Really Simple Syndication (RSS) feeds includes the defi-nition phase to create the RSS content, the schedule phase to publish Web content that an RSS feedcan request, and the tracking phase to record responses from recipients.

a multi-channel broadcast is used to make the content available to be pulled by an RSS feed reader.

RSS feeds distribute updated content to subscribers by displaying a headline, an optional shortdescription, and a link to a detailed article. To use broadcasts through an RSS feed, you create anRSS feed to define your content topic. You publish the content to the RSS feed by referencing theWeb publish URL for the feed when the feed XML is requested. Java servlets that are deployed ona Web application servers process requests by subscribers to read the content. JDBC technology isused to record the request in the response table.

Figure 1.3 shows the life cycle of multichannel broadcast that uses an RSS feed.


Figure 1.2 The Life Cycle of an E-mail Broadcast

Life Cycle of RSS Feeds F 13

Figure 1.3 The Life Cycle of an RSS Feed


Life Cycle of SMS Broadcasts

The life cycle of the SAS Digital Marketing SMS broadcast includes the definition phase to createthe content and the execution phase to deliver the broadcast.

Each SMS message uses a phone number that is stored in the customer database and retrieved byusing JDBC technology. After the message content and header for the text message are created,you can use the content editor to customize the text message. The SAS Digital Marketing serverprocesses the broadcast. You can also use grid computing across a grid network to distribute yourbroadcasts. The MTA sends the text messages to the SMTP-SMS gateway, which is used to delivershort text messages to the recipient.

Figure 1.4 shows the life cycle of an SMS broadcast.

Figure 1.4 The Life Cycle of an SMS Broadcast

Life Cycle of ASP Broadcasts F 15

Life Cycle of ASP Broadcasts

The life cycle of the SAS Digital Marketing ASP broadcast includes the definition phase to createthe content and the execution phase to deliver the broadcast.

Each ASP message uses a phone number that is stored in the customer database and retrieved byusing JDBC technology. After the message content is created and the ASP parameters are specified,you can use the content editor in the SAS Digital Marketing client to customize the text message.The SAS Digital Marketing server processes the broadcast. You can also use grid computing acrossa grid network to distribute your broadcasts. The ASP broadcast definition connects to mobilenetworks through an ASP that provides a HyperText Transfer Protocol (HTTP) post interface. Youconfigure the ASP broadcast definition to post the appropriate requests that send SMS, MMS, orWAP Push messages.

Figure 1.5 shows the life cycle of an ASP broadcast.

Figure 1.5 The Life Cycle of an ASP Broadcast


Customizing the Broadcasts

SAS Digital Marketing provides a variety of features that enable you to customize your broadcasts.With the broadcast wizard, you can create broadcasts that have customized content and trackinginformation. The broadcast wizard creates an XSL template that contains the rules for generatingcustomized content. A comprehensive content editor enables you to modify the components of abroadcast definition. You can use XSL to customize the e-mail or text message content so that eachrecipient receives a unique message. Likewise, you can use a third-party editor, such as FrontPage,Dreamweaver, or the TinyMCE HTML editor, to edit the message content.

You can configure SAS Digital Marketing to use grid computing in order to distribute a broadcasttransmission across multiple computers. Grid computing enables you to easily increase your e-mailmessage delivery capacity by adding more computers to the grid network.

JDBC technology enables you to access your customer data and response data. SAS Digital Mar-keting has been optimized for SAS JDBC providers. By using SAS JDBC providers in conjunctionwith SAS/ACCESS software, you can store your customer and response data on many differentdatabases. You can also use a third-party JDBC provider, such as mySQL, to access your customerand response databases.

Using This Documentation

Purpose of This Documentation

This document describes how to install and configure SAS Digital Marketing software.

This document is organized as follows:

� Chapter 1, “Introduction to SAS Digital Marketing,” explains the purpose of SAS DigitalMarketing and summarizes related information and services.

� Chapter 2, “Installing SAS Digital Marketing,” explains how to install the software.

� Chapter 3, “Configuring SAS Digital Marketing,” explains how to configure the software anddeploy the tracking servlets.

� Chapter 4, “Customizing the Server,” explains how to modify the SAS Digital Marketingserver settings after the software has been installed and configured.

� Chapter 5, “Modifying Advanced Server Properties,” describes the advanced server propertiesthat you can use to set global policies for your site.

� Chapter 6, “Managing Advanced Broadcast Tools,” explains several tools that assist in thecreation and management of broadcasts.

Intended Audience F 17

� Chapter 7, “Managing SAS Jobs,” explains how to use SAS jobs to create reports and consol-idate data.

� Chapter 8, “Managing JDBC Connections,” explains how to use the JDBC connections.

� Chapter 9, “Managing Broadcast Tracking and Replies,” explains how to use the E-mail ReplyManager to process broadcast replies.

� Chapter 10, “Optimizing SAS Digital Marketing,” explains how to improve performance bydistributing the broadcast transmissions across the grid network.

Intended Audience

This documentation is for users who install, configure, and optimize SAS Digital Marketing underthe UNIX or Linux operating environments, and on PC platforms. SAS and other programmingexpertise is not required.

Part II

Installation

Chapter 2

Installing SAS Digital Marketing

ContentsOverview of Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . 21

Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Directory Structure for SAS Digital Marketing . . . . . . . . . . . . . . . . 23Java Servlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Migrating Broadcasts from SAS E-mail Marketing . . . . . . . . . . . . . . 26

Installing a SAS Digital Marketing Server . . . . . . . . . . . . . . . . . . . . . . 26Introduction to the Server Installation . . . . . . . . . . . . . . . . . . . . . 26Run the Server Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Installing a SAS Digital Marketing Grid Node . . . . . . . . . . . . . . . . . . . . 30Introduction to the Grid Node Installation . . . . . . . . . . . . . . . . . . . 30Run the Grid Node Installer . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Installing a SAS Digital Marketing Client . . . . . . . . . . . . . . . . . . . . . . 32Introduction to the Client Installation . . . . . . . . . . . . . . . . . . . . . 32Run the Client Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Overview of Installing the Software

Software Components

Before you run SAS Digital Marketing, a site administrator must install the software and deployWeb archive files to a middle tier. SAS Digital Marketing provides utilities to install and configurethe following software components:

Serverinstalls SAS Digital Marketing clients and the SAS Digital Marketing server.

Grid nodeinstalls SAS Digital Marketing clients and a SAS Digital Marketing grid node.

Clientinstalls the SAS Digital Marketing Studio client.

22 F Chapter 2: Installing SAS Digital Marketing

Java Servlets and Web Studioconfigures Java servlets in the Web archive (WAR) files. You deploy these files on a Webapplication server.

SAS Digital Marketing can process sizable e-mail broadcasts across multiple computers when youinstall grid nodes and configure the server to use the computers in the grid network. The server candistribute the e-mail broadcast transmission across an unlimited number of grid nodes.

Installation Requirements

To use SAS Digital Marketing, you must have the following software and resources:

� a computer that is running under one of the following platforms or operating environments:

– Windows Server 2003 Family, Windows XP, or Windows 2000 Family

– Solaris 8, Solaris 9, or Solaris 64

– HPUX-IPF running HP-UX 11i Version 2

– HPUX-PA-RISC running HP-UX 11i, version 1 (64-bit)

– AIX, Release 5.1 or Release 5.2

– Red Hat Enterprise Linux 2.1 or 3.1

– SuSE Linux Enterprise Server 8 + Service Pack 1

� a valid license file

� JRE 1.4.1 or 1.4.2 for the server, and JRE 1.4.1 for the client

� an SMTP e-mail server for e-mail transmissions

� a JDBC provider such as a SAS/SHARE server or SAS Workspace Server



� a Web application server such as Apache Tomcat, BEA WebLogic, or IBM WebSphere

� a POP3 or IMAP e-mail account that processes returned e-mail (bounces) and replies.

� an e-mail gateway to send SMS messages

� an SMS Application Service Provider, such as Clickatell Mobile Messaging(www.clickatell.com ) and PSWinCom SMS gateway (www.pswin.com), or an SMTP-SMS gateway that sends SMS, MMS, and WAP Push messages to wireless devices

NOTE: IMAP support for JavaMail API is experimental in this version of SAS Digital Marketing.

Directory Structure for SAS Digital Marketing F 23

SAS Digital Marketing under AIX requires an IBM 1.4.1 32-bit JRE. For more information, seeSAS Note SN-012999. For information about specific hardware, software, and memory configura-tions, see the Install Center at http://support.sas.com.

NOTE: You can also use MySQL, MS-SQL, DB2, and Oracle as direct JDBC providers. However,SAS Digital Marketing is optimized for SAS JDBC drivers, which enables connectivity to any ofthe databases that SAS/ACCESS supports.

Directory Structure for SAS Digital Marketing

SAS Digital Marketing uses the following files and directories:

asps directorycontains the metadata for the ASP broadcast types.

broadcasts directorycontains e-mail and SMS broadcast definitions. The samples subdirectory contains examplesof broadcast definitions.

config directorycontains the server configuration files. These files include the server.properties file that fur-ther customizes the SAS Digital Marketing server.

content directorycontains the broadcast content (HTML, TXT, XSL, and AOL files).

deployments directorycontains the WAR files with servlets that you configured for deployment.

doc directorycontains documentation files.

history directorycontains history files for broadcast executions.

images directorycontains image files that are used to demonstrate bulk loading of resources.

jars directorycontains third-party JAR and custom CLASS files that are downloaded to a rich client con-nection.

lib directorycontains the JAR files that are required by SAS Digital Marketing.

logs directorycontains the server and broadcast logs.

meta-inf directorycontains the JavaMail descriptors for the SMTP spooler.

mid directorycontains the unconfigured SAS Digital Marketing servlet’s Web archive, bess.war, and theSAS Digital Marketing Web Studio archive, sdm.war.


nodeconfig directorycontains grid node settings.

pending directorycontains temporary files that are used for domain throttling.

replies directorycontains e-mail message replies and bounces.

reports directorycontains XSL templates that are used to generate HTML broadcast reports.

WEBROOT directorycontains Web resources files.

rss directorycontains that RSS Feed definitions that are used by the Feed Manager.

samples directorycontains the files that are examples of e-mail content.

sasmacro directorycontains SAS macro programs that are used to generate SAS reports.

spool directorycontains spooled e-mails that are stored by the SMTP spooler.

temp directorycontains temporary files that are used in broadcast executions.

This documentation uses the word ROOT to refer to the directory where you installed SAS DigitalMarketing. SAS Digital Marketing requires Write access to the ROOT directory and its subdirecto-ries when a user runs the server.

Java Servlets

SAS Digital Marketing stores the Java servlets for response tracking and the Web publication frame-work in the Web archive file, bess.war. You use the SAS Digital Marketing Servlet Configurationwizard to configure a WAR file for deployment that contains the servlets. For more information, see“Configuring the Tracking and Web Publication Tier” on page 54.

Java Servlet Requirements

To use the servlets in the bess.war file, your Web application server must be visible to the intendedrecipients of the broadcast. Corporate computing environments often use a firewall to prevent unau-thorized access to a company’s private information from the Internet or a network. SAS DigitalMarketing requires deployment of the WAR file that contains the servlets on a Web applicationserver that is outside your firewall and visible from the Internet.

Java Servlets F 25

Broadcast Tracking Servlets

SAS Digital Marketing provides the following tracking servlets:

redir servlettakes all the variables that are passed to the servlet, records them in a table, and then redirectsthe browser to the link variable.

crumb servletis a 1x1 GIF image that is embedded in the HTML content that tracks when an e-mail recipientviews the HTML file. The crumb servlet records all the variables that are passed in and returnsa blank 1x1 GIF image to the browser.

get servlettracks the links that were clicked in the text content.

NOTE: The get servlet is also used for HTML content when the IndexedLinks server propertyis set. For more information, see “Response Server Properties” on page 151.

optout servlettracks the opt-out responses from a broadcast.

For more information, see “Response Tracking” (Chapter 7, SAS Digital Marketing: User’s Guide).

Web Publication Servlets

SAS Digital Marketing provides the following Web publication servlets:

pub servletsretrieves formatted broadcast content from the SAS Digital Marketing server. Several variantsof the pub servlet are available that distinguish the context by which the content is requested.

res servletretrieves an ad-hoc Web resource that is hosted on the SAS Digital Marketing server.

rss servletretrieves an RSS feed that SAS Digital Marketing manages.

For more information, see “Overview of RSS Feeds” (Chapter 6, SAS Digital Marketing:User’s Guide).


Migrating Broadcasts from SAS E-mail Marketing

You can still use broadcast definitions that were created with SAS E-mail Marketing when youupgrade to SAS Digital Marketing. If you plan to use these broadcast definitions, then do notuninstall SAS E-mail Marketing before you install SAS Digital Marketing. After SAS DigitalMarketing is installed, copy the files from the following SAS E-mail Marketing directories:

� ROOT/content to the SAS Digital Marketing ROOT/content directory

� ROOT/broadcasts to the SAS Digital Marketing ROOT/broadcasts directory

� ROOT/history to the SAS Digital Marketing ROOT/history directory

� ROOT/logs to the SAS Digital Marketing ROOT/logs directory

You should not replace the entire SAS Digital Marketing directory. Merge the contents of both di-rectories instead. Otherwise, you will lose the predefined SAS Digital Marketing sample broadcastdefinitions.

Installing a SAS Digital Marketing Server

Introduction to the Server Installation

Your site must install SAS Digital Marketing on at least one server. After you have verified theinstallation requirements, start the SAS Digital Marketing installation program from the SAS Soft-ware Navigator on the SAS Digital Marketing CD-ROM.

NOTE: If SAS E-mail Marketing 2.1 or 2.2 is installed, then the installer installs a separate versionof SAS Digital Marketing. For information about using broadcast definitions that were created inSAS E-mail Marketing, see “Migrating Broadcasts from SAS E-mail Marketing” on page 26.

Run the Server Installer F 27

Run the Server Installer

To create a server, complete the following steps:

1. After the InstallShield wizard opens and you select a language, click Next.

2. Select Server as the installation configuration and click Next.

NOTE: If SAS Digital Marketing is already installed on your computer, then you are notprompted about how to configure the installation. The Installer wizard displays the software’scurrent location. Click Next to re-install SAS Digital Marketing in this location.


3. Specify the location of the directory to use for software installation and click Next. You musthave Write access to the directory. Click Browse to locate another directory.

4. Specify the directory location of the broadcast and the content files and click Next.

Run the Server Installer F 29

When you create a broadcast definition, a copy of the broadcast content is stored in the contentdirectory. This content is available for use when you execute the broadcast. If you uninstallSAS Digital Marketing before you install a new release of the software, then your broadcastswill not be available.

5. Specify the port number and click Next.

SAS Digital Marketing uses Java Remote Method Invocation (RMI) technology. The portthat you specify is the port number on which RMI’s registry accepts calls on this computer. Ifanother application on this computer uses port 9221, specify a different port number to avoidconflicts.

NOTE: Other ports are also used by RMI for client-server connectivity. To restrict the portsthat are used, see the CustomSocketFactory server property in “Properties for RestrictingPorts” on page 145.

6. Review the installation information and click Next to install the software. If you decide tochange a setting, click Back to return to the appropriate step in the wizard.

7. Decide whether to run the Configuration wizard and click Next. For more information, see“Configuring the SAS Digital Marketing Server” on page 38. If you select No, then clickNext and Finish to close the Installer window.


Installing a SAS Digital Marketing Grid Node

Introduction to the Grid Node Installation

When you expect to send e-mail to a large number of recipients, you can create a series of gridnodes on other computers that distribute the processing of the e-mail broadcast transmission. Afteryou install a grid node, you must modify the SAS Digital Marketing server to use the computersthat are in the grid network.

NOTE: Before you can use grid computing, a SAS Digital Marketing server must be installed.

Each computer that is part of the grid network requires one of the following platforms or operatingenvironments:

� Windows Server 2003 Family, Windows XP, or Windows 2000 Family

� Solaris 8 or Solaris 9

� HPUX-IPF running HP-UX 11i Version 2

� HPUX-PA-RISC running HP-UX 11i, version 1 (64-bit)

� AIX, Release 5.1 or Release 5.2

� Red Hat Enterprise Linux 2.1 or 3.1

� SuSE Linux Enterprise Server 8 + Service Pack 1

SAS Digital Marketing under AIX requires an IBM 1.4.1 32-bit JRE. For more information, seeSAS Note SN-012999. For more information about specific hardware, software, and memory con-figurations, see the Install Center at http://support.sas.com.

Run the Grid Node Installer

To create a grid node, complete the following steps:

1. Start the SAS Digital Marketing installation program from the SAS Software Navigator onthe SAS Digital Marketing CD-ROM, using the computer that will serve as a grid node.


Run the Grid Node Installer F 31

3. Select Grid Node as the installation configuration and click Next.


4. Specify the location of the directory to use for software installation and click Next. ClickBrowse to locate another directory.

NOTE: You must have Write access to this directory.

5. Specify the port number and click Next. SAS Digital Marketing uses Java Remote MethodInvocation (RMI) technology. The port that you specify is the port number on which RMI’sregistry accepts calls on this computer. If another application on this computer uses port9221, specify a different port number to avoid conflicts.

6. Review the installation choices and click Next to install the software. If you decide to changea setting, click Back to return to the appropriate step in the wizard.

7. Decide whether to run the Configuration wizard and click Next. For more information, see“Configuring a Grid Node” on page 256. If you select No, then click Next and Finish to closethe Installer window.


Installing a SAS Digital Marketing Client

Introduction to the Client Installation

To install SAS Digital Marketing as a client, your site must install SAS Digital Marketing as aserver on a computer that you can access through your network. A SAS Digital Marketing clientmust have the ability to connect to the SAS Digital Marketing server. For more information aboutconnecting to a server, see “Running SAS Digital Marketing” (Chapter 2, SAS Digital Marketing:User’s Guide).

Each computer that runs a SAS Digital Marketing client requires one of the following platforms oroperating environments:

� Windows Server 2003 Family, Windows XP, or Windows 2000 Family

� Solaris 8 or Solaris 9

� HPUX-IPF running HP-UX 11i Version 2

� HPUX-PA-RISC running HP-UX 11i, version 1 (64-bit)

� AIX, Release 5.1 or Release 5.2

� Red Hat Enterprise Linux 2.1 or 3.1

� SuSE Linux Enterprise Server 8 + Service Pack 1

SAS Digital Marketing under AIX requires an IBM 1.4.1 32-bit JRE. For more information, seeSAS Note SN-012999. For more information about specific hardware, software, and memory con-figurations, see the Install Center at http://support.sas.com.

NOTE: The Microsoft Windows operating environment provides the best performance for SASDigital Marketing Studio.

Run the Client Installer F 33

Run the Client Installer

To create a SAS Digital Marketing client, complete the following steps:

1. Start the SAS Digital Marketing installation program from the SAS Software Navigator onthe SAS Digital Marketing CD-ROM using the computer that will serve as a client.


3. Select Client as the installation configuration and click Next.


4. Specify the location of the directory to use for software installation and click Next. ClickBrowse to locate another directory.

NOTE: You must have Write access to this directory.

5. Review the installation choices and click Next to install the software. If you decide to changea setting, click Back to return to the appropriate step in the wizard. Click Finish to close theInstaller window.

Part III

Configuration

Chapter 3

Configuring SAS Digital Marketing

ContentsOverview of Configuring the Software . . . . . . . . . . . . . . . . . . . . . . . . 38Configuring the SAS Digital Marketing Server . . . . . . . . . . . . . . . . . . . 38

How to Configure the Server . . . . . . . . . . . . . . . . . . . . . . . . . . 38Run the Server Configuration Wizard . . . . . . . . . . . . . . . . . . . . . 39

Configuring the Tracking and Web Publication Tier . . . . . . . . . . . . . . . . . 54How to Configure the Middle Tier . . . . . . . . . . . . . . . . . . . . . . . 54Deploying the Servlet WAR File . . . . . . . . . . . . . . . . . . . . . . . . 54Testing the Tracking Servlets . . . . . . . . . . . . . . . . . . . . . . . . . 67Updating the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Reconfiguring the Tracking Servlets . . . . . . . . . . . . . . . . . . . . . . 71Configuring a Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Configuring SAS Digital Marketing Web Studio . . . . . . . . . . . . . . . . . . . 83How to Configure the Web Application . . . . . . . . . . . . . . . . . . . . 83Deploying the Web Studio WAR File . . . . . . . . . . . . . . . . . . . . . 83Updating the Server To Use Web Studio . . . . . . . . . . . . . . . . . . . . 83Configure the Web Studio Server . . . . . . . . . . . . . . . . . . . . . . . 84Implementing the Broadcast Scheduler . . . . . . . . . . . . . . . . . . . . 85Implementing the SAS Language Adapter . . . . . . . . . . . . . . . . . . . 86

Configuring SAS Information Delivery Portal . . . . . . . . . . . . . . . . . . . . 88About SAS Information Delivery Portal . . . . . . . . . . . . . . . . . . . . 88Add a Link to SAS Digital Marketing . . . . . . . . . . . . . . . . . . . . . 89

Validating Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Create a Sample Data Table . . . . . . . . . . . . . . . . . . . . . . . . . . 93Preview a Sample Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Configure a Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

38 F Chapter 3: Configuring SAS Digital Marketing

Overview of Configuring the Software

SAS Digital Marketing provides tools to configure the server and middle tiers and to validate yoursoftware installation. You use the SAS Digital Marketing Server Configuration wizard or selectServer Configuration from the Tools menu in SAS Digital Marketing Studio to specify serversettings. The Server Configuration wizard creates Web archive (WAR) files that are deployed onthe middle tier. The Server Configuration wizard can also create a service under the Windowsenvironment that automatically starts the SAS Digital Marketing server.

The middle tier contains the tracking and SAS Digital Marketing Web Studio deployment. Javaservlets on the tracking deployment monitor the broadcast response, process multichannel broad-casts, host broadcast content, and manage Web resources. The Server Configuration wizard createsthe WAR file that contains the servlets (bess.war) for the tracking and Web publication tier. Youdeploy the WAR file on a Web application server that is located outside a corporate firewall. Youcan also use the Servlet Configuration wizard in SAS Digital Marketing Studio to change the prop-erties of the Java servlets. SAS Digital Marketing provides Web pages that enable you to test themiddle tier and update the server to use the Java servlets. For more information, see “Configuringthe Tracking and Web Publication Tier” on page 54.

The Server Configuration wizard also creates the Web archive file (sdm.war) that contains the Javaservlets to run the SAS Digital Marketing Web Studio client. After the WAR file that containsthe servlets is deployed on a Web application server, you can manipulate broadcasts, manage Webresources, and produce advanced broadcast reports in a Web browser. You can locate this Web appli-cation server inside a corporate firewall. To create advanced reports in SAS Digital Marketing WebStudio, you also configure the SAS language adapter and Foundation SAS. For more information,see “Configuring SAS Digital Marketing Web Studio” on page 83.

NOTE: If your site plans to support multiple SAS Digital Marketing Web Studio interactive usersand you plan to generate numerous broadcast reports in batch mode, then you should consider asecond deployment of the WAR file that contains the servlets (sdm.war). You can run the broadcastreports in batch mode on one deployment, and your users can use the second deployment to workinteractively in SAS Digital Marketing Web Studio.

Configuring the SAS Digital Marketing Server

How to Configure the Server

You use the Server Configuration wizard to configure the server on the computer that is runningthe wizard. SAS Digital Marketing stores your configuration settings in the config.xml file that islocated in ROOT/config directory. You should not edit this file directly.

Run the Server Configuration Wizard F 39

NOTE: If a SAS Digital Marketing client is running on a server that you have just configured, then

either restart the client or click Refresh from the toolbar to use the new server settings.

Run the Server Configuration Wizard

To run the Server Configuration wizard, complete the following steps:

1. Start the Server Configuration wizard by selecting the SAS Digital Marketing Configura-tion shortcut from the Start menu under Windows or by running the sconfig shell script underthe UNIX or Linux operating environments.

After the wizard starts, a window appears that lists the pre-installation requirements. In orderto proceed with the configuration, you must provide the location of the license file that wasincluded in your site installation data.

NOTE: If the SAS Digital Marketing server is currently running, then always stop the serverbefore you use the Server Configuration wizard.

2. Click Next after you have reviewed pre-installation requirements. Then specify the locationof the license file and click Next.


SAS Digital Marketing assumes that your license file is located in the ROOT/config direc-tory for the software installation. Click Browse to locate the file in another directory.

NOTE: Your license is distributed with your site installation data and it is found with yourother SAS licenses.

3. Specify the location of the third-party database JDBC JAR files or custom CLASS files.Then click Next. SAS Digital Marketing incorporates these files into the WAR file that tracksbroadcast responses.

NOTE: : You might want custom CLASS files for ASP decoders, Adobe Dreamweaver Snip-pets. or MaxMind extensions.

SAS Digital Marketing can use a database from another vendor, such as MySQL, to trackreplies and responses from a broadcast. If the audit table, response table, or reply tableuse databases other than SAS/SHARE, then you must include JDBC connection third-partyJARs. For each database, you acquire the connection JARs that are required to connect to thatdatabase from Java. For example, DB2 requires the db2jcc.jar file.

To include JARs in the WAR file that contains the servlets, complete the following steps:

a) Click Add JAR.

b) For each database, specify the location of the JAR file in the Open window.

c) Click OK.

To delete a JAR file, select the file in the JARs box and click Remove.


If new JAR or CLASS files are installed on the SAS Digital Marketing server, then these filesare automatically installed on the SAS Digital Marketing Studio client when you connect tothis server. You are asked to restart the SAS Digital Marketing Studio client after the JARfiles are installed.

4. Specify the JDBC connection information for the SAS/SHARE server, SAS WorkspaceServer, or the third-party database server to use in SAS Digital Marketing and click Next.

To specify a new JDBC connection, click Add. To verify the JDBC connection, click Test.For more information, see “Managing the Connections Settings” on page 222.


5. Specify the settings for sending broadcasts and click Next.

You can specify the number of times that SAS Digital Marketing tries to send a broadcastmessage and whether to simulate the broadcast transmission. You can also specify to auto-matically use the opt-out table to filter the e-mail transmission.

For non-Asian languages, use 8-bit as the value for Default mime transfer encoding. SomeAsian languages use 7-bit mime transfer encoding or another other value. For more informa-tion, see MIME (RFC 2045).

Use the E-mail Servers table to verify your outgoing SMTP mail server and add additionale-mail servers. For more information about changing these settings, see “Send Options” onpage 112.


6. Specify the location of the middle tier, or specify that you want to create a new WAR filefor the Java servlets and click Next. The Java servlets collect response metrics for e-mailbroadcasts, process multichannel broadcasts, and manage Web resources.

If the WAR file that contains the Java servlets is already deployed on a Web application server,then select Use an existing tracking deployment. Specify the location of the middle tier byentering the base URL address for the Web application server. To verify that the trackingservlets work correctly, click Test.

If you want to create a new WAR file that contains the servlets for the middle tier, selectCreate a new tracking deployment. You specify settings for the JDBC connection, the linktable, and the opt-out table.


7. If you are creating a new tracking deployment, then specify the JDBC connection informationfor the SAS/SHARE server, SAS Workspace Server, or the third-party database server thatSAS Digital Marketing uses to collects response data and click Next.



8. If you are creating a new tracking deployment, then specify the link table to track the responseto embedded links in the text content and click Next.

Select an existing table, or enter a valid table name for the JDBC provider in the Table box.SAS Digital Marketing automatically creates the table if it is not found. If you want to use adifferent table connection, then use the Connections drop-down list to select the connectiondefinition.

Tracked links in text content can become quite large. Unlike with HTML content, the recipi-ent sees the actual link in the text content. When a tracked link is embedded in the broadcastcontent, SAS Digital Marketing adds the URL to the link table and generates an index. SASDigital Marketing uses the index to shorten the tracked URLs in the text content that a recip-ient receives. The table that contains the links must always be available so that the URLs arefound when a recipient clicks the links.

NOTE: You can set the IndexedLinks server property to use indexed links in HTML content.For more information, see “Response Server Properties” on page 151.

Select Redirect to custom error page if the link table or link is unavailable to specify thelocation of a Web page. This Web page opens when an e-mail recipient clicks an invalid linkor if the link table is not available. You must locate the Web page outside a corporate firewallso that it is available to your e-mail recipients. This Web page also displays when the linktable is inaccessible and the e-mail recipient clicks a tracked link in the e-mail content that isindexed.


9. If you create a new tracking deployment, then specify the opt-out table to record the e-mailaddresses of recipients and click Next. SAS Digital Marketing excludes the e-mail addressesin this table from receiving e-mail transmissions.


If the Automatically apply opt-out table during send processing option is set and SASDigital Marketing records an address in the opt-out table, then no broadcast e-mails are sentto this address. Addresses are recorded in the opt-out table when an e-mail recipient clicksa link in the e-mail message that has the opt-out servlet embedded. This link is created byusing the Insert HTML opt-out link or Insert TEXT opt-out link options in the Insertother expressions dialog box. Addresses are also recorded in the opt-out table when you seta Reply Manager rule threshold. For more information, see “Response Tracking” (Chapter 7,SAS Digital Marketing: User’s Guide).

Select Redirect to custom opt-out notification page to specify the location of a Web pagethat opens when an e-mail recipient decides to opt out of an e-mail broadcast. The Web pageshould include a message that you are processing the request to remove the recipient from themailing list.


10. Specify the settings for e-mail broadcasts and then click Next. For the initial phase of setup,you can use the default values.

You can specify the execution and preview characteristics. To prevent duplicate broadcastsfrom being sent to the same recipient address, you must set the options to create an audittable and record all audit events. You can also configure SAS Digital Marketing to distributethe broadcast transmissions to a grid network. For more information about changing thesesettings, see “E-mail Options” on page 107.

NOTE: If you select the Prevent duplicate e-mails per broadcast option, then SAS DigitalMarketing sends only one broadcast per e-mail address. Therefore, transaction broadcastswork only once for each e-mail address. You can override this duplication policy by settingthe !EM_PREVENT_DUPS! directive to true. For more information about this directive, see“Using E-mail Directives” (Appendix B, SAS Digital Marketing User’s Guide).


11. Specify the settings to log server actions and to create broadcast audit records and then clickNext. For the initial phase of setup, you can use the default values.

You can control when and where SAS Digital Marketing records the audit data. To createaudit records, set the Audit level to all, select Write audit records to a table, and clickConfigure Audit Table to specify the audit table. For more information, see “Logging Op-tions” on page 109.

Select Display server log in the server console window if you want the log informationto appear in this window. The log information is recorded in the ROOT/wrapper.log filewhen the server runs as a Windows service.

NOTE: For the SAS Digital Marketing clients to create reports that access the audit table, youmust specify an explicit host in the JDBC connection definition. Therefore, do not specify aJDBC connection that has localhost as the value in the Connection Definitions dialog box.


12. Specify the settings to process e-mail replies and click Next. You must first provide a POP3or IMAP e-mail account and a JDBC provider to record the reply classification. After thesevalues are set, you can configure the server to periodically download the replies and classifythem.

To configure the e-mail reply account, click Configure Reply Manager. For the SAS Dig-ital Marketing clients to create reports that accesses the reply table, you must specify anexplicit host in the JDBC connection definition. Therefore, do not specify localhost asthe Universal Resource Identifier (URI). For more information, see “E-mail Reply Options”on page 101.

NOTE: Support for IMAP is experimental for this release.


13. Specify the users that can access SAS Digital Marketing and the proxy settings for your siteand then click Next.

To specify the users that can access SAS Digital Marketing, select Basic from the SecurityMode drop-down list. Click Add, Edit, or Remove to create or modify the credentials thatauthenticates a user or a group of users.

To use a metadata server that centralizes the management of user credentials, select metadatafrom the Security Mode drop-down list. SAS Digital Marketing uses the metadata repositoryto authenticate that the user has permission to log on to the SAS Digital Marketing server.You must specify the location of the metadata server and the user credentials for the SASDigital Marketing administrator. For more information, see “Security Options” on page 128.

NOTE: When you use a metadata server for user authentication, SAS Digital Marketinggrants all users Level 3 permission. This level means you cannot stop or configure the SASDigital Marketing server.

To use ASP broadcasts, you must use an Internet proxy and specify the values for the proxyand port.


14. Specify whether to use the TinyMCE HTML editor in SAS Digital Marketing Web Studioand select Next.

If you want to edit the HTML content for a broadcast using the TinyMCE Web-basedJavascript editor, then select Download and install TinyMC third party software. Usethe URL drop-down list to select the location of the installation file. Click Browse to locatethe file in another directory. To use TinyMCE as the HTML content editor in SAS DigitalMarketing Studio, you must also set the WebAppURL server property. For more information,see “Integration Utils Server Properties” on page 141.

NOTE: To download the software, you might need to configure the SAS Digital Marketingserver to use an Internet proxy. Use the previous step to select Use an Internet proxy andspecify your proxy and port settings.


15. Specify the settings to spawn threads and click Next. By default, the broadcast executionruns in multiple threads for efficiency.

You can optimize the e-mail broadcast execution by specifying the number of threads. Youcan also specify the number of asynchronous threads that SAS Digital Marketing uses todeliver spooled SMTP messages to an e-mail server. For more information, see “Adjustingthe SMTP Spooler” on page 263.


16. Print or save the post-configuration checklist and click Finish.

SAS Digital Marketing updates the WAR files for the middle tier. These files are located inROOT/mid directory. You deploy the updated WAR files on a Web application server. Formore information, see

The post-configuration checklist provides a list of steps on how to deploy the WAR files andvalidate your settings. To create a paper copy of the instructions, select Print Check list. Forinformation about creating a sample broadcast to test the server configuration, see “ValidatingYour Configuration” on page 93.

To create a service under the Windows environment that automatically starts the SAS DigitalMarketing server when your computer starts, select Register SAS Digital Marketing as aWindows Service.


Configuring the Tracking and Web Publication Tier

How to Configure the Middle Tier

You deploy a WAR file that contains the tracking and Web publication serlvets on a Web applicationserver. SAS Digital Marketing uses this deployment to process Java servlet requests and host yourWeb resources. The Web application server must be visible to your intended e-mail recipients, solocate the server outside any corporate firewalls. SAS Digital Marketing supports deployment ofthe WAR file on BEA WebLogic, Apache Tomcat, and IBM WebSphere.

If you used the Server Configuration wizard to create a new tracking deployment, then a new WARfile that contains the servlets is automatically created. You can also use the Servlet Configura-tion wizard to change settings for the broadcast response tracking servlets or to configure the Webpublication servlets. For more information, see “Reconfiguring the Tracking Servlets” on page 71.

SAS Digital Marketing stores the servlet settings in the web.xml file in the updated WAR file thatcontains the servlets (bess.war). The file is located in the ROOT/deployments directory on thecomputer that was used to configure SAS Digital Marketing. After the WAR file is deployed, youcan use SAS Digital Marketing Web pages to test Java servlets on the middle tier. You can alsoupdate the SAS Digital Marketing server to use the Java servlets that you just tested.

NOTE: If you configure the Web publication servlets to use HTTP proxy settings, then you deployone WAR file that contains the servlets inside the corporate firewall that omits proxy URLs. You de-ploy another WAR file that the includes a proxy URL for the servlets outside the corporate firewall.For more information, see “Configuring a Proxy Server” on page 79.

Deploying the Servlet WAR File

After the Java servlets are configured, you can deploy one of the following Web application servers:

� BEA WebLogic

� Apache Tomcat

� IBM WebSphere

NOTE: You must deploy the WAR file that contains the servlets on a Web application server outsidea corporate firewall and make the server visible to the intended recipients of your broadcasts.

Deploying the Servlet WAR File F 55

Deploy to BEA WebLogic

To deploy the WAR file to a BEA WebLogic server, use the WebLogic Server Console to completethe following steps:

1. Click Deploy a new Web application Module from the Deployments node.

2. Click upload your file(s) in the Deploy a Web application Module pane.


3. Click Browse to locate the bess.war file that you configured with the Server or Servlet Con-figuration wizard. Then click Upload.

4. Navigate to the uploaded bess.war file, select it, and click Target Module.


5. Use the default name of bess and click Deploy.

WebLogic deploys the WAR file that contains the servlets. Now, test that the Java servlets havestarted. For more information, see “Verify the Tracking Servlets” on page 68.

Deploy to Apache Tomcat

To deploy the WAR file that contains the servlets to a Tomcat 4.1 server, copy the WAR file tothe webapps folder of the Tomcat installation and restart Tomcat. The name of the folder forthe Tomcat installation must not include any blank spaces. Upon restarting, Tomcat unpacks thebess.war file and configures the Java servlets for use. Now, test that the servlets have started. Formore information, see “Verify the Tracking Servlets” on page 68.


If you run Tomcat with the -security option, then make the following change in$CATALINA_HOME/conf/catalina.policy file:

grant codeBase "file:${catalina.home}/webapps/sdm/-"{permission java.security.AllPermission;};

grant codeBase "file:${catalina.home}/webapps/bess/-"{permission java.security.AllPermission;};

Restart Tomcat to use the new configuration option.

Deploy to IBM WebSphere

To deploy the WAR file that contains the servlets to an IBM WebSphere server, use the WebSphereAdministrative Console to complete the following steps:

1. Expand the Applications node in the Administrative Console and open Install New Appli-cation. In the Preparing for the application installation pane, specify the location of theWAR file. Specify the name bess in the Context Root box and click Next.


2. Click Next in the Preparing for the application installation pane to use the default values.


3. Click Continue in the Application Security Warnings pane.


4. Click Next to use the default values for Step 1 in the Install New Application pane.


5. Select the check box for SAS Digital Marketing Tracking Servlets, and click Next to usedefaults_host for Step 2.


6. Select SAS Digital Marketing Tracking Servlets check box, specify the Web applicationserver for the middle tier and click Apply. Click Next to use defaults_host for Step 3.


7. Click Finish in the Install New Application pane.


8. Click Save to Master Configuration after the WAR file is installed.


9. Click Save.

Testing the Tracking Servlets F 67

10. To start the Java servlets, expand the Applications node in the Administrative Console andselect Enterprise Applications. In the application list, check bess.war and click Start.

Now test that the servlets have started. For more information, see “Verify the Tracking Servlets” onpage 68.

Testing the Tracking Servlets

You use the SAS Digital Marketing Tracking Servlets Test page to verify the deployment of the mid-dle tier and test the Java servlets. After you verify the deployment, update a SAS Digital Marketingserver to use the tracking servlets.


Verify the Tracking Servlets

To run the Tracking Servlets Test page, complete the following steps:

1. Open a Web browser.

2. Append /test to the Web address for the root URL of the BESS deployments. For example,if your BESS deployments are located at http://appserver.com/bess, then the testURL is http://appserver.com/bess/test. If the Java servlets are running on themiddle tier, then the following test page appears:

NOTE: When a servlet does not start, stop and restart the Web application server, and then restartthe servlet.

Testing the Tracking Servlets F 69

Test the Crumb Servlet

To test the crumb servlet, complete the following steps:

1. Under Crumblet Tester, specify the broadcast events table in the Table box.NOTE: Your database vendor might require that you specify both a database name andtable name, such as Test.Responses. If the database name is omitted for some ver-sions of MySQL, then you receive a No database specified error.

2. Specify the identification number in the ClientID box. SAS Digital Marketing writes arecord to the specified response table. The record contains the identification number.

3. Click Test Crumblet Servlet to run the servlet and to create a 1x1 GIF image similar tothe image that SAS Digital Marketing embeds in the e-mail content.

NOTE: View events are not tracked for users of AOL 5.0. Therefore, the crumb servlet is notused. For users of AOL 6.0 and later, view events are treated as HTML.

When the test is successful, the Web page indicates that the crumblet servlet was successfullyinvoked. Likewise, the response table is created on the JDBC connection that you specified inthe Servlet Configuration wizard. This table should contain a row that includes the ClientIDand a preview click event (pclick) as the broadcast response. If JMS is configured, thenJMS listeners also receive a pview event that embeds the ClientID as a property. For moreinformation, see “Overview of JMS” on page 269.

Test the Redir Servlet

To test the redir servlet, complete the following steps:

1. Under Redirect Tester, specify the URL of the target Web page in the TargetURL box. For example, to use the SAS Web page as your target URL, specifyhttp://www.sas.com.

2. Specify the name of the table for broadcast events in the Table box.NOTE: Your database vendor might require that you specify both a database name andtable name, such as Test.Responses. If the database name is omitted for some ver-sions of MySQL, then you receive a No database specified error.

3. Specify the identification number in the ClientID box. SAS Digital Marketing writes arecord that contains the identification number to the specified response table.

4. Click Test Redirect Servlet to run the servlet.

When the test is successful, the Web page for the target URL displays. Likewise, the responsetable is created on the JDBC connection that you specified in the Servlet Configuration wizard.This table contains a row that includes a link to the target URL, the ClientID value, and apview event as the broadcast response. If JMS is configured, then JMS listeners receive apclick event that embeds the target URL link and the ClientID as the properties. For moreinformation, see “Types of Response Events” (Chapter 7, SAS Digital Marketing: User’sGuide).

To view the response table, use the JDBC Table Viewer that is included in the SAS Digital Market-ing. For more information, see “Using the JDBC Table Viewer” (Chapter 2, SAS Digital Marketing:User’s Guide).


Updating the Server

After you verify the deployment of the middle tier, use the Configure the SAS Digital MarketingTracking and Web Publication Tier page to quickly update a SAS Digital Marketing server. Youmust deploy the WAR file on a Web application server that is located outside a corporate firewall.

Assign the Tracking and Web Publication Tier Location

To run the Configure the SAS Digital Marketing Tracking and Web Publication Tier page, completethe following steps:

1. Open a Web browser.

2. Append /config to the Web address for the root URL of the BESS deployments. Forexample, if your BESS deployments are located at http://appserver.com/bess, thenthe test URL is http://appserver.com/bess/config.

3. Specify the location of the SAS Digital Marketing server.

4. Specify the user credentials to log on to the server.

Reconfiguring the Tracking Servlets F 71

5. Click Update to configure the server. When you receive the message that the middle tier issuccessfully updated on the server, click Close.

To verify that SAS Digital Marketing server is correctly updated, use the Server Configurationwindow. For more information, see “Middle Tier Options” on page 125.

Reconfiguring the Tracking Servlets

The Servlet Configuration wizard enables you to change the settings of the broadcast tracking andWeb publication servlets. After the WAR file that contains the servlets is modified, you must deploythe bess.war file to a Web application server.

Run the Servlet Configuration wizard

To run the Servlet Configuration wizard, complete the following steps:

1. Start a SAS Digital Marketing Studio client, and connect to the SAS Digital Marketing server.Then select Servlet Configuration from the Tools menu.

2. Specify the location of the bess.war file and click Next.


3. Specify the JDBC connection information for the SAS/SHARE server, SAS WorkspaceServer, or the third-party database server that SAS Digital Marketing uses to collect responsedata and click Next.


Select Turn on servlet debug mode to write debug messages to the Web server log. Debuginformation is written to the log when a recipient opens e-mail that contains a crumb or whena recipient clicks a link that is tracked. This option also enables you to access an exceptionlog from the Tracking Servlets Test page. For more information, see “Verify the TrackingServlets” on page 68.


4. Specify the link table to track the response to embedded links in the text content and clickNext.


Tracked links in text content can become quite large. Unlike with HTML content, the recipi-ent sees the actual link in the text content. When a tracked link is embedded in the broadcastcontent, SAS Digital Marketing adds the URL to the link table and generates an index. SASDigital Marketing uses the index to shorten the tracked URLs in the text content that a recip-ient receives. The table that contains the links must always be available so that the URLs arefound when a recipient clicks the links.

NOTE: You can set the IndexedLinks server property to use indexed links in HTML content.For more information, see “Response Server Properties” on page 151.

Select Redirect to custom error page if the link table or link is unavailable to specify thelocation of a Web page that opens when an e-mail recipient clicks a link that is not available.You must locate the Web page outside a corporate firewall so that it is available to your e-mail recipients. This Web page also displays when the link table is inaccessible and the e-mailrecipient clicks a tracked link in the e-mail content that is indexed.


5. Specify the opt-out table to record the e-mail addresses of recipients that you want excludedfrom receiving e-mail transmissions and click Next.


If the Automatically apply opt-out table during send processing option is set and SASDigital Marketing records an address in the opt-out table, then no broadcast e-mails are sentto this address. SAS Digital Marketing records e-mail addresses in the opt-out table when youuse the Insert HTML opt-out link and Insert TEXT opt-out link options in the Insert otherexpressions dialog box. The opt-out servlet is embedded in the broadcast message. Addressesare also recorded in the opt-out table when you set a Reply Manager rule threshold. For moreinformation, see “Response Tracking” (Chapter 7, SAS Digital Marketing: User’s Guide).

Select Redirect to custom opt-out notification page to specify the location of a Web pagethat opens when an e-mail recipient decides to opt-out of an e-mail broadcast. The Web pageshould include a message that you are processing the request to remove the recipient from themailing list.


6. Specify the location of the third-party database JDBC JAR files. SAS Digital Marketing usesthe JAR files to connect to your database server in order to write response records. Alsospecify the location of any third-party JMS JAR files that SAS Digital Marketing needs toconnect to a JMS provider. Then click Next.

SAS Digital Marketing can use a database from another vendor, such as MySQL, to trackreplies and responses from a broadcast. If the audit table, response table, or reply table usedatabases other than SAS/SHARE, then you must include JDBC connection third-party JARs.For each database, acquire the connection JARs that are required to connect to that databasefrom Java. For example, DB2 requires the db2jcc.jar file. To connect to the server with thedata table, specify the location of the JAR file that provides the JDBC connectivity.

SAS Digital Marketing can use JMS to process responses in real time. JMS might need athird-party JAR file to connect to the JMS Queue or to the JMS Topic that you post broad-cast events to. For example, if you use JMS with WebLogic as a JMS provider, then thewljmsclient.jar file is required when you deploy other Web application servers. For moreinformation, see “Overview of JMS” on page 269.


To include JARs in the WAR file that contains the servlets, complete the following steps:

a) Click Add JAR.

b) For each database, specify the location of the JAR file in the Open window.

c) Click OK.

To delete a JAR file, select the file in the JARs box and click Remove.

7. Specify URLs for the HTTP proxies. Then click Next.

HTTP proxy settings enhance the security of your network. The number of open HTTPconnections are limited between the SAS Digital Marketing server and the Web applicationserver outside your corporate firewall. SAS Digital Marketing uses a proxy server inside yourfirewall to process the requests that are received from the Java servlets.


To include an HTTP proxy in the WAR file, complete the following steps:

a) Click Add Proxy.

b) Specify the URL in the Enter proxy URL window.

c) Click OK.

To delete a proxy setting, select the name of the proxy in the URL in the Proxies box andclick Remove.

NOTE: To use HTTP proxy settings, you deploy two versions of the WAR file. This config-uration of the WAR file is deployed outside the corporate firewall. For more information, see“Configuring a Proxy Server” on page 79.

8. Decide whether you want to use JMS for real-time broadcasts and specify the JMS configu-ration. Then click Next.


9. Specify the location to store the updated bess.war file and click Finish.

You are now ready to deploy the WAR file that contains the servlets to your Web application serveron the middle tier. For more information, see “Deploying the Servlet WAR File” on page 54 and“Updating the Server” on page 70.

Configuring a Proxy Server F 79

Configuring a Proxy Server

When SAS Digital Marketing uses a middle tier to deliver message content, manage RRS feeds,and host Web resources, you can configure a WAR file that contains servlets to use a proxy server toprocess the HTTP requests. You improve network security by restricting connectivity between theSAS Digital Marketing server inside your corporate firewall and the Web application server outsideyour corporate firewall. The Java RMI technology that SAS Digital Marketing uses for remoteclient communication is prevented from randomly opening multiple ports and connections whenHTTP requests are received. By configuring a WAR file to use HTTP proxy settings, you limit theHTTP requests to a specified set of ports.

To use a proxy server, you create two middle tier deployments:

� a Web application server inside the corporate firewall with a WAR file that omits proxy URLs.This becomes the proxy server.

� a Web application server outside the corporate firewall with a WAR file that specifies at leastone port connection to the proxy server.

Deploy the Proxy Server

To deploy a proxy server, complete the following steps:

1. Use the Server Configuration wizard to create a new WAR file called bess.war.

For more information, see “Run the Server Configuration Wizard” on page 39.

2. Deploy this WAR file on a Web application server that is located inside your corporate fire-wall. For more information, see “Deploying the Servlet WAR File” on page 54.

3. After you test the tracking servlets, update the SAS Digital Marketing server to use the track-ing and Web publication tier. For more information, see “Updating the Server” on page 70.


4. In SAS Digital Marketing Studio, use the Servlet Configuration wizard to reconfigure theWAR file that contains the servlets to use HTTP proxy settings. Select Servlet Configu-ration from the Tools menu. Except for the HTTP proxy settings, click Next to use theexact settings of the WAR file that you deployed on the Web application server inside yourcorporate firewall.

To specify the port connections for the proxy server, complete the following steps:

a) Click Add Proxy.

b) Specify the URL for the proxy server in the Enter proxy URL window. This value isthe URL address for the tracking and Web publication tier that you deployed on a Webapplication server inside your corporate firewall.

c) Click OK.

For more information, see “Run the Servlet Configuration wizard” on page 71.

5. After you finish the steps of the Servlet Configuration wizard, deploy the WAR file that con-tains the servlets to a Web application server that is located outside your corporate firewall.

Configuring a Proxy Server F 81

6. Open the proxy server’s Web application port between the tracking deployments that areinside and outside your corporate firewall.

7. In SAS Digital Marketing Studio, open the Server Configuration window by selecting ServerConfiguration from the Tools menu. Select Middle Tier Options, and specify the base URLfor the tracking deployment that is located outside your corporate firewall. To verify that thetracking servlets work correctly, click Test.


8. Verify that your hosted Web resources and broadcast definitions access content on the middletier. Use the Web tab on the Properties dialog box for a broadcast definition or hosted Webresource.

To test a hosted Web resource, complete the following steps:

a) In SAS Digital Marketing, select the Web Resources tab to locate a hosted resource.

b) Open the HTML subfolder under the Samples folder.

c) Select an HTML file and right-click to select Properties from the pop-up menu.

d) Select the Web tab and click Test to verify that the SAS Digital Marketing server re-ceived the HTTP request from the middle tier.

For more information, see “Viewing the Web Resources” (Chapter 2, SAS Digital Marketing:User’s Guide).

Configuring SAS Digital Marketing Web Studio F 83

Configuring SAS Digital Marketing Web Studio

How to Configure the Web Application

The SAS Digital Marketing Configuration wizard automatically creates the WAR file that you needto use SAS Digital Marketing Web Studio. The configuration settings are stored in the sdm.warfile. This file is located in the ROOT/deployments directory on the computer that was used toconfigure SAS Digital Marketing.

After the WAR file is deployed, you can use the SAS Digital Marketing Web Studio client to auto-matically set the WebAppURL server property to the location of this deployment. This enables aSAS Digital Marketing Studio client to use the TinyMCE HTML editor to edit HTML content, toview visual reports, and to run advanced Web reports. For more information, see “Integration UtilsServer Properties” on page 141.

NOTE: You do not need SAS Digital Marketing installed on your computer to use SAS DigitalMarketing Web Studio. However, the SAS Digital Marketing Web Studio client must have theability to connect to a SAS Digital Marketing server.

Deploying the Web Studio WAR File

You must deploy the sdm.war file on a Web application server, such as Tomcat, WebLogic, orWebSphere, that is inside the corporate firewall. The steps to deploy the file are similar to those forconfiguring the tracking and Web publication tier. You use sdm rather than bess for the name ofthe Web application module in WebLogic or the context root in WebSphere. Tomcat automaticallyuses sdm as the Web application unless you renamed the sdm.war file. For more information, see“Deploying the Servlet WAR File” on page 54.

Updating the Server To Use Web Studio

You can use the Configure SAS Digital Marketing Server for Web Reporting page to quickly setthe WebAppURL server property to use the URL for the deployment of the SAS Digital MarketingWeb Studio. After the server is updated, you can select Run Visual Report from the Actions menuin SAS Digital Marketing to view a visual click-through report for an e-mail broadcast.


Configure the Web Studio Server

To update the server, complete the following steps:

1. Log on to SAS Digital Marketing Web Studio with administrative privileges (Level 4 per-mission). For more information, see “Open Web Studio” (Chapter 2, SAS Digital Marketing:Web Studio User’s Guide).

2. Click on the toolbar.

3. Specify the location of the SAS Digital Marketing server.

4. Specify the user credentials to log on to the server.

5. Click Update to configure the server.

6. After you receive the message that SAS Digital Marketing server is successfully updated,click Close.

Implementing the Broadcast Scheduler F 85

Implementing the Broadcast Scheduler

To schedule broadcasts in SAS Digital Marketing Web Studio, you must configure the SAS DigitalMarketing server to allow scheduling through the SAS Digital Marketing client. For more informa-tion, see “Scheduling Options” on page 117.

You must configure the SAS Digital Marketing server to enable Web Studio users to specify broad-cast recipients by using one of the following methods:

� an uploaded recipient file

� a table

� a distribution list

If you do not use one these methods to configure SAS Digital Marketing Web Studio, then thescheduling functionality is not available.

NOTE: You can also configure a global data model to simplify the underlying structure of the datasource for a broadcast. For more information, see “Managing Global Data Models” on page 166.

Schedule Broadcasts with an Uploaded Recipient File

The TempTable server properties enable you to execute from a file. If you set the TempTableserver properties to a valid JDBC connection, then you can schedule to send a broadcast to a list ofrecipients in a specified file. The list of recipients in this file must be separated by a new line.

For example, you might set the following server properties:

TempTableDriver=com.mysql.jdbc.DriverTempTableURI=jdbc:mysql://machine.na.sas.com:3306/TempTableUser=validuseridTempTablePassword=validpasswordTempTableBaseName=library.tablebase

In this example, SAS Digital Marketing checks the file for valid addresses as the file is uploaded toa temporary table with a base name of tablebase. The table is stored in the database that is definedby these server properties. For more information, see “Properties for Executing from a File” onpage 143.


Schedule Broadcasts from a Table

You set the WebSelectionTable server properties to specify the location of a valid JDBC connectionand library. Web Studio users schedule a broadcast transmission by selecting a table from the database that is located in the specified library.

For example, you might set the following server properties:

WebSelectionTableDriver=com.mysql.jdbc.DriverWebSelectionTableURI=jdbc:mysql://machine.na.sas.com:3306/WebSelectionTableUser=validuseridWebSelectionTablePassword=validpasswordWebSelectionTableLibrary=library

In this example, the scheduling functionality in SAS Digital Marketing Web Studio displays the listof tables in the library specified in the WebSelectionTableLibrary server property. You can thenselect the table that contains the list of broadcast recipients. For more information, see “Propertiesfor Executing from a Table” on page 143.

Schedule Broadcasts Using a Distribution List

You can also use distribution lists to schedule the broadcast. If only distribution lists are definedon the server, then you see only the option to schedule to a distribution list. For more informationabout creating a distribution list, see “Managing Distribution Lists” on page 158.

Implementing the SAS Language Adapter

Requirements for the SAS Language Adapter

The SAS language adapter enables you to easily access SAS Digital Marketing data and broadcastdefinitions within SAS ETL processes. The adapter also eliminates the need to make separateconnections to the different databases that store SAS Digital Marketing data. The SAS DigitalMarketing server becomes the access point for all SAS Digital Marketing data. A user simplylogs on to the SAS Digital Marketing server to retrieve the response data that is associated witha broadcast definition. For more information, see “Overview of the SAS Language Adapter” onpage 190.

Implementing the SAS Language Adapter F 87

The following software is required to use the SAS language adapter:


� a SAS Digital Marketing server

� SAS Digital Marketing Web Studio

� IOM workspace server (optional)


NOTE: To generate SAS reports in an Asian language, install Foundation SAS to use UTF-8 en-coding and set the locale of the SAS session to the Asian country.

You can run your SAS jobs either in batch mode or by using an IOM workspace server. An IOMworkspace server is recommended if your site has more than five users generating reports simulta-neously. If you choose to use the workspace server, then this server must be running.

For information about how to configure the IOM workspace server, see the SAS 9.1.3 IntegrationTechnologies Administrator’s Guide at http://support.sas.com/rnd/itech/doc9/admin_oma/sasserver/iombridge/iom_quicko.html.

For an example of a configuration file, see http://support.sas.com/rnd/itech/doc9/admin_ldap/sasserver/iombridge/ldifsamp.html.

SAS Digital Marketing ships with server properties that the site administrator can use to optimizethe performance of your IOM sessions or batch sessions. For information about these properties,see “Optimize Server Properties” on page 144.

Configure the SAS Language Adapter

To run a SAS job in SAS Digital Marketing, complete the following steps:

1. Verify that the sdm.war file is deployed on a Web application server. For more information,see “Configuring SAS Digital Marketing Web Studio” on page 83.

2. If you want to execute SAS jobs on an IOM workspace server, start the workspace server.

3. Select Server Configuration from the Tools menu and select the SAS options node.

4. Use the Integrated Execution Context drop-down list to select how you want to run the SASjobs from SAS Digital Marketing.

If you run SAS jobs in batch mode, then select Batch SAS and type the path of the SASexecutable in SAS Command Line box.

If you run the SAS jobs on the IOM workspace server, then select Workspace Server andspecify the name of the workspace server. You must also specify your username and passwordfor that server.

http://support.sas.com/rnd/itech/doc9/admin_oma/sasserver/iombridge/iom_quicko.html

http://support.sas.com/rnd/itech/doc9/admin_ldap/sasserver/iombridge/ldifsamp.html

http://support.sas.com/rnd/itech/doc9/admin_oma/sasserver/iombridge/iom_quicko.html

http://support.sas.com/rnd/itech/doc9/admin_ldap/sasserver/iombridge/ldifsamp.html


5. Click Test SAS Connection to verify that the SAS connection works.

NOTE: If you have registered SAS Digital Marketing as a Windows service and your SASconnection fails, then you might have to modify the properties of the service to specify theaccount and password that run the service. For more information, see “Configure a WindowsService” on page 95.

6. Select the Execute batch jobs periodically check box if you want to run the SAS job at aregular interval. You can specify the minutes between runs.

7. Customize the output from the SAS jobs. Use ODS Style to specify the style of the HTMLoutput. Use Graph Device to specify the graphical output format.

NOTE: If Java is selected as the graph device, then make sure that you apply the patches fromSAS Notes SN-V9-017502 and SN-V9-017593 to Foundation SAS. For more information,see http://support.sas.com/techsup/search/sasnotes.html.

NOTE: Depending on the graph device that you select, SAS Digital Marketing Web Studiousers might need to install additional software to view the graphical output from SAS reports.For more information, see “Requirements for Viewing SAS Reports” (Chapter 2, SAS DigitalMarketing: Web Studio User’s Guide).

8. Click OK.

You manage your SAS jobs from the SAS Job Editor. For more information, see “Developing SASCode” on page 195.

Configuring SAS Information Delivery Portal

About SAS Information Delivery Portal

SAS Information Delivery Portal is a J2EE Web application that enables you to aggre-gate data from a variety of sources and present the data in a Web browser. For more in-formation about SAS Information Delivery Portal, see the SAS Information Delivery Por-tal Help, which is available from within the product. For additional information, see theSAS Intelligence Platform: Web Application Administration Guide, which is available athttp://support.sas.com/documentation/configuration/913admin.html.

Add a Link to SAS Digital Marketing F 89

Add a Link to SAS Digital Marketing

To use SAS Digital Marketing from SAS Information Delivery Portal, you create a portal contentitem that is accessed by using a URL. To create a new link and add it to a collection portlet, completethe following steps:

1. Create a Level 1 user account on the SAS Digital Marketing server. You use this accountto view reports for the broadcast definitions on the SAS Digital Marketing server. In SASDigital Marketing Studio, select Server Configuration from the Tools menu. Then selectSecurity Options from the Server node and click Add to specify the user credentials. Formore information, see “Security Options” on page 128.

2. Verify that the sdm.war file has been deployed on a Web server such as Tomcat, WebLogic,or WebSphere. For more information, see “Configuring SAS Digital Marketing Web Studio”on page 83.

3. Log on to SAS Information Delivery Portal as a Content Administrator.

4. Select Create New Content from the Options menu.


5. Select Link and click Create from the Create New Content page.

6. Create the link that displays the broadcast groups and broadcast definitions. You must specifya name for the link and a URL. The description of the link and the keywords are optional.

For the URL, specify following the syntax:

http://deployedhost:port/sdm/weblist.jsp?noheader&server=server&user=user_id&password=pw

where

deployedhostis the location of server that is running the SAS Digital Marketing Web Studio deploy-ment. For more information, see “Configuring SAS Digital Marketing Web Studio” onpage 83.

serveris the location of the SAS Digital Marketing server that you use to store the broadcastsdefinitions.

user and passwordare the user credentials to log on to the SAS Digital Marketing server. Use the Level 1user account that you created.

Add a Link to SAS Digital Marketing F 91

7. Specify the groups of users that have access to the reports. Select PUBLIC from the Location(group) drop-down list and click Create.

8. Verify that the link is available. Click Done twice, and click Search on the SAS Portal homepage. Then specify the link name in the Keywords box, select Link in the Content Typesbox, and click Search to display the link.


9. Create a bookmark. Click and select Bookmark from the pop-up menu.

10. Log on to SAS Information Delivery Portal to open your personal portal. The link is nowavailable in the Bookmarks list.

Validating Your Configuration F 93

11. Click SAS Digital Marketing Reports to use Web Studio to create broadcast reports. Formore information, see “Monitoring Broadcasts in Web Studio” (Chapter 2, SAS Digital Mar-keting: Web Studio User’s Guide).

Validating Your Configuration

Create a Sample Data Table

When you edit, preview, or schedule a sample broadcast definition, SAS Digital Marketing auto-matically selects the sample data table in the specified library as the data source table.

To create a sample data source table, complete the following steps:

1. Start a SAS Digital Marketing Studio client, and connect to the SAS Digital Marketing server.For more information, see “Running SAS Digital Marketing” (Chapter 2, SAS Digital Mar-keting: User’s Guide).


2. Select Create Sample Table from the Tools menu. The Create Sample Table dialog boxopens.

3. Use the drop-down list to select the JDBC connection. If you want to use a different tableconnection, then use the Connections drop-down list to select the connection definition.

4. Select the location of the library, and enter the table name in the Table box.

NOTE: The examples in the documentation use the EXAMPLES library for the location ofthe data tables.

5. Click OK.

6. If the data source table already exists, then confirm that you want to replace it.

You can also create the sample data table by running the CONTACT_DETAILS.SAS program inthe ROOT/samples directory. Modify the program to include a LIBNAME statement that usesexamples as the libref. Then submit the program in a SAS session that runs on a SAS/SHAREserver. For more information about how to start a SAS/SHARE server, see the SAS SHARE User’sGuide.

Preview a Sample Broadcast

SAS Digital Marketing provides sample broadcast definitions in the ROOT/broadcast/samplesdirectory that you can use to validate your SAS Digital Marketing configuration settings. Thesebroadcast definitions use the sample data source table that is created selecting Create Sample Tablefrom the Tools menu.

Configure a Windows Service F 95

To preview a sample broadcast definition, complete the following steps:

1. Start a SAS Digital Marketing Studio client, and connect to the SAS Digital Marketing server.For more information, see “Running SAS Digital Marketing” (Chapter 2, SAS Digital Mar-keting: User’s Guide).

2. Select the AML Report - January 2004 broadcast definition in the E-mail folder under theBroadcasts folder.

3. Select Preview from the Actions menu or right-click to select Preview from the pop-upmenu. The Preview Broadcast wizard opens.

4. Click Next to use the sample data source table.

5. Specify an e-mail address to receive the sample broadcast. To set the number of entries inthe data source table that SAS Digital Marketing uses to create e-mail messages, change thevalue in the Sample size box.

6. Click Finish to close the wizard and send the broadcast.

7. Select the Log tab to verify that the broadcast transmission was sent. Check the Inbox for thee-mail address of the preview broadcast to verify that e-mail messages were received.

Configure a Windows Service

You can register SAS Digital Marketing as a service under the Windows environment. Then theSAS Digital Marketing server and grid nodes automatically start when your computer starts. Theservice is set up as a local system account that runs the application in the background. The finalstep in the SAS Digital Marketing Configuration wizard provides an option to configure a servicethat starts the server. To manually configure the service, complete the following steps:

1. Install and configure SAS Digital Marketing as described in “Installing a SAS Digital Market-ing Server” on page 26. Then validate your SAS Digital Marketing installation and the con-figuration settings. For more information, see “Validating Your Configuration” on page 93.

2. Verify that the service batch files properly start the server or grid node. You can run thesem.bat file or the semgridnode.bat file. Both files are located in ROOT directory.

3. After you have verified that the SAS Digital Marketing server is running, start a SAS DigitalMarketing client as described in “Running SAS Digital Marketing” (Chapter 2, SAS DigitalMarketing: User’s Guide). Then stop the server by selecting stop from the Actions menu, or

click stop on the toolbar.


4. Register the batch files as a service. Run either the SEMInstallApp-NT.bat file or theSEMGridNodeInstallApp-NT.bat file.

5. Restart your computer to start the service.

NOTE: To unregister the service, run either the SEMUnInstallApp-NT.bat file or theSEMGrideNodeUninstallApp-NT.bat file. The SAS Digital Marketing server or grid nodewill no longer start when the computer initializes.

For more information about troubleshooting problems, see the Java Service Wrapper documentationat http://wrapper.tanukisoftware.org/doc/english/index.html.

Chapter 4

Customizing the Server

ContentsOverview of Customizing the Server . . . . . . . . . . . . . . . . . . . . . . . . . 99Using the Server Configuration Window . . . . . . . . . . . . . . . . . . . . . . . 99

Open the Server Configuration Window . . . . . . . . . . . . . . . . . . . . 99Server Configuration Window Components . . . . . . . . . . . . . . . . . . 99

E-mail Reply Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101About E-mail Reply Options . . . . . . . . . . . . . . . . . . . . . . . . . . 101Configuring E-mail Replies . . . . . . . . . . . . . . . . . . . . . . . . . . 101

JMS Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102About JMS Configuration Options . . . . . . . . . . . . . . . . . . . . . . . 102Configuring JMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

SAS Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103About SAS Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Configuring SAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

ASP Definition Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105About the ASP Definition Manager . . . . . . . . . . . . . . . . . . . . . . 105Configuring an ASP Definition . . . . . . . . . . . . . . . . . . . . . . . . 105

Distribution List Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106About the Distribution List Manager . . . . . . . . . . . . . . . . . . . . . 106Configuring a Distribution List . . . . . . . . . . . . . . . . . . . . . . . . 106

E-mail Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107About E-mail Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Configuring E-mail Broadcasts . . . . . . . . . . . . . . . . . . . . . . . . 107Specifying Grid Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Logging Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109About Logging Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Customizing the Audit Records . . . . . . . . . . . . . . . . . . . . . . . . 110Define the Audit Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Send Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112About Send Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Configuring the Broadcast Transmission . . . . . . . . . . . . . . . . . . . 112Configuring SMTP E-mail Servers . . . . . . . . . . . . . . . . . . . . . . 113

Performance Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115About Performance Options . . . . . . . . . . . . . . . . . . . . . . . . . . 115Configuring the Performance . . . . . . . . . . . . . . . . . . . . . . . . . 115

98 F Chapter 4: Customizing the Server

Throttled Domain Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116About the Throttled Domain Manager . . . . . . . . . . . . . . . . . . . . . 116Configuring Throttled Domains . . . . . . . . . . . . . . . . . . . . . . . . 117

Scheduling Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117About Scheduling Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Configuring the Broadcast Scheduler . . . . . . . . . . . . . . . . . . . . . 118Using a Notification List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

WAP Integration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119About WAP Integration Options . . . . . . . . . . . . . . . . . . . . . . . . 119Configuring the WAP Integration . . . . . . . . . . . . . . . . . . . . . . . 119

Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120About Web Services Specifications . . . . . . . . . . . . . . . . . . . . . . 120Configuring Web Services Specifications . . . . . . . . . . . . . . . . . . . 120

Contact History Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121About Contact History Options . . . . . . . . . . . . . . . . . . . . . . . . 121Configuring Contact History . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Response History Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122About Response History Options . . . . . . . . . . . . . . . . . . . . . . . 122Configuring Response History . . . . . . . . . . . . . . . . . . . . . . . . . 123

Connection Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124About Connection Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Configuring the Connections . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Middle Tier Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125About Middle Tier Options . . . . . . . . . . . . . . . . . . . . . . . . . . 125Configuring the Middle Tier . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Advanced Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126About Advanced Server Properties . . . . . . . . . . . . . . . . . . . . . . 126Configuring the Advanced Server Properties . . . . . . . . . . . . . . . . . 126Viewing the Advanced Server Properties Settings . . . . . . . . . . . . . . . 127

Security Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128About Security Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Types of Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Basic Security Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Metadata Security Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131User Group Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Overview of Customizing the Server F 99

Overview of Customizing the Server

You can use the Server Configuration window to customize the SAS Digital Marketing server.The server configuration affects the creation, transmission, and analysis of broadcasts. It also af-fects control of SAS Marketing Automation integration, JDBC connections, the location of themiddle tier, and server access. SAS Digital Marketing stores server configuration settings in theconfig.xml file that is in the ROOT/config directory on the server that you are connected to.You should not edit this file directly.

Using the Server Configuration Window

Open the Server Configuration Window

To open the Server Configuration window, start a SAS Digital Marketing Studio client and connectto the SAS Digital Marketing server as an administrator. In SAS Digital Marketing Studio, selectServer Configuration from the Tools menu.

Server Configuration Window Components

The left pane of the Server Configuration window displays a hierarchical view of the server settingsthat are categorized by the function of an option. To examine or change a server setting, click oneof the following options:

� Broadcast Analysis

– E-mail Reply Options

– JMS Configuration Options

– SAS Options

� Broadcast Definition

– ASP Definition Manager

– Distribution List Manager

– E-mail Options


� Broadcast Transmission

– Logging Options

– Send Options

– Performance Options

– Throttled Domain Manager

– Scheduling Options

– WAP Integration Options

� Customer Intelligence

– Web Services

– Contact History Options

– Response History Options

� Server

– Connection Options

– Middle Tier Options

– Advanced Server Properties

– Security Opitons

Configuring E-mail Replies F 101

E-mail Reply Options

About E-mail Reply Options

You use E-mail Reply options to specify how to process broadcast replies. You must first providea POP3 or an IMAP e-mail account and a JDBC provider to record the reply classification. Afteryou provide these settings, you can configure the server to periodically download the replies andclassify them.

To view these options, select Tools!Server Configuration!E-mail Reply Options.

Configuring E-mail Replies

To automatically process replies, select Automatically check for and process e-mail replies. Youcan create two types of replies: correlated and uncorrelated. A correlated reply uses a unique e-mailaddress for each broadcast definition so that the broadcast is automatically connected to the reply.An uncorrelated reply uses the same e-mail address for every broadcast. For more information, see“Working with the E-mail Reply Manager” on page 235 and “Monitoring Replies” on page 232.

To configure the e-mail reply account, click Configure Reply Manager. For more information, see“Configuring the E-mail Reply Manager” on page 236.


JMS Configuration Options

About JMS Configuration Options

You use the JMS configuration options to configure the SAS Digital Marketing server to handlereplies in real time. The Java message service (JMS) is an enterprise API that asynchronously sendsand receives messages. A JMS provider runs as a service on a Web application server, such as BEAWebLogic. Then JMS queues and JMS topic are set up to provide real-time broadcast reply andresponse processing.

To view the JMS configuration options, select Tools!Server Configuration!JMS Configura-tion Options.

Configuring JMS

To configure the SAS Digital Marketing server to use JMS, select the check box and specify theJMS provider settings. For more information, see “Configuring a JMS Provider” on page 269 and“Using the JMS Provider” on page 281.

About SAS Options F 103

SAS Options

About SAS Options

You use the SAS options to specify the options to run the SAS System with SAS Digital Marketing.You must configure these options to use the SAS language adapter. The SAS language adapterenables you to access within SAS ETL processes the data and broadcast definitions from SASDigital Marketing Web Studio.

NOTE: Before you can run a SAS job and reports, you must deploy SAS Digital Marketing WebStudio and set the WebAppURL server property. For more information, see “Configuring SASDigital Marketing Web Studio” on page 83.

To view the SAS options, select Tools!Server Configuration!SAS Options.


Configuring SAS

Use the Integrated Execution Context drop-down list to select how you want to run the SAS jobsfrom SAS Digital Marketing. To verify that you have entered this information correctly and that theSAS connection works, click Test SAS Connection.

If you run SAS jobs in batch mode, then select Batch SAS and type the path of the SAS executablein SAS Command Line box. When you install Foundation SAS and SAS Digital Marketing on thesame server, the default location of the Foundation SAS installation automatically appears in theSAS Command Line box.

If you run the SAS jobs on the IOM workspace server, then select Workspace Server and specifythe name of the workspace server. You must also specify your username and password for thatserver. An IOM workspace server is recommended if your site has more than five users that generatereports simultaneously. If you use the IOM workspace server, then this server must be running.

NOTE: To generate SAS reports in multiple languages, install Foundation SAS to use UTF-8 en-coding. For more information, see “Implementing the SAS Language Adapter” on page 86.

Select the Execute batch jobs periodically check box if you want to run the SAS job at a regularinterval. You can specify the minutes between runs. By default, batch jobs are run every 60 minutes.

To customize the output from the SAS jobs, you can use the following options:

� ODS Style specifies the style of the HTML output.

� Graph Device specifies the graphical output format to use for any graphs that appear in theoutput.

If your Web browser is Mozilla Firefox, then you should select Java as the graphical output format.The ActiveX driver is not supported.

When you select ActiveX as the graph device, each SAS Digital Marketing client must install theSAS/GRAPH control for ActiveX. To install the ActiveX drive, use the support.sas.com Web siteto download the SAS/GRAPH driver. Currently, the URL address is

http://www.sas.com/apps/demosdownloads/setupcat.jsp?cat=SAS%2FGRAPH+Software

When you select Java as the graph device, make sure that you apply the patches fromSAS Notes SN-V9-017502 and SN-V9-017593 to Foundation SAS. For more information, seehttp://support.sas.com/techsup/search/sasnotes.html.

Configuring an ASP Definition F 105

ASP Definition Manager

About the ASP Definition Manager

You use the ASP Defintion Manager to create the metadata for an ASP broadcast. An ASP broadcastinterfaces with an application service provider (ASP) to deliver SMS, MMS, or WAP Push messagesto handheld wireless devices using phone numbers that are stored in a data source table. The ASPbroadcast definition connects to mobile networks by using an ASP that provides an HTTP postinterface. SAS Digital Marketing provides a generic interface to use the API specifications of theASP. You configure the ASP broadcast definition to post the appropriate requests that send SMS,MMS, or WAP Push messages.

To view the ASP definitions, select Tools!Server Configuration! ASP Definition Manager.

Configuring an ASP Definition

To create a new ASP definition, click Add. To delete an ASP definition, select the name and clickRemove. To modify an ASP definition, select the name and click Edit. To copy an ASP defini-tion, click Duplicate and specify a new name. When you click Edit or Add, the ASP DefinitionProperties dialog box opens. For more information, see “Managing ASP Definitions” on page 170.


Distribution List Manager

About the Distribution List Manager

You use the Distribution List Manger to simplify how a user selects the data source tables andvariables. SAS Digital Marketing uses this information in the broadcast definition to customizemessages and track broadcast responses. A distribution list contains information to assign the datasource tables and variables. When you define, preview, or schedule a broadcast, you can use distri-bution lists to create global data models and limit the data source tables that a user selects.

To view the distribution lists, select Tools!Server Configuration!Distribution List Manager.

Configuring a Distribution List

To create a new distribution list, click Add. The New Distribution List wizard opens. To delete adistribution list, select the name and click Remove. To modify a distribution list, select the name andclick Edit. The distribution list Properties dialog box opens. For more information, see “ManagingDistribution Lists” on page 158.

Configuring E-mail Broadcasts F 107

E-mail Options

About E-mail Options

You use the e-mail options to change the settings to preview and execute e-mail broadcasts. Youcan also specify how to distribute the broadcast execution across multiple servers.

To view the e-mail options, select Tools!Server Configuration!E-mail Options.

Configuring E-mail Broadcasts

Use Number of table observations to use for previewing to specify the default number of e-mailsthat SAS Digital Marketing sends when you preview an e-mail broadcast. SAS Digital Marketingstarts from the top entry in the recipient data source table to create the e-mails that are sent. UsePreview timeout in seconds to specify the amount of time in seconds that SAS Digital Marketinguses to create an e-mail before the preview transmission has a timeout.


Select Identify preview messages in the subject line to add a prefix to the e-mail subject line. Theprefix includes the word PREVIEW, the message number, and content type in the e-mail subject line.

Select Prevent duplicate e-mails per broadcast to filter out all duplicate e-mail addresses whenyou send a broadcast transmission. You must select all for the e-mail audit level and select Writeaudit records to a JDBC table on the Logging tab. SAS Digital Marketing records when a recipi-ent is sent e-mail and examines the audit table before e-mail is sent from another recipient table. Ifyou re-execute a broadcast and use the same recipient table, then SAS Digital Marketing does notsend a duplicate e-mail.

NOTE: If you select the Prevent duplicate e-mails per broadcast option, then SAS Digi-tal Marketing sends only one broadcast per e-mail address. Therefore, transaction broadcastswork only once for each e-mail address. You can override this duplication policy by setting the!EM_PREVENT_DUPS! directive to true. For more information, see “Using E-mail Directives”(Appendix B, SAS Digital Marketing User’s Guide).

Specifying Grid Nodes

The Available Grid Nodes for Distributed Execution table lists the nodes that SAS Digital Marketingcan use for distributive execution of broadcasts. Use Number of messages to generate per threadto specify the number of messages that SAS Digital Marketing distributes to each node on the gridnetwork when a thread is requested.

To specify a new grid node, click Add. To delete a grid node, select the host name and clickRemove. To update a grid node, select the server name and click Edit. When you click Edit orAdd, a dialog box opens. Specify the name of the grid node in the dialog box. For more information,see “Configuring a Grid Node” on page 256.

About Logging Options F 109

Logging Options

About Logging Options

You use the Logging options to specify the types of audit records that SAS Digital Marketing createsfor the broadcast transmissions. You can also specify the level of detail in records that SAS DigitalMarketing displays in the log. To remove the duplicate broadcasts, you must set the options to createan audit table and record all the audit events for every individual broadcast transmission. If you planto drill down through the reports in SAS Digital Marketing Web Studio, then you should also recordall the audit events. You can view audit records in the Query Broadcast Response window. For moreinformation, see “Viewing Broadcast Response” (Chapter 4, SAS Digital Marketing: User’s Guide).

To view the Logging options, select Tools!Server Configuration!Logging Options.


Customizing the Audit Records

You can specify the information that SAS Digital Marketing records in the audit table and the auditlog. Use the Audit level drop-down list to select the following records:

� none suppresses audit records.

� all creates audit records for every individual broadcast transmission.

� failures creates audit records only for broadcast transmission failures.

Select Write audit records to a table to write the records to an audit table and to any configuredJMS providers. To create a new table each time you execute a broadcast, select Create a uniqueaudit table per broadcast. SAS Digital Marketing appends a timestamp to the audit table namethat enables you to easily identify when the broadcast was executed. To specify the audit table name,click Configure Audit Table. For more information, see “Define the Audit Table” on page 111.

To control the amount of information that appears on the Log tab, use the Server log level drop-down list. SAS Digital Marketing displays the following information:

� Level 1 includes only the operations.

� Level 2 includes the operation and user.

� Level 3 includes the operation, user, and server method.

Select Display server log in the server console window if you want the log information to appearin this window. The log information is recorded in the ROOT/wrapper.log file.

Define the Audit Table F 111

Define the Audit Table

To identify the audit table, click Configure Audit Table. The Configure Audit Table dialog boxopens.

To specify information about the audit table, complete the following steps:

1. Select the folder for the audit table.

2. Select an existing table or enter the name of the table in the Table box. SAS Digital Marketingautomatically creates the table if it is not found in the folder.

3. Click OK to store your settings.

Use the Connections drop-down list to use a different table connection.

NOTE: In order for the SAS Digital Marketing clients to create reports that access the audit table,you must specify an explicit host in the JDBC connection definition. Therefore, do not specify aJDBC connection that has localhost as the Universal Resource Identifier (URI).


Send Options

About Send Options

You use the Send options to set the default values for a broadcast transmission. You can specify thenumber of times that SAS Digital Marketing tries to send a broadcast and whether to simulate thebroadcast transmission. You can also test your outgoing SMTP mail server and configure additionale-mail servers.

To view the Send options, select Tools!Server Configuration!Send Options.

Configuring the Broadcast Transmission

To change the number of attempts that SAS Digital Marketing makes to send a broadcast, specify avalue in the Number of send retries box. If you want to test the performance of a broadcast trans-mission without actually sending the broadcast, then select Simulate transmissions with a timedelay. Use Simulated send delay (in milliseconds) to specify the amount of time in millisecondsthat SAS Digital Marketing waits after an individual message is rendered.

Select Automatically apply opt-out table during send processing to use the opt-out table to filterthe broadcast transmission. When SAS Digital Marketing records an address in the opt-out table,no broadcast e-mails are sent to this address. SAS Digital Marketing records addresses in the opt-

Configuring SMTP E-mail Servers F 113

out table when you use the Insert HTML opt-out link and Insert TEXT opt-out link optionsin the Insert other expressions dialog box to embed the opt-out servlet in the broadcast message.Addresses are also recorded in the opt-out table when you set a Reply Manager rule threshold. Formore information, see “Response Tracking” (Chapter 7, SAS Digital Marketing: User’s Guide).

For non-Asian languages, use 8-bit as the value for Default mime transfer encoding. Some Asianlanguages expect 7-bit mime transfer encoding or another value. For more information, see MIME(RFC 2045). To override the encoding on a per e-mail basis, use the !EM_ENCODING! directive.For more information, see “Using E-mail Directives” (Appendix B, SAS Digital Marketing User’sGuide).

Configuring SMTP E-mail Servers

SAS Digital Marketing uses the servers in the SMTP E-mail Servers table to send the broadcast.You must specify at least one outgoing e-mail server. To define a new e-mail server, click Add.To delete an e-mail server, select the server name and click Remove. To update an e-mail server,select the server name and click Edit. When you add or update an e-mail server, the SMTP ServerSettings dialog box opens.

NOTE: The e-mail servers that you use to preview your broadcasts or to send reports must acceptpartial e-mail addresses.

General Options

Use the General tab to enter the name of your server and the port that the e-mail server useson that host. If the server is configured to require authentication, then select Server RequiresAuthentication and enter the user credentials.


Advanced Options

Use the Advanced tab to select the SMTP driver from the SMTP Provider drop-down list. Youcan configure SAS Digital Marketing to use a third-party JavaMail driver such as the PowerMTAdriver, or you can specify another third-party driver. You can also click Add to specify property andvalue pairs that SAS Digital Marketing uses to send e-mails on this e-mail server.

If you have multiple outgoing servers, then SAS Digital Marketing rotates the broadcast transmis-sion between the e-mail servers.

By default, preview broadcasts are sent to the same server as the broadcasts that are currently ex-ecuting. To improve performance, your site administrator can use the PreviewSMTPServer serverproperty to specify a different SMTP server to process the preview broadcast. For more information,see “Properties for Specifying a Different SMTP E-mail Server” on page 147.

Configuring the Performance F 115

Performance Options

About Performance Options

You use the Performance options to set the maximum number of threads that SAS Digital Marketingspawns in order to optimize the broadcast transmission. By default, the broadcast transmission runsin multiple threads for efficiency.

To view the Performance options, select Tools!Server Configuration!Performance Options.

Configuring the Performance

To improve the e-mail broadcast transmissions, specify the number of threads. You can also specifythe number of asynchronous threads that SAS Digital Marketing uses to deliver spooled SMTP mes-sages to an e-mail server. For more information, see “Adjusting the SMTP Spooler” on page 263.


Throttled Domain Manager

About the Throttled Domain Manager

You use the Throttled Domain Manager to control the maximum rate at which SAS Digital Mar-keting delivers e-mail to specific domains. Larger e-mail providers, such as AOL, MSN, or Yahoo,implement policies that identify e-mail as spam based on the rate at which messages are sent froman e-mail domain address. If you send a large volume of e-mail on one connection or quicklyresend multiple undelivered e-mail, then an e-mail provider might deny service and damage theeffectiveness of your broadcasts.

When you send a broadcast to a throttled domain, SAS Digital Marketing processes messages inthe ROOT/pending directory. If you use an SMTP spooler, then SAS Digital Marketing usestwo directories. The ROOT/spool directory contains messages that the STMP spooler can rapidlysend. The ROOT/pending directory contains messages that are not sent because of the restrictionon the maximum delivery rate. If the SAS Digital Marketing server stops broadcast transmission,then the throttled messages are still available to send. SAS Digital Marketing automatically resumesbroadcast transmission after the server restarts.

NOTE: Most high performance Mail Transfer Agents (MTA), like PowerMTA, automatically im-plement domain throttling. For high volume implementations, such as a daily e-mail transmissionrate over one million, you might consider using throttling at the MTA level.

To view the throttled domains, select Tools!Server Configuration!Throttled Domain Man-ager.

About Scheduling Options F 117

Configuring Throttled Domains

By default, the throttled domain settings for aol.com, gmail.com, hotmail.com and yahoo.com arebased on values that SAS has used to send broadcast transmissions. The Throttled Domain Managerenables you to add domains and specify the maximum number of messages to deliver per minute.

To define a new throttled domain, click Add, specify the name, and click OK. SAS Digital Mar-keting automatically sets the maximum delivery rate to 120 messages per minute. To change thedelivery rate, select the name and enter a value in the Maximum column. To delete a throttleddomain, select the name and click Remove.

Scheduling Options

About Scheduling Options

You use the Scheduling options to configure the broadcast scheduler and create a notification listthat SAS Digital Marketing uses to send messages about broadcast transmissions.

NOTE: Some platform-specific schedulers do not support a daily, weekly, or monthly schedules forthe execution of future tasks.

To view the Scheduling options, select Tools!Server Configuration!Scheduling Options.


Configuring the Broadcast Scheduler

If the SAS Digital Marketing server is run under Windows, then you can specify a user account thatWindows uses to execute a scheduled broadcast. A user account is not required when a Windowsadministrator starts the SAS Digital Marketing server. If you use a user account to schedule broad-casts, then this user must have administrator permissions; otherwise, the broadcast transmission willfail. The Windows Task Scheduler uses this account to log on to the computer and run the task thatexecutes the broadcast.

NOTE: If you specify a password with an expiration date, then you must remember to update theWindows system account for scheduling when the password changes.

Using a Notification List

Notification messages are sent to the e-mail addresses in the notification list when the server sched-ules execution, starts execution, cancels execution, or finishes execution of a broadcast definition.The CCAdmin server operation also instructs the server to send one proof copy of the broadcastcontent to the notification list when a broadcast starts to execute.

Create a Notification List

To create the notification list, complete the following steps:

1. Click New.

2. Enter a valid e-mail address for the scheduling notification.

3. Click OK.

To revise the notification list, select an e-mail address. Use the check boxes to specify the typesof scheduling events (add, start, finish, cancel, and remove) that generate a scheduling notification.By default, every e-mail address receives notification of each scheduling event. To edit the e-mailaddress, click Modify. To remove the e-mail address from the list, click Remove.

Configuring the WAP Integration F 119

WAP Integration Options

About WAP Integration Options

You use the WAP integration options to set a default Wireless Application Protocol (WAP) Integra-tion broadcast. SAS Digital Marketing uses the WAP URL address in an ASP broadcast definitionto deliver the mobile HTML content for the multichannel broadcast.

To view the WAP integration options, select Tools!Server Configuration!WAP IntegrationOptions.

Configuring the WAP Integration

SAS Digital Marketing lists the ASP broadcast definitions that include at least one parameter with aWAP URL address. Select the name of an ASP broadcast definition. To change the WAP integrationbroadcast for an individual multichannel broadcast, use the WAP tab in the Broadcast Propertiesdialog box. For more information, see “Managing WAP Integration Broadcasts” on page 178 and“WAP Properties” (Chapter 4, SAS Digital Marketing: User’s Guide).


Web Services

About Web Services Specifications

You use the Web Services to specify the connection parameters for the Web application serverthat SAS Customer Intelligence software uses to integrate with SAS Digital Marketing. The Webservices specifications are used by the SAS Digital Marketing server to locate the recipient list whena CI export definition is used to create a broadcast definition. The SAS Digital Marketing serveralso uses these settings to send contact history, response history, and reply history to SAS CustomerIntelligence software when a broadcast definition that uses a CI export definition executes.

To view the Web services specifications, select Tools!Server Configuration!Web Services.

Configuring Web Services Specifications

Use CI Mid-tier URL to specify the location of the middle tier. Enter the URL address for the Webapplication server. Use CI User name and CI Password to enter the user credentials. To verifythat the connection works correctly, click Test.

About Contact History Options F 121

Contact History Options

About Contact History Options

You use the Contact History options to specify broadcast transmission events that the SAS DigitalMarketing server sends to SAS Customer Intelligence software. When a broadcast definition thatuses a CI export definition executes and is unsuccessful, SAS Digital Marketing records the event inthe Audit table. The SAS Digital Marketing server periodically examines this table for new recordsand transmits specific events as a failed contact.

To view the Contact History options, select Tools!Server Configuration!Contact History Op-tions.


Configuring Contact History

Use the check boxes to select the events that you want recorded as a failed contact. SAS DigitalMarketing examines the Status column in the Audit table to track the following information:

� when status is duplicate, records duplicated e-mail addresses as a failed contact

� when status is invalid, records invalid e-mail addresses as a failed contact

� when status is abort, records aborted or failed e-mail sent as a failed contact

� when status is opt out, records elimination through opt out list as a failed contact

� when status is dynamic abort, records elimination through XSL template conditional logic asa failed contact.

NOTE: To send these events to SAS Customer Intelligence software, set the audit level to all andstore the records in an audit table. For more information, see “Logging Options” on page 109.

Response History Options

About Response History Options

You use the Response history options to specify the broadcast response events that the SAS DigitalMarketing server sends to SAS Customer Intelligence software. When a broadcast definition thatuses a CI export definition executes, the tracking servlets record responses in the Response table.The SAS Digital Marketing server periodically examines this table for new records and transmitsthe response history.

Configuring Response History F 123

To view the Response History options, select Tools!Server Configuration!Response historyOptions.

Configuring Response History

Use the check boxes to select the events that you want recorded as a response. SAS Digital Market-ing examines the Bessevent column in the Response table to track the following information:

� for an open event, records tracked view events as a response

� for a click event, records tracked click events as a response


Connection Options

About Connection Options

You use the Connection options to create or modify the JDBC connections for the data source tables.To open the Connection Definitions dialog box, select Tools!Server Configuration!ConnectionOptions.

Configuring the Connections

To modify a JDBC connection, select the table name. Use the text boxes to change the driver,Universal Resource Identifier (URI), user ID, and password that SAS Digital Marketing uses toconnect to a JDBC provider. For more information, see “Configuring JDBC Data Providers” onpage 222.

Configuring the Middle Tier F 125

Middle Tier Options

About Middle Tier Options

You use the Middle Tier options to specify the location of the tracking and Web publication tierthat has been deployed on a Web application server. Java servlets monitor the broadcast response,process multichannel broadcasts, host broadcast content, and manage Web resources.

To view the Middle Tier options, select Tools!Server Configuration!Middle Tier Options.

Configuring the Middle Tier

To specify the location of the middle tier, enter the base URL address for the Web application server.To verify that the tracking servlets work correctly, click Test.

NOTE: To run the wizard that enables you to customize the WAR file that contains the servlets,select Servlet Configuration from the Tools menu. For more information, see “Configuring theTracking and Web Publication Tier” on page 54.


Advanced Server Properties

About Advanced Server Properties

You use the server properties on the Advanced Server Properties tab to customize the SAS DigitalMarketing application for your site. These properties should be set only by an advanced user, suchas your site administrator.

To view the Advanced Server Properties tab, select Tools!Server Configuration!AdvancedServer Properties.

Configuring the Advanced Server Properties

The server properties are categorized into groups. You can use the Displayed Group drop-downlist to select the group of properties to display. SAS Digital Marketing sets as a preference the lastgroup that you select. The next time that you view the table, the last group that you selected isdisplayed by default.

To sort the server properties by group, click the heading in the Group column. By default, theserver properties appear alphabetically by name, without considering the alphanumeric case of theserver property name. If you sort the name in ascending order, then a server property that startswith a lowercase character appears at the bottom of the table. Conversely, if you sort the name in

Viewing the Advanced Server Properties Settings F 127

descending order, then a server property that starts with a lowercase character appears at the top ofthe table. Therefore, when you add a server property that does not start with an uppercase character,it appears either at the bottom or the top of the table.

The Set column indicates when a server property has been set. To configure a server property,assign a value to the Value column and select the check box in the Set column. If you decide not touse a server property, then delete the entry from the Value column. For a complete description ofeach server property, see “Overview of Advanced Server Properties” on page 133.

NOTE: You can also use the ebtool command to set the server properties in batch mode. Formore information, “Using Batch Mode” (Chapter 2, SAS Digital Marketing: User’s Guide).

Add a Server Property

To include additional server properties in the Server Configuration window, complete the followingsteps:

1. Right-click a row in the Advanced Server Properties tab.

2. From the pop-up menu, select Add. The Add Server Property dialog box opens.

3. In the New Property Name box, specify the name of the server property. Click OK.

This property is not assigned to a group and appears at the top of the Advanced Server Propertiestab. You can set this property by typing a value in the Value column.

Delete a Server Property

To reset the value of a server property to its default value, complete the following steps:

1. Right-click a row in the Advanced Server Properties tab.

2. From the pop-up menu, select Delete. A dialog box prompts you to confirm this deletion.Click Yes.

This property is deleted from the Advanced Server Properties tab. If you deleted a server propertythat shipped with SAS Digital Marketing, then the next time you open the Server Configurationwindow, the server property is again displayed. However, it is reset to its default value. If youdeleted a server property that you created, then this server property is permanently deleted.

Viewing the Advanced Server Properties Settings

You can also view the settings for the active server properties from the Current Server Propertiessection in the About SAS Digital Marketing dialog box. To open the About SAS Digital Marketingdialog box, select About SAS Digital Marketing from the Help menu.


Security Options

About Security Options

You use the Security options to control how users access SAS Digital Marketing and to specify theproxy settings for your site. If a firewall is used while SAS Digital Marketing is running, then youmust use an Internet proxy and specify your proxy and the port number.

To view the Security options, select Tools!Server Configuration!Security Options.

Types of Security

SAS Digital Marketing provides different levels of functionality-based security modes and the usercredentials. The following types of security modes are available:

� None does not require user credentials to log on to the server. All users have administrativeprivileges.

� Basic requires user credentials to log on to the server. SAS Digital Marketing authenticateseach user.

� Metadata requires user credentials to log on to the server. A metadata server authenticateseach user.

Basic Security Mode F 129

The following levels of user authorization are available:

Level 1 can view broadcasts, Web resources, or RSS content, preview broadcasts, and runbroadcast reports but cannot create or modify broadcasts, resources or feeds, sendbroadcasts, or stop the server.

Level 2 can create or modify broadcasts, Web resources, or RSS content, preview broadcasts,and run broadcast reports but cannot create RSS feeds, send broadcast transmissions,or stop the server.

Level 3 can create or modify broadcasts, Web resources, or RSS content, preview broadcasts,run broadcast reports, and send or stop broadcasts transmissions, but cannot createRSS feeds or stop the server.

Level 4 can create, view, preview, and send or stop broadcast transmissions as well as stop,pause, and resume the server. This user can configure the server, the Java servlets,security for distribution lists, groups, and RSS feeds, the Reply Manager, or the JDBCconnections and create or modify global data models, SAS reports about the broad-casts, or RSS feeds.

NOTE: When you use a metadata server to authenticate user credentials, SAS Digital Marketinggrants Level 3 permission to all users except the software administrator.

Basic Security Mode

The basic security mode authenticates user credentials based on information that you specify in SASDigital Marketing. To use the basic security mode, select Basic from the Security Mode drop-downlist.


SAS Digital Marketing automatically provides a default user ID for each user authorization level.The following users are provided:

User ID Password Authorizationguest guest1 Level 1writer writer1 Level 2runner runner1 Level 3admin admin1 Level 4

You can use the Groups tab to create and manager user groups.

NOTE: You can also manage the user and groups settings by running a SAS job in batch mode.SAS Digital Marketing provides a SAS program, called Example - Defining Users and Groups,in the SAS Job Editor under the Batch Jobs folder that you can modify. For more information, see“Working with SAS Jobs” on page 192.

Change User Settings

To change the user settings, complete the following steps:

1. Click Add in the Authentication box to create new user credentials. To modify the usercredentials, select a user name from the Users box and click Edit.

2. Specify the user name and password.

3. Select authorization level from the drop-down list.

4. Click OK to store the changes.

Metadata Security Mode F 131

To remove obsolete users, select the user name from the Users tab in the Authentication box andclick Remove. Then click Yes to confirm that you want to remove this user from the list.

NOTE: When you are not a Level 4 user, select Change Password from the Tools menu to changeyour password. For more information, see “Change Your Password” (Chapter 2, SAS Digital Mar-keting: User’s Guide).

Metadata Security Mode

The metadata security mode uses a metadata server to centralize the management of user credentials.SAS Digital Marketing uses the metadata repository to authenticate the user credentials. To use themetadata security mode, select Metadata from the Security Mode drop-down list.

You must specify the location of the metadata server and the user credentials for the SAS DigitalMarketing software administrator. Unlike with the basic security mode, you do not have to specifya different user ID and password for the user credentials. Using the metadata server authenticationforces the SAS Digital Marketing Server user credentials to match your operating environmentcredentials.

NOTE: When you use a metadata server to authenticate user credentials, SAS Digital Marketinggrants Level 3 permission to all users except the software administrator.


User Group Settings

You can assign users that have permission to access SAS Digital Marketing to one or more usergroups. You use a user group to simplify assigning read and write permission for broadcast groups,distribution lists, Web resources, and RSS feeds. For more information, see “Managing Security”on page 167.

Click Groups in the Authentication box to view the user groups. To create a new user group, clickAdd, specify the user group name, and select the group members. To delete a user group, select thegroup name and click Remove. To update a user group, select the user group name and click Edit.When you click Edit or Add, the User Group Settings dialog box opens.

To add or delete group members, select the user ID or group user name and click or

. Then click OK to save the new user group settings.

NOTE: : If the metadata security mode is used, then you must first enter the user ID to add it to theuser group.

Chapter 5

Modifying Advanced Server Properties

ContentsOverview of Advanced Server Properties . . . . . . . . . . . . . . . . . . . . . . 133Description of the Advanced Server Properties . . . . . . . . . . . . . . . . . . . 134

Audit Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Client User Interface Server Properties . . . . . . . . . . . . . . . . . . . . 135Edit Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Encoding Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 140Integration Utils Server Properties . . . . . . . . . . . . . . . . . . . . . . . 141JDBC Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Optimize Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 144Properties for Restricting Ports . . . . . . . . . . . . . . . . . . . . . . . . 145Preview Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Reply Management Server Properties . . . . . . . . . . . . . . . . . . . . . 147Response Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 151Scheduling Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . 153

Overview of Advanced Server Properties

SAS Digital Marketing ships with a list of server properties that you can use to set global policiesfor your site. For example, you can restrict the values for the From and Reply to fields. You canalso configure a location for response tables.

To set these server properties in SAS Digital Marketing Studio, select Server Properties inthe Server Configuration window. For more information, see “Advanced Server Properties” onpage 126. You can also use the ebtool command to set these server properties in batch mode. Formore information, see “Using Batch Mode” (Chapter 2, SAS Digital Marketing: User’s Guide).

NOTE: Only a user with administrative privileges (Level 4 permission) should modify the serverproperties.

To view the settings for the server properties, select About SAS Digital Marketing from the Helpmenu. The server property settings appear in the System Information section of the About SASDigital Marketing dialog box. These server properties are categorized into the following groups:

134 F Chapter 5: Modifying Advanced Server Properties

� Audit

� Client UI

� Edit

� Encoding

� Integration Utils

� JDBC

� Optimize

� Ports

� Preview

� Reply Management

� Response

� Scheduling

You can also use the ebtool command to set these server properties in batch mode. For moreinformation, see “Using Batch Mode” (Chapter 2, SAS Digital Marketing: User’s Guide).

Description of the Advanced Server Properties

Audit Server Properties

You can set the following audit server properties:

AuditAspRequestspecifies whether the application server provider (ASP) requests that are sent for each broad-cast message are written to the aspresp column in the audit table. The requests are sent whenthe broadcast is executed. By default, this property is set to false.

DiscardDynamicAbortEventsprevents SAS Digital Marketing from writing dynamic abort audit records for e-mail, SMS,ASP, and multichannel broadcasts to the audit table. This option helps conserve space in thedatabase.

Client User Interface Server Properties F 135

Client User Interface Server Properties

You can set the following client user interface (UI) server properties:

AdapterFontspecifies the font that SAS/GRAPH should use when generating graphs for the SAS reports.By default, this property is set to Arial.

AllowSpacesInGroupNamespecifies whether the name for a broadcast group can include blank spaces. By default, thisproperty is set to true.

AllowTrackedVarSelectionspecifies whether the Tracking panel is always available from the New Broadcast wizard inSAS Digital Marketing Studio. By default, this property is set to false.

AlwaysShowTrackingPanelwhen a customer intelligene (CI) export definition is used for the recipient list, specifieswhether to enable the user to select additional tracked variables. Otherwise, the user canselect only the variables that are required to correlate the broadcast to the original campaignin the CI common data model. SAS Digital Marketing does not store the optional variablesin the common data model. By default, this property is set to false.

AutoSelectNewBroadcastsspecifies whether new broadcasts are automatically selected in SAS Digital Marketing Stu-dio. By default, this property is set to false.

DisableGroupWebEditsspecifies whether you can edit groups in SAS Digital Marketing Web Studio. When you setthis property to true, the New Group option is not visible, and the Rename and Delete menuitems are dimmed. By default, this property is set to false.

EmailAddressCheckspecifies whether to perform stringent checking for an invalid e-mail address. When thisproperty is set to true, the e-mail address must have a local part followed by a domain part thatis separated by an @, and must not end in a period (localname@domainname). When youpreview or schedule a broadcast, SAS Digital Marketing identifies invalid e-mail addressesin the log and audit table. The property is set to false by default.

EmailAddressVariablespecifies the value for the e-mail address variable for any new broadcasts. When this propertyis set, all data source tables must contain the variable that you specified, and this variable mustcontain the e-mail addresses for the broadcast recipients.

When this property is set, users cannot select a different e-mail address variable because ofthe following changes to the user interface:

� In SAS Digital Marketing Studio, the E-mail Address Variable drop-down list isdimmed in the E-mail Broadcast Header panel of the New Broadcast wizard.

� In SAS Digital Marketing Web Studio, the Address Variable field is not available fromthe New Broadcast page.


By default, this property is not set, and the user can select the variable to use as the e-mailaddress variable.

For information about how to use server properties to create a global data model for incomingrecipient lists and for tracking data, see “Managing Global Data Models” on page 166.

EmailTrackedVariablesspecifies the tracking variables to use for an e-mail broadcast. The tracking variable shouldcontain unique information, such as a customer ID number, so that SAS Digital Marketingcan track the behavior of each broadcast recipient. To specify the tracking variables to use,specify values as a comma-separated list.

When this property is set, the user cannot change the tracking variable because of the follow-ing changes to the user interface:

� In SAS Digital Marketing Studio, the user cannot change the variable that is selected inthe Tracking Variables box in the Tracking panel of the New Broadcast wizard.

� In SAS Digital Marketing Web Studio, the Tracked Variables field is not displayed onthe New Broadcast page.

By default, this property is not set, and the user can select the variables to track.

NOTE: If you specify both the EmailTrackedVariables and the ResponseTableBase proper-ties and the variable that you specified for the EmailTrackedVariables property exists in yourdata source, then in SAS Digital Marketing Studio the Tracking panel does not appear in theNew Broadcast wizard or in the New Broadcast Content wizard.


EmailVariablesspecifies the variables that are in the recipient table. The variables should contain the e-mailaddresses for the recipients, unique tracking information (such as customer ID), or otherinformation that you might use to customize your broadcast content. To specify the e-mailvariables to use, specify values as a comma-separated list.

When this property is set, the user cannot change these variables because of the followingchanges to the user interface:

� In SAS Digital Marketing Studio, the Data Model panel of the New Broadcast wizardis not available, so end users cannot select the data source for the broadcast.

� In SAS Digital Marketing Web Studio, the Broadcast Variables field is not availablefrom the New Broadcast page.

By default, this property is not set, and the user can select the variables to use.


HideSASPredefinedLibrariesspecifies whether to show the GISMAPS, MAPS, SASHELP, and SASUSER libraries whenthe user can select a data source. Users can select a data source from the List Structure panelof the New Broadcast wizard, the Preview Broadcast wizard, or the Schedule Broadcastwizard in SAS Digital Marketing Studio.

Client User Interface Server Properties F 137

By default, this property is set to true, and these libraries are not available from the wiz-ards. As a result the user must specify a full two-level name (for example, EXAM-PLES.CONTACT_DETAILS) when selecting a data source. The site administrator can stillaccess these predefined libraries from the SAS JDBC Explorer window.

HideTablesdisplays in SAS Digital Marketing Studio a predefined set of tables that the administratorhas set up as distribution lists. If this property is set to true, then users at your site can usedistribution lists only in the New Broadcast wizard, the Preview Broadcast wizard, and theSchedule Broadcast wizard to select a data source table.

LockSentBroadcastsspecifies whether to lock broadcasts that have been previously sent or broadcasts that arescheduled for execution. If this property is set to true, then the SAS Digital Marketing Studiouser cannot edit the broadcast. This broadcast can be opened in read-only mode. When thisproperty is set to true, then the user sees the following in SAS Digital Marketing Studio:

� In the SAS Digital Marketing Studio window, if a user right-clicks on a broadcast thathas been sent or one that is scheduled for execution, then the pop-up menu that appearsdoes not contain the Delete, Define New Content, or Edit options. Instead, this pop-upmenu has a View option that the user can select to view the broadcast content. A dialogbox also opens telling the user that the broadcast has already been sent or is scheduledand that any edits are not saved.NOTE: If a broadcast is selected in the main window when you change the LockSent-Broadcasts property, then you must select the broadcast again for the options in thepop-up menu to update.

� In the content editor in SAS Digital Marketing Studio, the Save Broadcast option from

the File menu and the Save icon are not available. The user can edit the broadcastcontent, but when the user closes the content editor a message appears stating that thecontent is not saved.

� In the SAS Digital Marketing Web Studio, the Edit options are not available for broad-casts that have been executed.

SaveLastURLPasswordspecifies whether to save the last password in the URL userid/password dialog box in SASDigital Marketing Studio. By default, this property is set to false.

ShowCustomizeContentMenuItemsspecifies whether to show in SAS Digital Marketing Web Studio the View Customized HTMLand View Customized Text menu items for a broadcast that contains HTML or text content.By default, this property is set to false.

ShowRecipientTablespecifies whether SAS Digital Marketing Web Studio displays information about the recipienttable when a broadcast is scheduled. If a database table is used, then SAS Digital Marketingdisplays a Web page with the name of the table and the number of recipients. You click thetable name to display the contents of the table. The ShowRecipientTableRowCount serverproperty determines the number of rows that are displayed. If a distribution list is used, thenSAS Digital Marketing displays a Web page with the name of the distribution list and thenumber of recipients. By default, this property is set to false.


ShowRecipientTableRowCountspecifies the number of rows in the recipient table to display when SAS Digital MarketingWeb Studio is used to schedule a broadcast and ShowRecipientTable is set to true. By default,this property is set to 10.

TrackedVariableWarningThresholdspecifies the number of tracked variables that you can select from the data source table beforeSAS Digital Marketing displays a warning message. You should limit the number of trackedvariables when the value of the tracked variables are included in the tracked links. Otherwise,the URL address might become too long. By default, this property is set to 3.

UseFileDialogspecifies whether the Browse buttons in SAS Digital Marketing Studio should use AWT File-Dialog selection or Swing JFileChooser. If this property is set to true, then the AWT FileDi-alog selection is used. By default, this property is set to false and the Swing JFileChooser isused.

UserSourcePanelspecifies whether to display in SAS Digital Marketing Studio the User Input selection in theList Structure step of the New Broadcast wizard. By default, this property is set to false.

Edit Server Properties

You can set the following edit server properties:

Aol5Supportedspecifies whether SAS Digital Marketing Studio supports AOL 5.0. When this property isset to true, you can create and edit a broadcast definition that contains AOL 5.0 content. TheNew Broadcast wizard also displays the AOL Content and AOL Encoding options. Bydefault, this property is set to false.

BlankDuplicatedTablespecifies whether to omit the name of the data source table when you duplicate a broadcastthat does not use a global data model. This property prevents users from executing the dupli-cated broadcast against the recipient list from the original broadcast. By default, this propertyis set to false, and the table name is not removed.

NOTE: SAS Digital Marketing ignores the BlankDuplicatedTable server property becausea global data model is used.

DisableAltSyntaxspecifies whether to use the alternate syntax that SAS Digital Marketing Studio providesfor inserting variables into e-mail content. If this property is set to true, then the alternativesyntax is disabled. For more information about this alternate syntax, see “Syntax for Insertinga Variable in the Content” (Chapter 5, SAS Digital Marketing: User’s Guide).

By default, this property is set to false and the alternate syntax is enabled.

Edit Server Properties F 139

DisableAttachmentsspecifies whether attachments are allowed in e-mail campaigns. When you set this property totrue, SAS Digital Marketing ignores the attachments that you specify in the !EM_ATTACH!directive. For more information, see “Using E-mail Directives” (Appendix B, SAS DigitalMarketing: User’s Guide). By default, this property is set to false.

DreamweaverSnippetDirspecifies the default location of the snippets for your Dreamweaver installation. By default,SAS Digital Marketing uses a default location of the following:

%userprofile%nApplication DatanMacromedian

$DREAMWEAVER_RELEASEnConfigurationnSnippets

where DREAMWEAVER_RELEASE is the location that you specified in the HTML EditCommand box of the Preferences dialog box. You need to specify this server property onlyif the default location is not in this location. By default, this property is not set.

EditColorCodingcontrols whether the text for HTML, text, or AOL Rich Text source that appears in the contenteditor is color coded. When you use SAS Studio Marketing Studio with Asian languages,you need to turn off the color coding in the content editor. By default, this property is set totrue.

HTMLEditorCommandspecifies the third-party HTML editor to use in SAS Digital Marketing Studio. The defaultHTML editor is Microsoft Office FrontPage. The site administrator can change this defaultvalue. SAS Digital Marketing Studio users can override the default value from the Pref-erences dialog box. For more information, see “Setting the Preferences” (Chapter 2, SASDigital Marketing: User’s Guide).

StaticEmailSupportedspecifies whether SAS Digital Marketing clients provide the ability to create static e-mailbroadcasts. A static e-mail broadcast delivers identical content to each recipient in the datasource table. SAS Digital Marketing does not track responses or replies for a static e-mailbroadcast. Static broadcasts do not require modifications to the default configuration andrequire only an MTA for e-mail delivery. By default, this property is set to false.

SuspendStudioWhileEditingspecifies whether to close the content editor in the SAS Digital Marketing Studio when youopen an external editor. If you set this option to true, then the user cannot have both the con-tent editor from SAS Digital Marketing Studio and the external editor open simultaneously.By default, this property is set to false, and the user can have the content editor and the ex-ternal editor open simultaneously. If both the content editor and the external editor are open,then the user can edit content in an external editor (such as Dreamweaver) and simultane-ously view the changes in the content editor. For an example of how this works, see “EditingContent in Dreamweaver” (Chapter 5, SAS Digital Marketing: User’s Guide).

TextEditorCommandspecifies the third-party text editor to use in SAS Digital Marketing Studio. The defaulttext editor is NotePad. The site administrator can change this default value. SAS DigitalMarketing Studio users can override the default value from the Preferences dialog box. Formore information, see “Setting the Preferences” (Chapter 2, SAS Digital Marketing: User’sGuide).


Encoding Server Properties

You can set the following encoding server properties:

EncodeTrackedVariablesspecifies that the server that is used by java.net.URLEncoder.encode() to encode thetracked variables. If your tracking variables include DBCS values or spaces, then the valuesmight not be saved correctly in the response table. Specifying this property fixes the problemwhere DBCS characters are used for tracking or for variables with spaces.

NOTE: The server does not encode the tracked variables in the broadcast definitions thatwere created before this server property is set.

EncodingChoicesspecifies the encoding choices that are available to users when defining a new broadcast.

If you specify only one value for this property, then the HTML Encoding, Text Encoding,and AOL Encoding drop-down lists are not available from the following locations:

� the New Broadcast wizard in SAS Digital Marketing Studio

� the New Broadcast Content wizard in SAS Digital Marketing Studio

� the New Broadcast page in SAS Digital Marketing Web Studio

To specify several encoding options, use a comma-separated list.

EscapeNewLinescontrols whether new lines in your text content are compiled with enclosing <xsl:text>tags. Specifying this property results in larger compiled XSL files, but you must specifythis option to send Asian language broadcasts with plain text components. By default, thisproperty is set to false.

EscapeSpacescontrols whether spaces in your text content are compiled with enclosing <xsl:text> tags.Specifying this property results in larger compiled XSL files, but you must specify this optionto send Asian language broadcasts with plain text components. By default, this property isset to false.

HTMLEscapeNewLinescontrols whether new lines in your HTML content are compiled with enclosing<xsl:text> tags. By default, this property is set to false.

HTMLEscapeSpacescontrols whether spaces in your HTML content are compiled with enclosing <xsl:text>tags. By default, this property is set to false.

Integration Utils Server Properties F 141

Integration Utils Server Properties

You can set the following integration utilities server properties:

AppIdListerClassspecifies the class that contains the getApplicationIdentifiers method. You can use an appli-cation identifier to correlate a broadcast to another business process. The primary advantageof using an application identifier is that this identifier is carried with the response data and au-dit data. You cannot use the identifier to integrate response data from SAS Digital Marketinginto other business processes after a broadcast executes.

When you set this property, a list of valid application identifiers is displayed in the NewBroadcast wizard in SAS Digital Marketing Studio and the New Broadcast page in SASDigital Marketing Web Studio.

SAS Digital Marketing ships with an example for providing application identifiers to inte-grate with other applications or business processes. To use this example, set this property toExampleAppIdExits. This refers to the ExampleAppIDExits.java source file that is saved inthe ROOT directory of the SAS Digital Marketing server install.

By default, this property is set to blank.

BatchSASOptionsspecifies additional global arguments for the SAS command lines that create SAS reportswhen you select batch SAS as your SAS environment. For example, to ensure that the batchSAS session uses UTF-8 mode when SAS Marketing Optimization generates your reports,set the server property to -encoding ‘utf-8’ -dbcs.

HTMLValidationClasssets a global policy for HTML content. For example, a site can decide that JavaScript is notallowed in the content of e-mail broadcasts. A validation class can enforce that policy.

SpamAssassinCommandspecifies the SpamAssassin shell script or BAT file on your computer. If you are runningSpamAssassin as a daemon, then you can set this property to spamc.exe. By default, thisproperty is set to

C:\perl\bin\spamassin.bat

For more information about how to use the SpamScanClass and SpamAssassin Commandserver properties, see “Using the SpamAssasin Spam Filter” on page 181.

SpamScanClassspecifies the class that has implemented the scanMessage static method. A ScanMessageimplementation ships in com.sas.email.server.BulkEmailUtils. To use SpamAs-sassin scoring when your broadcasts are previewed, set this property to

com.sas.email.server.BulkEmailUtils

By default, this property is set to blank so that SAS Digital Marketing does not use SpamAs-sassin.

For more information about how to use the SpamScanClass and SpamAssassin Commandserver properties, see “Using the SpamAssasin Spam Filter” on page 181.


WebAppURLspecifies the URL for the Web application server that is running SAS Digital Marketing WebStudio. You must specify this property before you use the visualreport options with theebtool command. You must also set this option to export a Web resource from the WebResource Manager or import a Web resource into a broadcast.

NOTE: You do not need to specify this server property to deploy SAS Digital Marketing WebStudio. The Configure SAS Digital Marketing Server for Web Reporting page automaticallyupdates the SAS Digital Marketing server to use the URL for the deployment of the Webapplication.

Also, setting this property adds the following options to SAS Digital Marketing Studio:

� The Run SAS Report option is available from the Actions menu. You can run thisreport for individual broadcast definitions. This option is also available from the pop-up menu for a broadcast definition in SAS Digital Marketing Studio. You can also run

a SAS report by clicking in the toolbar.When the SAS Digital Marketing user runs a SAS report, the Run SAS Report pageopens in SAS Digital Marketing Web Studio. The user can select the SAS report torun. The SAS reports are created by the site administrator. For more information, see“Viewing SAS Reports” (Chapter 4, SAS Digital Marketing: User’s Guide).

� The Run Visual Report option is available from the Actions menu. You can run avisual report for an individual broadcast definition. This option is also available fromthe pop-up menu for a broadcast definition in SAS Digital Marketing Studio.When the SAS Digital Marketing user runs a visual report, the visual report for thatbroadcast opens in a new Internet Explorer window. The report’s content is based onthe parameters that the administrator specifies.

When you specify the WebAppURL server property, you can use the TinyMCD Web-basedJavascript editor as the HTML content editor in SAS Digital Marketing Studio. To edit abroadcast using this editor, right-click the broadcast name in SAS Digital Marketing Studio.From the pop-up menu, select HTML Content with TinyMCE from the Edit menu.

NOTE: You can download and install TinyMCE when you specify whether to use an exter-nal HTML editor from the SAS Digital Marketing Server Configuration wizard. For moreinformation, see “Run the Server Configuration Wizard” on page 39.

The syntax for the value that you specify is the following:

http://deployedhost:port/sdm/

JDBC Server Properties

Property for Specifying Bad E-mail Addresses

You can set the following server property to set the threshold for bad e-mail addresses:

BadUploadAddressThresholdspecifies the maximum number of e-mail addresses in an uploaded recipient file that can be

JDBC Server Properties F 143

invalid. When this threshold is exceeded in SAS Digital Marketing Web Studio, then theupload of the file to a temporary table stops. The value for this property is an integer value.By default, this property is set to -1, which means there is no threshold.

Properties for Executing from a File

You might want to execute from a file. To add a File selection to the Broadcast Scheduling wizard,you must specify the following server properties:

TempTableBaseNamespecifies the timestamp when a temporary table is created.

TempTableDriverspecifies the JDBC driver. The values that are available from the drop-down list are thedrivers that you have installed.

TempTablePasswordspecifies the JDBC password.

TempTableURIspecifies the URI. You can select the URI from the drop-down list or enter a new value. Thevalues that are available from this drop-down list depend on the driver that you selected.

TempTableUserspecifies the user ID for the JDBC connection.

When you specify these options, the file is uploaded as a temporary table for processing. Thistable is deleted by the SAS Digital Marketing Server after processing is complete. SAS DigitalMarketing supports only one recipient per line, and each e-mail address is verified as being a valide-mail address. If an e-mail address is not valid, then you are prompted when the error occurs.

Properties for Executing from a Table

You might want to execute from a table. To add a table selection to Schedule Broadcast wizard inSAS Digital Marketing Web Studio, you must specify the following server properties:

WebSelectionTableDriverspecifies the JDBC driver. The values that are available from the drop-down list are thedrivers that you have installed.

WebSelectionTableLibraryspecifies the base library that contains the recipient tables that you want to use.

WebSelectionTablePasswordspecifies the JDBC password.

WebSelectionTableURIspecifies the URI. The values that are available from this drop-down list depend on the driverthat you selected.

WebSelectionTableUserspecifies the user ID for the JDBC connection.


When you specify these options, you can choose from the Schedule Broadcast wizard in SAS DigitalMarketing Web Studio a table that contains the addresses of the recipients of the broadcast.

Optimize Server Properties

Properties for Optimizing Batch SAS Sessions

You can use the following server properties to optimize your batch SAS sessions:

MaximumBatchSessionsspecifies the maximum number of batch SAS sessions to run concurrently. By default, thisproperty is set to 2.

MaximumBatchWaitspecifies the maximum time (in seconds) to wait for an available SAS batch session beforereturning a "Server is too busy" message. By default, this property is set to 150 seconds or2.5 minutes.

Properties for Optimizing an IOM Workspace Connection

If you have five or more users who are generating reports concurrently, it is recommended that youconfigure an IOM workspace server for deployments.

MaximumIOMCachedConnectionsspecifies the maximum number of IOM connections to have cached in memory for quickeraccess. By default, this property is set to 3. If this property is set to -1, then no connectionsare cached, and the MaximumIOMConnections server property is ignored, if specified.

NOTE: If this property is set to -1, then the number of SAS Workspace Server sessions isequal to the number of jobs that are running at one time. This configuration is not recom-mended.

MaximumIOMConnectionAgespecifies the maximum time (in seconds) that an IOM workspace connection can remainidle and still be used. You might specify this property to prevent a workspace connectionfrom being closed. By default, this property is set to 600 seconds (or 10 minutes). If theworkspace connection has not been used in 10 minutes, then the connection is closed, and anew connection is created.

MaximumIOMConnectionsspecifies the maximum number of IOM workspace connections that you can establish at onetime. This maximum number includes cached connections and temporary connections. Thevalue that you specify is the maximum number of SAS jobs that can run simultaneously. Bydefault, this property is set to 3.

Properties for Restricting Ports F 145

MaximumIOMWaitspecifies the maximum time (in seconds) to wait for an available SAS workspace sessionbefore returning a "Server is too busy" message. By default, this property is set to 150seconds or 2.5 minutes.

Other Optimization Properties

You can also set the following optimization server properties:

FeedRefreshIntervalspecifies the amount of time in seconds that SAS Digital Marketing caches the publishedRSS XML. The default value is 600 seconds.

NetConservationturns off several events (such as OnThreadStart and OnThreadStop) for situations wherenetwork bandwidth is an issue.

networkaddress.cache.ttlspecifies the number of seconds to cache a successful lookup. This property is for the IPaddress caching policy for successful name lookups from the domain name service. Thevalue for this property is an integer. By default, this property is set to -1, which keeps thesuccessful lookup in the cache.

networkaddress.cache.negative.ttlspecifies the number of seconds to cache an unsuccessful lookup. This property is for the IPaddress caching policy for unsuccessful name lookups from the domain name service. Thevalue for this property is an integer. By default, this property is set to 10, which removes theunsuccessful lookup from the cache after 10 seconds.

NoLocalHostCheckspecifies whether to skip the localhost check when SAS Digital Marketing Studio is lookingup grid nodes. By default, when you allocate grid nodes, an in-process grid node is allo-cated if the requested host is localhost. In some TCP/IP tunneling scenarios, localhost couldactually mean proxy to another box. By default, this property is set to false.

Properties for Restricting Ports

By default, remote method invocation (RMI) uses random ports for its connections. Because theselection of the port is random, you cannot specify access restrictions on the range of ports that thesoftware might need to make its connections.

Many companies restrict the ports you can use in order to restrict network traffic and increasenetwork security. If you are using a firewall, VPN, or TCP/IP tunneling, then your site administratorhas specified a list of authorized ports that you can use.

To specify that SAS Digital Marketing Studio use a specific range of ports, you must specify thefollowing properties:


CustomSocketFactoryindicates that you want to specify a custom socket for RMI operations. By default, thisproperty is set to false.

SocketEndspecifies the port number of the end socket.

SocketStartspecifies the port number of the start socket.

Unlike other server properties, you specify these properties as command line options of the Javainvocation for each client, grid node, or controller. You can also set these properties on the Com-mandLineArgs statement in INI files in the ROOT directory in Windows environments or in shellscripts in UNIX environments.

The following example shows how you specify these options:

-DCustomSockeyFactory=true -DSocketStart=20000 -DSocketEnd=21000

Preview Server Properties

General Properties for Previewing

You can set the following preview server properties:

PreviewConfirmationdisplays a confirmation dialog box when a broadcast has executed or previews have beensent. This dialog box is displayed only when the SimplePreview property is also set to true.By default, this property is set to false, and the dialog box is not displayed.

PreviewListspecifies whether to show all the e-mail addresses that received a preview e-mail, if the Pre-viewConfirmation property is set to true. By default, this property is set to false.

PreviewSelectionMaxspecifies the number of rows to display in the Preview Recipient Selection panel of the Pre-view Broadcast wizard. By default, SAS Digital Marketing Studio displays the first 1000rows. The smallest value that you can specify is 100. Increasing the number of rows todisplay can impact performance. For more information, see “Run the Preview BroadcastWizard” (Chapter 4, SAS Digital Marketing: User’s Guide).

SimplePreviewspecifies whether to show the Preview Broadcast wizard when you generate a broadcast pre-view for an e-mail broadcast.

If this property is set to true, then a simplified dialog box opens if the data source tablein the broadcast definition is valid and is resolved. In this dialog box, you can specify therecipient address by selecting an e-mail address from a drop-down list, or you can type thee-mail address. In this dialog box, you can also specify the parts of the broadcast, such as the

Reply Management Server Properties F 147

HTML content or text content, to send. If you preview an e-mail broadcast, then the subjectline of the broadcast includes a version number, for example PREVIEW 1.1.

When you set the SimplePreview property to true, you might also want to set the Preview-Confirmation property to true. If you do, then SAS Digital Marketing Studio displays aconfirmation dialog box when a broadcast has executed or previews have been sent.

If this property is set to false, then the Preview Broadcast wizard opens.

Properties for Specifying a Different SMTP E-mail Server

By default, previews are sent to the same server as the broadcasts that are currently executing. Ifyou are executing a large number of broadcasts, then you might want to send these previews to adifferent SMTP e-mail server for a faster delivery of the previews. To specify a different SMTPe-mail server for previews, you must specify the following server properties:

PreviewSMTPPasswordspecifies the password for the SMTP e-mail server that you specified in the Pre-viewSMTPServer property.

PreviewSMTPPortspecifies the port of the SMTP e-mail server that you specified in the PreviewSMTPServerproperty.

PreviewSMTPServerspecifies the name of the SMTP e-mail server that you want to use for previews.

NOTE: The SMTP e-mail server that you specify must be configured and accessible by thecontroller and permit partial e-mail addresses.

PreviewSMTPUserspecifies the user ID for the SMTP e-mail server that you specified in the Pre-viewSMTPServer property.

NOTE: The mail servers that you use to preview your broadcasts or send reports must accept partiale-mail addresses.

Reply Management Server Properties

You can set the following reply management server properties:

DefaultFromspecifies a default value for the From box in the New Broadcast wizard. This value can beoverwritten when you create a new broadcast.

The syntax for the DefaultFrom property is the following:

[email protected]

NOTE: If you also set the PossibleFrom property, then you must specify this default valueas one of the values of the PossibleFrom property. If you do not set this property, then SAS


Digital Marketing does not display the default value that you specified for the DefaultFromproperty in the From box.

DefaultReplyTospecifies a default value for the Reply to box in the New Broadcast wizard. This value canbe overwritten when you create a new broadcast.

The syntax for the DefaultReplyTo property is the following:

[email protected]

NOTE: If you also set the PossibleReplyTo property, then you must specify this default valueas one of the values of the PossibleReplyTo property. If you do not set this property, thenSAS Digital Marketing Studio does not display the default value that you specified for theDefaultReplyTo property in the Reply to box.

DefaultSMSFromspecifies the default value in the From box in the New Broadcast wizard when you arecreating an SMS broadcast. By default, this property is set to blank.

DefaultSMTPFromspecifies a default value for the SMTP From box in the New Broadcast wizard. This valuecan be overwritten when you create a new broadcast.

The syntax for the DefaultSMTPFrom property is the following:

[email protected]

EmailFromOverridespecifies a value for the SMTP Email From box in the New Broadcast wizard, the NewBroadcast Content wizard, and the Header tab in the Properties dialog box. If you set thisproperty, then the SMTP Email From box is not available in the user interface, so userscannot change this value. The SMTP Email From box enables you to track correlatedreplies. For more information, see “Using Correlated Replies” on page 232.

InternalMessageFromoverrides the value of the From field for internal messages. You can send internal mail byselecting the Mail menu option from the Actions menu in the Query Responses window, theQuery Reply window, or the Summary window. You can also specify the e-mail notificationlist for internal messages from the Scheduling tab in the Server Configuration window. Formore information, see “Scheduling Options” on page 117.

By default, this server property is not set, and the value of the From field is used.

PossibleFromxxxspecifies the list of values that appear in the From box in the New Broadcast wizard and inthe Header tab of the Broadcast Properties dialog box. The value of xxx is the number of thee-mail address that you want to include in the list. For example, if you want John Smith’sand Marcel Dupree’s e-mail addresses available from the From box, then you would specifythe PossibleFrom property twice.

[email protected][email protected]

If you set this property, then only those e-mail addresses that you specified can be used ina broadcast. You must specify these properties in sequential order. If you skip a number,

Reply Management Server Properties F 149

then the list contains only the values before the skipped value. All values after the skip areignored, so if you specified PossibleFrom1, PossibleFrom2, and PossibleFrom4, then thefourth value (and any subsequent values) is ignored.

In the following example, the e-mail address specified for PossibleFrom4 does not appear inthe From box because it is specified out of sequence.

[email protected][email protected][email protected]

By default, the PossibleFrom property is set to blank.

If you also set the DefaultFrom property, then you must include the default e-mail address inthe list of possible values. The following examples show how SAS Digital Marketing Studiouses the values of the DefaultFrom and PossibleFrom properties to populate the From box.

� If the DefaultFrom property is blank and no value is specified for the PossibleFromproperty, then the user can enter any value for the From box in the New Broadcastwizard or Header tab in the Broadcast Properties dialog box.

� If you specified a value for the DefaultFrom property but no values were specified forthe PossibleFrom property, then the From box displays the value that you specified forthe DefaultFrom property.

� If you specified a value for the DefaultFrom property and you specified a value forthe PossibleFrom property but none of the possible values match the value of the De-faultFrom property, then the only values that are available from the From box are thePossibleFrom values. The first value in the list is the default.In the following example, only Marcel Dupree’s e-mail address is available from theFrom box.


� If you specified a value for the DefaultFrom property and you specified values for thePossibleFrom property and one of these values is the same as the DefaultFrom property,then the DefaultFrom value also appears in the From box, and it is selected as thedefault.In the following example, both John Smith and Marcel Dupree’s e-mail addresses areavailable from the From box.


PossibleReplyToxxxspecifies the list of values that appear in the Reply to box in the New Broadcast wizard andin the Header tab of the Broadcast Properties dialog box. The value of xxx is the number ofthe e-mail address that you want to include in the list. For example, if you want John Smithand Marcel Dupree’s e-mail addresses to be available from the Reply to box, then you wouldspecify the PossibleReplyTo property twice.



If you set this property, then only those e-mail addresses that you specified can be used ina broadcast. You must specify these properties in sequential order. If you skip a number,then the list contains only the values before the skipped value. All values after the skip areignored, so if you specified PossibleReplyTo1, PossibleReplyTo2, and PossibleReplyTo4,then the fourth value (and any subsequent values) is ignored.

In the following example, the e-mail address specified for PossibleReplyTo4 does not appearin the Reply to box because it is specified out of sequence.


By default, the PossibleFrom property is set to blank.

If you also set the DefaultReplyTo property, then you must specify the same default e-mailaddress using the PossibleReplyTo property to display the default e-mail address from theReply To drop-down list in the New Broadcast wizard. The following examples show howSAS Digital Marketing Studio uses the values of the DefaultReplyTo and PossibleReplyToproperties to populate the Reply To drop-down list.

� If the DefaultReplyTo property is blank and no value is specified for the PossibleRe-plyTo property, then the user can enter any value for the Reply To box in the NewBroadcast wizard or Header tab in the Broadcast Properties dialog box.

� If you specified a value for the DefaultReplyTo property but no values were specifiedfor the PossibleReplyTo property, then the From field displays the value for the De-faultReplyTo property.

� If you specified a value for the DefaultReplyTo property and you specified a value forthe PossibleReplyTo property but none of these are the same as the DefaultReplyToproperty, then the only values that are available from the Reply To drop-down list arethe PossibleReplyTo values. The first value in the list is the default.


� If you specified a value for the DefaultReplyTo property and you specified values forthe PossibleReplyTo property and one of these values is the same as the DefaultReplyToproperty, then the DefaultReplyTo value also appears in the Reply To drop-down list,and it is selected as the default.


ReplyFilterRegexenables you to specify regular expressions for the reply rules. When you specify this option,SAS Digital Marketing Studio treats the reply rules as Java expressions that are compiledwith the java.util.regex.Pattern class. By default, this property is set to false, andSAS Digital Marketing Studio matches the text in the replies to the reply rule. If the textin the reply matches a rule, then the message is added to that reply category. If you wantto specify regular expressions for the reply rules, then set this option to true. Using regularexpressions for filtering replies is slower but can provide greater flexibility for categorizingreplies.

Response Server Properties F 151

Response Server Properties

You can set the following response server properties:

BrowserSummaryspecifies whether to include the default summary report information about the types andversions of Web browsers that recipients used to interact with your e-mail broadcast. Settingthis property to true might increase the time it takes to generate a broadcast summary. Bydefault, this property is set to false.

DomainSummaryspecifies whether to include in the default summary report information about the domainsthat the broadcast was sent to. If you set this property to true, it might take longer to generatea broadcast summary. By default, this property is set to false.

IndexedLinkscreates shorter HTML links that obfuscate the tracking information (such as CLIENT_IDvalue) from the recipient. This property uses the get and getp servlets to generate a click orpclick event. By default, this property is set to false.

LinkToOmitxxxspecifies the links to omit from your tracking. The value of xxx is the number of the link thatyou want to omit. For example, if you want to omit two links from your tracking, then youwould specify the LinkToOmit property twice.

LinkToOmit1=http://www.sas.comLinkToOmit2=http://www.yourcompany.com

Links that you select to omit are not selected for tracking in the New Broadcast wizard andNew Broadcast Content wizard.

You must specify these properties in sequential order. If you skip a number, then only thelinks that are specified in sequential order are omitted. If you specified LinkToOmit1, Link-ToOmit2, and LinkToOmit4, then the fourth value (and any subsequent values) is ignored.

In the following example, the link specified for LinkToOmit4 is not omitted because it isspecified out of sequence.

LinkToOmit1=http://www.sas.comLinkToOmit2=http://www.yourcompany.comLinkToOmit4=http://www.yourdomain.com

By default, all links that appear in the HTML, text, and AOL Rich Text are selected fortracking.

MaxResponseTablesspecifies the maximum number of response tables to generate if the ResponseTableBase prop-erty is set to true. By default, this property is set to 1000.


NegativeLinkxxxspecifies a list of links to treat as negative response events when a recipient clicks any ofthese links. The value of xxx is the number of the link. You must specify these properties insequential order. For example, if you want to two links to be negative response events, thenyou would specify the NegativeLink property twice.

NegativeLink1=http://www.sas.com/apps/jmp/email_preference.jspNegativeLink2=http://www.sas.com/apps/userid/email_preference.jsp

These links are not selected for tracking in the New Broadcast wizard and New BroadcastContent wizard.

ReplySummaryspecifies whether to include in the default summary report information about the types ofreplies that were received from the e-mail broadcast. Setting this property to true mightincrease the time it takes to generate a broadcast summary. By default, this property is set tofalse.

ReplySummaryPeriodspecifies the number of days to look back in the reply table for determining implicitly corre-lated replies. The period starts from the time and date that you run the reply summary. Bydefault, this property is set to seven days. If you use the default and ran the reply summaryat 9:00am on August 18, then SAS Digital Marketing would look back in the reply tablethrough 9:00am on August 11. If you set this property to 0, then SAS Digital Marketing doesnot include implicitly correlated replies in the reply summary.

NOTE: To use this property, you must also set the ReplySummary property to true.

ResponseTableBasespecifies the prefix for the names of the response tables. The number of response tablesis specified by the MaxResponseTables property. The ResponseTableBase property enablesyou to configure where to save the response tables.

For example, you want to save all the response tables to the SDMDATA library and the prefixfor each table name should be RESPONSE. You set the ResponseTableBase property to SD-MDATA.RESPONSE to automatically save the response tables to the SDMDATA library. Asyou execute the broadcasts, several tables named SDMDATA.RESPONSE_xxx are created inthe SDMDATA library.

After this property is set, the Response table box is not available from the New Broadcastwizard in SAS Digital Marketing Studio. The user also cannot modify the settings for theresponse tables.

By default, this property is set to blank, and the user must specify a value for the responsetable in the New Broadcast wizard and the New Broadcast Content wizard.

NOTE: If you specify both the EmailTrackedVariables and the ResponseTableBase proper-ties and the variable that you specified for the EmailTrackedVariables property exists in yourdata source, then the Tracking panel does not appear in the New Broadcast wizard or the NewBroadcast Content wizard.

sem.testlinkspecifies the link to use when testing the redir tracking servlet. By default, this property isset to http://www.sas.com.

Scheduling Server Properties F 153

TrackMailToLinksspecifies whether to track the e-mail addresses that are specified using mailto tags in theHTML content of a broadcast. The behavior of mailto tags can vary depending on the clientthat is displaying the broadcast. These tracked links are treated the same as other trackedlinks in SAS Digital Marketing Studio. These links appear in the Link Summary section ofthe Summary window. By default, this property is set to false.

VarPassingOverrideselects the Pass tracking variables to the target URLs check box in the New Broadcastwizard. The Pass tracking variables to the target URLs option determines whether trackedvariables are included as parameters in the links that are embedded in the e-mail content.When this property is set to true, the user who is creating a new broadcast definition in SASDigital Marketing Studio cannot specify this option. This property enables the SAS DigitalMarketing administrator to set this option globally for your site. By default, this propertyis not set and the user can choose whether to set the Pass tracking variables to the targetURLs option for each broadcast definition.

Scheduling Server Properties

You can set the following scheduling server properties:

CCAdminspecifies whether SAS Digital Marketing Studio sends a proof copy of all e-mail broadcaststo the e-mail addresses that you specify on the Scheduling tab. By default, this property isset to false.

ExecuteWizardSkipIntrospecifies to skip the first step in the Scheduling wizard, if the table that was defined in thebroadcast definition exists. By default, this property is set to false.

NoSeparateScheduleBrowserspecifies whether the Scheduled Broadcast window appears in a separate window. If thisproperty is set to true, then the Scheduled Broadcast window does not appear in a separatewindow. By default, this property is set to false.

ScheduledKeepPeriodspecifies how many days to keep a broadcast in the scheduling list after the broadcast hasbeen executed. This option enables you to see on the Scheduling tab how many broadcastshave run over X number of days. By default, this property is set to 0, and no broadcasts arekept in this list.

Scheduler24HourTimespecifies whether the time in the Schedule Broadcast wizard appears as 24 hour time. If youset this property to true, then the time that appears in the Time to start broadcast executionbox of the Scheduling panel uses the 24 hour time format. By default, this property is set tofalse and the time values use the AM and PM format.


ScheduleShowTableDescspecifies whether to display the table descriptions in the Schedule Broadcast to Table window.If you set this property to true, then the table descriptions are displayed. By default, thisproperty is set to false.

SchedulingInstalleddetermines whether the scheduling functionality is installed and configured. If this propertyis set to true, then the scheduling functionality is installed. If you use SAS Digital Marketingwith SAS Marketing Automation, then any scheduling should be handled by SAS MarketingAutomation. If another application such as SAS Marketing Automation is going to handlethe scheduling, then you should set this option to false.

Part IV

Maintenance

Chapter 6

Managing Advanced Broadcast Tools

ContentsOverview of Advanced Broadcast Tools . . . . . . . . . . . . . . . . . . . . . . . 158Managing Distribution Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

About Distribution Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Creating a Distribution List . . . . . . . . . . . . . . . . . . . . . . . . . . 158Modifying a Distribution List . . . . . . . . . . . . . . . . . . . . . . . . . 161

Managing Global Data Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166About Global Data Models . . . . . . . . . . . . . . . . . . . . . . . . . . 166Types of Global Data Models . . . . . . . . . . . . . . . . . . . . . . . . . 166

Managing Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167About Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Change Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Managing ASP Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170About ASP Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Using the ASP Definition Manager . . . . . . . . . . . . . . . . . . . . . . 170Modifying the ASP Definition Properties . . . . . . . . . . . . . . . . . . . 171

Managing WAP Integration Broadcasts . . . . . . . . . . . . . . . . . . . . . . . 178About WAP Integration Broadcasts . . . . . . . . . . . . . . . . . . . . . . 178Configuring WAP Integration Broadcasts . . . . . . . . . . . . . . . . . . . 178

Using the SpamAssasin Spam Filter . . . . . . . . . . . . . . . . . . . . . . . . . 181About Spam Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Understanding SpamAssassin . . . . . . . . . . . . . . . . . . . . . . . . . 181Implementing a SpamAssassin Filter . . . . . . . . . . . . . . . . . . . . . 182

Using Geolocation Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183About Geolocation Technology . . . . . . . . . . . . . . . . . . . . . . . . 183Installing a Geolocation Database . . . . . . . . . . . . . . . . . . . . . . . 184Configuring a Server Extension . . . . . . . . . . . . . . . . . . . . . . . . 186MaxMind Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 187

158 F Chapter 6: Managing Advanced Broadcast Tools

Overview of Advanced Broadcast Tools

A broadcast definition contains information that SAS Digital Marketing uses to create, process,and track your e-mail or wireless text message transmissions. A broadcast definition includes abroadcast header, the message content, and metadata. SAS Digital Marketing uses the metadata toidentify the data model for the data source tables, the variables that track e-mail responses, and theusers that have permission to use the broadcast groups and Web resource groups.

As a site administrator, you can use several tools to simplify the creation of broadcast definitions.SAS Digital Marketing provides distribution lists to automate the selection of data source tablesand tracked variables for a broadcast. You can use these distribution lists and server properties tocreate global data models that limit the selection of the data sources for a broadcast. The ASPDefinition Manager enables you to create the metadata for an ASP broadcast. You can also useserver properties to add a spam filter score to the broadcast header when an e-mail broadcast ispreviewed.

Managing Distribution Lists

About Distribution Lists

A distribution list simplifies how a user selects the data source tables and variables that SAS DigitalMarketing uses in the broadcast definition to customize messages and track broadcast responses.Instead of selecting this data when you define, preview, or schedule a broadcast, a distribution listcontains information to assign the data source tables and variables. You can use distribution lists tocreate global data models and limit the data source tables that a user selects. For more information,see “Managing Global Data Models” on page 166.

Creating a Distribution List

Use the New Distribution List wizard to create the distribution list. You must specify the name forthe distribution list, a prefix for the response table, at least one data source table, an address variable,and at least one tracked variable. Currently, SAS Digital Marketing only supports tables as the dataelements. Users are unable to select the address variable or the tracking settings when a distributionlist is used to create a broadcast definition.

NOTE: You can also create a distribution list by running a SAS job in batch mode. SAS DigitalMarketing provides a SAS progam, called Example - Managing Distribution Lists, in the SASJob Editor under the Batch Jobs folder that you can modify. For more information, see “Workingwith SAS Jobs” on page 192.

Creating a Distribution List F 159

Run the New Distribution List Wizard

To create a distribution list, complete the following steps:

1. Select Server Configuration from the Tools menu in the SAS Digital Marketing window.Then select the Distribution List Manager from the Broadcast Definition node and clickAdd. The New Distribution List wizard opens.

2. Type the name for the distribution list, an optional description, and a prefix for the responsetable name. Then, selet the broadcast channel, and click Next.

In the Response table base name box, enter the prefix value to create a valid JDBC tablename. SAS Digital Marketing automatically assigns the response table name when you createa new e-mail broadcast definition.

Use the Channels box to specify whether the distribution list is for an e-mail or a phonechannel. SAS Digital Marketing uses the channel to determine the distribution lists that areavailable in the New Broadcast wizard. Select E-mail to create a distribution list for e-mailand multichannel broadcasts. Select Phone for SMS and ASP broadcasts.


3. Specify the data source tables, also called data elements, for the distribution list and clickNext. You can use multiple tables.

To select an element for the distribution list, complete the following steps:

a) Click Add. The Open Table dialog box appears.

b) Select the JDBC data table that contains the recipient information.

c) Click OK.

If you do not want to use a table, select the table name and click Remove. If you want toexamine the structure of a table, select the table name and click Details. The Properties dialogbox appears. Use the Columns tab to view the variables in the table.

When the recipients for the broadcast transmissions are stored in multiple tables, create alogical message group by selecting multiple data source tables. However, each table must usethe same variable to store the e-mail address or phone number of the recipients.

4. Specify the address variable, select the variables to e-mail responses, and click Finish. If youwant to change a setting, then click Back to return to the appropriate step in the wizard.

Modifying a Distribution List F 161

In the Address variable drop-down list, select the name of the variable in the table thatcontains e-mail addresses or wireless phone numbers. Use the Distribution List Variablesbox to select the variables that SAS Digital Marketing includes in the response table whenyou track the response to an e-mail broadcast.

Modifying a Distribution List

To modify a distribution list, select Server Configuration from the Tools menu in the SAS DigitalMarketing window and then select the Distribution List Manager from the Broadcast Definitionnode.

You use the Distribution List Manager to perform the following actions:

Addcreates a new distribution list.

Editdisplays or modifies the properties of an existing distribution list.

Removedeletes a distribution list.


To modify a distribution list, select the name of distribution list and click Edit. The Propertiesdialog box opens. A series of tabs enable you to view and change the properties for the distributionlist.

General Tab

Use the General tab to change the name of the distribution list, the optional description, the prefixfor the response table, and broadcast channel.


Variables Tab

Use the Variables tab to change the address variable and the tracked variables.

The value in the Address variable drop-down list identifies the variable in the data table that con-tains e-mail addresses or wireless phone numbers. The Distribution List Variables box identifiesthe variables that SAS Digital Marketing includes in the response table when you track the responseto an e-mail broadcast.


Elements Tab

Use the Elements tab to change the data source table or to select additional data source tables. Eachtable is one element of the distribution list. When you have multiple data elements, each table mustuse the same variable to store the e-mail address or phone number of the recipients.

To select an element for the distribution list, click Add. The Open Table dialog box appears. Selectthe JDBC data table that contains the recipient information and click OK. If you do not want touse a table, select the table name and click Remove. To examine the table structure for an element,select the table name and click Details. The Properties dialog box appears. Use the Columns tabto view the variables in the table.


Security Tab

Use the Security tab to set read and write permission for an individual user or a group of users in abroadcast definition that is created with the distribution list. For more information, see “ManagingSecurity” on page 167.


Managing Global Data Models

About Global Data Models

You use global data models to identify the underlying structure of the data source tables that SASDigital Marketing clients require to create a broadcast definition. A series of server propertiesenable you to create global data models. SAS Digital Marketing supports three types of global datamodels.

NOTE: You can also use a Customer Intelligence (CI) export definition as the data source. SASDigital Marketing retrieves the export database from the SAS Customer Intelligence software tocreate the broadcast definition.

Types of Global Data Models

No Global Data Model

By default, SAS Digital Marketing does not provide a global data model. Consequently, when abroadcast is created, a user must specify the data source table for the broadcast. When a new e-mailbroadcast is created, the user also specifies the response data table and the variables in the datasource table to track the broadcast response.

Fixed Number of Global Data Models

SAS Digital Marketing uses distribution lists to support a fixed number of global data models. Tocreate a fixed number of global data models, complete the following steps:

1. Create a distribution list for each data model. The distribution list includes the responsetable, the recipient data source, the address variable, and the tracked variables. For moreinformation, see “Managing Distribution Lists” on page 158.

2. Set the HideTables server property to true. SAS Digital Marketing restricts the data sourcesfor the broadcast definitions by prohibiting the selection of JDBC data tables in the NewBroadcast wizard. Users must select a distribution list for the data model.

After you create a fixed number of global data models, the Data Model tab in the Properties dialogbox displays the distribution lists.

Managing Security F 167

One Global Data Model

You can create a single global data model so that everyone at your site uses the same data structureto create their broadcasts. To support one global data model, you must set the following serverproperties:

EmailVariablesspecifies the variables that are in the recipient table. When you set this property, the usercannot select the data source table for the broadcast definition.

EmailAddressVariablespecifies the e-mail address variable for any new broadcasts. When you set this property, theuser cannot change the address variable for the broadcast header.

EmailTrackedVariablesspecifies the tracked variables to use for an e-mail broadcast. When you set this property,the user cannot change the tracked variable that SAS Digital Marketing stores in the responsetable.

ResponseTableBasespecifies the prefix for the names of the response tables. When you set this property, thenusers cannot assign the name for the response table.

NOTE: When you set these sever properties, SAS Digital Marketing uses only one data model tocreate a new broadcast definition. Distribution lists are not available.

For more information about the e-mail server properties, see “Client User Interface Server Prop-erties” on page 135. For more information about the ResponseTableBase server property, see“Response Server Properties” on page 151.

Managing Security

About Security

SAS Digital Marketing enables you to configure a broadcast group, a distribution list, a Web re-source group, or an RSS feed channel that grants read and write permission for an individual useror a group of users. You create user groups, that consolidate a group of users, on a SAS DigitalMarketing server in order to simplify how permission is granted. For more information, see “UserGroup Settings” on page 132.

Use the Security tab in the Properties dialog box to set security for an individual or user group.When a user has write authorization (at least Level 2 permission), you can deny write permission.When a user has read authorization (Level 1 permission) only, you cannot grant write permission.


Change Security

To change the authorization for a user or group of users, complete the following steps:

1. Open the Properties dialog box.

� For a broadcast group, select the folder in the navigation tree. Then select Propertiesfrom the pop-up menu.

� For a Web resource group, select a folder or a file in the Web Resources tab. Thenselect Properties from the pop-up menu.

� For an RSS feed, select an RSS feed channel in the RSS Feeds tab. Then select Prop-erties from the pop-up menu.

� For a distribution list, select Distribution List Manager from the Broadcast Definitionnode in the Server Configuration window. Select the distribution list and click Edit.

2. Select the Security tab and click Add.

3. Select the users or user groups that you want to change the read or write permission for andclick OK.

To select multiple users, press down the CTRL key and click the rows with the user name oruser group.

Change Security F 169

4. To change the authorization, select the user name or user group from the list of users. Thenuse the Permissions table to select either Allow or Deny to set read and write permission.

To grant a user only read authorization, select Allow in the Read row and Deny in the Writerow.

5. After you grant all the permissions, click OK.

By default, SAS Digital Marketing grants both read and write authorization to every user that has atleast Level 2 permission. To change the authorization for individual users, complete the followingsteps:

1. Select All Users and click Deny in the Write row.

2. Click Add and select the individual users or groups of users that should have write permission.Then click OK.

3. Select a user from the list of users, and then select Allow in the Write row.

4. After you grant all the permissions, click OK.

If you decide to delete a user or group from the list, then select the user name or user group andclick Remove. You cannot remove the All Users group.


Managing ASP Definitions

About ASP Definitions

Each ASP requires different parameters to connect to and send customized SMS, MMS, and WAPPush messages. SAS Digital Marketing provides a generic interface to create the structure andmetadata for an ASP broadcast definition. You can use the ASP Definition Manager to add new ormodify existing ASP broadcast types that are based on the API specifications of a third-party ASP.

SAS Digital Marketing stores the metadata for the ASP broadcast types in XSL files that are locatedin the ROOT/asps directory. You should not edit the XSL files directly. Instead, you should usethe ASP Definition Manager.

You must acquire from the ASP the specifications for the HTTP interface. The specifications areused when you create a new ASP broadcast. In order for an ASP broadcast definition to sendbroadcast messages, you must register with the ASP and purchase credits to use their service. Forexample, you might want to create ASP broadcast definitions that send SMS messages through aClickatell SMS gateway. To create a new ASP broadcast type, you use the API specifications forSMS that are located at http://www.clickatell.com.

To send an ASP broadcast behind a firewall, you must configure the SAS Digital Marketing serverto use proxy and port security settings. Use Security Options from the Server node in the ServerConfiguration window and select Use an internet proxy to specify your proxy and port settings.For more information, see “Security Options” on page 128.

Using the ASP Definition Manager

To create or modify the metadata for an ASP broadcast type, select Server Configuration from theTools menu in the SAS Digital Marketing window and then select the ASP Definitions Managerfrom the Broadcast Definition node. The ASP Definition Manager window opens.

Modifying the ASP Definition Properties F 171

The available ASP broadcast types appear in the ASP Definitions list. SAS Digital Marketingprovides the Clickatell SMS and Clickatell WAP broadcast types as examples of a third-partyASP. To use these ASP definitions, you must register with Clickatell and purchase credits athttp://www.clickatell.com. SAS Digital Marketing also provides the NowSMS broadcasttype to send mobile messages to the Now SMS/MMS gateway (NowSMS) when a GSM deviceor mobile phone is connected to a SAS Digital Marketing server. For more information, seehttp://www.nowsms.com.

You can perform the following actions in the ASP Definition Manager window:

Addcreates a new ASP definition type. To add an ASP definition, click Add. The ASP DefinitionProperties dialog box opens.

Editdisplays or modifies the properties of an existing ASP definition type. To view the propertiesof an ASP definition, select the name in the ASP Definitions list and click Edit. The ASPDefinition Properties dialog box opens.

Removedeletes an ASP definition type. To remove a definition, select the name from the ASP Defini-tions box and click Remove.

Donecloses the window.

Modifying the ASP Definition Properties

If you select Add or Edit in the ASP Definition Manager, then the ASP Definition Properties dialogbox opens. A series of tabs enable you to view and change the properties for an ASP definition type.You define parameters that match the API specifications of the third-party ASP. The New Broadcastwizard automatically includes the ASP broadcast definition types and incorporates the parametersin the wizard steps.

General Tab

Use the General tab to create the name for the ASP definition and to provide information about theASP specifications.


You can specify the following items on the General tab:

Namespecifies the name for the ASP broadcast type. The New Broadcast wizard displays this namein the Broadcast Type drop-down list.

Descriptionspecifies descriptive text about the ASP broadcast type. Format the text with HTML tags. TheNew Broadcast wizard displays the description after you select the broadcast type from theBroadcast Type drop-down list.

URLspecifies the Web address of the HTTP-to-SMS gateway. The Web address corresponds to anASP specification on where to post the HTTP request.

Response Decoderspecifies the class name of the decoder that SAS Digital Marketing uses to interpret the HTTPresponse. For more information, see “Implementing an Automatic ASP Response Decoder”on page 177.

To use the NowSMS ASP to send SMS messages through an HTTP post interface, you might enterthe following information:

Name: NowSMS

Description: <html>NowSMS is an easy-to-install SMS Gateway, MMS Gateway,WAP Push Proxy Gateway, and Multimedia Messaging Center (MMSC)for Windows NT/2000/XP. For more information about NowSMS, seehttp://nowsms.com. <p><p>To use the NowSMS gateway you must have aGSM modem or a phone connected to your SAS Digital Marketing server.


URL: http://serverlocation:8800/?

Response Decoder: AspResponseDecoder

NOTE: (Optional) You can write a custom decoder to interpret the responses that are receivedfrom the ASP. Use the specifications to determine the content of their responses. You can ex-amine ClickatellDecoder.java as an example of a decoder. For more information, see“Implementing an Automatic ASP Response Decoder” on page 177.

Administrative Tab

Use the Administrative tab to specify the parameters that the ASP uses to authenticate your requestfor access to the HTTP post interface. Administrative parameters usually occur one time in the ASPrequest and have a fixed value such as user ID, password, and api ID. The New Broadcast wizardprompts you for the Administrative parameters and stores the values in the ASP broadcast definition.

You can perform the following actions on the Administrative tab:

Addcreates a new administrative parameter. To add a parameter, click Add. The Parameter Prop-erties dialog box opens.

Modifymodifies the properties of an existing administrative parameter. To change the properties,select the name of the parameter and click Modify. The Parameter Properties dialog boxopens.


Removedeletes an administrative parameter. To remove a parameter, select the row with the name ofthe parameter and click Remove.

To define an administrative parameter, you specify the name of the parameter, a descriptive label,and the default value in the Parameter Properties dialog box. You also set whether the parameter isrequired by the ASP or is a password.

The value in the Name box corresponds to the name of the parameter that SAS Digital Marketingadds to the URL that gets posted to the ASP’s HTTP interface. The value in the Label box is usedby the New Broadcast wizard to describe the parameter. The value in the Default Value box is usedby the New Broadcast wizard to automatically assign a default value for the parameter.

You must define the parameters that the ASP requires on either the Administrative Parameterstab or the Parameters tab and select the Parameter is required to use ASP check box. When theNew Broadcast wizard prompts for the administrative parameters, you must specify the value ofa required parameter; otherwise, the wizard does not move to the next step. Set a parameter as apassword by selecting Parameter is used to specify a password. The New Broadcast wizard hidesthe password by displaying asterisks instead of the actual value.

To use theNowSMS ASP to send SMS messages, you create the following two administrative pa-rameters:

Name: User

Label: User:

Default Value:

Name: Password

Label: Password:

Default Value:


For both parameters, select Parameter is required to use ASP. For the password parameter, selectParameter is used to specify a password.

Parameters Tab

Use the Parameters tab to specify the remaining parameters that the ASP needs in order to de-liver SMS, MMS, or WAP Push messages. The New Broadcast wizard prompts you for the ASPparameters and stores the values in the ASP broadcast definition.

You can perform the following actions on the Parameters tab:

Addcreates a new non-administrative parameter. To add a parameter, click Add. The ParameterProperties dialog box opens.

Modifymodifies the properties of an existing parameter. To change the properties, select the name ofthe parameter and click Modify. The Parameter Properties dialog box opens.

Removedeletes a non-administrative parameter. To remove a parameter, select the row with the nameof the parameter and click Remove.

To define a non-administrative parameter, you specify the name of the parameter, a descriptive label,and the default value in the Parameter Properties dialog box. You also set whether the parameter isrequired by the ASP or is an address variable.


Every ASP SMS request to the HTTP post interface must include the recipient phone number andthe message content that you want sent to the recipient. You must examine the API specificationsof the third-party ASP to determine the parameters that specify this information.

Select Parameter is required to use ASP for parameters that are required by the ASP HTTPinterface. When the New Broadcast wizard prompts for the non-administrative parameters, youmust specify the value of a required parameter; otherwise, the wizard does not move to the nextstep.

Select Parameter specifies a WAP URL to use the parameter in the New Broadcast wizard tocreate a WAP integration broadcast.

Select Parameter is used to specify the recipient address variable to set the parameter that spec-ifies the column with the recipient phone numbers. The New Broadcast wizard requires that at leastone parameter contain the phone numbers. If you assign a default value, then use the variable in thedata source table that contains the phone numbers for the recipients.

To use the NowSMS ASP to send SMS messages, you might create the following non-administrativeparameters:

Name: Text

Label: Text:

Default Value: SMS message

Name: Phone number

Label: To:

Default Value:


For both parameters, select Parameter is required to use ASP. For the first parameter, selectParameter is used to specify the recipient address variable.

Implementing an Automatic ASP Response Decoder

You can implement a response decoder to interpret each HTTP response. The response decoderdecodes the HTTP response that is written to the audit table and provides an understandable formatin the Query Response window. You use the AuditAspRequest server property to specify that thedecoded response information is written to the audit table when the ASP broadcast definition isexecuted. The variable in the audit table is called aspresp. For more information, see “AuditServer Properties” on page 134 and “Auditing Broadcast Transmissions” (Chapter 4, SAS DigitalMarketing: User’s Guide).

Suppose you send a request to the ASP and receive the following response:

to=19191234567;result=200;msg_id=115247;

You might want an interpretation of this response written to the audit table:

200: Success; msg_id=117206;

This message enables you to quickly understand the response information, such as a successfultransmission, without having to examine the API specifications.

SAS Digital Marketing provides one sample decoder, ClickatellDecoder.java. To use theClickatellDecoder you must revise &user=user, &password=password, and &api=api tocorrespond to your Clickatell user ID, password, and api ID. Then you recompile the class.

Your response decoder must meet the following specifications:

� stores the compiled class in the ROOT directory on the SAS Digital Marketing server.

� includes a static method called decode that uses an input parameter of type String to takethe response string and a return parameter of type String to return the decoded response.Here is an example of a sample signature:

public static String decode(String response)

NOTE: After the class is compiled, you must restart the SAS Digital Marketing server in order touse any changes to the response decoder program.


Managing WAP Integration Broadcasts

About WAP Integration Broadcasts

A Wireless Application Protocol (WAP) integration broadcast uses the WAP URL address in anASP broadcast definition to deliver mobile HTML content for the multichannel broadcast. Youconfigure a WAP integration broadcast so that the interaction between the multichannel broadcastand WAP integration broadcast is transparent when the multichannel broadcast is scheduled.

Configuring WAP Integration Broadcasts

To configure a WAP integration broadcast, complete the following steps:

1. Register with an ASP provider and purchase credit, such as Clickatell for sending mobilemessages. Then use the ASP Definition Manager to define a connection to your ASP provider.Test your driver and verify that you can use the ASP definition to send an SMS message. Formore information, “Using the ASP Definition Manager” on page 170.

2. In the ASP Definition Manager, select the ASP definition that you created in the previous stepand click Duplicate. Specify a unique name for the new ASP definition.

3. Select the new ASP definition and click Edit. In the ASP Definition Properties dialog box,select the Parameters tab. Then select the WAP URL parameter and click Modify.

Configuring WAP Integration Broadcasts F 179

4. Select Parameter specifies a WAP URL and click OK. To save the ASP definition, clickOK.


5. Use this ASP definition in the New Broadcast wizard to create a new ASP broadcast. Thedefault WAP URL address is

http://www.google.com/m?q=sas.

To modify the URL address, use the Broadcast Properties dialog box.

For more information, see “Using Broadcast Properties” (Chapter 4, SAS Digital Marketing:User’s Guide).

6. Select Test on the General tab in the Broadcast Properties dialog box. Enter a mobile devicephone number and click OK.

7. Verify that the mobile device received the HTML content.

Using the SpamAssasin Spam Filter F 181

You can define several WAP integration broadcasts. To set the default WAP integration broadcast,use the WAP Integration Options in the Server Configuration window. After you set the WAPintegration option, all multichannel broadcasts automatically use this WAP integration broadcast tosend HTML content to a mobile device. For more information, see “WAP Integration Options” onpage 119.

To change the WAP Integration broadcast after the multichannel broadcast is created, use the WAPtab in the broadcast properties dialog box. For more information, see “WAP Properties” (Chapter 4,SAS Digital Marketing: User’s Guide).

Using the SpamAssasin Spam Filter

About Spam Filters

SAS Digital Marketing provides tools that enables you to compute spam filter scores for e-mailbroadcast messages. Mail filters use this score to identify e-mail messages as unsolicited commer-cial e-mail (UCE) or spam. You can use SpamAssassin to integrate spam filter scores in the previewfunctionality of SAS Digital Marketing when an e-mail message is sent.

Understanding SpamAssassin

SpamAssassin is open source software for e-mail spam filtering that is based on content-matchingrules. A large set of rules is provided that determine whether an e-mail message is spam. Spa-mAssassin searches specific fields in the e-mail header and the e-mail body for the occurrence ofcertain expressions. If a match is found, then the e-mail is assigned a spam filter score. SpamAssas-sin can add customizable e-mail header information to the e-mail message that includes the spamfilter score. The e-mail recipient or Internet service provider might use the score that results frommultiple tests or other criteria to determine whether the e-mail message is placed in a spam folder,deleted, or flagged. You can configure SAS Digital Marketing to display the SpamAssassin scorewhen an e-mail broadcast is previewed.

Each SpamAssasin test consists of a label and a description. Usually the label is an upper caseidentifier that is separated by underscores, such as LIMITED_TIME_ONLY. The description forthis label might be Offers a limited time offer. E-mail passes the test when the message containscertain variants of a phrase, such as limited time only. If SpamAssassin assigns +0.3 as the spamfilter score, then the e-mail must pass additional tests in order to meet a spam threshold. After thespam filter score reaches the spam threshold (5), SpamAssassin classifies the e-mail as spam. Sometests, such as those for invalid message IDs or years, are assigned a very high score, so that a singletest might cause the e-mail to meet the spam threshold.

When the total spam filter score is above the value of the required_hits setting that is specified in


the SpamAssassin configuration, the e-mail is identified as spam and rewritten according to severaloptions. For the default configuration, SpamAssassin appends the content of the e-mail as a MIMEattachment, with a brief excerpt in the message body, and a description of the tests that classifiedthe e-mail as spam. If the score is lower, then information about the passed tests and the total scoreis added to the e-mail headers. This score might be used in post-processing for less severe actions,such as tagging the e-mail as suspicious.

Implementing a SpamAssassin Filter

SAS Digital Marketing uses the version of SpamAssassin that is licensed by Perl(Mail::SpamAssassin in CPAN). For information about how to install SpamAssassin, seeSpamAssassin by Alan Schwartz. To use SpamAssassin with SAS Digital Marketing, you needonly the basic SpamAssassin shell script or BAT file. This script processes an incoming MIMEmessage on standard input and then outputs the scored message. You configure SAS DigitalMarketing to use SpamAssassin during an e-mail preview by setting the SpamScanClass andSpamAssassinCommand server properties.

Set the Spam Server Properties

To use SAS Digital Marketing with the versions of SpamAssassin that are licensed by Perl, completethe following steps:

1. Set the SpamAssassinCommand server property to the SpamAssassin shell script or BAT fileon your computer. If you run SpamAssassin as a daemon, then set the SpamAssassinCom-mand server property to SPAMC.EXE.

2. Set the SpamScanClass server property to use com.sas.email.server.BulkEmailUtils so thatSAS Digital Marketing uses a scanMessage implementation.

After you set the server properties, validate your SpamAssassin integration in a SAS Digital Mar-keting client. Use the broadcast definition in the Samples/E-mail folder to preview the EdumationMonthly Newsletter. This message generates a score of 1.4 that is below the default spam thresh-old value of 5.0. To see the spam filter score, examine the e-mail header in your e-mail reader.For more information, see “Examining the Spam Filter Score” (Chapter 4, SAS Digital Marketing:User’s Guide).

Using Geolocation Technology F 183

Using Geolocation Technology

About Geolocation Technology

SAS Digital Marketing can use geolocation technologies to support Geo marketing analysis. Thistechnology uses IP addresses to determine a user’s geographic latitude, longitude and, by infer-ence, city, region, and country. A user’s IP address is compared with known locations of otherelectronically neighboring servers and routers

Geo marketing analysis enables you to display data in a geographical context and to:

� determine the location of your customers

� characterize your customers or make inferences based on IP registration

� visualize the data in a geographic context by generating a digital map

� calculate summary information for specific locations

� view customer response within specific locations

SAS Digital Marketing can use MaxMind (www.maxmind.com) technologies to augment your re-sponse data. The response table contains geographical information based on recipient e-mail ad-dresses and the location of the response. While geolocation has some inherent precision problems,this technology is used for fraud detection and criminal investigations. As broadband support be-comes more prevalent over dial-up Internet access, the correlation between IP address and physicallocation becomes more accurate.

Once your response data is augmented with geographical information, you can visualize your e-mailresponse using SAS/GRAPH software.


You can also use the SAS language adapter to connect the geographic information to your selectionprocess and further segment the customers that receive particular e-mail offers. For more informa-tion, see Chapter 7, “Managing SAS Jobs.”

Installing a Geolocation Database

Several vendors provide IP registration data to support geolocation. SAS Digital Marketing inte-grates with MaxMind GeoIP City Database. A free version of the product, called GeoLite City,enables you to develop and test your geo marketing strategies. When the geo marketing strategy isready to deploy, you should purchase the more extensive database along with a subscription to keepthe database accurate.

To install MaxMind GeoIP City Database, complete the following steps:

1. Download the binary format of the GeoCity Lite or GeoCity database from:

http://www.maxmind.com/app/city

Installing a Geolocation Database F 185

This version of the database uses an open source Java API to efficiently search the database.

2. Unpack the binary archive file GeoLiteCity.dat or GeoIPCity.dat with a file com-pression utility such as WinZip. Store the file in the ROOT/config directory on the SASDigital Marketing server.

3. Download the latest version of the Java API from:

http://www.maxmind.com/download/geoip/api/java/

Unpack the archive file GeoIPJava-n.zip with a file compression utility such as WinZip.Store the file in a directory on the SAS Digital Marketing server such as c:/geobuild.

4. Build the Java API. MaxMind provides only the Java API in source form. To build theJava API, use a 1.4.n Java software development kit (SDK) that is available from the SunDeveloper Network at:

http://java.sun.com/j2se/1.4.2/download.html

5. In the DOS Prompt window, change the directory to the Java source directory undersource/com/maxmind/geoip. Compile the source jars by executing the following com-mand:

javac *.java


6. Back up the source directory and the jar file by executing the following command:

jar -cvf geocity.jar *

7. Copy the support jar file, geocity.jar, to the ROOT/lib directory on the SAS DigitalMarketing server.

Configuring a Server Extension

In order to access MaxMind GeoIP City Database, you must configure SAS Digital Marketing touse the MaxMind server extension. A server extension is a protected thread that is invoked whenthe SAS Digital Marketing server starts. In this thread you can perform periodic processing thatfacilitates reporting or integrates with other business processes.

MaxMind Server Properties F 187

SAS Digital Marketing automatically provides a MaxMind server extension. The server extensionsource is also provided in the ROOT/doc/javaext directory. This server extension periodicallyruns and augments the response data with geographic information.

To configure a server extension you must set the SEMServerExtension family of server propertiesin the server.properties file in the ROOT/config directory. To use the MaxMind serverextension, add the following server property:

SEMServerExtension1=MaxMindExtension

MaxMind Server Properties

SAS Digital Marketing provides the following server properties that are specific to the MaxMindserver extension:

MaxMindDatFilespecifies the complete path to the MaxMind DAT file. By default, SAS Digital Marketingsearches for GeoCity.dat or GeoLitCity.dat in the ROOT/config directory on theserver.

MaxMindServerspecifies the SAS Digital Marketing server that you want to use. By default, this property isset to localhost:9221.

MaxMindUserspecifies the user ID for the SAS Digital Marketing server that you specified in the Max-MindServer property.

MaxMindPasswordspecifies the password for the SAS Digital Marketing server that you specified in the Max-MindServer property.

MaxMindPeriodspecifies the period in days from the date of execution to continue to augment response data.By default SAS Digital Marketing augments only broadcasts that have executed in the past30 days. To improve performance, SAS Digital Marketing limits the length of the period.

MaxMindIntervalspecifies the interval in minutes to wait between each augmentation of the response data.By default the extension augments the response data with geographic information every 15minutes.

Verify the Geolocation Database

After the server is configured, you can examine the server log to verify that the MaxMind serverextension is running.

NOTE: MaxMind extension being installed.


NOTE: Checking for "\SASDigitalMarketing\5.1\.\config\GeoCity.dat"NOTE: Checking for "\SASDigitalMarketing\5.1\.\config\GeoLiteCity.dat"NOTE: MaxMind extension now running.

When the server extension executes, the log indicates how many IP addresses have resolved alongwith any errors that might have occurred.

NOTE: Augmenting response table for ’6183_both’ (Broadcast_zrn4k2)NOTE: Found 4 IP addresses to resolve.NOTE: Augmentation took 3234 milliseconds.NOTE: Augmenting response table for ’6211_Both’ (Broadcast_ysi8g2)NOTE: Found 0 IP addresses to resolve.NOTE: Augmentation took 641 milliseconds.NOTE: Augmenting response table for ’6245_both’ (Broadcast_108q8xv)NOTE: Found 0 IP addresses to resolve.

If you have pre-existing response data, then the first execution of the MaxMind server extensionmight require a considerable amount of processing time (hours). After the initial argumentation ofthe response data is complete, updates to new response data should require less than a minute.

When the server log contains no error messages, the MaxMind extension is properly configuredon the SAS Digital Marketing server so that your response data is automatically augmented withgeographic information. For information about the response table, “Response Table Layout” (Chap-ter A, SAS Digital Marketing: User’s Guide).

Maintain the Geolocation Database

The MaxMind GeoLite City database is less accurate and updated on a quarterly basis. For the mostaccurate response data, you should purchase the more extensive MaxMind GeoIP City databasealong with a subscription and regularly refresh the data.

To refresh the data with a new DAT file, complete the following steps:

1. Stop the SAS Digital Marketing server by selecting Stop from the Actions menu.

2. Copy the new DAT file to the ROOT/config directory on the SAS Digital Marketing server.

3. Restart your SAS Digital Marketing server.

Chapter 7

Managing SAS Jobs

ContentsOverview of the SAS Language Adapter . . . . . . . . . . . . . . . . . . . . . . . 190

Understanding the SAS Language Adapter . . . . . . . . . . . . . . . . . . 190How the SAS Language Adapter Works . . . . . . . . . . . . . . . . . . . . 190

Working with SAS Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192What Is a SAS Job? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192About the SAS Job Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 192Create a SAS Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Edit a SAS Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Remove a SAS Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Rename a SAS Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Developing SAS Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Working with the SAS Job Editor . . . . . . . . . . . . . . . . . . . . . . . 195Viewing the Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Selecting the Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Viewing the Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Viewing the Compiled SAS Code . . . . . . . . . . . . . . . . . . . . . . . 199Accessing Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Setting Preferences for the SAS Job Editor . . . . . . . . . . . . . . . . . . 203

Consolidating Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206About Consolidating Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Using the Default SAS Macros . . . . . . . . . . . . . . . . . . . . . . . . 206

190 F Chapter 7: Managing SAS Jobs

Overview of the SAS Language Adapter

Understanding the SAS Language Adapter

The SAS language adapter enables you (as the site administrator) to access the data and broad-cast definitions in SAS Extraction, Transformation, and Load (ETL) processes from SAS DigitalMarketing. The SAS language adapter eliminates the need for separate connections to the differentdatabases that contains SAS Digital Marketing data. Instead, you can connect to the SAS DigitalMarketing server to access the response data that is associated with SAS Digital Marketing broad-casts.

The advantages of using the SAS language adapter rather than accessing the SAS Digital Marketingdata directly are the following:

� Using the Web tier prevents the SAS code from having to know how to correlate the broadcastmonikers to database tables.

� You need to connect only to the SAS Digital Marketing server rather than connecting to eachdatabase that SAS Digital Marketing is configured to use. Consequently, if the administratorchanges the database, your SAS code is not affected by these changes. The code automaticallydetects the new data location.

You can use the SAS language adapter to do the following:

� to run several advanced reports, such as an audit histogram, a reply histogram, or a responsehistogram. For more information, see “Viewing SAS Reports” (Chapter 4, SAS Digital Mar-keting: User’s Guide).

� to consolidate SAS Digital Marketing data with the data from other solutions and businessprocesses. For more information, see “Consolidating Data” on page 206.

NOTE: You must have administrative privileges (Level 4 permission) to manage SAS jobs.

How the SAS Language Adapter Works

The SAS language adapter consists of several pieces that you must install and configure. Forinformation about installation requirements and how to configure the SAS language adapter, see“Implementing the SAS Language Adapter” on page 86.

NOTE: To generate SAS reports in multiple languages, such as Asian language and non-Asianlanguage, install Foundation SAS to use UTF-8 encoding. Make sure Foundation SAS supports bothUNICODE and DBCS. If batch SAS is used as your SAS environment and the default configuration

How the SAS Language Adapter Works F 191

for your SAS session does not use UTF-8 mode, then use the BatchSASOptions server property toset the ENCODING= option to use UTF-8. For additional information, see “Integration Utils ServerProperties” on page 141. If an IOM workspace server is used as your SAS environment, then seeSAS 9.1.3 Integration Technologies Server Administor’s Guide for information how to configureyour workspace server to use UTF-8 mode.

After you have configured the SAS language adapter, you can create and manage SAS jobs fromSAS Digital Marketing. When you execute the SAS job, the SAS program uses the Web reportingtier to query broadcast data as an XML stream. The SAS program that you develop using the SASlanguage adapter in SAS Digital Marketing can be run in any SAS® 9 environment, such as thefollowing:

� interactive SAS environment

� batch mode

� SAS Data Integration Studio

� SAS Enterprise Guide

� on the SAS Stored Process Server

The SAS Digital Marketing server provides an environment for running and developing SAS pro-grams that can be used with SAS Digital Marketing.

The following figure shows how the SAS language adapter works:

Figure 7.1 How the SAS Language Adapter Works


After the user executes a SAS program in any execution environment, the Web reporting tier iscalled from SAS using the URL access method to retrieve the XML query. An XML LIBNAMEis assigned to the URL FILEREF. Then by using the SAS Digital Marketing server, a SAS ETLprocess can access the broadcast data (from the response, reply, customer, or audit databases) likeany other SAS data set.

Working with SAS Jobs

What Is a SAS Job?

A SAS job is the file that contains the SAS code that you run to generate a SAS report or toconsolidate data. These jobs are organized into the following groups:

Group ReportsWhen you execute a SAS job in this group, the SAS code runs against all of the broadcasts inthe selected broadcast group.

Broadcast ReportsWhen you execute a SAS job in this group, the SAS code runs against the currently selectedbroadcast.

Batch JobsWhen you execute a SAS job in this group, the SAS code consolidates the data from SASDigital Marketing with the data from another application or process.

About the SAS Job Manager

SAS Digital Marketing ships with several default SAS jobs that create reply, send, and responsehistogram reports. You can use this SAS code as the basis for developing other reports for otherexecution environments. You can manage these reports from the SAS Job Manager.

To open the SAS Job Manager, select SAS Manage Jobs from the Tools menu.

Create a SAS Job F 193

Create a SAS Job

To create a SAS job, complete the following steps:

1. In SAS Digital Marketing, select Manage SAS Jobs from the Tools menu. The SAS JobManager dialog box opens.

2. Click Add. The New SAS Job dialog box opens.

3. In the Name box, specify the name of the new SAS job.

4. From the Type drop-down list, select the category for the job. You can choose from thefollowing types: Broadcast Report, Group Report, or Batch Job.

5. Select the Open new job in editor check box if you want the job to open in the SAS JobEditor after you click OK. For more information, see “Developing SAS Code” on page 195.

6. Click OK.


Edit a SAS Job

To edit a SAS job, complete the following steps:


2. From the list of SAS jobs, select the job that you want to edit and click Edit. The SAS JobEditor opens. For more information, see “Developing SAS Code” on page 195.

Remove a SAS Job

To delete a SAS job, complete the following steps:


2. From the list of SAS jobs, select the job that you want to delete and click Remove. A dialogbox prompts you to confirm this deletion. Click Yes. The SAS job is deleted from the SASJob Manager.

Rename a SAS Job

To rename a SAS job, complete the following steps:


2. From the list of SAS jobs, select the job that you want to rename and click Rename. TheRename dialog box opens.

3. In the New Name box, type the new name of the SAS job. Click OK. The new name for thejob appears in the SAS Job Manager.

Working with the SAS Job Editor F 195

Developing SAS Code

Working with the SAS Job Editor

Using the SAS Job Editor, you can edit the SAS code in your SAS jobs to customize and developnew reports.

The upper portion of the window displays the SAS code and the report that was created from anycode that you submitted. If no code has been submitted yet, then the text Select submit toexecute the SAS job is visible.


NOTE: If you are developing SAS code using the JAVA SAS/GRAPH driver, then any graphicaloutput in the report does not appear in the SAS Job Editor. When you submit the SAS code, anexternal Web browser window (such as Internet Explorer) opens to display the report. For moreinformation about how each graph device driver works with SAS reports, see “Requirements forViewing SAS Reports” (Chapter 2, SAS Digital Marketing: Web Studio User’s Guide).

The lower portion of the window contains the following tabs:

Log tabdisplays events from executing the SAS code and any errors. The log includes the time whenthe SAS code is executed and the total processing time.

Target tabenables you to select the group or broadcast against which to run the report.

NOTE: This tab is not available if you are editing a batch SAS job.

Properties tablists the properties of the current report.

Compiled SAS Code tabdisplays the compiled SAS code that you can run in any execution environment.

Viewing the Log

The Log tab reports the events from running the SAS code and any errors or warnings.

Selecting the Target F 197

After SAS Digital Marketing runs the SAS code, the icon on the Log tab changes to one of thefollowing:

� specifies that the code ran with no errors or warnings.

� specifies that an error occurred when running the SAS code. You should review theseerrors in the log.

� specifies that a warning was generated when running the SAS code. You should reviewthese warnings in the log.

The log also includes the time when the SAS code is executed and the total processing time.

Selecting the Target

The Target tab lists the groups or broadcasts against which you can run the report.


� If you selected a group report, then this tab lists the groups that you defined in SAS DigitalMarketing Web Studio. From this tab, you can select the group to use to run the report.

� If you selected a broadcast report, then this tab lists all of the broadcasts. From this tab, youcan select the broadcast to use to run the report.

NOTE: This tab is not available if you are editing a batch SAS job.

Viewing the Properties

The Properties tab lists the properties for the current report. You can see the graph device for thereport, whether the report was generated successfully, any SAS ODS options that were specified,the file extension, and the mime type.

Accessing Tasks F 199

Viewing the Compiled SAS Code

The Compiled SAS Code tab displays the compiled SAS code that you can run in any executionenvironment.

Accessing Tasks

The menu bar and the toolbar enable you to access tasks that create and manage your SAS code.The list of active menu options varies according to the current window and according to the kind ofobject that is selected. Unavailable menu options are disabled or hidden. Many menu and toolbaroptions are also available in pop-up menus. You use the menus to perform common tasks.

File Menu

Savesaves your SAS code.

Save Asenables you to specify a filename and location for the SAS code when you save it.

Page Setupopens the page setup utility so that you can specify the paper size, page orientation, page


margins, and printer properties.

Printprints the SAS code as it appears in the SAS Job Editor.

Closecloses the SAS Job Editor.

Edit Menu

Cutdeletes the selected text and stores it on the clipboard.

Copycopies the selected text onto the clipboard. Nothing is copied if you do not select any text.

Pasteinserts the contents of the clipboard into the SAS code at the pointer position.

Undodeletes the most recent text string that you typed or reverses your most recent edit action.

Select Allselects all the SAS code.

Find/Replacesearches for each case of a specific word or phrase in the SAS code. You can replace this wordor phrase with alternative text. When you search, you can specify to match by capitalizationor the entire word. You can also specify the direction of the search and whether to search boththe code and the comments, only the code, or only the comments.

Go To Lineenables you to jump to a line in the SAS code. This functionality is useful when you are tryingto fix compilation errors in the code.

View Menu

Refreshrefreshes the contents of the SAS Job Editor.

In Browserdisplays the report that is generated by the SAS code in a separate browser window. SelectPreferences from the Tools menu to specify the command that opens your external Webbrowser.

Find Previous Errormoves to the previous error or warning in the log. When SAS Digital Marketing runs the SAScode, any errors or warnings appear in the log. You can find these errors or warnings by usingthis menu option. For more information about the log, see “Viewing the Log” on page 196.

Find Next Errormoves to the next error or warning in the log. When SAS Digital Marketing runs the SAScode, any errors or warnings appear in the log. You can find these errors or warnings by usingthis menu option. For more information about the log, see “Viewing the Log” on page 196.

Accessing Tasks F 201

Actions Menu

Submitsubmits the SAS code for execution. The Log tab shows the results of the SAS job and anyerrors that might have occurred. If a report is created, it appears in the right pane of the SASJob Editor.

Tools Menu

Manage JDBC Connectionsmanages the connections to the JDBC data table. For more information, see “ConfiguringJDBC Data Providers” on page 222.

JDBC Table Viewerstarts the JDBC table viewer so that you can examine every record in the JDBC data table.For more information, “Using the JDBC Table Viewer” (Chapter 2, SAS Digital Marketing:User’s Guide).

Manage SAS Jobsopens the SAS Job Manager. For more information, see “About the SAS Job Manager” onpage 192.

Preferencesenables you to specify the appearance of the SAS code in the editor. For more information,see “Setting Preferences for the SAS Job Editor” on page 203.


Help Menu

Using this Windowstarts Help for the active window.

Help Contentsstarts Help for SAS Digital Marketing.

About SAS Code Editorprovides information about the release of the SAS Code Editor, and system information suchas the operating system name, the JRE version, and the ROOT and working directory names.

Using the Toolbar

The following buttons are available from the SAS Job Editor toolbar:

saves the SAS job.

submits the SAS code for execution. The Log tab shows the resultsof the SAS job and any errors that might have occurred. If a report iscreated, it appears in the right pane of the SAS Job Editor.

moves to the previous error in the log. When SAS Digital Marketingruns the SAS code, any errors or warnings appear in the log. You canfind these errors or warnings by using this menu option. For moreinformation about the log, see “Viewing the Log” on page 196.

moves to the next error in the log. When SAS Digital Marketing runsthe SAS code, any errors or warnings appear in the log. You canfind these errors or warnings by using this menu option. For moreinformation about the log, see “Viewing the Log” on page 196.

displays the report that was generated from the SAS code in an exter-nal Web browser.

prints the source content as it appears in the SAS Job Editor.

deletes the selected text from the source content and stores it on theclipboard.

copies the selected text onto the clipboard. Nothing is copied if youdo not select any text.

inserts the contents of the clipboard into the source content at thepointer position.

deletes the most recent text string that you typed or reverses your mostrecent edit action.

Setting Preferences for the SAS Job Editor F 203

searches for each case of a specific word or phrase in the SAS code.You can replace this word or phrase with alternative text. When yousearch, you can specify to match by capitalization or the entire word.You can also specify the direction of the search and whether to searchboth the code and the comments, only the code, or only the comments.

starts the JDBC table viewer so that you can examine every recordin the JDBC data table. For more information, see “Using the JDBCTable Viewer” (Chapter 2, SAS Digital Marketing: User’s Guide).

Setting Preferences for the SAS Job Editor

You can use the Preferences dialog box in the SAS Job Editor to specify the appearance of the SAScode and to define keywords.

Specifying the General Options

On the General tab, you can specify the following options:

Show line numbers


displays the line numbers in the SAS code. Displaying the line numbers can make it easier tofind errors in the code.

Auto indentindents the lines in the SAS code.

Document coloringapplies colors to the different elements in the SAS code. These colors help you quickly seethe comments, any macros, or other programming statements.

Read onlychanges the permissions on the file so that you can view the SAS code but cannot edit it.

Tab sizespecifies the number of spaces for a tab.

File typespecifies the type of file. In SAS Digital Marketing, the default file type is SAS ProgramFile.

NOTE: The other file types do not apply in SAS Digital Marketing.

Collapsible code sectionsspecifies whether you can expand and collapse sections in the SAS code. If you select thisoption, then you can also choose from the following options:

� Show section lines in text divides the code into sections by using horizontal lines.

� Show section brackets in margin displays in the margin brackets to show the contentthat is in each section.

Customize the Appearance of the SAS Code

By default, the SAS language editor highlights your text in different colors and font styles. This canhelp you easily distinguish the different elements in the SAS code and detect basic syntax errorsmore quickly. You can adjust the text color, font, font size, and font style to create and save yourown appearance schemes.

To customize the appearance of a file, complete the following steps:

1. Select Preferences from the Tools menu. The Editor Options dialog box opens.

2. Click the Appearance tab.

3. From the File type drop-down list, select SAS Program File to change the appearance of theSAS code.

NOTE: The SAS Program File option is selected by default. The other file types do notapply in SAS Digital Marketing.

4. From the Scheme drop-down list, select the Scheme that you want to use.

NOTE: If you want to apply this scheme to the SAS code, click OK. If you want to customizethis scheme, then continue with the next steps.

Setting Preferences for the SAS Job Editor F 205

5. In the Font section, select the Name and Size.

6. In the Elements box, select the syntax element for which you want to adjust the appearance.If you are not sure what the name of the element is, you can click an element in the samplefile that is displayed in the Preview box.

7. For the syntax element, select the foreground color, background color, and font style (forexample, bold, italic, and so on).

8. Repeat these steps for each element that you want to customize.

9. To save the scheme that you created, click Save As. In the Save Scheme dialog box, type thename of the scheme and click OK. The scheme now appears in the Scheme drop-down list.

NOTE: To delete a scheme that you have created, click Delete. You cannot delete the schemasthat ship with SAS Digital Marketing.

10. Click OK to apply your appearance changes.

Create User-Defined Keywords

You might want to create user-defined keywords for programming elements, such as SAS procedurestatements, variables, and other user-defined formats.

To create a user-defined keyword, complete the following steps:

1. Select Preferences from the Tools menu. The Editor Options dialog box opens.

2. Click the General tab.

3. Click Defined Keywords. The User defined keywords dialog box opens.

4. To add a new keyword, click Add. The Add user defined keyword dialog box opens.

5. Type the name of the new keyword in the Enter new keyword box and click OK.

The new keyword now appears in the User defined keywords dialog box.

To rename an existing keyword, select the keyword from the list and click Rename. In the Renameuser defined keyword dialog box, type the new name for the keyword and click OK.

To delete an existing keyword, select the keyword from the list and click Delete.


Consolidating Data

About Consolidating Data

You can use the SAS language adapter to consolidate SAS Digital Marketing data with the datafrom other solutions or processes.

For example, every night you want to consolidate your SAS Digital Marketing data with the datafrom another process. At the end of the SAS job, you could set a property that saves the date andtime of the last data consolidation. The next night when the build runs again, the SAS job consoli-dates only the SAS Digital Marketing data that was created or updated since the last consolidation.

To faciliate these types of consolidation jobs, SAS Digital Marketing has a set of SAS jobs that canbe configured to execute periodically in batch mode.

Several macros ship with SAS Digital Marketing. For more information, see “Using the DefaultSAS Macros” on page 206.

Using the Default SAS Macros

SAS Digital Marketing ships with several default macros. These macros are saved in theROOT/sasmacro/sem.sas file and eliminate the need to create ebtool URLs. You can includethe macro code directly in a SAS job, or you can use these macros in any execution context whereyou can run SAS code.

NOTE: Additional macros are described in the ROOT/sasmacro/sem.sas file. You can alsocreate custom macros. If you deploy these custom macros to the sem.sas file, then your macrosare available to all SAS jobs in any execution environment.

Using the Default SAS Macros F 207

SEM_DO_PREVIEW Macro

The SEM_DO_PREVIEW macro enables you to send a preview e-mail from within SAS.

The syntax for this macro is the following:

%macro sem_do_preview(intable,results,moniker,address)

The user-supplied values are the following:

� intable is the name of the data source table that contains the e-mail addresses and the cus-tomization data for the recipients.

� results is the table that contains the responses from sending the broadcast.

� moniker is the moniker of the broadcast that you want to send.

� address is the e-mail address of the preview recipient. The preview recipient should receive apreview e-mail for each row in the data source table.

The following is an example of how you might use this macro:

FILENAME _MACROS "sem.sas";%INCLUDE _MACROS;

FILENAME _WEBOUT TEMP;FILENAME _WEBMETA TEMP;

%let sem_server=localhost:9221;%let sem_user=admin;%let sem_password={sas001}YWRtaW4x;%let sem_broadcast_moniker=Broadcast_1108665300405;%let sem_broadcast_name=%nrstr(AML Report - January 2004);%let sem_url=http://localhost/sdm/;

data work.recipients;salutation_nm="Dr. Bob";email_address_txt="[email protected]";

run;

%sem_do_preview(work.recipients,work.results,&sem_broadcast_moniker,[email protected]);

ods html file=_webout;proc print data=work.results;run;ods html close;%sem_set_meta(text/html,.html,0,Report generation successful.);


SEM_DO_TRANSACTION Macro

The SEM_DO_TRANSACTION macro enables you to send an e-mail from SAS.


%macro sem_do_transaction(intable,results,moniker)


� intable is the name of the data source table that contains the e-mail addresses and customiza-tion data for the recipients.

� results is the table that contains the responses from sending the broadcast.

� moniker is the moniker of the broadcast that you want to send. Each row in the data sourcetable results in one broadcast message being sent.




%let sem_server=localhost:9221;%let sem_user=admin;%let sem_password={sas001}YWRtaW4x;%let sem_broadcast_moniker=Broadcast_1108665300405;%let sem_broadcast_name=%nrstr(AML Report - January 2004);%let sem_url=http://localhost/sdm/;

data work.recipients;salutation_nm="Dr. Bob";email_address_txt="[email protected]";

run;

%sem_do_transaction(work.recipients,work.results,&sem_broadcast_moniker);

ods html file=_webout;proc print data=work.results;run;ods html close;%sem_set_meta(text/html,.html,0,Report generation successful.);


SEM_EXPORT_PROPERTIES Macro

The SEM_EXPORT_PROPERTIES macro enables you to export the server properties to SASmacros.

NOTE: When a SAS job is initialized, the SEM_EXPORT_PROPERTIES macro is called automat-ically.


%macro sem_export_properties()




%let sem_server=localhost:9221;%let sem_user=admin;%let sem_password=(sas001)YWRtaW4x;%let sem_url=http://localhost/sdm/;

%sem_export_properties();%put &WebAppURL=;


SEM_GET_ALL_BROADCASTS Macro

The SEM_GET_ALL_BROADCASTS macro extracts the list of defined broadcasts into an outputtable.


%macro sem_get_all_broadcasts(table,period,details)


� table is the name of the reply table

� period is the number of days to look back to get broadcasts executed during that period

� details is whether to get the broadcast details

The following is an example of how to get a list of all the broadcasts that were executed in the past30 days:



%let sem_server=localhost:9221;%let sem_user=admin;%let sem_password=(sas001)YWRtaW4x;%let sem_broadcast_moniker=Broadcast=1108665300405;%let sem_broadcast_name=%nrstr(Data Quality Forum);%let sem_url=http://localhost/sdm/;

%sem_get_all_broadcasts(work.broadcasts,30,false);ods html file=_webout;proc print data=work.broadcasts;run;%sem_set_meta(text/html,.html,0,Report generation successful.);ods html close;


SEM_GET_ALL_REPLIES Macro

The SEM_GET_ALL_REPLIES macro extracts the replies from the reply table. If you do notspecify any response variables to retrieve, then all the rows in the table are retrieved. For moreinformation about the reply table, see “Reply Table Layout” (Appendix A, SAS Digital Marketing:User’s Guide).


%macro sem_get_all_replies(table,variables,where)



� variables are the rows of the variables to retrieve in the reply table

� where is the SQL WHERE clause for creating a subset of the response records

NOTE: The SEM_GET_ALL_REPLIES macro does not correlate the broadcasts to the replyrecords. To correlate broadcasts to the reply records, use the SEM_GET_REPLIES macro.





%sem_get_all_replies(work.replies,,);ods html file=_webout;goptions device=activex gsfname=_webout gsfmode=replace;run;

title "All Reply Data";proc gchart data=work.replies; pie3d type; run; quit;%sem_set_meta(text/html,.html,0,Report generation successful.);ods html close;


SEM_GET_AUDIT Macro

The SEM_GET_AUDIT macro extracts from the audit table the data for the specified audit variablesinto a table. If you do not specify any audit variables to retrieve, then all the rows in the table areretrieved. For more information about the audit table, see “Audit Table Layout” (Appendix A, SASDigital Marketing: User’s Guide).


%macro sem_get_audit(table, moniker,variables,where)


� table is the name of the audit table

� moniker is the broadcast moniker

� variables are the rows of audit variables to retrieve






%sem_get_audit(work.audit,&sem_broadcast_moniker,,);ods html file=_webout;title "Audit Data for ’&sem_broadcast_name’";proc print data=work.audit;run;%sem_set_meta(text/html,.html,0,Report generation successful.);ods html close;


SEM_GET_GROUP Macro

The SEM_GET_GROUP macro extracts the contents of a broadcast group.


%macro sem_get_group(b_table,g_table,path)


� b_table is the name of the table for the broadcasts in the group

� g_table is the name of the table for any subgroups in the broadcast group

� path is the path of the group to examine




%let sem_server=localhost:9221;%let sem_user=admin;%let sem_password=(sas001)YWRtaW4x;%let sem_group=%nrstr(\Samples\Dynamic);%let sem_group_name=%nrstr(Dynamic);%let sem_url=http://localhost/sdm/;

%sem_get_group(work.broadcasts,work.groups,&sem_group);ods html file=_webout;proc print data=work.groups;run;%sem_set_meta(text/html,.html,0,Report generation successful.);ods html close;


SEM_GET_HISTORY Macro

The SEM_GET_HISTORY macro extracts from the history data the broadcast history and replyhistory.


%macro sem_get_history(table,moniker,replies)


� table is the name of the table that contains the history data


� replies is whether to retrieve the reply history





%sem_get_history(work.history,&sem_broadcast_moniker,true);ods html file=_webout;proc print data=work.history;run;%sem_set_meta(text/html,.html,0,Report generation successful.);ods html close;


SEM_GET_PROPERTIES Macro

The SEM_GET_PROPERTIES macro extracts the values of the server properties into a table.


%macro sem_get_properties(table)

The user-supplied value for table is the name of the table that contains the server properties.





%sem_get_properties(work.properties);ods html file=_webout;proc print data=work.properties;run;%sem_set_meta(text/html,.html,0,Report generation successful.);ods html close;


SEM_GET_REPLIES Macro

The SEM_GET_REPLIES macro extracts the replies for a specific broadcast from the reply table.For more information about the reply table, see “Reply Table Layout” (Appendix A, SAS DigitalMarketing: User’s Guide).


%macro sem_get_replies(table,moniker,implicit)




� implicit is whether to get the implicit replies

NOTE: Your site administrator can set the ReplySummaryPeriod server property to specify thenumber of days to look back in the reply table for determining implicitly correlated replies. Formore information, see “Response Server Properties” on page 151.





%sem_get_replies(work.replies,&sem_broadcast_moniker,true);ods html file=_webout;title "Reply Data for ’&sem_broadcast_name’";proc print data=work.replies;run;%sem_set_meta(text/html,.html,0,Report generation successful.);ods html close;


SEM_GET_RESPONSE Macro

The SEM_GET_RESPONSE macro extracts from the response table the data for the specified re-sponse variables into a table. If no variables are specified, then all the variables in the response tableare retrieved. For more information about the response table, see “Reply Table Layout” (AppendixA, SAS Digital Marketing: User’s Guide).


%macro sem_get_response(table, moniker,variables,where)


� table is the name of the response table


� variables are the response variables to retrieve






%sem_get_response(work.response,&sem_broadcast_moniker,,);ods html file=_webout;title "Response Data for ’&sem_broadcast_name’";proc print data=work.response;run;%sem_set_meta(text/html,.html,0,Report generation successful.);ods html close;


SEM_GROUP_HISTORY Macro

The SEM_GROUP_HISTORY macro extracts from the history data the broadcast groups.


%macro sem_group_history(table,group,period)


� table is the name of the table that contains the history data

� group is the broadcast group

� period is the number of days to look back for broadcast executions

The following is an example of how you might use this macro to extract the 30-day history for agroup:




%sem_group_history(work.history,&sem_group,30);ods html file=_webout;proc print data=work.history;run;%sem_set_meta(text/html,.html,0,Report generation successful.);ods html close;


SEM_SET_META Macro

The SEM_SET_META macro sets the return type and status for a broadcast report. This macrotells the Web browser whether the report is an HTML file or an image file. It also states whether thereport was successful or failed to execute.


%macro sem_set_meta(mimeType,ext,rc,message)


� mimeType is the mime type that the job will return

� ext is the extension for the output

� rc is the return code from the job

� message is the status message to display to the user





%sem_group_history(work.history,&sem_group,30);ods html file=_webout;proc print data=work.history;run;%sem_set_meta(text/html,.html,0,Report generation successful.);ods html close;


SEM_SET_PROPERTY Macro

The SEM_SET_PROPERTY macro enables you to save the consolidation state so it is available thenext time that you run a SAS job. When a job is initialized, SAS Digital Marketing automaticallyexports any server properties that you set to SAS macro variables. This action enables you toreference the server property as a SAS macro. For example, a SAS macro called &WebAppURLgives you the location of your SAS Digital Marketing Web Studio deployment.


%macro sem_set_property(property,value)


� property is the name of the server property that you want to set

� value is the value of the property





%sem_set_property(MyProperty,%nrstr(My Value));%sem_get_properties(work.properties);ods html file=_webout;proc print data=work.properties;run;%sem_set_meta(text/html,.html,0,Report generation successful.);ods html close;

Chapter 8

Managing JDBC Connections

ContentsOverview of JDBC Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 221Configuring JDBC Data Providers . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Types of JDBC Data Providers . . . . . . . . . . . . . . . . . . . . . . . . 222Managing the Connections Settings . . . . . . . . . . . . . . . . . . . . . . 222Add a JDBC Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Using SAS JDBC Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225About SAS JDBC Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . 225Components of SAS JDBC Explorer . . . . . . . . . . . . . . . . . . . . . 226SAS JDBC Explorer Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Overview of JDBC Connections

Java Database Connectivity (JDBC) technology enables you to connect to your databases throughJava applications. SAS Digital Marketing use the data tables in these databases to customize yourbroadcast content and to record information about broadcast transmissions. For information aboutthe data tables, see “SAS Digital Marketing Tables” (Appendix A, SAS Digital Marketing: User’sGuide).

As a site administrator, you can manage JDBC connections by configuring JDBC data providers andspecifying the connection definitions. SAS Digital Marketing provides the JDBC Explorer for thesite administrator to manage and query the data tables. Other users can use the JDBC table viewerto view, copy, or export the data tables. For more information, see “Using SAS JDBC Explorer” onpage 225 and “Using the JDBC Table Viewer” (Chapter 2, SAS Digital Marketing: User’s Guide).

NOTE: SAS Digital Marketing provides several server properties to simplify how you manage theJDBC connections. For more information, see “JDBC Server Properties” on page 142.

222 F Chapter 8: Managing JDBC Connections

Configuring JDBC Data Providers

Types of JDBC Data Providers

SAS Digital Marketing can use any JDBC provider. However, the server has been optimized forSAS JDBC providers. The JAR file for the SAS/SHARE and SAS Integrated Object Model (IOM)provider is automatically installed with the server and servlets.

For third-party databases with SAS Digital Marketing, one or more JDBC third-party JAR files arerequired for each database. You can use the Server Configuration wizard to automatically add third-party JAR files to the Web reporting and the tracking servlet WAR files. For more information, see“Run the Server Configuration Wizard” on page 39.

The default connection assumes that a SAS/SHARE server is running as your local host. If you areusing SAS Digital Marketing in conjunction with a SAS Intelligence Platform, you can use the SASWorkspace server instead of a SAS/SHARE server. If you have administrative privileges (Level4 permission), then you can define multiple JDBC providers for use with the server, modify thedefault connection, or create a new connection.

Managing the Connections Settings

You use Connection Options under the Server node to create or modify the JDBC connectionsfor the data source tables. To open the Connection Definitions dialog box, select Tools!ServerConfiguration! Connection Options.

Managing the Connections Settings F 223

To modify a JDBC connection, select the name. Use the text boxes to change the driver, UniversalResource Identifier (URI), user ID, and password that SAS Digital Marketing uses to connect to aJDBC provider.

You can perform the following actions:

Addadds a new connection. To add a connection, click Add. Use the text boxes to specify thedriver, URI, user ID, and password that SAS Digital Marketing uses to connect to a JDBCdata provider. For more information, see “Add a JDBC Connection” on page 224.

NOTE: For the SAS Digital Marketing clients to create reports that access the audit table, youmust specify an explicit host in the JDBC connection definition. Therefore, do not specify aJDBC connection that has localhost as the URI.

Removeremoves a connection. To remove a connection, select the name from the Connections boxand click Remove.

Testtests a JDBC connection. To perform a test, select the name from the Connections box andclick Test. A message box appears that indicates whether the connection succeeded or failed.

You might need to change the driver, based on the type of database that you are connecting to.SAS Digital Marketing automatically includes the share and iom drivers. To connect to anotherthird-party database, specify the driver in the Driver box.


NOTE: When you change the driver, the URI box is automatically populated with a suggested serverand data port. This information might not be correct for your server. Enter the correct server anddata port for your connection.

Add a JDBC Connection

To add a connection, complete the following steps:

1. Open the Server Configuration window and select Connections Options under the Servernode, or open the JDBC Explorer and select Manage JDBC Connections from the Toolsmenu.

2. Specify the scope for the new JDBC connection. Select JDBC Connections in the Connec-tion Options list to add a JDBC connection that is available to all SAS Digital Marketingusers. Select My Connections in the Connection Options list to add a JDBC connectionthat is available only for your use.

3. Click Add.

4. Specify the name for the new connection.

5. Specify the driver, URI, user ID, and password. SAS Digital Marketing uses these values toconnect to a JDBC data provider. Click Test to verify the connection.

6. Click OK.

About SAS JDBC Explorer F 225

Using SAS JDBC Explorer

About SAS JDBC Explorer

When you have administrative privileges (Level 4 permission), use SAS JDBC Explorer to managethe JDBC connections and to access the JDBC tables on your site’s SAS Digital Marketing servers.With SAS JDBC Explorer you can:

� view the contents of an existing JDBC table

� create a duplicate table

� create a new table by copying an existing table’s structure

� submit SQL statements to query the tables or perform a calculation, such as a total

To open SAS JDBC Explorer in SAS Digital Marketing Studio, select JDBC Explorer from the

Tools menu or click Explore JDBC Connections, , from the toolbar.


Components of SAS JDBC Explorer

The SAS JDBC Explorer displays a hierarchical view of the contents of each connection in the leftportion of the window. This view is called the navigation tree. To view the contents of a specificconnection, click the connection name. If any libraries are defined, then a list of libraries appears.Click the library name to view in the right portion of the window the JDBC tables in that library.

NOTE: When the HideSASPredefinedLibraries server property is set to true, the GISMAPS,MAPS, SASHELP, and SASUSER libraries are still accessible from the SAS JDBC Explorer win-dow. For more information, see “JDBC Server Properties” on page 142.

The lower portion of the window contains the following tabs:

Log tabrecords events as they happen. The log includes the time when a table was created or deleted.It also lists any errors that occurred when an SQL statement was executed.

SQL tabenables you to submit an SQL statement to query the list of JDBC tables or to perform acalculation. Type the SQL statement in this tab, and then select Submit SQL Statementfrom the Actions menu. The Log tab displays any errors or notes that were generated whenthe SQL statement was executed. The log also lists if the SQL statements were executedsuccessfully.

NOTE: Many menu and toolbar tasks are also available from the pop-up menu on the SQLtab. This pop-up menu also enables you to insert an SQL statement or to undo or redo changesto your SQL code. To access the pop-up menu, right-click the SQL tab.

SAS JDBC Explorer Tasks

The menu bar and the toolbar enable you to access tasks that manage your JDBC tables. The list ofactive menu options varies according to the current window and according to the kind of object thatis selected. Unavailable menu options are disabled or hidden.

Many menu and toolbar options are also available in pop-up menus. For example, you can use themenu to open a JDBC table, or you can right-click in the table and select Open in the pop-up menu.

NOTE: The ability to manage the tables is dependent on the user’s database privileges when theselected table exists on a third-party database such as Oracle, Teradata, or DB2.

File Menu

Newopens the JDBC Explorer in a new window or enables you to add a new table.

SAS JDBC Explorer Tasks F 227

Duplicatecopies the selected table and adds the copied table to the same directory. By default, the nameof the copied table is Original-table-name_copy.

Clonecopies the table structure of the selected table. The content is not copied; only the structure iscopied. By default, the name of the cloned table is Original-table-name _clone.

Deletedeletes the selected table.

Renameenables you to rename the selected table.

Propertiesdisplays the properties of the selected JDBC table. The Properties window displays generalinformation, such as the name of the table and the connection, and the columns in the table,such as the column name, type, and size.

Closecloses the JDBC Explorer.

Edit Menu

Cutdeletes the selected table or tables.

Copycopies the selected text in the SQL tab onto the clipboard. Nothing is copied if you do notselect any text.

Pastepastes the text from the clipboard to the current location in the SQL tab.

Select Allselects all the content in the current library.

View Menu

Explorer Consoledisplays the Log and SQL tabs at the bottom of the Explorer window. You can choose todisplay or hide these tabs.

Refreshrefreshes the view of the JDBC Explorer.

Actions Menu

Clear Logclears the contents of the Log tab.

Submit SQL Statementenables you to submit the SQL statements that you entered in the SQL tab.


Tools Menu

Manage JDBC Connectionsmanages the connections to the JDBC data table. For more information, see “ConfiguringJDBC Data Providers” on page 222.

JDBC Table Viewerstarts the JDBC table viewer so that you can examine every record in the JDBC data table. Formore information, see “Using the JDBC Table Viewer” (Chapter 2, SAS Digital Marketing:User’s Guide).

Help Menu

Using this Windowopens Help for SAS JDBC Explorer.

Help Contentsstarts Help for the application. For more information, see “Using Help” (Chapter 2, SASDigital Marketing: User’s Guide).

About SAS JDBC Explorerprovides information about the release of the JDBC Explorer and also provides system in-formation such as the operating system name, the JRE version, and the home and workingdirectory names.

Using the Toolbar

In SAS JDBC Explorer, the following toolbar buttons are available:

moves up one level.

deletes the selected table.

copies the selected text in the SQL tab onto the clipboard. Nothing iscopied if you do not select any text.

pastes the text from the clipboard to the current location in the SQLtab.

refreshes the view of the JDBC Explorer.

opens the JDBC table viewer.

Chapter 9

Managing Broadcast Tracking and Replies

ContentsOverview of Broadcast Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . 230Tracking Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

About Tracking Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 230Set the Response Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Change the Response Table . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Monitoring Replies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232About Monitoring Replies . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Using Correlated Replies . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Using Uncorrelated Replies . . . . . . . . . . . . . . . . . . . . . . . . . . 232Create Correlated Replies . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Working with the E-mail Reply Manager . . . . . . . . . . . . . . . . . . . . . . 235About the E-mail Reply Manager . . . . . . . . . . . . . . . . . . . . . . . 235Configuring the E-mail Reply Manager . . . . . . . . . . . . . . . . . . . . 236Using the E-mail Reply Manager . . . . . . . . . . . . . . . . . . . . . . . 240E-mail Reply Manager Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 241Understanding Reply Filters and Reply Rules . . . . . . . . . . . . . . . . . 243

Working with the Reply Filter Categories . . . . . . . . . . . . . . . . . . . . . . 244Default Reply Filter Categories . . . . . . . . . . . . . . . . . . . . . . . . 244Add a Reply Filter Category . . . . . . . . . . . . . . . . . . . . . . . . . . 245Delete a Reply Filter Category . . . . . . . . . . . . . . . . . . . . . . . . . 246Reply Rules Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Managing Reply Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250Create a New Reply Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . 250Edit an Existing Reply Rule . . . . . . . . . . . . . . . . . . . . . . . . . . 251Delete a Reply Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Forwarding Replies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252About Forwarding Replies . . . . . . . . . . . . . . . . . . . . . . . . . . . 252Add a Forwarding E-mail Address . . . . . . . . . . . . . . . . . . . . . . . 252Edit a Forwarding E-mail Address . . . . . . . . . . . . . . . . . . . . . . . 253Delete a Forwarding E-mail Address . . . . . . . . . . . . . . . . . . . . . 253

230 F Chapter 9: Managing Broadcast Tracking and Replies

Overview of Broadcast Tracking

After a broadcast is executed, SAS Digital Marketing users can measure the effectiveness of abroadcast transmission by analyzing delivery rate, click through rate, and open rate. To track thebroadcasts, you must first deploy the broadcast response tracking servlets on a Web applicationserver that is visible to your recipients. Usually the tracking and Web publication tier is deployedoutside any corporate firewalls. For more information, see “Configuring the Tracking and WebPublication Tier” on page 54.

You can set tracking parameters that use SAS Digital Marketing to record an e-mail recipient’sresponse to a broadcast. These tracking parameters include the broadcast variables, the trackingvariables, and the e-mail address variables for an e-mail broadcast. For more information, see“About Tracking Parameters” on page 230. After a broadcast executes, the tracking servlets collectresponses to the broadcast. Each tracking servlet invocation generates a record in the response table.The columns in this record correspond to recipient’s response. SAS Digital Marketing Studio userscan specify the response table when the broadcast definition is created, or you can set the responsetable that your entire site uses. For more information, see “Set the Response Table” on page 231.

SAS Digital Marketing provides the E-mail Reply Manager with a set of predefined reply filtercategories to capture information about reply messages. The reply messages are processed and cat-egorized for all broadcast transmissions through an incoming domain mailbox. You should assignadministrator privileges (Level 4 permission) to a user that can assume the responsibility of manag-ing the E-mail Reply Manager. This includes monitoring the Other category for patterns that mightindicate the need for additional filter categories or rules. This individual must also decide whetherto take action for the different categories of replies. For more information, see “Working with theE-mail Reply Manager” on page 235.

Tracking Responses

About Tracking Parameters

As the site administrator, you can set the tracking parameters for the SAS Digital Marketing users atyour site. You can use either a distribution list or server properties. If these tracking parameters arespecified, then the Open and Link Tracking panels are not available in the New Broadcast wizard.How you specify these parameters depends on the data model that your site uses.

� If your site uses one global data model, then you can specify the EmailVariables, Email-TrackedVariables, and EmailAddressVariables server properties. SAS Digital Marketing Stu-dio uses the values that you specify and enforces them when appropriate.

� If your site uses multiple global data models, then you can specify logical distribution lists todefine each model.

Set the Response Table F 231

If you are uncertain about data model that your site will use, then do not specify the trackingparameters. For more information about data models, see “Managing Global Data Models” onpage 166.

Set the Response Table

You can set the response tables for your site by using the ResponseTableBase server property toconfigure how the response tables are saved. After this property is set, the Response table boxis not available from the New Broadcast wizard or Add RSS Content wizard, and the user cannotmodify the settings for the response tables. For more information, see “Response Server Properties”on page 151.

Change the Response Table

To change the response table, you must have administrative privileges (Level 4 permission).

NOTE: It is recommended that you do not change the response table after a broadcast executes.If you change the response table for an executed broadcast, then the new response table omits theresponse records for the e-mails that were previously sent.

To change the response table for a broadcast, complete the following steps:

1. In SAS Digital Marketing Studio, select the broadcast from the list of broadcast definitionsand select Change Response Table from the Edit menu.

NOTE: You cannot change the response table for a broadcast that has no tracked variablesassociated with it. If you select a broadcast without tracked variables, then the ChangeResponse Table menu item is not available.

2. In the Change Response Table dialog box, specify the new response table and click OK.

You can also change the response table from the Query Broadcast Response window. For more in-formation, see “Using the Query Broadcast Response Window” (Chapter 7, SAS Digital Marketing:User’s Guide).


Monitoring Replies

About Monitoring Replies

When you send an e-mail broadcast, the message header can contain three possible return e-mailaddresses: From, Reply To, and SMTP Reply To. The From and Reply To e-mail addresses arealways visible to the recipient, while the SMTP Reply To e-mail address is hidden. To managereplies in SAS Digital Marketing, you must set at least one return e-mail address to a domainmailbox that the E-mail Reply Manager is configured to monitor.

The E-mail Reply Manager uses a series of predefined filters to categorize e-mail broadcast replyand bounce messages. You can customize the reply filter categories and add processing rules.You can also use reply and bounce messages to eliminate invalid addresses from your broadcastrecipient lists. When the return e-mail header includes an XSL expression, SAS Digital Marketingcan correlate the e-mail replies from broadcast recipients or the e-mail messages that bounce backfrom an e-mail server.

Using Correlated Replies

A correlated reply is an e-mail message that a broadcast recipient sends back or that an e-mailserver bounces back, which SAS Digital Marketing connects to the originating broadcast. Theconnection occurs if the return e-mail address in the message header for the broadcast definition isset to the broadcast moniker at the incoming domain mailbox. When the Reply Manager receivesand processes the reply message, SAS Digital Marketing uses the moniker to correlate the messageback to the originating broadcast.

You can view all the reply messages for a selected broadcast from the Replies tab in the QueryBroadcast Response window. Correlated replies (reply messages that you can connect to a selectedbroadcast) are identified with a green flag. Uncorrelated replies (reply messages that are implicitlycorrelated to the selected broadcast) are identified with a yellow flag. For more information, see“Using the Query Reply Data Window” (Chapter 7, SAS Digital Marketing: User’s Guide).

Using Uncorrelated Replies

An uncorrelated reply is an e-mail message that a broadcast recipient sends back or that an e-mailserver bounces back, which is not connected to the originating broadcast. Uncorrelated replies areuseful when your primary interest is identifying the recipient e-mail addresses that bounce back andyou are uninterested in connecting replies to a specific broadcast transmission. For uncorrelatedreplies, the return e-mail address in the message header for the broadcast definition uses a singlee-mail address so the incoming domain mailbox is not unique.

Create Correlated Replies F 233

You can view all the reply messages for a selected broadcast from the Replies tab in the QueryBroadcast Response window. Uncorrelated replies (reply messages that are implicitly correlated tothe selected broadcast) are marked with a yellow flag while correlated replies (reply messages thatyou can connect to a selected broadcast) are marked with a green flag.

Example of an Uncorrelated Reply

You might send an e-mail to [email protected] and receive a reply that was a hard bounce. Becauseyou did not customize the return e-mail address for the broadcast definition, the hard bounce thatyou received is not tied to a specific broadcast. You know only that a hard bounce was receivedfrom a particular e-mail address. You cannot determine the broadcast message that was sent.

SAS Digital Marketing provides implicit broadcast correlation for these types of replies. The un-correlated replies that you received are matched to an audit table that was executed in the past ndays.

Create Correlated Replies

To correlate reply messages, complete the following steps:

1. Configure an incoming domain mailbox. A domain mailbox is a mailbox that receives allthe mail for a given domain. For example when your domain mailbox is configured forsas.com, any reply messages that use this domain ([email protected]) are sentto that domain mailbox. You can also use wildcard characters to set the domain mailbox. Forexample, reply messages for a specific broadcast, such as broadcast_*, go to a designatedmailbox.

NOTE: The domain configuration is external to SAS Digital Marketing and is specific to thee-mail server that you use.

2. In SAS Digital Marketing, configure the E-mail Reply Manager to use the domain mailboxthat you configured. Specify the incoming e-mail server and log on information for the do-main mailbox on the Inbox tab of the Reply Manager Configuration dialog box. For moreinformation, see “Configuring the E-mail Reply Manager” on page 236.

3. Each e-mail broadcast definition must include at least one return e-mail address that is set tothe broadcast moniker at the domain mailbox.

To ensure that every broadcast uses a return e-mail address that SAS Digital Marketing cancorrelate, set the EmailFromOverride server property. SAS Digital Marketing uses the valueof this server property for the SMTP Mail From address in every broadcast definition andusers cannot change it. You set the server property to the following value:

<xsl:value-of select="$moniker"/>@replydomain

where replydomain is the name of your domain mailbox. For more information onthe EmailFromOverride server property, see “Reply Management Server Properties” onpage 147.


As an alternative, you can set the EmailFromOverride server property to use a global domainmailbox for all broadcasts that are created at your site. Configure one mailbox to processthe replies, such as anything@replydomain. Then use the EmailFromOverride serverproperty to insert <moniker>@replydomain. SAS Digital Marketing hides the value ofthe SMTP Reply From address from your users when this server property is set.

If the EmailFromOverride server property is not set and you want the replies correlated, thenyour SAS Digital Marketing users must set at least one return e-mail address to the broadcastmoniker at the incoming domain mailbox. You can use the following approaches in theNew Broadcast wizard or the Properties dialog box for an e-mail broadcast or a multichannelbroadcast:

� Set the value of Reply to and From return e-mail addresses to


where replydomain is the name of your domain mailbox. As a best practice, thevalues of the Reply to and From should be the e-mail address of an actual person.Replies are sent to an actual person who can answer questions or address recipients’concerns.The advantage to this approach is that all replies are correlated to a broadcast. Thedisadvantage to this approach is that the e-mail recipient can see this address, and thee-mail might be identified as spam.

� Set the value of SMTP Mail From to


where replydomain is the name of the domain mailbox for your correlated replies.The advantage to this approach is that the e-mail recipients do not see this address. Thedisadvantage is that not all replies, such as Out of Office replies, are correlated.

Working with the E-mail Reply Manager F 235

NOTE: If the EmailFromOverride server property is set, then the SMTP Mail Frombox is not available.

For more information, see “Creating E-mail Broadcasts” (Chapter 3, SAS Digital Market-ing: User’s Guide) and see “Customizing the Header Information” (Chapter 5, SAS DigitalMarketing: User’s Guide).

Working with the E-mail Reply Manager

About the E-mail Reply Manager

SAS Digital Marketing uses reply categories to filter the reply messages for an e-mail or multichan-nel broadcast and creates a record about the reply in a reply table. As the site administrator, you cancustomize the reply categories and rules. The E-mail Reply Manager enables you to manage the re-ply categories and view the reply messages. You should consider assigning administrator privileges(Level 4 permission) to a user that can assume the responsibility of managing the E-mail ReplyManager. Someone should monitor the Other category for patterns that might indicate the need foradditional filter categories or rules. This individual must also decide whether to take action for thedifferent categories of replies.


SAS Digital Marketing stores the configuration information for the E-mail Reply Manager in thereplymgr.xml file that is located in the ROOT/config directory. You should not edit this filedirectly. Instead, you should use the Reply Manager Configuration dialog box that is available fromthe E-mail Reply Option node in the Server Configuration window. For more information, see“E-mail Reply Options” on page 101.

Configuring the E-mail Reply Manager

When you configure the reply message account, you can specify the e-mail account information,the location of the JDBC table to record the reply classifications, the reply categories, and the JMSqueue and topic.

You can modify these options by using the Reply Manager Configuration dialog box. You can openthe Reply Manager Configuration dialog box in the following ways:

� From the E-mail Reply Manager, select Reply Manager Configuration from the Toolsmenu.

� From the Server Configuration window click Configure Reply Manager from the E-mailReply Options node.

In the Reply Manager Configuration dialog box, use the following tabs to configure the reply mes-sage account:

� Inbox

� Reply Table

� Priority

� JMS

Configuring the E-mail Reply Manager F 237

Inbox Tab

You use the Inbox tab to specify the POP3 or IMAP e-mail account information. This accountreceives the e-mail replies and bounces for broadcasts transmissions that use return e-mail addresseswith the incoming domain mailbox in the message header.

You must specify the e-mail server information for the incoming domain mailbox. Enter the nameof the server host, and specify the port that the server uses on that host. The domain configurationis external to SAS Digital Marketing and is specific to the e-mail server that you use. If the serveris configured to require authentication, then specify the user credentials.

NOTE: Support for IMAP is experimental for this release.


Reply Table Tab

You use the Reply Table tab to specify the location of the JDBC table that SAS Digital Marketinguses to record the e-mail reply records.

You can specify the JDBC table in either of the following ways:

� Select an existing table from the list. The tables in this list depend on the JDBC connectionthat you have selected. To select a different table connection, use the Connections drop-downlist.

� Enter a valid table name for the JDBC provider in the Table box. This name can be for anexisting table or a new table. SAS Digital Marketing automatically creates the table if it isnot found in the folder.

NOTE: For the SAS Digital Marketing clients to create reports that access the reply table, youmust specify an explicit host in the JDBC connection definition. Therefore, do not specify a JDBCconnection that has localhost as the URI. For more information, see “Managing the ConnectionsSettings” on page 222.

Configuring the E-mail Reply Manager F 239

Priority Tab

You use the Priority tab to specify the reply categories. You can add, delete, and update replycategories as well as specify the order in which to process the categories.

For more information about the reply rules and categories, see “Understanding Reply Filters andReply Rules” on page 243.


JMS Tab

You use the JMS tab to set up a JMS queue and topic to handle replies in real time.

For more information, see “Overview of JMS” on page 269.

Using the E-mail Reply Manager

To open the E-mail Reply Manager, use SAS Digital Marketing Studio to perform any of the fol-lowing actions:

� Click the Reply Manager icon on the toolbar.

� Select Reply Manager from the Tools menu.

� Select Tools!Server Configuration!E-mail Reply Options and then click Configure Re-ply Manager.

E-mail Reply Manager Tasks F 241

E-mail Reply Manager Tasks

In the E-mail Reply Manager, the menu bar and the toolbar enable you to access tasks that managethe reply filter categories. The list of active menu tasks varies according to the current window andaccording to the kind of object that is selected. Inactive menu tasks are disabled or hidden.

File Menu

New Reply Filter Categorycreates a new reply filter category. For more information, see “Add a Reply Filter Category”on page 245.

Exitcloses the E-mail Reply Manager.

Edit Menu

Deletedeletes the selected reply messages. You cannot delete a reply filter category by using the Editmenu.

Select Allselects all the reply messages for the selected reply filter category in the navigation tree.


Actions Menu

Refreshrefreshes the contents of the E-mail Reply Manager.

Tools Menu

Query Reply Dataopens the Query Reply Data window. For more information, see “Using the Query ReplyData Window” (Chapter 7, SAS Digital Marketing: User’s Guide).

Reply Manager Configurationopens the Reply Manager Configuration dialog box. For more information about the availableoptions, see “E-mail Reply Options” on page 101.

JDBC Table Viewerstarts the JDBC table viewer. For more information, see “Using the JDBC Table Viewer”(Chapter 2, SAS Digital Marketing: User’s Guide).

Help Menu

Using this Windowprovides Help about the active window.

Help Contentsstarts Help for SAS Digital Marketing. For more information, see “Using Help” (Chapter 2,SAS Digital Marketing: User’s Guide).

About E-mail Reply Managerprovides information about the SAS Digital Marketing client and about the server release ofthe E-mail Reply Manager. Also provides system information such as the operating systemname, the JRE version, the ROOT and working directory names, and the settings of the serverproperties.

Using the Toolbar

The toolbar contains shortcuts to the tasks on the menu bar. The list of active tasks varies accordingto the current work area and according to the kind of object that is selected. Inactive tasks aredisabled or hidden. Tool tips appear when you place your mouse pointer over an icon on the toolbar.Click the icon to select a task. The following buttons are available on the toolbar:

creates a new reply filter category. For more information, see “Add aReply Filter Category” on page 245.

refreshes the contents of the E-mail Reply Manager.

opens the Query Reply Data window. For more information, see “Us-ing the Query Reply Data Window” (Chapter 7, SAS Digital Market-ing: User’s Guide).

Understanding Reply Filters and Reply Rules F 243

starts the JDBC table viewer. See “Using the JDBC Table Viewer”(Chapter 2, SAS Digital Marketing: User’s Guide).

Understanding Reply Filters and Reply Rules

When messages are not delivered successfully to the recipient or when the recipient sends a reply,the E-mail Reply Manager uses a filter to categorize the incoming message. SAS Digital Marketingstores these messages in a directory and adds a record to the reply table for each message. Thereply filter categories and their rules determine how to process these returned messages and whetherthe reply history is sent to SAS Customer Intelligence software. SAS Digital Marketing providesseveral predefined reply filter categories and rules that you can update and customize for your site.

NOTE: To use the reply filter, you must use broadcast definitions that create correlated replies. Formore information, see “Using Correlated Replies” on page 232.

Each reply rule consists of the following information:

� unique ID

� priority

� subject match

� body match

� sender match

SAS Digital Marketing assigns the unique ID that you cannot change. The subject match, bodymatch, and sender match are compared against the contents of the subject, body, and sender of thereply to determine whether the message matches a reply filter category. For example, if the body ofthe returned message contains the string user unknown, then the message is assigned to the HardBounce reply filter.

E-mail Reply Manager represents each reply filter category as a folder. If you click a reply filtercategory in the navigation tree, then the reply messages for that category appear in the E-mail ReplyManager in a table on the right.


To review the contents of a reply message, right-click the message and select Open from the pop-upmenu.

Working with the Reply Filter Categories

Default Reply Filter Categories

The E-mail Reply Manager enables you to manage the reply rules and define the categories for theserules. The following reply filter categories are automatically available:

Address Changemessages about changes in the e-mail address of a recipient.

Return Receiptautomated replies that notify you that the messages were received.

Attachment Warningattachments that were removed from a message.

Spam Warningmessages that were rejected by a spam filter.

Soft Bouncemessages that are not delivered at the moment.

Hard Bouncemessages that are not delivered.

Add a Reply Filter Category F 245

Out of Officemessages about recipients that are out of the office.

Unsubscribemessages about recipients that no longer want to receive broadcast messages.

Automated Responseautomated replies from the recipient’s address.

Repliesreplies to the broadcast message.

Othermessages that did not meet any of the reply rules defined in the other categories. This categoryis required by SAS Digital Marketing and must use Other as its name. You can specify anyvalue for the label. Do not assign any reply rules to this category.

Add a Reply Filter Category

To add a new reply filter category, complete the following steps:

1. In the E-mail Reply Manager, right-click the Reply Filter Categories folder in the navigationtree and then select New Reply Filter Category from the pop-up menu or select New ReplyFilter Category from the File menu.


2. In the Properties dialog box, use the tabs to specify the filter name, options, rules, and for-warding addresses for the reply filter. For more information, see “Reply Rules Properties” onpage 247.

3. Click OK.

NOTE: Messages that the E-mail Reply Manager has already categorized are not processed againand are not placed into new or updated categories. When you create new reply categories or changethe reply rules, then any messages that have already been saved and categorized are not processedagain with the new rules or placed into the new categories. This is also true if you delete categories.

Delete a Reply Filter Category

To delete a reply filter category, complete the following steps:

1. In the E-mail Reply Manager, select the folder for that category in the navigation tree.

2. Select Delete from the pop-up menu.

3. When the Delete Category dialog box opens, click Yes.

Reply Rules Properties F 247

If you delete a reply filter category, the E-mail Reply Manager no longer displays this category orthe reply messages in that category. However, the physical directory for the reply filter category andthe physical files that contain the reply messages are not deleted. SAS Digital Marketing does notstore the reply messages in another reply filter. The records for reply messages in this category alsoremain in the reply table.

Reply Rules Properties

By default, SAS Digital Marketing provides a list of rules for each reply filter category. These rulesdetermine whether a message matches a specified category.

To view the properties of an existing reply filter category, right-click the reply filter category inthe navigation tree and select Properties. The Properties dialog box for the selected reply filtercategory opens. A series of tabs enables you to describe the reply filter category and create rules tocategorize the reply messages.

General Properties

The General tab enables you to describe the reply filter category and set options that control howthe reply messages are processed.


You can specify the following options:

Labelspecifies the label for the reply filter. This is the name of the folder in the navigation tree ofthe E-mail Reply Manager.

Descriptiondescribes the types of messages in this reply filter category.

Namelists the name of the reply filter category.

Scan e-mail message body for embedded e-mail addressscans the reply for any embedded e-mail addresses. Select this option if messages that matchthis filter are returned with the recipient e-mail address in the body of the message. Oftenwhen a hard bounce occurs, all original content and headers are removed and the body ofthe bounced message contains details about the bad e-mail address. For this reason, the HardBounce category sets this option set by default.

Save a copy of reply messagessaves a copy of the reply messages for this reply filter. The reply messages are saved to theSAS Digital Marketing Server for the number of days that you specify in the Number of daysto keep copy box. You can view the contents of a message until the time that it is removed.Selecting this option saves disk space on the server.

Automatically register responders as opt-outsadds the e-mail addresses for the reply messages in this reply filter to the opt-out table. Thenumber of responses for a single e-mail address must match the occurrence threshold for opt-outs. For example, for the Hard Bounce category, you specify 2 as the occurrence threshold.If you receive two hard bounces from the same e-mail address, then that e-mail address isautomatically added to the opt-out table, and SAS Digital Marketing no longer sends anybroadcast messages to that address.

Use this reply filter with SAS Customer Intelligencesends reply history to SAS Customer Intelligence software. You must decide whether torecord the reply as a failed contact or as a valid response. To use the reply filter, you mustuse broadcast definitions that create correlated replies. For more information, see “UsingCorrelated Replies” on page 232.

Reply Rules Properties F 249

Rules Properties

The Rules tab enables you to view, create, edit, or delete reply rules. For more information, see“Managing Reply Rules” on page 250.


Forwarding Properties

The Forwarding tab enables you to specify e-mail addresses for forwarding reply messages thatmatch the reply filter category. For more information, see “Forwarding Replies” on page 252.

Managing Reply Rules

Create a New Reply Rule

To create a new reply rule for a reply filter, complete the following steps:

1. In the E-mail Reply Manager, right-click the reply filter category in the navigation tree andselect Properties.

2. Select the Rules tab in the Properties dialog box.

3. Click New. The New Reply Rule dialog box opens. The E-mail Reply Manager automaticallyassigns a new ID number for that reply rule. You cannot edit this ID.

Edit an Existing Reply Rule F 251

4. In the Subject Match, Body Match, or Sender Match boxes, you can specify the text tocompare to the reply messages. A reply is added to the reply filter category if the text is anexact match. If the text does not need to be an exact match, you can use an asterisk (*) as awildcard value.

For example, to categorize any reply messages with a subject of Recipient does notexist as a hard bounce, type this phrase into the Subject Match box. The content of thebody and the sender is not relevant, so enter an asterisk (*) in these boxes. With this rule, anye-mail that has a subject of Recipient does not exist is filtered to the Hard Bouncereply filter, regardless of the e-mail’s body content or sender.

NOTE: If you specify the ReplyFilterRegex server property, then you can specify regularexpressions for the reply rules. For more information, see “Reply Management Server Prop-erties” on page 147.

5. Specify a priority for each reply rule. If a reply fits the reply rules for several categories,then the value of the priority determines how the reply is categorized. For example, an e-mailmatches a reply rule for both the Spam Warning and Soft Bounce categories. The rule for theSpam Warning reply filter has a priority of 1, and the rule for the Soft Bounce reply filter hasa priority of 2. Because the priority of the rule for the Spam Warning is higher, the e-mail iscategorized as a Spam Warning.

Edit an Existing Reply Rule

To edit an existing reply rule for a reply filter, complete the following steps:




3. Select the rule that you want to change and click Modify. The Modify Reply Rule dialog boxopens.

4. Edit the options that you want to change. The options in this dialog box are identical to theoptions that are available when you create a reply rule. For more information, see “Create aNew Reply Rule” on page 250.

Delete a Reply Rule

To delete an existing reply rule for a reply filter, complete the following steps:



3. Select the rule that you want to delete and click Delete.

4. When the Delete Rule dialog box opens, select Yes.

Forwarding Replies

About Forwarding Replies

SAS Digital Marketing can forward e-mail when you need to provide automatic processing as wellas alternative processing. For example, you sent a recall notice to a set of customers who ordereda product. Any reply messages that SAS Digital Marketing receives are automatically processedby the Reply Manager. However, you also need to forward the hard bounces to an employee inthe customer service department so that this employee knows which customers did not receive thee-mail and can follow up with a phone call.

Add a Forwarding E-mail Address

To add an e-mail address for forwarding a reply message, complete the following steps:


Edit a Forwarding E-mail Address F 253

2. Select the Forward tab in the Properties dialog box.

3. Click New.

4. In the New forwarding address dialog box, type the e-mail address for the forwarded replymessages.

5. Click OK to save the information.

Edit a Forwarding E-mail Address

To edit an e-mail address for forwarding a reply message, complete the following steps:



3. Select the address from the list and click Modify.

4. In the Modify forwarding address dialog box, edit the address that you selected.

5. Click OK to save the information.

Delete a Forwarding E-mail Address

To delete an e-mail address for forwarding a reply, complete the following steps:



3. Select the address from the list and click Delete.

Chapter 10

Optimizing SAS Digital Marketing

ContentsOverview of Optimizing the Software . . . . . . . . . . . . . . . . . . . . . . . . 255Configuring a Grid Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Using the Server Configuration Wizard . . . . . . . . . . . . . . . . . . . . 256Customize the Grid Node Server . . . . . . . . . . . . . . . . . . . . . . . 256

Using the Grid Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260Configure the Server Node . . . . . . . . . . . . . . . . . . . . . . . . . . . 260Set Simulate Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261Test the Grid Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Optimizing Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262How to Optimize Performance . . . . . . . . . . . . . . . . . . . . . . . . . 262Adjusting the SMTP Spooler . . . . . . . . . . . . . . . . . . . . . . . . . 263Adjusting Performance Settings . . . . . . . . . . . . . . . . . . . . . . . . 264Adjusting Send Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264Adjusting the E-mail Settings . . . . . . . . . . . . . . . . . . . . . . . . . 265

Overview of Optimizing the Software

If your broadcast definition generates a very large number of messages, then you might want to usemore than one server to send the broadcast transmission. You can configure SAS Digital Marketingto process the broadcast across multiple computers by creating a series of grid nodes. You mustinstall SAS Digital Marketing as a grid node on each computer in the grid network. SAS DigitalMarketing can use an unlimited number of grid nodes to distribute your broadcast definitions. Formore information, see “Installing a SAS Digital Marketing Grid Node” on page 30.

In order for you to use a computer in the grid network, the grid node server must run when youexecute a broadcast. SAS Digital Marketing uses grid nodes to send e-mail, multichannel, SMS, orASP broadcasts transmissions. However, SAS Digital Marketing does not use grid nodes to previewthese broadcasts.

256 F Chapter 10: Optimizing SAS Digital Marketing

Configuring a Grid Node

Using the Server Configuration Wizard

The Server Configuration wizard enables you to specify the settings for the grid node. You can runthis wizard during the installation process or when you want to update the grid node server.

To configure the grid node, you adjust the maximum number of threads, add more e-mail servers,and set the tracking and Web publication middle tier options. Repeat this process on each computerin the grid network.

Customize the Grid Node Server

Complete the following steps to configure the grid node:

1. Start the Server Configuration wizard by selecting the SAS Digital Marketing Configura-tion shortcut from the Start menu under Windows or by running the sconfig shell script underthe UNIX or Linux operating environments.

2. After the Server Configuration wizard starts, click Next.

Customize the Grid Node Server F 257

3. Specify the value for the maximum number of threads that SAS Digital Marketing sends toimprove the performance of broadcast transmissions, and click Next. By default, SAS DigitalMarketing uses multiple threads to improve efficiency.

Set the Maximum number of threads for e-mail broadcasts to improve performance onthe grid node. Set Maximum number of SMTP spooler threads to improve performanceon the SMTP e-mail servers. For more information, see “Adjusting Performance Settings” onpage 264.


4. Specify the settings to send the broadcast transmissions and click Next.

Use the SMTP E-mail Servers table to define the additional e-mail servers. Then verifythat the settings for the outgoing SMTP e-mail server is valid. You must list at least oneoutgoing mail server. SAS Digital Marketing uses the e-mail servers to send the e-mails thatare rendered. For more information about changing these settings, see “Send Options” onpage 112.

Customize the Grid Node Server F 259

5. Specify the location of the middle tier where the tracking and Web publication servlets aredeployed and click Next. These Java servlets collect response metrics for e-mail broadcasts,process multichannel broadcasts, and manage Web resources.

The servlet WAR file that contains the tracking and Web publication servlets must be de-ployed on a Web application server outside your corporate firewall. To specify the locationof the middle tier, enter the base URL address for the Web application server. To verify thatthe Java servlets work correctly, click Test.

6. After you verify the servlets, click Finish to configure the grid node. If you want to change asetting, click Back to return to the appropriate step in the wizard.


Using the Grid Nodes

Configure the Server Node

After you install and configure the grid nodes, configure the computer that runs the SAS DigitalMarketing server to use the grid network. Then SAS Digital Marketing can distribute your broadcasttransmissions across the grid nodes.

NOTE: When you execute a broadcast transmission, SAS Digital Marketing cannot use a grid nodethat is not running.

To configure the server node, complete the following steps:

1. Start the SAS Digital Marketing server by selecting the SAS Digital Marketing Server short-cut from the Start menu under Windows, or by running the startsrv command under theUNIX and Linux operating environments. For additional information, see “Running SASDigital Marketing” (Chapter 2, SAS Digital Marketing: User’s Guide).

2. Start SAS Digital Marketing Studio by selecting the SAS Digital Marketing Studio shortcutfrom the Start menu under Windows, or run the studio shell script under the UNIX and Linuxoperating environments.

3. Select Server Configuration from the Tools menu. The Server Configuration window opens.

4. Select E-mail Options under the Broadcast Definition node. Then configure SAS DigitalMarketing to run broadcasts across the grid node servers. The Available Grid Nodes forDistributed Execution table shows the servers in the grid network that SAS Digital Marketinguses to distribute broadcast transmissions. You can add, update, or delete grid nodes.

Set Simulate Mode F 261

5. To add a grid node, click Add. In the Add grid node dialog box, type the name of a computerin the grid network and click OK. SAS Digital Marketing adds the new grid node server tothe Available Grid Nodes for Distributed Execution table.

6. Continue to add grid nodes until every computer that runs a grid node server is included inthe grid network.

Set Simulate Mode

To perform optimization testing of your server node and the associated grid node servers withoutactually sending messages, SAS Digital Marketing provides a simulate mode. To use the simulatemode, complete the following steps:

1. Run the Server Configuration wizard or open the Server Configuration window from the Toolsmenu on your server node.

2. Select Send Options under the Broadcast Transmission node or locate the step in the wizardthat sets default values for the Send options.

3. Select Simulate e-mail transmissions with a time delay and click OK to apply the setting.

Test the Grid Nodes

To test your grid nodes, complete the following steps:


1. Start SAS Digital Marketing on each grid node by selecting the SAS Digital MarketingGrid Node shortcut from the Start menu under Windows, or by running the gridnode com-mand under the UNIX and Linux operating environments. You can also start the SAS DigitalMarketing grid node server as a Windows service.

2. Use a computer that is running a SAS Digital Marking server and select the SAS DigitalMarketing Studio shortcut from the Start menu under Windows, or run the studio shellscript in the UNIX and Linux operating environments. SAS Digital Marketing Studio opens.

3. Ensure that you are simulating broadcast transmissions so that the message is not sent tothe recipients on your distribution list. For more information, see “Set Simulate Mode” onpage 261.

4. Execute an e-mail broadcast definition that has a large distribution list. In order for SASDigital Marketing to distribute the e-mail to the grid nodes, ensure that your distribution list isseveral times larger than the Number of messages to generate per thread value. This valueappears in E-mail Options under the Broadcast Definition node in the Server Configurationwindow.

5. Immediately examine the Job Queue tab in SAS Digital Marketing Studio on the server node.When the broadcast executes, examine the Threads tab. You see the computers in the gridnetwork that SAS Digital Marketing uses to execute your broadcast. You also see the threadsthat are running on each computer. You can examine the Threads tab in the SAS DigitalMarketing Monitor window for each grid node to see the threads that are running on thatcomputer.

Optimizing Performance

How to Optimize Performance

When the server node and its associated grid nodes are configured, you might want to adjust thefollowing server settings to improve performance:

� SMTP spooler

� Performance settings

� Send settings

� E-mail settings

NOTE: You should send your broadcast transmission in simulate mode before you make adjust-ments in order to avoid sending messages to your distribution list. For more information, see “SetSimulate Mode” on page 261.

Adjusting the SMTP Spooler F 263

Adjusting the SMTP Spooler

SAS Digital Marketing provides a high-performance JavaMail driver that spools messages to diskfor asynchronous message delivery to an SMTP mail server. The spooler has the following advan-tages:

� Your broadcasts execute faster when your SMTP server is unable to process the generatede-mail messages at the same rate that SAS Digital Marketing produces the messages.

� When the SAS Digital Marketing or SMTP mail server stops, the spooled e-mail messagesremain spooled. When another connection to an SMTP mail server occurs, the spooled e-mailmessages are delivered.

Before using the SMTP spooler, you should verify that SAS Digital Marketing functions properlywith the default JavaMail SMTP provider (com.sun.mail.smtp.SMTPTransport). You wantto verify that a connection to an SMTP server is available when you use your connection parameters.This step is important because the spooler uses these same connection parameters to send e-mailmessages, but not immediately when the broadcast is executed.

Note Most high performance Mail Transfer Agents (MTA), like PowerMTA, automatically imple-ment domain throttling. For high volume implementations that require domain throttling, such asa daily e-mail transmission rate over one million, you might consider using throttling at the MTAlevel.

Activate the SMTP Spooler

To activate the spooler, complete the following steps:

1. Run the Server Configuration wizard, or open the Server Configuration window from theTools menu on your server node.

2. Select Send Options under the Broadcast Transmission node or locate the step in the wizardthat sets default values for the Send options.

3. Select an e-mail server and click Edit. The SMTP Server Settings dialog box opens.

4. Use the Advanced tab and select com.sas.email.send.SpoolTransportProxy as the SMTPprovider. Click OK.

5. After you change the SMTP provider for each e-mail server, click OK to apply the settings.

You can also change the thread settings to control the number of spool threads that run asyn-chronously to deliver the e-mail messages. For more information, see “Performance Options” onpage 115.

NOTE: After changes are made to a spooler configuration, you should restart your SAS DigitalMarketing server to ensure that the changes take effect.


Adjusting Performance Settings

The Server Configuration window enables you to improve the performance of your broadcast trans-missions. Use the Performance Options under the Broadcast Transmission node to change thefollowing:

Maximum number of threads for e-mail broadcastsspecifies the maximum number of threads that SAS Digital Marketing runs on each grid nodethat sends the messages.

Maximum number of SMTP spooler threadsspecifies the number of asynchronous threads that SAS Digital Marketing uses to deliverspooled SMTP messages to an e-mail server.

For more information, see “Performance Options” on page 115.

Adjusting Send Settings

The Server Configuration window enables you to improve the performance of your broadcast trans-missions. Use the Send Options under the Broadcast Transmission node to change the following:

Number of send retriesspecifies the number of times to try re-sending e-mail.

Simulated send delay (in milliseconds)sets the number of milliseconds to pause for each message during simulation mode. Thispause approximates the network transaction time that is associated with actually sending amessage.

For more information, see “Send Options” on page 112.

Adjusting the E-mail Settings F 265

Adjusting the E-mail Settings

The Server Configuration window enables you to improve the performance of your broadcast trans-missions. Use the E-mail Options under the Broadcast Definition node to change the following:

Number of messages to generate per threadspecifies the number of e-mails to divide into blocks and to send to the grid nodes.

Prevent duplicate e-mails per broadcastfilters out all duplicate e-mail addresses when you send a broadcast transmission. You mustselect all for the e-mail audit level and Write audit records to a JDBC table on the Loggingtab.

For more information, see “E-mail Options” on page 107.

Part V

Appendixes

Appendix A

Using JMS With Broadcasts

ContentsOverview of JMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269Configuring a JMS Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Configure a JMS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269Test JMS in SAS Digital Marketing . . . . . . . . . . . . . . . . . . . . . . 278

Using the JMS Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Writing a Client to Process Response Events . . . . . . . . . . . . . . . . . . . . 281

Overview of JMS

JMS is a Java message standard that enables application components that are based on the Java 2Platform, Enterprise Edition (J2EE) to create, send, receive, and read messages. You must havea JMS provider to use JMS. To use JMS with SAS Digital Marketing, you configure JMS for usewith BEA WebLogic as the provider and test the JMS provider. Then you configure SAS DigitalMarketing to use the JMS provider and write a client to process response events.

Configuring a JMS Provider

Configure a JMS Server

To configure JMS for use with BEA WebLogic, complete the following steps:

1. Log on to the WebLogic Server Console and, in the Console tree, open

Services ! JMS ! Servers.

270 F Appendix A: Using JMS With Broadcasts

2. Click Configure a new JMS Server in the JMS Servers pane.

Configure a JMS Server F 271

3. Type SASDigitalMarketing as the name of your JMS server and click Create.


4. The SAS Digital Marketing server appears in the WebLogic Server Console. To verify thatthe SAS Digital Marketing server is deployed to your server, click the Target and Deploytab. Select your server from the Target drop-down list and click Apply.


5. Expand the Destinations node under

Services ! JMS ! Servers ! SASDigitalMarketing

and select Configure a New JMS Queue.


6. To create the JMS queue, specify ResponseQueue as the queue name and the JNDI name.Click Create.


7. To create a JMS topic, specify ResponseTopic as the topic name and the JNDI name. ClickCreate.


8. Expand the Connection Factories node under

Services ! JMS

9. Select Configure a New JMS Connection Factory.


10. To create the connection factory, specify SASDigitalMarketingFactory as the factory nameand JNDI name. Click Create.


11. To verify that the SASDigitalMarketingFactory is deployed to your server, click the Targetand Deploy tab, select the server, and click Apply.

Test JMS in SAS Digital Marketing

To test the JMS configuration, complete the following steps:

1. Deploy the tracking servlets as described in “Configuring the Tracking and Web Pub-lication Tier” on page 54. Then append /jmstest to the Web address for the rootURL of the BESS deployments. For example, if your BESS deployments are located athttp://myhost.com/bess, then use http://myhost.com/bess/jmstest to ac-cess the SAS Digital Marketing JMS Test page.

Test JMS in SAS Digital Marketing F 279

If you use WebLogic and the suggested names for the JMS queue, topic, and factory, thenthe default settings are correct. Otherwise, change these names to match your configurationbefore you click Test JMS Settings.

2. Start the SAS Digital Marketing Server by selecting the SAS Digital Marketing Servershortcut from the Start menu under Windows or by running the startsrv command under theUNIX and Linux operating environments.

3. Start SAS Digital Marketing Studio by selecting the SAS Digital Marketing Studio shortcutfrom the Start menu under Windows or by running the studio shell script under the UNIXand Linux operating environments.


4. Select JMS Queue Monitor from the Tools menu to open the E-mail JMS Queue Monitorwindow.

5. Type the settings that you verified on the SAS Digital Marketing JMS Test page, includingthe fully qualified hostname of the JMS URL.

6. Click Connect to connect to the JMS Queue that you verified on the SAS Digital MarketingJMS Test page.

7. On the SAS Digital Marketing JMS Test page, click Test JMS Settings. A test messageappears in the E-mail JMS Queue Monitor window.

Using the JMS Provider F 281

Using the JMS Provider

After you verify that your topic and queues are functioning correctly with the SAS Digital MarketingJMS Test page and the JMS Queue Monitor, configure the SAS Digital Marketing components touse JMS. The JMS configuration settings that are required by the configuration dialog boxes shouldmatch the settings that you previously verified on the JMS Test page.

You must specify the JMS settings in the following locations:

SAS Digital MarketingUse the Server Configuration window. For more information, see “Overview of Customizingthe Server” on page 99. To verify that these settings work properly, execute a small broadcastthat has the e-mail audit event set to all. During broadcast execution, your JMS applicationshould receive audit events. For more information, see “Auditing Broadcast Transmissions”(Chapter 4, SAS Digital Marketing: User’s Guide).

E-mail Reply ManagerUse the Reply Manager Configuration window that is available by selecting Configure ReplyManager from the Tools menu. To verify that these settings work properly, send an e-mailthat has Out of Office as the subject line to the e-mail account that your Reply manager isconfigured to use. When the Reply manager is run, your JMS application receives a replyevent that has a type property set to Out of Office. For more information, see “Working withthe E-mail Reply Manager” on page 235.

Tracking ServletsUse the Tracking Configuration wizard to prepare and deploy a new WAR file. For more infor-mation, see “Configuring the Tracking and Web Publication Tier” on page 54. To verify thatthese settings work properly, deploy the JMS-enabled servlets, and use the SAS Digital Mar-keting Tracking Servlets Test page to receive click and view events in your JMS application.For more information, see “Verify the Tracking Servlets” on page 68.

Writing a Client to Process Response Events

If you are unfamiliar with JMS programming, use the Java Message Service tutorial that is availableat the Web site http://java.sun.com/products/jms/tutorial/.

Example JMS Queue and Topic clients are included in the ROOT/doc/jms directory. Here is thedefault location for the JMS example on a computer that is running on the Windows environment.

C:/Program Files/SAS/SASDigitalMarketing/5.1/doc/jms

The readme.txt file or the readme.html file at this location contains build instructions and otherinformation about the sample JMS clients.

Glossary

API (application programming interface)a set of software functions that facilitate communication between applications and other kindsof programs, services, or devices.

ASP (Application Service Provider)a company that provides a software application on a shared server over the Internet. ASPstypically charge a fee for use of this software.

bouncean e-mail message that is returned to the sender because of an error in the delivery process.

broadcasta communication that is distributed by SAS Digital Marketing software through e-mail orthrough another electronic medium.

broadcast definitiona collection of information that describes a broadcast transmission. A broadcast definitionincludes header information, a recipient list, the type of message to send, the content to send,and a description of what to track. A broadcast definition also includes related executionrecords such as audit records, history records, and response records.

broadcast tracking servleta servlet that records data when an e-mail recipient either views an e-mail that contains theURL of a crumb servlet or clicks a tracked link in an e-mail. See also crumb servlet and redirservlet.

campaigna planned set of one or more communications that are directed at a selected group of cus-tomers or potential customers.

channela mode of communication such as an e-mail message or a print mailing.

correlated replyan e-mail reply that SAS Digital Marketing can connect to a specific broadcast definition byinserting the moniker for broadcast in the reply address. See also moniker.

crumb servleta type of broadcast tracking servlet that records data when a recipient views an e-mail thatcontains the URL of a crumb servlet.

grid computinga type of computing in which large computing tasks are distributed among multiple comput-ers on a network.

grid nodea specialized server that is used for broadcast distribution.

284 F Glossary

HTTP (HyperText Transfer Protocol)a protocol for transferring data to the Internet. HTTP provides a way for servers and Webclients to communicate. It is based on the TCP/IP protocol.

IMAPa method of getting e-mail from a server. IMAP is a more sophisticated set of rules than POP.See also POP.

J2EEan environment that can be used to develop Web applications.

JAR filea Java Archive file. The JAR file format is used for aggregating many files into one file. JARfiles have the file extension .jar.

JDBC (Java Database Connectivity)a standard interface for accessing SQL databases. JDBC provides uniform access to a widerange of relational databases. It also provides a common base on which higher-level toolsand interfaces can be built.

JDBC data providera data provider that complies with JDBC.

JDBC providerSee JDBC data provider.

JDK (Java Development Kit)a software development environment that is available from Sun Microsystems, Inc. The JDKincludes a Java Runtime Environment (JRE), a compiler, a debugger, and other tools fordeveloping Java applets and applications.

JMS (Java Message Service)an application programming interface (API) that enables client applications to access thefacilities of a message service. This interface provides a standard way for Java programs tocreate, send, receive, and read messages.

JVM (Java Virtual Machine)a program that interprets Java programming code so that the code can be executed by theoperating system on a computer. The JVM can run on either the client or the server. TheJVM is the main software component that makes Java programs portable across platforms.A JVM is included with JDKs and JREs from Sun Microsystems, as well as with most Webbrowsers.

MMS (Multimedia Message Service)an extension of SMS that enables the transmission of longer text messages with graphicalimages and audio clips to handheld wireless devices. See also Short Message Service.

monikera unique identifier for a broadcast definition that is assigned when you create a new broadcast.You can use the moniker to correlate reply, response, and audit events to the broadcast thatgenerated them.

MTA (Mail Transport Agent)an application that handles the sending and receiving of e-mail.

Glossary F 285

POPa method of getting e-mail from a server. POP offers fewer services than IMAP. See alsoIMAP.

redir servleta type of tracking servlet that records data in a response table when an e-mail recipient clicksa tracked link in an e-mail. See also crumb servlet.

reply filter categorya set of rules that are created in the E-mail Reply Manager. SAS Digital Marketing usesthese rules to categorize replies, forward replies, delete replies, and add e-mail addresses toan opt-out list.

RMI (remote method invocation)a Java programming feature that provides for remote communication between programs byenabling an object that is running in one Java Virtual Machine (JVM) to invoke methods onan object that is running in another JVM, possibly on a different host. See also JVM (JavaVirtual Machine).

RSS (Really Simple Syndication)an XML format to syndicate Web-based content. You use an RSS feed to monitor changes toWeb-based content using an RSS reader.

servleta Java program that runs on a Web server. Servlet code does not have to be downloaded to aWeb browser. Instead, servlets send HTML or other appropriate content back to a browser orto another type of Web-based client application.

SMS (Short Message Service)the transmission of text messages to handheld wireless devices through an SMTP-SMS gate-way. The messages are not more than 160 alphanumeric characters.

SMTPa set of rules that the Internet service provider uses to send e-mail.

threadthe smallest task or part of a program that can be executed independently of other parts of theprogram.

tracking servletSee broadcast tracking servlet.

WAP (Wireless Application Protocol)an open international standard that specifies how to transmit and access optimized Internetcontent on handheld wireless devices.

Web Archive file (WAR file)a type of Java file.

XSL (Extensible Stylesheet Language)a language that can be used to specify how XML documents will be formatted.

Index

accessibility features, iiiaddresses, see e-mail addressesarchitecture, 10ASP broadcasts

Clickatell, 170definition properties, 171definition types, 170life cycle of, 15NowSMS, 170response decoder, 177

ASP Definition Manager, 170settings, 105

attachment warning, 244audit records

customizing, 110logging settings, 109

audit server properties, 134audit table

configuring, 111

basic security mode, 129batch jobs, 192

distribution lists, 158batch SAS sessions, optimizing, 144BEA WebLogic server

configuring JMS with, 269deploying tracking servlets to, 55

bounces, 244broadcast definitions, 158broadcast moniker, 232broadcast replies, 232broadcast reports, 192broadcast responses

processing, 281tracking servlets, 25

broadcast schedulerconfiguring, 85

broadcast tracking, 230broadcasts

configuring transmissions, 112customizing, 16life cycle of, 11migrating, 26sending, 112tracking servlets, 54

Clickatell SMS broadcast type, 170Clickatell WAP broadcast type, 170clients

installing, 32processing response events, 281server properties, 135

config.xml file, 38configuration, see also server configuration

ASP definitions, 105audit table, 111broadcast transmissions, 112contact history, 121distribution list, 106domain throttling, 116e-mail broadcasts, 107e-mail reply account, 236E-mail Reply Manager, 236e-mail servers, 113grid nodes, 256JDBC data providers, 222JMS, 269, 278response history, 123SAS Digital Marketing Web Studio, 83SAS Information Delivery Portal, 88server nodes, 260server settings for performance, 262servers, 38Servlet Configuration wizard, 71spam filter, 181tracking servlets, 54validating, 93WAP integration, 119WAP integration broadcast, 178Web services, 120Windows service, 95

consolidating data, 206contact history

configuring, 122settings, 121

correlated replies, 232crumb servlet, 25

testing, 69Customer Intelligence

contact history, 121middle tier, 120reply history, 243, 248response history, 122

customizingaudit records, 110broadcasts, 16grid node configuration, 256

288 F Index

dataconsolidating with other business processes,

206data source tables, 158

sample, 93delivery architecture, 10deploying Java servlets

Web application, 24deploying servlets

Web application, 54deploying tracking servlets

Apache Tomcat, 57BEA WebLogic, 55IBM WebSphere, 58proxy server, 79

directory structure, 23Distribution List Manager, 161

settings, 106distribution lists, 158, 166

creating, 158modifying, 161

documentation, 16domain mailbox, 233domain throttling

configuring, 117

e-mail addressesaddress changes, 244embedded, 248for correlated replies, 232

e-mail broadcastsconfiguring, 107creating with distribution list, 158life cycle of, 11settings, 107, 265specifying grid nodes, 108

e-mail filter, 181e-mail reply account, configuring, 236E-mail Reply Manager, 235

accessing tasks, 241adding reply filter categories, 245configuring, 236deleting reply filter categories, 246deleting reply rules, 252forwarding reply messages, 250general properties of reply filter categories,

247managing reply rules, 250modifying reply rules, 251opening, 240reply filter categories, 244reply filters and reply rules, 243reply rules and categories, 244

e-mail reply settings, 101

configuring, 101e-mail servers, configuring, 113edit server properties, 138embedded e-mail addresses, 248encoding server properties, 140ETL processes, 10events

response events, 281Extract, Transform, and Load (ETL) processes, 10

file, executing from a, 143filtering

reply filter categories, 243, 244forwarding reply messages, 250, 252

add e-mail address, 252delete e-mail address, 253edit e-mail address, 253

geographical reporting, 183geolocation database, 184get servlet, 25global data models, 166

managing, 166grid nodes

configuring, 256configuring server nodes, 260customizing configurations, 256installing, 30simulate mode, 261testing, 261

group reports, 192

hard bounce, 244

IBM WebSphere server, deploying trackingservlets to, 58

installation, 21clients, 32directory structure, 23grid nodes, 30migrating broadcasts, 26requirements for, 22servers, 26

InstallShield wizardclient installation, 33grid node installation, 30server installation, 27

integration utilities server properties, 141IOM workspace connections, optimizing, 144

J2EE JavaMail, 10Java Message Service, see JMSJava servlets, 10, 24JDBC connections, 221

defining, 124, 222

Index F 289

JDBC data providers, 222SAS JDBC Explorer, 225

JDBC data providersconfiguring, 222connections settings, 222creating connections settings, 124types of, 222

JDBC Explorer, 225accessing tasks, 226components, 226opening, 225

JDBC server properties, 142JMS, 102

configuring the server, 102configuring with BEA WebLogic, 269JMS topic and queue, 273processing broadcast responses, 269processing response events, 281testing JMS configuration, 278

JMS provider, 281

keyboard shortcuts, iii

life cycle of broadcasts, 11ASP broadcasts, 15e-mail broadcasts, 11RSS feeds, 11SMS broadcasts, 14

logsettings for audit records, 109

MaxMind software, 184messages, see also text message broadcasts

copies of reply messages, 248forwarding reply messages, 250

metadata security mode, 131

New Distribution List wizard, 159new features, 3notification list, 118NowSMS broadcast type, 170

opt-out tableadding responders to, 248

optimization, 255adjusting configuration settings, 262adjusting SMTP spooler, 263configuring grid nodes, 256configuring server nodes, 260grid nodes, 260optimizing performance, 262testing grid nodes, 261

optimizingbatch SAS sessions, 144IOM workspace connections, 144

server properties, 144optout servlet, 25Out of Office notice, 245

performance optimizationadjusting configuration settings, 262adjusting SMTP spooler, 263

ports, restricting, 145preview server properties, 146Properties dialog box

Security tab, 168proxy settings, 128pub servlets, 25

redir servlet, 25testing, 69

replies, 245forwarding, 252processing, 101server properties, 147tracking, 232tracking correlated replies, 232tracking uncorrelated replies, 232

reply categories, 244reply filter categories, 243, 244

adding, 245deleting, 246general properties, 247

reply messagescopies of, 248forwarding, 250

reply rules, 243, 244creating, 250deleting, 252managing, 249modifying, 251properties, 247

reportsbroadcast groups, 192broadcasts, 192

res servlet, 25response decoder, 177response events

processing, 281response history

configuring, 123settings, 122

response server properties, 151response table

changing, 231geolocation data, 188setting, 231

responses, see See broadcast responsesresponses, automated, 245

290 F Index

return e-mail address, 232, 233return receipt, 244ROOT directory, 26RSS feeds

life cycle of, 11rss servlet, 25

sample broadcastspreviewing, 94

SAS Customer Intelligence software, 7SAS Digital Marketing, ii, 7

architecture, 8as Windows service, 95components, 21installing, 21optimizing, 255

SAS Digital Marketing serverinstalling, 26updating, 83

SAS Digital Marketing Web Studioconfiguring, 83deploying to Web application servers, 83

SAS E-mail Marketing, migrating broadcasts, 26SAS Information Delivery Portal, 88

configuring, 88linking to SAS Digital Marketing, 89

SAS JDBC Explorer, 225accessing tasks, 226components, 226opening, 225

SAS Job Editor, 195Compiled SAS Code tab, 199creating keywords for code, 205customizing code appearance, 204customizing options, 203Log tab, 196menus, 199preferences, 203Properties tab, 198Target tab, 197toolbar, 202

SAS Job Manager, 192SAS jobs, 192

batch jobs, 192broadcast reports, 192configuring, 104consolidating data, 206creating, 193default macros, 206deleting, 194editing, 194group reports, 192renaming, 194

SAS language adapter, 190

configuring, 103implementing, 86requirements, 86

SAS macros, 206SEM_DO_PREVIEW, 207SEM_DO_TRANSACTION, 208SEM_EXPORT_PROPERTIES, 209SEM_GET_ALL_BROADCASTS, 210SEM_GET_ALL_REPLIES, 211SEM_GET_AUDIT, 212SEM_GET_GROUP, 213SEM_GET_HISTORY, 214SEM_GET_PROPERTIES, 215SEM_GET_REPLIES, 216SEM_GET_RESPONSE, 217SEM_GROUP_HISTORY, 218SEM_SET_META, 219SEM_SET_PROPERTY, 220

SAS programs, see SAS jobsSAS reports, 183SAS settings, 103scheduling

configuring, 85, 118server properties, 153settings, 117

security settings, 128basic security mode, 129changing, 167metadata security mode, 131user groups, 132

send settings, 112, 264configuring broadcast transmissions, 112configuring e-mail servers, 113

server configurationaudit logging settings, 109connection settings, 124, 222e-mail broadcast settings, 107e-mail reply settings, 101JMS settings, 102modifying settings, 99SAS settings, 103scheduling settings, 117security settings, 128send settings, 112server properties, 126threads settings, 115throttled domain settings, 117tracking settings, 125

Server Configuration window, 262Server Configuration wizard, 39, 256server extension

MaxMind, 186server nodes, configuring, 260server properties, 126, 133, 186

Index F 291

adding, 127audit, 134client UI, 135configuring, 126deleting, 127editing, 138encoding, 140integration utilities, 141JDBC, 142MaxMind, 187optimize, 144previewing, 146reply management, 147response, 151restricting ports, 145scheduling, 153setting, 126SMTP e-mail server specification, 147viewing current settings, 127

serversadvanced properties, 133, 187configuring, 38configuring e-mail servers, 113executing from a file, 143executing from a table, 143installing, 26Web application servers, 24, 54Web Studio server, 83

Servlet Configuration wizard, 71servlets, see also tracking servlets

crumb, 25, 69deploying to Web application servers, 54get, 25Java, 10optout, 25pub, 25redir, 25, 69res, 25rss, 25

servlets WAR file, 24, 54, 57, 79Sever Configuration window

components, 99opening, 99

shortcuts, iiisimulate mode, 261SMS broadcasts

life cycle of, 14SMTP e-mail server, changing, 147SMTP spooler, 263soft bounce, 244software requirements, iispam warning, 244SpamAssassin software, 181

implementing a filter, 182

spooler, 263

table, executing from a, 143tables

audit table, 111data source tables, 158opt-out table, 248response table, 188, 231

testingcrumb servlet, 69grid nodes, 261JMS configuration, 278redir servlet, 69simulate mode, 261tracking servlets, 68

text message broadcastscreating ASP definition types, 170

threadsconfiguring, 115settings, 115, 264

Throttled Domain Managersettings, 116

Tomcat server, deploying tracking servlets to, 57tracking

correlated replies, 232server configuration settings, 125settings for, 125uncorrelated replies, 232

tracking and Web publication tierspecifying location of, 125

tracking architecture, 10tracking broadcast responses

changing the response table, 231E-mail Reply Manager, 240

tracking parameters, 230tracking servlets, 25, 54

crumb servlet, 25deploying servlets WAR file, 54, 79get servlet, 25optout servlet, 25proxy server, 79redir servlet, 25testing and verifying, 67, 68updating, 70

Tracking Servlets Test page, 68

uncorrelated replies, 232unsubscribe request, 245updating

SAS Digital Marketing server, 83tracking servlets, 70

user authentication levels, 128user credentials, 128

changing, 167

292 F Index

user groups, 132changing security, 168

validating configuration, 93verifying tracking servlets, 68

WAP integrationconfiguring, 119settings, 119

WAP integration broadcast, 178WAR files, 24, 54, 57Web application

viewing SAS reports, 183Web application servers

Apache Tomcat, 57BEA WebLogic, 55deploying Java servlets to, 24deploying servlets to, 54deploying Web Studio, 83IBM WebSphere, 58

Web publicationsecurity, 79servlets, 54

Web publication servlets, 54pub servlets, 25res servlet, 25rss servlet, 25

Web reporting, 83Web services

configuring, 120specifications, 120

Windows service, SAS Digital Marketing as, 95

Your Turn

We want 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 gives you the tools to flourish in any environment with SAS!Whether you are new to the workforce 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.

SAS® Press SeriesNeed to learn the basics? Struggling with a programming problem? You’ll fi nd the expert answers that you need in example-rich books from the SAS Press Series. Written by experienced SAS professionals from around the world, these 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® DocumentationTo 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: online help that is built into the software, tutorials that are integrated into the product, reference documentation delivered in HTML and PDF—free on the Web, and hard-copy books.

s u p p o r t . s a s . c o m / p u b l i s h i n gSAS® Learning Edition 4.1Get a workplace advantage, perform analytics in less time, and prepare for the SAS Base Programming exam and SAS Advanced Programming exam with SAS® Learning Edition 4.1. This inexpensive, intuitive personal learning version of SAS includes Base SAS® 9.1.3, SAS/STAT®, SAS/GRAPH®, SAS/QC®, SAS/ETS®, and SAS® Enterprise Guide® 4.1. Whether you are a professor, student, or business professional, this is a great way to learn SAS.

s u p p o r t . s a s . c o m / L E

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. © 2007 SAS Institute Inc. All rights reserved. 428713_1US.0307

Date post:	27-Oct-2014
Category:	Documents
Upload:	milan-tomic
View:	220 times
Download:	30 times

Admin Guide

Documents