We need to expose IMS as RESTful webservice consumer. I had referred a document "Creating a RESTful Web Service for IMS-Transaction" by Ivy Ho, which talks about exposing IMS as RESTful webservice provider. In that document they selected an OUTBOUND adapter option while creating an J2C bean(Page Num 4), which makes the data to be passed from application to adapter. Is it possible if I opted INBOUND adapter which makes the data to be passed in to the application from the adapter, will it help me to expose IMS as RESTful consumer.
If any proven methods are available, to expose our application as RESTful webservice consumer, kindly share the same ?
Is it possible in the SOAP GATEWAY server to handle REST calls of the client application. So my core application can consume the REST response of client application after the data mapping in the SOAP GATEWAY server.
Kindly share your views and thoughts. Thanks in advance.
The recommended route for your IMS application to consume an external REST service would be through the API Requester function for z/OS Connect EE. The following link provides a step by step guide for doing exactly what you want: https://www.ibm.com/support/knowledgecenter/en/SS4SVW_3.0.0/com.ibm.zosconnect.doc/scenarios/ims_apiReq_intro.html
The reason this would be recommended is it funnels all outbound calls through a single gateway which can be monitored, modified, and updated without affecting your applications.
SOAP Gateway will not be able to handle REST calls. I suggest looking into IMS Mobile Feature pack which is a restful endpoint for IMS.
IMS Mobile Feature Pack Description:
This feature provides a RESTful endpoint for mobile services to access back-end IMS resources through IMS Connect. A data transformation module is included that converts request and response messages between JSON and the native representation of the input and output messages. Tooling support for modeling, creating, testing, and managing services is provided through IMS Enterprise Suite Explorer for Development.
reference:
https://developer.ibm.com/wasdev/downloads/#asset/features-com.ibm.ims.imsmobile-1.0
https://developer.ibm.com/wasdev/downloads/#asset/features-com.ibm.ims.imsmobile-2.0
Related
I want to know details of an update from a remote WSUS server through RESTFul or any other Webservice call, Is that possible. I'm aware of Microsoft.UpdateServices.Administration and it's usage.
RESTful web services are not supported by WSUS Administration API.
SOAP has to be used to communicate with the server. There are many open source SOAP client appliations which can be used for this task.
Remember about the authentication mechanism which developing the solution.
I used Python3 requests, ntlm and zeep libraries to achieve this task.
What I'm trying to do is as follows,
Business use-case : A backend service with SOAP binding required to expose as a RESTful service. Consumers require to get the responses from JSON using the same API.
I have gone through below links but didn't find them useful. Configurations are either not given or not working.
http://asanka.abeysinghe.org/2013/05/implementing-api-facade-with-wso2-api.html
WSO2 API Manager convert SOAP to REST
WSO2 API Manager - can it convert REST requests to SOAP requests on the backend?
I know the step what to be done but what I'm wondering is how that should be done in the ESB. Exact configurations.
Backend service with SOAP binding required to expose as a RESTful - WSO2 ESB?
If you need to expose a SOAP Service and REST (POX or JSON), you can do it using ESB. You can create a API in ESB and does the mapping between JSON or POX to SOAP. There are samples available in the ESB documentation. Please check from here. You do not need a API manager, if you just need to expose some REST API. You can do it using ESB as well and you do not need to use API Manager.
What's the appropriate way to extend a Balana-OpenAZ based PEP to send XACML3 decision requests to a remote WSO2 Identity Server PDP?
You want to send XACML decision request from PEP to Identity Server PDP. Still Identity Server only supports SOAP based web service API, Thrift based API and WS-XACML. Therefore i guess, best way to start is using SOAP based web service API. You can find sample java based client from here to write a extension for Balana-OpenAZ PEP.
Say I have a REST API hosted on a webserver:
someone.com/api/
I want to expose this REST API through a proxy service using WSO2 ESB.
esb.com/api/
It should forward whatever is after esb.com/api/. So if I hit:
esb.com/api/param1/param2
It should hit the real service using:
someone.com/api/param1/param2
How do I pass the URI parts to the real webservice from a proxy service?
Don't try to use Proxy services for REST API. Proxy Services are for the Web Services. Use API s avialable in WSO2 ESB which are similar to proxy services and intended for REST API. This Oxygen Tank article and this sample document will be useful for you.
So i have a assignment to write some REST client calls to a REST web service which does not exist.
To work around it i created a mock web service using Jersey. But i am not sure what technology the actual REST service would use.
Please advise on what technology should i use to send down the REST calls to the server.
Also if possible also give me a sample of how to send down a XML GET request to the REST service.
Thanks much for the help.
Please advise on what technology should i use to send down the REST calls to the server.
REST is HTTP. You can use anything that sends HTTP requests:
Jersey Client
Any web browser
cURL
telnet
carrier pigeon
...
Also if possible also give me a sample of how to send down a XML GET request to the REST service.
It's just an HTTP GET request. How it's built/generated/sent depends on what library and programming language you're writing the client in. But the actual request itself would look something like this:
GET /foo/bar/baz HTTP/1.1
Host: www.example.com
Accept: text/xml
As far as I know Both Java and .Net environment has the tools to generate WebServices (SOAP and rest). What's your client development language ?
REST :Representational state transfer in simple terms used to send data between client and server . As
Client use some persistent URL for communication and it is stateless communication .
Java uses Jersey, the reference implementation of JAX-RS, implements support for the annotations defined in JSR 311, making it easy for developers to build RESTful web services by using the Java programming language.
So All u have to use for creating services is just some dependencies , bean configuration and some annotations (To Expose Service ) .
For calling REST Service , u can either call from browser . Browsers like (chrome ,mozilla ) provide some plugins to calling REST service or u can create a client to call REST Service .