This type of scenario can happen when using SSL offloading at the load balancer level. Therefore the URLs created in WSDL endpoints may differ from what the user sees in his current browser window

How to make sure all the links coming back through the ssl offloading process or proxies are accurate in order for the browser or SOAP  clients to use?

Examples
The current WSDL endpoint returned by the midtier is not correct and needs to be changed,
Example:  WSDL is called using using http but returns endpoints using https like below:

<soap:address location="https://<server name>/arsys/services/ARService?server=<ar server name>&webService=HPD_IncidentServiceInterface"/>

For non-container versions (20.02 or lower)
Open "viewer.properties" file available in Midtier's WEB-INF folder.
This contains an entry that is normally commented out:
The base_url controls the value of the "https://<server name>" for the endpoint, un-comment and set as required,
Also make sure a reverse proxy filter is enabled on midtier to create relative URLS while navigating on midtier forms.

Please make sure documentation to enable proxy filter is used
https://docs.bmc.com/docs/display/public/brid81/Proxy+server+and+load+balancer+settings
and
https://docs.bmc.com/docs/brid91/en/proxy-server-and-load-balancer-settings-610403031.html

Changes will require a restart of the Tomcat/midtier service or process.

For container versions (20.08 and higher)
NOTES

• I’m assuming only the midtier-user pod(s) are to be changed.  If you also want to update the midtier-int pod(s) then run the same commands against the midtier-int deployment.
• The steps below are one way to make the change. If the customer prefers to use a different process to update the deployment object, kubectl edit for example, they can do so.  All that is being done is to add a value to the MIDTIER_URL environment variable that already exists in the container but is blank by default.
• If Jenkins is used to make any changes to the system in the future the patch may be lost and will need to be re-applied.

1. Start by making a backup of the midtier-user deployment definition that can be used to revert any changes:
2.  Save this text as a file called patch.yaml - the indentation must be kept:
3.  Test the patch file with:
If the output is different, check for typos in previous commands.
4.  If all OK apply the patch:
***WARNING - this command will cause the midtier-user pod(s) to be restarted ***
Once the pod(s) have restarted verify the base_url is now set as required.

TO BACK OUT/REVERT THE CHANGE
If you want to revert to the original configuration:
***WARNING - this command will cause the midtier-user pod(s) to be restarted ***