Finding Used Ports on Mirth Connect Server #5250
Replies: 5 comments 1 reply
-
|
It is a process thing here including adding a tag with the port number to the channel to make it easier to see. There isn't a great "easy button" for this problem, you can see in issues recent requests to add this functionality as standard. There are options of course including sourcing stuff from DBs, etc. |
Beta Was this translation helpful? Give feedback.
-
|
What port is being used can definitely be tracked by pulling channel meta
out of db table.
…On Tue, Jun 21, 2022 at 12:26 PM pacmano1 ***@***.***> wrote:
It is a process thing here including adding a tag with the port number to
the channel to make it easier to see. There isn't a great "easy button" for
this problem, you can see in issues recent requests to add this
functionality as standard. There are options of course including sourcing
stuff from DBs, etc.
—
Reply to this email directly, view it on GitHub
<#5250 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFPLOOW4UCFRJNNA54GWBG3VQIJNZANCNFSM5ZNPGXUQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: <nextgenhealthcare/connect/repo-discussions/5250/comments/2996679@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
Not always. Ports can be set with a var. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, true
…On Tue, Jun 21, 2022 at 4:32 PM pacmano1 ***@***.***> wrote:
Not always. Ports can be set with a var.
—
Reply to this email directly, view it on GitHub
<#5250 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFPLOOSUIVV6EZYAEGZD3GDVQJGHHANCNFSM5ZNPGXUQ>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
In the paid space there are a few options. Both Zen and NextGen have channel analysis tools which will report on ports used by source and destination connectors. Zen has (had?) a tool as part of their Insight offering that would also do this analysis on your MC instance. NextGen has you upload a server export to their Success Community portal. It wouldn't surprise me if Innovar was working on something but I don't know their offerings. Those tools can't be doing anything too magical. Fundamentally they would have to look at the channel definition, inspect the source connector, then for the connector types that allow ports (network connectors as opposed to say a file reader) the port field can be parsed out. This can be done either in the MC database in the @aungktun did some work on this at #5245 . His query does not cover all the connector types but is a great start on the problem. You can see how he extracts connector details from the MC channel XML. I think its a great baseline, the next steps are just to add different connector types. Some additional ideas around adding this to the dashboard are:
I hope these references help you find a starting point. As you build on others work or write your own code, please do share that with the community. You're not the only one pecking at the problem! |
Beta Was this translation helpful? Give feedback.
-
|
Thank you Jon for compiling all info in one place.
…On Thu, Jun 23, 2022 at 8:56 AM jonbartels ***@***.***> wrote:
In the paid space there are a few options. Both Zen and NextGen have
channel analysis tools which will report on ports used by source and
destination connectors. Zen has (had?) a tool as part of their Insight
offering that would also do this analysis on your MC instance. NextGen has
you upload a server export to their Success Community portal. It wouldn't
surprise me if Innovar was working on something but I don't know their
offerings.
Those tools can't be doing anything too magical. Fundamentally they would
have to look at the channel definition, inspect the source connector, then
for the connector types that allow ports (network connectors as opposed to
say a file reader) the port field can be parsed out. This can be done
either in the MC database in the channel table, by looking at each
channel export individually, or a global server export. I vaguely remember
someone having a DB query that did this but I cannot find the project or
gist.
@aungktun <https://github.com/aungktun> did some work on this at #5245
<#5245> . His
query does not cover all the connector types but is a great start on the
problem. You can see how he extracts connector details from the MC channel
XML. I think its a great baseline, the next steps are just to add different
connector types.
Some additional ideas around adding this to the dashboard are:
- #5152 <#5152>
- I wrote https://github.com/jonbartels/mirth-connect-dashboard-count
in response to the above discussion, note this plugin is affected by a bug
in MC. It can only show ports on the dashboard and not on the channel list.
- #2115 <#2115> is
OOOOLD but was recently reopened
I hope these references help you find a starting point. As you build on
others work or write your own code, please do share that with the
community. You're not the only one pecking at the problem!
—
Reply to this email directly, view it on GitHub
<#5250 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFPLOOTZOIIBXRYL36UMOE3VQSCKLANCNFSM5ZNPGXUQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
I'm sure this has been asked a thousand times, but searching for "Open Ports", "Free Ports", "Unused Ports", etc, I can't seem to find an answer. What method do folks use to find the inbound ports that have been used/allocated in their Mirth Connect installs so that they can keep track of what's available and what can be used. Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions