Wildcards

Session-level policies and the SR language support wildcards:

% matches zero or more characters
? matches a single character

The % wildcard is slower than the ? wildcard.

Wildcards are allowed for the following parameters:

Groups
Session-level criteria
Search pattern (SEARCH_PATTERN)
Search prefix (SEARCH_PREFIX)
Tuples

This example has the following rule and rule actions, and uses wildcards for session-level criteria.

Session level criteria
- Database type = ORA%
- Database user = ?SCOTTt%
- Client host name = rh7u6x64t.%
Rule action
1. TRANSFORM SOURCE PROGRAM NAME
  - Source = SOURCE PROGRAM NAME
  - Search prefix = SQL PLUS
  - Output format = PEREL_PROGRAM
2. DISCARD SESION
  1. Request type = SQL
  2. Search prefix = SYSTEM

SR Language example:

SR_POLICIES
{
        IF (DB_TYPE = 'ORA%' DB_USER = '?COTT%' CLIENT_HOST_NAME = 'rh7u6x64t.%')
        {
                TRANSFORM_SOURCE_PROGRAM SEARCH_PREFIX = 'SQLPLUS' OUTPUT_FORMAT = 'PEREL_PROGRAM'
                DISCARD_SESSION REQ_TYPE = SQL SEARCH_PATTERN = 'SYSTEM'
        }
}

The following values match:

DB_TYPE matches ORACLE
DB_USER matches SCOTT
CLIENT_HOST_NAME matches rh7u6x64t.domain.name.com