Partners¶
Partners in django-pyas2
mean all your trading partners with whom you will exchanges messages, i.e. they are the receivers
when you send messages and the senders when you receive messages. Partners can be managed from the Django Admin.
The admin lists the existing partners and also you gives the option to search them and create new ones. Each
partner is characterized by the following fields:
General Settings¶
Field Name |
Description |
Mandatory |
---|---|---|
|
The descriptive name of the partner. |
Yes |
|
The as2 identifies for this partner as communicated by the partner. |
Yes |
|
The email address for the partner. |
No |
|
The HTTP/S endpoint of the partner to which files need to be posted. |
Yes |
|
The MIME subject header to be sent along with the file. |
Yes |
|
The content type of the message being transmitted, can be XML, X12 or EDIFACT. |
Yes |
|
Use this field to customize the confirmation message sent in MDNs to partners. |
No |
HTTP Authentication¶
Use these settings if basic authentication has been enabled for the partners AS2 server.
Field Name |
Description |
Mandatory |
---|---|---|
|
Check this option to enable basic AUTH. |
No |
|
User name to access the partners server. |
No |
|
Password to access the partners server. |
No |
Security Settings¶
Field Name |
Description |
Mandatory |
---|---|---|
|
Check this option to enable AS2 message compression. |
No |
|
Select the algorithm to be used for encrypting messages, defaults to None. |
No |
|
Select the |
No |
|
Select the hash algorithm to be used for signing messages, defaults to None. incoming messages from trading partners. |
No |
|
The |
No |
MDN Settings¶
Field Name |
Description |
Mandatory |
---|---|---|
|
Check this option to request MDN for outbound messages to this partner. |
Yes |
|
Select the MDN mode, defaults to Synchronous |
No |
|
Select the algorithm to be used in case signed MDN is to be returned. |
No |
Advanced Settings¶
Field Name |
Description |
Mandatory |
---|---|---|
|
Use Original File name to to store file on receipt, use this option only if you are sure partner sends unique names. |
No |
|
OS Command executed after successful message send,
replacements are |
No |
|
OS Command executed after successful message receipt,
replacements are |
No |