Page History

When you want to build a simple Blueriq model for your first call to a SOAP web service (i.e. be the service requestor) , you can use the example project you can use the example project WebCalculator (that comes with a standard Blueriq installation) to act as the service the service provider: create a new project based on this example project WebCalculator, save it and go to your runtime dashboard to expose it to expose it (if you don’t see the widget, press the button Widgets and check ‘Expose as a webservice’ and save it). When you do that, a button ‘View WSDL’ appears, that enables you to see and save the WSDL. This WSDL contains the communication contains the communication contract between the service requestor and the service provider.

Now when you create a new project to model the service requestor, you can have a quick start by using the WSDL import wizard. That can generate for you the Service model, the Schema set and the service model (i.e. the domain model from the service provider), the Schema set and SOAP service. Now all that is left for you to do, is to make an exposed flow an exposed Flow that contains a page for the user input and the result, and a service a Service call of type: AQ_WebServiceClient.

If you want, have a look at the other visual about modeling a service call from a (more realistic) project with separate implementation modules for the business model and the web service model and a data mapping.

When you want to see a basic example of Blueriq as a Service (BaaS), the quickest way is to create a new project, based on the example project WebCalculator (that comes with a standard Blueriq installation). You will see that this project has a Configuration module in which the Web service and its operations are defined. This is what you expose to the outside world in your runtime dashboard. The project also has an Configuration module in which the Web service and its operations are defined. This is what you expose to the outside world in your runtime dashboard. The project also has an Interaction module, that contains a service model (i.e. a domain model specifically for delivering the service), a Schema set and SOAP service as defined in the WSDL and XSD. When you expose the web service in your runtime dashboard, you can also view this WSDL. In the same Implementation module, some static instances are made for the response. For each operation this web service offers (add, subtract, multiply and divide), the actual calculation is simply done in the default expression of the appropriate attribute. You can check the other BAAS visuals for a more elaborate picture of what a BaaS can contain.

SoapServiceClient.

You can also check the visual SOAP call with data mapping for a more elaborate model.

Image AddedImage Removed