cancel
Showing results for 
Search instead for 
Did you mean: 

Class not found Exception While performing a Custom fetch developed in Agentry

madan_km
Participant
0 Kudos

Hi All,

I have created a custom fetch logic in Agentry and the necessary Java.

During transmission I have encountered a strange error.

I cant attach the actual log(its been blocked)

The error is not related to anything that I have developed in either Agentry/Java. It is saying that some .Jar files of SMP server cant be found(Which is of course in place).

Please see below for a glimpse of this error

Accepted Solutions (0)

Answers (2)

Answers (2)

madan_km
Participant
0 Kudos

Thanks Everyone.

Actually the problem was with improper SMP Server installation.

Its fixed now.

Nothing wrong from actual java and Agentry development

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Madan,


Please mark this Discussion with a Correct Answer and Helpful Answer where appropriate.  See http://scn.sap.com/community/support/blog/2013/04/03/how-to-close-a-discussion-and-why   Even if you discovered the solution without any outside contributions, it helps others to understand what the solution turned out to be.


--Bill

Former Member
0 Kudos

Did you add the Jar file with the custom logic into the Agentry's Application classPath?

Did you restart the application after updating the classPath, or updating the Jar file?

madan_km
Participant
0 Kudos

Hi Stephen,

Thanks for the response.

Yes I do have the necessary custom .Jar file marked in the class path of Agentry.ini file (Java-1 section) and yes I did restart the application/server several times.

But if you look at the error log, the .jar mentioned inside the log were inside the SMP server folder itself.

sravanthi_polu
Contributor
0 Kudos

Hi,

Please verify the below steps.

1. Place the custom jar file in Java folder of the application

2. Update the class path in Cockpit

3. Perform Application restart in Cockpit

4. Perform Sever re-start for SMP Server to recognise the new jar file

Verfiy the Jar file name mentioned in the class path exactly matches the jar file(ensure it is not case sensitive)

Thanks & Regards,

Sravanthi