FedEx XML Services Integration
Implementing a system to integrate with the FedEx XML services should be simple. They provide WSDL files for each of their services and any modern SOAP library can process these and generate proxy code. At Edoceo we used the PHP SOAP_Client for this and we've worked on client code in .NET.
Integration Issues
While not technical in nature here are some issues one is likely to face while trying to implement FedEx XML Services.
- Telephone Voice Prompt Failures
- When calling in for support for the Web Integrated Solutions one is instructed by FedEx support to say Web Solutions, Web Services, WIS or the like. None of these prompts work. The fastest way into tech support is to simply hit zero on the phone then as the human (usually answering in less than two minutes) to transfer to WIS.
- Inconsistent Answers
- One may also be frustrated by the amount of inconsistent answers provided by the FedEx team. Do not be discouraged. Simply call back and ask another support team member and repeat as necessary.
- Slow Responses
- When sending email into the FedEx support team one is told a response will be received withing 24 hours. In our experience the responses typically take upto 72 hours.
Code Generation
Generating code for these systems is quite simple. Most SOAP libraries understand WSDL files and are able to generate the necessary proxy. You must download the FedEx WSDL files from their system (which requires a signup) and point the WSDL parser to those files. It looks like this in PHP.
$wsdl = new SOAP_WSDL(FEDEX_WSDL_DIR.'AddressValidationService.wsdl'); $wsdl->trace = true; print $wsdl->generateAllProxies(); exit(0);