WSO2 Add BAM Profile in ESB

问题:

We're having troubles trying to add BAM Profiles to ESB following the manual:

http://docs.wso2.org/wiki/display/BAM201/Setting+up+BAM+Mediator#SettingupBAMMediator-ConfigureBAMServerProfilesandStreams

BAM 2.0.1 (latest version)

ESB 4.5.1 (latest version)

p2-repo from http://dist.wso2.org/p2/carbon/releases/p2-repo.zip (15-01-2013)

It works if you do it with both WSO2-servers in a single host, but it doesn't if ESB and BAM are running in separate hosts. No logs or traffic found outgoing or incoming through port 7611.

The BAM thrift port 7611 is open and listening in BAM host, and is reachable from ESB port.

Details follows:

# uname -a
Linux ESBHOST 2.6.32-220.el6.x86_64 #1 SMP Wed Nov 9 08:03:13 EST 2011 x86_64 x86_64 x86_64 GNU/Linux

# java -version
java version "1.7.0_11"
Java(TM) SE Runtime Environment (build 1.7.0_11-b21)
Java HotSpot(TM) 64-Bit Server VM (build 23.6-b04, mixed mode)

# /opt/esb_default/bin/wso2server.sh version
WSO2 Enterprise Service Bus v4.5.1
WSO2 Carbon Framework v4.0.2

# nc -zv BAMHOST 7611
Connection to BAMHOST 7611 port [tcp/*] succeeded!

Any clue how to find the problem or where to start to solve it? Thanks in advance

回答1:

Problem solved:

Even if you don't want to use secure connection, the port 7711 MUST be reachable and WILL BE USED. Also while 7611 is listening in ALL the IP addresses of the BAM server, 7711 is only listening in the configured management IP.

Since this two features are not documented (yet), it's worthy to mention here for other people that could face a similar issue. Thanks to WSO2 team for the support.

回答2:

Make sure you enter the BAM server's IP address when creating the BAM Server Profile in the UI. And also make sure you update BAM Server Profile information correctly in the ESB's mediator if you have changed some such information from BAM Server Profile UI. You have to manually update the mediation sequence after you have done it.