search cancel

Upgraded OC/SRM server install shows error message regarding CABI/BOXI server integration


Article ID: 130164


Updated On:


CA Spectrum


We see after upgrade to CA Spectrm R10.3.++ error messages in OC/SRM webserver logfile (catalina.out / stdout.log) indicating service is trying to connect to a configured CABI/BOXI host. The CABI/BOXI integration is not supported nor configurable under CA Spectrum R10.3++ anymore. 

The error message looks like:
<date> <time> - Error while determining Crystal Only users. com.crystaldecisions.sdk.exception.SDKException$ServiceFailure: 
    There was a problem retrieving the service EnterpriseSession from the server <boxihostname>:6400 (FWM 02002)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(
    at java.lang.reflect.Method.invoke(
    at org.springframework.util.MethodInvoker.invoke(
    at org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean$MethodInvokingJob.executeInternal(
    at org.springframework.scheduling.quartz.QuartzJobBean.execute(
    at org.quartz.simpl.SimpleThreadPool$

<date> <time> - Unable to obtain Business Objects Session
        There was a problem retrieving the service EnterpriseSession from the server <boxihostname>:6400 (FWM 02002). 
        Verify that the Business Objects CMS and related services are running. Will retry connecting in 60 seconds.


The CA Spectrum R10.3 and higher does not support CABI/BOXI integration anymore but upgrade task may not remove the CABI/BOXI integration parameter from internal configuration. 



This applies to all supported CA Spectrum platforms (Linux and Windows) when the CA Spectrum OC-SRM server install was configured with a CABI/BOXI integration prior to upgrade to CA Spectrum Release R10.3 and higher.


R10.3.1 installer is missing the BOCI/CABI cleanup - so manual cleanup is required by native mysql command to update reporting.registry entry.

Check for existing configuration per native mysql-command. All native mysql-command are executed per Spectrum install owner logon from directory $SPECROOT/mysql/bin at CA Spectrum OC/SRM server:

- show the current configuration data:
     ./mysql[.exe] --defaults-file=../my-spectrum.cnf -uroot -proot -e"select * from registry\G;" reporting
- update single entries out of this record
     ./mysql[.exe] --defaults-file=../my-spectrum.cnf -uroot -proot -e"update registry set ='value';" reporting

Sample: ./mysql[.exe] --defaults-file=../my-spectrum.cnf -uroot -proot -e"update registry set BOPort='0';" reporting

Here it is required to overwrite the entries:    BOPort and BOHost
Please set BOXI port-number to "0" - while BOXI hostname / URL set to "nothing". So set BOHost='';   ( which are 2 single_quotes without any space/blank character ).
When the reporting.registry parameters are modified, you are required to restart the OC/SRM tomcat service once. 

Additional Information

Using alias like "alias strmy='/app/spectrum/mysql/bin/mysql --defaults-file=/app/spectrum/mysql/my-spectrum.cnf -uroot -proot'

Then checking for configuration shows / here sample for not configured BOXI parameter:
[[email protected] bin]$ strmy reporting -e"select * from registry\G;" | grep BO
          ConvertedReportsToBOXI: false
                          BOPort: 0
                    BOTomcatPort: 0