Do we have a feature in WSO2 ESB REST API where we can deploy REST API services on Carbon server with different ports.
In the sense, REST-API-1 with port 1000
REST-API-2 with port 2000 and so on.
I don't want to use server port which is by default 8280 for all REST services.
I need unique ports for each REST API Service as mentioned above.
Thanks,
Abhishek
This is not supported. What you ca do is change the port. But you can't use different ports for each service.
Related
I'm using WSO2 ESB v.4.8.1 and WSO2 CEP v.3.1.0 and I want to integrate each other. The problem is that I fill IP Address, protocol, disable security connection, Authentication Port set 7711, Receiver Port set on 7611 and when event come to ESB in order to send to CEP I get this error:
ERROR AsyncDataPublisher Reconnection failed for ssl://<ip_address>:<port>
but security connection is disable.
I turn off firewall, set security connection but this doesn't help.
Has anyone know how to fix that?
I assume you are doing this by creating a BAM Server profile and providing a CEP Thrift endpoint. I would suggest you to try this out on a single machine with CEP running on port offset. This will let you identify whether the issue is with your network. If your running CEP on port offset 1, Reciever port should be 7612 and Authentication port should be 7712
I have followed the procedure for cluster deployment of wso2 API manager mentioned in
Referencing: http://docs.wso2.org/display/CLUSTER420/Clustering+API+Manager
But when i am running API manager with different profile wso2 API manager is started but is not accessible from the browser.However, if I change the port offset in carbon.xml to 0 and then r everything runs fine.Please tell me where is the issue.
When you change the port offset in carbon.xml, all default port values will be adjusted according to the port offset values.
If port offset is 2, the default HTTPS port 9443 will be changed 9445 in the run time. So you should access the management console via 9445 port.
Also see following wiki page about changing port offset for API Manager.
http://docs.wso2.org/display/AM160/Changing+the+Default+Ports+with+Offset
I hope this helps
I have to expose an API with the port other than 8280. i modified that in axis2.xml to port :8286 for HTTP Transportreceiver . Even after restarting the apigateway service , it is Refusing the connection on the particualar port.
Whats the process for modifying the ports.
You just have to change the Port offset of the API Manager Server. For that change offset configuration in <PRODUCT_HOME>/repository/conf/carbon.xml
<Offset>1</Offset>
This will change the NIO port which is 8280 by default to 8281 (8280 + 1).
After that make sure to edit all the hardcoded endpoints of default APIs available by following[1]
[1]http://docs.wso2.org/wiki/display/AM140/Configuring+Port+Offset
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.
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.