on 04-13-2016 3:28 PM
Hi experts,
We have java code maintained in attributes and methods under functions tab of our pi 7.1 mapping.
recently we have migrated the same to the PO 7.4.
In PI code was getting impacted at run time, whereas coming to PO its is not getting executed by which our message flow is getting impacted.
My question here is do we need to recompile the java code present in the PI into the jdk verison of PO (Code was not imported using archive) ?
Thanks in advance for your valuable suggestions:)
Many Thanks
Sai Chaithanya
Hello Sai,
Any specific error being thrown?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
interface determination did not yeild any actual interface
Reason:
Inbound message consists of - in the payload where the java code interperts the message and replace the - with _ and forwards to mapping.
Now as java code is not executing PO is looking for mapping with sender structure consists o-
as the interface is not found it is throwing interface determination yeild any actual interface
Thanks and Regards:
Sai Chaithanya
Hi Sritharan,
PFB code used
public void transform(TransformationInput in, TransformationOutput out)
throws StreamTransformationException {
try {
String xmlString="", modifiedxmlString ="", line ="";
InputStream ins = in.getInputPayload().getInputStream();
BufferedReader br = new BufferedReader( new InputStreamReader(ins));
while ((line = br.readLine()) != null)
xmlString +=line+"\n";
br.close();
//Replaces the - to _ charcter in xml structure
modifiedxmlString= xmlString.replace("-","_");
out.getOutputPayload().getOutputStream().write(modifiedxmlString.getBytes());
} catch (Exception e) { throw new StreamTransformationException(e.getMessage()); }
}
Hi Sai,
Check this note 1933223 - Migrated scenario fails with "com.sap.aii.adpter.xi.RoutingException: InterfaceDeterminati...
Regards,
Praveen.
Hello Sai,
At runtime, an operation-dependent Interface Determination will always result in a check whether the incoming payload fits to the structure of the Service Interface (as configured in the ESR). If the payload does not fit, the message is rejected. For classical scenarios, there is one exemption to this check: For a Service Interface which consists of only one operation AND the operation name equals exactly the name of the Service Interface, no runtime check is performed whether the payload fits to the interface structure. Effectively that means for such an Interface Determination arbitrary payloads are accepted and the Interface Determination is handled as if it wouldn't be operation-dependent.
Check the note-1933223(Guess Praveen already shared it)
Close the thread if your query is addressed.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.