Introduction
To fully understand this Binding Component architecture is necessary to focus on two main time: The Deploy time
and The Runtime
At deploy time the following sequence of events occurs:
- The Copy Cobol is parsed(To verify which Cobol's data types are supported please visit the page of the supported Cobol data types
).
- A Data structure correspondig to the copy cobol is created.
- A set of classes representing the service interfaces and parameters beans are dynamically created.
- A JBI Web service based on the previous classes is created.
- The JBI Web service is published as an internal JBI endpoint.
The following figure shows this process in an unformal sequence diagram:
At runtime the following sequence of events occurs:
- The JBI internal endpot is called by another JBI endpoint.
- The received payload is unmarshalled in a Java beans representing the service's input parameter.
- The newly created bean in then serialized in a commarea compliant with the CICS service's copy cobol.
- The commarea is sent to the CICS transaction using the JCA CICS ECI Connector.
- A reply commarea is received and deserialized in Java bean representing the result.
- The result java bean is marshalled into the reply payload.
- The reply payload is posted into the JBI bus.
The following figure shows this process in an unformal sequence diagram: