Getting API:s for DevStudio

[Former Member]

Hi !

I'm new on NetWeaver, and we are about to migrate from EP6 Sp2. My task is to deliver a dev - environment.

What is the best / easiest way do fetch the api:s for use with NW DevStudio?

If I should copy the api:s from the Portal to my development environment, what is the

copy patterns? ( In terms of copy *_api.jar .... )

Or is there a fancy plugin / function in DevStudio to handle this?

Rgrds

Peter

[pravesh_verma · Accepted solution]

Hi Peter,

Yes there is way to include the jars you want in the project. Just right click the project you are workingin and click the properties.

There a screen will appear. <b>Click Java build Path -> Libraries -> Add external Jar's</b>. Now browse the location and add the jars to the project.

I hope this solves your problem. If more clarification required then please revert back.

Regards

Pravesh

PS: Please consider rewarding points if helpful.

[Former Member · Accepted solution]

Thanks,

but the thing is I want to retreive all api:s from the portal, putting them in a local folder on my computer, and then from within my projects refer to that local api folder. The last part will be no problem, the question is where in the portal to search for the api:s in order to copy them. Maybe I could just make a copy _api., but then maybe I get some useless ones...

regards

Peter

[pravesh_verma · Accepted solution]

Hi Peter,

ok you want to search for the api's, then you have to search for required jar from the server location or some of them you can search from your local machine.

Go to: <b><your_NWDS_installation_directory>/SAP/JDT/eclipse/plugins</b>

Also If you want then you can use <b>Class locator</b> for including and finding the required jars for the project.

I hope now it helps you!!

Regards

Pravesh

PS: Please consider rewarding points on SDN!! Thanks in advance.

[Former Member · Accepted solution]

Ok thanks,

I didn't see the api:s was allready included in the DevStudio installation. So hopefully there are functions in the DevStudio for refreshing them as new patches comes ..

Brgrds

Peter

[detlev_beutner · Accepted solution]

Hi Peter,

the APIs are only a part of the servers APIs to use. They are only potentially updated with a new NWDS.

We always copy at least the BIN part of the server (if one doesn't have a local installation anyhow) - \usr\sap\<ID>\<INST>\j2ee\cluster\<NODE>\bin - to the local machine and define a classpath variable within NWDS to this root folder (beneath the same thing for the portal installation under ..\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF, but that doesn't seem to be in your focus).

Hope it helps

Detlev

[Former Member · Accepted solution]

Hi Detlev,

I have now copied the bin folder from the portal installation into my local computer. Then I created a classpath variable pointing at the local bin-folder. Then I created a test project and added the class varaible to the Libraries / build path.

But a warning is on the variable saying it's not pointing to an archive... Any idea?

[detlev_beutner · Accepted solution]

Hi Peter,

> Any idea?

Of course

The classpath variable is only the starting point, so that different people can store the stuff under different directories, but from the dir the varaible points to, the structure is the same. That's the sense of using CP-variables.

If you need a certain class (within a JAR) for the build classpath, you have to include this JAR into the classpath, that means extending the classpath varaiable.

Bu as Pravesh has already stated, if you use ClassLocator, you won't have to care about that too much, ClassLocator will do it for you, fully supporting classpath variables.

Please check the tool.

Hope it helps

Detlev

[Former Member · Accepted solution]

Thanks both Pravesh and Detlev,

I think I have to make a proper dive into this before more asking