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
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 have WSO2 EI application which has a lot of datasources and all of them are exposed as dataservices. Also, I have a lot of users that use this application. Now I want to migrate from local H2 database to MySQL cluster. I need to upload all my configurations about datasources, dataservices and users to this new database.
When I made search for database files in my WSO2 EI folder I have found a lot of database files and some of them have same name.
What kind of .db files I should copy in my WSO2 EI folder in order to properly migrate to new database?
Have a look at [1] which explains on upgrading efforts of EI.
[1] https://docs.wso2.com/display/EI610/Upgrading+from+WSO2+EI+6.0.0#UpgradingfromWSO2EI6.0.0-Upgradingthedatabases
Based on your question, I understand you want to upgrade to an industry standard RDBMS like MySQL instead of using the embedded database H2, that is packaged along with WSO2 products.
All WSO2 products have the SQL scripts for different RDBMS shipped along with the product, that can be found under dbscripts directory inside the installation folder. We can use the relevant .sql file for creating the DB schema. Also there is no need to manually copy the .db files to migrate to a new DB. WSO2 setup as specified in the below links, will handle that implicitly.
Refer the following link, for detailed steps on the migration activities.
https://docs.wso2.com/display/ADMIN44x/Working+with+Databases
https://docs.wso2.com/display/ESB490/Remote+Instance+and+Mount+Configuration+Details
https://docs.wso2.com/display/Governance520/Remote+Instance+and+Mount+Configuration+Details
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
I follow the guide Governance Partition in a Remote Registry found in WSO2 Documentaton. It seems to work fine but I am facing a strange problem. Let me explain my setup first.
Governance registry instalation
Installed GREG 4.5.3
Set the offset to 1 in order to GREG console mgmt runs on port 9444 (carbon.xml)
Create mysql database "wso2greg_reg" (for local/config/governance registry)
Updated datasource WSO2_CARBON_DB to point to wso2greg_reg database (master-datasources.xml)
Enabled clustering (axis2.xml)
Run GREG server with -Dsetup option in order to create all tables
Enterprise Service Bus instalation
Installed ESB 4.6.0
Set the offset to 2 in order to ESB console mgmt runs on port 9445 (carbon.xml)
Create mysql database "wso2esb_reg" (for local/config registry)
Updated datasource WSO2_CARBON_DB to point to wso2esb_reg database (master-datasources.xml)
Added datasource WSO2_GREG_DB to point to wso2greg_reg database (master-datasources.xml)
Enabled clustering (axis2.xml)
Set registry.xml to mount governance registry using wso2greg_reg database
Run ESB server with -Dsetup option in order to create all tables
My problem is happening when I start the two servers, dependening on which was the first server started I have diferent problems on the console managmenet of the secondly started server.
First case:
I start GREG first and ESB in second. When navigating to ESB Console MGMT, I am unable to add a new Pass Through Proxy, the respetive form is not showing and exceptions are logged to the ESB logs (see logs).
Second case:
I start ESB first and GREG in second. When navigating to GREG Console MGMT, the metadata menu is empty and exceptions are loged to the GREG logs (see logs)
Can someone point me to what I am doing wrong?
You need to create only one mysql database. It is this database that is used in the master-datasources.xml config for both G-Reg and ESB instances. What happens is, the mysql database is used as the central database.
Pls try this out and check if you still encounter the issues mentioned.
Cheers,
Gillian