The different components within a software system must be integrated such that efficiency and stability are ensured. Interoperability must be guaranteed at all times. This is the only way to exploit the benefits of the solutions in use and to achieve actual added value. These challenges can only be met if flexible and configurable interfaces are in place between the Planning, Execution and Control modules themselves and also with the other application systems used within the company. PSIintegration is a tool and integration architecture to enable easy connection of different application systems.
The applications are integrated using adapters and transport mechanisms. An adapter is composed of a variety of plug-ins. The plug-ins are fixed in a construction drawing/pattern. PSIintegration includes several standard adapters and transport plug-ins. Additional adapters can also be implemented by combining existing adapter plug-ins or via new project-specific plug-ins. The configuration of these adapters is supported by a graphical editor and uses XML Tool Description Language (XTDL). The adapters for the source system and target system form the technical and logical conditions for the access method (database, file, SAP RFC/BAPI, TCP/IP, queues, HTTP etc.), data structure and format for each system. The transport and processing plug-ins format, map and transform the data when it is transferred from the source system to the target system. Multiple target systems can also be operated from a single source system. Correct operation can be controlled and tracked using a telegram browser.
The Order Management module and additional PSI software modules can be easily integrated into existing software architectures using RESTful web services (REST: representational state transfer). It is generally possible to read data from any data formats and with different protocols, and to process the data within processes, for example, using an enterprise service bus (ESB). The system enables integration with Java applications. Both standard components (e.g. XSLT) and individual components can be used if data must be transformed. The results of processes within an ESB are provided in the desired formats and with the necessary protocols (e.g. file, FTP, IMAP, POP3, SMTP, HTTP, JDBC, TCP etc.). The Order Management module can be accessed and controlled directly via the web services.