Skip to Content
0
Former Member
May 02, 2007 at 12:32 PM

unable to create RFC iviews - connection test of the system failed

16 Views

hello,

I always try to configure my system to run an RFC iView...

The connection of myt system is failed for 1 of the 4 tests.

i don't know why.

I have filled this fields :

- application host

- ITS host name

- ITS path

- ITS protocol

- Logical system name (not sure it's correct)

- Sap client

- Sap system ID

- SAP system number

- Server port (not sure it's correct)

- System type

- Web as host name

- Web as path

- Web as protocol

and i have this error :

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 a SAP system is defined in the system object

4. Validate the following parameters: WAS protocol; WAS host name

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

Results

1. The system ID is valid

2. Retrieval of the system was successful

3. The system object represents an SAP system

4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (wsapv49.dhcp.xxx.xx.xxxx:8045)

5. HTTP/S connection successful

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 a SAP system is defined in the system object

5. Validate the following parameters: ITS protocol; ITS host name

6. Check the validity of any user mapping in the system object

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

Results

1. The system ID is valid

2. Retrieval of the system was successful

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 (wsapv49.dhcp.xxx.xx.xxxx:8045)

6. HTTP/S connection successful

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.

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.

2. Default alias of the system exists.

3. DQE connection successful. If you continue to experience problems, verify the DQE admin user ID and password properties for this system object.

can you help me to end this configuration?

thanks a lot.

(reward points for helful answers...)

Adrien