KB 025 – SP08 Release Notes

SPO8 Release Notes

Release Notes 4.08

Core changes to support fully dynamic metric types;
New IDOC extractor which supports data with dynamic structure;

The data sent to Splunk has the following structure:

Event TypeEvent SubtypeDescription
BD87IDOC header entry (EDDC)
BD87SGFVIDOC segment values (dynamic structure, EDID4)
BD87SGLGIDOC status entries (EDIDS)

Current constraints:

Segment fields which have the same field name as ones from the EDID4 table cannot be extracted, they are DOCNUM, COUNTER, SEGNUM, SEGNAM, PSGNUM, HLEVEL, DTINT2.

New Table reader extractor which supports data with dynamic structure, enhanced Filter Maintenance Dialog;

The dynamic data will be extracted according to the field list indicated in the Extractor Filter config. Currently Filter maintenance dialog has the following structure:

SP08 release note

Wildcards could be used as well.

Change Doc extractor: actual table records are sent to Splunk instead of CDPOS values;
The data from actual table could be read using two ways:

  1. The table key is read from the CDPOS table –in this case CDPOS table is read for each CDHDR record. Then CDPOS table key field is used to select the record from actual table;‘SelectType’=’CDPOS table’ should be indicated in the filter maintenance dialog to use this approach.
  2. The select key is CDHDR-OBJECTID field. If ‘KeyField’ is maintained on the table level, all records where indicated field equals CDHDR-OBJECTID will be selected, otherwise the first table key field will be used to compare with CDHDR-OBJECTID. In this case multiply records could be selected;SelectType = ’Key Field’should be indicated in the filter maintenance dialog to use this approach;

Change document extractor filter maintenance dialog:

SP08 release note

On the dialog header level wildcards are supported in the ‘Change doc. Object’ and ‘Transaction code’ fields.

In order to setup selection based on CDHDR-OBJECTID following steps should be performed:

  1. Fill in header level details and set ‘SelectType’ = ‘Key field’;
  2. On the ‘Tables to select from’level list of tables should be defined:
    SP08 release note
    Wildcards in ‘Table Name’ field is not supported in this case.Key field name could contain the value of the field that will be compared with CDHDR-OBJECTID during select or be empty, which means the first key field will be used for selection.‘Is Master’ flag should be set in case the result should be joined and sent to Splunk incorporated; in this case all non master tables will be joined with master ones.
    ‘Active’ flag is used to control whether this option should be considered by the extractor.
  3. For each table field list should be defined in the ‘Field values to get’ level:
    SP08 release note
    Wildcards are supported

In order to setup selection based on CDPOS table following steps should be performed:

  1. Fill in header level details and set ‘SelectType’ = ‘CDPOS table;
  2. On the ‘Tables to select from’ level list of tables should be defined like on the screen above.However the join is not supported, thus fields ‘Key Field Name’ and ‘Is Master’ is not considered by the extractor.
  3. For each table field list should be defined in the ‘Field values to get’ level.

Constraints:

Table fields with following names could not selected:TIMESTAMP ,OBJECTCLAS ,OBJECTID ,CHANGENR ,TCODE ,FLTNAME ,TABNAME , since they are used for technical information.

New logic in SM37 extractor, enhanced Filter Maintenance Dialog;Currently jobs started after last run time or completed after last run time are sent to Splunk.Additional field with job log has been added. The log is collected according to the setup done in the Administrator->Setup Metric->SM37 job filter.

SP08 release note

There are two possible options: collect log for Finished jobs or/and for Cancelled ones.

– Distribution jobs renamed to /BNWVS/* format;
– Metric serialization performance improvements;
– Filters for STAD extractor

By default, all STAD entries are extracted. However, it’s possible to limit the entries that get
extracted in two ways.

  1. By task type
    Goto Administrator->Setup metric->Metric configuration, two metric parameters can be specified to include/exclude task type

    • INCLUDE_TASK_TYPE
      This parameter is used to specify specific task types to extract. Please note that task
      types that have not been specified will not be extracted.
      Please populate this parameter with comma separated task types.
    • EXCLUDE_TASK_TYPE
      This parameter is used to specify task types to exclude.
      Please populate this parameter with comma separated task types.
  2. Exclude by application server, program, username, task type or transaction code Goto Administrator->Setup Metric->STAD filter

    For example: if RFC entries are not needed, populate

    • Counter: populate with unique number
    • Task Type: R
    • Other fields: populate with *

SP08 release note

Filter by task type is applied before exclusion filter.

– SOST extractor filter

Filters need to be specified beforethe new extractor extracts any data.
Combination of fields from table SOOS, SOES, SOST and SOOD
The format of the field is <field name>_<table name>.

For example:

  • If only transmitted requests should be extracted, following fields need to be specified
SOST Field NameCounterInclude / ExcludeOptionLowHigh
MSGNO_SOST1IEQ701
MSGNO_SOST2IEQ702
MSGNO_SOST3IEQ073
MSGNO_SOST4IEQ723
MSGID_SOST1IEQXS
  • If only requests with certain subject should be extracted, the following fields need to be specified.
SOST Field NameCounterInclude / ExcludeOptionLowHigh
OBJDES_SOOD1ICP**

– CPU usage has been appended to SM51 metric;
– LOGS extractor backward compatibility
Parameter rdisp/workdircannot have valuemore than 60 characters long.

Download PDF version here