BSAE WebInterface displays HTTP Status 404 – /bsae/null

BSAE WebInterface displays the following error message after a user logs in:

HTTP Status 404 – /bsae/null

type Status report

message /bsae/null

description The requested resource (/bsae/null) is not available.

No reporting functionality is available, although the Administration tab works properly.

This is usually caused by the BO Cms not running on the BSAE core. The logfile /var/log/opsware/omdb/server.log can be consulted for further information:

ERROR [STDERR] com.crystaldecisions.enterprise.ocaframework.OCAFrameworkException$NotFoundInDirectory: Server bsae01.hostname.com:6400 not found or server may be down (FWM 01003)

cause:java.net.ConnectException: Connection refused

detail:Server bsae01.hostname.com:6400 not found or server may be down (FWM 01003) Connection refused

1. It may be BO Cms is indeed stopped. If this is the case, it needs to be started:

/etc/init.d/bsae-bo start

2. A second issue can be BO Cms is unable to start due to some other causes. In this case, /var/log/messages needs to be consulted as it will contain the exact error. Is most of the cases this is due to an incorrect password for the Oracle user bo_admin:

Oct 7 10:28:58 bsae01 boe_cmsd[32020]: The root server reported an error Initialization Failure. (Reason: BusinessObjects Enterprise CMS: Unable to connect to the CMS system database ""cmdb"". Reason: ORA-01017: invalid username/password; logon denied BusinessObjects Enterprise CMS: Unable to connect to the CMS system database ""cmdb"". Reason: ORA-01017: invalid username/password; logon denied CDatabase::Open failure. ).

Advertisements

How to Migrate an existing dataminer to a new server

1. Shutdown Dataminer (DM) to stop processing data from Server Automation (SA):

./dataminer.sh stop
./dataminer.sh start –flushdatafiles; tail -F dataminer.log

This will restart the DM and process any unfinished work and then shut the dataminer back down.

Watch in the log for the dataminer to finish the data mining and shutdown

2. Zip up the current working dataminer directory and copy the dataminer tar file to a new server

3. On the existing server were the dataminer is currently running, either configure the dataminer to not start automatically or remove the bits completely form where its running today.

4. If there is a back log on the Server Automation Essentials (BSAE) server let the back log process

5. Copy the DM directory created on step 2 to the new DM server

6. Untar the tar file of the dataminer directory created in step 2 on the new dataminer server

Make appropriate metadata changes to dataminer before starting:

* FROM THE BSAE app SERVER*

cd /opt/opsware/omdb/bin
./dmconfig.sh –list to get the registration token for the new DM install config…as well as validate the name/description of the dataminer that is being moved.

Validate properties of dataminer via ./dmconfig.sh –listproperties –name <DM Name>

* SQL to run on BSAE DB SERVER*

update dataminer properties to target as follows, replacing all <variables>:
update cmdb_meta.jdbc_conn_props set property_value = ‘<TARGET CORE DB HOSTNAME/IP>:<TARGET CORE DB PORT>:<TARGET CORE DB SID>’ where source_id = <DM ID> and property_name = ‘database’
update cmdb_meta.data_sources set display_name = ‘<TARGET DISPLAY NAME>’ where source_ID = <DM ID>
update cmdb_meta.data_sources set description = ‘<TARGET DESCRIP>’ where source_ID = <DM ID>
commit;

* FROM THE BSAE app SERVER*/dataminer.sh start; tail -F dataminer.log

Validate changes via ./dmconfig.sh –list and ./dmconfig.sh –listproperties –name <DM Name>

7. Start dataminer and watch the dataminer.log file

8. Dataminer moved and now processing data