Deploying mule applications
- 1. 1l All contents Copyright © 2015, MuleSoft Inc. Deploying Mule Applications
- 2. Deploying Mule Applications: o During development, applications are deployed on an embedded Mule ESB runtime in Anypoint Studio. o For testing, QA, and production environment, applications can be deployed to: On-premise Mule Server Runtime: As a standalone application to a Mule ESB. As a WAR file with an embedded Mule instance to an application server. Mule ESB Runtime Features: o Easy to Install & can run multiple applications. o Uses a Java Service Wrapper which controls the JVM from our operating system and starts Mule. o Mule Management Console (MMC) for controlling applications: Deploying and un-deploying applications. Starting and stopping servers. Managing and monitoring applications. Deploying Mule Applications
- 3. Application Properties: o Application Properties are used as an alternative for hardcoding properties, credentials, resources etc. o These are injected into application at runtime. o These provide an easier way to manage credentials, changes and settings. o These can be encrypted. o These are defined in .properties files: Separate property files can host values specified to an environment: app-dev.properties. app-prod.properties. Application Properties
- 4. Existing Property Files: o Mule Projects contain two property files by default in src/main/app folder: mule-app.properties. mule-app properties is initially blank and is for custom application properties. For Mule ESB standalone, it must be passed to Mule Runtime when it starts. Mule-deploy.properties. It is a deployment descriptor which describes how the application should be deployed. Existing Property Files
- 5. Deploying Application to Mule ESB: o In Anypoint Studio, create a Mule Deployable Archive. o Install Mule ESB. o Modify wrapper.conf (to pass an environment variables) o Start Mule. o Start MMC. o Use MMC to deploy the application. Deploying Application to Mule ESB