Customizing the path to the Service Interface Procedures

Owned by SebastianD (Unlicensed)
Last updated: Dec 06, 2019 by Janine Zwanzig

We are always eager to reduce the amount of customizations at the side of our customers that may require a change in our source code. One area where we have seen a demand for flexibility is the location of the service interface procedures (and include files). By default these files are located in the OERA\support folder which is still a legacy from the original OERA code base from Progress Software.

Customizing the Service Interface Path

Recently we have introduced the file Consultingwerk\products.i that allows us to use conditional compilation based on the installed development tools from Consultingwerk. We have added a preprocessor variable OERASI to this file that can be used to change the directory where the OERA Service Interface procedures (and include files) are expected:  

/* default path to OERA Service Interface */
&GLOBAL-DEFINE OERASI support

List of files using OERASI preprocessor

Consultingwerk\OERA\ServiceAdapter.cls
OERA\support\beEntity.i
OERA\support\daEntity.i
OERA\support\launchserviceinterface.i
OERA\support\locateprocedure.i
OERA\support\proSIfetchDataset.p
OERA\support\proSIretrieve.p
OERA\support\proSIretreive1.p
OERA\support\proSIsubmit.p
OERA\support\proSIvalidateEntityName.p
OERA\support\startsuper.i

Changing the setting in products.i will require to recompile the above files.