Page 1 of 1

LANSA INTEGRATOR V15 - No document to bind

Posted: Tue Jul 06, 2021 11:58 pm
by Fabrice.geay
hi,
I have upgraded my developpment in V15 and now i have got errors when i call a webservice with the HTTPINBOUNDXMLBINDSERVICE.

in trace :
=================== TRACE OPEN ===================
manager: version : 15.0
manager: date : 2021-07-06 10:26:43 +0200
--------------------------------------------------
Job Name : PRDJSMLIB
Job User : QTMHHTTP
Job Number : 981232
Command : SERVICE_LOAD VALIDATING(*NO) DOMSET(*STREAM) SERVICE(HTTPINBOUNDXMLBINDSERVICE) CONTENT(*ANY) TRACE(*YES) TRACE_NAME(WS_ITELIS)
Inbound model : *DOCUMENT
Inbound reader : *STREAM
Create trace file : HTTP_KEYWORDS.TXT
Create trace file : HTTP_CONTENT.TXT
Command : OK "Service chargé correctement"
--------------------------------------------------

--------------------------------------------------
Job Name : PRDJSMLIB
Job User : QTMHHTTP
Job Number : 981232
Command : GET PROPERTY(SOAPACTION)
Command : OK "beneficiaires"
--------------------------------------------------

--------------------------------------------------
Job Name : PRDJSMLIB
Job User : QTMHHTTP
Job Number : 981232
Command : BIND TYPE(*INBOUND) SERVICE(ITELIS_BENEF_REQUEST) BINDTRACE(*YES)
Service type : *INBOUND
Load service : com.LAMUTUELLEVERTE.service.xml.ITELIS_BENEF_REQUESTService
Load archive : /LANSA_dcxpgmlib/jsm/instance/bindings/ITELIS_BENEF_REQUEST.xml.jar
Local entry load : com.LAMUTUELLEVERTE.service.xml.ITELIS_BENEF_REQUESTService
Local class load : com.LAMUTUELLEVERTE.service.xml.ITELIS_BENEF_REQUESTService
No document to bind
Command : ERROR "Pas de document pour édition de liens"
--------------------------------------------------
I have got 4 webservice like this.
I need all help. I can sent you all integrator's trace and rpgle code

Re: LANSA INTEGRATOR V15 - No document to bind

Posted: Thu Jul 08, 2021 7:38 am
by Theo de Bruin
Hi Fabrice,

- Did you check if the upgrade of the JSM instance in the IFS was succesfull ?
(perhaps some parts were locked durimg the upgrade )
e.g. . Has the subfolder UPGRADE been removed , and what does the upgrade log file tell you ?

- Did you check the HTTPINBOUNDXMLBINDSERVICE.properties file if that was still okay ?

- What is the contents of the trace file HTTP_CONTENT.TXT

- Did you send this to France support also ?

I guess you should first send this with all details to your local support!

Re: LANSA INTEGRATOR V15 - No document to bind

Posted: Thu Jul 08, 2021 8:18 pm
by Fabrice.geay
hi Theo,
the upgrade of the JSM instance in the IFS was succesfull. the subfolder has been deleted.

I have checked the HTTPINBOUNDXMLBINDSERVICE.properties with the save file and it was still okay. I have the same blocs but not at the same place.

The HTTP_CONTENT.TXT :
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:std="http://ws.jalma.com/stdclient">
<soapenv:Header/>
<soapenv:Body>
<ns6:beneficiairesRequest xmlns:ns6="http://ws.jalma.com/stdclient">
<ns6:enTete>
<ns6:dateMessage>???</ns6:dateMessage>
<ns6:nomClient>???</ns6:nomClient>
<ns6:nomUtilisateur>???</ns6:nomUtilisateur>
<ns6:motDePasse>???</ns6:motDePasse>
<ns6:origine>???</ns6:origine>
<ns6:numeroDossierExperteo>???</ns6:numeroDossierExperteo>
<ns6:dateDossier>???</ns6:dateDossier>
</ns6:enTete>
<ns6:assure>
<ns6:numeroSecuriteSociale>???</ns6:numeroSecuriteSociale>
<ns6:cleSecuriteSociale>???</ns6:cleSecuriteSociale>
<ns6:numeroAyantDroit>???</ns6:numeroAyantDroit>
<ns6:nom>???</ns6:nom>
<ns6:prenom>???</ns6:prenom>
<ns6:dateNaissance>???</ns6:dateNaissance>
<ns6:rang>???</ns6:rang>
</ns6:assure>
</ns6:beneficiairesRequest>

</soapenv:Body>
</soapenv:Envelope>

I have sent to Uk support / France support

Re: LANSA INTEGRATOR V15 - No document to bind

Posted: Thu Jul 08, 2021 8:21 pm
by Fabrice.geay
On the open command I have change the LOCALHOST with the ip for INTEGRATOR 14 and the call was succesfull