S1. Service Invocation Syntax

Service Methods are invoked by XDOC using Simple HTTP URL endpoints as described below.

Method Invocation Each Service Method can have its own HTTP endpoint. Typically, most Services use a base URL endpoint for all Method invocations, with the name of the Method appended as either a query string parameter, or extra query information to the base URL. Configuration of the URL endpoints is done in the axSystemConfig.xml file, which is located at the root of the XDOC software installation.

For flexibility in supporting different URL syntaxes, XDOC allows each URL to contain substitution tokens representing the name of the Method that is being invoked, and the unique identifier of the object (Container) in the Integrated Application being queried.

URL Token Description
$$method$$ The name of the Container Provider Interface method being invoked.
$$container$$ Unique identifier of the object in the Integrated Application.

XDOC parses each Method URL as follows.

For example, if using a single URL endpoint for all methods, you would construct your base URL to include a customer specific account code, which could then look as follows:

If you were using a RESTful style URL syntax, your GetContainer Method URL may look like:

Method Request Parameter Passing XDOC can be configured to pass Parameters to each Method using the following:

Method Response Data All Service Methods must return XML wrapped results. The XML is always wrapped in a common node as outlined in Section 2. Inside the ServiceReponse envelope is a ResponseData node that will vary based on the Method being invoked, and the corresponding XML Schema (XSD) for that return data.

XDOC always determines Success or Failure of the Method invocation by the following logic: