In order to enable Adapters at all, a Job Server has to be enabled for it. Go to the Data Services Server Manager, choose one Jobserver, edit it and check the box Support adapter, message broker communication. Click Apply and you will have to enter the passwords for all associated repositories, do this and then click ok and Close and Restart to finish the process.
The next step is to add and start an adapter. This is all done via the Data Services Management Console > Administrator.
Expand Adapter Instances and select the Job server you just setup for adapter communication:
Now we have to configure all the parameters required to start such an Adapter, a unique Name, the classpath with all the libraries required by this Adapter etc.
The CLASSPATH is the key in this screen. Each Adapter has a Template including a list of all required libraries. For each library, the LINK_DIR environment variable as added so that all libraries should actually be found.
And the last step is to go back to the "Status" tab, start the adapter, and check if it is running.
With the Adapter running, we can now use it to connect to the different systems by creating a datastore in Data Services Designer, a datastore of type "Adapter" pointing to the Job Server and its "WebService" adapter instance.
All the available properties inside the Advanced box are defined by the Adapter. In our case, the WebService requires access to a wsdl file to query the available objects. As this particular Adapter is used to call out to a remote system, like calling a database stored procedure, it only supports one kind if objects to be imported: "Functions".
And these Functions can be imported as you do in all other datastores, either via "import by name" or "open" to browse the datastore. But again, only if both operations are supported by the Adapter.