I am trying to publish a WSDL in the Governance Registry through the publish app of the GREG.
I have a problem with the endpoints of th wsdl.
The imported endpoint isn't usable from ESB. When I call the proxy service with this endpoint I obtain this error: ERROR_EXCEPTION : org.apache.synapse.SynapseException: Invalid endpoint configuration. {org.apache.synapse.FaultHandler}
This behaviour does not make sense for me. The integration between ESB and GREG should be useful to use previously GREG imported endpoint and wsdl when creating proxies. Am I missing something?
Thanks
the endpoint generated by GREG when publishing a WSLD is a kind of "catalog porpouse" artifact rather than an ESB artifact. You can check this just having a look to the XML code of the ESB endpoint and GREG endpoint.
Best Regards
Please find this useful article about G-Reg and ESB integration. This is a generic concept which will not be bounded to specific version of WSO2 product.
Related
I am trying to Expose a WSDL in WSO2 API Manager, by selecting WSDL Endpoint in the Implementation tab.
And providing the service name and Port respectively.
But while testing the same, from Api Store, the response is 0 - No response body. Also the WSDL is not being invoked.
Please help with this.
I have checked many blogs and videos, but can't find exact solution.
Ex WSDL that I am using is: https://ws.cdyne.com/phoneverify/phoneverify.asmx?wsdl
Used the same wsdl and expose the service using api manager and got the response from the web server. But as per the query posted above you are testing the soap service using api store. There may be mismatch the param you are posting to web service. Therefore use tool like soapUI to test the web service.
User the followings while exposing the SOAP Service
SOAP WSDL - https://ws.cdyne.com/phoneverify/phoneverify.asmx?wsdl
SOAP Endpoint - https://ws.cdyne.com/phoneverify/phoneverify.asmx
Reference -
[1] http://blog.rajkumarr.com/2015/08/how-to-expose-soap-services-as-soap-services-via-wso2-api-manager.html
[2] http://www.vitharana.org/2015/01/soap-web-service-as-rest-api-using-wso2.html
[3] https://docs.wso2.com/display/AM191/Invoke+an+API+using+a+SOAP+Client
I already created sample project for wso2 ESB twitter connector(method for create sample project) , but i don't know how to test that project in ESB (Create as Sequence Project).
Twitter Connector Documentation
When you invoke the sequence, with respective operations used in the sequence, you will notice that the connector operations executed.
better if you try with WSO2 developer studio, then you can easily create sequence with config.
http://sumuditha-viraj.blogspot.com/2013/10/how-to-use-wso2-developer-studio-cloud.html
here is another good article with practical usecase..
http://wso2.com/library/articles/2013/12/esb-connectors-in-action-enterprise-integration/
How can I expose the wsdl through WSO2 governance registry. I have promoted the service lifecylce through to production and was hoping to get an URL some which I can share with the service consumers for discovering the service and the contract. Any pointers are appreciated.
Update: "URL some " is a typo.. apologies. In a nutshell I am unable to comprehend how to accomplish UDDI / WS-Discovery aspects with instructions in the document. I am simply looking to expose the wsdl through a url such as this "host:port/services/environment/myservice?wsdl" and would like to have the flexibility of managing service endpoints for each environment. I have a client which has to discover the wsdl's dynamically and i am figuring out ways to expose it to them. In the process, stumbled upon the wso2 product and trying to figure out.
You can use ws-discovery
another option is , you can use UDDI registry to find your services..
I have already checked the information related to WSO2 ESB SAP Adapter from this link:
http://wso2.org/premium/summer-school-2011-session4-enterprise-integration-with-sap-and-wso2-esb
Is this the only information i can found about it?
I didn't find anything related to it in the official documentation of WSO2 ESB...
An example showing how to configure this adapter in the ESB will be very helpfull!
Thanks in advance,
Santiago.
You can refer following documentation for more info about WSO2 ESB integration with SAP.
http://docs.wso2.org/wiki/display/ESB460/Enterprise+Integration+with+SAP+and+WSO2+ESB
This documentation was added recently and I hope you will be able to find the information you are looking for.
WSO2 ESB comes with a variety of adapters to connect to all sorts of different systems. One of these adapters is the SAP adapter.
The WSO2 SAP adapter has full iDOC and experimental BAPI support. It used the SAP JCO library as underlying framework to communicate with SAP.
Installing the adapter couldn’t be easier. Its shipped with WSO2 ESB and the WSO2 ESB documentation website describes the installation procedure from the WSO2 perspective.
The installation procedure however does not guide you on how to find the settings you need in SAP.
That’s where this blogpost steps in. It is actually the first in a series of three. I’ll first take you through setting up the SAP connection. Then the next blogpost will introduce sending iDOCs and the last post will take you through invoking BAPIs at SAP.
So, let’s start off with some SAP adapter knowledge. I’ll refer to the WSO2 ESB SAP adapter as ‘SA’ in the following guide.
The SA is capable to be used as a Client as well as a Server. To setup the SA as client to a SAP system you’ll need to setup a client-side configuration fle. This file should be named [SAP-GWHOST].dest and must be placed in the [WSO2_HOME]/repository/conf/sap folder. This folder does not exist per default so make sure you create it and provide enough access rights for the WSO2 user to read the files within it.
To setup the WSO2 as an idoc server you must create a configuration file named [SAP-GWHOST].server.
Let’s first handle the client configuration file. There might be some differences based on your SAP system but the following settings should cover a lot of installations. The screenshots are based on SAP ECC version 6.0
In the examples here the SAP gateway is known as SAPSYS01.
Hello Stackoverflow & WSO2 community,
I want to thank you for the ongoing support from the beginning of my architecture building. I'm not much skilled at creating SOA solutions, and your support has been, is and will be much important.
While trying to solve the ESB problem, I was trying to connect BAM and ESB following the tutorial I found in wso2bam-1.3.2\samples\eventing-mode-mediation-monitoring.
My steps has been:
Adding the repository in WSO2 ESB;
Adding the "BAM Mediation Statistics Data Publisher" feature;
Enabling statistics on a simple service;
Adding the ESB server in the WSO2 BAM as: https://<ip-address>:9443/carbon/ or https://<ip-address>:9443/carbon/services, with
Data Collection Method: Eventing
Type of Data: Mediation;
Running the proxy service from an external client (Netbeans java application) - note that statistics were reported into the graphic near the proxy service of the ESB
Checking the BAM - but, for instance, the Service Calls gadget says:
No services found for the server https://<ip-address>:9443
I deduce something went wrong.
If you can help me again, I'm going to begin thinking about a way to give you some kind of useful feedback!
It seems BAM 1.3.2 seems to have an issue with the ESB. Could you try with BAM 1.3.0? It should just work.