Installing SDL Tridion 2011 SP1-HR1

A patch installer is available to install the SDL Tridion 2011 SP1 HR1 on the Content Manager Server. On Content Delivery, you need to apply the hotfix rollup manually.

About this task

The procedure for installing SDL Tridion 2011 SP1 HR1 is as follows:

  1. Download the hotfix rollup
  2. Update your Content Manager database
  3. Install the hotfix rollup on Content Manager (using the installer)
  4. Install the hotfix rollup on Content Delivery (manually)
  5. Optionally, configure the hotfix rollup for Content Delivery

Step 1: Download hotfix rollup SDL Tridion 2011 SP1–1

Hotfix rollups are available on SDL Tridion World as a ZIP file:

Procedure

  1. Go to SDL Tridion World and log in.
  2. Navigate to the Downloads > Patch Installers page.
  3. Download SDLTridion2011SP1HR#1.zip.
  4. Unpack the ZIP file. The hotfix rollup contains the following subdirectories:
    • Content Delivery
    • Content Manager
    • Database
    • Outbound E-mail
    • Redistributables

Step 2: Update your Content Manager database

Hotfix rollup SDL Tridion 2011 SP1–1 includes updates you need to perform on your Content Manager database.

Procedure

  1. If you are using an MS SQL database:
    1. Stop all TCM Services, Internet Information Services (IIS), and the TCM COM+ Application.
    2. Using Query Analyzer, OSQL, SQLCMD, or SQL Server Management Studio, log on to the SDL Tridion database using sa.
    3. Access the /Database/MSSQL directory and execute the SQL file HR_SQLSERVER.sql.
    4. Restart the TCM Services, Internet Information Services (IIS), and the TCM COM+ Application.
  2. If you are using an Oracle database:
    1. Stop all TCM Services, Internet Information Services (IIS), and the TCM COM+ Application.
    2. Using SQL*Plus, connect as tridion_sys to the database instance.
    3. Grant the following temporary rights to the Tridion database user (typically TCMDBUser):
      GRANT CREATE TRIGGER TO &TCMDBUser; 
      GRANT CREATE PROCEDURE TO &TCMDBUser;
      GRANT CREATE ANY TABLE TO &TCMDBUser;
      GRANT CREATE SEQUENCE TO &TCMDBUser;
      GRANT EXECUTE ON SYS.DBMS_UTILITY TO &TCMDBUser; 
    4. Using SQL*Plus, log on as the Tridion database user (typically TCMDBUser).
    5. Access the /Database/Oracle directory and execute the SQL script HR_ORACLE.sql.
    6. Check the file CM_HR_ORACLE.log for errors.
    7. Revoke the additional rights for the Tridion database user:
      REVOKE EXECUTE ON SYS.DBMS_UTILITY FROM &TCMDBUser; 
      REVOKE CREATE TRIGGER FROM &TCMDBUser; 
      REVOKE CREATE PROCEDURE FROM &TCMDBUser; 
      REVOKE CREATE ANY TABLE FROM &TCMDBUser;
      REVOKE CREATE SEQUENCE FROM &TCMDBUser;
    8. Restart the TCM Services, Internet Information Services (IIS), and the TCM COM+ Application.

Step 3: Install the hotfix rollup on Content Manager

You need to run the upgrade installer to install the hotfix rollup on your Content Manager:

Procedure

  1. Access the Content Manager folder and double-click the executable called SDLTridion2011SP1HR1.exe.
  2. Follow the instructions provided by the installer to upgrade your Content Manager Server.
  3. Optional: The installer restarts the Transport Service, Monitoring Service, and Translation Manager Service. If these services were switched off before installing the hotfix rollup, you will need to turn them off again manually.
  4. Optional: The installer resets configuration settings to default values, for example Timeout settings. Manually change the settings using the MMC Snap-in: in the Microsoft Windows Start menu, select Programs > SDL Tridion > SDL Tridion Content Manager configuration.

What to do next

If you install a new 2011 SP1 Content Manager Server in an existing environment, you need to run the installer from the command line using the command line parameter DB_REQUIRED_VERSION=6.1.0.1 because the hotfix rollup updates the database version from 6.1.0.0 to 6.1.0.1.

Step 4: Install the hotfix rollup on Content Delivery

You install the hotfix rollup on Content Delivery manually by copying the distributed JAR files into your Content Delivery installation \lib directory. The procedure for installation depends on how you installed Content Delivery and what software platform your are using:

Procedure

  1. If you are running Content Delivery in a Java Web application:
    1. Stop your Web application server or Web application containing the Content Deployer.
    2. Access the /Content Delivery/lib directory and copy the distributed JAR files into your Web application WEB-INF\lib directory, replacing the existing file.
    3. If you have Outbound E-mail 2011 SP1 installed, access the /Outbound E-mail directory and copy the audiencemanager_cartridge.jar into your Web application WEB-INF\lib directory, replacing the existing files.
    4. Start your Web Application Server or Web application.
  2. If you are running Content Delivery in a .NET Web application:
    1. Stop the Application Pool and/or IIS Server.
    2. Access the /Content Delivery/lib directory and copy the distributed JAR files into your IIS Web application bin\lib directory, or into your <Tridion installation>\lib directory if you installed Content Delivery in a central directory.
    3. Access the /Content Delivery/dotNet/x86 or /x86_64 directory depending on the system architecture and copy the distributed assemblies into your IIS Web application bin\ directory.
    4. Optional: If you have Outbound E-mail 2011 SP1 installed, access the /Outbound E-mail directory and copy the audiencemanager_cartridge.jar into your Web application \lib directory, replacing the existing file.
    5. Start the Application Pool and/or IIS Server.
  3. If you are running Content Delivery as a Windows service (not in a Web application):
    1. Stop the Content Deployer service.
    2. Access the /Content Delivery/lib directory and copy the distributed JAR files into your <Tridion installation>\lib directory.
    3. Start the Content Deployer service.
  4. Optional: Install hotfix 78355—the installation procedure for Hotfix 78355, concerning the Tridion Linking windows service (deprecated), is described in the hotfix.

What to do next

Step 5: Configure the hotfix rollup for Content Delivery (optional)

The Content Delivery configuration files delivered with the hotfix rollup (the /Content Delivery/configurations directory) include examples of how to implement features provided by specific hotfixes. If you need to use these features, update your existing configuration files by copying and pasting the following code:

Procedure

  1. Hotfix 78258 allows you to specify multiple hosts for one Publication. To configure the hotfix, open your cd_dynamic_conf.xml file in a text editor and add additional <Host> elements for each Publications in the <Publications> element. For example:
    <Publication Id="1">
      <Host Domain="localhost" Port="80" Protocol="http" Path=""/>
      <Host Domain="localhost" Port="8080" Protocol="http" Path=""/>
    </Publication>
  2. Hotfix 78968 allows you to override Claim Store behavior for read-only claims. To configure the hotfix, open your cd_ambient_conf.xml file in a text editor and configure a <ClaimStoreProvider> element in the <Configuration> element to a class that you have implemented to override the default behavior of the Claim Store. For example:
    <ClaimStoreProvider>com.tridion.ambientdata.claimstore.providers.WebClaimStoreProvider</ClaimStoreProvider>
  3. Hotfix 78523 allows you to turn off the reference counting mechanism on Keywords in the cd_storage_conf.xml file. The hotfix is intended for use in very specific situations—reference counting is fundamental to taxonomy functionality and in almost all cases you will not want to change the default behavior. For more information, refer to the hotfix.