Docstoc

Ssl2P1 Solaris User Guide

Document Sample
Ssl2P1 Solaris User Guide Powered By Docstoc
					Jonathan Pinnock and Associates
    Software Development, Consultancy and Some Pretty Cool Products




Reuters Triarch SSL to
PlatformOne™
Gateway

                                       Version 1.1
                             Solaris User’s Guide
                                      Revision 1.0
                                23 February 2004




                                            www.jpassoc.co.uk
Introduction
This document is the User’s Guide for the PlatformOne™ Reuters Triarch SSL Gateway, or ssl2p1,
under the Solaris operating system. ssl2p1provides a bi-directional gateway between a Reuters Triarch
SSL system and PlatformOne™.

This document should be read in conjunction with the general PlatformOne™ Solaris User’s Guide.




JPA Reuters Triarch SSL to PlatformOne™ Gateway Solaris User’s Guide                                    2
JPA/P1/SSL2P1/UG/1.1/1.0/Solaris
Jonathan Pinnock, JPA, 23/02/04
Installation
Installation is as described in the PlatformOne™ Solaris User’s Guide.




JPA Reuters Triarch SSL to PlatformOne™ Gateway Solaris User’s Guide     3
JPA/P1/SSL2P1/UG/1.1/1.0/Solaris
Jonathan Pinnock, JPA, 23/02/04
Running
ssl2p1 is run in the manner described in the PlatformOne™ Solaris User’s Guide. The master
configuration file has the following sections:

   Inbound      -       this is completely standard

   Outbound     -       this is completely standard

   Cache        -       this has minor extensions, as described below

   Sources      -       this is completely standard

   SSL          -       this is specific to ssl2p1, and is described below

   Status       -       this is completely standard




JPA Reuters Triarch SSL to PlatformOne™ Gateway Solaris User’s Guide                         4
JPA/P1/SSL2P1/UG/1.1/1.0/Solaris
Jonathan Pinnock, JPA, 23/02/04
Cache Section
The only aspect of the Cache section that specific to ssl2p1 is the structure of the cache file.

The cache file is the persistent representation of the inbound and outbound dataset – source mappings.
Here is an example:

<?xml version="1.0" encoding="UTF-8" ?>
<root>
    <dataset name="Dataset1" source="source1" location="local" />
    <dataset name="Dataset2" source="source2" location="remote" />
</root>

In this example, Dataset1 in PlatformOne™ originates in Triarch source1. source2 in Triarch
originates in PlatformOne™ Dataset2.

Location in this context effectively relates to the view from Triarch. A local dataset originates in
Triarch, whereas a remote dataset originates elsewhere.

The cache file is also used to define further settings for both local and remote datasets.

For local datasets, the following additional attribute may be defined:

Attribute/value                          Description                             Default
convert="pages"                          If this is set, incoming page-type      convert=""
                                         records are converted to
                                         PlatformOne™ pages

For remote datasets, the following additional attribute may be defined:

Attribute/value                          Description                             Default
cachesize="nnn"                          This may be set to override the         cachesize=""
                                         default value of the record cache
                                         defined in the SSL section (see
                                         below). If left blank, the default
                                         value is used.

In addition to this, additional FID mappings (over and above those specified in the Appendix A file)
may be defined, as in the following example:

          .        .                        .
          .        .                        .
          .        .                        .
      <dataset name="Dataset2" source="source2" location="remote">
          <fields>
              <field name="MyBid" fid="22" />
              <field name="MyAsk" fid="25" />
          <fields>
      </dataset>




JPA Reuters Triarch SSL to PlatformOne™ Gateway Solaris User’s Guide                                     5
JPA/P1/SSL2P1/UG/1.1/1.0/Solaris
Jonathan Pinnock, JPA, 23/02/04
A full cache file might therefore look like this:

<?xml version="1.0" encoding="UTF-8" ?>
<root>
    <dataset name="Dataset1" source="source1" location="local" />
    <dataset name="Dataset2" source="source2" location="remote">
        <fields>
            <field name="MyBid" fid="22" />
            <field name="MyAsk" fid="25" />
        <fields>
    </dataset>
</root>




JPA Reuters Triarch SSL to PlatformOne™ Gateway Solaris User’s Guide   6
JPA/P1/SSL2P1/UG/1.1/1.0/Solaris
Jonathan Pinnock, JPA, 23/02/04
SSL Section
This section is specific to ssl2p1, and is used to control those aspects of the system operation that are
specific to Triarch SSL. The following settings may be changed in this section:

   CacheSize

    This is the default size of the cache to be used for datasets sourced by ssl2p1. This may be
    overridden by settings for each dataset in the cache file. The default value is 4096.

   User

    This is the user name used in the sink mount.

   Application

    This is the application name used in the sink mount.

   Position

    This is the position used in the sink mount.

   FidFile

    This is the pathname of the FID map file (appendix A). The default value is appendix_a.txt.

   ListFile

    This is the pathname of the list or template definition file (appendix D). The default value is
    appendix_d.txt.

   Unmapped

    This is the character to be used to substitute for unmapped G1 characters in ANSI pages. The
    default value is ‘?’.

   RemountInterval

    This is the interval in seconds between attempts to remount the sink, following a disconnection.
    The default value is 300 seconds.




JPA Reuters Triarch SSL to PlatformOne™ Gateway Solaris User’s Guide                                        7
JPA/P1/SSL2P1/UG/1.1/1.0/Solaris
Jonathan Pinnock, JPA, 23/02/04
The following example shows all of these defined as their defaults:

         .      .       .
         .      .       .
         .      .       .
     <section name="SSL">
         <param name="CacheSize" value="4096" />
         <param name="User" value="" />
         <param name="Application" value="0" />
         <param name="Position" value="" />
         <param name="FidFile" value="appendix_a.txt" />
         <param name="ListFile" value="appendix_d.txt" />
         <param name="Unmapped" value="?" />
         <param name="RemountInterval" value="300" />
     </section>
         .      .       .
         .      .       .
         .      .       .




JPA Reuters Triarch SSL to PlatformOne™ Gateway Solaris User’s Guide   8
JPA/P1/SSL2P1/UG/1.1/1.0/Solaris
Jonathan Pinnock, JPA, 23/02/04

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:3
posted:8/27/2011
language:English
pages:8