Material catalogs provide information about vignettes, materials, and supporting data, such as ICC profiles, to the server.
Each material catalog consists of a required catalog attribute file and a set of optional catalog data files:
Catalog data files are associated with material catalogs by file references in the catalog attribute file. The same catalog data file can be shared by multiple material catalogs.
Catalog attribute files must have an
.ini file suffix and must be in the Image Rendering catalog folder ( PlatformServer::ir.catalogRootPath). Catalog data files can be in the same folder or any other folder accessible to the Render Server.
Updating material catalogs
The server continuously monitors the catalog folder. It automatically reloads a material catalog – including associated catalog data files – when it detects that the main catalog attribute file has been changed. Thus, to update material catalogs on the server, first replace all catalog data files that need to be changed, and then replace (or “touch”) the catalog attributes file to trigger the catalog reload.
The default catalog provides default values for all catalog attributes for all material catalogs. If a particular attribute cannot be found in a specific material catalog, the server uses the corresponding value from the default catalog instead. Similarly, the default catalog can be used to provide defaults for specific catalog data records (materials and ICC profiles). If a particular data record cannot be found in a specific material catalog, the server attempts to find it in the default catalog instead. This allows material catalogs to be sparsely populated and simplifies management of global attributes and data, such as shared templates, macros, and fonts.
In addition, the default catalog provides all attributes and data records (ICC profiles) when no specific material catalog is involved in an operation.
For correct functioning of the Render Server, the catalog attributes file for the default catalog must be named default.ini. It must also always exist in the catalog folder, and must be fully populated with all required attributes, excluding
attribute::RootId and the references to the various catalog data files, which are all optional.