I'm going to develop couple of Mule applications that will use SAP connector so I'd like to keep SAP libraries (sapjco3.jar, sapidoc3.jar and native sapjco3.dll) in the Mule domain however I'm struggling with how to export sapjco3.dll.
I'm not using MVN and I tried to place sapjco3.dll to the project /lib folder, also to src/main/domain/lib and src/main/resources/lib folder ... but it seems that Mule Eclipse plugin always ignores it when exporting the domain as "Anypoint Studio Project to Mule Deployable Archive".
Are there any best practises how to organise this in the domain ?
I am not sure how to organize these in the project when your exporting from Studio. But instead of keeping these jar files as part of the project, you can keep in the mule standalone server in the below locations
--> $MULE_HOME/lib/user
--> $MULE_HOME/lib/native
for further details, refer the mule documentation
https://docs.mulesoft.com/mule-user-guide/v/3.7/mulesoft-enterprise-java-connector-for-sap-reference
Related
Installed Anypoint studio configured it to use Mule 3.4, imported my flows and now when I select "run as" to test them I get an error saying I do not have a licence for data mapper even though I do not use the data mapper in the flows that I have imported from mule studio.
Can I disable or remove the data mapper component from Anypoint so I can run my imported flows (which where developed and work in Mule studio)?
You probably still have a reference to EE artifacts in the pom.xml. Or to EE schemas in the Mule XML configs. Or both...
Make sure to only refer to CE artifacts and schemes only.
I have installed Mobile first Server (not the development server that comes with eclipse)
I have created a project in eclipse with 2 applications. Then i deployed the war file using the configuration tool. And finally i uploaded the wlapp files using the worklight web console. Everything is ok but i have one question:
Should I deploy a different war each time i create an application in a different project in eclipse? Should i create all apps under the same project, so no other war should be deployed? How does this work?
Yes you can deploy different war files so MobileFirst runtimes in the same application server. The context root of course must be different for each war.
In the MobileFirst console you will see the different runtimes deployed in your application server. Then for deploying the applications/adapters you have to select one runtime.
If you put applications under a project in Eclipse you could deploy the applications under another project but only in some circumstances (several projects using the same security tests for example or no security defined). But it is better to deploy all the applications on the project where they are created. Because for example you could reference in your application security tests or push notifications that don't exist in the runtime where they are deployed.
I have a Zip file exported by Mule Studio. Need to deploy it on Mule Server using Jenkin Jobs. Please provide the Steps.
I am having mule enterprise standalone 3.3.2
Mule apps deployment apps is just as simple as most the other container ones. Just copy the zip to an APP folder. If you have an scp tool, there you go.
Of course this only applies to the community edition, enterprise edition is bundled with more sophisticated mechanisms of monitoring/management.
Agree with Victor here, however, you can use the MMC agent REST APIs also to deploy the apps directly to the mule platform which will also add the build into the repository.
You just need to look for an option how to place the zip in the $MULE_HOME/apps.
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.
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.