HP TP Desktop Connector V5.0A

HP TP Desktop Connector V5.0A SPD 34.81.24
There are four different programming interfaces avail-
able:
• Automation
• C-language
• Java
• Client Services
Automation Interface
The Automation interface supports any desktop tool
or Microsoft Office product that supports Automation.
ACMS tasks are presented as Automation objects.
C-language Interface
The C-language interface supports any desktop tools
that support a C-callable interface. ACMS tasks are
presented as callable C procedures.
Java Interface
• Sun Microsystems Java Development Kit (JDK) Java
2 Version 1.4.2
Client Services Interface
The client interface provides support for three models
of application development:
• Blocking interface where execution of the program
is blocked during execution of the TP Desktop
Gateways.
• Nonblocking support of exchange steps.
• Forced nonblocking that facilitates exchange I/O be-
tween ACMS tasks and Visual BASIC clients.
The services provided by the portable client interface
for Windows XP, Windows 2000, Windows 2003, Tru64
UNIX, and OpenVMS address the areas of:
• Sign in/out services—establish and terminate ses-
sions.
• Call processing services—send and receive applica-
tion requests
• Presentation procedure routines—called automati-
cally by the portable client to facilitate forms process-
ing for the desktop user (not supported in a forced
nonblocking environment).
Runtime System
Client runtime libraries are provided for the client operat-
ing systems to support the execution of client programs
that use the product’s services.
The TP Desktop Gateway is an asynchronous, multi-
threaded, runtime component residing on any OpenVMS
node, regardless of the location of ACMS applications
being called by desktop clients. There is generally one
gateway on a node. The gateway is an ACMS agent
that performs the following functions:
• Authenticates desktop clients (ACMS submitters).
• Calls tasks for users; this can include local and re-
mote ACMS task selection.
• Communicates with the desktop client program as
part of task exchange step (desktop presentation pro-
cedure) execution. This function is supported by the
client services only.
• Provides information to the system manager con-
cerning TP Desktop Connector submitters.
Management and Control
The TP Desktop Connector supports the following man-
agement and control features:
• The client interface reports errors from ACMS back
to the desktop client program for local error handling.
• The client interface optionally logs error messages to
a local desktop device file.
• Messages can be protected against sabotage or
network corruption by adding Cyclic Redundancy
Checking (CRC) for the client services only.
• The gateway reports ACMS and desktop client errors
to the ACMS software event logger.
• OpenVMS system managers can control desktop
client access to ACMS and remove desktop clients
from the ACMS system, using standard ACMS utili-
ties.
TPware .NET Support
TPware .NET is an interface between the Windows
based client applications and the TPware Gateway
server, which in turn communicates with the ACMS sys-
tem. It belongs to the TPware product family and,
manages and monitors the ACMS applications from the
Windows platform. It has a set of API Client Services
that are referenced by the Windows based applications
to communicate with the ACMS system on OpenVMS.
These API Client Services form the TPware .NET Inte-
gration Class Library. The TPware .NET and the TP-
ware Gateway server are the points of contact on the
respective Windows and OpenVMS platforms.
2