信息化规划建设(用友).pptVIP

* Notes: * Notes: * Notes: * * * * * * 用友也在做产品的标准化与集成 * * * * * * * * * * Strategic Imperative: An IT department must excel at application integration if it is to satisfy the growing requirements from the business side of the company. Application integration is defined as making independently designed application systems work together. This is a broad definition, encompassing not only tightly coupled request/reply exchanges among interdependent systems, but also simple, arms length batch file transfers between relatively autonomous application systems. Integration has two aspects, interoperability (for example, .NET interoperates with CICS) and application-level integration (for example, an SAP application integrates with an Oracle or legacy application). Interoperability is the mechanical part of application integration. Interoperability means getting software technologies, such as disparate operating systems (OSs), programming languages, application platforms, database management systems (DBMSs), network protocols and middleware, to work together. Where all developers use the same technology from the same vendor (de facto standards), interoperability is not an issue. Where the products come from different vendors, standards such as Java, SOAP, SQL, TCP/IP and XML help. Where products do not comply exactly with the same standards, interoperability requires gateways. Integration requires more than interoperability. The greater challenge is enabling applications to interact on a logical and semantic level. Developers must reconcile disparate data models, object models, process models, organization models and other aspects of design. This is harder than mechanical interoperability because an off-the-shelf gateway cannot solve the problem. Integration always requires some customization. * * * * In order to implement an SOA, both applications and infrastructure must support the SOA principles. Enabling applications involves the creation of service interfaces to exist