OpenTP1 Version 7 TP1/Client User's Guide TP1/Client/J
TP1/Client/J enables you to establish a permanent connection between a CUP and the TP1/Server, transfer an API issued by the CUP to the TP1/Server, and have it executed by a TP1/Server process. This functionality is called the remote API facility. When you use the remote API facility, you can also issue service requests to UAPs inside the firewall. In the case of a Java applet, because of Java security limitations, connection can be established only with a RAP-processing server that is active in the TP1/Server on the Web server to which the Java applet belongs. If an attempt is made to establish connection with a RAP-processing server that is active outside the TP1/Server on the Web server to which the Java applet belongs, the security manager returns SecurityException. An RPC that uses the remote API facility can use DCCM3 and TMS-4V/SP, as well as TP1/Server.
The following figure shows the flow of a service request when the remote API facility is used.
Figure 2-5 Flow of a service request when the remote API facility is used
All Rights Reserved. Copyright (C) 2006, 2009, Hitachi, Ltd.