This project will Provide a single source of shipment tracking and Customer information to FedEx applications to portray a consistent end-to-end view of every shipment, regardless of which OpCo or the number of OpCos handling the shipment.
This is a huge integration effort by this logistics company to collect and manage the information about their clients and shipments. Their 5 different operating companies are sending the 75 millions messages a day to this system to manage data. The system expected to respond with 2500 tps rate using 29 Linux boxes. The query expected to respond with in 0.025 seconds.
o To support the Transaction Per Second (TPS) requirements, Project rejected the Message Driven Beans (MDB) and implemented unique Session bean architecture
o TIBCO JMS services are wrapped under by custom classes (Decorator pattern) to gain grater reporting and monitoring control
o Preset dictionary based compression is used to save database space
o Since most of the query services are from the internal servers who again pass the data to down stream systems, http response are developed (similar to SOA). Web Service are planned only for the https requests with a full pledged XML response
o A Complete XML based message versioning is implemented to support multiple systems and simultaneous development. Major and minor schema versioning strategy is applied.
Future Development:
Implementing Business Workflows using TIBCO Business Work is being POCed. Initial work will commence soon
Current Responsibilities:
I am Involved in primarily in Message processing area. I am primarily involved in Message Quality Assurance (Schema validation and business workflow), Replay support, Logging/reporting services and some of the screen development.
I am also responsible for managing the Integration of components and Quality Assurance of the integrated components.
I am also managing for generic components and tools development. A struts and Tiles based web server is maintained for dissimilating project information.