docuBridge 5.7
October, 2015
© LORENZ Life Sciences Group
System Requirements
Specification
System Requirements Specification - docuBridge 5.7 Disclaimer
© LORENZ Life Sciences Group 2
Disclaimer
© 2015 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 5.7 Table of Contents
© LORENZ Life Sciences Group 3
Table of Contents
Disclaimer ................................................................................................................................ 2
Table of Contents .................................................................................................................... 3
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 ..................................................................................................... 5
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.1.1 Primary Server ..................................................................................................... 9
3.1.2 Primary + Extension Server(s) ............................................................................. 9
4. Primary Server Requirements ....................................................................................... 11
4.1 Hardware Requirements ........................................................................................... 11
4.2 Software Requirements ............................................................................................. 11
5. Client Requirements ...................................................................................................... 13
5.1 Hardware Requirements ........................................................................................... 13
5.2 Software Requirements ............................................................................................. 13
6. Operating System Support ............................................................................................ 15
6.1 Application Client Operating Systems ....................................................................... 15
6.2 Application Server Operating Systems ...................................................................... 15
6.3 Use of Virtualized Environments ............................................................................... 16
6.4 Use of Terminal Emulation Environments ................................................................. 16
7. Database Support .......................................................................................................... 17
7.1 MS SQL Server ......................................................................................................... 17
7.2 ORACLE ................................................................................................................... 17
7.2.1 ORACLE Database Server................................................................................. 17
7.2.2 ORACLE Data Access Components (ODAC) ..................................................... 18
System Requirements Specification - docuBridge 5.7 Table of Contents
© LORENZ Life Sciences Group 4
8. IIS Support ...................................................................................................................... 19
9. Content Management Systems ..................................................................................... 20
9.1 Documentum ............................................................................................................. 20
9.1.1 Documentum DFS – Webtop ............................................................................. 20
9.1.2 Documentum DFC – Webtop ............................................................................. 20
9.2 SharePoint (Native) ................................................................................................... 21
9.3 Mastercontrol (Native) ............................................................................................... 21
9.4 QUMAS ..................................................................................................................... 21
9.5 FirstDocs (on Documentum) ..................................................................................... 22
9.6 nextDocs (on SharePoint) ......................................................................................... 22
9.7 LiveLink/OpenText .................................................................................................... 22
9.8 Optimal Systems ECM .............................................................................................. 22
9.9 Veeva Vault............................................................................................................... 22
9.10 M-Files ...................................................................................................................... 23
10. Other Applications...................................................................................................... 24
10.1 LORENZ eValidator .................................................................................................. 24
10.2 LORENZ docuRender ............................................................................................... 24
10.3 Adobe Acrobat .......................................................................................................... 25
11. Appendix: Support Status .......................................................................................... 26
12. Revision History ......................................................................................................... 27
System Requirements Specification - docuBridge 5.7 Getting Started
© 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 lists support
levels for various important 3rd party components.
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.
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.
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.
System Requirements Specification - docuBridge 5.7 Getting Started
© LORENZ Life Sciences Group 6
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 5.7 General System Overview
© LORENZ Life Sciences Group 7
2. General System Overview
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
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
System Requirements Specification - docuBridge 5.7 General System Overview
© LORENZ Life Sciences Group 8
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 5.7 System Design Scenarios
© LORENZ Life Sciences Group 9
3. System Design Scenarios
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 Support for assistance.
3.1.1 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.1.2 Primary + Extension Server(s)
Instead of running two docuBridge 5.7 instances on one server, you can decide that you want
to run both instances on separate servers. The database may be on one of these servers or on
an external server. As docuBridge is able execute jobs in parallel on one JobService this
scenario can be used to distribute the load on the Primary 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.
System Requirements Specification - docuBridge 5.7 System Design Scenarios
© LORENZ Life Sciences Group 10
Figure 3-2
System Requirements Specification - docuBridge 5.7 Primary Server Requirements
© LORENZ Life Sciences Group 11
4. Primary Server Requirements
4.1 Hardware Requirements
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 Dual-Core Processor Quad-Core Processor or better
RAM 4 GB 8+ 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
Network Speed 100 MBit/Sec. 1000 MBit/Sec or above
Table 4-1
As always, 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.
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. Depending on your corporate policies and the intended size of the system, you may choose from any of the Operating Systems listed in chapter 6.
IIS Internet Information Server must be installed. Please see chapter 8 for more information.
System Requirements Specification - docuBridge 5.7 Primary Server Requirements
© LORENZ Life Sciences Group 12
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: 9, 10, 11
Firefox: 27.0 – 41.0
Chrome: 34.0 – 46.0
Note:
JavaScript must be enabled on all browsers 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
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
Table 4-2
System Requirements Specification - docuBridge 5.7 Client Requirements
© LORENZ Life Sciences Group 13
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.
Component Minimum Recommended
Processor Single-Core Processor Dual-Core Processor or better
RAM 2 GB 2+ GB
Display Configuration
Single Monitor, 1280 x 1024 Pixel Single Monitor, 1920 x 1200 Pixel or dual-monitor environment.
Network Protocols
TCP/IP
Network Speed 100 MBit/Sec. 1000 MBit/Sec
Table 5-1
As always, 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 such as Windows 7 or Windows Vista.
Note: For a complete list of Operating Systems and their current status please also refer to chapter 6
.NET Framework
Version 4.5 or higher
System Requirements Specification - docuBridge 5.7 Client Requirements
© LORENZ Life Sciences Group 14
Content Viewing
Possible Tools:
Adobe Acrobat (Standard or Professional. See chapter 10.2) Image Rasterizing (Provided via Installation Package)
Requires the “Microsoft Visual C++ 2010 Redistributable Package” to be installed on the System
Adobe Reader1
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: 9, 10, 11
Firefox: 27.0 – 41.0
Chrome: 34.0 – 46.0
Note:
JavaScript must be enabled on all browsers 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
1 Please note that Adobe Reader provides only viewing functionalities for content in the Submission Workbench.
System Requirements Specification - docuBridge 5.7 Operating System Support
© LORENZ Life Sciences Group 15
6. Operating System Support
In the following tables we list the system versions that are Certified, Support and Not
Recommended.
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 8.1 Certified
Windows 7 incl. Service Packs Certified
Windows Server 2012, 2012r2 incl. Service Packs (as Terminal Server)
Certified
Windows 10 Supported
Windows Server 2008 incl. Service Packs Supported
Windows 8 Supported
Windows 7 Supported
Windows Vista SP2 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 2012 R2 Certified
Windows Server 2012 incl. Service Packs Supported
Windows Server 2008 incl. Service Packs Supported
Table 6-2
System Requirements Specification - docuBridge 5.7 Operating System Support
© LORENZ Life Sciences Group 16
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 is it 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 7 on Windows 2008-
based environments) to behave identical to a true Windows 7 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 5.7 Database Support
© LORENZ Life Sciences Group 17
7. Database Support
In the following tables we list the system versions that are Certified, Support and Not
Recommended.
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 2012 incl. Service Packs Supported
SQL Server 2008 incl. Service Packs 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 and patch levels that
development and testing uses.
LORENZ officially tests against ORACLE Database Servers hosted on Windows Systems2.
7.2.1 ORACLE Database Server
Version docuBridge
Application Server
ORACLE 12c (Patch Level: 12.1.0.1.0)
Certified
ORACLE 11g R2
(Patch Level: 11.2.0.2.0) Supported
ORACLE 11g
(Patch Level: 11.1.x.y.z) Not Recommended
ORACLE 10g R2
(Patch Level: 10.2.0.4.0) Not Recommended
Table 7-2
2 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 5.7 Database Support
© LORENZ Life Sciences Group 18
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 (Patch Level: 12.1.0.1.2)
Certified
ORACLE 11g R2
(Patch Level: 11.2.0.2.1) Supported
ORACLE 11g
(Patch Level: 11.1.x.y.z) Not Recommended
Table 7-3
Note
The Oracle Instant Client needs the “Microsoft Visual C++ 2010 Redistributable Package” to be
installed 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.
System Requirements Specification - docuBridge 5.7 IIS Support
© LORENZ Life Sciences Group 19
8. IIS Support
In the following tables we list the system versions that are Certified, Support and Not
Recommended.
Note:
All other system versions are Not Supported.
Version docuBridge Application Server
IIS 8.5 Certified
IIS 8 Supported
IIS 7 Supported
IIS 6 Not Recommended
Table 8-1
System Requirements Specification - docuBridge 5.7 Content Management Systems
© LORENZ Life Sciences Group 20
9. Content Management Systems
In the following tables we list the system versions that are Certified, Support and Not
Recommended. All other Systems are Not Supported.
9.1 Documentum
Documentum recommends using Documentum Foundation Services (DFS) instead of
Documentum Foundation Classes (DFC) that is listed as deprecated since Documentum 6.
9.1.1 Documentum DFS – Webtop
Version Support Status
Documentum 7.1 Certified
Documentum 6.7 SP2 Supported
Table 9-1
9.1.2 Documentum DFC – Webtop
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.1 Supported
Documentum 6.7 SP2 Supported
Documentum 6.6 Supported
Documentum 6.5 SP3 Supported
Documentum 6.0 Supported
Documentum 5.3 Not Recommended
Table 9-2
System Requirements Specification - docuBridge 5.7 Content Management Systems
© LORENZ Life Sciences Group 21
9.2 SharePoint (Native)
Version Support Status
SharePoint Server 2013 Certified
SharePoint Server 2010 Supported
SharePoint Server 2007 Supported
Table 9-3
9.3 Mastercontrol (Native)
Version Support Status
MasterControl 10 Supported
MasterControl 9 Supported
Table 9-4
9.4 QUMAS
Version Support Status
Sharepoint
QUMAS ComplianceSP Version 2 Supported
DocCompliance
DocCompliance v4.5 Supported
DocCompliance v4.43 Supported
Interfaces
MyQUMAS v4.4 Supported
MyQUMAS v4.24 Supported
Table 9-5
3 Compatibilty mode must be used. If a document is tried to be registered via Drag & Drop from MyQumas or Qumas DocCompliance
System Requirements Specification - docuBridge 5.7 Content Management Systems
© LORENZ Life Sciences Group 22
9.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 9-6
9.6 nextDocs (on SharePoint)
Version Support Status
nextDocs Version 5.4 Supported
Table 9-7
9.7 LiveLink/OpenText
Version Support Status
OpenText CS10 Supported
LiveLink Version 9.7.14 Supported
Table 9-8
9.8 Optimal Systems ECM
Version Support Status
OS-ECM 7.0 Supported
Table 9-9
9.9 Veeva Vault
Version Support Status
Veeva Vault 12.5.3 Supported
Table 9-9
4Integration with LiveLink requires LiveLink Enterprise Web Services to be installed and configured.
System Requirements Specification - docuBridge 5.7 Content Management Systems
© LORENZ Life Sciences Group 23
9.10 M-Files
Version Support Status
M-Files 2015 Supported
Table 9-10
System Requirements Specification - docuBridge 5.7 Other Applications
© LORENZ Life Sciences Group 24
10. Other Applications
In the following tables we list the system versions that are Certified, Support and Not
Recommended.
Note:
All other system versions are Not Supported.
10.1 LORENZ eValidator
Version docuBridge
Application Server
eValidator 5.6 Certified
eValidator 5.5 Supported
eValidator 5 (other versions) Not Recommended
Table 10-1
10.2 LORENZ docuRender
If you are using the new Version of Adlib (Adlib PDF 5.x), no docuRender service for the
connection between docuBridge and Adlib is used.
Note:
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.
System Requirements Specification for the Adlib Express can be obtained via
http://www.adlibsoftware.com/.
In the following tables only Systems are listed that are Certified, Support and Not
Recommended. All other Systems are Not Supported.
Adlib Version
Version Support Status
Adlib PDF OEM 5.3.1 Certified
Adlib PDF OEM 5.2 Supported
Adlib PDF OEM 5.1.1 Supported
Adlib Express 4.10.6 Not Recommended
Table 10-2
System Requirements Specification - docuBridge 5.7 Other Applications
© LORENZ Life Sciences Group 25
10.3 Adobe Acrobat
Version docuBridge
Application Client
Adobe Acrobat DC5 Certified
Adobe Acrobat 9 Certified
Adobe Acrobat XI Supported
Adobe Acrobat X Supported
Adobe Acrobat 8 Not Recommended
Table 10-3
5 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 5.7 Appendix: Support Status
© LORENZ Life Sciences Group 26
11. 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 11-1
System Requirements Specification - docuBridge 5.7 Revision History
© LORENZ Life Sciences Group 27
12. Revision History
Revision Date Modifier Description
1.0 2015-10-08 M. Stein docuBridge 5.7
Table 12-1: Revision History
LORENZ Archiv-Systeme GmbH Eschborner Landstrasse 75 60489 Frankfurt/Main GERMANY Tel +49-69-78991-901 Fax +49-69-78991-129
LORENZ Life Sciences Ltd. No. 1 Farnham Road Guildford, Surrey GU2 4RG UNITED KINGDOM Tel +44-1483 903 861 Fax +44-207 6812676
LORENZ Polska APC Instytut Sp. z o.o. ul Grójecka 22/24/4 Warsaw 02-301 POLAND Tel +48-22-668 68 23 Fax +48-22-668 99 81
LORENZ International LLC 1515 Market Street Suite 1200 Philadelphia, PA 19102 USA Tel +1 866 956 7369 +1 866 9LORENZ Fax +1 866 295 6967
LORENZ Newbook Inc. 7045 Edwards Boulevard Mississauga, ON L5S 1X2 CANADA Tel +1 866 956 7369 +1 866 9LORENZ Fax +1 905 248 3971
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 4299 4219 Fax +91-44 4299 4310
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 559
© LORENZ Life Sciences Group docuBridge® and labelBridge® are registered trademarks of LORENZ Archiv-Systeme GmbH in the United States and other countries. Microsoft® and Microsoft Word® are U.S. registered trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be trademarks of their respective owners.
Top Related