iiX Online Support - ExpressNet

Support Home • ExpressNet • Express for Browsers • Express for Windows • MVR Information • A-Plus™, Credit, UDI/UDV • Criminal History

Search

Server-Dial Interface with Express for Windows

Server-Dial Interface with Express for Windows

Overview:

Effective with Express version 2.13 for Windows and later, the Server-Dial operation mode permits a customer to use the communications component of Express in conjunction with the customer's custom application. When Express is executed with the /SVRDIAL command line parameter, the communications component is automatically invoked, dials iiX, and transfers data to and from iiX without operator intervention. Files being sent to iiX in this manner must conform to the iiX specifications for a request; likewise, files received from iiX will conform to the specifications for report data as received and processed by Express.

Assumptions:

Dedicated communication workstation running MS Windows
Customer to write interface programs to get data from and put data into the customer's database/system

Procedure:

Step 1:
Customer installs Express for Windows on the workstation to be used for the communications. Installation process includes updating the software with the customer's account number and password, configuring the modem, and verifying the telephone number to be called. Express installs into a directory structure as follows (a typical installation is used for this example):

	\EXPRESSW
	\DATA
	\INBOUND
	\INBOUND\TMP
	\OUTBOUND
	\TEMP
	\USER

Also, as part of the installation, the file AMSEXPW.INI is added to the \WINDOWS directory on the workstation.

Step 2:
Customer interface-GET program extracts request data from the customer's database/system and writes Express-structured file in the Express \OUTBOUND directory.

The filename is MVRZRQQT.TXT for quicktime MVR requests and/or the filename is MVRZRQST.TXT for standard batch processing. Note: QuickTime MVR processing is limited to only a few states; if a quicktime request is made for a state where that service is not available, the request is rejected.

Step 3:
Customer interface-GET program launches AMSEXPW with new command line parameter /SVRDIAL. This will automatically dial, transmit & receive data files. NOTE: If any files are present in the INBOUND directory, the program will not run and communication will not occur; it is assumed that a previous run has not been fully processed.

Step 4:
Express will move received files to a designated directory; the designation will be via an entry in AMSEXPW.INI: The line in AMSEXPW.INI reads SVRDEST=. The default for this option will be the \USER subdirectory in the Express directory tree. The last file to appear in the SVRDEST directory will be a file, COMMSTAT.TXT, which will be an indicator of that the communication session has completed and will contain the status of that session. The presence of the status file will be the event to invoke the Customer interface-PUT program. This PUT program will then process the files received and assimilate the data into the customer's database/system system. Based on the information returned in the status file, the interface program will initiate an appropriate next action. The interface program will also remove all files from the SVRDEST area.

MVRZRPTS.TXT and MVRZRPQT.TXT are both MVR report files and should be handled in the same way.

Values found in COMMSTAT.TXT:

001 = Call Successful
002 = Call failed - no answer
003 = Call failed - lost connection

004 = Call failed - fatal error
005 = Call failed - user terminated
007 = Call cannot be attempted; need to clean up from previous session
008 = Call successful, but time-out occurred filling QuickTime requests; call back in 5 minutes

Limitations:	Request data and report data do not get loaded into the Express file system. This removes the need for frequent database file maintenance.
Feature:	If file exists in SVRDEST area, then Express will not call. The Express for Windows banner screen will be displayed, but no call is made. If a file is still resident in the SVRDEST area, then it is assumed a processing error with the PUT has occurred.

This page has been viewed 13233 times | Document Rating is -- / 5.00 | Last Updated on 4/28/2004 7:08:48 AM