A Comparative Evaluation of .net Remoting and JAVA RMI

Distributed application technologies such as Micrososoft.NET Remoting, and Java Remote Method Invocation (RMI) have evolved over many years to keep up with the constantly increasing requirements of the enterprise. In the broadest sense, a distributed application is one in which the application processing is divided among two or more machines. Distributed middleware technologies have made significant progress over the last decade. Although Remoting and RMI are the two of most popular contemporary middleware technologies, little literature exists that compares them. In this paper, we study the issues involved in designing a distributed system using Java RMI and Microsoft.NET Remoting. In order to perform the comparisons, we designed a distributed distance learning application in both technologies. In this paper, we show both similarities and differences between these two competing technologies. Remoting and RMI both have similar serialization process and let objects serialization to be customized according to the needs. They both provide support to be able to connect to interface definition language such as Common Object Request Broker Architecture (CORBA). They both contain distributed garbage collection support. Our research shows that programs coded using Remoting execute faster than programs coded using RMI. They both have strong support for security although implemented in different ways. In addition, RMI also has additional security mechanisms provided via security policy files. RMI requires a naming service to be able to locate the server address and connection port. This is a big advantage since the clients do not need to know the server location or port number, RMI registry locates it automatically. On the other hand, Remoting does not require a naming service; it requires that the port to connect must be pre-specified and all services must be well-known. RMI applications can be run on any operating system whereas Remoting targets Windows as the primary platform. We found it was easier to design the distance learning application in Remoting than in RMI. Remoting also provides greater flexibility in regard to configuration by providing support for external configuration files. In conclusion, we recommend that before deciding which application to choose careful considerations should be given to the type of application, platform, and resources available to program the application

Conceptual Design and Analysis of Service Oriented Architecture (SOA) for Command and Control of Space Assets

The mission-unique model that has dominated the DoD satellite Command and Control community is costly and inefficient. It requires repeatedly “reinventing” established common C2 components for each program, unnecessarily inflating budgets and delivery schedules. The effective utilization of standards is scarce, and proprietary, non-open solutions are commonplace. IT professionals have trumpeted Service Oriented Architectures (SOAs) as the solution to large enterprise situations where multiple, functionally redundant but non-compatible information systems create large recurring development, test, maintenance, and tech refresh costs. This thesis describes the current state of Service Oriented Architectures as related to satellite operations and presents a functional analysis used to classify a set of generic C2 services. By assessing the candidate services’ suitability through a SWOT (Strengths, Weaknesses, Opportunities, and Threats) analysis, several C2 functionalities are shown to be more ready than others to be presented as services in the short term. Lastly, key enablers are identified, pinpointing the necessary steps for a full and complete transition from the paradigm of costly mission-unique implementations to the common, interoperable, and reusable space C2 SOA called for by DoD senior leaders

Asynchronous instant messaging using service-oriented architectures (aimsoa), 2005

Instant messengers suffer from poor scalability, flexibility, security, and interoperability. This study attempts to solve these problems using the strengths of Service-Oriented Architectures. The key components to achieve these improvements include several Java related technologies such as JAX-RPC, JAXM, SOAP, WSDL, J2EE servlets and Enterprise Java Beans. SOAP provides a universal messaging protocol that heterogeneous parties can understand. JAX-RPC provides synchronous SOAP messaging, as well as a loosely coupled design that allows for a very flexible distributed architecture. JAXM provides asynchronous SOAP messaging. When used together, applications can implement robust instant messaging functionality. Registration, login, and other instant messaging configuration operations can be fulfilled through the use of JAX-RPC while JAXM can be used to fulfill requirements such as send and receive. Servlets and Enterprise Java Beans augment the benefits of Service-Oriented Architectures with the former being extremely scalable, portable, and modular. AIMSOA encapsulates these components to provide an instant messaging architecture solution that will augment the weaknesses of current instant messaging architectures by providing a solution for better scalability, flexibility, and interoperability

Web Services: Enabling Dynamic Business Networks

A Dynamic Business Network is a distinct system of participants (customers, suppliers, complimentors, competitors, service providers) that use the network to achieve customer satisfaction and profitability and where participants and relationships evolve over time. However, unpredictability and rapid change in a Dynamic Business Network creates a significant challenge in implementing and supporting business application software. Traditional information systems implementation methods require an a priori design and are built for a particular purpose for use over an extended period of time. Loosely coupled business networks change interrelationships between nodes both quickly and frequently, thus providing little or no notice for planning, implementing, or changing the supporting applications. The dynamic sourcing capabilities of the emerging Web Services framework provide a key to enabling these complex eco-systems. We explore the strategic and technological dimensions of Web Services and describe how they can be used to support dynamic business networks

The Development of a Model for Complaint Delivery on Aviation Industry in Indonesia Based on SMS Gateway to Promote Flight Safety

The variety of complaints appearing on Aviation Industry in Indonesia actually indicates the existence of problems on aviation system in Indonesia. The number of complaints may serve as an early detection in a system before the occurrence of an accident in a flight. Increasing numbers of flight service users in Indonesia had not been supported with an adequate complaint delivery, whether it is for internal complaints or external ones. One of available solutions is to detect whether all system components on Aviation Industry in Indonesia is good or not. In an effort to enhance system performance, a model for integrated complaint delivery is developed on Aviation Industry based on SMS Gateway in Indonesia. The model is expected to become a data bank on Aviation Industry to ease controlling, evaluating and improving condition performance on flight systems. This research used comparative and descriptive methods. It also results in applied product hence it is expected that the output can be used to complement the current product/program operated by Directorate General of Civil Aviation (DGCA). The development of a model for complaint delivery is conducted to make cellular phone numbers inputs for all stakeholders on aviation industry. This strategy activates all stakeholders to provide information regarding the current conditions for all subsystems in flight system in Indonesi

Bioconductor: open software development for computational biology and bioinformatics.

The Bioconductor project is an initiative for the collaborative creation of extensible software for computational biology and bioinformatics. The goals of the project include: fostering collaborative development and widespread use of innovative software, reducing barriers to entry into interdisciplinary scientific research, and promoting the achievement of remote reproducibility of research results. We describe details of our aims and methods, identify current challenges, compare Bioconductor to other open bioinformatics projects, and provide working examples