Hey Rob – the design or intended scope of the webservice will be good to know once you know more. In cloverleaf CAA/WS – you will get a basic framework for creating a webservice endpoint that will reference a SOAP or REST consumer.
The underlying consumer is where the actual service will live. You will need to decide if you are exposing a consumable WSDL for SOAP in order for clients to build the calls they will be making to your webservice, or examples on how to make REST calls to initiate whatever work the threads will be doing in order to give a payload response back to the client who made the call to your webservice.
You may need to do some heavy TCL and to David’s point, some SQL to get the job done in the engine.
When i expose endpoints to clients, depending on the use case, may use the ‘PATH’ trx ID(ie. the URL). Which allows me to only expose 1 endpoint, but give each client their own URL without creating multiple java/ws server threads.
Example:
https://hospitalorg.webservice.com:5000/getResults – is the main service, but i supply the orgs querying or posting to the webservice this:
https://hospitalorg.webservice.com:5000/getResults/OrthoSurgCenter/
https://hospitalorg.webservice.com:5000/getResults/PrimaryCareCenter/
Then you can use the TRXID to have some business logic to route or call different data lakes(most likely short – long term storage of results in a sql table). From there you can take the meta data stored in results to qualify the result against your criteria and post the full response back to the client with the result(s)
These design items will be the key to the build.
.
