JCA 1.5, Part 2: work flow management and services
Class: Junior
David Currie (david_currie@uk.ibm.com), the Occupational software engineer, IBM UK Ltd
May 30, 2005
David Currie will continue his three-part series of articles on the Java 2 Enterprise Edition (J2EE) Connector Architecture (JCA) in the latest version of the enhancement and changes. In this paper, who will introduce the new JCA 1.5 of the management contract, the contract allows the use of application server resource adapter to some of the features to scheduling and work. Another increase in the JCA - Services inflow - with the support of the enterprise information system in their own affairs in the implementation of this work.
JCA J2EE Connector 1.5 is the latest version of Architecture, which includes many important improvements and some major enhancements. This article is to introduce these changes by the three-part series of articles consisting of Part 2, on the establishment of the life-cycle management of the Part 1 on the basis of this paper is the work of JCA new management contract. The contract allows for resource adapter or delay the implementation of the work carried out periodically to create the timer, and allow the use of the application server timer synchronous or asynchronous thread handling. This paper will describe how support services in the inflow of resources to the server adapter into the affairs of such treatment, as well as resource adapter then how to control the affairs of completion.
If you want to use existing resources in the adapter function, or are considering the preparation of a new 1.5 JCA resource adapter, then this is an indispensable book. If the use of resources to the preparation of the application adapter, would like to know more behind the scenes, then this will attract you.
List 2 in the WorkManager methods of the four parameters (WorkListener) in the asynchronous method for these most useful. 5 shows a list of this interface:
references).
In the use of this standard interface, from the Java name and directory services Interface (JNDI) get a TimerManager achieve. Through to the management arrangements for a return to TimerListener achieve a Timer (rather than a commonj.timers.Timer java.util.Timer). Good time in the organization will call TimerListener, Timer can be used such as the cancellation of scheduled operation of the implementation of such operations.
As the name suggests, this specification also provides the management of the JCA an alternative. JCA here and the interface is very similar to those interfaces, in addition to the initial commmonj.work.WorkManager from JNDI get. The contracts also include additional acts: obstruction to a full schedule of work completed or the ability of the remote JVM can be implemented on the sequence of the possibility. And commonj Timer, commonj WorkManager application is not limited to resource adapter. J2EE any server-side components can use this function.
9 shows the list in order to use the type commonj was rewriting the list of eight examples:
4 ExampleWork with the same list, in addition, it has commonj Work interface requirements for the additional isDaemon methods. If the work exist for a long time, the method should return true.
list can be seen in two it was transmitted to the WorkManager. As can be seen in the list of 10, this class has set Affairs ID (XID) and the overtime affairs:
reference) to build a XID. Then call in the application server will be the object of work before this method run affairs and the execution threads linking.
Services into the application server, followed by the resource adapter on the charge of the affairs of this incident to the notice server. Specifically, it must notify the Service to complete the application server. It is through the list of the 11 XATerminator interfaces do this, they can get it from BootstrapContext in the realization of:
original English text.
david_currie@uk.ibm.com contact with him.
