20 Reasons to Migrate Magic eDeveloper, uniPaaS and Magic xpa to
.NET by Upgrading Rather than Converting
The Magic xpa Application Platform is a particularly strong platform in
terms of interoperability of applications. While C# .NET is designed to be
proprietary, Magic xpa Application Platform, while .NET based, is designed to
deliver greater interoperability. This is one of many reasons why converting a Magic eDeveloper, uniPaaS or
Magic xpa application to .NET in C# using a code generator makes no sense.
Developers looking for fully .NET applications should instead upgrade to
Magic xpa.
That’s why Magic xpa provides direct support for technologies like
Java, SNMP, MSMQ, JMS, WebSphere MQ, LDAP, Active Directory, Java Script, VB
Script, Client Certificates, Dynamic Data Exchange (DDE), IMAP, POP3, etc. All of these internal Magic xpa functions provide direct support for technologies that are otherwise quite difficult or impossible to support with C#.NET.
The ability of a single programming environment to interface with so many different, unique and tedious environments at a high-level provides tremendous advantages, reduces risk and helps to future-proof your applications. For example, Magic xpa provides direct Java support including support for Java
classes and objects called in a Magic application and Magic applications
exposed as Java classes and objects for use by Java programs.
The idea that C# can handle a converted Magic application is
ludicrous. Sometimes developers have no choice but to deal with older
technologies like DDE. So even though you might be able to convert your code,
without the Magic engine, there is no automatic way for raw C# to handle DDEs.
Let’s look at another simple example like SNMP. Magic xpa supports
Simple Network Management Protocol (SNMP) functionality. This lets Magic xpa
programs and the Magic xpa engine (the broker and the requester) send SNMP
compliant messages to a monitor. It also gives the system administrator control
over various Magic xpa modules via an SNMP monitor.
SNMP governs network management and monitors network devices and
their functions. Magic xpa is SNMP enabled, so the Network Management Station
(NMS), also referred to as an SNMP monitor, can query and manage the Magic xpa
broker (including its registered enterprise servers) and the Magic xpa broker
can report traps (alarms, failures, or other exceptional events).
Messaging is another great example of Magic’s superior
interoperability compared to C#. In distributed applications, two different
applications often need to communicate with one another to transfer
information. One of the ways to accomplish this is message queuing, which
ensures guaranteed delivery.
Message queuing lets applications send messages without waiting
for a reply and to continue with other processes. Other applications can
receive the messages at their leisure and continue processing according to the
data received.
Message queuing is a method by which program instances can
exchange data using an interface to a system-managed message queue, which is
managed by the operating system. Application programs create message queues,
and send and receive messages using an application program interface (API).
There are two main ways to send messages:
Send / Receive – This is used when there are one or more senders
who want to send messages to one receiver. Each message is addressed to a
specific queue, and the receiver extracts the message from the queue.
Publish / Subscribe – This is used when there are multiple senders
(publishers) and many receivers (subscribers). The publisher sends messages to
a central location, the topic, which sends the messages to anyone who has
subscribed to this specific topic.
Both of these methods provide the user with guaranteed message
delivery and are supported out-of-the-box with Magic xpa. Not so with C#.
Every access to the message queue is done using a set of functions,
such as open, close, and send. Magic xpa provides a message queuing component
with interfaces to three standard messaging queue systems: MSMQ (Microsoft),
JMS, and WebSphere MQ (IBM). C# does a passable job only with MSMQ.
For additional information on how an upgrade to Magic xpa is
superior to Magic to .NET conversion please convert here.
No comments:
Post a Comment