class file for com.seeburger.exception.SeeException not found

[former_member187010]

Hi Experts,

Recently we have upgraded our SAP PI system (from 7.1 to 7.4, dual stack) and Seeburger (from 1.8 to 2.2.2) in Dev environment.

We have successfully imported seeburger related software component version zip and tpz file available with the installation CD.

But now when we check any mapping or edit it, it is giving below error with the UDF's. Error and UDF snapshot attached.

"cannot access com.seeburger.exception.SeeException
class file for com.seeburger.exception.SeeException not found
VariableBean be=VariableFactory.getVariableInstance("");"

We already have imported SeeFunctionsPI.jar and SeeCommonCollectionPI.jar in the imported archive of our namespace also but still getting this error.

Could not understand why it is throwing "cannot access com.seeburger.exception.SeeException". In the imported archive I can see this class in SeeCommonCollectionPI.jar.

In the Quality system and production system same is working fine for the older system. They both are not being upgraded to latest version as of now and activity is in progress.

In ESR, SWCV for older seeburger version is also visible ("SEEBURGER_AUTOMOTIVE, 1.8.1 of seeburger"), which also have this jar in imported archives.

Is it creating any conflict? (I don't think so)

Also once the seeburger version is upgraded, i don't think older swcv should exist in ESR (may be a part of undeployement when basis upgrade it).

Need suggestions.

Regards

Jitender

[former_member182412]

Hi Jitender,

Have you added the jars under Archives Used tab in message mapping??

Regards,

Praveen

[former_member187010]

Hi,

Service desk suggested us the same and it is working now.

Strange part is then how it is working when no jars are there in "archive used" if we don't edit it. Without editing no error in object check or in runtime (sxmb_moni).

And if we edit it, mapping automatically import only SeeFunctionsXI jars in "archive used" section and not the second one.

New thing which we noticed regarding upgrade is, in ESR, mapping signature is referring to external definition from older seeburger software component.

Do we have to manually change the signature or with the upgrade it should automatically be changed.

Is there any other available option to change it at once to avoid risk of human error.

Regards

Jitender