How is http2 protocol enabled in weblogic 12c?
I read the documentation and I can’t find anything about it.
what aplication server best implements this protocol?
HTTP/2 protocol is not supported in WLS 12c.
WLS 14.1.x (To be determined) will support HTTP/2.
Related
Currently in Weblogic we are running two applications and communicating through JMS Queue. Now one of the application we are moving to Liberty Server. What are the configuration we need to do for JMS Queue connection between Weblogic and Websphere.
Depending on which JMS Provider are you using, you have several options:
if provider has compatible JMS Resource Adapter (e.g. WebSphere MQ) - you can use that RA together with Liberty jca feature
if provider has a sort of thin client, you can embed that client libraries together with your application, and manually setup connection
if your current provider doesn't support any of above, you can use external JMS server that has compatible JMS RA (for example WebSphere MQ) and integrate it with both WebLogic and Liberty.
Update based on comments
There is no simple way to access Liberty JNDI externally - see this post Connect to Websphere Liberty jmsServer from remote application server
You could try to access embedded JMS via API. It is discussed here: https://www.ibm.com/mysupport/s/question/0D50z000062ktc3CAA/helloworld-jms-client-connecting-to-embedded-liberty-jms-server?language=en_US
But to be honest, if I were you I would either:
use external JMS Provider that is compatible with both runtimes e.g. WebSphere MQ
or rewrite interface between WebLogic and Liberty to REST, so that WebLogic invokes via REST simple application that reads the request and puts it to the queue in embedded Liberty JMS engine to avoid calling JMS engine externally.
I am trying to figure out if Oracle JDBC driver supports SOCKS proxy or not. I am not finding any documentation related to this. Please let know if you are aware.
Yes, but only when disabling java NIO for jdbc by passing -Doracle.jdbc.javaNetNio=false to jvm or setting the property programmatically.
You can then use the standard socksproxyHost and socksproxyPort properties to configure the proxy.
No the Oracle JDBC driver doesn't support SOCKS5 proxy. In the soon to be release 18.1 version of the thin driver there will be support for HTTPS proxy and websocket.
I have a VPS (Ubuntu 14.04) with Apache2, Swift 3.1.1 and Vapor installed. I want to receive client side requests to my Vapor-Built-Service via HTTPS protocol (on port 8443 for example). I didn't find any newbie helper document to do this, so please help me.
Thanks.
After a lot of searching I found the answer:
1. You need to install Apache or Nginx on your VPS. Here I assume that the reader uses Apache. But for more info on installing Apache server on Ubuntu 14.04 you can take a look at here.
2. The next thing you need to do is to make Apache work with SSL (or HTTPS protocol). You can find a complete guide here.
3. Now it's time to set the Apache server as a reverse proxy server. You can find a good guide to do that here and here. don't forget to put the reverse-proxy-config-code at port 443 related part.
Update:
There is also another way which you can configure the Vapor directly. Take a look at here.
Wildfly supports monitoring over http-remoting-jmx protocol and Zabbix uses rmi. So is it good practise to use "standard" way of specifying JMX (in the Java opts) in the Wildfly? Or how can i achieve monitoring Wildfly using Zabbix?
Usually the applications that support remoting-jmx do no not work very well with rmi. You can patch the Java gateway to support remoting-jmx - there are community patches floating around. Keep in mind that it is completely unsupported. This support is supposedly coming with Zabbix 3.4 - see https://support.zabbix.com/browse/ZBXNEXT-1274 .
Do you see any risks of deploying WSO2 Governance Registry 4.5.3 on the same Linux server as a JBOSS EAP 6.x application server instance? What about port conflicts? Do I need to make any specific configurations on either the JBOSS or the WSO2 software?
Note: I don't mean to install the WSO2 Governance ON the JBOSS application server instance, but only on the same operating system instance as per the instructions in installation instructions.
It depends on your requirements and the performance expected.
You can check the default ports used by WSO2 Governance Registry from this doc.
If there is a port conflict, you can set a port offset in /repository/conf/carbon.xml as follows: <Offset>1</Offset>
You can also change the conflicting ports only by changing relevant configuration files since the port offset will affect to all ports.