1.What is an Application Messaging?

Application Messaging, based on the “publish-and-subscribe” model, allows PeopleSoft

applications to integrate with each other and with third party applications.
This model provides integration that is close to real-time, which means that the publisher
need not be connected to the subscriber when publishing the data (similar to how email
works). On one end, a message is created and published and on the other end, the
message is delivered to any number of subscribers.

2.What are the benefits of Application Messaging over previous solutions for system
integration?
Application Messaging provides many benefits over previous solutions for system
integration. However, the three key benefits are as follows:
• Synchronization of data. Application Messaging helps synchronize data stored in
different systems.
• System-to-system workflow. PeopleSoft workflow is based on business events—
conditions that trigger the need for a follow-up activity. Business events can direct
work from person to person and also from system to person. While Application
Messaging is not based on the existing architecture of PeopleSoft workflow, it does
enable system-to-system workflow by eliminating the need to programmatically
invoke each step of a business process spanning different systems. Instead of creating
a custom program to drive the workflow, the delivery of an application message to a
subscriber initiates the execution of the next step through the use of a subscription
process.
• Internet integration. Application messages flow through the Internet using XML and HTTP.
This open technology supports business-to-business integration, allowing PeopleSoft
applications to communicate with any other systems, anywhere in the world.
• Simplifies Integration. Application Messaging simplifies the task of integrating PeopleSoft
applications with third-party applications and legacy systems. Because it provides an
automated and efficient method of sending and receiving data between systems, it alleviates
the need for customized batch processes.
3.Mention the key components and of Application Messaging? State what each one
does?
Component What it does…
Message Used for designing messages and related objects
Designers (message nodes and message channels) with Application
Designer.
Message Server Coordinates message nodes, channels, queues, and
publish-and-subscribe events at runtime.
Message Used for checking delivery status of messages at runtime;
Monitor similar to Process Scheduler’s Process Monitor.

You use Application Designer to define three types of objects related to application
messaging:
• Message nodes
• Message channels
• Message definitions

What is a Message Node?

A Message Node is an object that represents a publishing or subscribing system on the
messaging network. A message node will often relate to an application server or
database name.
What is a Message Channel? Why Channels are used?
Channels are a logical grouping of messages. Each message must belong to one and only
one Message Channel. Channels are used for the following:
• Ordering of messages
• Routing of messages to specific message nodes
• Increasing throughput when using channel partitioning
• Security
• Easier maintenance of messages with common configuration properties
• Defining the processing attributes for timeout parameters, error thresholds, and delivery type
(Guaranteed or Best Effort Delivery)