To enable an openFT instance to send ADM traps to the ADM trap server, the FT administrator of the openFT instance must make certain settings in the operating parameters, see below. In addition, the asynchronous openFT server must be started.
The procedure for Unix and Windows systems is described below. You will find the descriptions for BS2000 and z/OS systems in the manual "openFT (BS2000) - Installation and Operation" and in the manual "openFT (z/OS) - Installation and Operation".
Carry out the following actions in your role as FT administrator:
Specify the following items in the -atpsv option of the ftmodo command:
the name of the ADM trap server:
The ADM trap server must be an ADM partner, i.e. it must either be defined in the partner list using the address format ftadm: //host... or the address must be specified directly using the format ftadm: //host... .the transfer admission for the admission profile defined in the ADM trap server for this purpose. See section “Configuring the ADM trap server”.
In the -atp option of the ftmodo command, you specify the events on which ADM traps are to be sent to the ADM trap server:
state change of the asynchronous openFT server
Change of partner status
Unavailability of partners
Change of request management status
Successfully completed requests
Failed requests
For reasons of performance, you should restrict the scope of the ADM traps to the necessary minimum, for instance to failed requests or the unavailability of partners. If, for example, ADM traps for all successfully completed requests are sent to the ADM trap server by several instances, this can place a heavy load on the local openFT system, the ADM trap server and the network.
Alternatively, you can also perform these actions using the openFT Explorer:
Choose Administration, Operating Parameters... to open the Traps tab.
In the ADM Trap Server group, enter the name of the ADM trap server and the transfer admission.
In the ADM column of the Type group, select the events on which ADM traps are to be sent.