Best Practices for Defining NDS Java Projects...

[Former Member]

We are doing a Proof of Concept on using NDS to develop non-SAP Java applications. We are attempting to determine if we can replace our current Java development tools with NDS/WAS.

We are struggling with SAP's terminology and "plumbing" for setting up/defining Java projects. For example, what is and when do you define Tracks, Software Components, Development Components, etc. All of these terms are totally foreign to us and do not relate to our current Java environment (at least not that we can see). We are also struggling with how the DTR and activities tie in to those components.

If any one has defined best practices for setting up Java projects or has struggled with and overcome these same issues, please provide us with some guidance. This is a very frustrating and time-consuming issue for us.

Thank you!!

[Former Member]

Hi Peggy,

In Component Model we divide software projects into small components.Components can use other components in well defined manner.

A development object is a part of a component that can be changed or developed in some way; it provides the component with a certain part of its functionality. A development object may be a Java class, a Web Dynpro view, a table definition, a JSP page, and so on. Development objects are always stored as “sources” in a repository.

A development component can be defined as a frame shared by a number of objects, which are part of the software.

Software components combine components (DCs) to larger units for delivery and deployment.

A track comprises configurations and runtime systems required for developing software component versions.It ensures stable states of deliverables used by subsequent tracks.

The Design Time Repository is for versioning source code management. Distributed development of software in teams. Transport and replication of sources.

You can also find lot of support in SDN for the above concepts with tutorials.

Refer this Link for a overview on Java development Infrastructure(JDI)

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/java/java development infrastructure jdi overview.pdf

To understand further

Working with Net Weaver Development Infrastructure :

http://help.sap.com/saphelp_nw04/helpdata/en/03/f6bc3d42f46c33e10000000a11405a/content.htm

In the above link you can find all the concepts clearly explained.You can also find the required tutorials for development.

Regards,

Vijith

[Former Member]

Peggy,

I'll take a stab at this.

For example, what is and when do you define Tracks, Software Components, Development Components, etc.

A track controls to what landscapes (systems) your software components will be deployed to. It can provide an approval mechanism as well.

A software component is usually represents a grouping of functionality that you would want to deploy at the same time.

A development component represents a single piece of your software component. This would be like the external libs, the data dictionary, ect.

We are also struggling with how the DTR and activities tie in to those components.

The DTR is like CVS. An activity is just all the changes that you have made to the code that resides locally. Once you are done with your activites, you should check them in, activate them, build them, and then release the changes into the development environment.

Thanks,

Eric

[Former Member]

Hi Peggy,

Do close the thread if your query is solved or update it.Reward points for the replies you find useful.

Regards,

Vijith