Table of Contents
Advertisement
Creating and Using Custom SAFs
Load and Initialize the SAF
For each shared library (plugin) containing custom SAFs to be loaded into the
Enterprise Server, add an
magnus.conf
The syntax for a directive that calls
Init fn=load-modules shlib=
•
shlib
•
funcs
shared library. Function names are case-sensitive. You may use dash (-) in
place of underscore (_) in function names. There should be no spaces in the
function name list.
If the new SAFs require initialization, be sure that the initialization function is
included in the
For example, if you created a shared library
do_small_anim()
init_my_animations
Init fn=load-modules shlib=animations.so
funcs="do_small_anim,do_big_anim,init_my_animations"
If necessary, also add an
newly loaded plugin. For example, if you defined the function
init_my_new_SAF()
would a directive such as the following to
Init fn=init_my_animations maxAnimLoop=5
Instruct the Server to Call the SAFs
Next, add directives to
the appropriate time. The syntax for directives is:
Directive fn=function-name [name1="value1"]...[nameN="valueN"]
•
Directive is one of the server directives, such as
124
Netscape Enterprise Server NSAPI Programmer's Guide • April 2002 (Draft)
directive that invokes the
Init
.
is the local file system path to the shared library (plugin).
is a comma-separated list of function names to be loaded from the
list.
funcs
and
do_big_anim()
, you would add the following directive to load the plugin:
directive that calls the initialization function for the
Init
to perform an operation on the
obj.conf
is:
load-modules
[path]sharedlibname
funcs="
animations.so
and also defines the initialization function
maxAnimLoop
magnus.conf
to instruct the server to call each custom SAF at
AuthTrans
SAF to
load-modules
SAF1,...,SAFn"
that defines two SAFs
parameter, you
:
,
, and so on.
Service
Advertisement
Table of Contents
