For the Advanced Reporting server, add the webserver_base_URI token under the <reportserver> section AND the <webserver> sections in the advrep_properties.xml file, as shown in the example excerpt below.
The same base URI should be used for both values and should match what was defined
for the <gatewaybaseuri> on the application server:
...
<reportserver>
<enabled>true</enabled>
<webservername>someadvrep.infor.com:80</webservername>
<webserver_base_URI>/InforEAM</webserver_base_URI> -->
<contentmanagernames>someadvrep.infor.com:9300</contentmanagernames>
</reportserver>
...
<webserver>
<enabled>true</enabled>
<primaryreportservername>someadvrep.infor.com:9300</primaryreportservername>
<webserver_base_URI>/InforEAM</webserver_base_URI> -->
<deployreportcontent>true</deployreportcontent>
</webserver>
...
Once the change to advrep_properties.xml has been completed, executing a redeploy will configure the reports server to properly use the new base URI when serving reports, as well as report attachments.
The base URI desired should always begin with a forward slash (/) and should contain the full base URI path desired. Do not include a forward slash (/) at the end of the base URI variable. This applies to both the base URI for the reportserver webserver_base_URI, as well as for the variable that specifies the webserver webserver_base_URI.
Under all scenarios, if it is desired to revert the application to use the default configuration in use prior to employing custom base URIs, either remove or comment out the base URI related token that controls the base URI behavior for the specific component with which the change is desired and execute a system redeploy.