The configuration file you are editing should already have at least one EXCI client configuration. (The EXCI user exit cannot
do anything useful unless there is at least one APPLID it can return.) See
Configuring EXCI for the client.
Use this procedure to enable an EXCI user exit module. An EXCI user exit is a routine supplied by the customer which can change
the APPLID (EXCI destination) specified by the application. This lets you redirect EXCI clients to a different region without
changing the application source. (You can also change what region an EXCI client connects to by changing the target URL of
the APPLID in the client configuration.)
-
Open the configuration file for editing.
-
Add a
<dfhxcurm> element as a child of the
<client> element. (Modify the
<dfhxcurm> element if it already exists. Only one
<dfhxcurm> element is permitted per configuration file.) Set the
file attribute to the path to the DLL that implements your
DFHXCURM routine. (The DLL file may have any name, but it must have an entry point named
DFHXCURM.) The value can include environment variables in the form
%name%, which will be expanded using the .NET Framework's Environment::ExpandEnvironmentVariables method.
Here is a sample
<dfhxcurm> element:
<dfhxcurm file="%MyApp%/userexit.dll" />
-
Save the file.
Restart the application, JES region, or IIS pool to enable the new configuration.