I'm trying to update an application in the evaluation version of Mule ESB EE.
I upload to repository, create a new deployment and start it.
But the server is still serving up the old .xml
I've tried stopping and starting the service, creating a new one with another name and whatnot but still no luck. Only thing that works is hot-deploying (drop the zip file into the directory) but that has the drawback of not showing up in the mmc.
Checking the Mulesoft forums yields one similar question that was posted 8 months ago (around october 2012) with no resolution.
Has anyone here run into this and knows of a fix?
Edit
I figured out a workaround:
When exporting the project in Mule Studio, instead of "Publish to Application Repository" select "Mule Studio Project to Mule......" (the zip file)
Using the mmc interface go to deployments tab, select repository and create new.
Import the .zip file you just created and deploy as usual.
(Also added this answer to the Mulesoft forum question)
I guess the workaround is all there is so I'm marking this as solved with that as the solution
Workaround:
When exporting the project in Mule Studio, instead of "Publish to Application Repository" select "Mule Studio Project to Mule......" (the zip file)
Using the mmc interface go to deployments tab, select repository and create new.
Import the .zip file you just created and deploy as usual.
Related
I'm trying to develop an application with Anypoint Studio and SAP. I imported the SAP connector from Mulesoft Exchange, added the correct SAP libraries (I added them as described by mulesoft --> 'add maven dependency' --> 'install' --> select the local File and change the version to the correct number. All red crosses became green checkmarks.) and entered my SAP server credentials. When I try the "Test Connection" button I get an error message:
The confusing part of this is, I can run the application and it deploys without a problem
I already downloaded and unzipped a 'new' anypoint studio, I tried multiple versions of JDK (1.8u201 [this one works without problems for my colleague], 1.8u241 and OpenJDK 8 LTS), I restarted my pc every time I changed my JDK, I tried to add the native JCo Library locally to the build path (checkmark becomes also green, but still the same error message + a lot of 'Building worksapce' errors) and tried to add all libraries to the local build path.
What could I do to get rid of this error message?
Ok. I found the solution to my problem.
I did everything in a correct way, but I extracted Anypoint Studio in my downloads folder and didn't change anything of the resulting path. So the path was very long and in combination with the libraries the path became too long and they could not be initialized.
So if you get this error try to move the Anypoint Studio folder/Anypoint Studio worksapce/folder where you store the libraries to your root folder (or at least try to keep the path short by changing the folder names).
I have some broken depencencies in a vb.net desktop app setup project and I have been unable to solve the problem. I wonder if I can do as follows:
Remove the setup project from the solution and delete it in windows explorer
Copy the setup project folder from my last backup of the solution files
Add the backed up folder to my solution
Are there any pitfalls to this method so that I should rather create the setup project again from scratch?
Okay I have created my project in Visual Studio 2012 express edition. I have used ClickOnce Application deployment to create a setup file. Everything works absolutely fine when i run the project in my computer. But when i install the same project in another computer database connections are not working saying path is not correct. I understand that the path given to connect to the database is of my system. Now that is my problem and what should i do to make the database stuff to work in other systems as well? Please help me as this would make my project complete!
Thanks in advance.
Generally the application would be deployed with an app/web.config. Or another configuration file. Your code then reads the connection string out of this file to find the database.
On deployment, you can change the config file after deployment, this can be done manually, or in IIS if its a web config file, not sure on automatic editing with click once deployments; but a config file or setting of some kind would be key.
I made a TFS custom build definition, in which, among other things, the projects sources are zipped in a delivery directory.
I'd also like to download the latest version of the documentation from the TFS project sharepoint documents collection.
As the DownloadFile seems to be version control centric, I tried to use an InvokeProcess activity, coupled with a wget call, but I'm facing authentication issues.
Am I missing a dedicated activity which may solve this issue?
I ended up giving access to the Sharepoint website to the account running the build service, and putting this account credential in the wget script.
Not a very good solution, but a working one nevertheless.
I have various IIS hosted service hosts with simple svc files etc. What I want to do is to be able to create deployment packages from our test server using IIS Export Package in a way that parameters may be saved and picked up at Export time so that the Export is repeatable and automatable. I.e. the Export will always use the necessary Manifest extensions such as XmlFile etc.
The web sites exist in the solutions and are then picked up using a Web Deployment project in each solution so that config substitutions are done etc.
We are currently on VS 2008 SP1 so do not have direct access to VS 2010
The first issue I have with MsBuild (running in TeamCity) is how to build the IIS web site (with target=Package) when there is no project file? In this way maybe I can avoid the Web Deployment projects (I use them for various configurations but don't want to do it this way for deploying to Production but rather export from our fully tested staging into a package file to be imported onto a production server).
Secondly, I want to avoid having to configure the Export in IIS 7 each time I run it. I want it simply to pick up the correct set of extensions to use and create the necessary parameters for me. Is this done from a Manifest file? I can see how to use the parameters.xml but I am unclear whether I need to use a manifest.xml (created by hand) and how to link it in. The idea is that a tester/deployment person should be able to do the Export simply without having to enable all of the extensions that are required
Any help or guidance will be greatly appreciated.
Ok, in the meantime I got it figured out.
I ended up using the document at Package an Application for the Windows Web Application Gallery which gave me the means by which I could extend our automated build in TeamCity to create the "repeatable" export packages.
In short I will use the current Web Deployment Projects to create the deployment artefacts and then in MsBuild combine them with the pre-prepared manifest.xml and parameters.xml files into Build artefacts folder and zip them up into a package. From there the task will be to Import the package into IIS Deploy in the target environment.
The parameters.xml file will be used to set the HostName for wcf clients and services, connection strings, app settings etc.
This turned out to be the best solutuion bcause I can put it into our automated build.