Extended Receiver Determination with Raw text file as source

[venkatanarayana_vagu]

Hi All,

We are working on flow, SFTP to JDBC,FTP (Extended Receiver Determination), during the extended receiver determination, I  have called the java mapping under operation mapping, under the java map, it has to check the JDBC lookup for that file validation if every thing is fine it has to send the file to both receivers and the respective interface determinations.

But when I execute end to end, my interface is failing at receiver determination error as below:

"Error when determining the receiver: Problem while determining receivers using interface mapping: Error while determining root tag of XML: ORDA/charset detection failed Problem while determining receivers using interface mapping: Error while determining root tag of XML:

But when I check my operation mapping stand alone test, it is successfully working fine. As I took the outbound service interface as raw text file and inbound interface as the standard BASIS component. I am working this on PI 7.3 dual stack.

About my java mapping, I simply getting the raw text content as input stream and reading the first line for the JDBC lookup. If my JDBC lookup is success then it will goes to the predefined xml structure which is same as standard Receivers service interface.

So here my doubt is, extended receiver determination with operational mapping (under it has java mapping) only works for XML file (XPATH)? or it suppose to work for raw text files at source?

[Ryan-Crosby · Accepted solution]

Hi,

That is because the system is going to execute the receiver determination to figure out where it should go before any operation mapping is executed as the operation mapping can differ per receiver.  You would have to setup your mapping to transform the message into some form of XML or you might be able to use the dummy ESR interface concept to get it to trigger your mapping as well.

Regards,

Ryan Crosby

[maheswarareddykonda · Accepted solution]

Hi Venkat,

i hope you are using standard  Message type for receivers structures

and since you are using java mapping , is that output of java mapping is matching with standard receiver structure?

.

[venkatanarayana_vagu · Accepted solution]

Hi Ryan,

Thanks for the hint. Even I tried with the NONEXIST OUTBOUND interface and tested but no luck. This time it is saying no receivers found. So you mean to say with out the xml structure, extended receiver determination will not work?

[venkatanarayana_vagu · Accepted solution]

Hi Maheswar,

I am using the standard receivers interface under my java mapping. Even thought I am getting the error.

[Ryan-Crosby · Accepted solution]

Hi,

The one thing that should work is creating a dummy ESR interface as XI 3.0 compatible and setting that up as the source for your java mapping with whatever target you require.  Then in your configuration set the dummy interface as your source and in the operation mapping.

Regards,

Ryan Crosby

[former_member182412 · Accepted solution]

Hi Venkat,

I think at runtime the JDBC lookup is failing, to prove that comment jdbc lookup code and pass the receivers and see if it works, if it works then problem is with JDBC lookup then identify why the jdbc lookup is not executing at runtime.

Regards,

Praveen.

[venkatanarayana_vagu · Accepted solution]

Thanks Ryan,

You are correct. I have made the out bound interface under the operation mapping as NONEXIST and it was worked as expected. I mean no need to create any service interface with NONEXIST. Just simply mention NONEXIST under outboun service interface at operation mapping and it worked.

Thanks for the hint

[venkatanarayana_vagu · Accepted solution]

Hi Praveen,

The JDBC lookup is very much working as expected. Issue is solved by making the out bound service interface as NONEXIST (dummy).