Kbase 16945: How to start and stop an Appserver broker on VMS
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
How to start and stop an Appserver broker on VMS
The App-Server is an additional product which can be purchased to
off load processing from clients to a remote process which will run th
The Application Server architecture provides the ability for a 4GL
program to execute 4GL procedures in the context of a remote Progress
session. Once the AppServer process has been started, the 4GL
client may make remote procedure requests to the Application
Server process to which it is connected. It is the intent that this
document provide a detailed description of how to start and stop an
Application Server on a Digital OpenVMS platform. The Application
Server was made available in 8.1A.
PROTOCOL CONFIGURATION SUPPORTED
PC Remote client --> VAX OpenVMS --> VAX OpenVMS
AppServer Broker Database broker
TCP is the only protocol that will be supported between the PC remote
client and the Application Server Broker on an OpenVMS platform.
DECnet is not supported. However, DECnet, TCP and Pathworks are
supported between the Application Server Broker and the Database
Broker on an OpenVMS platform. Refer to the 8.1a VMS release notes
on the supported TCP products.
STARTING THE APPSERVER BROKER
For the Digital OpenVMS platforms, you must use the foreign command
syntax and provide parameters to the images as they are defined for
the UNIX systems noted in the System Administration Reference Manual.
A VMS foreign command is a way to run VMS images directly from DCL
without needing to provide a command definition file (progress.cld).
You must first define a symbol to point at the image you wish to run,
then just invoke the image from the symbol as follows:
define proapbk bin:_proapbk.exe
proapbk "-S" myservc "-H" myhost "-N" tcp
This will start an application server broker using the service name
"myservc" on the node name "myhost" using TCP/IP. Note unix like
syntax and upper case for each of the progress parameters. These MUST
be enclosed in quotes and upper case for them to be recognized.
Also note that the VMS like command syntax /SERVICE/HOST/NETWORK
will not be recognized due to the command definitions (progress.cld)
file not provided. In order to assist you, a "starter" command file,
BIN:PROAPBK.COM is provided.
CONNECTING TO THE APPSERVER BROKER
A procedure is run by the application server when the requesting
application executes the CONNECT() method on a server handle. To run
this routine you must specify the -con parameter and the procedure
name at startup of the client process. For information about the
connection procedure, see Chapter 5, "Programming Details" in the
Building Distributed Applications Using the Progress AppServer.
STOPPING THE APPSERVER BROKER
Application server processes associated with the AppServer broker are
initialized by the AppServer Broker when a client requests access to
the Broker. The server process is terminated automatically when the
client disconnects from the AppServer Broker. Therefore, there is aa
one to one relation between a progress client and an AppServer server
process.
define proshut bin:_mprshut.exe
proshut "-AS" "-S" myservc
The -AS parameter is used to identify shutting down the AppServer
broker and the -S parameter is used to identify which AppServer you
are shutting down, based on the service name provided at startup of
the AppServer broker. Note that the quotes are also required for the
proshut command.
ADDRESSING APPLICATION SERVER PROBLEMS
The AppServer broker automatically logs information regarding the
startup of the broker, spawned servers and shutdown requests. The name
of the AppServer logfile is 'proapsv.lg'.
06/17/97
Progress Software Technical Support Note # 16945