Web Server Information about the Web Server contained in the POS Web Markup Language Server side tags used in HTML files to control generated HTML Http.ini files General content control for files in directories, auditing, searching and HTTP headers XML, SOAP, APIs Reference information about the XML transactions available in the POS. Transaction Definitions Reference material for transactions and elements. External Processors Information on building an External Processor to extend the internal core operation. FDL Library Direct API library, for alternative POS systems and other applications.

Handhelds How to develop Handheld and Wireless PDA applications. Index Database Controlling POS database interaction, referential integrity and alternative database engines. Storage Tables Details the physical database structures used. The Entity relationship diagrams. Original Documentation Metadata Definition How extended metadata can be defined for complex requirements. Internationalisation How to configure the POS for other countries, or tailor the POS to fit an environment exactly. Index

Internals Internal information on POS architecture. Supplied as background, subject to change without warning. Programs Descriptions of programs in the POS system, including command line options Global Identity Details of how globally unique product identifiers are allocated within the POS. Settings Settings control the broad operating characteristics of the POS Internal Structure Details of the internal structure of the POS and how it operates at a technical level. Crash File Information about the internal structure of crash.out files.

Fieldpine has many different interface techniques, and selecting the right approach for a design is important. The following table quickly summarises the various techniques available.

Direct Database interaction
Advantages Very easy to understand implement POS database can reside in corporate database structure, fully integrated Well suited to simple reading of information.	Disadvantages Need to understand Fieldpine Entity Relationship structure. May not be flexible as new features added. Fieldpine uses the presence of columns and tables to indicate if functionality should be enabled. Updating, may cause performance implications in networked environments.
XML Interface
Advantages Realtime Read and Write access Fully supported	Disadvantages May require 3GL programming tools
FDLLIB Interface
Advantages A simplied version of XML, does not require complete understanding of XML interface The interface technique used by many of Fieldpine Plugins	Disadvantages Applications must be developed in C++ Limited subset of XML
Scripted Reporting
Advantages Quick, easy to understand	Disadvantages Tends to be batch orientated Read Only access
DLL Plugins (External Processor)
Advantages Direct POS interaction - code becomes part of POS and can behave as it is part of the core Retail system Realtime Read and Write access Best choice when your interface needs to react to events as they occur, such as processing Web pages, custom XML interfaces. Fast Can have handles to database for direct access if required. (read only highly recommended)	Disadvantages Must be coded in 3GL Highest support level from customer viewpoint - your code is part of POS code stream