Architecture component description - HxGN EAM - 12.0 - Customization & Programming - Hexagon

HxGN EAM Architecture and Server Management
Language
English
Product
HxGN EAM
Search by Category
Customization & Programming
HxGN EAM Version
12

  • HxGN EAM Client Block - This component represents a PC (for example in a store) connected to the Internet and with an Internet Browser installed.

    • Html5 compliant browser (See H/W and S/W requirements guide for specific list) – JavaScript: This block represents a customer running the HxGN EAM Application utilizing the zero-footprint User Interface.

  • HTTP Server - This block, which may be formed by one or more servers, is connected to the Internet boundary. If the workload requires multiple servers, a load balancer is usually utilized (not shown on the diagram). This component receives Hypertext Transfer Protocol (HTTP) requests from a browser and responds with the screen content.

    • Static HTML - This block represents HTML static fragments which are stored on the HTPP server and cached for optimum performance.

    • Images - This block represents images which are stored and cached for optimum performance.

  • JSP/Servlet Engine - This component is responsible of dynamically putting together an HTML document, which will be sent back to the Browser. All presentation attributes are applied on this layer (i.e.: font size, images, colors, screen layout, etc.). No business rules are applied here!

    • OC4J - This block represents the Oracle Components for Java Servlet which directs the Thin User Interface Requests to the Forms and Reports processes.

    • Event Manager - This block represents the heart of the Model-View-Controller pattern, handling the data and system security requests to the respective Business Manager. This component also resolves the action to take as a result of browser event (i.e.: tab out of a field, click on a menu option, etc.). The distributed EJB call is performed using Remote Method Invocation (RMI) utilizing the Internet-Inter Orb Protocol (IIOP).

    • JSP Tags - This block represents an ultra-thin JSP which creates an XML fragment which is sent to the XSLT transformer.

    • XSLT Transformer - This component represents a set of stylesheets, which are user- dependent and get invoked to dynamically convert an XML result set into an HTML document.

  • EJB Container - This component has the responsibility of enforcing business rules and is the mechanism to add/update/delete data. No direct calls to the database are made as EJBs interacts with a DAO abstraction classes which handle the database communication.

    • Entity beans - This block represents the instantiated objects at a given time

    • Sessions beans - This block represent all the session state information which is needed from one client call to the next

  • Java Beans - This component represents a set of Java Bean classes

    • DAO - The Data Access Object is a set of classes which bridge the Object to Relational mapping and allows the EJBs to be utilized with different database vendors. The DAO classes connect through Java Database Connectivity (JDBC) drivers to the database.

  • Cognos - This component represents a set of Cognos ReportNet Servers

    • Gateway Server

    • Reports Server

    • Content Manager

  • Database Server - This block represents the data storage layer

MS SQL - This block represents Microsoft SQL Server database

  • Oracle RDBMS - This block represents the Oracle Relational Database Management System

  • Analytics DW - This block represents the Analytics Data Warehouse, which has Extraction, Transformation and Load stored procedures to create a fast access repository.

    For Cloud installs, databases are logically provisioned by Tenant ID and they are encrypted at the volume level. Each Tenant is provisioned with their own database schema; data segmentation occurs at the Tenant’s instance.

  • Mobile - This block illustrates the HxGN products HxGN EAM Mobile

  • VB.Net APP - This block represents the Mobile code written on Microsoft Visual Basic .Net

  • Web Services Engine - This block receives the SOAP calls and after verifying security, it calls the appropriate Business Manager to receive the XML result message. The distributed EJB call is performed using Remote Method Invocation (RMI) utilizing the Internet-Inter Orb Protocol (IIOP).

  • Custom App - This Block represent an application written by a third party consuming real-time Web Services, which may be written on any host language for example C. C++, Java, Visual Basic, Visual Basic .Net, C#, Lotus Notes, Microsoft Office, etc.

  • HTTP Server - This block, is connected to the Internet boundary. This component receives HyperText Transfer Protocol (HTTP) Simple Object Access Protocol (SOAP) requests from a client application and responds with an XML-SOAP Response. It also acts as storage of web services definitions utilizing the Web Services Definition Language (WSDL).

  • Databridge - This block represents the HxGN EAM Databridge product

  • In/Out Queues - This block represents two queues, one close to the HxGN EAM database, and one close to the ERP/CRM/HRIS system to integrate. The purpose of the queues is to guarantee delivery of the transactions posted on either end. Monitor software manages the status of these queues,

  • Data Maps - The data maps block maps the data elements from the OASIS compliant HxGN EAM messages to the target ERP/CRM/HRIS system. The connection to this system may be through JDBC, XML files or Flat files.

  • Customer APP - This block represents the client ERP, HR or HRIS system