Esko Pilot Automation Engine User Guide

deletion

of containers.

what you can do with files using the Pilot. Note that these users can still use the

Copy or Move File

and

Delete

File

tasks.

managing the tab 'Parameters' in a Job setup. Learn more in

Creating and Modifying a Custom Job Parameter

managing Jobs. Learn more in

Creating a Job

and

deleting

Jobs

Automation Engine

This access right: is about ...

Monitor: move tasks to trash or history

removing tasks from the Tasks list. See

Tasks list

Task

History

on page 48.

Pilot : Start the Pilot (in addition to

Shuttle)

logging in to a Pilot.

Queues: stop / start device queues

managing queues in the

Queue Monitor

and the

FlexRip

Queues

Task launching: set priority

(immediate / high)

setting a higher priority to the tasks this user launches.

Tasks: Inkremapping in inks panel

changing ink attributes in FlexRip or Imaging Engine tickets (LPI, angle, dot, remap, merge).

Tickets: create / modify / delete

(Global and Job tickets)

managing Global and Job tickets. See

Tickets

Tickets

View

Note:

This Access Right automatically grants the two below mentioned rights.

Tickets: create / modify / delete

(Job tickets only)

managing Job tickets. See

Tickets View

Tickets: Show All Tickets and their

Parameters (Public and other)

which tickets and parameters you can see in the Pilot (in the

Tickets

View, when launching a task or workflow in the

Files

View, or when opening a task ticket from the

Tasks

list).

When this is deselected, the user can only use:

• public tickets (see

Tickets

)

• public parameters in those public tickets (see

Using

Public Parameters

)

• the

Launch with

option on files (not the

New Task

option) (see

Launching a Task on a File

and

Launching a Workflow on a File

Note:

• Without this access right, a user can not create any ticket.

• In the Pilot's

Tickets Preferences

, you can use the

'Show only ...' options to simulate how the Pilot looks without this access right.

This is useful for an administrator to check which tickets and parameters a user still can see when he takes away this access right from that user.

Todo's: create / modify / delete

forwarding To Do actions to other users. Learn more in

To Do's

Automation Engine

This access right:

Viewer: Deep Zoom is about ...

using a deep zoom, both when viewing unprepared files and prepared files (when zoom is deeper than prepared for).

8.7.4 Managing Groups

You can create custom user

Groups

to easily change access rights for all group members at the same time.

You can not add Administrator users to a custom group. The Administrators group is a default group of all users that are allowed to administer users and to execute tasks that require an administrator right (for example in the

Server Admin web page

Creating Groups

Note:

You need to be logged in as an Administrator user.

In the

Users

tool or view, go to the

Groups

tab.

Press (or go to

File

New Group...

or use

CTRL + N

In the

New Group

dialog, enter the

Name

Description

and select a

Color

for the new

Group.

Click

to confirm.

See an example of user groups that may also have different access rights:

Selecting a group shows its member users.

Automation Engine

Defining Group Access Rights

You can assign relevant access rights to your custom groups.

Note:

You need to be logged in as an Administrator user.

• In the

Users

tool or view, go to the

Groups

tab.

a) Double-click a group to open its

Properties

window.

b) In the

Access Rights

tab, make the selection that you want for this group.

• You can also set a specific access right to several groups/users in one go. To do this, use the tab

Access Rights

(see an example

here

Note:

When a user is part of several custom groups, its access rights are a sum of the access rights assigned to those groups.

Adding Users to Groups

Note:

You need to be logged in as an Administrator user.

• To add users to a custom

Group

: a) Go to the

Groups

tab.

b) Select on one of the groups. All its users will be listed underneath.

c) Select the users you want to add to this group and close the dialog.

• To assign one or more

Groups

to a

User

: a) In the

Users

tab, double-click the user.

b) In its

Properties

dialog, go to the

Groups

tab.

c) Select the groups that you want to add this user to and close the dialog.

Automation Engine

9. Tools

Tools

are views and dialogs that you can open in a separate window, next to your Pilot. Many of these are also available as a View, in the left pane of the Pilot.

Closing the Pilot also closes all other open Tools.

Note:

Mind that every open tool counts as a client-server connection. Depending on your licenses, you might reach the maximum.

9.1 To Do List

The

To Do List

Tool is also a View, in the category

General

is also a View in the category

here

9.2 CTP Queues

The Tool

CTP Queues

CTP Flexo Views

on page 26. It is described in the chapter

CDI Platemaking Workflow

. Find a direct link

here

9.3 SmartNames

The

SmartNames

View and Tool is documented in the dedicated chapter

SmartNames

. Find a direct link

here

Automation Engine

9.4 Task History

To keep your Tasks view manageable, you might have to clean the list of tasks. If you do not want to keep some tasks, you can delete them. If you want to keep certain tasks or tickets for later use, you can add them to the

Task History

There are 2 ways to have finished tasks move to the Task History:

• In the Pilot, select one or multiple tasks (maybe after first setting a filter) and can click on

to move it to Task History.

• Tasks can also automatically move to this tool by using the

Task Cleanup Rules

(in the

Configure panel

AE Database

Tasks

). You can there define which ones should

automatically move to Task History. Learn more in

Task Cleanup Rules

on page 62.

To view the history, choose

Tools

Task History

. Initially none are shown. You only see tasks after clicking

Apply

on a chosen

Search

filter (or press

Enter

)

The Task History has a lot in common with the Tasks View. It lists all 'moved' tasks which you can relaunch, view and save.

You can archive entries in the Task History which you can restore later (learn more in

Why and

How To Archive parts of this History

on page 52). You can make XML reports of the tasks and use them to bill your customers.

The Task History panel has three parts:

Automation Engine

Task History XML Report

Task History Search options

Task History List

9.4.1 Task History Menus

File Menu

•

Open Task

: opens the ticket used for the selected task.

•

Export XML Report...

Writes a report of the current selection. This XML report contains task name, ticket name (whether or not the ticket was modified), the Operator, when it started, when the tasked ended, Status, Priority, job folder...

•

Archive...

It is possible to archive the data in the database to an XML file. This allows you to put the file on CD or store it somewhere else.

•

Import Archive...

Restores the data in the selected XML file in the database. A browse window pops up, browse to the archive.XML and click OK. The archive will be restored.

•

Restart History Server

This will shut down the History Server and reboot it.

•

Close Window

[Ctrl + W] Closes the window. If only one window is left, this is disabled (use

Exit, to close the last window).

Edit Menu

•

Select All

[Ctrl+ A] Selects all entries in the table.

Automation Engine

View Menu

•

Columns

: define which columns you want to see, for more information, please refer to the section on

Columns

•

Customize Current Filter

: Please see

filtering

•

Manage Views

[Ctrl + Shift + F] Here you can save the View Settings or select a previously created view.

•

Related Workflow Tasks

: Some tasks are part of a workflow, use this function to get a list of related tasks.

•

Stop

[Escape] This cancels the current database query and lets you set up a different specification.

•

Refresh

[F5] Perform another database query with the current settings.

9.4.2 Task History Toolbar

•

Open Task: opens the selected task.

•

XML Report... Writes a report of the current selection. This XML report contains task name, ticket name (whether or not the ticket was modified), the Operator, when it started, when the tasked ended, Status, Priority, Job folder...

Opens the Filter Settings dialog. Please see

filtering

Views: use the drop-down list to select 'Manage Views...' or an already defined view.

Filter

Filter Settings allow specific modification of the way the Tasks View is filtered. There are five tabs.

Automation Engine

•

Operator

Define the filter according to the Operator. Tick the ones you want to monitor.

•

State

Define the filter according to the Status of the task. Just tick the ones you'd like to view.

•

Task Type

By default, the Tasks View will show all tasks launched, but you can modify the filter in such a way that the Tasks View shows nothing but the type of tasks you are interested in.

•

Date

Define the Filter according to date and time.

• in a given time window (between [date and time] and [date and time])

• during the previous X hour(s)

• during the previous X day(s)

• during the previous X month(s)

•

Advanced

The Advanced Filter settings allow for precise queries.

Hit 'New' to define a rule. The set up is easy. You define a rule that shows X containing a certain string.

9.4.3 Task History List

The Task History list looks a lot like the

Tasks View task list

The list lists all tasks that have been moved from the Tasks View to Task History. You define

what you want to see. You can define the number of columns (see

View Menu > Columns

), you can click the head of a column to get the list to sort the way you like it, and you can filter the entries (see View Menu >

Filter

Automation Engine

9.4.4 Why and How To Archive parts of this History

Archiving serves two purposes:

• The Task History is used to make the Tasks View quicker, more user-friendly. All tasks stored in the Task History can be relaunched, it is a so called 'living archive'. As time goes by, you will end up with a Task History containing a lot of tasks that you may never want to relaunch. You can delete these tasks, but if you think that's not a good idea, you can use the

Archive function. so archiving can be a part of the Task History database maintenance.

• Archiving can be used to make a backup of the Task History data for safety reasons. You archive your data frequently, not because you need the space, but because you want to store your XML archive safely elsewhere, so you can easily restore it when problems should arise.

Archiving will store all information of certain tasks in an XML file. This adds the possibility of restoring those XML archives into the Task History. So your information will never be lost.

Note:

Archiving only works on selected tasks.

Archiving doesn't delete the archived tasks from the Task History.

Select the tasks you want to archive.

If you want to archive all tasks, press CTRL + A. If you want to make a sub selection, the Task

History reacts to the known shortcuts such as CTRL + click and SHIFT + click.

If you want to make an intelligent selection, and you don't want to lose time, you'd better use the

Filter

. You define what you want to see in the Task History (for example all tasks

Automation Engine

originating from one particular job, or handled by one particular operator, ...), click CTRL + A and you're ready to archive.

Click Archive (File Menu > Archive).

A dialog pops up, allowing you to browse to the place where you want the archive XML to be stored. Make sure to give the archive XML a meaningful name in order to avoid confusion

later on. Confusion might arise if you bear in mind that the Task History also uses the XML language to write an XML report.

Click OK.

A 'Confirm' dialog pops up and asks you whether or not you want to delete the archived items:

9.5 Devices

The View

Devices

is also available as a Tool in a separate window. Both are documented in the dedicated chapter

CDI Platemaking Workflow

. Find a direct link

here

Automation Engine

9.6 FlexRips

The

FlexRips

Tool is also a View, in the category

Setup

. It is described

here

9.7 Queue Monitor

The

Queue Monitor

Tool is also a View, in the category

Setup

here

9.8 Containers

The

Containers

Tool is also a View, in the category

Setup

here

9.9 Access Points

The

Access Points

View and Tool is described in the chapter

Integrating with External Systems

Find a direct link

here

9.10 Customers

The

Customers

Tool is also a View, in the category

Setup

here

9.11 Users

The

Users

Tool is also a View, in the category

Setup

here

9.12 Merger Monitor

If you use a

"RIP to ..."

FlexRip-ticket to output on a device that has been configured to work with merge queues, you can monitor the merging activities.

Note:

This merge tool was mainly used for Computer To Film devices.

Start the

Merger Monitor

by selecting 'Merger Monitor' from the

Tools

menu.

Automation Engine

The Merger Monitor consists of two panes.

The

left pane

lists all devices on which files have been merged or are currently waiting to be merged. In the example above there's one device listed

example_merge

. Every device on which something has been merged stays listed until the server is rebooted.

Select a device to see what is in its

merge queue

. Files that are to be merged are assembled in

pools

pool

is a group of files with the same characteristics (same plate size, negative or positive, ...).

These characteristics are defined by "

extract restrictions

" (in more recent features this is named 'Grouping Keys"). For example: jobs with a different Dot Gain Compensation setting will not be merged together. They will not belong to the same pool.

Some of these restrictions depend on the setting in the

General tab

of the ticket you use.

1. VDistortion

and

HDistortion

: Files must have the same vertical and horizontal distortion before they can be in the same pool.

Reverse

pool.

: Files have to be reversed in the same way before they can be in the same

Mirror

pool.

: Files have to be mirrored in the same way before they can be in the same

4. Dot Gain Compensation

: Only files with the same Dot Gain Compensation belong in the same pool.

The other restrictions are defined in the

Output

tab of the ticket you use.

1. Conf

: Files need to have the same plate size before they can be in the same pool.

2. Output path

and

Output File Name

: Files with different Output paths or Output File names will end up in different merge pools.

3. Resolution

: Files need to have the same resolution before they can be in the same pool.

4. Compression

: Files need to have the same compression before they can be in the same pool.

Automation Engine

Notice that

example_merge

has two pools : 20051128–1 and 20060215–1 . When you select the device, but not a pool, you get an overview of all files waiting to be merged. In order to visually indicate that files belong to different pools they have a different background color.

White and gray are used consecutively.

The

right hand panel

provides detailed information on files in the merge queue.

• The

Task ID

•

Priority

: this is the priority you defined in the Expose On ticket, not the priority of the task.

• The

Name

of the Job/File

• The

Inks

you are exposing, you defined them in the

Expose On ...

ticket.

Note:

There are two ways in which the inks are listed. C&M&Y&K or C+M+Y+K. They can be merged on separate films or on the same film.

• The

Page

number

• The

Size VH (mm)

Note:

The symbols used to indicate the size tell you whether or not the file can be rotated in the merger.

(

154

191

) indicate that the file can be rotated, an

(

154

191

) indicates that it cannot.

Rotation

is an option you can set in the

Transformations

part of

General

tab of the used task ticket.

•

Fill %

: This is (Job size / Plate size)

These percentages are relative, the overall fill depends on the margins and gap as they are currently defined in your ticket. You cannot simply add the percentages to get a correct idea of the overall fill. There are all kinds of reasons why files cannot be merged together and why the fill percentage is -as a result- not yet reached.

• The

State

of the file in this

Merger

queue

A file can be

on hold

(it's an option you can choose in the 'Expose On ticket'). A file can be

released

, but that does not mean that it will be merged, it still has to wait till the fill percentage is reached. You can

Force

a file

out

of the Merger queue. The forced out file will take as many files possible with it, if they have a 'release' status.

9.13 Configure

9.13.1 Overview and main functionality

Use the Configure tool to connect to a variety of devices and applications, and define general

Automation Engine settings.

To start Configure, go to

Tools

Configure

in the Pilot.

To Define Settings in Configure

Select the category in the left pane.

Automation Engine

Go to

File

New

Click on the default name that appears for that new item and wait a moment till the cursor allows you to change the name.

Define your settings on the right.

Go to

File

Save

Note:

(Windows) shortcuts:

•

'Insert'

: to add an item.

• 'Delete' : to delete the selected item.

•

'F2'

: to rename the selected item.

9.13.2 ArtiosCAD Servers

To configure a new ArtiosCAD Server in Automation Engine, go to

Tools

Configure

ArtiosCAD Servers

Note:

When the database is of the

DBMS Type

"Microsoft SQL Server", you can press to select the

Host

and Instance from a list.

How to configure a Standard Edition ArtiosCAD Server

Set up the ArtiosCAD Database Settings a) When using a

Microsoft SQL Server

Enter the

Name

of the ArtiosCAD database. Default is ArtiosCADdb .

Automation Engine

Enter the database

Host

name and the name of the SQL Server Instance when

ArtiosCAD is not deployed in the default unnamed instance (typically <ArtiosCAD

Server>\Esko

Enter the

Port

when not using the default.

b) When using

Oracle

Important:

The

Oracle Client Software

(

ODBC: Additional libraries for enabling ODBC applications

) needs to be installed on the Automation Engine Master and its Assistants.

When not installed, the

Create CAD Report from XML task

will not be able to connect to the

Oracle ArtiosCAD database.

Enter the name of the Oracle TNS

Service name

, for example Oracle X.E

Enter the name of the Oracle Database

Driver

Note:

The name of the

Oracle database Driver

can be found in the Drivers tab of the ODBC Control Panel ( %systemdrive%\Windows\\SysWoW64\Odbcad32.exe

) after installation of the Oracle Client Software.

Enter the database

Host

name.

Enter the

Port

when not using the default.

Enter the location of the ArtiosCAD

Defaults

This should be a

file:

URL, pointing to the ArtiosCAD Defaults., for example file://

MyMachine/ArtiosCAD

The Automation Engine Server should be able to reach this folder, and the service account of the BGMD Service should have read access to the folder. This account by default is the

System Account "BGSYSTEM" (but can be changed in

the System Account page

Note:

ArtiosCAD Defaults are

version specific

. The version of ArtiosCAD hosting the

Defaults must match with the version of CADX installed on the Automation Engine computer (Master and its Assistants)

When no ArtiosCAD Defaults location is specified, the

Create CAD Report from XML task

will use the ArtiosCAD Defaults installed on the Automation Engine computer (Master and its

Assistants).

Test the connection by clicking the

Test Connection

button.

You will get a message stating "

Connection to the database OK

", or get an error message

• when the Automation Engine server can't connect to the database,

• when the Automation Engine server can't get info about the Defaults location. If so, check if the location exists, and if it can be reached from the server.

• when the Defaults location is not a folder.

How to configure an Enterprise Edition ArtiosCAD Server

Select

Enterprise Edition

Enter the

WebCenter

location, typically http://<WebCenterServer>/WebCenter_Inst

Click

Open

to open the specified location in your default browser.

Enter the

User Name

and

Password

Automation Engine

Test the connection by clicking the

Test Connection

button.

You will get a message stating "

Connection to the database OK

", or get an error message when the Automation Engine can't connect to WebCenter.

9.13.3 Automation Engine Database

These databases are set up automatically when the Automation Engine server software is installed. In this item of the configure panel, you can see their settings, make changes and test their connection.

Attention:

In the

Automation Engine Server Web page

, in the section

databases

, you can also manage databases, but there to make changes after an installation and without the use of a Pilot.

Standard and Alternative Database Server Choices for Automation Engine

Before going in more detail, we here summarize the choices you have:

•

Standard installation with the standard database server (type)

• A standard installation of Automation Engine will install and use an

SQL Server Express

version.

•

In case you need a (much) more powerful database server

• In case you have reached the limits of the

SQL Server Express

version, you can make

Automation Engine work with a full

SQL Server

version. Learn more in

Databases

• Commercial printers with heavy loaded page workflows, can also choose to use an

Oracle

database, but only for their Application Server database.

•

Or use a small test database server for other special cases.

You can use an

"Embedded"

database:

• In exceptional cases on advise of Esko Support, for example to help solve a database problem.

• When first installing Automation Engine, to avoid that the installation installs the default

SQL Server Express, of which you know you will not use it anyway (because you already decided you will use a full SQL Server). This avoids having to uninstall that SQL Server

Express version and other peripheral software.

Important:

For more information on your options when installing Automation Engine, check the dedicated

Installation Guide

Generic setting (Setup tab): DBMS Type

We here describe the general settings of the

Setup

tab in the configuration of the various databases. See their own pages for any specific settings.

Note:

DBMS stands for "DataBase Management System".

DBMS Type "Microsoft SQL Server"

Automation Engine

These settings will be filled out correctly after installation of the server software. You can however change these settings.

Here is an example of the

Jobs

database:

•

Database

: Keep the default name or, before initial use of this database, enter a different name.

•

DBMS Type

: Select the driver type

Microsoft SQL Server

Important:

This type is valid both for an MS SQL Server Express as for a full MS SQL Server.

• You can press to select the

Host

and

Instance

from a list. Here is an example of such a list:

• Enter a correct

User

name and

Password

to access that database.

DBMS Type "Embedded" (only for test purposes)

This

Embedded

database engine is built into Automation Engine's installation kit.

Caution:

This

Embedded

database type is not suitable for production use! Embedded databases can only be used in very low volume and low load (test) circumstances.

Production level performance and stability may not be expected with this configuration.

For production use, choose a Microsoft SQL Server (or, in case of the Application Server database, Oracle). Failure to do so may, In a worst case, result in data loss or data corruption.

Automation Engine

• When the DBMS type is

Embedded

, set the

Folder

to point to the location where the embedded database will be kept on disk (for example

"C:\Esko\bg_data_database

\APPSRV"

for the Application Server database).

• Enter a correct

User

name and

Password

for the database user to create or access this database. Enter a blank user name and password when the database or the database user has not yet been created, except for the Application Server database, in which case you need to use the user name " sa ".

DBMS Type "Oracle"

Learn more about using Oracle as engine for the

Application Server

database in the chapter

Pre-Install IT Requirements

, in the page

Oracle as Database Server for the Application Server component

Generic setting (Setup tab): Testing the Connection and Applying the Config

Each database configuration has in its

Setup

tab two buttons:

Test Connection

and

Apply

Testing the Connection

Click the

Test Connection

button to perform these checks:

•

Is the database management system running?

These are possible error messages:

• When the instance is not running or accessible, you get Could not connect to the

SQL Server instance .

• When the user name / password is wrong or when there is no permission to connect, you get Trying to log in failed .

• When the host is not running or not reachable (wrong name), you get Unknown database host .

• When wrong information was typed in, you get

No such instance

•

What is the database system version?

• An error is shown when

The database system version is not supported

(anymore)

. For example: you selected an SQL Server 2000.

• A warning is shown when The database system version will soon be outdated . For example, in version 14.1, an SQL Server 2005.

•

Is the database online?

• In case of a wrong user name / password or wrong database privileges, you get Trying to open database failed .

• When the database doesn't exist, you get Could not find database .

•

What are the database user roles?

• When the user is not a member of required database roles, you get Insufficient roles .

•

What about the database system memory?

Automation Engine

•

The maximum server memory does not meet the recommendations

. This is about the memory of the (SQL) database server. For example, in version 14.1, a server minimally needs +- 4 GB.

•

The total physical memory does not meet the recommendations

. This is about the memory of the computer. For example, in version 14.1, a server minimally needs +- 4 GB.

•

Is the database system speed sufficient?

• You get a warning when

The connection is rather slow

. For example, in version

14.1, on average, connecting to the database system and getting version info takes more than 100 ms.

Note:

You can find updated and detailed minimal requirements on

http://www.esko.com/ systemrequirements

When all checks return an OK result, an info dialog will tell you that the

Database is online and accessible

Applying the Changed Configuration

After you tested the connection, and solved any errors, click

Apply

to save and apply this setup.

When you click

Apply

, Automation Engine restarts parts of its software and then starts accessing the database using the new settings.

Important:

When you do not click

Apply

, but only

Save

these (and other) changes in the Configure tool, then the changed settings will only be applied the next time the (full)

Automation Engine server software is restarted.

Tasks database

Launched tasks are stored in a database with a default name

FastLane_TM

The settings in the

Setup

tab are generic and described in the

DBMS Type

Applying the Configuration

Testing and

Task Cleanup Rules

In the Pilot, you can not keep all your finished tasks in the Tasks overview forever ; this would slow down Automation Engine and eventually fill up the tasks database.

You have the choice to

• remove them. In the Pilot tasks view, make a selection, press the

Delete

button and confirm.

• or move them to the

Task History

on page 48 tool. You can define

Cleanup Rules

to automate this cleanup.

Automation Engine

Attention:

Only finished tasks (those with a Successful done , Done with warning

Workflow failed

Failed

, or

Cancelled

) can be either moved to Task

History or be deleted. The cleanup rules mechanism will ignore tasks that are still running or waiting.

An example of

Task Cleanup Rules

The way to create these rules is very similar to making filters in many Pilot Views. You can learn how to do this from a similar example used in

Job View Filters

Attention:

The rules are executed from top to bottom, so their order is very important.

You can use the

Move Up

Move Down

buttons to make sure they are executed in the most productive order. For example: you typically first want to delete tasks and then start moving the rest to history.

Devices database

This database stores all the information that is shown in the Devices view, both for

CTP Flexo

and for

Cutting Tables

By default, this database uses the same database as for

Jobs

• Tab

Setup

Learn about these generic settings in the above pages on

DBMS Type

Applying the Configuration

Testing and

• Tab

Maintenance

Define after how many days you want to

Automatically delete records

in all the devicerelated databases. This deletes

• records in databases that are used in these Pilot Views:

• (CDI workflow):

Press Plates

Press Plate Sets

Merged Plates

• (Kongsberg workflow):

Sheets

view and (Sign & Display)

Orders

view.

The time you specified is calculated after the item's

Finished

date.

Automation Engine

• It also deletes the files in the Media Root Folder (see below) older than that specified time.

• Tab

Advanced

: Browse to specify the

Media Root Folder

When a job is finished on a Kongsberg table, a new item is added to the Kongsberg

Sheets view

. The JDF and cut file that this (database) item refers to are stored in a unique subfolder of this Media Root Folder.

Note:

Files related to the CDI Plate Merger are stored in the folder specified in

the Configure item "Plate Merger"

JDF database

This database is used when Automation Engine sends or receives JDF commands. For example when jobs are created via JDF or when WebCenter sends workflows to Automation Engine (via

JDF).

By default, this database uses the same database as for

Jobs

The settings in the

Setup

tab are as described in

Generic setting (Setup tab): Testing the Connection and Applying the Config

59 and

61.

Gang Run Printing database

This database is used by the

Gang Run Printing mode

By default, this database uses the same database as for

Jobs

The settings in the

Setup

tab are as described in

Generic setting (Setup tab): Testing the Connection and Applying the Config

59 and

61.

Task History database

The

Task History

is a tool that stores old tasks. You keep them there because you may want to look up the settings they used or to relaunch them on same or other files. Learn more in

Task

History

on page 48.

The settings in the

Setup

tab are as described in

Generic setting (Setup tab): Testing the Connection and Applying the Config

59 and in

on page

61.

Maintenance

In case this database is filling up or when you experienced that you do not need tasks of a certain age, it is advised to clean up.

•

Automatically delete tasks older than X days

. Choose this for an automatic partial cleanup.

•

Clear All Tasks in History

. This deletes everything in this database. You will be asked to confirm.

Automation Engine

Jobs database

Setup

By default the database used for jobs is named BSJobs .

Note:

The BS in the name BSJobs refers to an old Esko server software application.

The settings in the

Setup

tab are as described in

Generic setting (Setup tab): Testing the Connection and Applying the Config

59 and in

on page

61.

Maintenance

Dangling Jobs

are active Automation Engine

Jobs

that have a link to a job folder that is not there, probably because the folder was (re)moved or renamed.

Normally, each active

Job

relates to one job folder on disk. But it does happen that a user moves or deletes a job folder, for example via Windows Explorer or Macintosh Finder. This causes discrepancies between the information of that Job in the

Jobs

database and the actual situation on disk. Removing such dangling Jobs brings the database back in sync with the reality on disk.

Click

Remove

to make the database check, for each Job, whether or not their job folder still exists. You will be asked to confirm. When that folder does not exist, the Job will be removed from the Automation Engine database.

Note:

This implies that instead of deleting jobs via the Pilot, you are able to delete Jobs by deleting the corresponding folder and then manually cleaning up the dangling Jobs here.

Application Server database

This database is used when you use the Pilot Views that are valid for page workflows:

Pages

Proofs

and

Plates

(category

Commercial Print

By default, this database uses a database named fasttrack

The settings in the

Setup

tab are as described in

Generic setting (Setup tab): Testing the Connection and Applying the Config

59 and

: You then need to select the

61.

This database can also use the DBMS Type

Oracle

. Learn more about using Oracle as engine for the

Application Server

database in the chapter

Pre-Install IT Requirements

, in the page

Oracle as Database Server for the Application Server component

9.13.4 Automation Engine Web Service

This port number is used in a

Web Service Access Point

Automation Engine

By default this is port

4415

9.13.5 Cloud Storage Services

This is where you configure cloud storage destinations that the

Upload to Cloud Storage

task can upload files to and where a

Cloud Storage Access Point

can download files from.

Note:

Any form of SSO (as supported by some Cloud Storage services), is here not supported.

Access Points run as user ' BGSystem ' on the master Automation Engine server.

Configuring Box, Google Drive or OneDrive

Follow these steps to create an account:

Tools

Configure

Cloud Storage Services

, click

Add

and select the provider (Box,

Google Drive or OneDrive).

The

Add ... Account

dialog of the selected provider dialog informs you on the process and asks to sign in to that provider.

Attention:

When your internet browser is already open, an account could already be logged in to that service. To make sure you log in with the right account, close your browser first.

Click

Sign In

. Your browser opens a page asking permission for Automation Engine to view and manage files on that storage. When your browser does not auto-remember your credentials, it will first ask you to log in to that provider.

Here's an example using Google Drive (the used account name is shown top right):

Automation Engine

Click

Allow

to continue. The provider now grants access to the account and calculates a unique code.

• Google Drive shows this code in a dedicated web page. An example:

• Box and OneDrive display the code as part of the URL that the browser is redirected to.

An example:

• For Google Drive: Select the code and copy it

(Ctrl-c / Cmd-c)

• For Box and OneDrive: Select the full URL (or only the characters in the URL after the

' code=

') and copy it

(Ctrl-c / Cmd-c)

Go back to the

Add <provider> Account

dialog and paste the code or full URL in the

Code

field

(Ctrl-v / Cmd-V)

Automation Engine

Click

Continue

and add an

Account Name

and

Description

Click

Create

This account is now ready to be used in the tools that use cloud storage services.

Note:

You can reset the authorization for an account. This is needed when the authorisation token became invalid (it is broken, the administrator of the cloud storage deleted the site, ...).

Follow these steps:

• Select the account for which you want to reset the authorization.

• Click

Authenticate

• In the dialog that pops up, fill in the required key(s) and press

Authenticate

Configuring Amazon S3

Follow these steps to create an account for Amazon S3:

Tools

Configure

Cloud Storage Services

, click

Add

, select

Amazon S3

and click

In the

Add Amazon S3 Account

dialog, fill in the

Access Key ID

and

Secret Access Key

generated in the IAM module for the user linked to this account. Contact your administrator for more details.

These keys allow Automation Engine the following actions on the

buckets

(root folders) that are linked to this account:

• download, upload and remove files

• create new folders.

Automation Engine

Note:

The IAM-defined user must have sufficient permissions to access the required

buckets. Also consider limiting this user's access to one or more specific

buckets. Learn more about IAM policies and access to S3 buckets in

this online article

Attention:

When your internet browser is already open, an account could already be logged in to that service. To make sure you log in with the right account, close your browser first.

Click

Continue

and add an

Account Name

and

Description

Click

Create

to confirm and close the dialog.

Note:

You can reset the authorization for an account. This is needed when the authorisation token became invalid (it is broken, the administrator of the cloud storage deleted the site, ...).

Follow these steps:

• Select the account for which you want to reset the authorization.

• Click

Authenticate

• In the dialog that pops up, fill in the required key(s) and press

Authenticate

9.13.6 Create DCS Master

When you use the Create Master DCS task, you might want to map short names used in plates

(that might not mean anything) to full ink names. This is handy for example for plates with international ink definitions. By default,

and

are mapped to

Cyan

Magenta

Yellow and Black .

To add an ink definition, double-click an input field and start typing. Press 'TAB' to switch fields.

9.13.7 Digital Press

Use this to connect Automation Engine to the DFE (Digital Front End) of a digital press.

Select

Digital Press

and use

File

New

to create a new digital press connection.

Enter the name of your

DFE Server

and click

Connect

Note:

Make sure the DFE server is running and reachable over the network.

Automation Engine

If your connection is successful, you will see

Connection OK!

and details about the DFE server.

If your DFE server drives several presses, select the

Press

you want to connect to.

You will see details about the digital press.

Use

File

Save

to save your connection.

9.13.8 E-Mail Configuration

Automation Engine can use your E-mail server to send E-mails. These E-mails can be sent by a task

Notification

, by a dedicated

Send E-mail task

or as an extra tool when you opened a log

file.

•

Postmaster

is the E-mail address that will receive a warning mail when an E-mail could not be delivered.

•

Use as sender

: Select this to include a "

Sender

" SMTP header.

Automation Engine

The purpose of such a header is to indicate that the actual sender of the E-mail is different from the person in the '

From

' field of the E-mail. Some E-mail servers refuse to send this E-mail unless this field is specified. Certain E-mail clients will visualise the

sender

info as " sent by <postmaster> on behalf of <from>

• Check with your IT department for the correct settings of the

SMTP Server

and

SMTP Port

• Select the check box if you want to

Use a secure connection

instead of an unrestricted connection.

• If the

SMTP server

requests authentication, fill out the

User Name

and

Password

fields.

• Click on the button to

Send

Test E-mail

(see below).

•

Send Test E-mail...

The following authentication schemes are supported by the Automation Engine mail component:

PLAIN

LOGIN

and

DIGEST-MD5

•

From

: Indicates the address you're using to send the test E-mail. If no address is filled in, the postmaster address is used. You can choose a different sender to test if the mail server allows you to send e-mails on behalf of others. The

Send E-Mail

task relies on this behavior as it tries to send E-mails on behalf of the user that launches the task.

•

: Fill in a valid E-mail address that will receive the test mail.

•

Message

: You can enter a personal message or leave the default text.

• When finished, click

Send

to see whether the configuration is working properly. When the E-mail could be sent, an Info message will appear. When it failed, you will get a detailed warning message.

9.13.9 External Databases

External Databases

are databases from external systems (not part of Automation Engine).

Automation Engine uses links to such databases in

• a

Database Query SmartName

. Learn more in

Database Query SmartNames

• a

Database Access Point

. Learn more in

Database Access Point

• the

Interact with Database

task. Learn more in

Interact with Database task

Attention:

When integrating Automation Engine with an external database make sure you are compliant with the license agreements of that database manufacturer.

Note:

Configuring these links requires knowledge about database setups. If necessary, contact your IT database administrator to figure out the correct settings.

Automation Engine

Configuring External Databases

Go to

Tools

Configure

External Databases

Click

File

New

to configure a new link to a database.

A new database name is created with the name

db_number

(the number is the chronological number of the database).

In the left pane, click to select the new database and then click again to enable renaming that new database link. Type the name you want and press

Enter

to confirm.

Choose the appropriate

DBMS Type

These Database Management Systems (DBMS) are supported:

•

Microsoft SQL Server

•

ODBC Source

Note:

ODBC SmartNames created before version 14 remain unchanged but are deprecated and renamed to the

Type

32 Bit ODBC Query

•

Oracle

•

Other

(when a JDBC driver is used).

Attention:

Esko provides the drivers for both SQL and Oracle DBMS types. Not all database drivers can be freely distributed by Esko, and not all drivers have been tested. If you need to connect to

Other

types you have 2 options:

• connect using an ODBC System DSN for the database

• connect using a JDBC driver.

When your database manufacturer allows both ways, we recommend to use JDBC as a connection method. A JDBC connection is directly configured in Automation

Engine, whereas for ODBC you need to pass the DSN setup of the Windows system.

Enter the connection details. These are different per type of DBMS. See examples in

Specifics per DBMS

on page 73.

If required for the DBMS, enter the name of the

Host

. This is the database server

(computer) name.

If required for the DBMS, enter the

Port

number.

If required for the DBMS, enter the

User

name and

Password

that will be used to access the database.

Click '

Test Connection

' to test if your setup is valid. If it is not valid, the error message might contain details about the problem.

10.Disclaimer

: Be aware of the risks of direct database queries and of the fact that Esko takes no liability for them. You need to agree before this configuration can be saved.

11.

Click

File

Save

to save the configuration.

See the next section for some

specifics per DBMS

Automation Engine

Specifics per DBMS

Connecting to a Microsoft SQL Server

Connecting to a database server via ODBC

If the database manufacturer does not provide a JDBC driver, you can connect to the database using an ODBC link.

When the name of your system data source is for example '

ProductionDetails

', then enter it in the

Database

name field as ' jdbc:odbc:ProductionDetails

Note:

32-bit versus 64-bit ODBC:

• On 32-bit hardware (for example Windows Server 2003), Automation Engine tools that use these database links can only work with

32-bit Windows ODBC Data Sources

. You need to add the Data Source using the 32-bit ODBC Administrator tool (

%systemdrive%\Windows\

\SysWoW64\Odbcad32.exe

• On 64-bit hardware (for example Windows Server 2008 R2), Automation Engine tools that use these database links can only work with

64-bit Windows ODBC Data Sources

. You need to add the Data Source using the 64-bit ODBC Administrator tool (

%systemdrive%

\Windows\System32\Odbcad32.exe

Note:

As of Automation Engine 14.1 (2015), Esko only supports 64-bit systems for the

Automation Engine server(s).

Connecting to an Oracle Server

Automation Engine

Connecting an "Other" DBMS

Other

DBMS can be accessed if you can get the necessary drivers and information on how to access the DBMS via standard JDBC technology.

• Download the JDBC driver (a jar file) from the manufacturer’s website into a

Container

that is accessible to the Automation Engine (Master) server..

• Enter the required configuration fields. See an example:

• Check your JDBC driver manual for more details.

9.13.10 External Web Services

Using the

Interact with Web Service task

, Automation Engine can communicate with web services from external systems.

Automation Engine

To configure such a web service,

Go to

Tools

Configure

In the

Configure

window, select

External Web Services

Press the Insert key or go to

File

New

. Specify a name for the new

External Web

Service

Specify

URL

You can use a secure connection via SSL (a URL starting with https:// ) with or without a valid SSL certificate signed by a "Certificate Authority" (CA).

When using a secure connection without a valid certificate, import the certificate into the server

java KeyStore

. Use the following command on the Automation Engine server: keytool -import -alias mydomain -file myfile.crt -keystore C:\Esko

\bg_prog_fastserver_v40\jre\lib\security\cacerts

Check the

Allow unverified SSL Certificate

option to do this.

Warning:

This setting is not secure.

If you need to pass via a proxy, configure the proxy settings via

Tools

Configure

Web

Proxy

Select the

Authentication

mode from the drop-down options:

None

Basic

WebCenter

Caution:

About the "

WebCenter

" type authentication: if you try to connect to a

WebCenter 14 or more recent, you do not need to configure the WebCenter server, you can indicate it in the task. If you try to connect to an older WebCenter server, you have to configure the WebCenter server here and use the

Interact with Web

Service

task instead of the

Interact with WebCenter

task.

Provide

User Name

and

Password

Click

File

Save

9.13.11 FastImpose Site Preferences

The FastImpose site preferences serve to map ink names to custom names. For example if you want to map ' C ' to the French ' bleu ' on your plates.

Ink Names

Click

Add

to add two initial values to the list:

key

and

value

. Double click the words to edit them.

Tip:

A black rectangle around the field indicates that you can edit it.

If you want to change '

' to '

Bleu

', then enter

in the

Name

column, and '

Bleu

' in the

Customized Name

column:

Automation Engine

This does not change your file, but if you used marks that would output 'C' on plate, they will now mention that ink as 'Bleu'.

Surfaces

When the values that describe front - back printing modes, like

F/B, Front/Back, Back,

F, Front, B are not conform your language or your way of working, you can here change them.

An example: changing Front/Back to read Recto/Verso :

9.13.12 FlexProof - Image Downloader

Select the item

FlexProof - Image Downloader

and go to

File

New

Note:

Don't forget to save your settings. Use

File

Save

Automation Engine

Tab "General"

•

Type

: The type will appear after having synchronized. First fill in the other settings.

•

Proofer Node

: Enter the FlexProof computer name.

Attention:

The name of the Image Downloader Proof Node is case sensitive. This is not the case for the other devices.

•

Synchronize with Proof Node

.This may take a few seconds, the system will fill out the

‘

Type

’ field.

Tab "Queue"

•

Queue

: A default name is proposed. This field automatically updates when you rename the device.

•

Queue Job Limit

: A FlexRip's Dispatcher EskoLink queue can handle the expose command of 2 jobs at the same time. If you want the Automation Engine queue to allow sending 2 expose commands at the same time, then set the job limit of the Automation Engine queue on 2.

Putting this job limit on 1 will result in each expose command to that EskoLink queue being handled one by one: the second job will be ripped after the first one is completely finished

("First In First Out" principle).

Note:

Having jobs RIP'ed earlier on the FlexRip does not mean that your output device can output them any earlier.

Tab "Merge"

•

Merge

: Define if you want merge jobs on output.

•

Unit

. Select a unit for the below fields.

•

Margin

: Define an extra margin around the output.

•

Gap

: When merging, a gap adds an extra zone of empty pixels around each job.

•

Minimum Fill

: When merging, enter what percentage of minimum fill you want in the output. No output is generated before this fill percentage is reached.

9.13.13 FlexRip - Approval

Select the item

FlexProof - Approval

and go to

File

New

Note:

Don't forget to save your settings. Use

File

Save

Tab "General"

Automation Engine

•

Type

: The type will appear after having synchronized. First fill in the other settings.

•

Rip Node

: Enter the FlexRip/FlexProof computer name.

•

EskoLink Portnr.

: Enter the port number of the Dispatcher's EskoLink queue.

• Fill out these fields before you click

Synchronize with Rip

. This may take a few seconds.

Tab "Queue"

•

Queue

: A default name is proposed. This field automatically updates when you rename the device.

•

Queue Job Limit

Putting this job limit on 1 will result in each expose command to that EskoLink queue being handled one by one: the second job will be ripped after the first one is completely finished

("First In First Out" principle).

Note:

Having jobs RIP'ed earlier on the FlexRip does not mean that your output device can output them any earlier.

Tab "Merge"

•

Merge

: Define if you want merge jobs on output.

•

Unit

. Select a unit for the below fields.

•

Margin

: Define an extra margin around the output.

•

Gap

: When merging, a gap adds an extra zone of empty pixels around each job.

•

Minimum Fill

: When merging, enter what percentage of minimum fill you want in the output. No output is generated before this fill percentage is reached.

9.13.14 FlexRip - B

Select the item

FlexRip - B

and go to

File

New

Note:

Don't forget to save your settings. Use

File

Save

Tab "General"

•

Type

: The type will appear after having synchronized. First fill in the other settings.

•

Rip Node

: Enter the FlexRip computer name.

Automation Engine

•

EskoLink Portnr.

: Enter the port number of the Dispatcher's EskoLink queue.

• Fill out these fields before you click

Synchronize with Rip

. This may take a few seconds.

Tab "Queue"

•

Queue

: A default name is proposed. This field automatically updates when you rename the device.

•

Queue Job Limit

: A FlexRip's Dispatcher EskoLink queue can handle the expose command of 2 jobs at the same time. If you want the Automation Engine Queue to allow sending 2 expose commands at the same time, then set the job limit of the Automation Engine queue on 2.

Putting this job limit on 1 will result in each expose command to that EskoLink queue being handled one by one: the second job will be ripped after the first one is completely finished

("First In First Out" principle).

Note:

Having jobs RIP'ed faster on the FlexRip does not mean that your output device can output them any earlier.

•

Optimize Expose Sequence

: Select this to have all separations RIP'ed in one pass, which normally leads to faster output. For some jobs however, this way of working results in memory problems, when this happens, deselect this option so that all separations will be

RIP'ed separately (the RIP will be restarted after every separation).

Tab "Merge"

•

Merge

: We advise to set this to

as merging will then happen after this pass on the way to the Imagesetter and this gives a higher flexibility in merging (positive and negative can be merged on one film).

•

Unit

. Select a unit for the below fields.

•

Margin

: Define an extra margin around the separations.

•

Gap

: When merging, a gap adds an extra zone of empty pixels around each separation.

•

Minimum Fill

: When merging, enter what percentage of minimum fill you want in the output. No output is generated before this fill percentage is reached.

9.13.15 FlexRip - BI (Barco Imagesetter)

Select the item

FlexRip - BI (Barco Imagesetter)

and go to

File

New

Note:

Don't forget to save your settings. Use

File

Save

Tab "General"

Automation Engine

•

Type

: The type will appear after having synchronized. First fill in the other settings.

•

Rip Node

: Enter the FlexRip computer name.

•

EskoLink Portnr.

: Enter the port number of the Dispatcher's EskoLink queue.

• Fill out these fields before you click

Synchronize with Rip

. This may take a few seconds.

Tab "Queue"

•

Queue

: A default name is proposed. This field automatically updates when you rename the device.

•

Queue Job Limit

Putting this job limit on 1 will result in each expose command to that EskoLink queue being handled one by one: the second job will be ripped after the first one is completely finished

("First In First Out" principle).

Note:

Having jobs RIP'ed faster on the FlexRip does not mean that your output device can output them any earlier.

•

Optimize Expose Sequence

RIP'ed separately (the RIP will be restarted after every separation).

Tab "Merge"

•

Merge

: because this device type cannot merge, this settings is always on '

• Select a

Unit

for the below field.

•

Margin

: Define an extra margin around the separations.

9.13.16 FlexRip CDI, CDI Spark and CDI Compact

These three types of devices can be configured in the same way. Select the matching item and go to

File

New

Note:

Don't forget to save your settings. Use

File

Save

Tab "General"

•

Type

: The type will appear after having synchronized. First fill in the other settings.

Automation Engine

•

Rip Node

: Enter the FlexRip computer name.

•

EskoLink Portnr.

: Enter the port number of the Dispatcher's EskoLink queue.

• Fill out these fields before you click

Synchronize with Rip

. This may take a few seconds.

Tab "Queue"

•

Queue

: A default name is proposed. This field automatically updates when you rename the device.

•

Queue Job Limit

Putting this job limit on 1 will result in each expose command to that EskoLink queue being handled one by one: the second job will be ripped after the first one is completely finished

("First In First Out" principle).

Note:

Having jobs RIP'ed faster on the FlexRip does not mean that your output device can output them any earlier.

•

Optimize Expose Sequence

RIP'ed separately (the RIP will be restarted after every separation).

Tab "Merge"

•

Merge

: Define if you want merge jobs on output.

•

Unit

. Select a unit for the below fields.

•

Margin

: Define an extra margin around the output.

•

Gap

: When merging, a gap adds an extra zone of empty pixels around each job.

•

Minimum Fill

: When merging, enter what percentage of minimum fill you want in the output. No output is generated before this fill percentage is reached.

Tab "CDI"

When the CDI has a recent version of Grapholas software, the

Pixelclock

will here be shown as '

Automatic

Older versions ask you to define the values here:

•

Pixelclock

is set to 360.000.

Automation Engine

•

Perimeter

: Define the perimeter of the drum, in the selected unit.

9.13.17 FlexRip - HP Indigo 4000 Series

Select the item

FlexRip - HP Indigo 4000 Series

and go to

File

New

Note:

Don't forget to save your settings. Use

File

Save

Tab "General"

•

Type

: The type will appear after having synchronized. First fill in the other settings.

•

Rip Node

: Enter the FlexRip computer name.

•

EskoLink Portnr.

: Enter the port number of the Dispatcher's EskoLink queue.

• Fill out these fields before you click

Synchronize with Rip

. This may take a few seconds.

Tab "Queue"

•

Queue

: A default name is proposed. This field automatically updates when you rename the device.

•

Queue Job Limit

Putting this job limit on 1 will result in each expose command to that EskoLink queue being handled one by one: the second job will be ripped after the first one is completely finished

("First In First Out" principle).

Note:

Having jobs RIP'ed faster on the FlexRip does not mean that your output device can output them any earlier.

•

Optimize Expose Sequence

RIP'ed separately (the RIP will be restarted after every separation).

9.13.18 FlexRip - Proofer Output

Select the item

FlexRip - Proofer Output

and go to

File

New

Note:

Don't forget to save your settings. Use

File

Save

Tab "General"

Automation Engine

•

Type

: The type will appear after having synchronized. First fill in the other settings.

•

Rip Node

: Enter the FlexRip computer name.

•

EskoLink Portnr.

: Enter the port number of the Dispatcher's EskoLink queue.

• Fill out these fields before you click

Synchronize with Rip

. This may take a few seconds.

Tab "Queue"

•

Queue

: A default name is proposed. This field automatically updates when you rename the device.

•

Queue Job Limit

Putting this job limit on 1 will result in each expose command to that EskoLink queue being handled one by one: the second job will be ripped after the first one is completely finished

("First In First Out" principle).

Note:

Having jobs RIP'ed faster on the FlexRip does not mean that your output device can output them any earlier.

Tab "Proof"

Recombine Separations

You can define this workflow choice: or you choose to let the FlexRip recombine the separations or you choose to add a 'Proof (FlexProof)' task.

•

On the FlexRip

, you can add a margin, no merging is possible.

•

By Sequencing A 'Proof (Image Downloader)' Task

'FlexProof

- Image Downloader'

device from the list.

Note:

The list only shows those devices that are configured for the same node ; the RIP and Proof node must be identical.

9.13.19 FlexRip - Screened Output

Shared Settings for all FlexRip flavors of Screened and Unscreened Output

•

Tab "General"

•

Type

: The type will appear after having synchronized. First fill in the other settings.

•

Rip Node

: Enter the FlexRip computer name.

Automation Engine

•

EskoLink Portnr.

: Enter the port number of the Dispatcher's EskoLink queue.

• Fill out these fields before you click

Synchronize with Rip

. This may take a few seconds.

•

Tab "Queue"

•

Queue

: A default name is proposed. This field automatically updates when you rename the device.

•

Queue Job Limit

Engine queue on 2.

Putting this job limit on 1 will result in each expose command to that EskoLink queue being handled one by one: the second job will be ripped after the first one is completely finished ("First In First Out" principle).

Note:

Having jobs RIP'ed faster on the FlexRip does not mean that your output device can output them any earlier.

•

Tab "Merge"

•

Merge

: Define if you want merge jobs on output.

•

Unit

. Select a unit for the below fields.

•

Margin

: Define an extra margin around the output.

•

Gap

: When merging, a gap adds an extra zone of empty pixels around each job.

•

Minimum Fill

: When merging, enter what percentage of minimum fill you want in the output. No output is generated before this fill percentage is reached.

DCS

Select the item

DCS

below the item

FlexRip - Screened Output

and go to

File

New

Note:

Don't forget to save your settings. Use

File

Save

All options in the menu tabs are equal to those for other flavors. They are described in the

on page 83.

TIFF

Select the item

TIFF

below the item

FlexRip - Screened Output

and go to

File

New

Note:

Don't forget to save your settings. Use

File

Save

All options in the menu tabs are equal to those for other flavors. They are described in the

on page 83.

There is one exception for the TIFF flavor: The tab "Queue" offers this extra option:

Automation Engine

•

Optimize Expose Sequence

RIP'ed separately (the RIP will be restarted after every separation).

PDF

Select the item

PDF

below the item

FlexRip - Screened Output

and go to

File

New

Note:

Don't forget to save your settings. Use

File

Save

All options in the menu tabs are equal to those for other flavors. They are described in the

on page 83.

PS

Select the item

below the item

FlexRip - Screened Output

and go to

File

New

Note:

Don't forget to save your settings. Use

File

Save

All options in the menu tabs are equal to those for other flavors. They are described in the

on page 83.

9.13.20 FlexRip - Unscreened Output

DCS

Select the item

DCS

below the item

FlexRip - Unscreened Output

and go to

File

New

Note:

Don't forget to save your settings. Use

File

Save

All options in the menu tabs are equal to those for other flavors. They are described in the

on page 83.

TIFF

Select the item

TIFF

below the item

FlexRip - Unscreened Output

and go to

File

New

Note:

Don't forget to save your settings. Use

File

Save

All options in the menu tabs are equal to those for other flavors. They are described in the

on page 83.

There is one exception for the TIFF flavor: The tab "Queue" offers this extra option:

•

Optimize Expose Sequence

RIP'ed separately (the RIP will be restarted after every separation).

Automation Engine

PDF

Select the item

PDF

below the item

FlexRip - Unscreened Output

and go to

File

New

Note:

Don't forget to save your settings. Use

File

Save

All options in the menu tabs are equal to those for other flavors. They are described in the

on page 83.

PS

Select the item

below the item

FlexRip - Unscreened Output

and go to

File

New

Note:

Don't forget to save your settings. Use

File

Save

All options in the menu tabs are equal to those for other flavors. They are described in the