You are on page 1of 37

Axway B2Bi Training

Basics
Message Exchange Part 2
Message Exchange Part 2 – Overview
Items Trading Engine and Integration Engine Transports

Embedded Servers

DMZ Nodes

Custom Transport Definitions (SDK)

© 2017 Axway | CONFIDENTIAL 2


Module Objectives
• After completing this module you will be familiar with a number of essential
Message Exchange concepts, including the functionality and configuration of
Transports, Embedded Servers, DMZ Nodes and the usage of custom transports
(aka Pluggable Transport / Pluggable server)

© 2017 Axway | CONFIDENTIAL 3


Transport
Definitions

© 2017 Axway | CONFIDENTIAL 4


Axway B2Bi Transports
B2Bi
Trading Engine

Integration
Engine

• B2Bi manages the separate communication and message processing


operations by providing two Message Processing modes:
• “Limited” mode: Communication processing (trading engine) only
• “Standard” mode: Message processing (trading engine and integration
engine)
5
Axway B2Bi Transports – Trading Pickups

• An overview of Trading pickup


protocols provided through the
Trading Engine The total
number of available protocols
is license based.

© 2017 Axway | CONFIDENTIAL 6


Axway B2Bi – Integration Engine Transports
B2Bi
Trading Engine

Applications

Integration
Engine

• To communicate with applications, B2Bi provides a number of additional base


transports directly from the Integration Engine – which supplement the protocols
provided by the Trading Engine. Some of them are provided for backwards
compatibility reasons
• Integration Engine transports always operate in Standard Mode

7
Axway B2Bi Transports – Application Pickups

Trading Engine • An overview of Application


Transports pickup protocols provided
through the Trading Engine and
the Integration Engine. The total
number of available protocols is
license based. Application
transports must be selected /
Integration Engine activated during installation or
adapt with ConfigureB2Bi script
Transports afterwards.

© 2017 Axway | CONFIDENTIAL 8


Axway B2Bi Transports – Application Deliveries

Trading Engine • An overview of Application


Transports delivery protocols provided
through the Trading Engine and
the Integration Engine. The total
number of available protocols is
license based. Application
transports must be selected /
Integration Engine activated at installation or
afterwards via configureB2Bi
Transports script.

© 2017 Axway | CONFIDENTIAL 9


Axway B2Bi Transports – Partner Deliveries

• An overview of the Partner


Delivery protocols provided
through the Trading Engine
The total number of available
protocols is license based.

© 2017 Axway | CONFIDENTIAL 10


Embedded
Servers

© 2017 Axway | CONFIDENTIAL 11


Embedded Servers – UI

12
Embedded Servers – SFTP

13
Embedded SFTP Server – Configuration Community side

14
Embedded SFTP Server – Configuration Partner side (Steps)

1
2

15
Embedded SFTP Server – Configuration Partner side (Delivery)

16
Embedded SFTP Server – Configuration Partner side
(Transport Users)

17
Secure Relay –
DMZ Node & Zone
Configuration

18
Secure Relay
• Secure Exchange messages via DMZ
• Port-forwarding service
• Master agent versus router agent in the DMZ.
• Secure connections between B2Bi and Secure relay.
• Bi-directional message traffic

© 2017 Axway | CONFIDENTIAL 19


Secure Relay - Multiple Node Example (Inbound)

20
Secure Relay - Multiple Node Example (Inbound)

21
Secure Relay - Multiple Node Example (Inbound)

22
Secure Relay – Create a new node

Specify the
internal IP of
the DMZ node

23
Secure Relay – Export and Start Agent

24
Secure Relay – What is a Zone
(security separation of different networks)
Zone / Internet

SR A

Internet
B2Bi SR B
Node X

Zone / VPN

B2Bi
Node Y SR C
Private Network
SR D

25
Secure Relay – Create a new zone and use in node

26
Port Forwarding
& Proxying for
outbound
connections
27
Secure Relay - Port Forwarding (1/4)

28
Secure Relay - Port Forwarding (2/4)

DMZ

B2Bi Secure
Node X Relay A
Port Port
xxxx 1443
Forwarding

29
Secure Relay - Port Forwarding (3/4)

30
Secure Relay - Port Forwarding (4/4)

31
Secure Relay – Outbound Proxy (1/2)

32
Secure Relay – Outbound Proxy (2/2)

33
Message Exchange
Pluggable Transport / Server
overview

#axway
Pluggable Transports
• Add your own protocol to B2Bi.

• A pluggable transport can be used to:


• integration between B2Bi and application using a third-party API.
• Exchange additional document metadata.
• proprietary mechanism implementation.
• Enable a file system transport that supports directory multiplexing for inbound
delivery
• just another transport option.

35
Pluggable Transports
• Pluggable transport framework.
• The three interfaces are:

• PluggableClient
• PluggableSettings
• PluggableMessage

• Exchanging messages with external servers.


• pluggabletransports.xml.

© 2017 Axway | CONFIDENTIAL 36


End of
Message Exchange Part 2
module

You might also like