Procedures
LANC PCI Fast Ethernet
PTOP Connectivity

PTOP Zone
Limitations & Workarounds
PS/2 Workflow
Whisper Workflow

PTOP Zone

Not all the folders under the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server Data Volumes are published on the LAN network. Only a special folder called Jobs is visible. The Jobs folder must be located directly under Data Volumes / StationName 1.0. (or any other volume, e.g., 1.1. or 1.2) and not in "deeper" subfolders. All the subfolders of the Jobs folder are published on the LAN network as well, if they have the correct extensions. For details, see Folder Naming Convention below.

• When PTOP is started in the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server, the PTOP Zone is automatically created on the station.

• The Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server supports PTOP server, but not the PTOP client. In other words, operations can be initiated from the Whisper and the PS/2, or from the Mac via SciNet applications, but not from the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server.

Folder Naming Convention

To work properly with PTOP, you must conform to certain naming conventions on the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server:

• All the job folders that are created on the PTOP Zone Jobs folder must have the extension ".j".
• All the page folders contained in these job folders must have the extension ".p" to be seen from PS/2 and Whisper.

If you don't add these extensions, you simply won't see the folder over the LAN network. The naming convention defined above should be used both with the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server-PS/2 connection over NFS and over PTOP, otherwise the transfer of FLYTs is corrupted.

Limitations & Workarounds

• APR from Whisper is not supported.
• APR from PS/2 is supported only via NFS, but not via PTOP. We do NOT suggest using this workflow since it requires that you mount the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server and the PS/2 in both directions. We recommend doing APR from the Server only (if there is one at the site).
• We do not recommend working with more than 3 or 4 clients connected to the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server via PTOP at the same time.
• FLYT files that result from RIP on the PS/2 (as opposed to being created from "Execute") are not translated properly on the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server.

Workaround: Either send the CT+LW without the FLYT to a Hot folder sensitive to CT+LW, or execute the FLYT before sending it.

• FLYT files that include LW only that are sent from the PS/2 over both NFS and PTOP, and from the Whisper as well, are not translated correctly on the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server.

Workaround: Send only the LW, without the FLYT, to a Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server Hot folder sensitive to CT+LW.

• If a Whisper or PS/2 FLYT is to be resent to a Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server Hot folder where there is already a copy of the translated job, the copy fails. (e.g., the original FLYT or CT or LW has to be remade; in this case it is recommended that you correct and resend the whole FLYT not only the CT or LW).

Workaround: See to it in advance that the translated jobs will not stay in the Hot folder by specifying in the "Translate" application, a File Destination outside the Hot folder.

• The "Include Subfolders" option of the Hot folders may not be used with the workflows described below.

PS/2 Workflow

It is important to remember that:

• If the files coming from the PS/2 were Ripped only, you can send the CT and LW files to the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server for translation and further processing without FLYT (this is valid for files resulting from a RIP that generates a FLYT, and also for files resulting from a RIP that does not generate a FLYT).
• If you build a page on the PS/2, or manipulate the CT or LW files on the PS/2 after RIP using the PS/2 Execute feature to update the FLYT, you must send the FLYT to the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server for translation along with the associated CT and LW files. (The reason is that, in this case, the offset of the CT relative to the LW is no longer (0,0) as in the case above, and the information contained in the FLYT is required to correctly position the page elements).

Copying Files

To copy files from the PS/2 to the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server and back via PTOP:

• If they don't already exist, create and define the necessary Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server Hot folders; these must include the Translate step in the related templates.
• The Hot folders must be sensitive either to FLYT or to CT-LW (located under the "page" category) according to the workflow you are going to use (the difference is explained above). They translate to Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server Job/Page.

See limitation concerning the File Destination in Limitations & Workarounds.

• Working from the PS/2, select a FLYT and copy it to a mounted Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server Hot folder that is sensitive to FLYT files. The result is a CreoScitex Job with a page that contains the associated CT and LW files.
• If you RIP without generating the FLYT, select the CT and LW files and copy them to a Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server Hot folder that is sensitive to CT-LW files, or copy them into a regular Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server folder and translate them later (using a Hot folder as well); the result is a CreoScitex Job with a page that contains the CT and LW files. When you work without FLYT, you cannot rename your CT and LW files since their relationship is based on the naming convention only.
• You can copy files in two directions, from the PS/2 to the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server, or from the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server to the PS/2.

In both cases, you have to initiate this operation from the PS/2.

Additional PS/2 Workflow notes

• File Naming Convention:
  A multi-page job is ripped on the PS/2 according to the following naming convention:

JOB:	example
Page elements:	example_6	LW
	example_6I	CT
	example_6F	FLYT

Here we took only one page as an example. This same page will appear on the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server according to a different naming convention.

After the translation:

Job Folder:	example.job
Page Folder:	example-P7.p
containing the files:	example-P7.ct
	example-P7.lw

It is very important to note that page number n on the PS/2 becomes page number n+1 on the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server after the translation.

If you only copy the files from the PS/2 to the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server without using any Translate Hot folder, the files will keep the same PS/2 names while the FLYT will receive the .exc extension on the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server:

PS/2	Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server
LW example_6	example_6.lw
CT example_6I	example_6I.ct
FLYT example_6F	example_6F.exc

• Multi-page jobs are now fully supported. You might send files related to the same job from the PS/2 to the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server at different times, and they will be automatically placed in the right job and page folders when they arrive at the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server.

This feature only works if you send the files to the same File Destination folder in the Translate! (even if the files arrive there from different Hot folders). Remember to copy FLYT and CT - LW files from the PS/2 to the page folder level (xxx.p folder) on the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server.

Whisper Workflow

The following Workflow conditions apply to the Whisper:

• You can transfer files between a Whisper and a Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server via LAN C (PTOP). There is no Whisper/Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server connectivity via NFS.
• Regarding the file naming conventions, the same rules that apply for the PS/2 described above apply for the Whisper as well.
• Whenever you copy pages from the Whisper to the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server, you must send the FLYT.

Moving Files

To move files from the Whisper to the Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server and back via PTOP:

1. If they don't already exist, create and define the necessary Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server Hot folders:

• Hot folder sensitive to CT+LW; translates to Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server Job/Page.
• Hot folder sensitive to FLYT;, translates to Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server Job/Page.
• Hot folder sensitive to Handshake Page; translates to Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server Job/Page.
2. From the Whisper, select a FLYT and copy it to a mounted Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server Hot folder that is sensitive to FLYT files. The result is a CreoScitex Job with a page that contains the associated CT and LW files.
3. HS Pages workflow; if you need to transfer a page in HS format, select the "copy and translate" option on the Whisper, you can translate your page (i.e., the FLYT, but not CT+LW alone) to a HS page, and send it to Brisque or CreoScitex Ripro Archiver or CreoScitex Ripro Server Hot folder sensitive to HS pages.