Ruben de Laat edited this page Jul 10, 2013 · 3 revisions
Clone this wiki locally

SOAP is one of the three available channels to access the methods of the Service Interfaces.

This document describes how to use the SOAP interface of BIMserver 1.2

External applications can interact with the BIMserver via SOAP (and [Interfaces other protocols]). For SOAP you'll need a WSDL file which describes all the methods/objects that are available. The BIMserver provides several interfaces and two versions of SOAP (1.1 and 1.2).

soapversion can be either "soap11" or "soap12".
protocol can be either "http" or "https".
address can be an IP address or (sub)domain name.
port can be omitted (80) or an integer.

| URL | | protocol://address:port/soapversion/AdminInterface | | protocol://address:port/soapversion/AuthInterface | | protocol://address:port/soapversion/MetaInterface | | protocol://address:port/soapversion/PluginInterface | | protocol://address:port/soapversion/ServiceInterface | | protocol://address:port/soapversion/SettingsInterface | | protocol://address:port/soapversion/Bimsie1AuthInterface | | protocol://address:port/soapversion/Bimsie1LowLevelInterface | | protocol://address:port/soapversion/Bimsie1NotificationInterface | | protocol://address:port/soapversion/Bimsie1NotificationRegistryInterface | | protocol://address:port/soapversion/Bimsie1RemoteServiceInterface | | protocol://address:port/soapversion/Bimsie1ServiceInterface |

Example WSDL URL: http://localhost:8080/soap12/ServiceInterface?wsdl

SOAP Stack

To use SOAP you will need to have a "SOAP Stack" for your programming language. A SOAP Stack is just a library containing all the logic for the SOAP protocol. For most programming languages there are multiple, so it's up to you to choose one.

Your SOAP Stack is probably able to generate a bunch of code for your programming language based on a WSDL file/url, this is not required but makes your life a lot easier.


The newest version of the BIMserver SOAP interface can handle two kinds of token passing.

HTTP Session Based

Make sure to enable session management in your client, otherwise the server won't be able to remember who you are and you will get this message: {{{ "Authentication required for this call" }}}

For Apache CXF, you can enable sessions this way: {{{ ((, true); }}}

For .Net based clients, this can be done this way: {{{ client = new BiMserver.ServiceInterfaceService(); client.CookieContainer = new System.Net.CookieContainer(); }}}

SOAP Header Based

Some clients won't be able to alter the HTTP Headers, so an alternative is to use the SOAP Header. The BIMserver supports both ways without any server side configuration.

After you call login/autlogin, you will receive a token, this token must be included in all subsequent calls in the header. The SOAP message will have to look like this:

<soap:Envelope xmlns:soap="">
        <ns2:token xmlns:ns2="uri:org.bimserver.shared">
        <ns2:getAllUsers xmlns:ns2=""
            xmlns:ns3="uri:org.bimserver" />

To enable this kind of functionality in Apache CXF (Java)

    Token token = serviceInterface.getCurrentToken();
    List<Header> headers = new ArrayList<Header>();
    Header sessionHeader = new Header(new QName("uri:org.bimserver.shared", "token"), token, new JAXBDataBinding(Token.class));
    ((BindingProvider) serviceInterface).getRequestContext().put(Header.HEADER_LIST, headers);

The [BimServerClientLib BimServerClientLib] has an option to switch between both ways. When connection with the method connectSoap, the second argument indicates weather to use the first (false) or second (true) method.


From version 1.1, there is a "GeneratedSoapClient" project in SVN. This project contains generated source code based on Apache CXF and the latest BIMserver "ServiceInterface". It's just a convenience project.