[bgsystem]

Integration with Nexus

Why run Nexus workflows from the Automation Engine Pilot?
You can use all the power of Nexus workflows from within a Automation Engine Job. This allows you to bring both Automation Engine and Nexus workflows in line, running them from within a single controlling environment: the Automation Engine Pilot.

How does it work?
The Send to Nexus ticket gives you access to the workflows that are available on a specific Nexus server.

Any public parameters that have been defined in the Nexus workflow (NeXML) will show up on the Send to Nexus ticket in Automation Engine. In addition, these public parameters are SmartName-enabled, so you can use Job metadata to drive the Nexus workflows.

On the Nexus side the Copy to BackStage activity allows you to set up workflows that send their resulting files back to Automation Engine.

Behind the scenes, Automation Engine and Nexus communicate via the SOAP protocol, exchanging files and notifying each of other of their progress.

NeXML
Setting up public parameters in Nexus requires knowledge of NeXML. Please refer to the NeXML Manual for more information.

[bgsystem]

Interfacing to Nexus
TW_TTask:providing template ...
TW_TTask:providing smartnames (ticket-related) ...
TW_TTask:providing smartnames (jobparameters-related) ...
TW_TTask:providing smartnames (job-related) ...
Folder for outputs:\NexusOut\94713
Submitting towards
nexus://ae:5182/RIP@TifOutput2400?QueueID=/fripfile_s.file_sModel1.grx/TifOutput2400
parsing SubmitJob-response from http://ae:5182/soap/AlephServer
SubmitJobAnswer
200
——————————————————————————————
<SOAP-ENV:Body xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<m:SubmitJobResponse xmlns:m="http://www.artwork-systems.com/soap/AlephServer">
<Answer xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xsi:type="SOAP-ENC:Dictionary">
<MessageType xsi:type="xsd:string">SubmitJobAnswer</MessageType>
<Error xsi:type="xsd:int">200</Error>
</Answer>
</m:SubmitJobResponse>
</SOAP-ENV:Body>
——————————————————————————————

[slick]

It's a pain in the ass...
Nowadays you can have AEIE running on a single Win Server machine.

Who needs AE running on one machine, Nexus Server on another machine and Nexus client in yet another that furthermore has to be a mac?

With 3 machines you can have (1 x AE) + (3 x IE), as long as you have available cores on your AE server it's an hell of a config...

cheers
-s

[itubay]

nexus://ae:5182似乎就是一个网络协议，是Web服务吗？跟Shuttle有啥关系？

[bgsystem]

Esko Nexus Brochure Show for U

[slick]

作者: bgsystem

Esko Nexus Brochure Show for U

if i were you i'd grab the rest of the s**t from Agfa's site and post it here too.
Maybe one manual per post, huh?

https://www.agfagraphics.com/global/...-software.html

there's some other interesting 'vintage' s**t down there, like Backstage and Odystar!
Run! Post it fast, before someone beats you to it!

...spammer!

you're just spamming to earn coins to grab the latest esko software at CPC, and most probably to use it to do real work... shame on you...

cheers
-s