Dollar Universe Managers and avoiding hardcoded Uprocs

[Angus Reid]

​Dollar Universe v 6.9, Windows 2012 R2

When using Dollar Univierse managers such as SQL or Web managers it seems that it is only possible to create individual uprocs with hardcoded names.

i.e. if there is SQL job called calculate_numbers in DB test1 then using a SQL connector to DB test1 a Uproc called calculate_numbers can be created. Simple enough, however if there is another development database, test2, with the same SQL job a separate SQL connector is required and a new Uproc. This time the Uproc must be unique so would need to be called calculate_numbers_test2. With every additional dev stage a new unique Uproc is required. If there are multiple dbs then the number of Uproc grown and so does the coerresponding overhead in building clone environments and keeping them in step, there is also the path to live to consider.

This issue is also common for Web Manager where individual rather than generic Uprocs need to be built.

Is there a way using $U managers, to create single Uprocs that will run with environmental variables at runtime? This means only a single build of Uprocs and session is required but something at runtime like MUs or userid can be used to run the same suite of Uprocs on different development stages.

This could be achieved using a form of scripting but this situation is just in the case of $U Web and SQL managers. Is this possible?

[Angus Reid]

In the Web manager is it possible to use a variable as he path to a REST URL which is ​then dynamically worked out at runtime with say a MU variable?

[Angus Reid]

​For the WEB manager this would be in the REST Service name, can this be set as a variable or does it need to be an actual fixed URL?

Something like <RestService name="TEST_VAR_URL" url="%target_url%" where target_url is passed from a MU or uproc variable.