Professional Documents
Culture Documents
Table of Contents
For TaskSpace 6.7 SP2 Integration .................................................................................. 1
Table of Contents .............................................................................................................. 2
1.0 Preparing to Install Brava for TaskSpace ................................................................... 3
1.1 Supported configurations and Hardware Requirements: ................................................... 3
1.1.1 End-User Machine that Runs the Client Control ......................................................... 3
1.1.2 Application Server Environments for Brava! Enterprise for TaskSpace .......................... 3
1.1.3 Brava! Enterprise Job Processor and Brava! Enterprise Licensing Services .................... 4
1.1.4 Brava TaskSpace Client System Requirements .......................................................... 4
1.2 Hardware Requirements ............................................................................................... 5
1.2.1 Brava Server ........................................................................................................ 5
1.2.2 See Requirements of Application Server ................................................................... 5
1.3 Documentum TaskSpace Setup Requirements ................................................................. 5
1.4 New Integration Features ............................................................................................. 5
2.0 Installing Brava! Enterprise for TaskSpace................................................................. 7
3.0 Configuring your Installation ................................................................................... 18
3.1 Editing the ivf_config.xml File ..................................................................................... 19
3.1.1 Enabling Server Side Publishing ............................................................................ 19
3.1.2 Loading Paths ..................................................................................................... 20
3.1.3 Brava TaskSpace Parameters Used in the ivf_config.xml file ..................................... 23
3.2 Tips and Troubleshooting ........................................................................................... 29
3.2.1 Uninstalling Brava TaskSpace Components ............................................................. 29
3.2.2 Tips: .................................................................................................................. 29
3.2.3 Troubleshooting: ................................................................................................. 30
4.0 Contacting Informative Graphics .............................................................................. 31
1.1.3 Brava! Enterprise Job Processor and Brava! Enterprise Licensing Services
Windows XP Professional SP3 (32\64 bit)
Windows 2003 Server SP2 (32\64 bit)
Windows Server 2008 (32\64 bit)
Windows Server 2008 R2 (64 bit)
Windows Server 2008 R2 SP1 (64 bit)
.NET Framework: 4.0
Office version: Microsoft Office 2010 (32 and 64 bit), Microsoft Office 2007 SP2, or
Microsoft Office 2003 with 2007 compatibility pack*
*Although Office 2003 is supported, some JobProcessor features, such as XPS publishing
(SaveAsXPS), are not available with this version.
*If using Microsoft Office 2007 or 2007 SP1, you should have SaveAsXPS installed on your
system prior to installing the Brava Enterprise Job Processor. To do this, you can download
the Microsoft Save As XPS add-in from:
http://www.microsoft.com/downloads/en/details.aspx?familyid=BCE8F991-F0A4-47A0866B-2FD84A329E02&displaylang=en or update your Office version to 2007 SP2 or Office
2010.
*When installing to a Japanese environment only, please follow the instructions provided
through this link for switching Office IME 2007 and Legacy MS IME:
http://support.microsoft.com/kb/932104/ja
Support of the Brava! Job Processor for server side conversion of files
Support %dbstring
Printing based on User or Group
Stamp Template based on User or Group
If you have purchased more than one IGC product or integration, installing these various
products on the same server (or using one instance with multiple products or integrations)
is not supported.
Multiple product integration components cannot be installed on the same Brava Server or
Job Processor: Although various integrations use the same Brava components (Brava
Enterprise Server, Brava Enterprise Job Processor, and Brava Enterprise License Server),
the actual versions of these Brava Components are not identical and therefore must be
installed on separate servers and cannot be shared between the two.
This restriction also applies to the Brava ActiveX control that is used with various
integrations. The integrations include different versions of the Brava ActiveX control and
therefore both cannot be installed at the same time on a single client machine.
1. Run the Installation by clicking on the web package file that you downloaded. A Demo
Shield installation browser launches automatically. Select the Install Brava! for
TaskSpace button to begin the installation.
3. On the License Agreement screen, click I accept.. If you have read and agree to the
terms contained in the product license. Click Next.
4. Select which Brava Enterprise components you would like to install on this machine. You
can install the components on the same or different machines. Click Next.
6. At this point, Brava will check to see that IGC writer is installed, and is the correct version.
If not detected, the IGC Writer installation begins or updates to the correct version. The
Brava Enterprise installation should now detect the correct version of the IGC Writer printer
driver and continue with the installation.
(Skip to step #7 if IGC Writer is already installed)
a. IGC Writer Installation: If the setup did not detect the correct version, the IGC Writer
installation begins to install the IGC Writer printer driver. If you already have the correct
version installed, skip this section. On the Welcome screen, click Next>, then click Yes
on the license agreement screen after you have read and agreed to the terms of use.
10
b. In the Choose Destination Location screen, set the desired destination folder or accept
the default location. (IGC strongly recommends accepting all the defaults.) Click Next.
11
d. When installation has completed, click Finish at the InstallShield Wizard Complete
screen. The Brava Enterprise installation continues.
Note: It is recommended that the IGC Writer be installed under the same user
account as the Job Processor. If you are running the Job Processor under a different
account, you may have to manually set the CSF Writer properties for print-publishing
to work correctly, but this setup is not recommended, nor has it been certified.
12
7. If detected, the Brava installer will display the Tomcat version currently installed and
make it available for selection, or you may select Use different or undetected servlet
engine. Select the setup type of install and click Next.
Notes:
If you have elected NOT to use Tomcat (e.g. WebLogic or Websphere), you are
prompted to select a directory to deploy the Brava Server WAR file from. Its best to
select a common default location for your application server. With an application
server such as BEA WebLogic, it is recommended that WAR or EAR files be placed in
a common, accessible place such as the C:\bea\user_Projects\Domains directory to
ensure that the files (WAR and EAR) are located in a common default location for
deployment.
If Tomcat is installed on the installation machine, but is undetected by the
installation (due to the existence of a Tomcat service), choose Use different or
undetected servlet engine. Do not install Tomcat on top of the currently installed
Tomcat instance.
8. The Edit Data screen displays the URL that will be used for communication by the
Brava Client. The URL is broken down into its parts: The default servlet port to use for
Tomcat is 8080. If your application server is not Tomcat, or if you have configured
Tomcat to use a non-default port, enter the application servers communication port
number. Click Next.
URL Prefix: Enter either HTTP:// or HTTPS:// depending on whether the servers are
configured to communicate using SSL and https.
Hostname: Enter the fully qualified domain name of the server that is used for
communicating with the Brava Server.
Port: Enter the port number that your application server is using (where Brava Server
is running/deployed to).
Examples:
Tomcat (Default): 8080
WebLogic (Default) 7001
Websphere (Default) 9080
13
Note: If you selected Use different or undetected servlet engine in the previous step,
the following screen will appear during the install so you can input the Destination
Folder.
9. Browse to the location in the deployed TaskSpace from where the Brava Client files are
to be hosted and click Next. The default location will be
C:\<myservletengine>\webapps\taskspace\wdk\imageviewer\
14
10. Select an installation location for the Brava Server files and click Next.
15
12. Choose YES to install the Brava Enterprise Job Processor and License Server as
a service. Note that choosing No will require you to run the License Server and Job
Processor as console applications inside a login session, which is available on the Start
menu (StartAll ProgramsIGCBrava! License ServerStart Brava! License
Server and StartAll ProgramsIGCBrava! Job ProcessorStart Brava! Job
Processor)
13. Youll be prompted to enter the service username and password information for the
Brava Enterprise License Server and Job Processor Services. Click Next.
16
14. You will be prompted whether to start the Brava Enterprise License Server and Job
Processor services.
15. The installation is complete. You may be prompted to reboot your system at this time.
17
C:\Oracle\Middleware\user_projects\domains\base_domain\autodeploy\taskspace\custom
C:\Program Files (x86)\IGC\Brava!\Taskspace\Custom67sp2\strings
TO
C:\Oracle\Middleware\user_projects\domains\base_domain\autodeploy\taskspace\taskspa
ce\strings
C:\Program Files (x86)\IGC\Brava!\Taskspace\Custom67sp2\wdk
TO
C:\Oracle\Middleware\user_projects\domains\base_domain\autodeploy\taskspace\wdk
C:\Program Files (x86)\IGC\Brava!\Taskspace\Custom67sp2\WEB-INF
TO
C:\Oracle\Middleware\user_projects\domains\base_domain\autodeploy\taskspace\WEB-INF
3. In order to publish to CSF format, ensure that the dar (igc_csf_format_67sp2.dar) file is
installed on the content server. The dar file is located in the Brava!\Taskspace\dar
directory.
4. To use Brava in TaskSpace, you must deploy TaskSpace with Document Image Services.
18
To enable this mode alter the following parameters in the ivf_config.xml file:
#EnableConvertOnClientOfficeFormats requires additional purchase
EnableConvertOnClientOfficeFormats=FALSE
EnableConvertOnClientCADFormats=TRUE
EnableConvertOnClientImageFormats=TRUE
ClientLoadedMaxFileSize=2048
ConvertOnClientOFFICEFormats=pptx,docx,xlsx,cdr,dbf,doc,drw,fax,flw,fmt,fwk,htm,h
tml,img,mpp,msg,pcd,pct,pic,pict,pps,ppt,prs,prz,rnd,rtf,sam,shw,vsd,vw,wb1,wb2,w
db,wk1,wk3,wp,wp5,wp6,wpd,wpf,wpg,wq1,wri,ws,xbm,xls
ConvertOnClientCADFormats=906,slddrw,cgm,prt,cit,dwf,dgn,igs,dwg,dxf
ConvertOnClientImageFormats=txt,tif,tiff,pdf,bmp,png,gif,jpg,csf
19
Optional Steps: The following table lists the parameters (and possible values) contained in the
ivf_config.xml page that you can customize to meet your requirements. Many of these
parameters determine which features will be available to viewers using the Brava ActiveX Client.
You can choose to enable or disable a feature by setting its value to true or false.
See the Optional Brava ActiveX Parameters in the BravaForTaskSpace_BravaXParamsGuide.pdf
for a detailed list of all possible Brava Enterprise parameters. Note that many of the Brava
ActiveX Parameters that are specified in the ivf_config.xml file, are only used when the file is
viewed in Brava when selecting the TaskSpace "View" command. When a file is viewed in Brava
using the TaskSpace Preview feature, the parameters are pre-set and cannot be changed.
The format of the file is checked and compared against the 'ConvertOnClientXXXFormats'
parameter. If the format is found as a value of one of those parameters, the parameter
'EnableConvertOnclientXXXXFormats' is checked to see if Brava should load and render the file on
the client:
1. If the format is found and the 'EnableConvertOnClientXXXFormats' is set to TRUE, Brava
checks the file size to determine if it is larger or smaller than the value set for
ClientLoadedMaxFileSize:
a. If the file is smaller, Brava loads the file on the Client and renders it.
b. If the File is larger, Brava then checks to see if page serving is enabled on the
Content Server:
i. If page serving is enabled Brava loads and renders the file on the client.
ii. If page serving is disabled, Brava server/publisher renders the file:
1) If the Content Server is able to provide Brava with an ACS URL (with
no page serving), then Brava sends that ACS URL to the Brava Server.
Brava Server will then use that ACS URL to retrieve the file and publish
it.
20
2) If the content server is NOT able to provide Brava with an ACS URL,
the Brava component on the webapp server will HTTP POST the file to
Brava Server for publishing.
3) After 1) or 2) above, the file is send back to the Brava client in Brava's
native form for viewing.
2. If the format is not found or the 'EnableConvertOnclientxxxFormats' parameter is set to
FALSE for this format, server side publishing is enabled (see 3.1.1).
a. If the content server is able to provide Brava with an ACS URL (with no page
serving) then Brava sends that ACS URL to the Brava Server. Brava Server will then
use that ACS URL to retrieve the file and publish it.
b. If the content server is NOT able to provide Brava with an ACS URL, the Brava
component on the webapp server will HTTP POST the file to Brava server for
publishing.
c. After a. or b. above, the file is send back to the Brava client in Brava's native form
for viewing
ACS/BOCS
Load Path*
Yes
Yes
No
Yes
Yes
No
Yes
No
n/a
Yes
No
n/a
No
No
No
Yes
Yes
Yes
A
B
A
C
D
C
If image page serving is on, Brava will always try to client side load the file.
21
22
Description
This parameter should always be
IntegrationDllName=TaskSpaceIntegration
IntegrationUrl
IntegrationVersion
TaskSpaceMultiSourceCheck
23
Value
Valid string values are as follows:
All or 0 designates all levels of
messages are logged.
Debug or 1 designates finegrained informational events that
are most useful to debug an
application.
Description
This is the Level of Logging that can be done
by the Brava TaskSpace Client.
With a logging level set to Error only, Error and
Fatal Messages are logged.
%USERPROFILE%\\IGC\\x7_1\C
lientlog.txt Default
ConvertOnClient
TRUE - Default
FALSE
EnableThumbnails
TRUE Default
FALSE
TRUE
FALSE Default
SecurityOptionsFro
mServer
24
TaskSpaceSuppress
Messages
EnableChangeMark
Panel
TRUE Default
FALSE
EnableBookmarkPa
nel
TRUE Default
FALSE
EnableRedactVerify
Panel
TRUE Default
FALSE
EnableTakeoffPanel
TRUE
FALSE Default
EnableDisplayPanel
Bar
TRUE Default
FALSE
PanelToDisplay
1 (no panel)
EnableCopyText
TRUE Default
FALSE
EnableThumbnailsR
esize
TRUE Default
FALSE
25
TRUE Default
FALSE
EnableTIFFPublish
TRUE Default
FALSE
UserSettingsPath
Default value is
PersistUserSettings
Default value is
%USERPROFILE%\IGC\x7_1\
%USERPROFILE%\IGC\x7_1\
Default value is
%USERPROFILE%
\IGC\x7_1\Stamp
Images
Sets the default path for the Markup Raster tool. The
path must be set using double back slashes to work
properly. It is recommended that you use a path
relative to and within the users profile. The path
starting point of %USERPROFILE%\\ should help to
26
EnableMarkupClose
EnableMarkupBurnin
RedactionScriptsDirectory
UIEditRedlineText
TRUE Default
FALSE
TRUE Default
FALSE
Default value is
%USERPROFILE%
\IGC\x7_1\Redac
tionScripts
TRUE
FALSE
The following parameters control markup permissions and default markup permissions for users
with READ access.
EnableMarkupNew
EnableMarkupReview
EnableMarkupOpen
EnableCopyMarkupTo
AllPages
TRUE
FALSE
TRUE
FALSE
TRUE
FALSE
TRUE
FALSE
Default
Default
Default
Default
The following parameters control printing and stamp template permissions for users.
Printing_Control_For_Gro
ups
Printing_Control_For_Use
rs
TRUE
FALSE Default
TRUE
FALSE Default
27
Disable_These_Groups_Fo
r_Printing
Diable_These_Users_For_
Printing
Allow_These_Groups_To_
Control_Stamp_Templates
Allow_These_Users_To_C
ontrol_Stamp_Templates
EnableNewMarkupStampT
emplate
EnableOpenMarkupStamp
Template
EnableSaveMarkupStampT
emplate
EnableSaveAsMarkupStam
pTemplate
EnableCloseMarkupStamp
Template
Coma separated
list of valid
TaskSpace
Groups
Coma separated
list of valid
TaskSpace Users
Coma separated
list of valid
TaskSpace
Groups
Coma separated
list of valid
TaskSpace Users
TRUE
FALSE Default
Allow_These_Groups_To_Control_Stamp_Temp
lates=
Allow_These_Users_To_Control_Stamp_Templ
ates=
* The following parameters are set by the integration and should not be altered. Changing them
has no effect on how markups behave.
EnableMarkup=
EnableMarkupSave=
PreloadReadOnlyMarkupNames=
WarnOnUnsavedMrkClose=
EnableSaveAsDXF=
EnableMarkupSaveAs=
EnableMarkupNew=
GetMarkup=
MarkupList=
CreateMarkup=
UpdateMarkup=
UserName=
PreloadMarkupName=
28
3.2.2 Tips:
Ensure that the ivf_config.XML is configured properly
Ensure that the servlet engine that hosts the Brava Server war (BravaServer.war) is restarted
when changes are made to the server.properties file. Changes to the
server_precedence.properties or client_precedence.properties do not require this restart.
For Brava 7.1 for TaskSpace, the Client MSI packages can be found in the root of the Brava!
folder: C:\Progam Files (x86)\IGC\Brava!\Client MSI The default location for the
extraction is %userprofile%\IGC\x7_1
Where are the markups stored for Brava for TaskSpace? Markups created within Brava for
TaskSpace are stored within the annotations folder in the root folder defined for the
29
TaskSpace folder tab. If you create a TaskSpace Folder tab whose root folder path is defined
as: /Demo Files/Brava for TaskSpace, when a user views a file from this TaskSpace folder
tab, the markups saved will be stored in the "annotations" folder within the repository under
/Demo Files/Brava for TaskSpace/annotations
3.2.3 Troubleshooting:
If an administrator changes the global parameter useContentServer to FALSE, Brava will not
use any of the ACS/BOCS URLs. If you are processing very large files, ACS/Page serving must
be enabled.
When "Checking-In" another file type using "Upload From the File System" (for the purpose of
comparing two files), it is important to pick the proper format type of the checked-in file.
Failure to do so, may display a different extents of one of the files.
If you are using the Preview Panel and are searching for files using the Search Tab, you will
need to set the Preferences of the Document Preview to one of the following settings:
View expanded
Show the document in a pop-up window
The framework does not support custom viewers. Because of this, Renditions are not
supported.
The ClientLoadedMaxFileSize parameter in the ivf_config.xml file is not honored when using
the "Compare To Version", to compare two files. The size of the compare file will determine if
both files are cached by the Brava! Enterprise JobProcessor.
If you did not install the Brava! Enterprise JobProcessor, you will need to increase the value of
the ClientLoadedmaxFilesSize parameter. It is recommended to increase the size to that of
largest file size in your repository.
When adding a stamp that uses %dbupdatestring(), in order to update the associated
attribute in the repository, you must close Brava in one of these two ways:
1. If the file was opened in Brava using the TaskSpace View command, you must close the
Brava window using the red X in the upper right corner or the Close menu from the window
(also Alt+F4).
2. If the file was opened in Brava using the TaskSpace Open command, you must close the
TaskSpace Open Item by clicking on the small X that appears next to the Object Name for
the tab associated with the opened item.
When using multiple instances of Brava Viewer through TaskSpace, you may receive the
following warning after successfully launching a file in a new Brava window:
Warning: Page has Expired. The page you requested was created using
information you submitted in a form. This page is no longer available. As a
security precaution, Internet Explorer does not automatically resubmit your
information for you. To resubmit your information and view this Web page,
click the Refresh button.
30
This error can be corrected by clearing your temporary internet files through ToolsInternet
Options of your browser window. From the General Tab, click Delete Files in the Temporary
Internet Files section and click OK.
31