scholarly journals Into the Fold

2007 ◽  
Vol 129 (02) ◽  
pp. 36-38
Author(s):  
Jean Thilmany
Keyword(s):  
Service Oriented Architecture ◽  
Open Systems ◽  
Product Lifecycle Management ◽  
Enterprise Service Bus ◽  
Integration Framework ◽  
Business Applications ◽  
Service Oriented ◽  
End To End ◽  
Lifecycle Management ◽  
Plm System

This article focuses on the need for improvement in product lifecycle management (PLM) interoperation. PLM interoperation would allow companies to work with the best tools for its business and not be limited in communicating with customers and suppliers. PLM systems are getting a fresh look and one should expect to see more of the type now often called end-to-end open systems. The secret is the middleware, dubbed service-oriented architecture (SOA), which links all these applications in an interconnected web. IBM introduced plans for its Product Development Integration Framework, which will tie all business applications via SOA to create an end-to-end, open PLM system. The company is also marketing an enterprise service bus that can loosely couple its own business applications with other applications, which will then operate on the system. According to an expert, by linking research to engineering, Samsung’s products could hit the market quicker than if the two functions worked separately, and products could be designed in ways that had only just been conceptualized.

On Architecting and Implementing a Product Information Sharing Service

2008 ◽  
Vol 8 (1) ◽  
Author(s):  
Vijay Srinivasan ◽  
Lutz Lämmer ◽  
Steven Vettermann
Keyword(s):  
Information Sharing ◽  
Service Oriented Architecture ◽  
Product Information ◽  
Product Lifecycle Management ◽  
Business Information ◽  
Recent Developments ◽  
Service Oriented ◽  
Open Standards ◽  
Use Of Internet ◽  
Lifecycle Management

Recent developments in information technology are influencing the field of engineering informatics in some profound ways. Nowhere is the influence more evident than in the use of Internet-based technologies and standards to share engineering and business information across a worldwide enterprise. In turn, the business need for collaboration among various players and partners in a globally integrated enterprise is driving the development and deployment of open standards, service-oriented architecture, and middleware. The convergence of these developments has provided us an opportunity to architect and implement a product information sharing service described in this paper. The architecture is service oriented and is based on the Object Management Group's PLM Services 1.0 specifications. It is implemented using IBM’s WebSphere Process Server middleware and PROSTEP’s OpenPDM software. This product information sharing service is one of the first industrial examples of a successful application of service-oriented architecture to product lifecycle management.

scholarly journals In One Place

2009 ◽  
Vol 131 (03) ◽  
pp. 34-37
Author(s):  
Jean Thilmany
Keyword(s):  
Product Design ◽  
Tracking System ◽  
Product Lifecycle Management ◽  
Product Lifecycle ◽  
Software Developers ◽  
Product Data ◽  
Fully Integrated ◽  
Big Picture ◽  
End To End ◽  
Lifecycle Management

This review explores the prospects of using product lifecycle management (PLM) as an end-to-end solution. The components of PLM provide significant value, but there are no fully integrated offerings on the market that perfectly cover every aspect of product lifecycle, according to a report. In the absence of an end-to-end tracking system, one trend coming to prominence is the use of PLM as the complete system of record for all product data. Though a study concluded that PLM still has a way to go in terms of tracking product design from early inception right through sales to reclamation, it is becoming the main go-to source for a large amount of product data. Experts believe that PLM still has a way to go in terms of tracking product design from early inception right through sales to reclamation; however, it is becoming the main go-to source for a large amount of product data. Software developers are working to create tools that can incorporate ever more of the big picture and make it accessible to engineers.

Patterns for Migration of SOA Based Applications to Microservices Architecture

2021 ◽  
Author(s):  
Vinay Raj ◽  
Ravichandra Sadam
Keyword(s):  
Programming Languages ◽  
Service Oriented Architecture ◽  
Legacy Systems ◽  
Loose Coupling ◽  
Enterprise Service Bus ◽  
Web Based ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Key Features ◽  
Microservice Architecture

Service oriented architecture (SOA) has been widely used in the design of enterprise applications over the last two decades. Though SOA has become popular in the integration of multiple applications using the enterprise service bus, there are few challenges related to delivery, deployment, governance, and interoperability of services. To overcome the design and maintenance challenges in SOA, a new architecture of microservices has emerged with loose coupling, independent deployment, and scalability as its key features. With the advent of microservices, software architects have started to migrate legacy systems to microservice architecture. However, many challenges arise during the migration of SOA to microservices, including the decomposition of SOA to microservice, the testing of microservices designed using different programming languages, and the monitoring the microservices. In this paper, we aim to provide patterns for the most recurring problems highlighted in the literature i.e, the decomposition of SOA services, the size of each microservice, and the detection of anomalies in microservices. The suggested patterns are combined with our experience in the migration of SOA-based applications to the microservices architecture, and we have also used these patterns in the migration of other SOA applications. We evaluated these patterns with the help of a standard web-based application.

A Role of Enterprise Service Bus in Building Web Services

2017 ◽  
pp. 46-58
Author(s):  
Dinesh Sharma ◽  
Devendra Kumar Mishra
Keyword(s):  
Web Services ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Enterprise Service Bus ◽  
Fast Processing ◽  
Service Oriented ◽  
Open Standards ◽  
Or Organization ◽  
Services Use

Present is the era of fast processing industries or organization gives more emphasis for planning of business processes. This planning may differ from industry to industry. Service oriented architecture provides extensible and simple architecture for industry problem solutions. Web services are a standardized way for developing interoperable applications. Web services use open standards and protocols like http, xml and soap. This chapter provides a role of enterprise service bus in building web services.

Applying Semantic SOA-Based Model to Business Applications

2010 ◽  
pp. 1-20
Author(s):  
Tariq Mahmoud ◽  
Jorge Marx Gómez
Keyword(s):  
Service Oriented Architecture ◽  
Semantic Web Services ◽  
Business Environments ◽  
Business Applications ◽  
Proposed Model ◽  
Service Oriented ◽  
Semantic Service ◽  
Main Components ◽  
Medium Businesses ◽  
Business To Business

Nowadays, it becomes more and more critical and essential for the vendors in the business-related markets to tailor their products and software to meet the needs of the Small and Medium Businesses (SMB) since their market share has been enormously raised and the issues related to the Business-to-Business (B2B) environment are becoming great challenges to be considered. The semantic Service-Oriented Architecture (SOA)-based model involves Semantic Web Services to be applied in business environments in order to have a consistent framework that makes the data understandable for both humans and machines. The ultimate goal for using the authors’ proposed model is to transfer the enterprise Web into a medium through which data and applications can be automatically understood and processed. The main components of the proposed model and the vision of applying it to one of the business solutions will be illustrated in order to show how these components can work together to overcome the traditional SOA-based solutions weakness.

Airport Enterprise Service Bus with Self-Healing Architecture (AESB-SH)

2011 ◽  
Vol 1 (1) ◽  
pp. 1-13 ◽  
Author(s):  
Issam Al Hadid
Keyword(s):  
New Technologies ◽  
Service Oriented Architecture ◽  
Legacy Systems ◽  
Self Healing ◽  
Enterprise Service Bus ◽  
Information Accessibility ◽  
Automatic Information ◽  
Healing Agent ◽  
Service Oriented ◽  
Information Interchange

Airports need to adapt new technologies to react effectively and quickly to customers’ needs and to provide a better service such as the electronic ticket. In addition to the challenges of the ability to respond to the growing requirements of the automatic information interchange between the different systems to ensure safe and efficient airport operations. This paper provides an architecture based on the Service Oriented Architecture (SOA) that improves the information accessibility and sharing across the different Airport’s departments, integrates the existing legacy systems with other applications, and improves and maximizes the system’s reliability, adaptability, robustness, and availability using the Self-Healing Agent.

Adaptive Service Choreography Support in Virtual Enterprises

2008 ◽  
pp. 66-75 ◽  
Author(s):  
Adomas Svirskas ◽  
Bob Roberts ◽  
Ioannis Ignatiadis
Keyword(s):  
Web Services ◽  
Service Oriented Architecture ◽  
Virtual Enterprises ◽  
Business Applications ◽  
Service Oriented ◽  
Service Choreography ◽  
Business Function ◽  
Business Protocols ◽  
Usage Context ◽  
The Web

Service Oriented Architecture (SOA) approach in general and the Web services technology in particular enable creation of business applications from independently developed, deployed and owned components called services. A service captures a distinct business function offering some value independently of its usage context. However, it is not enough to have the business functionality of the partners packaged as (Web) services; there is also a need for business-aligned order of interaction between these services a.k.a. business protocols, which can also be reused. The contribution of the chapter is two-fold: it explores reusability of the applicable business protocols in different business scenarios and also suggests possible ways to adapt the implementations of the partners’ services (end-points) to the changes in the business protocols.

Sign in / Sign up

Export Citation Format

Share Document