Mule 骡子
我已经从Officel网站下载了mule standalone 3.6.1,并将其解压,然后从我发布mule的bin中解压 控制台:Mule 骡子,mule,esb,Mule,Esb,我已经从Officel网站下载了mule standalone 3.6.1,并将其解压,然后从我发布mule的bin中解压 控制台: MULE_HOME is set to C:\mule-standalone-3.6.1 Running in console/foreground mode by default, use Ctrl-C to exit... --> Wrapper Started as Console Launching a JVM... Starting the Mul
MULE_HOME is set to C:\mule-standalone-3.6.1
Running in console/foreground mode by default, use Ctrl-C to exit...
--> Wrapper Started as Console
Launching a JVM...
Starting the Mule Container...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
WARNING - Unable to load the Wrapper's native library because none of the
following files:
wrapper-windows-x86-64.dll
wrapper.dll
could be located on the following java.library.path:
C:\mule-standalone-3.6.1\bin\%LD_LIBRARY_PATH%
C:\mule-standalone-3.6.1\lib\boot
Please see the documentation for the wrapper.java.library.path
configuration property.
System signals will not be handled correctly.
INFO 2015-03-29 23:34:32,390 [WrapperListener_start_runner] org.mule.module.lau
ncher.MuleContainer:
**********************************************************************
* Mule ESB and Integration Platform *
* Version: 3.6.1 Build: b795785f *
* MuleSoft, Inc. *
* For more information go to http://www.mulesoft.org *
* *
* Server started: 29/03/15 23:34 *
* JDK: 1.8.0_40 (mixed mode) *
* OS: Windows 7 - Service Pack 1 (6.1, amd64) *
* Host: Rajeun-PC (192.168.1.186) *
**********************************************************************
INFO 2015-03-29 23:34:32,393 [WrapperListener_start_runner] org.mule.module.lau
ncher.coreextension.DefaultMuleCoreExtensionManager: Initializing core extension
s
INFO 2015-03-29 23:34:32,394 [WrapperListener_start_runner] org.mule.module.lau
ncher.coreextension.DefaultMuleCoreExtensionManager: Starting core extensions
INFO 2015-03-29 23:34:32,411 [WrapperListener_start_runner] org.mule.module.lau
ncher.DefaultArchiveDeployer: ================== New Exploded Artifact: default
INFO 2015-03-29 23:34:32,424 [WrapperListener_start_runner] org.mule.module.lau
ncher.MuleSharedDomainClassLoader: Using domain dir C:\mule-standalone-3.6.1\dom
ains\default for domain default
INFO 2015-03-29 23:34:32,533 [WrapperListener_start_runner] org.mule.module.lau
ncher.MuleDeploymentService:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Started domain 'default' +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INFO 2015-03-29 23:34:32,540 [WrapperListener_start_runner] org.mule.module.lau
ncher.DefaultArchiveDeployer: ================== New Exploded Artifact: default
INFO 2015-03-29 23:34:32,560 [WrapperListener_start_runner] org.mule.module.lau
ncher.application.DefaultMuleApplication:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ New app 'default' +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INFO 2015-03-29 23:34:37,266 [WrapperListener_start_runner] org.mule.module.lau
ncher.MuleDeploymentService:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Started app 'default' +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INFO 2015-03-29 23:34:37,270 [WrapperListener_start_runner] org.mule.module.lau
ncher.DeploymentDirectoryWatcher:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Mule is up and kicking (every 5000ms) +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INFO 2015-03-29 23:34:37,356 [WrapperListener_start_runner] org.mule.module.lau
ncher.StartupSummaryDeploymentListener:
**********************************************************************
* - - + DOMAIN + - - * - - + STATUS + - - *
**********************************************************************
* default * DEPLOYED *
**********************************************************************
********************************************************************************
***********************
* - - + APPLICATION + - - * - - + DOMAIN + - -
* - - + STATUS + - - *
********************************************************************************
***********************
* default * default
* DEPLOYED *
********************************************************************************
***********************
问题:
- 导航到包含Mule ESB Standalone副本的文件夹,然后将应用程序的zip文件粘贴到apps文件夹中。
- Mule每5秒(每5000毫秒)轮询一次应用程序文件夹;它会拾取您复制到“应用程序”文件夹的应用程序,然后自动提取并部署它。在命令行中,Mule通知您它已经部署了应用程序
2-是
3-使用应用程序的入站端点
4-在调试模式下从AnyPointStudio运行应用程序,回答第三个问题:-“然后我如何访问和测试我刚安装的服务器上部署的应用程序。” 您可以使用与在Mule/Anypoint studio中相同的方法测试应用程序。
例如,您的应用程序包含一个http入站端点。。。因此,要测试应用程序,您需要在浏览器中粘贴url路径并点击它。。一旦您这样做了,您就可以看到您的应用程序正在运行并产生您期望的结果。
这与在studio中运行和测试应用程序的方式相同 第4个问题的答案是,您最好在应用程序中使用log4j,并在流程的每个步骤中使用logger。
因此,每当流运行时,您都可以看到每个步骤都记录在独立服务器控制台中。
如果您想获得步骤的更多详细信息,请在调试模式下配置log4j 我想第一和第二个问题已经回答了