SAP Web AS Connection test error from EP to BW

[Former Member]

Hi,

I am getting a connection test error for BW system created in NW04s EP 7.

I am in the process of integrating BW with EP as per the SAP documention.

As per the documentation I have created BW system and alias in EP and export / import

of certification in EP & BW is done. BW profile parameters also adjusted for single sign on.

The web as ping service is active and am able to pint manualy.

Please provide me some idea on this issue.

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 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 (sapbw01.otegroup.com:8100)

5. The host name sapbw01.otegroup.com was resolved successfully.

6. The server sapbw01.otegroup.com was pinged successfully.

7. The Web AS ping service http://sapbw01.otegroup.com:8100/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.

8. An HTTP/S connection to http://sapbw01.otegroup.com:8100/sap/bw/BEx was not obtained successfully; this might be due to a closed port on the Firewall.

Thanks

Achuthanandan

[Former Member]

Dear Team,

I am facing the below issue after performing the BI-EP Integration while testing

SAP Web AS Connection:

: Test Details:

The test consists of the following steps:

1. Check the validity of the system ID in the system object

2. Check if the system can be retrieved

3. Check if the system object has a valid system alias

4. Check if an SAP system is defined in the system object

5. Validate the following parameters: Web AS protocol; Web AS hostname

6. Checks if the host name of the server can be resolved.

7. Pings the Web AS Ping service (works only if the service is activated on the Web AS, and only on ABAP Web AS)

8. Check HTTP/S connectivity to the defined back-end application

Results

1. The system ID is valid

2. System retrieved successfully

3. Retrieval of the default alias was successful

4. The system object represents an SAP system

5. The following parameters are valid: ICM Protocol (http) ICM Host Name (FFDUBID01V.federalfoods.ae:8000)

6. The host name (FFDUBID01V.federalfoods.ae) was resolved successfully

7. The WAS ping service (http://FFDUBID01V.federalfoods.ae:8000/sap/bc/ping) was not pinged successfully. If the ping service is not activated on the WAS, you can try to call the ping service manually.

8. An HTTP/S connection to http://FFDUBID01V.federalfoods.ae:8000/sap/bw/bex?sap-client=300 was not obtained successfully (this can be due to closed port on the firewall)

ITS Connection:

: Test Details:

The test consists of the following steps:

1. Check the validity of the system ID in the system object

2. Check if the system can be retrieved

3. Check if the system object has a valid system alias

4. Check if an SAP system is defined in the system object

5. Validate the following parameters: ITS protocol; ITS hostname

6. Checks if the host name of the server can be resolved.

7. Check HTTP/S connectivity to the defined back-end application

Results

1. The system ID is valid

2. System retrieved successfully

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 (FFDUBID01V.federalfoods.ae:8000)

6. The host name (FFDUBID01V.federalfoods.ae) was resolved successfully

7. An HTTP/S connection to http://FFDUBID01V.federalfoods.ae:8000/sap/bc/gui/sap/its/webgui?sap-client=300 was not obtained successfully (this can be due to closed port on the firewall)

Connection Test for Connectors:

: Test Details:

The test consists of the following steps:

1. Retrieve the default alias of the system

2. Check the connection to the back-end application using the connector defined in this system object

Results

Default alias retrieved successfully

Connection failed. Make sure user mapping is set correctly and all connection properties are correct.

Kindly i request you to please advise. Thanks in advance.

Naveed

[Former Member]

Hi,

Check if the link http://FFDUBID01V.federalfoods.ae:8000/sap/bc/ping is accessible via the browser. Also check if the hostname can be pinged from the Portal host.

Also would suggest updating the Portal system to the highest NW 7.0 SP available at the SMP.

Regards,

Srikishan

[Former Member]

Tx SICF>Webgui service>right click opens up correctly ? If not check how to publish it correctly.

Thanks

[former_member476886]

Although this thread was posted some years back, but we encountered the same problem and managed to solve it. Here is the solution that worked for us:

1) Logon to your Abap BI System and execute tcode SICF and click execute

2) Expand default_host --> sap --> right-click on bw and select activate service

3) Go to your portal and conduct connection test for Web AS again, it should work now

Cheers.

[Former Member]

Hi Pritam,

Still it is not working for me even after deactivating/activating BW using SICF. I am still receiving the same error.

Regards

Mradul

[Former Member]

Check the below parameter is there?

SAPLOCALHOSTFULL=sapbw01.otegroup.com

[Former Member]

Check the below parameter is there?

SAPLOCALHOSTFULL=sapbw01.otegroup.com

[Former Member]

Please check the parameter in BW i.e

icm/host_name_full=sapbw01.otegroup.com is there or not? If it is not there then keep it and restart SAP one time.

[Former Member]

Please check the parameter in BW i.e

icm/host_name_full=sapbw01.otegroup.com is there or not? If it is not there then keep it and restart SAP one time.

[Former Member]

Try "Note 937697 - Usage of SAP NetWeaver BI Diagnostics & Support Desk Tool"

Nilesh

[JPReyes]

Did you connect the system using RSPOR_SETUP on the backend and nwa templates on the portal side?

If nor read carefully the manual as this is important for the integration of EP and BW(BI)

Regards

Juan

[Former Member]

Hi,

I think this should not be a problem, is your its and connector test working fine then you can proceed with sso.

Regards,

Vamshi.

[Former Member]

hi guru,

i have same problem.my system not getting ping successfully..can u help me...how can i start ping service???

thanks

vipul a kapadia

[Former Member]

Hi,

There is no firewall between EP & BW service.

We are using kerberos authentication for EP single sign on from windows.

Regards

[Former Member]

s per the result you have given it says that the ping is not possible and also check whether the port 8001 is blocked in the firewall,you can try telneting the 8001 port if telnet doen't happen then you have to make sure that the telent works.

Regards,

Vamshi.