Hi, all. We are trying to migrate our SOAP applications from Tomcat-axis2 to Carbon(WSAS). Moreover, We are trying to put ESB as front end for the scalability and load-balancing.
However, it is not economical to prepare(purchase) another physical server for ESB, so I want to test an structure as such. Primary Server :ESB+WSAS Secondary Server:WSAS Then, how should I configure ESB and WSAS to operate them on the same machine(at Primary Server)? I have 3 ideas below. 1)Operate WSAS on Virtual Server(VMWare) Clearly it is possible and is possible and better in availability, its overhead will not be little. 2)Operate WSAS on same machine but another directory and process. In this case, WSAS and ESB are installed into different directories. It is possible by changing the ports of management console, axis2 and so on, but carbon-core and axis2 will be doubly started. 3)Integrate WSAS and ESB on same process It seems not impossible to deploy ESB on WSAS when referring to here. <http://evanthika.blogspot.com/2009/02/deploying-wso2-esb-20-on-apache-tomcat.html> And the opposite might be also. I think it is more natural to put WSAS on ESB, since ESB comes to the front end. But is this possible by editing the setting xmls and copying libs and jars? (I have compared both dependencies.html, and I have felt it would be very difficult for me, if not impossible. ) Moreover, when assuming it is possible (...or not impossible) How does WSO2 Management Console become? If management GUI is not available, the advantage of Carbon will be reduced by half for us. Do general users adopt 1) or 2) ? Then, it might be a foolish question, I'm sorry. Any suggestions and comments are appriciated. ---- Takahiro OGAWA http://www.brainsellers.com/ _______________________________________________ Esb-java-user mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
