OpenTP1 Version 7 TP1/Client User's Guide TP1/Client/J

[Contents][Index][Back][Next]

2.2.7 RPCs that use the remote API facility

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

[Figure]

  1. Create an instance of the TP1Client class that is provided by TP1/Client/J.
  2. Call the openConnection method to establish connection with the TP1/Server's RAP-processing server.
  3. Call the rpcCall method to issue a service request to the specified SPP via the RAP-processing server.
    You can call the rpcCall method as many times as necessary while the connection is established.
  4. Call the closeConnection method to release the connection with the TP1/Server's RAP-processing server.

Note
If you issue a service request to a server that is managed by the security facility of DCE using the RAP-processing server, ErrSecchkException is returned.
When using the remote API facility with the dccltrpcmaxmsgsize operand specified in the TP1/Client/J environment definition, if you issue a service request to the SPP of a TP1/Server for which the rpc_max_message_size operand is not specified in the system common definition, an RPC error is returned.