I have installed WSO2 AS, after I have installed GReg and ESB by Feature Install. It was OK.
But now I would like to know how to I have to configure GReg and ESB using same WSO2 Application Server.
For example, I would like to configure ESB and GReg following pattern #2 or pattern #3 of this blog post but considering that ESB and GReg were installed in same WSO2 AS instance.
Is that a correct escenary ? or I Have to install allways in separated AS ?
Regards!
Oscar
These patterns are used when you need to share registry spaces across multiple server instances. A common config registry space is used to share configuration details across multiple instances of the same product. A common governance registry space is used to share metadata across the multiple products in a platform.
In the setup you have described,since ESB and AS products are installed in the same server, there is no need for sharing the registry space.
Sharing the registry space would be required only if these products are run as separate server instances.
Is there any particular reason/requirement you have for the setup described?
Regards,
Gillian
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.
We use WSO2 Registry Governance 4.5.3 and ask ourselves how to get information introduced (Resources, Users, LifeCycle ...) from one version to another. I saw that check-in can help.
Is it able to work with different versions of WSO2 Greg and will it take information other than resources, it seems that not.
But then how to transfer automatically these other infos from one version to another ? Is it possible through an API and which ?
Thank you in advance for your response.
Jean-Pierre Indot
I tried migrating a datasource configuration (a basic text resource) from WSO2 GReg 4.1.1 to GReg 4.5.3 using the check-in client. The migration was successful.
But there is a possibility of this approach not being adequate for migrating more complex resources. (E.g.: Resources containing data structures)
Could you please share the nature of the resources you're trying to migrate, so that we can try to provide you with a more subjective solution.
After study WSO2 products, seems I got the following concepts, all of them are only my understanding, I don't know whether is correct or not, please advice:
All the products are running in Carbon which is a 'container' of the wso2 products, something like JSP like stuffs running in tomcat. am I right?
if No.1 is correct, so 'Enterprise Service Bus', 'Identity Server', 'Data Service Server', 'Governance Reistry' etc are all running in Carbon Server, actually I downloaded all the products, and I found they are all released with carbon together, which mean I can use command to start the management console directly, and each of them can running themselves, they have there own management console. right?
after I read Carbon user guide, it says 'all the products of wso2 are the components of Carbon', so I think 'Enterprise Service Bus', 'Identity Server', 'Data Service Server', 'Governance Reistry' can be put into one management console, which mean they can be integrated together, after I started Carbon server, all the features are running together?
I'm sorry ask such kind a stupid question, but after read many articles I still cant find out the structure between them, please advice, thanks in advance.
WSO2 middleware products come with a bunch of components. These are based on Java OSGi. So every product comes with a set of OSGi bundles (in OSGi terminology). Carbon is a core framework that's common to every product. This is again a bunch of OSGi components. Carbon core (which is also reffered to as just Carbon) contains a set of must have bundles. Logging, clustering, security etc... Carbon is a separate download also which you can run. Running carbon itself by its own is not very interesting unless you're doing something specific and you know what you're doing.
Now, coming back to the products .. each product have carbon core plus some more OSGi components. These additional components reflect product specific functionality. For example if you take the ESB, it's carbon core plus additional components that makes it an "ESB". Likewise for other products.
You can take the carbon server and install all these additional features. Feature installation is done via the same technology Eclipse is using to install plugins. Since everything is an OSGi bundle there has to be an OSGi container that all these run on. Carbon is running on top of Equinox OSGi container.
So Tomcat is also a separate OSGi bundle. You can install these components into any running carbon server and instantly add webapp hosting capability.
Yes. All WSO2 products are running inside WSO2 Carbon which is mainly a OSGi based framework.
Yes. A WSO2 Product (e.g., ESB) is a specialized Carbon framework. Management console is a part of Carbon where you can install external features to the product / uninstall existing features in the product to customize the product.
Yes theoretically. If the Carbon concept is correctly implemented in all the components of WSO2, they (ESB, IS, DSS as you said) should be installable in a single Carbon server without any problem using the WSO2 Feature Manager. But due to some dependency conflicts and version conflicts sometimes it may not be possible if you try to do it. But still you can resolve these OSGi conflicts in code level and make it possible to make them compatible, if you want.
Actually all the WSO2 products share the WSO2 components seamlessly among their products already. And in some instances we recommend to install multiple products in a single Carbon server. For example CEP feature is asked to be installed in BAM product when the user wants to use CEP as a realtime data processing solution with the BAM. For most other product combinations we have not yet tested well so the conflicts can occur. Thats why I said this theoretical.
We are evaluating multiple ESB products currently (Mule, Fuse and WSO2), and one of our key requirements is to easily migrate services between multiple environments. I can see how this can be done in WSO2 with g-reg for the most part, but am struggling to see how we would parametrise the endpoint uris and maintain them separately in each environment? (This seems fairly trivial in Mule and Fuse).
The preferred way is:
Create/save ALL endpoints as registry resource (either using management console or Developer Studio)
Since the endpoints are saved in the registry, now the ESB configuration is totally independent of the environment. (We can create a Carbon Application out of this, which is basically can be deployed in any environment)
So, if you need to move the configuration from dev->qa, you can use the same .car file created
I want to merge WSO2 ESB and Data Services Products to execute both of them
on one server.
Both of them are based on Carbon framework and consists of some OSGi bundles.
Is there a simple way to do this.
Best regards.
--Seyyed Jamal
Yes. You can install the ESB features in the DSS or vise versa. Feature installing way is common for all the WSO2 Carbon Servers (ESB, IS, AS, DSS, BAM .....). Here is a blog post I wrote on installing an AS feature in IS. It is the same procedure for the ESB or DSS, find the required features, install them.