JTA2 In-Memory Cross-Compiler

Transcription

1 JTA2 In-Memory Cross-Compiler Meister is the only product for SAP that is capable of transmitting a complex payload with table of tables without limits of size and complexity. JTA2 is an in-memory cross-compiler for JSON and ABAP. It s used as a method of communication between SAP Gateway 2.0 and any SAP backend above ECC 6.0. It receives the request in JSON from the sender Then compiles the JSON into ABAP to be used by the SAP ABAP stack As the execution ends, Meister gets the SAP ABAP stack response Then it compiles into a JSON pack to be returned to the sender Since Meister hides all OData complexity within the compiler itself, the User Interface receives a comprehensive response using SSC, which already has all defined dependencies between the entities and/or entity sets in a single call.

2 Predictive Caching Meister uses PAC algorithm to generate libraries of data aggregation models based on each user s profile. In a production environment with Meister, 1461 discrete line items were requested. The number of line items precached by the Predictive Cache engine were identical to the number that would have been collected by the SAP standard aggregation engine. The reported time taken to retrieve these discrete line items when cached was microseconds vs. 1, microseconds with the standard SAP process. The cache is indexed only by the agent name and/or organization unit associated with this agent and retrieved at run time by queries over the cache run time table using the agent or organizational unit. Map any outside-in JSON payload to an SAP table or BAPI response without increasing cache run time. The content is created by a mapping tool that correlates the outsidein payload with the necessary fields inside SAP ERP, not by discrete columns. For increased automation, Meister allows non-intrusive consumption of any workflow via a basic handler that operates on indicators from the mapper tool.

3 Protocol and Byte Compression In production, our client had a JSON payload of 41,086,334 bytes that was compressed to 1,950,066 bytes, attaining 95% compression.` To compensate for the larger payloads enabled by Smart Single Call, Meister uses two techniques for compression and performance: Protocol and Byte Compression (PBC). Protocol compression is enforced by Meister which achieves compression factors of 40% on average. Using Outside-in processes, the payload is returned via GET and is bound by the capacity of the calling browser or web Rest library being used by the UI. Meister adds to the Protocol Compression a byte compression logic that further reduces the payload returned by an average of 80%. Using Inside-out processes, the payload is returned via POST and therefore is only bound by the memory at the UI layer. Superior performance utilizing Protocol Byte Compression is compatible with other compression engines.

4 Smart Robotic Process Automation Meister Smart Robotic Process Automation (SRPA) enables automation of workflows and their tasks non-invasively from within SAP. Cache, collect and compress. Meister uses predictive caching to bring data into run-time cache where it is linked, keeping formulas in place. This collection of data contrasts with how SAP stores data in discrete columns where formulas can not be applied. The larger payloads associated with these linked data components are compressed to improve operating efficiency. Meister then uses the sniffer to apply business rules to the linked data to add the intelligence to the automated workflow. Meister enables attaching different sets of business rules to the linked data creating truly Smart Robotic Process Automation. The business rules you apply can create fully automated workflows or include manual interventions where desired. The interventions defined in the business rules can specify exceptions, general monitoring, random sampling, or suggested transactions based on your specific needs and goals. For manual interventions, once all information is gathered and presented to the UI, all of the line items can be processed by clicking on a single button on a single screen. Meister s smart workflows are powered by merging Smart Single Call, Predictive Caching, and Smart Robotic Process Automation into any workflow.

5 Smart Single Call Meister is the only product for SAP that is capable of transmitting a complex payload with table of tables without limits of size or complexity. Meister Smart Single Call allows the removal of all chattiness from the requesting agent to the SAP back-end. It uses a single request and returns a single response as complex as it needs to be. With Meister Smart Single Call, the UX developer needs to focus on only two things: the request JSON needs to execute a given transaction and the JSON response expected. With Smart Single Call, the UX developer sends the payload containing the request and receives a payload containing the response, and is not aware the call executed on the SAP back-end or any other system. Additionally, the UX developer no longer needs to be trained in the business logic, which is required in the case when discrete and chatted calls are performed. Meister is agnostic of the UX with enablement of mobility that becomes a choice for the business units and not an IT dependency. Furthermore, being solely based on JSON as a language and Rest over HTTP(S) with OData as a protocol, Meister is enabled by birth to run using Federated Authentication via OAuth or regular SAML2/X509 certificates. As shown to the left, Meister s Smart Single Call allowed the transaction of the discrete tables in logical combination. This was done via a single JSON Document where the transition lines are encapsulated by JSON itself with no need for the UX to know how to navigate these indirections.

6 Reporting Engine Does this sound familiar? Pull an SAP report as an Excel document. Export it to Business Warehouse then using ETL import it to a dashboard that displays out-of-date data? With Meister, you avoid the extract and conversion processes associated with the intermediary step of a DW because your Database ETL report writer speaks JSON and Meister does the compilation back and forth between JSON and ABAP. This means your data is real time and not stale. Reports reflect what is in SAP now. When your data requirements change you still need to update the report in SAP, but you skip the ETL and BW conversion reprogramming that typically represents 2/3rds of your costs. Additionally, with Meister you can schedule and retrieve your reports outside of SAP meaning additional devices and formats are accessible to your users.