Category: Technology

Multiplexing In Dynamics 365 Business Central

Multiplexing is a technique used to combine and send the multiple data streams over a single medium. The process of combining the data streams is known as multiplexing and hardware used for multiplexing is known as a multiplexer.

Multiplexing is achieved by using a device called Multiplexer (MUX) that combines n input lines to generate a single output line. Multiplexing follows many-to-one, i.e., n input lines and one output line.

Demultiplexing is achieved by using a device called Demultiplexer (DEMUX) available at the receiving end. DEMUX separates a signal into its component signals (one input and n outputs). Therefore, we can say that demultiplexing follows the one-to-many approach

Multiplexing in Microsoft Dynamics 365 Busienss Central

Multiplexing refers to the use of hardware or software that a customer uses to pool connections, reroute information, or reduce the number of devices or users that directly access or use Business Central, on premises Server. Multiplexing does NOT reduce the number of licenses of any type required to access the Business Central, on-premises Server. Any user or device that accesses Business Central, on-premises Server—whether directly or indirectly—must be properly licensed

Business Central, on-premises licenses are required for users or devices that directly input, query, or view data from the Business Central, on-premises Server. Similarity, Business Central, on-premises licenses are required for users or devices that input data into, query, or view data from Business Central, on-premises Server through a pooling device. Pooled connections use a non-interactive user account in Business Central, on-premises that can access the system but only via the web service layer. Internal users and devices accessing Business Central, on-premises data indirectly through a portal or via an API to a separate software such Microsoft Outlook must also be properly licensed, regardless of if they are set up as a Business Central, on-premises user in the server software. For example:

  • Internal users and devices access Business Central, on-premises data indirectly through a thirdparty application must still be properly licensed for Business Central, on-premises
  • Users or devices that access the software files, data, or content provided by the product that is made available through an automated process require Business Central, on-premises licenses
  • The number of tiers of hardware or software between the Business Central, on-premises Server
    and the users or devices that ultimately use data, software, or functionality does not affect the number of licenses required.