Launching Sash from the Command Line

7-2 Oracle WebLogic Communications Server Administration Guide

7.2.2 Connecting Sash to an External OWLCS Instance

By default, Sash connects to the local instance of OWLCS. If needed, you can override this default behavior and connect Sash to external instances of OWLCS or to another instance of Oracle WebLogic Server.

7.2.2.1 Connecting to an External Instance of OWLCS

Sash connects to the OWLCS server through RMI. Example 7–1 illustrates how to connect Sash to a server with the host IP address 10.0.0.234. Example 7–1 Connecting Sash to OWLCS sash –-host 10.0.0.234 When you connect to OWLCS, Sash prompts you for a username and a password. The user name is the same as that for OWLCS administrator OWLCSadmin. The password is the same as the password associated with the OWLCS administrator. Once you log in, the Sash command prompt sash appears. An error message displays if the login is unsuccessful.

7.3 Using Sash

There are two groups of Sash commands: commands that create, delete and update system objects and commands that query the system for information.

7.3.1 Viewing Available Commands

Entering help displays a list of all available commands in the server described in Table 7–1 . The list of commands varies depending on the components deployed to the server. Note: Whenever a user adds a new application usage, they must restart the server before the new application usage is available. Whenever a user deletes an existing application usage, they must restart the server for the deleted application usage to be completely unloaded that is, a deleted application usage will remain loaded until the server is restarted, when it is unloaded and is then completely unavailable. If a space precedes a sash command in a file, and then that file is used as input to the sash command, it does not work. Ensure that you remove any preceding spaces in sash commands in sash input files. Provisioning Users With Sash 7-3 Table 7–1 Sash Commands Command Description Aliases Subcommands privateIdentity Commands for adding and removing private communication identities used for authentication. None Subcommands include: ■ add – Adds a new user to the system. For example: privateIdentity add privateId=alice ■ delete – Removes a user from the system. For example: privateIdentity delete privateId=alice publicIdentity Commands for adding and removing public identities associated with a private identity. pubid Subcommands include: ■ add – Adds a public identity to the system which is associated with a particular user. For example: publicIdentity add publicId=sip:alicetest.company.com privateId=alice ■ delete – Deletes a communication identity from the system. For example: publicIdentity delete publicId=sip:alicetest.company.com privateId=alice account Contains commands for managing user accounts. This command enables you to set the account as active, locked, or as a temporary account. None Subcommands include: ■ add – adds a new account to the system. The syntax is as follows: account add uid=string [active=true|false] [locked=true|false] [accountExpiresAt=accountExpiresAt] [tempAccount=true|false] [description=string] [lockExpiresAt=lockExpiresAt] [currentFailedLogins=integer] For example: account add uid=alice active=true ■ delete – Deletes an account from the system. For example: account delete uid=string ■ update – Updates an account. For example: account update uid=string [active=true|false] [locked=true|false] [accountExpiresAt=accountExpiresAt] [tempAccount=true|false] [description=string] [lockExpiresAt=lockExpiresAt] [currentFailedLogins=integer] ■ info – Retrieves information for a specific account. For example: account info uid=string