...
To have a consistent “save point/backup” of a set of dependent models, it may be useful to handle more models in one EDMbinaryPackage
EDMbinaryPackage API
Note: Exporting/importing a BinaryPackage from an SSP requires the BinaryPackage to be located in the “EDM_SERVER_CLIENTS_FILES_PATH” directory.
Using emiRemoteExport/ImportBinaryPackage, the BinaryPackage may be located in the caller clients directory or in the EDM_SERVER_CLIENTS_FILES_PATH” directory
When the importing EDMserver system have direct access to the location of the BinaryPackage, renameFile will be used instead of copyFile. An option KEEP_BINARY_PACKAGE may be implemented in case such BinaryPackage should be used by other systems or kept for any other reasons
Functions:
- edmiExportBinaryPackage, edmiRemoteExportBinaryPackage
- edmiImportBinaryPackage, edmiRemoteImportBinaryPackage
Q & A
I'm currently testing from SSP (so via edmi). Later on may be XPX wrappers will be useful as well.
Some questions about logic/parameters:
...
- “.BPDESCR” BinaryPackage description
- “.I” and “.D” files, one of each
- Optionally: “.BII”, “.BID”, “.FB” files (one of each) when the model have been updated in write transactions
0 to n number of “.F” files.
- Optionally: “.BII”, “.BID”, “.FB” files (one of each) when the model have been updated in write transactions
- The “.I” ,“.D” , “.BII”, “.BID”, “.FB” files will always be copied in an update operation
- Only “.F” files updated later than corresponding “.F” file in the target model will be copied in an UPDATE operation.
- To keep track of the updates, the BinaryPackage description file may be used to make a “update history” in the target system.
EDMbinaryPackage API
Note: Exporting/importing a BinaryPackage from an SSP requires the BinaryPackage to be located in the “EDM_SERVER_CLIENTS_FILES_PATH” directory.
Using emiRemoteExport/ImportBinaryPackage, the BinaryPackage may be located in the caller clients directory or in the EDM_SERVER_CLIENTS_FILES_PATH” directory
When the importing EDMserver system have direct access to the location of the BinaryPackage, renameFile will be used instead of copyFile. An option KEEP_BINARY_PACKAGE may be implemented in case such BinaryPackage should be used by other systems or kept for any other reasons
...
language | cpp |
---|---|
title | sdai.h |
...
- .
...