To display roles in an application, expand the Search area, choose the application

Managing the Policy Store 9-11 ■ listResourceActions ■ createEntitlement ■ getEntitlement ■ deleteEntitlement ■ addResourceToEntitlement ■ revokeResourceFromEntitlement ■ listEntitlements ■ grantEntitlement ■ revokeEntitlement ■ listEntitlement ■ listResourceTypes ■ reassociateSecurityStore All class names specified in the above scripts must be fully qualified path names. The argument appStripe refers to the application stripe typically, identical to the application name and identifies the subset of policies pertaining to a particular application. For important information about the authenticated and the anonymous roles and WLST scripts, see Section 9.5, Granting Policies to Anonymous and Authenticated Roles with WLST Scripts. For the correct usage of the application stripe in versioned applications, see Section 9.6, Application Stripe for Versioned Applications in WLST Scripts.

9.3.1 listAppStripes

The script listAppStripes lists application stripes. This script can be run in offline or online mode. When run in offline mode, a configuration file must be passed, and it lists the application stripes in the policy store referred to by the configuration in the default context of the passed configuration file. When run in online mode, a configuration file must not be passed, and it lists stripes in the policy store of the domain to which you connect. In any mode, if a regular expression is passed, it lists the application stripes with names that match the regular expression; otherwise, it lists all application stripes. If this command is used in offline mode after reassociating to a DB-based, the configuration file produced by the reassociation must be manually edited as described in Running listAppStripes after Reassociating to a DB-Based Store . Script Mode Syntax listAppStripes.py [-configFile configFileName] [-regularExpression aRegExp] Interactive Mode Syntax listAppStripes[configFile=configFileName] [, regularExpression=aRegExp] The meanings of the arguments are as follows: ■ configFile specifies the path to the OPSS configuration file. Optional. If specified, the script runs offline; the default context in the specified configuration