Highlighted
Visitor.
1374 views

HPSM SR WSDL error

Jump to solution

Hi Experts,

My HP SM version is sm7.11. I created a webservice on ocmq to create and update SRs. I am trying update through SOAP UI my SR, then I am getting following error:


<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>A CXmlApiException was raised in native code : error 19 : scxmlapi(19) - Doc Engine call failed with cc 

Please suggest, what should i do to get rid of this issue.

Thanks

Akhil

0 Likes
1 Solution

Accepted Solutions
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: HPSM SR WSDL error

Jump to solution

You don't want to do it randomly.  When a quote is created, the number field and the phase.num field are pulled from the sequentional number counters within the system.  You can add some RAD code to get those.  For example:

 

$L.nbr.class="ocmq";$L.void=rtecall("getnumber", $L.rc, $L.new.quote.nbr, $L.nbr.class);number in $L.file=$L.new.quote.nbr

$L.nbr.class="ocmqphase";$L.void=rtecall("getnumber", $L.rc, $L.new.quotephase.nbr, $L.nbr.class);phase.num in $L.file=$L.new.quotephase.nbr

 

View solution in original post

0 Likes
12 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: HPSM SR WSDL error

Jump to solution

I'm not sure what's wrong with your request, what I can tell is following request is right:

curl -XPOST -H "Content-Type: text/xml;charset=UTF-8" -H "SOAPAction: "Update"" -H "Authorization: Basic ZmFsY29uOjE=" -d "<soapenv:Envelope xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/' xmlns:ns='http://schemas.hp.com/SM/7'> <soapenv:Header/> <soapenv:Body> <ns:UpdateIncidentRequest attachmentInfo='false' attachmentData='false' ignoreEmptyElements='true'> <ns:model> <ns:keys> <ns:IncidentID>IM10002</ns:IncidentID> </ns:keys> <ns:instance> <Urgency type='String'>2</Urgency> <ns:JournalUpdates> <ns:JournalUpdates>Another update to the activity log, but reassigning back to the raising group</ns:JournalUpdates> </ns:JournalUpdates> </ns:instance> </ns:model> </ns:UpdateIncidentRequest> </soapenv:Body> </soapenv:Envelope>" "http://localhost:13080/SM/7/"

 

Response:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><UpdateIncidentResponse message="Success" returnCode="0" schemaRevisionDate="2014-12-07" schemaRevisionLevel="6" status="SUCCESS" xmlns="http://schemas.hp.com/SM/7" xmlns:cmn="http://schemas.hp.com/SM/7/Common" xmlns:xmime="http://www.w3.org/2005/05/xmlmime" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.hp.com/SM/7 /Incident.xsd"><model><keys><IncidentID type="String">IM10002</IncidentID></keys><instance recordid="IM10002 - Not able to print due to lack of ink in printer." uniquequery="number=&quot;IM10002&quot;"><IncidentID type="String">IM10002</IncidentID><Category type="String">incident</Category><OpenTime type="DateTime">2013-12-30T03:07:46+00:00</OpenTime><OpenedBy type="String">falcon</OpenedBy><Urgency type="String">2</Urgency><UpdatedTime type="DateTime">2016-08-01T01:53:33+00:00</UpdatedTime><Description type="Array"><Description type="String">Seldom ink exist in printer, there's alway error, when printing.</Description></Description><Contact type="String">AARON, JIM</Contact><JournalUpdates type="Array"><JournalUpdates type="String">07/31/16 19:53:33 US/Mountain (Jennifer Falcon):</JournalUpdates><JournalUpdates type="String">Another update to the activity log, but reassigning back to the raising group</JournalUpdates><JournalUpdates type="String">07/31/16 19:47:37 US/Mountain (Jennifer Falcon):</JournalUpdates><JournalUpdates type="String">Another update to the activity log, but reassigning back to the raising group</JournalUpdates><JournalUpdates type="String">07/31/16 19:44:52 US/Mountain (Jennifer Falcon):</JournalUpdates><JournalUpdates type="String">Another update to the activity log, but reassigning back to the raising group</JournalUpdates></JournalUpdates><Company type="String">advantage</Company><Title type="String">Not able to print due to lack of ink in printer.</Title><UpdatedBy type="String">falcon</UpdatedBy><Status type="String">Categorize</Status><Phase type="String">Categorization</Phase><Impact type="String">3</Impact><Service display="Printing (North America)" type="String">Printing (North America)</Service></instance></model><messages><cmn:message type="String">US/Mountain 07/31/16 19:53:33: Incident IM10002 has been updated by falcon</cmn:message><cmn:message type="String">Incident record updated.</cmn:message></messages></UpdateIncidentResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>

 

Hope it helps,

Ling-Yan

0 Likes
Highlighted
Visitor.

Re: HPSM SR WSDL error

Jump to solution

Thanks Ling-yan for response.

It is on SM7. I created webservice on ocmq as shown below, whenever I run it on SOAP UI it gives same Error as "faultstring>A CXmlApiException was raised in native code : error 19 : scxmlapi(19) - Doc Engine call failed with cc -1</faultstring>
<faultactor>Server</faultactor> ". Please suggest badly stuck.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:pws="http://servicecenter.peregrine.com/PWS" xmlns:com="http://servicecenter.peregrine.com/PWS/Common">
<soapenv:Header/>
<soapenv:Body>
<pws:UpdateQuoteDetailRequest attachmentInfo="" attachmentData="" ignoreEmptyElements="true">
<pws:model query="">
<pws:keys query="">
<!--Optional:-->
<pws:QuoteNumber type="String" mandatory="" readonly="">SR100067</pws:QuoteNumber>
</pws:keys>
<pws:instance query="" uniquequery="" recordid="">
<!--Optional:-->
<pws:QuoteNumber type="String" mandatory="" readonly="">SR100067</pws:QuoteNumber>
<!--Optional:-->
<pws:open type="Boolean" mandatory="" readonly=""></pws:open>
<!--Optional:-->
<pws:category type="String" mandatory="" readonly="">Non-Approval Category</pws:category>
<!--Optional:-->
<pws:CurrentPhase type="String" mandatory="" readonly="">Assignment</pws:CurrentPhase>
<!--Optional:-->
<pws:Description type="Array">
<!--Zero or more repetitions:-->
<pws:Description type="String" mandatory="" readonly=""></pws:Description>
</pws:Description>
<!--Optional:-->
<pws:justification type="Array">
<!--Zero or more repetitions:-->
<pws:justification type="String" mandatory="" readonly=""></pws:justification>
</pws:justification>
<!--Optional:-->
<pws:Comments type="Array">
<!--Zero or more repetitions:-->
<pws:Comments type="String" mandatory="" readonly=""></pws:Comments>
</pws:Comments>

</pws:instance>
<!--Optional:-->
<pws:messages>
<!--Zero or more repetitions:-->
<com:message type="String" mandatory="" readonly="" severity="" module=""></com:message>
</pws:messages>
</pws:model>
</pws:UpdateQuoteDetailRequest>
</soapenv:Body>
</soapenv:Envelope>

Best Regards

Akhil

 

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: HPSM SR WSDL error

Jump to solution

Have you done a trace with RTM:3 and debugdbquery:999? Since this is a RAD error, that should help tell where the error is occuring.

0 Likes
Highlighted
Visitor.

Re: HPSM SR WSDL error

Jump to solution

Yes I did try this but logs also populating only given error nothing different. Just Now I removed all the validation from form and table, Now I am getting below error, Please suggest, if it can be taken care by making some modification to rmq.update process or something else.

<messages>
<cmn:message type="String">Key #2 is empty. (rmq.update,update.record)</cmn:message>
<cmn:message type="String">file:(ocmq) key:(number=SR100046) (rmq.update,update.record)</cmn:message>
<cmn:message type="String">The record being updated contains a NULL key (rmq.update,update.record)</cmn:message>
<cmn:message type="String">Unrecoverable error in application: se.call.process on panel call.rad.1</cmn:message>

 

Thanks

Akhil

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: HPSM SR WSDL error

Jump to solution

Can you tell if number, phase.num and open fields are populated?

Highlighted
Visitor.

Re: HPSM SR WSDL error

Jump to solution

Hi TomPowe,

Great! To some extent I indeed got success in save but it is not allowing me to update phase name only comments I am able to update. Please suggest.

Thanks

Akhil

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: HPSM SR WSDL error

Jump to solution

Are you trying to change the phase name because you want to push it to the next phase?  Clicking Save is different than clicking the Next Phase button, therefore you should be using a Next Phase instead of Update action..

0 Likes
Highlighted
Visitor.

Re: HPSM SR WSDL error

Jump to solution

In HPSM7, I don't see action as "next phase" in wsdl configuration as I have to do it through wsdl please suggest what should be the best way.

Thanks

Akhil

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: HPSM SR WSDL error

Jump to solution

Try adding this to the WSDL:

Under Allowed Actions tab,
Allowed Actions: newphase
Action Name: ChangePhase

 

 

0 Likes
Highlighted
Visitor.

Re: HPSM SR WSDL error

Jump to solution

Hi Tom,

Thanks for suggestion. But this one not working, I tried through update by removing few validations, only problem I am facing that I have to provide some random value for phase number as it is mandatory for me to provide from third party tool consuming this OCMQ webservice.

Please suggest if this could make any adverse effect on flow.

Thanks

Akhil

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: HPSM SR WSDL error

Jump to solution

You don't want to do it randomly.  When a quote is created, the number field and the phase.num field are pulled from the sequentional number counters within the system.  You can add some RAD code to get those.  For example:

 

$L.nbr.class="ocmq";$L.void=rtecall("getnumber", $L.rc, $L.new.quote.nbr, $L.nbr.class);number in $L.file=$L.new.quote.nbr

$L.nbr.class="ocmqphase";$L.void=rtecall("getnumber", $L.rc, $L.new.quotephase.nbr, $L.nbr.class);phase.num in $L.file=$L.new.quotephase.nbr

 

View solution in original post

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.