Container Edition Concepts
Version 1.1.0 January 2021
2 | Contents
Contents
Contents
2
TIBCO Documentation and Support Services
3
Overview
5
TIBCO BusinessConnect Container Edition Features
6
Key Concepts
7
Onboarding Process 8
Private Process using TIBCO ActiveMatrix BusinessWorks plug-in for
BusinessConnect 9
User Personas
12
Persona Involvement 13
TIBCO BusinessConnect Container Edition Components
15
Authentication Server 17
AuditSafe 17
FS REST 17
Security Concepts
20
Deployment
22
Fault Tolerance and Load Balancing
23
Smart Routing
24
Legal and Third-Party Notices
26
TIBCO Documentation and Support Services
For information about this product, you can read the documentation, contact TIBCO Support, and join TIBCO Community.
How to Access TIBCO Documentation
Documentation for TIBCO products is available on the TIBCO Product Documentation website, mainly in HTML and PDF formats.
The TIBCO Product Documentation website is updated frequently and is more current than any other documentation included with the product. To access the latest
documentation, visit https://docs.tibco.com.
Product-Specific Documentation
Documentation for TIBCO BusinessConnect™ Container Edition is available on the TIBCO BusinessConnect™ Container Edition page.
The following documents for this product can be found in the TIBCO Documentation site:
l TIBCO BusinessConnect™ Container Edition Release Notes
l TIBCO BusinessConnect™ Container Edition Installation and Deployment l TIBCO BusinessConnect™ Container Edition Concepts
l TIBCO BusinessConnect™ Container Edition Trading Partner Management l TIBCO BusinessConnect™ Container Edition Administration
l TIBCO BusinessConnect™ Container Edition Security Guidelines
How to Contact TIBCO Support
You can contact TIBCO Support in the following ways:
l For an overview of TIBCO Support, visit http://www.tibco.com/services/support.
l For accessing the Support Knowledge Base and getting personalized content about products you are interested in, visit the TIBCO Support portal at
https://support.tibco.com.
l For creating a Support case, you must have a valid maintenance or support contract
4 | TIBCO Documentation and Support Services
with TIBCO. You also need a user name and password to log in to
https://support.tibco.com. If you do not have a user name, you can request one by clicking Register on the website.
How to Join TIBCO Community
TIBCO Community is the official channel for TIBCO customers, partners, and employee subject matter experts to share and access their collective experience. TIBCO Community offers access to Q&A forums, product wikis, and best practices. It also offers access to extensions, adapters, solution accelerators, and tools that extend and enable customers to gain full value from TIBCO products. In addition, users can submit and vote on feature requests from within the TIBCO Ideas Portal. For a free registration, go to
https://community.tibco.com.
Overview
TIBCO BusinessConnect™ Container Edition is a lightweight, sophisticated tool your company can use for business-to-business electronic commerce transactions that are deployed uniformly and consistently across container-based PaaS platforms. It enables the secure transmission of documents and messages between partners using disparate
internal business systems.
You can containerize a TIBCO BusinessConnect application by using Docker. You can also run the Docker based TIBCO BusinessConnect application in a Kubernetes cluster on the cloud platform of your choice. To understand the concepts of TIBCO BusinessConnect™
Container Edition, you must be familiar with the following concepts:
l Docker concepts. See Docker Documentation.
l Kubernetes concepts. See Kubernetes Documentation.
6 | TIBCO BusinessConnect Container Edition Features
TIBCO BusinessConnect Container Edition Features
TIBCO BusinessConnect Container Edition is based on an orchestration framework and is scalable, lightweight, and supports widely accepted industry standards. Additionally, it also has a modernized user interface that makes the BusinessConnect components simple to configure and manage.
Modularity
TIBCO BusinessConnect Container Edition provides the benefit of modularity. Each module such as Admin Server, ConfigStore Management Server, Gateway Server, Interior Server, Poller Server, and AuditSafe can be deployed independently.
Scalability
TIBCO BusinessConnect Container Edition provides the benefit of independent, modular scalability. You can horizontally scale each module independently according to the workload.
Standards-based
TIBCO BusinessConnect Container Edition supports TIBCO BusinessConnect™ Container Edition - Services Plug-in (EZComm) and standard business protocol such as TIBCO BusinessConnect™ Container Edition - RosettaNet Protocol (RosettaNet) and TIBCO BusinessConnect™ Container Edition - EDI Protocol powered by Instream®.
Cloud Independence
TIBCO BusinessConnect Container Edition can run in most of Docker-based Platform as a Service (PaaS) environments. You can deploy, monitor, and manage the application using Kubernetes-based orchestration framework.
Key Concepts
This topic gives you a brief description of the terms that you may encounter when working with the product. To understand these basic concepts of TIBCO BusinessConnect
Container Edition, you can go through the following key concepts:
Trading Partners:
Trading Partners are the participants involved in a business relationship to carry out business transactions between each other. TIBCO BusinessConnect Container Edition defines two types of trading partners: Hosts and Partners.
l Host: A participant who sponsors a trading community, where standardized
business transactions occur between host and its trading partners. A host can be a retailer, a manufacturer, or any sponsor who creates a trading community.
l Partner: A participant who is outside the host's company and establishes business agreement with the host. For example, a partner can be a vendor, customer, or healthcare provider.
Trading Community:
Trading community is a conceptual domain within which business transactions occur between the host and its trading partners. TIBCO BusinessConnect Container Edition allows an enterprise to create a trading community, which consists of a host (the creator or sponsor of a trading community) and its respective partners.
Business Agreement:
Host and its trading partners are bound by a business agreement that includes detailed information, which the participants must agree upon before they exchange electronic documents with each other. The business agreement between host and partner must have information regarding the business protocols (inbound or outbound), the corresponding transport protocols, and operations. In TIBCO BusinessConnect Container Edition, the protocol-centric business agreement establishes a common method for exchanging business documents between the two participants.
Business Protocols:
Business Protocols are the standard methods used to exchange business documents between the participants. The host and the partner have to agree upon a common
8 | Key Concepts
protocol before exchanging business documents or any operation in the transaction.
This simplifies business transactions between the trading partners. For example, RosettaNet, EZComm, X12, and Gateway are the business protocols with their own specifications on how trading partners should send and receive business documents and its format.
Transport:
TIBCO BusinessConnect Container Edition supports HTTP, HTTPS, AS2_HTTP, AS2_
HTTPS, EMAIL, AS1_EMAIL, FILE, FTP, FTPS, and SSHFTP transports to facilitate secured communication and transmission of the electronic documents between the participants.
The type of the transport protocol depends upon the business protocols that are specified in the business agreement between the host and the trading partner.
Operations:
An operation is defined as the type of electronic document exchanged between the trading partners. The type of operation depends upon the business agreement established between the participants. For example, a typical B2B implementation manages operations such as purchase order, invoice, shipment status, and other types of operations with their respective number assignment.
Private Process:
Private process refers to the internal processes within your company that exchange data through the TIBCO BusinessConnect Container Edition server. Typically, a private process includes sending or receiving B2B documents deeper into or from the host's internal applications, such as an ERP system, a claims adjudication system, and other systems.
Onboarding Process
The process of adding a trading partner to a host's community and creating the business agreement between the partner and the host is called the Onboarding Process.
The following diagram illustrates the onboarding process in TIBCO BusinessConnect Container Edition:
Onboarding Process
l The arrows in the diagram represent the business protocols. Each type of the business protocol has its own color For example, red arrow represents RosettaNet protocol whereas blue arrow represents EZComm protocol.
l The business documents are exchanged between the Host and the Partner using the transport protocols such as HTTP/S and FTP.
Private Process using TIBCO ActiveMatrix BusinessWorks plug- in for BusinessConnect
With TIBCO ActiveMatrix BusinessWorks Plug-in for BusinessConnect and TIBCO ActiveMatrix BusinessWorks, you can create process definitions that serve as private processes for a TIBCO BusinessConnect Container Edition. TIBCO ActiveMatrix
10 | Key Concepts
BusinessWorks can either send requests to TIBCO BusinessConnect Container Edition or receive replies from it.
The following figure illustrates TIBCO ActiveMatrix BusinessWorks operating in conjunction with TIBCO BusinessConnect Container Edition.
TIBCO ActiveMatrix BusinessWorks Communicating with TIBCO BusinessConnect Container Edition
Company A implements a private process in TIBCO ActiveMatrix BusinessWorks and uses the Send Request/Notification activity to invoke a pre-configured B2B operation on a TIBCO BusinessConnect Container Edition server. TIBCO BusinessConnect Container Edition in Company A sends the request to TIBCO BusinessConnect Container Edition server at Company B, which has a process definition with the Receive Request/ Notification process starter.
This process definition receives the incoming request, processes it, and sends a response back to the TIBCO BusinessConnect Container Edition server using the Send Response activity. TIBCO BusinessConnect Container Edition then routes the reply back to the original requestor.
It is not necessary for TIBCO ActiveMatrix BusinessWorks to be used to implement the private process at both Company A and Company B. A different application can be used to send the request or receive the request. However, it is necessary for TIBCO
BusinessConnect Container Edition to be used at any site where TIBCO ActiveMatrix
BusinessWorks is used to send or receive TIBCO BusinessConnect Container Edition messages.
You can use TIBCO ActiveMatrix BusinessWorks to build the private processes, specifically using the tool TIBCO Business Studio™.
Using TIBCO Business Studio
TIBCO Business Studio is an easy-to-use GUI for configuring, designing, and testing TIBCO ActiveMatrix BusinessWorks projects. TIBCO Business Studio provides an integrated development environment including these components:
l Project directory l Project resources l Process design l Activity configuration
You can use TIBCO Business Studio as a modeling tool to design business processes as a part of your business-to-business integration as shown in the figure below:
TIBCO Business Studio
TIBCO Business Studio is used in the design time environment for designing and testing business processes and to prepare documents for secure transmission over the Internet. It contains a number of native palettes, including the TIBCO BusinessConnect palette.
To learn more about these palettes and how to work with the application, please refer to TIBCO Business Studio User’s Guide.
12 | User Personas
User Personas
You can create different user roles in TIBCO BusinessConnect Container Edition with reference to the user persons described in the following table:
Persona Description System
Admin
l Has sound technical knowledge.
l Manages deployment of servers and underlying technical services.
l Sets up initial set of users and create transport protocols.
l Sets up system settings, Gateway server, all inbound transports, and database connectivity.
Application Admin
l Manages initial and ongoing setup of key objects such as transport protocols, business protocols, and operation types.
l Performs CRUD (Create, Read, Update, and Delete) operations on hosts and users.
l Enables the business protocols and the operations that are shipped with TIBCO BusinessConnect.
l Can view all the business transactions.
l Does not have access to the users and roles.
Partner Specialist
l Manages partners and business agreements between the host and the partner.
l Performs the CRUD operations on the profiles of trading partners and business agreements using GUI.
l Creates and assigns Outbound/Inbound transports for available Business Protocols
l Selects hosts and business protocols and binds operations to the selected business protocols.
Business User
l Can view all the business transactions.
Note: The Admin role, which is a default role with all the privileges, can add the other users and roles based on the personas.
Persona Involvement
To understand the involvement of user personas in TIBCO BusinessConnect Container Edition, see the following process flow:
Procedure
1. System Admin activates inbound transport protocols. For example, enables HTTP inbound protocol and creates HTTP Gateway Service.
2. The protocols are already installed and enabled for the hosts. Application Admin creates one or more hosts, configure the properties of the protocols, enables different operations, and pairs any operations that need to be coupled.
3. Partner specialist can perform the following tasks:
a. CRUD Participant : Creates partner, searches or edits partners from the already existing list.
b. Certificates: Uploads public certificates, which either are shared by the partner through emails or are uploaded by the partner themselves.
c. Business Protocols: Selects business protocols from ones made available by Application Admin, for example, EZComm and RosettaNet.
For the selected business protocol, onboarder fills the applicable properties, including the Partner Name as required by the business protocol.
d. Transport Protocols: Selects applicable transport protocols for receiving transactions from a list that has been enabled by the System Admin. For example, HTTPS, SFTP, AS2 protocols. For each transport protocol, onboarder fills out a form, which includes properties of the transport protocol applicable to the partner.
e. Business Agreement: Selects which host to trade with and configures business agreement between the host and the partner.
Inbound: For each business protocol, if there are any secure FTP transports, onboarder specifies the URLs and applicable protocol properties. This enables
14 | User Personas
the Host to retrieve the transaction from the partner's FTP server.
Outbound: For each business protocol, onboarder selects the applicable operation types.
TIBCO BusinessConnect Container Edition Components
TIBCO BusinessConnect Container Edition comprises the following components. Each component of TIBCO BusinessConnect Container Edition should run in a Docker container.
To implement the different features of TIBCO BusinessConnect in the Docker environment, you must create a Docker image of each component. These component images run in their Docker containers and communicate with each other using TIBCO Enterprise Message Service messaging system.
The following diagram shows different components in TIBCO BusinessConnect Container Edition and their interaction with each other:
BusinessConnect Container Edition Components
Gateway Server
Gateway Server is located in the demilitarized zone (DMZ), and functions as the front gate by receiving the inbound transactions from trading partners. Multiple Gateway Servers can work together for load balancing.
16 | TIBCO BusinessConnect Container Edition Components
This server has several restrictions on the networks it can access. It is used to host HTTP gateway service, to receive B2B communications directly from the Internet with security features such as SSL and SSH. The firewall between the Gateway Server and the rest of your system protects against the threat of malicious communications. TIBCO
BusinessConnect Container Edition Gateway Server is a standalone Java executable that is not dependent on TIBCO ActiveMatrix BusinessWorks. However, it still needs TIBCO
Enterprise Message Service to communicate with the Interior Server. This server performs the following tasks:
l Receives inbound request through HTTP/S/CA transports protocols.
l Communicates with Interior Server using the TIBCO Enterprise Message Service message bus for Inbound messages that are received.
l Allows trading partner to exchange messages using business protocols.
l Hosts HTTP Service which supports HTTP, HTTPS, and HTTPSCA transports for document exchange.
Interior Server
Interior Server is the server on which TIBCO BusinessConnect Container Edition is installed on top of the other required TIBCO software products. Multiple Interior Servers can work as a cluster to achieve load balancing and fault tolerance. This server is located inside the company’s firewall and performs the following tasks:
l Handles all messaging level activities, such as message packaging and unpacking, encryption and decryption, signature and verification, and so on, according to numerous transport and vertical business standards.
l Takes care of business level logic to be executed by each individual protocol, such as document schema validation, business level acknowledgment generation, and so on.
l Communicates with Gateway Server and Poller Server using TIBCO Enterprise Message Service message bus for Inbound messages.
l It also communicates with AuditSafe server using REST APIs to post audit logs.
Poller Server
l Communicates with Interior Server using TIBCO Enterprise Message Service message bus to receive inbound messages.
l Retrieves inbound request from FTP and SFTP servers, Mail server, and shared file
directory.
l Includes both inbound and outbound pollers.
Admin Server
l Exchanges data with ConfigStore Management Server (CMS) using CMS REST API calls.
l Allows you to configure and manage BusinessConnect features like configuration of participants, operation editor, and business agreement.
ConfigStore Management Server
l Communicates with Admin Server and has access to the database.
l Performs CRUD operation on configstore.
Authentication Server
l Stores user information for both BusinessConnect Container Edition and AuditSafe l Authenticates user login for both BusinessConnect Container Edition and AuditSafe
AuditSafe
AuditSafe
l TIBCO BusinessConnect Container Edition saves audit logs to AuditSafe using REST API.
l Allows you to view the chain of logs for a transaction and detail for each log received, download payloads, configure views for AuditSafe dashboard.
FS REST
l TIBCO Foresight(R) REST API is a REST API providing EDI validation, response document generation, and translation services.
18 | TIBCO BusinessConnect Container Edition Components
For detailed information, see TIBCO Foresight(R) REST API documentation.
For detailed information of the components, see the following high-level architecture of TIBCO BusinessConnect Container Edition:
High-level Architecture
Database
This database contains the configuration information used and data log created by BusinessConnect Container Edition protocols, runtime data used by the BusinessConnect Container Edition server and protocols.
Communication Between the Servers
The TIBCO Enterprise message service is used by Gateway Server and Poller server to communicate with Interior Server for many purposes, such as the initial notifications when
a Gateway Server is started, and the notification when a large message arrives from trading partners.
Additionally, TIBCO Enterprise Message Service is also used for transferring configurations necessary for starting the gateway services, such as the HTTPS server keys and so on.
TIBCO Enterprise Message Service is also used for transferring small size messages between the Gateway Server and Interior Server.
Interior Server sends inbound messages to the private process and gets the request messages from private process using TIBCO Enterprise Message Service. Similarly, Poller Server forwards inbound messages to the TIBCO Enterprise Message Service message bus, which further sends message request to the Interior Server.
The load balancing feature of TIBCO Enterprise Message Service is leveraged by Interior Servers, so the inbound traffic is load balanced between these servers.
20 | Security Concepts
Security Concepts
This topic gives you a brief overview on how TIBCO BusinessConnect Container Edition secures and protects your data.
Secure Communication Channel
TIBCO BusinessConnect Container Edition achieves secure communication by using HTTPS over SSL/TLS, FTPS over SSL/TLS, or SSHFTP over SSH, where the whole communication pipe is encrypted.
Authentication
Authentication is used to assure the identity of the partner with whom you are
communicating. In a communication system, authentication is performed as a part of the handshake process to verify that the messages originate from their stated source. TIBCO BusinessConnect Container Edition authentication is based on X.509 SSL/TLS or SSH certificates.
Authorization
Authorization is the next step in achieving secure communication. It is used to check the configuration database and verify that the sender is authorized to perform the operations and receive certain responses.This is done through trading partner management, where permissions are set through binding the operations. After the sender of a message has been authenticated, TIBCO BusinessConnect Container Edition determines which operations the sender is currently allowed to perform by checking trading partner information in the repository. TIBCO BusinessConnect Container Edition uses repository information to determine how it responds to a message from the partner. In some cases, the partner may not be authorized to perform certain interactions. In order to conceal the information from unauthorized parties and to assure privacy of business data, TIBCO BusinessConnect Container Edition uses data encryption.
Message Encryption
To ensure only the intended recipient reads the data, the message is encrypted by converting plain text into cipher text.
Encryption also achieves privacy or concealing of information from unauthorized parties by using private and public keys combined with the secret key algorithms.
For example, the sender sends a message encrypted using Public Key provided by the recipient and the recipient decrypts the message using its own Private Key.
TIBCO BusinessConnect Container Edition uses either PKI (Public Key Infrastructure) or OpenPGP for public and private keys.
In Public Key encryption, anyone can encrypt a message intended for a recipient, while only the intended recipient is permitted to decrypt such a message. The one who creates the ciphertext message cannot decrypt their own message since they do not have the private key. Only the owner of the matching private key can decrypt the message encrypted with a specific public key.
Digital Signatures
Confidentiality of the business data is protected using encryption whereas digest algorithms protect the data integrity. These algorithms are utilized by digital signature algorithms to provide authentication services.
Authentication using digital signatures is done using S/MIME authentication. It involves adding a digital signature to the outgoing message. Digital signatures bind information to the identity of its originator. They are used to provide data origin authentication and data integrity.
For example, a sender can use their Private Key to add a Digital Signature to a piece of data in order to assure the recipient that the piece of data is originating from the sender, and the partners who have the corresponding Public key can decode this signature.
The process of adding digital signature is contrary to the encryption process used in message and transport encryption.
For detailed information on the various security methods implemented in
BusinessConnect Container Edition, see TIBCO BusinessConnect Container Edition Security Guidelines, Security .
22 | Deployment
Deployment
Each component of TIBCO BusinessConnect Container Edition is a service and all these services are deployed and run in the Kubernetes cluster.
The BusinessConnect Container Edition package contains most of the files that are required to build the Docker images for the BusinessConnect Container Edition components.
You are required to download only a few third-party library jars for building the Docker images for BusinessConnect Container Edition .
You must upload these Docker images onto the private Docker registry and properly set the properties after which the deploying script creates the secrets of Docker login, log4j2, certs, and mounted path and finally, deploy all the services of BusinessConnect Container Edition one at a time.
Fault Tolerance and Load Balancing
For fault tolerance and load balancing, the Docker based TIBCO BusinessConnect application is run in a Kubernetes cluster.
This Kubernetes has multiple master nodes and worker nodes. To avoid any physical failure of the machine all the BCCE service pods are allowed to run on the different nodes.
When any one of the pods fail, the new pod for the same service is started.
Also, the Kubernetes cluster is enabled with the load balancer for each service, which balances and manages several jobs and congestion caused due these jobs.
24 | Smart Routing
Smart Routing
In TIBCO BusinessConnect Container Edition, the messages are routed to the private processes using Private Process Smart Routing. Private Process Smart Routing makes it possible for users to route preferred messages to the selected private process instances while other messages can be received and processed by the rest of the instances in the same or in the different TIBCO ActiveMatrix BusinessWorks projects.
TIBCO BusinessConnect Container Edition allows you to define simple business rules to route messages to specific private processes. You can configure which messages should be routed to which private process instance using the Admin server through the Admin UI.
You can also specify a set of business rules, such as to route all messages from the trading partner A to the host B towards the private process C.
Configuring Private Process Smart Routing Smart routing requires:
l Configuring the TIBCO BusinessConnect Container Edition Admin server through Admin UI.
l Configuring of the private processes through the TIBCO BusinessConnect Palette in TIBCO ActiveMatrix BusinessWorks plug-in for BusinessConnect.
Using Admin UI, you can set up the business rules and specify the smart ID to be assigned to messages that meet the conditions of the rule.
Business Rules for Private Process Smart Routing
Business rules identify a set of messages based on one or more of these variables:
• Business protocol
• Sending partner
• Receiving partner
• Message direction (inbound or outbound)
• Operation ID
Using the TIBCO BusinessConnect Palette, you can configure which private processes will receive the messages that include specific smart IDs.
The private processes can inherit a smart ID from a shared resource. You can specify no smart routing for a private process within a shared resource and you can also specify a smart ID for a private process outside of a shared resource.
Smart Routing
For more information on configuring Smart Routing for private processes, see TIBCO BusinessConnect Container Edition Trading Partner Management, Private Process Smart Routing.
Configuring Private Process Smart Routing for the TIBCO BusinessConnect Palette When you select the check box Use Smart Routing, a text field named Smart Routing ID becomes visible and editable. By enabling this option on the shared resource, you can allow for the referencing event sources to use the specified smart ID value and inherit changes in the ID's value created on the given shared resource. If you want the specific event source to define its own Smart Routing ID, the check box Shared Smart ID must be cleared and an individual smart ID can be specified to take precedence over the ID (if any) on the referenced shared resource.
26 | Legal and Third-Party Notices
Legal and Third-Party Notices
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE
AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE
SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN
AGREEMENT TO BE BOUND BY THE SAME.
This document is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.
TIBCO, the TIBCO logo, the TIBCO O logo, TIB, and TIBCO Enterprise Message Service are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.
Java and all Java based trademarks and logos are trademarks or registered trademarks of Oracle Corporation and/or its affiliates.
This document includes fonts that are licensed under the SIL Open Font License, Version 1.1, which is available at: https://scripts.sil.org/OFL
Copyright (c) Paul D. Hunt, with Reserved Font Name Source Sans Pro and Source Code Pro.
All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.
This software may be available on multiple operating systems. However, not all operating system platforms for a specific software version are released at the same time. See the readme file for the availability of this software version on a specific operating system platform.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS.
CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR
INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.
This and other products of TIBCO Software Inc. may be covered by registered patents. Please refer to TIBCO's Virtual Patent Marking document (https://www.tibco.com/patents) for details.
Copyright © 2001-2021. TIBCO Software Inc. All Rights Reserved.
