\nSet Up<\/a>
\nGetting Data<\/a>
\nCRUD Actions<\/a>
\nPromoting<\/a>
\nNotes<\/a><\/p>\n
Introduction<\/h3>\n
A very common feature of modern web applications is an API that can be accessed from outside the framework for use in any architecture. m-Power has implemented such an API using RESTful web services, now available in supported templates. For more regarding REST, please see this link<\/a>.<\/p>\n Applications are set up exactly the same for both web services and standard applications. Apps must be compiled\/recompiled with the precompile option set to include web services. In the screenshot below, this is one of the two options at the bottom of the Application Settings page.<\/p>\n Note:<\/strong> If you choose to include both, your application will run exactly as before as web services are called from a different URL<\/a>.<\/p>\n Web services are only available in supported templates, which include:<\/p>\n Web 2.0 Multiple Record Inquiry<\/a> (Bootstrap: Multiple Row Data List) Once you have selected the desired output, you must then recompile the application. Overwriting is not required to add web services to an existing application.<\/p>\n Note:<\/strong> In order to use web services in a specific data dictionary, a new entry must be made to the web.xml file. m-Power will automatically make this entry, however, the first time a web service is made in a dictionary, you must restart Tomcat in order to use it. This will only need to be done the first time a web service app is created in each data dictionary.<\/p>\n For templates that support data read, use the following URL: \u2026where DD is your data dictionary and IXXXXXs is your app number. Additionally, any parms you would normally pass to the application can also be passed to the webservice like so: Note:<\/strong> For a complete list of parms, please see the supporting documentation for each selected template.<\/p>\n Once the URL call is made, a JSON string object will be returned as the response, similar to the screenshot below:<\/p>\n As can be seen, every field value has both the display value (CNAME) and the original value (CNAME_o). The raw data is the same, however the display value has some work done to it such as trimming leading\/trailing spaces, numbers formatted according to format codes, etc.<\/p>\n Note:<\/strong> The type and rtndata values can be ignored as they are not used in web services.<\/p>\n For templates that support CRUD actions (Create, Read, Update, Delete), use the following URL: \u2026where DD is your data dictionary, MXXXXXs is your app number, and ACTION is the desired action as follows: If there were no errors, you will receive a JSON response similar to the following screenshot:<\/p>\n Otherwise, the resulting error will be displayed:<\/p>\nSet Up<\/h3>\n
![](\"\/legacy\/images\/webservice1.png\")
<\/p>\n
\nWeb 2.0 Single Record Inquiry<\/a> (Bootstrap: Single Row Data List)
\n Display and Maintain Rows<\/a> (Bootstrap: Data List with Web Form)<\/p>\nGetting Data<\/h3>\n
\n\/mrcjava\/rest\/DD\/IXXXXXs\/get<\/p>\n
\n\/mrcjava\/rest\/DD\/IXXXXXs\/get?parm1=val1&parm2=val2<\/p>\n![](\"\/legacy\/images\/webservice2.png\")
<\/p>\nCRUD Actions<\/h3>\n
\n\/mrcjava\/rest\/DD\/MXXXXXs\/ACTION?key=val&parm1=val1&parm2=val2<\/p>\n
\nAdd \u2013 post i.e. \/mrcjava\/rest\/DD\/MXXXXXs\/post?key=val&parm1=val1&parm2=val2
\nUpdate \u2013 put i.e. \/mrcjava\/rest\/DD\/MXXXXXs\/put?key=val&parm1=val1&parm2=val2
\nDelete \u2013 delete i.e. \/mrcjava\/rest\/DD\/MXXXXXs\/delete?key=val<\/p>\n![](\"\/legacy\/images\/webservice3.png\")
<\/p>\n![](\"\/legacy\/images\/webservice4.png\")
<\/p>\nPromoting<\/h3>\n