关于 WSO2 API Manager 数据源 [英] About WSO2 API Manager data sources
问题描述
我现在正在执行 WSO2 API 管理器 + 分析 2.0 POC.当我将数据源从 H2 更改为 Oracle 时,在 wso2am-2.0.1-SNAPSHOT 中,有 2 个数据源配置文件:master-datasources.xml &metrics-datasources.xml,根据 安装和配置数据库,应该有 WSO2AM_DB、WSO2UM_DB 和 WSO2REG_DB 数据源配置,但我只找到 WSO2_CARBON_DB &WSO2AM_DB,所以我的问题是
I'm performing WSO2 API manager + Analytics 2.0 POC now. When i change datasource from H2 to Oracle, in wso2am-2.0.1-SNAPSHOT, there are 2 data source config files: master-datasources.xml & metrics-datasources.xml, according Installing and configuring the databases, there should be WSO2AM_DB, WSO2UM_DB and the WSO2REG_DB datasource configurations, but i just find WSO2_CARBON_DB & WSO2AM_DB, so my questions are
- 是 WSO2_CARBON_DB = WSO2UM_DB + WSO2REG_DB?
- 对于WSO2_METRICS_DB,根据启用指标和存储类型,如果我们启用JDBC存储,我们可以将所有组件指标信息存储在一个共享数据库中还是每个组件需要一个数据库(本地)?
- WSO2_MB_STORE_DB 有什么用?从脚本来看,它用于消息存储和安第斯山脉上下文存储.我们可以继续在生产中使用 H2 吗?集群环境?
- Is WSO2_CARBON_DB = WSO2UM_DB + WSO2REG_DB?
- for WSO2_METRICS_DB, according Enabling Metrics and Storage Types, if we enable JDBC storage, can we store all components metrics information in one shared db or it needs one db per component(local)?
- What's WSO2_MB_STORE_DB used for? from the scripts, it's for Message Store and Andes Context Store. Can we keep to use H2 in prod. cluster env.?
当我配置 wso2am-analytics-2.0.0-SNAPSHOT 时,我有以下问题:
When i config wso2am-analytics-2.0.0-SNAPSHOT, i have below questions:
- 我们可以共享 APIMGRT 相关组件和分析的 WSO2_CARBON_DB 设置吗?还是不分享更好?
- 对于WSO2AM_STATS_DB,分析是否负责汇总和写入,APIMGRT 负责读取?哪些 APIMGRT 组件需要读取它?
- 对于分析相关的商店,它支持 RDBMS、Cassandra、HBase,但不支持 mongodb,对吗?
- 对于GEO_LOCATION_DATA,这是做什么用的?我们可以只在生产中使用 H2 吗?环境?
- Can we share WSO2_CARBON_DB setting for both APIMGRT related components and analytics? or it's better to not share?
- For WSO2AM_STATS_DB, is analytics resposible to aggregate and write to it, APIMGRT responsible to read? Which APIMGRT components need to read it?
- For analytics related store, it supports RDBMS, Cassandra, HBase, but it does not support mongodb, right?
- for GEO_LOCATION_DATA, What's this used for? Can we just use H2 in prod. env.?
推荐答案
APIM:
1) 在默认包中,是的.但是在生产环境中,建议将它们分开为 WSO2_CARBON_DB、WSO2UM_DB 和 WSO2REG_DB(请注意您也需要 WSO2_CARBON_DB,用于存储本地数据.这可以是一个 h2 数据库)
1) In default pack, yes. But in a production environment, it is recommended to separate them as WSO2_CARBON_DB, WSO2UM_DB and WSO2REG_DB (Please note you need WSO2_CARBON_DB too, to store local data. And this can be an h2 database)
2) 你可以有一个共享数据库
2) You can have a shared DB
3) 仅当您使用 高级限制.用于此的表由 APIM 本身创建.所以你不需要在上面运行任何脚本.
3) WSO2_MB_STORE_DB is required only if you use Advanced Throttling. Tables for this are created by APIM itself. So you don't need to run any scripts on it.
APIM 分析:
1) 您可以共享 WSO2UM_DB 和 WSO2REG_DB.但不要共享(本地)WSO2_CARBON_DB.
1) You can share WSO2UM_DB and WSO2REG_DB. But don't share (local) WSO2_CARBON_DB.
2) 商店和出版商
3) 参见 WSO2 DAS with MongoDB
4) GEO_LOCATION_DATA 用于基于地理位置的统计数据.不推荐 H2.
4) GEO_LOCATION_DATA is used for Geolocation Based Statistics. H2 is not recommended.
这篇关于关于 WSO2 API Manager 数据源的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!