Overview

After upgrading SBM2015 SP1 test server to 2020R1 you pointed the 2020 R1 setup to the 2015 SP1 Database and you are facing BizPulse not starting with the NullPointerException:

​​​E:\SBM2020R1\bin>startbizpulseserver
SavvionJNDIService.init()
log4j:WARN No appenders could be found for logger (org.jboss.logging).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
com.savvion.sbm.bizpulse.engine.intf.RuleEngineAPI$BPException: Invocation failed; nested exception is:
        javax.ejb.EJBException: java.lang.NullPointerException
        at com.savvion.ejb.bizpulse.manager.BizPulseClient$BizPulseClientFactory
$BizPulseClientMixenInvocationHandler.handleExceptio n(BizPulseClient.java:174)
        at com.savvion.sbm.bizpulse.common.proxy.AbstractProxyFactory$DynamicInv
ocationHandler.invoke(AbstractProxyFactory.java:185)
        at com.sun.proxy.$Proxy4.start(Unknown Source)
        at com.savvion.ejb.bizpulse.manager.BizPulseClient.main(BizPulseClient.java:255)

Solution

Use the following query to check which BizPulse rules are installed (if any):

select MODULE_ID,APP_NAME,MODULE_NAME from BIZPULSE_RULEEXTENT;

The issue might be caused by the following entry in the BIZPULSE_RULEEXTENT table:

Note: The exact MODULE_ID may differ for different DBs. MODULE_NAME should be enough to identify the rule.

This rule is not installed by default but may be left after installation of any other application and not removed while installing the application.

1. Please check with Bizpulse Admin if this rule/application is loaded or not. If this rule is still associated with any application then that might fails.
2. After you will make sure the rule is not loaded, delete this entry from the BIZPULSE_RULEEXTENT table.
3. Restart BizPulse after committing.

Testing

After you delete the rule BizPulse will start in SBM2021 R1 without exceptions.