Presentation is loading. Please wait.

Presentation is loading. Please wait.

FDOT Implementation of Bid Express Leila T. Griffin October 14, 2004.

Similar presentations


Presentation on theme: "FDOT Implementation of Bid Express Leila T. Griffin October 14, 2004."— Presentation transcript:

1 FDOT Implementation of Bid Express Leila T. Griffin October 14, 2004

2 Topics FDOT Structure Citrix “Metaframe Presentation Server” Expedite 5.3a Installation BERC Installation Citrix Application Console Customizations – Bid Express – Surety2000

3 FDOT Structure Florida Department of Transportation (FDOT) has 9 Contract Administration Offices; Central Office, 7 District Offices and one Turnpike Enterprise. Each district has a domain and maintains their own policies, proxy servers, and internet access monitoring. Each district has access to the trnsport modules through the Citrix “Metaframe Presentation Server”.

4 Citrix “Metaframe Presentation Server” Citrix Product Applications are centrally consolidated and accessible via the Citrix Application Console. Simplifies deployment, management, monitoring and measurement. Citrix is secure, provides easy and instant access to trnsport applications from anywhere, at anytime, and over any connection. Ensures that the users have access to the right resources to protect the security of enterprise information assets.

5 File Server Cluste Citrix “Metaframe” Farm Ten additional servers

6 Citrix Farm Servers The servers are in a resource domain accessible to all domains in our organization through trusts. Each domain maintains their own policies, proxy servers, and internet access monitoring. Expedite programs and BERC are installed from the Citrix farm servers to a sharepoint on the file server. A non-authentication proxy server is used in the BERC.INI file. This address is not made public, and is not accessible to the users through standard browser controls, or the BERC management pages.

7 Expedite 5.3a Installation Installed on each Citrix farm server. Utilizes common file server (cluster) for: – Program exe and cfg files – Program input/output files Multiple gen.cfg files Each district has its own digital id public/private key pair User access is based on district domain groups that are recognized by the Citrix farm servers.

8 Expedite 5.3a Installation (Cont’d).BAT files created for each Expedite program – Allows to start programs from a CITRIX desktop icon – Allows for appropriate district file directory mapping based on Expedite district domain groups Each district has a separate Expedite/CITRIX domain group on LAN for user access File directory “permissions” managed thru cluster management utility, permissions grated to Expedite district file directories based on the district domain group.

9 Expedite 5.3a File Server Components Expedite input/output directories \\server_name\CO_EXPEDITE \\server_name\D1_EXPEDITE \\server_name\D2_EXPEDITE \\server_name\D3_EXPEDITE \\server_name\D4_EXPEDITE \\server_name\D5_EXPEDITE \\server_name\D6_EXPEDITE \\server_name\D7_EXPEDITE \\server_name\D8_EXPEDITE

10 Expedite 5.3a exe and cfg files BID, GEN and LOAD folders (\\server_name\APPS\expedite) The GEN folder contains multiple gen.cfg files – Gen_CO.cfg – Gen_D1.cfg – Gen_D2.cfg – Gen_D3.cfg – Gen_D4.cfg – Gen_D5.cfg – Gen_D6.cfg – Gen_D7.cfg – Gen_D8.cfg

11 Expedite 5.3a (Citrix Server Components) Registry entry and.BAT files associated with CITRIX desktop application icons \\server_name\AppSupport\Expedite\Batch – bondcheck.bat – eblib.bat – entry.bat – gen.bat – load.bat – patch.bat – others….

12 BERC Installation BERC was installed as a service and service executable was installed to a sharepoint on the file server cluster. The executable is accessible to each server in the Citrix farm. A domain account was created to launch the service. Rights were granted to the sharepoint where the executable was installed. Users were granted access to the sharepoint for the BERC data and configuration files. Share permissions were established.

13 BERC Installation (cont’d) Production URL: – \\dotvcofp001\apps\berc_prod\BERC\bin\BERCsv c.exe The application points to the Internet Explorer browser executable, which is then followed by the localhost IP address and the BERC service port number. – "C:\Program Files\Internet Explorer\IEXPLORE.EXE"

14 BERC Installation (cont’d) Keys are imported into the application configuration, by executing the import commands from any server in the Citrix farm. Once the import is performed from one server, the keys are then accessible to all servers pointing to that installation location, further leveraging the single point of installation.

15 BERC Installation (cont’d) Load output directories mapped to the Expedite district input/output directories instead of the default BERC output directories File permissions are granted to the common domain user account BERC login page allows user to choose appropriate district BERC load.cfg file are kept in sync with Expedite load.cfg file The FDOT public key for each district was created using the Expedite Bid program and imported into BERC.

16 BERC File Server Components BERC output directories mapped to Expedite directories – \\server_name\CO_EXPEDITE – \\server_name\D1_EXPEDITE – \\server_name\D2_EXPEDITE – \\server_name\D3_EXPEDITE – \\server_name\D4_EXPEDITE – \\server_name\D5_EXPEDITE – \\server_name\D6_EXPEDITE – \\server_name\D7_EXPEDITE – \\server_name\D8_EXPEDITE

17 BERC ini File Contain settings for each district – UserID= – Name= – Description= – PrintOnDownLoad= – PrinterName= – UpLoadApparentBids= – LoadOutputDir= – Home=

18 BERC Application Directory Files BIN ETC VAR WWW

19 Citrix Application Console User Login to Citrix applications

20 Citrix Application Console (cont’d) Desktop application icons are displayed when the user logs on to Citrix.

21 Citrix Application Console (cont’d) Expedite and BERC applications. The icons lunch the Expedite.BAT files

22 Citrix Application Console (cont’d) Citrix farm server connection widow displays the server the user is connect to and the applications that are being used by the user.

23 Bid Express Customizations Installed as a windows service The database was customized to work with a multi district environment Customizations to BIDX.COM web pages for FDOT multi-district lettings Enable digital id authentication for each district digital id Multiple admin accounts for each of the districts that only allow update to appropriate district information

24 Bid Express Customizations (cont’d) Enable digital id authentication for each district digital id Multiple admin accounts for each of the districts that only allow update to appropriate district information

25 Surety 2000 Changes were made to the Expedite BONDCHECK digital id authentication to handle each district digital id. BONDCHECK required digital ids to be created by Expedite BID, not BERC.

26 Contact Information Leila T. Griffin Systems Analyst Contracts Administration Office (850)


Download ppt "FDOT Implementation of Bid Express Leila T. Griffin October 14, 2004."

Similar presentations


Ads by Google