Resolution:
Description:
============
When running the EDIFACT example given in the User Guide, the following error occurs in the private process:


    &lttns:notificationResult xmlns:tns = "http://www.tibco.com/ns/ax/bc/EDI/2002/10/nonAeschema">
            &lttp>
                &lttpName&gtCompany2</tpName>
                &ltstatusCode&gt650</statusCode>
                &ltstatusMsg&gtNotification did not reach trading partner.XMLDocument could not be sent to the Trading Partner due to following reason:Errors were encountered during validation.</statusMsg>
            </tp>
        </tns:notificationResult>

Below is the error in the interior server logs.

Job-17019.17019 Exception: java.lang.NullPointerException at com.tibco.ax.tibedi.instream.XMLToEDIConverter.execute(XMLToEDIConverter.java:616) at com.tibco.ax.tibedi.runtime.pf.outbound.ConvertXDataToEDI.convertToEDI(ConvertXDataToEDI.java:288) at com.tibco.ax.tibedi.runtime.pf.outbound.ConvertXDataToEDI.Start(ConvertXDataToEDI.java:68) at com.tibco.ax.tibedi.runtime.pf.outbound.ConvertMsgInfo.xmlToEDIConversion(ConvertMsgInfo.java:545) at com.tibco.ax.tibedi.runtime.pf.outbound.ConvertMsgInfo.run(ConvertMsgInfo.java:205) at com.tibco.ax.tibedi.runtime.pf.outbound.ConvertMsgInfo.Start(ConvertMsgInfo.java:99) at com.tibco.ax.tibedi.runtime.pf.outbound.PrepareOutbound.prepareMsg(PrepareOutbound.java:619) at com.tibco.ax.tibedi.runtime.pf.outbound.PrepareOutbound.Start(PrepareOutbound.java:108) at com.tibco.ax.tibedi.runtime.pf.outbound.TransportCanonicalizer.sendThruNonGateway(TransportCanonicalizer.java:908) at com.tibco.ax.tibedi.runtime.pf.outbound.TransportCanonicalizer.Process(TransportCanonicalizer.java:879) at com.tibco.ax.tibedi.runtime.pf.outbound.TransportCanonicalizer.Initialize(TransportCanonicalizer.java:183) at com.tibco.ax.tibedi.runtime.pf.outbound.TransportCanonicalizer.Start(TransportCanonicalizer.java:82) at com.tibco.ax.tibedi.runtime.outbound.EDIOBBMHService.validateAndBuildMsgContext(EDIOBBMHService.java:1638) at com.tibco.ax.tibedi.runtime.outbound.EDIOBBMHService.preProcessMsg(EDIOBBMHService.java:168) at com.tibco.ax.fw.runtime.impl.AbstractService.preProcessor(AbstractService.java:290) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.tibco.plugin.gateway.InvokeOperationActivity.sInvokeServiceOp(InvokeOperationActivity.java:246) at com.tibco.plugin.gateway.InvokeOperationActivity$OperationThread.run(InvokeOperationActivity.java:376) at com.tibco.pe.util.ThreadPool$ThreadPoolThread.run(Unknown Source)


Environment:
============
TIBCO BusinessConnect™ 6.0
TIBCO BusinessConnect™ EDI Protocol powered by Instream®  6.4.0


Resolution:
===========
1). Check if the tibedi_plugin_info table is created. If not, try to create runtime tables manually under System Settings -&gtJDBC Configuration.

2). Check if the EDIFACT row is available in that table. If the table is empty, check that the correct JDBC driver is being used. For example, there may be two JDBC drivers (ojdbc5.jar and ojdbc6.jar) under the same folder and the Administrator and/or the BusinessConnect engine may pick up the ojdbc5.jar as the JDBC driver when creating the BC installation. To resolve this, remove the ojdbc5.jar or add the ojdbc6.jar file path to the beginning of tibco.class.path.extended parameter in the Tibcoadmin_&ltdomian>.tra.

A NullPointerException occur in the BusinessConnect log when executing the EDI sample project.