ASAP 2.7 Extension Manual

Configuring the ASAP Extension
HP NonStop ASAP Extension Manual—425265-004
2-5
Custom Entity Properties
2. Change the entity name in the EDL entity statement from APP to the name of your
entity.
3. Change the command entity property from APP\*,RAW,TAB,STATE,AGGREGATE
to one of these commands, depending on the number of monitored domains and
whether you are using aggregation:
APP\*entity, DETAIL,RAW,TAB,STATE,AGGREGATE
APP\*entity, DETAIL,RAW,TAB,STATE,AGGREGATEONLY
For large domain populations, AGGREGATEONLY dramatically reduces data flow
to ASAP Client.
4. Add a new Entity DETAIL statement to the entity definition. For example:
APP ^, DE,TAB,ST,AGG,MIN,COUNT 25
If SET AGGREGATE ONLY is defined for an entity so that detail records are not
being written to the database, add the MEMORY option:
APP ^, DE,TAB,ST,AGG,MIN,MEM,COUNT 25
5. Add a new Entity DataItems statement to the entity definition. For example:
DataItems “0 I, 1 S, 2 U”
For more information, see Configuring DataItems and Metrics on page 2-8.
6. Change the help text in the Entity Help statement.
7. Modify the MaxObjectives statement value if necessary. It defines the maximum
number of objective records for the entity.
8. Change the Version statement value.
9. Add custom attribute definitions in your EDL file after the last line in the file (the
ErrorState associated state definition). The maximum number of custom attributes
is 30.
10. Add an associated state for each attribute.
11. Compile and save your new EDL file.
12. Transfer your new EDL file to each NonStop server running ASAP.
13. Modify the ASAPUSER file on all NonStop servers to load your new EDL file.
14. Restart all parts of ASAP, including ASAP Client sessions.
Note. It is important to use option abbreviations like DE for DETAIL since the domain
name insertion (^) can introduce up to 64 addition bytes to the command string.
Note. Do not change any other Entity statements aside from what this procedure has
instructed.