An AS2 receiver is a configurable endpoint for receiving
data from a trading partner. The AS2 receiver is a bridge between
the transport protocol (HTTP or HTTPS) and B2B Advanced Communications.
Before you begin
You also can import a server configuration
as a resource from another installation of B2B Advanced Communications.
For more information, see ../com.ibm.help.meg.reference.doc/meg_resource_commands.html.
You
must configure an HTTP or HTTPS server and a thread pool before configuring
an AS2 receiver.
About this task
You must
create an AS2 receiver to receive messages from a trading partner.
Depending on your requirements, you can create multiple AS2 receivers
for a single trading partner or use a single AS2 receiver for multiple
trading partners.
Restriction: If you
receive the high watermark event, BCXCH111W, which indicates high grid memory,
active AS2 receivers immediately cease to accept any incoming messages for processing. The
associated HTTP server is quiesced so that messages that are already accepted can be processed. Only
after the memory clears and falls below the low watermark, can the AS2 receiver accept new
messages.
Procedure
- Click Systems Management and select Receivers.
- On the Receivers page, click New and
select AS2.
- In the New Receiver dialog box, specify
settings for the following fields:
| Field |
Description |
Name
|
Type a unique name for the AS2 receiver.
|
Description
|
Optional: Type a description for the AS2
receiver.
|
AS2 service URI
|
Type the AS2 service URI. An HTTP or HTTPS
server identifies an AS2 receiver by the service URI of the receiver.
The
AS2 service URI must start with a forward slash, followed by the address
or path. For example, /test-uri. The AS2 service URI is unique for
each AS2 receiver. You must have unique URI for SSL and non-SSL connections.
|
Messaging destination
|
Associate a messaging destination with the
AS2 receiver.
The messaging destination is used for processing
asynchronous MDN.
B2B Advanced Communications sends
the received and processed AS2 message (business document object,
payloads, and attachments).
|
Host server
|
Select a host server (HTTP or HTTPS server)
on which you want the AS2 receiver to be available.
When a host
server receives a message, it checks the AS2 service URI and routes
the message to the specified AS2 receiver.
The unique resource
locator (URL) format for the AS2 receiver must be in the following
format: http://<hostname/IP of the server machine>:<http
sever port created from UI>/<AS2 Receiver URI created from UI>
For
example, if the port number of the HTTP (or HTTPS) server that you
associated with the AS2 receiver is 63000, and the URI of the
AS2 receiver is /test-uri, then the URL of the AS2 receiver
must be http://hostname:63000/test-uri.
|
Payload threshold size
|
Optional: Specify data storage options for
the payload.
If the size of the payload exceeds the threshold
size, the payload is stored in storage and a reference to the payload
is provided in the message.
If the size of the payload is equal
to or less than the threshold size, the payload is transferred inline
with the message.
|
Thread pool
|
Optional: Specify data storage options for
the payload.
If the size of the payload exceeds the threshold
size, the payload is stored in storage and a reference to the payload
is provided in the message.
If the size of the payload is equal
to or less than the threshold size, the payload is transferred inline
with the message.
|
- Click Save to save the AS2 receiver
configuration. The AS2 receiver is automatically started when you
save the configuration.