In WSO2 API Manager 3.0.0, changing from embedded H2 Database to Mysql documentation state about changing of the following databases: WSO2_SHARED_DB, WSO2AM_DB, WSO2_MB_STORE_DB irrespective deployment option (Single Node or Active-Active). But it is required to change the WSO2_CARBON_DB default database H2 to MySql? If yes, then please direct to towards the steps required to change it to MySql from H2 in WSO2 API manager 3.0.0
Ref URL: https://apim.docs.wso2.com/en/latest/InstallAndSetup/SettingUpDatabases/ChangingDefaultDatabases/changing-to-mysql
When setting up the environment, you only need to move WSO2_SHARED_DB and WSO2AM_DB H2 databases to MySql. WSO2_CARBON_DB and MB_Store_DB can be kept as H2 database. You can refer [1] for configuring deployment.toml for Mysql.
[1] -
https://github.com/wso2/docker-apim/blob/master/docker-compose/apim-with-analytics/apim/config/repository/conf/deployment.toml#L19
Related
We are using default h2 database in wso2 identity server 5.10. we want to migrate h2 database to postgres data base with complete old data.
I did not find any link for migrating with data.
Can you please help on it.
I did not find any link for migrating with data.
WSO2 does not support migrating data between RDBMSs. You might have to find a third party tool for that.
Please Help!!!!!!!!Anyone please provide steps to change registry db from H2 to MySQL in WSO2
In Identity Server, 5.9.0 Registry data is stored in WSO2_SHARED_DB. by default this database is using embedded H2 database. You can change this by configuring deployment.toml file. Please follow the following documentation for instructions of changing it to a mysql database.
https://is.docs.wso2.com/en/5.9.0/setup/changing-to-mysql/
I'm using WSO2 EI 6.5.0 (latest release),
I'm wondering that Where can i find WSO2 database schema, stores all of things,
Those log files, written on Management console is saved in Database right ?
I am using Oracle DB (PL\SQL)..
I found oracle.sql from dbscripts folder - %E_HOME%,
How to connect WSO2's default database in PLSQL ?
Regards
By default wsoesb use h2 database. You can overwrite default database using oracle. There is documentation how to configure datasource, and there is, i am not sure something like carbon.xml where configure default datasource.
No, the logs are persisted in the files in ESB_HOME/repository/logs folder.
As #srimar mentioned, the default database is embedded H2. You can follow this doc to browse the embedded H2.
But WSO2 didn't recommend the embedded H2 database in the production
To configure the Oracle database you can follow this doc
I am trying to map a newly created local claim to the claims of a service providers.
Some notes about my WSO2 implementation:
I am using Postgres databases in AWS's Relational Database Service. I followed the steps here to set up my master, metrics, and bps databases: https://docs.wso2.com/display/ADMIN44x/Changing+to+PostgreSQL#ChangingtoPostgreSQL-ChangingthedefaultdatabaseChangingthedefaultWSO2_CARBON_DBdatasource
My steps to map the claim look like this:
Create a local claim
Attempt to add the newly created claim to a service provider
My issue is that the claim I created in step 1 doesn't appear in the dropdown in step 2. I have confirmed that the claim is being written to my master Postgres database under the idn_claim table. If it's in the idn_claim table, shouldn't it show in the dropdown when adding a claim?
The same steps have worked for me with the following setups:
Using the built-in H2 database (no config changes)
Using a LOCAL Postgres database that is setup using the same configuration files and seeding scripts as the scenario above.
I'm stumped about why everything works as expected using the H2 database or a Local Postgres database (with identical setup) but it doesn't work with a Postgres database in AWS.
A standard installation of Identity Server 5.1.0 creates beside the known WSO2CARBON_DB database two other h2 databases: "WSO2METRICS_DB" and "jpadb".
Unfortunately we couldn't find any documentation on this databases. Could someone please provide us with an pointer to the docs or give us a hint how to answer the following questions:
Are these two databases required? For what are they used?
If you configure WSO2 IS against a MySQL database, do I need to create these databases in MySQL as well?
Do I need to backup these databases?
In case of an upgrade of IS 5.0.0 to 5.1.0. How do I handle the two databases?
If you are migrating WSO2 Identity Server 5.0.0 to 5.1.0, you can refer the official documentation [1].
Metrics is a new feature added to Identity Server with 5.1.0 version. It has a separate database and the datasource is defined in repository/conf/datasources/metrics-datasources.xml file. The metrics feature is by default enabled in the config file repository/conf/metrics.xml file. With this feature, you can view JVM metrics by going to Configure -> Metrics -> JVM Metrics feature in the IS management console. All the metrics related data is stored in this new database.
For the metrics database, the database script is located in IS_HOME/dbscripts/metrics directory and there you can find the tables related to this feature which are created in the metrics database.
If you don't wish to use this feature, you may disable it from the metrics.xml file in conf.
The other jpadb is for the workflow feature introduced with IS 5.1.0. You can find documentation in [2]. So in a migration, these should be created separately and you don't need backup as these are new databases.
For your existing database in IS 5.0.0, there are some schema changes for existing tables. You can find DB migration scripts in [1].
[1] https://docs.wso2.com/display/IS510/Upgrading+from+a+Previous+Release#UpgradingfromaPreviousRelease-Upgradingthedatabase
[2] http://wso2.com/library/articles/2015/09/article-wso2-identity-server-5.1.0-workflow-feature-and-use-cases/
This jpabd is used by human task feature to store the task related information.
Identity server ships BPEL and HumanTask features and jpabd is part of that.
WSO2_METRICS_DB is used for WSO2 Carbon Metrics. https://docs.wso2.com/display/ML100/JVM+Metrics