Logile’s overriding design philosophy is flexibility.
- Flexibility in deployment. Our solution is modular and runs on the operating system and application server of your choice.
- Flexibility in user interaction. Users can access the system via any web browser on PCs, tablets, smart phones and various ruggedized mobile devices (e.g. Motorola/Symbol and Honeywell/HHP).
- Flexibility in customer-specific customization. Our framework and technologies make integrating your data, workflows and employees easy.
Our user interfaces have a familiar feel, are simple to use, and require minimal training—without sacrificing sophistication or functionality.
We architect our solutions to be modular, flexible, scalable and fault tolerant. Because our solution is based on the Java 2 Enterprise Edition (J2EE) platform, it can be deployed on all popular server architectures, including Windows/Intel, Unix (AIX, Solaris, HP-UX) and Linux.
We integrate databases within our solution using Object Relational Mapping (ORM) technology. This gives database independence and allows support for the major relational database servers including Oracle, SQL Server, DB2 and MySQL.
Reporting and analysis functionally is provided via an Online Analytical Processing (OLAP) engine. This allows user-defined, multi-dimensional reports, as well as integration with existing enterprise reporting solutions. Business Process Modeling (BPM) to capture workflows and business processes is supported natively within the suite.
We use Java Messaging Service (JMS) technology for internal communication between solution modules, as well as to integrate with external systems via Message Oriented Middleware (MOM) or Enterprise Service Bus (ESB) technologies. Data integration with existing retail systems, such as inventory movement, engineered labor standards and human resources management systems, can be facilitated via various interface mechanisms. These mechanisms include flat file and XML imports as well as direct database access and MOM/ESB interfaces, if available.
The messaging infrastructure supports rich and flexible messaging and notification systems that allow for timely, priority-based messages to employees at various levels throughout the enterprise. Notification via web clients and email is supplemented by messaging to cell phones (via SMS and Twitter), in-store paging systems, and alerts to handhelds, including intelligent pricing handhelds and PDAs/smartphones. The platform also supports user-customizable portals and dashboards.
Our solution is based on a platform that provides the greatest flexibility in deployment, as well as support for rapid application development and product modularization. The highlights of the technology stack are:
Logile’s solution is J2EE-based, allowing it to be operating system and application server neutral. It can be based on J2EE application servers ranging from open source servers such as JBoss and Sun Glassfish to commercial offerings such as IBM Websphere and Oracle Weblogic.
We use the JBoss Seam application framework, which supports rich web clients as well as portal functionality via the JSR-168 Portlets API and business process management (BPM). The BPM functionality is provided via the jBPM API from JBoss. As part of the Seam/J2EE platform, the application uses the Java Persistence API (JPA) to perform Object Relational Mapping (ORM). JPA is a pluggable API framework that maps data from relational databases into objects used by the application code in a database-neutral manner. There are numerous JPA providers ranging from the open source Hibernate to commercial products such as Oracle TopLink. Using JPA allows Logile’s solution to work with any of the major database vendors with few coding changes.
We use the open source Mondrian OLAP engine from Pentaho. This engine can interface with external reporting solutions such as Microsoft SQL Analysis Services using XML for Analysis (XMLA) or can be used as a standalone reporting solution. We also use Java Message Service APIs (JMS) for internal module communications and reliable message delivery. JMS can also be used to interface with external Message Oriented Middleware (MOM) and Enterprise Service Bus (ESB) products in a vendor-neutral fashion.