The agents send metadata to the CodeLogic Server, they are installed on the servers upon which the applications or databases are running. The applications and databases to be scanned are specified in the agent configuration files.
Agent ID
A unique GUID that identifies each registered agent.
API
(Application Programming Interface) A language and message format used by an application program to communicate with the operating system or some other control program such as a database management system (DBMS) or communications protocol. APIs are implemented by writing function calls in the program, which provide the linkage to the required subroutine for execution. Thus, an API implies that a driver or program module is available in the computer to perform the operation or that software must be linked into the existing program to perform the tasks.
Application
An application is a logical grouping of data analyzed from scans and varies based on the user's environment. Applications will display as top level items on the dependency map view.
Audit History
The audit history is a list of records organized by date. The records contain a list of changes for an item.
D
Dashboard
The CodeLogic Application Dashboard displays a high-level overview of your application.
E
Extension
An integration file for connecting CodeLogic to an IDE (Integrated Development Environment).
I
ID
Internal CodeLogic identification number used to reference the selected item.
IDE
A set of programming tools for writing applications, which include a source code editor, compiler and debugger. In an integrated development environment (IDE), all functions are activated from a common user interface and set of menus.
Impact Score
During a scan, CodeLogic collects information about your application to identify complex code and dependencies. We calculate a score based on this information to highlight parts of the code that may require refactoring or other remediation.
Item
Code and data assets identified during a scan. These include, but are not limited to, jars, classes, methods, tables, columns, etc.
M
Materialization
The process of creating a graph from the data collected during a scan. The graph is used to visualize the relationships between the artifacts and applications in the scan.
P
Plugin
An integration file for connecting CodeLogic to an IDE.
R
Relationships
The Relationships tab displays the number of inbound and outbound relationships for the selected Item. Selecting an Item in the Inbound or Outbound column will display the information for that Item.
S
Scan Space
A Scan Space is a structure which contains individual artifact scans. They are analogous to file system directories or folders.
Search
The CodeLogic Search is a user navigated hierarchical tree view of scanned items.
Search Nodes
Specialty graph nodes that are created when an artifact references an object outside the scope of the current artifact being scanned. This could be an endpoint, method, function, database column, etc. During the materialization process the CodeLogic server will utilize Search Nodes to make the appropriate connections to other applications, artifacts, and databases. Search Nodes that cannot be resolved are saved as Unresolved References in the resulting graph.
U
Unresolved Reference
An Unresolved Reference is a Search Node that could not be resolved during the materialization process. This could be due to a missing artifact, a missing database, or a missing endpoint.
W
Workspace
A Workspace is a user-defined collection of application scan data that is used to build visualizations and return report results. The data can be any combination of the applications you have configured in your CodeLogic Server.
Workspace Selector
The Workspace Selector displays the available workspaces for the user.