PROFESSIONAL SUMMARY:

• Over 10years of overall technical and business experience utilizing Java, JEE5, EJB 3.0,Weblogic10,Websphere7.0, Jboss, C++,JSP,Servlet, CORBA, XML, XSL andalso inimplementing Business Rules System.Around8+yearsexperiencespecificallyin usingdesigning Rules based solution using Confidential JRules.
• Involvedin Business Rule Analysis.
• Involved in setting Business Rule Models and Business Flows and Process Flows.
• Involved in implementing the best practices involving BRMS.
• Involved in extracting rules from Business Policies and Business Requirements.
• Involved in Rules Design,Rules Organizations and flows.
• Involved in deployments and testing rules.
• Experience in Confidential JRULES7.x,6.x, 5.x and Confidential 4.6.
• Experience in writing rules in IRL, TRL and also using BAL.
• Knowledge of automotive, insurance, Pharmaceuticals, retail, government and telecommunication business systems.
• Has ability to solve complex problemsand using logic and reasoning to identify the strength and weakness of various solutions and approaches to the problem.
• Strong communication, interpersonal, organizational, analytical and logical, decision making and listeningskills.
• Experience in Mentoring other developers
• Experience having interacted with Users and gathered specs.
• Experience in working with Code review group.
• Experience using templates with velocity for dynamic rules creation.
• Experience using Hibernate, AspectJ (AOP), and AJDT with Eclipse.
• Experience working on Confidential BUSINESS RULE STUDIO with Eclipse.
• Knowledge of working on JESS RULES ENGINE.
• Knowledge of BPEL/BPM using Oracle BPM.
• Have worked inWeblogicIntegration with JRules ( Confidential ) usingWeblogiccontrols.

PROFESSIONAL EXPERIENCE:

Confidential, IL

Responsibilities:

• Developed enterprise wide business object model and rules specific object models and schema.
• Designed and developed Decision Managements System using Confidential BRMS systems for multiple projects and services .Guided the team to achieve the roadmap for implementing Business Rules Strategy.
• Integrated Business Rules system to validate data quality and sets up threshold for MDM.
• Implemented varioustesting scenariosfor various requirements through Data Validation Services (DVS).
• Co - ordinate rules deployment with Business Users.
• Created Rule Mining Template for sharing the Rules with users and establish traceability from requirement to implementations.
• Organize rules in multiple projects and shares common BOM and rules set organized to meet functional requirements.
• Worked with Enterprise Architecture team on NOD (Notice of Decision) document for setting Integration standards within HealthNow.
• Used JMX events capture techniques to parse the rules set upon deployment.
• Externalized Decision Warehouse to external DB.
• Auditing the logs was enabled through Decision Warehouse.
• Tracing mechanism implemented through extending the default notification system for debug purpose.
• Have some experience with Informatica 9.1 PowerDesigner.
• Worked effective to understand needs and requirements to design a better systems and able to determine how rules system responds to changes for conditions and affect the outcomes.
• From the BusinessRequirements writeFunctional and Technical Design documents for appropriate application design and rules design.
• Helped testing team in setting up test data to system testing and Business Rules testing through DVS and other methods.
• Helped testing team and business unit to use the DVS, so that they can change rules through RTS and able promote the change with confidence.
• Integrate Informatica with MDM through RMI Invocation.
• Implemented various Integration solutions for Confidential with services usingMDB,Web servicesalso Native Invocation from Informaticaso Confidential can run in Same JVM within Informatica.

Environment: IBM ILOG7.2, IBMProcess Server7.0,Message Broker 6.0, Websphere 7.0, WID7.0,SQLDeveloper,Unix/Linux,JEE, EJB3.0,Informatica 9.1.

Confidential

Lead Developer

Responsibilities:

• LeadtheCenter of Excellencefor Business Rules Solutions Development andcome up with leading design and solutions to utilize Confidential across Enterprisewide effectively.
• Designed a Rule Governance Solutions so business users can make theirchanges usingthe Rule TeamServer (RTS) andchanges are deployed to Rule ExecutionServer.
• Automated the deployment process on timely manner there by reduce the time taken to deployment and avoid the human interventions for every rule changes.
• Worked as lead for designingand implementing BusinessRulesSolutions forSOA Services.
• Designing rulessystem,BOM,XOM,setting upvocabulary, implementingbestpractices.
• Organize rules and BOM in reusable and extensibleRule artifacts
• For every rule project come up with Rule Mining Template which helps both business and IT to trace implementation back to requirements and ease the maintenance and historydetailsall at one place.
• Involved inRuleHarvesting andidentify the rules from existing code (buried) and help extracting and alignrules with the decisionspoints,delivering thebusiness topology and documentationforBusinessRules,Flows andDecisions.
• Helps the business and IT to ensure all the decisions are met with requirements and solutions is optimized for performance.
• Worked in RulesDesign,creating Rule MiningTemplate,Interacting withBusiness, Ruleharvesting.
• Writing rules inBAL,IRL,TRL and Decisiontables.
• Automated rule parsing / refresh ondeployment especially for larger rulesets and online applications.
• Setup tracer, performance measurement at rule /task level.
• Improved runtime performance usinghashers,finders.
• Used MDB’s for data cache refresh to synch with ETL data migration.
• Implemented EJB interceptors for tracing / performance monitoring.
• Used Watir scripts to automate the setup of Roles and Responsibilities in RTS.
• Implemented persistence service with Hibernate.
• Used EJB 2/3 for exposing Rule Services to EJB Layers.
• Used testing framework build around JUnit using RSM for Java and XML Input.
• Migration work from JCS to Oracle Coherence3.5 and enforce the caching policy and constraints using business rules.

Environment: J2EE,EJB 2.x /EJB 3.0, Axis 2,JIBX binding, Hibernate 3.x, EJB 2.1, XML, AspectJ 1.5 with AJDT in Eclipse 3.3, Ant, JSF Framework, Weblogic 10.0, SQL Developer, Confidential JRULES 6.7.4/ Confidential 7.01, Unix .Sr.JavaJ2EE/Spring Hibernate and Developer

Senior J2EE, Java, ILogJrules Developer

Confidential

Responsibilities:

• Implementingservice tier using Spring.
• UseSpring / Hibernate for the persistence layer for the Auto Enrollment.
• UseAOP/AspectJfor performance,logging,security,transactions.
• UseAspectJ for filling up the Gap between XSD Objects and DB using Inter-Type Declarations.
• ImplementRules System using Confidential in J2EEenvironment.
• Involved with designing Activity Diagram and Use Cases.
• Extensively usehibernate framework forpersistence.
• Workon JUnit for creating test cases for all the Business Rules.
• UseRules Scenario Manager for creating scenarios and test cases for Unit Test/ QA testing.
• Setup SSP (Scenario Service Provider) for all applications.
• UseRTS for code promotion creating baselines.
• Involved in creating basicframework andgiving overall architectural solutions for Confidential, writing all the business rules using Confidential Jrules.
• Migratefrom different versions to latest version of Confidential . Also migrated business logic from PL/SQL, Oracle Stored procedures/ Application to Confidential . Responsible for Integrating with the Confidential Team Server, BRES, Scenario Manager. Supportmultiple projects in respect to Confidential .
• UseANT/Maven for building scripts.

Environment: J2EE,Spring2.x, Hibernate3.x, Servlet2.3, EJB2.1, XML,AspectJ1.5 with AJDT in Eclipse 3.3, Ant, JSF Framework, IBM Websphere6.1, IBM RAD7.0, DB2, Confidential JRULES6.7.2, Hibernate 3.3, Unix.

Sr. Developer

Confidential

Responsibilities:

• Java 1.5.11 and Confidential JRules 6.5 / 6.6.
• Involved in designing rules based system.
• Involved in creating rule model (XOM) for the system.
• Involved in authoring and reviewing business rules.
• Orchestrate the rules execution using the rule flow.
• Worked in creating hibernate mappings for data model.
• Involved in writing aspects for performance monitoring,logging, tracing using AspectJ and Spring AOP.
• Involved in creating event tracing for JRules 6.5.
• Involved in writing rules from the Functional Spec.
• Involved in creating Testing Framework using Java and Excel and Mock Objects.
• Involved in rules optimization.

Application Developer

Confidential

Responsibilities:

• Implemented web service using SDO.
• Worked on Creating XML-Castor Objects.
• Worked on hibernate mapping for entire applications.
• Used hibernate to map against Legacy database with composite keys.
• Worked in Confidential JRules 6.1 integration with FileNet P8 BPM.
• Used File based repository and also setup RuleTeamSever for shared access.
• Implemented logging/tracing mechanism using aspectJ.
• Created testing framework for running test with different set of XML request.
• DAO's exposed to the UIlayer through Spring Framework.
• Logging for Persistence layer implemented using Spring AOP.
• Used Dependent Injection for injecting SessionFactory into the DAO.
• Also used Spring AOP for managing transaction for the dao.
• Used Castor for Java XML binding.
• Used FacesPortlet for developing portlets using JSR 168 and deployed in IBM Portal 6.0 Server.
• Used AspectJ Inter-type declarations for setting up data externally on Generated BOMfrom XML Schema.
• Used AspectJ to cross cut all domain data values to handle data Conversion to defaultvalues.
• Facilitate auto code generation from XML Schema to BOM using castor and to also mapagainst Hibernate.

Developer

Confidential

Responsibilities:

• Involved in rule analysis and authoringof business rules.
• Involved in extracting rules from Business Policies and Business Requirements.
• Involved in Rules Design, Inference Networking models and Rules Organizations and rule flows.
• Involved in deployments and testing rules.
• Involved in performance analysis of rules system.
• Implemented both Sequential and Rete algorithm mode rules.
• Identify rules qualified for Sequential flow to improve performance.
• Applied filter at agenda level to regulate the rule flow.
• Modified the applications to enable using Web Rule Builder. So that the business team can update the changes they need.
• Applied filter on the Web rule builder so that only rules based on Decision table can be shown up in Web Rule Builder.
• Used DB2 based repository and so have shared access across the development team.
• Implemented data population to Decision table using DB.
• Implemented logging using Confidential event notifications.
• Implemented Rules Development Best Practices.
• Implemented Unit Testing methodology using Confidential Rules Studio. Also utilized Hibernate and HSQLDB for storing test/Decision table data’s.
• Implemented Tracing framework for Rules Layer using AspectJ M5(testing).
• Java, J2EE, Jrules and Confidential Developer
• Participated as J2EE Java and Confidential rules designer and developer.
• Created BOM, XOM for Confidential JRules.
• Deployed ruleapp in BRE Server.
• Integrated Project various modules into 1 repository usingextended repository.
• Involved in OR Mapping for the analysis model using Hibernate.
• Helped other developers to integrate rules with the use case.
• Involved in multiple use cases and developed Insurance Verification.
• Integrated with Liquid BPM 3.54 workflow engine.
• J2EE Java and Confidential Rules Developer
• Created BOM for Confidential JRules.
• Created OR Mapping for the analysis model using Hibernate.
• Used Struts for UI design.
• Developed various applications in dealer connect portal for this major automotive manufacturer. The applications developed under the dealer connect portal are used by dealers across the country.
• Participated as J2EE Java designer and developer.
• Used Rational Rose and UML to design and develop framework.
• Used Mercury testing tools for testing the application, which included writing Load Runner scripts.
• Produced application documentation.
• Supported production once the system went to production.
• Participated in users meetings, macro reviews, micro reviews, functional review meetings