Prinergy System Admin Guides 11.0

Page tree

Space language

Before setting up Mac client computer file-sharing, you must understand which server and client computers are qualified, the file-sharing protocols that are supported, and the limitations of each protocol.
Carefully read this information and plan your setup so that, after you set up the file-sharing protocol, you don't have to convert protocols later.
If you decide not to use the recommended configuration, you must understand the functionality and limitations of the protocol that you use.

The recommended configuration is:

  • Prinergy 8.0 or later
  • SMB with Named Forks file-sharing protocol
  • Mac OS X 10.8, 10.9, 10.10 or 10.11 on all Mac client computers

If you need to convert file-sharing protocols:

  • You must perform additional steps to retain file resources because file resources are not converted.
  • Do not convert to a protocol with more limitations than the one you're currently using.

 

Mac client computers are recommended to use the SMB protocol. AFP protocols are not qualified with Prinergy, including ExtremeZ-IP.


Protocols for connecting Mac client computers in Prinergy

SMB

The Server Message Block protocol is built into the Windows operating system. SMB is also known as CIFS and Microsoft Windows network. On UNIX servers, SMB can be implemented with Samba software.

SMB handles file resources in the following ways:

      • With named forks, storing file resources in alternate data streams (ADS).
      • With AppleDouble, using the AppleDouble file format for foreign files.
        AppleDouble stores file resources in separate files with a ._ prefix. For example, a file named input.pdf has a corresponding AppleDouble file that is named ._input.pdf.

Important: AppleDouble was supported for versions of Mac OS X prior to 10.5. Prinergy no longer supports these older versions of Mac OS X and therefore we recommend SMB with named forks rather than AppleDouble.

AFP

Apple Filing Protocol, which is built into the Mac OS. AFP stores file resources in resource forks.

Note: AFP is not qualified with Prinergy Workflow 8.0.

 

Network File System (UNIX connectivity)

NFS connectivity is not supported (as of Prinergy 5.1). Use SMB protocol instead to provide UNIX connectivity. With this change, UNIX client computers will not be able to access files/shares hosted in the Prinergy servers. Files needed by a UNIX client computer must be pushed from the Prinergy primary server to a UNIX server that is configured with SMB/CIFS protocol (such as Samba).


Software to assist Mac client computer connections

Samba

Open-source file server software that you can install on a UNIX tertiary server to provide SMB connections for the Windows Prinergy primary and secondary servers.

 

Limitations of Mac client computer file-sharing protocols

Many Mac client computer protocols have significant limitations in a Prinergy system.


SMB with Named Forks (alternate data streams)

    • SMB with Named Forks (also called alternate data streams) is not supported in Mac OS X versions prior to 10.5.
    • Mac OS X 10.8, 10.9, 10.10 and 10.11 client workstations are supported with Prinergy 7.5 and later.

AFP

AFP is not qualified with Prinergy Workflow 8.0.

NFS

NFS is not qualified for use with Prinergy.



  • No labels