3.3.4.4.4.3.1 Register to Oracle Tuxedo

Oracle Tuxedo uses the epifreg command to register the plug-ins to the Oracle Tuxedo registry so that the infrastructure can invoke the plug-in at run time. Oracle TSAM Plus uses the Oracle TSAM Plus framework to invoke the plug-in.

The following listing shows how the epifreg command is used to invoke a plug-in.

Using epifreg to Invoke a Plug-in

epifreg -r -p abc/tuxedo/tsam -i engine/performance/monitoring \
       -o SYSTEM -v 1.0 -f /test/abc/customplugin.so -e plugin_entry
epifregedt -s -k "SYSTEM/impl/bea/performance/monfan" \
       -a InterceptionSeq=bea/performance/monshm \
          -a InterceptionSeq=abc/tuxedo/tsam

In this, there are two steps required to register the custom plug-in Oracle Tuxedo.

1. Using “epifreg” to register the custom implementation to Oracle Tuxedo.
   1. “-p” option specifies the implementation id and it must be consistent the value specified in source code.
   2. “-v” indicates the version number.
   3. “-f” specifies the dynamic library path.
   4. “-e” specifies the “entry” routine described in the “General Steps” section.
2. Using “epifregedt” to change the fan-out plug-in “InterceptionSeq” attribute.

   Oracle TSAM Plus supports a Fan-out plug-in mechanism which means multiple plug-ins can work together. Oracle TSAM Plus Agent provides the Fan-out plug-in and a default interceptor plug-in. The custom plug-in is an additional interceptor plug-in.

   The “-a InterceptionSeq=xxx” option tells the Fan-out plug-in invokes the interceptor plug-in using the specified order. “xxx” is the implementation id. In this example, the Oracle Tuxedo default interceptor plug-in implementation ID, “bea/performance/monshm”, is invoked before the custom plug-in implementation ID “abc/tuxedo/tsam”.

3. If you have multiple custom plug-in developed, you need to register them first with “epifreg”, then modify the invocation sequence with “epifregedt” with the proper “InterceptionSeq” sequence.