000 06368nam a2200721 i 4500
001 7899155
003 IEEE
005 20200413152923.0
006 m eo d
007 cr cn |||m|||a
008 170418s2017 caua foa 000 0 eng d
020 _a9781627056373
_qebook
020 _z9781627059725
_qprint
024 7 _a10.2200/S00760ED1V01Y201702ICR057
_2doi
035 _a(CaBNVSL)swl00407289
035 _a(OCoLC)982699812
040 _aCaBNVSL
_beng
_erda
_cCaBNVSL
_dCaBNVSL
050 4 _aQA76.9.D3
_bX85 2017
082 0 4 _a005.7565
_223
100 1 _aXu, Hao
_c(Computer scientist),
_eauthor.
245 1 0 _aiRODS primer 2 :
_bintegrated rule-oriented data system /
_cHao Xu, Terrell Russell, Jason Coposky, Arcot Rajasekar, Reagan Moore, and Antoine de Torcy ; Michael Wan, Wayne Shroeder, and Sheau-Yen Chen.
264 1 _a[San Rafael, California] :
_bMorgan & Claypool,
_c2017.
300 _a1 PDF (xv, 115pages) :
_billustrations.
336 _atext
_2rdacontent
337 _aelectronic
_2isbdmedia
338 _aonline resource
_2rdacarrier
490 1 _aSynthesis lectures on information concepts, retrieval, and services,
_x1947-9468 ;
_v# 57
538 _aSystem requirements: Adobe Acrobat Reader.
538 _aMode of access: World Wide Web.
500 _aPart of: Synthesis digital library of engineering and computer science.
505 8 _aA. Exercises -- Short questions -- Essay questions -- Authors' biographies.
505 8 _a6. iRODS microservices -- 6.1 Microservice input/output arguments -- 6.2 About microservices and microservice plugins -- 6.3 Examples -- 6.3.1 The plugin factory -- 6.3.2 The microservice definition -- 6.3.3 Building and installing the example code -- 6.3.4 Testing the microservice --
505 8 _a5. The iRODS rule system -- 5.1 The iRODS rule architecture -- 5.2 Default iRODS rules -- 5.3 Session variables available for default iRODS rules -- 5.4 Dynamic policy enforcement points -- 5.4.1 Flow control -- 5.4.2 Parameter serialization -- 5.4.3 Dynamic pep signatures -- 5.5 Pluggable rule engine architecture -- 5.5.1 Rule engine plugin framework -- 5.5.2 Configuration (server_config.json) -- 5.6 The iRODS rule language -- 5.6.1 Comments -- 5.6.2 Directives -- 5.6.3 Boolean and numeric -- 5.6.4 Strings -- 5.6.5 Dot expression -- 5.6.6 Constant -- 5.6.7 Function -- 5.6.8 Rule -- 5.6.9 Data types and pattern matching -- 5.6.10 Control structures -- 5.6.11 Recovery chain for control structures -- 5.6.12 Types -- 5.6.13 Language integrated general query -- 5.6.14 Path literals -- 5.7 Delay execution -- 5.7.1 Syntax -- 5.7.2 Examples -- 5.8 Remote execution -- 5.8.1 Syntax -- 5.8.2 Examples --
505 8 _a4. Rule-oriented programming -- 4.1 Session state variables -- 4.2 Persistent state information variables --
505 8 _a3. iRODS architecture -- 3.1 Virtualization in iRODS -- 3.2 iRODS components -- 3.3 User environment variables -- 3.4 Configuration files -- 3.4.1 /odbc.ini -- 3.4.2 /.irods/.irodsA -- 3.4.3 /etc/irods/server_config.json -- 3.4.4 /.irods/irods_environment.json -- 3.4.5 Checksum configuration -- 3.4.6 Special characters -- 3.5 Plugin interfaces -- 3.5.1 Pluggable microservices -- 3.5.2 Composable resources -- 3.5.3 Pluggable authentication -- 3.5.4 Pluggable network -- 3.5.5 Pluggable database -- 3.5.6 Pluggable RPC API -- 3.5.7 Pluggable rule engine -- 3.6 Example plugins -- 3.6.1 Composable resources -- 3.6.2 Pluggable authentication --
505 0 _a1. Introduction --
505 8 _a2. Integrated rule-oriented data system -- 2.1 Data grid overview --
506 _aAbstract freely available; full-text restricted to subscribers or individual document purchasers.
510 0 _aGoogle book search
510 0 _aGoogle scholar
510 0 _aINSPEC
510 0 _aCompendex
520 3 _aPolicy-based data management enables the creation of community-specific collections. Every collection is created for a purpose. The purpose defines the set of properties that will be associated with the collection. The properties are enforced by management policies that control the execution of procedures that are applied whenever data are ingested or accessed. The procedures generate state information that defines the outcome of enforcing the management policy. The state information can be queried to validate assessment criteria and verify that the required collection properties have been conserved. The integrated Rule-Oriented Data System implements the data management framework required to support policy-based data management. Policies are turned into computer actionable Rules. Procedures are composed from a microservice-oriented architecture. The result is a highly extensible and tunable system that can enforce management policies, automate administrative tasks, and periodically validate assessment criteria. iRODS 4.0+ represents a major effort to analyze, harden, and package iRODS for sustainability, modularization, security, and testability. This has led to a fairly significant refactorization of much of the underlying codebase. iRODS has been modularized whereby existing iRODS 3.x functionality has been replaced and provided by small, interoperable plugins. The core is designed to be as immutable as possible and serve as a bus for handling the internal logic of the business of iRODS. Seven major interfaces have been exposed by the core and allow extensibility and separation of functionality into plugins.
530 _aAlso available in print.
588 _aTitle from PDF title page (viewed on April 18, 2017).
650 0 _aDatabase management
_xComputer programs.
650 0 _aiRODS (Computer system)
653 _amicroservices
653 _apolicies
653 _aassessment criteria
653 _ametadata catalog
653 _apolicy-based data management
653 _arule engine
653 _aiRODS
653 _apreservation environment
653 _adigital library
653 _adata grid
653 _adata life cycle
776 0 8 _iPrint version:
_z9781627059725
830 0 _aSynthesis digital library of engineering and computer science.
830 0 _aSynthesis lectures on information concepts, retrieval, and services ;
_v# 57.
_x1947-9468
856 4 2 _3Abstract with links to resource
_uhttp://ieeexplore.ieee.org/servlet/opac?bknumber=7899155
999 _c562253
_d562253