Confidential Page 1 2/6/2009
20090206120122_NWDS_Learning.doc Created by Chander Kararia
NETWEAVER DEVELOPER STUDIO PRACTICAL IMPLEMENTATION KNOWLEDGE DOCUMENT
FOR NEWBIES
VERSION 1.0
Confidential Page 2 2/6/2009
20090206120122_NWDS_Learning.doc Created by Chander Kararia
About Author
Chander Kararia has more than 2.5 years of professional work experience in IT
industry which he got working as a SAP NetWeaver Consultant in Enterprise
Portals (EP) and as a trainee in Java Technology. Presently, he is with KCP
Technologies, an ISO 9001:2000 certified companies and a part of the KCP Group
Company.
His skills include SAP – NetWeaver Developer Studio 7.0.13, Enterprise Portal 7,
JAVA-J2EE, Oracle 10g, MS Access, SAP-NetWeaver-XI (Exchange Infrastructure),
Mercator, Macromedia Dream weaver.
PROFESSIONALLY CERTIFIED BY
Email: [email protected]
Cell: +91 – 99406 54614
Confidential Page 3 2/6/2009
20090206120122_NWDS_Learning.doc Created by Chander Kararia
About Document
The document is going to teach how to work with NWDS – NetWeaver developer
Studio. This includes the basic knowledge of NWDI & how to develop a simple
application.
Confidential Page 4 2/6/2009
20090206120122_NWDS_Learning.doc Created by Chander Kararia
1. NWDI – NetWeaver Development Infrastructure, usually provided with java
environment, is a package includes the following:
a. DTR – Design Time Repository, is a version container of the files
created by the developer(s) for the particular application. Only the files
kept here are/will be available to the client server for production &
Quality. All files outside DTR are considered as local to the developer
m/c.
b. CBS – Component Build Service, used to build the DC(s). Whenever a
developer make changes in the files, an activity is created which is
checked in to DTR for further deployment to NWDI, is triggered at
CMS. If any internal DC(s) dependencies encountered, the remaining
DC(s) will automatically deployed.
c. CMS – Change Management System, used to maintain track of which
version is deployed.
d. SLD – System Landscape Directory, used to create the configuration
tracks for the development.
e. NWDS – NetWeaver Developer Studio, used as the front end by the
developer(s) to code.
2. Use the NWDS 7+ version for development. Before the installation of NWDS,
install the PDK (not JRE) version 1.4+.
3. When you will start the NWDS first time, click on the icon highlighted.
4. Add the different perspectives like DC, web Dynpro, java etc.
5. To create a new project, follow the path: File->New->Others.
Confidential Page 5 2/6/2009
20090206120122_NWDS_Learning.doc Created by Chander Kararia
6. Click Next->enter Project Name->click Finish. A new project is created, say
Hello Test.
7. Select Create Application.
8. Enter the application name, package name (make sure you do not enter
sap.com, it is reserved under SAP & may result in application blockage) &
select Authentication Check-box. Click Next.
Confidential Page 6 2/6/2009
20090206120122_NWDS_Learning.doc Created by Chander Kararia
9. Select “Create new component, means you are going to create a new
components in your current project” or “Use existing components, means you
are going to use some standard or pre defined components available in other
application (re usability is the best feature of NWDS)”. Click Next. Give the
Component Name, Window Name & View Name. Best practice: refer naming
standards given by SAP for web Dynpro coding at SDN.
10. Do as shown in the image to insert the UI elements to the view. To see the
properties of all the elements just add the element & right click select HELP
from the menu.
11. Go to context (can see in above picture last row) & right click to add the
node & attributes. Nodes & attributes of different data types will be created
Confidential Page 7 2/6/2009
20090206120122_NWDS_Learning.doc Created by Chander Kararia
here & mapped with the UI elements we have just added. At the
implementation level (coding in common language) these UI elements will be
represented by these contexts only.
12. Plugs (as you can see adjacent to Context) are used to navigate between the
two views created inside the same window or between the windows. There
are two types of Plugs, Inbound & outbound.
13. Action (as you can see adjacent to Plugs) used to create task for the
particular UI element method. For ex. UI element Button will have the Action
property name as OnClick. Defining the action name can be done here or
under the Outline Tab.
In the above picture you can see that the developer has created 2 events.
Actually, Actions can also be considered as Events. In the Implementation tab,
you need to write the code for the particular action to be performed by the UI
action.
14. Methods (as you can see adjacent to Action) are used to create a method
which will hold a separate piece of code. As such it is not required. But, it is
the best part of the coding standards which says, always separate or group
the similar or unique code. Note: Always use them.
Confidential Page 8 2/6/2009
20090206120122_NWDS_Learning.doc Created by Chander Kararia
15. Implementation (as you can see adjacent to Methods) used to write the
codes. Every component, action, method & plugs we have added to the view
has a set of predefined code. You can see & modify them here.
16. Now to deploy the project, you need to set the J2EE server & SDM host. That
can be done under Windows tab->preferences->SAP J2EE Engine.
You need to provide the Message Server Host & Port details. Click on Apply & Ok.
After that, check whether the server is configured correctly. This can be checked
under J2EE Engine View (to start that view follow the path, Windows->Show
Views->Others->J2EE->J2EE Engine). Click on refresh. You will see few green
colored circles. 1st is “dispatcher”, 2nd is “SDM” & 3rd is “Server”. You may have
more servers depending on organization settings.
Now again, go to Windows->preferences->Development Configuration Pool.
Enter your company server URL. Click Ok.
Confidential Page 9 2/6/2009
20090206120122_NWDS_Learning.doc Created by Chander Kararia
17. Application Deployment, can be done by right clicking on the application
under project you have created. Select Deploy New Archive & Run.
18. This completes your first application practical implementation.