In Designer BusinessConnect (BC) Server Config, I am unable to import schemas from the Operations Editor for EDI, EZComm, SOAP, RosettaNet and ebXML.
book
Article ID: KB0086350
calendar_today
Updated On:
Products
Versions
TIBCO BusinessConnect
-
Not Applicable
-
Description
Resolution: Description: ========== Importing protocol schemas from Operations Editor in Designer
Environment: ========== BusinessConnect all versions
Symptoms: ========= When I try to import protocol schemas (Import Selected Business Protocol) from BC Operations Editor in the Designer (BC Server Config), it does nothing. When I looked at the Designer > Window > Show Console, I can see below errors.
"Unexpected error encountered" at com.tibco.plugin.ax.bc.ProtocolInfo.<init>(ProtocolInfo.java:38) at com.tibco.plugin.ax.bc.InstallInfo.addProtocol(InstallInfo.java:106) [...] caused by: "Unexpected error encountered" at com.tibco.plugin.ax.bc.ProtocolInfo.getOpInfo(ProtocolInfo.java:349) at com.tibco.plugin.ax.bc.ProtocolInfo.getOpInfoList(ProtocolInfo.java:291) [...] caused by: Critical errors found while parsing the schema source: at com.tibco.ax.fw.xml5.BCXmlBuilder.reportSchemaFeature(BCXmlBuilder.java:1104) at com.tibco.plugin.ax.client.impl.BCParamInfoImpl.<init>(BCParamInfoImpl.java:47)
Cause: ====== When a schema is not uploaded for an operation in the Operations Editor, or an ecs file is uploaded into the operation schema instead of an xsd file for EDI protocols, this error occurs.
The root element name can be missing for the operation in the Operations Editor for EZComm, SOAP, RosettaNet and ebXML. The schema can be valid, but if the root element name is not specified in the operation in the Operations Editor, then this type of error may occur. A missing schema or incorrect file reference also may cause this issue for EZComm, SOAP, RosettaNet and ebXML protocols.
Resolution: ========= For EDI protocols, upload the schema (xsd) file in the Operations Editor for the schema. For EZComm, SOAP, RosettaNet and ebXML protocols, make sure the root element name has specified for an operation in the Operations Editor. Also make sure the physical schema file has uploaded, or if a file reference is used, insure that the schema file is at in that location.
Keywords/Tags: = = = = = = = = =
Issue/Introduction
In Designer BusinessConnect (BC) Server Config, I am unable to import schemas from the Operations Editor for EDI, EZComm, SOAP, RosettaNet and ebXML.