Administrators Guide
The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2007. SAS Digital Marketing 5.1: Administrators Guide. Cary, NC: SAS Institute Inc.
Contents
I Overview 1
3
7
II Installation
Chapter 2. Installing SAS Digital Marketing . . . . . . . . . . . . . . . .
19
21
III Conguration
Chapter 3. Chapter 4. Chapter 5. Conguring SAS Digital Marketing . . . . . . . . . . . . . . .
35
37 97 133
IV Maintenance
Chapter 6. Chapter 7. Chapter 8. Chapter 9. Managing Advanced Broadcast Tools . . . . . . . . . . . . . . . Managing SAS Jobs . . . . . . . . . . . . . . . . . . . . . Managing JDBC Connections . . . . . . . . . . . . . . . . .
155
157 189 221 229 255
V Appendixes
Appendix A. Using JMS With Broadcasts . . . . . . . . . . . . . . . . .
267
269
Glossary
283
Index
287
Credits
Documentation
Writing Lynne Bresler, Marie Dexter, Jennifer Jeffreys-Chen, Michael Monaco, and Jenna Moore Carolyn Sutton and Joan Knight Tim Arnold, Monica McClain, and Stacy Suggs
Software
Development Jennifer Jeffreys-Chen, Michael Monaco, and Susanna Wallenberger Jennifer Jeffreys-Chen and Merri Jensen
Support
Technical Product Management Steve Nash Michael Monaco
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 SMTPSMS gateway that sends SMS, MMS, and WAP Push messages to wireless devices N OTE : 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 improve usability of the product for users with disabilities. These features are related to accessibility standards for electronic information technology adopted by the U.S. Government under Section 508 of the U.S. Rehabilitation Act of 1973, as amended. If you have questions or concerns about the accessibility of SAS products, send e-mail to accessibility@sas.com.
You can also access menu items by using the keyboard shortcuts listed in the drop-down menus or by clicking ALT + the underlined letter.
iii
Part I
Overview
Overview
SAS Digital Marketing 5.1 has the following changes and enhancements: improved conguration in SAS Digital Marketing enhanced security features enhanced digital data repository enhanced support for broadcast denitions improved integration with SAS Customer Intelligence software enhanced reporting enhancements to the Web Studio interface documentation enhancements
Improved Conguration
Conguration of SAS Digital Marketing has been improved. You can now create the WAR les for tracking deployment and SAS Web Studio deployment on the middle tier from the SAS Digital Marketing Conguration wizard. No additional steps are required.
4 !
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. SAS Digital Marketing enables you to dene, test, and execute a multichannel campaign by using a broadcast wizard.
Enhanced Reporting ! 5
You can view export denitions from SAS Marketing Automation in SAS Digital Marketing. You can view broadcast denitions from SAS Digital Marketing in SAS Marketing Automation. You can link multiple cells to a single communication, even when different treatments are used to personalize content. SAS Digital Marketing and SAS Customer Intelligence share contact and response history tables. 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.
6 !
Documentation Enhancements
In addition to the existing SAS Digital Marketing references, a separate book, the SAS Digital Marketing Web Studio: Users Guide, has been created. This book contains information for all users of Web browser clients.
Chapter 1
integration with SAS Customer Intelligence software and predictive analytics to identify the best 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 are contained in an opt-out table a global duplication policy that lters out all duplicate e-mail addresses when you send a broadcast
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 Wireless Application Protocol (WAP) Push messages. Extensible Stylesheet Language (XSL) for e-mail content specication. Java Database Connectivity (JDBC) technology for access to data tables that provide digital message 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 congured e-mail server for SAS Digital Marketing to use. JavaMail supports Simple Mail Transfer Protocol (SMTP), Post Ofce Protocol (POP), and Internet Message Access Protocol (IMAP) communication methods to an MTA. N OTE : IMAP support for the JavaMail application program interface (API) is experimental in this version 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 Marketing provides several tracking and utility servlets for the mid-tier. You must deploy a Web application server to track e-mail broadcasts when you use these servlets. For more information, see Conguring the Tracking and Web Publication Tier on page 54. J2EE JavaMail technology to implement an e-mail client that records e-mail replies.
Intended Audience ! 17
Chapter 7, Managing SAS Jobs, explains how to use SAS jobs to create reports and consolidate 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 Reply Manager to process broadcast replies. Chapter 10, Optimizing SAS Digital Marketing, explains how to improve performance by distributing the broadcast transmissions across the grid network.
Intended Audience
This documentation is for users who install, congure, and optimize SAS Digital Marketing under the UNIX or Linux operating environments, and on PC platforms. SAS and other programming expertise is not required.
Part II
Installation
Chapter 2
Software Components
Before you run SAS Digital Marketing, a site administrator must install the software and deploy Web archive les to a middle tier. SAS Digital Marketing provides utilities to install and congure the following software components: Server installs SAS Digital Marketing clients and the SAS Digital Marketing server. Grid node installs SAS Digital Marketing clients and a SAS Digital Marketing grid node. Client installs the SAS Digital Marketing Studio client.
Java Servlets and Web Studio congures Java servlets in the Web archive (WAR) les. You deploy these les on a Web application server. SAS Digital Marketing can process sizable e-mail broadcasts across multiple computers when you install grid nodes and congure the server to use the computers in the grid network. The server can distribute 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 le 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 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 SMTPSMS gateway that sends SMS, MMS, and WAP Push messages to wireless devices N OTE : IMAP support for JavaMail API is experimental in this version of SAS Digital Marketing.
SAS Digital Marketing under AIX requires an IBM 1.4.1 32-bit JRE. For more information, see SAS Note SN-012999. For information about specic hardware, software, and memory congurations, see the Install Center at http://support.sas.com. N OTE : 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 of the databases that SAS/ACCESS supports.
nodecong directory contains grid node settings. pending directory contains temporary les that are used for domain throttling. replies directory contains e-mail message replies and bounces. reports directory contains XSL templates that are used to generate HTML broadcast reports. WEBROOT directory contains Web resources les. rss directory contains that RSS Feed denitions that are used by the Feed Manager. samples directory contains the les that are examples of e-mail content. sasmacro directory contains SAS macro programs that are used to generate SAS reports. spool directory contains spooled e-mails that are stored by the SMTP spooler. temp directory contains temporary les that are used in broadcast executions. This documentation uses the word ROOT to refer to the directory where you installed SAS Digital Marketing. SAS Digital Marketing requires Write access to the ROOT directory and its subdirectories when a user runs the server.
Java Servlets
SAS Digital Marketing stores the Java servlets for response tracking and the Web publication framework in the Web archive le, bess.war. You use the SAS Digital Marketing Servlet Conguration wizard to congure a WAR le for deployment that contains the servlets. For more information, see Conguring the Tracking and Web Publication Tier on page 54.
Java Servlets ! 25
You should not replace the entire SAS Digital Marketing directory. Merge the contents of both directories instead. Otherwise, you will lose the predened SAS Digital Marketing sample broadcast denitions.
3. Specify the location of the directory to use for software installation and click Next. You must have Write access to the directory. Click Browse to locate another directory.
4. Specify the directory location of the broadcast and the content les and click Next.
When you create a broadcast denition, a copy of the broadcast content is stored in the content directory. This content is available for use when you execute the broadcast. If you uninstall SAS Digital Marketing before you install a new release of the software, then your broadcasts will not be available. 5. Specify the port number and click Next.
SAS Digital Marketing uses Java Remote Method Invocation (RMI) technology. The port that you specify is the port number on which RMIs registry accepts calls on this computer. If another application on this computer uses port 9221, specify a different port number to avoid conicts. N OTE : Other ports are also used by RMI for client-server connectivity. To restrict the ports that are used, see the CustomSocketFactory server property in Properties for Restricting Ports on page 145. 6. Review the installation information and click Next to install the software. If you decide to change a setting, click Back to return to the appropriate step in the wizard. 7. Decide whether to run the Conguration wizard and click Next. For more information, see Conguring the SAS Digital Marketing Server on page 38. If you select No, then click Next and Finish to close the Installer window.
3. Select Grid Node as the installation conguration and click Next. N OTE : If SAS Digital Marketing is already installed on your computer, then you are not prompted about how to congure the installation. The Installer wizard displays the softwares current location. Click Next to re-install SAS Digital Marketing in this location.
4. Specify the location of the directory to use for software installation and click Next. Click Browse to locate another directory. N OTE : You must have Write access to this directory. 5. Specify the port number and click Next. SAS Digital Marketing uses Java Remote Method Invocation (RMI) technology. The port that you specify is the port number on which RMIs registry accepts calls on this computer. If another application on this computer uses port 9221, specify a different port number to avoid conicts. 6. Review the installation choices and click Next to install the software. If you decide to change a setting, click Back to return to the appropriate step in the wizard. 7. Decide whether to run the Conguration wizard and click Next. For more information, see Conguring a Grid Node on page 256. If you select No, then click Next and Finish to close the Installer window.
4. Specify the location of the directory to use for software installation and click Next. Click Browse to locate another directory. N OTE : You must have Write access to this directory. 5. Review the installation choices and click Next to install the software. If you decide to change a setting, click Back to return to the appropriate step in the wizard. Click Finish to close the Installer window.
Part III
Conguration
Chapter 3
N OTE : If a SAS Digital Marketing client is running on a server that you have just congured, then either restart the client or click Refresh from the toolbar to use the new server settings.
SAS Digital Marketing assumes that your license le is located in the ROOT/config directory for the software installation. Click Browse to locate the le in another directory. N OTE : Your license is distributed with your site installation data and it is found with your other SAS licenses. 3. Specify the location of the third-party database JDBC JAR les or custom CLASS les. Then click Next. SAS Digital Marketing incorporates these les into the WAR le that tracks broadcast responses.
N OTE : : You might want custom CLASS les for ASP decoders, Adobe Dreamweaver Snippets. or MaxMind extensions. SAS Digital Marketing can use a database from another vendor, such as MySQL, to track replies and responses from a broadcast. If the audit table, response table, or reply table use databases other than SAS/SHARE, then you must include JDBC connection third-party JARs. For each database, you acquire the connection JARs that are required to connect to that database from Java. For example, DB2 requires the db2jcc.jar le. To include JARs in the WAR le that contains the servlets, complete the following steps: a) Click Add JAR. b) For each database, specify the location of the JAR le in the Open window. c) Click OK. To delete a JAR le, select the le in the JARs box and click Remove.
If new JAR or CLASS les are installed on the SAS Digital Marketing server, then these les are automatically installed on the SAS Digital Marketing Studio client when you connect to this server. You are asked to restart the SAS Digital Marketing Studio client after the JAR les are installed. 4. Specify the JDBC connection information for the SAS/SHARE server, SAS Workspace Server, 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.
You can specify the number of times that SAS Digital Marketing tries to send a broadcast message and whether to simulate the broadcast transmission. You can also specify to automatically use the opt-out table to lter the e-mail transmission. For non-Asian languages, use 8-bit as the value for Default mime transfer encoding. Some Asian languages use 7-bit mime transfer encoding or another other value. For more information, see MIME (RFC 2045). Use the E-mail Servers table to verify your outgoing SMTP mail server and add additional e-mail servers. For more information about changing these settings, see Send Options on page 112.
6. Specify the location of the middle tier, or specify that you want to create a new WAR le for the Java servlets and click Next. The Java servlets collect response metrics for e-mail broadcasts, process multichannel broadcasts, and manage Web resources.
If the WAR le 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 by entering the base URL address for the Web application server. To verify that the tracking servlets work correctly, click Test. If you want to create a new WAR le that contains the servlets for the middle tier, select Create a new tracking deployment. You specify settings for the JDBC connection, the link table, and the opt-out table.
7. If you are creating a new tracking deployment, then specify the JDBC connection information for the SAS/SHARE server, SAS Workspace Server, or the third-party database server that SAS Digital Marketing uses to collects response data 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.
8. If you are creating a new tracking deployment, then specify the link table to track the response to 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 a different table connection, then use the Connections drop-down list to select the connection denition. Tracked links in text content can become quite large. Unlike with HTML content, the recipient sees the actual link in the text content. When a tracked link is embedded in the broadcast content, SAS Digital Marketing adds the URL to the link table and generates an index. SAS Digital Marketing uses the index to shorten the tracked URLs in the text content that a recipient receives. The table that contains the links must always be available so that the URLs are found when a recipient clicks the links. N OTE : 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 the location of a Web page. This Web page opens when an e-mail recipient clicks an invalid link or if the link table is not available. You must locate the Web page outside a corporate rewall so that it is available to your e-mail recipients. This Web page also displays when the link table is inaccessible and the e-mail recipient clicks a tracked link in the e-mail content that is indexed.
9. If you create a new tracking deployment, then specify the opt-out table to record the e-mail addresses of recipients and click Next. SAS Digital Marketing excludes the e-mail addresses in this table from receiving e-mail transmissions.
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 a different table connection, then use the Connections drop-down list to select the connection denition. If the Automatically apply opt-out table during send processing option is set and SAS Digital Marketing records an address in the opt-out table, then no broadcast e-mails are sent to this address. Addresses are recorded in the opt-out table when an e-mail recipient clicks a link in the e-mail message that has the opt-out servlet embedded. This link is created by using the Insert HTML opt-out link or Insert TEXT opt-out link options in the Insert other expressions dialog box. Addresses are also recorded in the opt-out table when you set a Reply Manager rule threshold. For more information, see Response Tracking (Chapter 7, SAS Digital Marketing: Users Guide). Select Redirect to custom opt-out notication page to specify the location of a Web page that opens when an e-mail recipient decides to opt out of an e-mail broadcast. The Web page should include a message that you are processing the request to remove the recipient from the mailing 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 broadcasts from being sent to the same recipient address, you must set the options to create an audit table and record all audit events. You can also congure SAS Digital Marketing to distribute the broadcast transmissions to a grid network. For more information about changing these settings, see E-mail Options on page 107. N OTE : If you select the Prevent duplicate e-mails per broadcast option, then SAS Digital Marketing sends only one broadcast per e-mail address. Therefore, transaction broadcasts work 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 about this directive, see Using E-mail Directives (Appendix B, SAS Digital Marketing Users Guide).
11. Specify the settings to log server actions and to create broadcast audit records and then click Next. 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 create audit records, set the Audit level to all, select Write audit records to a table, and click Congure Audit Table to specify the audit table. For more information, see Logging Options on page 109. Select Display server log in the server console window if you want the log information to appear in this window. The log information is recorded in the ROOT/wrapper.log le when the server runs as a Windows service. N OTE : For the SAS Digital Marketing clients to create reports that access the audit table, you must specify an explicit host in the JDBC connection denition. Therefore, do not specify a JDBC connection that has localhost as the value in the Connection Denitions dialog box.
12. Specify the settings to process e-mail replies and click Next. You must rst provide a POP3 or IMAP e-mail account and a JDBC provider to record the reply classication. After these values are set, you can congure the server to periodically download the replies and classify them.
To congure the e-mail reply account, click Congure Reply Manager. For the SAS Digital Marketing clients to create reports that accesses the reply table, you must specify an explicit host in the JDBC connection denition. Therefore, do not specify localhost as the Universal Resource Identier (URI). For more information, see E-mail Reply Options on page 101. N OTE : Support for IMAP is experimental for this release.
13. Specify the users that can access SAS Digital Marketing and the proxy settings for your site and then click Next.
To specify the users that can access SAS Digital Marketing, select Basic from the Security Mode drop-down list. Click Add, Edit, or Remove to create or modify the credentials that authenticates a user or a group of users. To use a metadata server that centralizes the management of user credentials, select metadata from the Security Mode drop-down list. SAS Digital Marketing uses the metadata repository to 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 SAS Digital Marketing administrator. For more information, see Security Options on page 128. N OTE : When you use a metadata server for user authentication, SAS Digital Marketing grants all users Level 3 permission. This level means you cannot stop or congure the SAS Digital Marketing server. To use ASP broadcasts, you must use an Internet proxy and specify the values for the proxy and port.
14. Specify whether to use the TinyMCE HTML editor in SAS Digital Marketing Web Studio and select Next.
If you want to edit the HTML content for a broadcast using the TinyMCE Web-based Javascript editor, then select Download and install TinyMC third party software. Use the URL drop-down list to select the location of the installation le. Click Browse to locate the le in another directory. To use TinyMCE as the HTML content editor in SAS Digital Marketing Studio, you must also set the WebAppURL server property. For more information, see Integration Utils Server Properties on page 141. N OTE : To download the software, you might need to congure the SAS Digital Marketing server to use an Internet proxy. Use the previous step to select Use an Internet proxy and specify your proxy and port settings.
15. Specify the settings to spawn threads and click Next. By default, the broadcast execution runs in multiple threads for efciency.
You can optimize the e-mail broadcast execution by specifying the number of threads. You can also specify the number of asynchronous threads that SAS Digital Marketing uses to deliver spooled SMTP messages to an e-mail server. For more information, see Adjusting the SMTP Spooler on page 263.
SAS Digital Marketing updates the WAR les for the middle tier. These les are located in ROOT/mid directory. You deploy the updated WAR les on a Web application server. For more information, see The post-conguration checklist provides a list of steps on how to deploy the WAR les and validate your settings. To create a paper copy of the instructions, select Print Check list. For information about creating a sample broadcast to test the server conguration, see Validating Your Conguration on page 93. To create a service under the Windows environment that automatically starts the SAS Digital Marketing server when your computer starts, select Register SAS Digital Marketing as a Windows Service.
2. Click upload your le(s) in the Deploy a Web application Module pane.
3. Click Browse to locate the bess.war le that you congured with the Server or Servlet Conguration wizard. Then click Upload.
4. Navigate to the uploaded bess.war le, select it, and click Target Module.
WebLogic deploys the WAR le that contains the servlets. Now, test that the Java servlets have started. For more 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 le:
grant codeBase "file:${catalina.home}/webapps/sdm/-" {permission java.security.AllPermission;}; grant codeBase "file:${catalina.home}/webapps/bess/-" {permission java.security.AllPermission;};
2. Click Next in the Preparing for the application installation pane to use the default values.
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 use defaults_host for Step 2.
6. Select SAS Digital Marketing Tracking Servlets check box, specify the Web application server for the middle tier and click Apply. Click Next to use defaults_host for Step 3.
9. Click Save.
10. To start the Java servlets, expand the Applications node in the Administrative Console and select 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 on page 68.
N OTE : When a servlet does not start, stop and restart the Web application server, and then restart the servlet.
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. N OTE : Your database vendor might require that you specify both a database name and table name, such as Test.Responses. If the database name is omitted for some versions of MySQL, then you receive a No database specified error. Specify the identication number in the ClientID box. SAS Digital Marketing writes a record to the specied response table. The record contains the identication number. Click Test Crumblet Servlet to run the servlet and to create a 1x1 GIF image similar to the image that SAS Digital Marketing embeds in the e-mail content.
2. 3.
N OTE : View events are not tracked for users of AOL 5.0. Therefore, the crumb servlet is not used. 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 successfully invoked. Likewise, the response table is created on the JDBC connection that you specied in the Servlet Conguration wizard. This table should contain a row that includes the ClientID and a preview click event (pclick) as the broadcast response. If JMS is congured, then JMS listeners also receive a pview event that embeds the ClientID as a property. For more information, 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 Target URL box. For example, to use the SAS Web page as your target URL, specify http://www.sas.com. Specify the name of the table for broadcast events in the Table box. N OTE : Your database vendor might require that you specify both a database name and table name, such as Test.Responses. If the database name is omitted for some versions of MySQL, then you receive a No database specified error. Specify the identication number in the ClientID box. SAS Digital Marketing writes a record that contains the identication number to the specied response table. Click Test Redirect Servlet to run the servlet.
2.
3. 4.
When the test is successful, the Web page for the target URL displays. Likewise, the response table is created on the JDBC connection that you specied in the Servlet Conguration wizard. This table contains a row that includes a link to the target URL, the ClientID value, and a pview event as the broadcast response. If JMS is congured, then JMS listeners receive a pclick event that embeds the target URL link and the ClientID as the properties. For more information, see Types of Response Events (Chapter 7, SAS Digital Marketing: Users Guide). To view the response table, use the JDBC Table Viewer that is included in the SAS Digital Marketing. For more information, see Using the JDBC Table Viewer (Chapter 2, SAS Digital Marketing: Users Guide).
5. Click Update to congure the server. When you receive the message that the middle tier is successfully updated on the server, click Close. To verify that SAS Digital Marketing server is correctly updated, use the Server Conguration window. For more information, see Middle Tier Options on page 125.
3. Specify the JDBC connection information for the SAS/SHARE server, SAS Workspace Server, or the third-party database server that SAS Digital Marketing uses to collect response data 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. Select Turn on servlet debug mode to write debug messages to the Web server log. Debug information is written to the log when a recipient opens e-mail that contains a crumb or when a recipient clicks a link that is tracked. This option also enables you to access an exception log from the Tracking Servlets Test page. For more information, see Verify the Tracking Servlets on page 68.
4. Specify the link table to track the response to 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 a different table connection, then use the Connections drop-down list to select the connection denition. Tracked links in text content can become quite large. Unlike with HTML content, the recipient sees the actual link in the text content. When a tracked link is embedded in the broadcast content, SAS Digital Marketing adds the URL to the link table and generates an index. SAS Digital Marketing uses the index to shorten the tracked URLs in the text content that a recipient receives. The table that contains the links must always be available so that the URLs are found when a recipient clicks the links. N OTE : 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 the location 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 rewall so that it is available to your email recipients. This Web page also displays when the link table is inaccessible and the e-mail recipient 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 excluded from receiving e-mail transmissions 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 a different table connection, then use the Connections drop-down list to select the connection denition. If the Automatically apply opt-out table during send processing option is set and SAS Digital Marketing records an address in the opt-out table, then no broadcast e-mails are sent to this address. SAS Digital Marketing records e-mail addresses in the opt-out table when you use the Insert HTML opt-out link and Insert TEXT opt-out link options in the Insert other expressions dialog box. The opt-out servlet is embedded in the broadcast message. Addresses are also recorded in the opt-out table when you set a Reply Manager rule threshold. For more information, see Response Tracking (Chapter 7, SAS Digital Marketing: Users Guide). Select Redirect to custom opt-out notication page to specify the location of a Web page that opens when an e-mail recipient decides to opt-out of an e-mail broadcast. The Web page should include a message that you are processing the request to remove the recipient from the mailing list.
6. Specify the location of the third-party database JDBC JAR les. SAS Digital Marketing uses the JAR les to connect to your database server in order to write response records. Also specify the location of any third-party JMS JAR les that SAS Digital Marketing needs to connect to a JMS provider. Then click Next.
SAS Digital Marketing can use a database from another vendor, such as MySQL, to track replies and responses from a broadcast. If the audit table, response table, or reply table use databases 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 database from Java. For example, DB2 requires the db2jcc.jar le. To connect to the server with the data table, specify the location of the JAR le that provides the JDBC connectivity. SAS Digital Marketing can use JMS to process responses in real time. JMS might need a third-party JAR le to connect to the JMS Queue or to the JMS Topic that you post broadcast events to. For example, if you use JMS with WebLogic as a JMS provider, then the wljmsclient.jar le is required when you deploy other Web application servers. For more information, see Overview of JMS on page 269.
To include JARs in the WAR le that contains the servlets, complete the following steps: a) Click Add JAR. b) For each database, specify the location of the JAR le in the Open window. c) Click OK. To delete a JAR le, select the le 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 HTTP connections are limited between the SAS Digital Marketing server and the Web application server outside your corporate rewall. SAS Digital Marketing uses a proxy server inside your rewall to process the requests that are received from the Java servlets.
To include an HTTP proxy in the WAR le, 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 and click Remove. N OTE : To use HTTP proxy settings, you deploy two versions of the WAR le. This conguration of the WAR le is deployed outside the corporate rewall. For more information, see Conguring a Proxy Server on page 79. 8. Decide whether you want to use JMS for real-time broadcasts and specify the JMS conguration. Then click Next.
9. Specify the location to store the updated bess.war le and click Finish.
You are now ready to deploy the WAR le that contains the servlets to your Web application server on the middle tier. For more information, see Deploying the Servlet WAR File on page 54 and Updating the Server on page 70.
4. In SAS Digital Marketing Studio, use the Servlet Conguration wizard to recongure the WAR le that contains the servlets to use HTTP proxy settings. Select Servlet Conguration from the Tools menu. Except for the HTTP proxy settings, click Next to use the exact settings of the WAR le that you deployed on the Web application server inside your corporate rewall.
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 is the URL address for the tracking and Web publication tier that you deployed on a Web application server inside your corporate rewall. c) Click OK. For more information, see Run the Servlet Conguration wizard on page 71. 5. After you nish the steps of the Servlet Conguration wizard, deploy the WAR le that contains the servlets to a Web application server that is located outside your corporate rewall.
6. Open the proxy servers Web application port between the tracking deployments that are inside and outside your corporate rewall. 7. In SAS Digital Marketing Studio, open the Server Conguration window by selecting Server Conguration from the Tools menu. Select Middle Tier Options, and specify the base URL for the tracking deployment that is located outside your corporate rewall. To verify that the tracking servlets work correctly, click Test.
8. Verify that your hosted Web resources and broadcast denitions access content on the middle tier. Use the Web tab on the Properties dialog box for a broadcast denition or hosted Web resource. 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 le 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 received the HTTP request from the middle tier.
For more information, see Viewing the Web Resources (Chapter 2, SAS Digital Marketing: Users Guide).
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 congure the server. 6. After you receive the message that SAS Digital Marketing server is successfully updated, click Close.
In this example, SAS Digital Marketing checks the le for valid addresses as the le is uploaded to a temporary table with a base name of tablebase. The table is stored in the database that is dened by these server properties. For more information, see Properties for Executing from a File on page 143.
In this example, the scheduling functionality in SAS Digital Marketing Web Studio displays the list of tables in the library specied in the WebSelectionTableLibrary server property. You can then select the table that contains the list of broadcast recipients. For more information, see Properties for Executing from a Table on page 143.
The following software is required to use the SAS language adapter: Foundation SAS 9.1.3 SP4 on any supported platform a SAS Digital Marketing server SAS Digital Marketing Web Studio IOM workspace server (optional) Internet Explorer 6, Internet Explorer 7, or Mozilla Firefox N OTE : To generate SAS reports in an Asian language, install Foundation SAS to use UTF-8 encoding 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 IOM workspace server is recommended if your site has more than ve users generating reports simultaneously. If you choose to use the workspace server, then this server must be running. For information about how to congure the IOM workspace server, see the SAS 9.1.3 Integration Technologies Administrators Guide at http://support.sas.com/rnd/ itech/doc9/admin_oma/sasserver/iombridge/iom_quicko.html. For an example of a conguration le, 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 optimize the performance of your IOM sessions or batch sessions. For information about these properties, see Optimize Server Properties on page 144.
5. Click Test SAS Connection to verify that the SAS connection works. N OTE : If you have registered SAS Digital Marketing as a Windows service and your SAS connection fails, then you might have to modify the properties of the service to specify the account and password that run the service. For more information, see Congure a Windows Service on page 95. 6. Select the Execute batch jobs periodically check box if you want to run the SAS job at a regular 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 HTML output. Use Graph Device to specify the graphical output format. N OTE : If Java is selected as the graph device, then make sure that you apply the patches from SAS Notes SN-V9-017502 and SN-V9-017593 to Foundation SAS. For more information, see http://support.sas.com/techsup/search/sasnotes.html. N OTE : Depending on the graph device that you select, SAS Digital Marketing Web Studio users 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 Digital Marketing: Web Studio Users Guide). 8. Click OK. You manage your SAS jobs from the SAS Job Editor. For more information, see Developing SAS Code on page 195.
5. Select Link and click Create from the Create New Content page.
6. Create the link that displays the broadcast groups and broadcast denitions. You must specify a 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 deployedhost is the location of server that is running the SAS Digital Marketing Web Studio deployment. For more information, see Conguring SAS Digital Marketing Web Studio on page 83. server is the location of the SAS Digital Marketing server that you use to store the broadcasts denitions. user and password are the user credentials to log on to the SAS Digital Marketing server. Use the Level 1 user account that you created.
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 home page. Then specify the link name in the Keywords box, select Link in the Content Types box, and click Search to display the link.
10. Log on to SAS Information Delivery Portal to open your personal portal. The link is now available in the Bookmarks list.
11. Click SAS Digital Marketing Reports to use Web Studio to create broadcast reports. For more information, see Monitoring Broadcasts in Web Studio (Chapter 2, SAS Digital Marketing: Web Studio Users Guide).
2. Select Create Sample Table from the Tools menu. The Create Sample Table dialog box opens.
3. Use the drop-down list to select the JDBC connection. If you want to use a different table connection, then use the Connections drop-down list to select the connection denition. 4. Select the location of the library, and enter the table name in the Table box. N OTE : The examples in the documentation use the EXAMPLES library for the location of the data tables. 5. Click OK. 6. If the data source table already exists, then conrm that you want to replace it. You can also create the sample data table by running the CONTACT_DETAILS.SAS program in the ROOT/samples directory. Modify the program to include a LIBNAME statement that uses examples as the libref. Then submit the program in a SAS session that runs on a SAS/SHARE server. For more information about how to start a SAS/SHARE server, see the SAS SHARE Users Guide.
To preview a sample broadcast denition, 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 Marketing: Users Guide). 2. Select the AML Report - January 2004 broadcast denition in the E-mail folder under the Broadcasts folder. 3. Select Preview from the Actions menu or right-click to select Preview from the pop-up menu. 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 in the data source table that SAS Digital Marketing uses to create e-mail messages, change the value 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 the e-mail address of the preview broadcast to verify that e-mail messages were received.
4. Register the batch les as a service. Run either the SEMInstallApp-NT.bat le or the SEMGridNodeInstallApp-NT.bat le. 5. Restart your computer to start the service. N OTE : To unregister the service, run either the SEMUnInstallApp-NT.bat le or the SEMGrideNodeUninstallApp-NT.bat le. The SAS Digital Marketing server or grid node will no longer start when the computer initializes. For more information about troubleshooting problems, see the Java Service Wrapper documentation at http://wrapper.tanukisoftware.org/doc/english/index.html.
Chapter 4
Throttled Domain Manager . . . . . . . . . . . . . . . About the Throttled Domain Manager . . . . . . Conguring Throttled Domains . . . . . . . . . Scheduling Options . . . . . . . . . . . . . . . . . . . About Scheduling Options . . . . . . . . . . . . Conguring the Broadcast Scheduler . . . . . . Using a Notication List . . . . . . . . . . . . . WAP Integration Options . . . . . . . . . . . . . . . . About WAP Integration Options . . . . . . . . . Conguring the WAP Integration . . . . . . . . Web Services . . . . . . . . . . . . . . . . . . . . . . About Web Services Specications . . . . . . . Conguring Web Services Specications . . . . Contact History Options . . . . . . . . . . . . . . . . About Contact History Options . . . . . . . . . Conguring Contact History . . . . . . . . . . . Response History Options . . . . . . . . . . . . . . . About Response History Options . . . . . . . . Conguring Response History . . . . . . . . . . Connection Options . . . . . . . . . . . . . . . . . . . About Connection Options . . . . . . . . . . . . Conguring the Connections . . . . . . . . . . . Middle Tier Options . . . . . . . . . . . . . . . . . . About Middle Tier Options . . . . . . . . . . . Conguring the Middle Tier . . . . . . . . . . . Advanced Server Properties . . . . . . . . . . . . . . About Advanced Server Properties . . . . . . . Conguring the Advanced Server Properties . . Viewing the Advanced Server Properties Settings Security Options . . . . . . . . . . . . . . . . . . . . About Security Options . . . . . . . . . . . . . Types of Security . . . . . . . . . . . . . . . . . Basic Security Mode . . . . . . . . . . . . . . . Metadata Security Mode . . . . . . . . . . . . . User Group Settings . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
116 116 117 117 117 118 118 119 119 119 120 120 120 121 121 122 122 122 123 124 124 124 125 125 125 126 126 126 127 128 128 128 129 131 132
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
Conguring JMS
To congure the SAS Digital Marketing server to use JMS, select the check box and specify the JMS provider settings. For more information, see Conguring a JMS Provider on page 269 and Using the JMS Provider on page 281.
SAS Options
Conguring SAS
Use the Integrated Execution Context drop-down list to select how you want to run the SAS jobs from SAS Digital Marketing. To verify that you have entered this information correctly and that the SAS 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 executable in SAS Command Line box. When you install Foundation SAS and SAS Digital Marketing on the same server, the default location of the Foundation SAS installation automatically appears in the SAS Command Line box. If you run the SAS jobs on the IOM workspace server, then select Workspace Server and specify the name of the workspace server. You must also specify your username and password for that server. An IOM workspace server is recommended if your site has more than ve users that generate reports simultaneously. If you use the IOM workspace server, then this server must be running. N OTE : To generate SAS reports in multiple languages, install Foundation SAS to use UTF-8 encoding. 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 regular interval. 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 species the style of the HTML output. Graph Device species the graphical output format to use for any graphs that appear in the output. 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 the SAS/GRAPH control for ActiveX. To install the ActiveX drive, use the support.sas.com Web site to 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 from SAS Notes SN-V9-017502 and SN-V9-017593 to Foundation SAS. For more information, see http://support.sas.com/techsup/search/sasnotes.html.
E-mail Options
Select Identify preview messages in the subject line to add a prex to the e-mail subject line. The prex includes the word PREVIEW, the message number, and content type in the e-mail subject line. Select Prevent duplicate e-mails per broadcast to lter out all duplicate e-mail addresses when you send a broadcast transmission. You must select all for the e-mail audit level and select Write audit records to a JDBC table on the Logging tab. SAS Digital Marketing records when a recipient is sent e-mail and examines the audit table before e-mail is sent from another recipient table. If you re-execute a broadcast and use the same recipient table, then SAS Digital Marketing does not send a duplicate e-mail. N OTE : If you select the Prevent duplicate e-mails per broadcast option, then SAS Digital Marketing sends only one broadcast per e-mail address. Therefore, transaction broadcasts work 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 Users Guide).
Logging Options
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 Marketing automatically 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. N OTE : 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 denition. Therefore, do not specify a JDBC connection that has localhost as the Universal Resource Identier (URI).
Send Options
out table when you use the Insert HTML opt-out link and Insert TEXT opt-out link options in 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. For more information, see Response Tracking (Chapter 7, SAS Digital Marketing: Users Guide). For non-Asian languages, use 8-bit as the value for Default mime transfer encoding. Some Asian languages 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 Users Guide).
General Options
Use the General tab to enter the name of your server and the port that the e-mail server uses on that host. If the server is congured to require authentication, then select Server Requires Authentication and enter the user credentials.
Advanced Options
Use the Advanced tab to select the SMTP driver from the SMTP Provider drop-down list. You can congure SAS Digital Marketing to use a third-party JavaMail driver such as the PowerMTA driver, or you can specify another third-party driver. You can also click Add to specify property and value 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 transmission between the e-mail servers. By default, preview broadcasts are sent to the same server as the broadcasts that are currently executing. To improve performance, your site administrator can use the PreviewSMTPServer server property 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.
Performance Options
Scheduling Options
Web Services
To view the Response History options, select Tools!Server Conguration!Response history Options.
Connection Options
descending order, then a server property that starts with a lowercase character appears at the top of the 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 congure a server property, assign a value to the Value column and select the check box in the Set column. If you decide not to use a server property, then delete the entry from the Value column. For a complete description of each server property, see Overview of Advanced Server Properties on page 133. N OTE : You can also use the ebtool command to set the server properties in batch mode. For more information, Using Batch Mode (Chapter 2, SAS Digital Marketing: Users Guide).
Security Options
Types of Security
SAS Digital Marketing provides different levels of functionality-based security modes and the user credentials. The following types of security modes are available: None does not require user credentials to log on to the server. All users have administrative privileges. Basic requires user credentials to log on to the server. SAS Digital Marketing authenticates each user. Metadata requires user credentials to log on to the server. A metadata server authenticates each user.
The following levels of user authorization are available: Level 1 can view broadcasts, Web resources, or RSS content, preview broadcasts, and run broadcast reports but cannot create or modify broadcasts, resources or feeds, send broadcasts, or stop the server. 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. can create or modify broadcasts, Web resources, or RSS content, preview broadcasts, run broadcast reports, and send or stop broadcasts transmissions, but cannot create RSS feeds or stop the server. can create, view, preview, and send or stop broadcast transmissions as well as stop, pause, and resume the server. This user can congure the server, the Java servlets, security for distribution lists, groups, and RSS feeds, the Reply Manager, or the JDBC connections and create or modify global data models, SAS reports about the broadcasts, or RSS feeds.
Level 2
Level 3
Level 4
N OTE : When you use a metadata server to authenticate user credentials, SAS Digital Marketing grants Level 3 permission to all users except the software administrator.
SAS Digital Marketing automatically provides a default user ID for each user authorization level. The following users are provided: User ID guest writer runner admin Password guest1 writer1 runner1 admin1 Authorization Level 1 Level 2 Level 3 Level 4
You can use the Groups tab to create and manager user groups. N OTE : 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 - Dening 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.
3. Select authorization level from the drop-down list. 4. Click OK to store the changes.
To remove obsolete users, select the user name from the Users tab in the Authentication box and click Remove. Then click Yes to conrm that you want to remove this user from the list. N OTE : When you are not a Level 4 user, select Change Password from the Tools menu to change your password. For more information, see Change Your Password (Chapter 2, SAS Digital Marketing: Users Guide).
You must specify the location of the metadata server and the user credentials for the SAS Digital Marketing software administrator. Unlike with the basic security mode, you do not have to specify a different user ID and password for the user credentials. Using the metadata server authentication forces the SAS Digital Marketing Server user credentials to match your operating environment credentials. N OTE : When you use a metadata server to authenticate user credentials, SAS Digital Marketing grants Level 3 permission to all users except the software administrator.
To add or delete group members, select the user ID or group user name and click . Then click OK to save the new user group settings.
or
N OTE : : If the metadata security mode is used, then you must rst enter the user ID to add it to the user group.
Chapter 5
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 more information, see Using Batch Mode (Chapter 2, SAS Digital Marketing: Users Guide).
By default, this property is not set, and the user can select the variable to use as the e-mail address variable. For information about how to use server properties to create a global data model for incoming recipient lists and for tracking data, see Managing Global Data Models on page 166. EmailTrackedVariables species the tracking variables to use for an e-mail broadcast. The tracking variable should contain unique information, such as a customer ID number, so that SAS Digital Marketing can 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 following changes to the user interface: In SAS Digital Marketing Studio, the user cannot change the variable that is selected in the Tracking Variables box in the Tracking panel of the New Broadcast wizard. In SAS Digital Marketing Web Studio, the Tracked Variables eld is not displayed on the New Broadcast page. By default, this property is not set, and the user can select the variables to track. N OTE : If you specify both the EmailTrackedVariables and the ResponseTableBase properties and the variable that you specied for the EmailTrackedVariables property exists in your data source, then in SAS Digital Marketing Studio the Tracking panel does not appear in the New Broadcast wizard or in the New Broadcast Content wizard. For information about how to use server properties to create a global data model for incoming recipient lists and for tracking data, see Managing Global Data Models on page 166. EmailVariables species the variables that are in the recipient table. The variables should contain the e-mail addresses for the recipients, unique tracking information (such as customer ID), or other information that you might use to customize your broadcast content. To specify the e-mail variables to use, specify values as a comma-separated list. When this property is set, the user cannot change these variables because of the following changes to the user interface: In SAS Digital Marketing Studio, the Data Model panel of the New Broadcast wizard is not available, so end users cannot select the data source for the broadcast. In SAS Digital Marketing Web Studio, the Broadcast Variables eld is not available from the New Broadcast page. By default, this property is not set, and the user can select the variables to use. For information about how to use server properties to create a global data model for incoming recipient lists and for tracking data, see Managing Global Data Models on page 166. HideSASPredenedLibraries species whether to show the GISMAPS, MAPS, SASHELP, and SASUSER libraries when the user can select a data source. Users can select a data source from the List Structure panel of the New Broadcast wizard, the Preview Broadcast wizard, or the Schedule Broadcast wizard in SAS Digital Marketing Studio.
By default, this property is set to true, and these libraries are not available from the wizards. As a result the user must specify a full two-level name (for example, EXAMPLES.CONTACT_DETAILS) when selecting a data source. The site administrator can still access these predened libraries from the SAS JDBC Explorer window. HideTables displays in SAS Digital Marketing Studio a predened set of tables that the administrator has set up as distribution lists. If this property is set to true, then users at your site can use distribution lists only in the New Broadcast wizard, the Preview Broadcast wizard, and the Schedule Broadcast wizard to select a data source table. LockSentBroadcasts species whether to lock broadcasts that have been previously sent or broadcasts that are scheduled for execution. If this property is set to true, then the SAS Digital Marketing Studio user cannot edit the broadcast. This broadcast can be opened in read-only mode. When this property 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 that has been sent or one that is scheduled for execution, then the pop-up menu that appears does not contain the Delete, Dene New Content, or Edit options. Instead, this pop-up menu has a View option that the user can select to view the broadcast content. A dialog box also opens telling the user that the broadcast has already been sent or is scheduled and that any edits are not saved. N OTE : If a broadcast is selected in the main window when you change the LockSentBroadcasts property, then you must select the broadcast again for the options in the pop-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 broadcast content, but when the user closes the content editor a message appears stating that the content is not saved. In the SAS Digital Marketing Web Studio, the Edit options are not available for broadcasts that have been executed. SaveLastURLPassword species whether to save the last password in the URL userid/password dialog box in SAS Digital Marketing Studio. By default, this property is set to false. ShowCustomizeContentMenuItems species whether to show in SAS Digital Marketing Web Studio the View Customized HTML and View Customized Text menu items for a broadcast that contains HTML or text content. By default, this property is set to false. ShowRecipientTable species whether SAS Digital Marketing Web Studio displays information about the recipient table when a broadcast is scheduled. If a database table is used, then SAS Digital Marketing displays a Web page with the name of the table and the number of recipients. You click the table name to display the contents of the table. The ShowRecipientTableRowCount server property determines the number of rows that are displayed. If a distribution list is used, then SAS Digital Marketing displays a Web page with the name of the distribution list and the number of recipients. By default, this property is set to false.
ShowRecipientTableRowCount species the number of rows in the recipient table to display when SAS Digital Marketing Web Studio is used to schedule a broadcast and ShowRecipientTable is set to true. By default, this property is set to 10. TrackedVariableWarningThreshold species the number of tracked variables that you can select from the data source table before SAS Digital Marketing displays a warning message. You should limit the number of tracked variables 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. UseFileDialog species whether the Browse buttons in SAS Digital Marketing Studio should use AWT FileDialog selection or Swing JFileChooser. If this property is set to true, then the AWT FileDialog selection is used. By default, this property is set to false and the Swing JFileChooser is used. UserSourcePanel species whether to display in SAS Digital Marketing Studio the User Input selection in the List Structure step of the New Broadcast wizard. By default, this property is set to false.
DisableAttachments species whether attachments are allowed in e-mail campaigns. When you set this property to true, 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 Digital Marketing: Users Guide). By default, this property is set to false. DreamweaverSnippetDir species 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 specied in the HTML Edit Command box of the Preferences dialog box. You need to specify this server property only if the default location is not in this location. By default, this property is not set. EditColorCoding controls whether the text for HTML, text, or AOL Rich Text source that appears in the content editor 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 to true. HTMLEditorCommand species the third-party HTML editor to use in SAS Digital Marketing Studio. The default HTML editor is Microsoft Ofce FrontPage. The site administrator can change this default value. SAS Digital Marketing Studio users can override the default value from the Preferences dialog box. For more information, see Setting the Preferences (Chapter 2, SAS Digital Marketing: Users Guide). StaticEmailSupported species whether SAS Digital Marketing clients provide the ability to create static e-mail broadcasts. A static e-mail broadcast delivers identical content to each recipient in the data source table. SAS Digital Marketing does not track responses or replies for a static e-mail broadcast. Static broadcasts do not require modications to the default conguration and require only an MTA for e-mail delivery. By default, this property is set to false. SuspendStudioWhileEditing species whether to close the content editor in the SAS Digital Marketing Studio when you open an external editor. If you set this option to true, then the user cannot have both the content 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 external 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 simultaneously view the changes in the content editor. For an example of how this works, see Editing Content in Dreamweaver (Chapter 5, SAS Digital Marketing: Users Guide). TextEditorCommand species the third-party text editor to use in SAS Digital Marketing Studio. The default text editor is NotePad. The site administrator can change this default value. SAS Digital Marketing Studio users can override the default value from the Preferences dialog box. For more information, see Setting the Preferences (Chapter 2, SAS Digital Marketing: Users Guide).
For more information about how to use the SpamScanClass and SpamAssassin Command server properties, see Using the SpamAssasin Spam Filter on page 181. SpamScanClass species the class that has implemented the scanMessage static method. A ScanMessage implementation ships in com.sas.email.server.BulkEmailUtils. To use SpamAssassin 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 SpamAssassin. For more information about how to use the SpamScanClass and SpamAssassin Command server properties, see Using the SpamAssasin Spam Filter on page 181.
WebAppURL species the URL for the Web application server that is running SAS Digital Marketing Web Studio. You must specify this property before you use the visualreport options with the ebtool command. You must also set this option to export a Web resource from the Web Resource Manager or import a Web resource into a broadcast. N OTE : You do not need to specify this server property to deploy SAS Digital Marketing Web Studio. The Congure SAS Digital Marketing Server for Web Reporting page automatically updates the SAS Digital Marketing server to use the URL for the deployment of the Web application. 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 this report for individual broadcast denitions. This option is also available from the popup menu for a broadcast denition 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 page opens in SAS Digital Marketing Web Studio. The user can select the SAS report to run. The SAS reports are created by the site administrator. For more information, see Viewing SAS Reports (Chapter 4, SAS Digital Marketing: Users Guide). The Run Visual Report option is available from the Actions menu. You can run a visual report for an individual broadcast denition. This option is also available from the pop-up menu for a broadcast denition in SAS Digital Marketing Studio. When the SAS Digital Marketing user runs a visual report, the visual report for that broadcast opens in a new Internet Explorer window. The reports content is based on the parameters that the administrator species. When you specify the WebAppURL server property, you can use the TinyMCD Web-based Javascript editor as the HTML content editor in SAS Digital Marketing Studio. To edit a broadcast 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. N OTE : You can download and install TinyMCE when you specify whether to use an external HTML editor from the SAS Digital Marketing Server Conguration wizard. For more information, see Run the Server Conguration Wizard on page 39. The syntax for the value that you specify is the following:
http://deployedhost:port/sdm/
invalid. When this threshold is exceeded in SAS Digital Marketing Web Studio, then the upload of the le 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.
When you specify these options, you can choose from the Schedule Broadcast wizard in SAS Digital Marketing Web Studio a table that contains the addresses of the recipients of the broadcast.
MaximumIOMWait species the maximum time (in seconds) to wait for an available SAS workspace session before returning a "Server is too busy" message. By default, this property is set to 150 seconds or 2.5 minutes.
CustomSocketFactory indicates that you want to specify a custom socket for RMI operations. By default, this property is set to false. SocketEnd species the port number of the end socket. SocketStart species the port number of the start socket. Unlike other server properties, you specify these properties as command line options of the Java invocation for each client, grid node, or controller. You can also set these properties on the CommandLineArgs statement in INI les in the ROOT directory in Windows environments or in shell scripts in UNIX environments. The following example shows how you specify these options:
-DCustomSockeyFactory=true -DSocketStart=20000 -DSocketEnd=21000
HTML content or text content, to send. If you preview an e-mail broadcast, then the subject line 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 PreviewConrmation property to true. If you do, then SAS Digital Marketing Studio displays a conrmation 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.
N OTE : If you also set the PossibleFrom property, then you must specify this default value as 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 specied for the DefaultFrom property in the From box. DefaultReplyTo species a default value for the Reply to box in the New Broadcast wizard. This value can be overwritten when you create a new broadcast. The syntax for the DefaultReplyTo property is the following:
DefaultReplyTo=user@sas.com
N OTE : If you also set the PossibleReplyTo property, then you must specify this default value as one of the values of the PossibleReplyTo property. If you do not set this property, then SAS Digital Marketing Studio does not display the default value that you specied for the DefaultReplyTo property in the Reply to box. DefaultSMSFrom species the default value in the From box in the New Broadcast wizard when you are creating an SMS broadcast. By default, this property is set to blank. DefaultSMTPFrom species a default value for the SMTP From box in the New Broadcast wizard. This value can be overwritten when you create a new broadcast. The syntax for the DefaultSMTPFrom property is the following:
DefaultSMTPFrom=user@sas.com
EmailFromOverride species a value for the SMTP Email From box in the New Broadcast wizard, the New Broadcast Content wizard, and the Header tab in the Properties dialog box. If you set this property, then the SMTP Email From box is not available in the user interface, so users cannot change this value. The SMTP Email From box enables you to track correlated replies. For more information, see Using Correlated Replies on page 232. InternalMessageFrom overrides the value of the From eld for internal messages. You can send internal mail by selecting the Mail menu option from the Actions menu in the Query Responses window, the Query Reply window, or the Summary window. You can also specify the e-mail notication list for internal messages from the Scheduling tab in the Server Conguration window. For more information, see Scheduling Options on page 117. By default, this server property is not set, and the value of the From eld is used. PossibleFromxxx species the list of values that appear in the From box in the New Broadcast wizard and in the Header tab of the Broadcast Properties dialog box. The value of xxx is the number of the e-mail address that you want to include in the list. For example, if you want John Smiths and Marcel Duprees e-mail addresses available from the From box, then you would specify the PossibleFrom property twice.
PossibleFrom1=john.smith@yourcompany.com PossibleFrom2=marcel.dupree@yourcompany.com
If you set this property, then only those e-mail addresses that you specied can be used in a 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 are ignored, so if you specied PossibleFrom1, PossibleFrom2, and PossibleFrom4, then the fourth value (and any subsequent values) is ignored. In the following example, the e-mail address specied for PossibleFrom4 does not appear in the From box because it is specied out of sequence.
PossibleFrom1=john.smith@yourcompany.com PossibleFrom2=marcel.dupree@yourcompany.com PossibleFrom4=susan.jones@yourcompany.com
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 in the list of possible values. The following examples show how SAS Digital Marketing Studio uses the values of the DefaultFrom and PossibleFrom properties to populate the From box. If the DefaultFrom property is blank and no value is specied for the PossibleFrom property, then the user can enter any value for the From box in the New Broadcast wizard or Header tab in the Broadcast Properties dialog box. If you specied a value for the DefaultFrom property but no values were specied for the PossibleFrom property, then the From box displays the value that you specied for the DefaultFrom property. If you specied a value for the DefaultFrom property and you specied a value for the PossibleFrom property but none of the possible values match the value of the DefaultFrom property, then the only values that are available from the From box are the PossibleFrom values. The rst value in the list is the default. In the following example, only Marcel Duprees e-mail address is available from the From box.
DefaultFrom=john.smith@yourcompany.com PossibleFrom1=marcel.dupree@yourcompany.com
If you specied a value for the DefaultFrom property and you specied values for the PossibleFrom 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 the default. In the following example, both John Smith and Marcel Duprees e-mail addresses are available from the From box.
DefaultFromTo=john.smith@yourcompany.com PossibleFromTo1=marcel.dupree@yourcompany.com PossibleFromTo2=john.smith@yourcompany.com
PossibleReplyToxxx species the list of values that appear in the Reply to box in the New Broadcast wizard and in the Header tab of the Broadcast Properties dialog box. The value of xxx is the number of the e-mail address that you want to include in the list. For example, if you want John Smith and Marcel Duprees e-mail addresses to be available from the Reply to box, then you would specify the PossibleReplyTo property twice.
PossibleReplyTo1=john.smith@yourcompany.com PossibleReplyTo2=marcel.dupree@yourcompany.com
If you set this property, then only those e-mail addresses that you specied can be used in a 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 are ignored, so if you specied PossibleReplyTo1, PossibleReplyTo2, and PossibleReplyTo4, then the fourth value (and any subsequent values) is ignored. In the following example, the e-mail address specied for PossibleReplyTo4 does not appear in the Reply to box because it is specied out of sequence.
PossibleFrom1=john.smith@yourcompany.com PossibleFrom2=marcel.dupree@yourcompany.com PossibleFrom4=susan.jones@yourcompany.com
By default, the PossibleFrom property is set to blank. If you also set the DefaultReplyTo property, then you must specify the same default e-mail address using the PossibleReplyTo property to display the default e-mail address from the Reply To drop-down list in the New Broadcast wizard. The following examples show how SAS Digital Marketing Studio uses the values of the DefaultReplyTo and PossibleReplyTo properties to populate the Reply To drop-down list. If the DefaultReplyTo property is blank and no value is specied for the PossibleReplyTo property, then the user can enter any value for the Reply To box in the New Broadcast wizard or Header tab in the Broadcast Properties dialog box. If you specied a value for the DefaultReplyTo property but no values were specied for the PossibleReplyTo property, then the From eld displays the value for the DefaultReplyTo property. If you specied a value for the DefaultReplyTo property and you specied a value for the PossibleReplyTo property but none of these are the same as the DefaultReplyTo property, then the only values that are available from the Reply To drop-down list are the PossibleReplyTo values. The rst value in the list is the default.
DefaultReplyTo=john.smith@yourcompany.com PossibleReplyTo1=marcel.dupree@yourcompany.com
If you specied a value for the DefaultReplyTo property and you specied values for the PossibleReplyTo property and one of these values is the same as the DefaultReplyTo property, then the DefaultReplyTo value also appears in the Reply To drop-down list, and it is selected as the default.
DefaultReplyTo=john.smith@yourcompany.com PossibleReplyTo1=marcel.dupree@yourcompany.com PossibleReplyTo2=john.smith@yourcompany.com
ReplyFilterRegex enables 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 compiled with the java.util.regex.Pattern class. By default, this property is set to false, and SAS Digital Marketing Studio matches the text in the replies to the reply rule. If the text in the reply matches a rule, then the message is added to that reply category. If you want to specify regular expressions for the reply rules, then set this option to true. Using regular expressions for ltering replies is slower but can provide greater exibility for categorizing replies.
Links that you select to omit are not selected for tracking in the New Broadcast wizard and New Broadcast Content wizard. You must specify these properties in sequential order. If you skip a number, then only the links that are specied in sequential order are omitted. If you specied LinkToOmit1, LinkToOmit2, and LinkToOmit4, then the fourth value (and any subsequent values) is ignored. In the following example, the link specied for LinkToOmit4 is not omitted because it is specied out of sequence.
LinkToOmit1=http://www.sas.com LinkToOmit2=http://www.yourcompany.com LinkToOmit4=http://www.yourdomain.com
By default, all links that appear in the HTML, text, and AOL Rich Text are selected for tracking. MaxResponseTables species the maximum number of response tables to generate if the ResponseTableBase property is set to true. By default, this property is set to 1000.
NegativeLinkxxx species a list of links to treat as negative response events when a recipient clicks any of these links. The value of xxx is the number of the link. You must specify these properties in sequential order. For example, if you want to two links to be negative response events, then you would specify the NegativeLink property twice.
NegativeLink1=http://www.sas.com/apps/jmp/email_preference.jsp NegativeLink2=http://www.sas.com/apps/userid/email_preference.jsp
These links are not selected for tracking in the New Broadcast wizard and New Broadcast Content wizard. ReplySummary species whether to include in the default summary report information about the types of replies that were received from the e-mail broadcast. Setting this property to true might increase the time it takes to generate a broadcast summary. By default, this property is set to false. ReplySummaryPeriod species the number of days to look back in the reply table for determining implicitly correlated replies. The period starts from the time and date that you run the reply summary. By default, this property is set to seven days. If you use the default and ran the reply summary at 9:00am on August 18, then SAS Digital Marketing would look back in the reply table through 9:00am on August 11. If you set this property to 0, then SAS Digital Marketing does not include implicitly correlated replies in the reply summary. N OTE : To use this property, you must also set the ReplySummary property to true. ResponseTableBase species the prex for the names of the response tables. The number of response tables is specied by the MaxResponseTables property. The ResponseTableBase property enables you to congure where to save the response tables. For example, you want to save all the response tables to the SDMDATA library and the prex for each table name should be RESPONSE. You set the ResponseTableBase property to SDMDATA.RESPONSE to automatically save the response tables to the SDMDATA library. As you execute the broadcasts, several tables named SDMDATA.RESPONSE_xxx are created in the SDMDATA library. After this property is set, the Response table box is not available from the New Broadcast wizard in SAS Digital Marketing Studio. The user also cannot modify the settings for the response tables. By default, this property is set to blank, and the user must specify a value for the response table in the New Broadcast wizard and the New Broadcast Content wizard. N OTE : If you specify both the EmailTrackedVariables and the ResponseTableBase properties and the variable that you specied for the EmailTrackedVariables property exists in your data source, then the Tracking panel does not appear in the New Broadcast wizard or the New Broadcast Content wizard. sem.testlink species the link to use when testing the redir tracking servlet. By default, this property is set to http://www.sas.com.
TrackMailToLinks species whether to track the e-mail addresses that are specied using mailto tags in the HTML content of a broadcast. The behavior of mailto tags can vary depending on the client that is displaying the broadcast. These tracked links are treated the same as other tracked links in SAS Digital Marketing Studio. These links appear in the Link Summary section of the Summary window. By default, this property is set to false. VarPassingOverride selects the Pass tracking variables to the target URLs check box in the New Broadcast wizard. The Pass tracking variables to the target URLs option determines whether tracked variables 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 denition in SAS Digital Marketing Studio cannot specify this option. This property enables the SAS Digital Marketing administrator to set this option globally for your site. By default, this property is not set and the user can choose whether to set the Pass tracking variables to the target URLs option for each broadcast denition.
ScheduleShowTableDesc species 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, this property is set to false. SchedulingInstalled determines whether the scheduling functionality is installed and congured. If this property is set to true, then the scheduling functionality is installed. If you use SAS Digital Marketing with SAS Marketing Automation, then any scheduling should be handled by SAS Marketing Automation. If another application such as SAS Marketing Automation is going to handle the scheduling, then you should set this option to false.
Part IV
Maintenance
Chapter 6
In the Response table base name box, enter the prex value to create a valid JDBC table name. SAS Digital Marketing automatically assigns the response table name when you create a new e-mail broadcast denition. Use the Channels box to specify whether the distribution list is for an e-mail or a phone channel. SAS Digital Marketing uses the channel to determine the distribution lists that are available in the New Broadcast wizard. Select E-mail to create a distribution list for e-mail and multichannel broadcasts. Select Phone for SMS and ASP broadcasts.
3. Specify the data source tables, also called data elements, for the distribution list and click Next. 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 to examine the structure of a table, select the table name and click Details. The Properties dialog box 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 a logical message group by selecting multiple data source tables. However, each table must use the 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 you want to change a setting, then click Back to return to the appropriate step in the wizard.
In the Address variable drop-down list, select the name of the variable in the table that contains e-mail addresses or wireless phone numbers. Use the Distribution List Variables box to select the variables that SAS Digital Marketing includes in the response table when you track the response to an e-mail broadcast.
To modify a distribution list, select the name of distribution list and click Edit. The Properties dialog box opens. A series of tabs enable you to view and change the properties for the distribution list.
General Tab
Use the General tab to change the name of the distribution list, the optional description, the prex for 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 identies the variable in the data table that contains e-mail addresses or wireless phone numbers. The Distribution List Variables box identies the variables that SAS Digital Marketing includes in the response table when you track the response to an e-mail broadcast.
Elements Tab
Use the Elements tab to change the data source table or to select additional data source tables. Each table is one element of the distribution list. When you have multiple data elements, each table must use 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. Select the JDBC data table that contains the recipient information and click OK. If you do not want to use 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 tab to 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 a broadcast denition that is created with the distribution list. For more information, see Managing Security on page 167.
Managing Security
About Security
SAS Digital Marketing enables you to congure a broadcast group, a distribution list, a Web resource group, or an RSS feed channel that grants read and write permission for an individual user or a group of users. You create user groups, that consolidate a group of users, on a SAS Digital Marketing server in order to simplify how permission is granted. For more information, see User Group 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 Properties from the pop-up menu. For a Web resource group, select a folder or a le in the Web Resources tab. Then select Properties from the pop-up menu. For an RSS feed, select an RSS feed channel in the RSS Feeds tab. Then select Properties from the pop-up menu. For a distribution list, select Distribution List Manager from the Broadcast Denition node in the Server Conguration 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 and click OK.
To select multiple users, press down the CTRL key and click the rows with the user name or user group.
4. To change the authorization, select the user name or user group from the list of users. Then use 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 Write row. 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 at least Level 2 permission. To change the authorization for individual users, complete the following steps: 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 and click Remove. You cannot remove the All Users group.
The available ASP broadcast types appear in the ASP Denitions list. SAS Digital Marketing provides the Clickatell SMS and Clickatell WAP broadcast types as examples of a third-party ASP. To use these ASP denitions, you must register with Clickatell and purchase credits at http://www.clickatell.com. SAS Digital Marketing also provides the NowSMS broadcast type to send mobile messages to the Now SMS/MMS gateway (NowSMS) when a GSM device or mobile phone is connected to a SAS Digital Marketing server. For more information, see http://www.nowsms.com. You can perform the following actions in the ASP Denition Manager window: Add creates a new ASP denition type. To add an ASP denition, click Add. The ASP Denition Properties dialog box opens. Edit displays or modies the properties of an existing ASP denition type. To view the properties of an ASP denition, select the name in the ASP Denitions list and click Edit. The ASP Denition Properties dialog box opens. Remove deletes an ASP denition type. To remove a denition, select the name from the ASP Denitions box and click Remove. Done closes the window.
General Tab
Use the General tab to create the name for the ASP denition and to provide information about the ASP specications.
You can specify the following items on the General tab: Name species the name for the ASP broadcast type. The New Broadcast wizard displays this name in the Broadcast Type drop-down list. Description species descriptive text about the ASP broadcast type. Format the text with HTML tags. The New Broadcast wizard displays the description after you select the broadcast type from the Broadcast Type drop-down list. URL species the Web address of the HTTP-to-SMS gateway. The Web address corresponds to an ASP specication on where to post the HTTP request. Response Decoder species the class name of the decoder that SAS Digital Marketing uses to interpret the HTTP response. 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 enter the following information: Name: Description:
NowSMS <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, see http://nowsms.com. <p><p>To use the NowSMS gateway you must have a GSM modem or a phone connected to your SAS Digital Marketing server.
URL:
http://serverlocation:8800/?
Response Decoder: AspResponseDecoder N OTE : (Optional) You can write a custom decoder to interpret the responses that are received from the ASP. Use the specications to determine the content of their responses. You can examine 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 request for access to the HTTP post interface. Administrative parameters usually occur one time in the ASP request and have a xed value such as user ID, password, and api ID. The New Broadcast wizard prompts you for the Administrative parameters and stores the values in the ASP broadcast denition.
You can perform the following actions on the Administrative tab: Add creates a new administrative parameter. To add a parameter, click Add. The Parameter Properties dialog box opens. Modify modies the properties of an existing administrative parameter. To change the properties, select the name of the parameter and click Modify. The Parameter Properties dialog box opens.
Remove deletes an administrative parameter. To remove a parameter, select the row with the name of the parameter and click Remove. To dene 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 is required by the ASP or is a password.
The value in the Name box corresponds to the name of the parameter that SAS Digital Marketing adds to the URL that gets posted to the ASPs HTTP interface. The value in the Label box is used by the New Broadcast wizard to describe the parameter. The value in the Default Value box is used by the New Broadcast wizard to automatically assign a default value for the parameter. You must dene the parameters that the ASP requires on either the Administrative Parameters tab or the Parameters tab and select the Parameter is required to use ASP check box. When the New Broadcast wizard prompts for the administrative parameters, you must specify the value of a required parameter; otherwise, the wizard does not move to the next step. Set a parameter as a password by selecting Parameter is used to specify a password. The New Broadcast wizard hides the password by displaying asterisks instead of the actual value. To use theNowSMS ASP to send SMS messages, you create the following two administrative parameters: Name: Label: Default Value: Name: Label: Default Value:
User User:
Password Password:
For both parameters, select Parameter is required to use ASP. For the password parameter, select Parameter is used to specify a password.
Parameters Tab
Use the Parameters tab to specify the remaining parameters that the ASP needs in order to deliver SMS, MMS, or WAP Push messages. The New Broadcast wizard prompts you for the ASP parameters and stores the values in the ASP broadcast denition.
You can perform the following actions on the Parameters tab: Add creates a new non-administrative parameter. To add a parameter, click Add. The Parameter Properties dialog box opens. Modify modies the properties of an existing parameter. To change the properties, select the name of the parameter and click Modify. The Parameter Properties dialog box opens. Remove deletes a non-administrative parameter. To remove a parameter, select the row with the name of the parameter and click Remove. To dene 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 is required by the ASP or is an address variable.
Every ASP SMS request to the HTTP post interface must include the recipient phone number and the message content that you want sent to the recipient. You must examine the API specications of 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 HTTP interface. When the New Broadcast wizard prompts for the non-administrative parameters, you must specify the value of a required parameter; otherwise, the wizard does not move to the next step. Select Parameter species a WAP URL to use the parameter in the New Broadcast wizard to create a WAP integration broadcast. Select Parameter is used to specify the recipient address variable to set the parameter that species the column with the recipient phone numbers. The New Broadcast wizard requires that at least one parameter contain the phone numbers. If you assign a default value, then use the variable in the data 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-administrative parameters: Name: Label: Default Value: Name: Label: Default Value:
Text Text: SMS message
For both parameters, select Parameter is required to use ASP. For the rst parameter, select Parameter is used to specify the recipient address variable.
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 successful transmission, without having to examine the API specications. SAS Digital Marketing provides one sample decoder, ClickatellDecoder.java. To use the ClickatellDecoder you must revise &user=user , &password=password , and &api=api to correspond to your Clickatell user ID, password, and api ID. Then you recompile the class. Your response decoder must meet the following specications: 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 take the 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)
N OTE : After the class is compiled, you must restart the SAS Digital Marketing server in order to use any changes to the response decoder program.
4. Select Parameter species a WAP URL and click OK. To save the ASP denition, click OK.
5. Use this ASP denition in the New Broadcast wizard to create a new ASP broadcast. The default 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: Users Guide). 6. Select Test on the General tab in the Broadcast Properties dialog box. Enter a mobile device phone number and click OK.
You can dene several WAP integration broadcasts. To set the default WAP integration broadcast, use the WAP Integration Options in the Server Conguration window. After you set the WAP integration option, all multichannel broadcasts automatically use this WAP integration broadcast to send HTML content to a mobile device. For more information, see WAP Integration Options on page 119. To change the WAP Integration broadcast after the multichannel broadcast is created, use the WAP tab in the broadcast properties dialog box. For more information, see WAP Properties (Chapter 4, SAS Digital Marketing: Users Guide).
Understanding SpamAssassin
SpamAssassin is open source software for e-mail spam ltering that is based on content-matching rules. A large set of rules is provided that determine whether an e-mail message is spam. SpamAssassin searches specic elds in the e-mail header and the e-mail body for the occurrence of certain expressions. If a match is found, then the e-mail is assigned a spam lter score. SpamAssassin can add customizable e-mail header information to the e-mail message that includes the spam lter score. The e-mail recipient or Internet service provider might use the score that results from multiple tests or other criteria to determine whether the e-mail message is placed in a spam folder, deleted, or agged. You can congure SAS Digital Marketing to display the SpamAssassin score when an e-mail broadcast is previewed. Each SpamAssasin test consists of a label and a description. Usually the label is an upper case identier that is separated by underscores, such as LIMITED_TIME_ONLY. The description for this label might be Offers a limited time offer. E-mail passes the test when the message contains certain variants of a phrase, such as limited time only. If SpamAssassin assigns +0.3 as the spam lter score, then the e-mail must pass additional tests in order to meet a spam threshold. After the spam lter score reaches the spam threshold (5), SpamAssassin classies the e-mail as spam. Some tests, such as those for invalid message IDs or years, are assigned a very high score, so that a single test might cause the e-mail to meet the spam threshold. When the total spam lter score is above the value of the required_hits setting that is specied in
the SpamAssassin conguration, the e-mail is identied as spam and rewritten according to several options. For the default conguration, SpamAssassin appends the content of the e-mail as a MIME attachment, with a brief excerpt in the message body, and a description of the tests that classied the e-mail as spam. If the score is lower, then information about the passed tests and the total score is 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.
You can also use the SAS language adapter to connect the geographic information to your selection process and further segment the customers that receive particular e-mail offers. For more information, see Chapter 7, Managing SAS Jobs.
This version of the database uses an open source Java API to efciently search the database. 2. Unpack the binary archive le GeoLiteCity.dat or GeoIPCity.dat with a le compression utility such as WinZip. Store the le in the ROOT/config directory on the SAS Digital Marketing server. 3. Download the latest version of the Java API from:
http://www.maxmind.com/download/geoip/api/java/
Unpack the archive le GeoIPJava-n.zip with a le compression utility such as WinZip. Store the le 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 the Java API, use a 1.4.n Java software development kit (SDK) that is available from the Sun Developer 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 under source/com/maxmind/geoip. Compile the source jars by executing the following command:
javac *.java
6. Back up the source directory and the jar le by executing the following command:
jar -cvf geocity.jar *
7. Copy the support jar le, geocity.jar, to the ROOT/lib directory on the SAS Digital Marketing server.
SAS Digital Marketing automatically provides a MaxMind server extension. The server extension source is also provided in the ROOT/doc/javaext directory. This server extension periodically runs and augments the response data with geographic information. To congure a server extension you must set the SEMServerExtension family of server properties in the server.properties le in the ROOT/config directory. To use the MaxMind server extension, add the following server property:
SEMServerExtension1=MaxMindExtension
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 along with any errors that might have occurred.
NOTE: NOTE: NOTE: NOTE: NOTE: NOTE: NOTE: NOTE: Augmenting response table for 6183_both (Broadcast_zrn4k2) Found 4 IP addresses to resolve. Augmentation took 3234 milliseconds. Augmenting response table for 6211_Both (Broadcast_ysi8g2) Found 0 IP addresses to resolve. Augmentation took 641 milliseconds. Augmenting response table for 6245_both (Broadcast_108q8xv) Found 0 IP addresses to resolve.
If you have pre-existing response data, then the rst execution of the MaxMind server extension might require a considerable amount of processing time (hours). After the initial argumentation of the 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 congured on the SAS Digital Marketing server so that your response data is automatically augmented with geographic information. For information about the response table, Response Table Layout (Chapter A, SAS Digital Marketing: Users Guide).
Chapter 7
for your SAS session does not use UTF-8 mode, then use the BatchSASOptions server property to set the ENCODING= option to use UTF-8. For additional information, see Integration Utils Server Properties on page 141. If an IOM workspace server is used as your SAS environment, then see SAS 9.1.3 Integration Technologies Server Administors Guide for information how to congure your workspace server to use UTF-8 mode. After you have congured the SAS language adapter, you can create and manage SAS jobs from SAS Digital Marketing. When you execute the SAS job, the SAS program uses the Web reporting tier to query broadcast data as an XML stream. The SAS program that you develop using the SAS language adapter in SAS Digital Marketing can be run in any SAS 9 environment, such as the following: 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 programs that can be used with SAS Digital Marketing. The following gure 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 is called from SAS using the URL access method to retrieve the XML query. An XML LIBNAME is assigned to the URL FILEREF. Then by using the SAS Digital Marketing server, a SAS ETL process can access the broadcast data (from the response, reply, customer, or audit databases) like any other SAS data set.
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 the following 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 Job Editor after you click OK. For more information, see Developing SAS Code on page 195. 6. Click OK.
The upper portion of the window displays the SAS code and the report that was created from any code that you submitted. If no code has been submitted yet, then the text Select submit to execute the SAS job is visible.
N OTE : If you are developing SAS code using the JAVA SAS/GRAPH driver, then any graphical output in the report does not appear in the SAS Job Editor. When you submit the SAS code, an external Web browser window (such as Internet Explorer) opens to display the report. For more information about how each graph device driver works with SAS reports, see Requirements for Viewing SAS Reports (Chapter 2, SAS Digital Marketing: Web Studio Users Guide). The lower portion of the window contains the following tabs: Log tab displays events from executing the SAS code and any errors. The log includes the time when the SAS code is executed and the total processing time. Target tab enables you to select the group or broadcast against which to run the report. N OTE : This tab is not available if you are editing a batch SAS job. Properties tab lists the properties of the current report. Compiled SAS Code tab displays the compiled SAS code that you can run in any execution environment.
After SAS Digital Marketing runs the SAS code, the icon on the Log tab changes to one of the following: species that the code ran with no errors or warnings. species that an error occurred when running the SAS code. You should review these errors in the log. species that a warning was generated when running the SAS code. You should review these warnings in the log. The log also includes the time when the SAS code is executed and the total processing time.
If you selected a group report, then this tab lists the groups that you dened in SAS Digital Marketing 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, you can select the broadcast to use to run the report. N OTE : This tab is not available if you are editing a batch SAS job.
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 of object that is selected. Unavailable menu options are disabled or hidden. Many menu and toolbar options are also available in pop-up menus. You use the menus to perform common tasks.
File Menu
Save saves your SAS code. Save As enables you to specify a lename and location for the SAS code when you save it. Page Setup opens the page setup utility so that you can specify the paper size, page orientation, page
margins, and printer properties. Print prints the SAS code as it appears in the SAS Job Editor. Close closes the SAS Job Editor.
Edit Menu
Cut deletes the selected text and stores it on the clipboard. Copy copies the selected text onto the clipboard. Nothing is copied if you do not select any text. Paste inserts the contents of the clipboard into the SAS code at the pointer position. Undo deletes the most recent text string that you typed or reverses your most recent edit action. Select All selects all the SAS code. Find/Replace searches for each case of a specic word or phrase in the SAS code. You can replace this word or phrase with alternative text. When you search, you can specify to match by capitalization or the entire word. You can also specify the direction of the search and whether to search both the code and the comments, only the code, or only the comments. Go To Line enables you to jump to a line in the SAS code. This functionality is useful when you are trying to x compilation errors in the code.
View Menu
Refresh refreshes the contents of the SAS Job Editor. In Browser displays the report that is generated by the SAS code in a separate browser window. Select Preferences from the Tools menu to specify the command that opens your external Web browser. Find Previous Error moves to the previous error or warning in the log. When SAS Digital Marketing runs the SAS code, any errors or warnings appear in the log. You can nd these errors or warnings by using this menu option. For more information about the log, see Viewing the Log on page 196. Find Next Error moves to the next error or warning in the log. When SAS Digital Marketing runs the SAS code, any errors or warnings appear in the log. You can nd these errors or warnings by using this menu option. For more information about the log, see Viewing the Log on page 196.
Actions Menu
Submit submits the SAS code for execution. The Log tab shows the results of the SAS job and any errors that might have occurred. If a report is created, it appears in the right pane of the SAS Job Editor.
Tools Menu
Manage JDBC Connections manages the connections to the JDBC data table. For more information, see Conguring JDBC Data Providers on page 222. JDBC Table Viewer starts 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: Users Guide). Manage SAS Jobs opens the SAS Job Manager. For more information, see About the SAS Job Manager on page 192. Preferences enables 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 Window starts Help for the active window. Help Contents starts Help for SAS Digital Marketing. About SAS Code Editor provides information about the release of the SAS Code Editor, and system information such as the operating system name, the JRE version, and the ROOT and working directory names.
searches for each case of a specic word or phrase in the SAS code. You can replace this word or phrase with alternative text. When you search, you can specify to match by capitalization or the entire word. You can also specify the direction of the search and whether to search both the code and the comments, only the code, or only the comments. starts the JDBC table viewer so that you can examine every record in the JDBC data table. For more information, see Using the JDBC Table Viewer (Chapter 2, SAS Digital Marketing: Users Guide).
displays the line numbers in the SAS code. Displaying the line numbers can make it easier to nd errors in the code. Auto indent indents the lines in the SAS code. Document coloring applies colors to the different elements in the SAS code. These colors help you quickly see the comments, any macros, or other programming statements. Read only changes the permissions on the le so that you can view the SAS code but cannot edit it. Tab size species the number of spaces for a tab. File type species the type of le. In SAS Digital Marketing, the default le type is SAS Program File. N OTE : The other le types do not apply in SAS Digital Marketing. Collapsible code sections species whether you can expand and collapse sections in the SAS code. If you select this option, 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 content that is in each section.
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 sample le that is displayed in the Preview box. 7. For the syntax element, select the foreground color, background color, and font style (for example, 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 the name of the scheme and click OK. The scheme now appears in the Scheme drop-down list. N OTE : To delete a scheme that you have created, click Delete. You cannot delete the schemas that ship with SAS Digital Marketing. 10. Click OK to apply your appearance changes.
Consolidating Data
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 customization 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 a preview 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 %let %let %let %let %let sem_server=localhost:9221; sem_user=admin; sem_password={sas001}YWRtaW4x; sem_broadcast_moniker=Broadcast_1108665300405; sem_broadcast_name=%nrstr(AML Report - January 2004); sem_url=http://localhost/sdm/;
data work.recipients; salutation_nm="Dr. Bob"; email_address_txt="bob@acme.com"; run; %sem_do_preview(work.recipients,work.results,&sem_broadcast_moniker,me@domain.com); 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. The syntax for this macro is the following:
%macro sem_do_transaction(intable,results,moniker)
The user-supplied values are the following: intable is the name of the data source table that contains the e-mail addresses and customization 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 source table results in one broadcast message being sent. 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 %let %let %let %let %let sem_server=localhost:9221; sem_user=admin; sem_password={sas001}YWRtaW4x; sem_broadcast_moniker=Broadcast_1108665300405; sem_broadcast_name=%nrstr(AML Report - January 2004); sem_url=http://localhost/sdm/;
data work.recipients; salutation_nm="Dr. Bob"; email_address_txt="bob@acme.com"; 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 SAS macros. N OTE : When a SAS job is initialized, the SEM_EXPORT_PROPERTIES macro is called automatically. The syntax for this macro is the following:
%macro sem_export_properties()
SEM_GET_ALL_BROADCASTS Macro
The SEM_GET_ALL_BROADCASTS macro extracts the list of dened broadcasts into an output table. The syntax for this macro is the following:
%macro sem_get_all_broadcasts(table,period,details)
The user-supplied values are the following: 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 past 30 days:
FILENAME _MACROS "sem.sas"; %INCLUDE _MACROS; FILENAME _WEBOUT TEMP; FILENAME _WEBMETA TEMP; %let %let %let %let %let %let sem_server=localhost:9221; sem_user=admin; sem_password=(sas001)YWRtaW4x; sem_broadcast_moniker=Broadcast=1108665300405; sem_broadcast_name=%nrstr(Data Quality Forum); 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 not specify any response variables to retrieve, then all the rows in the table are retrieved. For more information about the reply table, see Reply Table Layout (Appendix A, SAS Digital Marketing: Users Guide). The syntax for this macro is the following:
%macro sem_get_all_replies(table,variables,where)
The user-supplied values are the following: table is the name of the reply table 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 N OTE : The SEM_GET_ALL_REPLIES macro does not correlate the broadcasts to the reply records. To correlate broadcasts to the reply records, use the SEM_GET_REPLIES macro. 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 %let %let %let sem_server=localhost:9221; sem_user=admin; sem_password=(sas001)YWRtaW4x; sem_url=http://localhost/sdm/;
%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 specied audit variables into a table. If you do not specify any audit variables to retrieve, then all the rows in the table are retrieved. For more information about the audit table, see Audit Table Layout (Appendix A, SAS Digital Marketing: Users Guide). The syntax for this macro is the following:
%macro sem_get_audit(table, moniker,variables,where)
The user-supplied values are the following: table is the name of the audit table moniker is the broadcast moniker variables are the rows of audit variables to retrieve where is the SQL WHERE clause for creating a subset of the response records 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 %let %let %let %let %let sem_server=localhost:9221; sem_user=admin; sem_password=(sas001)YWRtaW4x; sem_broadcast_moniker=Broadcast=1108665300405; sem_broadcast_name=%nrstr(Data Quality Forum); sem_url=http://localhost/sdm/;
%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. The syntax for this macro is the following:
%macro sem_get_group(b_table,g_table,path)
The user-supplied values are the following: 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 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 %let %let %let %let %let sem_server=localhost:9221; sem_user=admin; sem_password=(sas001)YWRtaW4x; sem_group=%nrstr(\Samples\Dynamic); sem_group_name=%nrstr(Dynamic); 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 reply history. The syntax for this macro is the following:
%macro sem_get_history(table,moniker,replies)
The user-supplied values are the following: table is the name of the table that contains the history data moniker is the broadcast moniker replies is whether to retrieve the reply history 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 %let %let %let sem_server=localhost:9221; sem_user=admin; sem_password=(sas001)YWRtaW4x; sem_url=http://localhost/sdm/;
%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. The syntax for this macro is the following:
%macro sem_get_properties(table)
The user-supplied value for table is the name of the table that contains the server properties. 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 %let %let %let %let %let sem_server=localhost:9221; sem_user=admin; sem_password=(sas001)YWRtaW4x; sem_broadcast_moniker=Broadcast=1108665300405; sem_broadcast_name=%nrstr(Data Quality Forum); sem_url=http://localhost/sdm/;
%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 specic broadcast from the reply table. For more information about the reply table, see Reply Table Layout (Appendix A, SAS Digital Marketing: Users Guide). The syntax for this macro is the following:
%macro sem_get_replies(table,moniker,implicit)
The user-supplied values are the following: table is the name of the reply table moniker is the broadcast moniker implicit is whether to get the implicit replies N OTE : Your site administrator can set the ReplySummaryPeriod server property to specify the number of days to look back in the reply table for determining implicitly correlated replies. For more information, see Response Server Properties on page 151. 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 %let %let %let %let %let sem_server=localhost:9221; sem_user=admin; sem_password=(sas001)YWRtaW4x; sem_broadcast_moniker=Broadcast=1108665300405; sem_broadcast_name=%nrstr(Data Quality Forum); sem_url=http://localhost/sdm/;
%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 specied response variables into a table. If no variables are specied, then all the variables in the response table are retrieved. For more information about the response table, see Reply Table Layout (Appendix A, SAS Digital Marketing: Users Guide). The syntax for this macro is the following:
%macro sem_get_response(table, moniker,variables,where)
The user-supplied values are the following: table is the name of the response table moniker is the broadcast moniker variables are the response variables to retrieve where is the SQL WHERE clause for creating a subset of the response records 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 %let %let %let %let %let sem_server=localhost:9221; sem_user=admin; sem_password=(sas001)YWRtaW4x; sem_broadcast_moniker=Broadcast=1108665300405; sem_broadcast_name=%nrstr(Data Quality Forum); sem_url=http://localhost/sdm/;
%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. The syntax for this macro is the following:
%macro sem_group_history(table,group,period)
The user-supplied values are the following: 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 a group:
FILENAME _MACROS "sem.sas"; %INCLUDE _MACROS; FILENAME _WEBOUT TEMP; FILENAME _WEBMETA TEMP; %let %let %let %let %let %let sem_server=localhost:9221; sem_user=admin; sem_password=(sas001)YWRtaW4x; sem_group=%nrstr(\Samples\Dynamic); sem_group_name=%nrstr(Dynamic); sem_url=http://localhost/sdm/;
%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 macro tells the Web browser whether the report is an HTML le or an image le. It also states whether the report was successful or failed to execute. The syntax for this macro is the following:
%macro sem_set_meta(mimeType,ext,rc,message)
The user-supplied values are the following: 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 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 %let %let %let %let %let sem_server=localhost:9221; sem_user=admin; sem_password=(sas001)YWRtaW4x; sem_group=%nrstr(\Samples\Dynamic); sem_group_name=%nrstr(Dynamic); sem_url=http://localhost/sdm/;
%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 the next time that you run a SAS job. When a job is initialized, SAS Digital Marketing automatically exports any server properties that you set to SAS macro variables. This action enables you to reference the server property as a SAS macro. For example, a SAS macro called &WebAppURL gives you the location of your SAS Digital Marketing Web Studio deployment. The syntax for this macro is the following:
%macro sem_set_property(property,value)
The user-supplied values are the following: property is the name of the server property that you want to set value is the value of the property 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 %let %let %let sem_server=localhost:9221; sem_user=admin; sem_password=(sas001)YWRtaW4x; sem_url=http://localhost/sdm/;
%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
To modify a JDBC connection, select the name. Use the text boxes to change the driver, Universal Resource Identier (URI), user ID, and password that SAS Digital Marketing uses to connect to a JDBC provider. You can perform the following actions: Add adds a new connection. To add a connection, click Add. Use the text boxes to specify the driver, URI, user ID, and password that SAS Digital Marketing uses to connect to a JDBC data provider. For more information, see Add a JDBC Connection on page 224. N OTE : For the SAS Digital Marketing clients to create reports that access the audit table, you must specify an explicit host in the JDBC connection denition. Therefore, do not specify a JDBC connection that has localhost as the URI. Remove removes a connection. To remove a connection, select the name from the Connections box and click Remove. Test tests a JDBC connection. To perform a test, select the name from the Connections box and click 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 another third-party database, specify the driver in the Driver box.
N OTE : When you change the driver, the URI box is automatically populated with a suggested server and data port. This information might not be correct for your server. Enter the correct server and data port for your connection.
File Menu
New opens the JDBC Explorer in a new window or enables you to add a new table.
Duplicate copies the selected table and adds the copied table to the same directory. By default, the name of the copied table is Original-table-name_copy. Clone copies the table structure of the selected table. The content is not copied; only the structure is copied. By default, the name of the cloned table is Original-table-name _clone. Delete deletes the selected table. Rename enables you to rename the selected table. Properties displays the properties of the selected JDBC table. The Properties window displays general information, such as the name of the table and the connection, and the columns in the table, such as the column name, type, and size. Close closes the JDBC Explorer.
Edit Menu
Cut deletes the selected table or tables. Copy copies the selected text in the SQL tab onto the clipboard. Nothing is copied if you do not select any text. Paste pastes the text from the clipboard to the current location in the SQL tab. Select All selects all the content in the current library.
View Menu
Explorer Console displays the Log and SQL tabs at the bottom of the Explorer window. You can choose to display or hide these tabs. Refresh refreshes the view of the JDBC Explorer.
Actions Menu
Clear Log clears the contents of the Log tab. Submit SQL Statement enables you to submit the SQL statements that you entered in the SQL tab.
Tools Menu
Manage JDBC Connections manages the connections to the JDBC data table. For more information, see Conguring JDBC Data Providers on page 222. JDBC Table Viewer starts the JDBC table viewer so that you can examine every record in the JDBC data table. For more information, see Using the JDBC Table Viewer (Chapter 2, SAS Digital Marketing: Users Guide).
Help Menu
Using this Window opens Help for SAS JDBC Explorer. Help Contents starts Help for the application. For more information, see Using Help (Chapter 2, SAS Digital Marketing: Users Guide). About SAS JDBC Explorer provides information about the release of the JDBC Explorer and also provides system information such as the operating system name, the JRE version, and the home and working directory names.
Chapter 9
Tracking Responses
If you are uncertain about data model that your site will use, then do not specify the tracking parameters. For more information about data models, see Managing Global Data Models on page 166.
Monitoring Replies
You can view all the reply messages for a selected broadcast from the Replies tab in the Query Broadcast Response window. Uncorrelated replies (reply messages that are implicitly correlated to the selected broadcast) are marked with a yellow ag while correlated replies (reply messages that you can connect to a selected broadcast) are marked with a green ag.
where replydomain is the name of your domain mailbox. For more information on the EmailFromOverride server property, see Reply Management Server Properties on page 147.
As an alternative, you can set the EmailFromOverride server property to use a global domain mailbox for all broadcasts that are created at your site. Congure one mailbox to process the replies, such as anything@replydomain. Then use the EmailFromOverride server property to insert <moniker>@replydomain. SAS Digital Marketing hides the value of the 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, then your SAS Digital Marketing users must set at least one return e-mail address to the broadcast moniker at the incoming domain mailbox. You can use the following approaches in the New Broadcast wizard or the Properties dialog box for an e-mail broadcast or a multichannel broadcast: Set the value of Reply to and From return e-mail addresses to
<xsl:value-of select="$moniker"/>@replydomain
where replydomain is the name of your domain mailbox. As a best practice, the values 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. The disadvantage to this approach is that the e-mail recipient can see this address, and the e-mail might be identied as spam. Set the value of SMTP Mail From to
<xsl:value-of select="$moniker"/>@replydomain
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. The disadvantage is that not all replies, such as Out of Ofce replies, are correlated.
N OTE : If the EmailFromOverride server property is set, then the SMTP Mail From box is not available. For more information, see Creating E-mail Broadcasts (Chapter 3, SAS Digital Marketing: Users Guide) and see Customizing the Header Information (Chapter 5, SAS Digital Marketing: Users Guide).
SAS Digital Marketing stores the conguration information for the E-mail Reply Manager in the replymgr.xml le that is located in the ROOT/config directory. You should not edit this le directly. Instead, you should use the Reply Manager Conguration dialog box that is available from the E-mail Reply Option node in the Server Conguration window. For more information, see E-mail Reply Options on page 101.
Inbox Tab
You use the Inbox tab to specify the POP3 or IMAP e-mail account information. This account receives the e-mail replies and bounces for broadcasts transmissions that use return e-mail addresses with the incoming domain mailbox in the message header.
You must specify the e-mail server information for the incoming domain mailbox. Enter the name of the server host, and specify the port that the server uses on that host. The domain conguration is external to SAS Digital Marketing and is specic to the e-mail server that you use. If the server is congured to require authentication, then specify the user credentials. N OTE : Support for IMAP is experimental for this release.
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 connection that you have selected. To select a different table connection, use the Connections drop-down list. Enter a valid table name for the JDBC provider in the Table box. This name can be for an existing table or a new table. SAS Digital Marketing automatically creates the table if it is not found in the folder. N OTE : For the SAS Digital Marketing clients to create reports that access the reply table, you must specify an explicit host in the JDBC connection denition. Therefore, do not specify a JDBC connection that has localhost as the URI. For more information, see Managing the Connections Settings on page 222.
Priority Tab
You use the Priority tab to specify the reply categories. You can add, delete, and update reply categories 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 and Reply 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.
Select Reply Manager from the Tools menu. Select Tools!Server Conguration!E-mail Reply Options and then click Congure Reply Manager.
File Menu
New Reply Filter Category creates a new reply lter category. For more information, see Add a Reply Filter Category on page 245. Exit closes the E-mail Reply Manager.
Edit Menu
Delete deletes the selected reply messages. You cannot delete a reply lter category by using the Edit menu. Select All selects all the reply messages for the selected reply lter category in the navigation tree.
Actions Menu
Refresh refreshes the contents of the E-mail Reply Manager.
Tools Menu
Query Reply Data opens the Query Reply Data window. For more information, see Using the Query Reply Data Window (Chapter 7, SAS Digital Marketing: Users Guide). Reply Manager Conguration opens the Reply Manager Conguration dialog box. For more information about the available options, see E-mail Reply Options on page 101. JDBC Table Viewer starts the JDBC table viewer. For more information, see Using the JDBC Table Viewer (Chapter 2, SAS Digital Marketing: Users Guide).
Help Menu
Using this Window provides Help about the active window. Help Contents starts Help for SAS Digital Marketing. For more information, see Using Help (Chapter 2, SAS Digital Marketing: Users Guide). About E-mail Reply Manager provides information about the SAS Digital Marketing client and about the server release of the E-mail Reply Manager. Also provides system information such as the operating system name, the JRE version, the ROOT and working directory names, and the settings of the server properties.
starts the JDBC table viewer. See Using the JDBC Table Viewer (Chapter 2, SAS Digital Marketing: Users Guide).
To review the contents of a reply message, right-click the message and select Open from the pop-up menu.
Out of Ofce messages about recipients that are out of the ofce. Unsubscribe messages about recipients that no longer want to receive broadcast messages. Automated Response automated replies from the recipients address. Replies replies to the broadcast message. Other messages that did not meet any of the reply rules dened in the other categories. This category is required by SAS Digital Marketing and must use Other as its name. You can specify any value for the label. Do not assign any reply rules to this category.
2. In the Properties dialog box, use the tabs to specify the lter name, options, rules, and forwarding addresses for the reply lter. For more information, see Reply Rules Properties on page 247.
3. Click OK. N OTE : Messages that the E-mail Reply Manager has already categorized are not processed again and are not placed into new or updated categories. When you create new reply categories or change the reply rules, then any messages that have already been saved and categorized are not processed again with the new rules or placed into the new categories. This is also true if you delete categories.
If you delete a reply lter category, the E-mail Reply Manager no longer displays this category or the reply messages in that category. However, the physical directory for the reply lter category and the physical les that contain the reply messages are not deleted. SAS Digital Marketing does not store the reply messages in another reply lter. The records for reply messages in this category also remain in the reply table.
General Properties
The General tab enables you to describe the reply lter category and set options that control how the reply messages are processed.
You can specify the following options: Label species the label for the reply lter. This is the name of the folder in the navigation tree of the E-mail Reply Manager. Description describes the types of messages in this reply lter category. Name lists the name of the reply lter category. Scan e-mail message body for embedded e-mail address scans the reply for any embedded e-mail addresses. Select this option if messages that match this lter are returned with the recipient e-mail address in the body of the message. Often when a hard bounce occurs, all original content and headers are removed and the body of the bounced message contains details about the bad e-mail address. For this reason, the Hard Bounce category sets this option set by default. Save a copy of reply messages saves a copy of the reply messages for this reply lter. The reply messages are saved to the SAS Digital Marketing Server for the number of days that you specify in the Number of days to 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-outs adds the e-mail addresses for the reply messages in this reply lter to the opt-out table. The number of responses for a single e-mail address must match the occurrence threshold for optouts. 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 is automatically added to the opt-out table, and SAS Digital Marketing no longer sends any broadcast messages to that address. Use this reply lter with SAS Customer Intelligence sends reply history to SAS Customer Intelligence software. You must decide whether to record the reply as a failed contact or as a valid response. To use the reply lter, you must use broadcast denitions that create correlated replies. For more information, see Using Correlated Replies on page 232.
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 that match the reply lter category. For more information, see Forwarding Replies on page 252.
4. In the Subject Match, Body Match, or Sender Match boxes, you can specify the text to compare to the reply messages. A reply is added to the reply lter category if the text is an exact match. If the text does not need to be an exact match, you can use an asterisk (*) as a wildcard value. For example, to categorize any reply messages with a subject of Recipient does not exist as a hard bounce, type this phrase into the Subject Match box. The content of the body and the sender is not relevant, so enter an asterisk (*) in these boxes. With this rule, any e-mail that has a subject of Recipient does not exist is ltered to the Hard Bounce reply lter, regardless of the e-mails body content or sender. N OTE : If you specify the ReplyFilterRegex server property, then you can specify regular expressions for the reply rules. For more information, see Reply Management Server Properties on page 147. 5. Specify a priority for each reply rule. If a reply ts the reply rules for several categories, then the value of the priority determines how the reply is categorized. For example, an e-mail matches a reply rule for both the Spam Warning and Soft Bounce categories. The rule for the Spam Warning reply lter has a priority of 1, and the rule for the Soft Bounce reply lter has a priority of 2. Because the priority of the rule for the Spam Warning is higher, the e-mail is categorized as a Spam Warning.
2. Select the Rules tab in the Properties dialog box. 3. Select the rule that you want to change and click Modify. The Modify Reply Rule dialog box opens. 4. Edit the options that you want to change. The options in this dialog box are identical to the options that are available when you create a reply rule. For more information, see Create a New Reply Rule on page 250.
Forwarding Replies
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 reply messages. 5. Click OK to save the information.
Chapter 10
3. Specify the value for the maximum number of threads that SAS Digital Marketing sends to improve the performance of broadcast transmissions, and click Next. By default, SAS Digital Marketing uses multiple threads to improve efciency.
Set the Maximum number of threads for e-mail broadcasts to improve performance on the grid node. Set Maximum number of SMTP spooler threads to improve performance on the SMTP e-mail servers. For more information, see Adjusting Performance Settings on page 264.
4. Specify the settings to send the broadcast transmissions and click Next.
Use the SMTP E-mail Servers table to dene the additional e-mail servers. Then verify that the settings for the outgoing SMTP e-mail server is valid. You must list at least one outgoing mail server. SAS Digital Marketing uses the e-mail servers to send the e-mails that are rendered. For more information about changing these settings, see Send Options on page 112.
5. Specify the location of the middle tier where the tracking and Web publication servlets are deployed and click Next. These Java servlets collect response metrics for e-mail broadcasts, process multichannel broadcasts, and manage Web resources.
The servlet WAR le that contains the tracking and Web publication servlets must be deployed on a Web application server outside your corporate rewall. To specify the location of the middle tier, enter the base URL address for the Web application server. To verify that the Java servlets work correctly, click Test. 6. After you verify the servlets, click Finish to congure the grid node. If you want to change a setting, click Back to return to the appropriate step in the wizard.
5. To add a grid node, click Add. In the Add grid node dialog box, type the name of a computer in the grid network and click OK. SAS Digital Marketing adds the new grid node server to the Available Grid Nodes for Distributed Execution table. 6. Continue to add grid nodes until every computer that runs a grid node server is included in the grid network.
1. Start SAS Digital Marketing on each grid node by selecting the SAS Digital Marketing Grid Node shortcut from the Start menu under Windows, or by running the gridnode command under the UNIX and Linux operating environments. You can also start the SAS Digital Marketing grid node server as a Windows service. 2. Use a computer that is running a SAS Digital Marking server and select the SAS Digital Marketing Studio shortcut from the Start menu under Windows, or run the studio shell script 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 to the recipients on your distribution list. For more information, see Set Simulate Mode on page 261. 4. Execute an e-mail broadcast denition that has a large distribution list. In order for SAS Digital Marketing to distribute the e-mail to the grid nodes, ensure that your distribution list is several times larger than the Number of messages to generate per thread value. This value appears in E-mail Options under the Broadcast Denition node in the Server Conguration window. 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 grid network that SAS Digital Marketing uses to execute your broadcast. You also see the threads that are running on each computer. You can examine the Threads tab in the SAS Digital Marketing Monitor window for each grid node to see the threads that are running on that computer.
Optimizing Performance
Part V
Appendixes
Appendix A
Overview of JMS
JMS is a Java message standard that enables application components that are based on the Java 2 Platform, Enterprise Edition (J2EE) to create, send, receive, and read messages. You must have a JMS provider to use JMS. To use JMS with SAS Digital Marketing, you congure JMS for use with BEA WebLogic as the provider and test the JMS provider. Then you congure SAS Digital Marketing to use the JMS provider and write a client to process response events.
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 that the SAS Digital Marketing server is deployed to your server, click the Target and Deploy tab. Select your server from the Target drop-down list and click Apply.
5. Expand the Destinations node under Services ! JMS ! Servers ! SASDigitalMarketing and select Congure 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. Click Create.
8. Expand the Connection Factories node under Services ! JMS 9. Select Congure a New JMS Connection Factory.
10. To create the connection factory, specify SASDigitalMarketingFactory as the factory name and JNDI name. Click Create.
11. To verify that the SASDigitalMarketingFactory is deployed to your server, click the Target and Deploy tab, select the server, and click Apply.
If you use WebLogic and the suggested names for the JMS queue, topic, and factory, then the default settings are correct. Otherwise, change these names to match your conguration before you click Test JMS Settings.
2. Start the SAS Digital Marketing Server by selecting the SAS Digital Marketing Server shortcut from the Start menu under Windows or by running the startsrv command under the UNIX and Linux operating environments. 3. Start SAS Digital Marketing Studio by selecting the SAS Digital Marketing Studio shortcut from the Start menu under Windows or by running the studio shell script under the UNIX and Linux operating environments.
4. Select JMS Queue Monitor from the Tools menu to open the E-mail JMS Queue Monitor window.
5. Type the settings that you veried on the SAS Digital Marketing JMS Test page, including the fully qualied hostname of the JMS URL. 6. Click Connect to connect to the JMS Queue that you veried on the SAS Digital Marketing JMS Test page. 7. On the SAS Digital Marketing JMS Test page, click Test JMS Settings. A test message appears in the E-mail JMS Queue Monitor window.
The readme.txt le or the readme.html le at this location contains build instructions and other information about the sample JMS clients.
Glossary
API (application programming interface) a set of software functions that facilitate communication between applications and other kinds of programs, services, or devices. ASP (Application Service Provider) a company that provides a software application on a shared server over the Internet. ASPs typically charge a fee for use of this software. bounce an e-mail message that is returned to the sender because of an error in the delivery process. broadcast a communication that is distributed by SAS Digital Marketing software through e-mail or through another electronic medium. broadcast denition a collection of information that describes a broadcast transmission. A broadcast denition includes header information, a recipient list, the type of message to send, the content to send, and a description of what to track. A broadcast denition also includes related execution records such as audit records, history records, and response records. broadcast tracking servlet a servlet that records data when an e-mail recipient either views an e-mail that contains the URL of a crumb servlet or clicks a tracked link in an e-mail. See also crumb servlet and redir servlet. campaign a planned set of one or more communications that are directed at a selected group of customers or potential customers. channel a mode of communication such as an e-mail message or a print mailing. correlated reply an e-mail reply that SAS Digital Marketing can connect to a specic broadcast denition by inserting the moniker for broadcast in the reply address. See also moniker. crumb servlet a type of broadcast tracking servlet that records data when a recipient views an e-mail that contains the URL of a crumb servlet. grid computing a type of computing in which large computing tasks are distributed among multiple computers on a network. grid node a specialized server that is used for broadcast distribution.
284 ! Glossary
HTTP (HyperText Transfer Protocol) a protocol for transferring data to the Internet. HTTP provides a way for servers and Web clients to communicate. It is based on the TCP/IP protocol. IMAP a method of getting e-mail from a server. IMAP is a more sophisticated set of rules than POP. See also POP. J2EE an environment that can be used to develop Web applications. JAR le a Java Archive le. The JAR le format is used for aggregating many les into one le. JAR les have the le extension .jar. JDBC (Java Database Connectivity) a standard interface for accessing SQL databases. JDBC provides uniform access to a wide range of relational databases. It also provides a common base on which higher-level tools and interfaces can be built. JDBC data provider a data provider that complies with JDBC. JDBC provider See JDBC data provider. JDK (Java Development Kit) a software development environment that is available from Sun Microsystems, Inc. The JDK includes a Java Runtime Environment (JRE), a compiler, a debugger, and other tools for developing Java applets and applications. JMS (Java Message Service) an application programming interface (API) that enables client applications to access the facilities of a message service. This interface provides a standard way for Java programs to create, send, receive, and read messages. JVM (Java Virtual Machine) a program that interprets Java programming code so that the code can be executed by the operating system on a computer. The JVM can run on either the client or the server. The JVM 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 Web browsers. MMS (Multimedia Message Service) an extension of SMS that enables the transmission of longer text messages with graphical images and audio clips to handheld wireless devices. See also Short Message Service. moniker a unique identier for a broadcast denition that is assigned when you create a new broadcast. You can use the moniker to correlate reply, response, and audit events to the broadcast that generated them. MTA (Mail Transport Agent) an application that handles the sending and receiving of e-mail.
Glossary ! 285
POP a method of getting e-mail from a server. POP offers fewer services than IMAP. See also IMAP. redir servlet a type of tracking servlet that records data in a response table when an e-mail recipient clicks a tracked link in an e-mail. See also crumb servlet. reply lter category a set of rules that are created in the E-mail Reply Manager. SAS Digital Marketing uses these rules to categorize replies, forward replies, delete replies, and add e-mail addresses to an opt-out list. RMI (remote method invocation) a Java programming feature that provides for remote communication between programs by enabling an object that is running in one Java Virtual Machine (JVM) to invoke methods on an object that is running in another JVM, possibly on a different host. See also JVM (Java Virtual Machine). RSS (Really Simple Syndication) an XML format to syndicate Web-based content. You use an RSS feed to monitor changes to Web-based content using an RSS reader. servlet a Java program that runs on a Web server. Servlet code does not have to be downloaded to a Web browser. Instead, servlets send HTML or other appropriate content back to a browser or to another type of Web-based client application. SMS (Short Message Service) the transmission of text messages to handheld wireless devices through an SMTP-SMS gateway. The messages are not more than 160 alphanumeric characters. SMTP a set of rules that the Internet service provider uses to send e-mail. thread the smallest task or part of a program that can be executed independently of other parts of the program. tracking servlet See broadcast tracking servlet. WAP (Wireless Application Protocol) an open international standard that species how to transmit and access optimized Internet content on handheld wireless devices. Web Archive le (WAR le) a type of Java le. XSL (Extensible Stylesheet Language) a language that can be used to specify how XML documents will be formatted.
Index
accessibility features, iii addresses, see e-mail addresses architecture, 10 ASP broadcasts Clickatell, 170 denition properties, 171 denition types, 170 life cycle of, 15 NowSMS, 170 response decoder, 177 ASP Denition Manager, 170 settings, 105 attachment warning, 244 audit records customizing, 110 logging settings, 109 audit server properties, 134 audit table conguring, 111 basic security mode, 129 batch jobs, 192 distribution lists, 158 batch SAS sessions, optimizing, 144 BEA WebLogic server conguring JMS with, 269 deploying tracking servlets to, 55 bounces, 244 broadcast denitions, 158 broadcast moniker, 232 broadcast replies, 232 broadcast reports, 192 broadcast responses processing, 281 tracking servlets, 25 broadcast scheduler conguring, 85 broadcast tracking, 230 broadcasts conguring transmissions, 112 customizing, 16 life cycle of, 11 migrating, 26 sending, 112 tracking servlets, 54 Clickatell SMS broadcast type, 170 Clickatell WAP broadcast type, 170 clients installing, 32 processing response events, 281 server properties, 135 cong.xml le, 38 conguration, see also server conguration ASP denitions, 105 audit table, 111 broadcast transmissions, 112 contact history, 121 distribution list, 106 domain throttling, 116 e-mail broadcasts, 107 e-mail reply account, 236 E-mail Reply Manager, 236 e-mail servers, 113 grid nodes, 256 JDBC data providers, 222 JMS, 269, 278 response history, 123 SAS Digital Marketing Web Studio, 83 SAS Information Delivery Portal, 88 server nodes, 260 server settings for performance, 262 servers, 38 Servlet Conguration wizard, 71 spam lter, 181 tracking servlets, 54 validating, 93 WAP integration, 119 WAP integration broadcast, 178 Web services, 120 Windows service, 95 consolidating data, 206 contact history conguring, 122 settings, 121 correlated replies, 232 crumb servlet, 25 testing, 69 Customer Intelligence contact history, 121 middle tier, 120 reply history, 243, 248 response history, 122 customizing audit records, 110 broadcasts, 16 grid node conguration, 256
288 ! Index
data consolidating with other business processes, 206 data source tables, 158 sample, 93 delivery architecture, 10 deploying Java servlets Web application, 24 deploying servlets Web application, 54 deploying tracking servlets Apache Tomcat, 57 BEA WebLogic, 55 IBM WebSphere, 58 proxy server, 79 directory structure, 23 Distribution List Manager, 161 settings, 106 distribution lists, 158, 166 creating, 158 modifying, 161 documentation, 16 domain mailbox, 233 domain throttling conguring, 117 e-mail addresses address changes, 244 embedded, 248 for correlated replies, 232 e-mail broadcasts conguring, 107 creating with distribution list, 158 life cycle of, 11 settings, 107, 265 specifying grid nodes, 108 e-mail lter, 181 e-mail reply account, conguring, 236 E-mail Reply Manager, 235 accessing tasks, 241 adding reply lter categories, 245 conguring, 236 deleting reply lter categories, 246 deleting reply rules, 252 forwarding reply messages, 250 general properties of reply lter categories, 247 managing reply rules, 250 modifying reply rules, 251 opening, 240 reply lter categories, 244 reply lters and reply rules, 243 reply rules and categories, 244 e-mail reply settings, 101
conguring, 101 e-mail servers, conguring, 113 edit server properties, 138 embedded e-mail addresses, 248 encoding server properties, 140 ETL processes, 10 events response events, 281 Extract, Transform, and Load (ETL) processes, 10 le, executing from a, 143 ltering reply lter categories, 243, 244 forwarding reply messages, 250, 252 add e-mail address, 252 delete e-mail address, 253 edit e-mail address, 253 geographical reporting, 183 geolocation database, 184 get servlet, 25 global data models, 166 managing, 166 grid nodes conguring, 256 conguring server nodes, 260 customizing congurations, 256 installing, 30 simulate mode, 261 testing, 261 group reports, 192 hard bounce, 244 IBM WebSphere server, deploying tracking servlets to, 58 installation, 21 clients, 32 directory structure, 23 grid nodes, 30 migrating broadcasts, 26 requirements for, 22 servers, 26 InstallShield wizard client installation, 33 grid node installation, 30 server installation, 27 integration utilities server properties, 141 IOM workspace connections, optimizing, 144 J2EE JavaMail, 10 Java Message Service, see JMS Java servlets, 10, 24 JDBC connections, 221 dening, 124, 222
Index ! 289
JDBC data providers, 222 SAS JDBC Explorer, 225 JDBC data providers conguring, 222 connections settings, 222 creating connections settings, 124 types of, 222 JDBC Explorer, 225 accessing tasks, 226 components, 226 opening, 225 JDBC server properties, 142 JMS, 102 conguring the server, 102 conguring with BEA WebLogic, 269 JMS topic and queue, 273 processing broadcast responses, 269 processing response events, 281 testing JMS conguration, 278 JMS provider, 281 keyboard shortcuts, iii life cycle of broadcasts, 11 ASP broadcasts, 15 e-mail broadcasts, 11 RSS feeds, 11 SMS broadcasts, 14 log settings for audit records, 109 MaxMind software, 184 messages, see also text message broadcasts copies of reply messages, 248 forwarding reply messages, 250 metadata security mode, 131 New Distribution List wizard, 159 new features, 3 notication list, 118 NowSMS broadcast type, 170 opt-out table adding responders to, 248 optimization, 255 adjusting conguration settings, 262 adjusting SMTP spooler, 263 conguring grid nodes, 256 conguring server nodes, 260 grid nodes, 260 optimizing performance, 262 testing grid nodes, 261 optimizing batch SAS sessions, 144 IOM workspace connections, 144
server properties, 144 optout servlet, 25 Out of Ofce notice, 245 performance optimization adjusting conguration settings, 262 adjusting SMTP spooler, 263 ports, restricting, 145 preview server properties, 146 Properties dialog box Security tab, 168 proxy settings, 128 pub servlets, 25 redir servlet, 25 testing, 69 replies, 245 forwarding, 252 processing, 101 server properties, 147 tracking, 232 tracking correlated replies, 232 tracking uncorrelated replies, 232 reply categories, 244 reply lter categories, 243, 244 adding, 245 deleting, 246 general properties, 247 reply messages copies of, 248 forwarding, 250 reply rules, 243, 244 creating, 250 deleting, 252 managing, 249 modifying, 251 properties, 247 reports broadcast groups, 192 broadcasts, 192 res servlet, 25 response decoder, 177 response events processing, 281 response history conguring, 123 settings, 122 response server properties, 151 response table changing, 231 geolocation data, 188 setting, 231 responses, see See broadcast responses responses, automated, 245
290 ! Index
return e-mail address, 232, 233 return receipt, 244 ROOT directory, 26 RSS feeds life cycle of, 11 rss servlet, 25 sample broadcasts previewing, 94 SAS Customer Intelligence software, 7 SAS Digital Marketing, ii, 7 architecture, 8 as Windows service, 95 components, 21 installing, 21 optimizing, 255 SAS Digital Marketing server installing, 26 updating, 83 SAS Digital Marketing Web Studio conguring, 83 deploying to Web application servers, 83 SAS E-mail Marketing, migrating broadcasts, 26 SAS Information Delivery Portal, 88 conguring, 88 linking to SAS Digital Marketing, 89 SAS JDBC Explorer, 225 accessing tasks, 226 components, 226 opening, 225 SAS Job Editor, 195 Compiled SAS Code tab, 199 creating keywords for code, 205 customizing code appearance, 204 customizing options, 203 Log tab, 196 menus, 199 preferences, 203 Properties tab, 198 Target tab, 197 toolbar, 202 SAS Job Manager, 192 SAS jobs, 192 batch jobs, 192 broadcast reports, 192 conguring, 104 consolidating data, 206 creating, 193 default macros, 206 deleting, 194 editing, 194 group reports, 192 renaming, 194 SAS language adapter, 190
conguring, 103 implementing, 86 requirements, 86 SAS macros, 206 SEM_DO_PREVIEW, 207 SEM_DO_TRANSACTION, 208 SEM_EXPORT_PROPERTIES, 209 SEM_GET_ALL_BROADCASTS, 210 SEM_GET_ALL_REPLIES, 211 SEM_GET_AUDIT, 212 SEM_GET_GROUP, 213 SEM_GET_HISTORY, 214 SEM_GET_PROPERTIES, 215 SEM_GET_REPLIES, 216 SEM_GET_RESPONSE, 217 SEM_GROUP_HISTORY, 218 SEM_SET_META, 219 SEM_SET_PROPERTY, 220 SAS programs, see SAS jobs SAS reports, 183 SAS settings, 103 scheduling conguring, 85, 118 server properties, 153 settings, 117 security settings, 128 basic security mode, 129 changing, 167 metadata security mode, 131 user groups, 132 send settings, 112, 264 conguring broadcast transmissions, 112 conguring e-mail servers, 113 server conguration audit logging settings, 109 connection settings, 124, 222 e-mail broadcast settings, 107 e-mail reply settings, 101 JMS settings, 102 modifying settings, 99 SAS settings, 103 scheduling settings, 117 security settings, 128 send settings, 112 server properties, 126 threads settings, 115 throttled domain settings, 117 tracking settings, 125 Server Conguration window, 262 Server Conguration wizard, 39, 256 server extension MaxMind, 186 server nodes, conguring, 260 server properties, 126, 133, 186
Index ! 291
adding, 127 audit, 134 client UI, 135 conguring, 126 deleting, 127 editing, 138 encoding, 140 integration utilities, 141 JDBC, 142 MaxMind, 187 optimize, 144 previewing, 146 reply management, 147 response, 151 restricting ports, 145 scheduling, 153 setting, 126 SMTP e-mail server specication, 147 viewing current settings, 127 servers advanced properties, 133, 187 conguring, 38 conguring e-mail servers, 113 executing from a le, 143 executing from a table, 143 installing, 26 Web application servers, 24, 54 Web Studio server, 83 Servlet Conguration wizard, 71 servlets, see also tracking servlets crumb, 25, 69 deploying to Web application servers, 54 get, 25 Java, 10 optout, 25 pub, 25 redir, 25, 69 res, 25 rss, 25 servlets WAR le, 24, 54, 57, 79 Sever Conguration window components, 99 opening, 99 shortcuts, iii simulate mode, 261 SMS broadcasts life cycle of, 14 SMTP e-mail server, changing, 147 SMTP spooler, 263 soft bounce, 244 software requirements, ii spam warning, 244 SpamAssassin software, 181 implementing a lter, 182
spooler, 263 table, executing from a, 143 tables audit table, 111 data source tables, 158 opt-out table, 248 response table, 188, 231 testing crumb servlet, 69 grid nodes, 261 JMS conguration, 278 redir servlet, 69 simulate mode, 261 tracking servlets, 68 text message broadcasts creating ASP denition types, 170 threads conguring, 115 settings, 115, 264 Throttled Domain Manager settings, 116 Tomcat server, deploying tracking servlets to, 57 tracking correlated replies, 232 server conguration settings, 125 settings for, 125 uncorrelated replies, 232 tracking and Web publication tier specifying location of, 125 tracking architecture, 10 tracking broadcast responses changing the response table, 231 E-mail Reply Manager, 240 tracking parameters, 230 tracking servlets, 25, 54 crumb servlet, 25 deploying servlets WAR le, 54, 79 get servlet, 25 optout servlet, 25 proxy server, 79 redir servlet, 25 testing and verifying, 67, 68 updating, 70 Tracking Servlets Test page, 68 uncorrelated replies, 232 unsubscribe request, 245 updating SAS Digital Marketing server, 83 tracking servlets, 70 user authentication levels, 128 user credentials, 128 changing, 167
292 ! Index
user groups, 132 changing security, 168 validating conguration, 93 verifying tracking servlets, 68 WAP integration conguring, 119 settings, 119 WAP integration broadcast, 178 WAR les, 24, 54, 57 Web application viewing SAS reports, 183 Web application servers Apache Tomcat, 57 BEA WebLogic, 55 deploying Java servlets to, 24 deploying servlets to, 54 deploying Web Studio, 83 IBM WebSphere, 58 Web publication security, 79 servlets, 54 Web publication servlets, 54 pub servlets, 25 res servlet, 25 rss servlet, 25 Web reporting, 83 Web services conguring, 120 specications, 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 yourturn@sas.com. Include the full title and page numbers (if applicable). If you have comments about the software, please send them to suggest@sas.com.
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.
support.sas.com/saspress
SAS Documentation
To successfully implement applications using SAS software, companies in every industry and on every continent all turn to the one source for accurate, timely, and reliable informationSAS 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 PDFfree on the Web, and hard-copy books.
support.sas.com/publishing
support.sas.com/LE
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