IBM Unica emessage Version 8 Release 6 February 13, Startup and Administrator's Guide

Transcription

1 IBM Unica emessage Version 8 Release 6 February 13, 2015 Startup and Administrator's Guide

2 Note Before using this information and the product it supports, read the information in Notices on page 83. This edition applies to version 8, release 6, modification 0 of IBM UnicaeMessage and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 1999, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents Chapter 1. Hosted messaging using IBM Campaign and IBM emessage Establishing a hosted account with IBM... 1 Overall view of the startup process Before you begin working with emessage Chapter 2. Configuring the local IBM Unica Marketing environment for emessage Enabling emessage functions in Campaign Confirming emessage registration Displaying emessage menu options Specifying emessage system table characteristics.. 7 Configure access to emessage system tables Configuring access to local emessage system tables Required mapping for emessage system tables in Campaign Required restart of the web application server for Campaign Chapter 3. Connections to hosted services Requirements for configuring connection to IBM Unica Hosted Services Requirements for uploading data to IBM Unica Hosted Services Connection and port requirements Default upload connection by explicit FTP Data upload with implicit FTP Connection through an HTTP proxy Data download frequency and port setting System user to access IBM Unica Hosted Services. 22 Configuring the system user that accesses IBM Unica Hosted Services Configuring the addresses used to connect to IBM Unica Hosted Services Configuring addresses for connecting to IBM Unica Hosted Services Configuring secure communication for hosted 25 Generating a trusted keystore Configuring SSL when using WebLogic Configuring SSL when using IBM WebSphere.. 29 Chapter 4. Response and Contact Tracker operation Manual start of the RCT Manual operation of the Response and Contact Tracker Stopping the Response and Contact Tracker.. 32 About starting the RCT automatically as a service 32 Adding the Response and Contact Tracker as a service Removing the Response and Contact Tracker service Chapter 5. Startup verification Confirmation for system configurations Testing upload to IBM Unica Hosted Services Testing download from IBM Unica Hosted Services 37 Testing the connection to the hosted messaging interface Chapter 6. Configurations for IBM emessage What you can configure for emessage What to restart after configuration changes Configuring access to additional mailing execution history Configuring support for dimension tables Configuring access to local emessage system tables 43 Configuration properties for emessage Campaign partitions partition[n] emessage 43 Campaign partitions partition[n] server internal emessage servercomponentsandlocations hostedservices emessage partitions partition[n] hostedaccountinfo emessage partitions partition[n] datasources systemtables emessage partitions partition[n] recipientlistuploader emessage partitions partition[n] responsecontacttracker Chapter 7. Utilities for emessage The RLU script The RCT script The MKService_rct script The configtool utility To back up configuration settings Chapter 8. About troubleshooting emessage Log files for emessage Using log4j with emessage Chapter 9. Management of user access to messaging features Role and policy assignment for mailing access About roles and permissions in Marketing Platform and Campaign About security policies Messaging permissions in Campaign Making roles and permissions available How Campaign evaluates permissions Copyright IBM Corp. 1999, 2015 iii

4 Definition of permission states Permissions for mailings in Campaign Permissions for the Digital Assets category Permissions for the Documents category Permissions for the Administration category Messaging permissions for emessage Assigning emessage roles Controlling domains and short link domains 73 Maintenance of hosted domains Configuring default sender address and display names Controlling access to the list of sent messages Granting access to the list of sent messages Denying access to the list of sent messages Enabling the restriction to the sent message list 78 Permissions for emessage reports Contacting IBM Unicatechnical support 81 Notices Trademarks iv IBM Unica emessage: Startup and Administrator's Guide

5 Chapter 1. Hosted messaging using IBM Campaign and IBM emessage When IBM Unica Campaign is integrated with IBM UnicaeMessage, you can use emessage to conduct highly personalized marketing campaigns. emessage provides access to resources hosted by IBM so you can design, send, and monitor individually customized messages based on information stored in your customer datamart. v v In Campaign, use flowcharts to create lists of recipients and select personalization data for each recipient. In emessage, use design, transmission, and deliverability resources hosted by IBM to conduct marketing campaigns. Establishing a hosted account with IBM When you purchase an emessage subscription, IBM creates a hosted account on your behalf and sends you the account credentials that you will need to use emessage features. You apply these credentials when you configure your local IBM Unica Marketing applications to access the hosted environment over secure connections. You must have a valid account to access the resources that IBM provides as a software service. If your IBM Unica Marketing installation includes multiple partitions and you plan to use emessage in more than one partition, you need a hosted account for each partition. You cannot share accounts across installations or partitions. Establishing a hosted account is the beginning of the startup process, which lasts for approximately 90 days. For a general description of the process, see Overall view of the startup process. Overall view of the startup process You can activate features in IBM Campaign to conduct highly targeted and trackable marketing campaigns. Campaign uses functions that are provided by IBM emessage through resources that are hosted in data centers in the US and United Kingdom. An account to access these resources is included with your emessage subscription. IBM begins the startup process after it creates your hosted account. IBM helps you to become familiar with emessage, connect to hosted resources, and establish your reputation as a legitimate marketer among leading Internet Service Providers (ISPs). The process proceeds in three phases. The IBM Professional Services and Account Services teams guide you along the way. IBM Corporation 1999,

6 IBM Welcome Kit sent Conference call for kickoff account provisioned IBM performs trial mailings to "warm up" the new domain (about 30 days) Account Services remains engaged for ongoing consultation Handoff to Support as primary contact Planning Create reputation Production You Define your requirements Complete startup worksheet Approximately 90 days Configure access to hosted Build your reputation Send production volumes The Professional Services consultant is your primary point of contact with IBM during the startup process. When the account startup process completes, the Professional Services consultant transfers primary support responsibility to the IBM Product Support team. A dedicated Account Services (EAS) consultant provides special assistance for -related issues. Creating a favorable reputation among major Internet Service Providers (ISPs) is critical to ensuring that your marketing campaigns consistently reach their target recipients. When you start to run mailings, the EAS consultant reviews the mailing deliverability performance and suggests the best ways to gradually build your reputation. Startup activities and milestones Planning What happens Send account credentials and the Welcome Kit, including the Startup Worksheet. Schedule a conference call to introduce all involved parties, review the startup schedule, and understand the marketing objectives. Complete the Startup Worksheet to specify your domain requirements and mailing projections. Who is responsible IBM Unica Account Services IBM UnicaProfessional Services Your organization Create your reputation What happens Provision the account using information provided during the conference call and in the Startup worksheet. Begin warm up mailings to selected test accounts with major ISPs. This phase requires approximately 30 days to complete. Activate emessage inibm UnicaCampaign. Who is responsible IBM Unica operations IBM Unica operations Your organization (with support from IBM) 2 IBM Unica emessage: Startup and Administrator's Guide

7 What happens Configure access to hosted resources. Consult with the EAS consultant about which data center to specify. Start sending mailings. To build a favorable reputation, send small mailings initially, followed over time by larger and more frequent mailings. ISPs often try to limit spam by blocking large or frequent mailings from domains they do not recognize as legitimate. Provide deliverability results and reputation guidance as mailing volumes and frequency gradually increase. Who is responsible Your organization (with support from IBM) Your organization (with support from IBM) IBM Account Services Production What happens Send mailings at typical volume and frequency. Transfer primary contact responsibility to the IBM Support team. Maintain engagement for consultation on issues. Make contact on a regular basis for continuing account support. Who is responsible Your organization IBM Professional Services IBM Account Services Before you begin working with emessage Before you begin the hosted startup process, consider the following issues. v Some configurations require restarting the web application server. Plan emessage configuration activity to avoid interfering with large flowchart runs and other activities in Campaign. v IBM asks you to name one individual to serve as the primary contact point during the startup process. v Request hosted account credentials before you begin the startup process. You use these credentials to configure your systems to access the account. v Consult with your network administration staff. emessage requires specific port ranges when communicating with IBM Unica Hosted Services. v Confirm that you have the appropriate network permissions to make configuration changes. Chapter 1. Hosted messaging using IBM Campaign and IBM emessage 3

8 4 IBM Unica emessage: Startup and Administrator's Guide

9 Chapter 2. Configuring the local IBM Unica Marketing environment for emessage Using emessage to send hosted messages requires changes in the local installation of IBM Unica Marketing. Complete the steps described in the following sections. v Enabling emessage functions in Campaign v Registering emessage manually, if necessary on page 6 v Specifying emessage system table characteristics on page 7 v Required mapping for emessage system tables in Campaign on page 8 v Configuring access to local emessage system tables on page 8 v Required restart of the web application server for Campaign on page 9 If your environment contains multiple partitions, repeat these steps for each Campaign partition in which you use IBM UnicaeMessage. For more information about creating and working with multiple partitions, see the IBM UnicaCampaign Installation Guide. Enabling emessage functions in Campaign When you install Campaign, the installer also installs emessage in the default partition, but does not enable it. emessage functions are not available until you enable emessage. Before you begin Confirm that emessage is properly registered with IBM UnicaMarketing Platform. Registering emessage with Marketing Platform is part of the installation process for IBM UnicaCampaign. Procedure 1. In the IBM UnicaMarketing Platform, edit Campaign > partitions > partition[n] > server > internal > emessageinstalled. 2. To enable emessage, change the value to yes. Related tasks: Confirming emessage registration Confirming emessage registration IBM UnicaeMessage must be registered with IBM UnicaMarketing Platform. To confirm that emessage is registered successfully, you must examine the configuration for Marketing Platform. Procedure 1. Log in to IBM Unica Marketing. 2. Navigate to Settings > Configuration. 3. Look for the emessage configuration category. Copyright IBM Corp. 1999,

10 IBM UnicaeMessage is registered with Marketing Platform when the emessage category appears in the configuration properties hierarchy. What to do next If the emessage category does not appear in the properties hierarchy, see the IBM UnicaCampaign Installation Guide for information about how to register emessage manually. If the emessage category is available, you must enable emessage functions in Campaign. Related tasks: Enabling emessage functions in Campaign on page 5 Registering emessage manually, if necessary If the installer does not register emessage automatically, you must register emessage manually with the configtool utility provided with the IBM Unica Marketing installation. The configtool is in the tools\bin directory under your Marketing Platform installation. About this task By default, the Campaign installer automatically registers emessage with the IBM UnicaMarketing Platform, but does not enable it. In some situations, the Campaign installer does not connect with the Marketing Platform system tables to automatically register emessage. For more information about registering and configuring emessage, see the IBM UnicaeMessage Startup and Administrator's Guide. Procedure To register emessage manually, run the configtool utility as follows. configtool -r emessage -f "full_path_to_emessage_installation_directory\ conf\emessage_configuration.xml" Note: The emessage installation directory is a subdirectory of the Campaign installation directory. Displaying emessage menu options To use IBM UnicaeMessage, you must update the system configuration so that menu options for emessage display in the IBM UnicaMarketing Platform interface. To display the required options, use the configtool utility that is supplied with your IBM Unica Marketing installation. You must run configtool with specific parameters for each emessage menu option. Running configtool updates system configuration settings. You must restart the web application server to apply the changes. Although emessage is installed with Campaign, menu options for emessage do not appear until after you run configtool and restart the web application server. In the tools directory of the Marketing Platform installation, the configtool utility is located in the bin folder. 6 IBM Unica emessage: Startup and Administrator's Guide

11 Note: You must specify a path to the emessage installation directory as a configtool parameter. The emessage installation directory is a subdirectory of the Campaign installation directory. v To display emessage Settings in the Settings menu. configtool.bat -v -i -p "Affinium suite uinavigation settingsmenu" -f "full_path_to_emessage_installation_directory\conf\ emessage_op_odsettings_navigation.xml" v To display emessage Mailings in the Campaign menu. configtool.bat -v -i -p "Affinium suite uinavigation mainmenu Campaign" -f "full_path_to_emessage_installation_directory\conf\ emessage_op_mailings_navigation.xml" v To display emessage Documents in the Campaign menu. configtool.bat -v -i -p "Affinium suite uinavigation mainmenu Campaign" -f "full_path_to_emessage_installation_directory\conf\ emessage_op_documents_navigation.xml" v To display emessage Analytics in the Analytics menu. configtool.bat -v -i -p "Affinium suite uinavigation mainmenu Analytics" -f "full_path_to_emessage_installation_directory\conf\ emessage_op_analytics_navigation.xml" To verify that you successfully added the menu options, after you restart the web application server, log in to IBM Unica Marketing and open the Settings, Campaign, and Analytics menus to verify that the emessage options appear. Specifying emessage system table characteristics IBM UnicaeMessage requires information that describes the type, schema, and JDBC connection for the emessage system tables in your installation. The emessage system tables are created in the Campaign schema as part of the Campaign installation process. Procedure Provide the required information in the following configuration properties. See the Marketing Platform online help for each property to learn more about setting the configuration properties. v emessage > partitions > partition [n] < datasources > systemtables > type v emessage > partitions > partition [n] < datasources > systemtables > schemaname v emessage > partitions > partition [n] < datasources > systemtables > jdbcbatchsize v emessage > partitions > partition [n] < datasources > systemtables > jdbcclassname v emessage > partitions > partition [n] < datasources > systemtables > jdbcuri What to do next For additional information about configuration properties and configuring emessage, see Chapter 6, Configurations for IBM emessage, on page 39. Chapter 2. Configuring the local IBM Unica Marketing environment for emessage 7

12 Configure access to emessage system tables emessage components must be able to access system tables automatically, without manual user input. To allow emessage components to access system tables in the Campaign schema without requesting a manual database login, you define a system user in IBM UnicaMarketing Platform. You must configure this system user to provide the access credentials for the database that contains the Campaign schema. You configure system users and data sources in IBM UnicaMarketing Platform. For more information about how to create system users and data sources, see the IBM UnicaMarketing Platform Administrator's Guide. Configuring access to local emessage system tables IBM UnicaeMessage requires access to the emessage system tables in the Campaign schema. To allow emessage components to access system tables in the Campaign schema without requesting a manual database login, you must specify an emessage system user to provide the necessary database access credentials. About this task The system user that accesses the database is associated with an IBM UnicaMarketing Platform data source that contains the login credentials for the database that hosts the Campaign schema. For more information about system table configuration properties, see emessage partitions partition[n] datasources systemtables on page 49. Procedure 1. Specify the system user that you defined in the IBM UnicaMarketing Platform. Edit the following configuration property. emessage > partitions > partition [n] < datasources > systemtables > asmuserfordbcredentials 2. Specify the login credentials for the database that contains the Campaign schema and emessage system tables. Edit the following configuration property. emessage > partitions > partition [n] < datasources > systemtables > amdatasourcefordbcredentials Required mapping for emessage system tables in Campaign You must map emessage system tables in the Campaign schema to corresponding emessage database tables. The emessage system tables have emessage in the table name. In Campaign, map the following emessage system tables. v emessage Output List Table v emessage Output List Audience Fields Mapping Table v emessage Mailing Table v emessage Mailing Instance Table v emessage Data Table Column Mapping Table v emessage Personalization Field Mapping Table v emessage Personalization Field Usage Table 8 IBM Unica emessage: Startup and Administrator's Guide

13 For information about mapping tables, see the IBM UnicaCampaign Administrator's Guide. Required restart of the web application server for Campaign After making changes to the Campaign and emessage configurations, you must restart the web application server that hosts Campaign. Consult the documentation for your web application server for restart instructions. Chapter 2. Configuring the local IBM Unica Marketing environment for emessage 9

14 10 IBM Unica emessage: Startup and Administrator's Guide

15 Chapter 3. Connections to hosted services To access hosted services provided by IBM, you must configure a connection between the local IBM Unica Marketing installation and IBM Unica Hosted Services. Marketers access emessage features through the Campaign interface. Working with emessage requires that you establish a secure, automatic Internet connection that Campaign can use to upload recipient lists to IBM Unica Hosted Services. emessage components installed with Campaign also use this connection to download contact and response data to the emessage system tables in the Campaign schema. Note: Each instance of Campaign requires a unique connection to IBM Unica Hosted Services. If the Campaign installation includes multiple partitions, each partition requires a separate hosted account. The accounts can share the IP connection to IBM Unica Hosted Services. All communication between IBM Unica Marketing and IBM Unica Hosted Services is done over SSL. Each communication from IBM Unica Hosted Services is a response to a request from the local environment. IBM Unica Hosted Services never attempts to initiate a connection with your corporate network. All communication with IBM Unica Hosted Services originates from behind your corporate firewall. Requirements for configuring connection to IBM Unica Hosted Services Configuring a connection to IBM Unica Hosted Services requires administrative permissions and information about the hosted account established for your organization. To configure a hosted connection, you need the following. v User name and password provided by IBM for the hosted account v Permissions to create or modify system users in the IBM UnicaMarketing Platform v Administrative access to configuration properties maintained in the local IBM UnicaMarketing Platform installation v Administrative access to the web application server on which the IBM UnicaMarketing Platform and Campaign are deployed You must know, or be able to consult with people who know, your corporate data security requirements. Before you begin, review these procedures to understand how to create the necessary connection in compliance with your corporate firewall restrictions. You must be familiar with how to configure trusted connections on your web application server, either IBM WebSphere or Oracle WebLogic. IBM Corporation 1999,

16 Requirements for uploading data to IBM Unica Hosted Services An emessage component called the Recipient List Uploader (RLU) is part of your IBM UnicaCampaign installation. The RLU uses FTP in passive mode to manage the upload of mailing lists and associated metadata to IBM Unica Hosted Services. emessage uses passive FTP to upload data. When using passive FTP, the RLU initiates all upload connection requests as the local client. IBM Unica Hosted Services never initiates a connection request to your network. emessage supports two passive FTP methods, explicit FTP and implicit FTP. Explicit FTP is the default method used for uploading recipient lists. To use implicit FTP you must make changes in the emessage configuration properties. For more information about FTP in passive mode and using FTP over SSL, see RFC959 and RFC2228. Related concepts: Default upload connection by explicit FTP Data upload with implicit FTP on page 14 Connection and port requirements To communicate with IBM Unica Hosted Services you must have a connection to the Internet. IBM Unica Hosted Services uses specific ports. The local IBM Unica Marketing installation and IBM Unica Hosted Services use the following ports to communicate. HTTPS: port 443 FTP command port: v Explict FTP: port 21 v Implicit FTP: port 990 FTP data upload ports v U.S. data center Explicit FTP: ports to Implicit FTP: ports to v United Kingdom data center Explicit FTP: ports to Implicit FTP: ports to IBM Unica Hosted Services never initiates a connection with your local network. It only responds to connection requests initiated from behind your firewall. Default upload connection by explicit FTP By default, the Recipient List Uploader (RLU) uses explicit FTP when the system uploads an recipient list. The recipient list is also referred to as the Output List Table (OLT) 12 IBM Unica emessage: Startup and Administrator's Guide

17 The RLU establishes a connection with IBM Unica Hosted Services through the default FTP command port (port 21). It issues a request to encrypt the session over SSL. Over the secure connection, the RLU negotiates with the FTP server to establish a separate SSL link over a port that is randomly selected by the RLU. For more information about explicit FTP, see RFC The following diagram illustrates the default method for uploading recipient data from Campaign to IBM Unica Hosted Services. The following table describes the connection sequence. Step Action Description 1 Initial client FTP connection request From behind the corporate firewall, the RLU initiates a data upload session by using FTP over explicit SSL. The RLU sends the SSL connection request to the address for IBM Unica Hosted Services. You must configure this address in advance. To start the session, the RLU opens a randomly selected port on the client side as its FTP command port. IBM Unica Hosted Services accepts FTP command connections on port Remote FTP server response In response to the RLU request a secure SSL session, the FTP server designates the FTP data port to use for the recipient list upload. 3 Recipient List upload The RLU commences the list upload on the specified data port. When the upload finishes, the RLU drops the FTP connection. For the range of data ports the FTP server can specify, see Connection and port requirements on page 12. Chapter 3. Connections to hosted services 13

18 Related concepts: Requirements for uploading data to IBM Unica Hosted Services on page 12 Related tasks: Configuring addresses for connecting to IBM Unica Hosted Services on page 24 Configuring the system user that accesses IBM Unica Hosted Services on page 22 Configuring the explicit FTP connection No additional configuration is required. The RLU uses explicit FTP by default. Data upload with implicit FTP You can configure the RLU to use implicit FTP to upload recipient lists. Implicit FTP uses port 990 to establish a connection to IBM Unica Hosted Services. When you enable the RLU for implicit FTP, the entire session is encrypted from the start. Implicit FTP is unlike connection through explicit FTP, where the RLU explicitly requests a secure link. To use implicit FTP to upload recipient lists, you must reveal and configure a system configuration property in the emessage configuration properties. The following diagram illustrates how the RLU uploads recipient data to IBM Unica Hosted Services when the system is configured to use implicit FTP. The following table describes the connection sequence. 14 IBM Unica emessage: Startup and Administrator's Guide

19 Step Action Description 1 Initial client FTP connection request From behind the corporate firewall, the RLU initiates a data upload session by using FTP over SSL. The RLU sends the SSL connection request to the address for IBM Unica Hosted Services. You must configure this address in advance. To start the session, the RLU opens port 990. IBM Unica Hosted Services accepts encrypted FTP command connections only on port Remote FTP server response If IBM Unica Hosted Services recognizes the request as a valid implicit FTP request, the FTP server accepts the connection request. It designates the FTP data port to use for the recipient list upload. See Connection and port requirements on page 12 for the range of data ports the FTP server can specify. 3 Recipient List upload The RLU commences the list upload on the specified data port. When the upload finishes, the RLU drops the FTP connection. Related concepts: Requirements for uploading data to IBM Unica Hosted Services on page 12 Accessing the configuration parameters for implicit FTP upload To configure the system to use implicit FTP for uploading data, you must edit configuration properties that are hidden by default. You run a script to reveal the properties. About this task To configure the system to use implicit FTP for uploading data, make the following configuration properties visible. These properties are hidden by default. v emessage > servercomponentsandlocations > hostedservices > ftpport v emessage > servercomponentsandlocations > hostedservices > useftpimplicitssl This procedure reveals the configuration properties but does not configure them. To enable implicit FTP, you must access these properties in the emessage configuration and configure them. For information about how to configure these properties, see Enabling implicit FTP upload on page 16. Procedure To reveal ftpport and useftpimplicitssl, in the Tools directory of your emessage installation, run the switch_config_visibility script from the command line script, as follows. Windows \switch_config_visibility.bat -p "Affinium emessage servercomponentsandlocations hostedservices ftpport" -v Chapter 3. Connections to hosted services 15

20 true \switch_config_visibility.bat -p "Affinium emessage servercomponentsandlocations hostedservices useftpimplicitssl" -v true UNIX /switch_config_visibility.sh "Affinium emessage servercomponentsandlocations hostedservices ftpport" -v true /switch_config_visibility.sh "Affinium emessage servercomponentsandlocations hostedservices useftpimplicitssl" -v true What to do next You must restart the web application server to make these properties visible in the emessage configuration. Related tasks: Configuring access to additional mailing execution history on page 41 Enabling implicit FTP upload To enable implicit FTP, you must update the emessage configuration. Before you begin To complete this task, you must reveal two configuration properties. For more information, see Accessing the configuration parameters for implicit FTP upload on page 15. Procedure 1. Navigate to Settings > Configuration > emessage > servercomponentsandlocations > hostedservices. 2. Click Edit Settings. v Confirm that useftpimplicitssl is set to true. v Set ftpport to Save your changes. What to do next The changes do not take effect until you restart the web application server and the Campaign listener. You can do this now or wait until you complete all of the startup configuration steps. Connection through an HTTP proxy If your corporate firewall rules prohibit direct communication with the public Internet, you can connect to IBM Unica Hosted Services through an HTTP proxy server. emessage supports connecting through a SOCKS proxy server that allows both HTTPS and FTPS traffic. emessage supports SOCKS Protocol Version 5. Note: To connect to IBM Unica Hosted Services through a proxy server, you must install Campaign version or higher. 16 IBM Unica emessage: Startup and Administrator's Guide

21 The following diagram illustrates communication between the local and hosted environments when you use a SOCKS proxy. You configure the SOCKS proxy server in the local On Premises environment. Before you begin configuring the proxy server, confirm that you satisfy the following requirements. v The proxy server must be a SOCKS proxy server. v v The proxy server must be able to access the emessage OD environment. The server must allow traffic to and from the ports that are configured for the data center that is used by your hosted account. IBM maintains data centers in the United States and in the United Kingdom. The emessage OP environment must be able to access the SOCKS proxy server. Configuring routing for FTPS and HTTPS traffic through a SOCKS proxy To use a SOCKS proxy to access the hosted resources, you must update the web application server where you deployed IBM Campaign. You must also modify the startup scripts for the emessage RCT and RLU. Procedure v For FTPS traffic, apply the following configurations to the RLU and the web application server. Setting -Dibm.unica.emessage.ftps.proxy.host = <sockshost> Description Host name or IP of the SOCKS proxy. Chapter 3. Connections to hosted services 17

22 Setting -Dibm.unica.emessage.ftps.proxy.port = <socksport> -Dibm.unica.emessage.ftps.proxy.match.hosts= <comma separated list of host names and IP addresses> Description The port on which SOCKS proxy is running. Host names and IP addresses that are used when routing traffic through the SOCKS proxy. Provide values specific to the data center used by your account. -Dibm.unica.emessage.ftps.proxy.match.hosts= When the local and hosted environments establish a data connection, the IP address that is specified for -Dibm.unica.emessage.ftps.proxy.match.hosts is the IP address that the remote FTP server sends to the local FTP client. Set -Dibm.unica.emessage.ftps.proxy.match.hosts to one of the following values. The value that you enter depends on the data center that is used by your hosted account. Host name and IP addresses for the US data center: -Dibm.unica.emessage.ftps.proxy.match.hosts= Host name and IP addresses for the UK data center: ftpem.unicaondemand.com, , , , , , ftp-emeu.unicaondemand.com, , , , , , v For HTTPS traffic, apply the following configurations to the RCT and the web application server. Setting -Dibm.unica.emessage.https.proxy.host=<socksHost> -Dibm.unica.emessage.https.proxy.port=<socksPort> -Dibm.unica.emessage.https.proxy.type=SOCKS Description Host name or IP of the SOCKS proxy The port on which SOCKS proxy is running The type of proxy server. You must use a SOCKS proxy server. Configuring authentication to access a SOCKS proxy If your SOCKS proxy requires authentication, you must configure the web application server, RLU, and RCT to provide the access credentials. Procedure Configure the following for the web application server, RLU, and RCT. The values for username and password must be the credentials that are required to authenticate against the proxy. -Dibm.unica.emessage.proxy.auth.user = <username> -Dibm.unica.emessage.proxy.auth.password = <password> 18 IBM Unica emessage: Startup and Administrator's Guide

23 Configuring the RCT to use a SOCKS proxy You must modify the RCT to communicate through a SOCKS proxy server. The required settings depend on your operating system. Procedure v For the RCT in Windows environments, add the following proxy arguments to common.bat. The common.bat file is in the //emessage/bindirectory of your local emessage installation. set RCT_PROXY_ARGS= -Dibm.unica.emessage.https.proxy.host=<PROXY_HOST> -Dibm.unica.emessage.https.proxy.port=<PROXY_PORT> -Dibm.unica.emessage.https.proxy.type=SOCKS -Dibm.unica.emessage.proxy.auth.user=<PROXY_AUTH_USER> -Dibm.unica.emessage.proxy.auth.password=<PROXY_AUTH_PASSWORD> set RCT_JAVA_ARGS=%BASE_VM_ARGS% %RCT_MEM_ARGS% %RCT_EXTRA_VM_ARGS% %RCT_PROXY_ARGS% v For the RCT in UNIX environments, add the following proxy arguments to common.sh. The common.sh file is in the \\emessage\bin directory of your local emessage installation. Note: Do not directly modify rlu.sh, rct.sh, or setenv.sh. The system overrides the changes. RCT_PROXY_ARGS=" -Dibm.unica.emessage.https.proxy.host=<PROXY_HOST> -Dibm.unica.emessage.https.proxy.port=<PROXY_PORT> -Dibm.unica.emessage.https.proxy.type=SOCKS -Dibm.unica.emessage.proxy.auth.user=<PROXY_AUTH_USER> -Dibm.unica.emessage.proxy.auth.password=<PROXY_AUTH_PASSWORD>" RCT_JAVA_ARGS="${BASE_VM_ARGS} ${RCT_MEM_ARGS} ${RCT_EXTRA_VM_ARGS} ${RCT_PROXY_ARGS}" Configuring the RLU to use a SOCKS proxy You must modify the RLU to communicate through a SOCKS proxy server. The required settings depend on your operating system. Procedure v For the RLU in Windows environments, add the following proxy arguments to common.bat. The common.bat file is in the //emessage/bin directory of your local emessage installation. Chapter 3. Connections to hosted services 19

24 set RLU_PROXY_ARGS= -Dibm.unica.emessage.ftps.proxy.host=<PROXY_HOST> -Dibm.unica.emessage.ftps.proxy.port=<PROXY_PORT> -Dibm.unica.emessage.ftps.proxy.match.hosts=<comma separated list of host names and IP addresses> -Dibm.unica.emessage.proxy.auth.user=<PROXY_AUTH_USER> -Dibm.unica.emessage.proxy.auth.password=<PROXY_AUTH_PASSWORD> set RLU_JAVA_ARGS=%BASE_VM_ARGS% %RLU_MEM_ARGS% %RLU_EXTRA_VM_ARGS% %RLU_PROXY_ARGS% v For the RLU in UNIX environments, add the following proxy arguments to common.sh. The common.sh file is in the \\emessage\bin directory of your local emessage installation. Note: Do not directly modify rlu.sh, rct.sh, or setenv.sh. The system overrides the changes. RLU_PROXY_ARGS=" -Dibm.unica.emessage.ftps.proxy.host=<PROXY_HOST> -Dibm.unica.emessage.ftps.proxy.port=<PROXY_PORT> -Dibm.unica.emessage.ftps.proxy.match.hosts=<comma separated list of host names and IP addresses> -Dibm.unica.emessage.proxy.auth.user=<PROXY_AUTH_USER> -Dibm.unica.emessage.proxy.auth.password=<PROXY_AUTH_PASSWORD>" RLU_JAVA_ARGS="${BASE_JAVA_ARGS} ${RLU_MEM_ARGS} ${RLU_EXTRA_VM_ARGS} ${RLU_PROXY_ARGS}" Configuring the web application server to use a SOCKS proxy To connect to IBM Unica Hosted Services through a SOCKS proxy, you must modify the configuration of the web application server. For IBM Unica WebSphere servers, you modify the generic JVM arguments. For Oracle Weblogic servers, you modify the SetDomainEnv script. Procedure v If your web application server is IBM Unica WebSphere, add the following to the WebSphere generic JVM arguments. 20 IBM Unica emessage: Startup and Administrator's Guide

25 -Dibm.unica.emessage.https.proxy.host=<PROXY_HOST> -Dibm.unica.emessage.https.proxy.port=<PROXY_PORT> -Dibm.unica.emessage.https.proxy.type=SOCKS -Dibm.unica.emessage.ftps.proxy.host=<PROXY_HOST> -Dibm.unica.emessage.ftps.proxy.port=<PROXY_PORT> -Dibm.unica.emessage.ftps.proxy.match.hosts=<comma separated list of host names and IP addresses> -Dibm.unica.emessage.proxy.auth.user=<PROXY_AUTH_USER> -Dibm.unica.emessage.proxy.auth.password=<PROXY_AUTH_PASSWORD> v If your web application server is Oracle Weblogic, modify the setdomainenv script. The required settings depend on your operating system. In Windows environments, make the following changes: JAVA_OPTIONS =%{JAVA_OPTIONS} -Dibm.unica.emessage.https.proxy.host=<PROXY_HOST> -Dibm.unica.emessage.https.proxy.port=<PROXY_PORT> -Dibm.unica.emessage.https.proxy.type=SOCKS -Dibm.unica.emessage.ftps.proxy.host=<PROXY_HOST> -Dibm.unica.emessage.ftps.proxy.port=<PROXY_PORT> -Dibm.unica.emessage.ftps.proxy.match.hosts=<comma separated list of host names and IP addresses> -Dibm.unica.emessage.proxy.auth.user=<PROXY_AUTH_USER> -Dibm.unica.emessage.proxy.auth.password=<PROXY_AUTH_PASSWORD> In UNIX environments, make the following changes: JAVA_OPTIONS ='${JAVA_OPTIONS} -Dibm.unica.emessage.https.proxy.host=<PROXY_HOST> -Dibm.unica.emessage.https.proxy.port=<PROXY_PORT> -Dibm.unica.emessage.https.proxy.type=SOCKS -Dibm.unica.emessage.ftps.proxy.host=<PROXY_HOST> -Dibm.unica.emessage.ftps.proxy.port=<POXY_PORT> -Dibm.unica.emessage.ftps.proxy.match.hosts=<comma separated list of host names and IP addresses> -Dibm.unica.emessage.proxy.auth.user=<PROXY_AUTH_USER> -Dibm.unica.emessage.proxy.auth.password=<PROXY_AUTH_PASSWORD>' Chapter 3. Connections to hosted services 21

26 Data download frequency and port setting An emessage component called the Response and Contact Tracker (RCT) is installed as part of your IBM UnicaCampaign installation. The RCT regularly requests response and tracking data from IBM Unica Hosted Services. By default, the RCT issues a data request every 5 seconds. The RCT issues data requests over HTTPS (HTTP over SSL). IBM Unica Hosted Services accepts HTTPS connection requests on port 443, and only from hosts that you have specified during the hosted account startup process. Related concepts: Chapter 4, Response and Contact Tracker operation, on page 31 System user to access IBM Unica Hosted Services IBM UnicaeMessage components must be able to communicate with IBM Unica Hosted Services without requiring manual entry of login credentials. To establish automatic login, define a system user in IBM UnicaMarketing Platform that can provide the required access credentials. To simplify user administration and troubleshooting, you can modify an existing system user to access hosted services and local system tables. You can configure a single system user to provide credentials for multiple systems. For example, modifying the configuration of the Campaign system user creates a single user that can automatically access IBM Unica Hosted Services and the emessage system tables in the Campaign schema. The credentials that are required to access IBM Unica Hosted Services are the user name and password that IBM provided during the startup process. The credentials that you use depend on whether you are connecting to the data center that IBM maintains in the US or to the data center in the United Kingdom. Consult with IBM to determine which data center you use. For specific information about how to configure a system user to communicate with IBM Unica Hosted Services, see the IBM UnicaeMessage Startup and Administrator's Guide. For general information about how to create system users and data sources, see the IBM UnicaMarketing Platform Administrator's Guide. Configuring the system user that accesses IBM Unica Hosted Services emessage components in Campaign must be able to access IBM Unica Hosted Services automatically, without prompting for a login. System users that are configured in IBM UnicaMarketing Platform can reference a data source that provides the required user name and password. You can add the data source to a new system user or to an existing system user. To simplify user administration, you can update a system user that is already configured to access the Campaign schema so that it can also access IBM Unica Hosted Services. 22 IBM Unica emessage: Startup and Administrator's Guide

27 Before you begin To complete this task, you must know the IBM Unica Hosted Services user name and password that IBM assigned to your hosted account. Receiving the user name and password is part of the account startup process. You must have the appropriate access permissions and know how to create system users and data sources in the IBM UnicaMarketing Platform. About this task Note: If your installation contains multiple partitions, you must complete this task for each partition. You cannot share system users across partitions. Procedure 1. Create a platform data source to contain the user name and password that is required to access IBM Unica Hosted Services. For best results and easier maintenance, name this data source UNICA_HOSTED_SERVICES. Configure this data source as follows. For Data Source Login, enter the user name that you received from IBM during account startup. For Data Source Password, enter the password that you received IBM during account startup. 2. Specify the data source in the emessage configuration. Use the amdatasourceforacctcredentials configuration property. The configuration property is at emessage > partitions > partition[n] > hostedaccountinfo > amdatasourceforacctcredentials. By default, the specified data source is UNICA_HOSTED_SERVICES. 3. Specify a system user to access IBM Unica Hosted Services. You can specify an existing user or create a user. In the emessage configuration, use the amuserforacctcredentials configuration property. The configuration property is at emessage > partitions > partition[n] > hostedaccountinfo > amuserforacctcredentials. By default, the specified user is asm_admin. 4. Add the data source that is configured in Step 1 to the system user specified in Step 3. What to do next You must restart the web application server for the configuration changes to take effect. Related concepts: Default upload connection by explicit FTP on page 12 Confirmation for system configurations on page 35 Chapter 3. Connections to hosted services 23

28 Configuring the addresses used to connect to IBM Unica Hosted Services To ensure proper connection to IBM Unica Hosted Services, you must enter the addresses as values for configuration properties in the emessage configuration. The connection addresses that you enter depend on whether you are connecting to the IBM U.S. data center or to the IBM data center in the United Kingdom. Consult with IBM to confirm which data center your hosted account uses. For more information about how to configure connection information, see Configuring addresses for connecting to IBM Unica Hosted Services. Configuring addresses for connecting to IBM Unica Hosted Services To ensure proper connection to IBM Unica Hosted Services, you must enter the addresses as values for configuration properties in the emessage configuration. The connection addresses that you enter depend on whether you are connecting to the IBM U.S. data center or to the IBM data center in the United Kingdom. Before you begin Consult with IBM to confirm which data center your hosted account uses. Procedure In IBM UnicaMarketing Platform, navigate to Settings > Configuration. Inthe emessage configuration, navigate to the following emessage configuration properties and confirm or update the connection settings, depending on data center your account uses. Use the default settings if your account connects to the U.S. data center. v emessage > servercomponentsandlocations > hostedservices> uihostname The default is em.unicaondemand.com. To connect to the IBM data center in the United Kingdom, change this value to em-eu.unicaondemand.com. v emessage > servercomponentsandlocations > hostedservices> datahostname The default is em.unicaondemand.com. To connect to the IBM data center in the United Kingdom, change this value to em-eu.unicaondemand.com. v emessage > servercomponentsandlocations > hostedservices> ftphostname The default is ftp-em.unicaondemand.com. To connect to the IBM data center in the United Kingdom, change this value to ftp-em-eu.unicaondemand.com. What to do next If you change a configuration property, restart the web application server to apply the changes. Related concepts: Default upload connection by explicit FTP on page IBM Unica emessage: Startup and Administrator's Guide

29 Configuring secure communication for hosted Communications between the marketer and IBM Unica Hosted Services occur over Secure Sockets Layer (SSL). You must change the web application server configuration to use SSL. Making the required changes requires using the Java keytool utility. Configuring the secure communication involves the following actions. v Generate a trusted keystore. v Obtain a digital certificate from IBM Unica Hosted Services. v Add the trusted keystore to the web application server. v Import the IBM Unica Hosted Services digital certificate into the trusted keystore. The exact steps and sequence required to configure SSL depend on the type and version of web application server (WebSphere or WebLogic) on which you deployed IBM UnicaMarketing Platform and IBM UnicaCampaign. For WebLogic, see Configuring SSL when using WebLogic on page 26. For WebSphere, see Configuring SSL when using IBM WebSphere on page 29. Generating a trusted keystore Follow this procedure to create an identity keystore and a trusted keystore for configuring IBM UnicaeMessage to communicate with IBM Unica Hosted Services over SSL. You add the keystores to the web application server when you configure SSL. About this task IBM uses the following sample values in the procedures contained in this section. v Identity keystore: IBMUnicaClientIdentity.jks v Alias for the identity keystore: IBMUnicaClientIdentity v Password (-storepass) for the identity keystore: clientpwd v The security key (-keypass) for the identity keystore: clientpwd v Certificate based on the identity keystore: ClientCertificate.cer v Trusted keystore: IBMUnicaTrust.jks v Password (-storepass) for the trusted keystore: trustpwd The actual values that you enter must be specific to your installation. To complete steps in this procedure, run the Java keytool utility from the command line. Procedure 1. Generate an identity keystore. Use the genkey command, as shown in the following example. The example creates an identity keystore named IBMUnicaClientIdentity.jks. You can use a different name for the identity keystore that you create. Chapter 3. Connections to hosted services 25

30 keytool -genkey -alias IBMUnicaClientIdentity -keyalg RSA -keystore <IBMUnicaClientIdentity.jks> -keypass <clientpwd> -validity dname "CN=hostName, O=myCompany" -storepass <clientpwd> Note the following. v v You use the values for alias, keystore, keypass, and storepass later in this procedure and when you configure SSL in the web application server. For WebSphere 6.0, the keystore password (-storepass) and the key password (-keypass) must be the same. v In the distinguished name (-dname) the common name (CN) is the same as the host name used to access IBM Unica Marketing. For example, if the URL for IBM Unica Marketing is then the CN is hostname.example.com. The CN portion of the distinguished name is the only required portion; Organization (O) and Organizational Unit (OU) are not required. 2. Generate a certificate based on the identity keystore. Use the export command, as shown in the following example. The example generates a certificate named ClientCertificate.cer. You can use a different name for the certificate that you create. The values for keystore, storepass, and alias must match the values you specified for the identity keystore. keytool -export -keystore <IBMUnicaClientIdentity.jks> -storepass <clientpwd> -alias IBMUnicaClientIdentity -file <ClientCertificate.cer> 3. Generate the trusted keystore. Use the import command, as shown in the following example. The example generates a trusted keystore named IBMUnicaTrust.jks. You can use a different name for the trusted keystore that you create. keytool import -alias IBMUnicaClientIdentity -file <ClientCertificate.cer> -keystore <IBMUnicaTrust.jks> -storepass <trustpwd> Type Y when prompted to trust the certificate. What to do next Note the values that you defined for the following variables. Your values can be different from the values given in the example. v alias (in the example: IBMUnicaClientIdentity) v identity keystore (in the example: IBMUnicaClientIdentity.jks) v v storepass (in the example: trustpwd) The storepass value for the trusted keystore can be different from the storepass value for the identity keystore and certificate. keystore (in the example: IBMUnicaTrust.jks) Depending on your web application server, you also specify the identity keystore. You specify these installation-specific values when you configure SSL on the web application server for your IBM Unica Marketing installation. Configuring SSL when using WebLogic This section describes the steps required to configure SSL if you deploy IBM Unica Marketing components on Oracle WebLogic. This change is required to allow emessage components that operate inside Campaign to communicate with IBM Unica Hosted Services over SSL. 26 IBM Unica emessage: Startup and Administrator's Guide

31 About this task For specific guidance regarding navigation and working with the Oracle WebLogic user interface, consult the documentation for the specific Oracle WebLogic version you are using. Procedure Complete the following tasks. v Modify the WebLogic startup script v Modify the WebLogic configuration v Obtain a digital certificate from IBM Unica Hosted Services v Create a trusted keystore and import the IBM digital certificate Modifying the WebLogic startup script If you deployed Campaign on WebLogic, you must modify the WebLogic startup script and the WebLogic configuration for SSL so that WebLogic recognizes and accepts secure communication between locally installed emessage components and IBM Unica Hosted Services. Procedure Add the following arguments to the JAVA_OPTIONS in the WebLogic startup script. v -Dweblogic.security.SSL.allowSmallRSAExponent=true v WebLogic version 12c or higher: -Dweblogic.security.SSL.protocolVersion=TLS1 All previous versions: -Dweblogic.security.SSL.nojce=true Modify the WebLogic configuration You must change the SSL configuration in WebLogic. Procedure Use the WebLogic console to make the following change in the WebLogic SSL configuration for your domain. Change the Hostname Verification setting to None. Obtain a certificate from IBM Unica Hosted Services To configure SSL communication, you must download a digital certificate from IBM Unica Hosted Services. The certificate details are saved to a file with the.cer extension that you can import into the web application server keystore. About this task You lose access to IBM Unica Hosted Services when your existing SSL certificate expires. Use this procedure to download a new certificate. Procedure 1. In Internet Explorer, log into the address for IBM Unica Hosted Services that has been configured for your hosted account. v For the US data center, go to v For the UK data center, go to Chapter 3. Connections to hosted services 27

32 The login attempt results in a failed login, but allows you to use the browser to submit the certificate request. 2. Click the lock icon and select View Certificate. 3. Select the Details tab and select Copy to File. Save the file with a.cer extension to a location that is accessible to the web application server. The file that you create is the digital certificate that you insert into the keystore on the web application server. For example, save the certificate as IBMHosted.cer. Create a trusted keystore for WebLogic and import the IBM certificate For Weblogic, you must create a trusted keystore that accepts the IBM certificate. Before you begin Before you begin, use a web browser to download the IBM Unica Hosted Services digital certificate and save it as a.cer file. For example, the certificate can be named IBMHosted.cer (your file name can be different). For additional details, see Obtain a certificate from IBM Unica Hosted Services on page 27. About this task IBM uses the following sample values in the procedures contained in this section. v Identity keystore: IBMUnicaClientIdentity.jks v Password for the identity keystore: clientpwd v Trusted keystore: IBMUnicaTrust.jks v Alias for the trusted keystore: IBMUnicaHostedIdentity v Password (-storepass) for the trusted keystore: trustpwd v Digital certificate (-file) from IBM: IBMHosted.cer The actual values that you enter must be specific to your installation. To complete steps in this procedure, run the Java keytool utility from the command line. Procedure 1. Generate a trusted keystore for WebLogic. For details, see Generating a trusted keystore on page 25. You specify the identity keystore and the trusted keystore in the WebLogic configuration. 2. Use the import command in the keytool utility to add the IBM Unica Hosted Services certificate to the trusted keystore created in Step 1, as shown in the following example. Use the digital certificate that you downloaded from IBM. In this procedure, you also define an alias for the trusted keystore. keytool -import -alias IBMUnicaHostedIdentity -file <IBMHosted.cer> -keystore <IBMUnicaTrust.jks> -storepass <trustpwd> Type Y when prompted to trust the certificate. 3. In the WebLogic administration console, configure the keystores for the server. To specify the configuration rules, select the option for Custom Identity and Custom Trust keystores from the available choices. For the Custom Identity, you specify the identity keystore. For the Custom Trust, you specify the trusted keystore. 28 IBM Unica emessage: Startup and Administrator's Guide

33 For example, in the administration console, specify the following (using the example values from the trusted keystore you created in Step 1). v For the Identity: specify the identity keystore and associated password. For example, IBMUnicaClientIdentity.jks and clientpwd. v For the Trust: specify the trusted keystore and associated password. For example, IBMUnicaTrust.jks and trustpwd. Specify the full path to both keystores. 4. Restart WebLogic. WebLogic does not implement the configuration changes until you restart the web application server. 5. To test the SSL connection, log in to IBM UnicaCampaign and access various messaging features menus. Confirm that you can create , landing pages, and mailings. Configuring SSL when using IBM WebSphere This section describes the general steps required to configure SSL if you have deployed IBM Unica Marketing components on IBM WebSphere. This change is required to allow emessage components that operate inside Campaign to communicate with IBM Unica Hosted Services over SSL. Before you begin Before you begin, you will need to know the value for the configuration property uihostname. The value for uihostname is the URL for IBM Unica Hosted Services. For details, see Configuring the addresses used to connect to IBM Unica Hosted Services on page 24. About this task You must access the WebSphere security console to modify settings for SSL certificate and key management. This task requires a restart of the Campaign web application server to implement the changes. If you have deployed Campaign on WebSphere version 6.1 or higher, you must modify the WebSphere security configuration to retrieve the signer certificate from IBM Unica Hosted Services and add it to the WebSphere trust store. If you receive an error message indicating that your current signer certificate has expired, delete the current certificate and add a new one. For specific guidance regarding navigation and working with the WebSphere user interface, consult the documentation for the specific IBM WebSphere version you are using. Note: Before you begin, confirm that fixpack has been installed on the WebSphere sever. For more information, see IBM WebSphere Application Server V7.0 requires fixpack or higher on page 30. Procedure 1. Generate a trusted keystore. For additional details, see Generating a trusted keystore on page 25. To configure SSL, you need to specify the values that you define for the following variables. The values shown are for example only. Your values can be different. v alias: UnicaClientIdentity (example) Chapter 3. Connections to hosted services 29

34 v keystore: IBMUnicaTrust.jks (example) v storepass: trustpwd (example) 2. Select the new keystore in the WebSphere security console. For example, if you followed the example in Step 1, select IBMUnicaTrust.jks. 3. Obtain a security certificate from IBM Unica Hosted Services and import it into WebSphere, as described in the following steps. a. In the WebSphere security console, navigate to SSL certificate and key management > Key stores and certificates > NodeDefaultTrustStore > Signer certificates. Select the option to Retrieve from port. b. Configure WebSphere to establish a test connection to retrieve the signer certificate from IBM Unica Hosted Services. Enter the following values for the IBM Unica Hosted Services signer certificate. v Host The value that is defined for emessage >servercomponentsandlocations > hostedservices >uihostname v Port 443 v SSL configuration for outbound connection NodeDefaultSSLSettings v Alias The value that you entered for Host When you have finished, WebSphere communicates with IBM Unica Hosted Services to retrieve the information required to create a signer certificate for IBM Unica Hosted Services. 4. After WebSphere finishes creating the signer certificate, select the new certificate in the security console. The web application server uses the new certificate when establishing connections to IBM Unica Hosted Services. 5. Restart WebSphere WebSphere does not implement the configuration changes until you restart the web application server. IBM WebSphere Application Server V7.0 requires fixpack or higher If you plan to use the IBM WebSphere Application Server V7.0 to deploy any IBM Unica Marketing products, you must apply Fix Pack 17 (also referred to as Version ) or higher to address a security issue. This applies to all WebSphere Application Server 7.0 packages, including the version that is bundled with some IBM Unica Marketing products. You can obtain Fix Pack 17 or higher here: Note that on that page, you must select the correct Fix Pack before you download. For additional information about supported WebSphere versions for deploying IBM Unica Marketing products, see the Recommended Software Environments and Minimum System Requirements document for each product. 30 IBM Unica emessage: Startup and Administrator's Guide

35 Chapter 4. Response and Contact Tracker operation The Response and Contact Tracker (RCT) is installed in your local environment and communicates with IBM Unica Hosted Services to retrieve and process data for contacts, delivery, and recipient responses, such as link clicks and opens. The RCT must be running in order to retrieve link tracking and delivery notification data from IBM Unica Hosted Services. The Response and Contact Tracker (RCT) is installed in your local environment and communicates with IBM Unica Hosted Services to retrieve and process data for contacts, delivery, and recipient responses, such as link clicks and opens. The RCT must be running in order to retrieve link tracking and delivery notification data from IBM Unica Hosted Services. You can start the RCT in either of the following ways. v Start the RCT manually. v Start the RCT as a service Important: You must start the RCT manually the first time you use emessage, even if you registered the RCT as a service. You must restart the RCT when you make changes to configuration properties for emessage. You can restart the RCT at any time, even if you have configured it to run as a service. IBM Unica Hosted Services continues to store tracking data if the RCT is shut down or restarting. When it resumes operation, the RCT downloads the queued information. Related concepts: Data download frequency and port setting on page 22 Manual start of the RCT About starting the RCT automatically as a service on page 32 Manual start of the RCT Run the rct script to start and stop the Response and Contact Tracker (RCT). To start the RCT manually, run the rct script in the bin directory in your emessage installation. For more information about this script, see The RCT script on page 56. Related concepts: Chapter 4, Response and Contact Tracker operation Manual operation of the Response and Contact Tracker To operate the Response and Contact Tracker (RCT) manually, run the rct script in the bin directory in your emessage installation. IBM Corporation 1999,

36 Procedure v To start the RTC, run the rct script in the bin directory under your emessage installation, as follows. rct start v To stop the RCT, run the rct script as follows. rct stop What to do next For more information about this script, see The RCT script on page 56. Stopping the Response and Contact Tracker Stop the Response and Contact Tracker (RCT) by running the rct script. Procedure In the bin directory under your emessage installation, run the rct script as follows. rct stop What to do next IBM Unica Hosted Services continues to store tracking and response data it receives until you restart the RCT. For more information about this script, see The RCT script on page 56 About starting the RCT automatically as a service You can configure the Response and Contact Tracker (RCT) to start automatically by adding it as a service. Register the RCT service by running the MKService_rct script that is provided with the emessage software. When you run the MKService_rct script to register the service, you must use the rct script to manually start the RCT the first time. After that, the RCT restarts automatically every time you reboot the operating system of the machine where you installed the RCT. After configuring the RCT service, you can prevent the RCT from starting automatically by running the MKService_rct script with the -remove option. Related concepts: Chapter 4, Response and Contact Tracker operation, on page 31 Related tasks: Adding the Response and Contact Tracker as a service on page 33 Removing the Response and Contact Tracker service on page 33 Related reference: The MKService_rct script on page IBM Unica emessage: Startup and Administrator's Guide

37 Adding the Response and Contact Tracker as a service You can configure the Response and Contact Tracker (RCT) to start automatically by adding it as a service. About this task Register the RCT service by running the MKService_rct script that is provided with the emessage software. To add the Response and Contact Tracker (RCT) as a service, run the MKService_rct -install script from the bin directory under your emessage installation. The bin directory is created as a subdirectory in the Campaign installation directory when you install or upgrade to the latest version of IBM UnicaCampaign. Procedure To add the Response and Contact Tracker (RCT) as a service, run the MKService_rct -install script from the bin directory under your emessage installation. In UNIX or Linux, run this script with a user that has root permissions or permissions to create daemon processes. In Windows, the name of the service is Response & Contact Tracker. What to do next After you run the MKService_rct script, start the RCT manually with the rct script. You manually restart the RCT only once. After you start the RCT manually the first time, the RCT restarts automatically every time you restart the operating system of the computer where you installed the RCT. After configuring the RCT service, you can prevent the RCT from starting automatically by running the MKService_rct script with the -remove option. Related concepts: About starting the RCT automatically as a service on page 32 Related reference: The MKService_rct script on page 57 The RCT script on page 56 Removing the Response and Contact Tracker service If you have installed the Response and Contact Tracker (RCT) as a service, the RCT restarts each time you restart the system where you installed the RCT. To prevent the RCT from restarting automatically, you must remove the Response and Contact Tracker (RCT) service. Procedure To remove the RCT as a service, run the MKService_rct script with the -remove option. From a Windows command line, in your IBM Unica Marketing home directory, run Chapter 4. Response and Contact Tracker operation 33

38 emessage\bin\mkservice_rct.bat -remove. In UNIX or Linux, in your IBM Unica Marketing home directory, run emessage/bin/mkservice_rct.sh -remove. What to do next For more information about this script, see The MKService_rct script on page 57 Related concepts: About starting the RCT automatically as a service on page IBM Unica emessage: Startup and Administrator's Guide

39 Chapter 5. Startup verification To ensure access to all hosted features, test the configurations and connections for your Campaign and emessage installations after you enable emessage, expand your emessage installation, or upgrade the Campaign installation. Verify configurations and connections after you do any of the following. v Enable emessage for the first time v Upgrade your current IBM UnicaCampaign installation v Add a new partition to the emessage configuration maintained in IBM UnicaMarketing Platform Confirmation for system configurations To ensure that startup preparations are complete, confirm that the following configuration properties are set and that the settings meet the requirements for your emessage and Campaign installations. Configuration property Campaign partitions partition[n] emessage emessagepluginjarfile Setting Complete path to the location of the plug-in file that operates as the Recipient List Uploader (RLU). Enter the full local directory path in the file system for the computer that hosts the Campaign web application server. Campaign partitions partition[n] server internal emessageinstalled emessage servercomponentsandlocations hostedservices uihostname The IBM installer populates this setting automatically for the default partition when you run the installer. For other partitions, configure this property manually. Indicates that emessage is installed. Set this property to Yes in each partition where you want to enable emessage, including the default partition. When you set this property to Yes, emessage features become available in the Campaign interface. Address to IBM Unica Hosted Services for all communication except uploading lists. The default setting is em.unicaondemand.com, for the US data center. If you are connecting to the data center in the United Kingdom, change this value to em-eu.unicaondemand.com. emessage servercomponentsandlocations hostedservices datahostname The address for the connection that emessage uses for uploading metadata that is related to recipient lists to IBM Unica Hosted Services. The default setting is em.unicaondemand.com, for the US data center. If you are connecting to the data center in the United Kingdom, change this value to em-eu.unicaondemand.com. emessage servercomponentsandlocations hostedservices ftphostname The address for the connection that emessage uses for uploading recipient list data (except list metadata) to IBM Unica Hosted Services. The default setting is ftp-em.unicaondemand.com, for the US data center. If you are connecting to the data center in the United Kingdom, change this value to ftp-em-eu.unicaondemand.com. IBM Corporation 1999,

40 Configuration property emessage partitions partition[n] hostedaccountinfo amuserforacctcredentials emessage partitions partition[n] hostedaccountinfo amdatasourceforacctcredentials emessage partitions partition [n] < datasources systemtables type emessage partitions partition [n] < datasources systemtables schemaname emessage partitions partition [n] < datasources systemtables jdbcclassname emessage partitions partition [n] < datasources systemtables jdbcuri Setting The IBM Unica Marketing user that references the data source that contains the IBM Unica Hosted Services access credentials. You configure this value when you create a system user to access the resources that are hosted by IBM. The Marketing Platform data source that contains the IBM Unica Hosted Services login credentials. You configure this value when you create a system user to access the resources that are hosted by IBM. Type of database that hosts the system tables. Provide the correct value for your database. Name of the database schema for the system tables. Set to the appropriate schema name for your database. JDBC driver for system tables. Provide the correct value for your environment. JDBC connection URI for system tables. Provide the correct value for your environment. Specify the database type, database driver, host, port, and database name. For example:jdbc:oracle:thin:@yourdb.example.com:1234:dbname Consult your database documentation for specific instructions regarding how to construct the JDBC URL. The value that you enter must exactly match the value that is defined in your Campaign web server. emessage partitions partition [n] < datasources systemtables asmuserfordbcredentials emessage partitions partition [n] < datasources systemtables asmdatasourcefordbcredentials The IBM Unica Marketing user that references the data source that contains the system tables login credentials. You create this user when you configure access to the local emessage system tables. The Marketing Platform data source that contains login credentials to the database that contains the system tables. You create this data source when you create a user to access the emessage system tables. Related concepts: Chapter 6, Configurations for IBM emessage, on page 39 Related tasks: Configuring the system user that accesses IBM Unica Hosted Services on page 22 Configuring access to local emessage system tables on page 43 Testing upload to IBM Unica Hosted Services To test the ability to upload data to IBM Unica Hosted Services from your local environment, run the rlu script in check mode. 36 IBM Unica emessage: Startup and Administrator's Guide

41 Procedure In the bin directory under your emessage installation, run the rlu script in either of the following ways. v rlu -c v rlu --check Related reference: The RLU script on page 55 Testing download from IBM Unica Hosted Services To test the ability to download information from IBM Unica Hosted Services, run the rct script in check mode. Procedure In the bin directory under your emessage installation, run the rct script as follows. rct check Related reference: The RCT script on page 56 Testing the connection to the hosted messaging interface IBM hosts the messaging interface from its data centers in the US and UK. Test the connection to the hosted mailing interface by attempting to access an emessage feature. Procedure Log in to IBM Unica Marketing and select emessage mailings from the Campaign menu. If the connection to the emessage user interface is established correctly, the emessage mailings page opens and displays a list of mailings and related mailing characteristics. If the connection to the user interface is not established properly, you see an error. Chapter 5. Startup verification 37

42 38 IBM Unica emessage: Startup and Administrator's Guide

43 Chapter 6. Configurations for IBM emessage The IBMMarketing Platform provides various configuration properties to modify the behavior and appearance of IBMeMessage. Some configuration properties are set during installation. You can change configuration properties at any time. After you update the Campaign or emessage configurations, you must restart the Response and Contact Tracker (RCT) and the web application server that hosts Campaign. Characteristic or feature Enable or disable emessage in the Campaign partition. Configuration property (including path) Campaign partitions partition[n] server internal See Campaign partitions partition[n] server internal on page 45. Characteristics of recipient lists. Campaign partitions partition[n] emessage See Campaign partitions partition[n] emessage on page 43. URLs required to connect to IBM Unica Hosted Services. emessage servercomponentsandlocations hostedservices See emessage servercomponentsandlocations hostedservices on page 48. Database and account access credentials for connecting to IBM Unica Hosted Services. emessage partitions partition[n] hostedaccountinfo See emessage partitions partition[n] hostedaccountinfo on page 48 Database access and schema settings for the emessage system tables. emessage partitions partition[n] datasources systemtables See emessage partitions partition[n] datasources systemtables on page 49 Location of a script that runs in response to the actions or status of the Recipient List Uploader. (optional) emessage partitions partition[n] recipientlistuploader See emessage partitions partition[n] recipientlistuploader on page 52 Settings related to data download, processed by the Response and Contact Tracker (RCT). emessage partitions partition[n] responsecontacttracker See emessage partitions partition[n] responsecontacttracker on page 53 Copyright IBM Corp. 1999,

44 Characteristic or feature Configuration property (including path) Support for presenting lists of personalized data in emessage based on dimension tables in Campaign partitions partition[n] emessage Campaign. oltdimtablesupport See Configuring support for dimension tables. Support for tracking mailing execution history. See emessage partitions partition[n] responsecontacttracker on page 53 emessage partitions partition[n] responsecontacttracker See the enableexecutionhistorydatatracking parameter. For more information about working with configuration properties, see the IBM Marketing Platform Administrator's Guide. Related concepts: Confirmation for system configurations on page 35 What you can configure for emessage You can configure the following aspects of the local IBM UnicaeMessage installation. Characteristic or feature Enable or disable emessage in the Campaign partition. Configuration property (including path) Campaign partitions partition[n] server internal See Campaign partitions partition[n] server internal on page 45. Characteristics of recipient lists. Campaign partitions partition[n] emessage See Campaign partitions partition[n] emessage on page 43. URLs required to connect to IBM Unica Hosted Services. emessage servercomponentsandlocations hostedservices See emessage servercomponentsandlocations hostedservices on page 48. Database and account access credentials for connecting to IBM Unica Hosted Services. emessage partitions partition[n] hostedaccountinfo See emessage partitions partition[n] hostedaccountinfo on page 48 Database access and schema settings for the emessage system tables. emessage partitions partition[n] datasources systemtables See emessage partitions partition[n] datasources systemtables on page 49 Location of a script that runs in response to the actions or status of the Recipient List Uploader. (optional) emessage partitions partition[n] recipientlistuploader See emessage partitions partition[n] recipientlistuploader on page IBM Unica emessage: Startup and Administrator's Guide

45 Characteristic or feature Settings that are related to data download, processed by the Response and Contact Tracker (RCT). Configuration property (including path) emessage partitions partition[n] responsecontacttracker See emessage partitions partition[n] responsecontacttracker on page 53 Support for presenting lists of personalized data in emessage based on dimension tables in Campaign. See Configuring support for dimension tables on page 42. Campaign partitions partition[n] emessage oltdimtablesupport What to restart after configuration changes After making changes to the Campaign or emessage configurations, you must restart the Response and Contact Tracker (RCT) and the web application server that hosts Campaign. For information about how to restart the RCT, see The RCT script on page 56. For information about how to restart your web application server, consult the documentation for your web application server. Configuring access to additional mailing execution history You can request that IBM provide more data for mailing execution history. Access to additional mailing execution history data is available by request from IBM and by updating the emessage configuration. Data for mailing execution history is recorded your local emessage system tables in the UACE_ExecHistory table to describe completed mailing runs. Before you begin To download additional mailing run data, you must update the configuration property enableexecutionhistorydatatracking. By default, enableexecutionhistorydatatracking is not exposed in the emessage configuration properties. You can display this configuration property in your local emessage installation by running the switch_config_visibility.bat script, which is in the emessage\tools directory. About this task The following types of records are available if you install or upgrade to Campaign version v Message subject line v From address v User that updated the mailing v Document description v Mailing save date Chapter 6. Configurations for IBM emessage 41

46 Procedure 1. Request access to additional mailing execution history data. To request access, contact your IBM representative at 2. Update the emessage configuration. Configure the following configuration property. Affinium emessage partitions partition1 responsecontacttracker enableexecutionhistorydatatracking Set enableexecutionhistorydatatracking to True. What to do next You can query the emessage system tables to retrieve mailing run information from the UACE_ExecHistory table. For more information about the emessage system tables, see the IBM Unica Marketing System Tables and Data Dictionary. Related tasks: Accessing the configuration parameters for implicit FTP upload on page 15 Configuring support for dimension tables To support certain features that are provided by advanced scripts for ., the oltdimtablesupport configuration property must be set to True. When you upgrade to Campaign or later, you must change the value of this configuration setting manually. About this task emessage provides advanced scripts to create messages that display lists of personalized information. These lists require associating dimension tables created in Campaign with an Output List Table (OLT) that defines the recipient list. Output List Tables are created in the emessage schema. The oltdimtablesupport configuration property controls support for creating dimension tables in the emessage schema. When the value for this property is set to True, an OLT can use information provided in a dimension table. Prior to Campaign 8.5.0, the default value for oltdimtablesupport was False, not True. Complete the following steps to update the oltdimtablesupport property. For more information about how marketers use advanced scripts to create data tables, see the IBM UnicaeMessage User's Guide. Procedure 1. Go to Settings > Configuration > Campaign > Partitions > partition[n] > emessage 2. Click Edit Settings and set the value of the oltdimtablesupport property to True. 42 IBM Unica emessage: Startup and Administrator's Guide

47 Configuring access to local emessage system tables emessage components must be able to access the emessage system tables in the Campaign schema. You must create and configure a system user that can access the system tables automatically. The system user that was configured during the installation of Campaign already has the necessary access to the Campaign schema. About this task Note: If your installation contains multiple partitions, you must complete this task for each partition. You cannot share system users across partitions. If you want to use a different system user to access the emessage system tables, you must create a new system user in the Marketing Platform and create new platform data source with access to the Campaign schema. Procedure 1. In the emessage configuration, specify a system user that accesses the database that hosts the Campaign schema. You can create a new user or specify an existing user. The system user that you set up for Campaign already has access to the Campaign schema. Use the configuration property emessage > partitions > partition [n] < datasources > systemtables > asmuserfordbcredentials. By default the specified user is asm_admin. 2. In the emessage configuration, specify the data source that is configured to contain the user name and password that is required to access the database that hosts the Campaign schema. You can use the data source that was created to access the Campaign schema when you installed Campaign. Use the configuration property emessage > partitions > partition [n] < datasources > systemtables > amdatasourcefordbcredentials. Related concepts: Confirmation for system configurations on page 35 Configuration properties for emessage You access emessage configuration properties from the Settings menu in the Marketing Platform. Properties for configuring emessage are contained in the Campaign and emessage configuration categories. To access the configuration properties, navigate to Settings > Configurations. The Configurations page lists all of the available configuration properties for your IBM Unica Marketing installation. Campaign partitions partition[n] emessage Define properties in this category to define characteristics of recipient lists and specify the location of resources that upload the lists to IBM Unica Hosted Services. emessagepluginjarfile Description Chapter 6. Configurations for IBM emessage 43

48 Complete path to the location of the file that operates as the Recipient List Uploader (RLU). This plug-in to Campaign uploads OLT data and associated metadata to the remote services hosted by IBM. The location that you specify must be the full local directory path in the file system for the computer that hosts the Campaign web application server. The IBM installer populates this setting automatically for the default partition when you run the installer. For other partitions, you must configure this property manually. Because there is only one RLU for each emessage installation, all partitions must specify the same location for the RLU. Do not change this setting unless IBM instructs you to do so. Default value No default value defined. Valid Values Full local directory path to where you installed the Campaign web server. defaultseedinterval Description The number of messages between seed messages if defaultseedtype is Distribute list. Default value 1000 defaultseedtype Description The default method that emessage uses to insert seed addresses into a recipient list. Default value Distribute IDS Valid Values v Distribute IDS - Distribute IDs evenly, based on the size of the recipient list and the number of seed addresses available, inserts seed addresses at equal intervals throughout the entire recipient list. v Distribute list - Insert seed address for every defaultseedinterval IDs in main list. Inserts the entire list of available seed addresses at specified intervals throughout the recipient list. You must specify the interval between insertion points. olttablenameprefix Description Used in the generated schema for the output list table. You must define this parameter. Default value OLT Valid Values 44 IBM Unica emessage: Startup and Administrator's Guide

49 The prefix can contain no more than 8 alphanumeric or underscore characters, and must start with a letter. oltdimtablesupport Description This configuration parameter controls the ability to add dimension tables to output list tables (OLT) created in the emessage schema. Dimension tables are required to use advanced scripting for to create data tables in messages. The default setting is False. You must set this property to True so that marketers can create dimension tables when they use the emessage process to define a recipient list. For more information about creating data tables and working with advanced scripts for , see the IBM UnicaeMessage User's Guide. Default value False Valid Values True False Campaign partitions partition[n] server internal Properties in this category specify integration settings and the internalid limits for the selected Campaign partition. If your Campaign installation has multiple partitions, set these properties for each partition that you want to affect. internalidlowerlimit Description The internalidupperlimit and internalidlowerlimit properties constrain the Campaign internal IDs to be within the specified range. Note that the values are inclusive: that is, Campaign may use both the lower and upper limit. Default value 0 (zero) internalidupperlimit Description The internalidupperlimit and internalidlowerlimit properties constrain the Campaign internal IDs to be within the specified range. The values are inclusive: that is, Campaign may use both the lower and upper limit. If Distributed Marketing is installed, set the value to Default value emessageinstalled Description Indicates that emessage is installed. When you select yes, emessage features are available in the Campaign interface. Chapter 6. Configurations for IBM emessage 45

50 The IBM installer sets this property to yes for the default partition in your emessage installation. For additional partitions where you have installed emessage, you must configure this property manually. Default value no Valid Values yes no interactinstalled Description After installing the Interact design environment, this configuration property should be set to yes to enable the Interact design environment in Campaign. If you do not have Interact installed, set to no. Setting this property to no does not remove Interact menus and options from the user interface. To remove menus and options, you must manually unregister Interact using the configtool utility. Default value no Valid Values yes no Availability This property is applicable only if you have installed Interact. MO_UC_integration Description Enables integration with Marketing Operations for this partition. If you plan to set any of the following three options to Yes, you must set MO_UC_integration to Yes. For more information about configuring this integration, see the IBM UnicaMarketing Operations and Campaign Integration Guide. Default value no Valid Values yes no MO_UC_BottomUpTargetCells Description Allows bottom-up cells for Target Cell Spreadsheets on this partition. When set to Yes, both top-down and bottom-up target cells are visible, but bottom-up target cells are read only. Note that MO_UC_integration must be enabled. For more information about configuring this integration, see the IBM UnicaMarketing Operations and Campaign Integration Guide. Default value 46 IBM Unica emessage: Startup and Administrator's Guide

51 no Valid Values yes no Legacy_campaigns Description When the MO_UC_integration property is set to Yes, the Legacy_campaigns property enables access to campaigns created before enabling integration, including campaigns created in Campaign 7.x and linked to Plan 7.x projects. For more information about configuring this integration, see the IBM UnicaMarketing Operations and Campaign Integration Guide. Default value no Valid Values yes no IBM Unica Marketing Operations - Offer integration Description Enables the ability to use Marketing Operations to perform offer lifecycle management tasks on this partition. (MO_UC_integration must be enabled. Also, Campaign integration must be enabled in Settings > Configuration > Unica > Platform.) For more information about configuring this integration, see the IBM UnicaMarketing Operations and Campaign Integration Guide. Default value no Valid Values yes no UC_CM_integration Description Enables Digital Analytics online segment integration for a Campaign partition. If you set this option to yes, the Select process box in a flowchart will provide the option to select Digital Analytics Segments as input. To configure the integration for each partition, choose Settings > Configuration > Campaign partitions partition[n] Coremetrics. Default value no Valid Values yes no Chapter 6. Configurations for IBM emessage 47

52 emessage servercomponentsandlocations hostedservices Define properties to specify the URLs for connecting to IBM Unica Hosted Services. emessage uses separate connections for uploading recipient lists, metadata that describes recipient lists, and for general communication sent to the hosted environment. You must change the default values if you are connecting to IBM Unica Hosted Services through the data center that is established by IBM in the United Kingdom. Consult IBM to determine the data center to which you are connected. uihostname Description The address that emessage uses for all communication to IBM Unica Hosted Services, except uploading recipient lists and related metadata. Default value em.unicaondemand.com If you are connecting to the UK data center, change this value to em-eu.unicaondemand.com. datahostname Description The address that emessage uses for uploading metadata that is related to recipient lists to IBM Unica Hosted Services. Default value em.unicaondemand.com If you are connecting to the UK data center, change this value to em-eu.unicaondemand.com. ftphostname Description The address that emessage uses for uploading recipient list data (except list metadata) to IBM Unica Hosted Services. Default value ftp-em.unicaondemand.com If you are connecting to the UK data center, change this value to ftp-em-eu.unicaondemand.com. emessage partitions partition[n] hostedaccountinfo Define properties in this category to define user credentials for the database that contains account information that is required to access IBM Unica Hosted Services. Values that you specify here must be defined as user settings in the Marketing Platform. amuserforacctcredentials Description 48 IBM Unica emessage: Startup and Administrator's Guide

53 Use this property to specify the Marketing Platform user that contains a Marketing Platform data source that specifies the account access credentials that are required to access IBM Unica Hosted Services. Default value asm_admin Valid Values Any Marketing Platform user. amdatasourceforacctcredentials Description Use this property to specify the Marketing Platform data source that defines login credentials for IBM Unica Hosted Services. Default value UNICA_HOSTED_SERVICES Valid Values A data source that is associated with the user you specify in amuserforacctcredentials emessage partitions partition[n] datasources systemtables This category contains configuration properties that define the schema, connection settings, and login credentials for the database that contains the emessage system tables in your local network environment. type Description Type of database that hosts the emessage system tables. Default value No default value defined. You must define this property. Valid Values v SQLSERVER v ORACLE9 v ORACLE10 (also used to indicate Oracle 11 databases) v DB2 schemaname Description Name of the database schema for the emessage system tables. This name is the same as the schema name for the Campaign system tables. You must include this schema name when you reference system tables in scripts. Default value dbo Chapter 6. Configurations for IBM emessage 49

54 jdbcbatchsize Description The number of execution requests JDBC runs on the database at a time. Default value 10 Valid Values An integer greater than 0. jdbcclassname Description JDBC driver for system tables as defined in your Campaign web server. Default value No default value defined. You must define this property. jdbcuri Description JDBC connection URI for system tables as defined in your Campaign web server. Default value No default value defined. You must define this property. asmuserfordbcredentials Description Use this property to specify a system user that is allowed to access the emessage system tables. Default value No default value defined. You must define this property. Valid Values Any user that is defined in the Marketing Platform. This user is typically the name of the system user for Campaign amdatasourcefordbcredentials Description Use this property to specify the data source that defines login credentials for the database that contains the emessage system tables. This data source can be the same as the data source for the Campaign system tables. Default value UA_SYSTEM_TABLES Valid Values A Marketing Platform data source that is associated with the IBM Unica Marketing user you specify for asmuserfordbcredentials. 50 IBM Unica emessage: Startup and Administrator's Guide

55 The data source specifies a database user and credentials that are used to access the emessage system tables. If the default schema for the database user does not contain the system tables, you must specify the system table schema in the JDBC connection that is used to access the system tables. poolacquireincrement Description When the database connection pool runs out of connections, the number of new connections emessage creates for the system tables. emessage creates new connections up to the number specified in poolmaxsize. Default value 1 Valid Values An integer greater than 0. poolidletestperiod Description The number of seconds emessage waits between testing idle connections to the emessage system tables for activity. Default value 100 Valid Values An integer greater than 0. poolmaxsize Description The maximum number of connections emessage makes to the system tables. A value of zero (0) indicates that there is no maximum. Default value 100 Valid Values An integer greater than or equal to 0. poolminsize Description The minimum number of connections emessage makes to the system tables. Default value 10 Valid Values An integer greater than or equal to 0. Chapter 6. Configurations for IBM emessage 51

56 poolmaxstatements Description The maximum number of statements that emessage stores in the PrepareStatement cache per connection to the system tables. Setting poolmaxstatements to zero (0) disables statement caching. Default value 0 Valid Values An integer equal to or greater than 0. timeout Description The number of seconds emessage maintains an idle database connection before it drops the connection. If poolidletestperiod is greater than 0, emessage tests all idle, pooled, but unchecked-out connections, every timeout number of seconds. If poolidletestperiod is greater than timeout, the idle connections are dropped. Default value 100 Valid Values An integer equal to or greater than 0. emessage partitions partition[n] recipientlistuploader This configuration category contains an optional property for the location of a user-defined script that runs in response to the actions or status of the Recipient List Uploader. pathtotriggerscript Description You can create a script that triggers an action in response to the upload of a recipient list to IBM Unica Hosted Services. For example, you can create a script to send an alert to the list designer when the list upload completes successfully. If you define a value for this property, emessage passes status information about the Recipient List Uploader to the specified location. emessagetakes no action if you leave this property blank. Default value No default value defined. Valid Values Any valid network path. 52 IBM Unica emessage: Startup and Administrator's Guide

57 emessage partitions partition[n] responsecontacttracker Properties in this category specify behavior for the Response and Contact Tracker (RCT). The RCT retrieves and processes data for contacts, delivery, and recipient responses, such as link clicks and opens. pausecustomerpremisestracking Description emessage stores contact and response data in a queue in IBM Unica Hosted Services. Define this property to instruct the RCT to temporarily stop retrieving data from IBM Unica Hosted Services. When you resume tracking, the RCT downloads the accumulated data. Default value False Valid Values True False waittimetocheckfordataavailability Description The RCT periodically checks for new data that is related to contacts or recipient responses. Specify how often, in seconds, the RCT checks for new data in IBM Unica Hosted Services. The default value is 300 seconds, or every 5 minutes. Default value 300 Valid Values Any integer greater than 1. perfloginterval Description Define a value for this property to specify how often the RCT logs performance statistics to a log file. The value that you enter determines the number of batches between log entries. Default value 10 Valid Values An integer greater than 0. enableseparatepartialresponsedatatracking Description This property determines whether emessage forwards partial response data to the tracking tables in your local emessage installation. emessage requires the Mailing Instance ID and Message Sequence Number to properly attribute responses. When you enable separate partial Chapter 6. Configurations for IBM emessage 53

58 response data tracking, emessage places the incomplete responses in separate local tracking tables where you can review them or process them further. Default value True Valid Values True False 54 IBM Unica emessage: Startup and Administrator's Guide

59 Chapter 7. Utilities for emessage The RLU script emessage provides several scripts that you use to administer emessage functions. You can use the software utilities described in this section for a variety of startup and administration functions. In addition to software utilities used with IBM UnicaMarketing Platform, IBM UnicaeMessage uses utilities are specific to emessage and you use them only to manage emessage components. For more information about other utilities available for your IBM Unica Marketing installation, see the IBM UnicaMarketing Platform Administrator's Guide. Use the RLU script to check the status of the Recipient List Uploader (RLU). Note: You cannot use this script to start or stop the RLU. Use this script only to check the status of the connection between the RLU and IBM Unica Hosted Services. The RLU script is in your IBM Unica Marketing home directory at emessage > bin. The emessage directory is a subdirectory in the Campaign directory. In UNIX or Linux environments, run the script as rlu.sh. In Windows, run the script from the command prompt as rlu.bat. Syntax rlu -c --check [-h] Commands -c, --check Check that the RLU is correctly configured, and that is it connected to IBM Unica Hosted Services. Options -h, --help Display syntax for the script Example In a Linux environment, determine whether the RLU is connected to IBM Unica Hosted Services. rlu.sh --check Depending on the status of your system, the output of this command might look like this sample. Copyright IBM Corp. 1999,

60 Configuring Data Source [systemtables]... Testing configuration for partition partition1 Testing connectivity for partition partition1 Testing user accessibility for partition partition1 Succeeded. List uploader config and connectivity test succeeded for partition partition1 Related tasks: Testing upload to IBM Unica Hosted Services on page 36 The RCT script Use the RCT script to run or stop the Response and Contact Tracker (RCT) or to determine whether it can successfully connect to the hosted mailing environment in IBM Unica Hosted Services. This script is in the bin directory under your emessage installation. The emessage directory is a subdirectory in the Campaign directory. In UNIX or Linux environments, run the script as rct.sh. In Windows, run the script from the command prompt as rct.bat. Syntax rct [ start stop check ] Commands start Start the RCT stop Stop the RCT Options check Check the ability of the RCT to connect to IBM Unica Hosted Services. Examples v To start the RCT on Windows. rct.bat start v To stop the RCT on Windows. rct.bat stop v In a Linux environment, determine whether the RCT can connect to IBM Unica Hosted Services. rct.sh check If the RCT can successfully connect to IBM Unica Hosted Services, the output of this command might appear as follows. 56 IBM Unica emessage: Startup and Administrator's Guide

61 C:/Unica/emessage/bin>rct check Testing config and connectivity for partition partition1 Succeeded Partition: partition1 - Hosted Services Account ID: asm_admin Related tasks: Adding the Response and Contact Tracker as a service on page 33 Testing download from IBM Unica Hosted Services on page 37 The MKService_rct script Use this script to add or remove the Response and Contact Tracker (RCT) as a service. Adding the RCT as a service restarts the RCT every time you restart the operating system of the computer where you installed the RCT. Removing the RCT as a service prevents the RCT from restarting automatically. This script is in the bin directory under your emessage installation. In UNIX or Linux environments, run MKService_rct.sh. with a user that has root permissions or permissions to create daemon processes. In Windows, run the script from the command prompt as MKService_rct.bat. Syntax MKService_rct -install MKService_rct -remove Commands -install Add the RCT as a service -remove Remove the RCT service Examples v To add the RCT as a Windows service. MKService_rct.bat -install v To remove the RCT service on UNIX or Linux. MKService_rct.sh -remove Related concepts: About starting the RCT automatically as a service on page 32 Related tasks: Adding the Response and Contact Tracker as a service on page 33 Chapter 7. Utilities for emessage 57

62 The configtool utility The properties and values on the Configuration page are stored in the Marketing Platform system tables. The configtool utility imports and exports configuration settings to and from the Marketing Platform system tables. When to use configtool You might want to use configtool for the following reasons. v To import partition and data source templates supplied with Campaign, which you can then modify and duplicate using the Configuration page. v To register (import configuration properties for) IBM Unica Marketing products, if the product installer is unable to add the properties to the database automatically. v To export an XML version of configuration settings for backup or to import into a different installation of IBM Unica Marketing. v To delete categories that do not have the Delete Category link. You do this by using configtool to export your configuration, then manually deleting the XML that creates the category, and using configtool to import the edited XML. Important: This utility modifies the usm_configuration and usm_configuration_values tables in the Marketing Platform system table database, which contain the configuration properties and their values. For best results, either create backup copies of these tables, or export your existing configurations using configtool and back up the resulting file so you have a way to restore your configuration if you make an error when using configtool to import. Valid product names The configtool utility uses product names as parameters with the commands that register and unregister products, as described later in this section. With the release of IBM Unica Marketing, many product names changed. However, the names recognized by configtool did not change. The valid product names for use with configtool are listed below, along with the current names of the products. Product name Marketing Platform Campaign Distributed Marketing emessage Interact Optimize Marketing Operations CustomerInsight NetInsight PredictiveInsight Leads Name used in configtool Manager Campaign Collaborate emessage interact Optimize Plan Insight NetInsight Model Leads 58 IBM Unica emessage: Startup and Administrator's Guide

63 Syntax configtool -d -p "elementpath" [-o] configtool -i -p "parent ElementPath" -f importfile [-o] configtool -x -p "elementpath" -f exportfile configtool -r productname -f registrationfile [-o] configtool -u productname Commands -d -p "elementpath" Delete configuration properties and their settings, specifying a path in the configuration property hierarchy. The element path must use the internal names of categories and properties, which you can obtain by going to the Configuration page, selecting the wanted category or property, and looking at the path displayed in parentheses in the right pane. Delimit a path in the configuration property hierarchy using the character, and surround the path with double quotation marks. Note the following. v Only categories and properties within an application may be deleted using this command, not whole applications. Use the -u command to unregister a whole application. v To delete categories that do not have the Delete Category link on the Configuration page, use the -o option. -i -p "parentelementpath" -fimportfile Import configuration properties and their settings from a specified XML file. To import, you specify a path to the parent element under which you want to import your categories. The configtool utility imports properties under the category you specify in the path. You can add categories at any level below the top level, but you cannot add a category at same level as the top category. The parent element path must use the internal names of categories and properties, which you can obtain by going to the Configuration page, selecting the desired category or property, and looking at the path displayed in parentheses in the right pane. Delimit a path in the configuration property hierarchy using the character, and surround the path with double quotation marks. You can specify an import file location relative to the tools/bin directory or you can specify a full directory path. If you specify a relative path or no path, configtool first looks for the file relative to the tools/bin directory. By default, this command does not overwrite an existing category, but you can use the -o option to force an overwrite. Chapter 7. Utilities for emessage 59

64 -x -p "elementpath" -fexportfile Export configuration properties and their settings to an XML file with a specified name. You can export all configuration properties or limit the export to a specific category by specifying a path in the configuration property hierarchy. The element path must use the internal names of categories and properties, which you can obtain by going to the Configuration page, selecting the wanted category or property, and looking at the path displayed in parentheses in the right pane. Delimit a path in the configuration property hierarchy using the character, and surround the path with double quotation marks. You can specify an export file location relative to the current directory or you can specify a full directory path. If the file specification does not contain a separator (/ on Unix, / or \ on Windows), configtool writes the file to the tools/bin directory under your Marketing Platform installation. If you do not provide the xml extension, configtool adds it. -r productname -f registrationfile Register the application. The registration file location may be relative to the tools/bin directory or may be a full path. By default, this command does not overwrite an existing configuration, but you can use the -o option to force an overwrite. The productname parameter must be one of those listed above. Note the following. v When you use the -r option, the registration file must have <application> as the first tag in the XML. Other files may be provided with your product that you can use to insert configuration properties into the Marketing Platform database. For these files, use the -i option. Only the file that has the <application> tag as the first tag can be used with the -r option. v The registration file for the Marketing Platform is named Manager_config.xml, and the first tag is <Suite>. To register this file on a new installation, use the populatedb utility, or rerun the Marketing Platform installer as described in the IBM Unica Marketing Platform Installation Guide. v After the initial installation, to reregister products other than the Marketing Platform, use configtool with the -r option and -o to overwrite the existing properties. -u productname Unregister an application specified by productname. You do not have to include a path to the product category; the product name is sufficient. The productname parameter must be one of those listed above. This removes all properties and configuration settings for the product. Options -o When used with -i or -r, overwrites an existing category or product registration (node). 60 IBM Unica emessage: Startup and Administrator's Guide

65 When used with -d allows you to delete a category (node) that does not have the Delete Category link on the Configuration page. Examples v Import configuration settings from a file named Product_config.xml located in the conf directory under the Marketing Platform installation. configtool -i -p "Affinium" -f Product_config.xml v Import one of the supplied Campaign data source templates into the default Campaign partition, partition1. The example assumes that you placed the Oracle data source template, OracleTemplate.xml, inthetools/bin directory under the Marketing Platform installation. configtool -i -p "Affinium Campaign partitions partition1 datasources" -f OracleTemplate.xml v Export all configuration settings to a file named myconfig.xml located in the D:\backups directory. configtool -x -f D:\backups\myConfig.xml v Export an existing Campaign partition (complete with data source entries), save it to a file named partitiontemplate.xml, and store it in the default tools/bin directory under the Marketing Platform installation. configtool -x -p "Affinium Campaign partitions partition1" -f partitiontemplate.xml v Manually register an application named productname, using a file named app_config.xml located in the default tools/bin directory under the Marketing Platform installation, and force it to overwrite an existing registration of this application. configtool -r product Name -f app_config.xml -o v Unregister an application named productname. configtool -u productname To back up configuration settings To backup emessageand Campaign configuration settings, use the configtool utility to export a copy of current configuration settings from IBM UnicaMarketing Platform to a file. About this task For details about how to use the configtool utility, including explanation of syntax and parameters, see The configtool utility on page 58. Performing the backup with configtool exports all of the current property settings in the emessage category in the configurations. When performing the backup, specify a file name for the exported.xml file and note the location to which you save it. For example, In Windows: configtool.bat -x -p emessage -f emessageproperties.xml In UNIX or Linux: Chapter 7. Utilities for emessage 61

66 configtool.sh -x -p emessage -f emessageproperties.xml By default, the.xml file is exported to the MANAGER_HOME/xml directory. 62 IBM Unica emessage: Startup and Administrator's Guide

67 Chapter 8. About troubleshooting emessage Log files for emessage IBM UnicaeMessage provides various tools and techniques that you can use to investigate issues related to your Campaign and emessage installations. IBM Unica Marketing provides several log files that you can review to monitor your emessage installation and investigate issues. emessage log file This log contains the following types of information regarding information downloaded from IBM Unica Hosted Services. v general mailing information v mailing instance ID v link click data v data for bounced Located in the logs directory under your emessage installation. emessage temporary files This directory contains the data being uploaded. Located in the temp directory under your emessage installation. Campaign log files Using log4j with emessage You can review log files in the following locations for information related to mailing-related activity in Campaign. v Campaign\partitions\<partitionN>\logs Various log files relating to flowchart runs, including log entries from any emessage process contained in the flowchart. v Campaign\logs This directory contains campaignweb.log that contains information about upload activity performed by the Recipient List Uploader. emessage uses the Apache log4j utility for logging configuration, debugging, and error information related to the Response and Contact Tracker (RCT) and the Recipient List Uploader (RLU). For information about changing the system log settings, see: v The comments in the log4j.properties file. v The log4j documentation on the Apache web site: log4j/1.2/manual.html IBM Corporation 1999,

68 Using log4j with the Recipient List Uploader When you run the Recipient List Uploader (RLU) utility from the command line, it uses default logger settings. To change those settings, you modify the emsg_rlu_log4j.properties file. In the conf directory under your emessage installation directory, copy example_emsg_log4j.properties to emsg_rlu_log4j.properties. Modify emsg_rlu_log4j.properties as instructed by the comments in that file. When the RLU is invoked automatically by a flowchart, it uses the Campaign web application's logging, which is configured in campaign_log4j.properties under your Campaign installation directory. Using log4j with the Response and Contact Tracker When you run the Response and Contact Tracker (RCT) utility, it uses default logger settings. To change those settings, you modify the emsg_rct_log4j.properties file. In the conf directory under your emessage installation directory, copy example_emsg_log4j.properties to emsg_rct_log4j.properties. Modify emsg_rct_log4j.properties as instructed by the comments in that file. 64 IBM Unica emessage: Startup and Administrator's Guide

69 Chapter 9. Management of user access to messaging features Campaign and emessage use roles and permissions provided by the IBM UnicaMarketing Platform to control user access to messaging features in emessage and Campaign. You must have permissions in IBM UnicaMarketing Platform and Campaign to make the required changes. You must also be familiar with how to configure roles and permissions in the Marketing Platform and how to define security policies for Campaign. To conduct marketing campaigns, marketers access emessage mailing features in IBM UnicaCampaign. To create personalized communications and hosted landing pages, marketers work with features and content in the emessage Document Composer. For general information about how to configure roles, permissions, and policies, see the sections of the IBM UnicaMarketing Platform Administrator's Guide that describe how to manage security in the IBM UnicaMarketing Platform and IBM UnicaCampaign. Related concepts: Role and policy assignment for mailing access Messaging permissions in Campaign on page 68 Messaging permissions for emessage on page 73 Role and policy assignment for mailing access To log in to the IBM Unica Marketing system, marketers enter a system user name and password. The permissions that are granted to the system user determine how the marketer can access mailing features, personalized communications, and content in emessage and Campaign. Permissions are associated with roles that are defined in the IBM UnicaMarketing Platform. To control access to mailing features in Campaign, you can define roles within one or more security policies. All system users that access mailing features, communications, and content must be assigned an emessage role within a Campaign security policy. Through the policy, you selectively apply permissions for mailing features in Campaign and communications and content in the emessage Document Composer. Users that access mailing features must also be assigned the emessage user and admin roles. These roles are separate from the emessage roles available in Campaign security policies. Related concepts: Messaging permissions for emessage on page 73 Chapter 9, Management of user access to messaging features About roles and permissions in Marketing Platform and Campaign on page 66 Messaging permissions in Campaign on page 68 IBM Corporation 1999,

70 About roles and permissions in Marketing Platform and Campaign Roles in Marketing Platform and Campaign are a configurable collection of permissions. For each role in Marketing Platform and Campaign, you can specify permissions that control access to the application. You can use the default roles or create new roles. The set of available permissions is defined by the system; you cannot create a new permission. About role assignment Generally, you should give users roles with permissions that reflect the functions that users perform in your organization when they use IBM Unica Marketing. You can assign roles to a group or to an individual user. The advantage of assigning roles by group is that you can assign a combination of roles to the group, and if you later want to change that combination, you can do it in one place rather than having to do it multiple times for multiple users. When you assign roles by group, you add and remove users from your groups to control user access. How the system evaluates roles If a user has multiple roles, the system evaluates permissions from all those roles together. The ability to perform a function on a particular object is then granted or denied based on the aggregated permissions from all roles. In the case of Campaign, the ability to perform a function on a particular object is granted or denied based on the security policy of the object. Related concepts: Role and policy assignment for mailing access on page 65 emessage roles in the Global Policy on page 67 About security policies Security policies are the "rule books" that govern security in Campaign; they are consulted each time a user performs an action in the application. Security policies are created per partition (there is no sharing of security policies across partitions). A partition in Campaign can have multiple security policies. A security policy consists of multiple roles that you define. Each role contains a set of permissions that determine the actions users can perform and the objects that they can access. You can assign users to a role directly, or assign groups to a role (users in those groups would be assigned the role). When you create an object such as a campaign or offer in the top-level folder, you apply a security policy to the object. In addition, when you create a top-level folder, you apply a security policy to the folder, and any objects or subfolders you create within that folder inherit the security policy that you applied to the folder. Applying security policies to objects or folders allows you to separate the objects in Campaign for use by different groups of users. For example, you could configure your security policies so that users belonging to one policy cannot access or even view objects that are associated with other policies. 66 IBM Unica emessage: Startup and Administrator's Guide

71 You can create your own security policies or use the default global security policy included with Campaign. The global security policy Campaign includes a default global security policy that you can use as is or modify to suit the needs of your organization. If you choose not to create your own security policies, the global security policy is applied by default to the objects that you create in Campaign. You can use the global policy in addition to your own policies, or use your own policies exclusively. You cannot delete the global policy, even if it is not in use. Any security policies that you create exist under the global security policy. Under the global policy, you could create a separate security policy for employees of each division in your organization. The global security policy contains six pre-defined roles; you can add roles to the global policy if needed. You cannot delete the pre-defined roles, but you can modify their permissions. The pre-defined roles are: v Folder Owner - All permissions enabled v Object Owner - All permissions enabled v Admin - All permissions enabled. The default user asm_admin is assigned this role. v Execute - All permissions enabled v Design - Read and write permissions on most objects. Cannot schedule flowcharts or sessions. v Review - Read-only permissions The global security policy applies to all users through the Owner and Folder Owner roles, including users who have not been assigned to any other specific role in the global policy. Because the global policy always applies, it can be used, for example, to globally deny permissions to a role. Related concepts: emessage roles in the Global Policy emessage roles in the Global Policy In addition to the pre-defined Campaign roles, the Global Policy includes several roles that are specific to emessage. The Global Policy includes the following emessage roles. v emsg_admin - Able to access to all mailing features, all content, and all documents. v emsg_execute - Able to access to all mailing features, all content, and all documents. v emsg_design - Able to access to all content, all documents, and most mailing features. However, it is explicitly not granted permission to send production mailings. Chapter 9. Management of user access to messaging features 67

72 v emsg_review - Able only to view content and documents, and has limited permissions for working with mailings. It is explicitly not granted permission to add, edit, or delete mailings. It is allowed to view and send test and production mailings. Note: emessage does not support the Owner and Folder Owner roles that are created by default for Campaign. Related concepts: About roles and permissions in Marketing Platform and Campaign on page 66 The global security policy on page 67 Permissions for mailings in Campaign on page 70 Permissions for the Digital Assets category on page 71 Permissions for the Documents category on page 72 Messaging permissions in Campaign Campaign controls user access to mailing features by enabling or disabling specific permissions that are defined in roles that are assigned to a user or group. These roles are associated with one or more security policies. You can define multiple Campaign security policies and assign multiple roles to each policy. Each combination of policy and roles can define a specific set of permissions. For more information about how to manage security permissions, including sample security scenarios, see the IBM UnicaCampaign Administrator s Guide. Under Roles and Permissions for the IBM UnicaMarketing Platform, you assign user permissions for mailing features and content in the Campaign section, as follows. 1. Define user roles. System defined user roles for emessage are created by default under the Global Policy. You can also define custom roles and add them to the Global Policy or to other policies that you define. 2. Define security policies and add user roles to the policies. The Global Policy is defined by default. You can define additional policies for Campaign. 3. Define specific permissions for each role in each policy. You can define additional policies and custom roles with various sets of permissions for more control over access to mailing features in Campaign and the emessage Document Composer. Changes to permissions, roles, and policies are applied when the user logs in to IBM Unica Marketing. After you assign or change mailing permissions for a user, the user must log out and then log back in for the changes to be observed. Related concepts: Chapter 9, Management of user access to messaging features, on page 65 Role and policy assignment for mailing access on page IBM Unica emessage: Startup and Administrator's Guide

73 Making roles and permissions available Depending on your IBM UnicaMarketing Platform installation, the administrative controls that are required to define and apply roles and permissions might not be immediately visible. You can make the necessary controls visible by accessing the emessage Document Composer or a mailing in Campaign. About this task Perform the following procedure if you do not see all of the following permissions under the Campaign Global Policy. v Permissions for mailings in the Campaigns category v Permissions for the Content Library in the Digital Assets category v Permissions for emessage documents in the Documents category Procedure 1. Log in to IBM Unica Marketing. If you have multiple users that are configured, log in as a user with the most limited permissions. For example, log in as a user with only View permissions. 2. Navigate to Campaign > emessage Documents to access the Document Composer. Wait for the Document Composer to finish loading. 3. Navigate to Settings > User Roles and Permissions > Campaign > partition [n] > Global Policy When prompted, confirm that you want to leave the Document Composer by leaving the page. 4. Click Add Roles and Assign Permissions. The following emessage roles are visible. v emsg_admin v emsg_execute v emsg_design v emsg_review 5. Click Save and Edit Permissions. Mailing permissions are visible in the Campaigns, Digital Assets, and Documents categories. For more information about the specific permissions that are available, see the following topics. Related concepts: Permissions for mailings in Campaign on page 70 Permissions for the Digital Assets category on page 71 Permissions for the Documents category on page 72 How Campaign evaluates permissions When a user performs a task or tries to access an object, Campaign performs the following steps: 1. Identifies all groups and roles to which this user belongs within the global security policy. A user can belong to one, many, or no roles. A user belongs to the Owner role if they own an object; they belong to the Folder Owner role if Chapter 9. Management of user access to messaging features 69

74 they own the folder in which an object resides. A user belongs to other roles only if they have been specifically assigned to that role (either directly or because they belong in a group assigned to that role). 2. Identifies whether the object being accessed has been assigned to a custom-defined policy, if any exist. If so, the system then identifies all groups and roles to which the user belongs within this custom policy. 3. Aggregates the permissions for all roles to which the user belongs, based on results from steps 1 and 2. Using this composite role, the system evaluates the permissions for the action as follows: a. If any roles have Denied permission for this action, then the user is not allowed to perform it. b. If no roles have Denied permission for this action, then it checks to determine whether any roles have Granted permission for this action. If so, the user is allowed to perform the action. c. If neither a nor b is true, the user is denied the permission. Definition of permission states For each role, you can specify which of the pre-defined permissions are granted, not granted, or denied. These states have the following meanings. v Granted - indicated with a green checkmark. Explicitly grants permission to perform this particular function as long as none of the user's other roles explicitly denies permission. v Denied - indicated with a red "X". Explicitly denies permission to perform this particular function, regardless of any other of the user's roles which might grant permission. v Not Granted - indicated with a shaded gray "X". Does not explicitly grant nor deny permission to perform a particular function. If this permission is not explicitly granted by any of a user's roles, the user is not allowed to perform this function. Permissions for mailings in Campaign In Campaign, you create, configure, run, and monitor emessage mailings with controls on emessage mailing tabs. You manage each mailing on a separate tab. The following permissions control user access to the emessage mailing tabs. They are in the Campaigns category. Permission View Mailings Edit Mailings Delete Mailings Add Mailings Description Allows a user to view an emessage mailing tab in a campaign. The user cannot edit or change the mailing. Allows a user to configure or change an emessage mailing tab in a campaign. Allows a user to remove an emessage mailing from a campaign. Allows a user to create a mailing in a campaign. 70 IBM Unica emessage: Startup and Administrator's Guide

75 Permission Send production mailing Description Allows a user to initiate a production run of the mailing, enable a mailing for transactional , or schedule a production mailing run. Production mailings can include many messages. messages are sent to every individual identified as a production recipient on the recipient list that is associated with the mailing. Execute test run Allows a user to initiate a test run of the mailing. Test mailings usually involve a few messages. During a test run, an message is sent to every address identified as a test recipient on the recipient list that is associated with the mailing. Related concepts: emessage roles in the Global Policy on page 67 Related tasks: Making roles and permissions available on page 69 Permissions for the Digital Assets category The Digital Assets permissions control user access to content elements in the emessage Content Library, and to folders and subfolders in which they are stored. The Content Library is a repository for content elements (also called digital assets) that are used in communications that users create in the emessage Document Composer. Permissions View emessage digital assets Create new digital assets in the emessage content library Edit existing digital assets in the emessage content library Delete digital assets from the emessage content library Move digital assets from one folder to another Description Allows a user to open content elements to view properties and preview the content that can be added to a personalized communication. Allows a user to create a content element and add it to the Content Library. Allows a user to open and edit existing content elements. Allows a user to remove a content element from the Content Library. Allows a user to move content elements within the Content Library. Moving a content element requires assigning this permission to the source and destination folders. Related concepts: emessage roles in the Global Policy on page 67 Related tasks: Making roles and permissions available on page 69 Chapter 9. Management of user access to messaging features 71

76 Permissions for the Documents category The permissions in the Documents category control user access to create, edit, and manage personalized communications in the emessage Document Composer. Permissions View emessage documents Create new emessage documents Edit existing emessage documents Delete emessage documents Publish emessage document, making content available on the public Internet Copy emessage documents from one folder to another Move emessage documents from one folder to another Description Allows a user to view a document that is used to create an or hosted landing page. Allows a user to create a new personalized communication. Allows a user to change an existing personalized communication. Allows a user to remove a personalized communication. Allows a user to publish a personalized communication. Publishing a communication makes the document and all added content available for use in an emessage mailing. Allows a user to copy a personalized communication between folders in the Content Library. Copying a communication requires assigning this permission to the source and destination folders. Allows a user to move a personalized communication from one folder to another folder in the Content Library. Moving a communication requires assigning this permission to the source and destination folders. Related concepts: emessage roles in the Global Policy on page 67 Related tasks: Making roles and permissions available on page 69 Permissions for the Administration category The permissions in the Administration category of the Campaign Global Policy provide emessage administrators with access to settings that control which domains are made available to emessage users. The permissions allow the administrator to restrict the list of domains that the user can select as a From: domain in an communication that is created in the emessage Document Composer. To be able to control the list of domains available to emessage users, an administrator must have permission to Configure Domains. Permission to configure domains allows an administrator user to access the Policy Settings section of the emessage Settings window. The Policy Settings section does not display unless Configure Domains permission is explicitly granted to the administrator as part of the Campaign Global Policy. 72 IBM Unica emessage: Startup and Administrator's Guide

77 Permissions Configure Domains Description Controls access to the Policy Settings section of the emessage Settings page. If the administrator role is not granted permission to configure domains, the administrator cannot see the Policy Settings section. Messaging permissions for emessage IBM UnicaeMessage controls access to mailing features outside of the mailing tab in Campaign through the following pre-defined security roles. v emessage_admin v emessage_user Users must have both roles to have access to emessage mailing features. Related concepts: Role and policy assignment for mailing access on page 65 Chapter 9, Management of user access to messaging features, on page 65 Related tasks: Assigning emessage roles Assigning emessage roles To provide a user with full access to emessage mailing features, assign the pre-defined emessage roles to the user. Procedure 1. In IBM UnicaMarketing Platform, navigate to Settings > User roles & Permissions > emessage > partition [n] > emessage_admin. 2. Click Assign Users. 3. Select the user from the list of available users. Click Add to assign the role to the user. 4. Repeat steps 1-3 for the emessage_user role. 5. Save changes. Related concepts: Messaging permissions for emessage Controlling domains and short link domains Upon request, IBM configures one or more domains for your hosted account. IBM can also assign domains that marketers use to create shortened links in various types of messages. System administrators with appropriate permissions control the messaging domains that are available to marketers. About this task Depending on your business requirements, it might be desirable to restrict the list of messaging domains that are available to specific marketers. emessage administrators restrict the list of available domains through security policies that Chapter 9. Management of user access to messaging features 73

78 are applied to folders in the Document Composer. The ability of marketers to create and edit communications depends on the security policy that is applied to the folder that contains the communication. emessage administrators with appropriate permissions can control the list of domains that emessage users can use as the From: domain in communications. Administrators can also control the list of short link domains that is presented to marketers when they configure communications that use shortened links. For example, you can specify which short link domains are available when marketers add a social sharing link to marketing messages. emessage administrators use the Policy Settings page to grant permissions to use specific messaging domains. Access to the Policy Settings page is controlled by the Administration permissions that are granted through the Campaign Global Policy. Only administrators with the appropriate permissions can restrict access to domains through the Policy Settings page. Procedure 1. In the Settings menu, select emessage Settings. If you have the appropriate administrative permissions, the Policy Settings section displays on the emessage Settings page. 2. Click Display a list of policies and their settings. A list of security policies that are configured for your emessage installation displays. 3. Click a security policy that is associated with the system user whose messaging domain access you want to control. The Domains section displays the domains that are configured for your hosted messaging account. The Short Link Domains section displays the short link domains that are configured for your hosted messaging account. v In either section, click Use all domains to allow users that are associated with the policy to use any of the domains that IBM configured for your hosted account. This option is the default. v Click Use specific domains to select specific domains. Results Note: If you select Use specific domains, you must update the domain permissions when you register a new or short link domain for your hosted messaging account. The system does not assign permissions for the new domain automatically. For the users associated with the security policy, only the selected domains appear as an option for the From: address in communications. For communications that require shortened links, marketers can choose only from the specific short link domains that you select. After you save the new settings, the Document Composer updates the domain options that are available to marketers. For more information about how emessage marketers create and manage communications, see the IBM emessage User s Guide. 74 IBM Unica emessage: Startup and Administrator's Guide

79 Maintenance of hosted domains To send messages you must register at least one domain with IBM. To improve message deliverability, IBM works with you to establish and maintain the reputation of the domain with leading Internet Service Providers (ISPs) around the world. You can establish multiple domains with IBM. When you configure the header in an communication, the system populates the From address with the domain that you have registered with IBM. If you establish multiple domains with IBM, the available domains display in a drop-down list. System administrators can control the domains that marketers can select or modify. You can request that IBM add or delete domains established for your hosted messaging account. After IBM completes the change, the system updates the list of available domains. The change is reflected in the list of available domains the next time you create or edit an communication. Note: domain changes for your account do not update communications that you created before the change request. To change the domain for a communication created previously, you must reopen the communication and update the domain selection. For more information about how to register an domain with IBM, see IBM Enterprise Marketing Management (EMM) Domain Name Options for . To request changes related to your domains, contact the Account Services team at [email protected]. Configuring default sender address and display names For each domain that you have registered with IBM, you can define a default address and a default friendly name. The combination of address or friendly name and the domain appears as the From: address for the messages that you send. About this task Administrators can configure the default sender and display names on the Domain Settings page. The domain settings are part of the emessage Settings interface. Access to the Domain Settings page is controlled by the Administration permissions that are granted through the Campaign Global Policy. Only administrators with the appropriate permissions can restrict access to domains through the Policy Settings page. Procedure 1. Go to Settings > emessage Settings. In the Domain Settings section, click Display the list of domain settings. The Domain Settings page lists the default display names and addresses associated with domains that are registered to your hosted account. The list includes only the domains that your user permissions allow you to modify. The Default column indicates the combination of display name, address, and domain that appears as the default From address for new communications. Chapter 9. Management of user access to messaging features 75

80 2. Click Edit. The Edit Domain Settings window opens. The Domain Name column lists the available domains. You can do the following for any of the domains. v In the From Display Name column, enter a friendly name to appear as the default for an domain in the list. v In the From Address column, enter the local part of the address to appear as the default for an domain in the list. 3. Optionally, in the Default column, select one combination of display name address, and domain to appear as the default From address for new communications. If you do not select a default, the system uses the first domain on the list to create the default From address for new communications. 4. Save changes. Results The new address settings apply to all new communications that you create. The settings do not change address information for communications that you created previously. To update previous communications, you must reopen and modify each communication. Controlling access to the list of sent messages emessage provides a list of messages that have been sent from your emessage environment. Because the list includes links to messaging configurations, your security plans might require that you restrict access to the list. About this task The list of messages is presented on the emessage Mailings page. By default, all users in your Campaign and emessage environment can see the list of sent messages. However, when you enable the access restriction, you can prevent specific users from seeing the menu option to open the page that contains the list. Restricting access to the list of sent messages affects all partitions in your Campaign installation. If your Campaign installation includes multiple partitions, you must update user permissions separately in each partition to explicitly grant or deny permission to access the list. Controlling who can access the list of sent messages requires a series of tasks to change user permissions and the system configuration. Task Identify users who can access the list of messages. At first, all users are granted access. Identify users who are not allowed to access the list of messages. Enable the access restriction. More information Granting access to the list of sent messages on page 77 Denying access to the list of sent messages on page 77 Enabling the restriction to the sent message list on page IBM Unica emessage: Startup and Administrator's Guide

81 Results When you complete these tasks, the emessage Mailings option on the Campaign menu is visible only to users with roles that explicitly grant permission to access the list of mailings. Granting access to the list of sent messages If you restrict access to the list of sent messages, you must specifically grant access to users who must access the list. About this task Users access the list of sent messages by clicking the emessage Mailings link on the Campaign menu. You can grant a user access to the list of all sent messages by assigning the user a top-level administrative role that is explicitly granted permission to see the emessage Mailings link. The default top-level roles include Admin, Execute, Design, and Review. Permissions that you grant through the top-level roles apply to all objects in the partition. Procedure 1. Go to Settings > User Roles and Permissions > Campaign > partition (n). 2. Click Save and Edit Permissions. A list of permissions for the partition opens. The available top-level roles are listed across the top to the page. 3. In the Administration section, explicitly grant the View Mailing List Page permission to every role. Results When you enable access restrictions for the list of sent messages, users with roles that are explicitly granted the View Mailing List Page permission can see the emessage Mailings link on the Campaign menu. What to do next Create a role to deny access to the list of sent messages. Related tasks: Denying access to the list of sent messages Enabling the restriction to the sent message list on page 78 Denying access to the list of sent messages If you restrict access to the list of sent messages, you must specifically deny access to users who must not be allowed to access the list. About this task Users access the list of sent messages by clicking the emessage Mailings link on the Campaign menu. You can prevent a user from accessing the list of all sent messages by assigning the user a top-level administrative role that is explicitly denied permission to see the emessage Mailings link. Chapter 9. Management of user access to messaging features 77

82 The default top-level roles include Admin, Execute, Design, and Review. Permissions that you grant through the top-level roles apply to all objects in the partition. You can create new top-level roles to supplement the default top-level roles. The new roles can grant or deny specific permissions. Procedure 1. Go to Settings > User Roles and Permissions > Campaign > partition (n). The partition <n> page opens. 2. Click Add Role. Assign a name to the role and enter a brief description. Save the changes and return to the partition <n> page. 3. Configure the new role to deny access to the list of sent mailings. a. Click Add Roles and Assign Permissions. The Properties for Administrative Roles page opens. The new role displays in the list of roles. b. Click Save and Edit Permissions. A list of permissions for the partition displays as a matrix of selection icons that indicate the state of each permission for each role. The new role displays next to the other top-level roles across the top to the matrix. c. In the Administration section, explicitly deny the View Mailing List Page permission for the new role. Save changes. 4. Assign the new role to the users that you want to prevent from accessing the mailing list page. a. Go to Settings > Users. Select the user that you want to prevent from accessing the list of sent messages. b. Click Edit Roles. The new role that you created in the previous step (a role that is configured to deny access) appears in the list of Available Roles. c. Move the new role from Available Roles to Roles. Save changes. Results When you enable access restrictions for the list of sent messages, a user that is assigned the new role cannot see the emessage Mailings link. What to do next Update the configuration to enable access restrictions for the list of sent messages. Related tasks: Granting access to the list of sent messages on page 77 Enabling the restriction to the sent message list Enabling the restriction to the sent message list Users access the list of sent messages through the emessage Mailings option on the Campaign menu. If you restrict access to the list of sent messages, the Security Function ID property controls the display of this menu option and, therefore, controls access to the list of sent messages. About this task To restrict access to the list of sent messages, you must update the Security Function ID property in the Marketing Platform configuration. This property applies to all partitions in your Campaign installation. 78 IBM Unica emessage: Startup and Administrator's Guide

83 When you populate the Security Function ID with the correct value, the emessage Mailings option is available to only those users with a role that explicitly grants the View Mailing List Page permission. Users with roles where the View Mailing List Page permission is either denied or not granted, cannot see the emessage Mailings option. Procedure 1. Go to Settings > Configuration > Platform > Platform-wide navigation > Main navigation menu > Campaign > emessage Mailings. Click emessage Mailings to display the configuration settings. 2. Click Edit Settings. 3. In the Security Function ID field, enter Save changes. To see the results of the configuration change, log out of the system and log in again. Results Only users with roles that explicitly grant the View Mailing List Page permission can see the emessage Mailings link to access the list of sent messages. Related tasks: Granting access to the list of sent messages on page 77 Denying access to the list of sent messages on page 77 Permissions for emessage reports Your user permissions determine your ability to view emessage reports. For information about setting permissions to access standard emessage reports, see the section in the IBM Unica EMM Reports Installation and Configuration Guide for reporting and security. Chapter 9. Management of user access to messaging features 79

84 80 IBM Unica emessage: Startup and Administrator's Guide

85 Contacting IBM Unicatechnical support If you encounter a problem that you cannot resolve by consulting the documentation, your company's designated support contact can log a call with IBM Unica technical support. Use the information in this section to ensure that your problem is resolved efficiently and successfully. If you are not a designated support contact at your company, contact your IBM Unica administrator for information. Information to gather Before you contact IBM Unica technical support, gather the following information: v A brief description of the nature of your issue. v Detailed error messages you see when the issue occurs. v Detailed steps to reproduce the issue. v Related log files, session files, configuration files, and data files. v Information about your product and system environment, which you can obtain as described in "System information." System information When you call IBM Unica technical support, you might be asked to provide information about your environment. If your problem does not prevent you from logging in, much of this information is available on the About page, which provides information about your installed IBM Unica applications. You can access the About page by selecting Help > About. If the About page is not accessible, you can obtain the version number of any IBM Unica application by viewing the version.txt file located under the installation directory for each application. Contact information for IBM Unica technical support For ways to contact IBM Unica technical support, see the IBM Unica Product Technical Support website: ( IBM Corporation 1999,

86 82 IBM Unica emessage: Startup and Administrator's Guide

87 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information about the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd , Shimotsuruma, Yamato-shi Kanagawa Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk. IBM Corporation 1999,

88 IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 170 Tracer Lane Waltham, MA U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not 84 IBM Unica emessage: Startup and Administrator's Guide

89 been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs. If you are viewing this information softcopy, the photographs and color illustrations may not appear. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at Notices 85

90 86 IBM Unica emessage: Startup and Administrator's Guide

91

92 Printed in USA