Avoiding JVM Delays Caused By Random Number Generation

Monitoring and Troubleshooting 8-33 3. Save your change and exit the text editor. 8-34 Oracle WebLogic Communications Server Administration Guide Part II Part II Configuring Presence This Part contains the following chapter: ■ Chapter 9, Configuring Presence and Presence Web Services 9 Configuring Presence and Presence Web Services 9-1 9 Configuring Presence and Presence Web Services This chapter provides an introduction to the Oracle WebLogic Communication Services OWLCS in the following sections: ■ Section 9.1, Overview of Presence ■ Section 9.2, Configuring Presence ■ Section 9.3, Configuring Presence Web Services

9.1 Overview of Presence

Presence may be used to display an end-user’s availability and ability to participate in a chat or richer multimedia interaction. Client presence is often represented as a contact management list, which displays user availability as icons. These icons, which not only represent a user’s availability, but also a user’s location, means of contact, or current activity, enable efficient communications between users. The Presence application enables a service provider or an enterprise to extend presence service to end users. Major capabilities include: ■ Presence Status Publication ■ Presence Status Subscriptions ■ Privacy ■ Presence Hard State Presence Status Publication The term presentity is used here to refer to a Presence Entity a Presence Entity [presentity] is an entity, such as a person, who is defined by their ability and willingness to communicate. A presentity can publish a Presence Information Data Format PIDF document containing presence state to the Presence Server. Presence Status Subscriptions The Presence Server supports subscriptions to a presentity’s that is, a user’s status. The Presence Server supports the watcher information event package. This event package allows a presentity to be notified as soon as a watcher has subscribed to hisher presence state. The Presence Server notifies the user when the watcher subscriber requests authorization to view the presentity’s status. The Presence server also notifies all of the active, authorized watchers of the publication of a new presence document. 9-2 Oracle WebLogic Communications Server Administration Guide Privacy A presentity can create filtering rules allowing certain watchers to only see certain parts of the presence states. Whenever a watcher subscribes to a presentity’s presence, the Presence Server checks the authorization policy that the presentity has set to see if the watcher has the required authorization. If no matching rule can be found, the watcher is put in a pending state and a watcher info notification is sent to the presentity. Usually, the presentity’s client User Agent presents a pop-up box asking whether to accept or reject a new pending watcher. The answer is added to the presentity’s authorization policy document in the form of a rule for this watcher. The document is then updated by the client on the XDMS using HTTP. When the document is updated, the Presence Server reads the new policy document and acts on the new rule, changing the subscription state accordingly. Presence Hard State A presentity can leave a hard state note about their presence such as when going on vacation: On vacation - back on the 15th. Watchers to this presentitys presence state would be able to see this information.

9.2 Configuring Presence

Configuration of the Presence Server is done through the following MBeans: ■ Section 9.2.1, Configuring XDMS ■ Section 9.2.2, Bus ■ Section 9.2.3, PackageManager ■ Section 9.2.4, Presence ■ Section 9.2.5, PresenceEventPackage ■ Section 9.2.6, PresenceWInfoEventPackage ■ Section 9.2.7, UA-ProfileEventPackage ■ Section 9.2.8, Command Service XDMS Provisioning ■ Section 9.2.9, XCapConfigManager ■ Section 9.2.10, Aggregation Proxy ■ Section 9.2.11, Configuring Default Application Router for OPTIONS

9.2.1 Configuring XDMS

The following MBeans enables you to configure the XDMS XML Document Management Server: ■ Command Service XDMS Provisioning ■ XCapConfigManager Configuring Presence and Presence Web Services 9-3

9.2.2 Bus

Through the Bus MBean you can configure the internal asynchronous bus that the Presence Server is using for its internal job execution. Table 9–1 describes the attributes of the Bus MBean.

9.2.3 PackageManager

The PresenceEventPackage , PresenceWInfoEventPackage , and UA-ProfileEventPackage MBeans enable you to configure the event packages, which define the state information to be reported by a notifier to a watcher subscriber. Note: If you change any attributes of the following MBeans, you must restart OWLCS for these changes to take effect. ■ Presence ■ PresenceEventPackage ■ PresenceWInfoEventPackage ■ UAProfileEventPackage ■ XCapConfigManager Note: JGroups channels must only communicate with their intended peers. To ensure that event packages use JGroups correctly, different channels must use different values for the group name, multicast address and multicast port. See http:www.jboss.org for more information. Table 9–1 Attributes of the Bus MBean Attribute Value Type Description ThreadPoolSize int The number of threads held in the thread pool, which remains constant throughout the lifetime of the application. If no threads are used, then the specified number of threads remain idle. The default value is 15. HighWatermark int The number of pending jobs reached before the bus’s exhausted threshold level is reached. The default value is 20. KeepAlive long The number of seconds to keep an idle thread alive before dropping it. The default value is 60. LogDuration long A warning is logged to the system log for events that remain in the queue for a period exceeding the specified duration before they are broadcast to the bus. This warning indicates that server is about to be overloaded, since an old job has been sent to the bus. The default value is 60. LowWatermark int Specifies the low threshold level for the number of pending jobs. When this threshold is reached from below, the Bus logs a warning that it is about to be choked. At this point, no more warnings are logged until the high watermark level is reached. The default value is 15.