SAP NWBC for HTML and Desktop configuration steps

Summary :-

     This dcoumnenst conatin the information about requirement , hardware , configuration steps and Comparison of NWBC for Desktop and NWBC for HTML.

Created by  : Brindavan Mookaiah

Designation : SAP BASIS Consultant

Table of content:-

1)  Hardware and software requirement…………………………………………………………………………………….

2)  Differences Between NWBC for Desktop and NWBC for HTML……………………………………………….

3)  Configuration steps……………………………………………………………………………………………………………

4) Insatllation NBC for Desktop and HTML………………………………………………………………………………..

NWBC is shipped in two variants:

1. NWBC for Desktop is a MS Windows/.NET-based application that needs a local installation. It uses SAP GUI for Windows under the hood to run Dynpro-based transactions and integrates Web
applications using the Internet Explorer control in its shell.

2. NWBC for HTML is a browser based version using HTTP/s for connecting to a SAP NetWeaver Application Server ABAP backend. SAP GUI transactions are rendered using the SAP GUI for HTML.

  you prefer based on your client requirmenet.

Step 1

   Hardware and software requirement

Client Installation
NWBC for desktop  4.0 NWBC for HTML
Operating System Microsoft Windows platforms: X SP3, Vista, 7 Microsoft Windows platforms: XP SP3, Vista, 7
Hardware At least 1 GB memory ,Minimum screen size of 1024×768,The NWBC application (using .NET3.5 and WPF) running on the desktop consumes
main memory in the magnitude of 100 MB
No desktop installation is required,Browsers need minimal resources to render the HTML  representation of the navigation tree ,Refer to the PAM for details under NetWeaver 7.0
Internet Explore Microsoft Internet Explorer 8.0, 9.0 and 10 Microsoft Internet Explorer 6 / 7 / 8 / 9 / 10 / 11
software requirement .Net 3.5, SAP Netwarver web application server 7.31 Zero footprint

Step 2

Differences Between NWBC for Desktop and NWBC for HTML

Differences Between NWBC for Desktop and NWBC for HTML
Delta NWBC for Desktop – NWBC for HTML
Feature NWBC for Desktop NWBC for HTML
Menus:
                     Yes
             NO
Favorites
Personalize
Help
Individual menu entries
Search:
                      Yes
                  NO
Enterprise search
External search
Desktop search
Navigation Panel:
                       Yes
              NO
Drag&Drop of work centers
List of available work centers
Personalized work center icons
Quick navigation at work center
Quick Launch                         NO                 NO
Hide top-level navigation panel                        NO                  NO
Window manager                        NO                 NO
Branding image                        NO                 NO
Logoff URL                        NO                  Yes
SAP GUI integration SAP GUI for Windows (more applications, better performance) SAP GUI for HTML
Perfomance aspects Client:
The program running on the desktop consumes main memory in the magnitude of 100 MB.

Network :
2 HTTP requests with a payload of typically 50 KB (this depends on the role setup) to read the complete navigation tree. Further sporadic small HTTP requests are fired to the server to resolve navigation targets which are needed to start additional applications. This data is also only fetched once on demand and from then onwards cached on the client.

Server:
1 ABAP session with a lifetime of 15 seconds and main memory consumption of approximately 3 MB.

Client:
Browsers need minimal resources to render the HTML representation of the navigation tree. This can be neglected.

Network :
Each shell interaction step: 1 HTTP request with a payload of typically 20 KB.

Server:
Each interaction step: 1 ABAP session with a lifetime of 15 seconds and main memory consumption of approximately 3 MB.

Installation Desktop installation Zero footprint
System scenario Connect against an ABAP system or an Enterprise Portal Single ABAP system scenarios
Definition of initial window size and position Initial window size and position cannot be influenced

Step 3

Configuration steps

SAP NWBC Configuration – High Level
Internet communication Channel Enable /Modify HTTPS port setting (Check in T-code SMICM)
Internet Communication Frame work Enable /Activate ICF node in T-code SICF for NWBC cookbit
System security Install the SAPCRYPTOLIB, Enable the SSO cookies(login/accept_sso2_ticket=1,login/create_sso2_ticket=2),Configure the SSL in STRUST.
Fully Qulified Domain name ICM/host_name_full= XXX
System Scripting setting sapgui/user_scripiting=TRUE
Switch framework setting Activate Business function(/kyk/gen_aio_simplification) in T-code SFW5
Role maintenance In table maintenance t-code SM30 ( SSM_CUST= yes)
Software NWBC for desktop 4.0 & NWBC for HTML no software required

Step 4

4.1 Download NWBC forDesktop client installation from SAP(service Market place)

4.2 Install the NWBC for Desktop 4.0

4.3 Activate the NWBC on ABAP system in T-code SICF “/default_host/sap/bc/nwbc

NWBC.JPG

4.4 you will get the URL link like https://<servername>:portno/sap/bc/nwbc?sap-client=000

4.5 Cliec the NWBC and mentione the URL like bleow

NWB1.JPG

4.6 then click on log on

NWBC3.JPG

After enter the log on user name and password you will able to see the belwo screen.

NWBC5.JPG

NWBC7.JPG

NWBC for HTML

Once you activated the services , the URL will genarted and able to access SAP from HTML page.

HTML.JPG

HTML2.JPG

Note : Both scenarios the user-ID must exist in ABAP system & proper authorization.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply