William --
The product development approach for GeoEvent Server avoids developing connectors for specific devices or platforms. While there are some samples on the GeoEvent Server Gallery for data provider or device specific inbound connectors (e.g. Verizon Connect Connector for GeoEvent Server, or Geotab for GeoEvent Server), when considering connectors available out-of-the-box you generally want to identify what transport protocol will be used to send data to GeoEvent Server (e.g. HTTP, TCP, UDP, WebSocket) and how the data records will be formatted (e.g. generic JSON, generic XML, delimited text).
The answer to these two questions will guide you toward a configurable out-of-the-box inbound connector.
Since you mention the ActiveMQ connector, I'll offer that over time we have exposed (as SDK samples) connectors based on "message queues" and "message brokers" such as ActiveMQ, RabbitMQ, MQTT, and Kafka. Not all of the samples on the Gallery are plug-and-play with the latest release of GeoEvent Server. Connectors based on different message brokers follow GeoEvent Server's evolution. We started with ActiveMQ, migrated to RabbitMQ, and are now using Kafka internally to queue and manage event records. None of this changes GeoEvent Server integration fundamentals of identifying a data transport protocol and data record format.
I am not aware of anything developed specifically for WebLogic Thin T3 Client. This could be something you develop a specific connector for using the GeoEvent Server Java SDK. Implementation support for this type of project is available through Esri Professional Services.
Hope this information helps --
RJ
