In Anypoint Platform we have two business groups org1 and org2. In org1 group, I have updated the existing RAML API specification and same changes should be apply to org2 group API spec as well. Like this I have to update lot of applications. Is there any best method to update changes in one group to other?
Any tool suggest or any options in Anypoint Platform itself?
I understand that you have updated RAML files and you need to apply those changes to your Mule applications that are deployed in different business groups in Anypoint Platform.
Short answer: No, there is no existing tool to do that.
Long answer: updating files in your applications is done outside Anypoint Platform, for example in the IDE (Anypoint Studio) or whatever editor or development tools you have. In Anypoint Platform you use Runtime Manager to deploy updated applications. Runtime Manager doesn't has features to update files or any other changes inside your applications. This is a separation of concerns. Also Business Groups in Anypoint Platform are independent of each other. Each application deployed in Anypoint Platform is also independent of other deployments, even if the use the deployable file. So there is no way to say to Runtime Manager update this application file in all applications that use it. Having said that, you could probably use Anypoint Platform REST APIs and tools (like Anypoint CLI) to create your own tool to automate this kind of update, totally or partly, like when implementing a CI/CD deployment pipeline.
Related
Pardon if it's a dumb question, but I'm trying to build a personal website and, in order to kill two birds with one stone, use the website to fulfill the requirements for a web development class at my university. I want to build my website using Node JS with MongoDB and Bootstrap, but my course requirements at a later project require that I migrate my project (other students are expected to only have designed their website using pure HTML and CSS) into a .NET framework and use Microsoft SQL Server as a database.
I'd like to know whether or not I can wrap or use Node JS inside .NET or if it is feasible for me to fork my personal website to another version utilizing Microsoft technology.
Thanks.
No, you could not "wrap" or use in a practical way Node.JS inside of an ASP.NET web site. While you could theoretically start new processes from ASP.NET that run Node.JS code, it would be an unnecessarily complex setup (as you'd need to manage the processes, threads, etc.).
You can certainly use MongoDB and Bootstrap within an ASP.NET application, so some of your work could be shared.
If you will have the ability to configure IIS on your Windows server, you could use nodeiis to host a Node.js alongside a .NET site:
https://github.com/tjanczuk/iisnode
This approach works well. If you take this approach, be sure that any Node modules you include will work on Windows.
I want to add two applications inside one web role in Windows Azure. I'm using Visual Studio 2010.
There are a couple of ways of doing this.
The azure web role accelerator supports having multiple sites in a single web role (see https://github.com/microsoft-dpe/wa-accelerator-webroles). The documentation online regarding this is a little out of date due to the project having been discontinued. However its simple to setup. Just download the stuff from Github, compile and deploy the project from the download to your azure web-role, this then gives you an admin site where you can setup multiple applications within the web-role. You then deploy your application to there using web-deploy.
You can also add multiple sites to the service definition file, see http://www.wadewegner.com/2011/02/running-multiple-websites-in-a-windows-azure-web-role/ for an example of doing this.
How can we move our existing ASP .Net 2.0 application to the cloud platform ?
What all changes are required in existing application at code level as well as database level ?
Update: I have one ASP.Net 2.0 application with SQL 2008 database. I want to deploy it on the cloud environment with multi-tenancy support.
In that case what changes are required. Currently 'ConnectionString' is configured in web.config file. How to change the code/ database to achieve multitenancy support.
Basically I am looking for steps to move existing ASP.Net application to the cloud platform.
Please suggest resources for the same.
I am not sure what you mean by multitenancy suppport. Multitenancy usually means that you will need to work on your application and segregate the data for different organizations. Not sure what the cloud has to do with this. If you are expecting to just spin different instances for different organizations you will have to do work again with the API of the cloud provider in question. Some of them can manage applications and instances automatically.
Cloud provides scalability and elasticity (automatic scalability) it does not provide mutltitenancy by itself. To achieve maximum scalability you may need to use cloud data store (usually key/value) and let go of relational databases. This may require serious rearchitecturing of the application. Whether you need this scalability and elasticity is another topic and you may just use the cloud as infrastructure (i.e. they will manage the servers for you)
I am trying to a create an installer for my web application. My solution contains several projects. They include:
Class library project (referenced by the web application)
Web Application
Windows Service
Web Services project
Database project (execute update script)
I also have an unmanaged dll (crystal reports) in my web application project, so I might have to do some editing of the registry.
I ideally want to be able to use a web setup project to install the whole solution. Can this be done? Is there a better method/solution?
The short answer is "Yes" it can be done.
Other better solution? Well, I'm not a huge fan of VS.NET's installer/setup, can be kind of bulky, 3rd parties could be better at a price. Having said that, it should be able to satisfy your requirements.
I'm trying to create a standard way of rolling out web applications for our company. Currently we do it with zip files, vbscript/javascript, and manual some steps.
For thick client installs we generate MSI installers using Wise/Wix. We don't create installers currently for websites as in general they are just xcopy deploy. However we have some config files that need to be changed, verify that certain handlers are registered in IIS... The list goes on.
Do most people use MSI installers for web applications as well, or some other tool/scripting language?
I recently spent a few days working on automating deployments at my company.
We use a combination of CruiseControl, NAnt, MSBuild to generate a release version of the app. Then a separate script uses MSDeploy and XCopy to backup the live site and transfer the new files over.
Our solution is briefly described in an answer to this question Automate Deployment for Web Applications?
Do consider MSDeploy, that is the direction Microsoft will be investing in the future for deployment of web applications...
Know more about the future direction at Overview Post for Web Deployment in VS 2010
We have been using FinalBuilder (www.finalbuilder.com) for this purpose for long time and for some time also using InstallAce (www.Installace.com) for build deployment on the Web Farm.
You may want to look at:
How do I get a deployable output from a build script with ASP.NET
Step by Step ASP.NET Automated Build/Deploy
We use MSI to create basic installers for our web projects too, often using the Web Setup Projects in VS and sometimes completely custom installers. You may also want to look at MSDeploy.
We're moving to an MSI for our installs, so far with mixed results. I'm a control freak so I would personally prefer a series of scripts that I had more direct control over. I've used ANT in the past with good results.
Have you checked out NAnt and CruiseControl?
Combined, they can provide an easy and automated way to build and deploy your web apps.
I work for a state agency and we do all our deployments using a product called RepliWeb.
It works good because as dev's we have no control over the webservers. But we can deploy to a deployment area and run the RepliWeb job to do the deployment. Not sure on pricing though...