Description: Information about the Administration folder is shown in this area. The GUIDs of the child folders are shown here.

Information: Custom installations, such as for projects with ELO Business Solutions, can differ from the structures described here. If required, references to the various child folders in the administration folder should also refer to additional information sources.

Information: You may require the GUIDs to perform automatic tasks and to control the folders using scripts.

License overview: Use this menu item to display an overview of the licenses.

Users in system. Display an overview of the logged on users.

Server information: Switch to the Server information area.

Repository statistics: Display a repository overview in the Repository statistics area.

License report: Show an overview of the licenses in the License report area.

Child folders

Various program and system settings and special user documents are stored in the child folders of the administration folder. The child folders and their functions are explained below.

Information: The folders in the repository depend on the modules installed and the available licenses. For this reason, it is possible that certain folders will not exist in the repository and that other folders, which are not described here, will exist as a result of project-specific settings.

\ELO Background Images

• COLD background images for viewing COLD documents in MMF format.

\Business Solutions

ELO Business Solutions are modular solutions which are offered as packages including the whole configuration and all scripts.

• ELO Business Solutions modules. A module can include scripts for the ELO Indexserver, the ELO Java Client, ELO Automation Services, and the ELO Web Client.

Information: To give you a better overview, parts of the administration folder within a module are reproduced on filing.

Example: A module contains the folder "Indexserver Scripting Base". The folder contains all the scripts for the Indexserver module. When the module is installed, these scripts are referenced to the "¶Administration¶Index Server Scripting Base" administration folder.

\Business Solutions\development

• You can create a setup package with the help of the "Development" package. This makes it easier to transfer the configuration for contract management to another system, for example.

\Business Solutions Custom

• Contains custom configurations for Business Solutions modules. Business Partners can store configurations for custom adaptations in this folder. Custom modules usually map the same configuration structure as the associated base modules. ELO Business Solutions migrates modifications to the custom modules to the base modules when reading the configuration files. This ensures you can keep the solutions up-to-date.

\Default Indexes

• The Default Indexes folder contains all available default indexes (function: Save as default index).

\Dropzone

• Global: All global tiles are stored in this folder. These tiles are available for all users. The administrator can create multiple child folders and assign permissions in ELO so that different user groups can see them.
• Store: The tile definitions for the tile collection are saved to this folder (ELO Java Client only). The area folders are added below the Store folder. As in the Global folder, the administrator can define here which tile collections are visible to which user groups.
• User.<User-ID>: The personal tile definitions of each user are saved to this folder. In addition, the configuration is saved in the extra text of the user folder.

ELOapps

• Designated module: ELOwf
• This is where the database and the configuration for the ELOwf are stored (ELO apps).
• Apps: This folder contains archived and installed ELO apps. These are created using the App Manager or can be installed when repositories are imported.
• ClientInfos: This folder contains data objects (ClientInfo objects) that describe when a website is to be displayed in the client. These are created using the App Manager.
• Configuration: The global configuration (in the extra text) is stored in this folder. It contains configuration files (JSON format), which can be read out for individual apps.
• Icons: This folder contains ICO image files. Depending on the naming convention, these are available in the apps or can be read as a tile image in the ELO Web Client.
• Modules: This folder contains archived and installed ELO modules. The ELO modules are created using the App Manager or can be installed when repositories are imported.
• Additional information: You can access the ELO Apps API Documentation (Guides section) via the ELOwf status page.

\ELOas Base

• ELO Automation Services scripts.

\ELO Textreader

• The ELO Textreader creates a reference for documents that cannot be converted in the ELO error folder "Administration¶ELO Textreader¶Documents not converted". Once the cause of the error has been eliminated, the administrator can add the documents in this folder to the full text database.

\ELOwf Base

• This folder is used for storing the database and the configuration for the ELOwf (forms and feed).
• Classes: The CSS style files for displaying forms are stored in the extra text of the Classes folder. Users should also file their own CSS files to the Classes folder. These files are available in the form editor.
• Configuration: The extra text of the Configuration folder contains configuration data (folder paths, main language, etc.) for the ELOwf. The Configuration folder also contains the document frame that serves as a framework for forms.
• Feed\Script Locales: Information on localizing the feed for automatic script posts. You need to transfer files to this folder manually via one of the clients.
• Forms: The Forms folder contains all form templates.
• Images: You need to file image documents that are used in files in the Images folder. References are allowed.
• Preview: [from 10.01] The folder is used for previewing forms. This folder must be empty and should not be modified.
• Webapp: You can store additional script and HTML documents for forms in the Webapp folder. These are files that can be embedded in forms. You need to transfer files to this folder manually via one of the clients.

\ELOxc Base

• This folder contains the configuration settings for ELOxc.

\Fulltext Configuration

• This folder is used for the thesaurus.

\HTML Templates

• Templates for showing the keywording (HTML format)

\Java Client Scripting Base

• registryRemoteControl: Office macros for the ELO Java Client.
• Additional Java Client scripts can be stored here.

\IndexServer Scripting Base

• _ALL: File file Indexserver scripts that are to be executed by all available ELO Indexservers to the _ALL folder.
• <Server 1>: Indexserver scripts that should only be executed by a specific server can be filed to the folder bearing the name of the respective server.
• <Server n>: Additional Indexserver scripts for the respective ELO Indexserver.
• Synchronize Search Indexer: Configuration of Elasticsearch.

\Localization

• custom: Localization of scripts
• system: Localization (e.g. of form elements) using properties files.

\Replication Base

• Starting point for replication assuming that this has been defined in the replication settings. Other settings are possible. You can find further information in the ELO Replication manual.

Users\<Group>\<User>

• Default Indexes: Default index defined by the user. Default index that are available to all users are stored in the "Default Indexes" folder (see above).
• Private Folder: Personal documents are filed here.
• Inbox: Alternative to Intray. Unlike the Intray, the documents are added to the full text database, are version-controlled, and archived.

\Webclient Scripting Base

• The ELO Web Client is the module responsible for this folder.
• Scripts and associated files for the ELO Web Client are located in this folder. It is the filing location for scripts that are read and executed by the ELO Web Client when the program is started.

Information: The Business Partner or customer needs to transfer files to this folder manually via one of the clients.

You can find additional information on ELO Web Client scripts in the ELO Windows Client manual.

\Workflow Icons

• Icons used in the workflow