squirel sql

To get a connection to the database

Name: Give any name

Driver:Mysql Driver

URL:jdbc:mysql://local host:port no/database name

User:root

Password:give the required pasword.


Before adding alias,add Mysql driver
Right click mysql driver->extra class path add mysql.jar
(mysql.jar added externally)
then give ok.

cvs

To do the checkout process in windows:
Before start checking out in windows system,the directory must be configured in the cvs by the cvs admin.

The file must be marked as binary in the cvs

To mark a file as binary:

cvs admin -kb name_of_binary_file

mysql

1)To know the instances that are running
mysqld_multi report

2)To start the instance
mysqld_multi start

3)To use the database in the instance
mysql -u demouser -p -h 192.168.1.88 -P 4007 qamart;

To run the process in tomcat server

1)Run the build.xml in the program
when u run a war file will be created in a folder.
ex:yumeetl.war will be created in the folder temp

2)Copy the war file and paste in the webapps folder

3)edit the log4configuration.xml whether the path is correctly denoted.
file:/home/sathish/tomcat/webapps/yumeetl/WEB-INF/classes/log4configuration.xml

4)copy and paste yumeetl.xml to /home/sathish/tomcat/conf/Catalina/localhost

5)edit server.xml whether url value is correct

6)Start the tomcat server

To start the process

execute queries in qadb.
truncate table and insert in QRTZ_TRIGGERS, QRTZ_CRONTRIGGERS, QRTZ_JOBDETAILS
update QRTZ_TRIGGERS,

To view log tail -100f yumeappserver.log
To remove rm*.

TOMCAT

TO START TOMCAT

1)Go to tomcat/bin.

2)Set environment variables

a) export JAVA_HOME=/usr/java/jdk1.6.0_03/
b)export CATALINA_HOME=/usr/local/tomcat

3)Enter the command to start
./startup.sh

JavaServer Faces

JavaServer Faces (JSF) is a Java-based Web application framework intended to simplify development of user interfaces for Java EE applications. Unlike other traditional request-driven MVC web frameworks, JSF uses a component-based approach. The state of UI components is saved when the client requests a new page and then is restored when the request is returned. Out of the box, JSF uses JavaServer Pages (JSP) for its display technology, but JSF can also accommodate other display technologies (such as XUL). JSF includes:

• A set of APIs for representing user interface (UI) components and managing their state, handling events and input validation, converting values, defining page navigation, and supporting internationalization and accessibility
• A default set of UI components
• Two JavaServer Pages (JSP) custom tag libraries for expressing a JavaServer Faces interface within a JSP page.
• A server-side event model
• State management
• Managed Beans (JavaBeans created with dependency injection)

EJB

Enterprise JavaBeans™ (EJB) is a managed, server-side component architecture for modular construction of enterprise applications.

The EJB specification is one of several Java APIs in the Java Platform, Enterprise Edition. EJB is a server-side model that encapsulates the business logic of an application. The EJB specification was originally developed in 1997 by IBM and later adopted by Sun Microsystems (EJB 1.0 and 1.1) and enhanced under the Java Community Process as JSR 19 (EJB 2.0), JSR 153 (EJB 2.1) and JSR 220 (EJB 3.0).

The EJB specification intends to provide a standard way to implement the back-end 'business' code typically found in enterprise applications (as opposed to 'front-end' user-interface code). Such code was frequently found to reproduce the same types of problems, and it was found that solutions to these problems are often repeatedly re-implemented by programmers. Enterprise JavaBeans were intended to handle such common concerns as persistence, transactional integrity, and security in a standard way, leaving programmers free to concentrate on the particular problem at hand.

Types:

Session Beans are distributed objects having state: that is, they keep track of which calling program they are dealing with throughout a session. For example, checking out in a web store might be handled by a stateful session bean, which would use its state to keep track of where the customer is in the checkout process. Stateful session beans' state may be persisted, but access to the bean instance is limited to only one client.

Stateless Session Beans are distributed objects that do not have state associated with them thus allowing concurrent access to the bean. The contents of instance variables are not guaranteed to be preserved across method calls. The lack of overhead to maintain a conversation with the calling program makes them less resource-intensive than stateful beans. Sending an e-mail to customer support might be handled by a stateless bean, since this is a one-off operation and not part of a multi-step process.

Message Driven Beans were introduced in the EJB 2.0 specification, which is supported by Java 2 Platform, Enterprise Edition 1.3 or higher. The message bean represents the integration of JMS (Java Message Service) with EJB to create an entirely new type of bean designed to handle asynchronous JMS messages. Message Driven Beans are distributed objects that behave asynchronously. That is, they handle operations that do not require an immediate response.