Is there any authoritative documentation available for data found under the Registry UI menu (for example as found in WSO2 ESB admin screens)?
I have seen snippets of information about this registry, for example:
The configuration registry contains product specific configuration
that can be shared across multiple instances of the same product (a
cluster of ESB nodes for example).
Source: link
To start with, I have a few questions:
What is the difference between this registry and the WSO2 Governance Registry?
What are the typical use cases for a WSO2 esb admin user for interacting with this Registry?
What are the typical use cases for a WSO2 esb developer for interacting with this Registry?
Is there a description of all the meta data stored in this registry?
In All WSO2 products there is an internal registry which is used to store resources. WSo2 Governance Registry uses the same core features + some more feature that gives complete Governance scenario. If you need you can mount to an external WSo2 Governance Registry without using the internal registry you referred.You can find more details here.
Related
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 have added wso2 governance registry on wso2 BPS 3 as a feature from http://dist.wso2.org/p2/carbon/releases/turing/
and restarted.
When tried to add wsdl from file it giving error:
org.wso2.carbon.governance.api.exception.GovernanceException: Attribute Search Service not Found.
I am trying to use BPS, GREG as a single component to reduce servers in my project. After GREG added as a feature it adding ".wsdl" file at "_/system/governance" and it is not forming endpoints,services as GREG normally do.
Is there any way to get out of this problem.
Thank's in advance....
The reason for this is missing some of the features which needed in ordered to work governance features. I think best option is using Governance Registry separately and mount the registry of it to BPS. By doing this you can add services from Governance Registry and use them in BPS. You can follow this document for more information on registry mounting.
I know I can access the WSO2 Governance Registry programmatically using the API. Is it also possible to access and upload/modify information on another (non GREG) servers'registry and how?
Is the approach the same? Is it possible to upload hive scripts for example on BAM programically?
Accessing embedded registry from a 'non GREG' WSO2 product using the registry API, is described here [1] in WSO2 Application Server documentation page.
[1] http://docs.wso2.org/display/AS520/Basic+Registry+API+Knowledge
Thanks,
Isuruwan
I am planning to implement enterprise application using wso2. I have following list of functions in my application and I have already chosen wso2 products for them.
Dynamic Business Process - WSO2-BPS 3.0.1
Dynamic Rule -- WSO2-BRS 2.0
Integration with LDAP, Sharepoint -- WSO2-IS 4.0
SOAP & REST Services -- WSO2-AS 5.0.1
My concerns are:
1) How can I share resources (configuration files, registries, etc) between products?
2) If I create Tenant in IS then How it will be available to other carbon products. can I use same tenant in other carbon products?
3) Can I externalize storage of Tenants?
4) Single sign on (logged in one product can also access other products)
You can simply achieve this via our stratos Which will provide you to access to tenants from one product to another using centralised user store and you can use the Single sign on with Stratos which is by default available within products. You can play around with stratos from this.
If you download the local setup of stratos which will have all the WSO2 products as already pre-configured to run them in your private cloud. You can refer the README in the local setup pack for more information to run the setup.
The release 4.5.3 differs from the 4.5.1 in the sense that in the master-datasources.xml appears a new datasource for the WSO2AM_DB
What does this means?
How the two product relate to each other?
If I have a registry host and, API host and a MySQL host how can I have a shared registry?
As for what I configured before API manager was dependent from registry and BAM so I needed to have the DB for the registry and BAM (so install registry than BAM than API).
How do the new datasource change this dependancy path does Registry also be dependant on the API manager, but who creates the DB first?
Thanks
Luca
This does not mean Governance Registry is dependent on Api Manager. This is a datasource defined for API manager to use if available to store it is runtime data. You can use the same WSO2_CARBON_DB if you need but then you need to do some configurations. So this is purely to store API related run-time data additionally to Carbon database. (JNDI lookup for this datasource happens from API manager).
We configured WSO2_CARBON_DB datasource to point to our organization's Oracle database. GReg distribution includes specific scripts required to setup the data model.
In case we need to point WSO2AM_DB datasource to the same Oracle DB, we could not find any scripts or documentation for that.