![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
• Name A name for the operation.
• Protocol The business protocol to be used to create the schema and carry out the transaction. For more information about protocols, see Business Protocols.
•
• Process Definition of a high-level business process. This is the business logic for message sequence, decisions, and roles for each trading partner in a transaction. Technical details are not addressed.
• Vocabulary and Data Dictionary The technical aspects of creating a business message involve using vocabulary and data dictionary standards.In this example, the data dictionary lists the WidgetQuoteRequest element and defines the string data format for the type element.
• Implementation Framework Core The vocabulary and data dictionary standards are in turn built on packaging the message and transferring it to a trading partner using an implementation framework core. This core defines the technical details of how trading partners exchange information. For example, this core includes areas like the transport protocols that partners agree to use. This is the key to interoperability.
• Partner Agreement This is a specific agreement between partners. It refers to the particular conversation, message structure, transport protocol, and security attributes that partners choose for their communications. Depending on the business protocol, this also includes technical details like the certificates file and the URL for HTTPS transport.
• Conversation This includes certain communication options. Depending on the business protocol, these include transaction types like notify and synchronous or asynchronous request-response, and options like time-outs, retries, and exception handling.
• Message Envelope Depending on the business protocol, this includes MIME, S/MIME, XML, or CSV. Each business protocol must provide a message envelope to carry the message body. This envelope and message are then wrapped in an envelope provided by the transport protocol.
• Transport Protocol Depending on the business protocol, this includes HTTP, HTTPS, FTP, or SMTP.
• Security Depending on the business protocol, this includes authentication, access control, non-repudiation, and encryption.In TIBCO BusinessConnect, nested schemas of unlimited depth are supported for validation. They need to be configured as file references, including the root schema, with the exception of TIBCO BusinessConnect SOAP Protocol where interfaces that use these nested schemas have been imported using the WSDL import tool. Also, nested schema closures can be referenced with either relative or absolute paths. See File Specification Dialog in TIBCO BusinessConnect Trading Partner Administration.It is recommended to use relative paths for closure references. In case a full path is preferred and the references are of type file, the valid URI is as follows:If nested schemas are configured as File Reference, their location should not change compared to the configured location under BusinessConnect > Operations Editor. This is because the content of the schema components are loaded into TIBCO BusinessConnect schema cache on demand from the specified location.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |