Patterns: Implementing Self-Service in an SOA Environment

Chapter 12. J2EE Connector Architecture scenario 407

com.ibm.patterns.jcaService.MartAccounts output = new

com.ibm.patterns.jcaService.MartAccounts();

// Invoke the program

interaction.execute(iSpec, input, output);

12.3.5 Transaction management

The two-phase commit capability of CICS ECI resource adapters is only

supported with WebSphere Application Server for z/OS. However, we would still

recommend that you use container-managed transactions in distributed platform

environments, and allow the container to optimize the transaction using an

only-agent optimization or last participant support.

For more information, see IBM WebSphere Developer Technical Journal:

Transactional integration of WebSphere Application Server and CICS with the

J2EE Connector Architecture at:

http://www-128.ibm.com/developerworks/websphere/techjournal/0408_wakelin/

0408_wakelin.html

12.3.6 Security

The user ID and password required to access the back-end system can be

specified in the resource adapter properties in the WebSphere Application

Server runtime environment. The user ID and password can also be specified

using a component-managed authentication alias, a container-managed

authentication alias, or programatically using the ConnectionSpec.

12.4 Development guidelines for JCA

This section describes the implementation of a JCA connection in the ITSOMart

sample application. The sample was developed using Rational Software

Architect and deployed on WebSphere Application Server V6. The service

integration bus was used to provide the destination endpoints for the Web

service.