This document will guide you in the design and implementation of product workflows for your Pressero Automated Workflow Integrator (AWI) - Fiery Integration solution.
The Pressero AWI-Fiery Integration allows print service provider organizations to automate the production of web-to-print orders. Pressero improves the ordering and fulfillment experience for your web-to-print customers and enables a unified production workflow solution for your print operation.
The Pressero AWI-Fiery Integration workflows divide into three equally important parts, or solution components. On the Pressero side, there are two components: Products within a storefront, and Rules in Pressero’s Automated Workflow Integrator (AWI) Tool. Consider the Pressero product(s) that will be made available to order, as well as the rule for that product or product family that will need to be set up in the Automated Workflow Integrator Tool to automate production.
On the Fiery side, the third component of each AWI-Fiery integration workflow is the hot folders that must be built on the Fiery. The hot folders on the Fiery server receive the orders/jobs from Pressero.
For example, if you want to create a Pressero storefront product with a company brochure and have that order be queued automatically into a PRISMAsync-connected printer and printed, then the Pressero AWI Fiery integration will automate this process for you.
The table below summarizes the three considerations, the best order to consider each component in Design and Implementation phases, and the party responsible for implementing each component.
When getting started with the integration, always begin from the point of view of the Pressero products to be included in the workflow. Products herein are defined as printed products offered through a Pressero B2C or B2B storefront that are pre-defined. Customers of the Pressero storefront simply specify the quantity of the item to be ordered. The target is to design touchless workflows, where jobs flow from order submission in Pressero through AWI directly to a target printer’s Fiery, without key operator intervention. It is not recommended to offer customizable products or file upload-type products using the integration. Such job workflows should be managed in a less automated manner and submitted from Pressero to your production workflow using a separate workflow.
Design 1: Source File
When considering your pre-defined product, from a design point of view, begin with a 1-up PDF version of the product that you intend to offer in Pressero. For the purposes of this guide, we will assume that the PDF will live in Pressero, and be forwarded to the printer for each job ordered. Other implementations are possible, but we begin with this very straightforward approach. By having the print-ready file live in Pressero and having it forwarded with each order, this reduces confusion in the print operation and particularly on the shop floor.
Design 2: DFE Hot Folders
As a second step of the Design/Concept, you will need to determine the product settings within the Fiery for the product. Supported Fierys allow you to automate and pre-determine your production settings. Media, saddle stitching, trim, bleed, and other settings available on your destination printer may be pre-defined in your Fiery. By determining the exact production settings within the Fiery at this point, you simplify not only the creation of the workflow, but the workflow itself, ensuring that jobs flow seamlessly from Pressero through AWI to the correct output device, with the correct production settings.
In certain scenarios, you may choose to hold the job in the Fiery and have a key operator release jobs manually. Some Fierys also allow held jobs to be re-routed to other printers. This can be handy in certain situations.
Whether you are holding jobs or allowing them to print unattended, it is still necessary to predefine all the relevant production settings in advance to ensure that key operators print what the customer expects, without having to stop the workflow and check.
Once you have your settings in both Pressero and the Fiery determined, then you are ready to design your Fiery hot folders, which are the conduit from AWI into the Fiery. We suggest using sensible product groupings when creating your Fiery settings to minimize the amount of administrative work. See Appendix A: Magic Products, for additional recommendations on setting up Fiery hot folders to work well with Pressero.
Lastly, you now plan out your AWI Rule(s). The AWI, or Automated Workflow Integrator, is the tool by which jobs are transferred from Pressero to external workflows, including Fierys. The AWI transfers the order/job from Pressero to each targeted Fiery along with a Job Definition Format (JDF) ticket that provides information about the job to the Fiery.
The recommended approach is that for each Product Type in Pressero, you create one AWI rule that will forward jobs of the same type to a single production Workflow on your target Fiery. These rules, once setup, automatically route incoming jobs to the target device specified.
AWI is a very flexible tool, but AWI does not support manual user intervention on where jobs are routed. If you require a workflow that would support dynamic manual routing of jobs to destination printers, consider the Pressero PRISMAdirect solution. If you’ve already purchased Pressero and your production printers, you can add PRISMAdirect to the solution after the fact. Consult with your Canon Solutions America Sales Representative for more information.
JDF is a technical standard developed by the CIP4 organization. The purpose of the standard is to facilitate interaction between different systems in a printing or print-related workflow. Canon DFEs offer an interface based on the JDF standard which allows communication with external JDF-enabled software components such as Pressero.
The CIP4 JDF specification is a very extensive standard covering all areas in the life cycle of a print job, from preflight to image rendering to finishing and packaging. Canon has developed a proprietary standard for the JDF ticket which is a subset of the CIP4 description. Documentation on this Canon standard is available on a per-device basis; consult with your Canon Solutions America Professional Services representative to obtain this information if desired.
Once you have completed the Design/Concept phase for a product, you may then proceed to the Implementation. It is important to note that the order of implementation follows a different order of precedence than the Design/Concept phase, and your initial implementation (which may have been completed by your Canon Solutions America Professional Services Consultant already) contains one-time procedures for enabling Fiery services on the Fiery to allow the AWI to connect and send jobs to the printer.
Once you have designed the overall concept of each Product for your Pressero-Fiery solution, follow the instructions below to set up each product and establish the workflow. Review Appendix A, which provides guidance on designing your products and workflows and use the Product Setup worksheet in Appendix B when setting up products. This will help you in setting up the product initially in Pressero and serve as a diagnostic tool when troubleshooting issues.
It is strongly recommended for Pressero System Administrators to set up a development storefront to test products and workflows before publishing new products on live storefronts. We also recommend that when you first implement this solution, you begin with one product and establish all the connections for a single product and validate its function before attempting to add additional products to your environment.
There are three important considerations before you begin this part of the integration.
The AWI supports two Fiery configurations for digital production presses. The supported devices and current Fierys are listed below (JMF/JDF capability required). Older versions of Fierys may be compatible. Third-party production devices with similar Fiery controllers may also be supported but are not guaranteed. Consult with your Canon Solutions America Production Analyst.
imagePRESS C10000/C8000 color digital presses
AWI must be installed on a workstation with internet access.
Pressero AWI pulls job from Pressero based on the workflow preset.
These step-by-step instructions assume that you have planned out your workflow according to the guidelines outlined at the beginning of this document. We will setup two sample workflows, one for the Fiery, and one for a PRISMAsync Fiery.
These steps are written at a high level. Detailed click-by-click instructions are contained in the appendices.
Every Pressero subscription includes access to Aleyant’s Instant storefronts. These instant storefronts are of two types; one is B2C (myownprintshop) and one is B2B (redfrog). The purpose of the instant storefronts is to assist customers in quickly setting up and publishing functional storefronts for their B2C and B2B customers. Pressero users can have a new B2B storefront up and running almost instantly.
Each instant storefront comes with a wide variety of pre-defined products (both print and non-print) that can be customized quickly for a client’s needs. The B2C has 39 pre-defined products, and the B2B has 19. That’s a total of 58 pre-defined products.
It would be daunting to setup all 58 products with 58 individual workflows in a Pressero-Fiery Integration. Instead, here are two strategies.
The simplicity and value of this approach will be apparent when you have the same product in multiple storefronts; you will only need to add the product to the relevant Pressero storefronts. There will be no need to set up duplicate AWI and Fiery workflows. The new Pressero product will automatically flow into the correct AWI rule and Fiery workflow that already exists. It is also of value when you need to add a similar product to your system; instead of starting from scratch, you already know how to add the product to your system.
Note: All order-level functions are intended to be managed in Pressero. The purpose of the integration is to transfer jobs and quantities to the Fiery to facilitate production. Jobs arrive in the Fiery and are either printed unattended or wait in the Fiery in a HOLD status for key operators to release the jobs for production.
Note: Non-print jobs should be managed within Pressero and not setup for forwarding to AWI.
The table below summarizes the 13 magic products and places each instant storefront pre-defined product into an appropriate category.
The 13 magic products can be used strategically to group like jobs in workflows that allow for touchless or near touchless production workflows using the AWI Fiery workflow. The flowchart illustrates the decision tree that you can use to decide where products fit in the 12 magic printed products list provided in this section. Note: The decision tree graphic skips the obvious decision that non-stationary products (Magic Product 13) are not printed products.
Use this worksheet to specify the attributes and names of products that you will use in your AWI DFE Integration. By planning out each product and using the worksheet, you will save yourself time and trouble by keeping a keen eye on each product you want in the workflow, and not duplicating names and attributes, which might lead to an unstable or non-functioning system.
The table contains recommendations for two integrations: one PRISMAsync and one Fiery, and a CatchAll workflow. All you need to specify is the Pressero Storefront and the Pressero Product Name. For the CatchAll, there is no Product Name as the CatchAll is designed to capture all jobs that do not have a Product Attribute assigned.
Login into the Admin console of Pressero.
Follow your normal steps for creating a product. Refer to the Knowledge Base for assistance. This instruction assumes that you have completed your Pressero Administrator training and you are familiar with setting up products for your storefront portals. This instruction will only cover the special steps for creating a product so that the product will work with the AWI DFE Integration.
On the Attributes Tab, Select the JDF_PRISMAsync_WorkflowName Attribute. For the Value field, enter the name of the Workflow you assigned to the workflow, in this case, PresseroTest.
Click the Add to List button, and the Attribute Value pair will be added to the Attribute List on the right.
On the Attributes tab, select the JDF_EFI _FieryWorkflowPreset attribute. In the Value field, enter the name of the Workflow you assigned to the workflow, in this case PresseroJDFin.
The AWI DFE Integration relies on the DFE’s ability to use hot folders to accept jobs, and the ability of the DFE to automate the treatment of jobs submitted via hot folders based on pre-defined settings in the DFE. At the high level, the workflow is conceptually the same for both Fiery and PRISMAsync DFEs. At the DFE level, implementation of the workflows is specific to both the Fiery and the PRISMAsync.
1.0 Preliminaries: some specific JDF settings are controlled on Fiery servers globally. This includes enabling JDF, and job action when the job is received (Print, Print & Hold, Process, Process and Hold, etc.). For most environments, the best practice is to set the Job action to Process and Hold. Go to Fiery command Workstation, connect to your Fiery, select Configure, Job Submission, JDF Settings and enable JDF and set the Job action to your preference.
The JDF Hotfolder behaves differently from a traditional Fiery Hotfolder. To use this workflow, you must setup a job preset on the DFE first to allow the Fiery to know how to print your job when jobs are processed through the JDF Hotfolder. You will want to plan your presets carefully as you will want to use short but meaningful names that will work well as job presets, but you will also use these names in Fiery Hotfolders, AWI and in Pressero. Choose carefully. For this instruction, setup the job preset as PresseroJDFin. Do this first.
Now you are ready to setup a JDF Hotfolder on your Fiery DFE
Launch Fiery Hotfolders.
Assign a folder name.
Specify a location for the Hotfolder.
Connect to the appropriate Fiery RIP.
Preliminaries: you must ensure the JMF support is turned on on your PRISMAsync Fiery.
Go to Settings Editor > Configuration > Connectivity > JMF Support. Remember that Port number; you will need it later.
Log in to the PRISMAsync DFE via a web browser.
Go to the Workflow tab, then Automated Workflow.
Click Add (you may have to log in as System Administrator at this point, if you’re not already).
Set up the workflow parameters, such as setting it up as a saddle-stitched booklet; be sure to specify the destination as Waiting Jobs. Again, this is a best practice setting. You may choose another available destination to meet your environment’s requirements. Remember this workflow name as you will need it in step 15 below.
Switch to the Hotfolders tab
Click Add (the screen shot is showing an edit)
Assign a folder name
Assign the automated workflow you created in step 10.
On the workstation where you set up your Fiery Hotfolder, connect to your PRISMAsync device and map the PRISMAsync Hotfolder to a drive letter.
On the workstation where you installed the Pressero AWI, browse to the IP address of the PRISMAsync DFE in a Windows Explorer window (NOT a web browser), including two backslashes (i.e. \\10.89.135.213\).
Right-click on the Hotfolder you set in step 14 and choose Map Network Drive. Choose any free drive letter.
Click on Finish.
Download and install Pressero AWI (Automated Workflow Integrator)
Download and install the AWI tool at your local PC according to the instructions found at support.aleyant.com. You will find the links to download both Windows and Mac versions of AWI in Chapter 1b. Installation. (Note: for early adopters, a special link for the beta version of AWI will be provided separately.)
4.2 Switch to the Control Files tab and click the Generate Control File checkbox
4.2.1 Select the Control File EFI Fiery JMF/JDF (Beta)
4.2.2 Add the URL for the JMF Server.
Syntax http:\\ xxx.xxx.xxx.xxx:8010>
4.2.3 Click on the "..." button to the far right of the Control File Path
4.2.4 Browse to your Fiery Hotfolder you created in step 1.4
4.2.5 Click Save
4.3 Click the plus sign to add a new rule for the PRISMAsync / varioPRINT
4.3.1 Assign the name varioPRINT JDF
4.3.2 Assign the Rule Type to Product attribute key matches
4.3.3 Assign Value Matches to the name of your PRISMAsync Workflow
4.3.4 Assign Attribute Matches to JDF_PRISMAsync_Workflow
4.4 Switch to the Control Files tab and click the Generate Control Files checkbox
4.4.1 Select the Control File Canon PRIMSAsync JMF/JDF (Beta)
4.4.2 Add the URL for the JMF Server.
Syntax http:\\ :8010>
4.4.3 Click on the "..." button to the far right of the Control File Path
4.4.4 Browse to your Fiery Hot Folder you created in step 2.11
4.4.5 Click Save
4.5 Test your workflows by ordering each product type in your storefront.
The AWI-Fiery integration is relatively straightforward, although it does involve the integration of a cloud-based platform and a Fiery using a middleware application. Though thoroughly tested, some issues can arise. Fortunately, most issues documented to date are usually correctable by the installer.
For assistance troubleshooting your Pressero product and / or your AWI workflow, open a ticket with Aleyant in the Pressero Admin Portal, or use the live chat feature.
When troubleshooting the AWI, Aleyant will invariably request a copy of the AWI database. Refer to the Knowledge Base in the Pressero online help for determining the location of this file.
Often the fix for AWI is to reinstall an updated version of AWI that Aleyant will provide you. Take heart, when installing this updated version, AWI captures and retains all your existing rules and settings so you do not have to start from scratch. The gotcha is that you will have to login in again using the AWI Credentials. Make sure you record and retain this username and login.
For assistance troubleshooting Fiery hot folder issues, consult with your Canon Solutions America Professional Services Consultant. Creating, using and maintaining hot folders should be part of the standard training curriculum; however, we recognize that long periods can pass between the need for customers to touch these settings. Always open a ticket with the Canon Solutions America HelpDesk for assistance with your Fiery.
Trouble logging in? Simply enter your email address OR username in order to reset your password.
For faster and more reliable delivery, add firstname.lastname@example.org to your trusted senders list in your email software.