TP1/Client/J makes it possible for Java applets running on a Web browser, Java applications, and Java servlets running on an application server to use remote procedure calls (RPCs) to request services from an OpenTP1 server UAP. A program that is created by a Java applet, Java application, or a Java servlet to request services is called a CUP (client user program). A server UAP from which a CUP can request services is called an OpenTP1 service-providing program (SPP).

TP1/Client/J enables you to start a transaction from the SPP that was started by a CUP. When you do this, you can apply a distributed OLTP environment to application systems on the Internet or on an intranet. You can also support a variety of platforms with a single CUP because you use Java applets, applications, and servlets to create CUPs. There is no need to create a separate CUP for each platform.

In this manual, TP1/Server Base and TP1/LiNK are referred to collectively as TP1/Server. The TP1/Server Base versions that can process requests from TP1/Client/J are 03-05 and later; earlier versions of TP1/Server Base will not run.

The following figures show the relationships between TP1/Server and TP1/Client/J when a CUP is created by a Java applet, a Java application, or a Java servlet.

Figure 1-1 Relationships between TP1/Server and TP1/Client/J (for a CUP created by a Java applet)

When you create a CUP with a Java applet, you can centralize management of the CUP via the Web server; there is no need to distribute the CUP to clients.

Figure 1-2 Relationship between TP1/Server and TP1/Client/J (for a CUP created by a Java application)

Figure 1-3 Relationships between TP1/Server and TP1/Client/J (for a CUP created by a Java servlet)