Janus FTP Server examples - Revision history

JAL2: /* See also */

2012-02-21T16:52:14Z

JAL2: /* A simple development environment */

2012-02-21T01:52:34Z

A simple development environment

← Older revision		Revision as of 01:52, 21 February 2012
Line 11:		Line 11:
	<li>Test as well as production procedure files, each type defined		<li>Test as well as production procedure files, each type defined
	within its own folder (<code>/TEST</code> and <code>/PROD</code>).		within its own folder (<code>/TEST</code> and <code>/PROD</code>).
	These are set up with <var>JANUS FTP ASSIGN</var>.		These are set up with <var>[[Janus FTP Server command reference#JANUS FTP ASSIGN\|JANUS FTP ASSIGN]]</var>.
	<li>Everyone can read from the test procedure file.		<li>Everyone can read from the test procedure file.
	This is set up with the <var>DEFAULTPRIVS</var> parameter on the <var>ASSIGN</var> for <code>/TEST</code>.		This is set up with the <var>DEFAULTPRIVS</var> parameter on the <var>ASSIGN</var> for <code>/TEST</code>.
Line 18:		Line 18:
	then reference the group using the <var>USRGROUP</var> parameter.		then reference the group using the <var>USRGROUP</var> parameter.
	<li>All developers can update the test procedure file.		<li>All developers can update the test procedure file.
	This is set up with the <var>JANUS FTP ALLOW</var> for <code>/TEST</code>.		This is set up with the <var>[[Janus FTP Server command reference#JANUS FTP ALLOW\|JANUS FTP ALLOW]]</var> for <code>/TEST</code>.
	<li>All developers can read the production procedure file.		<li>All developers can read the production procedure file.
	This is set up with the first <var>JANUS FTP ALLOW</var> for <code>/PROD</code>.		This is set up with the first <var>JANUS FTP ALLOW</var> for <code>/PROD</code>.
Line 24:		Line 24:
	This is set up with the second <var>JANUS FTP ALLOW</var> for <code>/PROD</code>.		This is set up with the second <var>JANUS FTP ALLOW</var> for <code>/PROD</code>.
	<li>Everyone has the test area as a home folder.		<li>Everyone has the test area as a home folder.
	This is set up with the <var>HOME</var> that references <var>ALL</var>.		This is set up with the <var>[[Janus FTP Server command reference#JANUS FTP HOME\|JANUS FTP HOME]]</var> that references <var>ALL</var>.
	<li>There will be no anonymous FTP access (no <var>ANONYMOUS</var>		<li>There will be no anonymous FTP access (no <var>ANONYMOUS</var>
	parameter is specified on the <var>JANUS DEFINE</var> for the FTP Server).		parameter is specified on the <var>[[Janus FTP Server command reference#JANUS DEFINE for FTP\|JANUS DEFINE]]</var> for the FTP Server).
	<li>Active FTP is supported (perhaps the whole system is behind a firewall,		<li>Active FTP is supported (perhaps the whole system is behind a firewall,
	so there is no exposure, and active permits a greater variety of FTP clients).		so there is no exposure, and active permits a greater variety of FTP clients).
Line 33:		Line 33:
	<li>Specifying a <var>CLIENTSOCKET</var> value on the <var>JANUS		<li>Specifying a <var>CLIENTSOCKET</var> value on the <var>JANUS
	DEFINE</var> for the <code>FTPDEVEL</code> FTP server		DEFINE</var> for the <code>FTPDEVEL</code> FTP server
	<li>Defining a <var>CLSOCK</var> port whose name is the <var>CLIENTSOCKET</var> value		<li>Defining a <var>[[JANUS DEFINE#type\|CLSOCK]]</var> port whose name is the <var>CLIENTSOCKET</var> value
	</ol>		</ol>
	</ul>		</ul>
Line 79:		Line 79:
	JANUS START FTPDCLIENT		JANUS START FTPDCLIENT
	</p>		</p>

	==A simple anonymous FTP Server==		==A simple anonymous FTP Server==
	This example sets up a public anonymous FTP Server		This example sets up a public anonymous FTP Server

JAL2: /* FTP client and server interaction */

2012-02-21T01:44:21Z

FTP client and server interaction

← Older revision		Revision as of 01:44, 21 February 2012
Line 150:		Line 150:
	a matching folder structure is predefined for the server).		a matching folder structure is predefined for the server).
	For more information about defining these folder structures,		For more information about defining these folder structures,
	see <var>[[#JANUS FTP ASSIGN\|JANUS FTP ASSIGN]]</var>.		see <var>[[Janus FTP Server command reference#JANUS FTP ASSIGN\|JANUS FTP ASSIGN]]</var>.

	Since the <var class="product">Janus FTP Server</var> uses a Janus socket port and supports the		Since the <var class="product">Janus FTP Server</var> uses a Janus socket port and supports the

JAL2 at 01:39, 21 February 2012

2012-02-21T01:39:14Z

← Older revision		Revision as of 01:39, 21 February 2012
Line 243:		Line 243:
	</th><td>For a display of the FTP-specific settings like folder mappings and user permissions		</th><td>For a display of the FTP-specific settings like folder mappings and user permissions
	</td></tr></table>		</td></tr></table>

			==See also==
			The following topics complete the description of <var class="product">Janus FTP Server</var> support:
			<ul>
			<li>[[Janus FTP Server]]
			<li>[[Overriding FTP protocol commands]]
			<li>[[Janus FTP Server command reference]]
			<li>[[Integrating Janus FTP and Janus Web Server]]
			</ul>

	[[Category:Janus FTP Server]]		[[Category:Janus FTP Server]]

JAL2 at 01:10, 21 February 2012

2012-02-21T01:10:48Z

← Older revision		Revision as of 01:10, 21 February 2012
Line 1:		Line 1:
	The ~~two short~~ examples in the following subsections		The examples in the first two of the following subsections
	show how to set up <var class="product">Janus FTP Server</var>s in an online.		show how to set up <var class="product">Janus FTP Server</var>s in an online.
	The Janus FTP commands in the examples are introduced in [[Janus FTP Server#Janus FTP Server command overview\|"Janus FTP Server command overview"]] and described in greater detail in [[Janus FTP Server command reference\|"Janus FTP Server command reference"]]. The [[FTP client and server interaction\|"FTP client and server interaction"]] subsection looks at examples of tracing messages for an attempted file transfer in two different FTP environments.		The Janus FTP commands in the examples are introduced in [[Janus FTP Server#Janus FTP Server command overview\|"Janus FTP Server command overview"]] and described in greater detail in [[Janus FTP Server command reference\|"Janus FTP Server command reference"]]. The [[#FTP client and server interaction\|"FTP client and server interaction"]] subsection looks at examples of tracing messages for an attempted file transfer in two different FTP environments.

			__TOC__

	==A simple development environment==		==A simple development environment==
	In this example, a <var class="product">Janus FTP Server</var> is set up for a		In this example, a <var class="product">Janus FTP Server</var> is set up for a

JAL2 at 01:07, 21 February 2012

2012-02-21T01:07:07Z

← Older revision		Revision as of 01:07, 21 February 2012
Line 1:		Line 1:
	The ~~following~~ two short examples		The two short examples in the following subsections
	show how to set up <var class="product">Janus FTP Server</var>s in an online.		show how to set up <var class="product">Janus FTP Server</var>s in an online.
	The Janus FTP commands in the examples are introduced in [[Janus FTP Server#Janus FTP Server command overview\|"Janus FTP Server command overview"]] and described in greater detail in [[Janus FTP Server command reference\|"Janus FTP Server command reference"]].		The Janus FTP commands in the examples are introduced in [[Janus FTP Server#Janus FTP Server command overview\|"Janus FTP Server command overview"]] and described in greater detail in [[Janus FTP Server command reference\|"Janus FTP Server command reference"]]. The [[FTP client and server interaction\|"FTP client and server interaction"]] subsection looks at examples of tracing messages for an attempted file transfer in two different FTP environments.

	==A simple development environment==		==A simple development environment==

JAL2: /* FTP client and server interaction */

2012-02-21T00:52:42Z

FTP client and server interaction

← Older revision		Revision as of 00:52, 21 February 2012
Line 200:		Line 200:
	The <var class="product">FTP Server</var> dynamically creates a server socket (to which		The <var class="product">FTP Server</var> dynamically creates a server socket (to which
	the FTP client connects for the transfer of the file), which runs on a		the FTP client connects for the transfer of the file), which runs on a
	separate thread in the ~~online~~.		separate thread in the Online.
	When the transfer is done (successfully or not), the dynamically created		When the transfer is done (successfully or not), the dynamically created
	socket thread terminates, and the audit trail records a soft restart.		socket thread terminates, and the audit trail records a soft restart.

JAL2 at 23:04, 17 February 2012

2012-02-17T23:04:02Z

← Older revision		Revision as of 23:04, 17 February 2012
Line 1:		Line 1:
	The following two short examples		The following two short examples
	show how to set up <var class="product">Janus FTP Server</var>s in an online.		show how to set up <var class="product">Janus FTP Server</var>s in an online.
	The Janus FTP commands in the examples are introduced in [[Janus FTP Server command overview\|"Janus FTP Server command overview"]] and described in greater detail in [[#Janus FTP Server command reference\|"Janus FTP Server command reference"]].		The Janus FTP commands in the examples are introduced in [[Janus FTP Server#Janus FTP Server command overview\|"Janus FTP Server command overview"]] and described in greater detail in [[Janus FTP Server command reference\|"Janus FTP Server command reference"]].

	==A simple development environment==		==A simple development environment==

JAL2 at 22:38, 17 February 2012

2012-02-17T22:38:35Z

← Older revision		Revision as of 22:38, 17 February 2012
Line 241:		Line 241:
	</th><td>For a display of the FTP-specific settings like folder mappings and user permissions		</th><td>For a display of the FTP-specific settings like folder mappings and user permissions
	</td></tr></table>		</td></tr></table>

			[[Category:Janus FTP Server]]

JAL2: Created page with "The following two short examples show how to set up `Janus FTP Server`s in an online. The Janus FTP commands in the examples are introduced in [[Janus FT..."

2012-02-17T22:38:07Z

Created page with "The following two short examples show how to set up <var class="product">Janus FTP Server</var>s in an online. The Janus FTP commands in the examples are introduced in [[Janus FT..."

New page

The following two short examples
show how to set up <var class="product">Janus FTP Server</var>s in an online.
The Janus FTP commands in the examples are introduced in [[Janus FTP Server command overview|"Janus FTP Server command overview"]] and described in greater detail in [[#Janus FTP Server command reference|"Janus FTP Server command reference"]].

==A simple development environment==
In this example, a <var class="product">Janus FTP Server</var> is set up for a
development environment with the following characteristics.
<ul>
<li>Test as well as production procedure files, each type defined
within its own folder (<code>/TEST</code> and <code>/PROD</code>).
These are set up with <var>JANUS FTP ASSIGN</var>.
<li>Everyone can read from the test procedure file.
This is set up with the <var>DEFAULTPRIVS</var> parameter on the <var>ASSIGN</var> for <code>/TEST</code>.
<li>A Janus user group is used for the development team.
This allows fewer FTP commands to be used, since the <var>ALLOW</var> commands can
then reference the group using the <var>USRGROUP</var> parameter.
<li>All developers can update the test procedure file.
This is set up with the <var>JANUS FTP ALLOW</var> for <code>/TEST</code>.
<li>All developers can read the production procedure file.
This is set up with the first <var>JANUS FTP ALLOW</var> for <code>/PROD</code>.
<li>Only the team leader (Moe) can update production.
This is set up with the second <var>JANUS FTP ALLOW</var> for <code>/PROD</code>.
<li>Everyone has the test area as a home folder.
This is set up with the <var>HOME</var> that references <var>ALL</var>.
<li>There will be no anonymous FTP access (no <var>ANONYMOUS</var>
parameter is specified on the <var>JANUS DEFINE</var> for the FTP Server).
<li>Active FTP is supported (perhaps the whole system is behind a firewall,
so there is no exposure, and active permits a greater variety of FTP clients).
Active is enabled by:
<ol>
<li>Specifying a <var>CLIENTSOCKET</var> value on the <var>JANUS
DEFINE</var> for the <code>FTPDEVEL</code> FTP server
<li>Defining a <var>CLSOCK</var> port whose name is the <var>CLIENTSOCKET</var> value
</ol>
</ul>

The commands for the development FTP Server follow.
Notice that to enable active transfers,
the client (<var>CLSOCK</var>) port must be started as well as the main FTP port.
* Create the development team
JANUS DEFUSG STOOGES MOE LARRY CURLEY SHEMP GLW
* FTP server on port 3000
JANUS DEFINE FTPDEVEL 3000 -
FTPSERVER 4 -
CLIENTSOCKET FTPDCLIENT -
AUDTERM -
PASVPORT 3001 -
BINDADDR 198.242.244.100
* Client port definition for active transfers
JANUS DEFINE FTPDCLIENT * -
CLSOCK 5 REMOTE * * -
SOCKPMAX 5
JANUS CLSOCK FTPDCLIENT ALLOW

* Set up ftp access to test area.
* By default, all users can read it.
JANUS FTP FTPDEVEL ASSIGN /TEST TO FILE FTPTEST DEFAULTPRIVS READ
* Set up ftp access to prod area.
* There is no default access.
JANUS FTP FTPDEVEL ASSIGN /PROD TO FILE FTPPROD

* All developers can update test.
JANUS FTP FTPDEVEL ALLOW /TEST -
WRITE TO USGROUP STOOGES
* All developers can read prod.
JANUS FTP FTPDEVEL ALLOW /PROD -
READ TO USGROUP STOOGES
* Moe is the boss; he can update production.
JANUS FTP FTPDEVEL ALLOW /PROD -
WRITE TO USER MOE

* All start out with test as a home folder.
JANUS FTP FTPDEVEL HOME /TEST TO ALL

* Start them up.
JANUS START FTPDEVEL
JANUS START FTPDCLIENT


==A simple anonymous FTP Server==
This example sets up a public anonymous FTP Server
from which files may be downloaded —
a great way to distribute files.
It has the following characteristics:
<ul>
<li>A single folder, <code>/PUB</code>, that anonymous users read from to download files.
<li>The big boss, <code>Moe</code>, is the only one who can upload files to the server.
<li>Prefixing, using the default slash character (<tt>/</tt>), is displayed (see
the <var>PREFIX</var> parameter on the <var>FTP ASSIGN</var> command for <code>/PUB</code>).
<li>Only passive FTP file transfers are permitted (no <var>CLIENTSOCKET</var> is
specified on the <var>JANUS DEFINE</var> command).
</ul>

The commands for an anonymous FTP Server follow:
* Create FTP server on port 2121, anonymous allowed,
* only passive access is provided.
JANUS DEFINE FTPANON 2121 FTPSERVER 10 -
ANONYMOUS * -
AUDTERM -
PASVPORT 2555 -
BINDADDR 198.242.244.100

* Create public folder and use prefixing.
JANUS FTP FTPANON ASSIGN /PUB TO FILE FTPTEST PREFIX
* Grant Anonymous read access to the /PUB folder.
JANUS FTP FTPANON ALLOW /PUB READ TO ANONYMOUS
* Make user MOE the only person who can place files
* in the Anonymous FTP area.
JANUS FTP FTPANON ALLOW /PUB WRITE TO USER MOE

* Make /PUB the home folder for Anonymous users and Moe.
JANUS FTP FTPANON HOME /PUB TO ANONYMOUS
JANUS FTP FTPANON HOME /PUB TO USER MOE

JANUS START FTPANON
JANUS DISPLAYSOCK FTPANON


After connecting to the FTP server from his
FTP client, <code>MOE</code> puts/uploads the <code>README</code> file into his home folder, <code>/PUB</code>.
A fragment from a <var>DISPLAY PROC LIST</var> result for the <code>FTPTEST</code> file
confirms the prefixing used in the example.
Procedure <code>README</code> is stored with the folder name as a prefix:
/PUB/README 10/07/04 12:08:28 124 MOE


==FTP client and server interaction==
To connect to the Janus FTP server,
FTP clients must specify (in the way that is appropriate for the particular tool)
both the host ID and port of the FTP server.
A command line client trying to connect to the <var class="product">Janus FTP Server</var> defined in
[[#A simple anonymous FTP Server|"A simple anonymous FTP Server"]], for example,
might use:
open 198.242.244.100 2121


The FTP server correctly handles the type of upload (text or binary) that the client FTP package indicates.
This indication may be from an explicit user selection of a type,
or it may be from an FTP client that auto detects the appropriate mode.
By default, the server assumes type <code>A</code>
(ASCII, with translation to EBCDIC) until notified otherwise.

Users can upload multiple files at a time
(in the way that is appropriate for the particular client tool),
although the protocol dictates that multiple-file requests be
handled internally as multiple individual-file transfers.
Users can also upload directories and subdirectories (if and only if
a matching folder structure is predefined for the server).
For more information about defining these folder structures,
see <var>[[#JANUS FTP ASSIGN|JANUS FTP ASSIGN]]</var>.

Since the <var class="product">Janus FTP Server</var> uses a Janus socket port and supports the
<var>[[TRACE (JANUS DEFINE parameter)|TRACE]]</var> parameter (<var>JANUS DEFINE</var> command) and <var>[[JANUS TRACE]]</var> command for the port, you can debug your FTP application by setting <var>TRACE</var> and viewing the <var class="product">Model 204</var> audit trail,
as well as by invoking debugging and viewing your client tool log.
In the audit trail, Janus FTP server and client interactions are helpfully
marked with arrow indicators that identify whether
<code>RK</code> lines are messages from the client to the server
or from the server to the client.

For example, the lines below show Janus <var class="product">SirScan</var> output
(when <var>TRACE</var> is set at its default value, X'00')
for a failed upload of a file to an FTP server.
<code>FTP C->S:</code> identifies messages from the FTP client to the server, and
<code>FTP S->C:</code> the reverse.
19095422 2 1 RK TERM: FTP C->S: PWD
19095422 2 1 RK TERM: FTP S->C: 257 "/TEST/PUBS"
19095422 2 1 RK TERM: FTP C->S: TYPE A
19095422 2 1 RK TERM: FTP S->C: 200 ASCII mode enabled. EBCDIC
conversion automatic.
19095423 2 1 RK TERM: FTP C->S: PASV
19095423 2 1 RK TERM: FTP S->C: 227 Entering passive mode
(198,242,244,100,12,42)
19095423 3 2 AD MSIR.0114: Processing connection for port FTPPSV3004
from 198.242.244.36
19095423 3 2 RK TERM: FTP: PASV Server Socket connect.
19095423 2 1 RK TERM: FTP C->S: STOR COLORNOTES
19095423 2 1 RK TERM: FTP S->C: 150 storing: "/TEST/PUBS/COLORNOTES"
19095423 3 2 RK TERM: FTP: PASV Server Socket wakes up.
19095423 3 2 RK TERM: FTP: PASV Server Open.
19095424 3 2 RK TERM: *** M204.0620: FILE FTPTEST OPENED
19095424 3 2 RK TERM: *** M204.1203: FILE FTPTEST WAS LAST UPDATED ON
05.038 FEB 07 18.52.41
19095424 3 2 RK TERM: FTP: PASV Server Start XFER.
19095424 3 2 RK TERM: FTP: PASV Server End XFER.
19095424 3 2 LI
19095424 3 2 MS M204.1029: USER CONNECTION LOST (PHONE WAS HUNG UP)
19095424 3 2 AD M204.1022: USER RESTARTING SOFTLY
19095424 3 2 ST USERID='MOE' ACCOUNT='NO ACCOUNT' CNCT=12 SQWR=2 CPU=10
MOVE=7 AUDIT=13 DKPR=3
19095424 3 2 AD M204.0352: IODEV=15, OK MOE NO ACCOUNT LOGOUT
05.039 FEB 08 19.09.54 -52 C6F2F410
19095424 3 2 AD M204.1024: USER RESTARTED SOFTLY
19095425 3 1 RK TERM: FTP S->C: 500 Line too long, transfer aborted.


The FTP server in the example is defined much like the one in
[[#A simple development environment|"A simple development environment"]], able to
accommodate active and passive FTP mode.
The audit trail above shows the use of passive FTP, as requested by the FTP client.
The <var class="product">FTP Server</var> dynamically creates a server socket (to which
the FTP client connects for the transfer of the file), which runs on a
separate thread in the online.
When the transfer is done (successfully or not), the dynamically created
socket thread terminates, and the audit trail records a soft restart.

In comparison, the following example shows
the same attempted upload as the one above, but from a command-line client
that uses active FTP only.
The lines beginning with <code>ftp></code> are the user entries in the client tool.
The lines beginning with integers are the FTP server messages
received by the client.
The lines beginning with <code>---></code> are the commands the client actually
sends to the FTP server, as reported by the client's debugging facility.
ftp> put colornotes
---> PORT 198,242,244,36,8,235
200 Port command OK: "198,242,244,36,8,235"
---> STOR colorNotes
150 Storing: "TEST/PUBS/COLORNOTES"
500 Line too long, transfer aborted.


The client's <var>PORT</var> command above signals an active FTP transfer.
It identifies the
data port (server socket) to which the FTP server's <var>CLSOCK</var> socket must
connect for the upload.
The first four decimal digits following <var>PORT</var> form
the IP address of the FTP client host, and the last two digits form the
TCP address of the port.

In addition to the <var class="product">Model 204</var> <var>DISPLAY PROC LIST</var> command
(or the Sirius <var class="product">SirPro</var> product),
other useful <var class="product">FTP Server</var> debugging and reporting commands are:
<table class="syntaxTable">
<tr><th><var>[[JANUS DISPLAY]]</var>
</th><td>For a display of the FTP Server port definitions
</td></tr>
<tr><th><var>[[JANUS STAT or STATUS|JANUS STATUS]]</var>
</th><td>For a display of the FTP Server port activity (or inactivity)
</td></tr>
<tr><th><var>[[JANUS DISPLAYSOCK]]</var>
</th><td>For a display of the FTP-specific settings like folder mappings and user permissions
</td></tr></table>

← Older revision		Revision as of 16:52, 21 February 2012
Line 248:		Line 248:
	<ul>		<ul>
	<li>[[Janus FTP Server]]		<li>[[Janus FTP Server]]
	~~<li>[[Overriding FTP protocol commands]]~~
	<li>[[Janus FTP Server command reference]]		<li>[[Janus FTP Server command reference]]
	<li>[[Integrating Janus FTP and Janus Web Server]]		<li>[[Integrating Janus FTP and Janus Web Server]]
			<li>[[Overriding FTP protocol commands]]
	</ul>		</ul>

	[[Category:Janus FTP Server]]		[[Category:Janus FTP Server]]

Janus FTP Server examples - Revision history

JAL2: /* See also */

JAL2: /* A simple development environment */

JAL2: /* FTP client and server interaction */

JAL2 at 01:39, 21 February 2012

JAL2 at 01:10, 21 February 2012

JAL2 at 01:07, 21 February 2012

JAL2: /* FTP client and server interaction */

JAL2 at 23:04, 17 February 2012

JAL2 at 22:38, 17 February 2012

JAL2: Created page with "The following two short examples show how to set up Janus FTP Servers in an online. The Janus FTP commands in the examples are introduced in [[Janus FT..."

JAL2: Created page with "The following two short examples show how to set up `Janus FTP Server`s in an online. The Janus FTP commands in the examples are introduced in [[Janus FT..."