OpenText Blazon For Content Suite 16.6 - Blazon For Content Suite Administration Guide English (CLBRVWOTCS160600-ABZ-EN-01)

Blazon for Content Suite Administration
Guide
OpenText™ Blazon™ for Content Suite
This guide is intended for Blazon for Content Suite

administrators and integration users. It provides information
for installing and configuring new installations of the Blazon for
Content Suite components and using the integration features.
CLBRVWOTCS160600-ABZ-EN-01
Blazon for Content Suite Administration Guide
OpenText™ Blazon™ for Content Suite
Rev.: 2019-May-30
This documentation has been created for software version 16.6.
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 © 2019 Open Text. All Rights Reserved.

Trademarks owned by Open Text.
One or more patents may cover this product. For more information, please visit https://www.opentext.com/patents.
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
1 Installation .................................................................................. 5
1.1 Planning considerations ..................................................................... 5
1.1.1 Supported Configurations .................................................................. 6
1.1.2 Job Processor requirements .............................................................. 6
1.2 Blazon Enterprise component installation ............................................ 8
1.2.1 Queue Server installation ................................................................... 8
1.2.2 Job Processor installation ................................................................ 10
1.3 Blazon for Content Suite module installation ..................................... 12
1.3.1 Job Processor verification ................................................................ 12
1.3.2 Licensing ........................................................................................ 13
1.3.3 Install Blazon module to Content Server ........................................... 13
1.3.4 Linux installations ............................................................................ 13
2 Configure your OpenText Blazon module ............................. 15

2.1 Configure Blazon Settings ............................................................... 15
2.2 Configure Blazon as a Rendition ...................................................... 19
3 Blazon for Content Suite features and User’s Guide ........... 21

3.1 Output Format ................................................................................ 21
3.2 Redaction Options ........................................................................... 26
3.3 Destination ..................................................................................... 27
3.4 Blazon for OTCS workflow enhancements ........................................ 28
4 Tips and troubleshooting ....................................................... 31

4.1 General notes ................................................................................. 31
4.2 Troubleshooting tips ........................................................................ 31
4.3 Anti-Virus software .......................................................................... 32
5 Appendix A ............................................................................... 33
5.1 Supported file types ........................................................................ 33
5.1.1 Input file types (pre-published formats) ............................................. 33
5.1.2 Output file types (published formats) ................................................ 34
6 Copyright notices and acknowledgements .......................... 35

6.1 Blazon for Content Suite integration acknowledgements .................... 35
OpenText Blazon for Content Suite – Blazon for Content Suite Administration Guide iii
Chapter 1
Installation
This section contains information on installing and configuring Blazon for Content
Suite, which includes the Queue Server, CSF Writer, and the JobProcessor
components. The installation steps are outlined in an InstallShield Wizard for
convenience and ease of installation, however, a complete understanding of the
installation choices affords optimal setup.
The Blazon integration provides document conversion capabilities for most file
formats stored in Document Libraries within OpenText Content Server
(OTCS). Blazon is a highly scalable server for publishing document and image files
on-demand by users and can monitor Document Libraries for new files that are
uploaded. Published files are created and placed into the same or another Document
Library. The Blazon for Content Suite product utilizes the Blazon Enterprise Server
to perform publishing, thereby creating a new rendition of the file as PDF, CSF, or
TIFF that is added into an OTCS Document Library. You can add information to the
new file through banners and watermarks. The optional Blazon Redaction feature
adds redaction capability on the published files. The redaction feature makes it easy
for you to remove privacy information like social security numbers, names, phone
numbers and other sensitive or proprietary data before making documents available
to a wider audience. You can also search text for redaction using terms and wildcard
values.
1.1 Planning considerations

The Blazon for Content Suite integration is composed of three major deployment
components. The first is the integration solution that needs to be deployed to your
OTCS server(s). The other two components are part of the Blazon Enterprise
product; these are the Queue Server and the Job Processor. The Job Processor is the
engine that converts files to their target format. Since this is so resource intensive,
the Job Processor needs to be deployed on a separate machine from where OTCS is
deployed. The Queue Server is a web application that receives and queues requests
for the Job Processor.
If placed on the Content Server machine, the Queue Server needs be placed on a web
site with a different port than the OTCS server; note the Blazon for Content Suite
integration installation will create a site on port 8090 for the Queue Server if Content
Server is installed on the machine. However, for performance reasons, you’ll
typically want to install the Queue Server on the Job Processor machine, not the
Content Server machine.
OpenText Blazon for Content Suite – Blazon for Content Suite Administration Guide 5
Chapter 1 Installation
1.1.1 Supported Configurations

Installing Blazon Enterprise software on certified operating systems allows installers
to optimize performance.
.NET Framework requirement: If not detected, .NET Framework is installed on the

Job Processor.
IIS requirement: The following ASP.NET Role Services need to be enabled for the
IIS Version that is the default for the Operating System. ASP.NET roles can be found
under the Web server > Application Development category for roles.
Please refer to the product release notes document in the product support
documentation folder for detailed and the most up to date information on supported
platforms, systems, and versions.
https://knowledge.opentext.com/knowledge/cs.dll/open/61911833
1.1.2 Job Processor requirements

The Job Processor installation includes installation of the CSF Writer, which is
necessary for converting some file types. Please see OpenText Brava! - CSF Writer
User Guide (CLBRVW-UCW) for usage information.
Microsoft .NET Framework 4.6.2 is a requirement of the Blazon Job Processor and
will appear in the prerequisite list if not found on your machine during the
installation. If not detected, this .NET installation will run, and a system restart will
be required.
Service Account Requirements – The service account used to run the Job Processor
must have the following:
• Folder/Network permissions: Read and write access to the source and target
destinations for jobs (this is the displaylistcache in Blazon), as well as permission
to call the notification URL.
• Privileged Executable Launching permissions: The Job Processor service
launches instances of separate executables to handle multiple threads of
execution. These child processes need to inherit access to the printing subsystem
of Windows to successfully launch and interact.
• Printer Configuration:
– CSF Writer must be installed and configured.

– Administrative access to the CSF Writer printer driver is required.
– The CSF Writer requires that Print Spooler services be set to Automatic or
Started. The installation cannot start the Print Spooler service, required for
CSF Writer, if the service is Disabled.
– Permissions to manage the default printer.
• UAC should be disabled for the Job Processor service account
6 OpenText Blazon for Content Suite – Blazon for Content Suite Administration Guide
1.1. Planning considerations
• Microsoft Office: Access to the installed and activated version of Microsoft

Office. To render Office formats (DOC, DOCX, XLS, XLSX, PPT, and PPTX),
Office is required to be installed and licensed on the Job Processor machine(s),
and applications used for publishing initialized - before running the Job
Processor installation.
Note: Please see OpenText Brava! - CSF Writer User Guide (CLBRVW-UCW)
for additional information regarding MS Office and Outlook
requirements, installation, setup of Office applications, and more.
• Performance Counter permissions: The Job Processor accesses Windows
performance counters to track job status. The service account might need to be
added as a member of the Performance Monitor Users group if the service
account does not have full administrator privileges.
Notes
• The exact set of required permissions can vary, depending on which features
are configured, which version of Windows is used, and which version of
Office is used. Newer versions tend to be more restrictive and updates to
Windows, Windows components, or Office can sometimes change the
permissions required as well.
• We strongly recommend running the Job Processor with full administration
privileges if possible, which is the scenario that is used for product testing.
• Microsoft Office requirements are important to avoid failure when
publishing using either Office Automation (processing Office documents by
using the automation API provided as part of Office to either print to the
CSF Writer printer driver or to save the Office files to XPS or PDF format,
and then converting the result) or Print Publishing (processing documents
through an external application that prints them to the CSF Writer printer
driver, and then converting the captured data from that print operation).
• The requirements listed under printer configuration are important to avoid
problems when using Print Publishing.
• Print publishing sometimes causes third party applications to pop-up
confirmation messages. The CSF Writer sub-system attempts to
automatically handle the common messages, but does not suppress UAC
messages. Disabling of UAC is strongly recommended for the Job Processor
account to avoid job processing interruptions.
1.2 Blazon Enterprise component installation

The Blazon Enterprise components package installs the Blazon Enterprise Queue
Server and Job Processor, and a separate install package installs the Blazon
Enterprise for Content Suite integration module. Any or all of the components can
be installed individually. Due to the intensive CPU requirements of the
JobProcessor, running this component on a Content Server machine can cause CS
database transactions to time out when a library of files is being published.
As previously mentioned, it is strongly recommended that you install the Blazon

Enterprise Queue Server and Job Processor components on a machine separate from
the Blazon for Content Suite module machine.
1. Install the Queue Server on one machine

2. Install the Job Processor on one or more different machines
3. Run the Blazon for Content Suite module installer on the Content Server
machine to install the Blazon for Content Suite integration files
1.2.1 Queue Server installation

To install just the Queue Server:
1. Run this installation on one Queue Server machine. Double-click on the self-
extracting zip file that you downloaded. Setup will extract the MSI file to
prepare for installation.
2. When the InstallShield Wizard begins, on the Welcome screen, click Next.
3. Read the License Agreement and select I accept... if you have read, understand,
and agree to the terms of the Licensing Agreement. Click Next> to continue.
Click Cancel at any point during the installation to stop the installation.
Click <Back at any point to return to the previous window.
4. In the Choose Destination Location screen, click Browse to open Windows
Explorer and navigate to a desired location for the Blazon Enterprise files, or
click Next to accept the default location and continue.
5. In the Custom Setup screen, select the components you would like to install.
The Queue Server needs to be installed on just one machine. You will need to
run the installer again on each Job Processor machine to install the JobProcessor
components. To install only the Queue Server, select This feature will not be
available from the JobProcessor component list.
6. Services are installed by default. If you don't want to install services at this time,
choose This feature will not be available from the Install Service list. Note that
you will need to install services at a later time before you will be able to use
Blazon Enterprise.
7. The optional Enhanced Directory Monitoring feature is not used with the
Blazon for Content Suite integration and this install option can be ignored.
1.2. Blazon Enterprise component installation
8. In the Website information screen, if you don't want to accept the Default Web
Site, Virtual Directory name, and Port, enter your own unique name and port
of the web site that you would like Blazon Enterprise to use and click Next.
Caution
Use of a restricted name, such as “DefaultWebSite” or the computer's
hostname, will result in a “-1603” fatal error and the installation will
fail.
9. If you have elected to install services, the next screen will prompt you for your
Windows services login and password credentials. Enter valid domain and user
logon for the Queue Service, enter the username’s password in the Password
field. Services will be installed and startup automatically.
10. Click Install on the Ready to Install the Program screen and the program files
are installed.
Queue Service Account information

The following account information is needed for the Queue Service installation:
The Queue Service should be installed to run as an administrator account. Security

settings in the web.config and QueueService.exe.config are preconfigured to
allow the Queue Service and the ASP pages to communicate properly. You should
select or create a domain user for your Queue Service logon.
Directories
By default, the installation will create the following directories:
• C:\Program Files\OpenText\Blazon Enterprise, which contains the common

configuration file, Server.Properties, shared by the Queue Server and the
Queue Service.
• C:\Program Files\OpenText\Blazon Enterprise\IgcWebAppRoot
\QueueServer, which contains the ASP.NET based Queue Server.
• C:\Program Files\OpenText\Blazon Enterprise\QueueService, which

contains the Queue Service.
1.2.2 Job Processor installation

It is strongly recommended that the Queue Server and Job Processors be installed on
separate servers. Each Job Processor machine will need to have all of the
applications it will use for publishing specific formats (such as MS Office or Inventor
view) installed and initialized prior to running the Job Processor installation.
Before running the Blazon Enterprise Installation:
1. Open the Services control panel

2. Find the Print Spooler service
3. If not already started, ensure that the Startup type for the service is set to
Automatic and the service status is Started
Run the Blazon Enterprise Installation
1. Run the Installation on one or more separate Job Processor machines. When the
InstallShield Wizard begins, on the Welcome screen, click Next.
2. Read the License Agreement and select I accept... if you have read, understand,
and agree to the terms of the Licensing Agreement. Click Next> to continue.
3. In the Choose Destination Location screen, click Browse to open Windows
Explorer and navigate to a desired location for the Blazon Enterprise files or
click Next to accept the default location and continue.
4. From the Custom Setup screen, select to install the JobProcessor and all
subcomponents:
CSF Writer notes:
• By default, the CSF Writer installs as the user running the install. If you
are running the Job Processor under a different account (the same
domain user as specified earlier), you might have to manually set the
CSF Writer properties for print-publishing to work correctly.
• Before installing the CSF Writer feature, any previous versions of IGC
Writer should be uninstalled first, and then the machine rebooted.
• The print spooler service needs to be enabled and running in order to
install the printer driver. If the print spooler service is disabled, the
installer cannot start it.
5. In the Enter Queue Server Host Information screen, enter the host name and
port of the machine that the Enterprise Queue Server is or will be installed to.
6. If you have elected to install services at this time to run the Job Processor as a
service, the next screen will prompt you for your Windows services login and
password credentials that will be used to start the service. Enter valid domain
and user logon for the Blazon Job Processor service, enter the username’s
Password in the Password field. Services will be installed and startup
automatically.
1.2. Blazon Enterprise component installation
• If you install the Job Processor as a service (called BlazonEnterprise) YOU

MUST ENTER A USER ACCOUNT THAT HAS ADMINISTRATOR
RIGHTS ON YOUR MACHINE in order to avoid permissions errors after
the installation. The BlazonEnterprise service cannot run correctly as the
Local System Account because the service must interact with other processes
and components. Attempting to run the Blazon Enterprise service as the
Local System Account will cause unexpected and undesirable behaviors
with Blazon Enterprise.
• Both the Blazon Job Processor Service and the Job Processor Console are
installed. After installation you are given the opportunity to start the service.
As long as the service is not running, the console can run. The Job Processor
console must be started manually through your Windows Start menu
(>Start Blazon Job Processor) and be running on the desktop to allow
publishing. Note that if you exit out of the Command window where the
console was started, the console will stop.
7. Click Install on the Ready to Install the Program screen and the program files
and prerequisite installations are installed.
8. Prerequisite Installations: Microsoft .NET Framework 4.6.2 is a requirement of

the Blazon Enterprise Server and Job Processor. It will appear in the prerequisite
list if not found on your machine. Items listed in the prerequisite list will install
if not detected, and a system and setup restart will be required.
9. On the Installation Complete screen, click Finish to complete the Blazon

Enterprise installation.
Job Processor Account information

The following account information is needed for the Job Processor installation:
You should select or create a domain user for your Job Processor logon. This
account must have access to the source and destination directories that are
referenced in the jobs submitted for publishing.
Directory
By default, the installation will create the following directory:
C:\Program Files\OpenText\Blazon Enterprise\JobProcessor, which contains

the Job Processor and associated support files.
1.3 Blazon for Content Suite module installation

Run the Blazon for Content Suite module installer package (<version>
_blazon64_win.exe) on the Content Server machine and follow the Setup Wizard
onscreen prompts.
1.3.1 Job Processor verification

Below the Queue Statistic block of information, a list of all of your installed Job
Processors should display. If you don’t see an installed Job Processor in this list, then
it is not communicating with the Queue Service.
When the status of each Job Processor displays as UP on the Blazon Enterprise
Status Page, the system is ready for use.
Notes
• There might be a 1 or 2 minute delay before the status of the Job Processor
shows UP. Click Refresh or F5 as needed.
• If the Job Processor is installed on a server other than Queue Server machine,
the Queue Server service might need to be restarted before the new Job
Processor appears on the list.
Clicking on the link to Job Processor provides additional detail. Alternatively, the
following sample URL provides the same detail of the Job Processor.
http://yourJobProcessorServer:7070/status
Follow the steps below if you are still unable to determine the status:
Configuration check
1. Verify that the Job Processor is running.
2. Check the configuration in the JobProcessor.config file.
3. Verify that the value for queue.server.address points to the Queue Server
machine and that the port specified by queue.server.pop.port is accessible
across your network.
1.3. Blazon for Content Suite module installation
1.3.2 Licensing
By default, the Blazon Enterprise product installs a 30-day evaluation key (or
publishing of 1000 documents, whichever occurs first). You will receive a license file
called IGCKey.lic when you license your installation. Once you obtain this
permanent license key, you must copy the file to the following installation
directories to replace the 30 day evaluation license.
C:\Program Files\OpenText\Blazon Enterprise\JobProcessor\
Note: The default location given above might be different in your environment
if the installation location is changed.
A restart of the Job Processor is not necessary after updating the license file.
1.3.3 Install Blazon module to Content Server

Various modules are available for installation into OTCS. The Blazon Enterprise
module can be installed for OTCS after running the OpenText Blazon for Content
Suite module installation. Once installed, the new Blazon module will display,
along with its version number, in the Installable Modules list.
1. Log in to the OpenText Content Server Admin page ?func=admin.index.
2. Navigate to the Core System – Module Configuration section.
3. Select Install Modules.
Important
You must install the Blazon Module using the Install Modules option in
the Module Configuration, not the Upgrade Modules option.
4. The Blazon for OTCS module will display under Installable Modules.
5. Check the box next to the module and click Install.
6. When the module is finished installing, follow the instructions to reset the
Content Server service.
1.3.4 Linux installations

This section provides details for setting up Blazon for OTCS in a Linux Content
Server environment.
1. Create a Content Server system in Linux and install the Blazon for OTCS
module on the system.
2. Run the Blazon Enterprise installer on a Windows 2012 R2 system. A Blazon

Enterprise Work Directory will be created at the time of installation. Ensure
that this work directory has Read/Write permissions.
Example 1-1:
Blazon Enterprise Work Directory: \\10.96.945.xx\BlazonShare
3. Navigate to the Content Server Administration page, Blazon Configuration >

Configure Blazon Settings >Work Directory and configure the Blazon work
directory field with the path to the “BlazonShare”. Save your settings.
4. A new Linux Blazon Enterprise Work Directory folder will be created under
<CS_Home>. Provide Read/Write permissions to this folder.
5. Use CIFs (Common Internet File System) to mount a Windows share to the
Linux environment:
a. Open a terminal session.

b. As the Linux root account user, enter the following command:
mount -t cifs // <Windows Work Directory>/<Linux Path> -o
sec=ntlm,username=<Windows Admin Name>,password=<Windows Admin
Password>,noperm
Where <Windows Work Directory> = path from step #2 above and <Linux
Path> = CSHome\\<Blazon Enterprise Work Directory>.
Example 1-2:
[root@localhost bin]# mount -t cifs //10.96.94.xx/
BlazonShare /usr/local/contentserver/\\\\10.96.94.xx\
\BlazonShare -o sec=ntlm,username=Administrator,
password=Test4,noperm
6. Configure the remaining Blazon settings as described in “Configure your

OpenText Blazon module“ on page 15. To test functionality, add a file to
OTCS and Publish to Blazon.
Chapter 2
Configure your OpenText Blazon module
Once the Blazon for OTCS module is installed (as described in “Install Blazon
module to Content Server ” on page 13), the Content Server Administration page
will have a new section called Blazon Configuration. This section will have one link
labeled Configure Blazon Settings, and, if the OpenText Rendition module is
installed, it will have a second link labeled Configure Blazon as a Rendition
Engine.
2.1 Configure Blazon Settings

Queue Server
Blazon consists of two parts: a single Queue Server and one or more Job Processors.
When publishing jobs are requested, they are submitted to the Queue Server which
stores the jobs in a queue. The Job Processor(s) pulls jobs from the queue (in the
order in which they were placed there) and performs the requested processing.
The Blazon OTCS module needs to have a valid URL to communicate with the
Queue Server. By default, the Queue Server is configured to listen on port 8090. If
the Queue Server is installed on the same machine as Content Server, the URL can
use “localhost” as the URL’s hostname. The default URL looks like http://
localhost:8090/QueueServer/push.aspx, but will need to be modified if the
Queue Server is installed on a different machine or is configured to use a different
port.
Work Directory
The Blazon OTCS module requires a temporary directory to place files that will be
processed by Blazon and to retrieve files that Blazon has processed. The default
value for this property depends on the system but is usually a reasonable location
when the Job Processor is installed on the same machine as Content Server.
Chapter 2 Configure your OpenText Blazon module
When any Job Processor is installed on a different machine than Content Server, you
need to create a UNC shared directory to share data. Make sure that the user
account that the Job Processor service is configured to use and the user account that
the Content Server service is configured to use both have read and write access to
the share. Enter the path in standard UNC format (e.g. \\share\Temp\Blazon).
Blazon Group
If no Blazon group is defined, all users in OTCS are allowed to make use of Blazon
features. Too many users submitting too many jobs can negatively affect the
performance of the entire system. You can mitigate this reduction in performance
either by adding more Job Processor machines or by reducing the number of users
that can access the Blazon features from the Content Server interface.
To limit Blazon to certain users, add the groups here to which those users belong:
1. Click on the Group icon to open the group selection dialog.
2. Select a group by clicking on the Select link next to the group you wish to add.
The group will now appear in the text box.
3. After you submit the changes to the page, the selected group appears in the
Current groups list.
2.1. Configure Blazon Settings
Each group can later be removed by clicking on the Remove group icon next to
the group name.
Permissions
This area allows you to restrict who can use Blazon features based on document
permissions. Select the appropriate minimum document permission level allowed
for Content Server users to use Blazon.
Document Limits
Another method to reduce the impact of Blazon processing on the system is to limit
the number of documents a user can submit to Blazon at any one time, and to give
up on documents that appear to not be processing.
The Document limit field defines the maximum number of documents each user can
submit for processing using the multi-file Blazon Publish tool. You can set this to 0
to eliminate the limitation entirely. Doing so, however, can allow any user to
completely overload the Blazon software.
The Time limit field defines the number of seconds to wait before deciding that a
document is never going to process successfully. Up until the time limit expires for a
given job, until the expected output documents are available, Content Server
repeatedly checks the file system for those files to be completed. Checking for too
many documents that fail to publish can slow down Content Server. It is not
recommended that you remove this limitation. If needed, you can adjust it to less or
more time.
The Time available field defines how long (in hours) after a job has completed
(successfully or otherwise), that it will remain on the list of jobs on a user’s Blazon
Jobs status page. A value of 0 immediately removes the job from the list upon
completion.
Redaction Features
Redaction (eliminating sensitive information from documents) can be performed by
this optional Blazon redaction feature. This feature, when purchased, is enabled via
the Blazon licensing, and Enable redactions box should be checked by default. This
box can only be enabled if a redaction enabled Blazon license is present.
Optical Character Recognition

Optical Character Recognition can be performed by this optional Blazon OCR
feature. OCR converts image text into searchable, selectable text. This feature, when
purchased, is enabled via the Blazon licensing, and this box should be checked by
default. This box can only be enabled if an OCR enabled Blazon license is present.
Enable Versions Selection

Select this option to enable Content Server users to pick a specific version to be
published.
Enable Pages Selection

Select this option to allow users to pick specific pages to be published using the
normal page print format.
Blazon Output Format
This area allows you to set the default Blazon Publisher output formats and options
that will be used to populate the Publish with Blazon Output Format area when
Content Server users publish documents.
Rename Blazon Publishing
Use this area to change the naming of Blazon in the Action Bar Button, or the
Function menu. Leave empty to use the default values.
2.2. Configure Blazon as a Rendition
Job Priority
This value adjusts the Blazon job priority for the distributed agent. The
recommended value is 80. Be warned that setting this value below 55 will result in
significant delays to the processing of Blazon distributed agent tasks.
Publish Options
This area globally controls which options are available to users when they send files
to Blazon and are able to select Destination options for those files. Check each box
next to the option that you would like to enable for use with the Publish with
Blazon feature.
Publish Default
Use this section to set the default options and values used with the Publish with
Blazon Destination area for Content Server users.
2.2 Configure Blazon as a Rendition

If the OpenText Rendition module is installed, Blazon can be configured to be the
rendition engine. Blazon can create PDF and TIFF renditions. There are two ways
you can configure rendition rules to work with Blazon as described below, using
either preset rules or connect rules.
Preset Rules
If any of the listed file types (PDF, CSF, TIFF) do not have rules that already
represent them in the Rendition module, a preset rule will be available on this page
that will set up the rendition and version rules in the Rendition module as well as
register Blazon to be the engine for those rules.
For example, checking PDF on the Preset Rules area and clicking Submit will cause
a new rule to be created on the Rendition module’s Configure Version Folders
page and its Configure Rendition Folders page.
The preset rules include default MIME Types lists and configure the rendition
Version Folders and Rendition Folders in relation to the currently set Blazon work
directory.
Once a preset is assigned, it appears on this page in the Current Rules area.
Note: Removing rules from this Blazon Rendition rules page does not remove
them from the Configure Rendition Folders or Configure Version Folders
pages under the Rendition Administration.
Connect Rules
If both a version rule and rendition rule already exist in the Rendition module, and
the rendition rule specifies a Blazon-supported MIME Type (application/pdf,
application/x-bravax, or image/tiff), they will appear in this area of the page.
To make Blazon the rendition engine for a rendition and mime type pair, select
theMIME Type Rule that represents the files that need renditions, select the
Rendition Rule that will provide those files to Content Server, and click Submit to
connect the two rules using Blazon. This results in the pair being added as a current
rule.
To remove Blazon as the rendition engine for a pair of rules, click the Remove icon
next to the rule.
Also, remember that if Blazon is installed on a different server, all file paths need to
be UNC shares. This means that you should not use the Preset Rules when Blazon is
on a different system.
Tip: Clicking on the text Version Folders or Rendition Folder takes you to the
Rendition module admin pages for the corresponding rules.
Chapter 3
Blazon for Content Suite features and User’s Guide
Blazon for Content Suite provides single and multi-file publishing with options.
To process a single file, select the function menu for the document and click Send to
Blazon.
To process multiple files, while browsing a folder, library, or collection, check the
boxes next to the documents you wish to process, then click on the multi-file
(More...) button Blazon Publish (Publish/Redact when the redaction feature is
enabled). This will bring you to the summary and options page.
At the top of the page will be the summary of what is being processed. This includes
the document names, sizes, and total document count displays in the Item Count
area. You can specify which pages to publish, and order of publishing. When
finished selecting your publishing options as described in the following sections,
click Send to Blazon.
3.1 Output Format
The default output format and publish options in this area are set by your CS
administrator through the CS Administration Configure Blazon Settings >Blazon
Output Format area. You can select different options on a per file or per job basis.
Select one of the provided formats. If you wish to set custom options on the format,
click the Options button. This provides options that are unique to the output format
that you have selected.
PDF Publish Options

Select your publish options from the PDF publish options dialog:
• In the Pages: Size area, select to print the original page size, or select a size from
the Fit To list to force the PDF output to fit a particular paper size.
• In the Markup area, select how you would like to handle processing markups on
the file:
Chapter 3 Blazon for Content Suite features and User’s Guide
– Select Burn-in current markups to permanently burn in any open markups

into the published output. They become a permanent part of the document
image and are not PDF comments. Changemark notes are always transferred
over as PDF Comments to allow the Changemark details to be reviewed with
other PDF viewers.
– Select Insert markup as PDF comments to save any open markups as PDF
comments. If markups are saved as PDF comments, they can be altered from
Acrobat Professional.
– If Changemark notes are associated with the document, you can select to
Append Changemark notes. When selected, the content associated with each
Changemark note will print at the end of the print job as an appended page.
– If redaction entities exist in the current document, and reasons have been set,
you can choose to append redaction reasons summary pages by selecting
Append redaction reasons. When the published PDF file is viewed, the
redacted entities display text with numbered references corresponding to
each reason listed in the summary page.
• In the Include area, you can choose which existing elements of the current file to
include in your published PDF file: If Layering is selected, you must choose
whether to include All layers, or only the layers that are currently Visible in the
viewing window
• In the Coloring area, select how you would like to handle publishing colors and
line weights in the file for both the Document and markup layer(s):
– Original Colors - publishes with original colors

– Grayscale - publishes in shades of black to white
– Monochrome - publishes monochrome
• In the Create area, you can choose:
– PDF - choose this Type to create a standard PDF file.

–
- choose one of these Type options to create a PDF/A-1a, 1b,

2b, 2u, 3a, 3b, 3u, or PDF/E compatible file.
– Choose Fast Web View if you would like to enable this feature. Fast Web
View restructures a PDF document for page-at-a-time downloading (byte-
serving) from web servers. With Fast Web View, the web server sends only
the requested page, rather than the entire PDF. This option is especially
important with large documents that can take a long time to download from a
server.
3.1. Output Format
Note: If the PDF/A-1b or PDF/A-2b option is chosen, the password settings

are disabled. These types of files do not allow for password protection. In
addition, the PDF/A-1b option does not support layers and the layering
option is disabled. The layer state of a file published as PDF/A-1b will
reflect a single layer file that uses the current layer state at the time the file
is published. (In the published PDF/A-1b file, layers that were enabled at
publish time will be visible and layers that were not enabled will not be
visible).
• The Permit area allows you to specify user rights for the published document
when opened in Adobe Acrobat. You can choose to enable Change, Copy, and/or
Print permissions.
• In the Security area, you can choose to Password protect a published PDF
document. Enter the same password in the Password and Confirm fields. Users
will be prompted to enter the password before they can view the file in any PDF
viewer (Acrobat, Brava! Desktop, etc.) Note that this feature is disabled if PDF/
A-1b is selected as the output type.
• In the Watermark area, you can also choose to include Publish watermarks and
banners in your published PDF file by setting these through the Watermark/
Banners... button (see “Watermarks and Banners” on page 25). Select the Fit
document within banners option if you would like to squeeze the page to fit
within the borders of any banners that might exist.
TIFF Publishing Options

Select your publish options from the TIFF Publish Options dialog:
• In the Pages: Size area, select to print the default page size, or select a size from
the Fit To list to force the TIFF output to fit a particular paper size.
• In the Dots per inch area, enter an output resolution (DPI). The default is 300.
You can enter a preferred resolution in the text box provided. The minimum DPI
value is 60 and the maximum is 1200.
• Compression options: Use the default LZW, or select a preferred compression
type of JPEG, G4, or PACK.
• In the Options area, select how you would like to handle publishing Color and
Color depth in the file:
– Original Colors - publishes with original colors

– Grayscale - publishes in shades of black to white
– Monochrome - publishes monochrome
• You can choose to include “Publish” watermarks and banners in your published
TIFF file by setting these through the Watermark/Banners button. Select the Fit
document within banners option if you would like to squeeze the page to fit
within the borders of any banners that might exist.
CSF Publish Options

Select your publish options from the CSF Publish Options dialog:
• In the Pages: Size area, select to use the document's default page size, or you can
pick a size from the Fit to: list to force the PDF output to fit a particular paper
size.
• In the Include area, you can choose which existing elements of the current file to
include in your published CSF file. If Layering is selected, you must choose
whether to include All layers, or only the layers that are currently Visible in the
viewing window.
• In the Watermark/Banners area, you can also choose to include Print watermarks
and banners in your published CSF file by setting these through the Watermark/
Banners button (see “Watermarks and Banners” on page 25). If you enter text
into the Onscreen banner and Onscreen watermark fields, those banners and
watermarks will permanently display on the end-user's view of the published
CSF file and will take precedence over any Onscreen print or publish string that
might have been set on the file. Note that if you are republishing a CSF file to CSF,
you can only add banners and a watermark to fields that have not already been
set and locked in the current CSF file.
• Select the Fit document within banners option if you would like to squeeze the
page to fit within the borders of any banners that might exist.
• The Permit area allows you to specify user rights for the sealed document. When
the published document is viewed in a CSF reader (Brava! Desktop, Brava!
Reader, Brava! Enterprise), users will be able to click on the Visual Rights button
on the user interface to display the rights that are available for that document.
– Print/Copy/Save As - enables the following:
○ Print - enables printing of the secure document.

○ Copy to Clipboard - enables text content to be copied to the Clipboard
and pasted into another application.
○ Save View As - enables turning on and off the saving the current view as
JPG command in the CSF reader.
Note: If a loaded CSF file has Print/Copy/Save As disabled, the Print

Screen function will be disabled. Attempting to use the Print Screen key
places a Visual Rights tiled image over the Brava! viewing area,
obscuring the screen.
– Measurement - enables the measurement tools in the CSF reader.
– Markup - enables markup review and authoring or markup files associated
with published documents.
– Unredacted Viewing - This redaction feature is disabled if redactions are not
applied or have not been finalized in a previous step. When enabled and
selected, the CSF Publish Redactions Options dialog displays after you select
3.1. Output Format
OK. The dialog provides options for allowing only certain users an
unredacted view of the file by entering a redaction password.
• The Expire area lets you set expiration dates on the published document.
– No Date: Select Never as an expiration date if you do not want the published
document to expire.
– Select an absolute or relative date for access rights to expire on the published
document.
– Absolute Date: You can select a specific date for the document to expire by
selecting On and then selecting a date from the calendar control.
– Relative Date: You can select an expiration date relative to the date the
document is published. Simply choose In and use the spin box to input a
specified number of days that the document will be usable. If the In option
button is selected, the expiration absolute date field will update to reflect the
entered number of relative days. The expiration date must be at least one day
later than the publish date.
• In the Security area, select Password Protect to grant viewing rights to select
individuals. If selected, enter a password and confirmation in the text box. Users
will be prompted for the correct password before they will be allowed to view
the published file in any CSF Viewer.
Watermarks and Banners

All three Output Format publish options dialogs provide the ability to set
watermarks and banners.
To assign a watermark or banner value, select the position of the watermark or

banner using the icons in the Layout panel or the Position list in the Options area.
The large central Layout icon represents the watermark and can span the entire
page.
Once a position is selected, you can choose to alter the font, size, style (bold, italics,
or underline), and/or color. Then you can enter the text of the banner.
Banner and watermark text supports macros and values provided by Content
Server. To enter a macro, type the % key. A popup appears that will display the
available macros.
Click on the desired macro to be used and it will be inserted into the Text area.
Selecting the dbstring macro positions the cursor in between the parentheses of the
value %dbstring(), which allows you to specify values stored in Content Server.
(See OpenText Brava! for Content Suite - Brava! for CS Module Administration Guide
(CLBRVWOTCS-AGD) for available field names and syntax.)
3.2 Redaction Options

These features are available only with purchase of the optional Redaction add-on.
You can define redactions in several ways: use the included redact script builder,
upload a pre-written redact script, or upload a redact zone (a Brava! markup file
with redaction blocks placed at specific locations within the document).
Click on the Build a Redact Script button to launch the Redact Script Builder
screens.
3.3. Destination
The Names, Macros, and Terms tabs all have both a Redact button and UnRedact
button. After setting a redaction using the Redact button, you can create un-redacted
areas inside those redacted areas by specifying a subset of values that can appear
within those areas and then click UnRedact. The area will be redacted except for
those un-redacted elements.
3.3 Destination
Each publish option in this area can be enabled or disabled by your CS administrator
through the CS Administration Configure Blazon Settings > Publish Options area.
The default options for Destination are configured through the CS Administration
Configure Blazon Settings > Publish Default area.
When available, you can specify, per document, any of the available destinations for
the output of the process. If placed in the original location, you can instruct Blazon
to store the resulting files as new versions of their original counterparts, renditions
using the specified available rendition name, or replace the original entirely while
renaming the original by appending a suffix to the name.
To specify a different destination, you can choose to save the files using the same
name as the originals, zip them all into a single zip file by providing a valid zip
filename or merge the files into one single document of the chosen output type. If
you choose to merge the files into one, you can also select the option to add a table
of contents to the beginning of the resulting file, which lists the filenames of each file
in the set, each filename providing a quick link to the page within the file where the
original file begins.
3.4 Blazon for OTCS workflow enhancements

The Blazon module adds a new workflow step type called Publish (or Redact). This
step can be accessed on the Workflow Map editor by dragging the Publish icon
onto the map. Double-clicking the icon brings up the General properties tab.
Most of the options on this page are the same as those found on the standard Blazon
summary and options page, with these notable differences:
• No Items or Items Count. The workflow step allows you specify files that can be
added to the workflow later, during workflow execution.
• Step Name: A name given to the step.
• Type: The name of the step type, which is “Process with Blazon”.
• Work Files: A placeholder that specifies what files will be worked on when the
workflow step is executed.
• E-mail: If these values are filled in, an email will be sent when the step begins
execution.
Of special note is the Work Files: area. By default, the workflow attachments will be
used as the work files source folder. This can be changed to use a reference to some
other folder specified by a workflow attribute.
To set up an attribute that can be used as a work files reference:
1. Click on Map, then Attributes

2. Click Add Attributes, then Item Reference.
3. Give the new attribute a name and specify the Selectable Item Reference Types
as a Folder.
4. Click Add to Workflow Definition, then return to the Publish step definition.
Now, instead of defaulting to Workflow Attributes, you have a selection to
make from the Work Files list.
5. Click Select... and select the new attribute name.
3.4. Blazon for OTCS workflow enhancements
6. If you prefer, you can have multiple folder sources. Workflow Attachments is
always available for selection and any Item Reference type attributes will also
be available in the list.
7. If you change your mind and need to delete a selection, mouse over the item
and a line will be drawn through it. Clicking on

the stricken item will remove it.
Note: You must select at least one location in the Work Files section. Failure to
do so will prevent you from adding the step settings to the workflow
definition.
You can attach files and/or a folder reference attribute can be specified either
during the workflow configuration or during workflow execution. Choose an
option that makes sense for your needs.
The Publish step executes automatically in the workflow execution. When the
step begins, it is assigned automatically to the Admin user. Because the Admin
user is the owner of workflow operations, you can track the status of a Publish
step in progress by logging in as Admin and then using the Blazon Jobs link
under the Personal menu to see the jobs assigned to Admin.
Chapter 4
Tips and troubleshooting
This topic is a collection of troubleshooting tips for addressing common issues you
can encounter while installing and configuring your integration software. Every
installation and configuration is unique based on your requirements, third-party
software, and equipment. You will find the information in this topic helpful when
addressing setup, optimization and maintenance issues.
4.1 General notes

• The Blazon Job Processor component is a resource intensive application. If you
place it on a Content Server machine, it can interfere with OTCS operating
properly during intensive conversion activities. For this reason, it’s
recommended that you not place the Job Processor component on a Content
Server machine.
• Running the Job Processor on Windows Server 2008 causes dialog boxes to
appear to users logged into the Job Processor computer. To prevent this from
happening, disable the service Interactive Services Detection.
• For information on configuring Microsoft Outlook to convert .msg files, refer to
OpenText Blazon Enterprise - Blazon Enterprise Administration Guide (CLBRVW-
ABZ).
• Blazon Enterprise supports conversion of a large number of file types. It can use
a file’s default application print output to convert virtually any file type. To
enable conversion of additional formats, you need to add the format’s
corresponding application to the Job Processor machine, and the file’s extension
should be added to the publish.request.extensions.doc property in the
server.properties file located in the Blazon Enterprise base installation folder
(i.e. C:\Program Files\OpenText\Blazon Enterprise).
4.2 Troubleshooting tips

• If the conversion of large or graphic intensive PowerPoint files time out, update
the PrintJobTimout property in the C:\Program Files\OpenText\Blazon
Enterprise\CSFWriter\BIPrint.ini file from 120 to 500, and then restart the
JobProcessor service.
• If Office documents don't publish, verify that the Office applications are installed
on the Job Processor machine. These applications should be opened once
manually by the user account running the JobProcessor service prior to
converting these file types. An alternative to installing Office is to license the
Outside-In drivers. Contact your OpenText representative if you want to pursue
this option.
Chapter 4 Tips and troubleshooting
4.3 Anti-Virus software

The Job Processor is not supported on machines running anti-virus software. If you
have this configuration and you are experiencing problems, turn the anti-virus
software off on the Job Processor machine and restart the Job Processor.
If you must run virus protection software on the Job Processor server, you should
exclude the following directories from scanning:
C:\Windows\system32\spool\PRINTERS
C:\Windows\Temp
C:\Documents And Settings\{user}\Local Settings\Temp
C:\Program Files\OpenText\Blazon Enterprise\JobProcessor
C:\Program Files\OpenText\Brava! Enterprise\JobProcessor
If you are experiencing issues with excluding C:\Windows\Temp, you can update the
system output path of the CSF Writer Print Driver. The steps are:
1. In the Control Panel > Printers and Faxes panel, right-click on the CSF Writer
printer and select Properties.
2. Select the Advanced tab.

3. Click the Printing Defaults button.
4. Select the Filename Generation tab.
5. Change the Output Directory path to the following:

On the Queue Server machine (which is typically the same as the Job Processor
machine), the suggested path is:
C:\igcprq
On the Blazon Server machine, the suggested path is:
C:\Program Files\OpenText\Blazon Enterprise
6. Click OK to save your settings.
Chapter 5
Appendix A
5.1 Supported file types

To view the current list of supported input formats, please see the Blazon formats
document available from:
http://www.opentext.com/file_source/OpenText/en_US/PDF/opentext-article-
blazon-formats-en.pdf
Blazon Enterprise will read a supported input file type and publish it to an output
format valid for the input you specified.
Blazon Enterprise supports conversion of a large number of file types. It can use a
file’s default application print output to convert virtually any file type (meaning that
the Job Processor machine must have a Print to command available in the native
application for that extension) . To enable conversion of additional formats not on
this list, you need to install the format’s corresponding application on the Job
Processor machine. For example, Office formats require that Microsoft Office be
installed. In addition, the file’s extension should be added to the publish.
request.extensions.doc, pdf, drw, or 3d property in the server.properties file
located in the Blazon Enterprise base installation folder (i.e. C:\Program Files
\OpenText\Blazon Enterprise).
If a new extension is added to a publish.request.extension.<format> list, stop

and restart the Blazon Job Processor Service and restart IIS to acknowledge the new
entry.
5.1.1 Input file types (pre-published formats)

• Drawing File Extensions:
publish.request.extensions.drw=000,3df,3ds,
906,907,afp,arx,asm,bmp,
cal,ccz,cg4,cgm,cgmct,cgmt,cit,cmi,csf,mi,dft,dc,dgn,dgn7,dls,dsf,
dsn,dwf,dwfx,dwg,dxf,edc,emf,eps,fax,g3,gif,gp4,grp,hdp,hgl,hpgl,
hsf,i3f,iam,ica,icd,icf,ics,idw,iges,igs,ipt,iso,isf,jp2,pg,jpeg,
jpm,m3r,mcs,mil,mrk,mvp,mvs,neu,neu.1,par,pcd,plt,png,prt,prt.1,
ps,psd,psm,pub,ref,res,rle,rnl,rtl,sat,sid,sldasm,slddrw,sldprt,
slp,stl,step,stp,tg4,tif,tiff,txt,vda,vrl,wdp,wmf,wrl,x_t,xdl,
xgl,xml,xpr,xps,zgl
• Document File Extensions:
publish.request.extensions.doc=doc,dochtml,docx,
eml,htm,html,mht,mhtml,mpp,msg,pps,ppsx,ppt,pptx,rtf,vdx,vsd,vsdx,
vsx,xls,xlsx,
Chapter 5 Appendix A
xlsm,xltx,xlw
publish.request.extensions.pdf=pdf,key,numbers,pages
• 3D File Extensions:
publish.request.extensions.3d=par,psm,asm,sldprt,sldasm,
iges,wrl,iam,ipt,stl,sat,acis,slp,xgl,zgl,hsf,
3ds,ics,prt,xas,xpr,neu,x_t,vda,step,stp
5.1.2 Output file types (published formats)

2D Type 3D Type
CSF 3DF
XDL STL
PDF ISF
TIFF
Chapter 6
Copyright notices and acknowledgements
This software includes third party component software distributed by OpenText to

you pursuant to specific third party license agreements, whose terms and conditions
are as set forth in your license agreement with OpenText and/or the Terms and
Conditions of Embedded Products. Copies of such Embedded Software Licenses
relating to the use and distribution of such Embedded Products can be found in the
product install directory. You agree to comply with all such Embedded Software
Licenses which apply to the Software licensed to you by OpenText.
6.1 Blazon for Content Suite integration

acknowledgements
3rd party notices specific to Blazon for Content Suite include the following:
jsl18n library
• Copyright © 2010 Daniel Abrahamsson

• See jsl18n_LICENSE.txt

OpenText Blazon For Content Suite 16.6 - Blazon For Content Suite Administration Guide English (CLBRVWOTCS160600-ABZ-EN-01)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenText Blazon For Content Suite 16.6 - Blazon For Content Suite Administration Guide English (CLBRVWOTCS160600-ABZ-EN-01)

Uploaded by

Copyright:

Available Formats

Blazon for Content Suite Administration

OpenText™ Blazon™ for Content Suite

This guide is intended for Blazon for Content Suite

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1

Copyright © 2019 Open Text. All Rights Reserved.

No Warranties and Limitation of Liability

2 Configure your OpenText Blazon module ............................. 15

3 Blazon for Content Suite features and User’s Guide ........... 21

4 Tips and troubleshooting ....................................................... 31

6 Copyright notices and acknowledgements .......................... 35

1.1 Planning considerations

1.1.1 Supported Configurations

.NET Framework requirement: If not detected, .NET Framework is installed on the

1.1.2 Job Processor requirements

– CSF Writer must be installed and configured.

• Microsoft Office: Access to the installed and activated version of Microsoft

1.2 Blazon Enterprise component installation

As previously mentioned, it is strongly recommended that you install the Blazon

1. Install the Queue Server on one machine

1.2.1 Queue Server installation

Queue Service Account information

The Queue Service should be installed to run as an administrator account. Security

• C:\Program Files\OpenText\Blazon Enterprise, which contains the common

• C:\Program Files\OpenText\Blazon Enterprise\QueueService, which

1.2.2 Job Processor installation

Before running the Blazon Enterprise Installation:

1. Open the Services control panel

Run the Blazon Enterprise Installation

CSF Writer notes:

• If you install the Job Processor as a service (called BlazonEnterprise) YOU

8. Prerequisite Installations: Microsoft .NET Framework 4.6.2 is a requirement of

9. On the Installation Complete screen, click Finish to complete the Blazon

Job Processor Account information

C:\Program Files\OpenText\Blazon Enterprise\JobProcessor, which contains

1.3 Blazon for Content Suite module installation

1.3.1 Job Processor verification

1. Verify that the Job Processor is running.

2. Check the configuration in the JobProcessor.config file.

C:\Program Files\OpenText\Blazon Enterprise\JobProcessor\

1.3.3 Install Blazon module to Content Server

1. Log in to the OpenText Content Server Admin page ?func=admin.index.

2. Navigate to the Core System – Module Configuration section.

3. Select Install Modules.

5. Check the box next to the module and click Install.

1.3.4 Linux installations

2. Run the Blazon Enterprise installer on a Windows 2012 R2 system. A Blazon

3. Navigate to the Content Server Administration page, Blazon Configuration >

a. Open a terminal session.

6. Configure the remaining Blazon settings as described in “Configure your

Configure your OpenText Blazon module

2.1 Configure Blazon Settings

1. Click on the Group icon to open the group selection dialog.

Optical Character Recognition

Enable Versions Selection

Enable Pages Selection

Blazon Output Format

Rename Blazon Publishing

2.2 Configure Blazon as a Rendition

3.1 Output Format

PDF Publish Options

– Select Burn-in current markups to permanently burn in any open markups

– Original Colors - publishes with original colors