We provide IT Staff Augmentation Services!

Websphere Message Broker Developer/architect Resume

2.00/5 (Submit Your Rating)

Wilkes Barre, PA

SUMMARY

As a developer and architect in the Information Technology Industry I use my leadership capabilities and technical expertise to make effective and lasting changes to the business systems and applications of the enterprises I service.

For 10+ years I have developed enterprise solutions for clients in banking, finance, healthcare and the federal government sectors utilizing WebSphere Message Broker technologies.

While with NEON I was introduced to the Enterprise Application Integration paradigm. This venture, into integration application processing, established my current career path and widened my understanding of enterprise solutions. While a member of NEON I functioned as a technical resource, an Account Manager and as an Engagement Manager.

During my 16 years of service for Salomon Inc. and Anderson Consulting I developed and maintained the International Clearance System. As the application Lead I interfaced with representatives of the external clearance organizations and shared in the management of many enterprise wide and industry wide projects.

May 2012 – Oct 2012, Confidential, Wilkes Barre Pa

WebSphere Message Broker Developer/Architect

  • Position summary: In this assignment our team was responsible for the development of new offerings for the United States Postal Service. Our initial application addressed the processing of USPS transactions for package delivery notifications. These notifications are delivered through the use of sms messages. We utilized HTTP technology to transmit the delivery notification transactions to AT&T for delivery to the subscriber’s handsets. Soap and MQ messages are used to deliver the data through the various application layers. The interface is the first of a new enterprise SOA/ESB solution being designed.
  • Obtained a USPS clearance
  • Technology: WebSphere Message Broker 7.0.0.4, WebSphere MQ 7, DB2, MQExplorer

Nov 2011 – Feb 2012, Confidential, Franklin Tn

WebSphere Message Broker Developer/Architect

  • Position summary: On this project my focus was to improve the performance of the DecisionSvc message broker project. This project executes the business rules that are applied to the subscribers. The application had been terminating prematurely for unknown reasons. It was determined that these failures were caused by inefficient esql coding. I examined and modified the esql code for 40 business functions and a number of the message flows which control the overall processing of these functions. Over 9000 lines of esql code were examined for multiple types of improvement. The improvements I applied addressed code efficiency and code correction.
  • Technology: WebSphere Message Broker 6.1.0.9, WebSphere MQ 6.5, DB2, MQExplorer

I also documented the WellBeingPlan project for the project retirement efforts of the off shore team.

Sept 2011 – Nov 2011, Confidential, Honolulu Hi

WebSphere Message Broker Developer/Architect

  • Position summary: While on this project I provided development and architectural support for their CIS system. I was primarily responsible for the development of their

Generic Error Handler. While working on this process I was asked to set up the promoted properties of the message flow and also to assist in the design and development of the message flows. This error handler was designed to capture the errors and report them through the use of a relational database table. This solution utilizes the MQRFH2 header to hold information and pass it to the subsequent flows. The process reads the exception list, which was created by the occurrence of the error, to capture the error message and number. The process also captures other message broker information to complete the error reporting. The information that is collected by this flow is sent to downstream message flows and inserted into the error table.

  • Technology: WebSphere Message Broker 7, WebSphere MQ 7, DB2, MQExplorer

I was also responsible to assist the message broker trainees. It was my responsibility to oversee their assignments and support them with answers to their development questions.

June 2011 – Sept 2011, Confidential, St. Louis Mo

WebSphere Message Broker Developer/Administrator/ Architect

  • Position summary: Architecture and development of the Authorization Service Bus. I was involved with the architectural review of their solution as well as a participant in the development efforts. I reviewed the solutions for efficiency and resiliency, documenting the suggested changes to their application. Performance issues, in both the message flow structure and the associated coding, were reviewed and suggested modifications were documented. I also created documentation addressing performance related enhancements in configuration, deployment and coding. The detailed design for the resiliency efforts for the profile information processing and the application logging process were developed. Transaction orchestration was also reviewed and suggested modifications were being considered. This modification will increase the efficiency of the transaction processing.
  • Technology: WebSphere Message Broker 7.0.0.1, 7.0.0.2, WebSphere MQ 7.0, DB2, AIX 6.0 , MQExplorer
  • Additional responsibilities included assisting other team members on the use of the WebSphere Message Broker and WebSphere MQ Series products as they pertain to the Authorization Service Bus being developed. My best practices and knowledge, obtained from previous experiences, were shared.

My development assignments addressed the resiliency efforts for the profile information and application logging processes. The design issues for these message flow solutions addressed the requirements of continuous processing and data retainment. The profile information solution utilizes a contingency data source while the logging process utilizes a timed reload process.

Feb 2011 – June 2011, Confidential, Philadelphia, Pa

WebSphere Message Broker Developer/Administrator/ Architect

  • Position summary: Development and maintenance of WebSphere Message Broker message flows for IBC’s HIPAA Process. The EDI messages are passed to the WebSphere Message Broker through a WebSpehre MQ Series queue. The data elements in these parsed messages are validated using esql to enforce the business logic. After the validations are performed the data is transformed to a proprietary format through the use of Neon Transformation nodes. These transformations are performed on both accepted and rejected transactions which are then processed by legacy applications and eventually various business partners.
  • Technology: WebSphere Message Broker 6.0, 6.1.0.8, WebSphere Transformation Extender 8.2.0.3, WebSphere MQ 6.0, DB2, AIX 6.0 , MQJExplorer
  • Responsible for assisting other team members on the use of the WebSphere Message Broker, WebSphere Transformation Extender and WebSphere MQ Series products as they pertain to the HIPAA solutions being maintained and developed. This entails relating best practices and knowledge obtained from previous experiences.

Current assignments address the maintenance of the 4010A 837I and 837P transactions. These are the claim transactions for Institutional and Professional business partners. The message flows for these two transactions contain over 35,000 lines of esql.

Nov 2008 – Nov 2010, Confidential, Jersey City NJ

WebSphere Message Broker Developer/Administrator/ Architect

  • Position summary: Development and maintenance of WebSphere Message Broker message flows and message sets as well as WebSphere Transformation Extender maps and trees in support of the banks transaction processing.
  • Technology: WebSphere Message Broker 6.0, 6.1.0.3, WebSphere Transformation Extender 8.2.0.3, WebSphere MQ 6.0, DB2, AIX 6.0 , Message Test 1.2, 1.3 QPasa
  • Worked with IBM on the installation, configuration and testing of the Enterprise Platform framework (EP). Formerly known as EPP, Enterprise Payment Platform. This framework consolidates a number of critical applications into a common processing scheme and data administration. I developed a deployment procedure to reduce the conflicts that occurred during the deployment operation. I also created a number of ‘adapter’ message flows to connect the mainstream processing to the new EP environment.
  • Performed the migration of the WebSphere Message Broker 5.0 message flows to the new WebSphere Message Broker 6.1 environment. This included the testing of all existing message flows.
  • Responsible for the creation of new WebSphere Message Broker environments. This includes:
    • Coordinating with the database administrators, system administrators and the WebSphere MQ administrators
    • Creating the Configuration Manager
    • Creating the WebSphere Message Broker(s)
    • Loading the acl entries
    • Setting up the access for the application databases
    • Setting up the toolkit Topology for multi-broker access

Nov 2003 – Nov 2008, Confidential,Washington DC
U.S. Customs

Application Architect/WMB Developer (Full Access Security Clearance)

  • Position Summary: The Customs and Border Modernization Project is a large scale integration solution combining several key legacy applications concerning border crossings and financial transactions.
  • Technology: WebSphere Message Broker 6.0.2, WebSphere MQI 2.1, WebSphere Transformation Extender 8.0.1, WebSphere MQ 5.3 and 6.0, WBIA 5.5.5 and 6.0, DB2, AIX 4.3.3, OS/390
  • Developed message flows, MRM’s and WTX maps to support the processing of truck manifests and related transactions, application synchronization messages and insertion of financial transactions to a DB2 database
  • SME on all queuing and message flow issues
  • Monitored the MQ Series queuing system, the memory utilization of the WebSphere Application Server and error/application queues for the WMB / WMQI message flows
  • Developed procedural write-ups for knowledge transfer
  • Replayed transactions when system outages occurred and handled all related queuing concerns
  • Utilized segment tags to reduce the processing of a manifest from 200 seconds to 16 seconds
  • Worked with various application groups to ensure complete and accurate data transfer
  • Oversaw architecture of the asynchronous services
  • Other responsibilities

Deployment and Migration into multiple environments
Maintenance of the WBIA configuration file and repository
Documenting development issues
Assisting in the creation of new test environments
Technical support for development team members
Testing (Unit and Integration)

Nov 2001 – Nov 2003, Confidential, Philadelphia, Pa

Application Architect / WMQI Developer
Position summary: The HIPAA (Health Insurance Portability and Accountability Act) development project was a large-scale, governmentally mandated integration effort between the X12 EDI standard and IBC’s proprietary formats to allow for continued access to legacy applications and databases.

  • Technology: Websphere MQI 2.1, NEON, Websphere MQ 5.3, DB2, AIX 4.3.3, OS/390
  • Set the direction for the processing design of the conversion project
  • My responsibilities included:
    • Determining processing standards
    • Ensuring that business needs were met with planned implementation(s)
    • Acting as a technical resource for the development team
    • Coding and testing WMQI message flows and NEON formats
    • Assisting other team members on technical issues
    • Technical support for other application groups with their WMQI implementations/modifications
    • Conducting performance testing and implementing performance tuning

Dec 1997 – May 2001, Confidential, New York, NY

Engagement Manager
Position summary: NEON (New Era Of Networks) was one of the earliest companies in the EAI (Enterprise Application Integration) arena, where I was involved in every aspect of their consulting service.
Technology: NEON Formatter and Rules, eBiz Integrator, MQ Series 5.1, DB2, OS/390
Created SOW’s (Statements of Work) describing project objectives and setting vendor/client responsibilities
Coordinated with clients to assess their needs and propose new projects
Reported status to President of Professional Services and oversaw team of Project Managers

Project Manager
Created and maintained project plans while overseeing the development team
Led staff in problem resolution and reported related status
Communicated with clients on their day to day requirements

Technical, Hands-on Consultant
Developed NEON formats and rules to support client business process
Oversaw migration of NEON metadata between different environments and conducted related testing
Wrote C++ user exits, gathered requirements, maintained documentation and interrogated data

1994-1997, Confidential, New York, NY

Project Leader / Developer
Technology: COBOL, IMS, JCL, TSO, OS/390
Designed, coordinated and executed enterprise wide test plan for the “T+3” trade settlement cycle change
Interfaced with domestic/international clearance agents and client’s business organizations
Served as Project Leader/Programmer on various International bookkeeping applications

1993 – 1994, Confidential, New York, NY

Project Leader / Assistant Vice President
Technology: COBOL, IMS, JCL, TSO, OS/390
Maintained and supported the POLARIS custody application
ADHOC requests for custom reports and data transmission assistance

1981 - 1993, Confidential, New York, NY

Project Leader / Developer
Technology: COBOL, IMS, JCL, TSO, OS/390
Developed and managed the International Bookkeeping Entry system (IBE)
Created and supported the transmissions to international clearance agents: Euroclear, Cedel and Citibank
Facilitated move of the back office operations from New York, NY to Tampa, FL

Skills Profile

Middleware:

WebSphere Message Broker 6.0.2, 6.1.0.9, 7.0; WebSphere MQ Integrator 2.1; WebSphere Transformation Extender 8.0.1, 8.2.0.3, 8.3.0.3; WebSphere MQ 6.0, 7.0; MQ Series 5.3; MQ Explorer; QPasa, MQJ Explorer; MQ Mon; WBIA 5.5.5; Neon Rules and Formatter 3.62: NEON Adapter for XML

Productivity Tools:

MS Project; MS Office; FTP; Visio

Hardware:

PC Workstation; OS 390

Operating Systems:

AIX 6.0, 4.3.3.; Windows 2000, NT; XP; OS390

Languages:

C++, COBOL, ESQL

Databases:

DB2; IMS (DB/DC);

Protocols:

SWIFT, ASC X12, EDIFACT, TCP/IP

We'd love your feedback!