Configuration Store Reporting Schema Details The tables in TIBCO BusinessConnect have configuration data in blob format. For creating Jasper reports, new tables are derived from existing TIBCO BusinessConnect database schemas in order to store the binary (BLOB) information in a structured format. You can write SQL queries using these tables which are similar to the data source for generating JasperReports for Configuration data. These tables consist of key-value pair which holds data about partner settings, protocols, transports, business agreements, scheduled transmission and operation bindings components. In general, the key is internal identifier of a component's property of BusinessConnect. The table description for the Jasper Reporting schema is depicted in Table 129. Table 129 Configuration Store Reporting Schema Details Name Documentation BC_CS_PROTOCOL_PROPERTIES This table stores the host or the partner settings of each protocol enabled for a trading partner. The data is sourced from BC_PROTOCOL table. The PROTOCOLID of this table corresponds to BC_PROTOCOL.OBJOID. For example, the following query returns the names of trading partners having X12 protocol enabled with Outbound XML to EDI Data Encoding property set to UTF-8: SELECT TP.OBJNID FROM BC_PARTICIPANT TP INNER JOIN BC_PROTOCOL P ON P.OWNER_OID = TP.OBJOID INNER JOIN BC_CS_PROTOCOL_PROPERTIES PP ON PP.PROTOCOLID = P.OBJOID WHERE PP.PROTOCOLNAME = 'X12' AND PP.BCKEY = '_tpEnableOBEDIEncoding' AND PP.BCVALUE = 'UTF-8'; BC_CS_TRANSPORT_PROPERTIES This table stores the transport settings of each protocol enabled for a trading partner. The data is sourced from BC_CHANNELINFO table. The TRANSPORTID of this table corresponds to BC_CHANNELINFO.OBJOID. For example, the following query returns the names of trading partners that use HTTP Basic Authentication: SELECT TP.OBJNID FROM BC_PARTICIPANT TP INNER JOIN BC_PROTOCOL P ON P.OWNER_OID = TP.OBJOID INNER JOIN BC_CHANNELINFO TR ON TR.OWNER_OID = P.OBJOID INNER JOIN BC_CS_TRANSPORT_PROPERTIES TRP ON TRP.TRANSPORTID = TR.OBJOID WHERE TRP.TRANSPORTNAME = 'http' AND TRP.BCKEY = 'useHTTPBasicAuthentication' AND TRP.BCVALUE = 'true'; BC_CS_BA_PROTOCOL_PROPERTIES This table stores the Agreement Protocol Binding settings of each protocol configured for a Business Agreement between the trading partners. The data is sourced from BC_PBV table. The PROTOCOLBINDINGID of this table corresponds to BC_PBV.OBJOID. For example, the following query returns the names of trading partners having X12 protocol enabled with Regenerate Control Number For Batch Resend set to true SELECT TP.OBJNID FROM BC_PARTICIPANT TP INNER JOIN BC_BIZAGREEMENT BA ON BA.PROFILEB_OID = TP.OBJOID INNER JOIN BC_PB PB ON PB.OWNER_OID = BA.OBJOID INNER JOIN BC_PBV PBV ON PBV.OWNER_OID = PB.OBJOID INNER JOIN BC_CS_BA_PROTOCOL_PROPERTIES PP ON PP.PROTOCOLBINDINGID = PBV.OBJOID WHERE PB.OBJNID = 'X12' AND PP.BCKEY = 'Batching._regenerateCtrlNum' AND PP.BCVALUE = 'true' BC_CS_BA_STMS This table stores the Scheduled Transmission settings of applicable Agreement Protocol Binding configured for a Business Agreement between the trading partners. The data is sourced from BC_PBV table. The PROTOCOLBINDINGID of this table corresponds to BC_PBV.OBJOID. For example, the following query returns the Agreement name and Transmission Mode of Scheduled Transmission defined at Agreement Protocol Binding: SELECT BZ.DISPLAY_NAME baName, STMS.BCVALUE transmissionMode FROM BC_BIZAGREEMENT BZ INNER JOIN BC_PB PB ON PB.OWNER_OID = BZ.OBJOID INNER JOIN BC_PBV PBV ON PBV.OWNER_OID = PB.OBJOID INNER JOIN BC_CS_BA_STMS STMS ON STMS.PROTOCOLBINDINGID = PBV.OBJOID WHERE STMS.BCKEY LIKE 'TransmissionWindow' BC_CS_BA_OB_PROPERTIES This table stores the Operation Bindings settings of each Agreement Protocol Binding configured for a Business Agreement between the trading partners. The data is sourced from BC_OPB table. The PROTOCOLBINDINGID of this table corresponds to BC_OPB.OBJOID. For example, the following query returns the names of ebMS3 operations with Require MSH Receipt set to 'always' for Request Action: SELECT OP.OBJNID FROM BC_INTFCOMPONENT OP INNER JOIN BC_OPB OB ON OB.TX_OID = OP.OBJOID INNER JOIN BC_CS_BA_OB_PROPERTIES OBP ON OBP.OPERATIONBINDINGID = OB.OBJOID WHERE OBP.BCKEY = 'request.Receipt.mshReceiptRequired' AND OBP.BCVALUE = 'always' TIBCO BusinessConnect supports following database views: • BC_CS_PARTICIPANT • BC_CS_PROTOCOL • BC_CS_LOCATION • BC_CS_TRANSPORT • BC_CS_BIZAGREEMENT • BC_CS_PROTOCOL_BINDING • BC_CS_PROTOCOL_BINDING_VIEW • BC_CS_OPERATION_BINDING