AOC Message Interface Overview
Document Version: 5.8
Date: September 18, 2014
Copyright © 2009-2021 Jeppesen. All rights reserved. Your use of the AIM Bookshelf and all supporting documentation is subject to a separate license agreement between you and Jeppesen, a copy of which is included in the zip file or can be obtained from Jeppesen. The AIM Bookshelf is delivered "AS IS" without warranty of any kind and is not guaranteed to be free from errors or defects. You rely on the AIM Bookshelf at your own risk. No support for the AIM Bookshelf is implied through its publication. The AIM Bookshelf is intended solely for use as a reference and examples of interfaces to Jeppesen systems. Jeppesen may revise, update or cease publication at any time, without notice. Building to the specifications set forth in the AIM Bookshelf does not mean that your intended integration needs will be met or that an interface will function as documented. We recommend contacting Jeppesen directly to discuss professional services options with respect to production application integration and validation efforts.
Document Revision History
The following revision history table reflects all substantive changes to this document since the previous release.
Table Of Contents
This document discusses the AOC Message format, which defines how every message is "wrapped" and sent through an Airline Operation Center (AOC).
The intended audience for this document includes existing and potential Jeppesen customers, integration partners, and personnel with roles associated with application architecture, application development, system testing, implementation, and application support for the Message Wrapper.
The XML schema for this ICD is published in the following file: AOCMessage.XSD
In order to route messages accurately and effectively each message must be 'wrapped' such that the original message becomes the body and the header contains all the routing information needed by Jeppesen Solution Integrator (JSI).
The JSI wrapper wraps all inter-application and inter-process communications whether request/response, or publish/subscribe. It contains information about the type of message but no information about the content of the message. Such content is contained in the ICD between the sending application and receiving application.
Refer to the Message Overview for additional information concerning the use of this message.
The following table provides details on the message version and includes links to the message’s technical specification.