How to set the classloader mode in Netweaver 04s

[Former Member]

Hi All,

Can anybody tell me how to set classloader mode in Netweaver 04S?

In websphere , there is direct option you when you select the project through admin console. But I am able to find the place in the netweaver where I can set such mode.

classloader mode such as parentfirst, parent last etc

I want to set the mode parent last.

This is very urgent requirenment.So please let me know if anybody is having any input on this.

Thanks,

Chandan

[Former Member · Accepted solution]

Hi Siddhesh,

Can you explain in layman terms what you are trying to achieve?

-->

See, I have deployed my application named tdemand on Netweaver and Websphere.Later on due to some requirement, we had to upgrade Axis in our project. It The upgrade went off fine on Websphere.but there seems to be an issue on NW because NW has its own version of jaxrpc related jar files which are of older version. The same named jaxrpc related jar files are also present in our project which are of updated version. But when we run our application, the older version of jars( i.e. Netweaver specific jars) are being picked up instead of the jars which are included in our project.

Note: Netweaver related jars are located at <Drive Name>:\usr\sap\J2E\JC02\j2ee\cluster\server0\bin\ext\webservices_lib folder.

This issue is not occured on Websphere because There is a classloader configuration setting option.

Following are the steps that were followed for Websphere.

) In the Websphere admin console, go to Appication -> Enterprise Applications

2) Click on your application name

3) Set "class loader mode" to "parent last"

4) Set "WAR class loader policy" to "application"

5) Click "Apply" and save master configuration

See the steps 3, where we can select class loader mode.

This option i cannot see in the netweaver.

So just wanted to know how to configured such classloader option in Netweaver.

How have you deployed your application ?

--> I have deployed my application through visual admin.

Let me know if you need more information on this.

just searched on the SAP forum and help link, and found that this type of the problem can be solved through application-j2ee-engnee.xml.

if possible,Let me know the input on this also.

Thanks,

chandan

[former_member185954 · Accepted solution]

sorry dude, i cannot help much on this, i am a system admin, don't know much about application development

Have you opened a message with SAP OSS , if not please do.

Regards,

Siddhesh

[Former Member · Accepted solution]

Thanks Siddhesh,

That is the good option. But I am facing some difficulty here.

I am not able to understand which component I should choose to create message.

To send any machine following are the steps.

1) choose the system: I have selected the system

2) Prepare solution search: In this option, you need to select the component. Here i am not understanding which component I should select in order to create the message.

Can you guide on this?

Regards,

Chandan

[former_member698570 · Accepted solution]

Hi,

I had the same problem with javamail (SAP Provides old API and my custom Application ships with newer API Version) but I coul not get it working.

I even opened a SAP OS CALL but SAP did not provide a solution which solved my problem.

The support directed me to the following SAP Note:

Note 990854 - Class conflicts with third party libraries on J2EE Engine

If you want to open your own message:

I used the following system to open the message BC-JAS and got a quite quick response

Cheers and good luck

[Benny · Accepted solution]

Marcel,

as javamail is part of the J2EE standard and 7.0 relies on J2EE 1.3, you cannot expect to change this by just sending along the newer libs. You either use the older standard or ahev to use the newer server, which is in Netweaver CE 7.1. This then would be Java EE 5 and therefore the latest and greatest in javamail.

[Benny · Accepted solution]

Well, actually this is possible and it is described in the note mentioned before.

Learned something new today....

Regards,

Benny

[Former Member]

Hi Siddhesh,

Thanks for replying.

Actually,NW has its own version of jaxrpc related jar files (in <drive>:\usr\sap\J2E\JC02\j2ee\cluster\server0\bin\ext\webservices_lib folder) which are of a older version and are being picked up instead of the jars that are present in my application package. As a result, there are exceptions like:

#1.5#0018FE710E98005B000000000000182800044D0B9F1ED11B#1210612216444#System.err#tdemand.com/TrueDemandWeb#System.err#Guest#0#####Thread[Thread-271,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###java.lang.NoSuchMethodError: javax.xml.namespace.QName.getPrefix()Ljava/lang/String;#

#1.5#0018FE710E98005B000000010000182800044D0B9F1ED31A#1210612216444#System.err#tdemand.com/TrueDemandWeb#System.err#Guest#0#####Thread[Thread-271,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain### at org.apache.axis.wsdl.symbolTable.BackslashUtil.getQNameWithDifferentLocal(BackslashUtil.java:62)#

#1.5#0018FE710E98005B000000020000182800044D0B9F1ED379#1210612216444#System.err#tdemand.com/TrueDemandWeb#System.err#Guest#0#####Thread[Thread-271,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain### at org.apache.axis.wsdl.symbolTable.BackslashUtil.getQNameWithBackslashlessLocal(BackslashUtil.java:39)#

#1.5#0018FE710E98005B000000030000182800044D0B9F1ED3D3#1210612216444#System.err#tdemand.com/TrueDemandWeb#System.err#Guest#0#####Thread[Thread-271,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain### at org.apache.axis.wsdl.symbolTable.SymbolTable.populateServices(SymbolTable.java:3078)#

#1.5#0018FE710E98005B000000040000182800044D0B9F1ED42B#1210612216444#System.err#tdemand.com/TrueDemandWeb#System.err#Guest#0#####Thread[Thread-271,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain### at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:745)#

#1.5#0018FE710E98005B000000050000182800044D0B9F1ED481#1210612216444#System.err#tdemand.com/TrueDemandWeb#System.err#Guest#0#####Thread[Thread-271,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain### at org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543)#

#1.5#0018FE710E98005B000000060000182800044D0B9F1ED4D8#1210612216444#System.err#tdemand.com/TrueDemandWeb#System.err#Guest#0#####Thread[Thread-271,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain### at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:518)#

#1.5#0018FE710E98005B000000070000182800044D0B9F1ED52F#1210612216444#System.err#tdemand.com/TrueDemandWeb#System.err#Guest#0#####Thread[Thread-271,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain### at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)#

#1.5#0018FE710E98005B000000080000182800044D0B9F1ED585#1210612216444#System.err#tdemand.com/TrueDemandWeb#System.err#Guest#0#####Thread[Thread-271,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain### at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)#

#1.5#0018FE710E98005B000000090000182800044D0B9F1ED5E1#1210612216444#System.err#tdemand.com/TrueDemandWeb#System.err#Guest#0#####Thread[Thread-271,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain### at java.lang.Thread.run(Thread.java:534)#

#1.5#0018FE710E98004F00001A610000182800044D0B9F1F2B60#1210612216475#System.out#tdemand.com/TrueDemandWeb#System.out#Guest#0#####SAPEngine_Application_Thread[impl:3]_9##0#0#Info##Plain###2008-05-12 10:10:16,459 ERROR [com.tdemand.common.service.client.ServiceProxyUtil] - <Error processing WSDL document:

javax.xml.rpc.ServiceException: Error processing WSDL document:

javax.xml.rpc.ServiceException: Cannot find service: BootstrapService>

javax.xml.rpc.ServiceException: Error processing WSDL document:

javax.xml.rpc.ServiceException: Error processing WSDL document:

javax.xml.rpc.ServiceException: Cannot find service: BootstrapService

at org.apache.axis.client.Service.initService(Service.java:250)

at org.apache.axis.client.Service.<init>(Service.java:165)

at org.apache.axis.client.ServiceFactory.createService(ServiceFactory.java:198)

at org.springframework.remoting.jaxrpc.LocalJaxRpcServiceFactory.createJaxRpcService(LocalJaxRpcServiceFactory.java:182)

This problem is solved in websphere as probably because we have classloader configuration set through Admin console.

But just wanted to know does we have such option in NetWeaver? If yes, how to set the classloader mode to parent last.

Or if you know some other solution then let me know.

Thanks,

Chandan

[former_member185954]

Hello Chandan,

Can you explain in layman terms what you are trying to achieve.

How have you deployed your application ?

Regards,

Siddhesh

[former_member185954]

Hello Chandan,

Please check the following link:

http://help.sap.com/saphelp_nw70/helpdata/EN/84/0e3f15fc6af94f82c2e6449bcef3d1/frameset.htm

it provides you the list of admin commands the J2EE dispatcher can accept.

Please choose the command that will suit your purpose.

Regards,

Siddhesh