Does WSO2 have a OPCUA connector? - opc-ua

Does WSO2 ESB or WSO2 EI have a OPC UA connector?
We need to access a SCADA system via OPC using a WSO2 product (either ESB or EI).

There is no out-of-the-box support for OPC UA on WSO2. Supported protocols to integrate your existing network and applications as listed below:
Non-blocking HTTP/S transport
Transactional JMS transport 1.0 and 1.1 with binary, text and SOAP messages over JMS
Apache VFS file transport (for example, S/FTP, File, zip/tar/gz, WebDAV, CIFS, etc.)
Mail transport (POP3, IMAP, SMTP) with multipart content support
AMQP via Apache QPid
Financial Information eXchange (FIX)
Hessian binary protocol for web services

Related

Spring Cloud RPC transport

Almost every spring-cloud guide suggests Ribbon with Feign for RPC.
I wonder why Http Rest takes precedence over binary transport protocol for inner micro-services communication behind the API gateway?
What are the binary alternatives to http that support async invocation and all great features that Netflix OSS provides ? (auto-discovery, load-balancing, circuit breaker, retry policy etc.)
Thanks
There is nothing preventing you from using binary RPC like thrift or protobuffs or msgpack with spring cloud. You can use LoadBalancerClient.choose(<serviceId>) to get a host and port you could supply to any network client. Our integrations were the simple rest clients.
Here is a guide that integrates Spring MVC with google protocol buffers.

How to extend Balana OpenAZ PEP to send requests to remote WSO2 Identity Server?

What's the appropriate way to extend a Balana-OpenAZ based PEP to send XACML3 decision requests to a remote WSO2 Identity Server PDP?
You want to send XACML decision request from PEP to Identity Server PDP. Still Identity Server only supports SOAP based web service API, Thrift based API and WS-XACML. Therefore i guess, best way to start is using SOAP based web service API. You can find sample java based client from here to write a extension for Balana-OpenAZ PEP.

How do I communicate apache MQ with wso2 BAM server? (no ESB keeping it simple)

I am trying to get some simple web statistics using a wso2 BAM server, I have installed it, I understand how the events are defined, stored on the casssandra database etc. but I lack the most important thing: how to pass the events themselves to the BAM server?
I have programmed systems where json files are stored in a file ("queue") and my java process reads and processes them every 30 seconds, I thought this would be similar but the truth is I am pretty lost.
The port 7611 is TCP, listening.
Do I have to send the BAM server the events throught it?
Any help would be greatly apprecciated!
AFAIK, WSO2 BAM is not supported for apache mq directly. you have to use ESB or CEP to send events to BAM through thrift (Then you can use apache mq to send the events to ESB/CEP and through any of these product, you can send the events to BAM) .
But You can use the REST api to send the events to BAM which is more simple approach. Please refer the doc [1]. I thing future releases of BAM will support for jms (FYI, refer [2]).
[1] http://docs.wso2.org/wiki/display/BAM220/REST+API
[2] WSO2 BAM with JMS
Thnaks,
Mohan
BAM can get events either through REST API or through Thrift API.
7611 is the unsecured Thrift port and 7711 is the secured Thrift port by default.
As currently BAM does not have out-of-the-box Data Agent for Apache MQ, you have to write a one yourself.
If you want to publish events directly to BAM using Java you can use the DataBridge component in WSO2 code base. (i.e., use https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/data-bridge/org.wso2.carbon.databridge.agent.thrift/4.1.1)

What protocol provider to connect to JMX on WebSphere via SOAP?

I'd like to connect to the JMX server on a WebSphere application server instance using a SOAP over HTTP connector but I don't know where to find a compatible SOAP protocol provider.
I get a MalformedURLException when using a JMXServiceURL starting service:jmx:soap:... that says Unsupported protocol: soap. What jar(s)/protocol provider string do I need to include?
Update: I am playing with a standalone Java client.
Unfortunately, IBM only provides a proprietary API to connect with SOAP over HTTP. They don't provide an implementation of the standard JMX API for that protocol. I faced the same issue and I developed such a connector (which is basically a thin JMX compliant wrapper around IBM's proprietary API), which is now available as Open Source. You can find more information here:
https://github.com/kszbcss/xm4was/wiki/JmxClientConnector
The following document describes how to set up a standard JMX tool (VisualVM) to use that connector:
https://github.com/kszbcss/xm4was/wiki/VisualVMHowTo
As you can see from these documents, after adding the relevant JARs to the class path and setting the necessary system properties, you would simply connect using wssoap as protocol.
Check that in the path Application servers > <server_name> > Administration services > JMX connectors the relative SOAPConnector exists and is Enabled.
Refer at Infocenter for more information.

Apache CXF: Publishing a Web Service (SOAP over JMS) with failover feature

Apache CXF: It seems that failover feature is available, but for clients. I need to create a service that is binded to a JMS queue of a particular JMS server. The JMS provider(TIBCO) has capability of failing over. Is there a way in which I can allow my service to failover to another JMS server at runtime and publish it there? If cxf is not capable of doing this, is there any other framework which allows failover feature for publishing services over JMS?
Vidish,
Server :
The TIBCO EMS administrator needs to configure the FT connection factory and provide the connection factory name and URL details to you. Configure those details in your JMS configurations - that's all needed for server.
Client :
TIBCO JMS API provides failover mechanism. Sample code is available in TIBCO EMS installation folder.
Joy