Axway Gateway: Managing Transfers

Monitoring Transfers

This topic introduces the features that enable you to supervise, analyze, and maintain Gateway transfer operations and processes.

Mailbox

To understand how to use the Mailbox in Gateway, it is important that you understand what it is.

The Mailbox is a permanent file in which Gateway stores all data relating to Transfer Requests. During the transfer process, all Transfer Request statuses and data are updated in the Mailbox. This stored information enables Gateway to restart and complete transfers in the case of failure during the transfer process.

The Mailbox contains a complete description of the Transfers.

Each Transfer, successful or not, has its own record in the Mailbox. This record stores information such as:

  • Transfer origin and destination
  • Application used
  • Transfer status
  • Scheduling parameters:
    • start
    • date
    • priority

To view the Mailbox via online commands, you must display details of Transfer Requests using the peldsp select_trans command.

Backup Mailbox: Mirroring

The loss of an unduplicated Mailbox file can provoke the loss of all of the collected monitored information about Gateway. The Gateway Mirroring feature creates a second version of the Mailbox for backup purposes. This protects the Gateway Mailbox from catastrophic failures such as disk crashes. Refer to Managing the Mailbox (command line).

Connections and Connected Users

To monitor the activities of the Gateway server, you supervise current connections. These are connections that are still open, whether they are active (transferring data) or not.

Gateway can provide you with the following types of information about your current connections:

  • Identification
  • Localization
  • Resource consumption
  • Error ratio
  • Average transfer speed

To retrieve this information, use Connection and Connected User objects. Gateway creates these objects for connections and users that use Gateway. The life of the object is limited to the life span of the Connection or Connected User that the object describes. Unlike most other Gateway objects, you cannot create and store Connections and Connected Users. They only display current state information.

To select and display attributes of Connection and Connected User objects, use either the GUI or online commands.

Connections

A Connection object contains information describing a protocol session. Monitored information for connections enables you to detect any exceptional activity (excessive resource consumption, low transfer performance, important error ratios, intrusions, and so on). Use either the GUI or online commands to list current connections, display connection attributes, or stop the progress of a connection (kill the connection).

Connected Users

In the context of monitoring, a Connected User is an entity that is responsible for a set of connections. A Connected User is a virtual object that is identified with the Site used for these connections. All information that single connections carry is cumulated at the Connected User level. As for Connections, use either the GUI or online commands to list and display attributes, and disconnect Connected Users. A disconnection consists in killing all related connections with a single operation.

Logs

Gateway stores traces of all monitoring, protocol, and network events in a Log file. You can configure Gateway to write different levels of detail to the file. You consult log contents either using the GUI or by opening the Log file.

Statistics

If you select the corresponding option for your Gateway configuration, each transfer termination (correct ending or cancellation) triggers the deposit of information to a Statistics file. You can use the information in your Statistics files to analyze transfer performance.

Automatic maintenance operations

Automatic maintenance operations enable Gateway to run continuously, while at the same time:

  • Purging the Mailbox
  • Archiving the Log file
  • Archiving the Statistics file

Gateway executes automatic maintenance operations periodically according to the definition you set for the date/time cycle, and according to the volume of data that transits the Mailbox. Additionally, you can schedule batch jobs at the end of monitor maintenance processing.

Axway Sentinel

Sentinel is a Business Activity Monitoring (BAM) product, part of the Axway Platform platform.

If your Axway product package includes both Gateway and Sentinel, you can configure Sentinel to monitor Gateway transfer activities.

Related topics

Overview: Monitoring Axway Gateway

About Axway Sentinel

Viewing and managing Mailbox contents

Managing the Mailbox (command line)

Maintaining the Mailbox (command line)

Monitoring Connections

Monitoring Connected Users

Monitoring Connections (command line)

Monitoring Connected Users (command line)

Log files

Working with Logs

Working with Logs (command line)

Managing Statistics files (command line)

Automating maintenance operations

 

Links to documentation set for Axway Gateway 6.17.3:

Related Links