Resolution:
Description:
===========
A brief overview of what can occur when RV or EMS is not configured properly to work with BE.

Environment:
===========
All

Symptoms:
=========
The following are two of the possible errors/warnings that can be thrown usually at the startup routine:

- Could not load payload class:  com.tibco.cep.driver.tibrv.serializer.TibrvMsgPayload
- java.lang.NullPointerException
     ...
     ...
     at com.tibco.cep.driver.jms.serializer.MapMessageSerializer.deserialize(MapMessageSerializer.java:62)

Cause:
======
Because RV and EMS features are optional addendums to BE 4.0, they are not automatically script-configured in the BE TRA files. They must be manually updated when used.  For instance, the TRA file "Common Environment Variables" may look something like the following:

tibco.env.PSP=;
tibco.env.TIB_HOME=d:/tibco
tibco.env.BE_HOME=d:/tibco/be/4.0
tibco.env.RV_HOME=
tibco.env.EMS_HOME=d:/tibco/ems
...
...


It should actually look like the following instead:

tibco.env.PSP=;
tibco.env.TIB_HOME=C:/tibco
tibco.env.BE_HOME=C:/tibco/be/4.0
tibco.env.RV_HOME=C:/tibco/tibrv/8.1
tibco.env.EMS_HOME=C:/tibco/ems/5.0
...
...

Resolution:
=========
Ensure that when used, RV and EMS are correctly referenced in the "Common Environment Variables" section of the be-engine.tra file.  See the the "cause" section above for a hands-on example.

TIBCO Enterprise Message Service (EMS) and TIBCO Rendezvous (RV) relationship with TIBCO BusinessEvent (BE).