...
Monitorera mule.log för att se loggar
Kodblock tail -f /usr/local/mule-standalone-3.7.0/logs/mule.log $
- Ta bort tidigare version av samma applikation om det finns en sådan, tex olika releasekandidater (RC).
I /usr/local/mule-standalone-3.7.0/apps, radera vp-services-[version]-anchor.txt för att trigga så att Mule tar bort applikationen under kontrollerade former.
Kodblock rm /usr/local/mule-standalone-3.7.0/apps/vp-services-3.1.3-anchor.txt
Säkerställ att applikationen tagits av Mule genom katalogen vp-services-[version] inte längre finns kvar.
Kodblock ll -a /usr/local/mule-standalone-3.7.0/apps
- Driftsätt applikation (zip)
Kopiera den nedladdade zip-filen, vp-services-[version].zip, till /usr/local/mule-standalone-3.7.0/apps. Mule packar upp applikationen till en katalog vp-services-[version].
Kodblock cp vp-services-3.1.3.zip /usr/local/mule-standalone-3.7.0/apps
En fil med namn vp-services-[version]-anchor.txt (vp-services-3.1.3.zip) skapas vid en lyckad driftsättning.
Kodblock ll -a /usr/local/mule-standalone-3.7.0/apps -rw-r--r-- 1 mule mule 75 26 okt 21.59 vp-services-23.21.93-anchor.txt drwxr-xr-x 5 mule mule 4096 15 okt 13.17 vp-services-23.21.93
- Verifiera i loggar hur releasen gick, /usr/local/mule-standalone-3.7.0/logs/mule-app-vp.log och /usr/local/mule-standalone-3.7.0/logs/mule.log
I /usr/local/mule-standalone-3.7.0/logs/mule.log ser man status på driftsättningen.
Kodblock ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + New app 'vp-services-3.1.3' + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ INFO 2013-08-28 08:50:27,837 [WrapperListener_start_runner] org.mule.module.launcher.MuleApplicationClassLoader: [vp-services-3.1.3] Loading the following jars: ============================= - - - ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Started app 'vp-services-3.1.3' + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Kodblock ********************************************************************** * - - + APPLICATION + - - * - - + STATUS + - - * ********************************************************************** * vp-services-3.1.3 * DEPLOYED * **********************************************************************
I /usr/local/mule-standalone-3.7.0/logs/mule-app-vp.log ser man följande vid en lyckad start.
Kodblock ********************************************************************** * Application: vp-services-3.1.3 * * OS encoding: UTF-8, Mule encoding: UTF-8 * * * * Agents Running: * * JMX Agent * * Wrapper Manager: Mule PID #20712, Wrapper PID #20705 * ********************************************************************** 2013-08-28 08:51:31,182 INFO org.mule.module.logging.DispatchingLogger - Start force a reset of VagvalAgent... 2013-08-28 08:51:31,186 INFO org.mule.module.logging.DispatchingLogger - Initialize VagvalAgent TAK resources... 2013-08-28 08:51:31,187 INFO org.mule.module.logging.DispatchingLogger - Fetch all virtualizations from TAK... 2013-08-28 08:51:31,503 INFO org.mule.module.logging.DispatchingLogger - Fetch all permissions from TAK... 2013-08-28 08:51:31,801 INFO org.mule.module.logging.DispatchingLogger - Save virtualizations and permissions to local TAK copy: /home/mule/.tk.devtest.localCache 2013-08-28 08:51:31,932 INFO org.mule.module.logging.DispatchingLogger - Init VagvalAgent loaded number of permissions: 161 2013-08-28 08:51:31,934 INFO org.mule.module.logging.DispatchingLogger - Init VagvalAgent loaded number of virtualizations: 116 2013-08-28 08:51:31,935 INFO org.mule.module.logging.DispatchingLogger - Init VagvalAgent done 2013-08-28 08:51:31,936 INFO org.mule.module.logging.DispatchingLogger - Successfully force reset VagvalAgent
Om driftsättningen misslyckas skapas inte en vp-services-[version]-anchor.txt, applikationen startar inte och följande ses i /usr/local/mule-standalone-3.7.0/logs/mule.log
Kodblock ********************************************************************** * - - + APPLICATION + - - * - - + STATUS + - - * ********************************************************************** * vp-services-3.1.3 * FAILED * **********************************************************************
...