Can the appFabric replace the window services ?
Actually what is the difference of the appFabric and the window services ?Any references or examples are welcome which sight the differences
AppFabric is a distributed caching solution that can be used to enhance your hosting solution for more details check the following link
When the AppFabric is installed, It creates a set of windows services starts with "AppFabric" such as AppFabricCachingService and generally you don't start those services from the services console however you start them from the powershell such as start-cachecluster
Related
I've read some articles recently on setting up AWS infrastructure w/o enabling SSH on Ec2 instances. My web app requires a binary to run. So how can I deploy my application to an ec2 instance w/o using ssh?
This was the article in question.
http://wblinks.com/notes/aws-tips-i-wish-id-known-before-i-started/
Although doable, like the article says, it requires to think about servers as ephemeral servers. A good example of this is web services that scale up and down depending on demand. If something goes wrong with one of the servers you can just terminate your server and spin up another one.
Generally, you can accomplish this using a pull model. For example at bootup pull your code from a git/mecurial repository and then execute scripts to setup your instance. The script will setup all the monitoring required to determine whether your server and application are up and running appropriately. You would still need an SSH client for this if you want to pull your code using ssh. (Although you could also do it through HTTPS)
You can also use configuration management tools that don't use ssh at all like Puppet or Chef. Essentially your node/server will pull all your application and server configuration from the Puppet master or the Chef server. The Puppet agent or Chef client would then perform all the configuration/deployment/monitoring changes for your application to run.
If you with this model I think one of the most critical components is monitoring. You need to know at all times if there's something wrong with one of your server and in the event something goes wrong discard the server and spin up a new one. (Even better if this whole process is automated)
Hope this helps.
I've recently started looking at WSO2 Identity Server as an alternative to what my company is currently using.
I'm finding it difficult to determine what SOAP and REST services are exposed and what the URLs for those are.
I've tried starting the server (on my Windows machine) with wso2server.bat -DosgiConosle , but I can't seem to get the OSGi console after the server has started.
Is there any other way to get the list of services exposed by the product?
Also, I'm not aware of the service API being documented and made available - Are there plans to do this?
Any help in getting the list of services or an instruction on how to do it would be greatly appreciated.
WSO2 products currently do not have a documented service API. However you can use OSGi console to view the available service components details.
Make sure that when you start WSO2 IS with osgi console the following log is visible, which says that the console is enabled.
sh wso2server.sh -DosgiConsole
JAVA_HOME environment variable is set to /jdk1.6.0_30
CARBON_HOME environment variable is set to /wso2is-4.1.0
OSGi console has been enabled with options: -console
After server is properly started, press enter and osgi> console will be displayed.
[2013-07-24 16:33:57,215] INFO {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2 Carbon started in 17 sec
[2013-07-24 16:33:57,437] INFO {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL : https://localhost:9443/carbon/
osgi>
By entering necessary osgi commands you can see the activated OSGI service etc. For example if you need to see available services use,
osgi> services
This will list down all the services in the runtime. Use appropriate filters to find the WSO2 IS services by referring this blog post.
osgi> ls
This shows all the osgi service components along with their component ID and life-cycle status. If you need to now on particular service component use ls -c command.
The following question thread has useful information on WSO2 IS API too.
WSO2 identity server api
start the server with the following command(case sensitive)
wso2server.bat -DosgiConsole
and you should see the osgi> console
This link leads to an information how to list admin services exposed on WSO2 product (osgi console must be enabled)
List all ws in wso2
1) Start the server with osgi console.
wso2server.bat -DosgiConsole
2) Run following command 'listAdminServices'
osgi> listAdminServices
This should show all the admin services exposed by the server.
I am working on an automated deployment process for a web application. The deployment will need to:
Deploy DB changes to database using sqlpackage.exe
Deploy reporting services reports to the reports server using the web service
Deploy web app to web server(s)
Deploy fonts for reports
among other things
The first two are reasonably straightforward to run from the web server, as the web service and db are contactable, and the tools to deploy run over the network.
From reading it appears that powershell remoting should be the way to go, and internally this would not be a problem. However when deploying to production, this will be being carried out in a datacentre, where the machines (2web, 1db) are not on a domain at all. I'd like to come up with a generic process that can run both internally and externally with the appropriate configuration. Powershell remoting, with machines not in a domain appears to require a fair bit of configuration using https etc., as NT credentials can't be validated.
Should I battle out configuring powershell remoting, or would configuring this to just use psexec to execute a powershell script directly on the remote machien, copying the deployment artifacts to a drop folder on the remote machine be the best way to go?
psexec seems to "just work". It appears powershell remoting comes with a lot more pain.
Why not use psexec then? You can restrict it's role to just getting you on to the remote machine, and not let it infect your scripts. I have not attempted to get ps remoting working on a non-domain, but it general I have found it to be fairly high effort to get going. Psexec, as you say, can often be simpler.
Excuse the peddling, but the open source framework I helped build called PowerUp essentially does all this for your. It uses a model in which the powershell (well psake) scripts can move execution to another machine by calling a specific function. This can either be done with powershell remoting or psexec - you wouldn't need to change the script, it just requires a setting per environment to say which you would like to use.
Check other the sample at https://github.com/AffinityID/PowerUpSamples/tree/master/SimpleWebsite.
Hopefully that shows you enough, but if not let me know and we can go into more detail.
Recently I tried to enumerate the Windows Services on the VM where my Azure web role instance runs using ServiceController.GetServices() - there's a lot of them including Telephony and CloudDrive which I don't need and so having them started is a waste of resources.
Is it possible to have them not started?
Yes, but you'll need a startup task to do this. Here is what you'll do to stop and disable the Telephony service:
sc.exe stop TapiSrv
sc.exe config TapiSrv start= disabled
As you can see I'm not using the display name (Telephony) but I'm using the service name (TapiSrv). If you want to get a list of service names for your system you can simply execute this command (in Azure you can do this via RDP):
sc.exe query
Executing this command will also give you the state of the service (running, ...).
Note: When calling sc.exe config you need to put a space after the equals sign.
Note: Stopping services can take some time, so I suggest you use a background task to stop/disable the services, in order to keep the startup time of your instance to a minimum.
I'm using the VS 2010 GUI profiler to profile a service on my machine. I have to attach to a running service. When I stop the profiling session it kills the service. I don't think that it did that in VS2008. In any case I can't find any option that will allow the service to keep running.
Thanks for any help.
If you attach to the running service you should also be able to detach from the service.
Instead of choosing 'stop profiling', open the 'Attach Profiler to Process' dialog and select the service process and choose 'Detach'.