I will re-visit the HTTPSyncIn and HTTPSyncOut communication channels of Infor M3 Enterprise Collaborator (MEC) as a follow-up of my previous posts part 3 and part 6.
TL;DR: It turns out there is no obligation to use a channel detection, we can use any of the available detections (e.g. XML detection). Also, it turns out we can re-use the HTTPSyncIn in multiple agreements (i.e. shared port).
Previously
In part 3, I showed how to use the HTTPSyncIn and HTTPSyncOut channels for MEC to receive documents over HTTP (instead of traditionally FTP). And in part 6, I showed how to add nginx as a reverse proxy with TLS termination for MEC to receive the documents securely over HTTPS (encrypted).
As for MEC, an HTTPSyncIn and its port number can only be used in one agreement; otherwise MEC will throw “Target values already defined”:
As a workaround, I had to setup one HTTPSyncIn per agreement, i.e one port number per agreement. It is feasible (a computer has plenty of ports available), but in the configuration of nginx I had to setup one server block per agreement, which is a maintenance nightmare.
It turns out…
It turns out the HTTPSyncIn persists the message to disk and queues it for detection and processing:
That means I do not have to use a channel detection in the agreement, I can use any of the other detections, such as XML or flat file detection.
Channel
Like previously, setup one HTTPSyncIn (e.g. port 8085), it will apply to the entire environment:
And like previously, setup one HTTPSyncOut, it can be used by any agreement:
Detection
Setup as many XML detections as needed, e.g.:
Agreement
Here is the key difference compared to previously: select XML Detection, not channel detection:
In the processes, like previously, use the Send process with the HTTPSyncOut:
Setup as many agreements like that as needed.
nginx
If you use nginx for HTTPS, setup one server block only for all agreements (instead of one per agreement), listen on any port (e.g. 8086) and forward to the HTTPSyncIn port (e.g. 8085):
server {
listen 8086 ssl;
ssl_certificate .crt;
ssl_certificate_key .key;
location / {
auth_basic "Restricted";
auth_basic_user_file .htpasswd;
proxy_pass http://localhost:8085/;
}
}
Conclusion
Those were my latest findings on the easiest way to setup HTTPSyncIn in MEC to receive HTTP(S) when having multiple agreements. My previous recommendation to use one channel (one port) per agreement does not apply anymore. Everything will go through the same port, will be persisted and queued, and MEC will iterate through the detections to sort it out and process. I do not know if there are any drawbacks to this setup; for future discovery.
That’s it!
Let me know what you think in the comments below, click Like, click Follow to subscribe, share with your colleagues, and come write the next blog post with us.
M3 ideas 