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:
- Download the hotfix rollup
- Update your Content Manager database
- Install the hotfix rollup on Content Manager (using the installer)
- Install the hotfix rollup on Content Delivery (manually)
- 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
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
- If you are using an MS SQL database:
- Stop all TCM Services, Internet Information Services (IIS), and the TCM COM+ Application.
- Using Query Analyzer, OSQL, SQLCMD, or SQL Server Management Studio, log on to the SDL Tridion database using
sa. - Access the /Database/MSSQL directory and execute the SQL file
HR_SQLSERVER.sql. - Restart the TCM Services, Internet Information Services (IIS), and the TCM COM+ Application.
- If you are using an Oracle database:
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
What to do next
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
- If you are running Content Delivery in a Java Web application:
- Stop your Web application server or Web application containing the Content Deployer.
- Access the /Content Delivery/lib directory and copy the distributed JAR files into your Web application
WEB-INF\libdirectory, replacing the existing file. - If you have Outbound E-mail 2011 SP1 installed, access the /Outbound E-mail directory and copy the
audiencemanager_cartridge.jarinto your Web applicationWEB-INF\libdirectory, replacing the existing files. - Start your Web Application Server or Web application.
- If you are running Content Delivery in a .NET Web application:
- Stop the Application Pool and/or IIS Server.
- Access the /Content Delivery/lib directory and copy the distributed JAR files into your IIS Web application
bin\libdirectory, or into your<Tridion installation>\libdirectory if you installed Content Delivery in a central directory. - 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. - Optional: If you have Outbound E-mail 2011 SP1 installed, access the /Outbound E-mail directory and copy the
audiencemanager_cartridge.jarinto your Web application\libdirectory, replacing the existing file. - Start the Application Pool and/or IIS Server.
- If you are running Content Delivery as a Windows service (not in a Web application):
- Stop the Content Deployer service.
- Access the /Content Delivery/lib directory and copy the distributed JAR files into your
<Tridion installation>\libdirectory. - Start the Content Deployer service.
- 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: