(Glue-2108) Glue Components
- SNP
Glue Cockpit
Transaction
/DVD/GLUE
To launch the Glue Cockpit, use the transaction code /DVD/GLUE. Glue Cockpit provides overall information about the usage of GLUE. This includes the number of objects created on Hadoop, active delta monitoring as well as an overview of jobs with arrow buttons that open request monitor with corresponding jobs (running, finished, etc.). The object overview shows the number of existing Glue tables and extractors. Active delta shows the stream and batch, where the stream means the number of watched objects in watchdog which have a check period set to seconds. Batch means the number of scheduled jobs plus watched objects in watchdog which have a check period set to any other than seconds. Jobs overview shows the number of running, failed, finished, and scheduled jobs in the last 24 hours. From the Glue Cockpit, it is easy to navigate to all the main components of GLUE.
Glue Cockpit
Key components of Datavard Glue
Data Dictionary: a tool similar to ABAP Dictionary with SE11-style, designed for managing Glue data providers and Glue data targets
Data Browser: a browser providing data overview for Glue data objects
Extractor Workbench: a workbench for data transfer between SAP and Hadoop
InfoProvider Management: a tool used to create virtual InfoProviders for integrating with existing SAP data flows
Script Editor: a simple editor for creating various native Hadoop operations (e.g. Pig scripts, ETL, etc.)
Object Navigator: a tool providing central navigation between all Glue components
Storage Management: manages connection settings and communication with the Hadoop cluster
Transport Management: interfaces with the STMS and handles the object transportation through the SAP landscape
Glue Transaction Codes
You can use custom Glue transactions to access specific Glue features.
To get the complete list of Glue transactions, see the chapter below:
Glue Metaobjects
Most of the Glue functionalities require expert settings. They are very complex and their execution requires detailed information in order to work properly. For this reason, it would be difficult for a regular user to use these operations. To solve this, we have created Glue metaobjects that represent a subset of logical requirements for a specific family of tasks.
Metaobjects design process
Because of the mentioned complexity of Glue features, we have created an internal hierarchy of Features→operations →processes. Operations are actions that are carried out by users in order to execute this functionality. Processes are procedures, function calls, algorithms, and basically all kinds of technical actions serving the operations. We have collected these processes and found the intersection of their use within our operations and technical processes. The conclusion was a better understanding of what is required for every feature. We created an ideal UI which will lead the user towards the understanding and successful use of any Glue feature.