103 - Babelway - Monitoring Messages

The 103 - Monitoring Messages Babelway course will cover the basic tools focused on monitoring the messages that flow through the Babelway Platform.

We will cover all tools necessary to monitor the flow of your data through the Babelway environment. We'll go over details of messages, statistics, and error handling.

Agenda includes:
Monitoring
Message Details
Statistics
Troubleshooting
Errors
Notifications

Table of contents

Monitoring

What is a Message? (1:01)

Message Details

Each Message in Babelway contains a lot of information relevant to the files going through the system.

A message can be accessed in the Monitoring section of Babelway:

You can use the headers to filter through your system and find the messages you are looking for. When you click on the message, you are taken to the message details page:

There is a lot of information about the message on this page. The most relevant pieces are:

Summary - The overview of the message information

  • Date In Timestamp - So you know when the message was processed
  • Status
  • User Comment - An editable field that can be used among users to communicate on particular messages
  • Channel - A link to the channel that processed this message
  • Message In - A link to download the inbound message file (pre-transformation)
  • Message Out - A link to download the outbound message file (post-transformation)

Runtime Info

  • Timestamp - for further processing timestamps
  • Key - Unique ID for the Message
  • Reference - A field that can be mapped as metadata from the message in the transformation

Internal Files

  • Step Files - Babelway internal files at different stages of processing - Useful for troubleshooting transformations.
  • Other files - Context In/Out files are connection and processing logs - useful for troubleshooting connections.

Message Statuses

Messages within Babelway can exist in a variety of statuses. The flow of a message status is:

These message statuses are:

  • Processing - Message is being processed by a Babelway channel
  • Paused - Message Processing was temporarily stopped
  • In Delivery - Message is being transferred to the target system. Processing is complete, but complete delivery requirements are not yet met (ex: the file has not yet been downloaded by the partner).
  • Error - Message Processing is completely finished but there was an error in one step of the process
  • Error (Closed) - User action has closed a message in error.
  • Success - Message Processing is completely finished with everything happening as requested/expected.

Reports and Statistics (1:00)

In addition to the monitoring message section, Babelway offers tools to view the statistics of your environment. Below the 'Monitoring' section, you can click on 'statistics':

This can give you a high level view of your data and help you focus on trading partners that may need more attention because their messages are in error more frequently that what is acceptable. When you have several messages flowing through your channel, you can begin to see how valuable this information can be:

Errors & Troubleshooting

Understanding Errors (2:21)

Fixing Errors (3:14)

Notifications

Creating a Notification (1:24)

Task #1

Task #1

The following documents have been attached to the course:

Basic XML invoice.xml

<request>
<invoice>
	<invoiceHeader>
		<invoiceNumber>INV123</invoiceNumber>
		<invoiceDate>2016-03-01</invoiceDate>
		<poNumber>4500064817</poNumber>
	</invoiceHeader>
	<invoiceDetail>
		<lineItem>
			<quantity>1</quantity>
			<unit>EA</unit>
			<unitPrice>1.99</unitPrice>
			<description>Nails</description>
		</lineItem>
	</invoiceDetail>
</invoice>
</request>

Basic CSV Invoice.csv

Invoice Number,Invoice Date,PO Number,Quantity,Unit,Unit Price,Item Description
TEST01,11/23/2015,4500237392,10,,299.99,Ski Boots
TEST01,11/23/2015,4500237392,1,,19.99,Marketing Materials
TEST02,12/1/2015,4508390298,10,,49.99,Ski Poles

XML File 2.xml

<request>
<invoice>
	<invoiceHeader>
		<invoiceNumber>INV123</invoiceNumber>
		<invoiceDate>2016-03-01</invoiceDate>
		<poNumber>4500064817</poNumber>
	</invoiceHeader>
	<invoiceDetail>
		<lineItem>
			<quantity>1</quantity>
			<unit>EA</unit>
			<unitPrice>1.99</unitPrice>
			<description>Nails</description>
		</lineItem>
	</invoiceDetail>
</invoice>
</request>

XML File 1.xml

<request>
<invoice>
	<invoiceHeader>
		<invoiceNumber>INV123</invoiceNumber>
		<invoiceDate>2016-03-01</invoiceDate>
		<poNumber>4500064817</poNumber>
	</invoiceHeader>
	<invoiceDetail>
		<lineItem>
			<quantity>1</quantity>
			<unit>EA</unit>
			<unitPrice>1.99</unitPrice>
			<description>Nails</description>
		</lineItem>
	</invoiceDetail>
</invoice>
</request>

Complete the following task to test your skills on message monitoring.

Tasks:

  • Create a channel

  1. Gateway IN: SMTP Email, yourname@

  • Put monitoringmessages

  1. Message IN: Basic XML Invoice

  1. Message OUT: Basic CSV Invoice

  1. Gateway OUT: Null

  • Map all fields

  • Use date function on invoiceDate map : changeDateTimeFormat([invoiceDate], ‘yyyyMMdd’, ‘MM/dd/yy’)

  • Create notification to your email on Failure. Insert ‘URGENT!’ into subject of failed message

  • Deploy

  • Send via Email XML File 1 and XML File 2 to the SMTP Email gateway you created

  • View results, if any errors, resolve within mapping, deploy again

  • Resubmit errored messages