Netweaver Development Infrastructure (NWDI)

NWDI is basically for Developers who are working on Portal or J2ee engine. Developers are required for developing webdynpro application - j2ee engine and portal server.
It provides a team environment for developers working development landscape.. Infrastructure..

Components of NWDI:
DTR – Design time repository
CBS – Central Build Services
CMS – Change management system
SLD – System Landscape Directory

DTR – provides a central location for storing applications, software, software components or development components.

CBS – it stores or gives access to default libraries required for development software components.

CMS – its helps in transporting development components to different runtime systems.
    1.Development system
    2.Test Quality system
    3.Consolidation system
    4.Production system
It provides automatic transportation.

SLD – collection of systems in the organization.

TRANSPORT PACKAGES

Transport package is a collection of various PCD(Portal Content Directory) objects like iviews, pages, worksets, roles, portal themes, portal desktop etc..

The extension of a transport package is .epa (enterprise portal archive)

A transport package can contain another transport package.

The purpose of creating transport package is to export and import the PCD objects from one server to another server.

DEV >TEST
TEST >PRD
DEV > PRD

Role Activities

The activities Involved in system administration Role:
1.    Creating System objects
2.    Portal Display for Changing Look and feel of portal according to client preference
3.    Transport of packages ie. Import and export from one server to another
4.    Locking and unlocking the portal Content objects
5.    Monitoring the services related to portal
6.    Permissions for portal objects
7.    Provides Support Platform for initial troubleshooting

The activities involved in User Management Role:
1.    Creating Users, Roles, Groups in Portal
2.    Locking/unlocking Users, Roles, Groups in Portal
3.    Exporting Users, Roles and groups from portal
4.    Assigning Roles to users or groups (group is a collection of users)
5.    User Mapping for Backend Systems from portal.
6.    Batch Import of Users, Roles , Group Data into portal. The purpose of Batch Import is to create ‘n’    number of users, roles and groups into portal simultaneously.
7.    We can view the activity Reports which can give the information about currently logged in users.

The Activities involved in Content Administration Role:
1.    Creation of Iviews, Pages, Worksets, layout and folders. (The objects are considered as PCD objects – Portal Content Directory objects)

Predefined Roles given by SAP in portal

The Predefined Roles given by SAP in portal:
1.    System Administration
2.    Content Administration
3.    User Administration

Other Roles available in Portal Area:
1.    ESS Role
2.    MSS Role
3.    VC Role
4.    NWDI Role
5.    GP Role
6.    EU Role
7.    Super Admin Role

Super Admin Role is a composite role which contains three pre-defined roles
1.    Content Admin
2.    System Admin
3.    User Admin

Important Urls to access various predefined Portal Applications

IMPORTANT URLS

1.    To access Enterprise Portal

http://hostname:portno/irj/portal

2.    To access SLD

http://hostname:portno/sld

3.    To access NWDI

http://hostname:portno/devinf

4.    To access WebDynpro Content Administration

http://hostname:portno/webdynpro/welcome/Welcome.jsp

5.    To access User Administrator

http://hostname:portno/useradmin

6.    To access Portal Server System Properties

http://hostname:portno/index.html

7.    To access Support Platform for Initial Troubleshooting

http://hostname:portno/sp

8.    To access Visual Composer

http://hostname:portno/VC

9.    To access Composite Application Framework Administration

http://hostname:portno/caf

10.    To Administer Web Services

http://hostname:portno/wsnavigator

Changing the Look and Feel of Enterprise Portal Application

Changing the Look and Feel of Enterprise Portal Application.

Default Framework Page:
Default Framework page defines the default layout of the portal application.

Default Framework page contains:
1.    Mast Head (Branding Imaging and Company Logo)
2.    Tool Area (Search functionality)
3.    Roles
                           } - Top Level Navigation
4.    Workset
5.    Page Header
6.    Detailed Navigation
7.    Content Area  {Inner Page}

Portal Theme is required to change Look and feel (Branding image, company logo, fonts, colors etc) according to client preferences or enduser requirement.

The predefined theme templates given by SAP :
1.    SAP High Contrast Black
2.    SAP High Contrast
3.    SAP Chrome
4.    SAP Streamline
5.    SAP TradeShow

Theme Editor is used to design our own themes.
Creating Portal Desktop and theme:
1.    Logon to Portal
2.    Goto System Administration
3.    Goto Portal Display
4.    Theme Editor
5.    Select one of the Theme template
6.    Change Branding Image, company logos, fonts, colors etc..
7.    Click on Save As and specify

• Theme Name: ClassTheme
• Theme ID: ClassTheme
• Folder ID: portal_content/themes

8.    Click on Save and Click OK
9.    Click Save again.
10.    To make same changes in Roles + Workset etc under Top-level navigation
11.    Save
12.    Create a Desktop:
13.    Click on Desktops and Display Rules
14.    Right Click on Portal Conent ->New -> Portal Desktop
15.    Specify Portal Desktop Name: Class Desktop
          Desktop ID: Class Portal Desktop
    (Portal Desktop Editor allow us to create portal desktop)
    (Portal Desktop can contain Framework pages and Themes)16.    Expand portal content -> Expand Themes
17.    Right click on your theme and Select “Add theme to Portal Desktop”
18.    Assigning Framework page to Desktop:
19.    Expand Portal Users -> Expand standard Portal Users
20.    Right Click on Default Framework page and select “Add Framework Page to Desktop”
21.    Click on Save.
22.    Creating Rule Collections:
23.    Rule collection is used to assign portal desktops, portal themes to corresponding users, groups, roles, browsers etc.
24.    Expand Portal Administrators -> Expand Super Administrators and right click on “Master Rule Collection” -> open -> Object
25.    Rule collections are used to assign ‘Portal Desktop’ to Portal endusers.
26.    A Role collection contains IF, THEN expression condition
If user = *
Then Portal Desktop = Select or click on portal desktop path/link
Goto portal content, right click on our created Desktop and “Add portal Desktop to expression” and click on ‘Apply’
Click Save
27.    To check logoff and re-login

The Portal Desktop can be assigned based on : -
1.    User
2.    Roles
3.    Groups
4.    Bandwith
5.    Browser type
6.    Browser version
7.    Url Alias

Java Instance Startup Process

The above illustration describes the Java Instance Start up Process.

At first, on command 'startsap' - the Database is started first, then the SAP Central Services and then starts the Java Dispatcher and Server Process along with SDM. Jcontrol is started which internally starts Jlaunch process.