Enterprise JavaBeans Research Articles

An Implementation Suite for a Hybrid Public Key Infrastructure

Public key infrastructure (PKI) plays a fundamental role in securing the infrastructure of the Internet through the certification of public keys used in asymmetric encryption. It is an industry standard used by both public and private entities that costs a lot of resources to maintain and secure. On the other hand, identity-based cryptography removes the need for certificates, which in turn lowers the cost. In this work, we present a practical implementation of a hybrid PKI that can issue new identity-based cryptographic keys for authentication purposes while bootstrapping trust with existing certificate authorities. We provide a set of utilities to generate and use such keys within the context of an identity-based environment as well as an external environment (i.e., without root trust to the private key generator). Key revocation is solved through our custom naming design which currently supports a few scenarios (e.g., expire by date, expire by year and valid for year). Our implementation offers a high degree of interoperability by incorporating X.509 standards into identity-based cryptography (IBC) compared to existing works on hybrid PKI–IBC systems. The utilities provided are minimalist and can be integrated with existing tools such as the Enterprise Java Bean Certified Authority (EJBCA).

효율적인 데이터베이스 마케팅을 위한 데이터마이닝 전처리도구에 관한 연구

Abstract This paper is to construction of the data mining preprocessing tool for efficient database marketing. We compare and evaluate the often used data mining tools based on the access method to local and remote databases, and on the exchange of information resources between different computers. The evaluated preprocessing of data mining tools are Answer Tree, Climentine, Enterprise Miner, Kensington, and Weka. We propose a design principle for an efficient system for data preprocessing for data mining on the distributed networks. This system is based on Java technology including EJB(Enterprise Java Beans) and XML(eXtensible Markup Language). Key Words : Big data, Data Mining, Data Mining Tool, Preprocessing, Database Marketing * 본 연구는 2009년도 동남보건대학교 연구비 지원에 의하여 수행된 것임Received 16 September 2014, Revised 26 October 2014Accepted 20 November 2014Corresponding Author: Jun-Seok Lee(Dongnam Health University) Email: jslee@dongnam.ac.krⒸ The Society of Digital Policy & Management. All rights reserved. This is an open-access article distributed under the terms of the Creative Commons Attribution Non-Commercial License (http://creativecommons.org/licenses/by-nc/3.0), which permits unrestricted non-commercial use, distribution, and reproduction in any medium, provided the original work is ISSN: 1738-1916 properly cited.

An implementation of enhanced public key infrastructure

In this paper, we present the implementation of an enhanced public key infrastructure (PKI) which supports not only conventional public key cryptography (PKC) but also identity-based cryptography (IBC). In addition, we discuss the possible way of placing together IBC and PKI as well as solving the problems of user secret key revocation of PKI and IBC. As a proof of concept, an IBC framework is incorporated into Enterprise Java Bean Certified Authority (EJBCA) and the performance is reported.

EJB 3.0과 EJB 3.1의 소프트웨어 개발 생산성 비교 연구

Abstract The purpose of this study is to provide a quantitative evaluation index of object-oriented software development productivity for EJB 3.0 and EJB 3.1. A lightweight container architecture is a newly-developed architecture in order to solve demerits that N-Tiers enterprise architecture has and to support merits therein. A lightweight container architecture is not as heavy as EJB(Enterprise JavaBeans) architecture is, whereas it provides all the functionality of the EJB container. However, there have been insufficient studies on a performance evaluation of EJB 3.0 and EJB 3.1 on an identical platform. Since a quantitative analysis has been performed only with respect to a partial LoC(Line of Code) analysis, there have been insufficient objective evaluation indeces and guidelines for a new specification released. Accordingly, there has been limited evaluation of software development productivity and on new innovations in a project. Therefore, this study designed and implemented a movie reservation system in EJB 3.0 and EJB 3.1, which was based on the same development platform environment. This study then intends to provide evaluation guidelines for an objective software development productivity cl LoC(Lineand standardization thereof by development platform environment.

A highly scalable, interoperable clinical decision support service

To create a clinical decision support (CDS) system that is shareable across healthcare delivery systems and settings over large geographic regions. The enterprise clinical rules service (ECRS) realizes nine design principles through a series of enterprise java beans and leverages off-the-shelf rules management systems in order to provide consistent, maintainable, and scalable decision support in a variety of settings. The ECRS is deployed at Partners HealthCare System (PHS) and is in use for a series of trials by members of the CDS consortium, including internally developed systems at PHS, the Regenstrief Institute, and vendor-based systems deployed at locations in Oregon and New Jersey. Performance measures indicate that the ECRS provides sub-second response time when measured apart from services required to retrieve data and assemble the continuity of care document used as input. We consider related work, design decisions, comparisons with emerging national standards, and discuss uses and limitations of the ECRS. ECRS design, implementation, and use in CDS consortium trials indicate that it provides the flexibility and modularity needed for broad use and performs adequately. Future work will investigate additional CDS patterns, alternative methods of data passing, and further optimizations in ECRS performance.

I2SD: reverse engineering Sequence Diagrams from Enterprise Java Beans with interceptors

An Enterprise JavaBeans (EJB) interceptor is a software mechanism that provides for introducing behaviour implemented as separate code into the execution of a Java application. In this way, EJB interceptors provide a clear separation of the core functionality of the bean and other concerns, such as logging or performance analysis. Despite the beauty of the idea behind the i nterceptors, developing, testing and managing dependencies introduced by the interceptors are considered to be daunting tasks. For example, the developers can specify interceptors at multiple locations and by multiple means. However, different locations and specification means influence the order of the interceptor invocation, which is governed by more than 15 different intertwined rules defined in the EJB standard. To facilitate development of EJB applications, we have designed I2SD, Interceptors to Sequence Diagrams, a tool for reverse engineering EJB applications with interceptors to unified modeling language (UML) sequence diagrams. I2SD provides the developer with a visual feedback and can be used by quality managers to obtain insights in the ways interceptors are used in their project.

Transformation contracts in practice

Model-driven development (MDD) is a software engineering discipline which suggests that software development should be done at the modelling level and that applications should be generated from models. A key concept of MDD is a model transformation that generates software artifacts, such as code, from models. Since models are `first-class` citizens in MDD, their verification and validation are important tasks and so are the model transformations. A transformation contract, which is also a model, is a specification of what a particular model transformation must implement and essentially specifies a relation between metamodels and properties that must hold on such a relation. The authors have defined a design pattern that enforces transformation contract correctness over model transformations implementations. This study reports on (i) the proposed design pattern, (ii) the design of the UMLtoEJB model transformation that generates application code, following the Enterprise Java Beans standard, from class diagrams described in the Unified Modelling Language, and (iii) a discussion on how the transformation contracts approach may help different actors, in an MDD software development process with transformation contracts, to identify erroneous situations.

A language to bridge the gap between component-based design and implementation

Since years, multiple researches studied component-based software development. Nevertheless, most component-based software systems do not use components at implementation stage. We believe that one of the main causes is a lack of support for component-oriented programming (COP). Indeed, most of the proposed component models such as Unified Modeling Language (UML), Corba Component Model (CCM), Enterprise JavaBeans (EJB) are only available at design time. The fact that implementation relies on object-oriented languages which prevent developers from fully switching to COP. In this paper, we identify five important requirements (decoupling, adaptability, unplanned connections, encapsulation and uniformity) for COP based on an analysis of the state of the art and the limitations of existing work. We propose an extended version of the Scl component language that fulfills these requirements. A prototype of Scl and a concrete experiment validate this proposal.

Building safe PaaS clouds: A survey on security in multitenant software platforms

This paper surveys the risks brought by multitenancy in software platforms, along with the most prominent solutions proposed to address them. A multitenant platform hosts and executes software from several users (tenants). The platform must ensure that no malicious or faulty code from any tenant can interfere with the normal execution of other users’ code or with the platform itself. This security requirement is specially relevant in Platform-as-a-Service (PaaS) clouds. PaaS clouds offer an execution environment based on some software platform. Unless PaaS systems are deemed as safe environments users will be reluctant to trust them to run any relevant application. This requires to take into account how multitenancy is handled by the software platform used as the basis of the PaaS offer. This survey focuses on two technologies that are or will be the platform-of-choice in many PaaS clouds: Java and .NET. We describe the security mechanisms they provide, study their limitations as multitenant platforms and analyze the research works that try to solve those limitations. We include in this analysis some standard container technologies (such as Enterprise Java Beans) that can be used to standardize the hosting environment of PaaS clouds. Also we include a brief discussion of Operating Systems (OSs) traditional security capacities and why OSs are unlikely to be chosen as the basis of PaaS offers. Finally, we describe some research initiatives that reinforce security by monitoring the execution of untrusted code, whose results can be of interest in multitenant systems.

Analysis of ANSI RBAC Support in EJB

This paper analyzes access control mechanisms of the Enterprise Java Beans (EJB) architecture and defines a configuration of the EJB protection system in a more precise and less ambiguous language than the EJB 3.0 standard. Using this configuration, the authors suggest an algorithm that formally specifies the semantics of authorization decisions in EJB. The level of support is analyzed for the American National Standard Institute’s (ANSI) specification of Role-Based Access Control (RBAC) components and functional specification in EJB. The results indicate that the EJB specification falls short of supporting even Core ANSI RBAC. EJB extensions dependent on the operational environment are required in order to support ANSI RBAC required components. Other vendor-specific extensions are necessary to support ANSI RBAC optional components. Fundamental limitations exist, however, due to the impracticality of some aspects of the ANSI RBAC standard itself. This paper sets up a framework for assessing implementations of ANSI RBAC for EJB systems.

Integrated Design Supporting Business Model Stability

Enterprise JavaBeans(EJB) is Java’s component architecture for server-side distributed enterprise applications. The architecture of EJB applications is based on well-established solutions common to most distributed business systems. To utilize the architecture in an optimal way, we gave a layered and integrated optimization method based on mixed design patterns to reduce the coupling degree among tiers, classified the application architecture of the system. It reduced greatly the number of lookup JNDI and remote-calling, reduces the overhead of system and networks. It improve the extensibility and reusability of system. An example was given at last.

Web Oriented System Supporting Small-Medium Sized Manufacturers

. Small and medium sized manufacturing enterprises (SMEs) are challenged with the task of producing customized products in a timely and cost-effective manner. Winning competitive advantage is an imperative strategy for SMEs to compete with large sized organizations. The purpose of this research is to establish a Web oriented system to help SMEs to gain a competitive position with particular focus on the issues of product life cycle, supplier selection and product design specification. This is achieved by integrating three models, including Customer-Manufacturer-Competitor Orientation Analysis, Strategy-Position based Supplier Selection, and Component Based Partial Product Design Specification, into the system with the support of Web techniques including Enterprise Java Beans (EJB), JSP, Java Servlet, Java application, etc.

Architectural Approaches for HL7-based Health Information Systems Implementation

Information systems integration is hard, especially when semantic and business process interoperability requirements need to be met. To succeed, a unified methodology, approaching different aspects of systems architecture such as business, information, computational, engineering and technology viewpoints, has to be considered. The paper contributes with an analysis and demonstration on how the HL7 standard set can support health information systems integration. Based on the Health Information Systems Development Framework (HIS-DF), common architectural models for HIS integration are analyzed. The framework is a standard-based, consistent, comprehensive, customizable, scalable methodology that supports the design of semantically interoperable health information systems and components. Three main architectural models for system integration are analyzed: the point to point interface, the messages server and the mediator models. Point to point interface and messages server models are completely supported by traditional HL7 version 2 and version 3 messaging. The HL7 v3 standard specification, combined with service-oriented, model-driven approaches provided by HIS-DF, makes the mediator model possible. The different integration scenarios are illustrated by describing a proof-of-concept implementation of an integrated public health surveillance system based on Enterprise Java Beans technology. Selecting the appropriate integration architecture is a fundamental issue of any software development project. HIS-DF provides a unique methodological approach guiding the development of healthcare integration projects. The mediator model - offered by the HIS-DF and supported in HL7 v3 artifacts - is the more promising one promoting the development of open, reusable, flexible, semantically interoperable, platform-independent, service-oriented and standard-based health information systems.

Enhancing E-Service Collaboration with Enforcement and Relationship Management

In a business-to-business (B2B) e-service environment, cross-organizational collaboration is important for attaining the interoperability of business processes and their proper enactment. The authors find that B2B collaboration can be divided into multiple layers and perspectives, which has not been adequately addressed in the literature. Besides regular e-service process enactment, robust collaboration requires enforcement, while quality collaboration involves relationship management. These problems are challenging, as they require the enactment of business processes and their monitoring in counter parties outside an organization’s boundary. This paper presents a framework for B2B process collaboration with three layers, namely, collaboration requirements layer, business rule layer, and system implementation layer. The collaboration requirements layer specifies the cross-organizational requirements of e-service processes. In the business rule layer, detailed knowledge of these three types of process collaboration requirements is defined as business rules in a unified Event-Condition-Action (ECA) form. In the system implementation layer, event collaboration interfaces are supported by contemporary Enterprise JavaBeans and Web Services. Based on this architecture, a methodology is presented for the engineering of e-service process collaboration from high-level business requirements down to system implementation details. As a result, B2B process collaboration can be seamlessly defined, enacted, and enforced. Conceptual models of various layers are given in the Unified Modeling Language (UML). We illustrate the applicability of our framework with a running example based on a supply-chain process and evaluate our approach from the perspective of three main stakeholders of e-collaboration, namely users, management, and systems developers.

Version management and composition of software components in different phases of software development life cycle

The key factor of component-based software development is the composition of pre-fabricated components. Although research efforts have focused on this issue, yet the optimal performance of component-based systems has not been achieved. If the concept of version management is introduced along with composition technology then it will help in locating the component mismatch in the earlier stages of software development life cycle. This paper analyses the significance of version management and composition of software components in different phases like analysis phase, design phase and deployment phase of software development life cycle. A comparative analysis of different available component models like COM, .NET, Enterprise JavaBeans (EJB), CORBA, SOFA, UML 2.0 and Web Services with respect to these two issues is also discussed.

Architectural Approaches for HL7-based Health Information Systems Implementation

Objective: Information systems integration is hard, especially when semantic and business process interoperability requirements need to be met. To succeed, a unified methodology, approaching different aspects of systems architecture such as b u s i n e s s , i n f o r m a t i o n , c o m p u - tational, engineering and techno- logy viewpoints, has to be considered. The paper contributes with an analysis and demonstration on how the HL7 standard set can support health information systems integration. Conclusion Selecting the appropriate integration architecture is a fundamental issue of any software development project. HIS-DF provides a unique methodological approach guiding the development of healthcare integration projects. The mediator model – offered by the HIS-DF and supported in HL7 v3 artifacts – is the more promising one promoting the development of open, reusable, flexible, semantically interoperable, platform- independent, service-oriented and standard-based health information systems. Methods: Based on t he Health I n f o rma- tion Systems Development Frame- work (HIS-DF), common architectural models for HIS integration are analyzed. The framework is a standard-based, consistent, comprehensive, customizable, scalable methodology that supports the design of semantically interoperable health information systems and components. Results: Three main architectural models for system integration are analyzed: the point to point interface, the messages server and the mediator models. Point to point interface and messages server models are completely supported by traditional HL7 version 2 and version 3 messaging. The HL7 v3 standard specification, combined with service-oriented, model-driven approaches provided by HIS-DF, makes the mediator model possible. The different integration scenarios are illustrated by describing a proof-of-concept imple- mentation of an integrated public health surveillance system based on Enterprise Java Beans technology. Conclusion: Selecting the appropriate integration architecture is a fundamental issue of any software development project. HIS-DF provides a unique methodological approach guiding the development of healthcare integration projects. The mediator model – offered by the HIS-DF and supported in HL7 v3 artifacts – is the more promising one promoting the development of open, reusable, flexible, semantically interoperable, platform- independent, service-oriented and standard-based health information systems.

Four-key-parts interworking model of heteromerous distributed component systems

The distributed component technology is increasingly widely used in the development and deployment of distributed systems. How to ensure interworking of these systems appears to be very important. On the basis of the in-depth study on distributed component systems, this article puts forward a four-key-parts interworking model and the corresponding static and dynamic translation mechanism for the integration of distributed component systems. Then, as a example, the interworking between common object request broker architecture (CORBA) component model (CCM) and enterprise Java bean (EJB) is discussed in detail. Thus, this paper offers an important idea for making various distributed component systems interworking and integration.

Code Conjurer: Pulling Reusable Software out of Thin Air

For many years, the IT industry has sought to accelerate the software development process by assembling new applications from existing software assets. However, true component-based reuse of the form Douglas Mcllroy envisaged in the 1960s is still the exception rather than the rule, and most of the systematic software reuse practiced today uses heavyweight approaches such as product-line engineering or domain-specific frameworks. By component, we mean any cohesive and compact unit of software functionality with a well-defined interface - from simple programming language classes to more complex artifacts such as Web services and Enterprise JavaBeans.

Interface Grammars for Modular Software Model Checking

Verification techniques relying on state enumeration (e.g., model checking) face two important challenges: the state-space explosion, an exponential increase in the state space as the number of components increases; and environment generation, modeling components that are either not available for analysis, or that cannot be handled by the verification tool in use. We propose a semi-automated approach for attacking these problems. In our approach, interfaces for the components not under analysis are specified using a specification language based on grammars. Specifically, an interface grammar for a component specifies the sequences of method invocations that are allowed by that component. We have built an compiler that takes the interface grammar for a component as input and generates a stub for that component. The stub thus generated can be used to replace that component during state space exploration, either to moderate state space explosion, or to provide an executable environment for the component under verification. We conducted a case study by writing an interface grammar for the Enterprise JavaBeans (EJB) persistence interface, and using the resulting stub to check EJB clients using the JPF model checker. Our results show that EJB clients can be verified efficiently with JPF using our approach.

Design profiles: toward unified tool support for design patterns and UML profiles

AbstractIn the current trend of software engineering, patterns and profiles lend themselves as two powerful complementary mechanisms for documenting and enforcing design rules. In this paper, we study how unified tool support can be achieved for patterns and profiles by interpreting them as role‐based structural descriptions and exploiting existing tool support for role modeling. The approach is realized using so‐called design profiles, which allow both validation and generation of models according to rules expressed in the patterns and profiles. A prototypical tool environment supporting the approach has been developed. The practical applicability of the approach is demonstrated by specifying design rules of the enterprise Java beans (EJB) platform and by producing an environment for designing EJB‐based applications. We also discuss possible usage scenarios in the context of this case study. Copyright © 2008 John Wiley & Sons, Ltd.