How to create a .hdbvirtualtableconfig file for remote source and schema name change

[former_member590265]

Hi Team,

I am working on the HANA XSA project. In our project I have a requirement to access the cross container data. My source and target containers are located in the different tenants. So I am using SDA remote source and virtual tables between 2 tenants to access the data between the containers. Our development space and production spaces are located in different tenants.

In development spaces I have used SDA remote source connection 'ABC' and schema 'TEST_SCHEMA_1' in the .hdbvirtualtable file to create the virtual table. This virtual table in development space is working fine. But now I am facing problem in production space where SDA remote source connection name is changed to 'XYZ' and schema name is changed to 'TEST_SCHEMA'. In .hdbvirtualtableconfig file how I can configure these 2 changes so that my virtual tables in production space will created with SDA remote source connection 'XYZ' and schema 'TEST_SCHEMA'. As I know we cannot edit or create virtual tables in production space and now the only way .hdbvirtualtableconfig file. But I am not able to find any document or help on how to create .hdbvirtualtableconfig file which will include remote source connection name and schema name change in production space.

Thanks in advance.

BR,

Vivek.

[thomas_jung]

>Please correct me if my understanding is wrong. If my understand is right then I have another question how can I add the deployed project into webide?

Yes that is what I am saying. Why do you need to add the deployed project into the Web IDE? You are still thinking like design time and runtime are one in the same. They are not. The deploy is the runtime. The design time is in Git. If you want want a particular version of the design time in the Web IDE then just clone that branch from Git.

>I am looking for the functionality to define these both the configuration in logical schema and assign them into .hdbvirtualtableconfig file for single virtual table so that it can work in both development and production

This is the correct approach. If you use the logical placeholders, the actual values will be pulled in automatically at deploy time from the bound User Provided Service. This way the content in your MTAR (even the *config files) are stable and the same for each target deployment. The actual target names only have to be maintained in the User Provided Services in each target system.

[former_member590265]

Hi Thomas Jung,

I am not using any user provided service in my project. I am not using synonyms to access the tables. I am using virtual tables using SDA. I am not sure how to read the Remote Source name and Database Name using the user provided service. If possible please could you give me one example or link to the example where this scenario is explained.

Thanks.

Best Regards,

Vivek.