Description:
While deploying the application on the Tomcat engine, Error: "FATAL RMI exception"

************************
Fatal RMI Error
caused by: ; nested exception is:
        java.lang.NullPointerException

        at com.tibco.workflow.icjava.WfDocumentImpl.setContentBytes(WfDocumentImpl.java:1050)
        at com.tibco.ae.util.WfContentManager.addDescriptor(Unknown Source)
        at com.tibco.workflow.export.ExportHelper.addWfObjectDescriptors(Unknown Source)
        at com.tibco.workflow.export.ExportJobHelper.doJobExport(Unknown Source)
        at com.tibco.workflow.export.ExportManager.exportWorkflows(Unknown Source)
        at com.tibco.tra.tsm.plugin.TSMFormFlowBindingDeploy.deployWorkflows(Unknown Source)
************************
The above exception usually occurs during deployment when repository server was misconfigured due to the wrong setting of RV parameter in icrepconfig.xml or not running properly.


Symptoms:
TIBCO BusinessWorks Collaborator uses "WfDocument.setContentBytes()" IC API (IC Client) for updating the documents which internally uses the RMI APIs to maintain the documents on the IC server side. In Failure to connect to the repo server, you can run into the “FATAL RMI exception”.
Cause:
TIBCO BusinessWorks Collaborator uses "WfDocument.setContentBytes()" IC API (IC Client) for updating the documents, which internally uses the RMI APIs to maintain the documents on the IC server side. In Failure to connect to the repo server, you can run into the “FATAL RMI exception”.

For the above exception, check the following setting of the RV parameter in ‘icrepconfig.xml’ and ‘icconfig.xml’.
<tibrv>
            <IC_TIBRV_DAEMON default="tcp:7500"/>
            <IC_TIBRV_DESCRIPTION default=""/>
            <IC_TIBRV_NETWORK default=""/>
            <IC_TIBRV_RESPOND_GETNAMES default="1">1</IC_TIBRV_RESPOND_GETNAMES>
            <IC_TIBRV_SERVICE default="7500"/>
</tibrv>

After that, un-register and re-register the IC and Repo Server through the domain utility to reflect the changes in the Admin domain with the new RVD transport configuration.

“FATAL RMI exception” while deploying the application on the Tomcat engine.