What is Synapta Services Builder for IMS?

Synapta Services Builder for IMS was a software product designed to create web services from IMS and COBOL applications without screen-scraping. It enabled organizations to modernize their legacy systems by exposing IMS functionality through web-based interfaces. The product was originally released as myEXTRA! Smart Connector for IMS.

What were the primary use cases?

The primary use cases included integrating IMS applications with web and Java-based applications, enabling mobile access to IMS data, and creating new business processes that leverage existing IMS functionality. It was also used to modernize applications by providing a service-oriented architecture (SOA) for IMS.

What were the key benefits?

Key benefits included reduced development time compared to screen-scraping, improved application performance, and the ability to leverage existing IMS assets. It also provided a more secure and manageable way to expose IMS functionality compared to other methods.

What were the main components?

The main components included the Service Builder, the IMS Connector, the Java Runtime Environment, and the Web Services Gateway. The Service Builder was used to define and generate web services. The IMS Connector facilitated communication with IMS. The Web Services Gateway handled incoming and outgoing web service requests.

What types of APIs did it expose?

Synapta Services Builder for IMS exposed web services, typically using SOAP and REST APIs. These APIs allowed external applications to interact with IMS applications. API endpoint patterns were based on the services defined in the Service Builder.

What programming languages and protocols were supported?

The product supported Java for custom logic and integration. It used HTTP and HTTPS for communication. SOAP and REST were supported for web service interactions.

What were the network requirements?

The product required network connectivity between the Web Services Gateway and the IMS system. Specific ports needed to be open for HTTP/HTTPS traffic. The IMS Connector required access to the IMS system through appropriate network configurations.

How did it help businesses?

It enabled businesses to modernize their legacy IMS applications by exposing them as web services. This allowed for easier integration with modern applications, improved agility, and reduced the cost of maintaining legacy systems.

The ROI came from reduced development time, decreased maintenance costs, and the ability to leverage existing IMS assets. By avoiding screen-scraping, businesses could deploy new services faster and with lower risk.

How did it improve developer productivity?

The Service Builder provided a graphical interface for defining web services, reducing the need for manual coding. This allowed developers to focus on business logic rather than low-level integration details, improving productivity.

How did it support business agility?

By exposing IMS functionality as web services, businesses could quickly adapt to changing market demands. New services could be created and deployed rapidly, enabling faster time-to-market for new applications and features.

What authentication methods were supported?

The product supported various authentication methods, including basic authentication, and potentially integration with enterprise security systems. Specific methods depended on the configuration and the security features of the underlying IMS environment.

What access control model was used?

The access control model typically relied on the security features of the underlying IMS system and the web service configuration. This could include role-based access control (RBAC) or other access control mechanisms defined within IMS.

What encryption was used?

Encryption was supported for communication over HTTPS. Data transmitted between the Web Services Gateway and the IMS system could also be encrypted, depending on the configuration and the security settings of the IMS environment.

What audit and logging capabilities existed?

The product provided logging capabilities to track service requests, errors, and other events. Audit logs could be configured to record security-related events. The specific logging and auditing features depended on the configuration.

What administrative interfaces were available?

Administrative interfaces included a web-based console for managing services and configurations. Command-line interfaces (CLI) might have been available for specific tasks. The Service Builder provided a graphical interface for defining and deploying services.

How was user management handled?

User management was typically handled through the underlying operating system and/or the enterprise security infrastructure. The product itself did not have its own user management system, but relied on external authentication and authorization mechanisms.

What were the main configuration parameters?

Main configuration parameters included settings for connecting to the IMS system, defining web services, configuring security, and managing logging. These parameters were set through the administrative interfaces.

What monitoring and logging capabilities existed?

Monitoring capabilities included the ability to track service performance, monitor system resources, and view logs. Logging provided detailed information about service requests, errors, and security events. These features were accessible through the administrative interfaces.

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

Synapta Services Builder for IMS

Attachmate Not Supported z/OS

IMS Legacy Application/Data Access Java and Web Application Development

Vendor

Attachmate

Product Overview

The architecture of Synapta Services Builder for IMS comprised several key components. The Service Builder, a graphical user interface, allowed users to define web services by mapping IMS transactions to web service operations. The IMS Connector acted as the communication bridge between the Web Services Gateway and the IMS system.

It handled the low-level communication protocols and data transformations required to interact with IMS. The Web Services Gateway received incoming web service requests, routed them to the appropriate IMS transactions via the IMS Connector, and returned the results. The system supported SOAP and REST APIs.

The Java Runtime Environment provided the necessary environment for custom logic and extensions. The communication between components used HTTP/HTTPS. The IMS Connector utilized specific ports to communicate with the IMS system.

The product is not supported. Organizations should consider Verastream Transaction Integrator or other enterprise integration platforms for a supported architecture.

Frequently Asked Questions

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

Are You a Vendor? Claim Your Listing

Synapta Services Builder for IMS

Product Overview

Frequently Asked Questions

What is Synapta Services Builder for IMS and what was its purpose?

What is Synapta Services Builder for IMS?

What are the primary use cases for Synapta Services Builder for IMS?

What were the primary use cases?

What are the key benefits of using Synapta Services Builder for IMS?

What were the key benefits?

What are the main components of Synapta Services Builder for IMS?

What were the main components?

What types of APIs did Synapta Services Builder for IMS expose?

What types of APIs did it expose?

What programming languages and protocols were supported?

What programming languages and protocols were supported?

What are the network requirements for Synapta Services Builder for IMS?

What were the network requirements?

How did Synapta Services Builder for IMS help businesses?

How did it help businesses?

What was the return on investment (ROI) of using Synapta Services Builder for IMS?

What was the ROI?

How did Synapta Services Builder for IMS improve developer productivity?

How did it improve developer productivity?

How did Synapta Services Builder for IMS support business agility?

How did it support business agility?

What authentication methods were supported?

What authentication methods were supported?

What access control model was used?

What access control model was used?

What encryption was used?

What encryption was used?

What audit and logging capabilities existed?

What audit and logging capabilities existed?

What administrative interfaces were available?

What administrative interfaces were available?

How was user management handled?

How was user management handled?

What were the main configuration parameters?

What were the main configuration parameters?

What monitoring and logging capabilities existed?

What monitoring and logging capabilities existed?

Related Products

More from Attachmate

Similar Products

Help Improve This Directory

Are You a Vendor? Claim Your Listing