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

The product exposed APIs, likely supporting SOAP and potentially REST. It allowed developers to invoke CICS transactions through these APIs. The specific API endpoint patterns and method names would depend on the configuration and the CICS transactions being exposed.

What programming languages and protocols were supported for integration?

Synapta Services Builder for CICS supported integration with various programming languages, including Java. The product likely provided SDKs or libraries to facilitate integration. The specific protocols used for communication would depend on the API type, such as HTTP for REST or SOAP over HTTP.

What were the main system components of Synapta Services Builder for CICS?

The main system components included a service builder, a runtime environment, and potentially a metadata repository. The service builder was used to define and configure the web services. The runtime environment handled the execution of the services, and the metadata repository stored information about the CICS applications and web service definitions.

How did the components of Synapta Services Builder for CICS communicate?

Communication between components likely occurred through internal APIs and network protocols. The runtime environment would communicate with CICS using appropriate protocols, such as TCP/IP. The service builder would interact with the runtime environment to deploy and manage services.

What was the business value of using Synapta Services Builder for CICS?

Synapta Services Builder for CICS enabled organizations to modernize their mainframe applications by exposing them as web services. This allowed for easier integration with modern applications and systems, extending the lifespan and value of existing mainframe investments.

How did Synapta Services Builder for CICS improve efficiency and reduce costs?

By avoiding screen-scraping, the product provided a more efficient and reliable way to access CICS data. This resulted in improved performance and reduced development and maintenance costs compared to screen-scraping solutions.

How did Synapta Services Builder for CICS enable the reuse of existing applications?

The product facilitated the reuse of existing CICS/COBOL applications. By exposing these applications as web services, organizations could leverage their existing business logic in new applications without rewriting the mainframe code.

What authentication methods were supported by Synapta Services Builder for CICS?

The product likely supported authentication mechanisms to secure access to the exposed web services. Specific methods might have included user ID and password authentication, or integration with security frameworks available on the mainframe.

How was access control managed in Synapta Services Builder for CICS?

Access control was likely managed through the configuration of the web services. This could involve defining which users or applications were authorized to access specific CICS transactions. The product might have integrated with mainframe security systems for authorization.

What encryption methods were used by Synapta Services Builder for CICS?

Encryption was likely used to protect sensitive data transmitted over the network. This could include the use of HTTPS for secure communication. The product may have also supported encryption of data within the CICS environment.

What administrative interfaces were available for Synapta Services Builder for CICS?

Administrative interfaces likely included a GUI or web console for configuring and managing web services. These interfaces allowed administrators to define service mappings, configure security settings, and monitor the runtime environment.

How was user management handled in Synapta Services Builder for CICS?

User management was likely handled through the administrative interfaces, allowing administrators to create, modify, and delete user accounts. The product might have integrated with existing user directories or security systems on the mainframe.

What were the main configuration parameters?

Key configuration parameters included settings for connecting to CICS, defining service mappings, and configuring security. These parameters were set through the administrative interfaces and stored in configuration files.

What monitoring and logging capabilities existed?

Monitoring and logging capabilities were essential for troubleshooting and performance analysis. The product likely provided logging of service requests, errors, and performance metrics. These logs could be accessed through the administrative interfaces or external monitoring tools.

Share Your Product Experience

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

Share Your Experience

Synapta Services Builder for CICS

Name: Synapta Services Builder for CICS
Availability: InStock

Attachmate Not Supported z/OS

Legacy Application/Data Access Java and Web Application Development CICS

Vendor

Attachmate

Product Overview

The architecture of Synapta Services Builder for CICS comprised several key components. The service builder was the primary interface for defining and configuring web services. It allowed users to import CICS/COBOL copybooks, map CICS transactions to web service operations, and configure security settings.

The runtime environment was responsible for executing the web services. It handled the communication with CICS, data transformation, and security enforcement. A metadata repository stored information about the CICS applications, web service definitions, and configuration settings.

Communication between components likely occurred through internal APIs and network protocols, such as TCP/IP. The service builder would interact with the runtime environment to deploy and manage services. The product supported various API types, including SOAP and potentially REST.

Security features included authentication mechanisms and access control based on configuration. The product is no longer supported; migrate to a supported solution like Verastream Transaction Integrator.

Frequently Asked Questions

What was the primary function of Synapta Services Builder for CICS?

Synapta Services Builder for CICS enabled the creation of web services from CICS/COBOL applications without screen-scraping. It provided tools for non-mainframe applications to access CICS COBOL applications by reading CICS/COBOL copybooks. This allowed for the integration of mainframe applications with modern web and Java-based systems.

How did Synapta Services Builder for CICS enable integration with other systems?

The product facilitated the exposure of CICS transactions as web services, enabling access from various client applications. It simplified the process of integrating mainframe applications with other systems by translating CICS data structures into formats compatible with web services.

How did Synapta Services Builder for CICS handle CICS/COBOL data structures?

Synapta Services Builder for CICS provided tools to read CICS/COBOL copybooks. This allowed the product to understand the data structures used by CICS applications. This capability was crucial for translating data between CICS and the web service formats.

What approach did Synapta Services Builder for CICS use to access CICS applications?

The product was designed to avoid screen-scraping, which is a less efficient method of accessing mainframe data. Instead, it directly accessed the CICS applications, providing a more reliable and performant integration solution.

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

Share Your Product Experience

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

Share Your Experience

Share Your Product Experience

Synapta Services Builder for CICS

Product Overview

Frequently Asked Questions

What was the primary function of Synapta Services Builder for CICS?

How did Synapta Services Builder for CICS enable integration with other systems?

How did Synapta Services Builder for CICS handle CICS/COBOL data structures?

What approach did Synapta Services Builder for CICS use to access CICS applications?

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

What programming languages and protocols were supported for integration?

What were the main system components of Synapta Services Builder for CICS?

How did the components of Synapta Services Builder for CICS communicate?

What was the business value of using Synapta Services Builder for CICS?

How did Synapta Services Builder for CICS improve efficiency and reduce costs?

How did Synapta Services Builder for CICS enable the reuse of existing applications?

What authentication methods were supported by Synapta Services Builder for CICS?

How was access control managed in Synapta Services Builder for CICS?

What encryption methods were used by Synapta Services Builder for CICS?

What administrative interfaces were available for Synapta Services Builder for CICS?

How was user management handled in Synapta Services Builder for CICS?

What were the main configuration parameters?

What monitoring and logging capabilities existed?

Related Products

More from Attachmate

Extra!

FileXpress

Irma

Luminet

Reflection

Reflection for the Web

Similar Products

3270 SUPEROPTIMIZER/CICS

Ab Initio Business Rules Environment

Access Manager for CICS

Access Manager for IMS

ACCOLADE

ACI Host Link

Help Improve This Directory

Share Your Product Experience