DataLayer.Web Service

The DataLayer.Web Service element gives developers the ability to retrieve information from a SOAP-style web service and can handle values returned as either an XML dataset object or a string. The Logi Server Engine generates an XML rowset from the returned data and developers can use tokens to retrieve records from each column.

We also offer DataLayer.REST for use with web services that use a RESTful protocol.  


The DataLayer.Web Service element has the following attributes:



Connection ID (Required) The ID of a Connection.Web Service element defined in the _Settings definition. If this value is left blank, the datalayer will use the first connection in the _Settings definition. For clarity, developers are advised to enter an ID here in all cases.
ID An optional unique element ID. Recommended for easier identification when debugging.
XPath Specifies a standard XPath string that will be used to select a set of matching nodes. All of the matching nodes are then used to generate the resulting datalayer. If an XPath is defined, it will be processed before any user defined XSL file. Tokens may be used in this attribute value.

The Connection.Web Service element sets the parameters required to link the application to a web service; user account credentials are specified in its attributes.

 If you're trying to communicate with a web service that requires the TLS 1.1 or 1.2 protocol, you will need to use Logi Info v12.2-SP4 or later (earlier versions only support TLS 1.0). In addition, Info Java applications must use Oracle JDK 1.8 or OpenJDK 8 to make the protocol work.

Back to top


Working with DataLayer.Web Service

A web service can expose one or more of its methods so that they can be called by developers from an application. Web service methods return XML as either a dataset object or serialized string type. In both cases, the XML data may require special formatting for use within Logi reporting products. Logi Studio includes an XslTransform element which can be quite useful for converting XML in a datalayer into a format the Logi engine understands.

The information needed to configure the values of the Logi elements used with a web service can be found in the web service's WSDL document.

The following example illustrates how to use the DataLayer.Web Service element and its child elements:

  1. Add a DataLayer.Web Service element to the definition, as shown above, and configure its attributes per the attribute table in the previous section.
  2. Add a Web Service Method element beneath the datalayer, and give it a unique ID.
  3. Set its Method Name attribute value to the name of the web service method that is to be called.
  1. As shown above, add one or more Method Input Parameter elements beneath the Web Service Method element, based on the number of parameters you must pass to the web service method.

    If you're developing a .NET Logi application, these elements must be in the order that the parameters are expected by the web service.
    If you're developing a Java Logi application, the element ID attribute must be set to the name of the corresponding parameter.
    Consult the WSDL document to confirm correct parameter order and names.
  1. Set each parameter's Data Type attribute value to the correct data type.
  2. Set each parameter's Value attribute to the value (hard-coded or as a token) that you want to pass to the method.

Now when you run your report, the data from the web service should be retrieved into the datalayer.

When working with web services and data tables, you may not be sure what the column names of the returned data will be; this is a perfect time to use the Add data columns wizard found in Studio. Right-click the datalayer element, then select the options shown above in the pop-up menus. The wizard will interrogate the web service and insert the elements needed to display your data table columns.

Working with Complex Data Types

Some web services may require you to send data, such as a user name and password, to them using complex data types. These requirements should be handled by writing a plug-in, as our DataLayer.Web Service element is not capable of creating complex structures for transmission to a web service.

You can see an example of this type of plug-in in action in our Web Service with Complex Header sample plug-in.

Back to top


Using Studio's DataLayer Wizard

Logi Studio includes a wizard that can assist you in configuring DataLayer.Web Service. The wizard assumes that you have already added an appropriate database Connection element in the _Settings definition and configured it.


As shown above, the wizard can be started by selecting and then right-clicking the parent element under which you want to add the datalayer, and using the context menus to select "Add a Web Service DataLayer". The wizard will open; use it as follows:

  1. Select the ID of the Connection element from the drop-down list of available connections. Click Next to continue.

  2. The wizard will query the web service to determine its available web service methods. Select the desired method from the drop-down list. If an error occurs here, then the wizard was not able to connect to the web service and you should examine your Connection element attributes to ensure that they are correct. Click Next to continue.

  3. If the web method service requires parameters, the box shown above will be displayed, with each parameter listed. Enter a literal value or a token, as necessary, for each parameter and click Next.

  4. Click Finish to close the wizard.

  5. The wizard has inserted the datalayer and configured its attributes, as shown above, and has inserted and configured any required Web Service Method and Method Input Parameter elements. You will need to manually provide the input parameter values, either directly or using tokens.

Back to top


Multi-Step Web Service Access

Some web services require multiple interaction steps before they will return a result. For example, you may first need to tell the web service your security credentials, then tell it what data category you need, then tell it what format to put the results in, and then request the actual data. A single DataLayer.Web Service element is not designed for this kind of multi-step "conversation" with a web service. So how can this be accomplished?

One approach is to use multiple DataLayer.Web Service elements, one for each part of the conversation. In your report, just add multiple DataLayer.Web Service elements, one for each part of the conversation, and they will execute one after another.

In the example shown above, multiple DataLayer.Web Service elements are used, with each calling a different web service method, to complete the multi-step conversation required by the web service. The last one sends the query and the data is retrieved and available using standard @Data tokens.

Another approach is to write a plug-in to handle the multi-step conversation. When used withDataLayer.Plugin, the plug-in would issue the sequential web service method calls and place the resulting data into the datalayer for use in the report. DevNet members, after login, can see an example of this type of plug-in in action in our Web Service with Complex Header sample plug-in.

For more information, our Web Service Sample Application demonstrates the use of DataLayer.Web Service.

Back to top

keyword: webservice