Portfolio

Various Completed Projects and Brief Details listed below. The BSIS portion of the projects were completed using Camel code deployed in JBOSS Fuse (Apache Karaf). Some projects are hosted together in a Fuse instance, others have their own instance to avoid any issues in one section of the ESB from effecting the whole system. Issues faced with other developers code was related to out of memory exceptions and thread starvation. By isolating new projects into their own instances core functionality is preserved. After thouroughly vetting performance in the wild, the decision can be made safely as to which projects to combined.


PartNumberAuditTool.jpg
Part Audit Tool
  1. Line items sent from BOSS, ISPS, and BISI in various flat file formats via WMQ
  2. Line items converted from various formats to an agreed upon XML format from BSIS to BDM via web service
  3. a,b,c,d Tradeability Customer XML request set from BDM to BSIS to CT and back
  4. a,b Final Classification Detail XML Sent from BDM to BSIS to CT
CertificateOfOrigin system diagram
Certificate Of Origin
Countries FGV internal customer system diagram
Countries FGV Internal
  1. The Brokerage System will SFTP into the BSIS FTP Server and place valid FGV XMLs in the default directory.
  2. BSIS will read and delete the FGV XML file from the Brokerage System default directory.
  3. If the FGV XML file validates against the FGV XSD the file will be sent to FGV.
  4. A successful or unsuccessful response will be written to the RESPONSE folder in the directory the file was read from.
Countries FGV external customer system diagram
Countries FGV External
  1. A Brokerage System outside the UPS network will use the FTP2 service. The Brokerage System will FTP to the FTP2 server and place valid FGV XMLs in the /outbound directory.
  2. FTP2 Server will send the file to the BSIS FTP Server default directory.
  3. BSIS will read and delete the FGV XML file from the Brokerage System default directory.
  4. If the FGV XML file validates against the FGV XSD the file will be sent to FGV.
  5. A successful or unsuccessful response will be written to the RESPONSE folder in the directory the file was read from on the BSIS FTP Server.
  6. FTP2 Service will move the response from the BSIS FTP Server /RESPONSE folder to the FTP2 Server /inbound/RESPONSE directory
  7. The Brokerage System will monitor the FTP2 Server /inbound/RESPONSE directory and retrieve the response message.
Redesign of Process Boss Upload
ProcessBossUpload
  1. fromBoss recieves messages from a WMQ on any server. Sequences the message if part of a JMSX message group and places the message in an AMQ for processing.
  2. processBossUPload takes the message from the AMQ and inserts it into the DB with a New Status
  3. pbuMessageControl starts with a timer trigger. It pulls out a list of the primary keys (PKs) of shipments in the New Status. Marks the Pks status as In Progress and puts them in a queue for parsing.
  4. The PKs are pulled from the queue. The messages are retrieved from the DB, parsed, and multicast to all appropriate destinations
  5. Some routes require sequencing by shipmentOID. This is done by the query that pulls from the DB. Only pks in the New Status with no other messages with the same shipmentOid are retrieved.