Bug 1035321

Description of problem:

It's not very user friendly that user needs to configure 3 config files (dtgov.properties, dtgov-ui.properties & s-ramp-ui.properties) in order to get design-time governance working at non-default location (other than http://localhost:8080/*).

Suggested improvement:

Such distributed configuration supports various deployment schemas, which should be preserved but the default configuration could be taken from server variables like ${jboss.bind.address}:8080 + ${jboss.socket.binding.port-offset}/<war_name> to create appropriate urls that are needed for web applications. Only if user set these urls explicitly in config files (templates should be included) are these urls taken into account.

To sum up:
* no urls in configs -> expect gov app running at default locations: ${jboss.bind.address}:8080 + ${jboss.socket.binding.port-offset}/<war_name>
* urls explicitly set in config files -> use urls specified in config files

Version-Release number of selected component (if applicable):
* FSW 6.0.0.ER6 (Beta)

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Once I ran standalone.sh -b <some_ip> it will run on this ip and no additional manual configuration won't be necessary. Only if running in non-default deployment configuration like running sramp repository at different location to dtgov or even dtgov-ui on different node to dtgov task-api endpoint, etc., should be user forced to specify these urls explicitly.

Additional info: