Provisioning XDMS User Accounts Using the CommandService MBean

7-10 Oracle WebLogic Communications Server Administration Guide

7.5.2 Provisioning XDMS User Accounts from the Sash Prompt

To use XDMS commands to provision users and application usages from the Sash prompt, you must first connect to an application that consumes XDMS, such as Presence. For Windows systems, enter the following from the command prompt: launch_sash.bat -a application name On Linux, enter the following: launch_sash.sh -a application name For example, to connect to the Presence application on a Windows system: 1. From the command prompt, navigate to the sbin directory that contains the Sash executable. This file is located at MIDDLEWARE_ HOMEas11gr1wlcscommunicationssashsbin. 2. Enter the name of the Presence application using sash.bat -a presenceapplication. 3. When prompted, login to Sash using your OWLCS administrator name and password. 4. From the Sash command prompt, enter an XDMS command, such as xcap user list.

7.5.3 Using xcap Commands

This section describes how to manage user accounts and application usages using the xcap group of commands.

7.5.3.1 Provisioning XDMS User Accounts

The add, delete and list commands enable you to manage user accounts on the XDMS.

7.5.3.2 Adding XDMS Users

The xcap user add command adds an XDMS user with the given user name and application usage. For example, to add a user from the Sash prompt, enter: sash xcap user add userName=string appusage=string

7.5.3.3 Removing an XDMS User

The xcap user delete command removes an XDMS user with the given user name and all existing documents from the application usage. For example, to delete a user from the Sash prompt, enter: sash xcap user delete userName=string [ appusages=string ] The application usage parameter appusages is optional. If no application usage is specified, then the user is removed from all application usages. Note: Do not use the add command if the XDMS is configured to automatically create users. For more information on configuring XCAP, see Section 9.2.9, XCapConfigManager . 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