EDI Learning and Development (I)

Recently, I have a requirement to record the results of EDI development.

Configuration File: 01. EDI. Export. config (in the systemconfig directory of the EDI server)

02. EDI. typeconfig (used in three places: client systemconfig, appserver/systemconfig, EDI Service/systemconfig)

03. Check file: iftmbf. validator. XML (three places: client systemconfig/EDI, server/systemconfig/EDI, EDI Service/systemconfig/EDI)

(Change the value of name attribute in mapping to the new EDI name)

04. iftmbf. XSLT (during mapping, the corresponding node matches the XML file and converts the packet to the corresponding TXT format .)

Client configuration: three centers:

01. System Tools:-> basic data-> Status type-> order list-> shipping documents (hbl interface-> Add (corresponding to EDI. type. config)

Status definition-> delegate list

02. Basic data: Switch configuration-> switch control length (set this value only) is 6

03. EDI center: EDI type-> order list-> Add-> (the description is the downlink menu displayed on the Interface)

Code Conversion-> Customer Code-> Code Conversion Type-> Code Conversion list

Table in EDI configuration (used for upgrading and capturing scripts ):

Edi_code_convert_config

Sb_status_type

Edi_message_type

Edi_interchange_configuration

Edi_partner_code

Edi_message_reference

Edi_message_reference_detail

Stored Procedure:

Data fetch stored procedure: sp_edi_search_iftmbf

Verification stored procedure: sp_edi_check_xxx

Note: In the check file, search for "true" and run the check if the value is true. If the value is null, the check is not performed.

Mappingfiles-> add and delete fields in the XSLT file.

* ** Each time a new file is overwritten or added, the corresponding EDI service must be restarted ***

Upgrade:

01. Backup files (it's okay to rely on backup to survive ):

APP server systemconfig (EDI. type. config, EDI. Export. config)/EDI (iftmbt. validetor. XML)

APP Server Download/(update. XML, EDI. type. config. Zip, EDI. Export. config. Zip) (it seems that the EDI. Export. config file is only in the EDI server)

EDI server systemconfig (EDI. type. config, EDI. Export. config)/EDI (iftmbt. validetor. XML)

EDI server systemconfig/mappingfiles/iftmbf. XSLT

02. Upgrade file:

You only need to package the systemconfig file (Client: systemconfig/EDI. type. config, EDI. Export. config)

Other files in the corresponding paths of EDI server and app server (refer to backup)

Common Mistakes and solutions:

01. When a field is deleted, no verification prompt is displayed. (the corresponding msg_id is not obtained in EDI. server. As a result, no data is returned when the corresponding stored procedure is executed)

02. test Database message generation OK, but the official database log indicates that the packet generation is OK, but the corresponding packet cannot be found (covering the new EDI. export. the config file does not restart the EDI Service, causing the generated packets to be captured by FTP)

03. the generated message data is missing or the number of statistical packets at the end is incorrect (XSLT is used to debug the generated XML format message element node, and the corresponding node is not found during mapping, no corresponding message is generated. Statistics: There is a select: Count = "/* XXXXX" statistical expression in the XSLT file. In fact, I didn't understand this expression at all .)

TIPS:

Two debugging methods:

01. Capture the log_id of the corresponding order, find the number of messages returned by the corresponding Stored Procedure check and various types;

02. debug XSLT (open with Vs and add and generate messages in XML format) to check whether mapping nodes correspond one by one and whether the generated packets are in the same format and quantity.