Janus TCP/IP Base: Difference between revisions
m (Created page with "<var class="product">Janus TCP/IP Base</var> is part of the Janus family of products that provides connectivity to the <var class="product">Model 204</var> database. <var cla...") |
mNo edit summary |
||
| Line 1: | Line 1: | ||
<var class="product">Janus TCP/IP Base</var> is part of the Janus family of products that provides connectivity to the <var class="product">[[Model 204]]</var> database. <var class="product">Janus TCP/IP Base</var> is a pre-requisite for all other products in the Janus family, because without it, it is impossible to use these other products. | <var class="product">Janus TCP/IP Base</var> is part of the Janus family of products that provides connectivity to the <var class="product">[[Model 204]]</var> database. <var class="product">Janus TCP/IP Base</var> is a pre-requisite for all other products in the Janus family, because without it, it is impossible to use these other products. | ||
==The Janus family== | |||
A <var class="product">Janus TCP/IP Base</var> site will probably have one or more of the other products in the Janus family, though no others are required. The other Janus products are: | A <var class="product">Janus TCP/IP Base</var> site will probably have one or more of the other products in the Janus family, though no others are required. The other Janus products are: | ||
<ul> | <ul> | ||
| Line 20: | Line 21: | ||
A single <var class="product">Model 204</var> Online region can contain any number of the three different 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>). A <var class="product">Janus Open Server</var> or <var class="product">Janus Web Server</var> <var class="product">User Language</var> request can also invoke <var class="product">Janus Open Client</var> $functions; this enables server applications to exchange information with other <var class="product">Model 204</var> or non-<var class="product">Model 204</var> servers. | A single <var class="product">Model 204</var> Online region can contain any number of the three different 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>). A <var class="product">Janus Open Server</var> or <var class="product">Janus Web Server</var> <var class="product">User Language</var> request can also invoke <var class="product">Janus Open Client</var> $functions; this enables server applications to exchange information with other <var class="product">Model 204</var> or non-<var class="product">Model 204</var> servers. | ||
==Janus, the Sirius Mods, and UL/SPF== | |||
The Janus family of products is itself made up of two distinct components: | |||
<ul> | |||
<li>A collection of object code enhancements to the <var class="product">Model 204</var> database-engine | |||
nucleus. These enhancements are distributed as components of the <var class="product">Sirius Mods</var> and make up a collection of products including those in the Janus family. The <var class="product">Sirius Mods</var> include many non-connectivity related products (such as Fast/Backup, Fast/Reload, and the Fast/Unload User Language Interface) that are not part of the Janus family. No <var class="product">Sirius Mods</var> products are required to run <var class="product">Janus TCP/IP Base</var> other than itself.</li> | |||
<li>A collection of <var class="product">Model 204</var> procedures that contain <var class="product">User Language</var>, documentation, and assorted other data. | |||
<p> | |||
These <var class="product">Model 204</var> procedures install and implement the components of the User Language Structured Programming Facility, also known as <var class="product">UL/SPF</var>. All the <var class="product">UL/SPF</var> files reside in the SIRIUS procedure file (as of <var class="product">Sirius Mods</var> version 6.8). which also contains code and data useful to Janus users including <var class="product">Janus TCP/IP Base</var> users. </p> | |||
<p> | |||
<var class="product">UL/SPF</var> also includes files that are components of non-connectivity related products such as <var class="product">SirPro</var>, <var class="product">SirScan</var>, and <var class="product">SirMon</var>. No other <var class="product">UL/SPF</var> products are required to run <var class="product">Janus TCP/IP Base</var>, or any other Janus product, for that matter. </p> | |||
<p> | |||
Thus, to install <var class="product">Janus TCP/IP Base</var>, both the <var class="product">[[Sirius Mods]]</var> and <var class="product">[[ULSPF|UL/SPF]]</var> must be installed, following the instructions in the ''Sirius Mods Installation Guide'' and the ''UL/SPF Installation and Maintenance Guide'', respectively. When the <var class="product">Sirius Mods</var> is installed, all other products owned by the installing site that are part of the <var class="product">Sirius Mods</var> will also be installed. Similarly, when <var class="product">UL/SPF</var> is installed, all other products owned by the installing site that are part of <var class="product">UL/SPF</var> will be installed. </p></li> | |||
</ul> | |||
==Versions and compatibility== | |||
Because the <var class="product">Sirius Mods</var> and <var class="product">UL/SPF</var> have somewhat different release cycles, the version numbers for these two components will often differ in a distribution. For example, version 7.6 of the <var class="product">Sirius Mods</var> might be shipped with version 7.3 of <var class="product">UL/SPF</var>. All the products in <var class="product">UL/SPF</var> depend on certain features being present in the version of the <var class="product">Sirius Mods</var> that is installed in the <var class="product">Model 204</var> load module under which <var class="product">UL/SPF</var> is running. This implies, obviously, that the <var class="product">Sirius Mods</var> must be installed for any <var class="product">UL/SPF</var> component to operate correctly. And, as of version 6.8, the <var class="product">Sirius Mods</var> version must match or be higher than the <var class="product">UL/SPF</var> version number. | |||
The <var class="product">Sirius Mods</var> however, do not depend on any particular features of the <var class="product">UL/SPF</var> product, merely the presence of the <var class="product">UL/SPF</var> SIRIUS file. The SIRIUS file contains the code for the sample <var class="product">Janus Web Server</var>, and Janus port definitions have default rules that call to this file. Sirius Software has a strong commitment to backward compatibility with the <var class="product">Sirius Mods</var>. | |||
This means that any <var class="product">User Language</var> application (including <var class="product">UL/SPF</var>) that uses the <var class="product">Sirius Mods</var> will run correctly on subsequent versions of the <var class="product">Sirius Mods</var>. It is, thus, always possible to upgrade the <var class="product">Sirius Mods</var> without having to worry about upgrading <var class="product">UL/SPF</var>. This is not to say that this is always a good idea, only that it is possible and that the installed version of a <var class="product">UL/SPF</var> product will continue to run as it had before the <var class="product">[[Sirius Mods]]</var> upgrade. | |||
While the Janus family of products has a <var class="product">UL/SPF</var> component, most of the critical code is actually in the <var class="product">Sirius Mods</var> — object code enhancements to the <var class="product">Model 204</var> nucleus. The <var class="product">UL/SPF</var> component of the Janus family consists mostly of utilities, examples, and documentation. Because of this, the version number of a Janus product is generally considered to be the version of the <var class="product">Sirius Mods</var> in which it is contained. | |||
Janus product documentation assumes that a site is running <var class="product">Sirius Mods</var> version 6.7 or later and has installed <var class="product">UL/SPF</var> version 6.2 or later. Any documentation that requires a later version of the <var class="product">Sirius Mods</var> or <var class="product">UL/SPF</var> will be clearly marked to indicate this. For example, a <var>JANUS DEFINE</var> parameter that is only available in versions 7.7 and later of the <var class="product">Sirius Mods</var> will have a sentence such as "This parameter is only available in version 7.7 and later of <var class="product">Sirius Mods</var>" in its documentation. If a feature, $function, command, or parameter is not indicated as requiring any specific version of the <var class="product">Sirius Mods</var>, it can be assumed that it is available, as documented, in all versions of a Janus product; that is, all versions since version 6.7 of the <var class="product">Sirius Mods</var> and version 6.2 of <var class="product">UL/SPF</var>. | |||
[[Category:Janus TCP/IP Base]] | |||
Revision as of 22:51, 19 October 2011
Janus TCP/IP Base is part of the Janus family of products that provides connectivity to the Model 204 database. Janus TCP/IP Base is a pre-requisite for all other products in the Janus family, because without it, it is impossible to use these other products.
The Janus family
A Janus TCP/IP Base site will probably have one or more of the other products in the Janus family, though no others are required. The other Janus products are:
- Janus Network Security, which supports the Secure Sockets Layer (SSL) protocol, providing secure communications for users of Janus products. This is documented in the Janus Network Security Reference Manual.
- Janus Specialty Data Store, which enables Model 204 to operate as a Sybase/Microsoft SQL Server, principally for the Sybase OmniConnect feature of Adaptive Server. Features include optimized translation of SQL into User Language and cataloging tools to map unchanged Model 204 files onto normalized. This is documented in the Janus Specialty Data Store Reference Manual.
- Janus Open Client, which enables your Model 204 User Language applications to invoke Sybase/Microsoft Remote Procedure Calls (RPCs) or language requests (for example, SQL) to one or more Sybase or Microsoft Open Servers and/or SQL servers. This is documented in the Janus Open Client Reference Manual.
- Janus Open Server, which enables you to create Model 204 User Language applications which respond to requests from clients which use Sybase DB-Library Open Client calls and SQL EXECUTE statements. This is documented in the Janus Open Server Reference Manual.
- Janus Web Server, which enables you to provide access to Model 204 data and objects to clients (usually called browsers) via the World Wide Web.
A single Model 204 Online region can contain any number of the three different Janus server products (Janus Specialty Data Store, Janus Open Server, and Janus Web Server). A Janus Open Server or Janus Web Server User Language request can also invoke Janus Open Client $functions; this enables server applications to exchange information with other Model 204 or non-Model 204 servers.
Janus, the Sirius Mods, and UL/SPF
The Janus family of products is itself made up of two distinct components:
- A collection of object code enhancements to the Model 204 database-engine nucleus. These enhancements are distributed as components of the Sirius Mods and make up a collection of products including those in the Janus family. The Sirius Mods include many non-connectivity related products (such as Fast/Backup, Fast/Reload, and the Fast/Unload User Language Interface) that are not part of the Janus family. No Sirius Mods products are required to run Janus TCP/IP Base other than itself.
- A collection of Model 204 procedures that contain User Language, documentation, and assorted other data.
These Model 204 procedures install and implement the components of the User Language Structured Programming Facility, also known as UL/SPF. All the UL/SPF files reside in the SIRIUS procedure file (as of Sirius Mods version 6.8). which also contains code and data useful to Janus users including Janus TCP/IP Base users.
UL/SPF also includes files that are components of non-connectivity related products such as SirPro, SirScan, and SirMon. No other UL/SPF products are required to run Janus TCP/IP Base, or any other Janus product, for that matter.
Thus, to install Janus TCP/IP Base, both the Sirius Mods and UL/SPF must be installed, following the instructions in the Sirius Mods Installation Guide and the UL/SPF Installation and Maintenance Guide, respectively. When the Sirius Mods is installed, all other products owned by the installing site that are part of the Sirius Mods will also be installed. Similarly, when UL/SPF is installed, all other products owned by the installing site that are part of UL/SPF will be installed.
Versions and compatibility
Because the Sirius Mods and UL/SPF have somewhat different release cycles, the version numbers for these two components will often differ in a distribution. For example, version 7.6 of the Sirius Mods might be shipped with version 7.3 of UL/SPF. All the products in UL/SPF depend on certain features being present in the version of the Sirius Mods that is installed in the Model 204 load module under which UL/SPF is running. This implies, obviously, that the Sirius Mods must be installed for any UL/SPF component to operate correctly. And, as of version 6.8, the Sirius Mods version must match or be higher than the UL/SPF version number.
The Sirius Mods however, do not depend on any particular features of the UL/SPF product, merely the presence of the UL/SPF SIRIUS file. The SIRIUS file contains the code for the sample Janus Web Server, and Janus port definitions have default rules that call to this file. Sirius Software has a strong commitment to backward compatibility with the Sirius Mods.
This means that any User Language application (including UL/SPF) that uses the Sirius Mods will run correctly on subsequent versions of the Sirius Mods. It is, thus, always possible to upgrade the Sirius Mods without having to worry about upgrading UL/SPF. This is not to say that this is always a good idea, only that it is possible and that the installed version of a UL/SPF product will continue to run as it had before the Sirius Mods upgrade.
While the Janus family of products has a UL/SPF component, most of the critical code is actually in the Sirius Mods — object code enhancements to the Model 204 nucleus. The UL/SPF component of the Janus family consists mostly of utilities, examples, and documentation. Because of this, the version number of a Janus product is generally considered to be the version of the Sirius Mods in which it is contained.
Janus product documentation assumes that a site is running Sirius Mods version 6.7 or later and has installed UL/SPF version 6.2 or later. Any documentation that requires a later version of the Sirius Mods or UL/SPF will be clearly marked to indicate this. For example, a JANUS DEFINE parameter that is only available in versions 7.7 and later of the Sirius Mods will have a sentence such as "This parameter is only available in version 7.7 and later of Sirius Mods" in its documentation. If a feature, $function, command, or parameter is not indicated as requiring any specific version of the Sirius Mods, it can be assumed that it is available, as documented, in all versions of a Janus product; that is, all versions since version 6.7 of the Sirius Mods and version 6.2 of UL/SPF.