Handling the Seeburger Message Splitter
In this blog, I would like to explain how to solve an issue related to the Seeburger message splitter.
When we receive an EDI message via Seeburger Adapter in XI, it is split into two messages – the Main Message and the 997 (Functional Acknowledgement). In our case, this split was not happening on our system even though the Seeburger Adapter has been configured properly and we see that it shows now error anywhere in the system. And for the outbound EDI messages, we were getting an error “CallBicXIRaBean – Name Not Found exception”.
Later we found that the root cause of this message is that some of the modules were not deployed correctly.
So, I just wanted to share this with you all, feeling, this would help you out incase you face this issue.
Below are the steps that are to be performed:
Make sure the following modules for the Seeburger BIC Adapter are deployed.
- Message Splitter
Logon to the J2EE Visual Administrator -> Server->Services->JNDI Registry
Under this, we should see all the below modules
Under the seeburger node, check if the module for the Message Splitter exists.
If you see any of these modules missing, then go ahead and have the below modules deployed.
- CallBicXI RaEAR.ear
Then, once all of these modules are deployed, then go ahead and deploy the Mappings_User.sda file, which contains all the E2X and X2E mappings.
Please refer to the below article for further information on integrating XI with EDI.