Problem while creating Logical System Connecting Portal to ECC (Backend)...

Question

Hi
- I am trying to connect portal to ABAP so that from portal's iView i could access any ABAP T-Code (e.g. SE37).
- Secondly, just wanted to let you know that i am not implementing SSO.
- I used iView's SAP GUI Type = SAP GUI for HTML.
I made following 3 tests, out of which ITS connection is failed. and while previewing my iView i m not able to connect with ABAP and giving error:  "The URL http://192.168.1.104:8001/sap/bc/gui/sap/its/webgui was not called due to an error."
Could u pls guide me what to do....  And i mentioned everything at the bottom in detail.
Thanks & looking forwarded for your replies.....
SAP Web AS Connection (Successful)
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the server to see if it is alive.
7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
8. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (192.168.1.104:8001)
5. The host name 192.168.1.104 was resolved successfully.
6. The server 192.168.1.104 was pinged successfully.
7. The Web AS ping service http://192.168.1.104:8001/sap/bc/ping was pinged successfully.
8. An HTTP/S connection to http://192.168.1.104:8001/sap/bc/bsp/sap was obtained successfully.
ITS Connection (Failed)
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether the system object has a valid system alias
4. Check whether a SAP system is defined in the system object
5. Validate the following parameters: ITS protocol; ITS host name
6. Checks if the host name of the server can be resolved.
7. Pings the server to see if it is alive.
8. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. Retrieval of the default alias was successful
4. The system object represents an SAP system
5. The following parameters are valid: ITS Protocol (http) ITS Host Name (192.168.1.104:8001)
6. The host name 192.168.1.104 was resolved successfully.
7. The server 192.168.1.104 was pinged successfully.
8. User mapping is valid
9. An HTTP/S connection to http://192.168.1.104:8001/sap/bc/gui/sap/its/webgui/ was not obtained successfully; this might be due to a closed port on the Firewall.
Test Connection with Connector (Successful)
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
1. Retrieval of default alias successful.
2. Connection successful.
I am getting following error while Previeiwng iView.
Error when processing your request
What has happened?
The URL http://192.168.1.104:8001/sap/bc/gui/sap/its/webgui was not called due to an error.
Note
The following error text was processed in the system D10 : Template interpretation cancelled, syntax error.
The error occurred on the application server eccdcs1s_D10_01 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
      SYSTEM-EXIT of program SAPLSFUNCTION_BUILDER
      Function: RS_FUNCTION_INITIAL_SCREEN of program SAPLSFUNCTION_BUILDER
      Method: IF_WB_PROGRAM~PROCESS_WB_REQUEST of program CL_FB_FUNCTION_INITIAL_SCREEN=CP
      Method: DO_THE_NAVIGATION of program CL_WB_NAVIGATOR===============CP
      Method: DO_THE_NAVIGATION of program CL_WB_NAVIGATOR_VIS_AS_DYNPRO=CP
      Method: PROCESS_WB_REQUEST of program CL_WB_MANAGER=================CP
      Method: PROCESS_REQUEST_QUEUE of program CL_WB_MANAGER=================CP
      Method: IF_WB_MANAGER~SET_WORKSPACE of program CL_WB_MANAGER=================CP
      Method: START_INTERNAL of program CL_WB_STARTUP=================CP
      Module: MANAGER_START of program SAPLWB_MANAGER
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the   system D10 in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server eccdcs1s_D10_01 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server eccdcs1s_D10_01 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 001 -u: SAPUSER -l: E -s: D10 -i: eccdcs1s_D10_01 -w: 0 -d: 20090924 -t: 202054 -v: RABAX_STATE -e: ITS_CANT_LOAD_INCLUDE
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
Edited by: Harpal Singh on Sep 24, 2009 4:55 PM

Answer 1

Hi,
> Goto SE80, Select "Internet Service". Give service name as WEBGUI and enter. Right click on the WEBGUI and select Publish -  > Complete service.
Source : http://wiki.sdn.sap.com/wiki/display/BI/BiAdminCockpit+Issues
Or call transaction SIAC_PUBLISH_ALL_INTERNAL to publish all services.
[Note 964521 - Short dump ITS_CANT_LOAD_INCLUDE w/ call of SAP GUI for HTML|https://service.sap.com/sap/support/notes/964521].
Regards,
Pierre