Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Components of a Sample Use Case

 

Each use case can be considered as a collection of work done by the components of 64-bit version of standalone SBR Carrier, in terms of CPU, memory, and total transactions.

Table 36 shows the breakdown of use case tasks done by the SBR Carrier components.

Table 36: Use Cases Performed on a Standalone SBR Carrier

Task Execution Sequence

Subtasks

Description

Native

  1. SBR Carrier validates user credentials against the native user database.

  2. Local accounting is used for all accounting transactions.

SBR Carrier performs native user transactions under the following load scenarios:

  • PAP Authentication Only

  • Accounting Start Only

  • PAP Authentication, Accounting Start and Accounting Stop

SQL

  1. SBR Carrier validates user credentials against a SQL database.

  2. SBR Carrier returns Accept/Reject based on the response received from the SQL database server (any SQL database supported by JDBC) database.

  3. Local accounting (not SQL accounting) is used for all accounting transactions.

SBR Carrier performs SQL user transactions under the following load scenarios:

  • MySQL Authentication Only

  • MySQL Authentication, Accounting Start and Accounting Stop

Note: Session information is stored locally (.hst file).

LDAP

  1. SBR Carrier validates user credentials against an LDAP database using BindName authentication.

  2. SBR Carrier returns Accept/Reject based on the query response received from the LDAP database.

  3. Local accounting is used for all accounting transactions.

SBR Carrier performs LDAP user transactions under the following load scenarios:

  • LDAP Authentication Only

  • LDAP Authentication, Accounting Start and Accounting Stop

Note: Session information is stored locally, as LDAP is used for authentication only.