I have an application that needs to be deployed to two different servers (environments).
I have two environments on two separate servers, server1 and server2.
Both servers have different IIS Manager user accounts and passwords configured.
The builds however all happen on server1 and it appears that no matter what settings I pass via the build definition, everything gets deployed to server 1.
I can publish to server2 manually from the Publish command in VS2010 but this needs to be automated in TFS.
This used to work fine but then started happening a couple of weeks ago.
How can I correct this problem?
In the end, although I followed the IIS generated settings file, I had to set the MSDeployPublishMethod to WMSVC (it was set to MSDeploy). I can't tell you why this works and the other doesn't but this is how I solved it. If anyone has any details on where one can find out more about the various Web Deploy settings please advise!
Related
I have made a copy of one of our live ldap servers to use in testing environment.
In our live system we have 2 ldap servers in master/master configuration.
My question is on our testing environment as there is only one server how can I delete the offline ldap server from DSCC. I have tried to remove it using the web interface but as its offline it throws an can't communicate error.
I have also tried using the dsccreg remove-server command with no success.
Any ideas?
You probably want to look at MOS note 1920317.1
I have deployed my application running on my local server # http://localhost:8048/myservice?day=xx&month=yy&year=zzzz , it works succesfully on my local machine, in that it downloads a file from the http site. However when I deploy to Mule Management console . I understand that the default port is 8585. When I change the URL to MMC & give the default port with the same path, it does not download the file . Am I missingsomething
The MMC is a utility for managing and monitoring Mule Standalone Runtimes.
One of its functions is to deploy apps to a Runtime. You are not actually deploying to the MMC.
Does this help clarify the situation or do you want any further help on want The MMC is used for and how to do it?
Please check the logs inside MMC.It stores the logfiles date wise.See if your application has been deployed in MMC successfully and if yes then do the following things:
1)If you are using any path to download the file then cross check the path details.You can put a logger to crosscheck that.
2)Put a logger before the business logic and after the business logic and follow what it is logging in the log file.
3)In case your server is Linux then check the path separator pattern
MMC is a Mule Management Console which is used (provides provision) to deploy, undeploy, manage, monitor application and server both. From the statement you mentioned in your query it seems you are trying to deploy the app in the MMC - MMC is not a server its a console where you can register your ESB Runtimes -or- API Gateways (on-Prem) servers so that you can deploy the applications to the server/runtimes (which will go to the runtimes location $MULE_HOME/apps).
Please check if you have registered the server under MMC's Server tab - if not then you have to do this first and then it will allow you to perform application deployment using the MMC's APplication tab where you can upload your deployment archive/artifacts/build to the mmc repo and then you can deploy through the deployment options by selecting your server (which you have registered).
If I am missing something from your statement then please clarify more and will try to help you out here.
Azure VM, Cloud service or Web job?
I have a configurable console application which runs continuosly. Currently it is running on a VM and consumes lot of memory (it is basically doing data mining).
The current requirement is to have multiple instances of this application with different set of configuration which can be changed by specific users.
So where should I host this application such that the configuration can be modified using some front end which provides access managements(like Sharepoint),ability to stop it/restart (like WCF service) without logging on the VM?
I am open to any suggestions/ideas. Thanks
I don't think there's any sold answer to this question as there is the preference variable but for what it's worth, if it were up to me I would deploy it against individual azure VM's for each specific set of users. That way if the server resources went up because of config changes the user group made it is isolated to that group, and with azure, will scale automatically to meet the resource demand. Then just build a little .net web app to allow user to authenticate and change configuration settings.
You could expose an "admin" endpoint for your service (obviously you need authentication here!) that:
1. can return the current configuration
2. accept new configuration
3. restart the service (if needed). Stopping the service will be harder, since that leaves the question on how to start it again.
Then you need to write your own (or use a 3-party (like sharepoint or a CMS)) application that will handle your users and under the hood consume your "admin" endpoint.
Edit: The hosting part: If I understand you correctly your app is just an console application today, and you don't know how to host it? Well, there are many answers to that question. If you have a operations department go talk to them, if you are on your own play around and see what fits you and your environment best!
My tip: go for a http/https protocol/interface - just because there are many web host out there, and you can easy find tools for that protocol. if you are on the .NET platform check out Web.API or OWASP
Azure now has Machine learning to process data mining.
You should check if it's suit to you.
Otherwise, you can use Webjob:
Allow you to have multiple instances of your long time running job (Webjon scaling out).
AppSettings can be change from the Azure Portal or using the Azure Management API
Multiple TFS 2010 MSBuilds are not triggering Web Deploy to publish the web application to the IIS website.
This is for multiple different software products, multiple different build configurations, 2 different build agents (on 2 different servers), multiple IIS web site instances on multiple different servers.
3 different continuous deployment setups were previously working.
So hopefully this rules out miss-configuration of the build/build servers/hosting servers/web deploy and IIS.
According to the network manager nothing has changed on the network (all servers are local), and port 8172 is not blocked by any security configurations.
All builds succeed, web deploy fails silently (no error, nothing in the logs). It appears that web deploy is no longer being triggered.
Are there any other ports that are used here?
What else could be blocking the communication between MSBuild and Web Deploy?
Would you expect it to fail silently (nothing in the logs or passed back to MSBuild)?
UPDATE
This is a similar question How to determine if MSBUILD Arguments were executed for TFS Build Definition
Assuming you are using vs2012, on your build server make sure the following two folders exist: Web & WebApplications in
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0
If these dont exist then need to be copied from a machine your do development on. This worked for me, and solved all of my problems with the Deployment of projects.
I have two applications with a single domain name (www.domain.com and test.domain.com).
First one has been developed in .NET 2 and the other one with .NET 4.
I have configured Web.Config as these steps:
I've set the same machine key for both of them.
I've set the cookie name.
I've set the domain name to "domain.com".
Also, I've set hard-coded cookie domain name to "domain.com" .
Everything was working fine when both of them were running on a single web server. Recently, I've been asked to move test.domain.com to another server. After moving, authentication ticket is not valid on the second server.
I tested both of them on a single server again and everything was working fine, but in two servers users can't access to test.domain.com. (Authentication Ticket is invalid)
Edited:
The second server is a virtual (VMWare) server. I don't have any problem in physical servers.
I checked the server's time to be synchronized. I also used Fiddler to see if the server does not get the auth ticket and their ticket is sent to the 2nd server.
Note: Servers are located in different networks and maybe proxy or firewall causes this (I've no idea)
Is there anything I missed?
Finally I've found it here:
http://weblogs.asp.net/scottgu/archive/2010/09/28/asp-net-security-update-now-available.aspx
One of ther server was not update, after installing the patch the issue solved!