RavenDB automation - RESTful way to add users to system db for Windows Authentication? - ravendb

Situation:
Automated commercial RavenDB 3 server install & configuration on Amazon EC2 to a standalone server (no active directory domain). Local Windows users are automatically created.
Problem:
Using the HTTP client API, how to add local windows users to the Raven/Authorization/WindowsSettings document of the system database?
Reference:
The docs describe a method using the Studio to achieve this:
https://ravendb.net/docs/article-page/3.0/http/server/configuration/authentication-and-authorization

The document is just that, a standard RavenDB document. You can operate on that using the standard JSON REST endpoints to manipulate it.

Related

How to develop an ASP.NET Razor Pages web application using a cloud database?

I have been using local databases to develop web applications in ASP.NET Razor Pages. My experience was that the local database creates itself simultaneously with the development of the web application.
Currently, I need to work with a cloud database set up in Microsoft Azure. This cloud database already contains tables. How can I connect to the cloud database and call these tables and their attributes in razor pages?
You need read the offical document first.
There are two ways you can set your sqldb connections. One is written in the appsetting.json file, and the other is set in the portal, as mentioned in the official documentation.
The difference between the two is that the setting priority in the portal is higher than the configuration in the code file, and the configuration will be overwritten when it is released.
For novices, you can get the Connection strings in the portal. Then you first ensure that your program can run normally, and replace the connection string in the appsetting.json file with the string provided in the portal. If normal CURD operation is possible, then the connection is successful.

Configuring Domino Access Services

Domino Database and Folder/View present in the database shall be enabled to access documents and views present in domino database.
Manual procedure is mentioned to enable Domino Data services in the documentation.
Is it possible to programmatically enable Domino Data Services for Domino Database and views?
You can use the Extension Library REST Services.
Take a look at Extension Library REST Services.doc here you can find information about the four types of REST services which are included in the extension library.
UPDATE:
I would prefer to use the Extension Library xe:restService service.
If you have installed the Domino Designer you can find it as shown in the screenshot below:

How to move a windows .net runtime frontend application to the cloud (it uses a local sql server backend database)

I had a engineer design our .net application back in 2009, my guess is that it was coded using visual studio, and all I have is the installer application. We have been using it on our 1 or 2 local client machines very well for the past few years, but now I want to move this front end to the cloud. Instead of installing it as an application on our windows 7 machines.
It is a very simple application used in our small warehouse that keeps track of cargo/shipments etc. It uses Sql Server 2008 Express as a backend which is stored locally.
I know how to get the database in the cloud, their are many options for that, using Amazon or Azure, but how do i get the local client application to the cloud?
I dont have access to the visual studio code, i just have the runtime executable file..
I am sure there is no way to do this, and many of SO users will say i need to re-write the front end.
I have tried to contact the developer and they hav since closed down. Is their anyway i can run this in the cloud?
I welcome all options and solutions!
Thanks.
I believe you have two options for hosting this application:
If you are able to configure the database connection string, you could host the database in the cloud, and distribute the application to your end users. However, you've already stated that you know how to move the database, so I assume this isn't an option.
The only alternative is to run the entire application on a cloud server, and send the user interface to a client using terminal services. This makes it appear as if the application is running locally on the user's computer, while it is actually running on the server.
For an off-the-shelf solution to achieve this, you could consider using Microsoft's RemoteApp Azure service. I'm sure there are other similar offerings available.

Alternate Access Mapping not working in SharePoint 2010 Workgroup

I have tried to configure alternate access mappings in my SharePoint 2010 which is installed in WorkGroup Windows Server 2008 R2 server but could not make it work.
Here are my steps.
Go to Central Administration-> Manage Web Application.
Select a web application and extend it.
Provide the my12server.com in the host header and leave other default values as it is. I changed the zone to Extranet.
Click Ok.
After sometime, it creates Web Application in SharePoint and Web Site in IIS.
I have changed my hosts file by adding entry
192.168.1.11 my12server.com
Browse the new extended. It asks for credential. Supplied the correct credential but nothing got display. Just a blank page.
Note: I have however successfully extended web application when the SharePoint 2010 is in domain machine.
Please advice me.
Thanks
Prakash
SharePoint is designed to work in domain environments only. In other words, you cannot expect to run it on an underlying Windows Server which joined into a workgroup and expect full functionality. Although there are blog posts around describing installation in a workgroup environment (or, better to say, using local accounts), I wouldn't recommend wasting time with such a mode of operation.
Furthermore, it doesn't make sense to extend a web application just for the sake of providing another hostname. Extending web applications multiple times is mostly useful when you need different authentication providers for each of them. In your simple case you can just configure multiple Alternate Access Mapping records for a single web application.

Cannot access WSS 3.0 sites after movind Content and Config DBs

Problem:
No access to internal sites after new Instance of SQL was installed on MS SQL Server
Description:
I've got a WSS 3.0 installed on the W2K3 Sever.
Originally, there was only one Instance of MS SQL (MSDE) for Backupexec (bkupexec). Later, we installed WSS 3.0 and instead of installing the new instance of SQL we installed on the same instance (bkupexec). So, at some point all the DBs from Backupexec and DBs from WSS were all together within the same SQL instance.
After we noticed this we wanted to split those two into two separate instances: bcupexec and sharepoint. First, I have done a backup of all DBs within backupexec instance. Then, I installed new SQL Instance and called it Sharepoint and tried to restore all WSS DBs into the new SQL instance. Once that was done I check references in IIS so Content and Config would point into the new instance. But since then no go.
I can access Admin site from within IIS and from the browser. I cannot access any internal WSS sites. It asks for the authentication. All I am using is Windows authentication. Account is in AD.
As I am new to WSS I will be greateful for all suggestions and possible fixes.
If you have changed where the content DB's are located for your site collections you will need to detach and re-attach them using the SharePoint Central Admin.
Navigate to Application Management and switch to the application you're concerned about. Click "Content Databases" under the heading SharePoint Web Application Management. From here you can click "Remove content databse" and hit OK.
This will not remove the physical database from SQL, it will simply disassociate the database with that web application. You can then Add a content database from within the manage content databases screen and type the name of the database you wish to associate the application with.
If the permissions issues persist, ensure that Anonymous access is enabled for the application and that appropriate service account permissions are enabled for the DB's from within SQL and SharePoint.
Not sure this will help, but give this a try...
In central administration make sure you check on the site collection administrator for your site collections and make sure you are using that user.
In IIS Manager, check to make sure that user has access to the IIS web site.