Tibco Developer Resume

TECHNICAL SKILLS:

PROFESSIONAL EXPERIENCE:

Tibco Developer

Confidential

Responsibilities:

Requirements discussions with Business users.
Created Irise Hi - fidelity simulations during requirements phase
Identified new enhancements on existing applications
Improved user experience and interactions with the systems
Conduct SR meetings and Preparing System requirements Design Data mappings
Code reviews and management with offshore team in various tools & technologies like Coldfusion, Salesforce, Tibco .

Technical Architect

Confidential

Responsibilities:

Designed Nodal Implementation
Created Hawk monitoring framework with automated rulebase generator and dependency tracker
Customized GAL / GEH tools for clients
Designed Auto deployment framework
Worked on IBM Data Power
Common Service Middleware Architect

EAI Architect

Confidential

Responsibilities:

Designed RV based Global Routing Service, Retry service
Designed Audit & Logging service
Design Business processes ensuring Development best practices using BW Templates, following naming conventions etc

Sr, Tibco Analyst & Tech Lead Tibco Architect

Confidential

Responsibilities:

I was an Integration Architect & Confidential for OTC & SCM streams.Designed and documented common Tibco Confidential patterns for File based integrations, XI based XML applications and Web services implementations
Documented best practices in Tibco development to ensure sequencing, response time and performance of an application using Tibco EMS.
Communicated the process design to offshore development team
Comet Release 2.0: Tibco Analyst, XML Architect
I was an Integration analyst for FBM stream and mainly responsible to gather and document Integration Functional Specification, Desing SMF using OAGIS BOD's
Also responsible for Tech spec reviews and End to End testing

Sr B2B Tibco Developer

Confidential

Responsibilities:

This integration project implements the paper claims from Trading Partners (EDI 837), EDI 837 Institutional and professional claims. I am a member of architecture team to design solution and identify different services as part of 837 EDI processing.837 Claims will be assigned a Unique ClaimID by ClaimID Service and then ClaimSplitter will split 837 xml into multiple files, each file having only one claim. ClaimRouter service will route the inbound 837 claim to appropriate system (Denver, StLouis, Trizetto) within the enterprise.
Involved in architecting, designing and developing integration interfaces and services in Meridian department in various roles including senior developer, architect and Administrator, Analyzed various message loads, throughputs and designed EMS and BW engine topology accordingly, Architected, Designed and Developed JMS based RecoverableReplayService using BW and JMS

Sr Tibco Developer

Confidential

Responsibilities:

Project PRISM (PeopleSoft Re-Implementation at Confidential ) is a multi phased project driven by Human Resources and Information Technology teams.
Created Use cases and Integration System Sequence Diagram using Visio
Designed Personnel CDM(XSD)
Designed the high level and low level technical design documents with the help of UML methodologies
Created architecture diagrams for EMS topology and BusinessWorks deployment configurations for ensuring sequential processing
Involved in Architect decisions of using Soap over JMS(SSL channel) with data encryption provided as a new feature in TIBCO BW 5.3
Architected and designed the integration services to cater various requests
Established standards and guidelines for JMS queue names and RV Subject names
Evaluated TIBCO ADB adapter, Remedy Adapter, PeopleSoft Adapter against common standards and made the architect decision on the choice of technology
Trained Down stream application developers on TIBCO BW for 2 months

Tibco Developer

Confidential

Responsibilities:

Worked on a huge implementation "Sales & Services Management "
Involved in architectural discussions
Worked with application teams and designed the XSD’s, which acts as interfaces between various services
Established best practices in designing XSD Schemas
Established standards and guidelines for JMS queue names and RV Subject names
Created the BW project templates and configured shared resources and shared connections in the templates.
Created coding standards and guidelines document for other developers to follow.
Interacted with application team member and helped the business analyst to create requirement documents.
Created architecture diagrams for EMS topology and BusinessWorks deployment configurations.
Over saw the configuration of EMS servers load balancing and fault tolerance.
Designed the high level and low level technical design documents with the help of UML methodologies.