<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aperio Backend Reference :: Aperio Documentation</title><link>/backend/index.html</link><description>Chapter 6 Aperio Backend Reference Aperio backend software is responsible for comunication betwen IBMi and XT dispatcher. It also provides various helpers for RPG developers. This reference describes installation and upgrade Aperio backend software. Explains details about configuration Aperio backend and best practice. There is also chapter about “Work With Metadata” and “Work With Control” programs. There is also detail documentation of all commands supported by Aperio backend software.</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 07 Aug 2020 12:47:07 +0200</lastBuildDate><atom:link href="/backend/index.xml" rel="self" type="application/rss+xml"/><item><title>Aperio Objects Naming Reference</title><link>/backend/aperio_naming/index.html</link><pubDate>Tue, 14 Jul 2020 15:01:31 +0200</pubDate><guid>/backend/aperio_naming/index.html</guid><description>This section describes naming rules for all objects and names used to build APerio framework.
Iptor API framework The API framework was built as separate product which can be installed as stand alone. There is no need to have DC1 installation. Following rules were used to name objects in Iptor API Framework:
IAF100AP - API framework production library</description></item><item><title>APIDOC - Aperio documentation tags</title><link>/backend/apidoc/index.html</link><pubDate>Fri, 07 Aug 2020 12:47:07 +0200</pubDate><guid>/backend/apidoc/index.html</guid><description>The Aperio reads RPG source code and tries to determine the interface to program. What are the input parameters, what is the output data etc… Most of the work is done automatically but sometimes it is needed to put some documentation tags to preciselly tell the framework how the program interface looks like. This chapter describes how Aperio reads RPG source.
Aperio tries to determine program interface mainly based on original source code. For example: respAddElement('data');tells Aperio framework that output JSON will contain “data” field. Command reqExist('params':'warehouse'); tells that program has input parameter warehouse. Similar for reqGetValue('params':'warehouse'); command. Based on commands (procedure calls) Aperio can only determine the names of input and output parameters. The second step of analysing source is the analyse of parameter and data names. Based on parameter name Aperio can look into DC1 fref files and retrieve more descriptive attributes like “length”, “label”, “scale”, “type”. Aperio uses parameter name and searches it inside fref files using alias field. In case field name do not exists in any fref alias programmer has two options.</description></item><item><title>UPGAPI - Upgrade API</title><link>/backend/upgapi/index.html</link><pubDate>Mon, 27 Jul 2020 11:27:59 +0200</pubDate><guid>/backend/upgapi/index.html</guid><description>Upgrade API data command automates upgrade API process. During the process API framework library is upgraded with objects extracted from the save file containing entire Aperio framework saved. The command also changes owner of all objects in framework library (by default to the owner already set for Framework library) and updates data in Metadata, Control, Configuration and Notification libraries (calling necessary conversion program(s)).
Following parameters are available for this command:</description></item><item><title>DSPAPIDTAV - Display API Data Versions</title><link>/backend/dspapidtav/index.html</link><pubDate>Mon, 13 Jul 2020 17:13:07 +0200</pubDate><guid>/backend/dspapidtav/index.html</guid><description>The Display API Data Versions (DSPAPIDTAV) command shows all API elements installed on entire IBMi. It shows actual location of elements together with their versions.
NOTE: There are no parameters for this command.
Aperio backend framework can be installed as several parallel instantions on IBMi. For example, there can be separate instantion of framework per each environment. Administrator may decide to keep metadata info in separate libraries. In this case the number if Aperio backend libraries can grow. To help administrator maintain Apeio backend installation, command DSPAPIDTAV was created. Administrator can see all elements of aperio installed on IBMi together with their version.</description></item><item><title>EXPAPIDTA - Export Api Data</title><link>/backend/expapidta/index.html</link><pubDate>Mon, 13 Jul 2020 17:13:07 +0200</pubDate><guid>/backend/expapidta/index.html</guid><description>The Export API data command exports API data into 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 exporting process etracts chossen elements of Aperio and puts them into destnation library or destination save file.</description></item><item><title>FIXAPIMTD - Fix Api Metadata</title><link>/backend/fixapimtd/index.html</link><pubDate>Mon, 13 Jul 2020 17:13:07 +0200</pubDate><guid>/backend/fixapimtd/index.html</guid><description>Ths command either prints or delete metadata methods if corresponding program does not exist. This is strict administrator commands to quick clean metadata with entries which no longer exists in IBMi. Administrator can decide to print list of methods which are “suspicious”. Then run this command once again with different parameter to delete them. Following parameters are available for this command:
Parameter Mandatory Description ACTION Y *PRINT Print only the method list for which the corresponding program does not exist. *DELETE Print and delete methods from metadata if the corresponding program does not exist.</description></item><item><title>IMPAPIDTA - Import Api Data</title><link>/backend/impapidta/index.html</link><pubDate>Mon, 13 Jul 2020 17:13:07 +0200</pubDate><guid>/backend/impapidta/index.html</guid><description>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.</description></item><item><title>INZAPIDTA - Initialize Api Data</title><link>/backend/inzapidta/index.html</link><pubDate>Mon, 13 Jul 2020 17:13:07 +0200</pubDate><guid>/backend/inzapidta/index.html</guid><description>The Initialize API data command pre-sets of all necesary API data in the destination library. 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. Following parameters are available for this command:</description></item><item><title>INZAPIF - Initialize Api Framework</title><link>/backend/inzapif/index.html</link><pubDate>Mon, 13 Jul 2020 17:13:07 +0200</pubDate><guid>/backend/inzapif/index.html</guid><description>The Initialize API framework command initializes metadata, control, configuration or notifications files. This command also initializes API framework. Creates necesarry stored procedures.
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. Following parameters are available for this command:</description></item><item><title>RBDAPIMTH - Requild Api Methods (all)</title><link>/backend/rbdapimth/index.html</link><pubDate>Mon, 13 Jul 2020 17:13:07 +0200</pubDate><guid>/backend/rbdapimth/index.html</guid><description>The Rebuild entire metadata command run process of retrieveal API interface for each method in metadata. This command do not require any parameters.
NOTE: The rebuild process may take several minutes! Since Aperio backend version 2.2.0.0 run this command is not necessary.</description></item><item><title>UPDAPIMTD - Update API method</title><link>/backend/updapimth/index.html</link><pubDate>Mon, 13 Jul 2020 17:13:07 +0200</pubDate><guid>/backend/updapimth/index.html</guid><description>The Update API Method (UPDAPIMTH) command allows you add or update method into API metadata. This command retrieves also program interface from source file and update method level attributes.
Following parameters are available for this command:
Parameter Mandatory Description PGM Y API method RPG program. METHOD Y Method name. SUBSET Y Method subset. See subsets description Subsets Subset Sequence Description *CUSTLOCAL 1 Customer dev, single sites *CUSTCORP 2 Customer dev, multiple sites *IBSLOCAL 3 Iptor dev, signle site (Reserved for Iptor development) *IBSCORP 4 Iptor dev, multiple sites (Reserved for Iptor development) *COUNDELTA 5 Country dev, delta release (Reserved for Iptor development) *COUNTRY 6 Country dev, base release (Reserved for Iptor development) *INTDEV 7 International development (Reserved for Iptor development) *STDDELTA 8 Iptor standard, delta release (Reserved for Iptor development) *STANDARD 9 Iptor standard, base release (Reserved for Iptor development) *APIBASE 99 Base API level (Reserved only for internal Aperio API methods)</description></item><item><title>WRKAPICFG (DSPAPICFG) - Work with API Configuration</title><link>/backend/wrkapicfg/index.html</link><pubDate>Mon, 13 Jul 2020 17:13:07 +0200</pubDate><guid>/backend/wrkapicfg/index.html</guid><description>The Work with API Configuration (WRKAPICFG) command allows you to work with various API framework configuration files.
NOTE: There are no parameters for this command.
NOTE: The (DSPAPICFG) Display API Configuration command shows the same data as WRKAPICFG command but only with ability to display data. No possobility to maintain data.
Following general congiguration groups are available:
Confoguration group Description Exit points This group allows You co configure exit points. See exit points configuration Exit points Aperio has several exit points. They can be used to inject own code inside process of aperio.</description></item><item><title>WRKAPICTL (DSPAPICTL) - Work with API Control</title><link>/backend/wrkapictl/index.html</link><pubDate>Mon, 13 Jul 2020 17:13:07 +0200</pubDate><guid>/backend/wrkapictl/index.html</guid><description>The Work with API Control (DSPAPICTL) allows You to maintain API control information. In API control panel You can see basic authority se up in Aperio. The security is defined by attributes. Attributes can be defined either on general or method level.
NOTE: There are no parameters for this command.
NOTE: The (DSPAPICTL) Display API Control command shows the same data as WRKAPICTL command but only with ability to display data. No possobility to maintain data.</description></item><item><title>WRKAPIMTH (DSPAPIMTH) - Work With API Methods</title><link>/backend/wrkapimth/index.html</link><pubDate>Mon, 13 Jul 2020 17:13:07 +0200</pubDate><guid>/backend/wrkapimth/index.html</guid><description>The Work With API Mathods (WRKPAPIMTH) command is used to maintani API metadata. In API matadata panel You can describe API program interface. Attributes can be defined either on general or method level.
NOTE: The (DSPAPIMTH) Display API Methods command shows the same data as WRKAPIMTH command but only with ability to display data. No possobility to maintain data.
NOTE: There is one parameter to this command: Subset selection (SUBSET). Following values are suported:</description></item></channel></rss>