System ID Mapping Between Client and Server
Some document types are defined and then referenced only by System ID (in other words, by an absolute path). This complicates using Serveur Arbortext PE for publishing operations, because the document type is likely to be installed in a different location on the server than on the client.
To get around this problem, you can add a catalog file to a document type directory on the Serveur Arbortext PE that contains SYSTEM declarations for these document types. Each SYSTEM declaration should map an absolute path to the document type on a client to the absolute path to the document type on the Serveur Arbortext PE.
You'll want to follow the practice of reducing the number of mappings needed if you're using the Serveur Arbortext PE. Installing document types in the same location on every client machine will help minimize the total number of SYSTEM mappings you need to define.
Est-ce que cela a été utile ?