File Manager - Administration Guide : Installation

1. Installation

1.1. Mandatory Post Installation Tasks

After running the TVC installer, you must perform some tasks in order to take the TVC File Manager into use.

1.1.1. Task 1 – Modifying emxNavigator.jsp and emxNavigatorDialog.jsp

The first task is needed in order to include some functionality within the "emxNavigator.jsp" and "emxNavigatorDialog.jsp" pages, which are located within the common folder in your ENOVIA™ application directory.

These changes are needed in order to integrate the TVC File Manager with the ENOVIA™ applications.

Just after the "body" element tag in each of the files, add the corresponding include directive.

/common/emxNavigator.jsp

...
<body ...>
<%@include file="/tvc/filemanager/emxNavigator.jspf"%>
...

/common/emxNavigatorDialog.jsp

...
<body ...>
<%@include file="/tvc/filemanager/emxNavigatorDialog.jspf"%>
...

1.1.2. Task 2 – Modifying JPO’s

This step is not valid for Info Central based applications.

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;

These programs might be updated from one version of TVC to another. Hence, you should check if the program has been changed after installing a newer version of TVC.

Other Central based JPO

There could be other JPOs developed for other centrals, responsible for generating document actions. These JPOs are also to be updated to use File Manager based actions. Few of them are taken care by TVC. Please refer to the list of JPOs that should be replaced by their respective TVC JPOs using the above mentioned steps.

JPO Name	Respected TVC JPO Name
ENODCDocument	TVCENODCDocument

JPO Name

Respected TVC JPO Name

ENODCDocument

TVCENODCDocument

1.1.3. Task 3 - Update /WEB-INF/web.xml for 16x and Later

Due to issues of ENOVIA, you need to modify web.xml after installing TVC and add a by-pass filter as shown below:

<filter-mapping>
    <filter-name>ByPassPatternFilter</filter-name>
    <url-pattern>/tvc/office/client/*</url-pattern>
</filter-mapping>

This is needed for Applet based clients, which needs to be able to download the JAR files.

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>