Webservice Invocation

Consider you want to use an external model called ForecastModelPost, which is available in http://<IP Address/hostname of the Web Server>:<servlet port>/<context name>/rest-api/v1/ModelWebService/ForecastModelPost.

To access Application Rules, do as follows:

1. From the Process Modeller window, click the View icon corresponding to the Pipeline for which you want to add an Application Rule. The Process Flow tab is displayed.
2. Select Application Rules icon from the header to display the Application Rules window.
3. Click Add to display the Add Application Rules window.
   You can delete a rule by clicking the Delete button.
4. Select Rest Service from the Application Rule Type drop-down.

   Figure 9-3 Webservice Invocation Rule Details

   
   

   

   
   
5. Enter the details as shown. For more information on configuring a Rest Service, see the Rest Service Application Rule section.
6. In this example, the Data sent to the web service is a combination of both static and dynamic value (~~JSON_DB_DATA~~ is a data field holding a JSON string which is prepared as the previous step in the pipeline.)
7. Click Save. The ModelWebService Application Rule gets created in your logged-in Information Domain.
8. In the Process Flow window, Select the Service Task icon from Activity in the toolbar and drag and drop on the drawing canvas where you want to place it.
9. Double-click the icon on the canvas to display the Activity window.
10. Double-click the Service Task icon.
11. Enter the Activity details such as Activity Name and Activity Description.
12. Click the Check icon. The Implementation window is displayed.
13. Select the information domain where the ModelWebService Application Rule is defined, from the Infodom drop-down list. The list displays all the Infodoms mapped to the applications configured in your OFSAA instance.
14. Click the Participant Details window is displayed with all Application Rules of Execution Rule types available in your Process.
15. Select Model Webservice.
16. Click Accept to save.

    Figure 9-4 Webservice Invocation Activity Details