ClassNotFoundException: com.seeburger.jucon.dochandler.util.IGrammarInput

[Former Member]

I have a NW PI 7.1 installation which includes Seeburger. We are trying to transfer EDI documents from our VAN. The flow is to use Seeburger FTP, pass the message to the classifier and then (eventually) through the splitter and on to SAP.

The FTP adapter is retrieving data from the VAN and passing it to the classifier. The classifier, however, after reporting that it is commencing analysis, simply aborts without error messages or diagnostics and the next step in the log says the adapter is rolling back.

Furthermore, in the splitter application (http://pihost:piport/seeburger/index.html - press the splitter button), I get http error 500.

The defaultTrace log in NWA show a consistent error message which appears to be at the root of this issue:

Caused by: java.lang.ClassNotFoundException: com.seeburger.jucon.dochandler.util.IGrammarInput

I'm neither an expert Java programmer nor a PI Systems Administrator but I am, nevertheless, the NetWeaver Administrator expected to solve my developer's problem. Others on this forum have suggested to him that there is an installation error. The installation was done by our outsourcing partner and I don't know what they did but I installed the updated BIC and splitter, by simply deploying the .sca files off the disks, and experienced no apparent errors.

I note that there is no specific reference to anything obviously Seeburger related in my <sid>adm's PATH, LD_LIBRARY_PATH or CLASSPATH environment variables.

NWDS repository view shows me that the following libraries are all deployed...

com.seeburger.jucon.mapping.partner
com.seeburger.jucon.mapping.sys
com.seeburger.jucon.mapping.user

The SeePIBaseTools and SeePIExtendedTools are also deployed.

I've turned debugging on in the log configurator but the messages don't really tell me very much. I'm sure if I can persuade PI to find the class mentioned above the whole thing will start working but I don't know how to do that.

My developer has tried sending, rather than receiving, a message to the VAN. It didn't work but the error messages were a little more informative. It says

Application seeburger.com/com.seeburger.bicxiadapter.module cannot be started.  
Reason: it has hard reference to resource seeburger.com~com.seeburger.jucon.lib with type library which is not active on the server.

When I look in NWA under the Java Class Loader Viewer for libraries containing the word "jucon" in the name, I see three libaries:

seeburger.com~com.seeburger.jucon.apiwrappers
seeburger.com~com.seeburger.jucon.logger
seeburger.com~com.seeburger.jucon.mapping.sys

I can't see the library mentioned in the error message. This adds support to the theory that there is an installation error but where?

[Former Member]

Hi Murray

After the upgrade from XI 3.0 to PI 7.1 we are facing the same error as you mentioned.(both at sender side and receiver side).

What was your approach to resolve this? Was it only a seeburger patch?

Your response is greatly appreciated.

Thanks

Dhanish Joseph

[Former Member]

The solution for this seems to be to download and redeploy the very latest patch from SAPNet. We actually went through three iterations of "latest" and then added an additional "hot fix" direct from Seeburger before we got it all to work.

It also appears to be very important to UNDEPLOY the whole product before reDEPLOYin it to get things working. It was an ugly installation but it's all working and in production now.

[Former Member]

Hi Nicholas,

I'm currently facing a nasty (Seeburger) problem and I'm just wondering where I can download Seeburger patches.

We use SAP PI 7.11 with Seeburger version 2.1.3 (DVD material 51038105)

You also speak about a Seeburger hot fix. What was it about?

Thanks a lot

Dimitri Sannen

[Former Member]

Hi Sannen

Seeburger software is downloadable from SAPNet (service.sap.com/swdc). The download appears to always be a complete refresh of the product.

The hotfix I mentioned was identified by a consultant working with us. We opened a support call through SAPNet (SAPNet message) to request this hotfix and Seeburger support provided us with an ftp connection to download the patch.

Murray.

[Former Member]

Make sure all BIC components are deployed (including the 3 Mappings_* sca files) and check for the latest patch version. Version 2.1x has gone through major improvements!