Guide for installation and use of Sterling Commerce Command Line Client (CLC) in Unix Operating System

Guide for installation and use of Sterling Commerce Command Line Client (CLC) in Unix Operating System Page 1 of 29

Table of contents Changes made in this version : PBS A/S has changed its name to Nets Danmark A/S (Nets is a result of the merge between PBS and the Norwegian BBS). Nets has implemented a new server, which already now can be reached. The old IP-adress 194.239.133.111 is planned to be inactivated in the beginning of february 2011. Introduction... 4 Content... 4 Preparations before installation... 4 Rights... 4 Limitations... 4 Installation guide... 5 Download installation files from the Internet... 5 Change file extension CLC.pbs to CLC.exe... 6 Start installation... 7 Updates for the current software version... 12 Use of CLC... 13 Requirements for using CLC... 13 Your key... 13 Server's public keys... 13 CLC files... 13 cesshsftp... 13 Return codes... 14 sshclc.properties... 15 sshlog.properties... 15 autoscript_file... 15 <install>/.ssh/known_hosts... 15 Development and use of SFTP commands... 16 Limitations in use... 16 Term explanation... 17 Wildcard syntax... 18 Naming of files from PBS... 18 SFTP commands... 20 Introduction... 20 List... 20 Syntax descriptions... 21 dir or ls... 21 put... 21 mput... 21 get... 21 mget... 22 rm or delete... 22 quit or bye... 23 Example of a set up for automatic file exchange... 24 Introduction... 24 Important information... 24 Example... 24 Page 2 of 29

Detailed description... 25 Example... 25 Detailed description... 25 Example... 26 Detailed description... 26 Manual logon... 27 First time... 27 Subsequent manual logon... 27 Support... 29 Contact information... 29 Business hours... 29 Page 3 of 29

Introduction Content Preparations before installation Rights This guide is for users who want to use Sterling Commerce's Command Line Client (CLC) in UNIX, Linux and AIX computers that will be used for exchanging data with Nets via the SFTP protocol. The guide describes how the CLC software can be downloaded and then be used for controlling data communication with Nets. Please read the entire guide before starting the installation. CLC can always be uninstalled and re-installed without problems. You must make sure you have installed Winzip. You must make sure that Java ver. 1.3 (or newer version) has been installed. Contact your system administrator, if necessary. All rights to this guide and communication solution belongs to Nets. You may not copy, forward or in any other way make the material of parts thereof available to a third party without permission from Nets. Limitations The following platforms are supported by CLC: UNIX, Linux, AIX, HP-UX and SUN Solaris. Page 4 of 29

Installation guide Download installation files from the Internet To be able to install CLC you need to download the zipped file clcnix.pbs. It is assumed that the download will take place from a Windows computer. Log on to the Web site www.pbs.dk. Select Data Communication and you will find the software to be downloaded. Choose "CLC installation program for Unix (23.3 MB)" The following screen will be displayed: Click Gem to save the file on your PC. Choose the folder on your PC where you want the file to be located and then press Gem. When the file has been transferred, the following screen will be displayed. Page 5 of 29

Change file extension CLC.pbs to CLC.exe Before you can run the installation of the program the file "clcnix.pbs" must be unpacked and moved to the computer where the program will be run. The file is unpacked by pressing Åbn mappe, which causes you to open an explorer. If the above dialog box is closed automatically you can rename the file in the following way: Choose "Stifinder", which can be done by right-clicking on "Start" and choosing "Stifinder". Choose the folder where you saved the file "clcnix.pbs" by left-clicking on the folder. The file "clcnix.pbs" is now displayed. Right-click on the file and choose "Omdøb". Now edit the file name to be "clcnix.exe" by typing this file name over the old file name. You unpack the file by clicking on it and choosing where it will be located on your Windows computer. Then it must be moved to the Unix computer where the program will run. There are several methods to do this and you must contact your system administrator to find out how you move files between Windows and Unix. When the files have been moved you are ready to begin the installation. Page 6 of 29

Start installation The following is an example of an installation of CLC on an AIX system: ceunix@ttelesrv1:/ceunix/clc:./cesftp_inst ============================================== Sterling Commerce, Inc.,(TM) Connect:Enterprise Command Line Client (Secure FTP) Installation Procedure: You are beginning the Connect:Enterprise Command Line Client (Secure FTP) Installation Procedure. You will be asked to specify a directory (called the destination directory) where the Connect:Enterprise Command Line Client (Secure FTP) files are stored. Sterling Commerce, Inc.(TM) and Connect:Enterprise(TM) are trademarks of Sterling Commerce, Inc. in the U.S.A. and other countries. UNIX is a trademark of UNIX Systems Laboratories, Inc. ============================================== Press ENTER to continue: Enter the path where the CD-ROM drive is mounted (e.g. /cdrom or '.'):. Enter the destination directory path where the Connect:Enterprise Command Line Client (Secure FTP) is to be installed [$HOME/clcftp]: /ceunix/clc/clcftp You have selected /ceunix/clc/clcftp for installation. Do you want to continue?:[y n] clc_us_license.txt Page 7 of 29

clc_int_license.txt 7406 blocks Please specify whether you are a U.S.(domestic) or International user. Type "US" if you are located within the U.S. Type "INT" if you are located outside of the U.S.: Enter [US or INT]: INT Connect:Enterprise Command Line Client (Secure FTP) Carefully read all of the terms and conditions of this Agreement prior to opening or installing the Product. Sterling Commerce B.V, Sterling Commerce International, Inc. or any of its affiliated Sterling Commerce entities or such third party to whom either entity has granted certain marketing, redistribution or sublicensing rights ("Provider") will grant a right of use for the enclosed Connect:Enterprise Command Line Client and related documentation (the "Product") to You only on the condition that You accept all of the terms and conditions of this Agreement. USE OF THE PRODUCT INDICATES YOUR ACCEPTANCE OF THE TERMS AND CONDITIONS OF THIS AGREEMENT. You understand that by selecting the "ACCEPT" option at the bottom of this Agreement that You are agreeing to the terms of this Agreement. If You do not agree with the terms and conditions of this Agreement, You should select the "DECLINE" option at the bottom of this Agreement that will allow You to exit and terminate this transaction. Upon exiting, You should promptly return the Product to Your Provider. Upon return of the Product, this Agreement shall terminate. If applicable, Your Provider shall be solely responsible for refunding to You any applicable fees paid by You for the terminated Product. USE OF THE PRODUCT INDICATES YOUR ACCEPTANCE OF THE TERMS AND CONDITIONS OF THIS AGREEMENT. 1. Grant Of Right of Use. Provider hereby grants to You a nonexclusive and nontransferable right of use to use a single copy of the object code version of the Product under the terms and conditions of this Agreement. You may use this copy of the Product on a single compatible computer located within Your country in which it is originally located. Your right to use the Product is limited to Your transmittal of data solely to and from your Provider. The Product is not to be used for any other purpose, including but not limited to, the processing of data of any third parties or in connection with the operation of a service bureau. Except for a copy to be used for backup purposes, You may not copy or distribute the Product in whole or in part. You may not alter, modify, decompile, disassemble or reverse engineer the Product or apply any process or technique to the Product for the purposes of ascertaining the source code. 2. Title, Confidentiality. You acknowledge that this is an agreement for right of use and not an agreement for sale. Provider and/or its licensor ("Licensor") continue to own the copy of the Product for which a right of use is granted hereunder. You further acknowledge that title and all trade secrets, copyright, patent rights, trademarks, and other intellectual property rights in and to the shall remain with Provider and/or its Licensor. You may not disclose, or transfer the Product to any party. Your rights under this Agreement not be assigned, sublicensed, pledged, or otherwise transferred. You may not alter, remove or conceal any copyright, trade secret, or other proprietary rights notices that may appear on or Page 8 of 29

within the Product. You must reproduce all proprietary rights notices on any copies of the Product which are allowed under this Agreement. 3. Term. The right of use is effective until terminated. Termination of the right of use shall occur if: (i) You fail to comply with any term or condition of this Agreement; (ii) You cease to transmit data to and from the Provider for any reason, (iii) You elect to terminate the right of use for any reason, or (iv)you or Your Provider is in breach. Upon termination, You agree to destroy all copies of the Product, including backup copies. Section 2 shall survive termination of this Agreement for any reason. 4. Maintenance Support. Maintenance support for this copy of the Product may be offered by the Provider, at its sole discretion. You should direct any questions to Your Provider regarding whether or not maintenance support is being offered for the Product and, if applicable, the terms of maintenance support. 5. "As Is" Warranty. YOU UNDERSTAND AND AGREE THAT PROVIDER GRANTS THIS RIGHT OF USE FOR THIS PRODUCT "AS IS" AND NEITHER PROVIDER OR ITS LICENSOR(S) MAKES ANY WARRANTY, REPRESENTATION OR PROMISE OF ANY KIND. PROVIDER AND ITS LICENSOR(S) DISCLAIM AND EXCLUDE ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. NEITHER PROVIDER NOR ITS LICENSOR(S) WARRANT THAT THE PRODUCT WILL SATISFY YOUR REQUIREMENTS OR THAT THE PRODUCT IS WITHOUT DEFECT OR ERROR OR THAT THE OPERATION OF THE PRODUCT WILL BE UNINTERRUPTED. 6. Limitations of Remedies. YOU ACKNOWLEDGE AND AGREE THAT IN NO EVENT SHALL PROVIDER OR ITS LICENSOR(S) BE LIABLE TO YOU OR ANY OTHER PARTY FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL OR SIMILAR DAMAGES OR FOR LOST DATA OR PROFITS RESULTING IN ANY WAY FROM THE USE OR POSSESSION OF THE PRODUCT. 7. General. This Agreement shall be governed by the laws of Your country in which the Product is originally located and is the complete and exclusive statement of the agreement between You and Your Provider. This Agreement supersedes any proposal or prior agreement, oral or written, and any other communications between You and Your Provider relating to the subject matter herein. 8. Export Restrictions. You acknowledge that the Product is subject to United export controls under applicable export control regulations, including without limitation, the United States Export Administration Regulations. The Product, and underlying information and technology, may not be downloaded or exported or re-exported. Do you accept the above license agreement?:[y n] y Installing Connect:Enterprise Command Line Client (Secure FTP) Page 9 of 29

... Extracting Command Line Client Base components. PwdTerm.so cesftp.jar cesshsftp.jar ceuftpcust java_check sample_secureftp.cfg sshclc.properties sshlog.properties trusted.txt Readme.txt commons-logging.license EccpressoAll.jar SterlingUtil.jar TrustpointAll.jar TrustpointProviders.jar commons-logging.jar jce-jdk13-119.jar scisecurelib.jar scisecurelib_props.jar sslplus_jsse.jar 7406 blocks... Done. Verifying Command Line Client Base components are extracted.... Done. Do you want to setup the Java environment for the Connect:Enterprise Command Line Client (Secure FTP)?:[Y n] y ============================================== Sterling Commerce, Inc.,(TM) Connect:Enterprise Command Line Client (Secure FTP) Customization. To abort the process, enter Control-C. ============================================== Page 10 of 29

Please press ENTER to continue... Searching for Java... ******************************************************** Select the appropriate Java interpreter program. Contact your System Administrator if you are unsure about the appropriate selection. ******************************************************** 0 = User enters the absolute path to Java. 1 = version 1.3.1 at /usr/java130/bin/java 2 = version 1.3.1 at /usr/java130/jre/bin/java 3 = version 1.3.1 at /usr/java131/bin/java 4 = version 1.3.1 at /usr/java131/jre/bin/java 5 = version 1.4.1 at /usr/java14/bin/java 6 = version 1.4.1 at /usr/java14/jre/bin/java 7 = version 1.4.2 at /usr/java14/.private142/bin/java 8 = version 1.4.2 at /usr/java14/.private142/jre/bin/java Select [0-8]: 4 Creating /ceunix/clc/clcftp/secureftp.cfg Creating /ceunix/clc/clcftp/ceftp Creating /ceunix/clc/clcftp/cesshsftp Creating /ceunix/clc/clcftp/ssh-keygen.sh ============================================== The script files ceftp, cesshsftp and ssh-keygen.sh have been created. To bring up the Connect:Enterprise Command Line Client (Secure FTP), type ceftp or cesshsftp from the installation destination directory. ============================================== Building license.install file Connect:Enterprise Command Line Client (Secure FTP) installation has completed. Page 11 of 29

Updates for the current software version There may be updates available for the software you have just installed. You can control this on our web site www.pbs.dk. Current updates (if any) are shown. Just download the zip file containing the updates and install them into the library, where your CLC client has been installed. Page 12 of 29

Use of CLC Requirements for using CLC The following must be in place before you can use CLC: You must have receive a User ID (name of your mailbox) and an associated password You must have retrieved your key and placed it correctly You must be able to remember the pass phrase you used when generating your private key You must have the server's public key You must know the IP address for the server, which is 92.60.159.16 You must know the port, which is 10022 You must have opened your firewall to the combination of IP address 92.60.159.16 and port 10022 Your key Retrieval of key occurs via the Web page https://ft.pbs.dk/key by using your chip card, the associated User ID and password. (If necessary, see "User guide for key generation"). You can place your key wherever you wish, but please see the section "The private key" in the user guide named above where security issues surrounding storage of the key are described. Server's public keys CLC files cesshsftp You must have the server's public keys in the file with "known hosts". The best way to place it in the correct place is to manually start a session with the server from your computer. You will be prompted to save the server's public keys. By answering "always" the key will be saved correctly. This is described in more detail in the section about manual logon. After installation of CLC there will be a number of files in the directory that was chosen as the installation directory. In the following sections this will be referred to as <install>. In the example <install> is set to /ceunix/clc/clcftp. The following files are the most important: <install>.\cesshsftp the SFTP client program itself <install>.\sshclc.properties contains ssh parameters <install>\ sshlog.properties contains parameters to control logging <install>.\autoscript_file contains parameters and commands <install>\.ssh\known_hosts contains the public key from the host(s) that are being used to exchange files It must be emphasised that several of the files may be located in places other than <install> because they can be directly referred to via the parameters and configuration files. The program can be used together with a number of parameters: cesshsftp [-a autoscript_file] [-s propertyfile] [-d 0 1 2 3 [debug_file]] [-r] [-x] [-h] [-L key_file] [-P passphrase] Page 13 of 29

-a autoscript Specifies the location and file name of the automation script file. Refer to Writing Automation under autoscript_file -s propertyfile Indicates to override the default property file (sshclc.properties) with propertyfile. -d newloglevel Indicate newloglevel to override the default log level. Valid values are: 0 = No logging. 1 = General information. 2 = Debug information. 3 = Trace information. debugfile Indicate newlogfilename to override the default log file. -h Returns the command line syntax -L newkeyfile Indicates to override the default public authentication key file with newkeyfile. If you use this parameter, you can use the -P parameter to specify the passphrase. If you do not include the -P parameter in the command, you will be prompted for the passphrase. -P passphrase Specifies the passphrase associated with the newkeyfile specified with the -L parameter. -r Returns the product name, release, and build. -x Turns on result code exiting for the entire instance of the client. Used with automation scripts to exit if a command fails. Return codes Using the parameter x, the CLC delivers a return code after completion. The return codes are : 15 SSH key failed 14 ssh scripting failure 13 SSH command failure 12 SSH Disconnect 11 SSH TIMEOUT 10 Catatrophic failure 9 Reserved 8 Locsite parameter invalid 7 Command line parameter invalid 6 SSL file parameter invalid 5 get subcommand failed 4 put subcommand failed 3 Command failed 2 Authetication/login failure 1 Connection establishment failure 0 Good return code Page 14 of 29

sshclc.properties sshlog.properties autoscript_file <install>/.ssh/kno wn_hosts An example of property file is displayed here: # Sample ResourceBundle properties file #sockettimeout time=seconds, 1800=30 minutes sockettimeout=1800 compression=yes passwordauth=no publickeyauth=yes #cipherlist=3des-cbc,blowfish-cbc,aes256-cbc,aes192-cbc,aes128- cbc,cast128-cbc #maclist=hmac-sha1,hmac-md5-96,hmac-md5,hmac-sha1-96 keyfile=c:/<path for the file containing the key id_dsa>/newkey knownhostkeyfile=myknown_host An example of log-property is displayed here: ############################################## # Default Logging Configuration File ############################################## # Handler specific properties. # Describes specific configuration info for Handlers. ############################################## # default file output is in user's runtime directory. # Limit the message that are printed on the console to INFO and above. # the valid values are TRACE,DEBUG,INFO,WARN,ERROR,FATAL # the writelogfile value=true will write to log file com.sterlingcommerce.sshclc.sftplogger.defaultlog = INFO com.sterlingcommerce.sshclc.sftplogger.writelogfile = true Example of an autoscript file: ############################################## open <ip adresse> 10022 <mailboksid> c:\<path for the file containing the key id_dsa\id_dsa <passphrase> put filer\testfil3_8.mby dir quit ############################################## id_dsa is a reference to the user's key retrieved from Nets' Web site. Contains public keys for the hosts that have been contacted and always responded. You can also add keys manually, e.g. keys that have been downloaded. Page 15 of 29

Development and use of SFTP commands Limitations in use Important: You must always use a binary transfer for transmission of data to Nets. The data files you send to your mailbox at Nets must always have the same code page because your mailbox has been predefined for one of the code pages Nets supports. Guides and software from other software suppliers may contain SFTP commands other than those that have been specified in this guide. Nets is not obligated to support such commands or guarantee that they will work correctly when used for this SFTP solution. Page 16 of 29

Term explanation In the chart below you will find explanations of the terms that are used in this document. Term Explanation Marking SFTP command The commands the Nets supports in this solution bold Variable The possible variable parameters you can use in your command strings. See the Wildcard syntax section <wildcard> Server_id Address of the Nets SFTP server that can either be a Web address, e.g. ft.pbs.dk, if it is possible to create a name reference with the customer in italics id_dsa The private key when you receive it from Nets Bold 10022 The SFTP port on Nets s SFTP server No marking cesshsftp Client prompt in the software that is delivered from Nets. This will vary if you use other client software No marking -C SFTP parameter that activates compression of data No marking -b <path>whatever_script> SFTP parameter that executes a batch job The content of the batch job is described in whateverscript. No marking -oport= SFTP syntax for definition of port number on Nets s SFTP server. No marking MAILBXID The userid you received from Nets No marking @ Divider between userid and server name No marking Userid Your local UNIX/Linux user Bold passphrase What you typed in when you generated your key No marking Page 17 of 29

Wildcard syntax The chart below displays the supported syntax for use of wildcards Wildcard character Effect? The search with? entails selection of all occurrences. For example, a search with a wildcard 2? will entail selection of 22, 29 or 2a. * Search with * will entail selection of all occurrences regardless of the value in * and subsequent characters. For example, a search with a wildcard 2* will entail selection of 2, 23 or 23aa. [ ] This search entails selection of all occurrences that match what has been specified as a value within the two brackets. For example, the search [2*3] will select 23, 24563 and 233. Similarly, the search [b-k,p] will select all occurrences with values between b and k, as well as p. The search criterion [abc]* selects all occurrences starting with a, b or c. Naming of files from Nets Nets has used the naming convention below for data files that are delivered to you. This naming standard makes it possible to select special file types in building your scripts for retrieving files. Files that begin with T are transmission receipts. This allows you to see if the delivery has been received correctly on the Nets server. Files that begin with V are validation receipts. Here you can see if your data delivery has been accepted by the Nets system that will process it. Files that begin with D are files to you from a Nets system in unzipped format. Files that begin with Z are files to you from a Nets system in zipped format. To receive files in zipped format your mailbox must be set up for this. Note that, as a rule, there is no purpose in using this facility when you are using SFTP. Files that begin with F are delivery notes that certain Nets systems form together with D files. Page 18 of 29

Page 19 of 29

SFTP commands Introduction This section describes the SFTP commands that can be used in the SFTP solution. It is important to adhere to the described syntax rules to ensure correct data exchange with Nets. The examples assume that a command line client has been used but the commands can also be coded into a script for automatic execution. List The table below displays the supported SFTP commands and their meaning Command Meaning dir or ls Displays a list of your files in your mailbox at Nets put Sends a file to your mailbox at Nets (see note) mput Sends several files to your mailbox at Nets (see note) get Retrieves a file from you mailbox at Nets mget Retrieves several files from your mailbox at Nets rm or del Deletes a file from your mailbox at Nets quit or bye Logs you off from the SFTP server at Nets Page 20 of 29

Syntax descriptions dir or ls Syntax: dir or ls When this command is issued, a list of the files that are in your mailbox at Nets are delivered. The list you receive contains only files that are available to be downloaded to your computer. The files you have sent yourself to the mailbox will therefore NOT be displayed. put Syntax: put<path><filnavn> When this command is issued you can send one file at a time to your mailbox at Nets. <filnavn> is the name of the file that must be sent to your mailbox at Nets. <path> is the location of <filnavn> on your computer, for example for Windows: c:\nets-upload\ mput Syntax: mput<path><wildcard> When this command is issued you can send several files at a time to your mailbox at Nets. <wildcard> is selection criteria for files found in <path>, for example C:\nets-upload\netsdata.* get Syntax: GET <filnavn> <path><nytfilnavn> When this command is issued you can retrieve one file at a time from your mailbox at Nets. <filnavn> is the name of the file in your mailbox at Nets. <path> is the name of the directory on your computer where you wish to save the file. If you do not specify <path>, the file will be placed in the directory that is active. <nytfilnavn> is the name you want to give the file when it is stored on your computer. If you do not specify anything in <nytfilnavn> the file will be saved with the same name that is specified in <filnavn>. If you do not specify any <nytfilnavn> you can not use the <path> parameter either. Page 21 of 29

mget Syntax: mget <wildcard> When this command is issued you can retrieve several files at a time from your mailbox at Nets. <wildcard> is the selection criteria among the files that are available in your mailbox at Nets. Example : mget D* or only mget* mget D* will copy all files from the mailbox that start with D and mget * will copy all files from the mailbox. No result list is given when executing the mget command. Because there is no option of specifying a file name or directory, the files will have the same name as in the mailbox at Nets and they will all be placed in the active directory on your computer. rm or delete Syntax: rm or delete <filnavn> or <wildcard> The commands give you the ability to delete files in your mailbox at Nets. <filnavn> is the name of the file in the mailbox that you wish to delete. When using the parameter <wildcard> it is possible to delete all files that meet the selection criteria in your wildcard parameter. Always use caution when using this command and consider the exact relevance of deleting files from your mailbox yourself. You can not delete files that you yourself have sent to the mailbox at Nets. You cannot delete files that you have already retrieved one time. - In other words, you can only delete files that Nets has generated for you and that you have not yet retrieved. If you delete files from Nets without having checked the content of the file, Nets's information obligation to you is no longer valid. Page 22 of 29

quit or bye Syntax: quit or bye These commands mean you can log off from the SFTP server at Nets. Page 23 of 29

Example of a set up for automatic file exchange Introduction In this section we provide an example of setting up automatic file exchange. The requirement for this script is that you have downloaded the Command Line Client, which you can retrieve at www.pbs.dk/itservices/datacommunication. The purpose of the script is to retrieve all available files in your mailbox at Nets. Important information To be able to execute scripts to the Nets server you need to have received its public key. The best way to have it delivered is to start your first session to Nets manually. The system will ask you to save the public key. If you answer "Always" to the question about the extent to which you accept the public key, the file "known-hosts" will be updated for you. To automatically perform data transmission, it is important that you answer "Always". See the "Manual logon" section. Example Put in crontab with the desired time interval: get.sh This must have the content: cesshsftp a getscript.txt -x The content in getcript.txt is open serverid 10022 MAILBXID <install>/key/id_dsa passphrase lcd c:\receive\library mget * quit Page 24 of 29

Detailed description In the script above, the cesshsftp command starts the sshftp command line client. This must always be installed on your computer equipment. (See "Guide for installation of Command Line Client for SFTP solution".) The parameter a specifies that a script file must always be used that automates logon to the Nets server. The parameter x specifies that cesshsftp must deliver return codes upon completion of the program. (Refer to chapter about Return codes) MAILBXID in the script "getscript.txt" must always be replaced by the mailbox ID you received from Nets. The path <install>/key/id_dsa must be replaced by the path that shows the location of the private key. The lcd command is changing the local library in the example above to c:\receive\library Example Put in crontab with the desired time interval: put.sh This must have the content: cesshsftp a putscript.txt. The content in getcript.txt is open serverid 10022 MAILBXID <install>/key/id_dsa passphrase lcd <install>pbs mput * quit Detailed description In the script above, the cesshsftp command starts the sshftp command line client. This must always be installed on your computer equipment. (See "Guide for installation of Command Line Client for SFTP solution".) The parameter a specifies that a script file must always be used that automates logon to the Nets server. MAILBXID in the script "putscript.txt" must always be replaced by the mailbox ID you received from Nets and passphrase must be replaced by the passphrase you entered when receiving your private key. The path <install>/key/id_dsa must be replaced by the path that shows Page 25 of 29

the location of the private key. <install>/pbs must be replaced with the path, where you have placed the data files you want to send to Nets. Example Create a shell script file e.g. ft.sh with the content as follows : #!/bin/sh # retc=0 #Set user return value to 0 (zero) #Invoke the C:E CLC with return code checking on (-x) #./cesshsftp -a askopi01.txt -x retc=$? echo "Returkoden was: "$retc #Check return code if [ $retc -gt 1 ]; then echo "File transfer ended with error" else echo "File transfer ended OK" fi exit $retc Detailed description In the example above, you want to run ft.sh to start cesshsftp using a script file with the parameter a and ending the cesshsftp with delivering and processing the return code. Remember to reset the return code by starting with the command retc=0. Upon completion of cesshsftp, the return code is checked for being equal to or greater than 1. If so an error message is displayed otherwise a good message is displayed. The script can off course be extended to react upon certain return codes e.g. deleting files or copying files to other libraries. Page 26 of 29

Manual logon First time The example below shows how you log on to Nets' SFTP server the first time with the command line interface you can receive from Nets. Text in bold is your entry <install>/./cesshsftp ============================================ Sterling Commerce, Inc.,(TM) Connect:Enterprise Command Line SSH SFTP Client ============================================ cesshsftp> Enter Host Name: server_id 10022 The host ft.pbs.dk is currently unknown to the system The host key fingerprint is: 2048 31:3d:18:0d:90:fe:20:f9:83:e9:3f:1f:90:78:e6:ef Do you want to allow this host key? [Yes No Always]: Always cesshsftp> Enter User Name: MAILBXID (replaced with your userid) cesshsftp> Subsequent manual logon The example below shows a subsequent manual logon. Text with fed is your entry <install>/./cesshsftp ===================================================== Sterling Commerce, Inc.,(TM) Connect:Enterprise Command Line SSH SFTP Client ===================================================== Page 27 of 29

cesshsftp> Enter Host Name: server_id 10022 cesshsftp> Enter User Name: MAILBXID (must be replaced with your user id/user) cesshsftp> Page 28 of 29

Support Contact information If you have problems with the installation you can contact Nets' technical service department ServiceDesk in the following ways: Telephone number: +44 89 73 73, press 3 E-mail address: servicedesk@pbs.dk Business hours Monday - Thursday 08.30 16.30 Friday 09.00 16.00 Page 29 of 29