English
Language : 

TP01100 Datasheet, PDF (37/64 Pages) List of Unclassifed Manufacturers – TotalPlant Solution (TPS) System
Product Overview – Application Program Execution
NT Client Applications
There are several mechanisms for executing application processes in NT. One is to
invoke the client as an "Interactive Process." Another is to setup an automatic login
and start the application through the startup group and a third way is invoke the client
as a “Service Process” with the User ID set up by the system administrator. In any
case, the application ultimately runs under a process that acts as a client to the data
server and the TPS system.
CL Server
The CL Server provides a way to launch and schedule NT applications on the APP
from CL programs running in the TPN Application Module personality loaded on the
LCNP4 board.
Application Scheduling
Scheduling for those applications that require it can be accomplished through the
standard AM point-processing mechanism. The CL/AM extensions of the AM
personality of the APP provide the ability for a CL/AM program to trigger a new
instance of an NT application that starts, executes, and completes. The CL/AM
program waits until the execution of the application has completed before continuing.
On each activation, the CL program may pass an invocation string to the program being
activated. This can be used to communicate the reason for activation.
Only background CL programs may be used to initiate application programs. Multiple
applications, activated from a single AM point, are executed serially, the order of
execution determined by the CL insertion point order on the AM point.
Application Management
The CL Server provides management capability limited to the installation of single
applications within the APP. It assists in the management of executables initiated
through the CL/AM extensions defined above. It focuses on the following primary
functions.
• Install/deinstall applications which includes registration with CL Server
• View summary and state of installed applications through the CL Server specific
portion of the TPS Status Display, but not through HCI named data
• Aborting of selected applications through the CL Server specific portion of the TPS
Status Display, but not through HCI named data
11/98
TPS System Overview
37
R100
Honeywell Inc.