How to use OData service from Development and Quality using single gateway server.

[Former Member]

All my DPC and MPC classes are residing in backend system and alias are maintained in GW frontend system.

In order to save installation cost, my client wants to use same GW system in Quality as well.

The problem when I add service using RFC dest. for Development that service disappears from the Quality system. So, it either works for Development or Quality. How can I make it work for both? 

[former_member226566 · Accepted solution]

You can go to the transaction /IWBEP/REG_SERVICE and then you can maintain the service to whatever naming convention you wanna follow. I hope that will solve your problem. 

[Private_Member_148162]

HI Vamsi,

1. Create two system aliases(one for Dev Back end and another for Quality Back end)

2. Creare two user roles in Gateway system(Lets sat Role_dev, Role_quality)

3. Add 2 System alias providing the combination of User Role and System Alias.
4. Create user1 and user2 in GW and assign role_dev, role_quality respectively.

Then when you login using user1, your development system will trigger and when using user2 quality system will be triggered.

PS: If you assign both roles to same user, either default system or 1st one will triggered.

Hope this helps you out.

Thanks,

Phaneendra

[vamsixk]

Hi Hari,

I believe you can use a "Custom Dynamic System Alias" for that. Because system Alias dictates which system is used to fetch the DPC and MPC from.

Just came across this link by Andre Fischer .

You can configure just one service and then implement the BADI described above so that, the appropriate DPC and MPC are called.

Hope it helps.

Kind Regards,

Vamsi

[Former Member]

Well, it does look very promising, but I am sure there must be a way to just rename the service in quality so that it becomes available in the Quality system alias.

Only problem is the service name is same in Development as well as quality.

There must be something to change the service name.

For instance.

ZTEST_SRV in development

ZTEST_SRV_QUALITY in quality.

[AshwinDutt]

Hello Hari,

Service name cannot be changed. Its a unique name and remains same when moved to GW Quality, GW Pre-Prod and GW Prod Systems.

You can still connect the same GW Dev System to ECC Quality System by creating an another RFC Destination & System Alias which points to ECC Quality System.

Now assign this new System Alias ( which is pointing to ECC Quality System ) to the existing Services and keep System Alias pointing to the ECC Dev System as default one.

This way you can connect a particular service to both ECC Dev System and ECC Quality systems and test.

Your URL would b as below -> Sample one

/sap/opu/odata/IWFND/RMTSAMPLEFLIGHT;o=<ECC_Dev_Syatem_Alias>/CarrierCollection

/sap/opu/odata/IWFND/RMTSAMPLEFLIGHT;o=<ECC_Quality_Syatem_Alias>/CarrierCollection

Please check this.

Regards,

Ashwin

[Former Member]

Hi, thanks Ashwin for this valuable input.. As suggested I added two system alias to the service.

But it given an error

System Alias 'Alias_quality' not assigned to user 'HARI' and service 'ZSFLIGHT_SRV_0001'

I checked in SAP NetWeaver SAP Gateway OData Channel Administration General Settings Assign SAP System Aliases to OData Service

it is assigned, where else to assign it?

Thanks.

[vamsixk]

HI Ashwin ,

I didn't know that we could add the alias name as well to the URI. Thank you for this information.

If we go with this, then the UI will have to handle for different URLs when testing in DEV and Quality.

This will have to be specifically handled. Correct?

@Hari Sadu you might have to take this into consideration as well.

Kind Regards,

Vamsi

[AshwinDutt]

Passing System Alias in URL is to just check if the service is running after assigning system alias which is pointing to ECC Quality.

No change in the URL.

Since we are using same GW, we can set ECC Quality System Alias as a default one.

[AshwinDutt]

What is the error ? can you please share the screen shot ?

Also did you have at the look at the below as well ?