index.html The Company of The Virtual Business Platform
Home Products Services News Contact us
Semantion Registry and Repository 3.1
 
 
 

Semantion Registry and Repository 3.1 is a J2EE component-based registry that implements OASIS/ebXML Registry standard.

Semantion Registry supports web browser clients, SOAP-based XML messaging clients, and Java clients. In a combination with the Semantion Gateway and Semantion Federation Manager (components of the Semantion SOA Virtual Machine), it also supports JMS clients. It can run on a single machine or distributed over as many machines as needed to meet customers’ processing needs. Because of its very flexible architecture, it is suitable for registry installations of any size. Semantion Registry and Repository 3.1

  • runs on Windows, UNIX, and Linux platforms,
  • runs on JBoss application server,
  • supports Oracle database management system.

The main features supported by Semantion Registry and Repository are:

  • Enables definition of any business entity
  • .
  • Data, documents, and images classifications.
  • Search for meta-data, documents, and images.
  • SOAP, REST (Representational State Transfer), and JMS communication interfaces/providers.
  • Secured registry and repository communication supported by XML signature (integrated into the registry and repository security), SSL, XACML, and other security solutions.
  • Versioning.
  • Configurable automatic email notification for all registry and repository changes.
  • Flexible configuration via an XML configuration file.
  • Legacy systems integration.

 
Architecture

Semantion Registry and Repository multi-tier architecture includes:

  • Client Tier
  • Web Tier
  • Enterprise JavaBeans (EJB) Tier
  • Enterprise Information Systems Tier

Figure 1: Semantion Registry and Repository 3.1 Architecture
 
 

Client tier supports Web (browser) clients, SOAP-enabled clients, REST clients, and RS/RIM clients. Web clients fully support Web browser registry access. SOAP-enabled clients can send SOAP messages with OASIS/ebXML Registry Services requests to the registry. Semantion Registry replies with a SOAP message containing an OASIS/ebXML Registry Services response. REST clients access the registry via the REST Provider that supports HTTP Binding specified in OASIS/ebXML Registry Services 2.6 specification. RS/RIM clients are Java clients implemented in Semantion RS 3.1 and Semantion RIM 3.1 APIs. Semantion RS 3.1 fully implements both LifeCycleManager and QueryManager OASIS/ebXML Registry Services 2.1 interfaces while Semantion RIM 3.1 fully implements OASIS/ebXML Registry Information Model 2.1. RS/RIM clients should access Semantion Registry and Repository by Semantion RS 3.1 APIs only. You should not directly access Semantion Registry and Repository by RIM 3.1 APIs. Semantion does not support Semantion Registry and Repository if it is directly accessed by RIM.

Web tier includes Registry Controller, Query Controller, SOAP-based Provider, and REST Provider. Registry Controller accepts client requests and dispatches them to the appropriate registry component: Query Controller or RegistryService. Query Controller generates all query requests based on end-user inputs from Web browser clients and sends them to the RegistryService that calls QueryManager to process the query. Registry Controller submits all other registry requests to the RegistryService directly. SOAP (XML Messaging) Provider is the Semantion implementation of the registry XML messaging based on SOAP with Attachments API for Java (SAAJ). REST Provider implements all three HTTP Binding options specified in OASIS/ebXML Registry Services 2.6 specification: RPC Encoding URL, Submitter Defined URL and File Path Based URL.

Enterprise JavaBeans (EJB) tier is EJB 2.0 based. It includes RegistryService, LifeCycleManager, QueryManager, RepositoryManager, and Semantion RIM 3.1. RegistryService is included in Semantion MainService 3.1 component. It is an EJB session bean that controls access to the EJB tier. It also transforms registry requests from XML to Java and registry responses from Java to XML. Semantion uses ExoLab Castor API to implement XML to Java and Java to XML transformations. LifeCycleManager and QueryManager are EJB session beans that belong to Semantion RS 3.1 component. RepositoryManager is an EJB session bean that belongs to Semantion Repository 3.1 component. LifeCycleManager uses Semantion RIM 3.1 for Semantion Registry database access and RepositoryManager for Semantion Repository access. It supports the following registry operations: submit, update, remove, approve, and deprecate. Semantion RIM 3.1 is a full implementation of the OASIS/ebXML Registry Information Model 2.1. It is implemented in EJB container-managed persistent (CMP) entity beans. It also includes Semantion Java UUID Generator 1.0 that generates universally unique identifiers that conform to the format of a URN that specifies the OSF DCE 128 bit UUID. Semantion Java UUID Generator uses E2fsprogs utility to generate the OSF DCE 128 bit UUID. QueryManager is an EJB session bean that fully implements OASIS/ebXML Registry Services 2.1 filter queries and SQL query. RepositoryManager fully implements Semantion Repository access interface that includes the following repository item operations: insert, update, remove, and get. File System (FS) RepositoryManager is currently supported.

Enterprise Information Systems (EIS) tier includes Semantion Registry database(s), Semantion Repository, Enterprise Resource Planning (ERP) systems, Customer Relationship Management (CRM) systems, Supply Chain Management (SCM) systems, mainframe transaction processing systems, and legacy database systems. ebXML Registry meta-data is stored in the Semantion Registry database. Business documents and images are stored in the Semantion Repository. SOAP messaging, Semantion RS, Semantion RIM, and J2EE Connector architecture can be used for registry integrations with legacy systems (ERP, CRM, SCM, etc.).

 
 
Semantion Registry Developer Pack (SRDP) 2.4
 

Semantion Registry Developer Pack (SRDP) 2.4 is bundled with Semantion Registry and Repository 3.1. It includes the following Semantion APIs:

  • Semantion RIM 3.1 (OASIS/ebXML Registry Information Model Specification implementation),
  • Semantion RS 3.1 (OASIS/ebXML Registry Services Specification implementation),
  • Semantion Repository 3.1 (Semantion Repository Manager implementation),
  • Semantion MainService 3.1 (implements a full registry service access to Semantion Registry),
  • Semantion Messaging 3.1 (a SOAP client API with attachments), and
  • Semantion Util 3.1 (Semantion utilities),

Semantion RIM 3.1 is a J2EE software that fully implements the OASIS/ebXML Registry Information Model (RIM) Specification. Semantion RIM 3.1 is implemented in EJB container-managed persistent (CMP) entity beans. It works with any database management system that is supported by your J2EE Application Server. Semantion RIM 3.1 also includes Semantion Java UUID Generator 1.0 that generates universally unique identifiers that conform to the format of a URN that specifies the OSF DCE 128 bit UUID.

Semantion RS 3.1 fully implements both LifeCycleManager and QueryManager, OASIS/ebXML Registry Service interfaces. It also supports digital signature and web-based authentication/authorization security. Semantion RS 3.1 is designed to be secure, reliable, and scalable, thus making it a solid foundation for robust ebXML Registries that will support global business information exchange. LifeCycleManager and QueryManager are EJB session beans. LifeCycleManager uses Semantion RIM 3.1 for Semantion Registry database access. It supports the following registry operations: submit, update, remove, approve, deprecate, and add/remove slot operations. QueryManager is an EJB session bean that fully implements OASIS/ebXML Registry Services filter queries and SQL query.

Semantion Repository 3.1 implements repository interface that includes the following repository item operations: insert, update, remove, and get.

Semantion MainService 3.1 implements a full registry service access to the Semantion Registry and Repository. Using just few standard high level methods, you can program a full access to the registry with just few lines of code.

Semantion Messaging 3.1 is a SOAP client component that supports SOAP communication with the Registry. SOAP attachments that enables you to send and receive business documents are supported as well.

Semantion Util 3.1 includes common Semantion utility classes.

 
 
 
 

Copyright © 2001-2007 Semantion Inc. All rights reserved.
FERA-based SOA, Semantion, CPID, Semantion Registry, Semantion SRDP, Semantion RIM, and Semantion RS are trademarks or registered trademarks of Semantion Inc. in Canada and other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.