EAI Blog

This entry doesn't actually pertain to what we covered this week in class, but I did find this interesting program at work (RedPrairie).  It's called Integrator Explorer, and while I haven't used it yet, it seems like what we cover in this class will definitely help me when I need to use it.  I've just copied the basic description of this software below:

Integrator is RedPrairie’s unique interoperability and integration tool for the DigitaLogistixâ product suite. Integrator is a standalone product through which RedPrairie's DigitaLogistixâ suite of applications communicate with each other, with legacy host systems and with external enterprise resource planning (ERP) systems such as those developed by SAPâ, Oracleâ and PeopleSoftâ.

Integrator provides the capability to

• establish a DigitaLogistixâ central point of communication for legacy systems.

• map a single inbound transaction Communication from one system to another system in which one or more inbound IFDs are created, such as when item/part master information is sent from a legacy system to DLx Warehouse. to multiple DigitaLogistixâ products

• map a single outbound event A defined occurrence that triggers a transaction. The occurrence of an event causes Integrator to gather data from the triggering system's database or from an inbound IFD for communication to a target system. to multiple ERP and/or DigitaLogistixâ target systems

• import/export native ERP (ERP) A business management system that integrates all facets of the business, including planning, manufacturing, sales and marketing. or legacy data formats The layout in which IFD data is formatted. F = Fixed-byte format; IFD fields are located at specific byte positions in the IFD segment. P = Positional and delimited; IFD fields are delimited by a character (for example, a comma), but the position of the fields is significant. An example of this format is CSV (comma-separated variable length). PI = Position independent and delimited; IFD fields are delimited by a defined character and the position of the fields is not significant. The names of the IFD fields are stored next to the data.

• facilitate the import/export of the standard DigitaLogistixâ transaction set

• process fixed-byte, delimiter-based or multi-byte (internationally compliant) host transactions

• deliver data through synchronous A communication mode in which the triggering transaction that logged the event is responsible for sending the IFD data to its destination. If the data transfer fails for any reason, the triggering transaction will also fail. or asynchronous A communication mode in which the triggering transaction is not responsible for sending the data to the target system. A separate process periodically looks for transactions that require data to be sent. The required IFDs are generated and sent separately from the triggering transaction. communication

• de-couple interface documents The structure of a data set that Integrator will receive from a system or send to a system. The IFD defines the data in the format required by the target system. Also used to refer to an instance of the structured data. An IFD is made up of segments, and each segment is made up of fields. and the data set required for interface documents

• summarize multiple occurrences of the same DigitaLogistixâ event into a single ERP or legacy host transaction

• utilize the MOCA Command Server to call DigitaLogistixâ components (intrinsic), and

• support ERP-specific connectivity options.