AMHS MODUL PUMA

NAMA : ACHMAD ADHITYA PRATAMA

COURSE : KOMUNIKASI PENERBANGAN IV A
NIT : 30518001
INTRODUCTION

• Frequentis Puma is a client application designed to support all the X.400 User Agent and AFTN Terminal
functions in one integrated application. The application is written in Java and currently runs on Windows
7, Windows Vista, Windows XP and Linux platform
• Frequentis Puma is intended to operate in conjunction with Frequentis Smart Messenger AFTN UMS
and FOX MTA/MS
GETTING STARTED
Still using Windows Explorer, right click
on the extracted "puma.exe" executable,
create a shortcut to the "puma.exe"
executable, and drag the shortcut to
your desktop. For all invocations of the
Puma application simply double click on
the desktop icon.
PUMA OVERVIEW
The "Menu Bar" and "Tool Bar" contain menu
items and buttons respectively, used to execute
commands to perform the named actions. All
windows will have some menus and buttons, with
the actual items depending on window type.

Most windows are composed of a "Navigator"

pane to the left, an "Editor" pane toward the top,
and below the editor a "Preview" pane. The
Navigator is used to select a context (e.g.
account),
MAILBOX WINDOW
Puma’s Mailbox window, shown in Figure 3 is the main
screen users will use most of their time with Puma.
The Mailbox allows users to view and manage all X.400
and/or AFTN messages they have sent and received
using Puma.

It allows users to view total counts and counts of

unread messages in each folder. It permits filtering
and sorting of messages in the Mailbox Editor table, to
ease finding messages with a given priority, originator,
subject, date, etc.

The PUMA Mailbox provides many of the most

common mail management-related actions, such as
deleting messages, moving and copying messages,
saving messages to files, creating new folders, and of
course replying to and forwarding received messages.
Each of these mentioned features, and more, are
described in the remaining sections throughout this
manual.
Figure
MAILBOX FOLDERS
Inbox
The Inbox mailbox folder is the default destination folder for all incoming messages associated with the corresponding AFTN or X.400 User Account.
Incoming messages may also be copied to specified user folders based in "Inbox Editor Rules", to be described later.
Sent
The Sent mailbox folder is the final destination folder for all messages successfully sent from Puma for the givenX.400 or AFTN User Account. Messages
will only appear in this folder when they have been 100% acknowledged that the message switch has taken possession of a submitted message. Please
see description of the Outbox folder for details of processing a newly composed message.
Templates
The Templates folder is a storage folder for pre-formatted messages that can be used as a starting point for a new document. Templates are manually
stored via the "File > Save To > Templates" command. All template messages within the Templates folder will have a unique name, but may contain any
combination of partial information. For example, 0 recipients, 0 subject, 0 message body text are all valid starting states for a template message.
Drafts
The Drafts folder is a storage folder for messages drafted and stored via the "File > Save To > Drafts". These draft messages may be re-opened at a later
time to complete the message composition. Draft messages are completely internal to Puma, not shared with the message switch. Future Puma versions
will be able to automatically write compose content to the Drafts folder after N configurable minutes but this feature is not yet available.
Outbox
The Outbox mailbox folder is the initial folder for all outgoing messages composed from the given AFTN or X.400 User Account. When the user sends a
new message from the Compose Editor, it is first written to the user's Outbox folder, triggering a new message ready event, and if the account has a
socket connection to the UMS/FOX message switch, the message is attempted to be submitted to the switch.
Trash
The Trash folder is the storage folder for all deleted messages or folders associated with the corresponding AFTN or X.400 User Account. All messages
deleted in mailbox folders other than the Trash folder, are moved to the Trash folder and stored indefinitely until they are emptied from the Trash Folder
(or age past the configured purge interval time).
Rejected
The Rejected folder is a storage folder for messages that have been rejected from a message switch. Assuming no software bugs or protocol
errors, there should never be any messages sitting in this folder
Archive
Every message that was received inbound (Inbox) or transmitted outbound (Sent) is first stored into their respective Archive sub-folder. This
satisfies both legal and customer requirement that all messages for a configurable period of time (e.g. 60 days) can be fully audited.
FOLDER / MESSAGE MANAGEMENT

New mail folders can be created under the main account or inside other sub folders except
Archive.

To create a new folder at the same hierarchy level as the default mail folders, as shown in Figure
27:

1. Right-click on the Account node, i.e. top-level folder, ex. LATIAFTB) a. Select New Folder from
popup menu b. The “Create as a sub-folder of:” will have the Account root node selected
(LATIAFTB)
2. Enter Folder Name, ex. ‘NOTAM’
3. Click OK
COMPOSE MESSAGES FROM FORMS

• Compose Editor forms are an integral part of Puma, providing structured form fields for many common message types, such as
NOTAM, SNOWTAM, FPL, ARR, DEP, DLA, CHG, CNL, etc. With Puma release 4.2.0 and purchase of an optional PumaSDK,
customers may also now define their own Forms and cleanly integrate these into the Puma menu, compose and validation
functionality. Please see more details in Section 14 - Customer Defined Forms, regarding customer Form definitions.
• Flight Plan and ATS messages Forms
FPL Figure 56 shows the Puma X.400 Compose Editor Flight Plan (FPL) message form used to compose valid, properly formatted
FPL messages.For Flight Plans that are sent to IFPS, the FPL form may now contain additional “AD” FPL Redistribution AFTN
addresses. To be able to see these lines, the “Tools -> Option >Number of additional AFTN/AD rows for FPL Forms” has to be set
to number higher than 0. For description of Puma Options, see Chapter 12.6
ADDRESS BOOKS

Address Book - Window

The User can view Puma Address Books by selecting "Tools > Address Books" from the main menu bar, or from the Address
Books button. Within Puma there can exist one or more custom Address books to help organize and store Contacts and
Distribution Lists (DL). Future Puma releases will tie into Directory Services such that contact and distribution lists can be
shared across customer base, or possibly even shared globally.The User can select an existing address book and add entries
to it, or to create a new address book.
The User can add new contacts to the Address Book by selecting the New Contact button in the Address Book window. The User
can enter the contact name, AFTN address, and X.400 address in either XF or CAAS format or create only AFTN contact.
 User Accounts are essential in the operation and management
USER ACCOUNTS of messages in Puma, and it is not possible to send/receive
messages without properly configured accounts. After Puma
installation at least one account must be configured before real
Puma usage. The only reason user accounts are discussed this
late in the User Manual is that after initial configuration, it is
very infrequent that a user needs to return and view/edit an
account's configuration. On Puma application start, Puma will
automatically attempt to make socket connections to the set of
configured account servers.Puma will always have at least one
account, and it is not possible to delete below one account.
When Puma is first installed there is a Default Account
automatically created (of type AFTN) which may be configured,
or will automatically be removed if no changes and the user
creates their own account. Either way, there will always be at
least one account.Puma supports multiple account types
simultaneously allowing users to configure one or more
accounts to be accessed via the user’s Mailbox window or
"Tools -> Account Manager". The current types of Puma user
accounts are:
TOOLS MENU BAR
A fundamental methodology within the Puma application is to "remember" the previous action
by a user and attempt to use that information when performing that action the next time.
Remembering items such as previous file name/directory, previous account, last opened window
location and/or size all makes for a better user experience. For example, if the user took the time
to resize a window to a certain size and location, Puma should attempt to use those values the
next time the window is opened.

Even with all the persistence of previous actions, different users have different requirements for
features, work flow, colors, fonts, sounds, keyboard accelerators, etc., and to that end Puma
provides a very rich set of user customization. The following sections discuss the major feature
sets available under the Tools menu bar.
TERIMAKASIH