How do one invoke a secured SOAP web service deployed on weblogic using WSO2 ESB ? Example's given in the tutorial seems to work only for secured web services deployed on Axis 2 server, using Apache Rampart.
Please guide.
Thanks.
It won't make any difference whether its developed in Axis2 or not. If you want to invoke a secured service through WSO2 ESB you need to attach the corresponding security policy to the end point.If you can share any errors you get with that approach that be helpful to answer better.
Related
How do I upload the API I created in WSO2 Integration Studio installed on my own computer to the WSO2 API Manager on the remote server.
From the Add new server menu, I clicked the WSO2 Remote Server option under WSO2 and entered the host and server URL information, but it did not publish. When I examined WSO2's own documents, I could not find detailed resources about connecting to a remote server and publishing.
Can you help with this?
Can you add your integration studio version and WSO2 Api Manager version?
You can try this documentation https://apim.docs.wso2.com/en/latest/integrate/develop/working-with-service-catalog/
You can register the service in the service catelog as below.
Start the WSO2 Micro Integrator pointing to API Manager.
You should have the carbon app of that particular service in the Micro Integrator.
When Micro Integrator starts it registers the available services in the API Manager.
From logging into the APIM publisher you can create an API.
Instructions are available here - https://apim.docs.wso2.com/en/latest/integrate/develop/working-with-service-catalog/
I'm trying to deploy this example:
http://wso2.com/library/articles/2012/08/securing-sts-security-token-service-kerberos/
I'm doing in the version of the ESB 4.9.0. The problem I'm facing is that I can't find the security options for the echo proxy service.
Could you help me? Thanks in advance.
Enabling security for services via the UI was removed from ESB 4.9.0. This is removed from other service hosting supported middleware of WSO2 such as Data Services server and Application Server. Now the recommended way of securing the services is via the WSO2 Developer Studio. See the following webinar.
http://wso2.com/library/webinars/2015/12/how-to-secure-your-enterprise-services-with-wso2-esb-4.9/
And also the following documentation.
https://docs.wso2.com/display/ESB490/Applying+Security+to+a+Proxy+Service
I’m working with the WSAS, GREG and the ESB of wso2, I have seen a lot of examples of discovering services hosted on the WSAS with the GREG and using the ESB as a client of the GREG, but as a government strategy, I think I should have registered and managed all my services, them it would be useful if I could automatically discover the services hosted in the ESB to, so, I try to do it in the same way as with the WSAS but it didn´t work.
It is possible to automatically discover the services hosted on the ESB by the GREG?
it should work for ESB also
Did you configure ESB DiscoveryProxy at ESB axis2.xml?
[1]https://docs.wso2.org/display/Governance460/WS-Discovery+with+Governance+Registry
[2]http://wso2.com/library/articles/2011/08/rediscover-soa-wso2-carbon-wsdiscovery/
If I have some functionality I want to expose via REST in the WSO2 Application Server and it seems that I have two main choices:
Deploy as a JAX-RS Application
Deploy as a Service
When deploying as a service, it appears that I have options for Quality of Service that don't appear to be available for Applications.
Question: If I am creating a REST based functionality from scratch, should I prefer to design as a service rather than as an application, because the service has more flexibility?
In WSO2 Application Server there are two approaches to create RESTfull services.
Create RESTfull service using Axis2, then you should deploy them as "service"
Create JAX-RS spec based service using CXF, then you should deploy them as "JAX-RS" applications.
I'm interested in understanding a little more about how local transport may aid performance within the WSO2 ESB. I have looked at http://heshans.blogspot.co.uk/2011/06/local-transport-implementation-for-wso2.html which suggests that the Proxy Services can communicate via local transport with the local prefix. However, if a Web Application is also installed on the same ESB, is it possible to use local transport to communicate with the actual Web Service Endpoint? The reason I ask is that I am investigating the differences in JBoss SOA in comparison with WSO2 and would like to understand if there are any performance advantages using JBoss over WSO2 as it appears that JBoss supports InVM transport.
Any help would be much appreciated.
Regards.
The purpose of the local transport is communicate efficiently with the services runs on the same JVM. For instance ESB proxy talking to another proxy service. You can use WSO2 Application Server to deploy web apps, but if you call it from another ESB instance then you cannot use local transport(because there are two jvms).
What you can do is that, you can install the WSO2 Application Server features on WSO2 ESB and then deploy the webapp. In that case you can use local transport between the webapp and esb proxy services etc.