Over a million developers have joined DZone.

Exposing Enterprise Services via REST APIs

· Integration Zone

Today’s data climate is fast-paced and it’s not slowing down. Here’s why your current integration solution is not enough. Brought to you in partnership with Liaison Technologies.

Appery.io has always made it quite simple to integrated with backend systems via REST APIs — but what if those systems are behind the firewall and don’t support REST?? Many enterprise apps required access to data that is sitting on a SQL Database or on some business application like SAP or Oracle.

Enter RESTXpress!

With RESTXpress enterprises can easily expose databases and business applications securely via REST. Once exposed as REST services, they can easily be integrated into Appery.io apps.

Deployed behind the firewall, RESTXpress comes in two easy-to-install parts. An administrative console (running in a browser) easily sets up enterprise assets as REST services and a run-time gateway presents the enterprise assets as services to the outside world.

Right now, RESTXpress supports databases as assets to be made into REST services. You can use any SQL database with JDBC drivers. This month, we’ll be rolling out SOAP web services as a new type of enterprise asset that can be easily wrapped into a REST service.

And, RESTXpress is free!

You can watch a demo video, download the installer, or join the discussion community…all from one info page.

Is iPaaS solving the right problems? Not knowing the fundamental difference between iPaaS and iPaaS+ could cost you down the road. Brought to you in partnership with Liaison Technologies.

Topics:

Published at DZone with permission of Max Katz, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}