JAVA/3.4 Years - Sample Resume

  Name

E-mail: xxxxxxxxx@gmail.com

Ph: +91-9000000000

Professional Summary

• Overall 3 years and 4 months of Experience in Developing JAVA and J2EE   applications.
• Strong expertise in design and development of Web application using Struts MVC framework.
• Strong Experience in Developing Applications using JAVA and J2EE (JSP, Servlets, xhtml, Struts, jsf, JDBC and spring).
• Expertise in implementation of Applications in Java Server Faces.
• Knowledge in Web Services.
• Experience in designing front-end applications using XHTML.
• Good Knowledge about MVC2 architecture.
• Experience in using Eclipse and My Eclipse as development tools (IDEs).
• Good Implementation Knowledge in implementing Jasper Reports.
• Excellent commitment, dedication and planning towards goal oriented tasks and problem-solving skills with good interpersonal and communication skills

EMPLOYMENT OVERVIEW:

          As Software Engineer in Scorpos corporate services private Ltd, Hyderabad from Feb 2007 to Till Date.

ACADAMIC PROFILE:

• B.TECH  in Computer and Science Engineering(2006) from xxxxxxxx Institute of Science and Technology Engineering College with 62.5%
• Intermediate in Gowthami junior college  from Board of Intermediate Education with 89.4%
• C.B.S.E with 66.4%

Technical Summary:

Operating System                 : Windows 98, Windows XP

Database                             :  Oracle 9i

Languages                           : Java, C, C++.

Web Technologies                 : J2EE (Servlet, Jsp)   

Framework                          : JSF2.0, spring, Struts

Tools                                  : Edit plus, Eclipse, Seagate’s crystal Report, Plsql Developer.

Web Server                         : Apache Tomcat.

Projects Undertaken:

PROJECT 1:

Project             :           Dealer Management system.

Client                :           Greaves Cotton, Maharashtra.

Designation     :           Software engineer.

Environment    :           Java Server Faces, spring-jdbc, oracle-9i, xhtml, Tomcat 6.0

Duration           :           Oct ’09 –till date

Team Size        :           4.

Description:

Dealer Management System is a web based management solution that helps company to comply with automatic transactions. It is an essential tool for replacing manual maintenance. Dealer Management System has all the functionality you need to manage internal compliance needing automatic management.

Dealer Management System allows company to:

·         Maintain the track of their dealers;

·         Keeping a track of their transactions;

·         Have awareness of their required raw materials;

·         Update their information;

·         Track and manage compliance under specific regimes; and

·         Generate regular progress and audit reports.

Responsibilities:

·         Coding using Java Server Faces

·         Involved in coding of Managed Beans.

·         Developed presentation layer using xhtml.

·         Writing Business logic in model classes.

·         Validation checking using in-built attributes.

·         Coding for pagination using Prime Faces.

·         Developed Jasper Reports using Ireport Tool.

PROJECT 2:

Project             :           Export Management system.

Client                :           Indian Rayon, Mumbai.

Designation     :           Software engineer.

Environment    :           Java Server Faces, spring-jdbc, oracle-9i, xhtml, Tomcat 6.0

Duration           :           Dec ’08 to Oct 09.

Team Size        :           4.

Description:

This is web based and integration with SAP. An Export Management System is a program designed to monitor and manage the handling of export control issues within an organization. It should reflect the existing procedures followed by an Organization in its handling of controlled equipment and technology and build on those procedures to create a dynamic approach to this management. One important Purpose of this management system is

  to ensure that the organization will be accountable for export control matters in the event of      an audit by one of the agencies.

                       

Responsibilities:

·         Responsible for Java Server Faces

·         Involved in coding of Managed Beans.

·         Developed presentation layer using xhtml

·         Writing Business logic in model classes.

·         Validation using JavaScript.

·         Prepared test cases based on functional requirement Specification

·         Developed Crystal Reports using Eclipse.

  

PROJECT 3:

Project            :            CRM (CUSTOMER RELATIONAL MANAGEMENT)

Client               :            Greaves portable engines.

Designation    :           Software engineer.

Environment   :         Struts 1.1, Java, Oracle, JBoss, JDBC

Duration          :            Aug ' 07 –Nov-08.

Team Size       :            3.

Description:

                        This web project is designed for Greaves to handle its contact with its customers. CRM software is used to support these processes, storing information on current and prospective customers. Information in the system can be accessed and entered by customers in different Regions such as Northern Region, Southern Region, Western Region and Eastern Region. Details on any customer contacts can also be stored in the system. The rationale behind this approach is to improve services provided directly to customers and to use the information in the system for targeted marketing and sales purposes.

Salient Features:

 Easy user interface, High Security, Excel Export, Flexibility in terms of availability of past data, 24*7 availability, common platform for all stake holders to refer data and Message Board

Responsibilities:

·         Responsible for Struts Framework

·         Involved in coding of Action Classes.

·         Developed presentation layer using Jsp.

·         Writing Business logic in model classes.

·         Validation checking using struts.

·         Test cases for the modules.

·         Solve various issues while portalizing.

·         Solve pagination issue using display tag.

·         Learn the Struts tiles concept.

·         Test and deploy the project.

 PERSONAL PROFILE

      Name                          :           XXXX

     Date of Birth                      :           10-08-1985

     Father’s name                    :           XXXX

     Mother’s name                   :             XXXXXX

     Nationality                         :           Indian

      Sex                                     :           XXXX

      Martial Status                  :            XXXXX

      Languages Known              :             Telugu, English and Hindi

      Hobbies                              :           Watching Tennis, Listening to music.

DECLARATION

            I here by declare that all the information mentioned above is correct to the best of my knowledge and will be responsible for any flaws.

                                                                                                            Your’s sincerely,

                                                                                                            xxxxxx.

SAP Netweaver Gateway Basics

SAP Netweaver Gateway Basics:

SAP NetWeaver Gateway is a technology that provides a simple way to connect devices, environments and platforms to SAP software based on market standards. Completely flexible, SAP NetWeaver Gateway offers connectivity to SAP applications using any programming language or model without much need for SAP knowledge by leveraging REST services and OData/ATOM protocols.

Below are the generally used,

HTTP_METHODS:

GET        : Get Entityset or Entity

POST      : Create

PUT        : Update

DELETE   : Delete

Usual errors while testing the services:

400   Bad Request

1. When CSRF Token not added

2. Types of data sent are inconsistent

407   Method not allowed

1. URL/Request format and the selected HTTP Method are inconsistent.

500   Internal Server Error

1. If SQL Queries fail resulting in duplicate entries

These are the very common errors and will be updating the list going forward.

CSRF - Cross-Site Request Forgery: 

This is needed while sending create and update requests. Call the GET service to get the CSRF Token first and perform the create/update operation using the generated token.

*****************************************

Below are the methods implemented to get the service working for different purposes and explanation regarding the Method Parameters to be used while coding.

*_GET_ENTITYSET:

IV_ENTITY_NAME	Entity Name
IV_ENTITY_SET_NAME	Entity Set Name
IV_SOURCE_NAME	Entity Name
IT_FILTER_SELECT_OPTIONS	Values mentioned in FILTER Clause. But better to get it like given for IT_ORDER.
IS_PAGING	We do get TOP and SKIP values given in service URL and can be used to fetch data from database. This is for Paging of the data.
IT_KEY_TAB	This comes into picture when using Associations. Key value mentioned with Principal Entity.
IT_NAVIGATION_PATH	This comes into picture when using Associations
IT_ORDER	Fields mentioned for $orderby Clause. But better to get it from IO_TECH_REQUEST_CONTEXT->GET_ORDERBY() method as this will give correct field mapping.
IV_FILTER_STRING	Gives the FILTER String given on URL by $filter
IV_SEARCH_STRING	Strings used with Clause search will be in this parameter
IO_TECH_REQUEST_CONTEXT	Mentioned Format, Request ID, orderby, User Name, Service Path, Filter Values (FILTER_SELECT_OPTIONS), GET_TOP, GET_SKIP and Navigation Path etc. will be available in this instance. Look for the methods in this interface.
ET_ENTITYSET	Fill this internal table to show the entries in output
ES_RESPONSE_CONTEXT	This is to fill HTTP Response Header parameters. Custom HTTP Header parameters can be set using below procedure. This can be used, when some kind of extra  message to be passed to the UI when the response is a success. DATA:ls_header TYPE ihttpnvp. ls_header-name = 'my-custom-message'. ls_header-value = '{msg_typ:S, desc: Data Retrieved}'. /iwbep/if_mgw_conv_srv_runtime~set_header( ls_header ).

*_GET_ENTITY:

IV_ENTITY_NAME	Entity Name
IV_ENTITY_SET_NAME	Entity Set Name
IV_SOURCE_NAME	Entity Name
IT_KEY_TAB	Red colored value will be captured into this table. Let’s say key fields declared at Gateway Level. If the request url is the below, /sap/opu/odata/sap/ZMA_EMPS_SRV/Emp_DataSet('00000001')
IO_TECH_REQUEST_CONTEXT	Mentioned Format, Request ID, orderby, User Name, Service Path, Filter Values (FILTER_SELECT_OPTIONS), GET_TOP, GET_SKIP and Navigation Path etc. will be available in this instance. Look for the methods in this interface.
IT_NAVIGATION_PATH	This comes into picture when using Associations
ER_ENTITY	Output data will be populated into this
ES_RESPONSE_CONTEXT	This is to fill HTTP Response Header parameters. Custom HTTP Header parameters can be set using below procedure. DATA:ls_header TYPE ihttpnvp. ls_header-name = 'my-custom-message'. ls_header-value = '{msg_typ:S, desc: Data Retrieved}'. /iwbep/if_mgw_conv_srv_runtime~set_header( ls_header ).

*_CREATE_ENTITY:

IV_ENTITY_NAME	Entity Name
IV_ENTITY_SET_NAME	Entity Set Name
IV_SOURCE_NAME	Entity Name
IT_KEY_TAB	As Described Above
IO_TECH_REQUEST_CONTEXT	HTTP Method, Format of data, Operation etc. As Described Above
IT_NAVIGATION_PATH	As Described Above
IO_DATA_PROVIDER	Get the input data by the request can be retrieved using method READ_ENTRY_DATA. IO_DATA_PROVIDER-> READ_ENTRY_DATA( ).
ER_ENTITY	Fill this structure to show up the created entry in the Output Response.

*_UPDATE_ENTITY:

Same as *_CREATE_ENTITY

*_DELETE_ENTITY:

All Parameters                                  - As described above

/IWBEP/IF_MGW_APPL_SRV_RUNTIME~GET_EXPANDED_ENTITY

Build final table with exact deep structure ER_DEEP_ENTITY has. 

IO_EXPAND	IO_EXPAND-> MT_CHILDREN will contain below. Navigation property name should be appended to ET_EXPANDED_TECH_CLAUSES
ER_ENTITY	This will be a Deep Structure to hold header as well as Item data.
ET_EXPANDED_CLAUSES	Obsolete. Below is the replacement.
ET_EXPANDED_TECH_CLAUSES	Navigation property name should be appended to ET_EXPANDED_TECH_CLAUSES(This will be the name of child entityset). If this is not done, Method will be triggered number of times(as per number of records) though the data is filled in the first iteration.

/IWBEP/IF_MGW_APPL_SRV_RUNTIME~GET_EXPANDED_ENTITYSET:

All the parameters have been covered above.

/IWBEP/IF_MGW_APPL_SRV_RUNTIME~CREATE_DEEP_ENTITY:

All the parameters have been covered above.

Build final table with exact deep structure ER_DEEP_ENTITY has. 

Make sure the deep internal table named after child entityset. If not item data will not be populated.

CREATE _ENTITY and CREATE_DEEP_ENTITY will be called based on the input request given. If the request contains deep body then CREATE_DEEP_ENTITY will be called.