jurgen de craeye

We would like to use a CGI that uses BEA Tuxedo to access
some Tuxedo Queues. The problem is that for Tuxedo some
environment variables need to be set. Those variables
doesn't seem to be accessible for the CGI since the error
we're getting when using the Tuxedo API point in that
direction. Is there a way to enforce certain environment
variables or to verify the ones that are in use by the CGI
or even IIS?

david wang [msft]

You can enforce certain environment variables by first mapping a extension
to a Windows Batch script (such as .cmd to CMD.EXE), and then have the batch
script modify the environment variable prior to launching the BEA Tuxedo CGI
EXE -- the CGI EXE will now inherit this new environment.

The same trick can be used to dump the values of the environment.prior to
calling the CGI EXE.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//


We would like to use a CGI that uses BEA Tuxedo to access
some Tuxedo Queues. The problem is that for Tuxedo some
environment variables need to be set. Those variables
doesn't seem to be accessible for the CGI since the error
we're getting when using the Tuxedo API point in that
direction. Is there a way to enforce certain environment
variables or to verify the ones that are in use by the CGI
or even IIS?

The CGI is written in C.