In Automation Engine 14.0, Imaging Engine Powered by Adobe® does not include any CIP3 functionality. However, users migrating from NexusRIP can continue to use Nexus to generate CIP3 files even after migrating to Imaging Engine Powered by Adobe®.
Configure Automation Engine to connect to the Nexus server
In Automation Engine, set up your Nexus details in the Configure dialog.
From the Tools menu, select Configure and then add a new Nexus server. If Nexus is running, after adding the host address, you can test the connection to verify that the address is correct.
Set up a workflow in Nexus
In Nexus, create a new workflow that includes a CIP3 activity and sends the result to Automation Engine. This can be based on a standard "Basic RIP" workflow as shown or a PDF RIP workflow. You might find it easier to copy an existing workflow that includes a CIP3 activity, so that you can be sure the new one uses the same CIP3 parameters.
Make sure that the workflow has a hot folder.
If your Nexus installation is on a Mac, the hot folder should be on a Windows file server. There are permissions related problems if the hot folder is on the Mac server which prevent the Send to Nexus task working.
Set up an Automation Engine workflow
In Automation Engine, set up a workflow that RIPs the PDF using Imaging Engine Powered by Adobe® and makes a low-res raster that is converted back to PDF and sent to the Nexus workflow.
The tasks should be set up as follows:
The Image to Screened Separations task RIPs at full output resolution (e.g. 2400 dpi)
The Image to Contone Separations task creates low res 72 dpi TIFF output.
The Send to Nexus task should be configured to send to the Nexus workflow that was set up earlier.
When a PDF file is submitted to this workflow, high res output is made as normal. Low res TIFFs are then converted back to a PDF file which is then sent to the Nexus workflow. The Nexus CIP3 output is kept and the intermediate low res PDF is deleted.