Here is a list of Integration related acronyms that you may come across when working with GLU.Ware.
- ACK stands for “Acknowledgment” and is a signal used to indicate that a packet of data has been received successfully and can be used to confirm the receipt of a transmission. See the converse of ACK which is NACK
- An ACL (Access Control List) is a list of permissions that define who or what is allowed to access specific resources within a system, such as files, directories, or network services. It is used to enforce security policies and prevent unauthorized access.
- AML (Anti-Money Laundering) refers to a set of laws, regulations, and procedures aimed at preventing money laundering, which is the process of disguising illegal proceeds as legitimate funds. AML systems monitor financial transactions for suspicious activity and help identify and prevent money laundering.
- An API (Application Programming Interface) is a set of rules and protocols for building software applications that allows for communication between different systems. APIs allow different systems to exchange data and information, enabling integration and automation of processes.
- Amazon Web Services
- Business Intelligence
- Command Line Interface
- Data Encryption Standard
- A DMZ (Demilitarized Zone) is a network security concept where a small, secure network segment is placed between a secure internal network and an insecure external network (e.g. the internet). The DMZ acts as a buffer zone, allowing for secure communication between the internal and external networks while isolating and protecting sensitive internal systems from external threats.
- Domain Name System
- File Transfer Protocol is a standard network protocol used for transferring files between computers over the Internet or a local network.
- High Availability
- Hyper Text Transport Protocol
- Hyper Text Transport Protocol Secure
- Internet Protocol
- Internet Protocol Security
- iPaaS (Integration Platform as a Service) is a cloud-based platform that provides tools and infrastructure for connecting and integrating applications, data, and processes across multiple systems. iPaaS enables organisations to easily integrate their systems without the need for complex and costly on-premise integration solutions.
- A .JAR (Java ARchive) is a package file format typically used to aggregate many Java class files and associated metadata and resources (text, images, etc.) into one file for distribution.
- Local Area Network
- Mobile Network Operator
- Mobile Station International Subscriber Directory Number – this is simply a technical term for a mobile phone number.
- NACK stands for “Negative Acknowledgment”. In computer networking, NACK is a signal used to indicate that a packet of data has not been received or has been received with errors and needs to be retransmitted. See the converse of NACK being ACK,
- OWASP (Open Web Application Security Project) is a non-profit organization dedicated to improving web application security. It provides guidelines, tools, and resources for developers and security professionals to help prevent and mitigate common web application security threats, such as SQL injection, cross-site scripting, and other security vulnerabilities.
- Payment Application – Data Security Standard
- Payment Card Industry – Data Security Standard
- A POC (Proof of Concept) is a demonstration of the feasibility and potential value of a system integration project. GLU will often use a POC exercise to demonstrate how GLU.Ware will meet a potential customer’s requirements and solve their business problems. POCs are often used in the early stages of the GLU sales process to help secure customer buy-in and can help to de-risk a project before full implementation.
- Relational Database Service
- REST (Representational State Transfer) is an architectural style for building web services that allow for the exchange of information between systems. REST uses standard HTTP methods, such as GET, POST, PUT, and DELETE, and uses a URL to identify resources and actions. REST is a popular choice for system integration due to its simplicity, scalability, and compatibility with a wide range of programming languages and platforms.
- Security Assertion Markup Language
- SSH File Transfer Protocol
- System Integration Test – typically a stage in the SDLC when all Test End Points are available and the full Test cycle covering all Test Cases can be tested.
- Simple Mail Transfer Protocol
- SOAP (Simple Object Access Protocol) is a messaging protocol used for exchanging structured data in the implementation of web services. It defines a set of rules for encoding messages in a format that can be transmitted over a network, allowing systems to communicate and exchange information in a standardized way.
- Secure Shell
- Secure Socket Layer – in system integration, SSL is used to encrypt sensitive information during transmission, protecting it from eavesdropping and tampering. SSL has been replaced by its successor, TLS (Transport Layer Security), which provides equivalent security and is widely used to secure web communications and other networked applications.
- SSO (Single Sign-On) is a security mechanism that allows users to access multiple systems using a single set of credentials. In system integration, SSO can simplify the user experience and improve security by eliminating the need for multiple usernames and passwords, reducing the risk of forgotten or weak passwords, and centralising the management of user accounts. SSO can be achieved through various methods, such as federation, smart card authentication, or shared session cookies.
- Transmission Control Protocol
- Transport Layer Security
- Transactions per second
- TPS (Transactions Per Second) is a measure of the number of transactions processed by a system in a given second. It is a commonly used metric for evaluating the performance and capacity of a system, particularly in the context of database systems, payment systems, and other systems that process a large number of transactions.
- TTL (Time-to-Live) is a value used in computer networking to limit the lifespan of data in a network. It helps prevent data from circulating indefinitely by setting a maximum number of hops that a data packet can traverse before being discarded. This is important in system integration to ensure the reliability and efficiency of data transmission in a network.
- A VM (Virtual Machine) is an abstraction layer that enables multiple operating systems to run on a single physical machine. In DevOps, VMs are commonly used to create isolated, reproducible environments for software development, testing, and deployment, allowing teams to develop, test, and deploy applications without affecting each other’s work. VMs also provide scalability, flexibility, and ease of management, enabling teams to quickly spin up new environments, scale resources on demand, and automate the deployment and configuration of infrastructure.
- Virtual Private Network
- A .WAR file (Web Application Resource or Web application ARchive) is a file used to distribute a collection of JAR-files, JavaServer Pages, Java Servlets, Java classes, XML files, tag libraries, static web pages (HTML and related files) and other resources that together constitute a web application.
- XML (eXtensible Markup Language) is a markup language used for encoding structured data for storage and exchange between systems. It provides a flexible and human-readable way of representing data that can be processed by computers, enabling systems to exchange information in a standardized way.
- XSS (Cross-Site Scripting) is a type of web security vulnerability that allows attackers to inject malicious code into a website, compromising the security of users who visit the site. In system integration, XSS can occur when data from one system is integrated into another system without proper input validation or sanitization, allowing an attacker to inject malicious scripts into the integrated data. XSS attacks can steal sensitive information, such as cookies or login credentials, or perform malicious actions, such as injecting malware or redirecting users to phishing sites.
application.ymlfile is a configuration file used in the GLU.Engine to define settings and parameters for the application. It typically contains information such as database connections, environment-specific configuration, and settings for components and routes that have been configured into the GLU.Engine. The file is written in YAML format, which is a human-readable, data-serialization format. The settings in the
application.ymlfile provide the necessary information for it to run correctly.