Outbound Upgrade Manual. SDL Tridion Development Lab BV

Transcription

1 Outbound Upgrade Manual SDL Tridion Development Lab BV

2 SDL Tridion Development Lab BV NOTICE: The accompanying software package is confidential and proprietary to SDL Tridion Development Lab BV or its respective licensors. No use or disclosure is permitted other than as set forth by written license with the authorized distributors of SDL Tridion Development Lab BV. Trademarks SDL Tridion, SDL Tridion R5 and SDL Tridion SiteEdit are trademarks of SDL Tridion Development Lab BV or its respective licensors. All other company or product names used herein are trademarks of its respective owners. Additional Licenses Please contact your SDL Tridion sales representative to order additional licenses of SDL Tridion software. offers you a complete overview of SDL Tridion's sales offices and further contact details.

3 Table of contents Preface... 1 Related documents... 2 Chapter 1 Upgrading Outbound Checking changes in prerequisites for Outbound Upgrading Outbound Server Upgrading Outbound database (Microsoft SQL Server) Upgrading Outbound database (Oracle) Uninstalling Outbound 1.3SP Installing Outbound Upgrading Presentation Server Preparing to upgrade Pre-upgrade procedure Upgrading Subscription Management database (Microsoft SQL Server) Upgrading Subscription Management database (Oracle) Upgrading Presentation Server i

4 ii Outbound Upgrade Manual

5 Outbound Upgrade Manual Preface This document tells system administrators how to upgrade from Outbound E- mail 1.3SP1 to Outbound About this guide This manual is for system administrators who have Outbound 1.3SP1 installed on their system and want to upgrade to Outbound Note that upgrading to Outbound requires that you upgrade to SDL Tridion Audience The guide is intended for system administrators responsible for an SDL Tridion installation. 1

6 Related documents This guide is one document from the documentation set for SDL Tridion The full documentation set consists of the following documents, organized by the SDL Tridion 2009 project phase in which they are used: Planning phase The Content Delivery Project Planning Guide (a PDF document) helps project managers prepare for an implementation of Content Delivery. Setup phase The Installation Manual (a PDF document) explains how to get SDL Tridion 2009 modules up and running. The Product Prerequisites (a PDF document) explains which software SDL Tridion 2009 supports or requires. Implementation phase The Content Management Implementation Guide (a PDF document) explains how to set up BluePrint structure, configure security and workflow, and similar broad implementation topics. The Templating Manual (a PDF document) explains how SDL Tridion 2009 templates work, and how to use the Template Builder to create them. The Templating Implementation Manual TOM.NET (a Windows help file) explains how to interact with the.net version of the Tridion Object Model to create Template Building Blocks written in C# or another language supported by.net. This Guide also includes a complete reference of the TOM.NET API. The Templating and Customization Manual TOM (a Windows help file) explains how to interact with the COM+ version of the Tridion Object Model to create Templates written in VBScript or JScript, and how to perform other customizations of the Content Manager. This Guide also includes a complete reference of the TOM API. The Content Delivery Implementation Manual (ASP) (a Windows help file) explains how to implement Content Delivery functionality for an ASP Web site. The Content Delivery Implementation Manual (ASP.NET 5.3) (a Windows help file) explains how to implement Content Delivery functionality for an ASP.NET Web site using the SDL Tridion version 5.3 Content Delivery architecture (supports SDL Tridion R5.3 functionality). The Content Delivery Implementation Manual (ASP.NET 2009) (a Windows help file) explains how to implement Content Delivery functionality for an ASP.NET Web site using the SDL Tridion 2009 Content Delivery architecture (supports SDL Tridion 2009 functionality). The Content Delivery Implementation Manual (JSP) (a Javadoc Web site) explains how to implement Content Delivery functionality for a JSP Web site. The Business Connector Implementation Manual (a PDF document) explains how to implement the Business Connector, which enables external applications to access the Content Manager. 2

7 The Security Manual (a PDF document) explains the minimal user rights and privileges required for the Content Management and Content Delivery system parts to function correctly The Outbound Implementation Guide explains how to configure the product in detail, create Address Books, implement Content Manager security for Outbound , use the available templating frameworks: VBScript (Outbound Script Extension) or.net Compound Templating, implement subscription and tracking, and provides an overview of the Content Delivery APIs. The Outbound Contact Management (.NET) explains how to customize and extend Outbound on the Content Manager using C# or another language supported by.net. The API provides access to the Outbound item types and provides functionality to perform bulk import of Outbound Contacts. The Outbound Content Delivery (ASP.NET) describes the methods and properties which allow you to implement functionality on a.net Presentation Server. The API provides access to Outbound Contacts, tracking, synchronization services, link resolving on the Content Delivery system. The Outbound Content Delivery (Java) describes the methods and properties which allow you to implement functionality on a Java Presentation Server. The API provides access to Outbound Contacts, tracking, synchronization services, link resolving on the Content Delivery system. Usage and Maintenance phase The User Manual (a PDF document) explains to content authors and content editors how to work with content in the Content Manager Explorer Web interface. The Outbound User Manual explains which tasks an end user can perform using the GUI, and what it means to perform those tasks. The WebDAV Connector User Manual (a PDF document) explains to content authors and content editors how to work with content using a WebDAV interface. The Upgrade Manual (a PDF document) tells system administrators how to upgrade to the current version of SDL Tridion from a previous version. The Release Notes (a PDF document) explains how the current version of SDL Tridion has changed compared to previous versions, and which open issues remain. The Maintenance Guide (a PDF document) helps you maintain, troubleshoot and monitor your implementation of SDL Tridion

8 Chapter 1 Upgrading Outbound This chapter describes how to upgrade from Outbound 1.3SP1 to Outbound and consists of the following sections: Upgrading Outbound Server (see page 5) Upgrading Presentation Server (see page 11) 1.1 Checking changes in prerequisites for Outbound Outbound is fully integrated into SDL Tridion The prerequisites for Outbound are therefore the same as for those of SDL Tridion For detailed information, see the SDL Tridion 2009 Product Prerequisites. The following sections describe the most important changes to the prerequisites for Outbound IMAP IMAP as well as POP3 is now supported as protocol for bounce processing. Chilkat Chilkat Software is no longer a requirement Server-side scripting and database support In the previous version of Outbound , two Presentation Server configurations were supported: A COM/ASP-based Presentation Server using a Microsoft SQL Server database A Java/JSP-based Presentation Server using an Oracle database. Support for COM/ASP has been dropped and has been superseded by ASP.NET, and all combinations of server scripting and database are supported: ASP.NET-based Presentation Server with Oracle or Microsoft SQL Server Java/JSP-based Presentation Server with Oracle or Microsoft SQL Server Support for COM dropped Outbound is built on the.net platform. The following COM APIs are no longer supported and have been superseded by.net verssions: 4

9 Contact API (ASP) the API for developing ASP applications on the Content Delivery Presentation Server is no longer supported and has been superseded by the Outbound Content Delivery (ASP.NET) API. The API describes the methods and properties which allow you to implement functionality on a.net Presentation Server. Tridion Marketing Communication Solution API the API for customizing and extending Outbound using the COM+ version of the Tridion Object Model is no longer supported and has been superseded by the Outbound Contact Management (.NET) API which allows you to customize and extend Outbound on the Content Manager using C# or another language supported by.net 1.2 Upgrading Outbound Server This section describes how to upgrade the Outbound Server, from Outbound 1.3SP1 to Outbound 2009, which involves performing the following tasks: 1. Upgrading the Outbound database: Microsoft SQL Server Oracle 2. Uninstalling Outbound 1.3SP1 3. Installing Outbound Upgrading Outbound database (Microsoft SQL Server) Requirements Context You need to plan in advance what extended details you want (to add or remove) and adjust the migration script accordingly. Adjusting the migration script involves mapping the fields in your Outbound 1.3SP1 database to the fields in your Outbound database. Note also that you must make sure to keep the Outbound database (Content Manager) and Subscription Management database (Content Delivery) in sync. This task describes how to upgrade your Outbound 1.3SP1 database to Outbound database The procedure below describes upgrading on a Microsoft SQL Server database using the database scripts provided: 1.Outbound 13SP1 to 2009 Pre-analyze.sql 2.Outbound 13SP1 to 2009 Migration.sql 3.Outbound 13SP1 to 2009 Post-check.sql Important:You need to complete the migration BEFORE creating or updating items in Outbound otherwise content migration using the available script is no longer possible. 5

10 Steps to execute 1. Back-up the 1.3SP1 Outbound database. 2. Restore the 1.3SP1 Outbound database with the name TMCS13SP1 (the database scripts expect this name if the name is different, change the scripts accordingly). 3. Run the 1.Outbound 13SP1 to 2009 Pre-analyze.sql script on your Outbound 13SP1 database to check its compatibility with Outbound The script checks for the following: Mailings with no Distribution Lists assigned Deleted Contacts or queued s "Dirty" Contacts (Contacts that have changed but have not yet been synchronized with the presentation side) Distribution Lists shared between Publications Distribution Lists based on a Database View 4. Fix any errors or warnings as follows: For Mailings with no Distribution Lists assigned, it is recommended to assign an empty static Distribution List to the Mailing. For deleted Contacts, wait for synchronization to occur between the Content Management and Presentation Server databases; for Queued s wait until the s have been sent, or cancel the Mailing by clearing the queue. For dirty Contacts, it is recommended to wait for Contact synchronization to occur. If you upgrade before dirty Contacts are synchronized, these changes will not be synchronized. For Distribution Lists shared between Publications, create a copy of the Distribution List for each Publication and add these Distribution Lists to the respective Mailing. Distribution Lists based on Database View are migrated as empty Static Distribution Lists (as placeholders). After upgrade, you need to recreate the Database View as a Dynamic Distribution List. 5. Run the SDL Tridion Database Manager to create the Outbound E- mail 2009 database on the same database server as the Outbound E- mail 1.3SP1 database. 6. If you added your own Contact extended details in Outbound 1.3SP1, add these also to the following tables in the Outbound tridion_cm_ database: CONTACTS_EXTENDED_DETAILS IMPORT_CONTACTS Note: For more information on adding your own Contact extended details and updating the import Contacts fields, see Chapter 8 Configuring Contacts database of the Outbound E- mail Implementation Guide. 7. Modify the 2.Outbound 13SP1 to 2009 Migration.sql script: Specify the CONTACTS_EXTENDED_DETAILS fields used the script inserts by default the standard details used in 1.3SP1, but you also need to specify Contact extended details you added in Outbound E- mail 1.3SP1. If necessary, add the Locale field to the CONTACTS_EXTENDED_DETAILS table in Outbound 1.3, the Locale field was part of the CONTACTS table; in 2009, the field is no longer included. 6

11 Set parameter to the PublicationID where Distribution Lists not used in Mailings will be stored. Optionally, set parameter to indicate the Address Book where Contacts are added to (the ItemID in the TCM URI, for example 5 in tcm: ). If not specified, Contacts are added to the (Unassigned Contacts) Address Book Optionally, set parameter assigned to all Distribution Lists (the lower the number, the lower the priority). 8. Run the 2.Outbound 13SP1 to 2009 Migration.sql script from the Outbound database. 9. Run the 3.Outbound 13SP1 to 2009 Post-check.sql script. The script compares the number of rows in each table for both databases. Result The migration script adds the following Outbound 1.3SP1 standard details to the Outbound CONTACTS_EXTENDED_DETAILS table. MAIL (the values are added in the IDENTIFICATION_KEY field used by default for Contact identification) SALUTATION PREFIX NAME SURNAME COMPANY Mailings and their related Distribution Lists are migrated to the root Outbound Folder of the Publication the Mailing resides in. If Distribution Lists are not associated to a Mailing, they are added to the root Outbound Folder of the Publication specified by parameter. Contacts are added to the Address Book specified by parameter, or the (Unassigned Contacts) Address Book if not specified. Next steps Uninstalling Outbound 1.3SP1 (see page 10) Upgrading Outbound database (Oracle) Requirements The user who executes the upgrade scripts must be sysdba. You need to plan in advance what extended details you want (to add or remove) and adjust the migration script accordingly. Adjusting the migration script involves mapping the fields in your Outbound 1.3SP1 database to the fields in your Outbound database. Note also that you must make sure to keep the Outbound database (Content Manager) and Subscription Management database (Content Delivery) in sync. 7

12 Context This task describes how to upgrade your Outbound 1.3SP1 database to Outbound database The procedure below describes upgrading on a Oracle database using the database scripts provided: 1.Outbound 13SP1 Update sequences.sql 2.Outbound 13SP1 to 2009 Pre-analyze.sql 3.Outbound 13SP1 to 2009 Migration.sql 4.Outbound 13SP1 to 2009 Post-check.sql 5.Outbound 13SP1 to 2009 Migration Update sequences.sql Important:You need to complete the migration BEFORE creating or updating items in Outbound otherwise content migration using the available script is no longer possible. Steps to execute 1. Back-up the 1.3SP1 Outbound schema. 2. Restore the 1.3SP1 Outbound schema with the name TMCS13SP1 (the database scripts expect this name if the name is different, change the scripts accordingly). 3. Run the 1.Outbound 13SP1 Update sequences.sql script on your Outbound 13SP1 database. 4. Run the 2.Outbound 13SP1 to 2009 Pre-analyze.sql script on your Outbound 13SP1 database to check its compatibility with Outbound The script checks for the following: Mailings with no Distribution Lists assigned Deleted Contacts or queued s "Dirty" Contacts (Contacts that have changed but have not yet been synchronized with the presentation side) Distribution Lists shared between Publications Distribution Lists based on a Database View 5. Fix any errors or warnings as follows: For Mailings with no Distribution Lists assigned, it is recommended to assign an empty static Distribution List to the Mailing. For deleted Contacts, wait for synchronization to occur between the Content Management and Presentation Server databases; for Queued s wait until the s have been sent, or cancel the Mailing by clearing the queue. For dirty Contacts, it is recommended to wait for Contact synchronization to occur. If you upgrade before dirty Contacts are synchronized, these changes will not be synchronized. For Distribution Lists shared between Publications, create a copy of the Distribution List for each Publication and add these Distribution Lists to the respective Mailing. Distribution Lists based on Database View are migrated as empty Static Distribution Lists (as placeholders). After upgrade, you need to recreate the Database View as a Dynamic Distribution List. 6. Run the SDL Tridion Database Manager to create the Outbound E- mail 2009 database on the same database server as the Outbound E- mail 1.3SP1 database. 8

13 7. If you added your own Contact extended details in Outbound 1.3SP1, add these also to the following tables in the Outbound tridion_cm_ database: CONTACTS_EXTENDED_DETAILS IMPORT_CONTACTS Note: For more information on adding your own Contact extended details and updating the import Contacts fields, see Chapter 8 Configuring Contacts database of the Outbound E- mail Implementation Guide. 8. Modify the 3.Outbound 13SP1 to 2009 Migration.sql script: Specify the Outbound schema in ALTER SESSION SET CURRENT_SCHEMA. Specify the CONTACTS_EXTENDED_DETAILS fields used the script inserts by default the standard details used in 1.3SP1, but you also need to specify Contact extended details you added in Outbound E- mail 1.3SP1. If necessary, add the Locale field to the CONTACTS_EXTENDED_DETAILS table in Outbound 1.3, the Locale field was part of the CONTACTS table; in 2009, the field is no longer included. Set parameter to the PublicationID where Distribution Lists not used in Mailings will be stored. Optionally, set parameter to indicate the Address Book where Contacts are added to (the ItemID in the TCM URI, for example 5 in tcm: ). If not specified, Contacts are added to the (Unassigned Contacts) Address Book Optionally, set parameter assigned to all Distribution Lists (the lower the number, the lower the priority). 9. Run the 3.Outbound 13SP1 to 2009 Migration.sql script from the Outbound database. 10. Modify the 4.Outbound 13SP1 to 2009 Post-check.sql script to specify the Outbound schema in ALTER SESSION SET CURRENT_SCHEMA, then run the script. The script compares the number of rows in each table for both schemas. 11. Modify the 5.Outbound 13SP1 to 2009 Migration Update sequences.sql script to specify the Outbound schema in ALTER SESSION SET CURRENT_SCHEMA, then run the script. Result The migration script adds the following Outbound 1.3SP1 standard details to the Outbound CONTACTS_EXTENDED_DETAILS table. MAIL (the values are added in the IDENTIFICATION_KEY field used by default for Contact identification) SALUTATION PREFIX NAME SURNAME COMPANY 9

14 Mailings and their related Distribution Lists are migrated to the root Outbound Folder of the Publication the Mailing resides in. If Distribution Lists are not associated to a Mailing, they are added to the root Outbound Folder of the Publication specified by parameter. Contacts are added to the Address Book specified by parameter, or the (Unassigned Contacts) Address Book if not specified. Next steps Uninstalling Outbound 1.3SP1 (see page 10) Uninstalling Outbound 1.3SP1 Context After you have upgraded the Outbound database you can uninstall Outbound 1.3SP1. Uninstalling Outbound 1.3SP1 is a manual procedure. Steps to execute 1. Uninstall Chilkat. 2. Uninstall the Mailer, Bounce Processor, Trigger and Contact Synchronization services: a. Open a command prompt. b. Navigate to the C:\WINDOWS\Microsoft.NET\Framework \<version> folder. c. Enter InstallUtil.exe /u (the unistall command) and specify the path to the.exe for each service. For example: InstallUtil.exe /u "c:\program files\tridion\tms\services\synchronizer \tms_synch_service.exe" 3. Remove TMS folder in your Tridion installation open Windows Explorer and navigate to the TMS root folder, by default located in c:\program Files\Tridion\TMS. Note that removing the TMS root folder also removes TMCS Configuration application. 4. Remove the Tridion Marketing Communication Solution Web site. 5. Delete the Tridion Marketing Communication Solution COM+ application access Component Services in your Administrative Tools and in the tree, navigate to Computers > My Computer > Computers > COM + Applications. 10

15 Result Installing Outbound (see page 11) Installing Outbound You install Outbound on SDL Tridion 2009 (Content Manager) using the installer. For information on installation and configuration, see Chapter 13 Installing Outbound of the SDL Tridion 2009 Installation Manual. 1.3 Upgrading Presentation Server The Presentation Server is where your Tracking and Contact subscription Web pages are running. This section describes how to upgrade the Presentation Server, from Outbound 1.3SP1 to Outbound 2009, which involves performing the following tasks: 1. Preparing to upgrade 2. Pre-upgrade procedure 3. Upgrading the Presentation Server Subscription Management database Microsoft SQL Server Oracle 4. Upgrading the Presentation Server Preparing to upgrade This topic describes how to prepare for upgrade. Preparing for upgrade involves doing the following: Develop/redevelop Tracking and Subscription Web Pages Developing temporary Web pages for Contact Subscription Tracking and Subscription URLs Note: There are other considerations to bear in mind when upgrading, such as when to perform migration (for example between campaigns). Developing/redeveloping tracking and subscription Web Pages Subscription and Tracking functionality is implemented using the following Web pages: Contact subscription Contact profile synchronization Tracking Tracking retrieval 11

16 In Outbound 1.3SP1, two Presentation Server technologies were supported for implementing these Web pages: Java/JSP COM/ASP Outbound supports two Presentation Server technologies: Java/JSP.NET/ASPX If you were using Java/JSP in Outbound 1.3SP1, you may want to redevelop your JSPs when you upgrade to Outbound to: Identify Contacts differently in Outbound 1.3SP1, Contacts were identified by their address. In Outbound 2009, you can specify your own fields for Contact identification. Specify the Group ID when Contacts subscribe on your Web site, the GROUP ID indicates the Address Book which they are added to on the Content Management System (on synchronization). If no GROUP ID is specified, they are added to the (Unassigned Contacts) Address Book If you were using COM/ASP in Outbound 1.3SP1, before you upgrade to Outbound you have to develop Web pages for Tracking and Tracking retrieval, and Contact subscription and Contact profile synchronization using a supported API (Java or.net). For more information about developing Web pages for Tracking and Contact subscription, see the following documents: The Outbound Implementation Guide The Outbound Content Delivery (ASP.NET) API The Outbound Content Delivery (Java) API Developing temporary Web pages for Contact Subscription For the duration of the upgrade, the Contact Subscription Web pages will be unavailable on the Web site. You therefore need to develop temporary Web pages to inform customers of the situation. Tracking and Subscription URLs In Outbound you need to configure Tracking and Subscription URLs. These are fully qualified domain names specifying the URL of the Web pages in which a subscriber confirms/changes/unsubscribes their subscription, and the URL of the Tracking Web page that is referenced in your s to track user response to s. If you were using JSPs in Outbound 1.3SP1, you can use the same URLs in Outbound If you were using ASPs, the URLs will change to point to ASPXs. You will need to cater for this change, for example by creating URL redirects to the new Web pages. 12

17 1.3.2 Pre-upgrade procedure Context This task describes what you need to do before you start the upgrade: Steps to execute 1. Make sure all Contacts are synchronized on Content Manager (part of Upgrading the Outbound database). Note: You can continue running the Tracking and Web page during the migration. 2. Take Contact Subscription Web page offline and deploy temporary Web pages (the Subscription Management database must NOT be accessed during the migration). 3. Stop the following services on the Outbound Server: Outbound Synchronization service synchronizes Contact information between the Outbound database and the Contact Subscription database on the presentation side Outbound Collect Tracking Data service retrieves tracking information from the Tracking database on the presentation side Result Upgrading Subscription Management database (Microsoft SQL Server) (see page 13) Upgrading Subscription Management database (Oracle) (see page 15) Upgrading Subscription Management database (Microsoft SQL Server) Context The Presentation Server uses two databases, one for tracking data and one for storing changes to Contact Subscriptions. This task describes how to upgrade your Outbound Subscription Management 1.3SP1 database to Outbound for a Microsoft SQL Server database server (the tracking database does not require upgrading). Upgrading the Presentation Server Subscription Management (tridion_submgmt) database involves making sure that the CONTACTS_EXTENDED_DETAILS table is in sync with the CONTACTS_EXTENDED_DETAILS table in the Outbound (tridion_cm_ ) database. 13

18 Steps to execute 1. Back-up the 1.3SP1 Subscription Management database. 2. Open the Outbound 13SP1 to 2009 Subscription Management Migration.sql script in a text editor: a. Change the ALTER TABLE statement to match the CONTACTS_EXTENDED_DETAILS as defined on the Outbound database on the Content Management side. b. Optionally, change the UPDATE CONTACTS statement to link all Contacts with an Address Book other than with the (Unassigned Contacts) Address Book defined as the default (specify the Address Book ID the ItemID in the TCM URI, for example 5 in tcm: ). c. In Outbound 1.3SP1, the Locale field is part of the CONTACTS table. In Outbound 2009, the Locale field has been removed. If you want to continue to use the Locale field, you need to add it to the CONTACTS_EXTENDED_DETAILS table and alter the first UPDATE statement to copy rows from the CONTACTS table to the CONTACTS_EXTENDED_DETAILS table. 3. Run the Outbound 13SP1 to 2009 Subscription Management Migration.sql script. 4. Run the following stored procedures scripts, available on the the SDL Tridion 2009 installation CD-ROM, on your database: a. Navigate to the folder Database\TDM\Scripts\MSSQL\Shared \20\Subscription Management. b. Execute the SP_UTILS.sql script. c. Execute the OE_SubMgmt_Procedures.sql script. 5. In the Outbound 1.3SP1 Subscription Management database, define a unique index for the CONTACTS_EXTENDED_DETAILS table to uniquely identify Contacts. The default fields used when upgrading the Outbound database are IDENTIFICATION_KEY and IDENTIFICATION_SOURCE. Note: For more information on changing the unique index, see Chapter 8 Configuring Contacts database of the Outbound E- mail Implementation Guide. Result The migration script adds the following Outbound 1.3SP1 standard details to the Outbound CONTACTS_EXTENDED_DETAILS table. MAIL (the values are added in the IDENTIFICATION_KEY field used by default for Contact identification) SALUTATION PREFIX NAME SURNAME COMPANY Next steps Upgrading Presentation Server (see page 11) 14

19 1.3.4 Upgrading Subscription Management database (Oracle) Requirements The user who executes the upgrade scripts must be sysdba. Context The Presentation Server uses two database schemas, one for tracking data and one for storing changes to Contact Subscriptions. This task describes how to upgrade your Outbound Subscription Management 1.3SP1 schema to Outbound for an Oracle database server (the tracking database schema does not require upgrading). Upgrading the Presentation Server Subscription Management (tridion_submgmt) schema involves making sure that the CONTACTS_EXTENDED_DETAILS table is in sync with the CONTACTS_EXTENDED_DETAILS table in the Outbound (tridion_cm_ ) schema. Steps to execute 1. Back-up the 1.3SP1 Subscription Management schema. Note: If you encounter problems during upgrade and the database is in an invalid state, you must restore the back-up and repeat the upgrade. 2. Open the Outbound 13SP1 to 2009 Subscription Management Migration.sql script in a text editor: a. Specify the Subscription Management schema in ALTER SESSION SET CURRENT_SCHEMA. b. Change the ALTER TABLE statement to match the CONTACTS_EXTENDED_DETAILS as defined on the Outbound schema on the Content Management side. c. Optionally, change the UPDATE CONTACTS statement to link all Contacts with an Address Book other than with the (Unassigned Contacts) Address Book defined as the default (specify the Address Book ID the ItemID in the TCM URI, for example 5 in tcm: ). d. In Outbound 1.3SP1, the Locale field is part of the CONTACTS table. In Outbound 2009, the Locale field has been removed. If you want to continue to use the Locale field, you need to add it to the CONTACTS_EXTENDED_DETAILS table and alter the first UPDATE statement to copy rows from the CONTACTS table to the CONTACTS_EXTENDED_DETAILS table. 3. Run the Outbound 13SP1 to 2009 Subscription Management Migration.sql script. 4. Run the Add Outbound tables and procedures.sql script on the upgraded schema. 15

20 5. In the Outbound 1.3SP1 Subscription Management schema, define a unique index for the CONTACTS_EXTENDED_DETAILS table to uniquely identify Contacts. The default fields used when upgrading the Outbound schema are IDENTIFICATION_KEY and IDENTIFICATION_SOURCE. Note: For more information on changing the unique index, see Chapter 8 Configuring Contacts database of the Outbound E- mail Implementation Guide. Result The migration script adds the following Outbound 1.3SP1 standard details to the Outbound CONTACTS_EXTENDED_DETAILS table. MAIL (the values are added in the IDENTIFICATION_KEY field used by default for Contact identification) SALUTATION PREFIX NAME SURNAME COMPANY Next steps Upgrading Presentation Server (see page 11) Upgrading Presentation Server Context To upgrade the Presentation Server: Steps to execute 1. Install Outbound on the Presentation Server. For more information, see the following sections of the SDL Tridion 2009 Installation Manual: Section 13.5 Installing Outbound on.net Presentation Server Section 13.6 Installing Outbound on Java Presentation Server Note: You can install Outbound in parallel with the running Outbound 1.3SP1 installation. 2. Deploy Web pages for Contact Subscription: If you were using JSPs in Outbound 1.3SP1, you can continue using these in Outbound If you were using ASPs in Outbound 1.3SP1, you must replace these with newly developed ASPX pages. 3. Deploy Web pages for Tracking and Tracking retrieval: 16

21 If you were using JSPs in Outbound 1.3SP1, you can continue using these in Outbound If you were using ASPs in Outbound 1.3SP1, you must replace these with newly developed ASPX pages. Note: You can continue running the Tracking Web pages during the migration. 4. Perform the following configuration on the Outbound Content Manager Server (for detailed information, see section 13.7 Configuring Subscription and Tracking on Outbound Server of the SDL Tridion 2009 Installation Manual): a. Create Synchronization Targets for each Presentation Server on which you have installed subscription or tracking Web pages. b. Configure Publications to use Synchronization Targets and specify subscription and tracking URLs for more information, see the Tracking and Subscription URLs section in Preparing to upgrade (see page 11). c. Configure Synchronization intervals and batch size. d. Configure Confirmation defaults specifying the default e- mails sent to subscribers when they confirm, subscribe, change their profile, or unsubscribe from a Mailing. e. Configure Confirmation s specifying the s sent to subscribers when they confirm, subscribe, change their profile, or unsubscribe from a Mailing (these overrule the defaults). 5. Start the following services on the Outbound Server: Outbound Synchronization service Outbound Collect Tracking Data service 6. Delete your Outbound 1.3SP1 installation files. 17