We just try a ‘GET’ and give the entityId as input to see a result like this (as expected): You get an overview of entities, and the operations that are available for try-out. Note: This API is available since version 20.4! We already did a post on this ReST API layer. Once ready we dive into the /app/admin part of our platform to gain access to our ReST API part on that same entity! With the availability of our SOAP end-point it’s time to publish our entity to runtime. You can also access the service via the service layer of the platform Once we have it up and running we should be able to test our just exposed SOAP service with the ‘Service Test Tool’ artifact: Make sure to ‘Assign’ it to the OS process (as our application server TomEE is pretty good at handling SOAP calls).Interfaces: Just select the method set of our ‘case’ entity (or select any other interfaces if you created something fancier!?).Name: AppServer (or any other fancy name you like).Create a new service group (top left button).Open ‘System Resource Manager’ from your own organization (you need to have the ‘Administration’ role).In short steps as we already did a post on creating an ‘AppService’ service container: It looks really simple like this where we also exposed the ‘Read’ operation of the ‘Webservice’ BB:Īs we all know by now we also need to create an ‘AppServer’ service container in the ‘System Resource Manager’ artifact so, the platform ‘knows’ how to handle the requests that are send to this end-point. Watch and learn… Entity creation and webservice exposureįirst we dive into the entity (named ‘case’) creation on a new brand-new project in our organization and workspace. You will see the ReST service layer is already there for you to consume, the SOAP service layer must be extended with our own entity webservice BB. The end result will be a small set of requests that help you start calling any other SOAP / ReST end-point of the platform from the ‘Postman’ tool. ![]() This post will be divided is several sections as we need to craft things in AppWorks as well as understanding what is exposed at service level. Also, when you would like to build some fancy UI with any latest and greatest JavaScript framework, this post will give you a head start… This tool is your main entrance for calling authenticated SOAP/ReST services and when you understand the principles it’s not hard to understand the rest. This post will give you the first steps to call end-points of the platform with a tool called ‘Postman’. Most important here is off-course the authentication and this post will walk you through it. These services can be called from an external sources and for us it’s highly important to understand how this works so we can instruct other people how they need to communicate to our platform. In this installment we dive into the SOAP and ReST requests that make a call to the exposed services from our beloved AppWorks platform. Welcome to a new installment of AppWorks tips.
0 Comments
Leave a Reply. |