test

Sun Secure File Transport User Guide

Chapter 3 Sun SFT How-To

This chapter explains how to perform the following procedures when installing, configuring, launching, and transitioning to the Sun SFT:

How-To Install Sun SFT

Sun SFT is a Solaris package download that is available with or without the Sun Automated Service Manager package. Download the Sun SFT-only package if you already have SUNWsasm installed.

  1. Install Service Tags

    If SUNWservicetags version 1.1.4 or higher is not already installed, download Services Tools Bundle from http://www.sun.com/service/stb/index.jsp and run its installer.

  2. For SFT-with-SASM bundle, extract packages from downloaded file:gunzip -c SUNWsftransport-*.tar.gz | tar xf -

    For SFT-only, uncompress downloaded package file:gunzip SUNWsftransport-.pkg.gz

  3. Install Sun Automated Service Manager: If SUNWsasm package is not already installed, run the following command: pkgadd -d SUNWsasm-*.pkg SUNWsasm

  4. Register SASM for data transport: /opt/SUNWsasm/bin/sasm transport -r

  5. Install the SFT Solaris package: pkgadd -d SUNWsftransport-{version}.pkg SUNWsftransport

    The actual file name may vary because it is based on the version number of your download. The actual file name will be similar to the above name.

  6. Provide the information requested during installation to configure the Sun SFT client.

    Note –

    When reinstalling or upgrading Sun SFT, the configuration files are preserved.

How-To Uninstall Sun SFT

You can uninstall Sun SFT when you no longer want to use the software. Before you upgrade Sun SFT, you must uninstall the older version.

To uninstall Sun SFT use the pkgrm command: pkgrm SUNWsftransport

This command removes the Sun SFT software only, but leaves configuration files, log files and configured data directories in place. This is to retain all custom settings when upgrading Sun SFT. For a complete uninstall, follow the instructions printed during the pkgrm operation to remove the remaining files and directories. If not used for any other components, you can also uninstall Sun Automated Service Manager: pkgrm SUNWsasm

How-To Upgrade Sun SFT

Remove the old package with the pkgrm command as described in How-To Uninstall Sun SFT. Then install the new package with the pkgadd command as described in How-To Install Sun SFT.

How-To Edit the Configuration File

The /etc/opt/SUNWsftransport/sftransport.xml configuration file is installed when the Sun SFT package is installed. This file configures the main daemon parameters as well as all processing slot definitions. (A slot is a virtual holding place for files within a transfer directory.) You can edit this file directly to change the Sun SFT configuration. After making changes to the configuration file, you must restart the daemon for configuration changes to take effect.

Note –

See the sftransport(4) man pages for specific details.

The following is an example of the sftransport.xml file:


<sftransport>
 <config version="2">
   <sleepSeconds>3600</sleepSeconds>
   <transferTries>3</transferTries>
   <secondsBetweenTries>120</secondsBetweenTries>
   <transferPath>/var/opt/SUNWsftransport/transfer</transferPath>
   <failedPath>/var/opt/SUNWsftransport/failed</failedPath>
   <diskThreshold>90</diskThreshold>
   <geo>AMER</geo>
 </config> 
 <slots>
   <slot type="explorer" threads="5" archivePath="/mnt/explorer_archive">
     <url>/v1/queue/explorer</url>
   </slot>
   <slot type="casedata" threads="1" archivePath="">
     <url>/v1/queue/case-data<url>
   </slot>
 </slots>
 </sftransport>

How-To Launch Sun SFT

You launch Sun SFT by running /opt/SUNWsftransport/bin/sftransport. You can use the --start option to launch Sun SFT. This command ensures that Sun Automated Service Manager (SASM) is running, and activates the Sun SFT bundle. SASM remembers which bundles are active and restores them to that state each time SASM restarts. SASM starts at system boot via the application/management/sasm service on Solaris 10, and via the /etc/init.d/sasm script on Solaris 9.

How-To Send a File with Priority

When you select transferPath during the pkgadd, a subdirectory called priority is created in the transferPath directory. Files placed in this priority subdirectory are given preference over other files being transferred in the transferPath directory; however, since validation and file transfers occur in parallel, some non-priority items might finish transferring before a priority file. Sun Explorer files that are generated for a specific support case (using the explorer -C option to provide a case number) are treated as priority files whether placed in the priority subdirectory or the main transfer directory.

Note –

If the sftransport.xml file is edited to change the transferPath to a new directory, a subdirectory called priority must exist in that new directory before you can startup the Sun SFT daemon.

How-To Send Explorer Files to Sun

Sun SFT has the ability to recognize two distinct types of Explorer files. It is important that you understand the distinction because there are differences in how Sun SFT processes each type, and how these files are processed at Sun.

When working with Sun Support Services, you might be asked to send an Explorer file for extended diagnostics and troubleshooting. Once Sun SFT is installed and configured, it can be used to send high-priority Explorer files. When you run Explorer, include the -C option and the Sun Support Services Service Request number. For example:

explorer -C 12345678 -options

This causes Sun SFT to prioritize the delivery of this Explorer file ahead of other files that might be queued, and it will deliver the file to a Sun-internal location where it can be readily accessed by Sun Support Services. Complete Explorer documentation is available on http://docs.sun.com