![[Contents]](FIGURE/CONTENT.GIF)
OpenTP1 Version 7 TP1/Client User's Guide TP1/Client/J
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
Service requests to TP1/Web are performed by calling the rpcCall method.
If the TP1/Web Java to SPP gateway facility (DC_JGW facility) is used, TP1/Web sends the service request to the SPP on the backend OpenTP1 based on the message sent by the rpcCall method. TP1/Web answers response messages from the OpenTP1 SPP using the HTTP protocol.
If the TP1/Web Java to User Service facility (DC_JUSR facility) is used, user services running on TP1/Web can be called. You can freely describe processes with the user services running on TP1/Web. TP1/Web returns responses using the HTTP protocol.
If the TP1/Web connection facility provided by TP1/Client/J is used, there are two service request modes: synchronous response mode and chained mode. However, the chained mode uses the TP1/Web static session schedule facility, which can be used only when the DC_JGW facility is being used.
For details about the synchronous response mode and the chained mode, see 2.2.3 RPC modes.
In this mode, a CUP (Java applet) that uses TP1/Client/J sends a query message to TP1/Web and receives a response message. With synchronous response mode RPC, the next process does not execute until the CUP receives the response from TP1/Web.
In this mode, a CUP (Java applet) that uses TP1/Client/J sends a query message to TP1/Web and receives a response message. With chained mode RPC, the next process does not execute until the CUP receives the response from TP1/Web. To use chained mode RPC, TP1/Web must be set to use the static session schedule facility, and the TP1/Web service set requested by the openConnection method must be DC_JGW.
All Rights Reserved. Copyright (C) 2006, 2009, Hitachi, Ltd.