Oracle Server E10293-02 Benutzerhandbuch
Installing the Web Services
6-2 Oracle Communication and Mobility Server Developer’s Guide
Installing the Web Services
The Web services are packaged as a standard .ear file and can be deployed the same as
any other Web services through Enterprise Manager. The .ear file contains two .war
files that implement the two interfaces. If the Web services are deployed on the same
server as the presence server, they must be a child application of the Presence server.
any other Web services through Enterprise Manager. The .ear file contains two .war
files that implement the two interfaces. If the Web services are deployed on the same
server as the presence server, they must be a child application of the Presence server.
Installing the Aggregation Proxy
The aggregation proxy is packaged as a standard .ear file and can be deployed
through Enterprise Manager. There are two requirements:
through Enterprise Manager. There are two requirements:
■
The application name must be "aggregationproxyear".
■
The parent application must be "subscriberdataservices". The aggregation proxy
uses the authentication functions of subscriberdataservices to authenticate Web
services.
uses the authentication functions of subscriberdataservices to authenticate Web
services.
Configuring Web Services with the Aggregation Proxy
The Web services operate within a trusted domain where another entity performs
authentication. To authenticate Web services and identify the user of the services,
OCMS uses the aggregation proxy to insert the HTTP X-3GPP-ASSERTED-IDENTITY
header as defined in 3GPP TS 33.222 Generic Authentication Architecture (GAA); Access
to network application functions using Hypertext Transfer Protocol over Transport Layer
Security (HTTPS).
authentication. To authenticate Web services and identify the user of the services,
OCMS uses the aggregation proxy to insert the HTTP X-3GPP-ASSERTED-IDENTITY
header as defined in 3GPP TS 33.222 Generic Authentication Architecture (GAA); Access
to network application functions using Hypertext Transfer Protocol over Transport Layer
Security (HTTPS).
To define a Web services deployment server:
1.
Open the Enterprise Manager page for the aggregation proxy.
2.
Configure the WebServiceHost and WebServicePort to the host and port of the Web
services deployment server.
services deployment server.
3.
Configure the XCAPHost, XCAPPort, and XCAPRoot to the location and
parameters of the XDMS.
parameters of the XDMS.
Presence Web Services Interface Descriptions
The presence Web services consist of three interfaces:
■
PresenceConsumer: The watchers use these methods to obtain presence data
(
(
).
■
PresenceNotification: The presence consumer interface uses the client callback
defined in this interface to send notifications. OCMS does not currently support
PresenceNotification (
defined in this interface to send notifications. OCMS does not currently support
PresenceNotification (
■
PresenceSupplier: The presentity uses these methods to supply presence data and
manage access to the data by its watchers (
manage access to the data by its watchers (
Table 6–1 PresenceConsumer Interface
Operation
Description
subscribePresence
The Web Services send a SUBSCRIBE to the presence server.
getUserPresence
Returns the cached presence status because the status
changes of the presentity are asynchronously sent to the Web
services through a SIP NOTIFY. The Web services actually
have the subscription, not the Web services client.
changes of the presentity are asynchronously sent to the Web
services through a SIP NOTIFY. The Web services actually
have the subscription, not the Web services client.