4.10 WEBEVENT Data and Function Timeout

It is important to understand how WEBEVENT function data is handled as it relates to the jobs being maintained by the transaction server.

A LANSA WEBEVENT function terminates as soon as it has processed a DISPLAY or REQUEST command. However, the Web job is reserved for the user, pending further interaction unless you have coded the function to terminate the job immediately.

The LANSA Web Transaction Monitor will terminate a WEBEVENT function if the timeout period has elapsed. However, if you continue to interact with this WEBEVENT function, LANSA will automatically allocate a new job for the request and handle the data interchange. Your data is still intact. (You must not use the Job Identifier as the unique identifier, as any restarted WEBEVENT functions may not be allocated to the same job at the Data/Application Server.)

When WEBEVENT functions time out, LANSA maintains the data for these jobs temporarily at the Data/Application Server. When the user interacts with these functions subsequently, the temporary data is restored and the user is not impacted – a new LANSA job has been allocated and the temporary data restored for the function.

LANSA holds the temporary data for a specified period of time. This temporary data is cleared when the inactive time of the job exceeds this purge time period. The purge period time is set in the Purge WEBEVENT function data option on the Transaction Monitor tab when you configure the Data/Application Server using the LANSA Web Administrator. If the user interacts with the function after the purge time, browse list data will not be exchanged as it has been purged. For more details, refer to the Installing LANSA on Windows Guide.

Terminating WEBEVENT Jobs Immediately

LANSA Web functions provide you with a LANSA tag, <RDML MERGE=”&END”>, to indicate that the Web job is to be freed immediately (after the DISPLAY or REQUEST command) and returned to the pool of pre-started Web jobs.

This tag should only be used for functions, which have no user interaction once the function terminates. It should not be used for functions that have a browse list, which must be exchanged with a subsequent function.

For more details, refer to Using <RDML MERGE=”&END”>.