Changing the JRE version used by BSAE WebIntelligence reports

Changing the JRE version used by BSAE WebIntelligence Reports is not supported.

If you check the file /opt/opsware/omdb/bo/setup/ProductID.txt , you will see that BSAE version 9.11 has SAP BO Enterprise XI 3.1 SP2.

The supported JRE for this version of BO is shipped as part of the product, /opt/opsware/omdb/bo/bobje/jdk .


Error: Digital Signature could not be validated

In BSAE (Business Service Automation Essentials), in the /var/opt/opsware/omdb/collect/failures directory, in one of the failures files, the following error can be seen:

2012-07-16 06:25:49,039 [omdb.loader] INFO Loader started

2012-07-16 06:25:49,542 [omdb.loader] ERROR Exception thrown while validating file: Digital Signaturx|e could not be validated

2012-07-16 06:25:49,542 [omdb.loader] INFO Validating File…failed

2012-07-16 06:25:49,549 [omdb.loader] INFO Loader failed

2012-07-16 06:25:49,555 [omdb.loader] INFO Loader finished

This happens when signature validation is not enabled in BSAE.

Signature validation can be enabled by adding omdb.loader.validatefiles=true to /etc/opt/opsware/omdb/ Setting the value to false will disable it.

ERROR: No data to retrieve in Query1

The Business Object report throws the following error when executed or when the data is refreshed:

No data to retrieve in Query1

There could be a number of issues with this error. Some potential issues follow:

Insufficient permissions. The user may have insufficient access rights to run this query.

The database/BSAE connection has been dropped in BO.

The specified data does not exist.

The following actions are a good starting point to deal with this kind of error.

a) Permissions: The execution should be attempted with admin rights, or the permissions should be readjusted.

b) It is possible the Business Objects (BO) connection to Automation Reporter core or database has been dropped.

Stop BO (/etc/init.d/bsae-bo stop)

Stop BSAE (/etc/init.d/opsware-omdb stop)

Start BO (/etc/init.d/bsae-bo start)

Start BSAE (/etc/init.d/opsware-omdb start)

BO should always be started before BSAE. The startup time is about 10-15 minutes, so enough time should be allowed to pass before the report testing takes place again.

c) It is possible that there was no data for that specific date selection. A wider date range should be attempted. In addition – to gain a better understanding of the data – one could view the SQL used in the "Edit Query" form and comment out some of the date conditions to see if any data gets returned when no date range is specified.

Another reason why the data does not exist is also when the data has not made it into BSAE yet. If the data is too recent then enough time should be allowed to pass for the data to be mined and, after they are mined, the Nightly Job should be executed.

/opt/opsware/omdb/contrib/ 5

The nightly job should be run through the JMX-console and not the command line. The command line does not work in all situations.