http url differentiation between dev and qa

[Former Member]

Hi,

Our dev and qa environments are on the same ip but have a different instance number.

We were able to test the http sender interface in dev and have moved the objects to qa, but the http post from soapui is getting triggerd to dev instead of QA because both have the same ip and port. Is there any way to provide the differentiation?

Regards,

Lasya

[Former Member · Accepted solution]

Thanks both Dimitri and Pavan. I am able to ping the correct environment now by adding the &client to the HTTP URL, since this is different between the two systems.

[iaki_vila]

Hi Lasya,

I wonder how you can import your development to QA system if the IP and the port is the same. How are you addressing the ESR or the ID?.

Another similar solution to Dimitri is to have up the Service Registry and take the wsdl from there.

Regards.

[former_member183908]

Hi

even though on the same IP or host name i believe we will have different port numbers because of diff instance numbers.

for example if your dev url is : http://pihost:50100 QA url can be http://pihost:50300/

If you have access to the SAP MMC please check the difference.

Please check SICF in both for the port numbers

Thanks

[Dimitri]

Take your QA system, go to the sender agreement and display the WSDL.

Save that WSDL and import it into soapUI.

[Former Member]

Hi Pavan,

No the ports are also the same for both QA and Dev. I checked in ICM monitor.

Regards,

Lasya

[Dimitri]

check your URL closely. There should be sender and receiver information.

In case that deviates, you can make the distinction.

[Former Member]

Hi Dimitri,

The url has namespace, interface and service. Namespace and interface will be the same. The service is different(pointing to BS in QA), but it is still hitting against dev.

We have different username/passwords for dev and QA. The request is failing at the initial stage itself if we give the QA password with a log on error.

If we give the dev password, then it fails at the receiver determination step because the BS from QA is not available in dev.

I feel that it is hitting at dev just by looking at the ip. Is there any way to include the instance?

thanks,

Lasya