We are currently using ESB EI version 6.2.0, where we store values in a registry resource property. In ESB 6.2.0, registry values are stored in database.
While trying to export the registry using registry-migration-service-1.0.0.jar, although the registry resource is exported as a file, the registry resource property never gets exported.
For example, registry resource is ABC, with a property "Token" and value "123333", after running export we see the resource file created like below, but there is no mention of the property name/value pair
<?xml version="1.0" encoding="UTF-8"?>
<resource name="ABC" isCollection="false" path="/_system/governance/ABC" registryUrl="https://localhost:9443/registry" status="added">
<mediaType></mediaType>
</resource>
what is the right way of exporting registry from ESB so as to retrieve property values as well?
Related
I am trying to insert data into a database using the DB report mediator in WSO2 EI. Using Integration Studio 8.0.0 for developing the API. Everything works fine on hardcoding the connection parameters inline as shown below.
Now, I want to specify the connection parameters as registry entries. So, created local entries under registry config. But not sure how to set them as parameters in DB report configuration. When I tried as below, it reads the entire content of the registry local entry instead of just the value and fails. Need suggestions on how we can set the connection parameters as registry entries?
I have specified a custom WSDL in a proxy service with:
<publishWSDL key="conf:sample_proxy_wsdl1.wsdl" preservePolicy="true"/> according to this doc. But I keep getting the below error. What is key in this case?
Caused by: org.apache.synapse.SynapseException: Couldn't build the proxy service : HttpToJms. Unable to locate the specified WSDL to build the service
at org.apache.synapse.core.axis2.ProxyService.handleException(ProxyService.java:978)
at org.apache.synapse.core.axis2.ProxyService.buildAxisService(ProxyService.java:622)
at org.apache.synapse.deployers.ProxyServiceDeployer.deploySynapseArtifact(ProxyServiceDeployer.java:84)
... 73 more
This is what I see in the registry resource editor. Tried giving the deploy path publishWSDL key="conf:/_system/governance/endpoints/sample_proxy_wsdl1.wsdl" but still same error.
Your WSDL can be in WSO2 registry governance (gov) repository or configuration (conf) repository. According to the documentation, which you have follow it looks like you don't have proper registry path.
If you are using Governance repository key should looks like: key="gov:/endpoints/sample_proxy_wsdl1.wsdl" . And looking from your screenshot, with Registry resource editor, this should be proper for your.
If you are using Configuration repository, it should look like: key="conf:/endpoints/sample_proxy_wsdl1.wsdl""
I'm using WSO2 Intergration 6.6.0 , my attention : I want multiple projects can use/reuse Endpoint in registry resource project , is it possible ?
I created a registry resource project with 1 HTTP Endpoint , created a composite application archive including registry resource project and upload it to ESB server successfully.
But I don't know how to use/import this endpoint in a project.
Please help.
If your endpoint exists in a registry you can use it like
<call>
<endpoint key="gov:/endpoints/endpoint.xml"/>
</call>
In this example I used endpoint stored in governance registry in endpoints directory named endpoint.xml.
I am attempting to use Greg to hold endpoint URL's for services deployed into non-WSO2 containers (Weblogic/JBoss). I would like to use WSO2 ESB to perform mediation and routing of data through these endpoints.
However, when I look at the WSO2 ESB samples, it is not clear how I instruct the ESB to use WSO2's Greg. Below is the xml used to have the ESB use a registry deployed to the filesystem.
<definitions xmlns="http://ws.apache.org/ns/synapse">
<registry provider="org.wso2.carbon.mediation.registry.ESBRegistry">
<parameter name="root">file:./repository/samples/resources/</parameter>
<parameter name="cachableDuration">15000</parameter>
</registry>
</definitions>
My assumption is that the registry tag's provider element should probably be able to be overridden with a web-service address providing access to Greg.
When all is said and done, I would like to create simple BPMN configuration files that connect to Greg, obtain URI's and URL's for the services used by the file, and then to reference them as properties later in the BPMN route.
First question, is this a standard configuration, or is there a better way to integrate WSO ESB and Greg.
Second question, are there any examples I could refer to that will answer this question?
Please refer following documentation.
[1] http://wso2.org/library/tutorials/2010/04/sharing-registry-space-across-multiple-product-instances
[2]http://docs.wso2.org/wiki/display/ESB460/Storing+Various+WSO2+Enterprise+Service+Bus+Configurations
Those include how you can store and using WSO2 governance registry in highlevel.
If you need to manage endpoints through API in governance registry following will help.
[3] http://docs.wso2.org/wiki/display/Governance453/Endpoints+with+Governance+API
[4] http://docs.wso2.org/wiki/display/Governance453/Endpoint+Look-up+Sample
Futher this thread include some of the hints how you can access custom stored properties in Registry
[5]How to access system property from WSO2 ESB and Registry
WSO2 Governance Registry is a meta data repository, therefore you can use it to store the SOA artifacts (WSDL,Schems,Policies, Mediation configurations , customs artifacts ..etc) of your deployment. After that you can govern those artifacts through the Governance Registry. You can find more details in the ESB documentation[1].
[1]http://docs.wso2.org/wiki/display/ESB460/Config+and+Governance+Partitions+in+a+Remote+Registry
Thanks & Regards,
Ajith
I have WSO2 ESB and WSO2 GREG running with registry being mounted to ESB instance.
While trying to create Loging proxy service I picked up the WSDL from registry. The WSDL has a schema import which it depends on. However ESB fails to resolve the schema location trying to find it on the local FS.
Screen here
Logs here.
Can this be overcame? Or that's another bug for WSO2?
Thanks,
Vladimir.
Use exactly the same "SchemaLocation" attribute value used in your WSDL in the "SchemaLocation" attribute of the "resource" element of the "publishWSDL" option.
For example, if the WSDL has a the schema imported as,
<schema namespace="some_namespace" schemaLocation="./TestSchema.xsd">
Then the "schemaLocation" attribute of the "resource" tag should also have the same as mentioned below.
<resource schemaLocation="./TestSchema.xsd" ...>