Chapter 6 - Integrations

tBOT > tBot User Manual

Impostrip integration

 
  1. Create a new queue and add a download action to it
  2. Configure the tBot download action:



    a.Choose “tFlow” as the data source (default value)
    b. Enter the tFlow server URL to field 2, (Example: http://testtflow.com:8080/ - only the root URL is required)
    c. Enter API key 
    d. Enter Secret key 
    e. Choose “Download folder” - local directory for downloaded files (You can write it by hand or press F2/ellipsis to open directory selection.)
    f. Choose the interval to check new files on the server
    g. Choose retrieve interval and attempts count
    h. You can group files in “Download folder” by the customer’s names or order number. This means that tBot will create a special folder for customer’s name or order in the “Download folder” and put related files to this directory.
    i. Choose file type to download. You can select:
          Production (default value)
          Proof file
    j. Click “Test Connection”. You should see a message that connection settings are valid.
  3. Check the “Impostrip” checkbox:


     
  4. Select ini-file with Impostrip configuration(sample file: https://www.dropbox.com/s/umglhr8hqbvb69h/SampleConfiguration.ini?dl=0 ) The default location for the configuration file is C:\Program Files (x86)\Ultimate Technographics\Impostrip Automation\
  5. Check the combo box with hot folders. It should contain actual hot folders.
  6. Save Queue.
  7. tBot will create in tFlow a “virtual queue” for each Impostrip hot folder, so the user can select a destination in tFLOW. The format of the queue will be: {Queue name} – {Hot folder name}


     
  8. Impostrip integration supports batches:
    a. Below is a sample xml file generated by tBot for a single job:
    <UltimateImposition>
     <Redirection>
       <PrintJob JobID="1">
         <QueueName>
           <Name>Business-Cards</Name>
         </QueueName>
         <CustomValues>
           <CustomValue key="Order" value="686-9" />
         </CustomValues>
         <Documents>
           <DocFile>
             <FullPathName>C:\AWI\Files\2016-02-25-16-06-02-686.9-686-9-.pdf</FullPathName>
             <PageRange UseAllPages="true" />
             <Quantity>5.0</Quantity>
           </DocFile>
         </Documents>
       </PrintJob>    
     </Redirection>
    </UltimateImposition>

    b. Sample xml file generated by tBot for two jobs: 
    <UltimateImposition>
     <Redirection>
       <PrintJob JobID="1">
         <QueueName>
           <Name>Business-Cards</Name>
         </QueueName>
         <CustomValues>
           <CustomValue key="Order" value="686-9" />
         </CustomValues>
         <Documents>
           <DocFile>
             <FullPathName>C:\AWI\Files\2016-02-25-16-06-02-686.9-686-9-.pdf</FullPathName>
             <PageRange UseAllPages="true" />
             <Quantity>5.0</Quantity>
           </DocFile>
         </Documents>
       </PrintJob> 
       <PrintJob JobID="2">
         <QueueName>
           <Name>Business-Cards</Name>
         </QueueName>
         <CustomValues>
           <CustomValue key="Order" value="686-10" />
         </CustomValues>
         <Documents>
           <DocFile>
             <FullPathName>C:\AWI\Files\2016-02-25-16-06-02-686.10-686-10-.pdf</FullPathName>
             <PageRange UseAllPages="true" />
             <Quantity>10.0</Quantity>
           </DocFile>
         </Documents>
       </PrintJob>   
     </Redirection>
    </UltimateImposition>

Insoft Imposition integration

 
  1. Create a new queue and add a download action to it.
  2. Configure the tBot download action:



    a. Choose “tFlow” as the data source (default value)
    b. Enter the tFlow server URL to field 1(Example: http://testtflow.com:8080/ - only root URL required)
    c. Enter API key
    d. Enter Secret key 
    e. Choose “Download folder” - local directory for downloaded files (You can write it by hand or press F2/ellipsis to open directory selection)
    f. Choose interval to check new files on server
    g. Choose retrieve interval and attempts count
    h. You can group files in the “Download folder” by customer’s names or order number. This means that tBot will create a special folder for the customer’s name or order in the “Download folder” and put related files to this directory.
    i. Choose file type to download. You can select:
         Production (default value)
         Proof file
    j. Click “Test Connection”. You should see a message that connection settings are valid.
  3. Select “Insoft Imp” from the systems list:
  4. Load materials list from the Imposition configuration file
    a. Click “Load materials”
    b. Select ini-file with Imposition configuration(sample file: https://www.dropbox.com/s/6u3or73c3ogc9ez/ConfigXML.xml?dl=0)


     
  5. Check the combo box with materials and grades.  It should contain actual values.


     
  6. Save Queue
  7. tBot will create in tFlow a “virtual queue” for each material and grade, so the user can select a tFlow destination. Format of the queue will be: {Queue name} – {Grade name} – {GSM ID}


     
  8. Please, note that tBot requires ImpLink API 7.0. 

How to config Nexio and NetSuite integration

Primary Functionality

Connects Caldera Nexio and Aleyant tFLOW via tBOT to facilitate data exchange between the two applications. Through Nexio, tBOT can read Caldera printer configurations and publish them to tFLOW as virtual production queues, to which tFLOW users can send files to be printed. When a print file is sent to Caldera via the production queues, tBOT generates the JDF and JMF files used by Nexio to automate print setup in the RIP.

tBOT can also read the print log from Nexio such as print time, ink consumption, job state, etc., and send the information to another system such as an MIS.

Objective/Key Benefits

The JDF/JMF data exchange enables automated setup and print, speeding up the production process while decreasing the possibility for user error. Jobs can be defined upstream in the workflow and sent all the way through to print without user intervention.

Caldera connection requirements

 
  • Caldera RIP
  • Nexio license
  • Correctly configured Nexio plugin

tFLOW connection requirements

  • tFLOW Enterprise
  • tBOT
  • Correctly configured tBOT production queue connected to Nexio 

Benefits

  • One hot folder is created in each RIP
  • tBOT connects to the Nexio, reads printer configurations, and automatically creates queues
  • tBOT queues become visible in tFLOW, allowing user to submit from tFLOW to a specific printer configuration and parametrize RIP functionality on the fly

Limitations

  • Requires more setup than simple hot folder Benefits
  • Only one folder is needed in each RIP
  • Job parameters can be configured on the fly - resolution, substrate, quantity, etc.
  • JDF or XML instructions that accompany the print file pre-program the RIP with instructions
  • New print configurations are updated as tBOT queues automatically
  • Full print automation
  • Bi-directional flow of information allows print data to be sent back upstream

Nexio configuration

  1. Configure Nexio plugin on Caldera RIP


     
  2. Fill Field 1 “Base URL” with your Caldera RIP instance address
  3. Check Field 2 – Status should be “Running”
  4. Check field 3 “Base Path” (Field 3) – it will be needed later.
  5. Check field 4 “Path” (Field 4) – it will be needed later – this is the Nexio hot folder.

tBot configuration

  1. To integrate Net Suite and Caldera, configure your profile following the steps below:



    a. Click the “Profiles” button on the main screen
    b. Select a profile from the list or create a new one
    c. Select the source and destination systems
    d. Fill the parameters for the destination system connection. For the source system connection, the system will be configured in related queue action.
    e. Fill the mappings between the source system fields and destination system fields
    f. Click “Save” to confirm changes
  2. Create a new queue and add a download action to it
  3. Configure the tBot download action:


    a. Choose “tFlow” as the data source (default value)
    b. Enter your tFlow server URL to field 1 (Example: http://testtflow.com:8080/ - only root url required)
    c. Enter API key 
    d. Enter Secret key 
    e. Choose the “Download folder” - local directory for downloaded files (You can write it by hand or press F2/ellipsis to open directory selection)
    f. Choose the interval to check new files on server
    g. Choose retrieve interval and attempts count
    h. You can group files in the “Download folder” by the customer’s name or order number. This means that tBot will create a special folder for the customer’s name or order in the “Download folder” and put related files to this directory.
    i. Choose file type to download. You can select:
         Production (default value)
         Proof file
    j. Click “Test Connection”. You should see a message that the connection settings are valid.
  4. Select “Caldera (via Nexio)” from the systems list.
  5. Set the connection settings:
    a. Set the URL address to Nexio: it should be a combination of “Base URL” and “Base path” from step Nexio configuration step.
    b. Click “Load Devices” to get a list of printers.
    c. Select Export profile from step 1 if you need to export data to Net Suite.
    d. Select Nexio hot folder  - you can take it from Nexio configuration step 2.d


     
  6. Save queue.
  7. tBot will create in tFlow a “virtual queue” for each hot folder, so the user can select in tFlow destination. Format of queue will be: {Queue name} – {device name}
  8. Sample of JDF file generated by tBot
<?xml version="1.0" encoding="utf-8"?>
<JDF xmlns:cal="http://www.caldera.com/jdf"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="2 FALSSB7G2 Falcon 7ft Spike Graphic
Package" JobID="2 FALSSB7G2 Falcon 7ft Spike Graphic Package" JobPartID="1"
Status="Waiting" Activation="Active" Type="DigitalPrinting" Version="1.4"
ICSVersions="Base_L1-1.4" DescriptiveName="Production - Carlsbad: 2 FALSSB7G2 Falcon 7ft
Spike Graphic Package">
<ResourcePool>
<RunList Class="Parameter" ID="RL001" Status="Available">
<LayoutElement>
<FileSpec URL="file://FILES/1102110-4__HR.pdf" />
</LayoutElement>
</RunList>
<DigitalPrintingParams Class="Parameter" ID="DPP001" Status="Available" />
<Device Class="Implementation" ID="DEV001" Status="Available"
DeviceID="Rhotex-322:Stretch" />
<Component Class="Quantity" ID="C001" Status="Unavailable"
ComponentType="FinalProduct" />
</ResourcePool>
<ResourceLinkPool>
<DigitalPrintingParamsLink Usage="Input" rRef="DPP001" />
<DeviceLink Usage="Input" rRef="DEV001" />
<RunListLink Usage="Input" rRef="RL001" />
<ComponentLink Usage="Output" rRef="C001" Amount="1" />
</ResourceLinkPool>
<AuditPool>
<Created AgentName="Production - Carlsbad" AgentVersion="10.0"
TimeStamp="2016-11-18T07:04:32-08:00" />
</AuditPool>
</JDF> 
 
Sample of information extracted by tBOT for MIS system:
<print_width unit="Inchs">12.000000</print_width>
<print_height unit="Inchs">24.400000</print_height>
<media_width unit="Inchs">126.000000</media_width>
<media_height unit="Inchs">24.400000</media_height>
<media_usage_ratio>0.095238</media_usage_ratio>
<job_id>5402</job_id>
<job_name>1102110-4__HR.pdf</job_name>
<job_state idx="7">Finished</job_state>
<job_error/>
<server_name>Rhotex-322</server_name>
<server_host>10.0.20.23</server_host>
<create_time timestamp="1478900221">Tue Nov 22 01:02:15 2016</create_time>
<job_mode idx="3">PDF</job_mode>
<cut_barcode>63905CFC</cut_barcode>
<nb_printed>8</nb_printed>
<begin_time timestamp="1478901971">Tue Nov 22 01:03:15 2016</begin_time>
<print_time_sec>13</print_time_sec>
<op_time timestamp="1478901971">Tue Nov 22 01:03:28 2016</op_time>
<ink_cons unit="ml" total="0.585580">
<ink name="Cyan" short="C" unit="ml">0.100731</ink>
<ink name="Magenta" short="M" unit="ml">0.126355</ink>
<ink name="Yellow" short="Y" unit="ml">0.138821</ink>
<ink name="Black" short="K" unit="ml">0.134930</ink>
<ink name="LightBlack" short="k" unit="ml">0.084743</ink>
 

How to config Ergosoft integration

1. Create a new queue and add a download action to it
2. Configure the tBot download action:

    a, Choose “tFlow” as the data source (default value)
    b. Enter the tFlow server url to field 1(Example: http://testtflow.com:8080/ - only root url required)
    c. Enter API key 
    d. Enter Secret key 
    e. Choose “Download folder” - local directory for downloaded files (You can write it by hand or press F2/ellipsis to open directory selection)
    f. Choose the interval to check new files on the server
    g. Choose retrieve interval and attempts count
    h. You can group files in the “Download folder” by the customer’s names or order number. This means that tBot will create a special folder for customer’s name or order in the “Download folder” and put related files to this directory.
    i. Choose file type to download. You can select:
        Production (default value)
        Proof file
    j. Click “Test Connection”. You should see message that connection settings are valid.
3. Select “Ergosoft” from the systems list.
4. Select ini-file with configuration(sample file: https://www.dropbox.com/s/pgr62dxdbg5l2ww/SampleConfiguration.ini?dl=0 ), default location is “<UserDir>\Data\PrEnvFiles”

5.
Save Queue
6. tBot will create in tFlow a “virtual queue” for each hot folder, so the user can select in tFlow destination. Format of queue will be: {Queue name} – {hotfolder path}
7. If you want to use environments, you need to select related flag:
a. tBot will scan ini folder for *.prenv files
b. For each file tBot will create virtual folder : {Queue name} - {Printer environment name}
c. In XML tBot will add additional information about Printer environment
8. Ergosoft integration supports batches:
    a. Sample xml file generated by tBot for single job:
<?xml version="1.0" encoding="utf-8"?>
<HotFile NumCopies="5">
 <Image FileName="F:\Work\_tmp\0987-2_.pdf" />
</HotFile>
    b. Sample xml file generated by tBot for two jobs: 
<?xml version="1.0" encoding="utf-8"?>
<HotFile NumCopies="5">
 <Image FileName="F:\Work\_tmp\0987-1_.pdf" />
</HotFile>
<HotFile NumCopies="10">
 <Image FileName="F:\Work\_tmp\0987-2_.pdf" />
</HotFile>
9. When the file will be processed tBot will generate the xml file in selected hot folder, example:
https://www.dropbox.com/s/ysiya5reupptt69/OutputExample.xml?dl=0
 

How to config Compose integration

 
1. Create new queue and add download action to it
2. Configure tBot download action:
    a. Choose “tFlow” as data source (default value)
    b. Enter tFlow server url to field 1(Example: http://testtflow.com:8080/ - only root url required)
    c. Enter API key 
    d. Enter Secret key 
    e. Choose “Download folder” - local directory for downloaded files (You can write it by hand or press F2/ellipsis to open directory selection)
    f. Choose interval to check new files on server
    g. Choose retrieve interval and attempts count
    h. You can group files in “Download folder” by customer’s names or order number. This means that tBot will create special folder for customer’s name or order in “Download folder” and put related files to this directory.
    i. Choose file type to download. You can select:
        i. Production (default value)
        ii. Proof file
    j. Click “Test Connection”. You should see message that connection settings are valid.
 
3. Select “Compose XML” from systems list.
4. Set path for xml tickets (Example: “F:\Work\_tmp\tBot\Compose\Ticket”, there xml ticket will be generated)
5. Set path for job files (Example: “F:\Work\_tmp\tBot\Compose\Files”, there artworks will be saved)
6. Save queue.
7. Sample xml file generated by tBot for a single job:

<?xml version="1.0" encoding="utf-8"?>

<orderInfo xmlns="http://w2p.aleyant.com/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

    <OrderID>918</OrderID>

    <OrderNumber>996</OrderNumber>

    <OrderDate>2017-03-11T07:00:00.0000000+07:00</OrderDate>

    <OrderedBy>

        <LastName></LastName>

        <FirstName></FirstName>

        <Email></Email>

    </OrderedBy>

    <OrderItems>

        <orderInfoItem>

            <ItemId>1158</ItemId>

            <Seq>1</Seq>

            <ItemName>1-1-Store Banner, 4x8</ItemName>

            <productName>Store Banner, 4x8</productName>

            <productURL>store-banner-4x8-full-color</productURL>

            <Quantity>1</Quantity>

            <PricingParms>

                <Options>

                    <Option>

                        <Key xsi:type="xsd:string">Colors</Key><Value xsi:type="xsd:string"></Value>

                        <Key xsi:type="xsd:string">Paper Stock</Key><Value xsi:type="xsd:string"></Value>

                    </Option>

                </Options>

            </PricingParms>

        </orderInfoItem>

    </OrderItems>

</orderInfo>

How to config Zund integration

 
  1. Create new queue and add download action to it

  2. Configure tBot download action:

  1. Choose “tFlow” as data source (default value)

  2. Enter tFlow server url to field 1(Example: http://testtflow.com:8080/ - only root url required)

  3. Enter API key

  4. Enter Secret key

  5. Choose “Download folder” - local directory for downloaded files (You can write it by hand or press F2/ellipsis to open directory selection)

  6. Choose interval to check new files on server

  7. Choose retrieve interval and attempts count

  8. You can group files in “Download folder” by customer’s names or order number. This means that tBot will create special folder for customer’s name or order in “Download folder” and put related files to this directory.

  9. Choose file type to download. You can select:

  1. Production (default value)

  2. Proof file

  1. Click “Test Connection”. You should see message that connection settings are valid.

  1. Select “Zund” from systems list.

  2. Load material from config file (Example: )

  3. Check materials list

  1. Enter Zund server url(Example: http://localserver:8080/ - only root url required)

C:\Users\DrozdovVA\Desktop\3.png

  1. Save queue.

  2. tBot will create in tFlow “virtual queue” for each hot folder, so user can select in tFlow destination. Format of queue will be: {Queue name} – {material}

  1. tBot will make http request to Zund server and submit a new job.

How to config Phoenix Imposition integration

 

Configure Phoenix

  1. Configure Hotfolder in Phoenix Imposition:

    1. Set hotfolder name

    2. Set input path for xml-tickets

    3. Set output path for generating reports

C:\Users\DrozdovVA\Desktop\3.png

  1. Configure default actions:

<?xml version="1.0" encoding="UTF-8"?>

<phoenix-actions version="1.0">

  <create-job id="10" />

  <set-press id="20">

     <set-press-resource>

        <name>Defaults/B1 Sheetfed Offset</name>

     </set-press-resource>

  </set-press>

  <set-plate id="21">

     <set-plate-resource>

        <name>Defaults/745 x 605 mm</name>

     </set-plate-resource>

  </set-plate>

  <set-sheet id="22">

     <set-sheet-resource>

        <stock>Gloss Coated</stock>

        <name>1000 x 707mm Long</name>

     </set-sheet-resource>

  </set-sheet>

  <import-product-csv id="30"/>

  <save-job id="80"/>   

</phoenix-actions>

    1. Actions with id = 10 and 30 are mandatory. Make sure that your configuration contains these actions.

    2. Make note, if you add report generation into actions list, it format should be json.

  1. Run Phoenix server and check log for details:

Configure tBot

  1. Create new queue and add download action to it

  2. Configure tBot download action:

  1. Choose “tFlow” as data source (default value)

  2. Enter tFlow server url to field 1(Example: http://testtflow.com:8080/ - only root url required)

  3. Enter API key

  4. Enter Secret key

  5. Choose “Download folder” - local directory for downloaded files (You can write it by hand or press F2/ellipsis to open directory selection)

  6. Choose interval to check new files on server

  7. Choose retrieve interval and attempts count

  8. You can group files in “Download folder” by customer’s names or order number. This means that tBot will create special folder for customer’s name or order in “Download folder” and put related files to this directory.

  9. Choose file type to download. You can select:

  1. Production (default value)

  2. Proof file

  1. Click “Test Connection”. You should see message that connection settings are valid.

  1. Select “Phoenix imposition” from systems list.

  2. Configure integration parameters:

    1. Set Hotfolder path for generating xml-tickets

    2. Select “Wait for report” if you want to retrieve information from Phoenix

    3. Set folder for reports in json-format (Required only for retrieving results from report )

C:\Users\DrozdovVA\Desktop\3.png

  1. Save Queue

  2. tBot will wait for report for 7 days. If report not be generated – tBot will remove this job from list as unused.

Report should be generated in JSON format to its default location: “Out path” + “Job name” + job.json.

  1. Here is examples of files

    1. Sample xml ticket:

<?xml version="1.0" encoding="UTF-8"?>

<phoenix-resources version="1.0">

<create-job-resource idref="10"><id>1-1</id></create-job-resource>

<import-product-csv-resource id="30"><path>F:\Work\tBot\Phoenix\1-1.csv</path></import-product-csv-resource>

<save-job-resource idref="80"><path>1-1/job.phx</path></save-job-resource></phoenix-resources>

  1. Sample csv file with products:

Name,Description,Ordered,Stock,Grade,Artwork File,Notes

1-1,"first test order-1",1,,,"F:\Work\tBot\Phoenix\1-first test order-1.pdf",""

 

How to config Griffin integration

  1. Create new queue and add download action to it

  2. Configure tBot download action:

  1. Choose “tFlow” as data source (default value)

  2. Enter tFlow server url to field 1(Example: http://testtflow.com:8080/ - only root url required)

  3. Enter API key

  4. Enter Secret key

  5. Choose “Download folder” - local directory for downloaded files (You can write it by hand or press F2/ellipsis to open directory selection)

  6. Choose interval to check new files on server

  7. Choose retrieve interval and attempts count

  8. You can group files in “Download folder” by customer’s names or order number. This means that tBot will create special folder for customer’s name or order in “Download folder” and put related files to this directory.

  9. Choose file type to download. You can select:

  1. Production (default value)

  2. Proof file

  1. Click “Test Connection”. You should see message that connection settings are valid.

  1. Select “Griffin” from systems list.

  2. Set path for xml tickets

  3. Set default values for xml:

    1. Choose media type: Sheet or Role

    2. Set Width and Height for media size

    3. Set default values for Bleed and Spacing in mm

    4. Set Substrate value

C:\Users\DrozdovVA\Desktop\3.png

  1. Save queue.

  2. If you want to set dynamic values for default values you need to set additional properties for each job:

    1. Width (XML)  - Print Width(tFlow) - print_width (API)

    2. Height (XML)  - Print Height (tFlow) - print_height (API)

    3. Substrate (XML)  - Substrate (tFlow) - print_substrate (API)

    4. Bleed (XML)  - Artwork Bleed (tFlow) - artwork_bleed (API)

    5. Spacing (XML)  - Artwork Spacing (tFlow) - artwork_spacing (API)

  3. Sample xml file generated by tBot for a sheet media type:

<?xml version="1.0" encoding="utf-8"?>

<griffin-auto version="1.0" substrate="PVC" substrate-type="Sheet" substrate-width="1600mm" substrate-height="3200mm">

<artwork><quantity>1</quantity><bleed>5mm</bleed><spacing>3mm</spacing><front><path>F:\Work\_tmp\tBot\Phoenix\1-first test order-1.pdf</path></front></artwork></griffin-auto>

  1. Sample xml file generated by tBot for a roll media type:

<?xml version="1.0" encoding="utf-8"?>

<griffin-auto version="1.0" substrate="Polyester" substrate-type="Roll" substrate-width="1600mm">

<artwork><quantity>1</quantity><bleed>5mm</bleed><spacing>3mm</spacing><front><path>F:\Work\_tmp\tBot\Phoenix\1-first test order-1.pdf</path></front></artwork></griffin-auto>

How to config PrintFactory integration

 

Configure PrintFactory

  1. Configure Hotfolder in PrintFactory RIP:

    1. Set hotfolder name

    2. Set input path for xml-tickets

  1. Generate MIS Key to access cloud application:

    1. Go to http://app.printfactory.cloud/settings/external-api

    2. Generate Key

Configure tBot

  1. Create new queue and add download action to it

  2. Configure tBot download action:

  1. Choose “tFlow” as data source (default value)

  2. Enter tFlow server url to field 1(Example: http://testtflow.com:8080/ - only root url required)

  3. Enter API key

  4. Enter Secret key

  5. Choose “Download folder” - local directory for downloaded files (You can write it by hand or press F2/ellipsis to open directory selection)

  6. Choose interval to check new files on server

  7. Choose retrieve interval and attempts count

  8. You can group files in “Download folder” by customer’s names or order number. This means that tBot will create special folder for customer’s name or order in “Download folder” and put related files to this directory.

  9. Choose file type to download. You can select:

  1. Production (default value)

  2. Proof file

  1. Click “Test Connection”. You should see message that connection settings are valid.

  1. Select “PrintFactory” from systems list.

  2. Configure integration parameters:

    1. Set Hotfolder path for generating xml-tickets

    2. Set MIS Key from previous step

    3. Set Cloud server URL (default is  http://api.aurelon.com)

  1. Click “Load Devices” to check connection settings. You should see devices list in related combobox.

  2. Save Queue

  3.