ALM enhancement to update connection details with SAP DataReaders
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.
Comments
-
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
4
Categories
- All Categories
- 2K Forums
- 1.8K Platform
- 159 Academy
- 325 Resources
- 1 Board Knowledge Base
- 50 Best Practices
- 49 How-To Guides
- 19 Board Advocacy Program
- 192 Blog
- 4 Groups Hub
- 4 About Groups
- New Community Members
- DACH
- Japan
- 4 Community Captains
- 1 About Community Captains
- 2 Meet the Community Captains
- 1 Topics & Thought Starters
- Learn from the Board Captains
- Release Notes
- Academy
- 2 Board Academy
- 8 ILT/VILT Course Catalogue
- 13 e-Learning Course Catalogue
- 4 Academy Forum
- 1.2K Idea Exchange
- 337 Partner Hub
- 94 Support
- 14 FAQ's
- Customer Support Portal
- 54 Support Articles
- BEAP