I want to run mongos (that's the mongo route server named mongos, not a malformed plural, but I digress) on the server that's hosting our application layer. I need to run as a Windows service and I have poured over the directions on 10Gen's website. However, the tool set they recommend (Windows Resource Kit) is for Server 2003 (and prior) and is not recommended for use on 64-bit platforms. All my application servers are 64-bit 2008r2.
The documentation implies that mongos as a Windows service may be supported beyond v1.8.1. Has anyone had success deploying mongos as a Windows service on a 2008 server? If there is no native support, is there another version of the resource kit, or did you roll your own service wrapper?
Thanks for any information you may have.
-Seth
The request to add built-in support for running mongos.exe as a Windows service (the way you can run mongod.exe as a service) is outstanding as https://jira.mongodb.org/browse/SERVER-1589 -- you can vote for it to show your support.
srvany.exe does work in Windows Server 2008 R2 using the directions you referenced: I just tested it with MongoDB 2.0.2. The srvany.exe process is 32-bits, but it runs a 64-bit mongos.exe just fine.
Related
Is there any way to run the On Premise Independent Integration Servers in IBM ACE as a Windows Service.
Integration server when deployed on an independent VM or laptop or bare metal is managed by Integration node. Integration node can be run as a windows service. You can check your services.msc on windows platform to verify.
I have installed Hyperion EPM 11.1.2.4 in CentOS 7 i.e Foundation Services, Essbase and Financial Reporting. The database I have used is SQL Server.
CentOS is not the officially supported OS for Oracle HTTP server and hence I went ahead with Weblogic HTTP server.
Once I start the weblogic server and start all the EPM services, and when I login into the weblogic server administration console, I find my foundation services server in Admin state
Also when I login into my Oracle Fusion middleware, I can see all my foundation services and financial reporting Servers down.
And hence I am unable to access the servers like workspace, calculation manager.
But few of my servers are up and are in running state such as APS, CALC, EAS, EPMAWEBTIER. But I only can access Essbase.
I request you to check the images attached.
Oracle Weblogic Administration Console
Oracle Fusion Middleware
How can I access these servers?
Am I having these much of troubles just because I used weblogic HTTP server instead of Oracle HTTP server?
if you are installing EPM for learning purposes, I suggest you to take the easy way and use a supported OS. Installing this software into a non supported OS will give you additional problems that you will never be sure if are caused because the non-supported OS, or because your installation / tuning is wrong.
If you download and install a Windows Server VM, it would not expire, just show you the active license message, but it will be full working.
For learning purposes / temporal Virtual machines, it is way to go.
Thanks.
The problem statement:
Suppose there are 20 windows machines within a local network. One of the machines serves as the server and hosts the database. Now, the other 19 machines have the access to read from the server machine, but the server machine does not have username and password for any of the other 19 machines.
I have to update a desktop application installed on all the machine. There is a spring-boot application, hosted on the server machine which downloads the build. Now, as soon as I download the build I have to notify all the other 19 machines that build has been downloaded so that they can read and update themselves.
Solution 1: Install a windows service which will poll the server and check if updates are available.
Solution 2: Host a POST web API on the 19 machines and notify them by making a post call. I think installing IIS or Tomcat on every machine is not viable.
Is there any other optimal solution for notifying the client?
Note: We cannot take the RDP and neither have credentials but we can make use of already deployed windows application on the other 19 clients.
Solution 3: If your machines share the same domain, use msi install packages to update software all across domain by using Group Policy. It's common way.
Solution 4: Launch desktop application directly from server shared folder. It works good while server machine is always accessible and application is not too heavy for your LAN.
Here you need some care about writing new application files while it running on client computers. Good way is to keep a different folders for different versions and launch with shortcut pointing to latest one:
v1.3\app files here
v1.4\app files here
v1.4.6\app files here
v1.7\app files here
app.lnk → v1.7\app.exe
client machines launch the application with app.lnk.
Upd: if you update application when nobody works (see 1am…2am), you can omit all of this versioning stuff.
Solution 1: It work as well. You can use NSSM to easily launch your update script or exe-file as a Windows service.
I would use a windows service or a scheduled task (both could be the same application you provide, but with some arguments). It frequently checks if a new version is available (maybe only once a day).
If you only have a short time frame when the new version has to be installed on all machines you could also provide an installation date with the new version. (Maybe the check will be done through a REST api where the client sends the current installed version number and the server answers with an status code 200 and the body is either empty or provides an json object containing the new version number, the due date and the download url.)
Then the client can already download the new version and make it available on the machine, but it triggers the installation only when the due date is reached. This check of the due date can happen more often, cause all informations are already on the client machine and can be done locally.
Is there a way to find all the web services running in my system?specifically rest services if possible?I am using windows 7 system 64 bit.
Well, I think you are thinking in two different things...
The first is "services" running on your operating system (Windows 7), and a service could be more than a web service, for example your database or your application server.
The second, a web service is running (when it works fine) through a application server (JBoss, Weblogic, Glassfish), not in a operating system, so if you want to know your web services you must to log in into your application server and search them, or check in the folder of deployments to know about it.
I recently installed Windows Server Service Bus 1.0 (on a Windows Server 2008 R2 machine).
That also installs "Windows Fabric" (not AppFabric).
Could not find much information on it, and googleing it I stumbled on a Lync server post (Windows Fabric is also installed by Lync Server 2013).
Definition:
"Windows Fabric is a Microsoft technology used for creating highly reliable, distributable, and scalable applications."
From the Service Bus architecture intro,it looks like Fabric is what allows for services replication, high availabilty, and fault tolerance.
Anyone knows if that can be used to host custom .NET services? Or any kind of direction would be greatly appreciated.
Thanks in advance.
Cos
I went to a talk by Mark Eisenberg on May 28th at the Microsoft NERD Center near MIT in Boston MA. The talk was mostly about the Azure Service Fabric. General consensus was that if you're using Azure from the infrastructure as a service perspective you aren't really using it.
The next step up is to use Azure naively as a platform meaning that rather than create VMs and hosting them there you're creating cloud services and web jobs and web apps and using the new Logic Api's etc...
But if you really want to build a stateful, resilient service enterprise class you'll want to go underneath the PaaS and write against the Service Fabric directly for greater control.
That's where the money is.
I did a write up on the talk and what the Azure Service Fabric is a few days ago and posted it here.
I don't actually think that Windows Fabric is open product. It is used for infrastructure purposes, and not for deploying custom services. For your custom services you have to use platform built on top of Windows Fabric, like Service Bus, Windows Server App Fabric.
I think Windows Fabric is for internal use by Windows Azure and Private Cloud for clustering, load balancing and so on.
UPDATE:
I've started developing Windows Azure application and here is what I've found.
I've added a Service role to Azure application and started it on local development machine (under Azure emulator). And my service was published in and started under Windows Fabric!
So the conclusion is: Windows Fabric is a platform for running YOUR Cloud Services.
Fabric which the name suggests in itself, is back-end.
It is no different than iSCSI or EIGRP. The main difference is that it is generic in form rather than specific like the aforementioned services/protocols.
IIS is a server service specific to web hosting.
SQL the same but database only..
fabric, applied to host fabric aware services and software.
Windows Fabric is used internal by Microsoft to building highly available, resilient and scalable services. It has been used for Service Bus, SQL Database, Document DB etc. according to this video: Building Resilient, Scalable Services with Microsoft Azure Service Fabric
Until now it has not been available for external parties but has now been announced as Service Fabric which will be available on Windows Azure and Window Server 2016.
Read more here: http://azure.microsoft.com/en-us/campaigns/service-fabric/