Difference between revisions of "GT:Installation"

Latest revision as of 14:14, 21 January 2010

Installation Instructions for the Whistle SCE system.

Installation of a complete Whistle system involves: creating the Whistle data schema within the target database, the setup of database connectivity through ODBC on the application server, installation of the Georgia Softworks telnet server on an application server, setup of users in the windows domain and on the SQL server database, setup of the Whistle application along with its’ configuration, print services for labels and report creation, installation of barcode fonts on the print server, setup of the ADAGE TEE server and configuration of the aysnc barcode transaction, and finally installation of the Whistle Maintenance screens in the Adage environment.

Before you begin, make sure you have the whistle.zip install kit file.

*PLEASE READ ALL INSTRUCTIONS BEFORE YOU BEGIN*

Setup of Database Schema

1. Open up a sql query connection as “sa” to the database you wish to install the whistle database schema in. This should be the same database that Adage is installed in.
2. From the installation kit open the whistle_tables.sql file and run it. This script creates the initial tables, indexes, views, stored procedures, and triggers needed by the Whistle SCE system to store data. This script is run only once for setup of Whistle.
3. Also from the installation kit open and run the whistle_inserts.sql file. This script is configured to setup the metadata for all warehouses defined in Adage. It will need to be edited if additional warehouses are defined in Adage.
4. Open and run the whistle_security.sql file. This file will create the initial security metadata for system operation. This script is configured to setup the metadata for all warehouses defined in Adage. Again it will need to be edited if additional warehouses are defined in Adage. Note this script initially defines a user named “admin” with all rights at the end of the script.

Setup of Database Connectivity

1. Create a system level ODBC DSN connection through the Data Source Management application with a connection to the desired database.
2. From the Control Panel choose the Administrative Tools, then Data Sources (ODBC).
   1. Select the System Level tab then click the ‘add’ button.
   2. Choose SQL server, then click finish.
   3. Choose a name, for example adage_live, and note it for future use.
   4. Input the sql server name, and then choose next.
   5. Choose “With sql server...” authentication. Then fill in a user and password. This user will need ‘read access’ to all Adage/Whistle tables and read/write access to all wm* tables.
   6. Click next, and then mark the “change the default database to” check box. Off the drop down choose the target database, where the whistle schema is installed.
   7. Unmark the “Use Ansi nulls, paddings and warnings.”
   8. Click next, then finish.

Installation of Georgia Softworks Telnet Server

This is a very full-featured piece of software in its own right. The initial step should be to read and understand this products complete manual. It is in the installation kit as uts.doc.

1. From the install kit unzip uts128.zip into a convenient, temporary directory.
2. From new directory Run the setup.exe program. The Welcome screen of the setup program is displayed and you are reminded and urged to exit all windows programs before continuing. You are also reminded that you must have administrative privileges to install this program. Click Continue.
   1. The Installation options screen is displayed. Choose Full Install.
   2. A screen is displayed indicating the directory that the Georgia SoftWorks Telnet Server will be installed. The default is c:\gs_uts\. For ease of maintenance we suggest the default directory be used. Click Continue.
   3. A program group is installed. Run the registration program, fill out the required information and send the resultant text file to caa@coolearth.com for activation. A 30-day grace period before activation is provided.

There are several registry keys that should be changed after installation for best use with wireless RF devices that go into a power-saving mode. Changing these registry settings will keep the system from disconnecting the users’ session when the device (such as a hand-held computer) powers down.

1. From the start menu, choose run, enter regedt32.exe. Set the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GS_Tnet\Parameters\InactivityTimeout to decimal 3600
2. Next set the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GS_Tnet\Parameters\ClntChkTimeout to hexadecimal FFFFFFFF

In general using the automated logon scripting available with the telnet server provides a good deal of convenience and should be used.

1. In the c:\gs_uts directory you will find gs_auto.txt and gs_logon.txt. These are used for auto logons of the gs telnet client and 3rd party (like the ms windows client or Intermec) clients respectively. In each file specify the ip address of the person and the device for connecting the windows logon.
2. There is a c:\gs_uts\scripts directory where the server will check for a sub-directory name the same as the username of the person or device logging on. If created, the server will further look in the c:\gs_uts\scripts\username directory for a c_start.bat file and if present then run it. In this file you can set environmental variables, and execute the whistle sce wms.exe executable. This way the user is seamlessly dropped into the application environment.
3. The installation kit has an example c_start.bat file for your use. The example uses wms -DH for a hand held size screen. Change to wms -DF for fork truck mount computer or a desktop. Other command line parameters of use are -J for database user name -K for database password -U for whistle/adage user name -P for whistle/adage password. If -U and -P are specified then no whistle logon will be presented. Note, there is NO space between the parameter and the value; for example -DH not -D H.

Create Users on Application Server

At a minimum one windows user is required, so that devices and users can be used to authenticate through the telnet server. In practice it is best to have one user per hand-held, fork truck, and desktop user. In this way user sessions can be managed individually. Users may be domain/AD users or just local users on the application server. If TEE is going to be installed on a remote computer then the users should be domain users so they can be granted write privileges to the /einterface/inbound/new directory on the TEE server. Refer to MS documentation on how to create users.

Create Users on Database Server

At a minimum one database user needs to be created that has select access to all tables, and also select, insert, update and delete grants for all wm* tables. The best practice is to create one user account assigned to each device and user. This makes it easier to identify performance issues, contention issues, and to debug any support issue. Refer to MS documentation on how to create users.

Setup of the Whistle SCE Application

1. On the application server create a directory c:\coolearth with sub-directories of users and cache.

Grant read, write and execute to all users that will be connecting through telnet or terminal services to run the application to all three directories.

1. From the installation kit copy all files to the coolearth directory.
2. Execute the wms.exe application. You will see a prompt that asks F/H? Hit S (for setup) and then press ‘enter.’
   1. Hit down once until the db name field is highlighted. Enter the name of the data source you previously setup.
   2. Hit down arrow once more until the db user field is highlighted. Enter the name of a database user you have previously setup. This is the user the system will connect to the database as if the -J command line parameter is not specified.
   3. Hit down again to the db pass field. Enter the password for the database user. This can be overridden with the -K command line parameter.
   4. Hit down arrow again until the db Type field is highlighted use the A and Z keys to scroll up or down to the SQL Server choice.
   5. Press down until the Adage Version is highlighted. Use A and Z to scroll to the correct version.
   6. Scroll down once to “Use Adage Lots” and hit space bar to mark it as ‘active’. This option would only be turned off if you do not perform lot tracking in Adage, but want to track lots in Whistle only.
   7. Scroll down to ATF Path. Enter in the path to the TEE servers \einterface\inbound\new directory. It is better to use a UNC identifier like \\servername\einterface\inbound\new, but a mapped drive is also suitable.

Descriptions of the other settings, see the System Settings page.

Installation of Whistle PrintServer Services

The Whistle PrintServer is a Windows NT/XP/2003 service that dispatches printing requests to the printengine system, which creates labels and reports for the Whistle system.

1. Hit Start, Run, and then ‘enter’ cmd to get a command prompt window. Change directories to the c:\coolearth directory.
   1. From the command line type “instsrv PrintServer c:\coolearth\printserver.exe” (Don't type the quotes, just what is between them).
   2. From the Windows Control Panel, choose Administrative Tools, then Services. Look for the PrintServer service then start it up by pressing the button that looks like a cassette play button at the top of the services window.
2. Add needed label and paper printers to the server. From Windows Start Menu go to Printers/Faxes then add printers. Choose local print then hit next.
   1. Choose Create new port and “Standard TCP/IP port”. Hit next.
   2. At the next prompt enter the printers IP address. Hit next.
   3. At the next prompt choose the driver to use. Consult with the printer manufacture for the correct driver.
   4. Name the printer, no spaces in name.
   5. Repeat as needed to add all printers.

Install TrueType Font

The printing system requires a special font for the printing of barcodes. Copy from the c:\coolearth directory to the c:\windows\fonts directory the 3of9.tff font file. The coping action will automatically install it as a usable font.

Installation of TEE Server

Read and follow the INFOR provided TEE installation instructions. Coolearth recommends that TEE NOT be installed on the same server as the Whistle SCE Application server. This is for performance reasons. The INFOR provided Purchase Order Receipt transaction is not suitable for use, so we provide a replacement. Several components need to be imported into the EIA_COMMON source code environment for this new component to work. In the install kit you will find the Adage 45 EIA Receipt.zip.

1. Unzip this to a convenient directory. Open the CA OpenROAD development environment against your ADAGE source database, and choose the EIA_COMMON image. After this is open import one at a time cewhistlerecdetailo.exp, cewhistlerecdetailslotso.exp, cewhistlereceipto.exe, cewhistlesubloto.exp, ei_inbound_wreceipt_p.exp, eireceipto.exp. After this is done compile a new EIA_COMMON. This will replace the EIA_COMMON image that TEE is currently using.
2. Connect to the Adage / Whistle database with query analyzer or other similar tool and run the insert_meta_data.sql script. This inserts the meta data needed for TEE to use the new transactions and also inserts metadata for the new screens added to Adage for Whistle maintenance.

Installation of Whistle Studio

Whistle Studio is used for maintenance of the Whistle tables. It is a desktop application that runs under Windows XP/2003 or greater and requires the Microsoft .Net Framework 3.5 to be installed. The total size of the installation is around 50 megabytes of disk space. There are two different deployment strategies available – running a Microsoft Installer file (.msi) or using the ClickOnce application deployment technology.

Installation of Whistle Studio Using Microsoft Installer

Inside of Windows, click the WhistleStudioInstaller.msi file provided by Coolearth. This will launch the installer application. You may be asked to enter in the initial database credentials that the application uses to login, in addition to where it should be installed. Any updates to the program can be installed by simply running the new .msi provided, it will upgrade any files necessary and install over the top of the previous version.

Installation of Whistle Studio Using ClickOnce

ClickOnce application deployment requires a web server that can host pages with Frontpage Server Extensions enabled. The application is installed and downloaded from an internally accessed web page. The advantage to this strategy is that when the program is run, it can automatically check with the web server for any updated versions and install them all with the single click of a button. This way there is no need to update all the workstations running Whistle Studio individually.

To install the Whistle Studio for the first time with ClickOnce, navigate to the internal web page and click the ‘Install’ button.