Deploying the applications

Ad Hoc Correspondence, Correspondence Reviewer, and the SSSP application are Java applications and must be deployed to a Java application server.

Note:

The Ad Hoc and Reviewer applications are restricted to only access data from the site where they are deployed. Since they depend on the SSSP application for data, they must be deployed to the same Java application server as the SSSP application or with an HTTP web server as a front-end proxy.

Deployment in Control Center

You deploy the WAR files for the Ad Hoc, Reviewer, and SSSP applications in Control Center. For detailed information, see Deploying a web application in the Control Center documentation.

When you add an Ad Hoc and Reviewer application called <Name> in Control Center, the following files are deployed:

WAR file	Application
<Name>_reviewer.war	Correspondence Reviewer
<Name>_adhoc.war	Ad Hoc Correspondence
sssp.war	SSSP application If there is an SSSP application already deployed to the portal root or manual deploy path, this SSSP application is automatically reused.

For information about how to deploy the Ad Hoc application without the Reviewer application or vice versa, see Deploying a single application.

If Control Center is not available, you can deploy the web applications via the command line utilities. For more information, see the Command line utilities documentation. End of tip

Multiple application domains

You can link one Ad Hoc and Reviewer application to one or several application domains. Each application domain can be linked to one single Ad Hoc and Reviewer application.

Dependencies in webportal.properties file

Ad Hoc Correspondence has a dependency to the SSSP application. Correspondence Reviewer has dependencies to both the SSSP application and to Ad Hoc Correspondence.

The dependencies are defined in a webportal.properties file for each web application. The file also contains information about the application domains that the web application is linked to.

The webportal.properties files are generated when you link the Ad Hoc and Reviewer application to an application domain and reside in the following directory:

<Portal root>\<Name>_adhoc\WEB-INF\spring\properties <Portal root>\<Name>_reviewer\WEB-INF\spring\properties

If you update the linking, the webportal.properties files are automatically updated in the \properties folders in the portal root or manual deploy path.

Note:

Updated files in the manual deploy path must be manually copied to the Java application server.

Service gateway in application domain configuration file

The SSSP application uses web services, hosted by a service gateway, to access the runtime repository. The service gateway is defined in the application domain configuration file.

When you link the Ad Hoc and Reviewer application to an application domain, the application domain configuration file is copied to the following directory:

<TOMCAT_HOME>\webapps\sssp\domains

If you update the application domain configuration, the application domain configuration file is automatically updated in the \domains folder in the portal root or manual deploy path.

Note:

Updated files in the manual deploy path must be manually copied to the Java application server.

Keep customized property files

If you redeploy the WAR files, for example to apply a hotfix, any customizations that you have made to the property files are overwritten.

To keep customizations, you can use an external directory outside the portal root for the property files. For more information, see Keeping customized configuration files in the Control Center documentation.