Cisco Cisco Prime Collaboration Assurance 11.0 사용자 가이드
© 2012-2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 46 of 2
Syntax:
public ResponseReturn submitOrder (CUPMServiceStub stub, OrderValue order, ValidationType validationType,
RollbackType rollbackType, String endPointReference, String idPrefix);
Parameters:
• order—Creates a work order that is submitted to Prime Collaboration Provisioning if the NBI request is
accepted. The order is never a prospect work order in Prime Collaboration Provisioning.
• validationType—ENUM as to whether a work order should be validated before being submitted. Values
are VALIDATE_ONLY, SUBMIT_ONLY, VALIDATE_AND_SUBMIT.
• rollbackType—ENUM describing how the order should be rolled back if it fails. Value is PARTIAL.
• endPointReference—String to convert to an EndpointReference object that the asynchronous result
notification will be sent to.
• idPrefix—String added to the beginning of the numeric value generated by the server that becomes the
NBI ID. Note that in this case, the NBI ID is also used as the Order ID.
Returns:
CupmApiResponseValue—Object with NBI ID.
Throws:
SubmitOrderException—If the server cannot execute the NBI request.
ASyncReturn:
• CupmApiResultValue—Contains CupmApiStatus only.
• CupmApiFaultType—Included if the NBI request fails.
Contents of Order Object
The order object contains the order type (ADD, CHANGE, or CANCEL), and a set of service details. These values
are defined in an enumeration and they specify creating, modifying, or deleting a set of services.
The service detail object contains device name, device capability, Service Area ID, subscriber ID, Domain ID, and
a set of products.
The product object contains the product ID, a sequence number, the assocWith flag, a set of key attributes, and
product attributes. The sequence number defines the order of creation for each product, and it must be unique
among products in the same order. The assocWith flag is used for the ADD order type. If a product that is created
in one order detail needs to be associated with another product created later in the same work order, the
assocWith attribute must be specified so the service being added references back to the service already added. An
example of using assocWith is an order that contains multiple dependent products such as Phone, Line, Email,
Voicemail, and Unified Messaging Service.
Key attributes are required in CHANGE or CANCEL order types.