Listener Service association not working as expected

Bonjour Seb,

Je pense que vous êtes francophone, donc cela sera plus facile pour les explications. l'utilisation de l'étoile dans le listener(juste en face de Endpoint Adress) permet d'écouter sur toutes les adresses IP déclarées sur votre serveur.  Je commencerai par isoler une seule adresse IP d'écoute en remplaçant l'étoile par une IP unique (10.12.2.41:9003 à la place de *:9003) . Alors vous pourrez tracer les paquets. Au mieux, arrêtez la région, supprimez les listeners, et commencer par en déclarer un, en traçant les paquets. Puis déclarez le second. Prenez également le temps de vérifier la route empruntée (si un firewall , ou un routeur est utilisé). Au plaisir de vous lire. Cordialement. Elie

Hi,

The problem here has to do with the port number.

e.g.

Web Service X is only associated with Listener A on Port 9003

Web service Y is only associated with Listener B on Port 9004

However the two web services are both accessible from either one of the two listeners.

Normally Web Service X should be accessible from Listener A only (port 9003) and Web Service Y should be accessible from Listener B only (port 9004).

Hi Seb,

I have understood the issue. You have to put the focus on network operation, not on Micro Focus enterprise Server. So to help testing and tracking the problem, I suggest you to be more precise with the listener. Do not use the star and you will probably get a difference. I will help you with pleasure.

Regards.

Elie

Hi Seb,

I have understood the issue. You have to put the focus on network operation, not on Micro Focus enterprise Server. So to help testing and tracking the problem, I suggest you to be more precise with the listener. Do not use the star and you will probably get a difference. I will help you with pleasure.

Regards.

Elie

[quote][/quote]

However, both services are available from both listeners which should not be the case.

I'm afraid that assumption ("which should not be the case") is incorrect. As far as I recall, the listener association is used only for dynamic service resolution, when a COBOL web service proxy is configured to locate the service at runtime using the directory.

It is not enforced for actual service execution. That would have to be done by the Request Handler or the service dispatch mechanism in the SEP (as MFCS does not parse the request to determine which service is being invoked), and as far as I know neither look at the destination port for the request or the listener association(s) for the service.

It's also not possible to enforce this through RH user exits, as far as I can tell. Some exit points (e.g. Exit 4) have access to the service name, but not the communications details, or the service-listener association information.

In fact ... It looks like CAS (the ES application engine) doesn't even ask for or receive information about service-listener associations. Only MFDS (the directory) pays attention to those.

So this would be an enhancement request, and it's a substantial amount of work to implement. I don't recall anyone asking for it before now, so it doesn't seem to have a strong market driver, I'm afraid.

[quote][/quote]

You have to put the focus on network operation, not on Micro Focus enterprise Server. So to help testing and tracking the problem, I suggest you to be more precise with the listener. Do not use the star and you will probably get a difference. I will help you with pleasure.

Specifying the interface that each listener is bound to might be suitable in this case, but we don't have enough information to tell. It's possible that both listeners need to listen on the same interface (or all interfaces), but still restrict service access by destination port.

It's quite possible that the only way to resolve this is with a third-party content-inspecting firewall.

Hi Seb,

All activities manage by MFCS (Communication Server) are logged in log.html in the region where you declare the listeners ( may also be log-1.html, log-2.html or log-3.html). Have a look in this file. By the way what is you OS and version hot fix you are using ?

Hope hearing from you soon.

regards. Elie