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.
Related
I am doing a POC to integrate camunda with oracle database. It works well with h2 database. To integrate with oracle, I have followed this user guide (https://docs.camunda.org/manual/7.17/user-guide/spring-boot-integration/configuration/). My application programmatically creates a datasource and transaction manager so i have no control over it. I tried to create a secondary transaction manager using above user guide and it fails due to two transaction manager bean found.
Is there a way to connect with the programmatically created datasource instead of providing a configuration.
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
We are doing a DB Upgradation for WSo2 Governance Registry upgradation from 4.5.3 to 4.6.0. The sql scripts available in the documentation for creating some db schema in staging database is having discrepancy like scripts for creating few tables are missing. Can anyone provide valid scripts for staging database as we are trying out with mySql/Oracle database?
The reference link I am following is shown as below:
https://docs.wso2.com/display/Governance460/Upgrading+from+the+Previous+Release
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
I have tried to implement shared registry between clustered environment ESB 4.6.0 using GREG 4.5.3 following the guidance provided in provided in the documentation.
When I use the h2 db for currentDBConfig and the mysql database for mounted registry, WSO2 workers displays the following error when Deployment Synchronizer is automatically invoked:
Error while updating artifacts in the file system from the registry {org.wso2.carbon.deployment.synchronizer.registry.RegistryBasedArtifactRepository}
org.wso2.carbon.registry.synchronization.SynchronizationException: message code: ERROR_IN_READING_STREAM_TO_CREATE_META_FILE
When pointing currentDBConfig to the mysql database, the deployment synchronizer works ok and replicates configuration as expected, but according to the documentation it is not good practice.
How does the Deployment Synchronizer utilize the registry to update artifacts?
I have noticed that the User database uses by default the h2 database. Should it not be re-pointed to the shared governance registry database instead?
Thanks. Guillaume