ALM enhancement to update connection details with SAP DataReaders

Helmut Heimann
Helmut Heimann Employee, Community Captain
500 Comments 250 Likes Fourth Anniversary 25 Answers
edited December 2023 in Idea Exchange

When deploying a DataReader that uses the connection type SAP via Board SAP Connector the URL to connect to the source is not updated accordingly. Although the connection string looks correct the process is executed on a different server (QSS in this case).

You'll have to manually change each DataReader (adding a field to the mapping, saving the configuration, then removing the additional field, and saving again) to get it to work properly.

That's time-consuming and error-prone and no "real" deployment.

So, please enhance the ALM to update the according mapping. There should be no need to do anything manually after deploying.


15
Up
15 votes

Open For Voting · Last Updated

Comments

  • Björn Reuber
    Björn Reuber Employee, Community Captain
    500 Likes Fourth Anniversary 100 Comments 5 Answers

    from my point of view we have to problems here:
    - after transporting the wrong URL is displayed (so it displays the DR with the new choosen SAP connection, which for sure, has the same name as the old one)

    - SAP DR store internally always the "real" URI. So the URI does not contain a part of the SAP connector and the target extraction. So for sure this needed to be changed, to be able to transport also SAP DR in a good way

Categories