Cisco Cisco Prime Collaboration 10.5 User Guide

 

 

© 2012-2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. 

Page 61 of 2 

Returns the current expiration date. 

releaseOp Java Signature 

Tells the server that the client is done with the data and it may be purged. 

public ResponseReturn release (CUPMServiceStub stub, wsen:EnumerationContext enumerationContext); 

wsen:EnumerationContext—The latest version of this object that the client has received from the server. 

Returns: 

WS-Enumeration standard Release response message. 

Throws: 

RemoteException—If the server cannot execute the NBI request. 

SyncReturn: 

A response with no parameters. 

Prime Collaboration Provisioning NBI Implementation of WS-Notification 

A Prime Collaboration Provisioning client submits an NBI request to the Prime Collaboration Provisioning server. 

The two platforms are Web Services peers. The client is a NotificationConsumer and is subscribed to the Web 

Services resource that is the Prime Collaboration Provisioning server. The Prime Collaboration Provisioning server 

is a NotificationProducer. It has only one topic and is viewed as only one Web Services resource. When the Prime 

Collaboration Provisioning server completes the NBI request, it will publish a notification with the NBI request 

results. As each client subscribes to the server, a filter is implemented such that when the Prime Collaboration 

Provisioning server publishes the NBI request result notification, only the client that submitted that NBI request will 

receive the response. There is a one-to-one relationship between NBI requests accepted by the server and NBI 

request result notifications sent to the client. 

There are no cases where the Prime Collaboration Provisioning server will send a message to the client 

unsolicited. 

Notification Consumer Service 

The Prime Collaboration Provisioning NBI SDK provides a notification consumer service to receive the request 

notifications. The notification consumer service is written in Java and designed to be deployed in an axis2.war file, 

running under Tomcat.  

The default functionality for this service is to receive the notification on port 8080 and display the notification in the 

Tomcat console window.