FileNet P8 Process Engine, Version 5.0.+              

Verifying that all Process Engine 3.5 events have been transmitted to Case Analyzer

The steps in this procedure apply only if you are using a production Case Analyzer, they are not necessary for a simulation Case Analyzer.

The Case Analyzer gets its data from the Process Engine database. All generated events must be transmitted from Process Engine to Case Analyzer before the upgrade. The following steps must be taken to verify that transmission is complete. Some of these steps must be taken on the Process Engine database, some on the Process Engine server by using the vwtool utility, and some on the Case Analyzer VMAEDM database.

You will query the Case Analyzer VMAEDM database for a date/time value. Date/time values are stored in the Process Engine and Case Analyzer databases in different formats. When a value has been acquired from the Case Analyzer database, you will use vwtool to convert the value to the appropriate format for the Process Engine database. You will then run a query on the Process Engine database by using the converted date/time value as one parameter in the SQL query.

To verify that all Process Engine 3.5 events have been transmitted to Case Analyzer 3.5:
  1. Stop Process Engine applications. These applications include any applications that are generating events or running workflows.
  2. Keep both Process Engine and Case Analyzer running until all the events from Process Engine are transmitted to Case Analyzer.
  3. Complete the following sub-steps to acquire a date/time value from the Case Analyzer database and convert it to an appropriate format for the Process Engine database.
    1. On the Case Analyzer VMAEDM database, run the following SQL query:
      select InstallDate from X_SchemaInfo

      This returns a date and time string, such as 09/11/2006 16:23:59. This string must be converted.

    2. On the Process Engine server, start the vwtool utility to convert the Case Analyzer data/time string to Process Engine format.
    3. Enter the following at the vwtool prompt:
      convert
      Then press Enter. The following choice list displays:

      t - Time number to string
      s - String to time number
      e - Error tuple to three part
      p - Three part error to error tuple
      l - Log event type number to string
      i - User id to user name
      n - User name to user id

    4. At the Choice? prompt, enter: s

      and press Enter. This converts a string to a time number and returns the following information to indicate what the current date/time mask is, as in:

      Current System Mask: mm/dd.yyy hh:tt:ss

      Time Mask (CR=system mask):

    5. Press Enter to accept the default mask.
    6. When prompted to enter the time string (CR="), type the value that was returned from the SQL query ran on Case Analyzer VMAEDM in 3.a. (for example, 09/11/2006 16:23:59). Your input must match the format of the current system mask from 3.d above. Then press Enter .

      A string value is returned for the date/time entered, which you must make note of for the next set of queries. For example:

      Time...[0x4505F00F].........................1158017039 => '09/11/2006 16:23:59'

    7. Get a list of all regions on the disk by typing the following at a vwtool prompt:
      regions
    8. When prompted, respond by typing:
      d
    9. For every region, type the following at a vwtool prompt:
      reg X

      where X is the region number

    10. Type the following at the vwtool prompt:
      config
    11. Locate and make note of the physical table name associated with every event log.
    12. On the Process Engine database, run a SQL query (such as the following example) to verify that no untransmitted events remain in the Process Engine database. You will query for the number of records in every physical table associated with event logs, by using the names you acquired in the previous step. Following is an example of the query syntax:
      Select count(*) from f_sw.physical_table_name where 
      F_AEXmitStat = 1 and F_TimeStamp > PAInstallDate

      where:

      physical_table name is the table name from 3.k.

      The PAInstallDate is the number returned in 3.f.

    Note that the physical table name must be preceeded by f_sw. in the query.

    The query result must be 0. If the queries do not return 0, not all events have been collected, in which case Process Engine and Case Analyzer must keep running until all the events are transmitted and the queries return 0.



Feedback

Last updated: November 2010


© Copyright IBM Corporation 2010.
This information center is powered by Eclipse technology. (http://www.eclipse.org)