Horizon Advanced

Administration Training
Web Service History
 Title
Web Service History
Enabling Web Service History in Jboss AS 7
To enable Web Service History, Go to Admin Page -> Parameters.
Next, add row containing these fields (history | enable | true).

How to enable History INIT

To enable History INIT, Go to Admin Page -> Parameters.
Next, add a row containing these fields (history | init | yes).

Finally, restart Jboss to create data on the entities aud.

 Title
Web Service History
How to enable History INIT
An indication on the logs will be seen if the History Initialization is
successful.
 Title
Web Service History
History Entities
can be requested via web service of a REST format.
request is made through an HTTP GET command with query parameters
that specify the requested entity and the modification date.
the feedback/response is in JSON format
 Title
Web Service History
Access to the Service
via a unique URL supplemented by query parameters.
The URL has a format:
server_address/PCC4/History?Entity=entity_name&startdate=epoch_date

server_address address of the application server

entity_name name of the entity requested

epoch_date The start date of the query period, in epoch

format (number of milliseconds since
January 1, 1970).
 Title
Web Service History
Structure of the Response
the response, in JSON format, has a well-defined structure.
The data includes global attributes, including other data on the requested
entity
The overall structure is as follows:
 Title
Web Service History
Definitions:
entity_name - name of the requested entity
nb_operations - number of operations contained in the response
date_of_revision - clear date of the modification
TYPE_OPERATION – INIT, CREATE, CHANGE, REMOVE
entity_attributes – list of entity attributes
epoch_date_of_revision – revision date, in epoch format

The return format includes a fixed part and a part that depends on the
requested entity.
 Title
Web Service History
Errors in Return
SC_NOT_FOUND (404) – Missing parameters
SC_NOT_IMPLEMENTED (501): Undefined entity
SC_INTERNAL_SERVER_ERROR (500): error when generating data
 Title
History Entity Attributes
Fleet
id: group key in the db
name: name of the group
parent_fk: parent key in the db

Operator
id: operator key in the db
name: user name
login: username
LMNET_ID: Operator radio identifier

Zone_Level
id: zone level key in the db
name: name of the zone level
tree_level: level in hierarchy
 Title
History Entity Attributes
Product_Group
id: group key
name: name of the group
State
id: status key
name: name of the state
color: color coding associated with the state
Product
id: product key
name: product name
Lmnet_Name: radio ID
Prod1_ID: key of the 1st component product
Prod2_ID: key of the 2nd component product
{product_group list}: list of keys for groups containing the product
 Title
History Entity Attributes
Zone
id: product key
altitude: altitude of the zone
expired: expiration date of the zone
super_zone_id: key for the parent zone
zone_level_id: zone level key
name: name of the zone
lmnet_label: radio identifier

Equipment
id: key of the equipment
LMNET_ID
out_of_order
hours_control
type – Camions : tonnage, useNominal
− Pelle/Chargeuse: tonnage, loader_type
− Bull
− Foreuse
 Title
History Entity Attributes
History Table
For entities not attached to a stream, the history is saved in tables in the
main database.
For entities attached to a stream, the history is saved in tables in the
storage database.
For the history of Q_Event, both to an entity defined by a table and
attached to a stream, the history is saved in the main database
The history tables that have the same name as the base entity, with the
suffix _AUD (i.e CYCLE_AUD), are saved in the main database
For the horameters, which are technical data, the history is saved in the
data_AUD table of the main storage.
Thank you!
Logimine S.A.S.
Nîmes, France

Logimine NC.
La Foa, Nouvelle-Calédonie

Logimine Asia Inc.

Davao City, Philippines

Logimine Inc.
Montréal, Canada

info@logimine.com www.logimine.com

Back to Main Page