Projet

Général

Profil

« Précédent | Suivant » 

Révision 96454bcd

Ajouté par Sylvain Sauvage il y a presque 13 ans

Version 1.9-mock

This is version 1.9-mock. 1.9 because the API still have changes pending
(principally relative to the Discovery Services). “mock” because TLS
configuration is not yet available and the signatures (SigMa) are not fully
implemented.

  • All:
    - code cleaned and refactored
    - lots of bugs fixed
    - dependencies checked and trimmed
    - documentation added
    - Identity handling added
  • New library modules (Mu, Nu)
  • New signature modules (SigMa)
  • Access Layer and User interfaces (ALfA and OMeGa):
    - code refactored
    - new, better APIs
    - Identity handling added
    - use EPCglobal and DS events (no proxy types anymore)
  • New tempororay DSeTa web service (pending new DS)
  • ETa corrected and added to the IoTa-Installer
    - ETa-Callback modules are now available as web applications
    - filtering rules: if a part of an event is not allowed, now the whole
    event is deleted from the result (before only the rejectd part was)
  • CaPPa: overall refactoring of XACML handling
    - new temporary User web service
    - new Xi module: XACML Interrogation web service (was two modules: TCP and
    servlet)
  • PSi now signs its events
  • Installer, now also installs or configures:
    - ETa and its Callback modules
    - ActiveMQ
    - SigMa
    - certificate/signing key
  • Greyc letters figures:
    - new simplified figures (sans IoTa and simplified IoTa)
    - new figure for ETa modules
    - show 3rd party clients
    - data flows specified
    - TLS and link security added
    - IDs and trusted IDs added
    - color adjusted for printing
    - GREYC logo added

Voir les différences:

INSTALL
IoTa uses Apache Maven for build automation (http://maven.apache.org).
A convenience building script is provided: make-all.sh.
Compilation of each module is achieved with this command:
mvn compile
......
(All bracketted values `<name>` are place-holders.)
The IoTa-Installer can help you install and configure all the servers and
databases.
**The IoTa-Installer can help you to install and configure all the servers and
databases.**
All the applications and web applications have a `log4j.properties` file to
configure the logging output (file output, log format, log level, and so on).
......
unzip <application>-<version>.jar application.properties
Use the provided script to start the application:
./launch.sh
Use the provided script to start the application.
### Web Applications
......
$TTL 1d
;; zone, the vendor Id
$ORIGIN 7.6.5.4.3.2.1.sgtin.ons-peer.com.
$ORIGIN 7.6.5.4.3.2.1.sgtin.id.ons-peer.com.
@ IN SOA localhost info.example.com ( ; info@example.com
2012010101 ; serial version number
......
)
;; this server’s name
IN NS ons.example.com
IN NS ons.example.com.
; NAPTRs for products
; example product
; order pref flags service regex
2.1.0.9.8 IN NAPTR 0 0 "u" "epc+html" "!^.*$!http://www.example.com/!" .
IN NAPTR 1 0 "u" "epc+ds" "!^.*$!http://ds.example.com/ds/services/ESDS_Service!" .
IN NAPTR 1 0 "u" "epc+epcis" "!^.*$!http://epcis.example.com/epcis/!" .
IN NAPTR 2 0 "u" "epc+ided_epcis" "!^.*$!http://epcis.example.com/eta/!" .
IN NAPTR 3 0 "u" "epc+ds" "!^.*$!http://ds.example.com/ds/services/ESDS_Service!" .
IN NAPTR 4 0 "u" "epc+ds" "!^.*$!http://ds.example.com/dseta/ds/!" .
IN NAPTR 5 0 "u" "epc+ided_ds" "!^.*$!http://ds.example.com/dseta/ided_ds/!" .
; first, the HTML web page for product information
; second, the Discovery web service associated to this EPC
; then, the EPCIS-repository web service associated to this EPC
; then, the identified EPCIS-repository (ETa) web service associated to this EPC
; then, the Discovery web service associated to this EPC (WINGS version)
; then, the Discovery web service associated to this EPC
; finally, the identified Discovery web service associated to this EPC
; the order is free
On Debian and Debian-derived systems, you just need to install the `bind9`
package, to create one or more zone file as the cited example and to activate
those zones, that is to add that kind of statement in `named.conf.local`:
zone "7.6.5.4.3.2.1.sgtin.ons-peer.com" {
zone "7.6.5.4.3.2.1.sgtin.id.ons-peer.com" {
type master;
file "/etc/bind/db.ons.peer.com";
};
......
Remember that in order to avoid a recursive open relay DNS, you need to add
these options (in the `options` statement of `named.conf.options`):
allow-transfer { none };
allow-recursion { none };
allow-transfer { none; };
allow-recursion { none; };
recursion no;
### DNSSEC
Enable DNSSEC in bind9 with these options (in the `options` statement of
`named.conf.options`):
dnssec-enable yes;
dnssec-validation auto;
dnssec-lookaside auto;
You can generate keys and sign your zone files with, for example, the program
`zonesigner` from `dnssec-tools`.
### LDAP
Some applications (ETa) need an LDAP server.
......
On Debian and Debian-derived systems, you just need to install the packages
`slapd` and `ldap-utils`. You have to execute `dpkg-reconfigure slapd` in
order to complete the configuration.
### ActiveMQ
Some applications (ETa-Callback*) need an ActiveMQ JMS broker.
On Debian and Debian-derived systems, you just need to install the package
`activemq`.
### Memory Issues
Due to extensive introspection (e.g. by Hibernate or CXF), and if you want to
install all the web applications on the same server, the JVM “PermGen” memory
needs to be increased. For Apache Tomcat, it can be done with the environment
variable JAVA_OPTS. In POSIX shells, that can be done by a command like the
following one:
export JAVA_OPTS='-Xms2048m -Xmx4096m -XX:MaxPermSize=512m'
This environment variable needs to be set before starting Apache Tomcat hence
before starting the IoTa installer (as the IoTa installer starts Apache
Tomcat).
This is only necessary if you install all (or most of) the web applications in
the same servlet container.

Formats disponibles : Unified diff