To maintain the operating efficiency of WebSphere Partner Gateway, use the following procedures to archive or purge the file system and database log files.
Application log files are located in three areas: receiver, console, and router.
For example:
{INSTALL DIR}/logs/<bcgreceiver, bcgconsole, and bcgdocmgr>
To purge the application log files, follow these steps:
Non-repudiation files and directories are located in the following directory: {INSTALL DIR}/common/non_rep/. Start by archiving the oldest files located in directories starting at 0, and increasing in number for newer files.
Certain database tables may be purged when necessary, but other tables must not be modified in order to maintain proper system functionality. Tables starting with BP_ and LG_ may be purged with two exceptions: BP_ tables ending with _QUE and _HIST are continuously maintained by the RosettaNet engine and must not be changed. The BP_ tables ending with _QUE are queue tables, and the BP_ tables ending with _HIST are history tables which are used for archiving. For example, the BP_RNSTATEHDR_QUE table is archived in the BP_RNSTATEHDR_HIST table.
Tables starting with CG_ and PR_ contain configuration or profile data and must also remain unchanged for the system to function properly.
The criterion for purging table data is based upon the number of days that data must be kept online. Data in tables that end with _Hist are archived and purged on a daily basis. Also, any log information is truncated daily.
The purge criterion contains only one input parameter, p_days, which is the number of days that data should be kept online.
Table | History table | Action |
---|---|---|
RosettaNet |
||
BP_rnStateHdr |
BP_rnStateHdr_Hist |
Purge |
BP_rnStateDtl |
BP_rnStateDtl_Hist |
Purge |
BP_Sponsor_State |
BP_Sponsor_State_Hist |
Purge |
BP_rnStateHdrAuditLog |
none |
Truncate |
AS1/AS2 |
||
BP_State_Hdr |
BP_State_Hdr_Hist |
Purge |
BP_AS_State_Hdr |
BP_AS_State_Hdr_Hist |
Purge |
BP_AS_State_Dtl |
BP_AS_State_Dtl_Hist |
Purge |
The procedure purges data based upon the combination of the record creation date in the header and the p_days input parameter. The Time to perform TPA stored in the header is not considered. It is the responsibility of the DBA to make sure that the p_days parameter is larger than the maximum value of (Time to perform/1440). Time to perform is stored in minutes.
It is recommended that data in the BP_ tables be retained online for p_days or ((TimeToPerform/1440) +1 day), whichever is greater. Data in tables BP_DupCheck and BP_RnMsgDigest should be retained for seven days. Data in BP_Process_Log should be retained for two days.
Tables with names starting with DB, except DB_ProcAuditLog, are metadata tables. If DB_ProcAuditLog is on, it should be either purged or truncated daily, or done based on the needs of the user. This log is normally turned off for production because it is primarily used in development and QA environments.
With the exception of: LG_EventCd, LG_Media, and LG_media_Cfg, tables with names starting with LG_ are log and summary tables. These are metadata tables and must remain unchanged in order to maintain proper system functionality. Tables starting with LG_Access_ are no longer used by WebSphere Partner Gateway.
The following log tables can be archived and purged based upon Activity ID, and the driving table should be LG_Activity. The createdate or RcvDocTS can be used to determine the number of days that data should be retained online. RcvDocTS may be a better option because it is an indexed column. Data can remain online for seven days or ((TimeToPerform/1440) +1 day), whichever is greater.
The following log tables can be purged based on creation date.
The following summary tables must remain unchanged in order to maintain proper system functionality.