This document contains instructions for installation of the file "bdpjm.war" on an already installed BoKS Reporting Manager 6.7 (BRM).

This hotfix fixes two issues with BRM 6.7.


Description

The HFBRM-0006 hotfix corrects the following issues:

# 12149, 8915

DUPLICATE MEMBERS IN BOKS DATABASE CAUSES DELETING HOSTGROUP TO FAIL
Member duplicates in the BoKS database get imported into the BRM database when doing ondemand. When deleting the host group in a live feed it fails to remove the members because of the duplication.
When then deleting the host group an error is returned from the database because it still contains the child members.
This issue exists for Oracle.

# 12149, 8916

DEADLOCK PROBLEM FOR PARALLEL JOBS
When parallel live feed jobs are running and competing for the same resources, a deadlock occurs due to the lack of index for the foreign key in the child table. When deleting rows from the parent table it will then take a table lock on the child table. If two jobs are operating on the same table this is likely to cause a deadlock in the database.
A configuration parameter DomainConcurrency can be set in boksbrm.properties to force the live feed jobs to run sequentially.

Known Issues


# 8924

MUST RESTART BRM AFTER CREATE DOMAIN TO ENABLE SEQUENTIAL MODE
If the DomainConcurrency property is set to SEQUENTIAL, BRM must
be restarted after creating a new domain in order for the live
feed jobs to run in sequential mode.

Resolution / Workaround

Install Hotfix HFBRM-0006, available for download from the HelpSystems Community Portal. Installation is done in two steps:

  1. Add the configuration parameter DomainConcurrency.
  2. Install the hotfix (Oracle or MySQL).

Note: Before you begin, it is important to verify the integrity of the new bdpjm.war file.

bdpjm.war:

SHA1 535e0b6a41de18dd241f1da5a6e1fb9be19df1e2

Add configuration parameter DomainConcurrency:

  1. To run live feeds in sequential mode, edit the file bdpjm/config/boksbrm.properties and add the parameter DomainConcurrency=SEQUENTIAL (default value is PARALLEL).

Installation for Oracle database:
1. Log in as the user running BRM (e.g. brmadmin).

2. Extract the package under e.g. /tmp:

$ cd /tmp
$ gunzip -c HFBRM-0006-1.tar.gz | tar xf -

3. Stop BRM (and wait for it to stop):

$ /etc/init.d/boksbrm stop
$ /etc/init.d/boksbrm status

If it has not stopped after a minute, kill the process (process id is shown with the status argument).

4. Go to the BRM installation directory (e.g. /opt/boksbrm) and then further into the brm/jakarta directory. E.g.:

$ cd /opt/boksbrm/brm/jakarta

5. Remove the old bdpjm.war file:

$ rm webapps/bdpjm.war

6. Remove the webapps/bdpjm directory:

$ rm -rf webapps/bdpjm

7. Remove the work/Catalina/localhost/bdpjm directory:

$ rm -rf work/Catalina/localhost/bdpjm

8. Copy the new bdpjm.war to the webapps/ directory:

$ cp -p /tmp/HFBRM-0006/bdpjm.war webapps/
$ chmod 644 webapps/bdpjm.war

9. Start BRM:

$ /etc/init.d/boksbrm start
$ tail -f /opt/boksbrm/bdpjm/log/boksbrm.log

10. Verify that BRM has started correctly by logging in to the BRM web interface

http://:8080/brm

Run the report BRM Status -> BRM Domain Status or use the "domainstatus" command line utility:

$ /opt/boksbrm/bdpjm/bin/domainstatus -v -a

If the status for AC and AU (if applicable) shows as OK and the time for the last update is newer than the time of the upgrade, the upgrade has been successful. Otherwise you may have to perform a manual synchronization by running the "ondemanddomain" command.

See the FoxT Reporting Manager 6.7 Administrator's Guide.


Installation for MySQL database:
1. Log in as the user running BRM (e.g. brmadmin).

2. Extract the package under e.g. /tmp:

$ cd /tmp
$ gunzip -c HFBRM-0006-1.tar.gz | tar xf -

3. Stop BRM (and confirm that it has stopped):

$ /etc/init.d/boksbrm stop
$ /etc/init.d/boksbrm status

If it has not stopped after a minute, kill the process (process id is shown with the status argument).

4. Go to the BRM installation directory (e.g. /opt/boksbrm) and then further into the brm/jakarta directory. E.g.:

$ cd /opt/boksbrm/brm/jakarta

5. For MySQL: Make a backup of the mysql-connector.jar from the webapps/bdpjm/WEB-INF/lib/ directory. (It will be restored later in this procedure):

$ cp -ip webapps/bdpjm/WEB-INF/lib/mysql-connector-*.jar .

Note that the actual name of the "mysql-connector.jar" file may vary in that it typically has the version embedded in its name.

6. Remove the old bdpjm.war file:

$ rm webapps/bdpjm.war

7. Remove the webapps/bdpjm directory:

$ rm -rf webapps/bdpjm

8. Remove the work/Catalina/localhost/bdpjm directory:

$ rm -rf work/Catalina/localhost/bdpjm

9. Copy the new bdpjm.war to the webapps/ directory:

$ cp -p /tmp/HFBRM-0006/bdpjm.war webapps/
$ chmod 644 webapps/bdpjm.war

10. Start BRM. Wait for the start-up to complete. (You may ignore the log file errors):

$ /etc/init.d/boksbrm start
$ tail -f /opt/boksbrm/bdpjm/log/boksbrm.log

11. Stop BRM and confirm that it has stopped:

$ /etc/init.d/boksbrm stop
$ /etc/init.d/boksbrm status

12. Restore the mysql-connector.jar file:

$ cp -p mysql-connector-*.jar webapps/bdpjm/WEB-INF/lib/

13. Start BRM:

$ /etc/init.d/boksbrm start
$ tail -f /opt/boksbrm/bdpjm/log/boksbrm.log

14. Verify that BRM has started correctly by logging in to the BRM web interface

http://:8080/brm

Run the report BRM Status -> BRM Domain Status or use the "domainstatus" command line utility:

$ /opt/boksbrm/bdpjm/bin/domainstatus -v -a

If the status for AC and AU (if applicable) shows as OK and the time for the last update is newer than the time of the upgrade, the upgrade has been successful. Otherwise you may have to perform
a manual synchronization by running the "ondemanddomain" command.

See the FoxT Reporting Manager 6.7 Administrator's Guide.


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: May 30, 2018