I'm not familiar with Filenet.
I am using IBM FileNet as document management system. How Can I consume Filenet web services Apis in my AngularJs Application.
Please Help me out, if anyone has tried this.
Thanks
Use the FileNet api to develop a class or web service that returns the records from FileNet and then have the Angular app digest the records returned.
See:
http://www.ibm.com/developerworks/data/library/techarticle/dm-0810carpenter/
and
https://www.ibm.com/support/knowledgecenter/SSNW2F_5.2.1/com.ibm.p8.ce.dev.ce.doc/gs_concepts.htm
In very simple terms, FileNet is a just another content Management system.
It has an API that you use to query the backend(Content Engine) for a
documents that matches your criteria.
Each document you get has content(most of the time, a physical file), and properties (In fileNet terms MetaData).
You will need some technology in the middle to translate the data you aquired to a form that is consumable by Angular (JSON). Something that we can call for the moment a Rest Engine.
This "Engine" should help you expose end points (Simple web addresses http:///Path/To/Data) that is attached to java methods that returns the JSONs you made.
To be able to pull that out successfully, you need to have a good grasp of Angular (Services), and then knowledge of one "Rest Engine" (or something you can use similarly, even a servlet would help you for the moment), and finally a very simple knowledge of FileNet basic operations.
A RESTFUL service tier that leverages FileNet EJB API which are much faster than WS APIs (esp. when in a distributed deployed environment) is to be built for this if you are working in an enterprise-level project.
Related
This could be a silly question but I want to confirm about it. I am a backend Laravel developer and have created my website. Now I want to create mobile mobile apps but have no knowledge of front-end.
Due to lockdown situations I want to use this time to create the backend API for my apps. Now I want to know is it ok or a normal practice to create APIs without knowing anything about front end. (Like is it possible that I just create all the endpoints now that are throwing data in JSON and then the front-end developer will use them to integrate in the front-end? Thanks
P.S: I dont know how the app front-end will look like but I know what data will be needed in each page/view.
I think you can do this easily with graphql.
A Frontend dev and also beginners with Apollo in the frontend can easily introspect and build the stuff.
If you can choose your Frontend stack there is no problem with rest either.
I always do the Frontend first approach.
Mocking the data for graphql types and building the api later seems to me the best workflow ever.
See ya. Much fun with your project
Yes it is possible very possible to do that it would be nice is the API is well documented using postman or swagger for a better experience when frontend engineers want to integrate
Many API's in the world today are never consumed by a browser or app on the frontend, sure it can make life easier knowing why you are building it.
But at the end of the day, a good API is simple and easy to understand. It just allows a developer to fetch data from a system but normally with some idea about each type of request.
For example, if you had an API for a university the endpoints could be as follows:
/pupils => Get/Sets pupil data.
/teachers => Get/Sets teacher data.
/classes => Get/Sets class subjects and references ID's of both Pupils and Teachers.
So if you wanted all the Pupils in a given class you would query the /classes endpoint and then for each Pupil ID you would query the /pupil endpoint.
Sometimes not having a frontend makes the API even more generic because you might think differently when you do not have a frontend.
I have created an Ionic app which uses pouchdb to store items locally and then syncs them with remotely with couchdb
I am looking to create a REST api for this app which uses the items stored in my couchdb from the app. A web app will also show all of the items from the mobile ionic app.
I have experience with Node using Express. Would node/express be the best/easiest thing to use when building the api build? Or is there another much simpler more popular way?
You can use Firebase https://firebase.google.com/, it' a mobile platform that helps you quickly develop high-quality apps
If you're not completely set on using NoSQL on your API, you should really take a look at Django Rest Framework.
If you can map your data to objects, I'm sure you can go from zero knowledge to having an API up in hours. The quickstart tutorial is fully functional and you can set that up in just minutes! Plus, having more frameworks and languages under your belt can only be a good thing.
There's a Node client which you can use in your Expresss server for Couch DB called Nano , just like you would use mongoose for dealing with MongoDB . Since CouchDB already provides the ability to retrieve data using http, so you can even use an http wrapper like request but you can use Nano for a higher level abstraction.
You can then go ahead build an API that simply proxies those requests to your CouchDB instance.
I require some advice in terms of choice of language, I hope that I'm allowed to ask this question here.
To provide some framework information:
As from next week, I'll be following a Java course to get my graduate degree in programming.
For this graduate, they mention that we'll need to develop a webapp in Java.
At the same time, coincidence wants that we are currently developing a webapp that allows users to search popular activities (events) and follow hashtags to render a specific activity feed.
For the front end we currently use some client libraries (Marionette, Backbone, Underscore, Requirejs).
For the server front end (router, rendering server pages), we currently use nodejs.
The question is if it would be a good choice to use Java to build the REST service (to serve both the server and client front ends). The webapp includes a social network, organisers can create their own profile, users can bookmark all sorts of things, ... well, there will be pretty database intensive actions (we'll be using a relatively complex relational model with MySQL).
We might still be using Node to handle push notifications with web sockets but we haven't really discussed this yet.
Since we'll get time at school to work on our project in group, I'd have plenty of time to build the backend REST api with Java which seems like a huge opportunity for me in terms of time. I'm just wondering if there would be any real tradeoffs to do it with Java for this purpose.
Thanks.
I think this would be a huge opportunity to build a REST backend in Java.
Take a look at Spring for a fast and effective way to server HTML
Also you could look at Spring Boot for serving REST APIs. If you follow the tutorials you'll be up an running in minutes.
Good luck
I found a project online (Jboss Teiid) that seems to only have a JDBC/Java API for connecting and managing the tool. I want to build a web-app (preferably in Angular) to manage Teiid, but I'm honestly not sure the best way. Would it be best to create a REST API to interact with Teiid since it only has a Java API? The JDBC driver is good for querying data, but the JAVA API is the only way to administer the tool and perform admin functions which i need.
Is there a better way? if there was a javascript client this would be easy, i'm just not sure the best route to connect my javascript web-app to this java tool.
Any thoughts/guidance greatly appreciated!
Thanks
API docs: http://docs.jboss.org/teiid/8.11.0.Final/apidocs/
If you are working with a JBoss stack, then might as well use their tooling. JBoss Forge can scaffold both a JAX-RS REST service and your Angular front-end at the same time.
I want to create a Android application (using Cordova/PhoneGap Ionic Framework, which means it's source code will be JavaScript + HTML + CSS and AngularJS as well. I need that app to sync to a cloud database service, but, I also have a .NET based project, which need to sync to the same database. I wanted to use like a Firebase-ish backend, that could manage all the database stuff, as I wrote only (at least mostly) front-end code for my app. Keeping in mind that I need a NoSQL database service.
To give an example:
I want my app to communicate with, let's say, CouchDB (IrisCouch on the cloud to be specific), and my .NET project to listen to the changes my app makes to the database, and handle them. What I need is a platform where I only need to call API's functions, or the closest I can get to that. I tried Firebase already, but that will get too expensive, as I need something cheaper, at least for now. Am I expecting too much? Do I really need to write server-side code in this case, and if so, which would you guys think it's the best way?
For back-end you can use ASP.NET Web-API which supports ASP.NET Identity with OAuth login like Facebook, Twitter etc. and on front-end you can you use IonicFramework with AngularJs to call those API.
Helpful resources:
ASP.NET
IonicFramework
AngularJS
Restangular (Restful operations made easy for angular)