Skip to Content
0
Former Member
May 23, 2007 at 10:41 AM

Problem with SAP Portal Connections etc.

748 Views

Dear All

We are facing some problems in our portal configurations.

Our Development and Production portals cannot seem to connect

to the back end R3 systems. We are able to log on properly but

when accessing some sections such as ESS, we receive the following

errors

-


Network Error (tcp_error)

A communication error occurred: ""

The Web Server may be down, too busy, or experiencing other

problems preventing it from responding to requests. You may

wish to try again at a later time.

For assistance, contact your network support team

-


and some sections of the portal give

-


“Could not connect to the R/3 System”

-


When testing the connections that are made to the R/3 systems.

It fails for WAS, ITS, Connectors and DQE.

The configuration and the Connection test result are given below.

For development when we try to access the ITS directly through

the Web Browser with

http://epd1.<company>.com:80/scripts/wgate/webgui/!

we get proper access to the ITS but in the portal

connection test it fails.

Require some quick assistance.

Regards

-


Configuration and Connection Test -


Portal Development:

-


WAS

-


WAS Description :

WAS Host Name :

WAS Path :

WAS Protocol - :

ITS

-


ITS Description : ITSR3D

ITS Host Name : epd1.<company>.com:80

ITS Path : /scripts/wgate/webgui/!

ITS Protocol : http

Connector

-


Application Host : SAPR3D1.<domain>.<cn>

Gateway Host :

Gateway Service :

Logical System Name :

Remote Host Type :

SAP Client : 110

SAP System ID (SID) : R3D

SAP System Number : 00

Server Port : 3600

SNC Library Path :

SNC Mode : 0

SNC Name :

SNC Partner Name :

SNC QOP (Security Level) : 0

System Type : SAP_R3

Trace Mode : 0

_____ Connection Test _________

SAP Web AS Connection

Test Details:

The test consists of the following steps:

1. Check that the system object defines an SAP system

2. Validate the following parameters: wap.WAS.protocol; wap.WAS.hostname

3. Check the HTTP/S connection to the defined backend application

Results

1. The system object represents an SAP system.

2. The following parameters are not valid: wap.WAS.protocol () ; wap.WAS.hostname ()

ITS Connection

Test Details:

The test consists of the following steps:

1. Check that the system object defines an SAP system

2. Validate the following parameters: wap.ITS.path; wap.ITS.protocol; wap.ITS.hostname

3. Check the HTTP/S connection to the defined backend application

Results

1. The system object represents an SAP system.

2. The following parameters are valid: wap.ITS.path (/scripts/wgate/webgui/!) ; wap.ITS.protocol (http) ; wap.ITS.hostname (epd1.<company>.com:80)

3. HTTP/S connection failed. Make sure the protocol, host name, and user mapping are correctly defined.

Test Connection with Connector

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

Retrieval of default alias successful

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

Portal Production:

-


WAS

-


WAS Description : R3P

WAS Host Name : sapr3pgrp.<domain>.<cn>:8001

WAS Path : /sap/bc/bsp/sap

WAS Protocol - : http

ITS

-


ITS Description : ITSP

ITS Host Name : ep.<domain>.<cn>

ITS Path : /scripts/wgate/

ITS Protocol : http

Connector

-


Application Host : sapr3pgrp.<domain>.<cn>

Gateway Host :

Gateway Service :

Logical System Name : R3PCLNT800

Remote Host Type : 3

SAP Client : 800

SAP System ID (SID) : R3R

SAP System Number : 01

Server Port :

SNC Library Path :

SNC Mode : 0

SNC Name :

SNC Partner Name :

SNC QOP (Security Level) : 0

System Type : SAP_R3

Trace Mode : 0

_____ Connection Test ________

SAP Web AS Connection

Test Details:

The test consists of the following steps:

1. Check that the system object defines an SAP system

2. Validate the following parameters: wap.WAS.protocol; wap.WAS.hostname

3. Check the HTTP/S connection to the defined backend application

Results

1. The system object represents an SAP system.

2. The following parameters are valid: wap.WAS.protocol (http) ; wap.WAS.hostname (sapr3pgrp.<domain>.<cn>:8001)

3. HTTP/S connection failed. Make sure the protocol, host name, and user mapping are correctly defined.

ITS Connection

Test Details:

The test consists of the following steps:

1. Check that the system object defines an SAP system

2. Validate the following parameters: wap.ITS.path; wap.ITS.protocol; wap.ITS.hostname

3. Check the HTTP/S connection to the defined backend application

Results

1. The system object represents an SAP system.

2. The following parameters are valid: wap.ITS.path (/scripts/wgate/) ; wap.ITS.protocol (http) ; wap.ITS.hostname (ep.<domain>.<cn>)

3. HTTP/S connection failed. Make sure the protocol, host name, and user mapping are correctly defined.

Test Connection with Connector

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

Could not retrieve default alias. Make sure the system object has at least one alias.

Test Connection through the DQE

Test Details:

The test consists of the following steps:

1. Checks the existence of a backend admin user ID/password in the system properties.

2. Checks the existence of a default alias for the system.

3. Checks the DQE connection.

Results

1. DQE admin user ID or password is missing in the system properties. Make sure those properties exist for this system object