How to create a system object in portal that points to a web dispatcher

[Former Member]

Hi,

How do we create a system object in the portal for a web dispatcher? The web dispatcher in turn points to an ECC system. The path for communication is EP>Web Dispatcher>ECC

Regards,

Sridevi

[Former Member]

Hi,

I found out that this cannot be achieved. This can be achieved only in the code and not by a system object.

Regards,

Sridevi

[former_member227283]

Hi,

We have configured the same by system object in our landscape and not used any code.

Everything is woking fine without any issue.

Thanks

Anil

[Former Member]

Hi Sridevi,

I am not sure if you do the above scenario. Instead you can create a system object for ECC in portal and point web dispatcher to portal.

Is it not going to be the same ?

I am still thinking...

Cheers...,

Raghu

[Former Member]

No. This will not be the same. we already have a web dispatcher that load balances the requests to the portal. This is applicable only to the portal and not the backend ECC.

[Former Member]

oh...sorry...i got the scenario wrong.

Well..i do not have any idea abt this....

Cheers...,

Raghu

[former_member227283]

Hi ,

IT will be same as ECC , only you have to replace the host name of ECC with webdispatcher in system object.

Thanks

Anil

[Former Member]

Which hostname should be changed? the Application hostname or WAS hostname or ITS hostname. I changed the WAS and ITS host

names to point to the web dispatcher. Then for testing whether the requests are actually going through the web dispatcher i stopped the web dispatcher and executed a report pointing to CPR. It still worked. This shows that it is not going through the web dispatcher.

[former_member227283]

Hi ,

Try to execute as below.

> Create new system on portal for ECC.

> Then goto edit mode of newly created system

> Scroll down the Property Category to Connector

*Application host = < give hostname of ECC system & not of webdispatcher >

*Gateway host = < give hostname of ECC system & not of webdispatcher >

Else fill all the entry of ECC in connector

> Scroll down the Property Category to ITS

> ITS hostname = < give hostname of webdispatcher >:<port of webdispatcher>

Else fill all the entry of ECC in ITS

> Scroll down the Property Category to Web AS

> Web AS Hostname = < give hostname of webdispatcher >:<port of webdispatcher>

Else fill all the entry of ECC in Web AS

Once above all changes are done , save the setting.

And run the Connection test with keeping webdispatcher started.

Then after , Run the connector test with Kepping webdispatcher stopped.

Thanks

Anil

Edited by: Anil Bhandary on Jun 11, 2010 9:03 AM

[Former Member]

Hi,

I have made the following changes to the ECC System Object:

Application Host: ECC Host

ITS Host: WebDisp Host

Gateway Host: ECC Host

WebApp Host: Web Disp Host

Then i stopped the web dispatcher and tried to connect through the system object. I am still able to connect to the ECC system. This means it is not hitting the web dispatcher.

Regards,

Sridevi

[former_member227283]

Hi,

Just try to do the connection test of system object & let us know the result.

Thanks

Anil

[Former Member]

conn test fails with the message :

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 (mtw02spwp02.mindtree.com:80)

5. The host name mtw02spwp02.mindtree.com could not be resolved successfully.

[Former Member]

Hi,

Connection test for the following succeeded:

1. 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 (mtw02spwp02:80)

5. The host name mtw02spwp02 was resolved successfully.

6. The Web AS ping service http://mtw02spwp02:80/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://mtw02spwp02:80/sap/bc/bsp/sap was obtained successfully.

2. 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 (mtw02spwp02:80)

6. The host name mtw02spwp02 was resolved successfully.

7. An HTTP/S connection to http://mtw02spwp02:80/sap/bc/gui/sap/its/webgui was obtained successfully.

Next test for SSO failed:

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 that Single Sign-On is configured correctly

Regards,

Sridevi

[former_member227283]

Hi,

1. Before doing connection test, did stopped the sap webdispatcher ?

2.

The Web AS ping service http://mtw02spwp02:80/sap/bc/ping was not pinged successfully

mtw02spwp02

Thea above hostname is of webdispacther ???

If yes, it mean know your request is redirecting through webdispacther and your requirement has been fullfilled.

Thanks

Anil

Edited by: Anil Bhandary on Jun 11, 2010 11:39 AM

[Former Member]

Even when the web dispatcher is up i get the same error. Moreover even when i stop the web dispatcher i am able to access the reports pointing to the ECC system. This implies that the requests are not hitting the web dispatcher and directly going to the ECC system.

[former_member227283]

Hi,

Can you paste the value of instance profile of webdispatcher in forum.

Pls paste the value of webdispatcher which is pointing to ECC system.

Thanks

Anil

[Former Member]

SAPSYSTEMNAME = WP2

SAPGLOBALHOST = MTW02SPWP02

SAPSYSTEM = 00

INSTANCE_NAME = W00

DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64

DIR_EXECUTABLE = $(DIR_CT_RUN)

#----

---

1. Accesssability of Message Server

#----

---

rdisp/mshost = mtw02sdcr02

ms/http_port = 8100

#----

---

1. Configuration for medium scenario

#----

---

icm/max_conn = 500

icm/max_sockets = 1024

icm/req_queue_len = 500

icm/min_threads = 10

icm/max_threads = 50

mpi/total_size_MB = 80

icm/host_name_full = mtw02spwp02.mindtree.com

#----

---

1. SAP Web Dispatcher Ports

#----

---

icm/server_port_0 = PROT=HTTP,PORT=80

[former_member227283]

Hi,

icm/server_port_0 = PROT=HTTP,PORT=80

as per the above parameter you have bind the webdispatcher on Standard HTTP port i.e 80.

Do the following steps and let us know the result.

1. Try to acces the URL

http://mtw02spwp02

if you are able to get any of the SAP screen except the error page not display it mean your sap webdispatcher has been started succesfully, then go ahead with following

Goto system object and change the setting in WEBAS and ITS .

Bofore mtw02spwp02:80

After mtw02spwp02 remove 80 and keep only hostname.

once done this changes, do the test run and share the result on forum.

Thanks

Anil

[Former Member]

Hi,

The url http://mtw02spwp02 gives me a "Service Cannot Be Reached" message. However i am able to access http://mtw02spwp02.mindtree.com/sap/public/icf_info/icr_groups?sap-client=900 and it gives me the correct result. I am also able to access the admin console of the web dispatcher. So there is no problem with the WD. I removed the port entry in the system object description and still the same result.

Regards,

Sridevi

[former_member227283]

Hi,

I removed the port entry in the system object description and still the same result.

Check whether your portal host is able to resolve the hostname of ECC webdispatcher.

1. Login to host of Portal.

2. Ping mtw02spwp02.

If hostname is not able to resolve then , add the ECC webdispatcher hostname i.e mtw02spwp02 & mtw02spwp02.mindtree.com in the host file of Enterprise portal.

Then once again try to ping the hostname of ECC webdispatcher.

Once it is done, try to do connection test again.

Thanks

Anil