0 оценок0% нашли этот документ полезным (0 голосов)
495 просмотров3 страницы
The document provides solutions for errors that may occur when accessing the NWBC link after installing GRC 10 AC. The solutions include:
1. Activating relevant service nodes under SICF
2. Ensuring at least one HTTP and SMTP service is created and active
3. Adding required ICM and MS parameters to the instance profile
4. Updating the hosts file on end user PCs
5. Generating standard role profiles using SUPC
6. Activating required Web Dynpro ABAP services
The document provides solutions for errors that may occur when accessing the NWBC link after installing GRC 10 AC. The solutions include:
1. Activating relevant service nodes under SICF
2. Ensuring at least one HTTP and SMTP service is created and active
3. Adding required ICM and MS parameters to the instance profile
4. Updating the hosts file on end user PCs
5. Generating standard role profiles using SUPC
6. Activating required Web Dynpro ABAP services
The document provides solutions for errors that may occur when accessing the NWBC link after installing GRC 10 AC. The solutions include:
1. Activating relevant service nodes under SICF
2. Ensuring at least one HTTP and SMTP service is created and active
3. Adding required ICM and MS parameters to the instance profile
4. Updating the hosts file on end user PCs
5. Generating standard role profiles using SUPC
6. Activating required Web Dynpro ABAP services
After installing GRC 10 AC component, a user may experience an error starting NWBC and may experience one of the following errors: 1. Invalid HTTP Configuration 2. HTTP Configuration/service not defined 3. NWBC transaction code returns blank screen 4. NWBC transaction code returns some service node errors. Cause: The above mentioned errors/issues occurs due to incorrect configuration. Ensure to complete all the below discussed configurations: Solution: # 1 Activate all the relevant service nodes From SICF Maintain ICF Service Transaction code, ensure to activate the below service nodes/sub nodes: default_host-> sap -> public default_host-> sap -> bc default_host-> sap -> grc Ensure to activate all the below sub nodes too (this will have the NWBC node too). # 2 Ensure to add atleast one HTTP & SMTP service To verify the existing ICM services, one can go to SMICM ICM Monitor transaction code. The services are available from Goto -> Services.In case if there are no services listed, create atleast one HTTP and SMTP service using the Service -> Create option. here is an example of the set up.
Also, ensure that both the services are Active.
# 3 Add the below ICM & MS parameters: The below parameters (considering that the system has only one HTTP and SMTP service) are required to be added in the instance profile (via transaction code RZ10). icm/server_port_0 ms/server_port_0 ms/server_port_1 icm/server_port_1 To know the parameter options, refer the parameter default value in RZ11. Ensure to restart the server once the parameters are added.
# 4 Update hosts file in end user PCs
The hosts file should have the GRC server entry. Ensure that it is updated, since the NWBC URL should not have any IP addresses directly. # 5 Please notice the profiles for the standard roles are not generated on a new installation, run SUPC to make sure all SAP_GR* profiles have been properly generated. #6 Check to make sure you have the following roles in place: 1) SAP_GRC_FN_ALL 2) SAP_GRC_FN_BASE 3) SAP_GRC_FN_BUSINESS_USER 4) SAP_GRC_NWBC also, check this note see this note : http://search.sap.com/notes?id=1088717 WDA services needs to be activated. if not, this has to be a URL issue with the latest SP06 version. Services for Web Dynpro ABAP For Web Dynpro ABAP (WDA), you must activate the following services in the system: Using WDA applications /default_host/sap/bc/webdynpro Note that, in this case, you should activate only the node itself, not the subnodes. /default_host/sap/public/bc This node is automatically activated when you activate the subnodes described below. Similarly, in this case, you must activate only the node itself and the following subnodes: /default_host/sap/public/bc/ur /default_host/sap/public/bc/icons /default_host/sap/public/bc/icons_rtl /default_host/sap/public/bc/webicons /default_host/sap/public/bc/pictograms /default_host/sap/public/bc/webdynpro/* (ssr, mimes, and so on) /default_host/sap/public/myssocntl