Maximising Your Investment The traditional tips & tricks session MAXIMISING YOUR INVESTMENT © 2015 DALIM SOFTWARE GmbH Master the file monitoring process MAXIMISING YOUR INVESTMENT © 2015 DALIM SOFTWARE GmbH Agenda Master the file monitoring process Discover ES metadata ingestion Adjust ES to win the race Same same, but different - TWIST and eTWIST Track what we do for you Group and customise emails Master the file monitoring process How it is working ES File Server A File Server B Master the file monitoring process How it is working ES dalimws Server A Server B http(s) File Server A dalimws file input plugin http(s) File Server B dalimws file input plugin Master the file monitoring process Plugin file input Local Fast: subscription to OS events Never loose the track Master the file monitoring process Discover ES metadata ingestion MAXIMISING YOUR INVESTMENT © 2015 DALIM SOFTWARE GmbH Using metadata inside ES Types of metadata Embedded metadata (like IPTC; XMP) ES metadata (Metadata sets) Import of metadata PreviewGeneration extracts embedded metadata Manipulating of metadata Procedures in document workflows Custom JobTicket Layouts Export metadata ES metadata ES metadata managed in Metadata sets are stored in database ES can be displayed and manipulated with Job Ticket Layouts Export Downloaded files does not contain metadata Ingest metadata with ES TWIST or InputMetaData tool ES TWIST and BT_InsertMetadata Create a ES TWIST workflow Use the BT_InsertMetadata tool Configure the Tool Provide the PPD Variables to import metadata Create an ES workflow Provide metadata to the ES TWIST workflow Be aware of it Very complex to provide the necessary metadata Maintenance if new metadata should be ingested InsertMetaDataTool Create an ES workflow All you need is the InsertMetaData tool Create a User action Create a user action that trigger the workflow The result ETwist with BT_InsertMetaData All meta data that the ES TWIST workflow do allow InsertMetaData tool All assigned meta data Additional tipp What does it mean: Ingest all meta data all IPTC information changed in ES all assigned Metadata including custom Metadata sets managed by Custom Job Tickets You can transport general instructions as meta data Extracted metadata are created if not exits Adjust ES to win the race MAXIMISING YOUR INVESTMENT © 2015 DALIM SOFTWARE GmbH Adjust ES to win the race What is ES Tomcat server Database Adjust ES to win the race Tomcat engine configuration /symlnks/common/tomcat7.0/bin/env.sh Memory allocated Options Debug Adjust ES to win the race Tomcat link to PostgreSQL /symlnks/common/tomcat7.0/conf/context.xml Connection with the database Options of the connection Adjust ES to win the race PostgreSQL maintenance Maintenance crontab entry Backup and vacuum every day Re-index every 3/6/12 months Adjust ES to win the race PostgreSQL engine configuration /symlnks/var/es/database/name/postgresql.conf Memory allocated Options (connection with tomcat) Log Same same, but different TWIST and eTWIST MAXIMISING YOUR INVESTMENT © 2015 DALIM SOFTWARE GmbH Components Function ETWIST TWIST Editor Java Web Start Java Web Start and native App Gate ES_Web dedicated java program Repository Tomcat plugin within ES_Engine dedicated java program Server Tomcat plugin Scheduling SQL database Loadbalancing Tomcat plugin + SQL DB C++ based wflserver program C++ based wflserver program C++ based wflserver program Log ES database + wflserver.log wflserver.log Tools in the Editor What’s in Common Source code for file interpretation Basic tools are strictly identical Param files, PPD, fonts are shared Workflows fully compatible up to some details When to use ES_Connect You are willing to work file oriented ! Submitting files Through a simple hot folder structure with dynamic hot folder With cups/samba printer queue Includes samba hotfolder export Load balancing Limit the servers running a workflow Forking processes inside workflow can be load balanced Merging processes Merging files is easier When to use ES_Connect Workitem support Workitems can be managed through WEBLINK Stop workflow in a validate to use LITHO and check/edit files Tracking TWIST Editor tracks and manages all processes in your cluster No history available after process log deletion Processing control available through WEBLINK User management One user database in the repository A separate user database for WEBLINK When to use ETWIST You are willing to work Job oriented ! Submitting files ES hotfolder device can be installed on separate machines JDF Devices can be split between DMZ and internal network Tasks scheduling Done at ES level, better dispatching all along workflow steps Can restart a step at every moment Alwan and GMG piloting and overview in project view Workflow backup management The ES export function gets you all necessary ETWIST workflows When to use ES-TWIST Interaction with ES Easy transfer of variables to ETWIST Need to return easily variables to ES ES Working stages can send several files to one workflow User Action may require ETWIST to get several files into one single process Imposition management ChannelMapping for Imposition forms must be done by ETWIST When to use ES-TWIST Workitem support Workitems can be managed through the project view Tracking ES keeps the logs for the full life of the documents in ES User management All is stored in the ES-DB no more WEBLINK + TWIST CONFIGURATOR needed Limitations of ES_Connect Loadbalancing ES does not know if TWIST is working on “non-ES” files ES does not know the load of TWIST Connectivity ES does not know the list of TWIST workflows Setting up PPD parameters more complex Sending variables back to ES not possible without XMP inserted into the resulting file Limitations of ETWIST Hotfolder ES-TWIST workflows do not have hotfolder No CUPS printer queue to print files to a workflow Tracking ES-TWIST does not keep the process log in its process view Process log window is experimental List of processes should only be tracked through ES You are obliged to store the files into ES to track their log ES - TWIST Communication 6 steps for a document to reach the wflserver : ES Project ES Workflow ES_Connect Step WebService TWIST TWIST Gate TWIST Server ES - TWIST Communication ES Project JMF within ES_Engine ES Workflow ES_Connect Step WebService TWIST TWIST Gate TWIST Server ES - TWIST Communication ES Project ES Workflow JMF within ES_Engine ES_Connect Step WebService TWIST TWIST Gate TWIST Server ES - TWIST Communication ES Project ES Workflow ES_Connect Step JMF between ES_Engine and TWIST Plugin WebService of a Tomcat running dalimws WebService TWIST TWIST Gate TWIST Server ES - TWIST Communication ES Project ES Workflow ES_Connect Step WebService TWIST Tomcat TWIST API connection to gateport 6042 like WEBLINK TWIST Gate TWIST Server ES - TWIST Communication ES Project ES Workflow ES_Connect Step WebService TWIST TWIST Gate TWIST Server Internal TWIST communication over port 6011 ES - ETWIST Communication ES Project ES Workflow ETWIST Step WebService ETWISTServer ETWIST Server Less components involved = quicker and more stable ES - ETWIST Communication ES Project JMF within ES_Engine ES Workflow ETWIST Step WebService ETWISTServer ETWIST Server ES - ETWIST Communication ES Project ES Workflow JMF within ES_Engine ETWIST Step WebService ETWISTServer ETWIST Server ES - ETWIST Communication ES Project ES Workflow ETWIST Step JMF between ES_Engine and ETWIST Plugin WebService of a Tomcat running ETWIST WebService ETWISTServer ETWIST Server ES - ETWIST Communication ES Project ES Workflow ETWIST Step WebService ETWISTServer Internal ETWIST communication within Tomcat ETWIST Server Huge XML can be returned to ES <?xml version="1.0" encoding="UTF-8"?> <JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" xmlns:Dalim="http://www.dalim.com/JDF/Extensions" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" ID="D292545-2731275-6057734" JobID="292545" JobPartID="2731275-6057734" QueueEntryID="ESPRiTJDFQueue_Dalimes_116_12331_JDF" SpawnID="" Status="Completed" Type="Dalim:Section_Booklet_Impo" Types="" Version="1.3" xsi:type="Dalim:ESPRiTTwistBase"> <ResourcePool> <RunList ID="D8638761-0-0" PartIDKeys="RunSet Run"> <RunList Status="Available"> <LayoutElement> …………. …………. …………. …………. …………. …………. …………. <Dalim:_VAR_DALiM_WorkFlow_Variables_DALiM_Variable_jdfOut_type Run="etwist,146205" Status="Available" Value="hires"/> <Dalim:_VAR_DALiM_WorkFlow_Variables_DALiM_Variable_jdfOut_type Run="etwist,146202" Status="Available" Value="hires"/> <Dalim:_VAR_DALiM_WorkFlow_Variables_DALiM_Variable_jdfOut_type Run="etwist,146203" Status="Available" Value="hires"/> <Dalim:_VAR_DALiM_WorkFlow_Variables_DALiM_Variable_jdfOut_type Run="etwist,146200" Status="Available" Value="hires"/> <Dalim:_VAR_DALiM_WorkFlow_Variables_DALiM_Variable_jdfOut_type Run="etwist,146201" Status="Available" Value="hires"/> </Dalim:_VAR_DALiM_WorkFlow_Variables_DALiM_Variable_jdfOut_type> <Device Class="Parameter" DeviceID="WS_Dalimren1-1053091577_ETwistServerPlugin_Section_Booklet_Impo" ID="Dal1426148451023" Status="Available"/> </ResourcePool> <ResourceLinkPool> <RunListLink Usage="Input" rRef="D8638761-0-0"/> <ApprovalSuccessLink Usage="Output" rRef="D8638770-0-0"/> <Dalim:ETwist_LogLink Usage="Output" rRef="D8638773-0-0"/> <Dalim:DALiM_WorkFlow_VariablesLink Usage="Input" rRef="D8638776-0-0"/> <RunListLink Usage="Output" rRef="D8638779-0-0"/> <Dalim:_VAR_DALiM_WorkFlow_Variables_DALiM_Variable_jdfOut_pstatusLink Usage="Output" rRef="D916869469"/> <Dalim:_VAR_DALiM_WorkFlow_Variables_DALiM_Variable_jdfOut_ignorefileLink Usage="Output" rRef="D1629998258"/> <Dalim:_VAR_DALiM_WorkFlow_Variables_DALiM_Variable_jdfOut_typeLink Usage="Output" rRef="D2079321074"/> <DeviceLink Usage="Input" rRef="Dal1426148451023"/> </ResourceLinkPool> <AuditPool> <PhaseTime AgentName="Dalim Generic device" AgentVersion="1.0" Author="WS_Dalimren1-1053091577" End="2015-03-12T09:20:51+01:00" Start="2015-03-12T09:16:41+01:00" Status="InProgress" TimeStamp="2015-03-12T09:16:41.159+01:00"/> <ProcessRun AgentName="Dalim Generic device" AgentVersion="1.0" Author="etwist/Section_Booklet_Impo" Duration="0:4:10" End="2015-03-12T09:20:51+01:00" EndStatus="Completed" Start="2015-03-12T09:16:41+01:00" TimeStamp="2015-03-12T09:20:51.194+01:00"/> </AuditPool> 7.8MB of log for a 72 pages booklet Conclusion ETWIST can technically run on same box as TWIST ETWIST can only be a slave of ES TWIST is a standalone product or/and a slave of ES Variables exchange between TWIST and ES is limited ETWIST mandatory for imposition management ETWIST mandatory for User Actions ETWIST hardworker cost = TWIST hardworker cost Migration of hard worker from TWIST to ETWIST allowed Track what we do for you MAXIMISING YOUR INVESTMENT © 2015 DALIM SOFTWARE GmbH Track what we do for you [email protected] Track what we do for you [email protected] Track what we do for you [email protected] and helpdesk.dalim.com Track what we do for you [email protected] and helpdesk.dalim.com Track what we do for you [email protected] and helpdesk.dalim.com Track what we do for you [email protected] and helpdesk.dalim.com Track what we do for you partner.dalim.com Group and customise emails MAXIMISING YOUR INVESTMENT © 2015 DALIM SOFTWARE GmbH How to notify your users Possibilities of sending e-mails Output channels Notifications How to notify your users Output Channel Create new email output channels (NEVER Change the defaults) Place a DigitalDelivery to an email output channel when ever you want to send a email Create different output channels with different emails to send your messages How to notify your users Output Channel What about translation (according user language)? What about deadlines and reminder? What about grouping? How to notify your users Notifications Users subscribe to event notifications Users decide if events are grouped to less messages E-mails caused by predefined and milestone events How to notify your users One Event more than one email layout! Global setup of notification (assigned to all organisations and customers) Every organisation could use his own template setup Every customer could use his own template setup Maintain the notification system Step by step Create e-mail templates (NEVER Change the defaults) Configure the notification templates global Adjust the notification templates per organisation (optionally) Adjust the notification templates per customer (optionally) Always create an english translation The english translation is the fallback The last setting wins The customer setup is overriding the organisational setup and this one overrides the global settings. Mixes between customising and inheritance are possible Thank you! http://www.dalim.com MAXIMISING YOUR INVESTMENT © 2015 DALIM SOFTWARE GmbH
© Copyright 2024