Webnbsp;Dynpronbsp;fornbsp;ABAPnbsp;Config…

After you install the Application Server ABAP (AS-ABAP), all Internet Communication Framework (ICF) services are delivered as inactive (this is for security reasons). Following the installation you must decide, on an application-related basis, which services you must manually activate.

ICF, Service
You are not authorized to view this page
RAISE_EXCEPTION
Forbidden,
HTTP error 403
Host is not active
Service is not active
CL_WDR_UCF=>STARTUP_CHECKS,
Exception CX_WD_GENERAL: In the call list of the dump, you find the method CL_WDR_CLIENT_ABSTRACT_HTTP=>STARTUP_CHECKS.

Since several services may be executed when you call a URL, you must activate all service nodes in the SICF tree. As a result, the URL path is represented in ICF subnodes (services). If, for example, you want to activate services for the URL /sap/public/icman , you must activate the service tree default_host in transaction SICF. You must then activate the individual services sap, publicandicman 
You can activate an ICF service as follows:

If the default_host node is inactive in transaction SICF, the HTTP request may produce a "RAISE_EXCEPTION" ABAP runtime error
              stating that the HOST_INACTIVE exception condition was triggered.

If a service is inactive in transaction SICF, the system displays the error text "Forbidden" when you access this service.
You can also use the report rsicf_service_activation to activate a group of ICF nodes that can be predefined. When you execute this report, you can use the following predefined groups (technical name):

• WEB DYNPRO ABAP

• WEB DYNPRO ABAP DESIGN TIME

• WEB DYNPRO ABAP TEST APPS

For Web Dynpro ABAP (WDA), you must activate the following services in the system:

• Using WDA applications

• Using the WDA development environment

• WDA test applications for troubleshooting

• Support for the Internet protocols (HTTP, HTTPS and SMTP) in the AS-ABAP

• Using the load distribution

• ICF test applications:

• 1009930

• 1008689

Various problems may occur when you load a view in the View Designer, mainly with the preview display.


1) A Java Script error dialog box ("Object expected") appears immediately after the loading process or when you switch to change mode.


2) The preview is not displayed. Instead, the error message "403 Forbidden" appears.


3) When you try to start the View Designer using a proxy, an error message appears, indicating that the page cannot be displayed, or that the DNS or server cannot be found.


4) The entire preview area in the View Designer remains white, but no error message is issued.


5) The preview is not displayed. Instead, the system issues the error message "The page cannot be displayed".

Web Dynpro ABAP, view, View Designer, layout, preview, JavaScript, proxy, HTTPURLLOC

1 a) An error occurred while urgently required Java Script files were read from the Mime Repository (-> Note 979039).

  b) This error stems from a timing problem between the View Designer and HTML Control. The mode is changed before the preview is fully loaded. This Java Script error therefore occurs during the reloading operation (which is connected to the mode change). No feasible options are available to solve this problem.


2 a) One or more services required by the View Designer are not available. These must be activated in transaction SICF.
(-> Notes 1008689, 1088717, 603624)

  b) The HTTP protocol (standard) is mistakenly used, where HTTPS should in fact be used. In transaction SMICM, deactivate the HTTP service for all affected application servers.


3) The proxy connection requires a corresponding entry in the HTTPURLLOC table. Either the entry cannot be read, or it is not available (-> Notes 979039, 983386)


4) Check the HTTPURLLOC table. It may contain an incorrect entry.


5) Using transaction SMICM or RZ11, check the setting of the profile parameter icm/host_name_full. This should display a fully specified host name, but under no circumstances must it display entries of the form "localhost".

In addition to the notes specified above, refer to the notes listed under "Related Notes".


In addition, the following documentation links may be useful (you can directly access the links in the attached HTML file):

HTTPURLLOC: http://help.sap.com/saphelp_nw2004s/helpdata/en/42/d547ab30b6473ce10000000a114e5d/frameset.htm

url generation:
http://help.sap.com/saphelp_nw2004s/helpdata/en/59/31ae42e0fac911e10000000a1550b0/frameset.htm

SMICM and service functions:
http://help.sap.com/saphelp_nw2004s/helpdata/en/ac/8f813a34872769e10000000a114084/frameset.htm

profile parameters:
http://help.sap.com/saphelp_nw2004s/helpdata/en/95/1528d8ca4648869ec3ceafc975101c/frameset.htm