What type of API did Application Delivery Intelligence expose?

ADI exposed a REST API for accessing and manipulating testing data. Specific endpoint patterns included `/projects`, `/tests`, and `/results`. These endpoints supported standard HTTP methods such as GET, POST, PUT, and DELETE.

What programming languages were supported for integration?

ADI supported integration with Java and other languages through its API. Client libraries and SDKs were available for simplifying API interactions.

What protocols did Application Delivery Intelligence use for communication?

ADI communicated using HTTP/HTTPS for API requests and responses. It also supported protocols like JMS for asynchronous messaging and data synchronization.

How did Application Delivery Intelligence reduce testing costs?

ADI helped organizations reduce testing costs by optimizing testing efforts and identifying defects earlier in the development lifecycle. This resulted in fewer defects in production and lower remediation costs.

How did Application Delivery Intelligence improve application quality?

By providing insights into code quality and test coverage, ADI helped improve the overall quality of applications. This resulted in more reliable and stable software releases.

How did Application Delivery Intelligence improve stakeholder visibility?

ADI provided stakeholders with visibility into the testing process, allowing them to track progress and make informed decisions about release readiness. This improved communication and collaboration between development, testing, and business teams.

What authentication methods were supported?

ADI supported authentication methods such as LDAP, SAML 2.0, and X.509 certificates. These methods allowed organizations to integrate ADI with their existing identity management systems.

What access control model was used?

ADI used a role-based access control (RBAC) model to manage user permissions. This allowed administrators to assign specific roles to users, granting them access to certain features and data.

What encryption was used and where?

ADI used encryption to protect sensitive data both in transit and at rest. This included encrypting data stored in the database and using HTTPS for communication between components.

What audit/logging capabilities existed?

ADI provided audit logging capabilities to track user activity and system events. This allowed administrators to monitor security events and investigate potential security breaches.

What administrative interfaces were available?

ADI provided a web-based administrative interface for managing users, configuring system settings, and monitoring system performance. This interface allowed administrators to easily manage the ADI environment.

What monitoring/logging capabilities existed?

ADI provided monitoring and logging capabilities to track system health and identify potential issues. This included monitoring CPU usage, memory usage, and disk space, as well as logging system events and errors.

What databases or storage mechanisms were used?

ADI stored its data in a relational database such as Db2. Regular database backups were recommended to ensure data recoverability in the event of a system failure.

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Application Delivery Intelligence

Name: Application Delivery Intelligence
Availability: InStock

IBM Not Supported z/OS

Tools and Utilities Testing

Vendor

IBM

Product Overview

Application Delivery Intelligence (ADI) featured a three-tier architecture comprising a presentation layer (web-based UI), an application layer (analysis engine), and a data layer (relational database). The application layer exposed a REST API for integration, with endpoints such as `/projects`, `/tests`, and `/results`. Communication between components occurred via HTTP/HTTPS and JMS.

509 certificates, using a role-based access control (RBAC) model. The data repository typically utilized a relational database such as Db2. Key components included the data repository, analysis engine, reporting module, and administrative interface.

ADI has been merged into IBM Application Discovery and Delivery Intelligence (ADDI). Organizations should plan a migration to ADDI, focusing on data migration and API compatibility. Alternatives include Micro Focus Enterprise Suite and CAST Application Intelligence Platform, but these may require significant architectural adjustments.

Frequently Asked Questions

What type of testing data did Application Delivery Intelligence manage?

Application Delivery Intelligence (ADI) provided a centralized repository for managing testing data, including code coverage, quality metrics, complexity analysis, and performance data. This allowed teams to track testing progress and identify areas for improvement.

How did Application Delivery Intelligence help improve testing strategies?

ADI used the collected testing data to provide recommendations for improving testing strategies. This included identifying gaps in test coverage, suggesting new test cases, and prioritizing testing efforts based on risk and impact.

How did Application Delivery Intelligence integrate with other tools?

ADI integrated with various testing tools and development environments through its API. This allowed for automated data collection and seamless integration into existing development workflows.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

Share Your Product Experience

Application Delivery Intelligence

Product Overview

Frequently Asked Questions

What type of testing data did Application Delivery Intelligence manage?

How did Application Delivery Intelligence help improve testing strategies?

How did Application Delivery Intelligence integrate with other tools?

What type of API did Application Delivery Intelligence expose?

What programming languages were supported for integration?

What protocols did Application Delivery Intelligence use for communication?

How did Application Delivery Intelligence reduce testing costs?

How did Application Delivery Intelligence improve application quality?

How did Application Delivery Intelligence improve stakeholder visibility?

What authentication methods were supported?

What access control model was used?

What encryption was used and where?

What audit/logging capabilities existed?

What administrative interfaces were available?

What monitoring/logging capabilities existed?

What databases or storage mechanisms were used?

Related Products

More from IBM

Access 1

ACF/NCP

ACF/SSP

ACO SolutionPac

Ada/370

ADF II

Similar Products

_beta access admin

_beta access audit

_beta access easy

_beta doc|z plus

_beta doc|z transform

(E)JES

Help Improve This Directory

Are You a Vendor? Claim Your Listing