我们正在与WSO2业务活动监视器2.5.0(WSO2 BAM)一起评估WSO2 API Manager 1.8.0(WSO2 AM).从我们的支持合作伙伴Yenlo,我们得到WSO2建议使用WSO2 BAM 3.0进行新安装,因为从BAM 2.5.0到BAM 3.0.0的变化是巨大的.
BAM 3.0尚未发布(请参阅JIRA中的发布计划).但里程碑4应该可用.
但我唯一能找到的是BAM的里程碑3和DAS(Data Analytics Server)的里程碑4,如本电子邮件中所述.此外,DAS的更改日志指向BAM的JIRA问题.
DAS是BAM的新名称吗?
我们有一些服务(用WSO2 API Manager公开).我们想为消费者进行计费.
遗憾的是,我们的结算规则需要一些仅在已实施服务中可用的详细信息.我可以看到两种方法来处理它:
我的问题是,如果有一种方法如何在响应(传输层中的标头)中向API管理器提供一些额外的服务元数据,以及它是否可以通过API管理器传递给BAM进行监控,计费分析等...
我在具有CEP和APIM实例的服务器中运行BAM 2.4.0.我也用+2端口偏移运行它.但是当我启动BAM时,控制台打印:
[2014-03-06 16:34:04,126] ERROR {me.prettyprint.cassandra.connection.HConnectionManager} - Could not start connection pool for host localhost(127.0.0.1):9160
[2014-03-06 16:34:04,128] WARN {me.prettyprint.cassandra.connection.CassandraHostRetryService} - Downed localhost(127.0.0.1):9160 host still appears to be down: Unable to open transport to localhost(127.0.0.1):9160 , java.net.ConnectException: Connection refused
[2014-03-06 16:34:04,141] ERROR {org.wso2.carbon.bam.notification.task.internal.NotificationDispatchComponent} - All host pools marked down. Retry burden pushed out to client.
me.prettyprint.hector.api.exceptions.HectorException: All host pools marked down. Retry burden pushed out to client.
at me.prettyprint.cassandra.connection.HConnectionManager.getClientFromLBPolicy(HConnectionManager.java:393)
at me.prettyprint.cassandra.connection.HConnectionManager.operateWithFailover(HConnectionManager.java:249)
at me.prettyprint.cassandra.service.ThriftCluster.addKeyspace(ThriftCluster.java:168)
at org.wso2.carbon.bam.datasource.utils.DataSourceUtils.createKeyspaceIfNotExist(DataSourceUtils.java:80)
at org.wso2.carbon.bam.datasource.utils.DataSourceUtils.getClusterKeyspaceFromRDBMSConfig(DataSourceUtils.java:92)
at org.wso2.carbon.bam.datasource.utils.DataSourceUtils.getClusterKeyspaceFromRDBMSDataSource(DataSourceUtils.java:96)
at org.wso2.carbon.bam.notification.task.internal.NotificationDispatchComponent.initRecordStore(NotificationDispatchComponent.java:72) …Run Code Online (Sandbox Code Playgroud)