Papyrus Adapters

are handling applications that span multiple systems and require the passing of documents and data between these systems.

Interacting with outside systems via API's that trigger actions in different systems requires typically a significant amount of custom programming and there is no assurance that the correspondence system can continue to monitor the process once control is passed to a third party application or system.

Papyrus simplifies this integration and reduces drastically the time and effort required through the use of enterprise application servers and providing Adapters for different third party systems such as major ERP systems i.e. SAP messaging systems such as MQ Series, interface with e-mail, workflow and legacy systems. The Adapter is used to convert messages and events into activities inside the Papyrus Objects system.

For example MQ Series Interface:
In many applications, it is required to call the letter generation from the host application. The adapter is a message translator, that waits for events to take place. When such an event occurs the RECEIVER will use its MATCH definitions to find a TEMPLATE in its library which is instantiated and filled according to the TYPE PROPERTIES.

In this flexible manner, there is no programming, compiling adapter programs or the need to distribute them, involved in defining how an adapter reacts to a certain event. Obviously version control can be used to manage the adapter and template setup.

The picture displays the MQ Series Adapter with its references to the message library and a TASK, which is instantiated through a message. The message mapping and data mapping from the MQ message does not require programming but is simply defined in the MQ Receiver and the templates in the folder.

The GUI window is only used by the Administrator or developer and never seen by the user who receives the messages. The TASK just appears in his work folder.