cancel
Showing results for 
Search instead for 
Did you mean: 

Webas and ITs connection test fails during connection test in Portal

Former Member
0 Kudos

Hi,

Webas and ITs connection test fails during connection test in Portal, which was working earlier with same parameter settings .

Please find the error.

SAP Web AS Connection

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 WAS ping service; works only if the service is activated on the ABAP WAS.

7. 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 (hostname:8000)

5. The host name hostnamewas resolved successfully.

6. The Web AS ping service http://hostname.com:8000/sap/bc/ping was not pinged successfully. If the ping service is not activated on the Web AS, you can try to call the ping service manually.

7. An HTTP/S connection to http://hostname:8000/sap/bw/BEx was not obtained successfully; this might be due to a closed port on the Firewall.

ITS Connection

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. 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 (hostname:8000)

6. The host name hostnamewas resolved successfully.

7. An HTTP/S connection to http://Hostname:8000/sap/bc/gui/sap/its/webgui was not obtained successfully; this might be due to a closed port on the Firewall.

Thanks and Regards,

Satish

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

ansawered

Former Member
0 Kudos

I experienced this same issue. I executed transaction SICF as suggested above and found serice ""/sap/bc/gui/sap/its/webgui " inactive. I activated the service and this resolved the issue.

p330068
Active Contributor
0 Kudos

Hi Sathish,

Please check and verify WAS infromation in backend system : Go to SE37 >> Test/Execute Function module RSBB_URL_PREFIX_GET and for ITS infromation in backend system : Go to SE37 >> Utilities >> Settings >> Select "Internet Transaction Server" >> Look for ITS server name/port and path.

Refer to /people/marcel.salein/blog/2007/03/14/how-to-create-a-portal-system-for-using-it-in-visual-composer

Also please update host file and check if there is any Firewall in network causing the problem.

Regards, Arun Jaiswal

Former Member
0 Kudos

Hi Satish,

I believe services for WAS and ITS are not active at your ECC side.

Go to SICF and check for below services -

/default_host/sap/bc/gui/sap/its/ (with sub trees)

/default_host/sap/public/bc/bsp (subtrees as well)

And also do test connection by right clicking on the service to be sure.

Regards,

Dipesh

former_member227283
Active Contributor
0 Kudos

Hi,

1. Check abap stack is up or not.

2. login to host of portal server and do telnet abap stack host on port 8000 (hostname:8000)

telnet <abap stack> 8000

let us know the result

Thanks

Anil

Former Member
0 Kudos

Hi Anil,

Thanks,

The ABAP Stack is Up and Running .

Regards,

Satish

Former Member
0 Kudos

Hello Sathish,

Please check the HTTP services from SMICM / restart the services.

Try to open the test URL explicitly from a browser & check if there are any other problem.

Also if you are using web dispatcher in your landscape - please check too.

Regards,

Sumanta