Openfire access to database with webservice - web-services

I want to develop a IM client with openfire. And there is an existed system with database, we need openfire to access to the existed database to find the users.
I want to operate the database with webservice.
How can I do this?
Thanks

In order to use an external database, use this tutorial, it works well openfire integration
There is no way to use webservices to do this

Related

How to make an api completely independent from the main Django Project?

I have a django project that is hosted internally, and this project feeds the database. I need an API that serves the data of that database to a public domain (that api does not do any DML only selects), but this API needs be hosted in a diferent machine and even if the project that is hosted internally explodes that api needs to keep working.
I am using DRF for the api
I did an api project that has its own apps, views, serializers and models(those models connect to the db existing table like this) and only have the fields that I need represented. Is this the right way to do this or am I missing something? The thing that I am worried is if one of the columns of a model changes name i will have to change the model in the api, but that is a very rare modification.
I don't know if I understood the question correctly but it seems from your question that you have a DJANGO project along with the DATABASE hosted on a particular machine. If that is the case then if your server goes down external API's will not be able to fetch your data.
If on the other hand you have a dedicated server or RDBMS for only your database then you will be able to fetch the data using any API connecting to that database server.

Firebase-powered app with web service code

I am planning to use Firebase database and want to know how it fits in to the following scenario.
lets say I have a browser app, android app / iOS which uses Web Services to get / insert data, web services talks to the Data Base and returns data to the client.
This way I have to write code once in my web services and all the clients use that to retrieve and insert data to the database.
If I want to use Firebase, will I be following the same approach of having webservices between the client's and the Firebase DB.
I have done some sample Firebase examples where it it gets data from database directly without web services and in this approach we have to write our logic on each client (Web browser/ android app/ iOs app).
I have looked into this article
https://firebase.googleblog.com/2013/03/where-does-firebase-fit-in-your-app.html?showComment=1480073224245#c464815735109872173
The Pattern 2 has the server concept but that does not look appropriate in my scenario.
Can I have my web service and Firebase database and get data Synchronization capabilities.
Correct me if I am wrong and please suggest the approach I need to take.
Thank you for your valuable suggestions in advance.
Thanks & regards,
Rao Burugula
The article you link gives you the most common options for integrating Firebase into your app. Pattern 2 is the easiest way to use the Firebase Database and run your own server-side code:
In this model the Firebase Database sits between the app on the user's device and your back-end code. By using this model, you can still get all the benefits of the realtime synchronization, security rules and scalability, but also have back-end code that runs in a trusted environment.
Of course you can also go for a more traditional three-tier model, where your app server sites between the devices and the database. But in that case the Firebase database won't have direct interaction with your app anymore, so you'll have to take care of the realtime aspects of the synchronization (if you want those) in your own code.
I also recommend reading the Google Cloud documentation on using the Firebase Database and App Engine's Flexible Environments. The architecture described there is the same, but a bit more up-to-date:

How to Create a Process in Informatica Cloud Real time which gets exposed as Restful service and can be invoked from browser or else where?

Can we create a Webservice using Informatica?
I am very new to Informatica.
Is the below requirement possible in using Informatica?
My requirement is -
"I want to create a Real Time RESTful webservice within Informatica Cloud which will fetch data from an Oracle Database and present output in JSON format when an particular URi is invoked."
Note: I am not trying to connect to a Webservice, so please don't tell me about Webservice connector.
I want to create a Webservice Server Provider within Informatica so that when someone calls a URI in browser, this should query the Webservice deployed inside the Informatica Cloud and present the data on the browser in JSON format
Edit: Re-framed the question in a more Informatica kinda language
Note: If you provide step by step process I would really appreciate it.
I am a Java developer and I started learning Informatica like a week ago, I started from "What is Informatica?". So please explain as if you are explaining an idiot.
Update :: I have been using the following link as a reference. Using this as is doesn't work. I have been trying this for months now. I get an error while deploying. "Can't be deployed within tenant context" So definitely I am missing something. Can anybody throw some light on this please ?
http://www.onbostonharbor.com/Informatica/index.htm#page/bpm-na-process-developer/GUID-575B15AD-B21D-4979-9801-70564434FF2B.1.033.html
Oliver, is this still something you're trying to do?
In Informatica Cloud, you can define a JDBC connection to any JDBC-accessible database. To access the associated database via REST, there's an extra step on the connection definition where you specify that that you wish to OData-enable that particular connection. (OData being a particular REST specification.) You also have to specify which tables you'd like to expose. When you publish this connection, there will be a URL or service address that you can use to invoke this. You don't have to have this inside a full-blown process.
Then from within a browser or any HTTP-compatible client (Postman, for example), you are able to access any of the tables you've exposed using OData commands.
You can get some good background on OData at http://www.odata.org/getting-started/basic-tutorial/.
Hope this helps.

Sending data to the web service

I'm developing an application that requires storing data on an internet database.
Because of WP7 doesn't support databases,I think if I send my variables-datas to the web services that i craated,i can do what i want.
I know how to write a webservice but how can i send my variables to the webservice from WP7?
You can have a look at http://www.sterlingdatabase.com/ which provides a nice and lightweight database. I'm also using this in my project and it works fine.

Microsoft Dynamics CRM -- Do people build websites with it?

Forgive my ignorance, but do people build websites with Microsoft Dynamics CRM?
I have a potential client who says that is the technology they will use for a new web project, for which I would be doing the HTML templating. I want to learn all I can as I am new to this particular system, but I can't seem to find anything related to web building and CRM. Is it more likely the client is using another piece of technology that they are neglecting to tell us about?
Any experience or insight about this process is greatly appreciated!
You can't build website using MSCRM, but you can build ASP.Net website using CRM content easily. The API provided by MSCRM is a set of web services, that can be queried in a website to populate pages content.
Also, you can directly query the Database if you want ReadOnly content, and only for read-only content, because it is not supported to update/create data using SQL connections.
Note that it's required to have the external connector license to use any data in the CRM, thru the API and even thru direct SQL queries.
I have built a website using .NET, utilising the CRM4 API and database. All the website did was to submit queries to CRM using the CRM web services and metadata web services, and get data back. This company was already using CRM for their back end, so it's much easier for the front end to use the same database as well since it's a simple one.
The alternative would be to create an intermediate connector between the 2 systems -- backend and front end, which is not as efficient (for our case anyway).