Tutorial - Creating a PeSIT Partner
In this tutorial, you will:
Configure a remote PeSIT partner.
View the configuration in effect during a file transfer with a corresponding UDMG local PeSIT server, see Tutorial - Creating a PeSIT Server.
Step 1 | From the UDMG navigation pane, select Management > Partners. The Partner list displays. |
---|---|
Step 2 | Click New. The Partner Details displays.
|
Step 3 | Click the Configuration tab on the Partner detail panel
|
Step 4 | Click Save and Confirm. |
Step 5 | Click the Accounts tab on the Partner detail panel. Add an account. It is required to define at least 1 account for a PeSIT partner, for the registration of the file transfer request. The authentication on the PeSIT server is performed with the parameters (Pre Connect, caller ID, Server ID, Access Control that are defined on the configuration tab.
|
Step 6 | Click Save |
Step 7 | Configure the rules at partner and/or account level. For example pesit-01_partner_send Create the rule:
Please note that, because the remote partner is set to be local UDMG PeSIT server, the Remote Directory is set to the virtual path of a receiving rule for the local server: |
Step 8 | Click the Save icon |
Step 9 | Authorize the sending rule for the partner: |
Step 10 | Initiate a file transfer to upload a file. The file is ready under Use the Command Line Interface to register the transfer:
|
Step 11 | Follow the transfer request from the Activity Transfer and History dashboards. There are 2 records in this case, because UDMG is used both as the client and the server in the transaction:
|
Note
According to the protocol specification, the following constraints are checked when setting the configuration parameters:
Pre Connect Username is mandatory and must be less than 9 characters
Pre Connect Password is mandatory and must be less than 9 characters
Caller ID (PI3) field is mandatory and must be less than 25 characters
Partner ID (PI3) field is mandatory and must be less than 25 characters
- Data Element Max Size (PI25) is mandatory and must > 0
Access Control (PI5) is optional and must be less than 17 characters
- Article Length (PI32) is mandatory and must > 0
An error "the protocol configuration is invalid" is raised if one of these values is not correct.