Cisco Cisco Prime Network Services Controller 3.0 Guide Du Développeur
Page 19
OL-28369-01
The response includes the following details:
<configResolveDn
dn="org-root/org-tenant_d3337/pol-p1"
cookie="<real_cookie>"
commCookie="7/13/0/a3c"
srcExtSys="10.193.34.70"
destExtSys="10.193.34.70"
srcSvc="sam_extXMLApi"
destSvc="policy-mgr_dme"
response="yes">
<outConfig>
cookie="<real_cookie>"
commCookie="7/13/0/a3c"
srcExtSys="10.193.34.70"
destExtSys="10.193.34.70"
srcSvc="sam_extXMLApi"
destSvc="policy-mgr_dme"
response="yes">
<outConfig>
<policyRuleBasedPolicy
descr=""
dn="org-root/org-tenant_d3337/pol-p1"
intId="10811"
name="p1"/>
dn="org-root/org-tenant_d3337/pol-p1"
intId="10811"
name="p1"/>
</outConfig>
</configResolveDn></configResolveDn>
Failure Responses
Responses to failed requests include XML attributes for errorCode and errorDescr. The following example shows
the response to a failed request that tried to create a policy with the same name as another policy already in the
system:
the response to a failed request that tried to create a policy with the same name as another policy already in the
system:
<configConfMo
dn="org-root/org-tenant_d3337/pol-p1"
cookie="<real_cookie>"
commCookie="7/13/0/2038"
srcExtSys="10.193.34.70"
destExtSys="10.193.34.70"
srcSvc="sam_extXMLApi"
destSvc="policy-mgr_dme"
response="yes"
errorCode="103"
invocationResult="unidentified-fail"
errorDescr="can't create; object already exists.">
cookie="<real_cookie>"
commCookie="7/13/0/2038"
srcExtSys="10.193.34.70"
destExtSys="10.193.34.70"
srcSvc="sam_extXMLApi"
destSvc="policy-mgr_dme"
response="yes"
errorCode="103"
invocationResult="unidentified-fail"
errorDescr="can't create; object already exists.">
</configConfMo>
Empty Result Responses
A query request for a nonexistent object is not treated as a failure. If the object does not exist, a success message
is returned, but the XML document contains an empty data field, <outConfig> </outConfig>, which indicates that
the requested object was not found. The following example shows resolution by DN on a nonexistent policy:
is returned, but the XML document contains an empty data field, <outConfig> </outConfig>, which indicates that
the requested object was not found. The following example shows resolution by DN on a nonexistent policy:
<configResolveDn
dn="org-root/org-tenant_d3337/pol-p1"
cookie="<real_cookie>"
commCookie="7/13/0/203e"
srcExtSys="10.193.34.70"
destExtSys="10.193.34.70"
srcSvc="sam_extXMLApi"
destSvc="policy-mgr_dme"
response="yes">
<outConfig>
</outConfig>
cookie="<real_cookie>"
commCookie="7/13/0/203e"
srcExtSys="10.193.34.70"
destExtSys="10.193.34.70"
srcSvc="sam_extXMLApi"
destSvc="policy-mgr_dme"
response="yes">
<outConfig>
</outConfig>
</configResolveDn>