HomeGuides
Log In
Guides

Client Connection: PESIT

Suggest Edits

Fields with the asterisk * are mandatory.

PropertiesDescription
NAME *Name of the PESIT connection you are creating. The maximum number of characters is 128. Blanks and these special characters: ' " | are not supported.
DESCRIPTIONDescription of the PESIT connection you are creating. The maximum number of characters is 2048.
STATUS Enable or disable the client connection. Possible values:

  • Enabled (default value)
  • Disabled
    • HOST * Remote host IP Address or hostname.
    PORT * Port to connect to the remote host (1 to 65535).
    USERNAME *Username to be used for the connection. The maximum number of characters is 320.
    PASSWORD User password.
    CONNECT THROUGH DMZEnable or disable DMZ proxy. Possible values:

  • Enabled
  • Disabled (default value)
    • PESIT REMOTE NODE IDENTIFIERRemote identifier of PESIT. Logical identifier that is submitted to Data One. If an ID different from the ID contained in this field is submitted, the connection fails. The maximum number of characters is 24. Blanks are not supported. Special characters allowed: - _ .
    PESIT LOCAL NODE IDENTIFIERLocal Identifier of PESIT. Logical identifier that Data One submits to connect. If an ID different from the ID contained in this field is submitted, the connection fails.
    The maximum number of characters is 24. Blanks are not supported. Special characters allowed: - _ .
    INTERVAL BETWEEN SYNC POINTSNumber of synchronization points in Kb used to restart a transfer after an incident. Default number: 1024. The value of this field must always be greater or equal to 4.
    ACKNOWLEDGEMENT WINDOW SIZEAcknowledgement window size. This is the number of synchronization points without answer that can be sent before the transfer is stopped. Default number: 3.
    MAX RETRIESMaximum number of retries. If this field is empty or set to 0, no retries will be executed and the job will be set to Failed if the first attempt is not successful. A high value corresponds to a high number of retrying attempts.
    RETRY INTERVALThis field will appear only if you have set the maximum numbers of retries to 1 or greater.
    Time (in seconds) waited before retrying executing a job. The lower the value, the more frequent the retrying attempts. If this field is empty or set to 0, no retries will be executed and the job will be set to Failed if the first attempt is not successful.

    PESIT Protocol Configuration

    To set up a PeSIT configuration, define the following entities:

    • a VFS
    • a Remote Actor with a User
    • a remote connection to a Remote PeSIT node
    • a Server template with PeSIT protocol

    In the Actors section, click the New button and create Partner PXFB01.
    Click the New User button and create User USR99:

    1755

    Go to the VFS tab and click the NEW button to define a VFS for Partner PXFB01:

    Go to Setup → STENG, Clusters & Servers and define a new PeSIT remote Server to connect to/be connected from.
    Click the NEW SERVER button and define connection parameters to the remote PeSIT Node XFB01:

    ParametersValue
    PROTOCOL TYPEPeSIT
    SERVER NAMEPXFB01_PROTOCOL
    DESCRIPTIONRemote Access Config Pesit x XFB01
    ENABLEDYes
    DMZ PROXY ENABLEDNo
    REMOTE HOSTIP of the remote Host
    REMOTE PORTPort of remote Host
    USERNAMEUsername to establish the connection
    REMOTE IDXFB-01
    LOCAL IDSPENTC12

    Warning!

    Do not set a password to connect to the XFB-01 remote PeSIT node. The parameters not mentioned can be omitted.

    Now define the PeSIT Server Template, with the following parameters:

    Server configuration:

    ParametersValue
    PROTOCOL TYPEPeSIT
    TEMPLATE NAMEPESIT01
    DESCRIPTIONPeSIT local server
    ENABLEDYes
    DEFAULT LISTENING PORT51600
    DIAGNOSTIC PORT 151601
    DIAGNOSTIC PORT 251602
    MAXIMUM PDU SIZE30000

    The PESIT server is now installed in the STENG folder. Note that if the path of this folder is longer than 52 characters, the PESIT server cannot be run, and an error appears in the
    messages.log.
    To solve this issue, you must create a Symbolic Link (SymLink) and edit the server.env file as shown in the example here below:
    Steng folder = /home/user1/installation/ghibli-home/wlp/usr/servers/steng

    Information available in the server.env installation file:
    KEYMXMS=PRIMPESI-AA7BB8O483
    OSIVERS=3.6B.01
    OSIROOT=/home/user1/installation/ghibli-home/wlp/usr/servers/steng/pesit/SPRun/pesit

    Create the SymLink:
    Go toln -s /home/user1/installation/ghibli-home/wlp/usr/servers/steng /home/user1/PesitDeploy

    and modify the server.env file:
    KEYMXMS=PRIMPESI-AA7BB8O483
    OSIVERS=3.6B.01
    PESIT_DEPLOY_DIR==/home/user1/PesitDeploy
    OSIROOT=/home/user1/PesitDeploy/pesit/SPRun/pesit

    Incoming call:

    ParametersValue
    NAMEIc_pesit01
    DESCRIPTIONIncoming call x XFB-01
    INCOMING ADDRESS0.0.0.0
    ACTORPXFB01

    Allocate the Server Template to a cluster.

    Warning!

    Use 0.0.0.0 as IP for local PeSIT to expose the right listening server port.

    The configuration is now completed.

    Updated 5 months ago