Cool Solutions

Unleash the power of Filr by automating & integrating using REST APIs!

kdevadas

By:

July 21, 2016 10:17 am

Reads:2,384

Comments:0

Score:Unrated

Print/PDF

Why APIs?

Ability to integrate, automate & customize are becoming must haves for software of current times.

Automation & integration helps save a lot of time & money and potentially cuts down the risk of manual mistakes.

Customization helps make the IT administrator & end user’s life a lot simpler.

APIs are the programming interfaces which helps connect software system with other systems and thus helps integrate, automate & customize.

Why REST?

REST scales very well since the client and server are very loosely coupled. REST also provides server the flexibility to change the resources it has exposed without needing the Client to be rewritten. The API set can be defined by Filr, there isn’t anything that the client needs to know/use other that what Filr server defines. Also the client needs only know the initial URI, and can subsequently choose from Filr server supplied options to navigate or perform actions.

Where to start?

Go to Filr documentation site and start with ‘Getting Started & Tutorial”.

 REST API screenshot

You will get an overview there and then get details info on the APIs in Administration REST API Reference & Client REST API Reference.

Can I see it in action?

Yes: register for the live webinar scheduled for July 27th 2016 to hear from a Filr customer “Witteveen+Bos” on how they deploy Filr & use Filr REST APIs.

So, go on and unleash the hidden powers of Filr using REST APIs!!!

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading...

Tags: , , , , , ,
Categories: File Services and Management, Filr, Technical

0

Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS