Accessing WebServices inside of customization code

Thanks Jose and Mark for you replies. 

 

Mark, we decided to go this way because Vantage needs to communicate with our in-house software.  The problem is that an API was created to facilitate the communication and the API has some limitation.  One of them is that it cannot run on Windows 7.  Another problem is now that we are moving up to Epicor 9, all dlls need to be housed under the client directory.  So this was why we felt that wrapping the API into a Web Service is best.  This would allow us to leave the in-house API in one location and no longer deal with forcing a common folder under the client directory in Epicor.

 

Jose, Sorry that I cannot answer your question regarding the web service’s protocol.  Again we have someone in-house that will create the web service, so is there a specific protocol that Epicor requires?

------------------------------------------------------------------------------------------------------------------------ CONFIDENTIALITY NOTICE: The data attached/enclosed may contain information (including technology and technical data) which is subject to the U.S. International Traffic in Arms Regulations (ITAR) or Export Administration Regulations (EAR). This information may not be exported, released, or disclosed to foreign persons either inside or outside the United States without first obtaining the proper U.S. export license or written authorization. In addition, the information and articles described herein are either patented or proprietary, and the copying or reproduction thereof is prohibited without ADVANCED Motion Controls prior written consent. If you are not the intended recipient (or have received this e-mail in error), please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Thank you for your compliance. X3BTB534