Tracking client caches

Client cache loads are identified by the following API calls:

• ARValidateFormCache (VFC)
   Determines if a client cache load is necessary.

• ARExport (EXP)
   Represents a client cache load.
  
  To track these calls on a client, turn on client-side API logging. This debugging feature is invoked by setting ARAPILOGGING environment variables, prior to startup of the AR System client. The output will be captured in arapi.log files and can be generated from any AR System server C-API client (for more information, see Knowledge Base article ID 20009823).
  
  Client-side logging ( ARAPILOGGING=24 ) not only shows that the VFC API was called and resulted in an EXP API call, but also shows why the EXP was called. For example, it detects if the forms are out of date or the user information is modified.
  
  The following entries from a sample client-side log shows a VFC call:

  
  vfc
  Home Page
  1244591344
  1244591344
  1244591344
  1244591344
  ARValidateFormCache results
  Return Code: OK
  Form Last Changed: 1244585158
  Number Active Links: 2
  Number Changed Active Links: 0
  Changed Menu List: (0)
  Groups Last Changed: 1244585157
  User Last Changed: 1244585218
  Changed Guide List: (0)
  Status List: 0 items
  Start Time: 1244647616.159000 (Wed Jun 10 2009 08:26:56)
  Finish Time: 1244647616.174000 (Wed Jun 10 2009 08:26:56)
  Elapsed Time: 0.015000

  Note

  Server-side API logging shows VFC and EXP calls occurring across all connected clients.

  You can also examine the SQL log for instances of CREATE VIEW and ALTER TABLE.
  
  These statements indicate that someone used BMC Remedy Administrator (pre- 7.5.00), Developer Studio (7.5.00 and later), Migrator, or a custom API program to modify forms.