System Requirements Specification€¦ · System Requirements Specification docuBridge FIVE and TWO 19.1 . System Requirements Specification docuBridge FIVE and TWO 19.1 , . . , ...

System Requirements

Specification docuBridge FIVE and TWO 19.1

April 2019

© LORENZ Life Sciences Group

System Requirements Specification docuBridge FIVE and TWO 19.1

Table of Contents

Disclaimer ................................................................................................................................. 4

1. Getting Started .................................................................................................................. 5

1.1 Introduction ................................................................................................................ 5

1.2 How this document is organized ................................................................................ 5

1.3 Target Audience ......................................................................................................... 5

1.4 Terms & Definitions .................................................................................................... 6

2. General System Overview ................................................................................................ 7

2.1 The docuBridge System Architecture ........................................................................ 7

2.2 The Choice is Yours ................................................................................................... 8

3. System Design Scenarios ................................................................................................. 9

3.1 Introduction ................................................................................................................ 9

3.2 Primary Server ........................................................................................................... 9

3.3 Primary + Extension Server(s) ................................................................................... 9

4. Primary Server Requirements ......................................................................................... 11

4.1 Hardware Requirements .......................................................................................... 11

4.1.1 Basic and Standard Systems ............................................................................ 11

4.1.2 Enterprise System ............................................................................................ 11

4.2 Software Requirements ........................................................................................... 12

5. Client Requirements ........................................................................................................ 14

5.1 Hardware Requirements .......................................................................................... 14

5.2 Software Requirements ........................................................................................... 14

6. Operating System Support .............................................................................................. 16

6.1 Application Client Operating Systems ...................................................................... 16

6.2 Application Server Operating Systems .................................................................... 16

6.3 Use of Virtualized Environments .............................................................................. 17

6.4 Use of Terminal Emulation Environments ................................................................ 17

7. Database Support ........................................................................................................... 19

7.1 MS SQL Server ........................................................................................................ 19

7.2 ORACLE .................................................................................................................. 19

7.2.1 ORACLE Database Server ............................................................................... 20

7.2.2 ORACLE Data Access Components (ODAC) ................................................... 20


8. Content Management Systems ....................................................................................... 22

8.1 Documentum DFS - Webtop .................................................................................... 22

8.2 SharePoint (Native) .................................................................................................. 22

8.3 Mastercontrol (Native) .............................................................................................. 22

8.4 Veeva Vault .............................................................................................................. 22

8.5 QUMAS .................................................................................................................... 23

8.6 FirstDocs (on Documentum) .................................................................................... 24

8.7 D2 (on Documentum) ............................................................................................... 24

8.8 CARA ....................................................................................................................... 24

8.9 nextDocs (on SharePoint) ........................................................................................ 24

8.10 LiveLink/OpenText ................................................................................................... 25

8.11 Optimal Systems ECM ............................................................................................. 25

8.12 M-Files ..................................................................................................................... 25

9. Other Applications ........................................................................................................... 26

9.1 LORENZ Foundation ............................................................................................... 26

9.2 LORENZ eValidator OEM ........................................................................................ 26

9.3 LORENZ docuRender .............................................................................................. 26

9.4 Adobe Acrobat ......................................................................................................... 27

10. Appendix: Support Status ............................................................................................ 28


© LORENZ Life Sciences Group 4

Disclaimer

© 2019 LORENZ Life Sciences Group

All rights reserved in whole or in part and in all forms of media throughout the world. Any

rights not expressly granted herein are expressly reserved by LORENZ Life Sciences Group.

All information and articles in this document are covered by copyright law. Articles and

documents contained in this document are the copyright of LORENZ Life Sciences Group.

Any commercial reproduction of any material included here is expressly prohibited.

Except as stated above, no part of this document may be reproduced, stored in a retrieval

system, or transmitted in any form, or by any means, electronic, mechanical, photocopying,

recording or otherwise, without prior written permission of LORENZ Life Sciences Group, or

the respective copyright owner.

Copyright includes the use of any underlying hypertext markup used in the creation of this

document.

All trademarks, service marks and logos (trademarks) of companies and products mentioned

or used in this document are the property of their respective owners.

Trademarks

The following trademarks of other companies may appear in this document:

Microsoft is a registered trademark of Microsoft Corporation in the United States and/or other

countries

Microsoft Windows including all versions are registered trademarks or trademarks of

Microsoft Corporation in the United States and/or other countries.

Acrobat is a trademark of Adobe Systems Inc.

All other names of products or companies mentioned in this document are trademarks or

registered trademarks of their respective owner.



1. Getting Started

1.1 Introduction

This document describes the system requirements for docuBridge and outlines the general

architecture of the docuBridge platform. It lists system design scenarios and shows support

levels for various 3rd party components.

This document describes both docuBridge FIVE and docuBridge TWO system requirements.

Sections are preceded by an indication of their relevance to one or more docuBridge

variations, e.g. LORENZ docuBridge FIVE and/or docuBridge TWO

LORENZ docuBridge variations have the following product logos:

Figure 1-1

1.2 How this document is organized

This guide is organized in chapters plus appendices:

• Chapter 1 contains general information about the document and its use.

• Chapter 2 contains an overview of the docuBridge System Architecture

• Chapter 3 contains supported System docuBridge Design Scenarios

• Chapter 4 contains the hardware and software requirements for the docuBridge

Primary Server

• Chapter 5 contains the hardware and software requirements for the docuBridge

Client

• Chapter 6-9 contains certified and supported Systems and Components

• Appendices list the support levels for 3rd Party Components.

1.3 Target Audience

This document is targeting the experienced IT Person who is tasked with system sizing for a

docuBridge system, installing a docuBridge system on a single server or evaluating the

technical background of docuBridge for planning or decision-making processes.

This document may also be of interest to a Project Manager or Department Manager with a

casual understanding of IT Technology who wants to gain insight on the technical platform a

docuBridge system is operated on.



1.4 Terms & Definitions

The following list defines some terms and definitions used throughout the scope of this

document.

Component Description

Primary Server The docuBridge Primary Server is the core of the docuBridge system where all available services are hosted and executed. (Including the LORENZ Foundation.)

Extension Server The docuBridge Enterprise Edition supports the addition of Extension Servers to the system. Those servers can be configured to host distributed Job Service Instances.

Database Server The docuBridge system requires a database to store data. The Database Server hosts this database and makes it available to the docuBridge system.

Instance An Instance represents a logically configured set of related services connecting to one CoreServices. One docuBridge System consists of one Instance with services hosted on one physical server or distributed across multiple servers (Job Service).

Table 1-1



2. General System Overview

LORENZ docuBridge FIVE

2.1 The docuBridge System Architecture

Figure 2-1

The docuBridge System is based on a Service Oriented Architecture (SOA). Unlike previous

versions of docuBridge, the introduction of Services separates – for the first time – the

business logic of specific tasks from the user interface and encapsulates each task in a

better manageable entity.

The result is a system that is scalable to the actual needs – the set of services required to

operate a docuBridge system is clustered into an Instance. Instances can be operated on a

single physical server or spread across several physical servers to provide redundancies and

increase performance.

The service-oriented approach also makes the system easier to validate: updates to the

system can now be issued to a specific, independently versioned Service or set of Services.

When implementing such an update, the impact on the system is easily determined and re-

validation of the system can be controlled by an appropriate risk assessment.

Also, the service-oriented approach reduces the workload on the end user’s system –

either the local PC or a terminal services environment: the client is no longer performing

heavy-duty tasks with local resources, thus eating up valuable memory and CPU cycles – it

will simply issue a job to a centralized service that will then take care of the actually

processing. The end user may even shut down his system after the job request has been

send!

The general performance of the system should increase: the fact that in many cases less

information is transferred over the network because most of the work is moved to the

Services means a higher throughput than ever before. Take publishing as an example: in the



past, the client requested all content files, transferred them over the network to the local

machine and eventually published back to a network drive. Twice, the data had to cross the

network lines – with a centralized Service taking care of the publishing, network transfer is

kept in a controlled, usually high-bandwidth environment, the corporate service center!

The service-oriented approach also supports tightened security, paying tribute to the

needs of many of our customers: all information in the system is accessed through the

system. Publishing, for example, will take place centrally so no content files are transferred to

a local PC and the result will be stored in a centralized location. Access to this location now

is governed by access privileges, not simply physical access to the machine as such.

2.2 The Choice is Yours

The Service Oriented Architecture offers possibilities – and the good thing about it is that

each customer can choose how far to go: the system will run perfectly fine in a Single

Instance Environment on a single server, just like past versions did – or you might be looking

into a slightly larger system…

Customers installing into a Single Instance / Single Server Environment will still benefit from

many of the features lined out above. Additionally, customers have the possibility to grow at

any time. When your existing implementation becomes too small, add processing

capabilities. If the system currently meets your expectations, there is no need to change it.



3. System Design Scenarios

LORENZ docuBridge FIVE and docuBridge TWO

3.1 Introduction

The docuBridge platform offers a variety of possible scenarios when it comes to designing

the environment the software is operating in. With this release of docuBridge, LORENZ

supports the following scenarios:

• Primary Server

• Primary Server + Extension Server(s)

Should you require assistance with the selection of an appropriate scenario or want to use a

scenario not lined out here, please contact LORENZ for assistance.

3.2 Primary Server


This scenario includes a single Server hosting the primary instance. This is what you will get

by installing the system without any customizations. The database may be on the same

server or on an external server. You can have several such servers at your site (for example

to separate testing from production). They will all operate independently of each other.

Figure 3-1

3.3 Primary + Extension Server(s)


As docuBridge is able to run with distributed JobServices on Extension Servers, this scenario

can be used to distribute the load on the Primary Server. The database may be on one of

these servers or on an external server. This configuration allows to e.g.

• separate Publishing Jobs from Imports Jobs



• distribute parallel Publishing on different machines to increase the overall

performance

• to make sure that one JobService is always available for Publishing or Import Jobs

• etc.

In the following picture, the extension server runs an extension instance with a JobService

only. The primary instance on the primary server also runs a JobService.

Figure 3-2



4. Primary Server Requirements


4.1 Hardware Requirements

The following Hardware Requirements recommendations are based on the license package

of the system. LORENZ differentiates between a Basic License, a Standard License and an

Enterprise License.

4.1.1 Basic and Standard Systems


The hardware listed below is sized to ensure proper operation of a docuBridge system,

leaving enough processing power to the system to satisfy the operation in small to medium

environments at a reasonable performance.

Component Minimum Recommended

Processor-Cores 2 4

RAM 4 GB 16 GB

Display Configuration As required. The docuBridge Primary Server does not have any specific requirements towards the display capabilities of the system.

Network Protocols TCP/IP, HTTP

Network Speed 100 MBit/Sec. 1000 MBit/Sec or above

Table 4-1

4.1.2 Enterprise System



Processor-Cores 4 4+

RAM 32 GB 32+ GB

Display Configuration As required. The docuBridge Primary Server does not have any specific requirements towards the display capabilities of the system.


Network Speed 100 MBit/Sec. 1000 MBit/Sec or above

Table 4-2



Please Note:

• These suggestions for sizing the hardware of a server shall be treated as guidance

and should be pursued with reasonable foresight of potential system growth.

• LORENZ docuBridge Service communication is managed via Microsoft Windows

Communication Foundation (WCF). To build WCF services that can scale and are

high performant this configuration might need to be adapted in certain environments.

Service throttling in WCF is used to limit the service throughput so that the resource

consumption (memory, processor, disk, network, etc.) in the system is at an

acceptable level, e.g. ensure the service doesn't consume resources beyond

acceptable limits.

o By default, Microsoft set the maximum of connections to a service, e.g. a user

session, to “100 * processor count”.1 This means that the amount of CPUs is

also related to the amount of users connecting to the system.

o If you want to operate docuBridge in an environment where available CPUs

and the number of users connecting to the system does not fulfill this

requirement you can add more CPUs (recommended) or you can change the

default configuration to allow more connections. In this case please contact

LORENZ.

• All hardware shall be designed for continuous operation, i.e. no consumer hardware

but server grade hardware should be used.

4.2 Software Requirements

The software listed below names the required items that need to be present in order to install

and operate a docuBridge Primary Server.

Component Status / Comment

Operating System An Operating System for the docuBridge Primary Server is required.

Please Note:

For a complete list of Operating Systems and their support status

please also refer to chapter 6.

There are known issues with systems running with a custom scaling

other than 100% for text and apps.

IIS Internet Information Server must be installed.

Browsers The following browsers have been tested and are supported in this release. Even though a specific version of a browser is not listed, it still may work (especially for browsers with rapid release cycles such as Chrome, Firefox).

• Internet Explorer: 11

1 https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/wcf/servicethrottling

https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/wcf/servicethrottling




• Edge: 44.0

• Firefox: 66.0

• Chrome: 73.0

Note:

• JavaScript must be enabled on all browsers

• Web Applications are optimized for the Internet Explorer

For best performance:

• 'Disable script debugging' in the browser's config options must be checked;

• Caching on Internet Explorer must be activated.

.NET Framework Version 4.6.2 or higher

LORENZ Foundation Version 19.1 (see 9.1)

ORACLE In case you are using ORACLE as an RDBMS and your ORACLE Database is installed on a dedicated server, you need to ensure the availability of an appropriate ORACLE Client layer. → ORACLE Data Access Components (ODAC) for .Net 4 The Oracle Instant Client needs the “Microsoft Visual C++ 2010 Redistributable Package” to be installed in order to run properly. Please also refer to chapter 7.2.2

Image Rasterizing (webAccess)

Image Rasterizing (Provided via Installation Package) → Requires the “Microsoft Visual C++ 2010 Redistributable Package” to be installed on the System2

Table 4-3

2 LORENZ docuBridge Rasterizer – Powered by Foxit. Copyright(C) 2003-2018 by Foxit Software Incorporated



5. Client Requirements


5.1 Hardware Requirements

The hardware listed below is sized to ensure proper operation of a docuBridge Client in a

typical office environment, leaving enough processing power to the system to satisfy the

operation typical business applications while working with docuBridge.


Processor-Cores 2 2+

RAM 3 GB 3+ GB

Display Configuration Single Monitor, 1920 x 1080 Pixel Single Monitor, 1920 x 1080 Pixel or dual-monitor environment.


Network Speed 100 MBit/Sec. 1000 MBit/Sec

Table 5-1

Please Note: These suggestions for sizing hardware shall be treated as guidance and should

be pursued with reasonable foresight of potential system growth.

5.2 Software Requirements

The software listed below lists the required elements that need to be present in order to

operate the docuBridge system.


Operating System The docuBridge software is a Microsoft Windows-based application that utilizes technologies available on modern Windows Platforms.

Please Note:

For a complete list of Operating Systems and their support status

please also refer to chapter 6.

There are known issues with systems running with a custom scaling

other than 100% for text and apps.

.NET Framework Version 4.6.2 or higher

Content Viewing Possible Tools:




• Default View (Built-In)3

• [optional] Adobe Acrobat (Standard or Professional. See chapter 9.3)

• [optional] Adobe Reader4

Browser The following browsers have been tested and are supported in this release. Even though a specific version of a browser is not listed, it still may work (especially for browsers with rapid release cycles such as Chrome, Firefox).

• Internet Explorer: 11

• Edge: 44.0

• Firefox: 66.0

• Chrome: 73.0

Note:

• JavaScript must be enabled on all browsers

• Web Applications are optimized for the Internet Explorer

For best performance:

• 'Disable script debugging' in the browser's config options must be checked;

• Caching on Internet Explorer must be activated.

Table 5-2

3 The Default content view uses the PDFium library. Copyright 2019 PDFium.org

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY

DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING

NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY

OF SUCH DAMAGE.

4 Please note that Adobe Reader provides only viewing functionalities for content in the Submission

Workbench.



6. Operating System Support


In the following tables we list the system versions that are Certified, Supported and Not

Recommended.

Please Note: All other system versions are Not Supported.

6.1 Application Client Operating Systems

LORENZ requires the production versions of the docuBridge Client to be installed on a Client

Operating System. In order to simplify system testing, it is possible to install a docuBridge

Client directly on the docuBridge Application Server. This cannot be used for productive

compilation and/or publishing.

Operating System Status

Windows 105 Certified

Windows Server 2012/R2 incl. Service Packs (as Terminal Server)

Certified

Windows Server 2016 incl. Service Packs (as Terminal Server)

Supported

Windows 8 incl. Service Packs Supported

Windows 7 incl. Service Packs Supported

Windows Server 2008 R2 incl. Service Packs (as Terminal Server)

Supported

Table 6-1

6.2 Application Server Operating Systems

LORENZ requires the production version of the docuBridge Application Server to be installed

on a Windows Server Operating System. The installation of the docuBridge Application

Server on a Windows Client Operating System is not supported for productive compilation

and/or publishing.

LORENZ does not support the Installation of docuBridge on Windows Server Operating

Systems derived from any not supported constellations.

5 Please Note: To use the Windows Authentication functionality for LORENZ web applications on MS Windows 10, you will need to have MS Windows 10 Pro. MS Windows 10 Home edition does not support Windows Authentication.



Operating System Support Status

Windows Server 2016 Certified

Windows Server 2012/R2 incl. Service Packs Certified

Windows Server 2019 Supported

Windows Server 2008 R2 incl. Service Packs Supported

Table 6-2

6.3 Use of Virtualized Environments

LORENZ supports the use of virtualized environments, both for the docuBridge Application

Server and the docuBridge Client. Our own testing is, in part, performed on such

environments.

However, LORENZ does not formally certify any virtualization platform because we consider

these platforms to be transparent, i.e., we expect the virtualization environment with an

installed supported or certified operating system to perform identically when compared to the

same operating system installed into a physical environment.

Nevertheless, LORENZ would like to remind customers that there are certain techniques that

can be applied to virtualized environments which may cause issues with the licensing engine

of LORENZ docuBridge. The hardware code for docuBridge is calculated based upon a

combination of characteristics of the system in which it is installed: BIOS, CPU, Primary

HDD, NIC MAC Address, Mainboard, and Operating System. If through the use of

virtualization specific procedures too many of these identifiers change (e.g. when moving a

virtualized environment to a different node) then the system will consider the license to be

invalid.

6.4 Use of Terminal Emulation Environments

LORENZ also supports the use of terminal emulation environments such as CITRIX and

Windows Terminal Services.

LORENZ does not formally certify these environments because we consider these platforms

to be transparent. We expect the exposed operating system (e.g. Windows Server 2012-

based environments) to behave identical to a true Windows Server 2012 installation.

LORENZ considered with the specifics of such environments when designing the application

(e.g. separation of application and user-related data) and shall continue to do so where

appropriate in the future.

LORENZ is aware that certain technologies behave differently on terminal emulation

environments, including (but not limited to) display characteristic, support for Windows

Presentation Framework (WPF), etc. Where possible, we have tried to eliminate the impact



of such behavior, e.g. by not using complex animations which are known to have issues on

such environments.



7. Database Support



Recommended.


7.1 MS SQL Server

Version Support Status

SQL Server 2016 incl. Service Packs Certified

SQL Server 2017 incl. Service Packs Supported



SQL Server 2008 incl. Service Packs Not Supported

Table 7-1

7.2 ORACLE

As ORACLE generally offers a large number of patches, some of which are not made

publicly available, LORENZ has decided to specify the actual versions that development and

testing uses.

LORENZ officially tests against ORACLE Database Servers hosted on Windows Systems6.

6 LORENZ does not expect the same ORACLE Version to behave differently on a UNIX System than

on a Windows system, but cannot rule out the possibility that there may be differences.



7.2.1 ORACLE Database Server


ORACLE 12c7 Certified

ORACLE 18c Supported

ORACLE 11g R2 Supported

ORACLE 11g Not Recommended

Table 7-2

7.2.2 ORACLE Data Access Components (ODAC)

LORENZ recommends using the ORACLE Data Access Components (ODAC) – also

referred to as “ORACLE Instant Client” – using the XCopy Distribution.

On docuBridge Application Servers running a 32bit Operating System, you need to install the

32bit ODAC package. On docuBridge Application Servers running a 64bit Operating System

(such as Windows Server 2008 R2), you need to install the 64bit packages of ODAC. The

ODAC package needs to be installed for .Net 4.


ORACLE 12c Certified

ORACLE 18c Supported

ORACLE 11g R2 Supported

ORACLE 11g Not Recommended

Table 7-3

Please Note:

Please use the ODAC Package that is related to your Database installation e.g. if ORACLE

12.1.0.1 is installed also use the ODAC for version 12.1.0.1.

We got some indication that Oracle Instant Client ODAC 12.1.0.2.0 can cause issues that may

result in service crashes. Therefore, we do not recommend using this version.

The Oracle Instant Client needs the “Microsoft Visual C++ 2010 Redistributable Package” to be

installed on the docuBridge application server to run properly. If this package is not installed, you

7 We got some indication that Oracle 12c can cause performance issues in environments that have

upgraded from Oracle 11g to Oracle 12c. Therefore, we do recommend enhanced testing before

using this in production.



may receive an error during an analyze run with the configPanel stating that the file

“msvcr100.dll” is missing.



8. Content Management Systems



Recommended. All other Systems are Not Supported.

8.1 Documentum DFS - Webtop


OpenText Documentum 16.4 Certified

Documentum 7.2 Supported

Documentum 7.1 Supported

Documentum 6.7 SP2 Supported

Table 8-1

8.2 SharePoint (Native)


SharePoint Server 2016 Supported




Table 8-2

8.3 Mastercontrol (Native)


MasterControl 11.6 Supported

MasterControl 11.5 Supported

MasterControl 11 Supported

MasterControl 10 Supported

MasterControl 9 Not Recommended

Table 8-3

8.4 Veeva Vault

Please Note:



The docuBridge release was developed based on and tested against the version of the Veeva

Vault listed below using the then current version of the Veeva Vault API. Therefore, this new

docuBridge release requires at a minimum the stated Veeva Vault version.

Previous docuBridge releases that were tested against previous versions of Veeva Vault and the

Veeva Vault API will continue to operate as Veeva certifies the upwards compatibility of the

Veeva Vault API with all releases of Veeva Vault.

“Beginning with the release of 18R3, Veeva Vault will disable TLS 1.0 and 1.1 and require TLS

1.2 with strong ciphers in order to align with industry best practices for security and data

integrity. Once we disable TLS 1.0 and 1.1, non-TLS 1.2 HTTPS connections, web browsers,

and Vault API integrations will be unable to access Veeva Vault.” (Published July 2, 2018 by Veeva Vault)


Veeva Vault 19 Certified

Table 8-4

8.5 QUMAS

Please note: .NET Framework 3.5 is required for a working connection between docuBridge

and Qumas.


Sharepoint

QUMAS ComplianceSP Version 2 Supported

DocCompliance

DocCompliance v4.8 Supported





Interfaces

MyQUMAS v5.1 Supported


8 Compatibilty mode must be used. If a document is tried to be registered via Drag & Drop from

MyQumas or Qumas DocCompliance





Table 8-5

8.6 FirstDocs (on Documentum)


FirstDocs is integrated via Documentum Connector. Please see Documentum (Native) for detailed information. The integration is also dependent on the FirstDocs Client being used using the original Documentum Webtop drag & drop format.

Supported

Table 8-6

8.7 D2 (on Documentum)


D2 is integrated via Documentum Connector. Please see Documentum (Native) for detailed information.9

Supported

Table 8-7

8.8 CARA


CARA 3.11 (via REST API) Certified

Integration via Documentum Connector. Please see Documentum (Native) for detailed information.10

Supported

Table 8-8

8.9 nextDocs (on SharePoint)


nextDocs Version 5.4 Supported

9 Please Note: Drag&Drop from D2 to docuBridge is not supported. Please use the Copy&Paste

feature described in the Configuration Files Admin Guide.

10 Drag&Drop from CARA to docuBridge is only supported for single files (using a custom widget). To

use the Copy&Paste feature described in the Configuration Files Admin Guide, a custom widget needs

to be enabled for CARA, please contact your vendor for details.



Table 8-9

8.10 LiveLink/OpenText


OpenText CS16.2 Certified11

OpenText CS10 Supported

LiveLink Version 9.7.112 Supported

Table 8-10

8.11 Optimal Systems ECM


OS-ECM 8.0 Supported

OS-ECM 7.0 Supported

Table 8-11

8.12 M-Files


M-Files 2015 Supported

Table 8-12

11 Drag&Drop from OpenText CS16 to docuBridge is only supported for single files. 12 Integration with LiveLink requires LiveLink Enterprise Web Services to be installed and configured.



9. Other Applications



Recommended.


9.1 LORENZ Foundation13


Foundation 19.1 Certified

Table 9-1

9.2 LORENZ eValidator OEM


eValidator 19.1 Certified

eValidator 18.2 Supported

eValidator 18.1.1 Supported

eValidator 18.1 Supported

Table 9-2

9.3 LORENZ docuRender

LORENZ docuRender is an Adlib rendition server integrated into your docuBridge solution. In

the following tables, the Adlib PDF sever only Systems are listed that are Certified,

Supported and Not Recommended. All other Systems are Not Supported.


Adlib PDF 6.0.1 Certified

Adlib PDF OEM 5.4.3 Not Recommended

Adlib PDF OEM 5.3.2 Not Recommended

Table 9-3

13 The LORENZ Foundation is the core component that hosts the Core Services (formerly hosted by docuBridge) and therefore mandatory.



For those upgrading from Adlib 4.x, for Adlib PDF 6.x and 5.x, no docuRender service for the connection between docuBridge and Adlib is needed.

Please Note: Adlib Express 4.x. no longer supported and is not recommend. This version was

set to end of life in October 2017.

System Requirements Specification for the Adlib Express can be obtained via

http://www.adlibsoftware.com/.

9.4 Adobe Acrobat


Adobe Acrobat DC14 19.010.20098 Continuous Track Certified

Adobe Acrobat DC 17.011.30127 Classic Track Certified

Adobe Acrobat XI Supported

Adobe Acrobat X Supported

Adobe Acrobat 9 Supported

Adobe Acrobat 8 Not Recommended

Table 9-4

14 Please Note:

• Adobe Acrobat DC has a problem with its installation package that leads to viewing problems

in docuBridge. Please perform a repair installation of Adobe Acrobat DC after you have

installed it the first time.

• The above listed version of Acrobat DC has been tested and is therefore certified for this

release. Even though a specific version of Acrobat DC is not listed, it still may work (especially

for Adobe Acrobat Continuous Track with rapid release cycles).

http://www.adlibsoftware.com/



10. Appendix: Support Status

Status Description

Certified If an item is listed as certified it means that LORENZ has successfully tested this item in combination with our products. This category is considered very Low Risk from a customers’ perspective in terms of potential issues, validation requirements, etc.

Supported If an item is listed as supported it means that LORENZ has seen this working in combination with our products, we have not included it in our “final” acceptance testing of the product. This category is considered Low Risk from a customer’s perspective in terms of potential issues, validation, etc.

Not Recommended If an item is listed as not recommended it means that even if it might be possible to use it in combination with our product, we have seen scenarios in which this combination resulted in issues (technical and business). Therefore, we do not recommend the use of this item. We will provide technical support on a “Best efforts” basis, but we are not likely to make changes to accommodate issues discovered. Additional charges may apply for supporting this category. This category is considered a Medium Risk from the customer’s perspective in terms of potential issues, validation, etc.

Not Supported If an item is not listed, it means that we have found reproducible evidence that this item is causing issues in combinations with our products. Could possibly work but we expect major issues (technical or business). We may be able to assist in some situations, but our official position is “Don’t do it!” and we may require a formal sign-off from the customer to that effect before providing assistance. Additional charges may apply for assisting with this category. Even a reasonably complete IQ/OQ/PQ process may not be sufficient to detect or avoid potential problems in this category. This category is considered a Medium to High Risk from the customer’s perspective in terms of potential issues, validation, costs, etc.

Table 10-1

LORENZ Life Sciences Group

Internet: www.lorenz.cc | E-Mail: www.lorenz.cc/email

LORENZ Archiv-Systeme GmbH

Eschborner Landstrasse 75

60489 Frankfurt/Main

GERMANY

Tel +49 69 78 991-901

Fax +49 69 78 991-129

LORENZ Life Sciences Ltd.

No. 1 Farnham Road

Guildford, Surrey GU2 4RG

UNITED KINGDOM

Tel +44 14 83 903 861

Fax +44 20 76 812 676

LORENZ Polska

APC Instytut Sp. z o.o.

ul Grójecka 22/24/4

Warsaw 02-301

POLAND

Tel +48 22 6686 823

Fax +48 22 6689 981

LORENZ International LLC

1515 Market Street, Suite 1200

Philadelphia, PA 19102

USA

Tel +1 866 9567 369

+1 866 9LORENZ

Fax +1 866 2956 967

LORENZ Newbook Inc.

2355 Derry Road East, Unit 39

Mississauga, Ontario, L5S 1V6

CANADA

Tel +1 905 6709 997

+1 800 5889 334

LORENZ Life Sciences India Pvt Ltd.

Olympia Tech Park, Level -2, Altius

No: 01, Sidco Industrial Estate

Ekkatuthangal, Guindy

Chennai-600 032

INDIA

Tel +91 44 42 994 219

Fax +91 44 42 994 310

Digital Media System Co., Ltd.

Tsukiji No. 1

Nagaoka Building 2-3-4

Tsukiji, Chuo-ku, Tokyo 104 - 0045

JAPAN

Tel +81-3-5550 5595

Fax +81-3-5550 5596

System Requirements Specification€¦ · System Requirements Specification docuBridge FIVE and TWO 19.1 . System Requirements Specification docuBridge FIVE and TWO 19.1 , . . , ...

Documents