Removing an XDMS User

Provisioning Users With Sash 7-11

7.5.3.4 Searching for Application Usage for an XDMS User

The xcap user appusages command returns all the application usages applicable to a given user. To review the application usages assigned to a user, enter the following from the Sash prompt: sash xcap user appusages userName=string

7.5.3.5 Listing XDMS Users

The xcap user list command returns all of the XDMS users in the system, or optionally returns the XDMS users for a given application usage. sash xcap user list [ all=true|false ] [ appusage=string ] If the optional all parameter is not set, then the resulting display is limited to a maximum of 100 users.

7.5.3.6 Provisioning Application Usage

The commands for provisioning of XDMS application usage are in the appusage group xcap appusage. Three types of applications are supported: resource-lists_au.xml, pidfmanipulation_au.xml and presrules_ au.xml. The SASH command for adding application usage is: xcap appusage create appusage=application_usage configurationFilename=application_au.xml Three types of applications are supported as shown in.

7.5.3.7 Listing All Application Usages

The xcap appusage list command returns all the application usages on the server. For example, enter the following from the Sash prompt: sash xcap appusage list

7.6 Scripting with Sash

You can construct scripts for common tasks that contain several operations. Sash can be evoked to execute a file containing a list of commands. To enable scripting, Sash provides such command-line flags as: ■ -- exec short name: -e: When this command-line flag is followed by a command enclosed within quotation marks, Sash executes the command and then exits. ■ -- file short name: -f: When this command-line flag is followed by a filename, Sash reads the file and executes all commands in the file as they were entered and then exits. Table 7–2 Supported Application Types applicationUsage configurationFilename resource-lists resource-lists_au.xml pidf-manipulation pidfmanipulation_au.xml pres-rules presrules_au.xml 7-12 Oracle WebLogic Communications Server Administration Guide Example 7–4 illustrates a text file called ocsm_users.txt, which contains a group of users defined with the identity add command. You can provision these users by entering -f OWLCS_users.txt from the Sash prompt: Example 7–4 Creating Users from a Text File OWLCS_users.txt identity add privateId=candace publicId=sip:candacedoc.oracle.com role=user password=1234 realm=doc.oracle.com identity add privateId=deirdre publicId=sip:deirdredoc.oracle.com role=user password=1234 realm=doc.oracle.com identity add privateId=evelyn publicId=sip:evelyndoc.oracle.com role=user password=1234 realm=doc.oracle.com identity add privateId=frank publicId=sip:frankdoc.oracle.com role=user password=1234 realm=doc.oracle.com ■ -- nonewline: This command-line flag facilitates parsing output by stripping returns or newlines from the messages returned from the executed commands. Although this command facilitates parsing, it makes reading messages manually more difficult.

7.7 Error Logging in Sash

Sash does not log to any files with the default configuration, it only prints messages on the console. The log level for Sash is configured in ORACLE _ HOMEas11gr1wlcs1communicationssashconf.