Page History
...
The grouping settings import file is structured as follows:
<grouping>
<group name="<name>" technology="<technology code>" entity="<entity code>" proxy_alias="<Framework node alias>">
<identifier name="<identifier string>" />
1...N
</group>
1...N
...
</grouping>
The following is an example of a grouping settings import file:
<grouping>
<group name="OA Users" technology="OA" entity="U" proxy_alias="win-1">
<identifier name="admin" />
<identifier name="visitor" />
<identifier name="operations" />
</group>
...
</grouping>
The following table describes the elements of the grouping settings import file.
Table 7-4 Elements 4 Elements of the grouping settings import fileElement Description
| Element | Description |
|---|---|
| Group |
...
| name | The name of the group. May not exceed 20 characters. |
| Group |
...
| technology | The technology code of the group. To find a valid code, see Table 7-5 on page 103. |
| Group |
...
| entity | The entity code of the corresponding technology. To find a valid code, see Table 7-5 on page 103. |
| Identifier |
...
| name | The identifier text associated with the group. Full string and % wildcard characters allowed. |
| Group proxy_ |
...
| alias | The alias name of the warehouse system the Group is assigned to. '*' indicates all warehouse systems. |
The following table shows how the different grouping technologies can be mapped to entities.
Table 7-5 Mapping 5 Mapping grouping technologies to entities
| Technology name | Technology |
|---|
...
SAP SP Transactions A
SAP SP Application Servers P
SAP SP Servers S
Web WW URLs A
Web WW Transactions P_T
Web WW SAP Titles P_ST
Web WW Siebel Titles P_ST
Web WW PeopleSoft Panels P_PG
Web WW Servers S
Web WW Instances I
Web WW Pages BT
Web WW URL File Extensions UE
Web WW Domains SI
...
| code | Entity name | Entity code | |
|---|---|---|---|
| SAP | SP | Transactions | A |
| SAP | SP | Application Servers | P |
| SAP | SP | Servers | S |
| Web | WW | URLs | A |
| Web | WW | Transactions | P_T |
| Web | WW | SAP Titles | P_ST |
| Web | WW | Siebel Titles | P_ST |
| Web | WW | PeopleSoft Panels | P_PG |
| Web | WW | Servers | S |
| Web | WW | Instances | I |
| Web | WW | Pages | BT |
| Web | WW | URL File Extentions | UE |
| Web | WW | Domains | SI |
| Web | WW | Page Siebel Views | PV |
About the SLA settings import file
The SLA settings import file is structured as follows:
<slas>
<sla name="<sla name>" entity="<entity code>" technology="<technology code>"
sla-type="<sla type>" activity-type="<activity type>" application="<application name>" red="<breach threshold>"
yellow="< breach threshold >" proxy_alias="<Framework node alias>">
<identifier name="<identifier string>" />
<identifier name="<identifier string>" />
</sla>
</slas>
The following is an example of an SLA settings import file:
<slas>
<sla name="Tuxedo default SLA" entity="A" technology="TU" sla-type="S" activity-type="" application="" red="5000" yellow="2000" proxy_alias="win-1">
<identifier name="%PAP" />
<identifier name="APP%" />
</sla>
</slas>
The following table describes the elements of the SLA settings import file.
Table 7-6 Elements 6 Elements of the SLA settings import file
| Element |
|---|
...
| Description |
|---|
| SLA |
...
| name | The name of the SLA. May not exceed 20 characters. |
| SLA |
...
| technology | The technology code of the SLA. To find a valid code, see Table 7-7 on page 104. |
| SLA |
...
| entity | The entity code of the corresponding technology. To find a valid code, see Table 7-7 on page 104. |
| SLA |
...
| Type | Either service time (S) or response time (R). To find the corresponding type for each technology, see Table 7-7 on page 104. |
| SLA proxy_ |
...
| alias | The alias name of the warehouse system the SLA is assigned to. '*' indicates all warehouse systems. |
The following table shows how the different SLA technologies can be mapped to entities.
Table 7-7 Mapping 7 Mapping SLA technologies to entities
| SLA |
|---|
...
| type | Technology name | Technology code | Entity name | Entity code |
|---|---|---|---|---|
| Service time | Microsoft .NET | DN | Servers | S |
| Service time | J2EE | JE | Servers | A |
| Service time | Oracle | OR | Program | P |
| Service time | Oracle Applications | OA | Forms | A |
| Service time | Other | OT | Tiers | A |
| Service time | SQL Server | SQ | Programs | P |
| Service time | Tuxedo | TU | Services | A |
| Service time | WebSphere MQ | MQ | Reader Applications | GA |
| Service time | Web (server) | WW | URLs | A |
| Response time | SAP | SP | Transactions | A |
| Response time | Web (client) | WW | Pages | A1 |
Service time Microsoft .NET DN Servers S
Service time J2EE JE Servers A
Service time Oracle OR Program P
Service time Oracle Applications OA Forms A
Service time Other OT Tiers A
Service time SQL Server SQ Programs P
Service time Tuxedo TU Services A
Service time WebSphere MQ MQ Reader Applications GA
Service time Web (server) WW URLs A
Response time SAP SP Transactions A
Response time Web (client) WW Pages A1
...
Precise. Performance intelligence from click to storage. Learn more > >
...