Varun Rajasekaran-TIBCO

1 | P a g e
VARUN RAJASEKARAN
(949) 371 -7649
varunvaidya85@gmail.com
SUMMARY
 7 years of experience working in IT.
 6.5 years of experience in working with different SOA and EAI tools such as TIBCO and Mule
 Excellent experience in installing, configuring and maintaining TIBCO Infrastructure in Linux, Unix
and Windows environments.
 Excellent experience in developing, testing, deploying and managing Tibco Data Integrations.
 Excellent experience in Tibco EMS Administration.
 Experience in coding and performance tuning Tibco Data Integrations and Tibco EMS.
 Have worked in setting up Development best practices for TIBCO BW, ADB and BC for a more stable
Production Environment
 Administration experience in Tibco Business Events and Active Spaces
 Experience in automating TIBCO deployment using ANT
 Experience in developing JMS standard of applications for communicating with Tibco EMS.
 Experience in MQ administration (Mainframe and Unix) and converting MQSI integrations to Tibco.
 Experience in using Tibco Hawk, Sitescope and Unix scripting for monitoring Tibco Integrations,
Databases, MQ, EMS and managing middleware environment involving TIBCO and MQ.
 4 years of experience in working as a Team Lead.
 3.5 years of experience in working at Client Site.
 Experience in developing Standards/Process for Enterprise application integration.
 Excellent experience in EDI, for B2B communication, and in administering the EDI environment.
 Experience in using CA API Gateway and Splunk
SKILLS SUMMARY
Operating System: Windows 2000/XP/7, Linux, UNIX
Integration Tools: Tibco Designer 5.x, Tibco RV 7.x & 8.x, Tibco Business Works 5.x, Tibco ADB 5.x, 6.x and
7.x, File Adapter 5.x, Teradata Adapter 5.x, LDAP adapter 5.x, Hawk SNMP adapter
4.x, TIBCO Business Connect 6.x, TIBCO Business Events 5.x, TIBCO Active Spaces 2.x,
TIBCO GI, WMQI Control Centre, MQ Explorer, Mule.
Monitoring Tools: TIBCO Hawk 4.7, Qpasa, Splunk
Versioning Tools: TIBCO XMLCanon.
Messaging Servers: TIBCO EMS Server 4.x and later, IBM Websphere MQ.
Message Browsing Tools: EI Explorer, MQJ Explorer, Hermes.
B2B tools : GXS Enterprise, GXS Application Integrator, Axway Cyclone,
TIBCO Business Connect.
API Gateway tools: CA API Gateway
Databases : Oracle, DB2, MS SQL.
Languages : C, Java.

Varun Rajasekaran
2 | P a g e
EXPERIENCE HIGHLIGHTS
Organization: UST Global
Project #1
Title : Migration and Domain Stabilization
Client : HEB Grocery Company
Operating System : Linux, Unix, Windows
Software/Tools : TIBCO Administrator, EMS, Hawk, BW, ADB adapter, Teradata Adapter,
LDAP Adapter, File Adapter, RV, XML Canon, Layer 7, Splunk
Team Size : 11
Role : Onsite Lead
Period : 10/01/2013 to current
Project Objective:
The objective of this project include migrating off of the old Dell hardware and Linux OS and upgrade the
entire TIBCO Product Suite, used in our domains, comprising of Tibco BW, EMS, RV, Hawk, ADB Adapter,
File Adapter, LDAP Adapter and Teradata Adapter along with the deployed Integrations, hawk rules and
the running EMS instances.
Project Description:
The Dell Blade servers in which the TIBCO software was running were going to be Out of warranty and the
Linux Redhat release and TIBCO Product Suite was going to be out of support. So we undertook a project of
upgrading and migrating the entire TIBCO Product Suite to newer Hardware and Linux Redhat release.
This project was done in an environment, where very minimum downtime was allowed, as HEB requires
the TIBCO services to be running 24*7
Role and Responsibilities:
As the onsite lead for this project, I was involved in the following activities.
 Work with different application teams, connecting to the several EMS instances and plan for
migrating the TIBCO EMS instances to newer hardware and also upgrade the TIBCO EMS from 5.0
and 7.0
 Plan on migrating the different BW Pub-Sub, P2P and web service Integrations from BW 5.6 to BW
5.10
 Installation, configuration and benchmarking of Tibco Business Events and Active Spaces
 Do POC on Layer 7 to be used in the web service architecture for better monitoring, security and
flexibility

Varun Rajasekaran
3 | P a g e
 Do POC on configuring BW, Layer 7 and EMS to write logs to SPLUNK
 Test these different migration plans in Certification with different application and server teams
 Identify areas of improvement with the different Integrations, monitoring systems and Root cause
analysis of recurring issues
 Delegate these different tasks to offshore and monitor and help them in getting it completed
 Document the details on the new environment and create Problem Determination Procedures for the
different systems in the new environment
 Sharing the knowledge with the team.
The major tasks I have completed while working in this project are;
TIBCO EMS Migration
In this project, I was leading the effort, from a TIBCO Admin perspective, in migrating the different
EMS instances to newer Dell Servers with Red Hat release 5.11 and also upgrade the EMS from 5.0
to 7.0. This effort also included changing the EMS cluster monitoring software from Veritas
Clustering to Red Hat Clustering
This effort required contacting the different applications that were using the JNDI factories to
connect to the EMS instances and plan the migration in a way that would require the least
downtime. There were 19 such EMS instances servicing different application teams.
Since the EMS software was also being upgraded from 5.0 to 7.0 and there were several addition
features included in the 7.0 release like the usage of multi core processors we had to do a proper
benchmarking of its capabilities and test the migration plans in certification before implementing in
Production.
The EMS cluster monitoring software was also changed from Veritas Clustering to Red Hat
clustering which was completely automatic in failing over a particular EMS instance to another
server in the cluster in case of an EMS shutdown.
TIBCO BW/Adapter Integrations Migration
In this project, I was leading the effort, from a TIBCO Admin perspective, in migrating the different
BW Integrations to the new domain with the newer servers and also upgrade the BW from 5.6 to
5.10. These Integrations include the Pub-Sub, P2P and web services Integrations using BW and
different adapters including File, ADB, TERADATA and LDAP. It required elaborate testing and
even code changes with some of the Integrations that had plug ins that didn’t behave the same way
when upgraded; like the Cobol Copybook plugins.
As part of the web service migration we introduced Layer 7 gateway in the web service framework
for better monitoring, security and flexibility. Previously we were just using F5 for web service load
balancing. But during the migration we did a POC by introducing Layer 7 between the F5 and the
web services to better manage and monitor the usage of our web services
We also did a POC on Splunk as part of this migration to store the logs from BW, EMS and Layer 7
by modifying the syslog.conf files in the servers

Varun Rajasekaran
4 | P a g e
Root cause Fixes
As part of this project we had also come up with a list of problems that needed root cause analysis
and fixes. This included gaps in the monitoring system, Production incident reduction, analysis of
recurring incidents and coming up with fixes for them.
Project #2
Title : TIBCO, MQ &EDI Administration and Applications Production Support
File Adapter, RV, XML Canon, Hermes, MQ, Qpasa, GXS
Enterprise, GXS Application Integrator, Axway Cyclone, Business Connect.
Team Size : 6
Role : Onsite Lead
Period : 01/01/2012 to 10/01/2013
Project Objective:
The objective of this project includes providing support and maintenance of the Enterprise Application
Integration and Electronic Data Interchange environment in a 24x7 critical applications portfolio for HEB, a
privately held San Antonio(Texas) based supermarket chain with over 300 stores, more than 10 Warehouses
and 56,000 employees.
HEB uses TIBCO and MQ as the middleware solutions for integrating all the different applications spread
across the Linux, UNIX & Windows environments, in stores and warehouses. The TIBCO infrastructure
consists of more than 300 administration domain and more than 2000 Integrations. It consists of 2 Central
Production domains one for EAI and the other for EDI (TIBCO Business Connect). HEB uses EDI for the
electronic commerce with the trading partners.
As the onsite lead for the TIBCO, MQ and EDI Administration and Production Support (24x7) team, I was
involved in the following activities.
 Supporting and Administering more than 300 TIBCO administration domain and more than 2000
TIBCO BW Integrations deployed in these domains.
 Analyzing, estimating, prioritizing and resolving production support requests opened for the team.
 Lead the team in resolving critical Production issues.
 Interacting one to one with the client POC for gaining business and application knowledge.
 Documenting the knowledge and learning from project experiences. Creating and maintaining
System appreciation, problem Determination Procedure and best practices documents.

Varun Rajasekaran
5 | P a g e
 Sharing the knowledge with the team.
 Planning, prioritizing and delegating the tasks to the team members.
 Undertaking root cause analysis on situations. Working towards creating a high availability
application environment by decreasing the number of incidents through root causes fixes.
 Working along with client managers, partners and the team towards continuous improvement of
the systems to enhance client business and to maintain a high level customer satisfaction.
Suggesting areas of improvements. Analyzing and assessing the enhancement scope, identifying
technical solutions and alternatives, developing estimates and deliverables.
 Identifying TIBCO Integration enhancements, developing, testing and deploying.
 Creating test cases and maintaining the test data for future.
 Managing and maintaining XMLCanon.
 Performing routine operational middleware administration activities.
 Installing, configuring, and testing TIBCO software patches and new versions in conjunction with
other Application Development teams.
 Coordinating the planned and emergency application changes in Integrations and the
environments.
 Planning and deploying application changes and software upgrades in the different environments
in conjunction with Application Development teams.
 Managing capacity including capacity planning and monitoring usage limits.
 Performing Middleware/Application Performance Management and Fault Monitoring.
 Designing and creating Hawk rules for monitoring and managing the TIBCO Applications, TIBCO
Administrator, EMS, EMS objects, MQ Queue Managers, Server resources and Databases.
 Administering EMS and Creating EMS objects including queues, topics, bridges, routes, durables,
users, groups for all different environments.
 Configuring RVD and RVRD for Business Connect.
 Installation of TIBCO Software in Linux, UNIX & Windows environments.
 Creating SWDs and RPMs for installation in Solaris and Linux Servers.
 Creating and managing the MQ Queue Manager, queues and channels, in UNIX and WINDOWS
environment.
 Configuring the trading partners, document and trading relationships in the EDI system.
 Monitor different EDI transactions like 204 (Load Tender), 214 (Shipment Status), 210 (Loada
Tender Response), 850/875 (Purchase Orders), 880/810 (Invoices) and 820 (EFT Payment)
 Developing processes and guiding the team to comply with these processes.
 Creating shell scripts for monitoring and management purposes.
TIBCO EDI migration
In this project, I was leading the effort, from a Production Support perspective, in migrating EDI
from legacy system to TIBCO Business Connect environment.
The legacy system had consisted of GXS suite of Products which was basically used for translating
multiple EDI documents to a format as required by the back end system using different model files.
It was using Axway Cyclone and GXS VAN for transport.

Varun Rajasekaran
6 | P a g e
In an effort to integrate EDI in to TIBCO, all EDI documents were migrated to TIBCO BC where the
Business Connect instance was doing the translation from EDI standard to XML or vice versa
depending on whether it’s inbound or outbound EDI.
Private processes were either updating a back end system or feeding off of a backend system and
converting the data from XML to the format required for the backend system or vice versa
depending on whether it was inbound or outbound EDI.
This project involved the following tasks
 Setting up a testing environment to test all EDI documents
 Troubleshoot failures and suggest development team for fixes
 Migrate monitoring scripts from Legacy to TIBCO environment
 Seamless migration in Production from Legacy to TIBCO BC
Some of the EDI documents that were involved in the migration include Purchase Orders, ASNs,
Invoices, Logistics data and Bank Transactions. Transport protocols currently being used in TIBCO
BC include AS2, FTP, SFTP and SOAP.
TIBCO Version Upgrade
In this project, I was leading the effort in TIBCO version upgrades for the EDI and EAI domains in
DEV, CERT and PROD environments.
TIBCO EAI domain upgrade (Mar 2013 to Jun 2013)
Since some of the TIBCO Products were nearing end of Support and to resolve some Production
issues we had planned to migrate to newer EAI domain. We had upgraded RV 8.1 to 8.3, TRA 5.6 to
5.7.4, BW 5.6 to 5.7, EMS 5.0 to 7.0 and ADB 5.5.0 to ADB 6.3
This project involved working with TIBCO Support to resolve compatibility and other issues with
the new Software, changing the Infrastructure architecture to suit the new TIBCO Products, test
multiple Integrations in the new Environment and a seamless migration from the existing to the
new environment in Production
TIBCO EDI domain upgrade (Nov 2012)
The TIBCO EDI domain was a little more than year old and since we wanted some additional
features we had migrate to a newer TIBCO EDI domain. We had upgraded RV 8.1 to 8.3, TRA 5.6 to
5.7.4, BC 5.3.3 to 6.0.1, BW 5.6 to 5.7, EMS 5.0 to 7.0 and ADB 5.5.0 to ADB 6.3.
We had to upgrade to TIBCO BC 5.3.3 from 5.3.1 (pretty easy upgrade) and then to 6.0.0, to be able to
upgrade to BC 6.0.1. The upgrade to 6.0.1 brought in some significant changes like the JRE upgrade
to 1.6 and changes in communication between Gateway and Interior server

Varun Rajasekaran
7 | P a g e
Earlier we had been using a DMZ instance of Business Connect and Interior instance of Business
Connect and they were communicating over RVRD. With this change the DMZ instance was
replaced by a Gateway Server (GS engine) that uses JMX and RV (RVRD) communication with
TIBCO Administrator and Interior Server
Apart from working in the above project, I was also involved in conducting trainings and interviews for
new comers. I was involved in arranging training sessions for the team from TIBCO consultants
Project #3
Title : TIBCO, MQ &EDI Administration and Applications Production Support
LDAP Adapter, File Adapter, RV, XML Canon, Hermes, MQ, Qpasa, GXS
Enterprise, GXS Application Integrator, Axway Cyclone, Business Connect.
Team Size : 6
Role : Team member
Period : 05/01/2009 to 12/31/2011.
Project Objective:
The objective of this project includes providing support and maintenance of the Enterprise Application
Integration and Electronic Data Interchange environment in a 24x7 critical applications portfolio for HEB, a
privately held San Antonio(Texas) based supermarket chain with over 300 stores, more than 10 Warehouses
and 56,000 employees.
HEB uses TIBCO and MQ as the middleware solutions for integrating all the different applications spread
across the Linux, UNIX & Windows environments, in stores and warehouses. The TIBCO infrastructure
consists of more than 300 administration domain and more than 2000 Integrations. It consists of 2 Central
Production domains one for EAI and the other for EDI (TIBCO Business Connect). HEB uses EDI for the
electronic commerce with the trading partners.
As the offshore TIBCO/MQ/EDI Admin/Production Support team member, I was involved in the following
activities
 Supporting and Administering more than 300 TIBCO administration domain and more than 2000
TIBCO BW Integrations deployed in these domains.

Varun Rajasekaran
8 | P a g e
 Reporting to the Onsite lead on daily tasks and check for Pending tasks.
 Maintain team related trackers, folders and PDP.
 Administering EMS and Creating EMS objects including queues, topics, bridges, routes, durables,
users, groups for all different environments.
 Installing, configuring, and testing TIBCO software patches and new versions in conjunction with
other Application Development teams.
 Deploying the project in the development environment and creating the hawk rules for this
application.
 Installation of TIBCO Software in Linux, Unix & Windows environments.
 Creating SWDs and RPMs for installation in Solaris and Linux Servers.
 Creating and managing the MQ Queue Manager, queues and channels, in UNIX and WINDOWS
environment.
 Work on failures in EDI inbound documents from Trading Partners on a daily basis and
communicate to them to get it resent and resolved
Creating RPMs and Installing TIBCO Software in the Store servers
In this project, I was leading the effort to build TIBCO environment in more than 300 Linux servers
located at different stores. The TIBCO domain setup process was automated by building RPM
packages. The RPMs were designed and created for installing the TIBCO products, configuring the
environment, security, deploying the TIBCO Integrations, creating EMS objects, deploying hawk
monitoring rules and scheduling scripts. This project required simultaneous efforts of different
other application teams and had to be completed on time to meet the business requirements.
Project #4
Title : POC on Mule (An Open Source ESB tool)
Client : EA Sports
Operating System : Windows
Software/Tools : Mule ESB, TIBCO
Team Size : 1
Role : Team Member
Period : 03/01/2009 to 06/01/2009
Project Objective:
The objective of this project includes doing a POC in Mule for the client, EA Sports. This meant creating use
cases and developing appropriate solutions and presenting it to the client

Varun Rajasekaran
9 | P a g e
The client wanted to switch to an Open source tool for implementing SOA in their architecture. So we were
involved in doing a POC for the Standard edition of Mule to study, create and test use cases and suggest
them to the client. Direct interaction with the client was very limited.
As the offshore team member, I was involved in the following activities
 Do a POC to understand the features of the tool
 Responsible for one to one interaction with my manager to get the client requirements and design
use cases accordingly
 Creating design document to project the use cases and solutions
 Identify opportunities to make the tool to communicate to different external systems
EDUCATION, TRAINING & CERTIFICATIONS
 Education Details:
 Completed Bachelor of Engineering in Electronics and Communication engineering from Anna
University, with First Class.
 Training Details:
 Underwent two months course in Software professional Training.
 Two months training in TIBCO. This included TIBCO Rendezvous, TIBCO BusinessWorks, TIBCO
Administrator, TIBCO EMS, TIBCO Adapters, TIBCO Workflow, TIBCO Hawk and XML Canon.
 Attended several classroom training sessions on UNIX, PL/SQL and Java.

Varun Rajasekaran-TIBCO

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Varun Rajasekaran-TIBCO

Similar to Varun Rajasekaran-TIBCO (20)

Varun Rajasekaran-TIBCO