System Requirements Specification docuBridge
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 .........................................................................................................18
7.1 MS SQL Server ......................................................................................................18
7.2 ORACLE ................................................................................................................18
7.2.1 ORACLE Database Server ..............................................................................19
7.2.2 ORACLE Data Access Components (ODAC) ..................................................19
System Requirements Specification docuBridge
8. Content Management Systems .....................................................................................20
8.1 Documentum ..........................................................................................................20
8.1.1 Documentum DFS – Webtop ...........................................................................20
8.1.2 Documentum DFC – Webtop ..........................................................................20
8.2 SharePoint (Native) ................................................................................................21
8.3 Mastercontrol (Native) ............................................................................................21
8.4 QUMAS ..................................................................................................................22
8.5 FirstDocs (on Documentum) ...................................................................................22
8.6 D2 (on Documentum) .............................................................................................22
8.7 CARA (on Documentum) ........................................................................................23
8.8 nextDocs (on SharePoint) ......................................................................................23
8.9 LiveLink/OpenText .................................................................................................23
8.10 Optimal Systems ECM ...........................................................................................23
8.11 Veeva Vault ............................................................................................................23
8.12 M-Files ...................................................................................................................24
9. Other Applications .........................................................................................................25
9.1 LORENZ Foundation ..............................................................................................25
9.2 LORENZ eValidator OEM.......................................................................................25
9.3 LORENZ docuRender ............................................................................................25
9.4 Adobe Acrobat .......................................................................................................26
10. Appendix: Support Status ..........................................................................................27
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 4
Disclaimer
© 2017 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.
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 5
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-10 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.
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 6
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
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 7
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 the majority of the work is moved to the
Services means a higher throughput than ever before. Take publishing as an example: in the
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 8
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!
Last but not least, 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.
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 9
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
LORENZ docuBridge FIVE and docuBridge TWO
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)
LORENZ docuBridge FIVE
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
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 10
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
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 11
4. Primary Server Requirements
LORENZ docuBridge FIVE and docuBridge TWO
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
LORENZ docuBridge FIVE and docuBridge TWO
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
LORENZ docuBridge FIVE
Component Minimum Recommended
Processor-Cores 4 4+
RAM 16 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-2
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 12
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.
All hardware requirements relate to the fact that a server platform is used that is designed for
continuous operation.
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. Note:
For a complete list of Operating Systems and their current status please also
refer to chapter 6
There are known issues with systems running with a screen resolution
higher than 100% or higher for text, apps and other.
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
Edge: 40
Firefox: 56.0
Chrome: 61.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.
MSMQ Microsoft Message Queue Server (MSMQ)
.NET Framework Version 4.5 or higher
LORENZ Foundation Version 1.2 (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.
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 13
Please also refer to chapter 7.2.2
Image Rasterizing Image Rasterizing (Provided via Installation Package) Requires the “Microsoft Visual C++ 2010 Redistributable Package” to be installed on the System1
Table 4-3
1 LORENZ docuBridge Rasterizer – Powered by Foxit.Copyright(C) 2003-2017 by Foxit Software Incorporated
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 14
5. Client Requirements
LORENZ docuBridge FIVE and docuBridge TWO
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.
Component Minimum Recommended
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 Protocols TCP/IP, HTTP
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.
Component Status / Comment
Operating System The docuBridge software is a Microsoft Windows-based application that utilizes technologies available on modern Windows Platforms. Note:
For a complete list of Operating Systems and their current status please also
refer to chapter 6
There are known issues with systems running with a screen resolution higher
than 100% or higher for text, apps and other.
.NET Framework Version 4.6.2 or higher
Content Viewing Possible Tools:
Adobe Acrobat (Standard or Professional. See chapter 9.3)
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 15
Image Rasterizing (Provided via Installation Package) Requires the
“Microsoft Visual C++ 2010 Redistributable Package” to be installed on the
System2
Adobe Reader3
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: 40
Firefox: 56.0
Chrome: 61.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
2 LORENZ docuBridge Rasterizer – Powered by Foxit.Copyright(C) 2003-2017 by Foxit Software Incorporated 3 Please note that Adobe Reader provides only viewing functionalities for content in the
Submission Workbench.
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 16
6. Operating System Support
LORENZ docuBridge FIVE and docuBridge TWO
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 10 Certified
Windows Server 2012/R2 incl. Service Packs (as Terminal Server)
Certified
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.
Operating System Status
Windows Server 2016 Certified
Windows Server 2012/R2 incl. Service Packs Certified
Windows Server 2008 R2 incl. Service Packs Supported
Table 6-2
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 17
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.
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 18
7. Database Support
LORENZ docuBridge FIVE and docuBridge TWO
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.
7.1 MS SQL Server
Version docuBridge Application Server
SQL Server 2014 incl. Service Packs Certified
SQL Server 2016 incl. Service Packs Certified
SQL Server 2012 incl. Service Packs Supported
SQL Server 2008 incl. Service Packs Not recommended
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 Systems4.
4 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.
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 19
7.2.1 ORACLE Database Server
Version docuBridge Application Server
ORACLE 12c5 Certified
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.
Version docuBridge Application Server
ORACLE 12c Certified
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 to use this
version.
The Oracle Instant Client needs the “Microsoft Visual C++ 2010 Redistributable
Package” to be installed on the docuBridge application server in order to run properly.
If this package is not installed you may receive an error during an analyze run with
the configPanel stating that the file “msvcr100.dll” is missing.
5 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.
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 20
8. Content Management Systems
LORENZ docuBridge FIVE
In the following tables we list the system versions that are Certified, Supported and Not
Recommended. All other Systems are Not Supported.
8.1 Documentum
Documentum recommends using Documentum Foundation Services (DFS) instead of
Documentum Foundation Classes (DFC) that is listed as deprecated since Documentum 6.
8.1.1 Documentum DFS – Webtop
Version Support Status
Documentum 7.2 Certified
Documentum 7.1 Supported
Documentum 6.7 SP2 Supported
Table 8-1
8.1.2 Documentum DFC – Webtop
Please Note:
Documentum states in the Release Notes that „PIA is deprecated in version 6“
To use Documentum DFC it is required to install the Primary Interop Assembly (PIA) Version
6.5.0.18. The docuBridge system supports all Documentum Versions that support this PIA
version. If you need further clarification about which PIA is supported by your Documentum
system please contact your vendor.
Please find below the Documentum DFC versions that have been tested with the required
version of the PIA (6.5.0.18).
Version Support Status
Documentum 7.2 Supported
Documentum 7.1 Supported
Documentum 6.7 SP2 Supported
Documentum 6.6 Supported
Documentum 6.5 SP3 Supported
Documentum 6.0 Supported
Table 8-2
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 21
8.2 SharePoint (Native)
Version Support Status
SharePoint Server 2016 Supported
SharePoint Server 2013 Certified
SharePoint Server 2010 Supported
SharePoint Server 2007 Supported
Table 8-3
8.3 Mastercontrol (Native)
Version Support Status
MasterControl 11.6 Certified
MasterControl 11.5 Supported
MasterControl 11 Supported
MasterControl 10 Supported
MasterControl 9 Not Recommended
Table 8-4
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 22
8.4 QUMAS
Version Support Status
Sharepoint
QUMAS ComplianceSP Version 2 Supported
DocCompliance
DocCompliance v4.6 Supported
DocCompliance v4.5 Supported
DocCompliance v4.46 Supported
Interfaces
MyQUMAS v4.4 Supported
MyQUMAS v4.2 Supported
Table 8-5
8.5 FirstDocs (on Documentum)
Version Support Status
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.6 D2 (on Documentum)
Version Support Status
D2 is integrated via Documentum Connector. Please see Documentum (Native) for detailed information.7
Supported
Table 8-7
6 Compatibilty mode must be used. If a document is tried to be registered via Drag & Drop
from MyQumas or Qumas DocCompliance
7 Please Note: Drag&Drop from D2 to docuBridge is not supported. Please use the
Copy&Paste feature described in the Configuration Files Admin Guide.
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 23
8.7 CARA (on Documentum)
Version Support Status
CARA is integrated via Documentum Connector. Please see Documentum (Native) for detailed information.8
Supported
Table 8-8
8.8 nextDocs (on SharePoint)
Version Support Status
nextDocs Version 5.4 Supported
Table 8-9
8.9 LiveLink/OpenText
Version Support Status
OpenText CS10 Supported
LiveLink Version 9.7.19 Supported
Table 8-10
8.10 Optimal Systems ECM
Version Support Status
OS-ECM 7.0 Supported
Table 8-11
8.11 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.
8 Please Note: 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.
9Integration with LiveLink requires LiveLink Enterprise Web Services to be installed and
configured.
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 24
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.
Version Support Status
Veeva Vault 17 Certified
Table 8-12
8.12 M-Files
Version Support Status
M-Files 2015 Supported
Table 8-13
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 25
9. Other Applications
LORENZ docuBridge FIVE and docuBridge TWO
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.
9.1 LORENZ Foundation10
Version docuBridge Application Server
Foundation 1.2 Certified
Table 9-1
9.2 LORENZ eValidator OEM
Version docuBridge Application Server
eValidator 5.10 Certified
eValidator 5.9.2 Supported
eValidator 5.9.1 Supported
eValidator 5.9 Supported
Table 9-2
9.3 LORENZ docuRender
Please Note:
Adlib PDF 5.x: If you are using the new Version of Adlib (Adlib PDF 5.x), no
docuRender service for the connection between docuBridge and Adlib is needed.
Adlib PDF 4.x: The software LORENZ docuRender Rendition Service acts as
Interface between the Adlib Express® Rendition server and the LORENZ docuBridge
Server for installations with Adlib Express 4.x. Please note, Adlib will set this version
end of life in October 2017.
System Requirements Specification for the Adlib Express can be obtained via
http://www.adlibsoftware.com/.
10 The LORENZ Foundation is the core component that hosts the Core Services (formerly hosted by docuBridge) and therefore mandatory.
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 26
In the following tables only Systems are listed that are Certified, Supported and Not
Recommended. All other Systems are Not Supported.
Adlib Version
Version Support Status
Adlib PDF OEM 5.4.3 Certified
Adlib PDF OEM 5.3.2 Supported
Versions smaller or equal to Adlib PDF OEM 5.3.1 Not Recommended
Adlib Express 4.10.6 Not Recommended
Table 9-3
9.4 Adobe Acrobat
Version docuBridge Application Client
Adobe Acrobat DC11 Certified
Adobe Acrobat 9 Certified
Adobe Acrobat XI Supported
Adobe Acrobat X Supported
Adobe Acrobat 8 Not Recommended
Table 9-4
11 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.
System Requirements Specification docuBridge
© LORENZ Life Sciences Group 27
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 listed as not supported, 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