software users guide - PWP - splash

Document Sample
software users guide - PWP - splash Powered By Docstoc
					                                     3                                     Chapter

      Installing the Proclaim Software
The installation instructions in this chapter are correct as of version 4.0. The
installation medium will contain a file with current instructions (called
install.txt) and an up-to-date version of this document (called
Proclaim.doc).

The Proclaim software consists of networking and screen interface packages for the
hub site, and networking and screen interface packages for the remote site. All
packages are contained in a UNIX tape archive (tar) file, which may be delivered
on an actual magnetic tape or electronically transmitted to the site. A contents list for
all packages is shown in Appendix A.

The steps for configuring and installing the Proclaim software are summarized below
for illustrative purposes only. Since these steps do not account for platform
differences, you should follow the procedure that appears in the install.txt file
in your installation kit.

Note: Before you begin, be sure you already have Oracle7 Server running on the
      server machine. Verify that the Oracle tablespace allocation is adequate to
      contain 12 tables of about 5 MB each. (In general, 60 MB should be
      sufficient.)

1. Configure the network at your hub site. (This includes editing the cfg4.map
   and netcfg4.map files, as well as configuring the local transmitter by editing
   the /etc/services and /etc/inetd.conf files and initializing
   transmitter service.)

2. Install Proclaim networking software on your hub server.

3. Configure the network at your remote sites. (This includes copying the
   cfg4.map and /etc/hosts files. Optionally, you may also choose to
   configure the remote transmitter.)

4. Install Proclaim networking software on your remote sites.
5. Install the Proclaim GUI software on your Oracle server and/or client machines.
6. Install the Oracle Forms software by running the Oracle installation program,
   ORAINST.

7. Create the Oracle7 tables needed by running Proclaim SQL scripts.



                                              Proclaim Multicaster User Manual Page 1
               8. Test the system.
               The rest of this chapter provides a detailed description of these steps.


1. Configuring the Network at the Hub Site
               Before starting the installation, edit the following two configuration files to reflect
               the characteristics of your network:

               cfg4.map
                  netcfg4.map

               These text files are read by the Multicaster Control Program (MLTC) when it starts
               up. In addition, you will need to configure the local MFTP transmitter.

Editing the cfg.map File
               The cfg4.map file is required on the hub transmitter machine as well as on each
               remote receiver machine. At the transmitter site, the MLTC and MFTP processes use
               it to map individual receiver host names to the symbolic group names used by the
               Proclaim software. In addition, the MFTP receiver process at each remote site uses it
               to determine which symbolic multicast groups it is a member of.

               Whenever a new remote site is added to or removed from the network, the Proclaim
               software needs to be informed of this fact by the corresponding change to
               cfg4.map. The new cfg4.map file must be propagated to all of the remote
               receiver sites. When such a change is made, the MLTC and receiver MFTP processes
               must be stopped and restarted to become aware of the change to cfg4.map.

               There are two types of entries in cfg4.map, Group and M-node, as detailed below.

               Group Entry
               The Group entry defines a logical group of receivers that can receive a multicast.
               The format is shown below.

                   Group_name : host1, host2, host4
                                                                        
                                (1)          (2)        (2)        (2)


               where the fields are as follows:

               (1) The symbolic multicast group name. You can use any name you like for the
               group name, using up to 80 alphanumeric or underscore characters.

               (2) A comma-separated list of remote receiver IP host names; the host names are the
               standard ones found in /etc/hosts or by using the Domain Name Service. To


Page 2 The send_files Program
add another receiver host name to a multicast group, just add the new name to that
group definition line. The individual host names must be separated by a single
comma and one space. To extend the definition line beyond 80 characters, type a
comma as the last character of the previous line and continue typing more individual
host names on a new line. Here is a sample Group entry:

    Group_all         :     albany,         toronto,       buffalo

M-node Entry
Because there may be more than one path to these receivers, a Class D address is not
directly associated with a group, but rather with an entity called a “Multicasting
Node,” or M-node. An M-node is a physical or symbolic node capable of routing an
IP address. The format for this type of entry in the cfg4.map file is shown below.

    Group_name.node                  :   IP_address
                                                     
            (1)            (2)                 (3)


where the fields are as follows:

(1) The symbolic multicast group name this multicast address will be associated
with. It must match a Group definition elsewhere in the cfg4.map file.

(2) The name of the node associated with this multicast address. This node is
permitted to be symbolic, but must exist as part of a link definition in
netcfg4.map. A symbolic node would be used, for example, on a LAN, where no
routing device is required. The node must be present, however, so that the MLTC
can determine a transmission path.

(3) A multicast IP address that represents this symbolic group address. This is a
Class D IP address, which you can also choose as long as it has the proper Class D
address format. (If your network can or will pass these packets to the Internet, Class
D addresses must be applied for through the Internet application process.) For an
internal intranet using the Proclaim software, these typically are chosen as:

        233.0.0.2         233.0.0.3        233.0.0.4       etc.
               Sample cfg4.map Entry
               Information for each group defined in the cfg4.map file should be entered as
               shown in the sample below:
               Group1 : hostA, hostB
                  Group1.M-node1 : 233.0.0.3
                  Group1.M-node2 : 233.0.0.5

               Note that each Group must have one or more M-node routes associated with it to
               provide alternate paths for file transmission. For example, for an SMDS network, the
               M-node is the name of the Ethernet-to-SMDS bridge. (For information on the scheme
               used for mapping IP multicast manual addresses to SMDS group addresses, see
               Appendix C.)

               The TCP/IP software requires a route assignment for each IP address listed in
               cfg4.map when they are used as destinations. An example of a command to add
               such a route using the UNIX route command looks like:

               route      add    -net 233.0.0.3            -interface         hub_host

               where hub_host is the name of the IP interface on the local hub host that the
               multicast address should be routed to. Normally, this will just be the host name of the
               hub machine. Under Digital's UNIX, the route may also be added using the
               netsetup utility; this entry should appear in the file /etc/routes so that it
               will be added after you reboot.

                       Note: The route needs only to be added on the hub machine and any remote
                       MFTP transmitter machines; it is not required on any remote receiver
                       machines.

               Comments may be added to the cfg4.map file by first typing the # character in
               column 1 of the line.

Editing the netcfg.map File
               Internally, the MLTC represents the network topology as a directed acyclic graph.
               Externally, you describe the connections that make up your network configuration to
               the MLTC in the netcfg4.map file. The netcfg4.map file contains a
               description of the network model used by MLTC to choose and schedule MFTP
               transmitters for each file transmission request. It is also used to calculate the
               transmission bandwidth for these requests. netcfg4.map is used only by the
               MLTC at the hub site, and is not needed on the remote transmitter or receiver
               machines.




Page 4 The send_files Program
The syntax of the lines in the netcfg.map file is as follows:

Link_local : 10 :                   hub_host,               host1
                                                                    
       link name         link capacity starting node name   ending node name
    (of your choice)    (in Mbits/sec.)


A sample netcfg.map is shown below:

Link_local             : 10    : hub_host, host1
   Link_a :             10 :    hub_host, INET
   Link_b :             1.17    : INET, CA1
   Link_c :             1.17    : INET, CA2
   Link_d :             1.17    : CA1, host2
   Link_e :             1.17    : CA1, host3
   Link_f :             1.17    : CA1, host4

In this example, the path from the local MFTP transmitter, hub_host, to the
remote receiver host host1 is via a single link (Link_local) whose capacity is
10 Mbits/sec. A file transfer to host1 may be scheduled by the MLTC to run at 10
Mbits/sec.

The absolute path to the remote receiver host host2 from the hub_host is via
three links in series: Link_a, Link_b and Link_d. The first is from
hub_host to INET at 10 Mbits/sec, followed by one from INET to CA1 at 1.17
Mbits/sec, followed finally by a link from CA1 to host2, also at 1.17 Mbits/sec. A
file transfer request that involves host2 as a destination may only proceed at the
speed of the slowest link, in this case, 1.17 Mbits/sec.

Notice that the paths to host2 and host3 share the same intermediate node,
namely CA1. If a file transfer is in progress to a group that includes host2, but not
host3, then a subsequent transfer request to a group that includes host3 will be
scheduled by the MLTC to start only after the one to host2 completes.

Note: For intermediate links in a series, the node names are arbitrary and do not
      represent IP host names. IP names are only required as the starting and
      ending node names of a complete connection.

Comments may be added to the netcfg4.map file by first typing the # character in
column 1 of the line.
Configuring the Local MFTP Transmitter
               You will need to configure the local MFTP transmitter at the hub site. (If you prefer,
               you can do this after step 2, but we recommend you do it now.) The MLTC starts
               either a local or remote MFTP transmitter process by initiating a request for an
               Internet Service on either the local or remote IP host. The name of the service used
               by the MLTC is MFTP4t, and is managed by the UNIX inetd daemon process.
               The MFTP transmitter service must be enabled on the hub machine in order for any
               MFTP transmissions to occur. Remote MFTP transmitters are optional at the remote
               Proclaim sites.

               There are two UNIX system configuration files that must be modified to enable this
               service: /etc/services and /etc/inetd.conf.

               Editing the /etc/services File
               On the hub machine, add the following line to the end of /etc/services:

               MFTP4t 6530/tcp                   #Proclaim MFTP Transmitter Service
                                                                                
                      (1)        (2)                                        (3)


               where the fields are as follows:

               (1) The service name. The name should be MFTP4t. The "t" designates a
               transmitter, as future releases may start receivers as Internet Services.

               (2) The Internet socket port number and protocol type associated with the service.
               The recommended convention is 65 plus the version of the software. In this case, it
               would be 6540, corresponding to version 4.0.

               (3) Comments follow the # character.

               The format of this file is described in more detail in the UNIX man page for
               services.

               Editing the /etc/inetd.conf File
               On the hub machine, add the following line to the end of /etc/inetd.conf:

       MFTP4t stream tcp nowait root /raid/MFTP4 MFTP4t /raid
                                                                                               
                     (1)        (2)    (3)        (4)       (5)       (6)             (7)       (8)


               where the fields are as follows:

               (1) The service name. This must match the service name in the services file.



Page 6 The send_files Program
          (2) The socket type.

          (3) The protocol type.

          (4) The blocking mode for the service.

          (5) The user id the service is to be started as.

          (6) The absolute path name of the executable program that represents the service.

          (7) The name of the running process that the MFTP transmitter will have. This must
          match the service name (1).

          (8) The directory that this process will use as the default directory for writing its log
          and error files to.

          The format of this file is described in more detail in the UNIX man page for
          inetd.conf.

          Initializing the Local MFTP Transmitter Service
          Once you have modified the /etc/inetd.conf file, you need to make the
          inetd daemon aware of this change by sending it a HUP (hangup) signal. Use the
          following two-step procedure:

          1. Identify the process id of the UNIX inetd daemon:
              # ps -ef | grep inetd

          This should return something like:
          root   414   1   0.0     Mar 16 ??       0:00.78         /usr/sbin/inetd


          2. The second field displayed is the process id (pid) of the inetd process. Use this
             value to issue the command:
              # kill -HUP 414

          The local MFTP transmitter service has now been configured on the hub machine,
          and is available as soon as the Proclaim software has been installed in the /raid
          directory there.


2. Installing Proclaim Networking Software at the Hub Site
          After you have configured the cfg4.map and the netcfg4.map files, as
          described above, you are ready to install the Proclaim networking software on your
          hub server.
                To install the Proclaim networking hub site package

               1. Change to the root user id.
               In the steps below, the # prompt indicates commands issued as the root user.

               2. Change to a temporary directory (e.g., /tmp), and extract the contents of the
                  archive:
                    # cd /tmp
                    # tar xv                            (for magnetic tape distribution)
               or
                    # tar xvf mltc4.tar                 (for electronic distribution)

               This copies the entire contents of the tape to the local directory (/tmp). (The contents
                  of this tape is shown in Appendix A.)

               3. Run the shell script called mltc4_setup to perform the rest of the installation
                  automatically:
                    # ./mltc4_setup

                    Note: The default destination directory for Proclaim files is /raid and is built
                          into the mltc4_setup script. If this is not the desired directory, edit
                          this script to use another target directory before execution. Throughout
                          the rest of this document, the /raid directory name refers to the
                          installation directory choice made here.

               Under Digital’s UNIX, this script will

                          Install the boot-time startup script mltc4_setup in /sbin/init.d
                           so that the MLTC daemon process will automatically start when the hub
                           machine is booted.

                          Create a soft link /sbin/rc4.d/S99mltc4 to the file
                           /sbin/init.d/mltc.

                          Move the other Proclaim files, including the MLTC and MFTP
                           executables and the API library and header files, to their target directory
                           (/raid). A complete list of these files is provided in Appendix A.

               4. Move your customized cfg4.map and netcfg4.map files to the target
                  directory (/raid).
               5. Start the MLTC daemon the first time with the following command:
                    # /sbin/init.d/mltc4 start




Page 8 The send_files Program
            There are some command line options for mltc4, although normally you won’t
               need to use them to change settings. These options are described below in the
               section MLTC Command Line Options.

            The start command runs two processes, MLTC4d and MLTC4. (MLTC4d is a
               wrapper script that spawns the MLTC4 daemon itself.)

            6. Confirm that these two processes are running by entering:
                  # ps -ef | grep MLTC4

            You should see a display listing the MLTC processes similar to this:
                  root     514   508 0.0 11:02:20  0:00.01 /raid/MLTC4 -e -m ./MFTP4
                      root     515  507 0.0 11:02:20   0:00.02 sh /raid/MLTC4d


            7. The MLTC writes error messages to the file /raid/MLTC4_nnn.err, where
               nnn is the Julian day of the year. (For example, error messages for January 1
               are written to the file /raid/MLTC4_000.err.) If you do not see the above
               MLTC processes after issuing the mltc start command, check the error file for
               errors. If the reason for the failure is not evident from this file, contact Proclaim
               Technical Support. If there are no errors, you are ready to install Proclaim
               networking software on the remote machines (see section 4. Installing Proclaim
               Networking Software at Remotes Sites on page 11).

Starting and Stopping the MLTC
            The MLTC daemon may be stopped at any time by issuing this command:
            # /sbin/init.d/mltc4 stop

            The MLTC daemon will automatically be restarted whenever the system is rebooted.
            It may be manually restarted with the command shown in step 5 above.

MLTC Error File
            The MLTC writes internal error messages to the text file
            /raid/MLTC4_nnn.err

            where nnn is the Julian day of the year. You may check this file for error messages
            if you suspect problems relating to the MLTC process.
MLTC Command Line Options
               The default command line options for MLTC are read from the file
               /raid/MLTC4.conf when the MLTC daemon process is started. These settings
               usually do not need to be adjusted. However, you can change them by using the
               options listed below (all are optional).

               Option Parameter              Description
               -C        cfg_file            Name of host configuration file (default is
                                             cfg4.map).
               -d        MFTP_delay_time     Seconds between MFTP launches (default is 5).
               -E        err_file            Name of MLTC error file (default is
                                             /raid/MLTC4_nnn.err, where nnn is the
                                             Julian day of the year.
               -e                            Turn off SNMP error reporting (default is SNMP
                                             reporting on).
               -h                            Help—prints this list of options.
               -m        MFTP_service_name Name of MFTP service (default is MFTP4t).
               -N        netcfg_file         Name of network configuration file (default is
                                             netcfg4.map).
               -o        MFTP_port_number    UDP port used by MFTP processes (default is
                                             6640). The recommended convention is 66 plus
                                             the version number. In this case, it would be 6640,
                                             corresponding to version 4.0. Note: This port is
                                             not the Internet socket port described on page 6.
               -p        pkt_throttle        Maximum number of packets that can be sent
                                             without an acknowledgment message.
               -q        max_pkt_resend      Maximum number of times that a given packet can
                                             be resent.




Page 10 The send_files Program
3. Configuring the Network at the Remote Sites
          Before you install the Proclaim networking software at the remote sites, be sure that
          a correct and up-to-date version of the cfg4.map file is present in the /raid
          directory of each remote machine. The simplest method is to treat the version of
          cfg4.map from the hub machine as the master copy, and copy it to the remote
          machine, using either the standard UNIX ftp or rcp utilities.

          The receiver MFTP process on a remote host joins all multicast groups that this host
          name is a member of. Membership is determined by the presence of the remote host
          name in one or more entries of the cfg4.map file on the remote host. The local
          /etc/hosts file on the remote machine is used to validate all individual host
          names found in cfg4.map, and so it is a good idea to also copy the /etc/hosts
          file from the hub machine to the remote machine to ensure consistency.

          If you want the MLTC on the hub machine to run a remote MFTP transmitter on a
          remote machine, add the MFTP transmitter service to the /etc/services and
          /etc/inetd.conf files on that remote machine. The procedure is the same one
          described in the section Configuring the Local MFTP Transmitter on page 6. If you
          don’t want remote MFTP transmission on a remote site at this time, skip this step.


4. Installing Proclaim Networking Software at Remotes Sites
          The MFTP receiver software for the remote site is bundled into an archive called
          mftp4.tar. It is a subset of the full Proclaim release. No MLTC is included. If an
          electronic archive of mftp4.tar is available, it may be sent to the remote machine
          via the standard UNIX ftp or rcp utilities.

           To install the Proclaim remote site package

          1. Change to the root user id.
          In the instructions below, the # prompt indicates commands issued as the root user.

          2. Change to a temporary directory (e.g., /tmp), and copy the contents of the
             archive tar from the hub site to here:
             # rcp hub_name:mftp4.tar remote_name:/tmp/mftp4.tar

          3. Run the shell script called mftp_setup to perform the rest of the installation
             automatically:
             #./mftp_setup

          Under Digital’s UNIX, this script will:
                          Install the boot-time startup script mftp4 in /sbin/init.d so that
                           the MFTP receiver daemon process will automatically start when the
                           remote machine is booted.

                          Create a soft link /sbin/rc4.d/S99mftp4 to the file
                           /sbin/init.d/mftp4.

                          Move the other MFTP files, including the MFTP executable, to their
                           target directory (/raid). A complete list of these files is provided in
                           Appendix A.

                   Note: The default destination directory for MFTP receiver files is /raid and
                         is built into the mftp4_setup script. If this is not the desired target
                         directory, you will need to edit this script to use another target directory
                         before execution.

               4. Move or copy your customized cfg4.map file to the target directory (/raid).
               5. Start the MFTP receiver daemon on the remote machine the first time with the
                  following command:
                   # /sbin/init.d/mftp4 start

               There are some command line options for MFTP, although normally you won’t need
                  to use them to change settings. These options are described below in the section
                  MFTP Command Line Options.

               The mftp start command runs two processes, MFTP4d and MFTP4. (MFTP4d is a
                  wrapper script that spawns the MFTP4 receiver process itself.)

               6. Confirm that these two processes are running by entering the following command
                  on the remote machine:
                   # ps -ef | grep MFTP4

               You should see a display listing the MFTP processes similar to this:
               root 507 1 0.0 11:02:20 ?? 0:00.04 sh /raid/MFTPd
                  root 515 507 0.0 11:02:20 ?? 0:00.02 /raid/MFTP -q 10 -r 1.0 -w 9 -p 25


               7. The MFTP receiver process writes error messages to the text file
                  MFTP4r_nnn.err, where nnn is the Julian day of the year. If you do not
                  see the above MFTP receiver processes after issuing the mftp start command,
                  check the error file on the remote machine for errors. If the reason for the failure
                  is not evident from this file, contact Proclaim Technical Support. If there are no
                  errors, proceed with the Proclaim software installation at the other remote sites.
               8. After you have successfully completed the installation at all remote sites, proceed
                  to install the Proclaim GUI software, as detailed on page 15.


Page 12 The send_files Program
Starting and Stopping the MFTP
            The MFTP receiver may be stopped at any time by issuing the following command:

            # /sbin/init.d/mftp4 stop

            The MFTP receiver will automatically be restarted whenever the system is rebooted.
            It may be manually restarted with the command shown in step 5 above.

MFTP Error and Log Files
            The MFTP process writes error messages to the text files:

            /raid/MFTP4t_nnn.err (transmitter)
               /raid/MFTP4r_nnn.err (receiver)

            which are located at the hub site and each Proclaim remote site. The messages in
            these files are for internal errors only, and do not refer to the status of individual
            transmission requests that may have failed for any number of external reasons.

            The status of each transmission request received by an MFTP receiver is written to
            the text files:

            /raid/MFTP4t_nnn.log (transmitter)
               /raid/MFTP4r_nnn.log (receiver)

            In addition, there are two more files containing detailed information about the file
            transfers:

                    MFTP4t_nnn.metrics (transmitter)
                    MFTP4r_nnn.metrics (receiver)

            Both failed and successful requests are logged to these files.
MFTP Command Line Options
               The default command line options for the MFTP receiver process are read from the
               file /raid/MFTP4.conf when the MFTP receiver daemon process is started.
               These settings normally do not need to be adjusted. However, you can change them
               by using the options listed below. Note that the -f and -a options are required when
               the MFTP program is run at a transmitter site.

      Option      Parameter                  Description
       -a         dest_name                  Symbolic group name or individual host name of the
                                             destination (required if run at a transmitter site).
       -f         file_name                  Name of file to transmit (required if run at a
                                             transmitter site).
       -C         cfg_name                   Name of host configuration file (default is
                                             cfg4.map).
       -c         max_cycles_ackn            Maximum cycles since last acknowledge.
       -d         dis_name                   Discard host name.
       -E         err_name                   Name of MFTP error file (default is
                                             MFTP4t_nnn.err (transmitter)
                                             MFTP4r_nnn.err (receiver).
       -g         max_block_gap              Maximum number of blocks active.
       -h                                    Help—prints this list of options.
       -L         log_name                   Name of MFTP log message file (default is
                                             MFTP4t_nnn.log (transmitter)
                                             MFTP4r_nnn.log (receiver).
       -l                                    Set loopback on.
       -m                                    Turn MFTP-SNMP messaging on (default is
                                             messaging off).
       -n                                    Set destination file no-overwrite on (default is file no-
                                             overwrite off).
       -o         port_number                UDP port number (default is 6640). For details, see
                                             page 10. Note: The port number must be the same for
                                             MFTP transmitters and receivers).
       -p         max_pkts_b/w_ackn          Maximum packets since last acknowledge.
       -q         max_request_cnt            Maximum resend requests allowed.
       -r         max_rate                   Maximum transfer rate.


Page 14 The send_files Program
    Option        Parameter                 Description
     -s           host_name                 Host name of transmitter (default is the local host).
     -t           ttl                       IP Time-to-Live value.
     -w           max_wind_down_cnt         Maximum cycles before shutdown.
     -v                                     Set diagnostic mode on (default is diagnostic mode
                                            off).


             Note: When the MLTC process on the hub machine launches an MFTP transmitter
                   process on behalf of a user request via the API, the MLTC automatically
                   selects the proper MFTP options and their values to use for that particular
                   transmission. Included in this list are the -f, -a, -r and -m settings. You may
                   view the values selected by the MLTC by issuing the following command on
                   the hub machine while a file transfer request is in progress:

             # ps -ef | grep MFTP4


5. Installing the Proclaim GUI Software
             The Proclaim GUI software is contained in two executables called
             Proclaim.fmx and Request_Loop. They are installed separately from the
             Proclaim networking software; Request_Loop is installed on your Oracle hub
             server and Proclaim.fmx is installed on your Oracle client machine.

             Note: Be sure that Oracle7 Server and SQL*Net are installed before installing the
                   Proclaim GUI software.

              To install the Proclaim GUI software on the hub server

             1. Log on to the hub server.

             2. Change to the root user id.
             3. Change to a temporary directory (e.g., /tmp), and extract the contents of the
                archive:
               # cd /tmp
               # tar xv                              (for magnetic tape distribution)
             or
               # tar xvf proclaim_client                      (for electronic distribution)

             This copies a series of *.zip and *.sql files to the local /tmp directory. (The contents
                of this tape is shown in Appendix A.)
               4. Copy Request_Loop into the same directory where the files to be transferred
                  are located.


                To install the Proclaim GUI software on the client machine

               1. Log on to the Oracle client machine.

               2. Create an ORAINST directory on your C: drive.
               3. Create the following two directories under ORAINST:

                       FORWIN95
                       FORWINNT

               4. Using ftp (or any other program you prefer) and a binary mode setting, copy
                  the *.zip files from the hub server to the client machine within their own
                  directories, so that the files are stored like this:

                       C:\ORAINST\FORWINNT\FORWINNT.ZIP
                       C:\ORAINST\FORWIN95\FORWIN95.ZIP
               5. On the client machine, within the new directories, un-zip each file by typing:
                   pkunzip -d zip_file_name.zip


6. Installing Oracle Forms
               At this point, you can run the Oracle installation program, ORAINST, to transfer all
               the files needed to run the Forms software into the ORANT directory.

                To install Oracle Forms on the client machine

               1. Log on to the Oracle client machine and go to the FORWINNT directory.

               2. Start ORAINST by double-clicking its icon.

               3. Complete the information in the standard Oracle Forms dialog boxes as they
                  appear. Be sure to install the software in the ORANT directory and install only
                  the Oracle Forms Runtime software.

                   To install Runtime, double-click on Developer 2000 - Forms 4.5.7.0.10, which
                   will open the selections below. Then select Forms Runtime 4.5.7.0.10 and press
                   the Install button. This installs all required Runtime files.
               4. Exit the ORAINST program.
               5. Copy the Proclaim.fmx executable from the hub server to the Oracle client
                  machine, into the Forms45 directory.



Page 16 The send_files Program
          Note: You need to copy Proclaim.fmx and run ORAINST on each machine
                where you want to run Oracle Forms.


7. Creating the Required Oracle7 Tables
          The Proclaim software uses predefined Oracle7 tables to store the data needed for
          file transmissions. To make it easier to create these tables, SQL scripts are included
          on the installation tar file.

          These SQL scripts may be modified to fit the requirements established by your DBA.
          For example, your DBA may want to increase the size of the tablespace or of
          individual tables.

          Note: Be sure your DBA has established a userid of “oracle” with Create
                permissions.

           To run the table creation scripts
          1. Using ftp (or any other program you prefer), copy the *.sql files from the
             Oracle server to the Oracle client machine.

          2. Log on to the Oracle server by typing:
             sqlplus oracle_username/password@tablespace_name

          3. Type the following command at the SQL> prompt:
             @pclm_make_new_tables.sql

          This main SQL procedure automatically calls additional SQL procedures to create
             the Oracle7 tables used by the Proclaim software:
                  dest
                  dest_list
                  dest_list_elements
                  dist_order
                  g_note
                  pfile
                  pfile_list
                  pfile_list_elements
                  pgroup
                  status

          Listing files are produced to verify everything was created properly.
           To create the file transmission database
          1. Type the following command at the SQL> prompt:
             @create_transfer_list.sql
               This creates the Oracle7 table transfer_list.
               2. Either manually or via a scheduling program, collect the information about the
                  files you want to transmit.
               3. Insert the information into the Proclaim file, transfer_list.
               The file format is shown below:
                  field name              null?          type
                    -----------------------------------------------------
                     start_d_t_key                          number(38)
                     asset_id                not null       varchar2(10)
                     destination             not null       varchar2(255)
                     time_need                              number(38)
                     send_status             not null       varchar2(20)
                     request_id                             number(38)
                     source                                 varchar2(10)


                To load the file transmission database

               1. Log on to the client machine where you have chosen to run Oracle Forms by
                  typing:
                   sqlplus oracle/password@tablespace_name

               2. Install the needed Proclaim stored procedures by typing and running:
                   @create_transfer_list_plsql.sql
                      @load_transfer_list_plsql.sql

               This creates two stored procedures, AddNewRequest and LoadRequests,
                  which transfer data stored in the transfer_list table into the Proclaim
                  Oracle7 tables. These stored procedures are executed every time data from the
                  transfer_list needs to be loaded into the Proclaim tables to allow file
                  transfers to occur, or when you press the Update button on the Operations
                  window.




Page 18 The send_files Program
8. Testing the System
          After you have installed the Proclaim software at the hub and remote sites, you are
          ready for testing. Use the send_files4 program (installed in /raid at the hub
          site) to send a sample data file to some selected destinations. This program
          automatically displays messages on your screen describing the results of each file
          transfer request.

          A complete description of send_files4 is found in Appendix D. A sample
          invocation is:
          send_files4 -f names_file -s -t 10 -v -d

          where names_file contains a user-selected set of destination host names and files
          to be transferred. You need to customize the contents of names_files to reflect
          your particular remote host configuration.

          You should also start the screen interface to verify Proclaim.fmx is installed
          properly.

           To verify that minimum system requirements are met

          1. Log on to the client machine where you loaded Proclaim.fmx and verify that
             SQL*Net is running by starting it and exiting.
          2. Verify that SQL*Plus is running by starting it and exiting.
          3. If you are using Windows NT, verify that it is running.


           To start the Proclaim software screen interface
          1. From the Oracle client desktop, start the Oracle Runform program by double-
             clicking its icon.

             The Runform logon window is displayed.


          2. In the File field, enter the path to Proclaim.fmx. Then enter your Oracle
             userid, password, and database name. You can leave the remaining fields blank.

          3. Press OK.

             The main Probita window is displayed.


          4. After you have verified the Proclaim GUI software runs properly, delete all files
             within the ORAINST directory.
Troubleshooting
               If there are any network problems on the transmitting hub site, send_files4 will
               write messages to an error file. This information is the starting point for diagnosing
               problems.

               Important: Be sure you run the send_files4 program as a normal user, not as
                          root. If you try to run the program as root, the following types of
                          messages will be displayed on your screen:

           P1503:MulticastAPI 1 96/03/20@14:51:15         (flicker.probita.com) Can't bind local
              address.

           96/03/20@14:51:15
           File: UNet.cxx Function: UNet_c::open Line: 390
           Can't bind local address: Address already in use

           96/03/20@14:51:15
           File: UNet.cxx Function: UNet_c::UNet_c          Line: 233
           Problem opening socket.

           96/03/20@14:51:15
           File: MulticastAPI.cxx Function: Multicaster API: private_init              Line: 285
           Couldn't create a socket.

           96/03/20@14:51:15
           File: MulticastAPI.cxx Function: MulticastAPI::MCA_set_diag              Line: 1775
           Failed during Multicaster API initialization.
           Error:mca_set_diag failed: Internal error;contact Probita

               If you see these messages, type (as root) the following command:
               # rm /tmp/MAPI_SC30

               and then rerun send_files4 as a normal user.

Getting Diagnostic Information
               To get diagnostic information about MLTC and MFTP transmitter processes, use the
               -d option of send_files4. This writes diagnostic information to the
               MFTP4t_nnn.log file at your hub site, and can be useful for troubleshooting.




Page 20 The send_files Program
MLTC and MFTP Transmitter Troubleshooting
           If the send_files4 test fails, first determine from the send_files4 output if
           the problem originates with the request itself (e.g., non-existent file or destination
           group name).

           Then verify network connectivity to one of the failed sites with the standard UNIX
           commands (ping, telnet, ftp).

           If connectivity is not an issue, next you should examine the following files at the hub
           site for explanatory messages:

           /raid/MFTP4t_nnn.log            Timed packet transmission and acknowledge statistics
           /raid/MFTP4t_nnn.err            Reports of internal MFTP transmitter problems
           /raid/MLTC4t_nnn.err            Reports of internal MLTC problems
           /raid/MFTP4t_nnn.metrics        Detailed transfer information


MFTP Receiver Troubleshooting
           If the problem is not obvious yet, or the test is partially successful (the file was
           successfully sent to some of the destinations, but failed to get to others), log on to one
           of the failed remote sites and examine the following files there for explanatory
           messages:

           /raid/MFTP4r_nnn.log            Status of each transmission request received from the hub
           /raid/MFTP4r_nnn.err            Reports of internal MFTP receiver problems
           /raid/MFTP4t_nnn.metrics        Detailed transfer information

           If you still have not found the source of the problem, contact Proclaim Technical
           Support. Be sure to have copies of the above log and error files (from both the hub
           and failed remote site) available, as well as a listing of the following files:

           From the hub site:

           /raid/MLTC4.conf
           /raid/cfg4.map
           /raid/netcfg4.map
           /etc/hosts

           From the failed remote site(s):

           /raid/MFTP4.conf
           /raid/cfg4.map
           /etc/hosts


SNMP Agents
           To be determined.
Page 22 The send_files Program

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:7
posted:5/1/2010
language:English
pages:22