Att 10_GEX Customer Application-Mar09.doc

139 KB Posted

Attached to
LED Taxiway Lighting Fixtures
Solicitation number
FA8056-11-R-0001
Issued by

About this file

From the source

Att 10_GEX Customer Application-Mar09

View the file

Other files

File Type Posted
RFP_FA8056_11_R_0001_Question_and_Answers 1_FBO - 6-23.pdf PDF
FA8056-11-R-0001 - Amendment 1.pdf PDF
Att 5_sample_options_file_xml.txt TXT text file
Att 3_CatalogData.dtd DTD file
Ex A_CDRL - Taxiway.pdf PDF
Att 9_Vendor GEX Interface Control Agr.doc DOC document
Att 1_CLINS for Initial Order.pdf PDF
Att 7_sample_thumbnail.gif GIF image
Att 6_sample_picture.jpg JPG image
Att 8_GEX Brochures 12-01-2008.doc DOC document
LED Taxiway RFP.pdf PDF
Att 4_Catalog_Sample_xml_file.txt TXT text file
Att 2_Sample CONUS Bases - 5-26.pdf PDF
Show all 13

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file
Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

March 2009 GEX Customer Application The information gathered in this questionnaire is required to determine and establish the correct connections on the Global EXchange (GEX) for electronic transactional submissions. All connectivity to GEX is required to use secure certificate or key-based authentication. Please use the worksheet to identify your preferred connectivity path (SFTP, HTTPS, or MQ over SSL) and submit the completed questionnaire via email to GEX@BTA.MIL General Information

Company/Organization/Agency Name:
DODAAC:

Street Address:

Street Address:

City:
State:
Zip Code:

Primary POCs

System Administrator Name:

Telephone:
Ext:
DSN:
email:

Technical POC Name:

Telephone:
Ext:
DSN:
email:

Functional POC Name:

Telephone:
Ext:
DSN:
email:

Identify POC(s) to receive notifications of data alerts, translation failures, transaction reports.

POC:
POC:

Briefly describe the Purpose for this Connection request (i.e. Interface to IUID Registry, WAWF, SPS)

Drop catalogs for AFWay II

Is your system hosted in a Defense Enterprise Computing Center (DECC) environment?

If Yes, Location of the DECC:

Required Secure GEX Connection

SFTP (FTP over SSH):
MQ over SSL:
HTTPS:

If you require a secure connectivity option other than SFTP, HTTPS, MQ/SSL, or a VPN-based solution, please provide details in the following section.

OTHER Required Secure GEX Connection

Protocol:
Security Used:

Connection Details:

If you are requesting GEX to Pull data from your system, is a DD Form 2875 (System Authorization Access Request) required?

If Yes, Authorizing Security Administrator Name:

Telephone:
Ext:
DSN:
Fax:

Is your site requesting to Initiate the Connection and Push data to the GEX?

If Yes, Please complete a DD Form 2875 and fax to the Production, COOP and Test sites will need you to fill out. Please fax the form to our Production GEX Site (Ogden): Byron Droge FAX 801-605-7453 , Production GEX Site (Columbus) : Lisa Hill, FAX 614-692-1109 and Test GEX Site (JITC) : Christie Warner, FAX 520-538-2214.

If request is granted, the GEX IP/Hostname, Account Login, and Password will be provided during setup.

Use the detailed connectivity options below to determine which secure connection method is best for your system. Additional details can be provided if there are questions on specific options for each of the protocols listed below.

SFTP Connectivity Options Using SFTP, both client and server connectivity options are supported with pushing and pulling of files available. Please fill in the appropriate information based on the requirements for your system. GEX initiated connections are the preferred method.

GEX SFTP Connection (GEX initiates the connection)

FIPS 140-2 compliant Tectia 5.2 SFTP Client will be used at GEX.

External Test/Production IP address of your system: (Test): /(Prod):
Test/Production Hostname:

(Test): /(Prod):

Hardware and OS :

Firewall at your site, Y/N:
Type:

Established login account for the GEX (Maxlength for login = 31)

Login: Key exchange during setup. (Public key auth required. Password auth will be phased out.)

Full Pathname for data pickup by GEX:

Filename conventions used:
Multiple or Batched:

GEX typically PULLS all files in Path and DELETES after Pull unless otherwise specified:

Estimated number of transactions per day from your site:

Full Pathname for data drop-off by GEX if necessary:

Filename conventions requested:
Multiple or Batched:

Customer SFTP Connection (Remote system initiates the connection to GEX)

FIPS 140-2 compliant Tectia 5.2 SSH Server will be used at GEX.

IP address of your system:
Hostname:
IP Address (NAT'ed) of your firewall:
Hardware and OS :
Firewall at your site, Y/N:
Type:

Established login account at the GEX (Maxlength for login = 31)

Login: Key exchange during setup. (Public key auth required. Password auth will be phased out.)

Filename conventions used:
Multiple or Batched:

Estimated number of transactions per day from your site:

Full Pathname for data drop-off by your system if necessary:

Filename conventions requested:
Multiple or Batched:

HTTPS Connectivity Options Using HTTPS, both client and server connectivity options are supported. The sending system will initiate the connection making two-way data transfers a PUSH/PUSH interface. GEX HTTPS, Pulling of data could also be an option if your system provides that capability. Please fill in the appropriate information based on the required for your system.

GEX HTTPS Connection (Section applies to both Client and Server connections)

TLS v1 Required

Cipher Types Accepted for FIPS Compliance (DHE-RSA-AES256-SHA : DHE-DSS-AES256-SHA : AES256-SHA:EDH-RSA-DES-C : BC3-SHA:EDH-DSS-DES-CBC3-SHA : DES-CBC3-SHA : DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA : AES128-SHAEXP1024-DHE-DSS-DES-CBC-SHA : EXP1024-DES-CBC-SHA:EDH-RSA-DES-CBC-SHA : EDH-DSS-DES-CBC-SHA : DES-CBC-SHA : EXP-EDH-RSA-DES-CBC-SHA:EXP-EDH-DSS-DES-CBC-SHA : EXP-DES-CBC-SHA)

Data Transfers Required (Receiving Data, Sending Data, or both) :

IP address/Hostname of your Test/Production system: (Test): / (Prod): /
Test/Production URL for GEX Pushing Data:

(Test): (Prod):

Hardware and OS :
Multiple or Batched:
Firewall at your site, Y/N:
Type:
Certificate Authority Used:
SOAP Wrapper Required (if any):
HTTP Method (POST, PUT, GET):
HTTP Variables (Content, Filename, etc):

Body MIME Type/Subtype (URL Encoded, text/xml, octet stream, etc) :

Estimated number of transactions per day from your site:

MQ/SSL Connectivity Options Using MQ/SSL, both MQ client and server connections are supported. Queue Managers and queues can reside on either GEX or remote systems. GEX can use MQ client connectivity to retrieve data from remote systems or provide queues on GEX to facilitate data exchanges. GEX requires that FIPS-compliant SSL queue managers be used for data transfers. (Note: GEX uses the term “circuit” when referring to MQ channels to eliminate confusion with GEX channels) GEX MQ Connection (GEX initiates the connection)

External Test/Production IP address of your system: (Test): / (Prod):
Test/Production Hostname:

(Test): / (Prod):

Hardware and OS :

Firewall at your site, Y/N:
Type:

Transfer Type

No Segmentation:
Segmentation by GEX:
Segmentation by MQ:

SSL Cipher Type:

Incoming Queue Manager Location

Local:
Remote:
Hostname:
Queue Manager:
Server Connection Circuit:
Remote Sending Circuit:
Remote Queue to Pull From:
Use Default Pull Queue Name
Yes:
No:

Local Receiver Queue:

GEX typically PULLS all files in Path and DELETES after Pull unless otherwise specified:

Estimated number of transactions per day from your site:

Multiple or Batched:

GEX MQ Connection (Remote system initiates the connection to GEX)

External Test/Production IP address of your system: (Test): / (Prod):
Test/Production Hostname:

(Test): / (Prod):

Hardware and OS :

Firewall at your site, Y/N:
Type:

Transfer Type

No Segmentation:
Segmentation by GEX:
Segmentation by MQ:

SSL Cipher Type:

Transfer Mode
Batch:
Multiple:

Outgoing Queue Manager Location

Local:
Remote:

Test/Production Hostname/IP Address:

(Test): /(Prod):

(Test): /(Prod):

Remote Queue Manager:

Local Outgoing Queue Manager:

Use Default Circuit Name
Yes:
No:
Local Send Circuit:
Remote Receiver Queue:
Remote ‘Push To’ File Pattern:
Outgoing Data Format
Binary:
ASCII:

Estimated number of transactions per day from your site:

PAGE

File details come from the government source that posted it. Updated .