OpenText™ Brava!

™ for Content Suite

Architecture Overview

This guide presents information on the architecture of the

Brava! Enterprise Server, Brava! Job Processor, Brava!
License Server, the Web Server, and OpenText Content
Servers to help you determine how to set up the various
product components to interact properly in your specific
environment.
OpenText™ Brava! for Content Suite
Architecture Overview
Rev.: May 23, 2018
This documentation has been created for Brava! software version 16.4.
It is also valid for subsequent software versions as long as no new document version is shipped with the product or is published
at https://knowledge.opentext.com.

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: https://support.opentext.com
For more information, visit https://www.opentext.com

Copyright © 2018 Open Text. All Rights Reserved.

Trademarks owned by Open Text.

Disclaimer

No Warranties and Limitation of Liability

Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.
Table of Contents
Slide 1 .......................................................................................................................................................... 4
Slide 2 .......................................................................................................................................................... 6
Slide 3 .......................................................................................................................................................... 7
Slide 4 .......................................................................................................................................................... 8
Slide 5 .......................................................................................................................................................... 9
Slide 6 ........................................................................................................................................................ 10
Slide 7 ........................................................................................................................................................ 11
Slide 8 ........................................................................................................................................................ 12
Slide 9 ........................................................................................................................................................ 13

Last updated: Wednesday, May 23, 2018

Slide 1

Single OpenText Content Server w/ Brava Components

and Brava Job Processor Server

OT Content Server Brava Job Processor

Brava Module
Tomcat
Brava Web App
Brava License Server

© 2008 Informative Graphics Corporation

No changes need to be made to the “Configure Brava! Servers” Admin page. Default
settings will be sufficient.

NOTE: The Brava! Webapp and Tomcat do not need to reside on the same server as the
OpenText Content Server. If you choose to move the Brava! Server off the OpenText
Content Server, then you will need to define the Brava! Server URL in the “Configure Brava!
Servers” Admin page. This is discussed in the Brava! Module Admin Guide.

Here are some benefits of having Brava! Server reside on the same machine as the
OpenText Content Server:

Benefit #1: The Brava! Job Processor can be an extremely power-hungry piece of code. If
the Brava! Job Processor goes up to 100%, then it’s going to be stealing cycles that should
probably be serving cached content, properties, licenses, etc. to clients. If you put Brava!
Server on the same box as the Brava! Job Processor, you run a risk of making Brava! usage
a miserable experience during heavy periods of document conversion. If the company has
one extra server and wants to put Brava! on it, we would recommend using it for the Brava!
Job Processor and putting the Brava! Server on the Content server. If two extra machines
are available, then it will work to put Brava! Server on one of them and the Brava! Job
Processor on another.

Last updated: Wednesday, May 23, 2018 4

Benefit #2 : In load-balanced configurations, where you have a different Brava! Server for
each Content server in the OpenText cluster, and the Brava! Servers are not load-balanced
themselves, putting the Brava! Server on the same machine as the Content server it’s
attached to effectively load-balances the Brava! Server and the OpenText Content server as
a single unit within the cluster—if either the Content server or the Brava! Server on the
node fails, the entire node will fail, improving the failover abilities of the load balancer.

There are also some good reasons to put Brava! Server on a different machine:

• Policy. If you just can’t put Brava! Server on the same machine as OpenText, then of
course you can put it on a different server. No problem. But you should also have a 3rd
server to serve as the main Brava! Job Processor.
• Load-balanced Brava! Servers. If you want to set up a cluster of Brava! Servers, then
you must put them on their own boxes.

Last updated: Wednesday, May 23, 2018 5

Slide 2

Multiple Clustered Content Servers and

Single Brava Server

Cluster (Active / Passive)

Brava Server
Content Server - 1
Tomcat
Brava Module Brava Web App
Brava License Server

Content Server - 2
Brava Job Processor
Brava Module

© 2008 Informative Graphics Corporation

Please refer to the Brava! for OpenText Module admin guide for directions with defining the
Brava! Server URL location.

Both OpenText Content servers will have the same Brava! Server URL defined.

Last updated: Wednesday, May 23, 2018 6

Slide 3

Multiple Clustered-Load Balanced Content Servers, Multiple Clustered Brava Servers,

Brava Job Processors, (for load balancing hot fault tolerance)

Cluster (Active / Passive) Cluster (Active / Passive)

Content Server - 1 Brava Server - 1

Brava Job
Brava Module Tomcat Processor

Brava Web App

Front-end Brava License Server
load
Load
balancer
balancer
with sticky
with
or
sticky or
persistent
persistent
sessions
sessions
enabled
enabled

Content Server - 2 Brava Server - 2

Brava Module
Tomcat Brava Job
Processor
Brava Web App
Brava License Server

© 2008 Informative Graphics Corporation

You need to make sure the Load Balancer has “sticky sessions” enabled.

With regards to licensing the Brava! License Server, if there is a cluster of Brava! servers,
the license needs to be tied to the Brava! machine name, not the Brava! cluster name.

IMPORTANT: When configuring a multiple Brava! Server setup for a high availability
configuration, a shared cache environment is required for user synchronization. Please refer
to the Brava! Enterprise core installation guide for detailed information on setting up shared
cache.

Last updated: Wednesday, May 23, 2018 7

Slide 4

Multiple Content Server Instances, Single Brava Server components, Brava Job Processors,
(for load balancing and maximize CPU usage – Vertical Scalability)

Content Server
Instance- 1
Brava Module

Front-end Brava Server

load
balancer
with sticky Tomcat
or Brava Job
persistent Brava Web App Processor
sessions
enabled Brava License Server
Content Server
Instance- 2
Brava Module

© 2008 Informative Graphics Corporation

Both “Configure Brava! Server” Admin pages for each OpenText Content Server instance will
need to define a specific machine for the Brava! Server location. This will be done by
checking the radio button for “Brava! Server is installed at this URL” and then defining the
URL needed to hit the Brava! Server web application.

Make sure the clients can ping the Brava! Server. If they cannot ping by machine name
then they must be able to ping by IP. Whatever works needs to be the value set in the
above-mentioned variable. Also, please make sure the appropriate machine name or IP is
defined in the client_precedence.properties file.

Last updated: Wednesday, May 23, 2018 8

Slide 5

Remote cache configuration with single

Brava Server at primary site

Primary Content Brava Server

Brava Job
Server Instance - Processor
Tomcat
1
Brava Module Brava Web App
Brava License Server

Remote Content
Server Instance-
2

© 2008 Informative Graphics Corporation

Please refer to the Brava! for OpenText Module Admin Guide for detailed information on
setting up Remote Brava! Servers.
In this scenario, only a single Remote Brava! Server is being implemented and thus only a
single Remote Brava! Server will be defined in the “Configure Brava! Server” Admin page
under Remote Brava! Servers heading.

NOTE: Each Remote OpenText Content Server Instance does not need to have a Brava!
Server attached to it. They can, however, for performance reasons (slow connection, etc).

Last updated: Wednesday, May 23, 2018 9

Slide 6

Remote cache configuration with

remote Brava Server(s)

Primary Brava Server

Primary Content
Server Tomcat Brava Job
Brava Module Processor
Brava Web App
Brava License Server

Remote Brava Server

Remote Tomcat Brava Job
Cache -1 Processor
Brava Web App
Brava License Server

Remote
Cache - 2

© 2008 Informative Graphics Corporation

Please refer to the for Brava! for OpenText Module Admin Guide for detailed information on
setting up Remote Brava! Servers.
In this scenario, only a single Remote Brava! Server is being implemented and thus only a
single Remote Brava! Server will be defined in the “Configure Brava! Server” Admin page
under Remote Brava! Servers heading.

Then anyone using the Primary server for OpenText Content Server access also gets to use
the primary Brava! Server. Anyone who connects to RC1 gets to use the remote Brava!
Server. Anyone who connects to RC2 gets to use the Primary Brava! Server.

NOTE: Each Remote OpenText Content Server Instance does not need to have a Brava!
Server attached to it. They can, however, for performance reasons (slow connection, etc).

Last updated: Wednesday, May 23, 2018 10

Slide 7

Multiple Content Servers w/Brava Server components, Brava Job Processors,

(for load balancing hot fault tolerance and maximize availability and
throughput – Horizontal Scalability)

ContentServer - 1

Brava Module
Brava Job
Brava Server Processor
Brava Web App
Tomcat
Front-end
load balancer Brava License Server
with sticky
or persistent
sessions
enabled Content Server - 2

Brava Module
Brava Server
Brava Job
Tomcat
Processor
Brava Web App
Brava License Server

© 2008 Informative Graphics Corporation

No changes need to be made to the “Configure Brava! Servers” Admin page. Default
settings will be sufficient.

Explanation: The Brava! Server is tightly tied to a single Content Server. The Brava!
Server that the Content Server connects to when users connect to OpenText will be the
same Brava! Server that users connect to as a client. The thing that enables this is sticky
sessions on the load balancer.

Last updated: Wednesday, May 23, 2018 11

Slide 8

Livelink SEA with single Content Server

and Brava Components

ContentServer - 1

DMZ
Brava Module
Content Server
Servlet Brava Server
Brava
Support Files Tomcat Brava Job
Processor
Brava Web App

Brava License Server

© 2008 Informative Graphics Corporation

Please refer to the installguide for detailed information on configuring Brava! Server
Mappings for a SEA servlet configuration.

Last updated: Wednesday, May 23, 2018 12

Slide 9

Livelink SEA with two load-balanced Content Servers

and separate Brava Components

DMZ
Content Server Content Server - 1
Servlet Brava Job
Brava Brava Module Processor
Support Files Brava Server
Tomcat
Brava Web App
Front-end
load balancer
Brava License Server
with sticky or
persistent
sessions
enabled Content Server - 2
Brava Job
Brava Module Processor

Brava Server
Tomcat
Brava Web App
Brava License Server

© 2008 Informative Graphics Corporation

Please refer to the installguide for detailed information on configuring Brava! Server
Mappings for a SEA servlet configuration regarding internal and/or external connections to
the Brava! Server.

Last updated: Wednesday, May 23, 2018 13