When performing a distributed installation, the order in which components are installed is important. Follow these instructions carefully. For more information about each property, see the comments in the advrep_prop erties.xml file.
-
Perform a manual installation of HxGN EAM Advanced Reporting on the machine that will be the Primary Content Manager by configuring the advrep_properties.xml file as follows (note that only changes from a normal installation are shown here) and then running AdvRepIns.bat (Windows) or AdvRepIns.sh (UNIX):
<contentmanager>
<enabled>true</enabled>
<primary>true</primary>
<contentmanagernames> cm1.yourdomain.com:9300,
cm2.yourdomain.com:9300</contentmanagernames>
<allow_consumer_access_to_report_folders>false</allow_consumer_access_to_report_folders>
<allow_consumer_login>true</allow_consumer_login>
</contentmanager>
<reportserver>
<enabled>false</enabled>
<webserver>
<enabled>false</enabled>
<deployreportcontent>true</deployreportcontent>
Set the <deployreportcontent> to true, for the Primary Content Manager only.
-
Perform a manual installation of HxGN EAM Advanced Reporting on the machine that will be the standby Content Manager by configuring the advrep_properties.xml file as follows (note that only changes from the primary content manager install are shown here) and then running AdvRepIns.bat (Windows):
<servercfg><contentmanager><primary> false
<servercfg><webserver><deployreportcontent> false -
Perform manual installations of HxGN EAM Advanced Reporting on each additional machine that will be a standby Content Manager as indicated in step 2.
-
Perform a manual installation of HxGN EAM Advanced Reporting on the machine that will be a Report Server by configuring the advrep_properties.xml file as follows (note that only changes from a normal installation are shown here) and then running AdvRepIns.bat (Windows):
<contentmanager>
<enabled>false</enabled>
<reportserver>
<enabled>true</enabled>
<webservername> ws.yourdomain.com:80</webservername>
<contentmanagernames> cm1.yourdomain.com:9300,cm2.yourdomain.com:9300</contentmanagernames>
</reportserver>
<webserver>
<primaryreportservername> rs1.yourdomain.com:9300</primaryreportservername><enabled>false</enabled>
<primaryreportservername> rs1.yourdomain.com:9300</primaryreportservername>
<deployreportcontent>false</deployreportcontent>
</webserver> The deployreportcontent is set to false which is a change from past releases.
-
Perform manual installations of HxGN EAM Advanced Reporting on each additional machine that will be a Report Server as indicated in step 4.
-
Perform a manual installation of HxGN EAM Advanced Reporting on the machine that will be a Web Server by configuring the advrep_properties.xml file as follows (note that only changes from a normal installation are shown here) and then running AdvRepIns.bat (Windows):
<webserver>
<enabled>true</enabled>
<primaryreportservername> rs1.yourdomain.com:9300</primaryreportservername>
<deployreportcontent>false</deployreportcontent>
</webserver> -
From any web browser, test the following URL, http://ws.yourdomain.com:80/, to ensure a valid installation. You should get a login prompt. If not, check the InforEAMAdvRep/crn/logs directory on each machine for errors.
-
After you have deployed the Advanced Reporting Server go to the Application Server and open the file MPConfiguration.xml.vm located in the <App Server>\deconfig\templates\jboss folder with a text editor. Search for the tag <DISPATCHURL> and add a value like rs1.yourdomain.com:9300 where rs1 is your primary Report Server. Then run deploy on the Application server.