简体   繁体   English

通过Tooling Vs Management Console开发WsO2 ESB

[英]WsO2 ESB development thru Tooling Vs Management Console

Why does the management console provide features to develop a service or customize a component of WSO2 ESB? 为什么管理控制台提供用于开发服务或自定义WSO2 ESB组件的功能?

What's the purpose of one Vs other? 一个VS另一个的目的是什么?

Doesn't the development stops after handover of CAR files/artifacts to DevOps team? 在将CAR文件/工件移交给DevOps团队后,开发不会停止吗?

My understanding with Management Console is to deploy, manage(start-stop) & monitor ESB services/integration flows. 我对管理控制台的理解是部署,管理(启动-停止)和监视ESB服务/集成流程。

Is there an overlap on these two ? 这两个有重叠吗? The documentation itself provides two ways to do the same thing. 文档本身提供了两种执行同一操作的方法。 I mean why? 我的意思是为什么?

TIA, TIA,

--M --M

All these features are available in Management console for users to try out easily. 管理控制台中提供了所有这些功能,供用户轻松试用。 For example, when they want to see what are available feature etc, quickly. 例如,当他们想要快速查看可用功能等时。

When you're using ESB in real development, you should use toolings instead. 在实际开发中使用ESB时,应改用工具。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM