One Network Platform - Server API
API specification for the One Network Platform Server. The One Network Platform Server APIs facilitates the development of modular, multi-party networks. The API is divided into the following areas:
|Common, shared persistent models and related objects|
|Services for reading and writing data from the database, including both low-level SQL access and high-level Model reads and writes|
|Describes the operating environment, including what modules are deployed, a service locator, access to a shared filesystem, etc.|
|Grid computing infrastructure for parallel task execution|
|Integration support, including REST, asynchronous messaging and notifications|
|Incremental eXecution Management engine for horizontally scalable planning algorithms|
|Miscellaneous tools for development and deployment|
|Supports the implementation of workflows to manage the lifecycle of Models|
Support for a generic, international Address.
Allows one to attach an arbitrary number of "notes" to a Model, similar to a discussion thread on a forum.
Service and interface for currency conversion.
Types and utilities related to Date handling.
Contains enumerations available in enumerated field types for all models.
Provides a simple pub/sub mechanism, allowing Modules to collaborate in a synchronous, loosely-coupled fashion.
Standard interfaces for representing a "Field": a typed, named piece of data.
Services and interfaces for manipulating menus in the user interface.
Contains utilities used in Module development.
Contains services for interacting with a "payment gateway" for charging customers (for example: stripe.com).
Contains data models which support PaymentGatewayService.
Service and interface for filtering global screen elements from UI.
Standard interfaces for manipulating tabular data.
Supporting classes related to the "Task" and "TaskReqmt" models.
Contains services for interacting with a "tax provider" which computes appropriate taxes based on government regulations.
Service and interface for converting between different units of measure.
Objects to represent and manipulate user credentials and preferences.
APIs for reading and writing Models developed with the SDK.
Interfaces and helper classes for implementing customized permission policies on Models.
Services and supporting classes for the persistence and retrieval of module "policies" which drive application behavior.
Services for ad-hoc querying and other lower-level database access.
Interface for loading data using a template file and variable bindings.
"tlv" is short for TimeLine View - this package contains interfaces into the data fetched for a Timeline view in the user interface.
Provides services which allow end-users to define "validation rules" with Excel-like function syntax.
Provides information about the environment into which Platform is deployed.
Provides services and annotations for dependency-injection support with Spring.
Provides reusable annotations for commonly used Component variants.
Event message for Enterprise Process Template.
APIs used to introspect SDK Modules.
Simple service locator for acquiring instances of Platform service interfaces.
Interface into One Network's Computational Grid for parallel, dependency-aware task execution.
Service for scheduling background jobs.
Common interfaces and utilities for used in integration.
Supports the manipulation of CSV data - typically used in the context of inbound integration.
Used for parsing, processing and generating EDI messages in X12 and/or EDIFACT format.
Service for parsing "fixed-length format" files, i.e.
Service for converting between JSON and Model objects.
Provides classes for interacting with other Modules in a loosely-typed way (without adding explicit compile-time dependencies).
APIs for using Platform's message queuing system.
Services for sending email notifications.
Service for integrating to external services through OAuth.
Push technology describes a style of Internet-based communication where the request for a given transaction is initiated by the server, not by the client.
Infrastructure for implementing REST-ful web services using JAXRS.
REST annotations, used primarily for documentation purposes when running the "rest-doc" target in ant.
Standard JSON value objects passed in REST calls in standard Platform components, such as the the Report panel.
Helper classes related to the Model Create/Detail framework, providing support for manipulating model view/action invocation results prior to returning to the client layer.
Helper classes related to the "Network Widget" component in Command Center.
Helper classes related to Problems, providing support for manipulating problem-related queries prior to returning to the client layer.
Helper classes related to the Report framework, providing support for manipulating report invocation results prior to returning to the client layer.
Helper classes related to the Model Templates feature, providing support for manipulating template invocation results prior to returning to the client layer.
Used for parsing, processing and generating SAP "IDoc" files.
Infrastructure for implementing SOAP-based web services using JAXWS.
Service for converting between XML and Java Objects.
Interface into One Network's Intelligent eXecution Manager - leverages the Grid architecture to implement incremental planning algorithms.
Utilities for creating & manipulating java collections.
Classes for implementing Stateless Session Beans in Platform.
Provides access to internationalized messages.
Utilities for manipulating java streams and other I/O classes.
Extensions of log4j used for logging in Platform.
Classes for implementing automated unit and functional test cases (both inside and outside the container).
Includes following rules:
Utilities supplementing the Hamcrest testing framework.
A library of classes representing widgets in a Command Center user interface.
Utilities related to time and calendars.
Services to facilitate the implementation of model workflows.