1. What are JCo destinations? What it contains?

1.

Jco Connection are JAVA SAP connectors, these are used to connect Backend
system properties, like source system(JAVA) name and destination system(ABAP)
name, which are divined as part SLD.
it contains also type of data your fetching from ABAP to JAVA system
2. What is the purpose of creating JCo destinations?

1.

These are used to connect Backend system properties, like source system
(JAVA) name and destination system (ABAP) name.
3. Who will create JCo destinations?

1.

J2EE ADMIN or Portal Admin

4. How many types of JCo destinations are available? What are they?

1.

JCO's are 2 types, Model Data and Meta Data, we need one pair of these two
connect any system.
5. When we prefer System Objects and JCo destinations?

1.

When you accessing the backend system through portal we need to have
system object,
Whereas you are trying to connect to backend from webdynpro for java (NWDS) we
need to use JCO's
1.

1.

1.

6. What is model data Meta data with example?

a)
Model data: Data is coming from tables which means its describes the actual data present
in the table. Mode data is a specify application data as datatype.
b)
Metadata: Metadata is a structure of the table; metadata is specifying dictionary Meta
data as datatype.
Exp:
SNo
1
2

F.Name
Lname
Contact No (Metadata)
S
Reddy
9886278888 (Model data)
M
Venkat
9730040900
7. Where and how to assign area group pages to portal role?
I have created a new portal role example ess this role worksets and pages
We can copy the overview of type workset map iview from standard ess role and give the area group name
Check the overview in the standard ess role give application parameters as sap.xss
Menuarggrp=area group name and sap.xss.
Memuhdr=header name.
8. How many configuration levels?
a) Top level navigation:
the TLN iview for every role combination existing in your portal although all users with the
same role combination will see the same TLP and have same instance in the cache users with
different themes, Languages, Browser version.
b) Detailed
DTN is an extension of TLN is displayed in the DTN iview of the navigation panel
according to ur role structure. The DTN to a page and that page to a role before you can see it.
DTN iview assigned to desktop innerpage
c) Content
Exp:
Role1: first level navigation

Worksetsecond level
Foldersdetailed navigation entry folders
Folder2 ---page 1 page2
Folder3---page3 page4
9. When RFC destination failure case in SM9?
The RFC destination failure login data incorrect a logon screen automatically appears for a dialog
user. The target machine is not accessible are the host name ip address and path correct, the host name
command must issue the correct hostname. If the connection is to be setup a registered RFC program.

1.

1.

10. What are the Types of controller in webdynpro java?

Interface controller:
It is global controller which is used to share the data among multiple components.
Component controller:
Custom controller:
View controller:
Window controller:
1.
10. A) Service controller?
The service controller automatically writes few lines of code for execute the methods its create
object for an executable node. In WD init() method in component controller.
1.
10. B) what is SVS (Simple value sector)?
Drop down key is consider as SVS
1.
11. Service Controller in webdynpro java?
It is used by developer at design time code is automatically reflected.
1.
12. View Set and types of view sets?
It is a collection of views
Types of view set grid layout, TLayout, Tlayout-90tlayout-180.
1.
13. What are context and context mapping and model binding?
Context is nothing but storage of database at run time; dynamic data storage is nothing but context.
Context mapping the attributes of one context is mapped to attribute of another context is called context
mapping.
A.
Exp: component (Contextnodeattribute)
B.
View (contextnodeattribute)

1.

1.
1.

a.
b.
c.

Model binding: attribute of any context is bind to model object attributes.

Structured binding: fields are maintained the structure in dictionary is bind to nodes of any context.
Table mapping binding: attributes of view context is bind to table UI elements of attributes is nothing but table
mapping binding.
14. What is cordinality of a node?
It is controller the number of records accommodation a node. Cordinality can also control the
number of records can be selected from table.
4 types of cordinality
0------n, 0------1, 1------1 and 1------n
15. Singleton node?
Single ton node are represent by a single node instance, node collection comes cache time load
selection of the format node changes.
16. What is window and types of windows?
It is displaying the content in views with various UI elements
3 types of windows
Popup window
External window
Dialog box window

17. Backend Roles not displayed in Portal groups?

Q) A new backend role has been created by the name xxx. I need to map portal role with the backend role.
When i go to useradmin and search the backend role (xxx) in groups, i dont find the backed role. Is there any
configuration i need to do?

Ans:

We will be able to locate the role under this folder

"pcd:portal_content/com.sap.portal.migrated/SAPComponentSystems/roles/"
When you are searching for the roles or group use the wild characters * .
Prefix and suffix the role you are searching with a * and you should be able to find
it. Also, during the role upload process, ensure that the role is transported to the
portal first, before searching for the same.

Prerequisites for Role Upload

Before you can upload objects to an SAP Net Weaver Portal from an ABAP system, you must
satisfy the following requirements:

Import the portal plug-in to the ABAP system

Up to release SAP NetWeaver Application Server (AS) ABAP 6.20 you
must import the SAP Enterprise Portal plug-in 6.0.
Download the plug-in from the SAP Service Marketplace
at http://service.sap.com/swdc (Downloads tab) SAP Installations
& Upgrades Entry by Application Group Plug-Ins SAP Enterprise
Portal Plug-In WP-PI <AS ABAP release> Installation. See also SAP
Note 723189.
From release AS ABAP 6.40, the functions of SAP Enterprise Portal plug-in are
included in PI_BASIS, no import necessary.
You must have authorization in the back-end system
In the back-end system you need authorization S_RFC for function group PWP2.
Configure the system landscape in the portal
In your portal system landscape, you must create a system for each ABAP
system from which you upload objects. You must define a connection to the
ABAP system for this system. For moreinformation about system landscapes,
see System Landscape.
When you create a system with a connection to an ABAP system, you must
maintain at least the following property categories:

Connector

User Management

Internet Transaction Server (ITS)

As of SAP NetWeaver 7.0 AS ABAP Support Package Stack 7, ITS is
integrated into the Internet Connection Manager.
Define a system alias for each system you create in the portal.
The system alias must match the logical system name of the ABAP
system (for example,QWACLNT100).
Prerequisites for uploading the user-role assignment
To reuse the user-role assignments from the ABAP system in the portal after
the upload, you must satisfy one of the following requirements:

Use identical user IDs in the portal and in the ABAP system and you
perform the role upload with the SAP Logon Ticket logon method. If the
user IDs are identical, a user that corresponds to a user in the back-end
system is automatically assigned in the portal when the user assignment
of a role is uploaded from the back-end system. The easiest way to do
this is to define the ABAP system as data source for the User
Management Engine (UME).
If you perform the role upload with

the User ID and Password logon method, you must maintain the user
mapping in the portal for all the users in the back-end system. This only
makes sense if you only need to do so for a few users.

1.
1.

1.

1.
1.

1.
1.

1.

1.

1.

User mapping must be unambiguous. If more than one portal user is

mapped to a single user in the ABAP system, you cannot upload user-role
assignments.
18. Creating JCO destination which logon methods u can use?
UID/PWD, logontickects, X5090ERTS
19. What is collaboration?
It is used to provide interaction between the people (end users,
employees) collaboration NetWeaver provide chatting mails voice over
internal protocol collaboration provide both synchronous and asynchronous
communication. Synchronous collaboration both sender and receiver will be
online, asynchronous only receivers it is in online.
20. Apply portal themes which controls we have customized in
portal?
Masthead, tool area, top-level navigation, DTN and Content area.
21. What is purpose of theme editor?
It is import and export themes from portal server.
22. What is procedure for applying themes to all end users to belong
to portal?
Using Rule collection
If user =*
Then portal desktop=our desktop
23. How to send the data one component to another component?
By using interface controller
24. What is the advance of MVC?
MVC is model view controller which separates presentation logic and
business logic. Model represents business logic.
View represents presentation logic.
What is purpose of interface view?
Communication between two applications by using start up dialup and exit
plug
Startup plug is starting the applications and Exit plug is stopping the
application.
25. What is the portal content translation?
It is a collection of various PCD objects like pages iview and
worksets and roles that has to be translated.is used for portal internationalization
for providing multiple supports.
26. SAP GUI for window, GUI for Java and GUI for HTML?
GUI for window: if Tcode is running under ABAP engine sap GUI
software required in a client machine.
GUI for Java: if Tcode is running under ABAP engine J2SDK software
required.
GUI for HTML: if Tcode is running under ABAP engine ITS
required.
27. How and where to change model data JCO destination and Meta
data JCO destination?

Whenever import function module part of a model object internally

model access will be available under model selection. The metadata used as
part of function modular will be available under dictionaries. Model data JCo
destination can be changed under model selection in NWDS. Meta data JCo
destination can be changed under dictionaries selection in NWDS.
1.

1.

1.

1.

1.
i.
ii.
iii.
iv.
v.

28. What is view and model object?

View is a visual screen area and contain screen element.
Model objects contain input and output nodes with attributes it is
combination of model class and model properties.
29. Data modular and navigation modular?
Data modular used to define dataflow between models, views and
controllers with the help of context mapping and model binding.
Navigation modular used specifies navigation between views using out
bound in bound plug navigation.
30. When will you create custom controller?
The custom controller whenever calling N number of function
modules or no of model objects or N no of BAPI/RFC from backend system we will
create custom controller.
31. Where is the path of Config toll and SDM, visual admin and copy
the business packages?
Config toll path:
/user/sap/sr6/devbmg500/j2ee/jspm/go.bat.
SDM
:
/j2ee/configtool/configtool.bat
Visual Admin
:
/j2ee/admin/go.bat
Business packages:
/user/sap/trans/eps/in/cms server6SR6
32. How many types of NWDI contains?
NWDI contains 4 types
i) Design time repository(DTR)
ii) Component Build Service(CBS)
iii) Change management service(CMS)
iv) SLD
33. What is system object and what are system properties?

System Object is a set of connection properties to represent an external or SAP systems (SAP
R3, /CRM/BI) used to retrieve data into portal. We can create a System Object in any one of the three
ways.
Based on System Template (Template)
Based on Portal Content
(PAR)
Coping Existing Systems
(System)

Steps to Create a System Object in the portal are as follows

System Alias settingsConnector settings
ITS settings
WAS settings
User Management Settings
Creating System Object for R3 System:
You can create R/3 backend system connection objects using the SAP provided template
Dedicated Application Server for R/3 System.

System Name:
The title, or friendly name, for the system
Mandatory, exists for each system.
Example System Name: CRM_200
System Type: The type of the SAP system, such as ERP, BW, and so on:
SAP_R3
SAP_BW
SAP_CRM
Example System Type: SAP_CRM
Application Host:
Address or name of SAP Application Server (dedicated component)
Say like R/3 server on : 10.1.1.10
Gateway Host:
Used by JCO to connect to the gateway service, this connects to the SAP system.
Note: Relevant only in the Dedicated SAP system template.
Sample Gateway Host: 10.1.1.10
Gateway Service: Service: sapgw00 --> In general, sapgw+

Logical System Name: Logical system name to which the system is pointing
Say Logical system Name:
Here you have to enter the logical system name of your central system. SAP recommend the
following notation: CLNT
For example you have a central development system called Erinome with the Alias CB0 and
the client 100 then you have a logical system name CB0CLNT100.

Remote Host Type:

Type of remote host
Default value: 3
Sample Remote Host Type: 3
SAP Client:
Logon parameter to client of back-end system Sample: 200
System ID (SID):
Name of SAP back-end system Sample: SXP
SAP System Number:
Number of SAP back-end system instance (dedicated).
Sample System No: 00
Server Port:
Port number of application server. Sample Server Port: 3200
The following ITS settings are required when using transaction iViews
Go to the property category for ITS or WAS according to the basis layer of the backend System.
Description:

Description of the server Sample: Sample ITS

Protocol:
Http or https Sample: HTTP
Host Name:
Name of the server as full qualified host name Sample ITS Host Name: 10.175.0.29
Path:
The path prefix for the used web applications Sample ITS Path: /scripts/wgate/webgui/!
After providing properties for Connector and ITS/WAS. We need to create Logon method for
implementing SSO between portal and backend system.
To do this activity we need to go to the property User Management.
Logon Method SAP: Logon Ticket / UIDPW
User Mapping Type: Admin, user
Go to the Display drop down list box to provide System Alias.
System Alias:
At least one alias should be created for system object to perform user mapping and as well as
providing access to iview to connect to the backend system for retrieve data.
Alias: Can give any Name. For Sample given following alias: CRM_200
Finally click on save to apply all the properties to the system object.