Cisco Cisco Prime Collaboration 10.6 User Guide

Page 78 of 2

DeviceValue device = (DeviceValue)xmlObject; DeviceDocument deviceDocument =

DeviceDocument.Factory.newInstance(); deviceDocument.setDevice(device);

// This also applies to domain, serviceArea, Subscriber, Order, InventoryItem,
Product,

// ServiceDetail, PhoneInfo, String, CupmApiFaultType, CupmApiList } else if (

nodeNameKey.equalsIgnoreCase("EnumerationContextType") ) {

// For Enumeration Object, better to use node name instead of support class so
client

// is not limited to the Axis2 implementation of Enumeration
EnumerationContextType

enumerationContext = (EnumerationContextType)xmlObject;
EnumerationContextDocument

enumerationContextDocument = EnumerationContextDocument.Factory.newInstance();

enumerationContextDocument.setEnumerationContext(enumerationContext); } else if (

typedXmlObject instanceof OrderSummaryDocument ) {

// OrderSummary comes back as a document so must used the typedXmlObject for
casting

OrderSummaryDocument orderSummaryDocument = (OrderSummaryDocument)typedXmlObject;
if ( ps

!= null ) ps.println(orderSummaryDocument.toString()); } else if ( typedXmlObject

instanceof com.cisco.cucms.cupm.nbi.v1.KeywordListDocument ) {

// KeywordList comes back as a document so must used the typedXmlObject for
casting

com.cisco.cucms.cupm.nbi.v1.KeywordListDocument keywordListDocument =

(com.cisco.cucms.cupm.nbi.v1.KeywordListDocument)typedXmlObject; if ( ps != null
)

ps.println(keywordListDocument.toString()); } else { System.out.println("WARNING
- unknown

class = " + xmlClassName + " node name = " + nodeNameKey ); } }

When I run getOrder or listOrder with a return attribute of all, some of the settings do not match the

attribute values that were passed in the initial submitOrder request.

When the order is retrieved from the Prime Collaboration Provisioning database, some settings (in particular,

boolean settings) have their internal attribute values returned.

When I create a createServiceArea request or a submitOrder request, an attribute that looks correct to

me is rejected. Why is that?

Attribute names are case sensitive. Make sure that your name exactly matches the XSD string. Also, double

check the to make sure that the attribute definition is in the right object. For example, device and device

capability are different levels in the createDevice request.

When I create a createServiceArea request with VoiceGatewayReference, the request is rejected with

message stating, “Invalid VoiceGatewayReferenceName,” but the specified VoiceGatewayReference

exists in CUPM. Why is that?

VoiceGatewayReferenceName will be considered as valid only if the Slot and Subunit properties are

configured for the VoiceGatewayReference. Ensure that the VoiceGatewayReference name you are specifying

in the request has a slot and subunit configured.