User’s guide - TPS

1 TPS /NFM user s guide TPS Systems, Inc. 14100 San Pedro Avenue, suite 600 San Antonio, TX 78232-4399 (210) 496-1984 voice (210) 490-6805 fax Software Copyright 1999-2017 by TPS Systems, Inc. Manual Copyright 1999-2017 by TPS Systems, Inc. All rights reserved. International protection under the Berne Convention. TPS is a registered trademark owned by TPS Systems, Inc. Sun , Solaris and JAVA are registered trademarks of Sun Microsystems, Inc. UNIX is a registered trademark of UNIX System Laboratories, Inc. Linux is a registered trademark of Linus Torvalds. Windows, Windows 95, Windows NT, Internet Explorer are registered trademarks of Microsoft Corporation. HP-UX is a registered trademark of Hewlett-Packard Corporation. IBM, AIX, AS/400, and OS/390 are registered trademarks of International Business Machines Corporation. MVS, System/36 and System/370, and IBM 4690 OS Version 2 are trademarks of International Business Machines Corporation.

2 Stratus is a registered trademark of Stratus Technologies International, Android is a registered trademark of Google Inc. AWS is a registered trademark of Amazon Web Services, Inc. Software version Manual revised 06-13-17 Table of Contents 1: INTRODUCTION .. 1 3 3 SYSTEM 4 REQUIRED HARDWARE AND 6 USING THIS 2: INSTALLATION .. 9 11 UNIX 11 AIX 11 LINUX 12 SUN SOLARIS 13 HP-UX 13 SCO OPENSERVER 5 14 WINDOWS 14 4690 15 OS/390 16 I5 (AS/400) 17 ANDROID INSTALLATION AND 19 3: 23 25 CONFIGURATION 25 27 28 4: CONFIGURATION .. 29 31 CONFIGURING THE user 31 ACCESSING THE user 32 user INTERFACE GENERAL 33 34 39 USERGROUP 40 41 48 NODE ACCESS POINT (NAP).. 50 NODE 53 54 66 SYSTEM 78 MULTICAST 88 INITIAL 93 94 WATCH 96 NFM CLIENT 100 5: 107 109 109 PLAN PLAN DAY HOUR 114 115 6: ADVANCED 119 121 USING 121 USING ENVIRONMENT 122 WORKING WITH NODE 126 PLAN EXECUTION 129 ERROR 131 FILE 134 DATA 135 ENCRYPTION AND CONNECTION 136 NFM MULTIPLE SERVER 140 7: BANDWIDTH MANAGEMENT.

3 145 147 BANDWIDTH 147 BANDWIDTH 148 8: TOOLS .. 153 DATA REFORMATTING 155 NFM COMMAND LINE 161 NFM REMOTE SERVER 180 NFM FILE 183 user 186 EMAIL 190 9: QUICK FUNCTIONS .. 193 195 QUICK 195 QUICK 197 QUICK LIST & QUICK 197 QUICK 198 QUICK FUNCTIONS 198 QUICK 199 user HOME 201 10: 203 205 PROBLEMS LOGGING 205 PROBLEMS COMMUNICATING WITH NFM 206 PROBLEMS RELATED TO SYSTEM DATE & 207 UNEXPECTED RESULTS FROM A 207 WHEN ALL ELSE 208 209 APPENDIX A: RETURN 211 APPENDIX B: FTP 212 APPENDIX D: PPP 219 APPENDIX E: HTTP 223 APPENDIX F: AWS S3 227 INDEX .. 231 233 1: Introduction TPS /NFM user s guide Introduction 3 Overview What is NFM? Welcome to the power, flexibility, and versatility of the TPS /Network File Manager (NFM). NFM provides advanced file transfer capability while maintaining a comfortable level of familiarity for long-time IBM users.

4 TPS /NetWork File Manager is a Client/Server system designed to distribute files and other resources throughout a corporation s network. This robust, but easily, manageable file transfer mechanism allows files to be managed through a central server with file distribution taking place from the server to the client or among clients (peer-to-peer). TPS /NetWork File Manager Server is responsible for the management of the transmission of data from a source location to a target location. The Network File Manager system allows a user to customize this process through the use of transmission plans. Transmission plans detail the types of transfer, the files to be transferred, the nodes involved, and various other control factors. While remaining extremely flexible, transmission plans allow repetitive tasks to be performed on a regular basis with little or no user intervention.

5 A single server or multiple servers can be configured depending on the complexity and capacity of the network. Authorized personnel using a browser interface or a stand-alone Windows application can easily manipulate the configuration and management of the file transmissions within the network. The TPS /NetWork File Manager system uses IP sockets to communicate with NFM client enabled nodes and additionally manages FTP file transfers with non-client nodes, including mainframes and Internet FTP sites. Highlights Ability to monitor and configure activity using a browser interface anywhere on the network based on security levels. Custom plan builder to control step-by-step file transfers and program execution. Sophisticated scheduler that provides automation of plan execution, including calendar based repetition. Dynamic monitoring capabilities for viewing plans in progress.

6 Detailed error reporting capabilities. Remote file browsing capabilities. Peer-to-peer file transfers on demand. Transfer files with or without client software. Monitor node resources. SNA and/or TCP/IP file transfer concurrently. Extensive logging capabilities. Report activities by exporting data to third party databases. NetView-like transmission plan terminology. System security. Chapter 1 TPS /NFM user s guide 4 System components NFM consists of five primary types of components that are available for a combination of multiple operating systems. These include the following: NFM Server TPS Command Server NFM Client NFM Non-client node NFM (GUI) user interface NFM Server The NFM server is the main engine of the NFM system. It contains all configurations for the NFM system in database form at one central location. The NFM server runs as a series of unattended programs that respond to dialog from the NFM user interface as well as handle all scheduled and on demand operations involving NFM remote stations (or nodes).

7 TPS Command Server This is a separately packaged service module which is utilized by multiple TPS Systems software products. This program enables the NFM user interface to communicate with the NFM server. This program must be installed and running on the same computer as the NFM server to enable the user interface to function. NFM Client This refers to any node that is running the NFM client software. The client is responsible for performing request from the NFM server to send and receive files as well as local program execution. Like the server, the client runs unattended with no local user interface. The NFM client is also responsible for supporting the remote file browsing capability inherent to the system. The client is capable of performing file transfers directly between itself and another NFM client node. A peer-to-peer transfer of this type is still controlled by the NFM server but the data is sent directly between the clients.

8 This reduces bandwidth requirements at the server while still maintaining centralized control. The NFM client package also includes a command line utility program that enables the NFM remote server interface feature to be utilized. This feature allows programs or operators at the NFM client site to initiate NFM activity, including uploading files, without the need for the NFM server to continually poll the client to decide when to begin transferring. Because of the peer-to-peer nature of the NFM system, the NFM server computer must also be defined as an NFM client if it is to be accessed as a node during plan activity. Any use of the server as a file repository is simply done by design in the implementation of user written plans. TPS /NFM user s guide Introduction 5 NFM Non-client node This refers to any node that is defined to the NFM server but is not running the NFM client software.

9 These nodes rely on a different mechanism to facilitate file transfer and program execution (but not necessarily both). An example would be an FTP site, which could be an Internet site, where the NFM client could not be installed. The available NFM functionality to such nodes will vary based on their type. For example, the NFM file browsing capability also works with an FTP type node but not an HTTP one. An SOCKET node has the capability of executing a program but an FTP one does not. Additionally, during a file transfer between a source and target node, at least one of the two nodes must be an NFM client node. In order to transfer between two non-clients sites it would be necessary to pull files from the source site to an NFM client and then separately push the files to the target site. NFM user interface This is the JAVA-based user interface for the NFM system.

10 This program communicates directly to the NFM server to perform and monitor NFM system activities. Any number of users can be logged on simultaneously to the NFM system. The user interface stores no control or configuration information on the local computer. It acts only as a graphics terminal into the NFM system. There are two different methods for configuring an NFM user interface: Browser interface This option is accessed by simply running a browser and visiting an HTTP (web) server (typically also the NFM Server computer) that hosts the NFM user interface Java application. Although it requires some additional setup, the browser interface has the following advantage over using the stand-alone option: - It makes the user interface immediately available to any Java enabled web browser that can access the web server on the network, without the need to install additional NFM software on the computer.