The Import API data command imports API data from library or save file. Aperio backend consist following elements:
| Element | Description |
|---|---|
| Framework | Consist set of programs, commands and objects required to process communication to dispatcher. It contains also set of tools for RPG programmer. |
| Config | Consists set of files witch store configuration of framework. For example definition of exit programs. |
| Metadata | Consists set of files and objects required to save program interface (API metadata). Keeps also statistics or requrests. |
| Control | Consists set of files which store security infirmation about metadata. |
| Notifications | Not used. Consists set of files which are used to keep notifications messages, subscribed servers and all data required to send notification to the browser. |
The importing process load chosen elements to the destination library. During importing process data are upgraded to destination version of aperio.
Following parameters are available for this command:
| Parameter | Mandatory | Description |
|---|---|---|
| DATA_TYPE | Y | Selection of Aperio elements to be imported. See data types for details |
| DEVICE | Y | Specifies the device used for the import operation. *LIB Save exported data into library, *SAVF Save exported data into save file. |
| SAVFF | N | Specifies source savefile which contains objects to be imported. |
| LIB_FROM | N | Specifies source library which contains the objects to be imported. |
| LIB_TO | Y | Specifies destination library where imported objects are copied to. |
| LIB_API | Y | Specifies API framework library where all necessary objects to complete the import process reside. This is version reference library. By pointing it You can decide what version of API element should be created in destination library. |
| MODE | Y | Specifies whether imported data will replace entire existing data or only imported records will be replaced. For example: Someone exported only three methods from metadata to the savefile. During import he can use mode *UPDATE to replace only these three methods in destination metadata. The all aother methods will remain untouched. If he will choose *REPLACE mode then all methods wil be deleted in destination library anl only these three will be loaded to metadata. |
NOTE: There are special set of methods defined for subset *APIBASE (Sequence 99). These methods are always refreshed diring import process, regardless of MODE parameter.
Following data types can be chossedn to import:
| DATA_TYPE | Description |
|---|---|
| *IMPMETA | Import metadata element only. |
| *IMPCTL | Import control element only. |
| *IMPCFG | Import configuration element only. |
| *IMPNOT | Import notification element only. |
| *IMPALL | Import all above Aperio elements. |