To understand the involvement of user personas in TIBCO BusinessConnect Container Edition, see the following process flow:
Procedure
System Admin activates inbound transport protocols. For example, enables HTTP inbound protocol and creates HTTP Gateway Service.
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.
Partner specialist can perform the following tasks:
CRUD Participant
: Creates partner, searches or edits partners from the already existing list.
Certificates: Uploads public certificates, which either are shared by the partner through emails or are uploaded by the partner themselves.
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.
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.
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 the Host to retrieve the transaction from the partner's FTP server.
Outbound: For each business protocol, onboarder selects the applicable operation types.
