Brava for Filenet FAQ:

yompmulligrubsInternet και Εφαρμογές Web

31 Οκτ 2013 (πριν από 4 χρόνια και 12 μέρες)

129 εμφανίσεις

Brava for Filenet FAQ:

1.

After the installation right clicking on a file to view in Workplace/XT does not show a Brava
!

option

a.

Check to make sure the actions.xml was updated during the install. For WorkplaceXT
check both the actions.xml and menuactions.xml.
If not rerun the install or update
manually following the instructions in the install guide.

b.

Make sure the that the appropriate integration installation was selected during the
installation, either Workplace or Workplac
e
XT

2.

After clicking Brava>Annotate, y
ou receive an error “unable to communicate to
Brava

server
servername:port number.

a.

This may be due to a number of reasons

i.

The license is not valid. Navigate to the license server folder in the
Brava

installed folder, and see if a file called errors.txt exi
sts, if so, open the file and
check the error. If license is not valid, contact Informative Graphics for support.

ii.

Brava Server is not running. The Brava server has to be turned on and running.
Depending on your deployment the Brava Server may be running in

Tomcat or
Websphere. Make sure the application server is turned on and that the Brava
Server application is deployed and running.

iii.

Brava server is unreachable. Check to make sure that proper network
communication exists between the
Brava

server and the Wor
kplace or
Workplace XT server. The port used must be open and communication must
exist between both servers.

3.

Which
components

are required on the Workplace or WorkplaceXT servers

a.

Although all the Brava components could be installed on the server, provided
minimum
requirements are met, only the integration component is required to be installed on the
Workplace or WorkplaceXT servers

4.

Which property files need to be updated if server name changes

a.

All default Brava Enterprise property files need to be updated.

i.

Job processor.config

ii.

Server.properties

iii.

Client_precedence.properties

b.

Filenet integration specific

i.

Brava.properties






The depiction below is a logical diagram, not an actual physical system diagram. See item #3 for a
discussion of each component.






1)

Can Brava for IBM Fi l eNet P8 be depl oyed i n a Vi rtual Machi ne Envi ronment?

a.

Yes

2)

What are the basi c hardware requi rements for Brava

for IBM Fi l eNet P8
?

a.

Brava! Enterpri se hardware requi rements are hi ghl y dependent on the user l oad, number of

uni que fi l e vi ews, types of fi l es, and other confi gurati on

/ use detai l
s. In general i f al l Brava!
Components are to be i nstal led on a si ngl e
physi cal or vi rtual
machine the recommended
requi rements woul d be as fol l ows:


i.

Quad core Intel or AMD processor.

ii.

4 GB RAM

iii.

15GB

(mi n)
+ HDD space

for cached pages (anythi ng from 15GB to 1TB)

3)

What environment is required?

a.


The FileNet environment can be running on any platform supported by FileNet

b.


Brava is scalable, and made up of five components (as i
ndicated in the drawing above).



Client, Brava Server, Job Processor, Integration Component and License Server.



i.


The Brava! Server


This is a java servlet that needs to be deployed on
a
servlet engine. It is certified to be deployed on tomcat 5.5 and 6.0 and
Websphere 6.1 in a windows environment.



ii.


Job Processor


This component runs as a windows service and requires
windows 2003 or 2008 (32 or 64 bit).



iii.


License server
-

This component runs as a windows service and requires
windows 2003 or 2008(32 or 64 bit), usually installed on the same machine as
the Job Processor.



iv.


Client control


This can be hosted on any web server that users have access
to, it is a combination of files (ActiveX control or Flash) that users download
automatical
ly upon first viewing a file.



v.


Integration component


This piece must be installed on the workplace or
WorkplaceXT servers, it consists of additional files that are placed onto the
deploy
ed workplace or WorkplaceXT machines. It has been certified to run in
Websphere 6.1 on windows, Weblogic 10.3 on windows, Weblogic MP2 on
Linux Redhat 5.4, and supported in Websphere 7.0 in AIX 6.1.

c.


All components can be installed on the same mac
hine or separated out, the Brava!
Server install comes prepackaged with Tomcat, a different app server can be used if
necessary. The Client is an Active/X control that can be used in Internet Explorer
(preferred) or Mozilla Firefox (with Active/X plug
-
in).

An Adobe FLASH client is also
available, but the Flash client can only VIEW annotations, not CREATE annotations.

d.


The Job Processor MUST run on a windows platform.


This platform requirement is
dependent on the volume of users, number of transacti
ons, and file types being viewed.


An instance of MS Office is typically also installed on the Job Processor so that print
publishing can be deployed for crystal
-
clear viewing of MS office file types.


The
guideline for this base system is dual or quad co
re processor, 4GB RAM, 20 GB disk
space (disk space is dependent on displaylistcache size, the higher the setting more disk
space would be needed)

e.


Brava Server is the “traffic cop” for transactions.



f.


The Web Application Servers supported

include Websphere, WebLogic, and Tomcat
.
Informative Graphics has certified Linux and Windows, and it is working on AIX, but AIX
has not been added to our support list yet.

2)


Are there any pre
-
requisites?

a.


The FileNet environment (version 4
.0 or 4.5) should be fully installed and working
before Brava is installed.


Version 4.5 is required for our Workplace/XT integration.

b.


Workplace or Workplace/XT must be deployed if you plan to use our out
-
of
-
the
-
box
integration.

c.


Customer m
ust have either Websphere (6.1), Tomcat (5.5, 6.0), WebLogic (10.3)
Application Servers deployed and working.

d.


Installation of the Brava Job Processor requires local console
-
level login (no Windows
Remote Desktop) to the windows server where the sof
tware will be installed.


Of course
Admin
-
level permissions are required during installation. If remote access to the
windows system is required, RealVNC is supported for remote login at installation time.

3)


How can we integrate Brava with P8?


Is j
ust wizard to install?


Are there any required
connectors?

a.


Our software is distributed in an install package that does nearly all of the integration
with a simple installation.


The demo I prepared for you had no custom integration
required.


Ther
e are some minor steps documented in the instructions.

The install
manual is attached.


Install package and trial software can be retrieved from:
ftp://ftp2.infograph.com/DL/BravaEnte
rpriseForFileNet.exe


b.


Brava is designed as a toolkit that can be expanded beyond our existing integration to
FileNet.


Our integration can be viewed as a “template” onto which integrators and
developers can more deeply embed Brava viewer functiona
lity into FileNet applications.


Our SDK is located at this FTP site:
ftp://ftp.infograph.com/brava/BEX6_2_SDK.zip
.


4)

How is Brava for
IBM FileNet P8 Licensed?

a.

Licensing is per user. Brava is priced per
-
seat, and features an 8
-
hour refresh. Any time
a user at the client opens their first Brava Session, that license is dedicated to that IP
address (user workstation) for 8 hours. After 8

hours, the license becomes available for
other users. We have a declining cost per
-
seat as volume increases.
Our pricing is
established based on two categories:

i.

File formats

1.

CAD

(includes Document)

2.

Document

(excludes CAD), but includes image and office f
ormats

ii.

Per
-
User Capability Sets (3 levels)

1.

view/print

2.

view/print/annotate

3.

view/print/annotate/redact

5)

How do I get configuration assistance or a quote for Brava for IBM FileNet P8?

a.

Brava for IBM FileNet P8 is sold by IBM Global Business Services (GBS) and a

select
group of Informative Graphics / IBM Business Partners. For direct pricing, please
contact Informative Graphics
jrod@infograph.com
.



General Brava Cache function overview (non
-
cached file view, unique view)
:


1.

The integration sends authentication data to the Brava
server and submits the publish request

2.

Brava server retrieves properties of the file (time, date
last modified, GUID, etc…) checks the cache if the file
has already been published, if not then the f
ile is
retrieved from FileNet Content Engine and writes
source file to cache, it creates a folder for the file and
places the file there.

3.

Job processor picks up the source file from cache and
converts the file. It launches 2 threads, 1 for publishing
the f
irst page and another for publishing the entire files

4.

When first page publish completes, the JP (job
processor) creates a folder in the cache and places the
first page there.

5.

The Brava Server sends the first page to the client from
the cache.

6.

When full doc
ument publishing completes, the source
file is deleted and the same folder is used for the fully
converted file.

7.

At the 2 minute mark after the first page was published
it is deleted from the cache.

8.

At the time that the full file is converted and placed in

the cache, an event is fired to truncate the cache to the
stated maximum size. After each file published, a
maximum of 10 previously cached files will be removed
based on age of the files. This is done to match the
preset maximum size of the cache.

9.

Brava
server sends the converted file to the client
machine



General Brava Cache function overview (cached file view):


1. The integration sends authentication data to the Brava
server and submits the publish request

2. Brava server retrieves properties of the
file (time, date
last modified, GUID, etc…) checks the cache if the file has
already been published, if it is, it picks up the cached files
and sends it to the client.