Defining server ports - Revision history

JAL: /* See also */

2013-04-29T01:06:33Z

JAL2: moved Janus / Connectivity concepts to Defining server ports: title too vague

2012-03-09T17:24:21Z

moved Janus / Connectivity concepts to Defining server ports: title too vague

← Older revision	Revision as of 17:24, 9 March 2012
(No difference)

JAL2: /* JANUS DEFINE and JANUS DEFINEREMOTE */

2012-03-09T17:22:41Z

JANUS DEFINE and JANUS DEFINEREMOTE

← Older revision		Revision as of 17:22, 9 March 2012
Line 23:		Line 23:
	<li>Assign a port number to a <var class="product">[http://www.sirius-software.com/maint/download/josrvr.pdf Janus Open Server]</var> application.		<li>Assign a port number to a <var class="product">[http://www.sirius-software.com/maint/download/josrvr.pdf Janus Open Server]</var> application.
	<li>Assign a port number for [[Janus IFDIAL Library\|Janus IFDIAL]] processing.</li>		<li>Assign a port number for [[Janus IFDIAL Library\|Janus IFDIAL]] processing.</li>
	<li>Assign a (<var>MASTER</var>) port number for use by non-<var class="product">Janus Open Server</var> users to access <var class="product">[http://www.sirius-software.com/maint/download/josrvr.pdf Janus Open Client]</var> applications.		<li>Assign a (<var>[[MASTER (JANUS DEFINE parameter)\|MASTER]]</var>) port number for use by non-<var class="product">Janus Open Server</var> users to access <var class="product">[http://www.sirius-software.com/maint/download/josrvr.pdf Janus Open Client]</var> applications.
	</ul>		</ul>

JAL2: /* JANUS DEFINE and JANUS DEFINEREMOTE subcommands */

2012-03-09T17:13:42Z

JANUS DEFINE and JANUS DEFINEREMOTE subcommands

← Older revision		Revision as of 17:13, 9 March 2012
Line 15:		Line 15:
	Sybase provides a way of mapping an application name to a host name (or address) and port number. This makes it possible to access a specific application by specifying only a single application name. This mapping is done through a mapping file called the "interfaces file" on Unix workstations, and through entries in WIN.INI or SQL.INI under Microsoft Windows. For more information on this mapping, refer to the Sybase DB/Library manuals.		Sybase provides a way of mapping an application name to a host name (or address) and port number. This makes it possible to access a specific application by specifying only a single application name. This mapping is done through a mapping file called the "interfaces file" on Unix workstations, and through entries in WIN.INI or SQL.INI under Microsoft Windows. For more information on this mapping, refer to the Sybase DB/Library manuals.

	==JANUS DEFINE and JANUS DEFINEREMOTE ~~subcommands~~==		==JANUS DEFINE and JANUS DEFINEREMOTE==

	A <var>[[JANUS DEFINE]]</var> command can do any one of the following:		A <var>[[JANUS DEFINE]]</var> command can do any one of the following:

JAL2: /* JANUS DEFINE and JANUS DEFINEREMOTE subcommands */

2012-03-09T17:12:32Z

JANUS DEFINE and JANUS DEFINEREMOTE subcommands

← Older revision		Revision as of 17:12, 9 March 2012
Line 22:		Line 22:
	<li>Assign a port number to a <var class="product">[[Janus Web Server]]</var>, <var class="product">[[Janus FTP Server]]</var>, <var class="product">[[Janus Telnet Server]]</var>, or <var class="product">[http://www.sirius-software.com/maint/download/jsdsr.pdf Janus Specialty Data Store]</var> server.		<li>Assign a port number to a <var class="product">[[Janus Web Server]]</var>, <var class="product">[[Janus FTP Server]]</var>, <var class="product">[[Janus Telnet Server]]</var>, or <var class="product">[http://www.sirius-software.com/maint/download/jsdsr.pdf Janus Specialty Data Store]</var> server.
	<li>Assign a port number to a <var class="product">[http://www.sirius-software.com/maint/download/josrvr.pdf Janus Open Server]</var> application.		<li>Assign a port number to a <var class="product">[http://www.sirius-software.com/maint/download/josrvr.pdf Janus Open Server]</var> application.
	<li>Assign a port number for Janus IFDIAL processing.</li>		<li>Assign a port number for [[Janus IFDIAL Library\|Janus IFDIAL]] processing.</li>
	<li>Assign a (<var>MASTER</var>) port number for use by non-<var class="product">Janus Open Server</var> users to access <var class="product">[http://www.sirius-software.com/maint/download/josrvr.pdf Janus Open Client]</var> applications.		<li>Assign a (<var>MASTER</var>) port number for use by non-<var class="product">Janus Open Server</var> users to access <var class="product">[http://www.sirius-software.com/maint/download/josrvr.pdf Janus Open Client]</var> applications.
	</ul>		</ul>

JAL2: /* JANUS DEFINE and JANUS DEFINEREMOTE subcommands */

2012-03-09T16:59:14Z

JANUS DEFINE and JANUS DEFINEREMOTE subcommands

← Older revision		Revision as of 16:59, 9 March 2012
Line 17:		Line 17:
	==JANUS DEFINE and JANUS DEFINEREMOTE subcommands==		==JANUS DEFINE and JANUS DEFINEREMOTE subcommands==

	A [[JANUS DEFINE]] command can do any one of the following:		A <var>[[JANUS DEFINE]]</var> command can do any one of the following:

	<ul>		<ul>
			<li>Assign a port number to a <var class="product">[[Janus Web Server]]</var>, <var class="product">[[Janus FTP Server]]</var>, <var class="product">[[Janus Telnet Server]]</var>, or <var class="product">[http://www.sirius-software.com/maint/download/jsdsr.pdf Janus Specialty Data Store]</var> server.
			<li>Assign a port number to a <var class="product">[http://www.sirius-software.com/maint/download/josrvr.pdf Janus Open Server]</var> application.
	<li>Assign a port number for Janus IFDIAL processing.</li>		<li>Assign a port number for Janus IFDIAL processing.</li>
	<li>Assign a ~~port number to a~~ <var ~~class="product~~>~~Janus Open Server~~</var> ~~application.~~		<li>Assign a (<var>MASTER</var>) port number for use by non-<var class="product">Janus Open Server</var> users to access <var class="product">[http://www.sirius-software.com/maint/download/josrvr.pdf Janus Open Client]</var> applications.
	~~<li>Assign a~~ port number ~~to a~~ <var class="product>Janus ~~Specialty Data Store~~</var> ~~server.~~
	~~<li>Assign a port number~~ to a <var class="product>~~Janus Web Server<~~/~~var> server~~. ~~In addition to the second option above, assigning a port number to a <var class="product>~~Janus Open ~~Server~~</var> ~~application, a JANUS DEFINE command can also:~~
	~~<li>Assign a (MASTER) port number for use by non-Janus Open Server users to access Janus Open Client~~ applications.
	</ul>		</ul>

	A [[JANUS DEFINEREMOTE]] command can do any combination of the following:		A <var>[[JANUS DEFINEREMOTE]]</var> command can do any combination of the following:

	<ul>		<ul>
	<li>Assign a remote host address and port number for Janus Open Client processing,		<li>Assign a remote host address and port number for <var class="product">Janus Open Client</var> processing,
	and assign which local port numbers can call the remote host/port (non-INONLY).		and assign which local port numbers can call the remote host/port (non-INONLY).
	<li>Specify the address of a remote host and the <var class="product>Janus Open Server</var> applications it may access (non-OUTONLY).		<li>Specify the address of a remote host and the <var class="product">Janus Open Server</var> applications it may access (non-OUTONLY).
	</ul>		</ul>

JAL2 at 16:16, 9 March 2012

2012-03-09T16:16:35Z

← Older revision		Revision as of 16:16, 9 March 2012
Line 1:		Line 1:
	==Server ~~Ports~~==		==Server ports==

	In order for a client application to communicate with a server application, it must have a way to identify the server application on the network. Under the TCP/IP protocols, the identity of a server has two parts. The first part identifies the machine on which the server runs. This part is called the machine's (or host's) IP address. The second part distinguishes the server application from other applications on the host. This part is called the port number.		In order for a client application to communicate with a server application, it must have a way to identify the server application on the network. Under the TCP/IP protocols, the identity of a server has two parts. The first part identifies the machine on which the server runs. This part is called the machine's (or host's) IP address. The second part distinguishes the server application from other applications on the host. This part is called the port number.
Line 7:		Line 7:
	A port number is a number from 1 to 65535 that is assigned to every server application that is available on a host. In the case of <var class="product">Janus IFDIAL</var>, the Janus server products (<var class="product">Janus Specialty Data Store</var>, <var class="product">Janus Open Server</var>, and <var class="product">Janus Web Server</var>), and Janus server sockets, this port number is specified by the second parameter on the <var>[[JANUS DEFINE]]</var> command.		A port number is a number from 1 to 65535 that is assigned to every server application that is available on a host. In the case of <var class="product">Janus IFDIAL</var>, the Janus server products (<var class="product">Janus Specialty Data Store</var>, <var class="product">Janus Open Server</var>, and <var class="product">Janus Web Server</var>), and Janus server sockets, this port number is specified by the second parameter on the <var>[[JANUS DEFINE]]</var> command.

	Since this port number must be unique for the host, it is impossible to start (<var>[[JANUS START]]</var>) a port with a port number that matches a port number for any other application running on the same host. This includes any Janus port on the same or a different Online that uses the same IP address. This also includes any other non-Janus server application. For example, port number 23 is almost always used by the telnet server. An attempt to start a Janus server for port number 23 will undoubtedly encounter a port in use situation and be unable to start.		Since this port number must be unique for the host, it is impossible to start (<var>[[JANUS START]]</var>) a port with a port number that matches a port number for any other application running on the same host. This includes any Janus port on the same or a different Online that uses the same IP address. This also includes any other non-Janus server application. For example, port number 23 is almost always used by the telnet server. An attempt to start a Janus server for port number 23 will undoubtedly encounter a port-in-use situation and be unable to start.

	On a system with several local server applications, or with more than one Online (maybe test and production) with several Janus ports, a simple strategy to keep port numbers from conflicting is to assign a range of ports to each Online. For example, port numbers 300-399 might be reserved for the test Online, and port numbers 400-499 might be reserved for the production Online.		On a system with several local server applications, or with more than one Online (maybe test and production) with several Janus ports, a simple strategy to keep port numbers from conflicting is to assign a range of ports to each Online. For example, port numbers 300-399 might be reserved for the test Online, and port numbers 400-499 might be reserved for the production Online.

JAL2: /* References */

2012-03-02T22:19:34Z

References

← Older revision		Revision as of 22:19, 2 March 2012
Line 35:		Line 35:
	</ul>		</ul>

	==~~References~~==		==See also==
			<ul>
	~~See:~~ [[List of Janus commands]] \| [[:Category:Janus Web Server\|Janus Web Server]] \| [[Janus SOAP]]		<li>[[List of Janus commands]]
			<li>[[:Category:Janus Web Server\|Janus Web Server]]
			<li>[[Janus SOAP]]
			</ul>

	[[Category:Janus TCP/IP Base]]		[[Category:Janus TCP/IP Base]]

JAL2: /* References */

2011-10-19T21:42:28Z

References

← Older revision		Revision as of 21:42, 19 October 2011
Line 37:		Line 37:
	==References==		==References==

	See: [[List of Janus commands]] \| [[:Category:Janus Web Server]] \| [[Janus SOAP]]		See: [[List of Janus commands]] \| [[:Category:Janus Web Server\|Janus Web Server]] \| [[Janus SOAP]]

	[[Category:Janus TCP/IP Base]]		[[Category:Janus TCP/IP Base]]

JAL2: /* Server Ports */

2011-06-28T20:04:41Z

Server Ports

← Older revision		Revision as of 20:04, 28 June 2011
Line 3:		Line 3:
	In order for a client application to communicate with a server application, it must have a way to identify the server application on the network. Under the TCP/IP protocols, the identity of a server has two parts. The first part identifies the machine on which the server runs. This part is called the machine's (or host's) IP address. The second part distinguishes the server application from other applications on the host. This part is called the port number.		In order for a client application to communicate with a server application, it must have a way to identify the server application on the network. Under the TCP/IP protocols, the identity of a server has two parts. The first part identifies the machine on which the server runs. This part is called the machine's (or host's) IP address. The second part distinguishes the server application from other applications on the host. This part is called the port number.

	A host's IP address is a 32-bit unsigned binary number that is displayed in ~~&amp;#x201C;~~dotted~~&amp;#x201D;~~ format, for example, 198.242.244.33. To avoid having to refer to these types of addresses, most networks have nameservers or names files that map names to IP addresses. That way, a client application can connect to a host by a name (such as IBM3090) rather than by an address.		A host's IP address is a 32-bit unsigned binary number that is displayed in "dotted" format, for example, 198.242.244.33. To avoid having to refer to these types of addresses, most networks have nameservers or names files that map names to IP addresses. That way, a client application can connect to a host by a name (such as IBM3090) rather than by an address.

	A port number is a number from 1 to 65535 that is assigned to every server application that is available on a host. In the case of Janus IFDIAL, the Janus server products (Janus Specialty Data Store, <var class="product>Janus Open Server</var>, and <var class="product>Janus Web Server</var>), and Janus server sockets, this port number is specified by the second parameter on the [[JANUS DEFINE]] command.		A port number is a number from 1 to 65535 that is assigned to every server application that is available on a host. In the case of <var class="product">Janus IFDIAL</var>, the Janus server products (<var class="product">Janus Specialty Data Store</var>, <var class="product">Janus Open Server</var>, and <var class="product">Janus Web Server</var>), and Janus server sockets, this port number is specified by the second parameter on the <var>[[JANUS DEFINE]]</var> command.

	Since this port number must be unique for the host, it is impossible to start ([[JANUS START]]) a port with a port number that matches a port number for any other application running on the same host. This includes any Janus port on the same or a different Online that uses the same IP address. This also includes any other non-Janus server application. For example, port number 23 is almost always used by the telnet server. An attempt to start a Janus server for port number 23 will undoubtedly encounter a port in use situation and be unable to start.		Since this port number must be unique for the host, it is impossible to start (<var>[[JANUS START]]</var>) a port with a port number that matches a port number for any other application running on the same host. This includes any Janus port on the same or a different Online that uses the same IP address. This also includes any other non-Janus server application. For example, port number 23 is almost always used by the telnet server. An attempt to start a Janus server for port number 23 will undoubtedly encounter a port in use situation and be unable to start.

	On a system with several local server applications, or with more than one Online (maybe test and production) with several Janus ports, a simple strategy to keep port numbers from conflicting is to assign a range of ports to each Online. For example, port numbers 300-399 might be reserved for the test Online, and port numbers 400-499 might be reserved for the production Online.		On a system with several local server applications, or with more than one Online (maybe test and production) with several Janus ports, a simple strategy to keep port numbers from conflicting is to assign a range of ports to each Online. For example, port numbers 300-399 might be reserved for the test Online, and port numbers 400-499 might be reserved for the production Online.

	The [[BINDADDR]] parameter of the [[JANUS DEFINE]] command also allows you to specify which IP address to use for a Janus server, if your operating system is configured to bind a port to one of multiple IP server addresses.		The <var>[[BINDADDR]]</var> parameter of the <var>[[JANUS DEFINE]]</var> command also allows you to specify which IP address to use for a Janus server, if your operating system is configured to bind a port to one of multiple IP server addresses.

	Sybase provides a way of mapping an application name to a host name (or address) and port number. This makes it possible to access a specific application by specifying only a single application name. This mapping is done through a mapping file called the ~~&amp;#x201C;~~interfaces file~~&amp;#x201D;~~ on Unix workstations, and through entries in WIN.INI or SQL.INI under Microsoft Windows. For more information on this mapping, refer to the Sybase DB/Library manuals.		Sybase provides a way of mapping an application name to a host name (or address) and port number. This makes it possible to access a specific application by specifying only a single application name. This mapping is done through a mapping file called the "interfaces file" on Unix workstations, and through entries in WIN.INI or SQL.INI under Microsoft Windows. For more information on this mapping, refer to the Sybase DB/Library manuals.

	==JANUS DEFINE and JANUS DEFINEREMOTE subcommands==		==JANUS DEFINE and JANUS DEFINEREMOTE subcommands==

← Older revision		Revision as of 01:06, 29 April 2013
Line 36:		Line 36:
	==See also==		==See also==
	<ul>		<ul>
	<li>[[~~List of~~ Janus ~~commands~~]]		<li>[[Janus TCP/IP Base]]
	<li>[[~~:Category:~~Janus ~~Web Server\|~~Janus ~~Web Server~~]]		<li>[[Janus environment definition]]
	<li>[[Janus ~~SOAP~~]]		<li>[[Storage requirements]]
			<li>[[Translate tables]]
			<li>[[Janus commands]]
			<li>[[Janus user parameters]]
	</ul>		</ul>


	[[Category:Janus TCP/IP Base]]		[[Category:Janus TCP/IP Base]]