# Installation and Upgrade Guide

# Installing, Upgrading, and Deploying the Documentum Portlets

This section describes the following steps that ensure successful installation and deployment of the Documentum Portlets software:

1. Ensure you have performed pre-installation procedures. For details, seeInstalling, Upgrading, and Deploying the Documentum Portlets.
2. Install product files on the Documentum Portlets host and the Image Service. For details, see Installing or Updating Product Files.
3. Deploy the product package to a Web application server. For details, see Deploying the Documentum Portlets Package to Your Application Server.
4. Set PT_HOME for the Web application. For details, see Setting PT_HOME for the Web Application.
5. Run a diagnostic test to verify successful installation and deployment. For details, see Verifying Your Deployment.

## Installing or Updating Product Files

Note: | If you have previously installed Documentum Portlets, we recommend uninstalling the earlier files before installing the current version.

To install product files:

- On the Documentum Portlets host computer, extract the ptdctmportlets.zip file to the <PT_HOME> location.

## Deploying the Documentum Portlets Package to Your Application Server

After installation you must deploy the Documentum Portlets package to your WebLogic application server. You use the WebLogic administrative console to deploy the Documentum Portlets package to the application server.

To deploy to a WebLogic application server:

1. Open the following URL in your browser: http://<hostname>:7001/console
2. Type your user name and password in the dialog boxes and click Sign In.
3. In the left column directory tree, expand the Deployments folder and then click the Web Application Modules folder.
4. In the right pane, click Deploy a New Web Application.
5. Select ptdctmportlets: localhost \ <PT_HOME> \ ptdctmportlets \ 4.1 \ webapp, and click the Target Module radio button.
6. On the next page, click Deploy.

For information on verifying successful deployment, see Verifying Your Deployment.

## Setting PT_HOME for the Web Application

If you deployed the Documentum Portlets application to a Web application server that is not the host for other AquaLogic User Interaction applications, complete the following steps to set PT_HOME for this Web application.

1. Copy <PT_HOME>\ptdctmportlets\4.1\settings\config\pthome.xml to <PT_HOME>.
2. Open pthome.xml and replace <PT_HOME> with C:\bea\alui (or whatever location you gave as the value for the PT_HOME variable).
3. Restart the Web application server.

If you deployed the Documentum Portlets application to a Web application server that is the host for other AquaLogic User Interaction applications, PT_HOME is already set for the for the Web application. Complete the following steps to set PT_HOME for this Web application.

1. Open the pthome.xml configuration file used by the existing AquaLogic User Interaction applications in a text editor. Typically, the pthome.xml file is in the <PT_HOME> directory if you installed software in the default <PT_HOME> location.
2. Add the following product section within the <pthome> element:

    <product name="ptdctmportlets">

       <install version="4.1">

          <path>C:\bea\alui\ptdctmportlets\4.1</path>

                                   <configpath>C:\bea\alui\ptdctmportlets\4.1\settings\config
    </configpath>

       </install>

    </product>

3. Restart the Web application server.

Note: | Replace the C:\bea\alui with whatever location you specified for your <PT_HOME> variable

## Verifying Your Deployment

The Documentum Portlets installation provides a deployment verification utility you can use to verify successful deployment.

To verify deployment:

1. Open a Web browser to the index page for the verification utility, for example:

http://<RemoteServer>:7001/ptdctmportlets/custom/check/

2. Complete the steps as described in the utilities summary page to verify the correct configuration of deployment components.

Note: | If you encounter errors, follow instructions in the error messages or see Troubleshooting.