ATraining Report

On

With special reference to the study institute of

-Submitted to-

As a Mini Training report for

Master of Computer Application MCA (2nd year)

Year : 2006-2007

-Submitted-Students of

(Computer Department)

Name: Guided By:

I NTRODUCTION O F I T C OAL I NDUSTRY

The IT coal industry in general and in SECL came out been in a formal way in 1980’s. The machine introduce was mini computers with UBIX operating system as an Cobol as a interface application software. The business process that was introduces a salary wages financial accounting, store and inventory cost sheet and sales bill.

The operating mode was batch processing where from periodic reports, analysis, and statements was generated and tackled to different level of management from the encrypted transaction data.

Basically this system was useful at that movement of time with in a limited machine and human skill property. The system can give management saport information but after a curt of time etc. It was not a static information to meet an a instance query or requirement for there more every business process is a standalone concept and not related on integrated to each other, as a type process on that event of communication, relation RDBMS and web based technology.

SECL in particular coal India engineers was planning to introduce latest datapart software, where customize web best TRP, in this customize TRP every transaction capture and activity level and will have be a relation to other business and activity for this oracle RDBMS is choosen for repositioned database and web server, application server will be connecting to the client end java and JSP technology is been used.

P ROFILE O F T HE C OMPANY

South Eastern Coalfields Limited is the largest coal producing company in the country. It is one of the eight subsidiaries of Coal India Limited (A Govt. of India Undertaking) under the Ministry of Coal . The company was adjudged the best PSU in the country for 97-98 and was awarded Jawaharlal Nehru Memorial National Award for pollution control and energy conservation in the year 2003 and Excellence award in 2004 and 2006. SECL has been awarded " Mini Ratna" Status by Govt of India in 2007 . In year 2008-09 ,total  coal  production  by SECL

was 101.3 million tones. In the year 2006-07 out of total coal production of 360.94 million tonnes produced by Coal India Ltd.,   total  coal  production  by SECL was 88.502 million tonnes from open cast and underground mines which was highest among all subsidiaries company of Coal India Ltd. SECL has been making profits since its inception.

SECL is an invaluable part of our country and it is proved by its motto which has been depicted in the following picture

Basically Computers were introduced in SECL in early1980’s and its main purpose over the years was to ease out the tedious task of “Payroll”. With the advent of PC’s and development in technology it was decided to use the computing power of computers in many other fields of importance in SECL; the result was COALNET which is probably one of the best ERP package being developed and implemented.

A BOUT C OAL N ET

COALNET is an ERP Package developed for Coal Industry of India and customized for Coal India Limited. This application covers all the functionality to run the business process smoothly and efficiently. This application is scaled and designed to fulfill the intense requirement of Enterprise Computing of an Organization like Coal India having eight large Subsidiary situated at different dispersed location of India . Functionalities covered in this application are Finance, Production, Personnel, Project, Materials, Payroll, Sales & Marketing, Equipment and customized modules like VVIP, Grievance and Parliament Affairs. This Application also provides a B2B portal and Geographical Information System (GIS).

COALNET has been designed to provide a web based - platform independent, integrated application software system to revolutionize information management in Coal India adding substantially to organizational management and competitiveness of COAL INDIA.

What is Coal Net?

Web Based Integrated Application Software Platform Independent Application Highly Secured Application Using Latest Technology (Java & Oracle DB and Oracle Application

S/W) Integration of information and distributing it online to users to Put in place an Information Infrastructure Build up efficiency through constant/event-oriented

monitoring

Objectives:-

Uniformity Rationalization Integration of information and distributing it online to users to Put in place an Information Infrastructure Build up efficiency through constant/event-oriented

monitoring

Features:-

Uniform data and file structures with uniform meaning to each data field. Bridge programs may be required to integrate with the legacy and stand alone system .

Full internal consistency and Internet compatibility to help the business process with such external agencies as customers, suppliers, regulatory authorities and the controlling authority (MoC) for the holding company.

Compatible information system to the operation and control needs at level of individual colliery /projects, area, subsidiary and at the holding company.

Timely availability of accurate information with accountability and data tracking.

Transparency and information support to stake holders (e.g. employees and government) with a view to minimize delays in redresal of grievances.

Visualization:-

Phase I (CIL HQ to All Subsidiary HQ) Phase II (Subsidiary HQ to Areas) Phase III (Areas to Units)

Phase-III

Currently the Coal Net project is being developed and implemented in SECL Headquarters Bilaspur (C.G.) and is in phase-I .

MOC

CIL HQ

SUB HQ1 SUB HQ2 SUB HQ3

AREA1 AREA2 AREA3

COLL 1 COLL 2 WASH 1

PHASE I

PHASE II

I NTRODUCTION TO EQUIPMENT MONITORING SYSTEM

The module of Coal Net Application I have worked on is named as Equipment Monitoring System (EMS).

Coal India Limited is a government undertaking that is responsible for meeting out the Coal requirements of not only India but also some of the other countries of Asia also.

Coal is dug out from mines, processed and transported to different areas to meet the requirements. For mining, processing, transporting and other operations many equipments such as Crane, Dozer etc are used.

To ensure that Coal requirements are fulfilled efficiently and in an easiest way it is essential that the equipments by which they are dug out, processed to make usable and transported etc; are in good condition, work to the best and are available when needed.

Equipment Monitoring System is being developed to monitor each and every equipment that is being used in CIL to increase their productivity by their effective and efficient management.

The proposed Equipment Monitoring System will deal with

1) Requirement Processing

2) Equipment Performance Monitoring

3) Rehabilitation Monitoring

4) Deployment details of individual equipment.

This system will be integrated with Material Management and Production systems.

These activities were all being performed manually and with standalone computers prior to the implementation of this system. This entailed lots of unnecessary wastage of resources. A need for the automation of all these and linking through web was felt

Equipment Monitoring System is based on the Three-Tier Client Server Architecture.

Three - Tier Application Access

Front Tier :- Client Application Middle tier :- Application Server Back end :- Data Base Logic and Processing

Front-Tier Middle-Tier End-Tier

The front tier is concerned with the appropriate formatting of data to be displayed to the user (client browser).

The middle tier contains java classes that implement the business logic and communicate with the enterprise database at the back end using JDBC API call.

Logical Structure of the Application:-

Server Side Client Side

Logical Structure of the Application:-

User View Business Logic Enterprise

JSP Pages (Java components) Database

Physically the components (i) and (ii) in the above figure are deployed on an application server, which communicates with the front end HTTP server.

The HTTP server forwards any client (browser) request to the JSP container, which then asks for the service of an appropriate JSP and sends back any response from the JSP to the HTTP server.

The HTTP server then sends back the response to the client browser where it is being presented to the user.

(i) Front Tier (ii) Middle Tier (iii) Back End

The JSP asks for the service of the appropriate business component through the proper interface, which then communicates with the back end enterprise database using JDBC API Call.

Application Components:-

The Components that the application is comprised of are shown in the above figure. For each functionality, a single JSP page has been identified which communicates with a particular Web Bean class. The Web Bean class instantiates a particular handler that publishes an interface used by the Web Bean class to invoke the appropriate methods on the back end database class. The database class ultimately communicates with the back end database tables associated with the functionality to add, modify, delete and search data.

JSP Page WEB Bean Handler JDBC Classes

Database

Entity Class (Represents Data)

User End Middle - Control Database End

The Java component Structure of the Application

Short Description of the Java Components:

1. Entity Classes

The entity class encapsulates data in a particular table associated with the functionality. It defines a set of setter (setXXX) and getter (getXXX) methods to access the attributes (say XXX) of the class.

2. JDBC Classes

These are the back-end database classes, which communicate with the enterprise database using JDBC API call. They implement the business logic to process the data passed to them. These classes have add, modify, delete and search methods (for both the header and the detail tables) implemented in them to allow the user insert new data in the database, modify or delete data or search the database tables to find out data required by the user. To map the search

Parameters specified in the search JSP with the database table columns these classes define two methods: getColumnName and getColumnType, which are utilized by the search methods to form the SQL query.

3. Handlers

Handlers abstract the instantiation of the back end database classes. These components actually are composed of two Java classes: Handler Interface Class and Handler Implementation Class. The Web Bean instantiates an appropriate Handler Id string as specified in the CoalNetParameter.ini. Handlers provide the interface to access the business logic defined in the database class. The implementation class defines the methods of the interface that include the logic to access the methods of the back-end database class.

 

4. Web Beans

JSP communicates with the Web Bean by invoking the save methods on it. Within the save method the Web Bean retrieves the form data from the request object and depending upon the user action calls the

appropriate private method (add, modify or delete) from where the appropriate method on the Handler Interface is accessed. When the same table is updated from different screens the build Object method is used to populate the member variables of the entity class corresponding to the table whose values are not available from the Form data. Search methods (getSearchData/getAllDetails) are invoked on the Web Bean to retrieve the data from the database tables.

Only the user who has all the powers and permission is allowed to access the system.

T ECHNICAL S APORTS

1. JSP (JAVA SERVER PAGES) :-

While there are numerous technologies for building web applications that serve dynamic content, the one that has really caught the attention of the development community is JavaServer Pages (JSP). And not without ample reason either. JSP not only enjoys cross-platform and cross-Web-server support, but effectively melds the power of server-side Java technology with the WYSIWYG features of static HTML pages.

JSP pages typically comprise of:

Static HTML/XML components. Special JSP tags Optionally, snippets of code written in the Java programming

language called "scriptlets."

Consequently, you can create and maintain JSP pages by conventional HTML/XML tools.

It is important to note that the JSP specification is a standard extension defined on top of the Servlet API. Thus, it leverages all of your experience with servlets.

There are significant differences between JSP and servlet technology. Unlike servlets, which is a programmatic technology requiring significant developer expertise, JSP appeals to a much wider audience. It can be used not only by developers, but also by page designers, who can now play a more direct role in the development life cycle.

Another advantage of JSP is the inherent separation of presentation from content facilitated by the technology, due its reliance upon reusable component technologies like the JavaBeans component architecture and Enterprise JavaBeans technology. This course provides you with an in-depth introduction to this versatile technology, and uses the Tomcat JSP 1.1 Reference Implementation from the Apache group for running the example programs.

JSP Advantages

Separation of static from dynamic content: With servlets, the logic for generation of the dynamic content is an intrinsic part of the servlet itself, and is closely tied to the static presentation templates responsible for the user interface. Thus, even minor changes made to the UI typically result in the recompilation of the servlet. This tight coupling of presentation and content results in brittle, inflexible applications. However, with JSP, the logic to generate the dynamic content is kept separate from the static presentation templates by encapsulating it within external JavaBeans components. These are then created and used by the JSP page using special tags and scriptlets. When a page designer makes any changes to the presentation template, the JSP page is automatically recompiled and reloaded into the web server by the JSP engine.

Write Once Run Anywhere: JSP technology brings the "Write Once, Run Anywhere" paradigm to interactive Web pages. JSP pages can be moved easily across platforms, and across web servers, without any changes.

Dynamic content can be served in a variety of formats: There is nothing that mandates the static template data within a JSP page to be of a certain format. Consequently, JSP can service a diverse clientele ranging from conventional browsers using HTML/DHTML, to handheld wireless devices like mobile phones and PDAs using WML, to other B2B applications using XML.

Recommended Web access layer for n-tier architecture: Sun's J2EE Blueprints, which offers guidelines for developing large-scale applications using the enterprise Java APIs, categorically recommends JSP over servlets for serving dynamic content.

Completely leverages the Servlet API: If you are a servlet developer, there is very little that you have to "unlearn" to move over to JSP. In fact, servlet developers are at a distinct advantage because JSP is nothing but a high-level abstraction of servlets. You can do almost anything that can be done with servlets using JSP--but more easily!

Comparing JSP with ASP

Although the features offered by JSP may seem similar to that offered by Microsoft's Active Server Pages (ASP), they are fundamentally different technologies, as shown by the following table:

JavaServer Pages

Active Server Pages

Web Server Support

Most popular web servers including Apache, Netscape, and Microsoft IIS can be easily enabled with JSP.

Native support only within Microsoft IIS or Personal Web Server. Support for select servers using third-party products.

Platform Support

Platform independent. Runs on all Java-enabled platforms.

Is fully supported under Windows. Deployment on other platforms is cumbersome due to reliance on the Win32-based component model.

Component Model

Relies on reusable, cross-platform components like JavaBeans, Enterprise JavaBeans, and custom tag libraries.

Uses the Win32-based COM component model.

Scripting

Can use the Java programming language or JavaScript.

Supports VBScript and JScript for scripting.

Security

Works with the Java security model.

Can work with the Windows NT security architecture.

Database Access

Uses JDBC for data access.

Uses Active Data Objects for data access.

Customizable Tags

JSP is extensible with custom tag libraries.

Cannot use custom tag libraries and is not extensible.

JSP or Servlets?

It is true that both servlets and JSP pages have many features in common, and can be used for serving up dynamic web content. Naturally, this may cause some confusion as to when to opt for one of the technologies over the other. Luckily, Sun's J2EE Blueprints offers some guidelines towards this.

According to the Blueprints, use servlets strictly as a web server extension technology. This could include the implementation of specialized controller components offering services like authentication, database validation, and so forth. It is interesting to note that what is commonly known as the "JSP engine" itself is a specialized servlet running under the control of the servlet engine. Since JSP only deals with textual data, you will have to continue to use servlets when communicating with Java applets and applications.

Use JSP to develop typical web applications that rely upon dynamic content. JSP should also be used in place of proprietary web server extensions like server-side includes as it offers excellent features for handling repetitive content

JSP Architecture

The purpose of JSP is to provide a declarative, presentation-centric method of developing servlets. As noted before, the JSP specification itself is defined as a standard extension on top the Servlet API. Consequently, it should not be too surprisingly that under the covers, servlets and JSP pages have a lot in common.

The JSP page implementation class file extends HttpJspBase, which in turn implements the Servlet interface. Observe how the service method of this class, _jspService(), essentially inlines the contents of the JSP page. Although _jspService() cannot be overridden, the developer can describe initialization and destroy events by providing implementations for the jspInit() and jspDestroy() methods within their JSP pages.

Once this class file is loaded within the servlet container, the _jspService() method is responsible for replying to a client's request. By default, the _jspService() method is dispatched on a separate thread by the servlet container in processing concurrent client requests, as shown below:

JSP Access Models

The early JSP specifications advocated two philosophical approaches, popularly known as Model 1 and Model 2 architectures, for applying JSP technology. These approaches differ essentially in the location at which the bulk of the request processing was performed, and offer a useful paradigm for building applications using JSP technology.

Consider the Model 1 architecture, shown below:

In the Model 1 architecture, the incoming request from a web browser is sent directly to the JSP page, which is responsible for processing it and replying back to the client. There is still separation of presentation from content, because all data access is performed using beans.

Although the Model 1 architecture is suitable for simple applications, it may not be desirable for complex implementations. Indiscriminate usage of this architecture usually leads to a significant amount of scriptlets or Java code embedded within the JSP page, especially if there is a significant amount of request processing to be performed. While this may not seem to be much of a problem for Java developers, it is certainly an issue if your JSP pages are created and maintained by designers--which is usually the norm on large projects. Another downside of this architecture is that each of the JSP pages must be individually responsible for managing application state and verifying authentication and security.

The Model 2 architecture, shown above, is a server-side implementation of the popular Model/View/Controller design pattern. Here, the processing is divided between presentation and front components. Presentation components are JSP pages that generate the HTML/XML response that

determines the user interface when rendered by the browser. Front components (also known as controllers) do not handle any presentation issues, but rather, process all the HTTP requests. Here, they are responsible for creating any beans or objects used by the presentation components, as well as deciding, depending on the user's actions, which presentation component to forward the request to. Front components can be implemented as either a servlet or JSP page.

The advantage of this architecture is that there is no processing logic within the presentation component itself; it is simply responsible for retrieving any objects or beans that may have been previously created by the controller, and extracting the dynamic content within for insertion within its static templates. Consequently, this clean separation of presentation from content leads to a clear delineation of the roles and responsibilities of the developers and page designers on the programming team. Another benefit of this approach is that the front components present a single point of entry into the application, thus making the management of application state, security, and presentation uniform and easier to maintain.

2. JAVASCRIPT :-

Java script is a purpose, prototype based, object oriented scripting language developed jointly by sun and Netscape and is meant for the WWW. Java Script borrows most of its Syntax from Java but also inherits from awk and perl.

Java Script is almost as easy to learn as HTML, and it can be embedded directly in HTML Documents. Java Script is a high level scripting language that does not depend or expose particular machine representation or operating system services.

FEATURES

Java Script is embedded into html documents and is executed within them.

Java script is Browser dependent. It is an interpreted language that can be interpreted by the browser

at run time. It is an object based language. It is loosely typed language. It is event driven language and support event handlers to specify the

functionality of a button.

3. INTERNET EXPLORER 6.0 :-

An Internet browser is required to access the “Equipment Monitoring System” S/W. Microsoft Internet Explorer 6.0 is a free internet browser that works across many different computer platforms. Regardless of the website you are visiting internet explorer 6.0 can display the most complex web pages.

S YSTEM S EQURITY

1. CHECKS AND CONSTRAINTS

System security refers to various validations on data in form of checks and constraints to avoid the system fro failing. It is always important to ensure that

only valid data is entered and only valid operations are performed on the system. The system employs two types of checks and controls.

1.1. CLIENT SIDE SECURITY

Various client side validations are used on the client to ensure that only valid data are entered. Some checks imposed are

A JavaScript program is used to fill up date in the date fields only. JavaScript is used to ensure that numeric field is filled with numeric data

only. Maximum length of the fields of the forms is appropriately defined. Forms cannot be submitted without filling up the mandatory data so that

manual mistakes of submitting empty fields that are mandatory can be sorted out at the client side to save the server time and load.

Tab indexes are set according to the need and taking into account the ease of user while working with the system.

1.2 SEVER SIDE SECURITY

Server side checks are necessary to save the system from failing and intimating the user that some invalid operation has been performed or the performed operation is restricted. Some of the server side checks imposed is:

Server side constraint has been imposed to check for the validity of Primary Key and foreign key. A primary key value cannot be duplicated. Any attempt to duplicate the primary key value results into a message intimating the user about that. Values through the forms using foreign key can be updated only for existing foreign key values.

Exception is caught in the programs and is used constructively to avoid system failure. User is intimated through appropriate messages about the successful operations or exceptions occurring at server side.

F UTURE S COPE O F T HE P ROJECT

The Equipment Monitoring System is one of the modules of ERP package named “CoalNet”. It is a web based project that is implanted in headquarters but it is to be linked across all subsidiaries and collieries.

The module is not fully implemented in the environment. Some of the features are to be tested in live environment and updated.

New modules and functionality can be added as new need arises.

C ONCLUSIONS

This was the first considerably training undertaken by me during my MCA course. It was an experience that changed the way I perceived project development. The coding could not be started before the whole system

was completely finalized. Even then there were so many changes required and coding needed to be changed.

On the whole it was a wonderful experience to work in this system and I would have considered my education incomplete without undertaking such a training which allowed me to apply all that I have learnt.