I have a question: for what purpose database is needed for Worklight server?
If it's for application center only (e.g. statistics, devices registrations, etc..), and I don't plan to use application center, can I avoid to use database?
Or if Workligth application needs the database (e.g. from what I heard - application's Adapters are registered in database) - then I must to use database always?
Thanks
Yes, a database is required for when using Worklight, be it for adapters, push or SMS notifications, various authentication mechanisms, Application Center (separate database than for Worklight Server), etc.
Related
I want to use a database between two sides of a software product consisting of two separate applications:
User side (Mobile) ---> Database <--- Admin side (Web application)
Questions:
Can Azure Cloud Services solve this problem or does a better solution exist?
Does Azure Cloud Services provide an SQL database in the cloud?
1) Yes, https://azure.microsoft.com/en-in/services/sql-database/
2)Connect two or more applications to the same database using Hibernate
this might help
3)https://azure.microsoft.com/en-in/documentation/articles/data-management-azure-sql-database-and-sql-server-iaas/
I working on my school project.My project purpose is movie rating application with ionic.When I will present my application on the phone.I need to get data on the internet.So I have to use cloud system for keep in web service and sql database.Oh also I will using sql database.I want to build database and web service on the azure.But its my first time for azure.How can I migrate my sql database to azure and how can I create web service in azure.Im rookie these things.I need a starting point.I searched on the web but cant find a good tutorial :(
If your SQL Database and WebService structure is not a requirement, you can also explore other options such as Mobile Apps. Mobile apps is a workload on Azure specifically built for such scenarios to connect with mobile devices and two way data communication. It uses what is called "Table storage" on Azure. You can start with that and later on move to a no-sql database such as DocumentDB for persistent storage and querying.
You can find a step by step tutorial below on how to create the Mobile apps and connect it to different platform such as Windows Phone, Android or iPhone. The link here is for Android. If you wish to use other platforms you can use the tab to switch to them. It will even give you a sample project that you can download and run directly which can get you started pretty quickly. I also have a blog post around this if you are interested.
https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-android-get-started/
Hope this helps!
Is it possible to handling handling external inserts/updates to Azure SQL Database from Azure Mobile Services (INSERT, UPDATE, directly to db and etc.)
I know about scripting. All tables working fine, and visible from Mobile Service manage center.
I need to handle events like direct SQL requests to DB from DB management portal or Azure Web sites, without direct requests to Mobile Service (REST API, and etc.)
Is the question how to execute SQL commands from a mobile device directly against the database (SQL Database) without first going through the REST API and scripting layer Mobile Services provides?
If so, then the answer is essentially no. The mobile device needs some way to communicate with the database, it uses the API and scripting layer to do this. Of course, you could build your own web service layer that then works with the database. But, this layer is what Mobile Services is providing for you out-of-the-box.
However, if the question is can you issue SQL commands against the database using tools like SQL Server Management Studio or even other web sites, then the answer is yes. The SQL Database which Mobile Services provides is a regular SQL Database. You have full control over it. You can connect to it and issue commands just like you would with SQL Database (via an ORM or direct SQL statements).
Does anyone know if it is possible to install more than one database in Worklight Server?
Reason for that; I have different underdevelopment applications, developed using different databases (DB2,MySQL, and Derby).
There are some flaws in this question...
you do not install databases in Worklight. Rather, Worklight uses the database you choose to use for it.
You do not develop applications using databases. Rather, your applications communicate with databases and other backend systems (in the case of Worklight, using adapters).
The answer is No.In worklight.properties you may specify only 1 database type for Worklight Server to work with.
In Worklight 5, 1 Worklight project = 1 Worklight Server instance, with its own specific setup.
A Worklight project may contain several applications, depending on how and what you develop. This way you could switch them all to use the same database type.
Extra:
The only time where you can specify another, different or not, database type is when you have Reports enabled. This, however, would not be a recommended approach. You shouldn't use different database types for the same instance of Worklight.
Also, the concept you mention is not possible in Worklight. For different applications to communicate with different databases, it means your applications belong to different Worklight projects, which means that each project belong to a different Worklight Server. In this case, if you have multiple Worklight Servers, then sure, each server can work with a different database, but you cannot have 1 Worklight Server to communicate with multiple databases, each catering for a different Worklight project.
We have an SQL contacts database that links into all our project information with lots and bells and whistles.
It has recently been suggested that we make the contacts part of this information available to our end users in their email clients - so we are looking at setting up an LDAP server
Are there any out there that will allow us to map the information in the DB (probably a view I'd suspect) to an LDAP server?
OpenLDAP has support for a metadata driven SQL backend using back-sql. The state of testing varies with your chosen RDBMS backend.
UnboundID's Synchronization Server supports synchronizing databases with directory servers in real-time and in bulk.