Book a demo
Developer portal TWIST

TWIST

The DALIM ES WEBLINK HTTP front-end is a graphical way to monitor and manage TWIST processes on a DALIM TWIST cluster. WEBLINK uses the TWIST API to communicate and interact with one or more DALIM TWiST servers. The requests are sent using the HTTP protocol, and the answers are formatted in XML.


Here, you will find information that will help get you started and understand how you can use the TWIST API to do more complex calls.

Twist

Requirements

You are a customer of DALIM SOFTWARE and own a DALIM TWIST license, including the WEBLINK license option.
Contact your favourite Business Developpement Manager if you would like to have a more basic license such as a TWIST Express or a limited offer.

API Users

The TWIST API is not protected and can be used without any access protection. If you have access to the Tomcat twist context of your server over the port 8080 (http://<serverNAME>:8080/twist), you will be able to use all API functions.


If you want to protect the API page, you will need to place an Apache Webserver in the front, set up an HTTP Proxy Pass and forbid direct access to the http://<serverNAME>:8080/twist page.

Getting Started

Requirements

You just need any Web browser capable of showing the XML replies of the TWIST API and able to access this page:

http://<serverNAME>:8080/twist

We recommend to using Mozilla Firefox or Google Chrome.

Make your first call

Make a call to get the list of DALIM TWIST Processes:


http://192.168.5.221:8080/twist/twistProcesses

This will return such an XML:


This XML file does not appear to have any style information associated with it. The document tree is shown below.
<TwistCluster>
<TwistServer logicalname="es55service" name="es55service:6029" processcount="0" version="5">
<WFL-ProcessList/>
</TwistServer>
</TwistCluster>

TIP: For your first call, you can use a REST client tool (for example, Postman or Paw) with an OAuth 1.0 implementation.

  1. Set the authorization to OAuth version 1.0
  2. Populate the consumer and token key/secret pairs
  3. Update the authorization header
  4. Send the request