Objective


Over 7 years of IT experience with different technologies which includes WebMethods 6.1/6.01 Trading Networks, Main Frame Interation Server, UCCnet Implementation, Backstage Adapter, SAP R/3 Adapter, MQ Series Adapter, Siebel Adapter, JAVA, EJB, JSP, Servlets, RMI, JAVA SCRIPT, JAVA BEANS, HTML, XML and UNIX. Extensive experience in WebMethods Server administration and Unix servers. Strong communication and interpersonal skills with the ability to work in a challenging environment.

Deep knowledge of EAI and B2B solutions and Techniques Enterprise Architecture, Canonical Design, Request Reply Framework, B2B Design, Hub Partner Consolidation, Inbound Outbound Transformation Framework. Experience in Building integration solutions for Mainframes/Mid-Range/Client-Server/ERP systems.

Sun Certified Java 2 Programmer

SKILLS : Languages Java, C and C++
Designing Tools Microsoft Visio 2000.
WebMethods WebMethods 6.01 webMethods Enterprise Server, WebMethods Integration Server, Trading Networks, Workflow Server, Modeler, webMethods UCCnet Adapter, webMethods Backstage Adapter, webMethods SAP R/3 Adapter, EJB Adapter, Siebel 7.0 adapter, WebMethods EDI Adapter, MQSeries Adapter, Oracle Adapter, Integration Logic Agent, Application Transaction Coordinator Adapter, Siebel 7.0/2000 Adapter
Error Tracking Crowe Chezik C2Track with ILA.
Knowledge Adapter Development Kit, JDE OneWorld Adapter, XML Adapter and IO Adapter.

Java Skills
Java 1.2 Java Applets, Java Beans, Java Swing, Java Servlets, JSP, JDBC, RMI, HTML, DHTML
Development Tools Gentran, Visual Caf, IBM Visual Age 3.5.
Middle Tier EJB with WebLogic 5.1 and IBM WebSphere 3.5
Databases ORACLE 8i/11i SQL Server, MS-Access and Sybase.
Web Servers Tomcat 3.2 Apache 1.3 and JavaWebServer 2.0
Application Servers WebSphere 3.5 WebLogic 6.0/5.1
Operating Systems Windows NT, Win2K, Unix and Solaris


Employment

2005 -  Present
Senior webMethods Developer

SDR is an interface with a acquired Bank by Banknorth. The interface integrates with Banknorth's back end Mainframe using MIS. The basic functions implemented for the SDR are
Customer Locate, Statement Transaction Details, Funds Transfer, Stop, Hold Check Payments.

Environment : webMethods 6.1 Mainframe Adapter, MIS, JSP, Java, PS Utilities, Common Utilities, XML, Host Messaging, CVS version control Systerm.

2005 -  2005
Technology Lead

COSAR
provides a facility to receive and validate Service Activation Requests from cable operators and soon from the internet, calls services provider Cable Operator C. The SARs are requests to activate a subscriber, telephone number, so COSAR distributes them to :
OSN, FRNT
for emergency services activation ; and SSBS for billing activation.

The COSAR Functional Specification identifies that the application was required to : Provide a single point of entry for Cable Operator SARs either by file or user interface.
validate the Cable Operators SARs and send response, via CDTRANS, detailing whether each SAR was accepted or rejected.
Maintain a central database of Cable Operator SARs.

Distribute SAR, cable operator subscriber information to other systems which included in their context diagram : o FRNT for emergency services activation.
o SSBS for billing activation.
Improve the service offered to Cable Operators and reduce the 72 hours service level from receipt of a SAR to acting on all relevant C and W applications to 24 hours. Note : the new requirement being to reduce this to 12 hours.
Cater for projected volume increases to 10000 SARs per week by April 1993. Note : currently COSAR is processing on average 10000 SARs per day, with migration peaks at 50000 per day and an overall record of 100000 per day.

The SARs enabled Cable Operators to : Add a new service
Cease an active service
Modify an active service
Cancel, Kill a pending SAR.
TOS or ROS an active service

Environment : webMethods 6.1 Generic FTP utility, Java, J2EE, EJB, WebSphere App Studio, Portlets, Rational Rose, Visual Source Safe, Oracle 9i, SQL * Plus.

Motorola Incorporation, Chicago, IL Sep04 to Oct 04

Migration of webMethods Projects into Clustered Environment Migration Coordinator

Part of infrastructure team and helping the team in setting up the webMethods 6.1 Cluster Environment to port all the stand alone Projects onto new webMethods 6.1 Cluster.

Motorola has got 100s of Integration projects that are non clustered and running on Active works 3.0 webMethods 4.x and webMethods 5.x and also on webMethods 6.x. This Migration project is to bring all the environments under 1 roof with webMethods 6.1 Cluster.

Motorolas eStandard documents are Rosettanet PIPs. Using webMethods PRT, Modeler, Monitor, Deployer tools as part of the Migration.

Responsibilities : Understanding the Architecture of existing projects and porting it onto new Cluster environment.
Deploying each project and necessary components using webmethods Deployer.
Integration testing of each project by involving the development teams and trading partners if necessary.
Generating and deploying the Models for the required projects.

Deploying the Trading Networks profiles, docs, processing rules and TPAs using wm Deployer.
Setting up remote aliases, JDBC connections required for each project architecture.
Configured the extend settings, for the session time outs between remote connections.
Configuring the Motorola proprietary Utility packages to store, access data that is ported between environments using xml file. Developed using the pub. storage services.

2004 -  2004
Administrator

The project involved synchronizing Catalog Item data with UCCnet Global Registry using webMethods UCCnet Adapter, webMethods Backstage Adapter. The Item Master being maintained in General Mills ERP SAP. The relationships between an item and the retailers who are subscribed to the item are maintained in the Oracle database named DLS.

The webMethods process initiates when a scheduler job pushes an IDOC from SAP to webMethods with all the active items with in last 24 hrs. webMethods process determines the new items to be added, changes if any for the existing items and any items that are to be removed from the Global Registry and Publishes to the Broker. Another process on webMethods subscribes to the document and act upon the action add, update or delete on the Backstage database.

UCCnet maintains the data pool of all items published by a Supplier in the Global Registry. Retailers will subscribe to the Global Registry of UCCnet for any updates. UCCnet sends or receives documents using EDIINT AS2 or UTAPI transport protocol.

Backstage database is a replica of the UCCnet Global Registry at the supplier side. Backstage Adapter comes with webMethods will give the User Interface to add, review, update, delete catalog items from Backstage and submit the request to UCCnet manually.

Responsibilities : Involved in design, architecture for the implementation of UCCnet and Backstage for Supplier side of the world.
Creating technical design specs for the interface UCCnet implementation with SAP and Oracle
Material Master is maintained in SAP and every day SAP R/3 Adapter pulls all active items that are changed with in last 24 hrs from SAP as IDOC.
Configuring the Partner Manager routing rules for inbound and outbound transactions.
Configuring the UCCnet Adapter to route the documents from Backstage to UCCnet Global Registry.
Installing and Configuring the Backstage Adapter for maintaining the Backstage Data pool at Supplier site. Oracle database is used to create the Backstage data pool schema.

Created profiles and setting up the Trading Partner Agreements in Trading Networks.
Configuring and applying the certificates for EDIINT AS2 connectivity to Global Registry.
Involved in designing the Canonical object for publishing to Broker.
Involved in developing the services to push data into Backstage database by crunching through the IDOC received from SAP.
Designing the Business Process Model for the back end development to push data into Backstage using webMethods Modeler.

Environment : webMethods 6.1 Trading Networks, webMethods Modeler, UCCnet Adapter, Backstage Adapter, SAP R/3 Adapter, JDBC Adapter, EDIINT AS2 HP Unix.

2002 -  2004
Administrator

Involved in Installation of webMethods 6.0.1 Server as both Back End and DMZ server on HP-Unix server. Also involved in setting up multiple instances of webMethods 6.1 Servers on IBM AIX. Installation of Adapters and configuring the Adapters. Also supporting the Development team during production as ON CALL support.

Flextronics is 1 of the largest customers of Avaya. Avaya Supply chain uses webMethods 6.01 server to communicate with Flextronics for the entire business to be done online.
Inbound : Avaya sends the quotation to the Flextronics through a tool called GES Configuration tool. The Flextronics then place the order based on the quotation through the Secure FTP as flat file. The flat file is picked up by webMethods polling services on the reverse invoke server and then webMethods server invokes a service on webMethods back end server which will process the purchase order and sends it to SAP R/3 using defined routing rules as an IDOC.

Outbound : Avaya sends the shipment notice, goods delivery notice and other documents to Flextronics. The IDOCs from Avaya SAP R/3 system will comes to webMethods through webMethods SAP Gateway and SAP listener on webMethods server. The routing rules or defined to receive the IDOCs from SAP and invoke a service on webMethods backend server with the IDOC as an input. WebMethods Services will process the IDOC and converts the IDOC into Flextronics understandable format and generates a flat file and ftp the file to Unix server. Then we have an autosys job that does the Secure FTP to Flextronics and notify the support team incase it fails while sending.

Responsibilities : Configuration of SAP R/3 Adapter for the SAP Production Server.
Creating, Defining the SAP Listener.
Creating webMethods SAP Gateway in SAP R/3.
Creating routing rules for the IDOCs to be processed in both inbound and outbound transactions.
Converting the EDIFACT documents to IDOCs and vice versa.
EDIINT AS2 documents transported to through Trading Networks to the external partner.
Generate MDN acknowledgements and pass it back to the trading partner.
All the communication is thru the secured HTTPS protocol.
Developed flow services to process the IDOC came from SAP R/3 and generate flat file.
Developed flow services to process the EDIFACT documents and generate IDOC to send it to SAP R/3.

Environment : webMethods 6.01 Server, Trading Networks, SAP R/3 adapter, EDIINT, AS2 standards, EDIFACT 97 Flat files, SAP R/3 HP-Unix and Windows 2000.

Fault eBonding, Trouble Ticketing Senior Developer, Administrator

Project Scope : Avaya Communications is a vendor to AT and T telecom for the fault eBonding project. EBonding is basically to report the trouble tickets opened for a problem found at AT and T sites to Avaya. Avaya service people will go and fix the problem with in a time period and notify AT and T when its fixed. All the transactions passes through Avaya Trading Networks for both inbound and outbound. AT and T is using the CIM Standard XML's for document exchange with Avaya. Avaya uses MQ Series Adapter to communicate with Avaya backend which handles the Trouble Tickets called Maestro.

Responsibilities : Involved in design Documentation for the implementation of eBonding
Designed Microsoft Visio presentations for the inbound and outbound transaction flow diagrams

Created profiles, Document Types and Processing Rules in Trading Networks for eBonding.
Configured WebSphere MQ Adapter for transferring messages to message queue.
Designed and created Canonical object for publishing to Broker.
WebMethods flow services transforms XML coming from AT and T into fixed length string and sends it to MQ Adapter for delivery to the back end called Maestro for inbound transactions.
WebMethods flow services transforms the fixed length string into CIM standard XML format which is AT and T defined format and sends it to Trading Networks for delivered to AT and T using HTTPS for outbound transactions
Used publish, subscribe model for multiple vendors to be involved in future.
Involved in coding the flow services and java services.
Involved in unit testing, integration testing and user acceptance testing.

Environment : webMethods 6.01 Server, Trading Networks, SAP R/3 adapter, WebSphere MQ Adapter, SAP R/3 ABAP, BAPI, HP-Unix and Windows 2000

Siebel eSales Guided Selling System Senior webMethods Developer

The Siebel Guided Selling Tool will provide Dealers and Distributors the ability to create Shopping Cart Quotes. This is is accomplished through a Guided Selling experience using Siebels eAdvisor, Trilogy and the Siebel Catalog. Once this GS Quote is created in Siebel eSales, it may be punched out to an Order Processing application at a distributor site or sent as an email to the distributor. The dealer may obtain pricing and delivery information from the Distributors Site and place an order.

The punch out can either be 1 of 2 Transmit Modes : An email comprised of the Quote as readable text and a XML document of the Quote as an attachment.
An https Post of the Quote as a XML document to a distributors website or Order Processing Application
The purpose of this interface is to provide the means to accomplish points 1 and 2 above by gathering the required data from Siebel eSales, pushing it to webMethods which will either send out an email or post the XML document in a near real time business to-business data transaction over the Internet to the Distributors Website

This interface will use the Siebel to-webMethods adapter EAI webMethods Transports to push the required data as an XML string to the webMethods Integration Server. WebMethods will delivery the package and return a status to the Interface.

Source : Siebel eSales Guided Selling System
Middleware : webMethods

The Distributor
Frequency : On demand in Real Time
Volume : Initially 2000 per day based upon an initial count of 100 users. Growth projected =
30% from year 1 to year 2
Responsibilities :
Configured the Siebel Adapter to connect to Siebel 7.0.
Involved in designing the integration and developing the code for the integration.
webMethods will take the data passed from Siebel and reformat it into a cXML document.
Created the documents for mapping into plain text or cXML for sending email or posting to distributor.
webMethods will use the Transmit Mode parameter passed from Siebel to determine if the output is either email or https post of the XML document.
If the Transmit Mode is email, webMethods will compose the email with the Quote details as readable text and attach the XML document and sends it to the distributor.
If the Transmit Mode is https post, webMethods will send the cXML document to the Distributors website or Ordering System using https post.

webMethods waits for a Return Status and the URL of the Distributors Quote Processing System from the Distributor and passes the status back to Siebel.

Environment : webMethods 6.01 Server, webMethods Siebel Adapter, cXML, HP-Unix and Windows 2000.

Business Transformations

Avaya is 1 of the largest Networks and technology services providers for the fortune 500 companies. Business Transformations is writing the Standards and Governance for Avaya technology center and bring their technology into 1 platform ie, onto EAI wherever applicable. WebMethods being the EAI server, tool is going to take the advantage of bringing all the platforms to 1 point from where it can communicate to every technology center.

All the departments are going to use EAI webMethods to talk to any other department which is not a similar technology. WebMethods will provide services to every department to communicate to other department through connectors configured in webMethods. All the partners is connected through the Trading Networks a software component of webMethods to exchange the documents and which authenticates the partners before they log into Avaya domains.

Responsibilities : Writing the Standards and Governance documents.
Gathering Requirements and Specifications for the centralized environment.
Designing the Integrations between different software teams across Avaya.
Implementing the Integrations using webMethods and Trading Networks.
Testing the Integrations and maintaining the software releases.
Moving the successfully tested release to production environment.

Environment : webMethods 6.01 Server, webMethods 4.6 Integrations Server, webMethods 5.0 Enterprise Server, Trading Networks, webMethods SAP R/3 adapter, WebSphere MQ Adapter, SAP R/3 ABAP, BAPI and HP-Unix and Windows 2000.

2002 -  2002

Charter Communications is a Fortune 500 Company which is the largest Cable TV and Cable Internet provider company in the Central Part of United States of America.
VOD : This integration handles message routing and tracking utilizing the ftp services. The process runs on a regular time using the scheduler facility from webMethods.
Telephony : The integration is intended to update the telephone billing systems with the latest data using ftp services. Data which is coming from the switch is sending to the appropriate billing System Company through the webMethods FTP services.

CEON Implementation : The implementations are part of Coyote project. It had various integrations namely Self Install, Member Services. The self install interface gets input from the JSP front end and the info is communicated to Mentis and workflow is implemented. The interface communicates to CEON to Configure the Cable Modem. Member Services Interface caters to all the customer requirements like creating email accounts, creating web space, modifying profile etc.

Responsibilities : Involved in designing the specification for the interfaces by coordinating with different teams participating in the Integration.
WebMethods Integration Server is used to develop the workflow for the interfaces.

SQL Server is using for logging the status of each and every transaction.
Notifying the support team through webMethods SMTP service by sending email with the error details attached as a XML file.

2001 -  2002

Residential Funding Corporation is a mortgage banking company that buys assets from financial institutions, secures them and sells them back to private investors. 1 of the key initiatives for RFC in the year 2001 is to move the loan funding process from the mainframe to the client server world of Windows NT. 1 of the key components to this is the IMS to Oracle Data Replication project, known as the Near Real Time initiative. Today, associates make business decisions based off of Start of Day tables that are downloaded to Oracle early each morning. The NRT project aims to give operations associates access to data as soon as it has changed on the mainframe, allowing for greater flexibility and reliability in the decision making process. This is the first of many steps that will need to be taken to facilitate the funding process in the Windows NT environment and ultimately to migrate off the mainframe.
The NRT project uses Web Methods Enterprise Server, Mercator and IBM's MQ Series to facilitate the flow of information from the mainframe to the client server environment. 7 integrations were designed and implemented using Web Methods Enterprise Server and IBM's MQSeries. The integrations were designed to handle approximately 2 million messages per month, so performance and scalability were critical factors in the design. In addition to performance, the integrations were designed to provide guaranteed delivery and complete recovery from failure.

Responsibilities : Involved in designing the integrations for webMethods between IBM MQSeries and Oracle on NT.
All the 7 source MQ events are mapped to 7 separate Canonical Events for the 7 different Integrations through source ILA events which will track the integration failure at the source side.

On the other side of the integration, I have mapped the 7 Canonical events to the target database through target ILA events which is used to track the failed integrations.

Canonical events are independent for each integration and will pass through the same source and target ILA events.
Analyzed the requirements for the integrations and involved in interacting database, functional and testing teams for further enhancement of the project.
Upgrading total integrations from Webmethods Enterprise 4.1.1 to Webmethods Enterprise 4.5.
Configured 7 7 MQSeries Adapters to pull the messages of the Queue, When the IMS application pushes the data into Queues sitting on IBM MQSeries Server for Near Real Time.
The logic behind the process of Error Tracking was handled by using a Third Party tool called C2Track and C2Test from CROWE CHIZEK.
ILA with C2Track gives the facility of resubmitting the failed Integrations either on a mass publishing basis or single event basis.
It gives the facility to modify the event before u want to resubmit to the WebMethods.

Customized Adapter called Event Logger is used to keep track the status of each integration from IMS to Windows NT.
The RFC Error Adapter is configured for carrying error information from Webmethods Enterprise to Tivoli.
Environment : WebMethods Enterprise Server 4.5/4.1.1EAI, IBM MQSeries Adapter, Integration Logic Agent, Oracle Adapter, customized e-mail and Event Logger Adapters, IBM MQ Series, C2Track and Tivoli, Windows 2000 Professional Server

2000 -  2001

Eastman Chemicals is Chemical Products Manufacturing Company having multiple numbers of customers across the United States of America. They have SAP R/3 with ALE, IDOC for their Enterprise. WebMethods SAP BC is used to interact with the Eastman ERP for format conversions of inbound and outbound transactions. Their main objective is to integrate their business partners and customer to reduce the overhead of maintaining different types of formats and also to run some of their internal applications. The WebMethods B2B server listens for the Purchase Orders coming from their Customers in different formats. The Webmethods B2B receives the Orders and converts them to their local formats for maintaining the database and responding back to them with acknowledgements, invoices for further business.
On top of their business integration we integrated their Enterprise Applications for moving their data from 1 application to another application for the company's internal usage. The Customer base application receives the Purchase Orders from different customers and converts them to the local database of the customer base application. The warehouse management needs the same data for shipping the good to the customers. Webmethods Enterprise Server with Siebel 2000 Adapter and Oracle Intelligent Adapter used for moving the data between applications through the Application Transaction Coordinator.
Responsibilities : Involved in Analysis, design, development and testing of the project.
Coded services with WebMethods SAP BC for converting the incoming documents into SAP IDOC format.
Developed a B2B Bridge service which interacts with WebMethods Enterprise from the WebMethods B2B Server.
The Entire Integration initiated when the B2B Server receives a document and then the Enterprise Server receives a notification from the Webmethods B2B Server.
Integrated applications between Oracle and Siebel 2000 using Webmethods Enterprise.

The source and target events are published and subscribed to Canonical events for the total end to-end integration.
Source Events are mapped to Canonical events through source ATC for tracking the integration log details.

Canonical evens are mapped to Siebel through target ATC for total end to-end integration and the errors during integration is logged to ATC Log tables in the database.

Publish and Subscribe permissions are assigned to the source, Canonical and Target events to get error free integrations.

Dates are converted from 1 format to other using customized java services and java API used for customized java services.
Developed WebMethods Flow services for rerouting the failed Transactions which are monitored by Trading Networks Console.
Created structural event for updating different database tables in 1 shot.
Created flow and Java services on WebMethods B2B which is invoked by Webmethods Enterprise for the integration to be continued.
Created Configured operations for B-E Server Bridge Adapter which accepts 1 input and gives back 1 output.

Environment : WebMethods B2B Server, WebMethods Enterprise server, EAI, Active Works, IBM MQSeries, Siebel 2000 Edition, Oracle Adapter, Application Transaction Coordinator and Integration Logic Agent, Windows 2000/NT and Unix in Production

1998 -  2000
M.I.T.L,A Business Partner

1999 -  2000

Description : The product deals with Invoicing, Billing developed for Chrysler Inc, Detroit which manufactures different models of Cars. The project is divided into 3 phases.
Phase 1 deal with online Purchase Order Management through dealer Network channel.
Phase 2 deals with preparation of Sales Plan, Weekly Production Plan, Daily Production Plan based on unique Model No, Quantity. While preparing Sales Plan for the month Manufacturer can hold fully or partially any PO at their own discretion and Dispatch Orders is generated for the left out quantity against a PO. Plant can view the total Indent quantity, Purchase order quantity and will fill up the Production quantity based on their Manufacturing capacity. In turn Manufacturer will reshuffles the Sales Planned quantity based on the Production Quantity. Finally the revised Sales Plan is stored and proceeds to billing based on the Dispatch Orders.
Phase 3 deals with Billing and is for generating the Invoice based on the Delivery Order and it takes care about the payment.

Responsibilities : Developed JSPs to generate dynamic content based on user request.
used HTML to develop user interface.
JavaScript is used to validate the user input in the GUI.
Used Session Beans for querying data from Database.
Used Entity Beans to represent Purchase Order, Sales Plan and Dispatch Order information.
Master Child relationship was maintained using PL/SQL Stored Procedures while inserting new data into multiple database tables.
Used Visual Caf to deploy the EJBs on WebLogic Server.
Used Shell Scripting to start the WebLogic server.
Shell Scripts were used to track the information of the logged in users for giving permissions based on the user type.
Shell Scripts were used to load the flat file data to the database.

1999 -  1999

This IBS is a part of ICICI which mainly deals with Internet Banking. As soon as you enter into the site you need to choose the link to Internet Banking, so that you will move to the Internet Banking module.

Internet Banking System is for ICICI Bank which allows customers of ICICI Bank to log onto Online Internet Banking. The Site Provides facility to their customers for accessing their account to view his balance. It provides the facility to transfer funds between any other account holders of their bank. It provides the users to open an Account through Internet. You can personalize your account ; change the password, request for the Cheque Book and some other facilities it provides to their customers.
Responsibilities : Designed and developed the HTML front end screens and validated forms using Java Script.
Used Frames and Cascading Style Sheets to give a better view to the WebPages.
Utilized Servlets for handling various requests from the client browser and sending responses.
Introduced Session tracking mechanism to handle clients effectively.
WebLogic 4.5 used as both Application and Web Server.
High Security provided to the Customer's inf. through HTTPS, SSL.
Conversion of the output from the SQL query at server side was transferred in proper HTML formats.

1998 -  1999

The Customer Administration and Billing system project is intended to be fully integrated customer administration and billing package initially for the mobile telecommunications environment, It is being developed initially for use by Singapore Telecom mobile communication division which have become independent subsidiaries of Singapore Telecom called Mobile Link and Page Link.
The Singapore Telecom was dealing with Mobile, Pager and Long Distance Calls. This project validates all type of the Calls based on the specifications given by Singapore Telecom to recognize Calls. CABS is implemented as a Object Oriented System based on Client, Server Architecture using C++, Rogue Wave Tools like Tools. h++, DBTools. h++ and Sybase as backend on Solaris. A 100GB Sybase database was used as backend. To ensure maximum portability across backend Sybase, Rogue Wave DBTools. h++ is being used to implement Batch Applications. Used Booch Methodology for operational specifications. Batch processing module is developed using C++ and DBTools. h++.
Responsibilities : As a team member of Batch Processing Module involved in development and testing.
Developed C++ code for Validation and Billing Modules.
used DBTools. h++ to interact with Sybase Backend.
Used Debugging Tools DBX and Sun Workshop for Testing executables.
Used Rational PURIFY GUI tool on Sun Solaris to find out memory leaks.
used Tools. h++ utility Classes.
Experienced in GSM specific Mobile Call Validation.
Environment : Sun Solaris, Sun Workstation, Sybase, C++, Sybase, Rouge Wave Utility Libraries

Education