Web Service in Integrated Logistics InformationSystemGuide Words: Integrated Logistics; modeling notationAbstract:This paper describes a system for the integration of different logistic chain Actors. Theproposed system exploits the open Internet standards and is based on connection model betweenLogistic system users and service providers. The Integrated Logistics Information System (ILIS)concerns global logistics and involves interrogating information relating to production means, storagepoints and means of transport.We study in this paper theproblematic of communication inter-andintra-company functions in the ILIS context. By using UML propose a hierarchical model to integratethe different Actors of Logistic chain. By exploiting the open Internet standards we present a servicesproviders platform based on web service approachI.INTRODUCTIONWeb has become a standardized infrastructure for a great number of diverse applicationsincluding,among others,access to information, communication, e-commerce, energy managementand sophisticated medicine applications. This standardized infrastructure guarantees accessibility andusability advantages to the whole range of participants including end users, logistic Actors and serviceproviders.Technologies have been developed which enable services to be bundled together that use differentcommunication media and protocols.Our proposed approach isbased on thegeneric framework ofe-services.The logistic chain of a product is the whole of the companies which take part in themanufacturing process, of distribution and sale product, of the first of the suppliers to the ultimatecustomer. This concept of logistic chain is very wide and very complex because the suppliers havethemselves their own suppliers and the customers are often suppliers of other customers. The controland the piloting of any logistic chain require too much data-processing on the level of the managementof physical and informational flow. From the design to the exit of manufacture, a product is dealt withby various systems,most of thetime distributed anddeveloped inheterogeneousplatforms.Thedivision of this information flow coming from these various systems is necessary to better control on
Web Service in Integrated Logistics Information System Guide Words：Integrated Logistics; modeling notation. Abstract：This paper describes a system for the integration of different logistic chain Actors. The proposed system exploits the open Internet standards and is based on connection model between Logistic system users and service providers. The Integrated Logistics Information System (ILIS) concerns global logistics and involves interrogating information relating to production means, storage points and means of transport. We study in this paper the problematic of communication inter- and intra-company functions in the ILIS context. By using UML propose a hierarchical model to integrate the different Actors of Logistic chain. By exploiting the open Internet standards we present a services providers platform based on web service approach. I. I NTRODUCTION Web has become a standardized infrastructure for a great number of diverse applications, including, among others, access to information, communication, e-commerce, energy management and sophisticated medicine applications. This standardized infrastructure guarantees accessibility and usability advantages to the whole range of participants including end users, logistic Actors and service providers. Technologies have been developed which enable services to be bundled together that use different communication media and protocols. Our proposed approach is based on the generic framework of e-services. The logistic chain of a product is the whole of the companies which take part in the manufacturing process, of distribution and sale product, of the first of the suppliers to the ultimate customer. This concept of logistic chain is very wide and very complex because the suppliers have themselves their own suppliers and the customers are often suppliers of other customers. The control and the piloting of any logistic chain require too much data-processing on the level of the management of physical and informational flow. From the design to the exit of manufacture, a product is dealt with by various systems, most of the time distributed and developed in heterogeneous platforms. The division of this information flow coming from these various systems is necessary to better control on
all the stages of products manufacture, to be able to intervene quickly, carry out corrections, or tocarry out the various stages validation. It is thus necessary to relate between the various systemstaking charges the same product manufacturing. Indeed the division of information and the best ofvarious knowledge bases, offer a better control and allow the faster resolution of problems which caroccur intervene along the various stages of the product development. This information division allowsimproving the company reactivity and productivity.The communication between the variousinformation systems ofthelogisticchainmustevolveto aproactiverelationbased ontheinformationdivisionandthecollaborativedevelopment.The manufacturing process optimization is a crucial function to guarantee the products andservices provided quality.But it is asa complex function as complex as many aided informationsystems, management of many functions became necessary and must cohabit.They are obviouslymore or less complementary or redundant, sometimes incoherent, always heterogeneous; These are thereasons which justified the creation of the platform PEGASE whose objective is to facilitate theintegration of these various systems by defining a single and coherent description systems ofproduction to be maintained, a generic architecture (based on the concept of Web Service) and byproposing models and technological solutions of integration.PEGASE is a platform of integration, with all the problems inherent in these technologies, distributionof the components, discovered services, definition of the services, controls of the access, etc.This paper present after this section the integration strategy, in section three we present theproblematic of integrated logistic; in section four we exposed UML language for modelling, in thefive sections we deal with PEGASE platform. We finish this paper by conclusion.IL.INTEGRATIONSTRATEGYThe growth of the number of distributed information in the companies implies a need to exchangeand/or share information coming from distinct and heterogeneous data bases. However, informationstorage on various sites and in several applications can involve later architecture problems to thecompanies. The data are dispersed, thus involving ineffective processes trades and a total fall of theproductivity. The arrival of great software packages of integrated management, equipped with manyfunctionalities which support the user's needs and the diversity of the functions of the companiesconstitute the information system main part. In parallel, the software applications can from now oncommunicate, cooperate, thanks to the emergence of new technologies allowing by the same occasionto cross the doors and the borders of the organizations. Internet, passing from the statute of simple
all the stages of products manufacture, to be able to intervene quickly, carry out corrections, or to carry out the various stages validation. It is thus necessary to relate between the various systems taking charges the same product manufacturing. Indeed the division of information and the best of various knowledge bases, offer a better control and allow the faster resolution of problems which car occur intervene along the various stages of the product development. This information division allows improving the company reactivity and productivity. The communication between the various information systems of the logistic chain must evolve to a proactive relation based on the information division and the collaborative development. The manufacturing process optimization is a crucial function to guarantee the products and services provided quality. But it is as a complex function as complex as many aided information systems; management of many functions became necessary and must cohabit. They are obviously more or less complementary or redundant, sometimes incoherent, always heterogeneous; These are the reasons which justified the creation of the platform PEGASE whose objective is to facilitate the integration of these various systems by defining a single and coherent description systems of production to be maintained, a generic architecture (based on the concept of Web Service) and by proposing models and technological solutions of integration. PEGASE is a platform of integration, with all the problems inherent in these technologies, distribution of the components, discovered services, definition of the services, controls of the access, etc. This paper present after this section the integration strategy, in section three we present the problematic of integrated logistic; in section four we exposed UML language for modelling, in the five sections we deal with PEGASE platform. We finish this paper by conclusion. II. INTEGRATION STRATEGY The growth of the number of distributed information in the companies implies a need to exchange and/or share information coming from distinct and heterogeneous data bases. However, information storage on various sites and in several applications can involve later architecture problems to the companies. The data are dispersed, thus involving ineffective processes trades and a total fall of the productivity. The arrival of great software packages of integrated management, equipped with many functionalities which support the user's needs and the diversity of the functions of the companies, constitute the information system main part. In parallel, the software applications can from now on communicate, cooperate, thanks to the emergence of new technologies allowing by the same occasion to cross the doors and the borders of the organizations. Internet, passing from the statute of simple
media to the statute of the "universal" support, and which makes it possible to integrate and offerservices to the users, to have a role of integrator of applications. Integration of Information Systems ofthe companies falls under this context, in the medium of the paradoxes, antagonisms, even, of thetechnological lures.Within the framework of the relations intra firms or/and will between firms the problematic ofintegrated information system is situated. The goal being to be able to inter-connect a whole ofapplications, a whole of services in order to answer the user expectations and the new fashions oforganization while keeping any flexibility. Indeed, this inevitable share, communications, should notbe made with the detriment autonomy of each unit, each user, each tool put in some context. Forts ofthese observations, several working groups were constituted having for objective to proposespecifications, standards, standards that it is on the computerized exchanges, technologies for the Weband the buses software. However, if some of these proposals seem to be essential (XML for example)others enter in competition and tend to become more and more complex (CORBA and Java/RMI, JBetc.). The Application Integration has become a need to cope with the distribution of information inthe companies. These Enterprises adopted four different approaches to face this need [4]:The Manual Approach:The Manual Approach represents the most expensive and most primitiveone for the Application Integration. Reports/ratios are printed and then seized again manually in otherapplication. In spite of its huge cost, this approach is nowadays the most widespread among thecurrentcompanies.The Import/Export Approach:With this approach, the data are exported by an operator orautomatically by the software, are transferred then imported in another application. One of the majordisadvantages of this approach is the static nature of the data. The changes carried out after an exportdid not appear unless another export is realized. Consequently, the second application lays only anapproximate statute of the data. This approach is not appropriate for real time transfers. It is oftennecessary to develop several applications to transform the data in a format readable by the secondapplication.The access approach to the primitive data structures: This approach has been revolutionary sincethe editors of the data bases allowed the subjacent data bases to accede to the data structures. Thatallowed acceding to the data in real time. The data could be thus read constantly and were preciseHowever, the share of applications should duplicate the functionalities. Any modification made in thestructure of the data (for example, to add a new files) required the modification of all the applications
media to the statute of the "universal" support, and which makes it possible to integrate and offer services to the users, to have a role of integrator of applications. Integration of Information Systems of the companies falls under this context, in the medium of the paradoxes, antagonisms, even, of the technological lures. Within the framework of the relations intra firms or/and will between firms the problematic of integrated information system is situated. The goal being to be able to inter-connect a whole of applications, a whole of services in order to answer the user expectations and the new fashions of organization while keeping any flexibility. Indeed, this inevitable share, communications, should not be made with the detriment autonomy of each unit, each user, each tool put in some context. Forts of these observations, several working groups were constituted having for objective to propose specifications, standards, standards that it is on the computerized exchanges, technologies for the Web and the buses software. However, if some of these proposals seem to be essential (XML for example), others enter in competition and tend to become more and more complex (CORBA and Java/RMI, JB etc.). The Application Integration has become a need to cope with the distribution of information in the companies. These Enterprises adopted four different approaches to face this need [4]: The Manual Approach: The Manual Approach represents the most expensive and most primitive one for the Application Integration. Reports/ratios are printed and then seized again manually in other application. In spite of its huge cost, this approach is nowadays the most widespread among the current companies. The Import/Export Approach: With this approach, the data are exported by an operator or automatically by the software, are transferred then imported in another application. One of the major disadvantages of this approach is the static nature of the data. The changes carried out after an export did not appear unless another export is realized. Consequently, the second application lays only an approximate statute of the data. This approach is not appropriate for real time transfers. It is often necessary to develop several applications to transform the data in a format readable by the second application. The access approach to the primitive data structures: This approach has been revolutionary since the editors of the data bases allowed the subjacent data bases to accede to the data structures. That allowed acceding to the data in real time. The data could be thus read constantly and were precise. However, the share of applications should duplicate the functionalities. Any modification made in the structure of the data (for example, to add a new files) required the modification of all the applications
reaching the structure of the data to be able to profit from this change. One of the principal advantagesof access to the primitive data structures of was the formulation of ad hoc requests by the usersstarting from products such Microsoft Excel. However, the users were to learn how the programmersconceived the structures of data and to follow a new formation if the structures were modified.The API Approach: To solve the problem integrity of the data quoted in the third integrationapproach, several editors of applications such as SAP and PeopleSoft created their personalized API toauthorize other applications to share the functionalities of the applications and the data. However,each API and each method used for call was different. These API were narrowly coupled with thespecific applications, the other editor's applications and tools of development had to investenormously to deal with each editor applications API. Even if the concept seemed promising, theseAPI were never accepted by the other editors.The Web services are based on personalized APIapproach, thus profiting from all these advantages and proposing some others. The Web services useopen standards. Is not narrowly coupled and is not related to only editor technologies. The Webservices also allow for an application to call another thanks to the standard protocols such as SOAPand XML. This approach guarantees integrity of the data because the application is the unique whichtreats the data. In the event of functionalities change of enterprise, only the functionalities of suitableapplication must be modified. Being given that the Web services are not narrowly coupled, the editorscan more easily deal with this technology. Thanks to the assumption of responsibility of the servicesWeb by the majority of the applications editors and all the principal editors of development tools,integration of applications becomes from nowmore current, thus making it possible the developers tochoose development tools adapted rather than to be satisfied by tools usually used in the enterprise.Moreover, when the companies consider to buy applications, they can now concentrate on thefunctionalities of application and its advantages rather than on subjacent technology.As long asapplication is directed Web services, application can be integrated with the other applications. In short,the Web services allow an access in real time to the data, while guaranteeing integrity of the data andwhile authorizing the share of the data.In this paper, we proposed to use a Web based front-end integration strategy. The Web basedintegration strategy uses system-independent and vendor-independent neutral information models atthe “front-end"(at the input/output level) to achieve interoperability. Key components of thisWeb-based front-end integration strategy include standard XML (Extensible Markup Language)schemes and shared building object and construction activity indexes. The standard XML schemes
reaching the structure of the data to be able to profit from this change. One of the principal advantages of access to the primitive data structures of was the formulation of ad hoc requests by the users starting from products such Microsoft Excel. However, the users were to learn how the programmers conceived the structures of data and to follow a new formation if the structures were modified. The API Approach: To solve the problem integrity of the data quoted in the third integration approach, several editors of applications such as SAP and PeopleSoft created their personalized API to authorize other applications to share the functionalities of the applications and the data. However, each API and each method used for call was different. These API were narrowly coupled with the specific applications, the other editor’s applications and tools of development had to invest enormously to deal with each editor applications API. Even if the concept seemed promising, these API were never accepted by the other editors. The Web services are based on personalized API approach, thus profiting from all these advantages and proposing some others. The Web services use open standards. Is not narrowly coupled and is not related to only editor technologies. The Web services also allow for an application to call another thanks to the standard protocols such as SOAP and XML. This approach guarantees integrity of the data because the application is the unique which treats the data. In the event of functionalities change of enterprise, only the functionalities of suitable application must be modified. Being given that the Web services are not narrowly coupled, the editors can more easily deal with this technology. Thanks to the assumption of responsibility of the services Web by the majority of the applications editors and all the principal editors of development tools, integration of applications becomes from now more current, thus making it possible the developers to choose development tools adapted rather than to be satisfied by tools usually used in the enterprise. Moreover, when the companies consider to buy applications, they can now concentrate on the functionalities of application and its advantages rather than on subjacent technology. As long as application is directed Web services, application can be integrated with the other applications. In short, the Web services allow an access in real time to the data, while guaranteeing integrity of the data and while authorizing the share of the data. In this paper, we proposed to use a Web based front-end integration strategy. The Web based integration strategy uses system-independent and vendor-independent neutral information models at the ‘‘front-end’’ (at the input/output level) to achieve interoperability. Key components of this Web-based front-end integration strategy include standard XML (Extensible Markup Language) schemes and shared building object and construction activity indexes. The standard XML schemes
serve as the glue for integration and also reference models for object semantics. The indexes are usedto globally and uniquely identify each object involved in the collection of information objects of anydocuments. The Web-based front-end integration strategy depends on XML and related technologies,such as XML scheme, SOAP (Simple Object Access Protocol) and XML/Object Serialization.XML isdesigned to improve the functionality of the Web by providing a more flexible and adaptableinformation identification.It is called extensiblebecause it is not a fixed format like HTML(a single,predefined markup language). Instead, XML is actually a “met language", a language for describingother languages, which lets you design your own customized markup languages for an unlimitednumberofdifferenttypes ofdocuments.An XML scheme is a document that describes the valid format of an XML data set. This definitionincludes what elements are (and are not) allowed at any point, what the attributes for any element maybe, the number of occurrences of elements and so on. SOAP provides a simple and lightweightmechanism for exchanging structured and typed information between peers in a decentralizeddistributed environment using XML. XML/Object binding/marshaling offers a system the capabilityof mapping almost any kind of XML data definitions into an object model.Although XML parsers can also build a generic object model from an XML document, such anobject model does not necessarily reflect the requirements of an application. In many cases, softwareapplications have their own internal object models. When such applications receive an XML file, it isidealtomarshal theXMLdatasets intotheinternal objectmodel of theapplication.Ontheotherhandwhen the application needs to send out some information in XML format, it is straightforward to mapthe internal object model into the XML format that complies with the predefined XML Scheme. Withthe availability and the maturity of such technology, heterogeneous systems can share the semantics ofinformation Objects by sharing an XML scheme that defines the information objects. Betweenheterogeneous systems, SOAP, as an industry standard, can be used as a data exchange protocol. Oncea system receives some XML data sets, the system can use the XML/Object marshalling tool to mapthe XML data set to its internal object model. Thus, with these technologies, a system can manipulateobjects from other systems just as if these objects were local to it.II.INTEGRATEDLOGISTICSLogistics is a vast field. Classical definitions of the word “LOGISTICS” appear in several works"Greek mathematicians called logistics the art of calculating".In our context, logistics is“the art oftransferring and transforming matter and information together and Just-in-Time with the permanent
serve as the glue for integration and also reference models for object semantics. The indexes are used to globally and uniquely identify each object involved in the collection of information objects of any documents. The Web-based front-end integration strategy depends on XML and related technologies, such as XML scheme, SOAP (Simple Object Access Protocol) and XML/Object Serialization. XML is designed to improve the functionality of the Web by providing a more flexible and adaptable information identification. It is called extensible because it is not a fixed format like HTML (a single, predefined markup language). Instead, XML is actually a ‘‘met language’’, a language for describing other languages, which lets you design your own customized markup languages for an unlimited number of different types of documents. An XML scheme is a document that describes the valid format of an XML data set. This definition includes what elements are (and are not) allowed at any point, what the attributes for any element may be, the number of occurrences of elements and so on. SOAP provides a simple and lightweight mechanism for exchanging structured and typed information between peers in a decentralized, distributed environment using XML. XML/Object binding/marshaling offers a system the capability of mapping almost any kind of XML data definitions into an object model. Although XML parsers can also build a generic object model from an XML document, such an object model does not necessarily reflect the requirements of an application. In many cases, software applications have their own internal object models. When such applications receive an XML file, it is ideal to marshal the XML data sets into the internal object model of the application. On the other hand, when the application needs to send out some information in XML format, it is straightforward to map the internal object model into the XML format that complies with the predefined XML Scheme. With the availability and the maturity of such technology, heterogeneous systems can share the semantics of information Objects by sharing an XML scheme that defines the information objects. Between heterogeneous systems, SOAP, as an industry standard, can be used as a data exchange protocol. Once a system receives some XML data sets, the system can use the XML/Object marshalling tool to map the XML data set to its internal object model. Thus, with these technologies, a system can manipulate objects from other systems just as if these objects were local to it. III. I NTEGRATED LOGISTICS Logistics is a vast field. Classical definitions of the word“LOGISTICS” appear in several works: “Greek mathematicians called logistics the art of calculating”. In our context, logistics is “the art of transferring and transforming matter and information together and Just-in-Time with the permanent