The ENOVIA File Collaboration Server (FCS) is a mechanism to deploy file servers across the enterprise for efficient handling of file operations within the ENOVIA system. File data is a key contributor to the type of information that is managed by the ENOVIA system. End users manage files by performing check-in and check-out operations. These file can vary in size and depending on the user’s physical location relevant to the ENOVIA system, the performance can greatly be compromised for each file operations. With the FCS architecture, the file servers are placed closer to the end users working at remote sites throughout the world. As a result, file transfers to and from the server are optimized for performance.

The FCS architecture provides the following advantages:

• Enables file servers to be physically located closer to end users for optimal performance

• Facilitates file replication for sharing of data across other enterprise users

• Allows administrators to locally control and manage file data

The FCS architecture also complies with typical IT standards such that:

• Communication between the ENOVIA system and the file server is done through HTTP(s); no wide area network (WAN) database connections are required

• Communication between the user (browser) and the file servers is also through HTTP(s)

• Communication between multiple file servers to support replication is done through HTTP(s)

• Access to local file servers does not require ENOVIA re-authentication

• Support for secured network configurations using reverse/forward proxy and network authentication

Replicate file data across distributed file servers for local access by all enterprise users

Add custom extensions to support additional services such as DRM and other requirements

Distributed File Servers

As users access file data managed by the ENOVIA system, the files can be stored and retrieved from local file servers which provides optimal performance versus retrieving file data from centralized file servers across the wide area network.

FCS Proxy Support and Network Authentication

The FCS server can be deployed with secure and network-friendly configurations. ENOVIA File Collaboration Server (FCS) supports reverse/forward proxy server configurations as well as network authentication.

Automatic File Replication

With distributed file servers, file replication is necessary to facilitate local file transfers for every user. File replication allows files to be stored in multiple file servers. In FCS architecture, the ENOVIA system automatically replicates files across file servers if the file at a local server is stale. This replication occurs on the fly as a user performs a download operation or can also be proactively initiated using background scripts. To overcome network bandwidth and latency, the FCS server automatically compresses certain file types during synchronization to optimize replication performance.

Local File Management

In certain environment, customers may require files to be locally managed versus centrally administered. With FCS architecture, customers can enable distributed file servers to manage file data locally. In this scenario, file replication is turned off so that the file content is not copied to remote locations.

Simplified Setup

The FCS deployment is a simple installation with minimal configuration and prerequisites. The FCS architecture requires an ENOVIA supported Java Application Server and uses standard protocols such as HTTP(s) for secured communication and file transfers. In addition, standard internet configurations like reverse and forward proxies are also supported for improved security and performance. For added flexibility, the remote FCS servers can be one major release prior to ENOVIA Live Collaboration’s server software. This enables deployments to first upgrade the central server to install the latest product capabilities before upgrading remote FCS sites.

Custom FCS Triggers

The ENOVIA File Collaboration Server supports file download and upload triggers. This functionality enables implementers to provide custom code to manipulate the file content as the file data moves to and from the FCS. With this capability, implementers can satisfy various use cases based on customer requirements. As an example, administrators can address Digital Rights Management (DRM) requirements by encrypting the file data as it is being transferred to the user for decryption by the browser or decrypt the file content as it is being stored at the FCS server. Other requirements such as virus checking and watermarking can also be satisfied based on required needs.

Development and APIs

The FCS capabilities are implemented using Java APIs that are leveraged by the ENOVIA Applications. These APIs are fully documented to enable integration of custom add-on modules and/or third-party add-on modules for managing files within the ENOVIA system.