Author: Robert Sample
Posted: Fri Mar 10, 2017 3:58 am (GMT 5.5)
I found this in the CICS 5.2 manuals:
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Posted: Fri Mar 10, 2017 3:58 am (GMT 5.5)
I found this in the CICS 5.2 manuals:
| Quote: |
| Before you can plan to use SOAP web services in CICS®, you need to consider these questions for each application.
Before you begin Do you plan to deploy your CICS application in the role of a service provider or a service requester? You may have a pair of applications that you want to connect using CICS support for web services. In this case, one application will be the service provider; the other will be the service requester. Do you plan to use your existing application programs, or write new ones?If your existing applications are designed with a well defined interface to the business logic, you will probably be able to use them in a web services setting, either as a service provider or a service requester. However, in most cases, you will need to write a wrapper program that connects your business logic to the web services logic. If you plan to write new applications, you should aim to keep your business logic separated from your web services logic, and, once again, you will need to write a wrapper program to provide this separation. However, if your application is designed with web services in mind, the wrapper might be simpler to write. Do you intend to use SOAP messages?SOAP is fundamental to the web services architecture, and much of the support that is provided in CICS assumes that you will use SOAP. However, there may be situations where you want to use other message formats. For example, you might have developed your own message formats that you want to deploy with the CICS web services infrastructure. You can do this with CICS, but you will not be able to use some of the functions that CICS provides, such as the web services assistant, and the SOAP message handlers. If you decide not to use SOAP, your application programs will be responsible for parsing inbound messages, and constructing outbound messages. Do you intend to use the CICS web services assistant to generate the mappings between your data structures and SOAP messages?The assistant provides a rapid deployment of many applications into a web services setting with little or no additional programming. And when additional programming is required, it is usually straightforward, and can be done without changing existing business logic. However, there are cases which are better handled without using the web services assistant. For example, if you have existing code that maps data structures to SOAP messages, there is no advantage in reengineering your application with the web services assistant. Although the CICS web services assistant supports the most common data types and structures, there are some that are not supported. In this situation, you should check the list of unsupported data types and structures for the language in question, and consider providing a program layer that maps your application data to a format that the assistant can support. If this is not possible, you will need to parse the message yourself. For details on what the assistant can and cannot support, see High-level language and XML schema mapping. If you decide not to use the CICS web services assistant, you can use a tool such as Rational® Developer for System z® to create the necessary artifacts, and you can then provide your own code for parsing inbound messages, and constructing outbound messages. You can also use the provided vendor interface API. Do you intend to use an existing service description, or create a new one?In some situations, you will be obliged to use an existing service description as a starting point. For example:â¢Your application is a service requester, and it is designed to invoke an existing web service. â¢Your application is a service provider, and you want it to conform to an existing industry-standard service description. In other situations, you may need to create a new service description for your application. ïPlanning a SOAP service provider application In general, CICS applications should be structured to ensure separation of business logic and communications logic. Following this practice will help you to deploy new and existing applications in a web service provider in a straightforward way. You will, in some situations, need to interpose a simple wrapper program between your application program and CICS web service support. ïPlanning a SOAP service requester application In general, CICS applications should be structured to ensure separation of business logic and communications logic. Following this practice will help you to deploy new and existing applications in a web service requester in a straightforward way. You will, in almost every situation, need to interpose a simple wrapper program between your application program and CICS web service support. |
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth