Work with protocols, formats and standards

B2Bi supports the exchange of messages and files over a wide array of protocols and standards.

B2Bi message exchanges can be classified in two general categories:

Exchanges with applications

You can configure B2Bi to exchange (send and consume) messages and files with applications on your private network. You set up application pickups and deliveries within a community.

In B2Bi, exchanges with applications can be further classified in two types:

  • Application exchanges managed by the trading engine (standard exchanges)
  • Application exchanges managed by the integration engine (exchanges compatible with some migrated installations)

Which type of application exchange should I use

In general, you work with the application exchanges managed by the trading engine. Certain protocols (such as FTP / Email) can be managed either by the trading engine or the integration engine. The “duplicate” protocols provided by the integration engine are available for backward compatibility reasons. In non-migrated deployments, you should always use the trading engine application exchanges when a choice is available. Additionally, a few typical application protocols, such as ALE and “Custom Delivery” are provided by the integration engine only, and may be selected for use in non-migrated configurations.

Application exchanges managed by the trading engine

The B2Bi trading engine supports the following protocols for exchanges with applications:

  • FTP
  • SFTP
  • File system
  • File system with message data (deliveries only)
  • JMS
  • IBM MQSeries
  • MLLP
  • Web Services API client
  • Web Services (HTTP)
  • PeSIT
  • Pluggable server

Application exchanges managed by the integration engine

The B2Bi integration engine supports the following protocols for exchanges with applications:

  • Application Custom
  • Application ALE (delivery only)
  • Application email
  • Application FTP
  • Application file system
  • Application HTTP
  • Application HTTP server
  • Application MIME EMAIL (delivery only)
  • Application Sink

Manage B2Bi exchanges with applications

The following topics describe application pickups and deliveries, and how to manage them:

Exchanges with trading partners

You can configure B2Bi to exchange (send and consume) messages and files with trading partners located in both private and public networks. You set up community trading pickups in community objects, and partner trading deliveries in partner objects.

Trading partner exchange types

The B2Bi trading engine supports the following protocols and standards for exchanges with trading partners:

  • AS4 (web service)
  • cXML (HTTP)
  • ebXML (HTTP, SMTP)
  • ebXML intermediary (HTTP, SMTP)
  • EDINT AS1 (email)
  • EDINT AS2 (HTTP)
  • EDINT AS3 (FTP, SFTP)
  • Generic email (SMTP/POP)
  • MLLP
  • No packaging (FTP, SFTP, File system, JMS IBM MQSeries, , WebDAV,)
  • Odette FTP V1
  • Odette FTP V2
  • PeSIT
  • PGP (FTP, SFTP, email)
  • RosettaNet 1.1 (HTTP)
  • RosettaNet 2.0 (HTTP)
  • Secure file (HTTP, FTP, SFTP, file system, JMS, IBM MQSeries, WebDAV)
  • Web Services (HTTP)
  • X.420
  • X.435

Manage B2Bi exchanges with trading partners

The following topics describe community trading pickups and partner trading deliveries, and how to manage them:

Additional information for working with protocols and standards in B2Bi

The following topics provide additional information about how to manage specific protocols and standards in B2Bi:

Partner self-registration

AS4

ebXML

Email client partners

eSubmissions support

FTP client scripting interface

FTP scripts for B2Bi application exchanges

HTTP outbound proxy

HTTP security solutions

HTTP connection troubleshooting

Java Transformation Language

MLLP

OFTP

PeSIT

PGP secure trading

RosettaNet

Secure file message protocol

Web Services

WebSphere MQ configuration

WebSphere MQ multiple instances

X.400

XSLT

Related Links