Skip to main content
Version: 4.2.5

Directory structure

note

Directories in italics are examples only. The names of the system directories correspond with the system IDs.

note

Additional application config files are stored in %LOCALAPPDATA%. Each application has its own sub-directory (for example, iCore_Solutions_AB) containing its application user.config files.

Directories under Program files

Use environment variable %PROGRAMFILES(X86)% to access Program files folder.

iCore
BinDirectory for iCore binary files, such as .exe-files, dll-files, .hlp-files etc. For example, this is where you can find the Build Component tool.
Branding
ComDirectory for iCore binary files, such as .dll:s, service etc.
ConfigConfiguration directory containing Enterprise Information System adapters.
Adapters
Langdef
Stylesheet
Workflows
XML Schemas
PowerShell Examples
PSModuleContains PowerShell modules.
SysTemplateSystem templates for creating a new system.
Web service templatesContains iCore web service templates used to install web services iCoreInvoke and iCoreAPI.
DataContains data directories called Edi, In-house, Node and Scan.
DocMain directory for system documentation. This directory contains documentation, for example, of the Developer module and the Administration Tool.
ScriptImportsSample scripts delivered with the iCore product, for example EDIFACT etc.
TempDirectory for temporary files.
UtilitiesUtilities that are not automatically installed, but can be set up when required, for example Port Monitor.
iCore AdministratorThis folder is only available if you have installed the Administrator .msi.
VersionThe version number of the installed version (for example 4.1.4.0).
PSModulesDirectory for PowerShell modules.
SasProxyContains files used when installing the SAS proxy.
TemplateContains web service template used to install the Administrator site.

Directories under ProgramData

Use environment variable %PROGRAMDATA% to access Program files folder.

iCore Solutions
iCPS
LocalConfigConfiguration for system(s).
<systemid>System-specific configuration file.
SystemsThe iCore systems created on this machine.
<systemid>Example of an iCore system directory with
subdirectories containing existing data types and scripts.
DataUsed for storage of files associated with a Node. The format of the files stored in Node may vary,
depending on the current type of processing performed.
There must be one Node directory per iCore Runtime Environment System.
NodeContains all Node files for the system.

Directories under AppData

Use environment variable %APPDATA% to access Program files folder.

iCore Solutions
iCPS
SystemsThe iCore systems created on this machine.
<systemid>
ScriptsContains user defined scripts and ready-made system scripts. There is one Scripts directory per iCore system.
ApplicationContains dlls and source directories (for temporary use).