Jco Destinations for aliases
We have a Java web dynpro on one host in it's own instance that calls data from an ERP ABAP system on another host as another instance. Our entire landscape is HA, where the apps all call each other by the alias. We can fail any instance to site B along with the respective DNS entry and the other intances (ABAP) can continue accessing the failed over host by alias with a simple 'hostname buffer refresh' in SM50.
But with the web dynrpo, we get our system info from the SLD, which has the actual host names listed. We use RZ70 on the respective system(s) to pass info to the SLD, so it's not using the alias that is defined in the system profile, but instead the actual host name.
So when we failed over the ERP ABAP system, our web dynpro was unable to find it until we deleted the MetaRFC Jco Destination and recreated it with the correct real host name (the SLD already updated itself with the new hostname in the nightly job).
This is very limiting and makes a failover scenario more difficult and adds a manual step. How could we make sure that the SLD transfer from an ABAP system use the alias as defined in the system profile?