[Top] [Prev] [Next] [Bottom] [Contents]

Running Files, Executables, and FUNCTION objects on the Gateway

To run Files, Executables, and Function Objects on the Gateway you should set two options in the Object Definition in the Object Editor. The first indicates that you want to run the object on the gateway. Set the option RunGenericOnOrb to True. The second defines on which gateway (i.e. vendor) to run the object. Set the option OrbDefaultVendor to one of the following:

SYBASE
ORACLE
INFORMIX

Running an object on the gateway has several implications:

The user who started the gateway is the process owner as opposed to "nobody" for a Server Application.
The starting directory of the gateway is the directory in which it was started. The HTTP server sets the start directory of the Server Application.
The environment will depend on the process owner.
The directory structure, depending on which CPU and NFS each runs on, may vary unpredictably.
The gateway may be harder to debug since you must attach to a running process.

For Function objects to run on the gateway, you must rebuild the gateway, as described in the previous section. To add new function objects to the gateway, add a call to a registration function in the Main of the gateway, dborbd_main.c, found in the bin directory of the Sapphire/Web distribution.

This function should register all object implementations with calls to the function, SaRegisterObjImp, and modify the make macro, APPL_OBJS, in the Makefile.orb file. Although more difficult to do, this may help off-load significant capability from the Server Application, making it smaller.

The Sapphire/Web client API is limited on the gateway to SutList type calls and the Function implementation functions, SaReq....

[Top] [Prev] [Next] [Bottom] [Contents]

info@bluestone.com

Copyright © 1997, Bluestone. All rights reserved.