Is it possible to use activemq brokerservice without port number. I am using activemq as embeded to write my app logs to DB. But I am in trouble with open ports while side by side deploying to the weblogic
If you only need in VM client connections you can use ActiveMQ's VM Transport and not add any other network based transports.
Related
The Server and Client (setclientmode(true)) modes need Java and take quite a while to startup (Ignition.Start). The server is the one that holds the cache. I presume that the client node is like a 'local' copy of the cache.
However, Ignite also supports a ThinClient - where we can 'open a connection' and run queries from Ignite.NET without having Java installed. The only configuration required by a ThinClient is the Host IP Address. How can we connect to a specific grid on the ignite server using the Thin Client?
Is this something that is expected to come in the upcoming releases?
Every server node is listening to some specific port for connections from thin clients. By default this is port 10800, but it can be changed. If this port is occupied, then next available is used.
So, if you want to connect to some specific node, then you should specify its IP and port, that will be used for connection.
Documentation: https://apacheignite-net.readme.io/docs/thin-client#section-configuring-server-nodes
I want to use rabbitmq in a project, some clients have to comunicate with the rabbitmq server over internet
What is the best way to expose rabbitmq on the Internet ?
should i use a http gateway or directly expose the rabbitmq port ?
Guillaume.
Yes, you can, it is what https://www.cloudamqp.com/ does.
You need to implement the same security policies you'd use for a web site.
For example, put a load-balancer in front of your rabbitmq cluster, use the SSL connections, you could also configure your firewall to accept the connections only from specific ip addresses etc etc..
I'm trying to understand the topology of Worklight. Specifically how does a WL Server handles its applications.
If I understood correctly, a WL Server has a <httpEndpoint>. This means that a set of WL Applications will have their context root on that port. Right?
This means, If I want to put /worklightconsole on a custom port, I'll need a network installation instead of a standalone so that I can have a cluster of WL instances and each one will bind to a different port.
Did I understood this matter correctly? Then I can use a reverse proxy to needle my requests to the correct instance of WL Server.
Right?
Thanks in advance!
http://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.1.0/com.ibm.worklight.installconfig.doc/admin/c_typical_topology_of_an_ibm_wor.html
Yes the httpEndpoint entry defines the http and https port and the WL applications have their context root on these ports.
If you have different Liberty Servers with the same WL runtime, be sure that the you share the same database and same schema.
After that you can use a Web Proxy to load balance the requests between the different Liberty servers.
I want to establish a UDP Connection from a terminal device to My App On Cloud Foundry.
all output from applications on Cloud Foundry is delivered by proxy via a web server (nginx) and as far as I know only http and https are open.
Perhaps you should look at alternative ways of communicating with your console application, what kind of communication are you trying to achieve?
Using the CF_HOST:UDP_PORT from your terminal device should be OK. I suppose that an application (Java, Perl, etc) is deployed on your terminal device and on the CF server an application with a UDP channel is deployed.
This is an old post but i've had a similar problem when porting my app to pivotal's cloud foundry platform.
Turns out you can continue to use tcp or udp for any outgoing traffic without doing any special configuration (e.g. service binding, etc) but only http or https for incoming traffic. However, there is an interesting workaround proposed here
Does anyone know if there is a port that absolutely has to be open on the SQL server to allow service broker traffic? We were testing what happens when you close off all ports on the SQL server except (1433, 445, 3389) and the query notification still worked. We were under the impression that 4022 has to be open for the service broker to work we a default listening port.
Is there a SQL system view that shows what port the service broker is communicating on?
Is there a command to terminate all active query notifications on a database so the database can be dropped?
Thanks
If your service broker architecture is passing messages between servers (endpoints) then it will need ports other than the normal SQL ones.
If client code such as query notifications is accessing service broker then it uses SQL statements (with some new syntax) through the standard SQL connection and this part doesn't use any additional ports.
From How to: Activate Service Broker Networking (Transact-SQL):
Service Broker does not send or receive messages over the network by
default. To activate Service Broker networking in an instance, create
an endpoint for Service Broker.
When you create an endpoint you specifically assign a port to use:
CREATE ENDPOINT BrokerEndpoint
STATE = STARTED
AS TCP ( LISTENER_PORT = 4037 )
FOR SERVICE_BROKER ( AUTHENTICATION = WINDOWS );
Port 4022 is used when Service Broker communicates with other broker instances. How are you using Service Broker? If all the work is internal to your database then it never needs to use a TCP endpoint.
Query Notification does not require a Service Broker endpoint because it always deliver the messages locally, int he same DB where you started the notifications from. Although configuring QN to deliver notifications to a remote machine is possible, ding so is basically unheard of. See The Mysterious Notification.
As for the question: Service Broker requires only the configured endpoint port to be open. You can see the listening port in sys.tcp_endpoints. If the configured authentication is Windows then the ports needed for Kerberos/NTLM (135, ?389) are also required in order to authenticate the SSB connections. Note that the SMB port (445) is not required by SSB ever. If SSB endpoint configured authentication is certificates then no additional port is required. See How does Certificate based Authentication work.