Configurator API : SOAP interface

The communication with the touchatag service is via SOAP Web Services (SOAP 1.2 (doc.literal)). The WSDL is available at the following location: http://acs.touchatag.com/soap/configurator-1.0?WSDL

1 - 3. See general description.

4. The external application server sends a getApplicationConfig() message to the touchatag server (using the ID as an argument)

5- 7. See general description.

8. The external application server uses the user input to decide (= external application logic) which actions to bind to the tags, and then sends an updateTransaction(handleRequest) message to the touchatag server. This handleRequest object contains three properties:

• The applicationConfig data: this is data that is not interpreted by the touchatag server. It is only used by the external application server to be able to correctly represent pages when the user is creating an application based on a pre-configured application, or when he/she is editing an existing application. The formatting and content of this applicationConfig data is the responsibility of the external application server. This way, the touchatag server stores the configuration data for all the applications that are using the external system, and the external system doesn't have to worry about that.
• The specification data: this is the data that the touchatag server interprets to decide which application to launch when a given tag is used. It is mandatory for the external application server to send specification data to the touchatag server at this point in the flow. If the touchatag server receives no valid specification data, the wizard will redirect the flow back to Step 2.
• The configurationTransactionId that was appended to your configurator applet (cfr point 3 in the flow).

9. See general description.