5 Post-Installation Tasks

This chapter describes the tasks you must complete after you install and start Oracle WebCenter Interaction, such as configuring the BaseURL, merging changes from your previous deployment, deploying the portal application and Image Service to your application server, and rebuilding your search indexes.

Perform the following steps:

1. Add the BaseURL parameter to portalconfig.xml.

   The BaseURL parameter is a new openconfig setting. During upgrade, your original portalconfig.xml file is preserved so as not to overwrite your changes. This means that new settings will not appear in your portalconfig.xml file, and you must add them manually.

   To add the BaseURL parameter, using a text editor, and add the following to the portal:CachedSettings section of the portalconfig.xml file (located in install_dir\settings\portal:

   <setting name="BaseURL">
         <value xsi:type="xsd:string">strBaseURL</value>
   </setting>
   

   Note:

   You might want to reference the portalconfig.xml file that is installed with new installations, which is located in install_dir\uninstall\ptportal\10.3.3\register\common-settings\noarch\settings\portal\.

2. Merge any changes you had in your configuration.xml file to the newly installed configuration.xml file.

3. Merge any changes you had in your adaptive layout files to the new adaptive layout files.

   During upgrade, the files in install_dir\ptimages\imageserver\plumtree\portal\private\pagelayouts are backed up to install_dir\backup\ptimages\imageserver\plumtree\portal\private\pagelayouts. You must merge any changes you made to those files into the new files.

4. If necessary, deploy the portal application to your application server.

   If you are installing Oracle WebCenter Interaction to a Java application server and the portal was not autodeployed, you must manually deploy the portal WAR or EAR to your application server. The portal WAR and EAR are located in install_dir\ptportal\10.3.3\webapp\.

   • If you are deploying to Oracle WebLogic Server or IBM WebSphere, deploy portal.ear.

5. If necessary, deploy the Image Service to your application server.

   If you are installing Oracle WebCenter Interaction to a Java application server and the portal was not autodeployed, you must manually deploy the Image Service to your application server. For details, see Deploying the Image Service.

6. Restart your portal and search services. For details, see Starting the Oracle WebCenter Interaction Services..

   Caution:

   Do not start the automation server service.

7. Rebuild the portal search index. For details, see Rebuilding the Search Index.

8. Upgrade any other Oracle WebCenter products you previously installed using the associated 10.3.0.1 installers.

   For example, if you use identity services, content services, Oracle WebCenter Collaboration, Oracle WebCenter Analytics, or any other Oracle WebCenter products, you must also upgrade those products. For details, see the upgrade guides for the associated products.

9. If you are using Oracle WebCenter Collaboration or Oracle-BEA AquaLogic Interaction Publisher, rebuild the associated search indexes.

   To rebuild the indexes, access the administration utility for each product through your portal. For details, see the following administrator guides:

   • Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Collaboration

   • Administrator Guide for AquaLogic Interaction Publisher

10. Start your automation server service. For details, see Starting the Oracle WebCenter Interaction Services.

11. Perform additional post-upgrade tasks for optional components as described in the following appendices:

    • If you installed the Tagging Engine, complete the tasks described in Appendix A, "Completing Installation of the Tagging Engine."

    • If you installed or upgraded the Oracle WebCenter Interaction Content Service for Documentum, complete the tasks described in Appendix B, "Completing Installation or Upgrade of Oracle WebCenter Interaction Content Service for Documentum."

    • If you installed the Oracle WebCenter Interaction Content Service for Oracle Universal Content Management, complete the tasks described in Appendix C, "Completing Installation of Oracle WebCenter Content Service for Oracle Universal Content Management."

    • If you installed or upgraded the Oracle WebCenter Interaction Content Service for Lotus Notes, complete the tasks described in Appendix D, "Completing Installation or Upgrade of Oracle WebCenter Interaction Content Service for Lotus Notes."

    • If you installed the Oracle WebCenter Interaction Content Service for Microsoft Windows Files, complete the tasks described in Appendix E, "Completing Installation of Oracle WebCenter Interaction Content Service for Windows Files."

      Note:

      There are no post-install steps if you upgraded Oracle WebCenter Interaction Content Service for Windows Files.

    • If you installed the Oracle WebCenter Interaction Content Service for Microsoft Exchange, complete the tasks described in Appendix F, "Completing Installation of Oracle WebCenter Interaction Content Service for Microsoft Exchange."

      Note:

      There are no post-install steps if you upgraded Oracle WebCenter Interaction Content Service for Microsoft Exchange.

    • If you installed or upgraded the Oracle WebCenter Interaction Identity Service for LDAP, complete the tasks described in Appendix G, "Completing Installation or Upgrade of Oracle WebCenter Interaction Identity Service for LDAP."

    • If you installed or upgraded the Oracle WebCenter Interaction Identity Service for Microsoft Active Directory, complete the tasks described in Appendix H, "Completing Installation or Upgrade of Oracle WebCenter Interaction Identity Service for Microsoft Active Directory."

    • If you installed the Oracle WebCenter JSR-168 Container, complete the tasks described in Appendix I, "Completing Installation of Oracle WebCenter JSR-168 Container."

Deploying the Image Service

Note:

This step is unnecessary if you selected .NET IIS during installation, or if you instructed the installer to autodeploy the Image Service to Apache.

The Image Service is a collection of static, non-secure files that should be served by an HTTP server, such as Apache HTTP Server. The Image Service files are located in install_dir\ptimages\imageserver.

This directory should be aliased in your HTTP server configuration so that the URL specified for the Image Service when the installer was run is correct. For example, if you were running an Apache HTTP Server on port 8082, and you had specified http://webserver:8082/imageserver as your Image Service URL, you might configure Apache HTTP server as follows:

Note:

This is only an example. In a production environment the imageserver directory should be aliased to the Web server by a knowledgeable Web server administrator.

1. In a text editor, open the file Apache_home\conf\httpd.conf.

2. Alias your install_dir\ptimages\imageserver directory to \imageserver on the Web server by adding the following alias to the httpd.conf file:

   Alias \imageserver\ “install_dir\ptimages\imageserver\”
   

3. Create a Directory entry for the imageserver directory:

   <Directory “install_dir\ptimages\imageserver”>
   Options Indexes MultiViews
   AllowOverride None
   Order allow,deny
   Allow from all
   </Directory>
   

4. Save httpd.conf and exit the text editor.

5. When Apache HTTP Server is restarted, http://webserver:8082/imageserver/ should point to install_dir\ptimages\imageserver.

Starting the Oracle WebCenter Interaction Services

This section describes how to start the services associated with Oracle WebCenter Interaction components and the order in which they must be started. Depending on which components you installed, some services might not be applicable to your portal installation.

1. Go to the Windows Services control panel.

   In the Start menu, click Control Panel, then Administrative Tools, then Services, or, at the command prompt, type services.msc.

2. Start Oracle WCI Search host_name.

   Note:

   It is important that third-party virus scanners do not attempt to scan the search service archives.

3. Start Oracle WCI Search Cluster Manager.

4. Start Oracle WCI API Service.

5. Start Oracle WCI LDAP Directory.

6. Start Oracle WCI Automation Service.

   Caution:

   Do not start the automation service until you have rebuilt the portal search index, and, if necessary the Oracle WebCenter Collaboration and Oracle-BEA AquaLogic Interaction Publisher, search indexes

7. Start Oracle WCI Notification Service.

8. Start Oracle WCI Document Repository Service.

9. Start Oracle WCI Logger Service.

10. Start Oracle WebCenter Configuration Manager Service.

11. Start Oracle WCI Content Upload Service.

12. Start Oracle WCI Tagging Service.

13. Start Oracle WCI Search Service.

14. Start Oracle WCI Remote Portlet Service.

15. Start Oracle WCI Content Service for Documentum.

16. Start Oracle WCI Content Service for UCM.

17. Start Oracle WCI Content Service for Microsoft Exchange.

18. Start Oracle WCI Identity Service for LDAP.

Running the Diagnostics Script

This section describes how to use the diagnostics script to determine the health of your Oracle WebCenter Interaction installation before running the portal for the first time after upgrade.

before running the diagnostics script, you must completely configure Oracle WebCenter Interaction using the Configuration Manager. You must also upgrade the portal database.

Run the diagnostics script before starting your portal for the first time after upgrade. It tests basic portal startup functionality. If there are issues with your Oracle WebCenter Interaction installation, the diagnostics script generates a list of warnings and recommendations about how to correct the issues.Run the script, follow the recommendations, and correct any issues before starting your portal for the first time.

• Run the diagnostics script, install_dir\ptportal\10.3.3\bin\diagnostic.bat

Note:

If the diagnostics script fails, run install_dir\ptportal\10.3.3\bin\ptverify.bat and review any issues it discovers.

Rebuilding the Search Index

This section describes the proper procedure for rebuilding your Search index.

Note:

We do not recommend clicking Run Once from the administrative folder or selecting Run Once from the Job Editor. If you click Run Once from the administrative folder, the job log is not available in the Job Editor, which may inhibit troubleshooting if the rebuild fails. If you select Run Once from within the Job Editor, the Search Update Agent is not scheduled to run again in the future.

1. Log in to the portal as the administrator.

2. Click Administration.

3. From the Select Utility drop-down menu, select Search Service Manager.

4. Schedule the next search repair to occur either in the past or in the very near future.

5. Click Finish.

6. Navigate to the administrative folder that contains the search update agents that are registered with the Automation Service.

7. Schedule a search update agents to run in the past or in the very near future.

8. Click Finish.

The next search update agent that runs rebuilds the search index.