Folder and File Preparation

Folder and File Preparation on Aurea CRM Server.

Directory Structure - Example

<GlobalPatchDirectory>\8.1.770.60227_bb_release_20130624.zip
<GlobalPatchDirectory>\Config_1001.gz
<GlobalPatchDirectory>\global.ps1
<GlobalPatchDirectory>\my_global_patch.exe
<GlobalPatchDirectory>\images\new_image.png
<GlobalPatchDirectory>\styles\custom.theme\constants.css
<CommunicationPath>\<offlineStationNumber>\out\20130714.0
<CommunicationPath>\<offlineStationNumber>\patches\my_special_patch.exe
<CommunicationPath>\<offlineStationNumber>\patches\special.ps1

Prepare the following directories and files on the server to be used by the Aurea CRM web offline setup and the initialization process:

  • Create the folder structure as specified by the < CommunicationPath > and < GlobalPatchDirectory > tags in the Offline.xml, see Offline.xml.
  • Create initial data stock downloads for the offline clients, see Defining Users as "Offline Users". The communication files are output to < CommunicationPath > \{ offlineStationNumber }\out.

    You can compress large communication files using gzip (*. gz ).

  • If you want to deploy custom Offline.xml and settings.xml files, you need to copy them to < GlobalPatchDirectory >\system\settings.

    If you only use the settings that are provided by the SilentClient.ini file, the Offline.xml and settings.xml files are automatically created/updated during setup.

  • If your SU and WWW users have passwords, you need copy the users.xml file to < GlobalPatchDirectory >\system\settings as well.
  • If needed (e.g. to deploy custom scripts, images etc. used by Aurea CRM web), copy additional files (uncompressed or *.zip) to the appropriate directories:
    • global files -> < GlobalPatchDirectory >
    • client-specific files -> < CommunicationPath >\{ offlineStationNumber }\patches

    Inside these directories you need to use the same directory structure as your (future) Aurea CRM web offline installation, i.e. to deploy custom images, copy them to < GlobalPatchDirectory >\images.

Note: When creating *.zip files make sure that all files are compressed using the DEFLATE algorithm. CRM.launcher can not handle files compressed with DEFLATE64.
Note: Windows automatically uses DEFLATE64 when zipping files larger than 2000 MB (uncompressed size).