This is step 12 of performing a full installation of Enterprise Server 9. (See a list of all steps)
Purpose of this step
By modifying the file storage settings you control the way the data is stored, including the following aspects:
- File name conventions
- Files stored externally or locally
In Enterprise Server, files are stored in a file system, including on an external drive in situations where disk space is at a premium.
This article describes the way in which files are stored, how to set up external storage and how to manage the process of locally storing files by client applications.
When a file is stored in the File Store, the file name that is used is taken from one of two methods, each using its own convention:
- For files directly belonging to an object:
File name example: 329-native.v0.1
- For files belonging to pages of a layout object:
<object ID>-page<number>-[1|2|3][optional -portrait|-landscape][-<edition>]. v<major>.<minor>
File name example: 231-page-1-2-landscape-8-v0.4
The following definitions are used in both conventions:
|Data (filled-in at runtime)
|Choice: a or b
|Optional: a or nothing
|Alternate layout page in portrait orientation
|Alternate layout page in landscape orientation
|Major version number
|Minor version number
The major version number is increased whenever the object is saved in a status that has the Create Permanent Version option selected (see Workflow Status settings.)
When the object is saved for statuses that don’t have this option enabled, the minor version number is increased instead.
Permanent versions (such as v1.0, v2.0, v3.0, etc), are never automatically removed. The oldest minor versions are automatically removed when the object outgrows the configured number of versions to track.
For more information about versioning, see Saving file versions with Enterprise Server.
For each object type you can have more than one file saved:
- Layouts, articles, images, and pages have several renditions stored which include the native file, thumbnail files, and preview files.
- Layouts, articles, and images have versions stored. The number of versions is configurable per object type (see Saving file versions with Enterprise Server).
For layout objects, all pages reside in the binary .indd file. However, for each of its pages a thumbnail and preview is stored as well. Optionally, an output rendition is stored too, in either PDF or EPS format.
Example: Assume you have enabled the following features (see Page preview generation):
When saving an InDesign document consisting of 2 pages to a status that has the Output flag enabled, page files are saved in the FileStore as shown below (in the example, the file has been given object id “57”).
* The Rendition Type is referring to the WDSL definition. Note that both EPS and PDF formats are stored as “output” rendition type. Having both output formats enabled is NOT supported.
In order to ensure optimum performance when many files are stored, sub folders are automatically created by the system.
For instance, if you are about to store more than 100 objects in one folder, the system creates a sub folder named “1”. Files between 100 and 200 are stored inside that folder. The folder creation is done recursively, so if you store the 1000th file in the File Store, a sub folder named “10” is created inside the “10” folder.
With the exception of the parent “File Store” folder, which you must create manually, Enterprise will create all required sub folders automatically . The newly created sub folders carry the same access attributes as their parent root folder.
Make sure that the root folder exists and that the access rights are correctly configured. The Web Server user needs the following access rights set:
- Mac OS: “www”
- Windows: “IUSR_<servername>”
- Linux: “nobody”.
Configuring the number of files stored
The following option controls the number of objects stored within one folder :
- File: configserver.php file
- Name of option: ATTACHMODULO
- Possible values: any numerical value
- Default setting: 100
define ('ATTACHMODULO', 100);
External storage disks can be used for storing files on a different disk than where the Enterprise database is installed. Enterprise allows you to use external drives for the File Store as well as for high-resolution adverts.
In addition, files can be stored on a remote or integrated third-party content source, such as a wire feed of a news agency.
For an example of using a File Store on a system outside the system on which Enterprise Server is installed,see the Knowledge Base article Configuring an external Windows file store for Mac OS using Apache .
Note: Although this is a specific example involving a Mac OS X system with an Apache HTTP Server set up to use a File Store residing on a Windows 2000 machine, the same principle can be applied when using other systems.
When high-resolution adverts are used in a Brand, you are likely to want to keep them in the Enterprise workflow system. Nevertheless, in most cases there is no real need to actually import the (potentially large) files into the File Store. Enterprise Server therefore allows you to configure an external drive.
This is controlled by the following option:
- File: configserver.php file
- Area: SERVERFEATURES
- Name of option: HighResStoreMac or HighResStoreWin
- Possible values: the path to your external drive
new Feature( 'HighResStoreMac', 'Volumes/HighResFileStore/' ),
Note: For more detailed information about these settings, see Configuring storage for high-resolution adverts in Enterprise Server 9.
Enterprise can be integrated with 3rd-party content sources such as Wire feeds of news agencies. The connection is made through a Content Source plug-in which is managed through the Server Plug-Ins Maintenance page. See Enterprise Server Plug-ins.
The default behavior of the Smart Connection plug-ins for InDesign and InCopy is to always store native files (InDesign and InCopy documents) to the local hard disk without sending them to the server. This is done to reduce network traffic and speed up intermediate save operations.
Enterprise Server can be configured in such a way that the file is always saved directly to the database instead of locally. For more information, see Always save a layout or article to Enterprise using Smart Connection.
Step 13. Reviewing security settings