SAS Marketing Operations Management 6.6: Upgrade and Migration Guide

Transcription

1 SAS Marketing Operations Management 6.6: Upgrade and Migration Guide SAS Documentation June 2017

2 The correct bibliographic citation for this manual is as follows: SAS Institute Inc SAS Marketing Operations Management 6.6: Upgrade and Migration Guide. Cary, NC: SAS Institute Inc. SAS Marketing Operations Management 6.6: Upgrade and Migration Guide Copyright 2017, SAS Institute Inc., Cary, NC, USA All Rights Reserved. Produced in the United States of America. For a hard copy book: No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, or otherwise, without the prior written permission of the publisher, SAS Institute Inc. For a web download or e-book: Your use of this publication shall be governed by the terms established by the vendor at the time you acquire this publication. The scanning, uploading, and distribution of this book via the Internet or any other means without the permission of the publisher is illegal and punishable by law. Please purchase only authorized electronic editions and do not participate in or encourage electronic piracy of copyrighted materials. Your support of others' rights is appreciated. U.S. Government License Rights; Restricted Rights: The Software and its documentation is commercial computer software developed at private expense and is provided with RESTRICTED RIGHTS to the United States Government. Use, duplication, or disclosure of the Software by the United States Government is subject to the license terms of this Agreement pursuant to, as applicable, FAR , DFAR (a), DFAR (a), and DFAR , and, to the extent required under U.S. federal law, the minimum restricted rights as set out in FAR (DEC 2007). If FAR is applicable, this provision serves as notice under clause (c) thereof and no other notice is required to be affixed to the Software or documentation. The Government s rights in Software and documentation shall be only those set forth in this Agreement. SAS Institute Inc., SAS Campus Drive, Cary, NC June 2017 SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. indicates USA registration. Other brand and product names are trademarks of their respective companies. 6.6-P1:momupg

3 Contents Chapter 1 Prerequisites for Migration Pre-migration Tasks Replacing ALUser Chapter 2 Migration to SAS Marketing Operations Management Migrating to SAS Marketing Operations Management 6.6 from Migrating to SAS Marketing Operations Management 6.6 from Migrate the Database Scripts Manually Chapter 3 Post-migration Steps Migrating from SAS Marketing Operations Management 6.4 to SAS Marketing Operations Management Migrating from SAS Marketing Operations Management 6.5 to SAS Marketing Operations Management Moving the Setup Grant Permissions to the Database User Chapter 4 Database Performance Tuning Tune the Database Set Database Isolation Level to Read Committed Snapshot Chapter 5 Troubleshooting Troubleshooting in Case of Failure

4 iv Contents

5 1 Chapter 1 Prerequisites for Migration Pre-migration Tasks Replacing ALUser Pre-migration Tasks Complete the following tasks before you migrate SAS Marketing Operations Management to the latest version: Make sure that the passwords of the existing users in the ALENT_USER table do not include %=. If these characters are in the password, set the password to blank. If SAS Marketing Operations Management and other SAS products are installed on the same server, complete the following steps for an upgrade in place of SAS Marketing Operations Management 6.6 : 1. Be sure to create the depot for the upgrade in place of SAS Marketing Operations Management 6.6 and other SAS products using the same ship event. Select the latest ship event for the products. For example, SAS Marketing Operations Management 6.6, 17W Perform the upgrade in place for SAS Marketing Operations Management 6.6 from the depot that was created using the license file for SAS Marketing Operations Management Perform the upgrade in place for the SAS products from the depot that was created using the license file for SAS products, as mentioned in Step 1 on page 1. If SAS Marketing Operations Management and SAS Digital Marketing are installed on the same server for the previous versions using the MOMSDM bundle, then for the upgrade-in-place, select the SAS Digital Marketing license file. After the upgrade in place is complete, replace the SAS Marketing Operations Management license manually by completing the following steps (which are also described in the renewal instructions): 1. On the server where SAS Marketing Operations Management is installed, search for the SID file location: a. To locate the SID file location, open the file <installationdirectory>\configuration\xml\assetlink.xml on the SAS Marketing Operations Management web services server, and search for [SIDFILELOCATION].

6 2 Chapter 1 Prerequisites for Migration b. Make a note of the current SID file path along with SID filename. 2. Go to the SID file path or location where the current SID file is present. 3. Copy the new SID file from the SAS Marketing Operations Management 6.6 depot to the SID file path. 4. Modify the assetlink.xml file and provide the new SID file location in the [SIDFILELOCATION] key. 5. Restart the IIS service and all the SAS Marketing Operations Management windows services on the solution server. The new license is applied for the SAS SAS Marketing Operations Management 6.6 installation. If you have facets with mandatory fields, then be sure to provide a default value for the field. Make sure the base installation on all the servers is SAS Marketing Operations Management 6.4 or 6.5. Verify that the latest third-party software prerequisites are installed on the servers before migration. See SAS Marketing Operations Management 6.6: Installation, Configuration, and Administration Guide. Make sure the Migration Scripts.zip file is present with the installer. You can use this for your reference. The scripts are available in the downloaded SAS Software Depot package in the products\mominstall wx6 xx sp0 1 folder. If you have customized any code, merge the custom code with the SAS Marketing Operations Management 6.6 code base. Migrations of XML files such as form configuration, list configuration, predefined search configurations, and tab configurations are made automatically in 6.6. If any customization is related to any integration between SAS Marketing Operations Management and any other SAS Customer Intelligence solutions, refer to the appropriate deployment guides that are available at In SAS Marketing Operations Management, if the SASMOM Role role is present and the SAS Marketing Operations Management database user belongs to the SASMOM Role role, then remove the user from the SASMOM Role role and add the user to the db_owner role. To change the user role: 1. Select Start ð Programs ð Microsoft SQL Server ð Databases ð Database ð Security ð Users. 2. Double-click the SAS Marketing Operations Management database user. 3. In the Database User Properties window, select Membership from the left pane. Select the db_owner role under the Database role membership section in the right pane. Click OK. 4. If the SASMOM Role role is selected for the SAS Marketing Operations Management database user, then deselect this role. Before installing SAS Marketing Operations Management 6.6, back up the following items: Installation Directory SAS Marketing Operations Management Registry: HKEY_LOCAL_MACHINE \SOFTWARE\Assetlink Tenant database and the ODS database for all tenants XML MountPoint of all tenants

7 Replacing ALUser 3 C:\Program Files (x86)\installshield Installation Information\{992CF3BB-4B72-41BA-A6BF-061B5AF1D48E} folder Note: The InstallShield Installation Information folder is a hidden folder. Enable viewing of hidden files and folders for making a backup. After the backup is completed, revert the setting to hide the hidden files and folders. The application server should be available. Start the IIS on this machine (this is required by the SAS Marketing Operations Management 6.6 installer). SAS Marketing Operations Management 6.6 should be installed on the servers in the setup in the following sequence: 1. Application Server 2. Solutions Server 3. Cataloger Server and Media Server 4. All Media Processor servers Replacing ALUser If you are changing the ALUser to domain user or any other local system user, then follow these steps before migration. MOMUSR refers to the ALUser, the local system user, or the domain user that is used for installation. 1. If the MOMUSR is a domain user, then add the user to the System Administrator Group. 2. If the MOMUSR is a local system user, then add the user to the System users and the administrator group. Select User cannot change password and Password never expires, and add the user to the Administrator Group. 3. Complete the following steps manually: a. Folder Security Permissions: Provide full access to the MOMUSR on the following folders: For migration from SAS Marketing Operations Management 6.4 to 6.5 and from SAS Marketing Operations Management 6.5 to 6.6: installationfolder\mktgoperationsmgmt folder installation-folder\sasmomtools folder Temp Locations: C:\Temp, C:\Windows\Temp, and C:\Windows \Microsoft.NET\Framework64\v \TemporaryASP.NET Files mount point XML mount point Provide access to the user on the Security tab: i. Right-click the folder and click Properties. ii. Click the Security tab and click Edit. iii. Click Add user, add MOMUSR, and provide Full Control. Click OK. b. DCOM Configuration: To change the user in the DCOM configuration: i. On the server, select Start ð Run and type Dcomcnfg.exe.

8 4 Chapter 1 Prerequisites for Migration ii. Navigate to Component Services ð Computers ð My Computer ð DCOM Config. iii. For each application listed in Table 1.1 on page 4, complete the following steps: iv. Right-click on the application and select Properties. v. On the Security tab, specify the following settings: Launch and Activation Permissions: If you select the Customize option, click Edit. Add users in the Group or user names section. Allow Local Launch, Remote Launch, Local Activation, and Remote Activation permissions. Access Permissions: If you select the Customize option, click Edit. Add users in the Group or user names section. Allow Local access, and Remote access permissions. Configuration Permissions: If you select the Customize option, click Edit. Add users in the Group or user names section. Allow Full Control to the user. Here are the DCOM settings for the Microsoft Office Processor Server: Table 1.1 DCOMConfig User: MOMUSR Applications Permissions Microsoft Excel Application Microsoft Word Document Microsoft PowerPoint Slide Launch and Activation Customize Customize Customize Access Use Default Use Default Use Default Configuration Customize Customize Customize 4. On the Identity tab, complete the following steps for all applications in the DCOM configuration: a. Select the This User radio button. b. Click Browse to select MOMUSR. c. Add the user to the Group or User Names. Provide the appropriate password for the Password and Confirm Password fields. d. Click Apply to apply the configuration, and then click OK to save and close the configuration. 5. If you specified DCOM settings in the previous steps but the Queue Manager Service fails to launch the respective applications, then change the DCOM configuration settings: a. Go to Computer Management ð System tools ð Local Users and Groups, and add the MOMUSR to the Administrators group. b. Go to the DCOM Config settings, right-click the item, and select Properties

9 c. Click the Identity tab and select the The Launching User radio button. d. Click Apply and OK to save the settings. Replacing ALUser 5

10 6 Chapter 1 Prerequisites for Migration

11 7 Chapter 2 Migration to SAS Marketing Operations Management 6.6 Migrating to SAS Marketing Operations Management 6.6 from Migrating to SAS Marketing Operations Management 6.6 from Migrate the Database Scripts Manually Migrating to SAS Marketing Operations Management 6.6 from 6.5 Note: If you are upgrading the operating system, then first upgrade to SAS Marketing Operations Management 6.6, and then upgrade to Windows Server 2012 R2. You can upgrade the operating system or the hardware after you upgrade to SAS Marketing Operations Management 6.6. See Moving the Setup on page 14 for more information. During installation, when you are prompted to specify the user type or enter the user name, password, and port number, be sure to enter the same values as for the previous installation. The SAS Marketing Operations Management 6.6 installer performs the following tasks: Updates NTFS for all the tenants Updates the tenant database and the ODS database for all the tenants created on SAS Marketing Operations Management 6.5 installation Installs SAS Marketing Operations Management 6.6 on all the servers used in a setup for a client (For example, application, solution, cataloger and media processors, Adobe InDesign, and so on.) Note: Be sure to use the same setup while migrating. That is, if you have a single machine installation, migrate to a single machine. If you have multi-machine installation, migrate to a multi-machine. You can install SAS Marketing Operations Management on a single server or on multiple servers. The migration utility detects what type of installation is done previously (single or multi-machine). Be sure to install SAS Marketing Operations Management 6.6 on all the servers in the setup. 1. In the SAS Software Depot, double-click Setup.

12 8 Chapter 2 Migration to SAS Marketing Operations Management Select the language, and click OK. 3. On the Select Deployment Task page, select Install SAS software. Click Next. 4. On the Review Required Updates page, click Next. 5. On the Specify User Type page, select domain or local system user. 6. On the user details page enter the user name and password, and click Next. The password entered for the local system user must meet the password policy requirements for the local machine. The local system user is created during the installation process. The domain user must belong to the administrators group on the local machine. 7. On the Server Details page, enter the DNS port number and click Next. The default port number for HTTP is 80 and for HTTPS is On the Port Number page, enter the internal port number and click Next. The default port number for HTTP is 80 and for HTTPS is On the Script Execution page, select Manually or Automatically, and then click Next. If you select the manual mode, you must complete the steps described in Migrate the Database Scripts Manually on page 9 after the installation process is complete. 10. After the file system check is complete, click Next. 11. On the Deployment Summary page, click Start. 12. After the installation is complete, click Next. On the next page, click Finish to close the SAS Deployment Wizard. Note: If SAS Marketing Operations Management is installed with another SAS product, a Specify Configuration Directory/Level window appears after the installation is complete. Click Cancel to terminate the configuration process for the other SAS products and continue. Migrating to SAS Marketing Operations Management 6.6 from 6.4 Note: If you are upgrading the operating system, then first upgrade to SAS Marketing Operations Management 6.6, and then upgrade to Windows Server 2012 R2. You can upgrade the operating system or the hardware after you upgrade to SAS Marketing Operations Management 6.6 See Moving the Setup on page 14 for more information. During installation, when you are prompted to specify the user type or enter the user name, password, and port number, be sure to enter the same values as for the previous installation. The SAS Marketing Operations Management 6.6 installer performs the following tasks: Updates NTFS for all the tenants. Updates the tenant database and the ODS database for all the tenants created in SAS Marketing Operations Management 6.4 installation.

13 Installs SAS Marketing Operations Management 6.6 on all the servers used in a setup for a client. (For example, application, solution, cataloger and media processors, Adobe InDesign, and so on.) Note: Be sure to use the same configuration for your migration. That is, if you have a single-machine installation, migrate to a single machine. If you have multi-machine installation, migrate to a multi-machine installation. You can install SAS Marketing Operations Management on a single server or on multiple servers. The migration utility detects the type of installation that was used previously (single or multi-machine). Be sure to install SAS Marketing Operations Management 6.6 on all the servers in the setup. 1. In the SAS Software Depot, double-click Setup. 2. Select the language, and click OK. 3. On the Select Deployment Task page, select Install SAS software. Click Next. 4. On the Review Required Updates page, click Next. 5. On the Specify User Type page, select domain or local system user. 6. On the user details page, enter the user name and password, and click Next. The password that you enter for the local system user must meet the password policy requirements for the local machine. The local system user is created during the installation process. The domain user must belong to the administrators group on the local machine. 7. On the Server Details page, enter the DNS port number and click Next. The default port number for HTTP is 80 and for HTTPS is On the Port Number page, enter the internal port number and click Next. The default port number for HTTP is 80 and for HTTPS is On the Script Execution page, select Manually or Automatically, and then click Next. If you select the manual mode, you must complete the steps described in Migrate the Database Scripts Manually on page 9 after the installation process is complete. 10. After the file system check is complete, click Next. 11. On the Deployment Summary page, click Start. Migrate the Database Scripts Manually After the installation is complete, click Next. On the next page, click Finish to close the SAS Deployment Wizard. Note: If SAS Marketing Operations Management is installed with another SAS product, a Specify Configuration Directory/Level window appears after the installation process is complete. Click Cancel to terminate the configuration process for the other SAS products and continue. Migrate the Database Scripts Manually After the installation process is complete on all servers, the application server runs the latest code base (6.6). All required files, executables, and libraries are also running the latest code base. You must run the database scripts manually. You must execute the scripts hop-wise for each release of SAS Marketing Operations Management in succession:

14 10 Chapter 2 Migration to SAS Marketing Operations Management From SAS Marketing Operations Management 6.4 to From SAS Marketing Operations Management 6.5 to 6.6 To execute the scripts hop-wise: 1. Migrate from SAS Marketing Operations Management 6.4 to 6.5: a. Execute database scripts manually on the database server. Scripts are located on the application server at Installation-folder\Database\SQL Server \64_R1_U0_To_65_R1_U0 Migration. Execute the database scripts on the SAS Marketing Operations Management database server in following order: Migration Schema Creation.sql Migration Inserts.sql 3. 1_MOM_DB_Migration_Create_Script.sql 4. 2_MOM_DB_Migration_Insert_Script.sql Execute database scripts on the ODS database server in following order: 1. 1_ODS_DB_Migration_Create_Script.sql 2. 2_ODS_DB_Migration_Insert_Script.sql b. Ensure that the 6.4 to 6.5 node Order="16" that is in the AssetlinkUpdatesList.xml file contains Source="Yes". (The AssetlinkUpdatesList.xml file is located in installation-folder\ SAS MOM Updates.) If it does not, add Source="Yes" to the 6.4 to 6.5 node as follows: <AssetlinkUpdate OldVersionMajorNumber="6" OldVersionMinorNumber="4_R1" OldVersionUpdateNumber="0" NewVersionMajorNumber="6" NewVersionMinorNumber="5_R1" NewVersionUpdateNumber="0" Order="16" DBScriptsExecutionMode="Automatic" Source="Yes"> c. Ensure that SCHEMA_VERSION_NO is 6.5 in the database. If it is not, update the version number. ID SCHEMA_ VERSION_ NO MAJOR _VER MINOR_ VER UPDATE_ VER HOTFIX_ VER COMME NTS 1 SCH_Ver_ SAS MOM d. Run the migration utility manually on the application server. The utility is located on the application server at installation-folder\migrationbinaries \DataMigrationCommonWorkspace.exe. e. Check the logs for any errors. The logs are located at installation-folder \Logs\MIGRATIONLOGS_6_6_R1_U0. 2. Migrate from SAS Marketing Operations Management 6.5 to 6.6: a. Execute database scripts manually on the database server. Scripts are located on the application server at installation-folder\database\sql Server \65_R1_U0_To_66_R1_U0 Migration.

15 Execute the database scripts on the SAS Marketing Operations Management database server in following order: Migration Schema Creation.sql Migration Inserts.sql 3. 1_MOM_DB_Migration_Create_Script.sql 4. 2_MOM_DB_Migration_Insert_Script.sql Execute database scripts on the ODS database server in following order: 1. 1_ODS_DB_Migration_Create_Script.sql 2. 2_ODS_DB_Migration_Insert_Script.sql Migrate the Database Scripts Manually 11 b. Ensure that the 6.5 to 6.6 node Order="17" that is in the AssetlinkUpdatesList.xml file contains Source="Yes". (The AssetlinkUpdatesList.xml file is located in installation-folder\ SAS MOM Updates.) If it does not, add Source="Yes" to the 6.5 to 6.6 node as follows: <AssetlinkUpdate OldVersionMajorNumber="6" OldVersionMinorNumber="5_R1" OldVersionUpdateNumber="0" NewVersionMajorNumber="6" NewVersionMinorNumber="6_R1" NewVersionUpdateNumber="0" Order="17" DBScriptsExecutionMode="Automatic" Source="Yes"> c. Ensure that SCHEMA_VERSION_NO is 6.6 in the database. If it is not, update the version number. ID SCHEMA_ VERSION_ NO MAJOR _VER MINOR_ VER UPDATE_ VER HOTFIX_ VER COMME NTS 1 SCH_Ver_ SAS MOM d. Run the migration utility manually on the application server. The utility is located on the application server at installation-folder\migrationbinaries \DataMigrationCommonWorkspace.exe. e. Check the logs for any errors. The logs are located at installation-folder \Logs\MIGRATIONLOGS_6_6_R1_U0

16 12 Chapter 2 Migration to SAS Marketing Operations Management 6.6

17 13 Chapter 3 Post-migration Steps Migrating from SAS Marketing Operations Management 6.4 to SAS Marketing Operations Management Migrating from SAS Marketing Operations Management 6.5 to SAS Marketing Operations Management Moving the Setup Prerequisites Install and Configure the Servers Run the Utility Grant Permissions to the Database User Migrating from SAS Marketing Operations Management 6.4 to SAS Marketing Operations Management 6.6 After successful migration on all the machines: 1. Check the logs at the following location for any errors:\logs \MIGRATIONLOGS_6_6_R1_U0. The logs are created during the installation process under the installation folder. 2. Restart all the servers in the installation. 3. If the component facet with digital assets was not configured in SAS Marketing Operations Management 6.4, then you can ignore the following exception: Exception occurred while processing node. NodeType: Node NodeOperation:Create NodePath: Form/RELATEDFACETS/FACET[translate(@IsSeries, 'abcdefghijklmnopqrstuvwxyz', 'ABCDEFGHIJKLMNOPQRSTUVWXYZ') = 'YES']/RELATEDENTITIES/ENTITY[@TYPENAME='DIGITALASSET'] 4. For installations that include the Site Builder module: For each site that was created, ensure that the CSS that is used is edited per the standard SAS Marketing Operations Management 6.6 CSS. In order to accommodate users who use Firefox, clear the history to get the latest CSS and images. Note: If you do not clear the history, the star rating for an asset is not displayed.

18 14 Chapter 3 Post-migration Steps For sites that were created previously, copy the Delete icon from installation-folder/tenant-name/app_themes/default/images on the solution server and add it to the installation-folder/tenantname/app_themes/site Builder/Images on the solution server. 5. If your previous installation contained customized code, replace the standard code with the custom code. 6. After the system is running on SAS Marketing Operations Management 6.6, move the backup folder OldInstallationBackup_Before_6_6_R1_U0 out of the installation folder. This folder might be useful for future reference. 7. Search for crossdomain.xml on the web server and Media server machines and delete the search results for crossdomain.xml. If you have a single-machine installation, delete all crossdomain.xml files. Migrating from SAS Marketing Operations Management 6.5 to SAS Marketing Operations Management 6.6 After successful migration on all the servers: 1. Check the logs at the following location for any errors:\logs \MIGRATIONLOGS_6_6_R1_U0. The logs are created during installation under the installation folder. 2. Restart all the servers in the installation. 3. If the component facet with digital assets was not configured in SAS Marketing Operations Management 6.5, then you can ignore the following exception: Exception occurred while processing node. NodeType: Node NodeOperation:Create NodePath: Form/RELATEDFACETS/FACET[translate(@IsSeries, 'abcdefghijklmnopqrstuvwxyz', 'ABCDEFGHIJKLMNOPQRSTUVWXYZ') = 'YES']/RELATEDENTITIES/ENTITY[@TYPENAME='DIGITALASSET'] 4. For installations that include the Site Builder module: For each site that was created, ensure that the CSS that is used is edited per the standard SAS Marketing Operations Management 6.6 CSS. In order to accommodate users who use Firefox, clear the history to get the latest CSS and images. Note: If you do not clear the history, the star rating for an asset is not displayed. 5. If your previous installation contained customized code, replace the standard code with the custom code. 6. After the system is running on SAS Marketing Operations Management 6.6, move the backup folder OldInstallationBackup_Before_6_6_R1_U0 out of the installation folder. This folder might be useful for future reference. Moving the Setup You can move SAS Marketing Operations Management from IP to FQDN, IP to IP, or FQDN to FQDN in cases of a new operating system or new hardware. In this

19 Moving the Setup 15 documentation, Source server refers to the old server on which the installation is already present and working. Destination server refers to the new server. MOMUSR refers to the ALUser, local system user, or domain user that is used for installation. Prerequisites Verify the following information before you perform the installation and run the Modify IP or FQDN utility: Make sure the installation at the source is SAS Marketing Operations Management 6.6. Verify that the number of servers used for the SAS Marketing Operations Management installation at the destination is the same as the number on the source. Verify that the drives at the source on which the following items are located are the same for the destination: installation folder mount point XML mount point outbox Ensure that you are replicating the source deployment. For example, if you have a single machine setup, the same setup should be available when you are installing SAS Marketing Operations Management 6.6 on new servers. If you have a multimachine setup, then replicate the same setup. All the drives and folders should be the same as for the old servers. See SAS Marketing Operations Management 6.6: Installation, Configuration, and Administration Guide for information about required third-party software. Install and Configure the Servers 1. Stop all the SAS Marketing Operations Management related windows services and IIS on all the source servers. 2. Install SAS Marketing Operations Management 6.6 on all the servers in the setup at the destination. See SAS Marketing Operations Management 6.6: Installation, Configuration, and Administration Guide. 3. Make sure that the deployment configuration of SAS Marketing Operations Management components are the same as the installation on the source server. 4. On the destination server, create the same number of tenants that are on the source server. Create the tenants manually and with the same outbox path, XML mount point path, and mount point path as the source server. 5. Stop all the SAS Marketing Operations Management related windows services and IIS on all the destination servers. 6. Do not delete the SASMomTools folder found at the same level as the Installation folder after installation. 7. All the drives and folders used by the destination server for SAS Marketing Operations Management should be the same as the source servers. Copy the following items from the source servers to the destination servers: contents of the installation directory on all the servers

20 16 Chapter 3 Post-migration Steps file mount point XML mount point vaults Cataloger mount point (this folder should be a shared folder for the MOMUSR) 8. Give Full control to the MOMUSR on the CatalogerMountPoint folder for each tenant. 9. The following folders should be shared with complete access sharing permission: CatalogerMountPoint for each tenant (MOMUSR, IUSR, NETWORK SERVICE, SYSTEM) Network folder configured in the Digital Asset Manager for each tenant (MOMUSR) 10. Restore all the databases for all the tenants on the new database server. The database names for all the tenants on the destination setup should be the same as the source setup. 11. Copy the registry key entry m_hashkey from the source server registry path SOFTWARE\Assetlink\SASMOMEncryptionKey to the destination servers. Run the Utility 1. Make a backup of the Computer\HKEY_LOCAL_MACHINE\SOFTWARE \Assetlink registry. 2. Make sure you have a backup of all the tenant databases. 3. Stop all the SAS Marketing Operations Management services and IIS on all the servers. 4. Execute the utility on all the destination servers by logging on to the server as MOMUSR. The ModifyIPorFQDN.exe is located in the Installation Directory\Binaries folder on the destination server. Double-click ModifyIPorFQDN.exe and enter the source and destination information. 5. Start the IIS. 6. Ensure that DNS points to the IP or FQDN given to the new servers. 7. If you configured any FTP sites on the source server, re-configure them on the destination server. 8. If you have any integration with other systems, then change the IP or FQDN for that system. 9. Restart all the SAS Marketing Operations Management services and the ASP.NET services. 10. Verify that the UNC path is accessible (vaults or Cataloger Mount Point). 11. Verify the SAS Marketing Operations Management system. Check the following log files located in Installation Directory\IPToFQDNBackUp: IPtoFQDNLoggerFile.txt IPtoFQDNErrorLoggerFile.txt IPtoFQDNRestoreLoggerFile.txt IPtoFQDNRestoreErrorLoggerFile.txt

21 Grant Permissions to the Database User 17 Note: To revert to the original configuration, click Restore. All the changes made in the files and registry revert to their original settings. You can restore the database manually from the backup. Grant Permissions to the Database User In day-to-day usage, the SAS Marketing Operations Management database user does not require a creator or owner permission. You need to grant only a limited set of permissions to the SAS Marketing Operations Management database user on the tenant and the ODS database individually. The SAS Marketing Operations Management database user login account refers to the database server login account that was created through Server ð Security ð Logins for the tenant. The SAS Marketing Operations Management database user refers to the user account created for an individual database that corresponds to the user login account present in the SQL Server under Databases Database ð Database ð Security ð Roles ð Database Roles. If the SASMOM Role role was not created during installation of the previous version of SAS Marketing Operations Management, then create the role following the steps given below. If the user already exists, then follow from Step 7 on page 19 onwards. Note: Complete the steps using the sa login account or a user account that has permissions to create a user and role, change the user role membership and database ownership, and grant or deny the database permission. To grant the required permissions: 1. Ensure that no one is using SAS Marketing Operations Management. Stop the SAS Marketing Operations Management services and IIS on all the servers and ensure that none of the SAS Marketing Operations Management scheduled tasks are running. 2. Go to Databases ð Database ð Security ð Roles ð Database Roles. Right-click Database Roles and select New Database Role. Create a role SASMOM Role and click OK. 3. Double click SASMOM Role role and click Securables link in the left pane. 4. In the right pane, search the Tenant database. Select the following permissions: Table 3.1 Permissions List Grant List Alter Authenticate Connect Note: Do not select this access on SQL Server 2008 R2. Delete Execute Deny List Alter any application role Alter any assembly Alter any asymmetric key Alter any certificate Alter any contract

22 18 Chapter 3 Post-migration Steps Grant List Insert Select Update Deny List Alter any database audit Alter any database DDL trigger Alter any database event notification Alter any dataspace Alter any fulltext catalog Alter any message type Alter any remote service binding Alter any role Alter any route Alter any service Alter any symmetric key Alter any user Backup database Backup log Checkpoint Create aggregate Create assembly Create asymmetric key Create certificate Create contract Create database ddl event notification Create default Create fulltext catalog Create function Create message type

23 Grant Permissions to the Database User 19 Grant List Deny List Create queue Create remote service binding Create role Create route Create rule Create schema Create service Create symmetric key Create type Create view Subscribe query notifications Take ownership 5. Search the ODS database, and set the same permissions as for the Tenant database. 6. To give the user restricted access: If the SAS Marketing Operations Management database user is not listed under Databases ð Database ð Security ð Users, then verify whether the dbo login user corresponds to the SAS Marketing Operations Management database user account. Double-click the dbo user and verify whether the login name is the same as the SAS Marketing Operations Management database user login account. If they are the same, then set the database owner to the sa account. Right-click on the database, select Properties, and then click the Files link in the left pane. If the SAS Marketing Operations Management database user is listed under Databases ð <Database> ð Security ð Users, then double-click on the SAS Marketing Operations Management database user. Remove the user from the db_owner role by clearing the check box (in the Database role membership section), and then click OK. 7. If the SAS Marketing Operations Management database user is not listed under Databases ð Database ð Security ð Users, then create the SAS Marketing Operations Management database user corresponding to the user login account that you created for the database server. Right-click Users and select New User. Provide the SAS Marketing Operations Management database user name for the User name and select SAS Marketing Operations Management database user login account as login name. 8. Go to Databases ð Database ð Security ð Users. Double-click on the user name, and select the SASMOM Role role under the Database role membership section.

24 20 Chapter 3 Post-migration Steps 9. If the user is a member of the dbcreator role, remove the SAS Marketing Operations Management database user login account from that role. To do so, go to Server ð Security ð Logins, double-click on the user name, and click Server Roles link in the left pane. Note: Before you create a new tenant, add the SAS Marketing Operations Management database user login account back in the dbcreator role.

25 21 Chapter 4 Database Performance Tuning Tune the Database Set Database Isolation Level to Read Committed Snapshot Tune the Database Be sure to follow the best practices specified by the customer organization for database space issues related to log files. Following are the Temp DB optimization recommendations: Number of data files: Create one data file per CPU. A dual-core CPU is considered to be two CPUs. Click Files and enter the following information: Initial Size: 500 Mb Autogrowth (File growth): 50 Mb Path (Location): You should add the Tempdb database on disks that differ from those that are used by user databases. Note: For more information about these recommendations, see msdn.microsoft.com/en-in/library/ms175527(v=sql.105).aspx. Set Database Isolation Level to Read Committed Snapshot To tune the database for better performance: 1. Stop all SAS Marketing Operations Management Services on all the servers in the installation. 2. Reset IIS on the application server. 3. Run the following script using SQL Server Management Studio on the tenant database. Do not run this script on the ODS database. /* T-SQL Script to kill the user process in current MOM DB except call nacurrent connection

26 22 Chapter 4 Database Performance Tuning with ALTER DATABSE command */ NVARCHAR(5),@CURRENT_SPID SMALLINT,@DBNAME NVARCHAR(75) = DB_NAME() DECLARE C1 CURSOR FOR SELECT SP.SPID FROM SYS.SYSPROCESSES SP INNER JOIN SYS.DATABASES DB ON SP.DBID = DB.DATABASE_ID AND DB.NAME AND SP.SPID <> OPEN C1 FETCH NEXT FROM C1 = 0 BEGIN EXEC ('KILL '+@SPID) FETCH NEXT FROM C1 END CLOSE C1 DEALLOCATE C1 EXEC (N'ALTER DATABASE '+@DBNAME+' SET READ_COMMITTED_SNAPSHOT ON ') GO Note: Ideally this script should not take more than 10 seconds. If you do not follow these steps, the script runs in an infinite loop. 4. Start all SAS Marketing Operations Management Services.

27 23 Chapter 5 Troubleshooting Troubleshooting in Case of Failure Troubleshooting in Case of Failure 1. In case the installer fails for some reason or the installation is canceled, revert to the previous installation by doing the following steps manually: Restore installation folder from backup Restore Registry from backup Restore Database for each tenant Restore XML MountPoint for each tenant Restore the folder at <OS_Drive>\Program Files\InstallShield Installation Information\{992CF3BB-4B72-41BA- A6BF-061B5AF1D48E} from the backup. After the NTFS backup is restored, share the folders and give sharing access to users (Everyone and MOMUSR) on the shared folders such as MediaProcessor and Cataloger MountPoint. Provide access on the installation folder to the following users: IUSR_MachineName NETWORK SERVICE MOMUSR ASPNET User After the restoration is completed on all the machines, log on into the system and assure that the system is restored properly. Note: You can start the installation again after the restoration. 2. If you migrate SAS Marketing Operations Management to 6.6 with port changes other than default, then links in the notifications received before migration do not work. The SAS Marketing Operations Management versions prior to 6.4 did not support configurable port numbers. For these links in the notifications to work, suffix the port number with a colon (:). 3. If the destroy session with the DELETE method does not work, you should uninstall the WebDAV Publishing feature. On the solutions server that hosts the REST API,

28 24 Chapter 5 Troubleshooting select Server Manager ð Roles ð Web Server (IIS) ð Role Services ð WebDAV Publishing. If WebDAV Publishing is installed, click Remove Role Services.

29

30