can we use Linux server as MID server to transfer files between ServiceNow and another server

avinashkande
Tera Contributor

Can we use Linux server as MID server to transfer files between ServiceNow and another server and vice versa, if so how to achieve that ? Please suggest

2 REPLIES 2

ersureshbe
Giga Sage
Giga Sage

Hi, Mid server is an agent to install windows or Linux machines. The attachment API is going to help to achieve the requirement. I would recommend to check the another server feasibility (Base64, Binary format). If files transfer to the 3rd party system you should check with the 3rd party system.

Regards,
Suresh.

Oddeoh
Tera Contributor

You can consider the MID server as basically the On-Prem to Off-prem SaaS processing "gateway" server. Once setup, it can also run other scripts, tools or processes that the OS supports at the same time (as long as MID server resource needs are not significantly impacted).


Make sure the Linux server meets the 64-bit OS requirements to setup a MID server on. (RHEL6, CentOs6, Ubuntu14) and get it integrated with your ServiceNow instance.
https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/product/mid-server/reference/r_MID...


Assuming from this post that you are not able to access (i.e. security, network constraints), or do not want to do scheduled imports and transforms that are configured and handled ideally from within ServiceNow. Or these information sets are not ultimately going into ServiceNow from external systems.

In that case, this is done by creating scheduled OS jobs (ie. chron jobs) on the MID server to run scripts to move files around outside of ServiceNow, or to the local MID server for import. You can host FTP mounts or file shares on the MID server if that helps extensibility to external systems to move data.

In practice, IMHO, where possible, the process that generates the data ("Provider") is often a better mechanism to used to push the output file or data to where you want it consumed or is to be "Subscribed By" its targets. Let the process (as a discrete "Service") publish via API, FTP, etc. if you can to its output targets. Such that, if the service rendering or providing the data fails, you will know as there is no file to pickup or no data ingested, and it helps in troubleshooting where to go. With zero "false positives" by downstream consumers, you are also self-documenting what targets are subscribing or receiving the data.

Likewise, configuring the ingestion and/or transform from within ServiceNow's many methods is preferred as well. Those facilities can pull the data from the local MID-server data presentation mechanisms or what is accessible as well.