The ExpereAPI uses XML-based standards through a common transport protocol. Using these standard tools, an application can access a service based on a WSDL (Web Service Definition Language) file by using Simple Object Access Protocol (SOAP). test
The Expere Integrated Enterprise uses a common namespace for all request and response schemas. The namespace is:
http://schemas.bankerssystems.com/2004/ExpereAPI/ExpereIEServices
The binding for the ExpereAPI service is BasicHttpBinding with the following structure:
http://schemas.bankerssystems.com/2004/ExpereAPI/ExpereIEServices/IExpereAPI/[operationName]
In a NET implementation, the Microsoft .NET Framework provides a collection of tools and functions for consuming and producing WSDL documents. A command-line tool,
wsdl.exe, creates a proxy class from a WSDL that can be used in .NET applications. You can produce a WSDL document by appending ?WSDL to the URL of a .NET Service. The format looks something like:
http://[servername]/[virtual directory]/[service].svc?wsdl
An example endpoint, or default URL, for the
ExpereAPI service might look like:
http://[servername]/Expere/ExpereAPI.svc?wsdl
There are a couple ways to access the files:
- You can access the files through Windows Explorer and open the service file through a Web browser. Using Windows Explorer, navigate to the Expere directory in the Program Files folder (the default path is C:\Program Files\WKFS\Expere\). From there, you can open the ExpereAPI.svc (C:\Program Files\WKFS\Expere\Services\).
- You can access the files through IIS and browse the directory and service files. The default installation establishes a virtual directory in IIS that can be used to access WSDL files. Using IIS, navigate to the Services/Import virtual directory and browse the ExpereAPI.svc file.
Note: In a Java implementation, the services can be accessed through the ExpereIEServices.ear file. In this file, a child file, Endpoint.war, contains an API folder where the WSDL file can be found.
