I am currently using WSO2 IS version 4.0.0, trying to add a new partition to default Embedded Ldap server (apacheds) using apache directory studio v2.0. So far not successful in creating new partition. Appreciate if someone can help me with right steps?
I couldn't manage to create a new partition, but however I renamed existing partition by following the steps mentioned here ...
How to change primary LDAP domain of WSO2 IS 4.5.0
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.
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 access the registry of WSO2 BPS and WSO2 ESB from Java in order to automatically fill the registry based on the data I provide.
I have already found a number of resources about the required Java code and dependencies, this being the most helpful one: [WSO2 Governance Registry]Using WSRegistryServiceClient. However, the approach described in these resources depends on the WSRegistryService service. This service is included in Governance Registry by default, but not in the other WSO2 products. I have verified that my code works for the Governance Registry. For any other WSO2 product on my machine, I get this error:
The service cannot be found for the endpoint reference (EPR) https://localhost:9445/services/WSRegistryService
I found an old thread suggesting that it should be possible to install the WSRegistryService on other WSO2 products as well, but I have not been able to find out how to do so. I can't seem to find it within the features I can install from the web console of the products. I have also tried manually copying the relevant jar from the plugins directory of Governance Registry into the plugins directory of other products, but that doesn't seem to be sufficient.
Note that my application for filling the registry will not be running on the carbon server whose registry I want to access, so using CarbonContext.getThreadLocalCarbonContext() (an approach I found in some other articles) is not an option.
I think your referring to how to install features to WSO2 products,
Please find this documentation.
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 am new to WSO2 ESB and then I've started by following the initial steps described on WSO2 ESB product documentaion page. After the first samples succesfully run, I've got myself stuck trying to exercise the Database mechanism.
According to WSO2 ESB documentation - http://docs.wso2.org/wiki/display/ESB460/Databases - Admin Console feature must be installed to add a new database. So, I've tried to add that feature to my ESB installation by creating several repositories (http://dist.wso2.org/p2/carbon/releases/3.0.0 up to 4.0.5 and even the local version of 4.0.5 p2-repo.zip) , but after all I had no success in finding the Admin Console Feature, so no Database option for me. Even after adding the Datasources Feature, the Database option did not show up.
What am I missing here ? Is the documentation outdated ?
Thanks.
Otmar, That particular database provisioning feature that you are referring to as admin console feature was renamed to "rss manager". Please lookup for the feature with that name in the p2 feature repository.