File Manager - Administration Guide : Installation

1. Installation

1.1. Mandatory Post Installation Tasks

After installing TVC, you must perform two tasks in order to take the TVC File Manager into use.

1.1.1. Task 1 – Modifying emxNavigator.jsp

The first task is needed in order to include some functionality within the "emxNavigator.jsp" page (resides in the common folder in your application directory). The only change needed in this file, is to add a single line of code.

Just after the "body" element tag, add the include line below:

<body ...>
<%@include file = "/tvc/office/tvcOfficeObjectTag.jspf"%>
...

1.1.2. Task 2 – Modifying JPO’s

This step is not valid for Info Central based applications. Pleas look at chapter 7 if you are using the Info Central.

The second task will replace the functionality in two JPO’s that generates the action links for a document (i.e. the links that are generated to download, view, checkout, check-in, lock, unlock or update a file).

The names of the programs to replace are:

emxCommonDocumentUI
emxCommonFileUI

While the TVC Office component was installed, two programs were added to the database. The two programs mentioned above must be replaced with these new programs. The MQL code below illustrates how to do so. Simply launch the commands from a MQL prompt (ensure that correct user and password is used).

# Set context to a super user, for example creator +
set context user creator password xxxxxx;

# Make backups of the original programs +
mod program emxCommonDocumentUI name emxCommonDocumentUI-BACKUP; +
mod program emxCommonFileUI name emxCommonFileUI-BACKUP;

# Rename the corresponding TVC programs +
mod program TVCemxCommonDocumentUI name emxCommonDocumentUI; +
mod program TVCemxCommonFileUI name emxCommonFileUI;

If your environment is setup for mode, then you must include the TVC JAR files from the application server within the MX_CLASSPATH variable. Otherwise the JPO’s will neither compile nor execute.

The simplest approach to include the same classes for the server and the application server is to include the "WEB-INF/classes" folder and the "WEB-INF/lib" folder within the MX_CLASSPATH variable.

These programs might be updated from one version of TVC to another. Hence, you need to update these program objects whenever you upgrade TVC to a newer version.

1.2. Using File Manager with Container based LDAP Authentication

If you have configured your Main Collaboration Server to use container based LDAP authentication, you need to update the deployment descriptor (the web.xml file) and add a so called security constraint in there together with the security constraints as described by the ENOVIA documentation regarding LDAP authentication.

In your web.xml file, you add the following section. Add it together with the other security constraint definition.

<security-constraint>
    <web-resource-collection>
        <web-resource-name>FCS</web-resource-name>
        <description>FCS requests</description>
        <url-pattern>/servlet/fcs/*</url-pattern>
    </web-resource-collection>
</security-constraint>