Home

rvs Tiny - ServiceNet

1. ASCII is the standard code for UNIX and DOS Windows systems Here is the short expanation of the conversion tables that are offered by rvs Tiny EBCDIC was developed for IBM Mainframe computers ASCII US ASCII ISO 646 the ASCII character set defines 128 characters 0 to 127 decimal This character set is a subset of many other character sets with 256 characters including the ANSI character set of MS Windows ANSI Windows ANSI Values 0 to 127 are the same as in the ASCII character set values 128 to 255 are similar to the ISO Latin 1 character set EBCDIC 037 support characters which are used in the following countries Australien Brasilien Kanada Neuseeland Portugal Stidafrika USA EBCDIC 273 supports characters especially umlauts which are used in the following countries Germany Austria and Switzerland Examples createSendJob d C text txt s RVS v test In this example the C text txt file is sent to the RVS rvs center with a virtual name test 33 The virtual file name parameter option v is mandatory Examples createSendJob d C text txt s RVS v OFTP_TEST F F M 80 ANS 0 BM2 73 In this example the C text txt file is sent to the rvs center RVS witha virtual name OF TP_TEST this file is a text file of whicheach line has a length of 80 characters without CR LF F F M 80 Before transmission the file will be converted from ANSI to IBM037 I AN
2. Index A activateStation 36 ARCDIR 18 archiveJobs 51 B Batch file 33 C ConfigFile 17 Configuration files 29 CONTACT 24 28 createSendJob 38 Customizing configuration files 17 D DB 18 E EERP 25 29 EERP_OUT 25 28 29 50 ENDED 18 42 ENTERPRISE 25 EX _BUF CRE 27 EX BUF SIZ 27 F FAILED 18 42 G GATEWAY_STATION_NK 28 getJob 49 getJobList 48 H handleEERP 25 28 29 50 HOLD 25 28 29 HostAllowFile 18 HostDenyFil 18 I IMMEDIATE 25 28 29 INBOX 18 IP ADDR 25 28 29 J jobFilter 29 JobStart 29 JobstartConfigFile 18 L LINE_TYPE 27 LOCATION 25 LogConfigFil 17 LOGDIR 18 M monlog log 18 N NAME 25 O ODETTE 26 27 28 Odette port 24 ODETTE _ID 24 27 28 OUTBOX 18 P Platforms 7 Port 25 28 29 R RCV 18 REC PW 25 27 revision log 51 RMiIServiceHost 19 RMISeviceName 19 RootDir 17 Routing station 28 rvs center 26 rvsTiny properties 17 RVSTINY_ HOME 8 rvsTinyConfig xml 18 rvsTinyStationlist xml 19 S sendAttempts 30 showMonitorLog 35 SID 24 26 27 28 SN 18 SND PW 25 27 startServer 33 rvs Tiny User Manual Rev 2004 06 04 gedas deutschland GmbH Fachbereich rvs Systems 63 rvs Tiny User Manual STATION LOC 26 STATION_NK 26 STATION_RT 28 StationsConfigFile 18 stopServer 33 STREET 25 STREETNUMBER 25 T TCPIP BASIC 24 25 28 29 TCPIP_REC 25 26 TEMP 18 tiny log 18 Typographic conventions 8 V
3. VDA 25 VDSN 30 vdsn 30 W What is rvs 5 What rvs is not 5 64
4. You are free to choose the names for the rvsTinyJobstart and rvsTinyStationlist files the only requirement is that they are specified in the respective XML element are valid XML files and are located in the conf directory The same also applies tt HostAllowFile and HostDenyFile Example lt StationsConfigFile gt stationen xml lt StationsConfigFile gt The stationen xml file is a station list in XML format containing the required rvs Tiny parameters see chapter 3 2 and is located in the rvs Tiny conf directory The entries for RMISeviceName and RMIServiceHost are for internal communication and must not be changed Note You must stop and restart rvs Tiny each time you have made changes to any configuration file see chapter 4 1 and 4 2 3 2 Customizing the station configuration Station Configuration The installer offers you the possibilty to set up a local station and the rvs center For further customization of stations creation of new stations and their modification or deletion you can use the Graphical User Interface GUI or configuration files in XML format The obligatory parameters for these two stations the local and the rvs center have already been polled during installation and the SRVSTINY_HOME conf rvsTinyStationlist xml station configuration file has been appropriately adapted This configuration is also visible in the GUI If you do not need more entries fo
5. Requests help information Example startGUI Please read the chapter 3 for more information about the features of rvs Tiny GUI 2 6 rvs Tiny update installation Please read the chapter 5 for more information how to update rvs Tiny with central administration 16 Configuration 3 Configuration The present chapter describes how to customize configuration files via the rvs Tiny GUI or via rvs Tiny command line Note You do not need to make any changes to obtain a functioning system if you have correctly specified all parameters during installation and you do not require more stations than the local station and the rvs center You must restart rvs Tiny each time you have made changes to a configuration file 3 1 Customizing the global configuration files Files Two configuration files are of vital significance for the global rvs Tiny settings SRVSTINY_HOME conf rvsTinyConfig xml SRVSTINY_HOME conf rvsTiny properties 3 1 1 rvsTiny properties This is a Java properties file containing entries of the following format lt name gt lt value gt This file refers to 3 important locations contains three important parameters The rvs Tiny installation directory parameter RootDir The global rvs Tiny configuration file parameter ConfigFile The global configuration file for system logging parameter LogConfigFile Sample file comment lines starting wit
6. Displays a description ofthe current command Requests help information rvs Tiny User Manual Rev 2004 08 23 gedas deutschland GmbH Fachbereich rvs Systems 35 rvs Tiny User Manual Example ex C WINDOWS System32 cmd exe showMonitorLog G Programs rvsTiny bin gt showMonitorLog Ready to receive monitor log lines from server INF network CONNECTION_CREATE_SUCCESS TCP IP Connection established with t he following parameters GDDEBEC167369 3385 a INF protocol SENT_F_PDU Sent OFTP Event SSID Start Session ID lt Odettel D OTINY gt INF protocol RECEIVED_F_PDU Received OFTP Event SSID Start Session ID lt OdetteID ORUSNT gt INF protocol RECEIVED_F_PDU Received OFTP Event ESID End Session ID lt No rmal session termination Reason 66 gt INF network CONNECTION_CLOSE SUCCESS INF controller CREATE_SENDJOB New SendJob got created JobI D 6466621552366 er INF network CONNECTION_CREATE SUCCESS TCP IP Connection established with t he following parameters GDDEBEC167369 3365 P INF protocol SENT_F_PDU Sent OFTP Event SSID Start Session ID lt Odettel D OTINY gt INF protocol RECEIVED_F_PDU Received OFTP Event SSID Start Session ID lt OdettelID ORUSNT gt INF protocol SENT_F_PDU Sent OFTP Event SFID Start File ID lt DEST ORUSN T ORIG OTINY UDSN TEST DATE 6 40662 TIME 15523 SIZE 1 gt INF protocol RECEIVED_F_PDU Received OFTP
7. These allow you to save changes Save discard them Cancel or reverse them Undo Undo All Configurating a local station The possible tabs for the local station configuration are Local Station OFTP Odette parameters TCP IP Please read the chapter 3 2 3 and 3 2 4 for detailed explanation of those groups of parameters The parameters Name Phone and Remarks from the tab Local Station are comments The tab TCP IP is rvs Tiny User Manual Rev 2004 08 23 21 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual equivalent to the TCPIP_BASICS element parameter group in the XML station configuration file Configuration of the rvs center The possible tabs for the rvs center are Neigbour Station OFTP Odette parameters Line Type TCP IP Please read the chapter 3 2 3 and 3 2 5 and for detailed explanation of those groups of parameters A right click on the rvs center opens the context menu which offers then the options Add routed station and Activate connection With the option Add routed station you can add a set of routed stations that are reachable via the rvs center Activate connection activates the connection to the rvs center Setting up a routed station A rvs Tiny DER File View Customize Help gt AX I Help Transfer Stations Exit E Station RVS Neighbour Station oFTP Line Type TCP IP Re Paramet Add Routed Station pel aramee sD
8. but it is still not sent EERP DELETED 7 User deleted EERP Job will stop ENDED 8 Receive job has successfully ended after sending EERP 42 Working with rvs Tiny e ENDED WITH_JS_ERROR 9 Receive job run into error during calling jobstart e FATAL ERROR 10 Receive job run into fatal error Note Please see in the rvs portable Reference Manual chapter 3 3 for ODETTE protocol sequences such as EFNA SFID EFID EERP 4 6 Synchronization of Send Jobs The Odette file transfer is asynchronous That means If you create a send job a file will be only provided to be sent The sending of the file will not possible only after a connection to a partner station has been established In automated business with a lot of processes is desirable to react directly if the sending of a file was not successfilly in a certain period of time As a solution for this problem rvs Tiny offers on client side a functionality for synchronized file transfer This program remains active until the transfer is successfully finished or an error occurs It is possible to define the number of send attempts or the time in which a file fransfer has to be successfully done or the whole transfer will be count as an error Note A transfer is regarded as having been successfully completed when the ODETTE acknowledgement EERP End to End Response for this transfer has been received The convertAndSend program offers you the synchroniz
9. executed automatically The next step is to get a copy of the RCI s configuration that arrived as the file cfg rsp jar This should be done by the program prepareUpdateStation on the command line This program will copy for you the arrived configuration file cfg rsp Jar and store it to the WorkDir see chapter 5 2 for the explanation of WorkDir Example prepareUpdateStation bat s TINY11 Result The directory C rvsTiny management mgmt workspace TINY11 UPDATE_STATION_040828_113315 out with the complete configuration of the station TINY11 will be created If this action was successfull you will find a corresponding message in the file activity log This log file is stored in the directory SRVSTINY_HOME management mgmt log 56 rvs Tiny Central Administration Now you can administrate the configuration of the rvs Tiny station e g TINY11 You can exchange a license key modify the XML configuration files or substitute the appropriate jar files to make an update of rvs Tiny Please read the chapters 5 3 1 5 3 2 und 5 3 3 for more details about the particular configuration procedures Send the modified configuration to the RCI TINY11 You have to send the whole directory C rvsTiny management mgmt workspace TINY11 UPDATE_STATION_040828_113315 with the command commitUpdateStation bat s TINY11 d C rvsTiny management mgmt workspac
10. srrrreereeseene enoe ne eee eee werne k e He KHK HAK HEWE KA HE HAK HKH HKHKKR 9 2 1 Syst m requirements 4555x385 1o5 3 a Dd rk year y lea R ben di e oe kade w ya rk 9 2 2 Oblaming allicense naar in e Sek AA kefe vag hic tours K k Gale lee 9 2 3 Fresh install of rys Tiny si544 15 00di e apa N Kek Ha kan k ke eed eka E ka e V 10 2 4 rvs Tiny as Windows service M EE eee kek kek keke kre kek re kek Kek ke kek Ke Kek HA 15 2 5 How to start rvs Tiny GUT J erkeke keke kek ereke ek ee keke ek kek reke kre kk KK KA Ke KAR KK KA HA 16 2 6 rvs Tiny update installation lt 4 i 54xnis xy si xle resay kesa i KH Es e nk i Ku keve A ke V ean kik bek 16 3 Configuration S4 i ii si kik kk Ken k ne eee KE HE V keye ke c ke tek n E EW e n De k Cu EK Z be EK K OK in KU SEK AH assiro HEGE AE ise 17 3 1 Customizing the global configuration files k k eke kek kek k 17 3 1 1 FVSTINY Properties ND DD HHHH H HHHH HHHH 17 3 l 2 rvsTimyConti ge XW ls dy od ea dees rin SR Y k ekes n KE Ree eke s kun b be kek EN s k ke day Kek 18 3 2 Customizing the station configuration u kk eke kek ke keke kek k ek 19 3 2 1 Customizing stations via GUI eroii prere eet i kiyanek kieve RE we KA e KE ke yake kk He eken ein aie 20 3 2 2 Customizing stations in the XML configuration file L Lekek 23 3 2 3 I
11. 3 2 1 for explanation how to set up stations and the station TINY22 must also have station TINY2O as routed station via the rvs center The station TINY20 must be a Complete Installation and the station TINY22 only a Typical Installation please see the chapter 2 3 for the explanation of Typical and Complete Installation 58 rvs Tiny Central Administration To be able to modify an rvs Tiny parameter TINY20 must at first get the configuration of TINY22 it will be done with the following command orderConfiguration s TINY22 If this step was successful you will receive a message OrderConfiguration exited with return code 0 in the console and the file cfg rsp jar from the station TINY22 will be received as a response of this request please see in the Ended Transmissions Admin window of the TINY20 GUI The next step ist to get a copy of the TINY22 configuration that arrived as the file cfg rsp jar to the WorkDir of TINY20 Please see the chapter 5 2 for the explanation of the WorkDir prepareUpdateStation bat s TINY22 Result The directory C rvsTiny management mgmt workspace TINY22 UPDATE_STATION_040829_133315 out with the complete configuration of the station TINY22 will be created If this action was successful you will find a corresponding message in the file activity log This log file is stored in the directory SRVSTINY_HOME manag
12. Event SFPA Start File Positive Answer lt gt The Monitor messages are written to the RVSTINY_ HOME rvsTiny log monlog 1log file 4 4 Activating a station activate Usethe activateStation program to activate the rvs center in the Station command line How to activate the rvs center via the GUI please see chapter 3 2 1 Note You cannot activate a routed station You can activate only a direct neighbouring node neighbour station rvs center Usage activateStation verbose Optional parameters verbose Verbose message output help Displays a description of the current command Requests help information Heed messages in the command prompt window starting with message or error if rvs center activation fails e g due to an incorrect IP address Correct the configuration file with the station table when the IP address is incorrect You must stop and restart rvs Tiny each time you have saved the configuration file 36 Working with rvs Tiny 4 5 Sending a file It is possible to send a file via the GUI or via the command line How to start GUI please read the chapter 2 5 GUI Select the icon Send file or Transfer in the function bar The Transfer window opens with the sub entry Create New Transmission in the Transfer tree Selection of Create New Transmission opens a window on the right hand size of the screen entitled Create New Transmission Now you can type or select the send
13. ODETTE_ID gt 00013005623GEDASSKK lt ODETTE_ID gt lt CONTACT gt lt NAME gt local station lt NAME gt lt ENTERPRISE gt lt LOCATION gt lt STREET gt lt STREET_NUMBER gt lt DEPARTMENT gt lt PHONE gt lt PHONE gt lt FAX gt lt MAIL gt lt INET gt lt FREETEXT gt lt FREETEXT gt lt CONTACT gt lt TCPIP_BASIC gt lt IP_ADDR gt 139 1 87 68 lt IP_ADDR gt lt PORT gt 3305 lt PORT gt lt TCPIP_BASIC gt lt TCPIP_REC gt lt MAX_INCOMING_SESSIONS gt 5 lt MAX_INCOMING_SESSIONS gt lt MAX_INCOMING_SESSIONS gt 1 lt MAX_INCOMING_SESSIONS gt lt TCPIP_REC gt lt ENABLED gt Yes lt ENABLED gt lt STATION_LOC gt In the following example the local station SID is LOC the ODETTE ID 00013005623GEDASSKK The neighbor node can reach this station under IP address 139 1 87 68 and at port 3305 TCPIP_REC Note The TCPIP_REC block with the MAX INCOMING SESSIONS and MAX OUTGOING SESSIONS parameters and the ENABLED parameter are not being evaluated at present and are reserved for future application Do not edit nor delete these parameters 3 2 5 STATION_NK station entry rvs center This area contains information on a direct neighbor station rvs center only Again this area must be present in the station configuration exactly once only lt STATION_NK gt lt SID gt RVS lt SID gt lt ODETTE_ID gt 00013005623GEDASMEL lt ODETTE_ID gt lt CONTACT gt 26 Configuration lt
14. RVS o Network TCPAP Name rvs center Activate connection Phone 030 39971 777 Remarks W 2 Unknown localhost rvsTiny 1 4 0 rvs Tiny beta 02 2004 Pre condition You must already have set up a direct neighbouring node the rvs center via which you can reach the routed station Set up a routed station by a right click on the neighbour station the rvs center and selecting from the context menu the item Add routed station For you the connection type line type by which this station is to be reached is of no importance this is dealt with by the direct neightbouring node the rvs center For this reason the connection type to the routed station is not shown The possible tabs for this type of station are Routed Station OFTP Odette parameters Please read the chapter 3 2 3 and 3 2 6 for detailed explanation of those groups of parameters 22 Configuration rvs Tiny E BK File View Customize Help 2 lt gt Ta 2 Send file Transfer Stations Admin Exit LE E Station ROU123 U TOPE E RvS Routed Station oFTP De maz ROU123 Re Parameter Yalue SID ROU123 Routing Station RVS Name routed station Phone Remarks B Unknown localhost rsTiny 1 4 0 rvs Tiny beta 02 2004 ee A routed station in rvs Tiny can only be reached via the rvs center This is shown by the parameter Routing Station
15. The following parameters are to be set Format F MaxRecl 80 Y Yes N No If you set Serialization Y the files will be sent in the same order as the send jobs were created The next job will only be sent if the previous is completely finished All send jobs for the serialization must have the same LABEL In the GUI the VDSN will be used as label That means that all jobs for the same serialization group must have the same virtual data set name VDSN maximal record length for the files in format F or V please see the examle for the parameter Format For ASCII EBCDIC conversion the following conversion tables are available ASCH IBM037 ASCI IBM237 ANSI IBM073 ANSI IBM273 For EBCDIC ASCII conversion the following conversion tables are available IBM037 ASCIH IBM237 ASCII IBM037 ANSI IBM273 ANSI Please see the note beneth the parameters table for the command line for more explanation about the conversion tables Requests help information Verbose message output Requests help information center via the 38 Working with rvs Tiny Usage createSendJob d lt filename gt s lt receiver sid gt I lt input code gt 0 lt output code gt t lt conversion table gt F lt format gt M lt length gt S lt serialisation gt l lt label gt h verbose Required parameters d lt filename gt s lt receiver sid gt v lt vdsn gt Optional se
16. be a text file where each line has a length 80 without CR LF The following parameters are to be set F F M 80 maximal record length for the files in format F or V please see the examle for the parameter Format With the parameters input code and output code you can select one of the conversion tables that rvs Tiny offers The possible conversion tables are For ASCII EBCDIC conversion the following conversion tables are available ASCH IBM037 ASCH IBM237 ANSI IBM073 ANSI IBM273 For EBCDIC ASCII code conversion the following conversion tables are available IBM037 ASCH IBM237 ASCH IBM037 ANSI IBM273 ANSI Please see the note beneath this table for details about code tables Example If you want to use the conversion table ASCII IBM237 as input code you should write ASCH I ASCTIT as output code IBM237 O IBM237 It is also possibile to set as input output code only the values A E In this case is A ASCII and E IBM037 code conversion ASCH IBM037 see input code your own conversion table with the complete path Please read the User Manual chapter Code Conversion for more information how to create the own conversion table 44 Working with rvs Tiny S lt serialize gt lt label gt za lt attempts gt zt lt timeout gt Optional convert parameters ce Optional parameter verbose help Y Yes N No If you set the opti
17. file is used to log successfully processed send or receive jobs Usage archiveJobs verbose help Optional parameters help Displays a description of the current command verbose Verbose message output Requests help information Terminated jobs are deleted from the SRVSTINY_HOME rvsTiny Jjobs ENDED directory and the data is written into the revision log file in the SRVSTINY_HOME rvsTiny archive directory rvs Tiny User Manual Rev 2004 08 23 51 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual 52 rvs Tiny Central Administration 5 rvs Tiny Central Administration This chapter describes the powerful feature of rvs Tiny how to remotely administer other rvs Tiny stations rvs Tiny is an ideal software for star topologies where many stations are connected with one central server rvs center Therefore it is essential for the network administrator being able to remotely administer all rvs Tiny installations 5 1 Introduction The rvs Tiny Central Administration enables the configuration of numerous rvs Tiny installations by using special configuration files The configuration files will be sent from a rvs Tiny station we call it Local Configuration Instance LCI to the station that should be administrated we call it Remote Controlled Instance RCI The both instances are located in the rvs Tiny star network Please s
18. in the GUI that is equivalent to the parameter GATEWAY STATION NK in the element parameter group STATION_RT of the XML station configuration file Besides entering the freely selectable station name SID in the Routed Station tab you only have to enter the Odette ID in the Odette tab to complete the station configuration of the routed station Once you have saved the parameters for a routed station you can no longer change the station ID SID Changing the station ID would mean configuring an entirely new station without deleting the old one A right click on the routed station opens the context menu which offers then an option Delete station 3 2 2 Customizing stations in the XML configuration file On the other hand the station configuration can be done editing the XML station configuration file rvsTinyStationlist xml see chapter 3 1 2 for the explanation where this file is to be found The STATION LOC element in the configuration file is equivalent to the Local Station in the GUI STATION NK is Neighbour Station and STATION_RT is Routed Station in the GUI Excerpt from the rvsTinyStationlist xml file lt xml version 1 0 encoding ISO 8859 1 gt lt RVS_STATION_CONFIG gt lt Setting for the local station gt lt STATION_LOC gt lt STATION_LOC gt lt Setting for the neighbour station gt lt STATION_NK gt rvs Tiny User Manual Rev 2004 08 23 23 gedas deutschland GmbH Fachbereich
19. is available by the program handleEERP see chapter 4 8 Active Send Transmissions To delete this job activate the Delete button Ifthe job is active you must first pause it as rvs Tiny will not allow you to delete a job which is actually being transmitted To pause the job use the button marked Hold A job which has been paused can be released again by pressing the Release button Command Line Use the get JobList program to list all jobs Usage getJobList a e verbose Optional parameters a Detailed information on jobs currently being processed e Information on terminated jobs 48 Working with rvs Tiny f Information on failed jobs h Requests help information verbose Verbose message output Requests help information Example getJobList e Result cx C WINDOWS System32 cmd exe iC Programs rusTinyNbin gt getJobList e BRR RRR job 8484212288438080 lt RCU state ENDED job 8484212288448080 lt RCU gt state ENDED job 848421221358880 lt RCU gt state ENDED job 8484212213518808 lt RCU gt state ENDED LakaZaZakeka kn 2an Ze nka kn n ZnZakua Za 2nkea kaka za List ended size 4 EHRE TEN G Programs rvsTiny bin gt Information on a job entry getJob Use the get Job program to retrieve information on a particular send or receive job Usage getJob n lt jobid gt a verbose Required parameters n lt jobid gt Information on a send or rece
20. rustinyservice i rvs Tiny User Manual Rev 2004 08 30 15 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual With the command rvstinyservice c rvs Tiny Server was started on the command line console With the command rvstinyservice i rvs Tiny was installed as system Windows service Now you can find rvs Tiny as a service in the list of system services Start gt Control Panel gt Administrative Tools gt Services If you want to start rvs Tiny every time the system starts you can set the startup type to Automatic by choosing Automatic from the combo box in the Startup type area Example Windows XP german version rysTiny Server Gestar Automatisch Lokales System 2 5 How to start rvs Tiny GUI To start the GUI use the program start GUT It is a batch file in the directory SRVSTINY_HOME bin So you have to change to the SRVSTINY_HOME bin directory e g C Programs rvsTiny bin to be able to execute this program Alternatively you can start rvs Tiny GUI using the rvs Tiny program group Start gt Programs gt rvsTiny gt Start GUI Usage startGUI local All parameters are optional local starts the OFTP server module in the same process as the GUI no transmission of data will be possible without the GUI running an already running OFTP server process might lead to errors help Requests help information
21. rvs Systems rvs Tiny User Manual Comments Station list lt STATION_NK gt lt Setting for routed stations gt lt One entry for each routed station gt lt STATION_RT gt lt STATION_RT gt lt RVS_STATION_CONFIG gt Lines starting with lt and ending with gt are interpreted as comments Edit this file if you have to change mandatory parameters ODETTE_ID TCPIP_BASIC or if you wish to assign values to other optional parameters such as CONTACT Use a text editor e g Edit Text Pad to do so Please make sure to save your XML files as valid XML documents after editing as rvs Tiny otherwise will not be able to read them and may fail to start correctly The changes in the GUI will be visible immediately afer saving in the XML station configuration file the changes in the XML station configuration file will be visible in the GUI only after a new start of the rvs Tiny command startServer Note For correct TCP IP communication you must ensure that the IP ports for RMI 1099 and for Odette e g 3305 are free The following chapters will describe all station parameters in detail 3 2 3 Identification of rvs Tiny stations There are several parameters in the station list that identify rvs Tiny stations Of these only the SID ODETTE_ID and TCPIP_BASIC parameters are obligatory The SID parameter was assigned during rvs Tiny installation the parameter for the local station
22. scheduling system rvs does not care about the contents of the files it is transporting It only acts as a transparent transport medium and performs no semantic interpretation of the data it carries rvs is not an EDI converter You can however purchase additional components for converting between specific message formats e g VDA ODETTE EDIFACT XML using rvs as transport service from gedas deutschland GmbH rvs is not a network control or monitoring tool rvs Tiny User Manual Rev 2004 08 23 5 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual rvs Tiny available features What is rvs Tiny rvs Tiny is a communication software with a graphical user interface based like rvs on the OFTP protocol It can connect applications with partners For this reason the software is ideal for star topologies where many branches or mobile employees are connected with one central server see the following picture rvs Tiny rvs Tiny rvs Tiny A we rvs Tiny lt _ rvyscenter lt s rvs Tiny ar W Sa rvs Tiny rvs Tiny rvs Tiny The following features are available in rvs Tiny 2 0 center or to the routed stations reachable via rvs center send files to the rvs receive files from the rvs center or from routed stations v
23. 4 convertAndSend d C INTEGRATION test txt s RVS v TEST cf C rvsET system fmtDesc fw kanban ineas xml ct C rvsET system stylesheets ineas2deljit xslt cf2 C rvsET system fmtDesc edifact 97 orig xml In this example the C INTEGRATION test txt file is sent to the rvs center RYS with a virtual name TEST The test t xt file was also converted with the EDI converter WEDIConv installed in the directory C rvsET first from the inhouse format test txt tothe XML format fw kanban ineas xml and then to the EDIFACT message edifact 97 orig xm1 In the first step was used a stylesheet ineas2deljit xslt for the special presentation Note If you use convertAndSend to send files you must pay attention to the fact that with this feature a new send job after an occured error can cause a double transmission e g if the file is already transmitted but the in the zt parameter defined time out period passed without receiving the EERP The transmission can be still active independent from the own local station e g by the rvs center In this case the new sending of the file can cause double transmission The application above rvs must be able to handle this particular situation A possible solution is the file name must be unique or it must get a unique counter a counter stamp 4 7 Listing of all receive and send jobs The most important information about the send and receive jobs ca
24. 994 email rvs service gedas de rvs Tiny User Manual Rev 2004 08 23 7 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual Character styles RVSTINY HOME Skills 1 2 Representation means This chapter describes the typographic conventions used in this manual and explains the meaning of specially highlighted expressions Typographic conventions e Instructions begin with a bullet Other lists begin with the en dash Courier Commands menu commands file names path names programs examples scripts options qualifiers data sets fields modes window names dialog boxes and statuses BOLD and IN CAPITAL Parameters environment variables variables LETTERS Inverted commas Links to other manuals sections and chapters literature Bold Important terms names of operating systems proper names buttons function keys Directories As user directories are found on different locations for the different operating systems we use the variable RVSTINY_HOME in this manual Default values are C Programs rvsTiny for Windows XP and Windows 2000 Substitute the variable with your correct path 1 3 Target group This manual is meant for regular users of rvs Tiny as well as administrators It provides an overview of the basic rvs Tiny functions The following skills are required to be able to use rvs Tiny good knowledge of the current operating system k
25. INY_HOME management mgmt datastore This directory will be created only after a succesfull transmission and response to the request for the configuration file of the RCI Please see the chapter 5 2 for the explanation how to make a configuration request SRVSTINY_HOME management mgmt log activity log This log file contains protocols of all configuration actions Each entry comprises a timestamp the type configuration request or configuration response respectively the SID of the administrated rvs Tiny station RCI and a message text RVSTINY_HOME management mgmt templates This directory contains templates for management actions It is not necessary to deal with this directory except for updates ofthe administration software itself SRVSTINY_HOME management mgmt workspace This directory stores configurations of RCIs for editing It contains subfolders that are named after the RCI s SID see the tool prepareUpdateStation chapter 5 2 for an example The Remote Controlled Instance RCI The RCI is a is rvs Tiny station which should be administrated remotely It can be a Typical Installation of rvs Tiny Please see the chapter 2 3 for the explanation of the installation procedure and does not have to be a Complete Installation such as LCI When rvs Tiny RCI receives a configuration request a file cfg req jar a dedicated job will be launched This job starts the rvs Tiny configuration pro
26. NAME gt neighbour station lt NAME gt lt lt lt lt lt lt lt FAX gt lt lt lt FREET lt CONTACT gt lt LINE_TYP ENTERPRISE gt LOCATION gt STREET gt STREET_NUMBER gt DEPARTMENT gt PHONE gt lt PHONE gt MAIL gt INET gt EXT gt lt FREETEXT gt Ey lt LINE_SUSP gt No lt LINE_SUSP gt lt PSESSIONS gt 1 lt PSESSIONS gt lt ACTIV lt DE lt LINETYP lt ODETTE gt lt SND REC D X X _B _B TTE gt E_CON_SETUP gt Yes lt ACTIVE_CON_SETUP gt LAY gt O lt DELAY gt E gt PW gt H5C lt SND_PW gt PW gt L3Y lt REC_PW gt BLOCKS gt 0 lt SND_BLOCKS gt REC_BLOCKS gt 0 lt REC_BLOCKS gt E UF_CRE gt 0 lt EX_BUF_CRE gt E UF_SIZ gt 0 lt EX_BUF_SIZ gt EERP_IN gt NORMAL lt EERP_OUT gt I ERP_OUT gt NORMAL lt EERP_OUT gt P_BASIC gt lt IP_ADDR gt 139 1 65 42 lt IP_ADDR gt lt PORT gt 3305 lt PORT gt lt TCPIP_BASIC gt lt STATION_NK gt The password rvs Tiny expects from the neighbor SID Station ID see chapter 3 2 3 ODETTE_ID ODETTE ID see chapter 3 2 3 CONTACT Contact information see chapter 3 2 3 LINE_TYPE For future application not being evaluated ODETTE Parameter block comprises parameters for OFTP SND_PW The password rvs Tiny sends to the neighbor ODETTE password exchange between two neighbor stations and verification always occurs while a session i
27. NTACT gt TTE gt EERP_OUT gt NORMAL lt EERP_OUT gt ETTE gt ON_RT gt SID Station ID see chapter 3 2 3 ODETTE_ID ODETTE ID see chapter 3 2 3 CONTACT Contact information see chapter 3 2 3 GATEWAY_STATION_NK This field comprises the station s SID used to execute communication with the routed station configured here For rvs Tiny is may only be the direct neighbor station rvs center because rvs Tiny only allows for a direct neighbor station ODETTE Parameter block comprises parameters for OFTP 28 Configuration EERP_OUT Procedure for sending receipts EERPs NORMAL Generation of a receipt after successful file reception and immediate active transmission HOLD Generation of a receipt after successful file reception The receipt however is only sent after having been released with the handleEERP program Default NORMAL TCPIP_BASIC TCP IP parameters required for connection establishment IP_ADDR IP address or DNS name of the own or the partner station PORT Port on which a TCP IP listener is to be started 3305 by default JobFilter 3 3 Customizing the JobStarts The JobStart configuration comprises rules that allow special programs to be launched when appropriate files are being sent or received All programs of the jobFilters in question are started their sequence cannot be influenced if more than
28. NYO2 TINYO1 must at first get the configuration of TINYO2 with the command orderConfiguration s TINYO2 If this step was successful you will receive a message OrderConfiguration exited with return code 0 in the console and the fllecfg rsp Jar will be received see in the Ended Transmissions Admin window ofthe TINY01 GUD The next step ist to get a copy of the TINYO2 configuration that arrived as the file cfg rsp jar This must be done with the following command prepareUpdateStation bat s TINY02 rvs Tiny User Manual Rev 2004 08 23 57 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual Result The directory C rvsTiny management mgmt workspace TINYO2 UPDATE_STATION_04 0828 113315 out with the complete configuration of the station TINYO2 will be created If this action was successful you will find the message in the file activity log This log file is stored in the directory SRVSTINY_HOME management mgmt log Now you can rename the ol C rvsTiny manage workspace TINYO2 license key license prope C rvsTiny manage workspace TINYO2 2 2 Send the modified configuration to T d license key from ment mgmt the directory UPDATE_STATION_040828_113315 out conftolicenseOLD properties and copy the new rtiestoth ment mgmt e directory UPDATE_STATION_040828_113315 out conf How t
29. SI O IBM273 code createSendJob d C TEMP part txt s RVS v PART S Y l AUTO In this example the C TEMP part1 txt file is sent to the rvs center RVS with a virtual name PART this file belongs to the serialized group of files with the label for the whole group AUTO The message createSendJob exited with return code 0 appears when a send job was successfully created A temporary file named for example 040329170027000 is created in the SND directory while a send job is being processed This name is made up of the date 040329 the time 170027 and a consecutive three digit number 000 for files arriving in the very same second In the following example job 040329170027000 waits for a receipt EERP from the rvs center and is therefore still in the SND directory SND and RCV are directories where jobs currently being processed are intermediately stored The Status field indicates the job s processing phase WF_EERP Waiting For EERP means waiting for EERP receipt lt xml version 1 0 encoding ISO 8859 1 gt rvs Tiny User Manual Rev 2004 08 23 Al gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual Status lt Job gt lt ID gt 040329170027000 lt ID gt lt Static gt lt FileName gt C Answer txt lt FileName gt lt VDSN gt TESTFILE lt VDSN gt lt SID gt RVS lt SID gt lt Direction gt SND lt Direction gt lt Date gt 040329 l
30. amme rvsTiny bin gt startServer nowDate 64238 endDate 99365 kaz rus Tiny Server has started ka 14 Installation on Windows systems Starting and stopping via the Start menu Start rvs Tiny by choosing Start gt Programs gt rvsTiny gt rvsTiny or the Start menu command you specified during installation in the Start menu This will guide you to the SRVSTINY_HOME bin directory where you can start any of the startServer bat stoperver bat batch files by double clicking 2 4 rvs Tiny as Windows service Unter some circumstances it is desirable to run rvs Tiny in background even though you are not logged in to the computer Therefore you have to install rvs Tiny as a system service Note The term Service means a program that can be started from the operating system and works in the background This is possible starting the batch script rv st inyservice bat out of the directory SRVSTINY_HOME bin Usage rvstinyservice lt parameters gt options The possible parameters are C starts rvs Tiny on console i installs rvs Tiny as service m r removes rvs Tiny as service S starts rvs Tiny as service h usage Example e C WINDOWS System32 cmd exe E G in gt rustinyservice c a Running rusTiny Server nowDate 84238 endDate 99365 tal rvs Tiny Server has started tad Batchvorgang abbrechen J ND J iC Programme rusTiny bin gt
31. ation of send jobs functionality It is similar to the createSendJob program it has additionally the options for the synchronized file transfer and for the conversion of an EDI message with the EDI converter WEDIConv see WEDIConv User Manual Usage convertAndSend d lt filename gt s lt receiver sid gt I lt input code gt 0 lt output code gt t lt conversion table gt F lt format gt M lt length gt S lt serialisation gt 1 lt label gt za lt attempts gt zt lt timeout gt converter parms h verbose Required parameters d lt filename gt File name of the file to be sent s lt receiver sid gt Recipient station ID v lt vdsn gt Virtual file name the length of the file name used for ODETTE transfer must not exceed 26 characters rvs Tiny User Manual Rev 2004 08 23 43 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual Optional send parameters F lt format gt M lt length gt I lt input code gt O lt output code gt t lt conversion table gt Format of the file to be sent T text file a stream of ASCII characters U unstructured binary byte stream V variable variable record length F fixed fixed record length The files in format F or V must be text files with the appropriate line record length Example If you want to send a file in format fixed with the record length 80 it must
32. ble IBM037 ASCII IBM237 ASCH IBM037 ANSI IBM273 ANSI Please see the note beneath this table for details about code tables Example If you want to use the conversion table ASCII IBM237 as input code you should write ASCH I ASCII as output code IBM237 O IBM237 It is also possibile to set as input output code only the values A E In this case is A ASCII and E IBM037 code conversion ASCH IBM037 see input code your own conversion table with the complete path Please read the User Manual chapter Code Conversion for more information how to create the own conversion table Y Yes N No If you set the option S Y the files will be sent in the same order as the send jobs were created The next job will only be sent if the previous is completely finished All send jobs for the serialization must have the same LABEL In the GUI the VDSN will be used as label In the command line you can specify your own label Name of group of serialized send jobs User specified descriptive label for this job If you do not specify this parameter the VDSN will be user as a label Requests help information Verbose message output Requests help information Note The text file are stored on most systems in one of two computer codes namely ASCII American National Standard Code for Information Interchange or EBCDIC Extended Binary Coded Decimal Interchange Code 40 Working with rvs Tiny
33. cess that handles the configuration request and generates the configuration response The configuration response is sent back from the RCI to LCI as file c g r sp jar 5 2 Command Tools of the Central Administration The whole process all configuration and administration cases is to be done by the following command tools These tools are located in the directory SRVSTINY_HOME bin as batch files please see the chapter 1 2 for the explanation of SRVSTINY_HOME so you must change to this directory to be able to execute them 54 rvs Tiny Central Administration orderConfiguration bat fetches the configuration of an RCI and stores it in s SID CRep Example C rvsTiny management mgmt datastore TINYPW In this example TINYPW is the SID of RCI ofthe station that should be administrated prepareUpdateStation bat s gets a RCI configuration copy out of CRep to the lt SID gt WorkDir in order to serve as starting point for modifications Example for the WorkDir In the directory C rvsTiny management mgmt workspace the following subdirectory will be created TINYPW UPDATE_STATION_040826_11 4418 out This is a subdirectory for the TINYPW station the date of the creation is 2004 08 26 the time of the creation is 11 44 18 commitUpdateStation bat s sends a modified configuration from the WorkDir lt SID gt d lt WorkDir gt without out subdirectory to an RCI RCI should be set
34. ctory or available via the rvs Tiny GUI Note To launch an rvs Tiny program you must change to the SRVSTINY_HOME bin directory 4 1 Starting the rvs Tiny server startServer UsethestartServer program to start rvs Tiny Example startServer It is not possible to specify any parameters A successful start is indicated as follows rvs Tiny Server has started Note The RMI port 1099 is necessary for the RMI registry so if this port is occupied rvs Tiny Server will not start successfully 4 2 Stopping the rvs Tiny server stopServer Usethe stopServer program to stop rvs Tiny Usage stopServer m lt mode gt verbose All parameters are optional m lt mode gt Time for jobs to terminate before rvs Tiny is stopped Possible values 0 default 120 seconds 1 60 seconds 2 30 seconds 3 20 seconds 4 10 seconds verbose Verbose message output help Requests help information rvs Tiny User Manual Rev 2004 08 23 33 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual Requests help information Example stopServer Result The server stops after 120 seconds Example stopServer m 3 Result The server stops after 20 seconds rvs Tiny Server has stopped 4 3 Displaying Monitor messages It is possible to display Monitor messages via the GUI or via the command line Use this program to trace the cur
35. ddress of your computer If this address is not known to you type in the command line the command hostname for the host name or the command ipconfig for the IP address of your computer Passwords receive and send passwords should be exchanged with the direct neighbour station rvs center in bilateral agreement Your send password is the receive password at the rvs center station The send password of the rvs center is your receive password For routed stations you do not need passwords For rvs Tiny you do not have to be a RACF user as it is necessary for rvsWIN it is the ODETTE ID which identifies the participients in the file transfer Some parallels between rvs Tiny and rvsWIN rys Tiny as well as rvs WIN enables to send files in format fixed or variable to the mainframe computer e g rvsMVS rvs Tiny User Manual Rev 2004 08 23 61 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual Code translation code conversion ASCH gt EBCDIC when sending or receiving files also possible in rvs Tiny but with a greater number of selectable conversion tables Resident Receive Entries in rvsWIN are equivalent to Jobstarts after receive in rvs Tiny please read the chapter 3 3 of rvs Tiny User Manual for more information The Control File of rvsWIN is equivalent to Transfer window directory Jobs in the rvs Tiny GUI please see the chapter 4 7 62
36. dentification of rvs Tiny stations L keke ee kek k k ee kek k kek Ke k 24 32 4 7 STATION LOG station entry 2 2 ask Ei ae p NG hen din ae n d Ver vn tes 26 32 5 STATION NK station entry eiai sd khan e adek sa ached 14ya sae NT u nal 26 32 6 STATION RT Station erty yess x5 545415 RER el ar ere a R AE e a Ri VA ek 28 3 3 Customizing the JobStarts M E eee keke ke kek kek kek ke kek k k kek nenne KAK Ke 29 4 Working with rvs Tiny 000000000000s000000000200000000000000 o s n eo os cepo kerese see se keseteo s sobe eres e ses tei 33 4 1 Starting the rvs Tiny server E eke ek e ke ee essen keke ee kek k Ke kk KK AK KA KAK 33 4 2 Stopping the rvs Tiny server lt xi diy d y y ke da r xadake ya feke baya rake ka Fe ayy a aaaea Fz kev ew canan 33 4 3 Displaying Monitor messages Mh kereker eee eee ke ek ee kek ee ee ke kre kar ke kk ek kK Kek RR 34 4 4 Activating a staton sa nandi eai e Ra MER eka n Gly a hay Pek Par d v ebe A A 36 4 5 Sendinga fe ay4 s iyyi ern ka d E kun de eW er ne eb An EKA KE ee W n de KANE Ke K e E Ree de KE kas K Ren des 37 4 6 Synchronization of Send Jobs u eee eke kek ke kek keke kek keke kek k k k 43 4 7 Listing of all receive and send jobs u eee eke kek keke ee kek keke 46 4 8 Deleting r releasing EERPS 4 2 683 E Ranaknem in
37. ds for the German word Rechner Verbund System Verbund System The rvs computer communication system is a well established base service for electronic data interchange EDI rvs serves to ensure transmission of electronic data between heterogeneous computer platforms using different network protocols To do so rvs implements a universal network model which you can configure in each network node rvs provides an efficient and reliable transport service for both standardized EDI message types and files of any format or contents You can receive only such files that are explicitly destined for rvs This means that rvs does not allow any unauthorized access to remote or to own data files The system was originally developed by Volkswagen AG and has been used in the German and European automobile industries for a number of years but also by banks insurances and industry worldwide rvs uses the OFTP protocol An extension to the OFTP standard was developed for Volkswagen AG It has been enhanced by a line driver for SNA LU 6 2 What rvs is not rvs is not an online system It neither supports direct terminal like access to other sites nor does it provide a communication pipe from application to application on a data record level You cannot directly execute transfers in your own application You rather can place send orders from within you application to rvs which will be handled asynchronously rvs is not a job
38. e Send file Transfer i Stations Eu Bl Station LXX T TcP P E aes Local Station ortp TCP IPI1 Re Parameter ROU123 A SD Bate Name local station Ea ROU234 Phone Remarks j 4 Unknown localhost rvsTiny 140 rvs Tiny beta 02 2004 ee On the left side of the stations window you will see the station tree to the right is a station parameter table The station tree depicts all of the stations which exist in the rvs Tiny database e g your local station and the rvs center you have already configured during the installation so they are now visible in the station tree as well as their connection type TCP IP at present The station table on the right hand side of the window displays all of the parameters for the station currently selected With the aid of the various station tabs OFTP TCP IP you can configure various parameter groups Grayed fields indicate that these parameters cannot be edited Note Once you have saved the parameters for a station you can no longer change the station ID SID Changing the station ID would mean configuring an entirely new station The parameters which are obligatory for station configuration are marked in the column Re Required with the symbol 2 Example Odette Id is obligatory in the OFTP tab On the right hand side of the window beneath the station parameter table is a series of buttons Save Cancel Undo Undo All
39. e TINY11 UPDATE_STATION_040828_113315 This command will store the whole modified directory and send it to the RCI TINY11 again as a file cfg req jar After successfully receiving a file cfg req jar at the RCI TINY11 rvs Tiny will be stopped it all happens with the process commitUpdateStation you do not have to do any particular steps the modified configuration will be updated the update job checks if all was correct and sends back a response as a file cfg r sp Jar The result of the update is again logged in the file act ivity log Note In case of non success the old configuration will be activated again 5 3 1 How to exchange a license key file This chapter describes the typical case in administrating rvs Tiny how to exchange an invalid license key In this example the station TINYO1l will administrate the station TINY 02 Prerequisites The station TINYO1 must have the station TINYO2 in the station table as routed station via the rvs center please read the chapter 3 2 1 for the explanation how to set up stations and the station TINY 02 must also have station the TINYO1 as routed station via the rvs center The station TINYO1 must be a Complete Installation and the station TINYO2 only a Typical Installation please see the chapter 2 3 for the explanation of Typical and Complete Installation To be able to replace a license key file of TI
40. e enter informations about your local station IP addresshostname GDDEBC33378 Port 3305 Odette ID onn1 300564GEDASSKK InciallAninwhere hy zern G Cancel Previous Next Then follows the dialog for the direct neighbor station rvs center parameters All of these parameters are mandatory as well and must be specified to ensure proper operation of rvs Tiny rvs Tiny User Manual Rev 2004 08 30 13 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual 2 rvs Tiny 2 0 RC3 Neighbour Station Please enter informations about the neighbour station IP addresshostname 139 1 87 68 Port 3305 Odette ID 000130045GEDASRYS Password send HL6 Password receive XF4 Previous Next The last dialogs informs you of the successful installation of rvs Tiny Starting and stopping To test start and stop rvs Tiny using the following commands startServer starts the rvs Tiny process stopServer stops the rvs Tiny process These two commands are available as batch files in the SRVSTINY_HOME bin directory Starting and stopping via the command prompt You can also start and stop rvs Tiny using the command prompt In this case you must change to the SRVSTINY_HOME bin directory e g C Programs rvsTiny bin Successful start Start A successful start is indicated as follows ex C WINDOWS System32 cmd exe startServer G Progr
41. ed 3305 by default SND_PW The password rvs Tiny sends to the neighbor station ODETTE password exchange between two neighbor stations and verification always occurs while a session is being established JREC_PW The password rvs Tiny expects from the neighbor station EERP_OUT Procedure for sending receipts EERPs NORMAL Generation of a receipt after successful file reception and immediate active transmission HOLD Generation of a receipt after successful file reception The receipt however is only sent after having been released with the handleEERP program Default NORMAL At present the station list comprises the following not yet evaluated parameters The lt TCPIP_REC gt block with the lt MAX INCOMING SESSIONS gt and lt MAX OUTGOING SESSIONS gt parameters The ENABLED parameter To apply for an ODETTE ID in Germany please contact ODETTE ID Verband der Automobilindustrie e V VDA Abt Logistik Postfach 17 05 63 60079 Frankfurt Ph 49 69 7570 0 rvs Tiny User Manual Rev 2004 08 23 25 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual Get the complete description of OFTP from http www odette org 3 2 4 STATION LOC station entry Local station This area comprises information on the local station it must be present exactly once in the station configuration Local station example lt STATION_LOC gt lt SID gt LOC lt SID gt lt
42. ee the following picture RCI RCI LCI rvs Tiny rvs Tiny rvs Tiny RCI N Rek RCI rvs Tiny lt _ rvs center lt s rvs Tiny RCI e RCI f N RCI rvs Tiny rvs Tiny rvs Tiny To distinguish the configuration files for the central administration from the normal rvs Tiny XML configuration files such as rvsTinyStationlist xml the files for the central administration will be named configuration container files These are cfg req jar for configuration requests sent by LCI to RCI and cfg rsp jar for configuration responses sent by RCI to LCI The Local Configuration Instance LCI Each rvs Tiny installation can be used as LCI when during the setup procedure in the window Choose Product Feature the Complete Installation is selected please see the chapter 2 3 for the explanation how to install rvs Tiny rvs Tiny User Manual Rev 2004 08 23 53 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual The LCI maintains a special directory where the configuration data of all RCI s rvs Tiny stations that are to be administrated are stored the Configuration Repository CRep The location of CRep is SRVSTINY_HOME management Please refer to the chapter 1 2 for the explanation of SRVSTINY_HOME The entries of CRep SRVSTINY_HOME management are SRVST
43. ement mgmt log Now you can edit the file rvsTinyStationlist xml from the directory C rvsTiny management mgmt workspace TINY22 UPDATE_STATION_040829_133315 out conf and modify it e g parameter ODETTE _ID or TCP IP address parameter IP_ ADDR for the local station of TINY22 STATION LOC or other stations rvs center or routed stations The next step is to send the modified configuration to TINY22 you must send the whole directory but without out directory C rvsTiny management mgmt workspace TINY02 UPDATE_STATION_040829_133315 with the command commitUpdateStation bat s TINY22 d C rvsTiny management mqmt workspace TINY22 UPDATE_STATION_040829_133315 This command will store the whole modified directory and send it to station TINY22 again asa file cfg req jar e After successfully receiving a file cfg req jar at the station TINY22 rvs Tiny at station TINY22 will be stopped it all happens with the process commitUpdateStation you do not have to make any particular steps and the modified configuration will be updated Then the update job checks if all was correct and sends back a response to the station TINY20 as a file cfg rsp jar The result of the update is again logged in the file activity log Note In case of non success the old configuration will be activated again rvs Tiny User Manual Rev 2004 08 23 59
44. gedas rvs Tiny Version 2 0 User Manual rvs Tiny User Manual The products listed in this manual are protected by copyright rvs Tiny User Manual 2004 by gedas deutschland GmbH PascalstraBe 11 10587 Berlin This manual is protected by copyright All rights reserved No part of this book may be used or reproduced in any form or by any means including photocopies microfilm or any other means or stored in a database or retrieval system without obtaining prior permission from gedas Rights are also reserved as far as lectures radio and television is concerned We reserve the right to make changes to the content of this manual without giving prior notice gedas is not liable for technical or printing errors or defects in this manual Moreover gedas shall not be liable for damage which is directly or indirectly caused by delivery performance and use of this material Contents Contents 1 Introduction lt 4545ss 5i 5e ur ee r s Heke b n seke e KE knee e wesl h e r W Q ee WAE SEWE KOK e U Vek e Uu We nek GUV ek ve eke 5 1 1 Short description of the system u ekere erek keke keke kek k k ke kk kk KK KA 5 1 2 Representation means eee kek ekere kek ke kek kek ke kak kk Ka kk kk ke kr ka kk ka k k 8 1 3 Target OTOUD seen een de e y ci e a Oe er erie ere cae S 8 2 Installation on Windows systems
45. gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual 5 3 3 How to make an update of rvs Tiny This chapter describes a typical case in administrating rvs Tiny how to make an update of an another rvs Tiny station In this example the station TINY 30 will administrate the station T 1 Prerequisites The station T station table as routed station via the the rvs INY33 NY30 must have the station T1 INY33 in the center please read the chapter 3 2 1 for explanation how to set up stations and the station TINY30 must also have station T1 T INY33 as routed station via the rvs INY30 must be a Complete Installation and the station TINY 33 only a center The station Typical Installation please see the chapter 2 3 for the explanation of Typical and Complete Installation e To be able to make an update of rvs Tiny at the station TINY 30 you must get at first the configuration of TINY33 orderConfiguration s TINY33 If this step was successful you will receive a message OrderConfiguration exited with return code 0 and the file cfg rsp jar will be received see in the Ended Transmissions Admin window of the T1 The next step ist to get a copy to the WorkDir of the T1 NY30 GUI NY 33 configuration that arrived as the file cfg r sp jar Type the follwing command in the command line
46. h will be ignored RootDir C Programs rvsTiny configuration xml file ConfigFile C Programs rvsTiny conf rvsTinyConfig xml log config file LogConfigFile C Programs rvsTiny conf rvsTinyLogger xml rvs Tiny User Manual Rev 2004 08 23 17 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual Elements 3 1 2 rvsTinyConfig xml The following table lists the most important elements of the rvsTinyConfig xml file ELEMENT DESCRIPTION DB Directory for job administration with the ENDED FAILED RCV and SND subdirectories The RCV and SND subdirectories are used to store temporary not fully processed jobs The FAT LED directory holds the failed the ENDED directory the completed jobs These directories are also visible in the GUI Admin window Jobs TEMP Directory for temporary use INBOX Directory where completely received files are stored OUTBOX Temporary directory for files to be sent ARCDIR Archive directory where files such as the Revision log are stored LOGDIR Directory for both log files monlog log and tiny log JobstartConfigFile Configuration file for job start StationsConfigFile Station configuration file Comprises the configuration parameters for the local station the neighbor station and routed stations HostAllowFile Configuration file containing DNS names or IP addresses of hosts that
47. hapters 5 3 1 5 3 2 and 5 3 3 Note The following commands are available as batch files in the SRVSTINY_HOME bin directory please see the chapter 1 2 for the explanation of SRVSTINY_HOME so you must change to this directory to be able to execute them e at first get the configuration of the RCI of the rvs Tiny station that should be administrated Use the program orderConfiguration for this step Example If you would like to administer the configuration of the rvs Tiny station TINY11 launch the program orderConfiguration in the command line with the following command orderConfiguration s TINY11 This command generates a configuration request file cfg req jar see the chapter 5 1 for the explanation of the meaning of cfg req jar and sends it via OFTP to the station TINY11 The transmission of the file cfg req jar may be watched in the rvs Tiny GUI Admin window When the RCI TINY11 receives the file cfg req jar the configuration process will be started The configuration process stops rvs Tiny station TINY11 archives the actual configuration in a file cfg rsp jar starts rvs Tiny TINY 11 again and sends the configuration container file cfg rsp jar back to the LCI rvs Tiny station of the administrator If this step was successful you will receive a message OrderConfiguration exited with return code 0 in the console All these steps are part of the program orderConfiguration and will be
48. ia rvs center center activate the rvs view information about receive jobs send jobs failed jobs and ended jobs display monitor messages delete or release EERPs End to End Response if necessary archive information about the processes send or receive jobs in the revision log define job filters and actions when sending or receiving files code conversion with various code conversion tables format conversion log files for tracing the Monitor activities and for troubleshooting rvs Tiny uses a batch interface and the file system to communicate with the application If capable to do so the linked application can indicate successful processing and have successful dispatch indicated rvs Tiny is implemented in Java Introduction TCP IP protocol At present rvs Tiny only supports the OFTP TCP IP protocol Note As rvs Tiny is planned to substitute the product rvsWIN there is a chapter 5 4 How to change from rvsWIN to rvs Tiny in this manual with some advices for the roll out procedure Supported platforms rvs Tiny is a Java application and therefore supports a wide range of platforms At the moment are the following installers availabe rvs Tiny for MS Windows XP with TCP IP rvs Tiny for MS Windows 2000 with TCP IP If you want an installer for another platform please contact us rvs after sales service phone 49 30 39971 777 fax 49 30 39971
49. is LOC and RVS for the rvs center SID This is a locally unique station ID which must consist of up to sixteen characters It is a strictly local definition remote stations do not have access to these names they only know the ODETTE IDs ODETTE_ID ODETTE ID is a worldwide unique identification of all nodes using the ODETTE file transfer protocol OFTP This 25 character name consists of the letter O an 18 character organization identifier provided by the ODETTE codification group and a6 character computer sub address that is administrated by each organization If you communicate within your own closed network only the ODETTE ID may be freely chosen as long as it remains unique in your network CONTACT Contact information to be further specified later these parameters are optional 24 Configuration NAME Name of the contact partner responsible for this station computer ENTERPRISE Company enterprise LOCATION Location STREET Street STREETNUMBER Street number DEPARTMENT Department PHONE Phone number FAX Fax number MAIL Email address INET Enterprise website FREETEXT At your disposal TCPIP_BASIC TCP IP parameters required for connection establishment IP_ADDR IP address or DNS name ofthe own or the partner station PORT Port on which a TCP IP listener is to be start
50. ive job with ID lt jobid gt Optional parameters a All available job information is given help Requests help information verbose Verbose message output Requests help information Example getJob n 040329173456000 rvs Tiny User Manual Rev 2004 08 23 49 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual Result job 040329173456000 RCV state ENDED Example getJob n 040329173456000 Result cx C WINDOWS System32 cmd exe 68 ENDED G Programs rvsTiny bin gt getJob n 040329173456000 a List job number 040329173456000 lt RCU sS C Programs rusT iny f iles inbox TESTFILE2 TESTFILE2 ENDED last change C Programs rvsTiny bin gt 4 8 Deleting or releasing EERPs handleEERP Use the handleEERP program to delete or release receipts EERP_OUT It is also possible to delete or release EERPs via the GUI Please see the chapter 4 7 Usage handleEERP r d lt num gt verbose Required parameters r d lt num gt ID of the job for which the EERP is to be released deleted Optional parameters help Requests help information verbose Verbose message output Requests help information 50 Working with rvs Tiny 4 9 Archiving the entries of processed send or receive jobs in the revision log archiveJobs The archiveJobs program creates a revision 1log file in the SRVSTINY_HOME rvsTiny archive directory this
51. may send rvs Tiny commands to the rvs Tiny server HostDenyFile Configuration file containing DNS names or IP addresses of hosts that may not send rvs Tiny commands to the rvs Tiny server Example Excerpt from rvsTinyConfig xml ttt HH tH HHH HF lt Environment gt lt DB gt c Programs rvsTiny jobs lt DB gt lt TEMP gt c Programs rvsTiny files temp lt TEMP gt lt INBOX gt c Programs rvsTiny files inbox lt INBOX gt lt OUTBOX gt c Programs rvsTiny files outbox lt OUTBOX gt lt ARCDIR gt c Programs rvsTiny archive lt ARCDIR gt lt JobstartConfigFile gt rvsTinyJobstart xml lt JobstartConfigFile gt lt StationsConfigFile gt rvsTinyStationlist xml lt StationsConfigFile gt lt MonlogStylesheet gt MonlogStylesheet xslt lt MonlogStylesheet gt lt PersistenceArchive gt RevisionLog xml lt PersistenceArchive gt lt HostAllowFile gt host allow lt HostAllowFile gt lt HostDenyFile gt host deny lt HostDenyFile gt lt RMIServiceName gt rvsTiny lt RMIServiceName gt 18 Configuration lt RMIServiceHost gt localhost lt RMIServiceHost gt lt JobQueueTimeout gt 3000 lt JobQueueTimeout gt lt Environment gt CVSTinyConfig xml H HHHHEEEEEE EHH EHH EH You can define and edit the paths for the DB TEMP INBOX OUTBOX LOGDIR and ARCDIR elements Example lt DB gt D rvsTiny jobs lt DB gt lt TEMP gt C Programs rvsTiny temp lt TEMP gt
52. n be shown via the GUI or via the command line How to start GUI please read the chapter 2 5 GUI Select the icon Transfer in the function bar The Transfer window opens with the sub entry Jobs in the Transfer tree Now you can select between the Active Receive Send Transmissions Ended Transmission and Failed Transmissions 46 Working with rvs Tiny A rys Tiny File View Customize B a F Send file j Admin gt Transfer fa Create New Transmission di Transmissions J Ej Active Receive Transmission Ay Active Send Transmissions f Ended Transmissions ag Failed Transmissions Qe Bi 3 Unknown localhost rvsTiny 1 4 0 vs Tiny beta 02 2004 Note A transfer is regarded as having been successfully completed when the ODETTE acknowledgement EERP End to End Response for this transfer has been received Single click on selected job sub ordner gives you an overview of all jobs in this ordner in the right hand window rys Tiny PEK File View Customize Help B lt gt Te dD Send file Transfer Stations Admin Help Exit gt Transfer E nn Active Receive Transmissions N Jobs ID Direction VDSN SID Status Created at Active Receive Transmissior 040816 receive MEETIN RVS EERFP_ 16 08 0 A Active Send Transmissions Ended Transmissions ag Failed Transmissions B 3 Unknown localhost rvsTi
53. nd parameters F lt format gt M lt length gt File name of the file to be sent Recipient station ID Virtual file name the length of the file name used for ODETTE transfer must not exceed 26 characters Format of the file to be sent T text file a stream of ASCII characters U unstructured binary byte stream V variable variable record length F fixed fixed record length The files in format F or V must be text files with the appropriate line record length Example If you want to send a file in format fixed with the record length 80 it must be a text file where each line has a length 80 without CR LF The following parameters are to be set F F M 80 maximal record length for the files in format F or V please see the examle for the parameter Format rvs Tiny User Manual Rev 2004 08 23 gedas deutschland GmbH Fachbereich rvs Systems 39 rvs Tiny User Manual I lt input code gt O lt output code gt t lt conversion table gt S lt serialize gt l lt label gt h verbose With the parameters input code and output code you can select one of the conversion tables that rvs Tiny offers The possible conversion tables are For ASCII EBCDIC conversion the following conversion tables are available ASCII IBM037 ASCH IBM237 ANSI IBM073 ANSI IBM273 For EBCDIC ASCII code conversion the following conversion tables are availa
54. nen 50 4 9 Archiving the entries of processed send or receive jobs in the revision log 51 5 rvs Tiny Central Administration errerreeeeeee neee ee nee ee eee enoe nene e ee He eHK KHK HK KK 53 5 1 Introduction ss 5 4 225 u la een een se MEN aan ZER Zila ees 53 5 2 Command Tools of the Central Administration keke k keke 54 5 3 How to work with the central administration features ueneenenensennennnennneennnnnnn 56 5 3 1 How to exchange a license key file J keke keke kk ee essen 57 5 3 2 How to change a station parameter nsenessesseesnnesnnenseennennnnnnennsenseennennesnnnsnnnnen 58 5 3 3 Howto make an update of rvs Tiny J eee eee eke ee ke keke keke k k k e ks 60 5 4 How to change from rvsWIN to rvs Tiny u eee ekere ke keke k ke ke 61 Index A K ye e ku r SE kut eez ee s k ca Ua Ses nE e e Ue Ea we e ik e Ee a k ye Ve Eku Ee se ee k we ar KV UA e Ua Se b K DE E WEN ee ke ie ia ek 63 rvs Tiny User Manual Rev 2004 08 23 3 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual Introduction 1 Introduction In this chapter you will find a short description of rvs and rvs Tiny as well as an explanation of typographic conventions used in the present manual 1 1 Short description of the system What is rvs rvs Rechner The abbreviation rvs stan
55. nowledge of the communications techniques in use TCP IP Before starting to work with rvs Tiny it is advisable to have read this book Installation on Windows systems 2 Installation on Windows systems The present chapter describes the system requirements as well as the rvs Tiny installation procedure 2 1 System requirements To successfully operate rvs Tiny you need the following software Software Operating system Windows XP or Windows 2000 Javaruntime environment JRE 1 3 1_XX or Java Software Development Kit 1 3 1 XX Please make sure a Java runtime environment is present on your system prior to installing rvs Tiny The software is freely available for download from http java sun com Initially you need at least 8 MB free space on your hard disk Depending on the amount of usage the retention period for old entries and the time between database cleanups the space requirement may be considerably larger At present rvs Tiny only supports the OFTP TCP IP protocol As a rule rvs Tiny ships on CD ROM or magtape Your system must be able to read these media Please contact your distributor if you have different requirements 2 2 Obtaining a license You need a license key to work with rvs Tiny rvs after sales Please contact the rvs after sales service phone 49 30 39971 777 fax 49 service 3039971 994 email rvs service gedas de to receive a license key To purchase a license ke
56. ny 1 4 0 vs Tiny beta 02 2004 By double clicking on a job line in the right hand section of the window you can obtain a detailed view of the relevant job rvs Tiny User Manual Rev 2004 08 23 47 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual Release EERP OUT Delete EERP OUT Delete Release Job getJobList rys Tiny File View Customize Help L Si m a Send file Transfer Stations Admin gt Transfer T create NewTransmission receive Transmission Zl Jobs Parameter ge Active Receive Transmission ID 040816144222000 D Active Send Transmissions Ended Transmissions 4 Failed Transmissions Filename e wrvsinvs JavalrysTiny files inbox MEETIN Direction receive VDSN MEETIN SID RVS Created at 16 08 04 14 42 22 Status EERP_HOLDED Last Change 16 08 04 14 42 22 Bytes transmitted 213504 n 5 Releas Delete Show Show Er Active Receive Transmissions If you click on the line Active Receive Transmission and then double click on a particular job line you will see all details about the particular receive job in transmission With the buttons in this right hand window you can change the status of the EERP_ OUT for this particular job The Button Release releases the EERP_OUT in status Hold status EERP HOLDED The Button Delete deletes the EERP_OUT The same functionality
57. o obtain the new license key please read the chapter NYO02 you must send the whole directory C rvsTiny management mqmt UPDATE_STATION_040828_113315 workspace TINYO2 with the command commitUpdateStation bat s TINYO2 C rvsTiny manage workspace TINYO2 ment mgmt d UPDATE_STATION_040828_113315 This command will store the whole modified directory and send it to the station TINYO2 again as a file cE g req jar After successfully receiving the file cf g req jar at the station T INY02 rvs Tiny at TINYO2 will be stopped it happens all with the process commitUpdateStation you do not have to do any particular steps the modified configuration will be updated the update job checks if all was correct and sends back a response as a file cfg rsp jar The result of the update is again logged in the file activity log Note In case of non success the old configuration will be activated again 5 3 2 How to change a station parameter This chapter describes a typical case in administrating rvs Tiny how to change a rvs Tiny parameter e g the ODETTE ID It is the same procedure for changing any other rvs Tiny parameter In this example the station TINY20 will administrate the station T 1 INY22 Prerequisites The station TINY2O must have the station TINY22 in the station table as routed station via the rvs center please read the chapter
58. on S Y the files will be sent in the same order as the send jobs were created The next job will only be sent if the previous is completely finished All send jobs for the serialization must have the same LABEL In the GUI the VDSN will be used as label In the command line you can specify your own label Name of group of serialized send jobs User specified descriptive label for this job If you do not specify this parameter the VDSN will be used as a label count of send attempts for synchronized transmission time out for synchronized transmission in seconds format description for converter step 1 format description for converter step 2 optional stylesheet for converter step 1 optional converter direction for converter step 1 default EDI2XML converter direction for converter step 2 default XML2EDI log level for converter default 0 line feed behaviour for the EDI message output 0 no LF as segment separator 1 LF as segment separator default identation for XML output 0 no identation 1 identation on default encoding for the XML output default UTF 8 rvs Tiny User Manual Rev 2004 08 23 gedas deutschland GmbH Fachbereich rvs Systems 45 rvs Tiny User Manual Examples convertAndSend d C teil56 txt s RVS v TEILE za 4 In this example the C teil56 txt file is sent to the rvs center RVS with a virtual name TEILE count of send attempts is limited to
59. one jobFilter applies to the send or receive job It is possible to customize JobStarts via the GUI or via the JobStart configuration file Customizing via GUI At first you should open the Administration window selecting the Admin icon in the function bar Then select the item Jobstart in the Administration tree on the left size How to start GUI read please in the chapter 2 5 It is possible to chosse between Jobstarts in receive direction and Jobstarts in send direction A Jobstart in receive direction is equivalent to a resident receive entry in rvs A Jobstart in send direction is equivalent to a Jobstart after send attempt in rvs A new Jobstart will be created with a right click on a Jobstart after receive or a Jobstart after send attempt in the Administration tree Add new entry To select the already existing Jobstart double click the appropriate line of the appropriate JobStart in the right hand window The following JobFilters entries are possible Direction SID VDSN Process and SendAttempts Please refer to the table of the JobFilters for a detailed description Customizing via XML configuration file rvsTinyJobstart xml Like most of the other rvs Tiny configuration files this file is in the XML format as well lt jobstarterData gt lt jobfilters gt lt jobfilter gt lt vdsn gt lt vdsn gt lt sid gt lt sid gt rvs Tiny User Manual Rev 2004 08 23 29 gedas deutschland GmbH Fachbereich r
60. parameters En rys Tiny File View Customize Help B lt gt Ta Send file Transfer Stations Admin lt Transfer amiCreate New Transmission qi Jobs Active Receive Transmission A Active Send Transmissions Er ded Transmissions ag Failed Transmissions RVS C FM TEST nstallation rtf INSTALLATION U unstructured N no 0 E 3 Unknown localhost rvsTiny 1 4 0 rvs Tiny beta 022004 Required parameters SID Recipient station ID File File name of the file to be sent VDSN Virtual file name the length of the file name used for ODETTE transfer must not exceed 26 characters rvs Tiny User Manual Rev 2004 08 23 37 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual Optional send parameters Format Serialization MaxRecl Conversion table h verbose Command Line createSendJob command line Use the createSendJob program to send a file to the rvs Format of the file to be sent T text file a stream of ASCII characters U unstructured binary byte stream V variable variable record length F fixed fixed record length The files in format F or V must be text files with the appropriate line record length Example If you want to send a file in format fixed with the record length 80 it must be a text file where each line has a length 80 without CR LF
61. particular steps the modified configuration will be updated the update job checks if all was correct and sends back a response as a file cfg rsp jar The result of the update is again logged in the file activity log Note In case of non success the old configuration will be activated again 5 4 How to change from rvs WIN to rvs Tiny In this chapter are described the special circumstances for the user who would like to change from rvsWIN to rys Tiny rvsWIN is a File Transfer Application under MS Windows in connection with rvsMVS It is not based on OFTP Odette File Transfer Protocol It is an 3270 emulation with a SNA Line rys Tiny is an OFTP based file transfer solution for large star topology networks comprising several hundred remote stations It is implemented in Java please read the chapter 2 1 about the system requirements JRE 1 3 1_XX or Java Software Development Kit 1 3 1_XX The following steps are necessary if you want to change from rvsWIN to rvs Tiny the new rvs Tiny installation setup program the valid license key file license properties Please read the chapter 2 2 for the explanation how to obtain the rvs Tiny license In the installation procedure of rvs Tiny are some mandatory parameters that didn t exist in rvs WIN These are ODETTE ID please refer to chapter 3 2 3 for the explanation how to obtain this ID TCP IP Address or the hostname it is the IP a
62. prepareUpdateStation bat s TINY33 Result The directory C rvsTiny management mgmt workspace T INY33 UPI DATE_STAT ON__0 4 out with the complete configuration of the station T created If this action was successful you will find a corresponding message in the file activity log 0830_113315 NY 33 will be Now you must rename the old jar file rvstiny jar from the directory C rvsTiny management mgmt workspace T NY33 UP DATE_STAT out libto rvstinyOL ON__040830_113315 D jar and replace it with the new one Please contact us to receive the actual files for the update E Mail rvs service gedas de Tel 49 30 39971 777 fax 49 30 39971 994 Send the modified configuration to T NY33 station you must send the whole directory C rvsTiny management mgmt workspace T with the command NY33 UP DATE_STAT commitUpdateStation bat s TI C rvsTiny management mgmt workspace T INY33 INYO2 UPI DATE_STAT ON_040830_113315 d LON_040830_113315 This command will store the whole modified directory and send it to T INY33 again as a file cfg req jar 60 rvs Tiny Central Administration e After successfully receiving the file cEg req jar at the station TINY 33 rvs Tiny of TINY33 will be stopped it all happens with the process commitUpdateStation you do not have to do any
63. r Choose Insine Dy zere G Cancel Previous Next Define the program group to install rvs Tiny icons to in the fourth dialog 2 rvs Tiny 2 0 RC3 Choose Shortcut Folder Where would you like to create product icons In anew Program Group rvsTiny In an existing Program Group usa o l In the Start Menu On the Desktop other Choose Dont create icons Create Icons for All Users InsiellAnyehere by zen G Cancel Define the Java runtime environment for rvs Tiny operation in the next dialog The installer searches for installed components and proposes the versions found in a dialog rvs Tiny has been released for use from version 1 3 1_X onwards 12 Installation on Windows systems SI rvs Tiny 2 0 RC3 Choose Java Virtual Machine Please Choose a Java VM for Use by the Installed Application C jdk1 3 1_01Wbinijava exe CAjdk1 3 1_01 jreibin java exe C Programme WavaSoftJREW 3 1 bin java exe Search For Others Choose Another InsiallAnywhere hy zern G Cancel Previous f The following dialogs deal with the settings in the station list You must first configure the entry for the local station The three parameters in the dialog are mandatory and must be specified Please read the chapter 3 2 for more information about setting station parameter e g how to obtain the ODETTE ID 2 rvs Tiny 2 0 RC3 Local Station Pleas
64. r routed stations this completes the station configuration sending and receiving files is now possible rvs Tiny User Manual Rev 2004 08 23 19 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual 3 2 1 Customizing stations via GUI To start the GUI use the program startGUI Usage startGUI local All parameters are optional local starts the OFTP server module in the same process as the GUI no transmission of data will be possible without the GUI running an already running OFTP server process might lead to errors help Requests help information Requests help information After the successfull start of the GUI the following window appears rvs Tiny PEK File View Customize Help a ws Send file Transfer Stations Admin gt Transfer X gt fa Create New Transmission gt Transfer Eg Jobs Active Receive Transmission Transfer allows the creation of new send job entries A Active Send Transmissions and the control of existing jobs Ended Transmissions A Wax Failed Transmissions AR w E Possible activities are Creation of new send entries viewing and managing of jobs viewing and conversion of received files 5 Unknown localhost rvsTiny 1 4 0 rvs Tiny beta 02 2004 To open the station window select the Stations icon in the function bar 20 Configuration n 5 A rys Tiny File View Customiz
65. rent Monitor messages and to analyze error messages if applicable GUI Select the Admin icon in the function bar of rvs Tiny GUI The Administration window opens with the Admin tree and the sub entry Log Messages How to start of rvs Tiny GUI please read the chapter 2 5 Placing a tick in the box marked Receive log messages allows you to view the messages from the SRVSTINY_HOME rvsTiny log monlog log file Only messages occuring after the GUI is started will be displayed 34 Working with rvs Tiny A rvs Tiny File View Customize Help B lt gt Send file Transfer a 7 1 Stations Admin Exit A Administration B Stations B Jobstart XO after receive after send attemps Parameter DD Server Log Messages receive log messages on protocol RECEIVED_F_PDU Received OFTP Event SSID Start protocol SENT_F_PDU Sent OFTP Event SSID Start Sessior protocol RECEIVED _F PDU Received OFTP Event SFID Start controller CREATE_RECEIVEJOB New ReceiveJob got createc protocol SENT_F_PDU Sent OFTP Event SFPA Start File Pc Line Wrap Command Line BG Unknown localhost vsTiny 1 4 0 rvs Tiny beta 0212004 Use the showMonitorLog program to trace the current Monitor messages and to analyze error messages if applicable Usage showMonitorLog Optional parameters verbose help verbose Verbose message output
66. s being established REC_PW EX_BUF_CRE For future application not being evaluated EX_BUF_SIZ For future application not being evaluated rvs Tiny User Manual Rev 2004 08 23 gedas deutschland GmbH Fachbereich rvs Systems 27 rvs Tiny User Manual JEERP_OUT Procedure for sending receipts EERPS NORMAL Generation of a receipt after successful file reception and immediate active transmission HOLD Generation of a receipt after successful file reception The receipt however is only sent after having been released with the handleEERP program Default NORMAL TCPIP_BASIC TCP IP parameters required for connection establishment IP_ADDR IP address or DNS name of the own or the partner station PORT Port on which a TCP IP listener is to be started 3305 by default Routing station 3 2 6 STATION_RT station entry This entry defines for each rvs station through which neighbors it can be reached lt STATIO lt SID lt ODE lt GAT lt CON eRe gt ROUTEDSTATION lt SID gt TTE_ID gt OROUT lt ODETTE_ID gt EWAY_STATION_NK gt RVS lt GATEWAY_STATION_NK gt TACT gt lt NAME gt lt lt lt lt lt A ATA NCA lt CO lt ODE lt lt OD lt STATI ENTERPRISE gt LOCATION gt STREET gt STREET_NUMBER gt DEPARTMENT gt PHONE gt FAX gt AIL gt INET gt FREETEXT gt
67. t Date gt lt Time gt 170027 lt Time gt lt Static gt lt Dynamic gt lt RestartPos gt 0 lt RestartPos gt lt RecCount gt 0 lt RecCount gt lt FilePos gt 19 lt FilePos gt lt RevBytes gt 0 lt RcevBytes gt lt SendAttempts gt 0 lt SendAttempts gt lt Status gt WF_EERP lt Status gt lt Dynamic gt lt Job gt IV s Tiny copies the job into the ENDED directory if it has been successfully terminated e g after an EERP has been received The FAILED directory holds jobs that could not be successfully processed Possible states for Send Jobs RESTART 1 wait after error to send file again WF SFID_ANSWER 2 wait for answer for already sent SFID WF_CDT 3 wait for credit renewal WF_EFID ANSWER 4 wait for answer to already sent EFID WF_EERP 5 wait for EERP ENDED 6 send job has ended ENDED_WITH_JS_ERROR 7 send job run into error during call of jobstart FATAL _ERROR 8 send job run into fatal error Possible states for Receive Jobs RESTART wait after error to receive file again RESTART AFTER EFNA 2 File could not be delivered EFNA sent or not Assuming partner will send file again RESTART AFTER EFPA_FAILURE 3 File already delivered but EFPA failed Assuming partner will send file again RECEIVING 4 Receiving file data after EFPA EERP_HOLDED 5 File was completely received EERP is on hold and needs to get released EERP RELEASED 6 User released EERP
68. tions Jobstart 040813123501000 Jobstart KO after receive Parameter Value after send attemps 040813123501000 g Parameter receive Log Messages ROU123 test_OFTP12 C iresentr bat Delete B 3 Unknown localhost rvsTiny 1 4 0 rvs Tiny beta 02 2004 Example GUI If rvs Tiny sends successfully SendAt tempt s 0 a file with the virtual file name test 888 to the rvs center RVS the program C sendjob bat will be started A rvs Tiny File View Customize Help B J amp Send file Transfer Stations Admin vA Administration I stations Jobstart 040813123548000 Jobstart KO after receive Parameter Value after send attemps ID 040813123548000 Parameter send Log Messages RYS test 888 C sendjob bat 0 ae ___8 pe LE fulare changes vsTiny 1 4 0 rvs Tiny beta 02 2004 rvs Tiny User Manual Rev 2004 08 23 31 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual Delete a JobStart If you want to delete a JobStart select it at first with a double click Now you can remove it with the Delete button 32 Working with rvs Tiny 4 Working with rvs Tiny Batch files The present chapter describes all programs available for everyday use of rvs Tiny These programs are located as batch files in the SRVSTINY_HOME bin dire
69. vs Systems rvs Tiny User Manual lt direction gt SND lt direction gt lt sendAttempts gt 0 lt sendAttempts gt lt process gt C jobstart bat lt process gt lt jobfilter gt lt jobfilter gt lt jobfilter gt lt jobfilters gt lt jobstarterData gt This file comprises any number of jobFilter elements The table below gives a detailed description of individual jobFilter sub elements vdsn Virtual file name regular expression as filter sid Station ID regular expression as filter for the station ID direction Defines filter rules for the communication direction Possible values SND when sending files RCV when receiving files sendAttempts Number of failed attempts to send Successful file transmission is indicated by 0 here process mandatory Program to be started when all filter conditions apply A defined set of parameters is passed to the programs Parameters 1 jobId 2 Station ID of sender or recipient 3 File name of the file sent or received 4 VDSN 5 Date and time of the job 6 Number of attempts to send Example GUI If rvs Tiny receives a file with the virtual filename test_OFTP12 froma routed station ROU123 the program C resentr bat will be started 30 Configuration A rvs Tiny File View Customize Help L SS m a I Send file Transfer Stations Admin Exit vA Administration IB sta
70. with the option s for stationID Example commitUpdateStation bat s TINYPW d C rvsTiny management mgmt workspace TINYPW UPDATE_STATION _040826_114418 Note The name of the WorkDir directory consists of CRep see 5 1 RCT SID TINYPW in the table example directory UPDATE_STATION with the timestamp consisting of date and time in the table example 040826_114418 and the directory out WorkDir contains all essential rvs Tiny directories and files By changing these files the following configuration actions for example are possible Modify station configuration by modifying RVSTINY_HOME conf rvsTinyStationlist xml Modify jobstarts by modifying SRVSTINY_HOME conf rvsTinyJobstart xml Update the software by replacing jar files in the directory SRVSTINY_HOME 1lib rvs Tiny User Manual Rev 2004 08 23 55 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual 5 3 How to work with the central administration features The following steps will show you the typical configuration run It may be used as a basic example when a rvs Tiny network administrator deals with rvs Tiny Central Administration These steps are always necessary independent of the fact whether you want to make an update change some rvs Tiny parameter or exchange the license key file More details about the particular administation tasks you will find in the c
71. y Type hostname in the command prompt window Run gt cmd Send the command output your computer name e g BWcd000 34 to the rvs after sales service Please make sure to heed upper and lowercases as otherwise a valid license key for your computer cannot be generated You will be sent your license key file by email Save the license key file in the SRVSTINY_HOME conf directory as license properties Note Please read the chapter 1 2 for the explanation of SRVSTINY_HOME rvs Tiny User Manual Rev 2004 08 30 9 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual 2 3 Fresh install of rvs Tiny Installation steps This chapter describes the installation of rvs Tiny Please read the chapter 2 1 System requirements before installing Start Windows and log in as a Windows user with administrator rights e Start the rvsTiny_X X_setup exe installer where X X indicates the rvs Tiny version number by double clicking or using the Windows command Start gt Run e Choose the installation language German English Spanish in the first dialog Click lt OK gt to go to the next installation step 10 Installation on Windows systems The second dialog gives a brief introduction to the installation procedure 2 rvs Tiny 2 0 RC3 Introduction InstallAnywhere will guide you through the installation of rvs Tiny 2 0 RC3 lt is strongl
72. y recommended that you quit all programs before continuing with this installation Click the Next button to proceed to the next screen Ifyou want to change something on a previous screen click the Previous button You may cancel this installation at any time by clicking the Cancel button AAPA AAT AVAlE aie Cancel Previous Inthe next dialog you can select between Typical Complete or Minimal installation Complete Installation is necessary if you want to execute the central administration commands such as update rvs Tiny at another rvs Tiny station modify configuration of another rvs Tiny stations 2 rvs Tiny 2 0 RC3 Choose Product Features Typical nssTiny will be installed without Remote Administration commands This option is recommended for most users Complete rvsTiny will be installed including Remote Administration commands This option is recommended for rvsTiny network administrators Minimal Only required application features will be installed This option is recommended only for users with limited disk space InsialAnywwhere ly Zero G Cancel Previous Choose the rvs Tiny installation directory in the third dialog rvs Tiny User Manual Rev 2004 08 30 11 gedas deutschland GmbH Fachbereich rvs Systems rvs Tiny User Manual rvs Tiny 2 0 RC3 x Choose Install Folder Where Would You Like to Install CAProgramsirssTiny Restore Default Folde

rvs Tiny - ServiceNet

Contents

Download Pdf Manuals

Related Search

Related Contents