IOS-158 practice question 3 of 10

Both IMS and IMS via ION API connection point types can replace which one of the following connection point types for more secure access to Infor applications in the cloud?

Full set: 41 questions
Answer options
A: IO Box connection points
B: Technology connection points Correct answer
C: File connection points
D: Database connection points
Correct Answer:
B. Technology connection points
Explanation

The IMS (Infor Messaging Service) and IMS via ION API connection points are modern, secure methods for application integration within the Infor OS cloud platform. They are designed to replace the legacy Technology connection point type. Technology connection points were used for generic web service (SOAP/REST) integrations, which often required less secure authentication methods and manual endpoint management. By contrast, IMS and ION API connections are deeply integrated with Infor Federation Services (IFS) for robust, OAuth 2.0-based security, providing a more secure, standardized, and manageable way to access Infor cloud applications.

Why Incorrect

A. IO Box connection points: These are specifically for integrating on-premise applications and file systems with the Infor cloud, not for application-to-application messaging which IMS handles.
C. File connection points: These are used for file-based data exchange. While data can be sent via messages, IMS is not a direct replacement for a file-based integration architecture.
D. Database connection points: These provide direct access to a database. IMS is a messaging and API gateway, which offers a different, decoupled integration pattern, not a direct replacement for database connectivity.

References

1. Infor OS Documentation, ION Desk User Guide: This guide details the various connection point types. It describes the "Technology" connection point as a means to connect to generic web services. The documentation for ION API and IMS connection points emphasizes their role in providing secure, managed access to Infor applications, positioning them as the modern successors to the less-secure, generic Technology connection points for cloud integrations. (Reference: Infor OS CE 2021.x, Infor ION Desk User Guide, Chapter on "Connection points").

2. Infor OS Documentation, ION Connect Administration Guide: This document explains the architecture of Infor ION Connect. It contrasts older integration methods with the modern, secure, and scalable architecture provided by the Infor Messaging Service (IMS) and the ION API gateway. The guide implicitly supports the replacement of generic technology connectors with these purpose-built, secure mechanisms. (Reference: Infor OS CE 2022.x, ION Connect Administration Guide, Section on "ION API" and "Infor Messaging Service").

3. University Courseware on Enterprise Application Integration (EAI): Academic principles of EAI advocate for moving from point-to-point, technology-specific integrations (akin to Infor's Technology connection points) to a standardized, message-based, or API-managed middleware layer (akin to IMS and ION API) to enhance security, scalability, and maintainability. (e.g., Course materials on Service-Oriented Architecture and Middleware from institutions like Carnegie Mellon or Stanford often cover this architectural evolution).

Scroll to Top