Resolution:

When running Business Events events engine in BE-BW (you start Business Works engine from you Business Events engine), some of the BusinessWorks starter processes do not start when started from TIBCO Administrator, but the same works fine when starting the BusinessEvents engine from the command/shell prompt. 

Resolution

 

When deploying a BE-BW project in TIBCO Administrator, you need to configure a BusinessWorks Process Archive (PAR) in your Enterprise Archive (EAR). Sometimes not all the BusinessWorks starter processes are included in this PAR, which is the main reason for this issue. So first check the PAR. If you have included all the StarterProcesses, rebuild the EAR and deploy it.

The reason that it works when the same project is started via the command line is because in the TRA used in this startup method, you may have specified the property tibco.bwrepourl which has the reference to the directory where you had the complete BE-BW project. By default it loads all the Business Works starter process from this directory.

When running BusinessEvents events engine in BE-BW (starting Business Works engine from BusinessEvents engine), the BusinessWorks starter processes does not start when started from TIBCO Administrator.