Upload and Download Example - Sterling Connect:Direct as PNODE Initiates a Transfer FROM Sterling B2B Integrator

In this example, the PNODE is a Sterling Connect:Direct® Server named CD.CHICAGO. The SNODE is a Sterling Connect:Direct Server Adapter named CDSA.DALLAS.

The Sterling Connect:Direct process contains the following:

FROM GIS PROCESS
        SNODE=CDSA.DALLAS
        SNODEID=(cduser1,cduser1)
STEP1 COPY
        FROM (
                FILE=”po-12558-a202”
                SNODE
       )
        TO (
                FILE=”payload.txt”
                PNODE
                DISP=RPL
       )
PEND

The cdinterop-user-properties file contains the following entries:

cduser1 [CDSA.DALLAS] upload=/mailbox/out
cduser1 [CDSA.DALLAS] download=/mailbox/in
admin [CDSA.DALLAS] upload=/mailbox/upload
admin [CDSA.DALLAS] download=/mailbox/download

The Connect:Direct Server Adapter computes the source filename by appending the local filename po-12558-a202 to the cduser1 [CDSA.DALLAS] upload parameter value:

Result: /mailbox/out/po-122558-a202

The Sterling Connect:Direct User Authorities for cduser1 contains the following Directory Restrictions:

Directory Restriction  
Upload C:\Connect Direct\data\upload
Download C:\Connect Direct\data\download

Sterling Connect:Direct computes the destination filename by appending the local filename payload.txt to user cduser1's download parameter value:

Result: C:\Connect Direct\data\download\payload.txt