File Repository Servers

There is an Input and an Output File Repository Server in every Crystal Enterprise implementation. The Input File Repository Server manages all of the report objects and program objects that have been published to the system by administrators or end users (using the Crystal Publishing Wizard, the Crystal Management Console, the Crystal Import Wizard, or a Crystal designer component such as Crystal Reports). The Output File Repository Server manages all of the report instances generated by the Report Job Server and the program instances generated by the Program Job Server.

Tip:    If you use the Crystal Enterprise SDK, you can also publish reports from within your own code.

The File Repository Servers are responsible for listing files on the server, querying for the size of a file, querying for the size of the entire file repository, adding files to the repository, and removing files from the repository.

Note:    

• The Input and Output File Repository Servers cannot share the same directories. This is because one of the File Repository Servers could then delete files and directories belonging to the other.
• In larger deployments, there may be multiple Input and Output File Repository Servers, for redundancy. In this case, all Input File Repository Servers must share the same directory. Likewise, all Output File Repository Servers must share a directory.
• Objects with files associated with them, such as text files, Microsoft Word files, or PDFs, are stored on the File Repository Server.

Related topics

• Intelligence tier