This error occurs if the EMS topics do not exist when the BW application is deployed and started. You will see the following startup error in the logs while deploying the BW application.

<<<<
....
Activation error with process starter [Processes/InboundMessageFlow/BC-Integration/notifyErrorAdvisoryJMS.process]Activation error with process starter [Processes/InboundMessageFlow/BC-Integration/notifyErrorAdvisoryJMS.process] at com.tibco.pe.core.ProcessStarter.setState(Unknown Source) at com.tibco.pe.core.JobPool.if(Unknown Source) at com.tibco.pe.core.JobPool.resume(Unknown Source) at com.tibco.pe.core.JobPool.a(Unknown Source) at com.tibco.pe.core.JobPool.startNotFT(Unknown Source) at com.tibco.pe.PEMain.a(Unknown Source) at com.tibco.pe.PEMain.do(Unknown Source) at com.tibco.pe.PEMain.a(Unknown Source) at com.tibco.pe.PEMain.<init>(Unknown Source) at com.tibco.pe.PEMain.main(Unknown Source)caused by: Consumer couldn't start: com.tibco.tibjms.naming.TibjmsFederatedQueue cannot be cast to javax.jms.Topic at
....

>>>>

Resolution

=======

This error occurs if the "Auto Create destinations" flag is disabled. To resolve this in Designer, open the BusinessConnect ServerConfig palette and under the JMS tab, check the flag set for "Auto Create destinations".