We are developing a solution to process EDI Purchase Orders (850 and 860) in Boomi.
We have few partners which have various divisions (each located in different continent) and each division can send us Purchase Orders.
All the POs come to us with same AS2 IDs but with different ISA/GS segments. In fact only GS values are different in our case.
We are trying below 2 solutions.
First Approach :
1. AS2 Listener writes the EDI file to a disk.
2. 2nd process (with TP as start shape and disk as communication method) reads the file and does further processing.
Even though this approach is working fine, we have to schedule multiple processes to read the file.
Second Approach :
1. Use a single process to validate both AS2 and EDI Segments (ISA & GS headers).
2. We created a AS2 shared communication channel and used it in different trading partners.
As soon as we deploy the 2nd process ( using AS2 shared communication channel in TP), the process is getting an error and refusing to start as listener.
Did we miss any configuration for using AS2 shared communication channel ?
Is there any alternate method for allowing Multi AS2 for various Trading Partners ?
Error Message :
java.lang.IllegalStateException: Duplicate route com.boomi.connector.as2server.AS2AccountServer$RouteId@3fecf7ec at com.boomi.connector.as2server.AS2AccountServer.register(AS2AccountServer.java:168)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at com.sun.proxy.$Proxy42.register(Unknown Source)