OFML Data Setup
First install EAIWS, EAILS and DataClient using Windows Installation or Linux Installation, including the platform prerequisites and PMV enable script. Then follow the steps on this page: prepare the pCon.login account, server license and refresh token before configuring DataClient authentication, installing data and connecting the installed catalogs to EAIWS.
Link DataClient to pCon.login
DataClient requires a pCon.login account for licensing and for downloading updates. Use an account intended for server operation rather than an individual employee’s account. Ensure that it has a pCon.update DataClient for Server license.
Generate a refresh token in pCon.login account access. Use this token in the update script below. Treat it as a credential and restrict access to the script containing it.
DataClient does not automatically revoke tokens because they may still be used elsewhere. Before explicitly revoking one, check whether saved favorites or other installations still use it; token-revocation commands do not check this for you.
If migrating from DataClient license files, contact EasternGraphics support to obtain the server license for your pCon.login organization.
Choose the data source
DataClient supports two sources:
- pCon.update Server: download and install data using your account’s available updates.
- Local directory: install update packages that you have already transferred to the server.
Keep the directory containing local update packages separate from the installed data. The examples use these paths. On Windows, replace <installPath> with the destination configured in the installer’s config.xml. The data and package directories are suggested locations; if you choose other locations, use those same paths in the update script and session configuration.
| Purpose | Windows | Linux |
|---|---|---|
| Installed data from pCon.update Server | <installPath>\pCon\_data\pCon.update |
/opt/pCon/_data/pCon.update |
| Local update packages | <installPath>\pCon\_data\manual\pCon.update_packages |
/opt/pCon/_data/manual/pCon.update_packages |
| Installed data from local packages | <installPath>\pCon\_data\manual |
/opt/pCon/_data/manual |
For local installation, create the package directory and copy your update packages into it. You can use further subdirectories, for example by date, if you also adapt the script’s source path.
Configure and run the update script
Download the script for your platform, extract it and edit the settings before running it. Match settings by their names rather than line numbers. Use one update source per run.
Windows
Download the Windows update script. Add the PCON_ROOT definition before the script’s path settings and replace YOUR_INSTALL_PATH with the configured installPath, without a trailing backslash. This variable belongs to the batch script and is not set automatically by the installer. Configure the paths and token:
set "PCON_ROOT=YOUR_INSTALL_PATH\pCon"
set "DCCexe=%PCON_ROOT%\DC\pCon.update\DataClient\bin\dcc.exe"
set "EAIWSDir=%PCON_ROOT%\EAIWS\"
set "TOKEN=YOUR_REFRESH_TOKEN"
set "DATAPATH=%PCON_ROOT%\_data\pCon.update\"
For updates from pCon.update Server, enable the script’s internet-source command and disable its local-source command:
"%DCCexe%" set-update-source --internet
For local packages, set POOLDIR and the destination DATAPATH, then enable the local-source command and disable the internet-source command:
set "POOLDIR=%PCON_ROOT%\_data\manual\pCon.update_packages"
set "DATAPATH=%PCON_ROOT%\_data\manual\"
"%DCCexe%" set-update-source --local --local-path "%POOLDIR%"
Adapt the startup-file refresh command to the filename configured in Connect the data to EAIWS. For example, if using session.cfg, replace the script’s startup.cfg reference with session.cfg:
copy /B "%EAIWSDir%etc\startup\session.cfg" +,,
Use quotes around executable and directory paths in the script’s other commands as well, particularly if installPath contains spaces. Run the edited batch script from Command Prompt and check its output for errors.
Linux
Download the Linux update script. Set the path to dcc:
DCC=/opt/pCon/DC/pCon.update/DataClient/bin/dcc
For pCon.update Server, enable the script’s internet-update call with your token and data destination:
perform_update_internet 'YOUR_REFRESH_TOKEN' '/opt/pCon/_data/pCon.update'
For local packages, enable the local-update call instead, passing the token, package directory and data destination:
perform_update_local 'YOUR_REFRESH_TOKEN' '/opt/pCon/_data/manual/pCon.update_packages' '/opt/pCon/_data/manual'
Adapt the startup-file refresh command to your EAIWS directory:
touch -h /opt/pCon/EAIWS/etc/startup/*.cfg
Run the edited dcc_update.sh script as eaiws, with access to the package and data directories, and check its output for errors.
Connect the data to EAIWS
After the first successful data installation, create a session start-up file in the EAIWS etc/startup directory. Use session.cfg for the default session configuration. For multiple configurations, use separate filenames and select the required one when opening a session.
The recommended setup uses the catalog registration file installed with the data. The following examples use the pCon.update Server data destination from above.
Windows session.cfg
Create <installPath>\pCon\EAIWS\etc\startup\session.cfg. In the following properties, replace YOUR_DATA_PATH with the actual data destination configured by DATAPATH in the update script, using forward slashes and omitting the trailing slash. For the suggested internet-update location, this is the configured installPath followed by /pCon/_data/pCon.update. The .cfg file does not automatically expand the batch script’s %PCON_ROOT% or %DATAPATH% variables.
app.gf.data.profile=default
app.basket.currencies=currencies
app.framework.locale=en_US
app.gf.data.profile.path=YOUR_DATA_PATH/catalogs/profiles
app.gf.data.profile.registration=YOUR_DATA_PATH/catalogs/default.profiles
Forward slashes in the Windows configuration example avoid backslash escape sequences in property values.
Linux session.cfg
Create /opt/pCon/EAIWS/etc/startup/session.cfg:
app.gf.data.profile=default
app.basket.currencies=currencies
app.framework.locale=en_US
app.gf.data.profile.path=/opt/pCon/_data/pCon.update/catalogs/profiles
app.gf.data.profile.registration=/opt/pCon/_data/pCon.update/catalogs/default.profiles
Adapt the locale and paths. For data installed from local packages, use the actual local data destination from the update script: on Linux, for example /opt/pCon/_data/manual; on Windows, use the chosen DATAPATH value with forward slashes in place of YOUR_DATA_PATH. Ensure that the referenced registration file and profile directory exist and are readable by the EAIWS service account.
Select a single catalog profile
As an alternative to the registration file, specify an installed catalog profile by its filename without the extension:
app.basket.currencies=currencies
app.framework.locale=en_US
app.gf.data.profile=egr_ANY
app.gf.data.profile.path=/opt/pCon/_data/pCon.update/catalogs/profiles
Replace egr_ANY with an actual installed profile name and adapt the path for your platform. In this alternative, omit app.gf.data.profile.registration and define app.gf.data.profile only once.
Open sessions with the configured data
openSession uses session.cfg by default. For a custom file such as startup.cfg, pass the -startup option with the base name startup, without the directory or .cfg extension.
New or changed start-up files apply to newly opened sessions. Existing sessions continue using their previous configuration. Keep the script’s startup-file refresh step so that data updates also refresh the relevant configuration’s modification time.
See Session Start-Up File Options for further settings. Continue with Verify the Installation.