Figure 1 - ISP provides access services and ftp hosting services
Part A - Beehive File Transfer Overview (including SendFile.NET)
Part C- Beehive Client (SFSecure)
Appendix A - Beehive html Forms
Appendix B - Preparing Beehive for distribution
Part A - Beehive file transfer system overview
1 Overview of Desktop ftp clients and ftp manager
Beehive SF SFSecure is a drag and drop ftp client that permits html forms to be completed off-line and batch uploaded, along with attached files, to an ftp server somewhere on the net. The Beehive SF Secure application works as part of a system that also includes 1) any standards compliant ftp server and 2) the Beehive ftp manager. All Beehive connections are TCP/IP and may be made through PPP or a dedicated Internet IP connection. Beehive's ftp manager application enables a wide variety of client-server configurations - allowing ftp servers to be local or remote to the final file transfer destination. The Beehive ftp manager automatically moves the received Beehive folders and forms to the destination folder location of the administrator's choice, prints the received form as a notification and generates e-mail receipts.
Beehive is equally suitable for environments where a 3rd party Internet Service Provider (ISP) is providing Internet access services and hosting the ftp server or where a company is using it's own Intranet for ftp hosting. Beehive also uses a simple 1-2-3 receive operation :
Figure 1 - ISP provides access services and ftp hosting services
The diagram above shows remote Client Connections using the Beehive ftp forms desktop client or the Beehive SendFile.NET browser client. The diagram also shows a remote Printer Connection using the Beehive ftp Manager to poll an ISP hosted ftp server for files to download.
Figure 2 - Company provides ftp host services
The diagram also shows a configuration where the ftp server is local to the final destination (Printing Facility) and the Beehive ftp Manager is local to the server. This is also the configuration when the customer is running the Beehive File Transfer Appliance. When using the Beehive File Transfer appliance, the ftp manager runs directly on the server as a Linux application.
Setting up a Beehive Desktop system has four components:
1) the administrator must create the Beehive "send" directory on the ftp server and ensure that there is a userID and password that gives read/write access to this directory;
2) the administrator installs the Beehive ftp manager and creates the secure key for access to the ftp site using the read/write UserID and password. Beehive ftp forms uses a "secure key" system that hides the path and login information for the ftp site so that many users may send to the same directory without visibility into other people's transactions.
3) the administrator creates the customized client installers with custom form, splash screen, site key and serial number (see appendix B). The administrator will usually create one or more custom html forms for inclusion with the client, prior to distributing the client software. (see appendix A). The administrator may also change the client "splash" screen using ResEdit.
4) the Beehive ftp forms client application is installed at the user's location along with the secure key and any custom forms. Once the Beehive ftp forms client self extracting archive is decompressed, the user must run the Beehive ftp forms application and enter his user information before he may start to send jobs.
Once everything is configured, jobs may be sent using the Beehive client 1-2-3 procedures:
Jobs may also be retrieved using a 1-2-3 procedure:
Auto-Updating of Client Software
All Beehive clients - Macintosh, Windows and Browser, support an auto-updating protocol, that enables them to obtain the latest forms, splash screens, site keys and even application code when they first start-up. Before the client sends files, the application goes out and looks at the update server for changes and makes the new changes available to the user.
2 Overview of Sendfile.NET Browser Client
The Beehive file transfer system also includes the Sendfile.NET browser client. This client is setup for Beehive customers as part of the standard turnkey installation. SendFile.NET is a file transfer portal which works in conjunction with the Beehive file transfer system to provide both browser-based ftp services but also to manage all clients in the Beehive system. SendFile.NET is universal - anybody with an e-mail address and a browser can use it, without downloading software to their computer desktop! The Sendfile.NET client may send to a standard Beehive ftp manager location or to an end user's e-mail address. The diagram at the bottom of this page shows how SendFile can send to any user with an e-mail address. The diagram on page 4 shows how SendFile jobs alternatively may be serviced by a Beehive ftp manager.
www.SendFile.NET is the URL link to special set of Internet servers that enable reliable, secure, high speed file sending and receiving operations. Each Beehive/Sendfile account is given a unique 32 character account code which is added to the SendFile URL to ensure that the proper forms, site keys and logos are loaded into the client's browser along with the JAVA Applet, from our central server.
Each Beehive/SendFile sponsor account, i.e. the printer or prepress company that has purchased the subscription also receives a special URL that loads an administrative page. From this page the administrator may change forms, ftp keys and logos which will automatically propagated to all clients in their network - both Beehive desktop clients and SendFile browser clients.
Beehive/SendFile.NET File Transfer - By the Numbers:
The SendFile client may be launched by either clicking on the appropriate URL from a web page (see the "How to Send us files page" setup, or it may be launched by people dropping files or folders onto the Beehive "Fileprep" desktop icon. Either way, the SendFile portal will load the ftp Java applet, support html and the custom forms, keys and logo into the customer's browser. The standard SendFile window has buttons for Send Files, Inbox, Outbox and User Information. The default form and destination will appear in the content window and any files and folders dropped onto FilePrep will appear in the attachments window.
Sample SendFile page :
This page is using an e-mail recipient addressing scheme. Alternatively, addressing may be fixed to a specific Beehive ftp manager site.
The user merely fills out the form and clicks on the "Send Now" button at the bottom of the form when they are completed filling out the form and attaching files. A file transfer status window will open and show them the progress of their transfer.
SendFile jobs are handled in the Beehive system just like the desktop client jobs. The html form and the attachments are loaded into a Beehive job folder and the sender's receive the same e-mail notifications.
3 Beehive/SendFile Turnkey Setup
When a customer orders a Beehive turnkey subscription, Beehive Engineers set up almost everything! All the printing or prepress site does is add the "How to Send us Files" page to your web site. Your customers go to this special web page and download or link the ftp client they wish to use to send you files.
The SendFile.NET browser-based JAVA applet does not require an application to downloaded. Your custom account is assigned it's own 32 character extension to the SendFile URL and that unique URL is embedded in 2 locations in the "How to Send us Files" web page. One of the links is for new users, who are prompted to enter their user information, the other link is for existing users who are ready to begin to send you files.
The Beehive engineers also create a custom Macintosh ftp forms client and add it here. We add your logo, custom form and encrypted site key. When a customer clicks on the Mac client link, the application is automatically downloaded, decompressed and installed by their browser. The .sea.bin extension of the installer file tells the browser how to handle and install the application.
We create a self installing Windows archive, .exe file, for your custom Windows ftp client and add the link here. The Windows ftp forms .exe installer automatically installs the application and places the Beehive ftp forms drag and drop icon on the customer's desktop.
The Beehive engineers also place your logo/splash image on this page to complete the customization. Because this page is just html, you are free to copy it and change it in any way you choose.
The following is a simple outline of what Beehive engineers do to setup your site:
1) they send you a simple customization questionnaire which requests the following three items:
2) After the customer clients are made, the SendFile account is setup and the "How to Send us Files" page is made, the engineers mail the customer 2 emails:
1 Windows System Requirements for ftp manager
The Beehive ftp manager, Windows Version, is designed to run in a polling, non-dedicated mode.
The host should meet these minimum system requirements for the Beehive ftp manager:
2 Administrator's Installation Procedures
2.1 Setting up the ftp server and determining the connection parameters
The administrator must first tell the Beehive ftp manager about the connection parameters to the ftp server. These parameters include: the valid Internet name of the ftp server (or the machine TCP/IP address), the path to the destination directory on the server, the ftp UserID and the ftp password.
Probably the simplest setup for most sites is to allocate a subdirectory on your existing web site for your ftp path. This works at most sites because web servers almost always have an ftp server on them (be sure to confirm this with your ISP or network administrator).
For instance, if your web files are located on a directory called "/pub/myco" then create a new directory called "/pub/myco/jobsin". The name of the directory is arbitrary but be sure to enter whatever name you choose correctly into the site setups described later (remember that ftp is usually case sensitive).
Important FTP Configuration Warning - Be sure to confirm with your ISP or TCP/IP network administrator that you have been allocated sufficient disk space in your ftp path to accommodate inbound files. You must plan to have enough space to handle 3-5 of your largest received jobs at the same time. For instance, if the largest jobs you receive are 100Mb then you should have 300Mb of ftp disk space. After the Beehive ftp manager has handled an incoming job, you have the option of having it delete the job folder from the ftp directory. This parameter is especially important in configurations where the ftp server is housed at an ISP and you are billed based on the amount of disk storage allocated to your account.
2.2 Beehive ftp manager installation
Downloading using the URL and running Installer
1) Use the URLs emailed to you to download the ftp manager self extracting archive. The installer should automatically extract the installer files to the Windows Temp directory and then execute the "Setup.exe" file.
NOTE : if Setup.exe does not automatically execute, you may have to Double click on the "Setup.exe" file to begin the installation.
Figure 3- Beehive ftp manager installer welcome window
2) Select a disk location for the installed files.
Figure 4 - Selecting Installation Directory
Figure 5 - Selecting Program folder in Installer
3) Select a name for the Windows Program Folder, then click "Next".
4) Confirm the settings you have selected, then click "Next".
Figure 6 -Final Installer Configuration Parameters
5) When the installation is done, you will be prompted to restart your computer. You will need to do this to be able to use all of the special Beehive Drag and Drop functions which are extensions to the rudimentary Windows OS drag and drop functionality.
6) After the restart, you should open the Beehive folder in the Programs folder - you will have a Beehive ftp manager folder with the following contents:
Figure 7 - The Beehive ftp manager folder contents
Note: _isreg32.dll and DelsL1.isu are installed by the Beehive ftp manager installer but are for the internal use of the application only. After the ftp manager application is configured, it will create 3 more configuration files : "FTPMan.ext", "FTPMan.prx" "FTPMan.cfg" and "FTPMan.smt". These files need to be in the ftp manager folder for proper operation.
2.3 Configuring the Beehive ftp manager
Once the Beehive ftp manager software has been installed you must launch it and configure it. Configuration includes selecting a destination folder for the downloaded files, selecting the polling schedule, and turning printing on or off. It also includes configuring the connection setup between the ftp manager and the ftp server and optionally generating a secure key.
First, open the ftp manager connection setup by selecting FTP-Manager/Connection Setup from the menu bar.
Figure 8 - Selecting the Connection Setup from the FTP-Manager menu
This will open the Connection setup window:
Figure 9 -Creating a new ftp site setup
Enter the appropriate ftp parameters and check compression if desired.
When you have entered your ftp connection parameters, you may test them by clicking the "Test" button. The ftp manager will start a session and displays the file transfer window:
Figure 10 - File Transfer Window during FTP Connection test
If the connection is OK then the FTP Manager will log in to the ftp site and return a listing of the contents of the Site Content for that directory. The listing below shows 4 jobs waiting for pickup.
Figure 11 - Successful FTP Connection test
Most errors can be detected by the test and an appropriate message should be returned if the connection failed. The FTP manager will display all errors in an error log Window. This error window is non-modal and will not affect the operation of the ftp manager.
The FTP log on error is obvious, check that you have the ftp connection parameters entered correctly, especially the UserID and password.
Figure 12 - FTP Logon failure, Showing complete Error Console
The "unable to connect to ftp server" error usually means that either the TCP/IP connection to the Internet is faulty or the "server name" (usually the site name or the TCP/IP address of ftp server) is incorrect.
Figure 13 - FTP Connection test failure
When the "Command: MKD thebeehive.com" fails, it means that the userID and password does not provide write access, i.e. the Beehive ftp forms client cannot create the directory for the job on the ftp server.
Figure 14 - FTP Make Directory failure
In some Internet configurations, most notably, those with an Internet Firewall installed, you may have to name an Internet proxy for the connection. On both Mac and Windows the proxy can be entered as a name (proxy.thebeehive.com) or in dotted decimal format (128.10.200.18). The default port that Beehive uses for the FTP proxy is 80. This is the port that is most commonly used for proxies. In case the proxy is on a port other than port 80, the user can add a colon or a space after the server name/IP address and then enter the port number; for example, if the proxy is on port 100, the user can type
"proxy.thebeehive.com:100" or "proxy.myco.com 100"
In Windows, there is no Internet Config program as there is on the Macintosh, so Beehive must add this information in the "Proxy" window - Select FTP-Manager/Proxy Settings from the Menu bar.
Figure 15 -Selecting FTP Proxy settings from menu bar
The "Use FTP Proxy" checkbox determines whether a FTP proxy is to be used, and the name/IP address of the ftp proxy, and the port can be entered in the edit fields below, along with the Usr ID and password.
Figure 16 -FTP Proxy settings Window
Be sure to consult with your network administrator to determine if a proxy is being used. ISP based configurations rarely use a proxy.
2.3.3 Making a secure site key
Once you have configured a successful ftp site configuration, you may want to encrypt it and save it as a secure key, especially if you are going to have a large number of people sending into the same site and path. By saving the site information as a secure key, you will allow your users to all share the same "send" directory in a completely private way (nobody knows where the jobs are physically going, nor do they know the userID and password).
After the FTP connection has been successfully tested, press the "Make FTP Key" and select a name and folder destination for the encrypted key file.
Figure 17 - Saving a secure FTP Key File
Be sure to name the file something logical so your users will know where they are sending their job. After the key has been saved, be sure to distribute it with your Beehive ftp forms client by inserting it into the "Keys" directory of the Beehive ftp forms client installer.
2.3.4 Email Preferences for Receipts
Beehive ftp manager needs some information in order to send receipts by e-mail. Open the SMTP settings from the FTP-Manager Menu.
Figure 18 - Opening the SMTP Settings
This will open the SMTP settings window.
Figure 19 -SMTP Settings Window
2.3.5 Beehive ftp manager Configuration Window
Now select FTP-Manager/Configure from the menu bar to finish configuring the Beehive ftp manager:
Figure 20 -Selecting the Configure window
This will open the configuration window:
Figure 21 - FTP Manager Configuration window
NOTE : The ftp manager has the ability to route files differently based upon the name of the destination ftp site. For example, you may Add a site name called "JohnsJobs". Then select the newly created JohnsJobs item from the destination list and then browse to select it's destination folder. You would transfer files to this folder location when the "To:" field is set to "JohnsJobs" in the Beehive ftp forms client. When multiple folder destinations are set up, the administrator must ensure that the key "site name" created in the ftp site window matches the Destination Address Name created in the FTP Manager Configuration. If there is no match for the contents of the To: field on an inbound ftp form - it is sent to the default address.
2.3.6 Configuring File Mappings
File mappings are used when files are sent cross-platform. Windows files do not have file types like on the Mac, but they do have extensions to determine which application will open them. On the other hand, Mac files have file types and creator codes, but Mac file names don't usually have extensions (if they do, they are not significant).
With the Windows version of Beehive ftp manager file mappings only take effect when the "Decode MacBinary Files" checkbox is checked in the FTP manager config window. When a macBinary file comes in, the FTP manager can try to assign an appropriate file name extension to that file. To open the file mapping window, select File Mappings from the FTP-Manager Menu bar.
Figure 22 - Opening the File Mappings Window
This action will open the mappings window:
Figure 23 -File Mappings Window
The file mappings window is used to assign PC extensions to Mac file types. For example, files of type 'TEXT' are text files and should receive the .txt extension on windows so they will get the right icon and will be opened with notepad. To do this, the user would type TEXT in the little edit field in the middle of the file mapping window and then press the <<Add button to add TEXT to the file type list on the left of the window. Then he can select TEXT from that list and he should check the "Text" radio button because it is an ASCII file. In that case, line feed characters will be added to the file so that it is readable on windows. Then he should type in "txt" in the edit field to the right of the window and click on the ^Set^ button to set the extension for TEXT files.
Optionally, the user can add non-default creator codes for a file type, as there are different types of TEXT files. For example, html files are also of type TEXT on the mac, but the user may want to open them in Netscape. In that case, he would select TEXT from the file type list, type in the creator code of Netscape in the edit file in the middle of the window and click the Add>> button to add it to the creator code list to the right. Then he would select that creator code and type in "htm" in the edit field on the right and click the ^Set^ button to give HTML files the .htm extension so they will be opened with netscape. Normally, the file type should be enough to determine its extension, so there will be no need for non-default creator codes.
If the Macintosh version of FTP manager downloads a file that has been sent with a Windows client, it does not know which file type and creator code to give to that file. This is what file mappings are used for. In that case, the FTP manager will look at the file's extension, and map the corresponding Macintosh file type/creator code to it so the file will receive the correct icon. On the Mac, the way these file mappings are made is determined by the File mappings window of Internet Config, which pops open when File Mappings is selected in beehive. In this window there is a list of extensions and their corresponding Macintosh file types and creator codes. For example, a .txt file is a text file so it gets the 'TEXT' file type and 'ttxt' (SimpleText) creator code. Also, the plain text radio button is checked to say that this is an ASCII file, so the FTP manager will strip any line feed characters from the windows text file before storing it on the mac, to make it readable (mac text uses only carriage returns whereas windows uses <CRLF> at the end of each line). Also, the user can choose to post process a file and choose an application to do the post processing.
2.4 Starting the Beehive ftp manager
Once you have configured the ftp manager, you may start it by selecting "Transfer Files" from the FTP-Manager menu.
Figure 24 -Starting Beehive ftp manager
You will see the ftp Manager Status Window appear.
Figure 25 -ftp manager, status Idle
Between polling periods, the ftp manager console is idle.
When the time for the next session arrives, the ftp manager will change it's status to busy and begin to download the files. The file transfer gauge will show the percentage of the file transferred as well as the file name in the activity log.
Figure 26 -Beehive ftp manager File Transfer Window
The information in the activity log is also written to file if you selected logging in the configuration window.
The Beehive ftp manager will create folders in the destination directory for each of the jobs received. The folders are created using a naming convention that includes the first 8 characters of the sender's company name followed by a unique 3 digit extension.
Figure 27 -Jobs in Destination Folder after ftp manager session
If you open up each of the job folders, you will find the attached files and folders as well as the form (if the ftp manager has been configured to put the form messages in with the job folder). Forms may be displayed by double-clicking on them, they will be opened by the Beehive forms viewer.
Figure 28 -Contents of job folder showing Beehive form
After the files are moved, the Beehive ftp manager will open the Beehive forms viewer to print the forms.
Figure 29 -Beehive forms viewer printing a received form
If a printing error occurs, the ftp manager will display an error dialog.
Figure 30 -Beehive forms printing error message
When the transfer is over, the ftp manager status will return to idle.
2.5 Beehive ftp manager listing and Queue Management
The most important new features in the version 2.5 release of Beehive ftp manager are in the areas of ftp queue management. This is especially important in environments that are using and ISP to house the ftp server.
When the ftp manager is running, it displays it's Status Window. Starting in Version 2.5, administrators can open a listing of the jobs in the ftp queue by simply clicking on the "Open FTP Site" button.
This will open the ftp site listing, showing all of the jobs ready to be processed by the ftp manager.
Figure 31 -Opening FTP Site Contents by clicking on "Open FTP Site" button.
The administrator may further explore the contents of each job by double clicking on any of the folders to see their contents. To navigate back up the directory structure the user may double-click on the "parent" folder.
The ftp site content window allows the administrator 2 main processing functions:
To delete a file or folder, just highlight it (or multiples by shift-clicking) and then press the "Delete" button.
Figure 33 -Delete Dialog Box.
To move a job up to the top of the queue and begin to immediately process it, select it and then press the "Process Jobs Now" button.
With the ftp manager, you may also drag and drop files and folders to (and from) the ftp listing. Operation is just as you would expect:
To retrieve files from the ftp server - click on the file or folder that you want to retrieve, and while you hold the mouse down, drag the file or folder to your local drive. While the file is being downloaded, the file transfer window will appear to give you a status of the download.
To send files to the ftp server - click on a file (or folder) on your local drive, and while you hold the mouse down, drag it to the ftp listing. While the file is being downloaded, the file transfer window will appear to give you a status of the download.
Important Note: It is not recommended that you drag and drop files to and from the standard Beehive ftp forms "receive" folder. The folders named "1", "2", etc. are specially designed to be processed by the ftp manager. It is better to use the "process" button so that all of the tasks such as file decoding, receipts, etc. are done for the jobs that were sent with a form.
3 Help and Troubleshooting
The following hints are provided to help you solve any problems that you might experience in the setup and operation of your Beehive ftp manager.
Standard Setup Test: To test the connection, just single click on the test button (in the connection setup window) after you have configured your ftp connection setup. If the ftp connection is successful, you will see a dialog box that says connection OK. If an error occurs, then you must fix the connection parameters, i.e. ensure that the ftp name or TCP/IP address of the server is right, the correct ftp path is listed, and the login user ID and password values are correct. Then try the "test" button again.
Error Description: When you click on the "Test" button in the connection setup and you get a connection error message.
Solution: this means that one of the ftp parameters for your ftp site is not properly configured. Check with your admin for the correct Internet name of the ftp server (or TCP/IP address), path, UserID and Password. Also remember that ftp is case sensitive.
The "unable to connect to ftp server" error usually means that either the TCP/IP connection to the Internet is faulty or the "server name" (usually the site domain name or the TCP/IP address of ftp server) is incorrect.
When the "Command: MKD XXXXXX.com" fails, it means that the userID and password does not provide write access, i.e. the Beehive ftp forms client cannot create the directory for the job on the destination ftp server. Beehive ftp forms will typically not work with anonymous ftp rights because this typically only provides read and retrieve privileges.
The "FTP log on error" is obvious, check that you have the ftp connection parameters entered correctly, especially the UserID and password.
Problem : A job has been sent to the ftp server but the ftp manager never processes it.
Solution : It is possible that the ftp site information for the ftp manager does not match the ftp site key name in the ftp forms client (the site name in the To: field of the client determines where the files are being sent).
Problem : A job has been sent to the ftp server but the ftp manager never send the e-mail receipt.
Solution : Ensure that the SMTP server is correctly configured under the ftp manager menu item. Also ensure that the "return receipts" checkbox is enabled in the ftp manager configuration window.
Problem : A job has been sent to the Beehive ftp manager but the ftp manager never prints the form.
Solution : First ensure that a copy of the Beehive Forms viewer resides on the same computer as the Beehive ftp manager and that a printer has been chosen on the ftp manager computer. If this has been done, then you should be able to manually print from the forms viewer after double-clicking on the form.
If the form prints from the viewer then ensure that the "Print Messages" checkbox is selected in the Configure Gateway window.
NOTES : When testing the Beehive ftp manager, you do not have to wait for the polling schedule, you can force a session by selecting "Transfer Files" from the FTP-Manager menu.
If any other problem occurs, contact your system administrator or call Beehive Software Technical Support at 360-738-6863.
Part C - Beehive Client for Windows SFSecure
1 Overview and System Requirements
Beehive SFSecure is a file transfer application that permits html forms, prepared off-line, to be batch uploaded to any Internet (or Intranet) ftp server. The Beehive SFSecure application uses a PPP, Multilink PPP, or network TCP/IP connection to make its connection to the ftp server. The TCP/IP connection must be setup and tested prior to installing Beehive SFSecure. If you have any questions about this TCP/IP connection requirement, consult your ISP or network administrator.
Beehive SFSecure is installed by running the "setup.exe" application . After the installer is completed, the user must run the "FTPForms.exe" application and enter information about his name, company and address in the user information window. He is now ready to Drag and Drop folders onto the Beehive ftp forms icon.
Beehive ftp forms System Requirements:
2.1 Downloading the application from the URL
Click on the URL for the Windows client in the "How to send us files" page. The browser should automatically download the self extracting archive, uncompress it and load the installer contents in the Windows Temp folder. It should then immediately execute the Setup.exe installer and begin to prompt you through the installation. NOTE: if the Setup.exe installer doesn't start immediately, go to the ftp forms folder in the Windows Temp folder and double-click on the "Setup.exe" file.
Figure 1 -Contents of the Beehive ftp forms installer
First you will see the installer welcome screen, click "next" to advance to select the destination folder.
Figure 2 -Beehive Installer Welcome Window
You may select the default "\Beehive\SFSecure" directory or you may select another directory using the "browse" button.
Figure 3 - Selecting the Destination Directory for the Installer
Finally you may name the Windows program folder. The default is "Beehive".
Figure 4 -Selecting the Windows Program Folder for Beehive
When you select "Next" the installer will complete the installation according to the parameters you selected.
Figure 5 -Confirming the Beehive Installation Information
At the end of the installation, you will be prompted to restart your machine. This will add the drag and drop extensions to windows.
Figure 6 -Restarting computer after Installation
The installation creates a directory called "\Beehive\SFSecure" in the Programs folder and installs a "SFSecure.exe" application file, Windows Help, a "forms template" subdirectory and whatever customization files were added to the zipped installer file.
Customization Notes: A custom splash screen file - "splash.bmp" file should be copied into the main directory of the installer disk/zip file. Any custom form templates or secure keys can go into the "Form Templates" and "Keys" subdirectories in the zip file, respectively. The keys will automatically be added to the ftp site list (and the folder is deleted) if the user runs the Beehive SFSecure application when prompted.
Special TCP/IP Connection Installation Note:
These installation instructions assume that TCP/IP or PPP has been correctly setup on the machine you are working with. A simple test to ensure this is to run Netscape (or Internet Explorer) and confirm that it is working; typically if Netscape runs, then so will Beehive. If you do not have your TCP/IP correctly configured, then please consult Appendix B - configuring TCP/IP connectivity on a Windows machine.
After you have installedBeehive SFSecure, you may launch the application for the first time, by either double-clicking on the Beehive Shortcut on the desktop or by dragging your files (or folders) onto the Beehive icon. Beehive will first prompt you with the user Information Window so all your messages will automatically carry information about who you are.
Any information entered here will be entered into the "From" field on all forms you send and will be auto-filled into the user fields in the html forms that the administrator has configured the forms for "Auto-fill".
Figure 9 -Beehive User Information Window
Fill out all the fields (especially the E-mail, Name and Phone number fields which are mandatory). DO NOT ENTER A PASSWORD, UNLESS YOU ALREADY HAVE A SENDFILE (Browser client) ACCOUNT, THE SYSTEM WILL ASSIGN YOU PASSWORD AND SEND IT TO YOUR EMAIL BOX)!
Click Send. The system will quickly register you, check for updates and then open the Beehive Sendfile Secure Application. You are now ready to use the Beehive Application - Proceed to section 3 for instructions on how to transfer files and forms (unless you want to setup your own ftp site, then continue with section 2.3).
Changing User Information
If you ever need to update your user information, launch the program by double-clicking on the Beehive SFSecure icon. You will see the standard Beehive menu bar. Select "User Setup" from the "File menu". The User Infomation window will open, make your changes and click OK. Use a tab to move from field to field in the User Setup window. Clicking "Cancel" closes the window without saving your changes.
Figure 8 -Selecting User Information from Menu
2.3 Setting up the connection to the ftp server
After Beehive has been installed, you can tell Beehive how to connect to any ftp server you choose. Select "Site List" from the SendFile item in the menu bar.
Figure 10 -Opening the Beehive Site List from the menu
This will open the FTP Site List window.
Figure 11 -The Beehive Site List Window, showing a secure key
If the administrator has preconfigured the installer with one or more secure ftp sites, they should be listed in the window.
If the sites are "secure" they will have a red "Stop hand" icon and will only display the Site Name (the Server, Path, UserID and Password info is encrypted). If the site is "open" (read/write) then all of the site parameters will be displayed.
You may select a default send site by highlighting a name in the site window and then clicking on the "Default Send Site" button. The default site will be chosen as the destination for all forms unless the user changes the "To: field in the forms window when they are preparing a form.
Adding an ftp site
Your administrator will usually preconfigure Beehive with a secure site key as the default send site but you may also want to add some other "non-secure" destinations for other ftp workflows that you may need. You may also add "secure" keys to your site list that may have been distributed by the administrator.
To add a non-secure site to the list:
"Cancel" will exit the window without any changes.
Figure 12 -Adding a non-secure FTP site to the site list
To add a "secure" site to the list (if you have the encrypted key on your computer):
"Cancel" will exit the window without any changes.
Figure 13 - Adding a secure FTP site key to the site list
2.4 Configuring Beehive for use with a Proxy Server
If you are going to use Beehive in an environment that has a proxy server to control outgoing ftp access, then you will need to tell Beehive ftp forms about the proxy server. Select "Proxy Settings" from the FTP menu item.
This will open the proxy window. Check the "Use FTP Proxy" checkbox and enter the value given to you by your firewall administrator.
Figure 14- Configuring Beehive for use with a proxy server.
3.1 Dragging and dropping files and selecting forms
Beehive may be launched one of three ways: either 1) by dragging files or folders onto the Beehive ftp forms icon or 2) by double-clicking on the icon or 3) by using the Windows "Send to" command.
Dragging and Dropping with a Default form selected
In many environments, the Beehive sender is using the same form over and over. In cases like this, it is efficient to select a default form for auto-selection whenever files or folders are dragged and dropped onto the Beehive icon.
Figure 15 -Dragging a folder onto the Beehive icon to launch the application
If Beehive has a default form selected - when you drag files or folders onto the Beehive icon, the program will open directly to the default form window with the default ftp site name in the "To:" field and the dragged and dropped folders listed as attachments. Just fill out the form and click "send" to complete the transfer.
If you want to select a default form:
NOTE: Any html form template that is loaded into the forms template folder of the Beehive ftp forms folder will be available for selection in the popup list.
Dragging and Dropping in multiple form environments
In some multiple forms environments, the Beehive sender needs to make a choice of which form he needs to use after he has dragged files onto the Beehive icon. Beehive has an "Ask User" option that will prompt the user for which form to use after they have dragged a folder onto the icon.
Figure 16 -Ask User for Startup form after drag and drop
After the user selects the form from the "Startup Form" window that pops open - Beehive will open directly to the selected form window with the default ftp site name in the "To:" field and the dragged and dropped folders listed as attachments. Just fill out the form and click "send" to complete the transfer.
If you want to enable the "Ask User" forms selection function:
The Beehive window also has an "Auto Quit after send" checkbox that will automatically quit the application when it is done sending files.
Double-clicking to Launch the program
If you double-click on the Beehive icon, then the application will open and display the Beehive "Welcome to SendFile Secure" Window. To proceed into offline form preparation, select a form from the popup button and then click on "Open Form" - the selected form window will open with the default ftp site selected as the destination in the "To:" field and with no files attached.
Figure 17 - Beehive SendFile Secure Welcome Window and Splash Image
Using the Windows "Send to:" command
Windows 95 and NT offer a special "Send to" feature which Beehive supports. When you right-click on any file or folder, a pop-up menu will open allowing you to select the "send to" command.
If you copied a FTPForms shortcut into the "Send to" directory in the Windows directory, then Beehive or FTPForms (prior to V3.0) will be listed as one of the Send to:" options. If you select FTPForms as the "Send to" destination - the Beehive application will open with the selected files or folders as attachments to the default form.
Figure 18 - Using the Windows Send to command
Selecting Forms from the Menu bar
You may also launch forms by selecting "New " from the "Forms" menu. The default form will be launched.
After the form has been selected, either from the menu, or by default during drag and drop, or by selection from the popup list of the welcome window.. the Beehive form window will open and display the selected form in a scrollable panel.
Figure 19 - A new form window in Beehive ftp forms
Attaching Files to your Beehive job may be accomplished two ways:
1) you may launch the program by dragging file(s) or folder(s) directly onto the Beehive icon. Any file(s) or folder(s) dropped on the icon will appear in the Attached files list.
2) if you have opened a form from the Beehive Forms window or using Forms/New menu item the form will open with no attachments. However once a form is open you may click on the "Add Files.." button on the bottom of the form. You will be presented with the standard File Attachment dialog box.
To remove an unwanted file(s) from your attachment list, just highlight the file and then select the "Remove Files" button on the bottom of the form window.
IMPORTANT NOTE: Starting in version 3.0, Beehive ftp forms desktop user may also drag and drop files and folders directly into the attachment list.
Once you have filled out a new message form and attached the files, you may immediately send the job if you choose. Just click on the "Send now" button. The job will be moved into the "Outbox" and then immediately sent to the ftp site destination chosen with the "To" button on the form. You may change the ftp site destination by selecting from the list in the "To:" field popup.
Version 3.0 offers an alternative e-mail addressing scheme if the administrator has included the "recipient-email" field in the form:
Enter E-mail Address of Recipient : <INPUT TYPE="text" NAME="recipient-email" SIZE="41">
If this field is available and the user fills it out with a valid e-mail address for a recipient, then the job will be stored into the ftp server and the intended recipient will be notified with an e-mail, containing a URL in it, to link him into Sendfile.NET where he can pick up the file. See the Sendfile diagram in the Overview section for more information on using this feature.
Once the job starts sending, the file transfer window will be displayed.
Figure 20 - File Transfer Status Window
After the job is completed sending, the icon in the "Outbox" window will change from an open envelope to a closed envelope.
Holding a Message
You may prepare several jobs and hold them until you are done preparing them all, and then send them all together. After you have finished preparing each job, just click on the "Send later" button. A copy of the job will be held in the FTP outbox (it will have an open envelope icon until it is successfully sent).
3.4 Working with the Outbox Window
The "Outbox" window displays all jobs both unsent and sent. It allows you to accomplish 2 basic operations:
1) to select unsent jobs and send them and
2) to review previously sent jobs and copy them into new forms for reuse.
To open the FTP Outbox window select "Outbox" from the SendFile menu item.
This will open the Outbox window:
To select any message just click on the item in the list; it will display the form and the message header info.
Figure 21 - Outbox
Once you have selected and displayed a message, you may:
When you are done with the Outbox window select Close.
3.5 Receiving and Sending Files with the Site List
New to version 2.5 is the Site List window. This window displays all of the ftp sites for which you have access. This listing can be displayed by selecting the "Site List" menu item from the SendFile menu.
Figure 22 - FTP site list showing an "open" site
From the site list, you can open any of the non-secure sites merely by double-clicking on their name in the site list. The client will immediately make a connection to the server and open a listing of the directory/path defined in the FTP Connection Setup Window.
You can navigate through the directories in the usual fashion, namely by double clicking on a directory, or by using the keyboard to highlight a directory and pressing the enter key. The operation of this window is consistent with other Internet programs.
The directory list has full drag and drop functionality. Select an item from the list, or shift-select multiple items, and then drag them anywhere in the Windows file system to download them to that location. This works for files and folders. Dragging items to the trash will delete them. A confirmation message will be displayed. Also, files or folders can be dragged from Windows into the FTP Site Content window, to upload those items into the current directory.
Figure 23 -FTP listing obtained by double-clicking on an "open" site from the site list
File Transfer Options
The "Auto", "Text" and "Binary" controls specify the mode in which files will be transferred to and from the FTP site. Normally, the user will not have to deal with this. He can just maintain the default settings, and all the files sent to the FTP site will be properly encoded. In some cases, e.g. the user is transferring html files to a web site, they may choose text to ensure that the files aren't treated as binary files.
3.6 Using the Beehive Client in Auto-Send Mode
Starting in version 2.7, Beehive offers an Auto-Send mode that allows users to continually poll a location for new files and then automatically send them to the default ftp destination. To enable this feature select the "Auto-Send Config" item from the "SendFile" menu.
The Auto-Send Config window will open:
Figure 24 - Auto-Send Config window
Starting in version 3.0, Beehive desktop clients may be automatically have their forms, ftp site keys, logo/splash screens and even the executable version upgraded from the corresponding central Sendfile administration account. To enable this feature select the "Update Settings" item from the "SendFile" menu.
The Update settings window will open:
Figure 25 - Update Settings window
Enter the IP address of the update host, if you are using the Beehive sendfile system, keep the default.
Using the radio button list select your update option:
Beehive ftp forms has an online help function which opens from within the program. When the help file opens, it will have an index of topics - just click on the appropriate topic and it will open the page.
Figure 26 -Help Window
The Beehive ftp forms Windows client also comes with the user manual in .pdf format. You will need the Acrobat reader to read this manual online.
Beehive was designed to eliminate a number of typical ftp file transfer problems experienced by users. If a problem occurs, it usually means that something is improperly configured in the ftp site setup. To test the connection, just launch Beehive and open the FTP site window from the SendFile menu. Select the site you want to test by highlighting it in the list. Now select "Edit site", this will open a window which contains a "Test" button that can check if the connection is properly setup. If the connection is OK a dialog box will return a "No error" message. If an error dialog occurs, then you must fix the site setup, then save and test again:
Error Description: When you click on the "Send" button the job is not sent and you receive a user licensing message.
Solution: this means that the serial number entered in the User Setup Window is invalid or missing; contact your administrator and receive a valid number. This may also indicate that the user did not "launch" the application as the last part of the installation procedure (only required in versions prior to v2.5).
Error Description: When a form opens up, the user information fields are not being auto-filled.
Solution: the administrator probably did not set up the forms template correctly. The template must contain the correct field names in all caps in the form fields to enable auto-fill.
Error Description: There are no destination options in the "To:" field of the forms.
Solution: the administrator probably did not distribute a secure key for the destination site in the installer archive. Contact the administrator to obtain this file.
Error Description: There are no custom forms, destination site keys, serial number or custom splash screen.
Solution: the administrator may not have added the custom form in the forms template folder of the installer, the site key into the keys folder, and the serial number and splash.bmp file into the root of the installer directory. However, more than likely, this error was caused when the user did not select the "launch" checkbox at the end of the installation. Launching the application finishes the installation by loading all of the customizations including forms, site keys, serial number and splash screen. Reinstall and check "launch" button.
Error Description : Client (manager or forms client attempts to connect to ftp server and just hangs.
Before you can configure this setup you must get the following parameters from your firewall administrator:
Procedure for Configuration:
In Shorthand:
If any other problem occurs contact your system administrator or call Beehive Software Technical Support at 360-738-6863.
Appendix A - Beehive html Forms
Starting in version 2.7, Beehive clients use native html for forms, clients prior to V2.7 used a forms converter which was required to make Beehive forms templates. This appendix assumes that the client software is version 2.7 or later.
Beehive forms may be viewed merely by double-clicking on them. The Beehive Forms viewer is the creator of the received forms and will automatically be linked to view them. If the forms viewer is missing then you will not be able to view the forms. The Beehive Forms Viewer is distributed with the Beehive ftp manager.
Fig A1 - Beehive Forms Viewer
Presetting Viewable Form Size
The forms viewer allows the system administrator to select default form size, i.e. the size at which the form will open. The administrator may drop the html form onto the forms viewer and it will open in read only mode. The administrator may then use the resize tool in the lower right hand corner of the form window to set the size of the displayable form. Finally, by selecting "Save As Template.." from the File menu, he may save the form with these dimensions saved with the form.
Fig A2 - Setting Initial Display Size of Form
A.2 Proper Forms Structure and Unsupported html Tags
In version 3.0 of the Beehive software, Beehive now uses native html forms and NO longer needs the forms converter software for Mac and Windows.
The following shows the proper html structure for Beehive forms headers and footers.
Proper Header
The following tags are not supported in Beehive desktop forms:
Version 2.7 and 3.0 use the new formats for supporting the "autofill" function. Each of the fields: company, name, address, city, state zip, phone, fax, e-mail, and account number may be autofilled from the user information window into the Beehive forms by entering the following text values into the corresponding text fields in the Beehive form.
Appendix B - Preparing Beehive for distribution
Most sites distribute the Beehive client application to their customers one of 2 ways:
Beehive allows you to customize the ftp forms application by creating your own html forms, changing the splash screen logo and adding your own list of ftp sites (secure or visible). Customizing the customer's diskettes will make their installation easier. Beehive ftp forms does not require a complex installer, in fact, to customize the Beehive ftp forms settings for your customers: just make the customizations and then add them to the appropriate directories on the Windows ftp forms client installation disk.
Specific Customizations
You may change the graphic that appears in the welcome window when the Beehive application starts up. Just add a custom file called "splash.bmp" to the installer. Your graphic will be automatically loaded into the Beehive application when it is run. There is also an opportunity to put your own custom form(s) into the installer. Follow the procedures for creating a custom form in the Beehive ftp manager manual and place the finished form files into the "forms templates" directory. All forms files must have the .bft extension for use with a windows client.
You will also want to add your site information to the installer. After you have generated a "secure key" for your site using the Beehive ftp manager, just copy that secure key file into the "keys" directory of the installer. If you have a site license, you may also include a txt file called "serial.txt" (that contains your 10 char serial number) with the installer. If this file is present, the serial number will be loaded automatically.
Internet Distribution
To distribute the client across the Internet, just take the complete contents of the installation disk and compress it into a .zip file. If you want to make it a self extracting archive, then you must additionally run the .zip file through a .exe utility.