HiDiFiNeD Tech Life - Hitesh Bhupta

WebSphere Deployment Manual

2012-08-21T18:57:00.000+05:30

Deployment Manual for IBM WebSphere 6.1

Install IBM websphere. Setup will guide you through simple steps.

Please note the admin user id and password specify during installation

After installation. Start websphere application server by following steps

Starting application server

Console showing startup

3. After startup start Administrator console using following steps

4. Administrator console started (Login with ID & password) provided

5. Administrator console after login

6. Creating Data Source

a. Select ResourcesàJDBCàJDBC Provider from left panel

b. Select the scope and click new to create new data source

c. Specify JDBC-Provider details and click next.

d. Specify the ojdbc14.jar path. Click next

e. Summery page displays JDBC provider details and click finish

f. Select JDBC Provider from left panel, click Oracle JDBC driver that we created previously

g. Click on data source link

h. Click new to create new data Source

i. Type in the JNDI name, and select authentication from drop down list, if you do have any authentication created click on the link “Create new J2C authentication alias”

j. Create new alias, type in the database user id, database password, description and click apply

k. Follow the same steps from step H through F, after giving JNDI click next

l. In URL type à jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = IP)(PORT = 1521)))(CONNECT_DATA =(sid =SID_NAME)(SERVER=shared)))

- Select data store helper class name

- Click next

m. After having a glance at summery page, click finish.

n. Click save to save changes to data repository

o. Select the newly created data source and click Test Connection

Test connection showing success

Installing new application

a. Before deploying you application on Websphere we need to create a war file

b. Steps to create a war file

a. Set you jdk path

b. Go to you application (WAR) directory

c. Use jar –cvf war_name.war *.*command to create war file

c. In the full path specify/browse the file

d. Type in you context-root which will be used to access your application

e. Click next

f. Specify the application deployment path.

g. And with default settings click next

h. Select the entry to map with server

i. Click next

j. Summary page displays all the information regards application.

k. Click finish to start deployment

Snap showing deployment started

l. After deployment click save.

m. Select applicationàEnterprise Application, which displays all the application deployed

n. Select your application and click start

Application started

3. Stopping application server

Select startàprogramsàIBM WebsphereàProfileàApp01àstop server

Stop console

Note: - If you have any new JAR files to be added, add the files at InstallDirectory/IBM/Webshpere/lib/

Quartz Integration On Oracle Weblogic

2012-08-07T14:52:00.002+05:30

Quartz Integration On Oracle Weblogic

1. Pre-requisite for quartz integration

Pre-requisite to integrate quartz on WebLogic are as follows

1. Oracle WebLogic installed

2. Oracle/Database installed for connectivity

3. Application classes/jars, database connectivity drivers ( ojdbc14.jar )

4. JDK 1.6.0.3 or above

2. Starting Quartz on Oracle Weblogic (Windows Platform)

Before starting the application server, perform the following steps

1. Place the following jars/files in following directory

Installed Drive\Oracle\Middleware\user_projects\domains\testdomain\lib

� org.jar

� custom.jar

� com.jar

� jta-1_1-classes.jar

� quartz-weblogic-2.1.5.jar

� QuartzScheduler.cfg

2. Place the log4j.xml file in following directory

Installed Drive\Oracle\Middleware\user_projects\domains\testdomain

Note : "testdomain" in above path is the domain created while installing weblogic

3. Configuration changes

� QuartzScheduler.cfg

FileLogHeartbeats=Y ScreenLogShowHeartBeats=Y scriptFile=Framewrk/subs/json.lib,Framewrk/subs/filter.js,Framewrk/subs/da te.lib,Framewrk/common/FuncUtils.jds,Framewrk/common/dbUtils.jds,Frame wrk/common/DBSchema.js,Framewrk/subs/common.lib,Framewrk/main.jds orgMsgLogPath=C:/log serverPath=E:/Weblogic/weblogicwar/mfx_4_1_0_retail.war jndiName=mfx_4_1_0_retail_xa

FileLogHeartbeats : Log the quartz instance ScreenLogShowHeartBeats : On weblogic console show the quartz log scriptFile : Applications files to be loaded in quartz instance orgMsgLogPath : System path to log quartz info

serverPath : Path of application

jndiName : JNDI name used to connect to the deployed application.

Note : jndiName is the name of the data source created to connect to the application

4. Changes in application web.xml file

Path : Path to WAR\WAR Name\WEB-INF

Add the following tag and details to web.xml file inside the <web-app> tag

<servlet-name>QuartzInitializer</servlet-name>

<servlet-class>org.quartz.ee.servlet.QuartzInitializerServlet</servlet-cla

ss>

<init-param>

aram-name>shutdown-on-unload</param-name>

aram-value>true</param-value>

</init-param>

<init-param>

aram-name>start-scheduler-on-load</param-name>

aram-value>true</param-value>

</init-param>

<init-param>

aram-name>config-file</param-name>

aram-value>quartz.properties</param-value>

</init-param>

oad-on-startup>1</load-on-startup>

</servlet>

Note : If these changes are not made in the web.xml file of the application, the quartz scheduler will not run for the deployed application

5. Place the "quartz.properties" file in deployed application

Path : Path to WAR\WAR Name\WEB-INF

� Quartz.properties

#=============================================================

# Configure Main Scheduler Properties

#=============================================================

org.quartz.scheduler.instanceName = QuartzScheduler org.quartz.scheduler.rmi.export = false org.quartz.scheduler.rmi.proxy = false org.quartz.scheduler.xaTransacted = false

#org.quartz.scheduler.instanceId = AUTO

#=============================================================

# Configure ThreadPool

#=============================================================

org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool org.quartz.threadPool.threadCount = 100 org.quartz.threadPool.threadPriority = 4

org.quartz.scheduler.logger = schedLogger org.quartz.logger.schedLogger.class = org.quartz.impl.Log4jLogger

#=============================================================

# Configure JobStore

#=============================================================

org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreCMT

org.quartz.jobStore.driverDelegateClass =

org.quartz.impl.jdbcjobstore.StdJDBCDelegate

org.quartz.jobStore.dataSource = mfx_4_1_0_retail_xa

org.quartz.jobStore.tablePrefix = QRTZ_

#=============================================================

# Configure Datasources

#============================================================= org.quartz.dataSource.mfx_4_1_0_retail_xa.jndiURL = mfx_4_1_0_retail_xa org.quartz.jobStore.nonManagedTXDataSource = mfx_4_1_0_retail_xa org.quartz.jobStore.maxMisfiresToHandleAtATime=60000

org.quartz.plugin.triggHistory.class =

\org.quartz.plugins.history.LoggingTriggerHistoryPlugin

org.quartz.plugin.triggHistory.triggerFiredMessage = \Trigger \{1\}.\{0\} fired job \{6\}.\{5\} at: \{4, date, HH:mm:ss MM/dd/yyyy}

org.quartz.plugin.triggHistory.triggerCompleteMessage = \ Trigger \{1\}.\{0\}

completed firing job \{6\}.\{5\} at \{4, date, HH:mm:ss MM/dd/yyyy\}.

Configuration changes to be made

� Configure JobStore Section

Properties

org.quartz.jobStore.dataSource - Name of the data source created in weblogic to connect to the database

� Configure Datasources Section

Properties

org.quartz.dataSource.mfx_4_1_0_retail_xa.jndiURL = mfx_4_1_0_retail_xa org.quartz.jobStore.nonManagedTXDataSource = mfx_4_1_0_retail_xa

mfx_4_1_0_retail_xa in above properties is the data source name

6. Weblogic environment settings changes for quartz integration

� Open the "setDomainEnv.cmd" file and add the following code snippet

Path : Installed

Drive\Oracle\Middleware\user_projects\domains\testdomain\bin

Snippet :

Search for "LOG4J_CONFIG_FILE%" in the file and before that line add the following snippet

� set

LOG4J_CONFIG_FILE="E:/Oracle/Middleware/user_projects/domains/c

redence/log4j.xml"

This is the path to log4j.xml file that we placed in weblogic above in the guide.

7. Once the above changes are done restart the weblogic server and you will see

following messages flashing on weblogic console indicating the quartz status

Configuring Web Logic 10.3.5 and log4j for your Java Application

2012-07-17T19:01:00.003+05:30

I recently spent several days trying to track this down why Apache log4j for my Java application was working when deployed to Oracle WebLogic Server 10.3.5. I am posting my findings here in the hopes of saving others some time. I found several blogs that talked about this, but the end result was that log4j was still not working correctly. There was always one step missing. A co-worker and I finally figured it out for both Linux and Windows.

1. Copy wllog4j.jar from your WebLogic server/lib directory and place it in your domain_root/lib folder.
2. Copy your version of log4j.jar to your domain_root/lib folder.
3. Copy your log4j.xml to your domain_root folder.
4. Log in to the your WebLogic admin server console. Click on Servers -> Admin Server -> Logging. Click on advanced mode, and change the logging implementation from JDK to Log4J. Save your changes.

Most of the blogs had these items, but the one critical piece that was missing:
5. (Linux)Edit the setDomainEnv.sh file in the domain_root/bin directory. and find the following code:


if [ "${LOG4J_CONFIG_FILE}" != "" ] ; then
       JAVA_PROPERTIES="${JAVA_PROPERTIES} -Dlog4j.configuration=file:${LOG4J_CONFIG_FILE}"
       export JAVA_PROPERTIES
fi

Insert the following above those lines of code(replacing the path with the one for your system's domain_root directory:


LOG4J_CONFIG_FILE=”/u01/app/oracle/middleware/user_projects/domains/base_domain/log4j.xml”
Export LOG4J_CONFIG_FILE

5. (Windows)
Edit the setDomainEnv.cmd file in the domain_root/bin directory. and find the following code:


if NOT "%LOG4J_CONFIG_FILE%"=="" (                                                          
            set JAVA_PROPERTIES=%JAVA_PROPERTIES% -Dlog4j.configuration=file:%LOG4J_CONFIG_FILE%
)

Insert the following above those lines of code(replacing the path with the one for your system's domain_root directory:


set LOG4J_CONFIG_FILE=”C:\Oracle\Middleware\user_projects\domains\base_domain\log4j.xml”

6. Activate the changes and restart the admin server.

Here is a sample log4j.xml file. Obviously, you will need to update it for a valid location for your file appender, and replace yourcompany and yourproject with valid values.

Again, I hope that this will save someone the pain I went through to track this down.

Apache SSL with JBoss

2011-11-11T16:58:00.000+05:30

Prerequisites
Jboss-4.2.2.GA installed

1. Install Apache 2.2
C:\Program Files\

2. Copy Apache server to new server
i. C:\Program Files\Apache Software Foundation\Apache2.2\conf\
httpd.conf
ii. C:\Program Files\Apache Software Foundation\Apache2.2\conf\uriworkermap.properties
iii. C:\Program Files\Apache Software Foundation\Apache2.2\conf\worker2.properties
iv. C:\Program Files\Apache Software Foundation\Apache2.2\conf\workers.properties.minimal
v. C:\Program Files\Apache Software Foundation\Apache2.2\conf\workers.properties

3. Get the .crt file and .key file and store it in
C:\Program Files\Apache Software Foundation\Apache2.2\conf\

4. Copy Apache server to new server (All files in module directory)
i. C:\Program Files\Apache Software Foundation\Apache2.2\modules

5. In file C:\Program Files\Apache Software Foundation\Apache2.2\conf\httpd.conf make following changes.
i.
LoadModule jk_module modules/mod_jk.so
JkWorkersFile conf/workers.properties
JkLogFile logs/mod_jk.log
JkMountFile conf/uriworkermap.properties
JkMountCopy All
ii.
Uncomment/add lines

Include conf/extra/httpd-ssl.conf

iii
ServerName 127.0.0.1:443 {host name like host.domain.com}

6. In file C:\Program Files\Apache Software Foundation\Apache2.2\conf\extra\httpd-ssl.conf

make following changes.

i. {apache server ip and SSL port}

ii. ServerName 127.0.0.1:443 {host name like host.domain.com}

iii. Change the .crt and .key file name
SSLCertificateFile "C:/Program Files/Apache Software Foundation/Apache2.2/conf/ssl.crt"
SSLCertificateKeyFile "C:/Program Files/Apache Software Foundation/Apache2.2/conf/ssl.key"

7. In file C:\Program Files\Apache Software Foundation\Apache2.2\conf\workers.properties

make following changes.
i. worker.tomcat1.host=192.168.1.246 {Jboss server ip}
ii. worker.tomcat2.host=192.168.1.246 {Jboss server ip}
iii. worker.tomcat3.host=192.168.1.246 {Jboss server ip}

8. Restart Apache and type URL with apache server ip
(https://192.168.1.46/testapp/Server.jsp) {Here ip address is of Apache server }

Integrating Quartz with JBoss

2011-11-11T16:21:00.000+05:30

Quartz Overview

Quartz is a full-featured, open source job scheduling service that can be integrated with, or used along side virtually any Java EE or Java SE application - from the smallest stand-alone application to the largest e-commerce system. Quartz can be used to create simple or complex schedules for executing tens, hundreds, or even tens-of-thousands of jobs; jobs whose tasks are defined as standard Java components that are programmed to fulfill the requirements of your application. The Quartz Scheduler includes many enterprise-class features, such as JTA transactions and clustering.

What Can Quartz Do For You?

If your application has tasks that need to occur at given moments in time, or if your system has recurring maintenance jobs then Quartz may be your ideal solution.

Sample uses of job scheduling with Quartz:

Driving Process Work flow: As a new order is initially placed, schedule a Job to fire in exactly 2 hours, that will check the status of that order, and trigger a warning notification if an order confirmation message has not yet been received for the order, as well as changing the order's status to 'awaiting intervention'.
System Maintenance: Schedule a job to dump the contents of a database into an XML file every business day (all weekdays except holidays) at 11:30 PM.
Providing reminder services within an application.

Features

Runtime Environments

Quartz can run embedded within another free standing application
Quartz can be instantiated within an application server (or servlet container), and participate in XA transactions
Quartz can run as a stand-alone program (within its own Java Virtual Machine), to be used via RMI
Quartz can be instantiated as a cluster of stand-alone programs (with load-balance and fail-over capabilities)

Job Scheduling

Jobs are scheduled to run when a given Trigger occurs. Triggers can be created with nearly any combination of the following directives:

at a certain time of day (to the millisecond)
on certain days of the week
on certain days of the month
on certain days of the year
not on certain days listed within a registered Calendar (such as business holidays)
repeated a specific number of times
repeated until a specific time/date
repeated indefinitely
repeated with a delay interval

Jobs are given names by their creator and can also be organized into named groups. Triggers may also be given names and placed into groups, in order to easily organize them within the scheduler. Jobs can be added to the scheduler once, but registered with multiple Triggers. Within a J2EE environment, Jobs can perform their work as part of a distributed (XA) transaction.

Job Execution

Jobs can be any Java class that implements the simple Job interface, leaving infinite possibilities for the work your Jobs can perform.
Job class instances can be instantiated by Quartz, or by your application's framework.
When a Trigger occurs, the scheduler notifies zero or more Java objects implementing the JobListener and TriggerListener interfaces (listeners can be simple Java objects, or EJBs, or JMS publishers, etc.). These listeners are also notified after the Job has executed.
As Jobs are completed, they return a JobCompletionCode which informs the scheduler of success or failure. The JobCompletionCode can also instruct the scheduler of any actions it should take based on the success/fail code - such as immediate re-execution of the Job.

Job Persistence

The design of Quartz includes a JobStore interface that can be implemented to provide various mechanisms for the storage of jobs.
With the use of the included JDBCJobStore, all Jobs and Triggers configured as "non-volatile" are stored in a relational database via JDBC.
With the use of the included RAMJobStore, all Jobs and Triggers are stored in RAM and therefore do not persist between program executions - but this has the advantage of not requiring an external database.

Integrating Quartz with Jboss

Pre-requisite required for integration

Jboss ( 4.4.2 )
Quartz 1.6.6 ( It can be downloaded from http://quartz-scheduler.org/downloads/catalog )
Additional Jars and libs

jboss-xa-jdbc.rar
commons-dbcp-all-1.3-r699049.jar

Placing the additional jars/libs required

Copy jboss-xa-jdbc.rar to JBOSS_HOME\server\default\deploy directory
Place commons-dbcp-all-1.3-r699049.jar to JBOSS_HOME\server\default\lib directory

Steps to integrate.

JBoss already has got Quartz bundled with it. But actually you can not do much with this as it supports only RAMJobStore. So to use it effectively we need to do some more. We have to copy quartz-1.6.6.jar and quartz-jboss-1.6.6.jar in the JBOSS_HOME/server/default/lib directory. Then, we need to create a xml file to configure Quartz as a service in JBOSS_HOME/server/default/deploy directory ( xml file can be found with Quartz download lib directory ).

Create the data base
We need to create the database where all job and trigger information will get stored eventually. The sql scripts are bundled with Quartz download under docs/dbTables directory.
quartz-service.xml
As already mentioned we need to create the quartz-service file . Let me just enclose a sample file.

             name="user:service=QuartzService,name=QuartzService">      jboss.jca:service=DataSourceBinding,name=QuartzDS               true                         org.quartz.scheduler.instanceName = DefaultQuartzScheduler    org.quartz.scheduler.rmi.export = false    org.quartz.scheduler.rmi.proxy = false    org.quartz.scheduler.xaTransacted = false        org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool    org.quartz.threadPool.threadCount = 100    org.quartz.threadPool.threadPriority = 4           org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreCMT    org.quartz.jobStore.driverDelegateClass =  org.quartz.impl.jdbcjobstore.StdJDBCDelegate    org.quartz.jobStore.dataSource = QUARTZ        org.quartz.jobStore.tablePrefix = QRTZ_    org.quartz.dataSource.QUARTZ.jndiURL = java:QuartzDS        org.quartz.jobStore.nonManagedTXDataSource = QUARTZ    #org.quartz.dataSource.QUARTZ_NO_TX.driver = oracle.jdbc.driver.OracleDriver    #org.quartz.dataSource.QUARTZ_NO_TX.URL = jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.103)(PORT = 1521)))(CONNECT_DATA =(sid =rajni)(SERVER=shared)))    #org.quartz.dataSource.QUARTZ_NO_TX.user = mercury_dcd    #org.quartz.dataSource.QUARTZ_NO_TX.password = mercury_dcd        org.quartz.jobStore.maxMisfiresToHandleAtATime=60000        org.quartz.plugin.triggHistory.class = \org.quartz.plugins.history.LoggingTriggerHistoryPlugin    org.quartz.plugin.triggHistory.triggerFiredMessage = \Trigger \{1\}.\{0\} fired job \{6\}.\{5\} at: \{4, date, HH:mm:ss MM/dd/yyyy}    org.quartz.plugin.triggHistory.triggerCompleteMessage = \  Trigger \{1\}.\{0\} completed firing job \{6\}.\{5\} at \{4, date, HH:mm:ss MM/dd/yyyy\}.

The point to note here is that we'll need two datasource elements for this configuration. One is standard datasource managed by JBoss container (see the line org.quartz.jobStore.dataSource = QUARTZ) another one is not managed by the container, on which quartz can call commit/rollback by itself. We have to confugure the container managed datasource as a standard jboss *-ds file, whereas we configure the non_managed_datasource inside this quartz-service.xml itself. Here one gotcha is for the container_managed datasource, we'll need to use XA datasource (I am not very sure why regular local datasource does not work. Maybe reason being Quartz works in a clustered environment, just a guess though).

Adding a new job to Quartz requires the following details.

Sample oracle-ds file:

      QuartzDS    oracle.jdbc.xa.client.OracleXADataSource     jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.103)(PORT = 1521)))(CONNECT_DATA =(sid =rajni)(SERVER=shared)))    mercury_dcd    mercury_dcd    TRANSACTION_READ_COMMITTED    5    0     2000    2    true    false    org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter                 mySQL

Run.bat / Run.sh

Setting classpath to be able to use Quartz libs from Application war

JBOSS_HOME\jboss-4.2.2.GA\server\default\lib\quartz-1.6.6.jar;

JBOSS_HOME\jboss-4.2.2.GA\server\default\lib\commons-dbcp-all-1.3-r699049.jar;

JBOSS_HOME\lib\custom\classes\Executor.class; ( Is discussed below )

JBOSS_HOME\jboss-4.2.2.GA\lib\custom\classes\QuartzScheduler.class; ( Is discussed below )

Note:

On completion of above steps, restart Jboss server and see that the Quartz service is deployed successfully

Working with Quartz

To simplify the pain in creating and manage the jobs within Quartz, I have created a class that manages all the processes like adding job, deleting job, rescheduling job, pause/resume job, metadata and start/stop scheduler.

Currently this class support only CRON TRIGGERS.

Add a new job to Quartz scheduler

Function :

public String addQrtzCronJob(HashMap jobHashMap)

{

try

{

//Getting the schedular context

InitialContext ctx = new InitialContext();

Scheduler scheduler = (Scheduler) ctx.lookup(((String)jobHashMap.get("dsXName")).toString());

//checking schedular shutdown status

if(scheduler.isShutdown())

{

createLog("\n"+new Date()+" {status:'unsuccess',error:'Schedular for source "+((String)jobHashMap.get("dsXName")).toString()+" already shutdown.',msg:''} ");

return "{status:'unsuccess',error:'Schedular for source "+((String)jobHashMap.get("dsXName")).toString()+" already shutdown.',msg:''}";

}

// defines job and execution class

JobDetail job = new JobDetail(((String)jobHashMap.get("jobName")).toString(), ((String)jobHashMap.get("jobGroup")).toString(), Class.forName(((String)jobHashMap.get("exeClass")).toString()) );

//Passing params to exector class

job.getJobDataMap().put("FUNCTION",((String)jobHashMap.get("funcName")).toString());

job.getJobDataMap().put("PARAMS",((String)jobHashMap.get("funcParams")).toString());

job.getJobDataMap().put("LOGPATH",(String)getQuartzCfgPath());

//Defines cron trigger with cron expression

CronTrigger trigger = new CronTrigger(((String)jobHashMap.get("trgName")).toString(), ((String)jobHashMap.get("tgrGroup")).toString(), ((String)jobHashMap.get("jobName")).toString(),

((String)jobHashMap.get("jobGroup")).toString(), ((String)jobHashMap.get("cronExpr")).toString());

//Setting mis fire instrunction for trigger

trigger.setMisfireInstruction(CronTrigger.MISFIRE_INSTRUCTION_FIRE_ONCE_NOW);

// Adds the job to schedular

scheduler.addJob(job, true);

// Schedules the job

Date ft = scheduler.scheduleJob(trigger);

createLog("\n"+new Date()+job.getFullName() + " has been scheduled to run at: " + ft+ " and repeat based on expression: "+ trigger.getCronExpression()+" ::getQuartzLogPath()="+getQuartzLogPath());

return "{status:'success',error:'',msg:'Job added successfully'}";

}

catch(Exception e)

{

createLog("\n"+new Date()+" {status:'unsuccess',error:'"+e.toString()+"',msg:''} ");

return "{status:'unsuccess',error:'"+e.toString()+"',msg:''}";

}

ExeClass : The class that is to be called on execution by default it should be “custom.classes.Executor”

dsXName : The Data source name

jobName : Job name for the given job

jobGroup : Job group associated with the job, if job group is null, its takes the default job group.

trgName : Trigger name for the given job

tgrGroup : Trigger group name

cronExpr : CRON Expression to specify the time/period for job execution.

FuncName : This is the name of function which is to be called when the job executes

funcParams : Params are the extra information passed to function

Delete a job

Function:

public String deleteQrtzCronJob(String dsXName,String jobName,String jobGroup)

{

try

{

createLog("\n"+new Date()+" deleteQrtzCronJob called dsXName="+dsXName+",jobName="+jobName+",jobGroup="+jobGroup);

InitialContext ctx = new InitialContext();

Scheduler scheduler = (Scheduler) ctx.lookup(dsXName);

boolean deleteJob = scheduler.deleteJob(jobName, jobGroup);

if(deleteJob)

{

createLog("\n"+new Date()+" {status:'success',error:'',msg:'Job deleted successfully.'}");

return "{status:'success',error:'',msg:'Job deleted successfully.'}";

}

else

{

createLog("\n"+new Date()+" {status:'unsuccess',error:'Job cannot be deleted',msg:''}");

return "{status:'unsuccess',error:'Job cannot be deleted',msg:''}";

}

}

catch(Exception e)

{

createLog("\n"+new Date()+" {status:'success',error:'"+e.toString()+"',msg:''} ");

return "{status:'unsuccess',error:'"+e.toString()+"',msg:''}";

}

}

Deleting a job within Quartz requires the following details.
1. dsXName : The Data source name
2. jobName : Job name to be deleted
3. jobGroup : The job group associated with the job to be deleted
Reschedule a job

Function :

public String reScheduleQrtzCronJob(HashMap jobHashMap)

{

try

{

//Getting the schedular context

InitialContext ctx = new InitialContext();

Scheduler scheduler = (Scheduler) ctx.lookup(((String)jobHashMap.get("dsXName")).toString());

//checking schedular shutdown status

if(scheduler.isShutdown())

{

createLog("\n"+new Date()+" {status:'unsuccess',error:'Schedular for source "+((String)jobHashMap.get("dsXName")).toString()+" already shutdown.',msg:''}");

return "{status:'unsuccess',error:'Schedular for source "+((String)jobHashMap.get("dsXName")).toString()+" already shutdown.',msg:''}";

}

//Defines cron trigger with cron expression

CronTrigger trigger = new CronTrigger(((String)jobHashMap.get("trgName")).toString(), ((String)jobHashMap.get("tgrGroup")).toString(), ((String)jobHashMap.get("jobName")).toString(),

((String)jobHashMap.get("jobGroup")).toString(), ((String)jobHashMap.get("cronExpr")).toString());

//Setting mis fire instrunction for trigger

trigger.setMisfireInstruction(CronTrigger.MISFIRE_INSTRUCTION_FIRE_ONCE_NOW);

// Adds the job to schedular

Date ft = scheduler.rescheduleJob(((String)jobHashMap.get("trgName")).toString(), ((String)jobHashMap.get("tgrGroup")).toString(), trigger);

createLog("\n"+new Date()+" {status:'success',error:'',msg:'Job rescheduled successfully with expression'"+((String)jobHashMap.get("cronExpr")).toString()+"} ");

return "{status:'success',error:'',msg:'Job rescheduled successfully with expression'"+((String)jobHashMap.get("cronExpr")).toString()+"}";

}

catch(Exception e)

{

createLog("\n"+new Date()+" {status:'success',error:'"+e.toString()+"',msg:''} ");

return "{status:'unsuccess',error:'"+e.toString()+"',msg:''}";

}

Rescheduling a job within Quartz requires the following details.

ExeClass : The class that is to be called on execution by default it should be “custom.classes.Executor”

dsXName : The Data source name

jobName : Job name for the given job

jobGroup : Job group associated with the job, if job group is null, its takes the default job group.

trgName : Trigger name for the given job

tgrGroup : Trigger group name

cronExpr : CRON Expression to specify the time/period for job execution.

Pause a job

Function :

public String pauseQrtzCronTrigger(String dsXName,String trgName,String trgGroup)

{

try

{

createLog("\n"+new Date()+" pauseQrtzCronTrigger called dsXName="+dsXName+",trgName="+trgName+",trgGroup="+trgGroup);

InitialContext ctx = new InitialContext();

Scheduler scheduler = (Scheduler) ctx.lookup(dsXName);

scheduler.pauseTrigger(trgName, trgGroup);

createLog("\n"+new Date()+" {status:'success',error:'',msg:'Trigger stop/paused successfully.'}");

return "{status:'success',error:'',msg:'Trigger stop/paused successfully.'}";

}

catch(Exception e)

{

createLog("\n"+new Date()+" pauseQrtzCronTrigger exception : {status:'unsuccess',error:'"+e.toString()+"',msg:''} ");

return "{status:'unsuccess',error:'"+e.toString()+"',msg:''}";

}

Pause a job within Quartz requires the following details.

dsXName : The Data source name
jobName : Job name to be paused

jobGroup : The job group associated with the job to be paused

Resume a job

Function :

public String resumeQrtzCronJob(String dsXName,String jobName,String jobGroup)

{

try

{

createLog("\n"+new Date()+" resumeQrtzCronJob called dsXName="+dsXName+",jobName="+jobName+",jobGroup="+jobGroup);

InitialContext ctx = new InitialContext();

Scheduler scheduler = (Scheduler) ctx.lookup(dsXName);

scheduler.resumeJob(jobName, jobGroup);

createLog("\n"+new Date()+" {status:'success',error:'',msg:'Job resumed successfully.'}");

return "{status:'success',error:'',msg:'Job resumed successfully.'}";

}

catch(Exception e)

{

createLog("\n"+new Date()+" resumeQrtzCronJob exception : {status:'unsuccess',error:'"+e.toString()+"',msg:''} ");

return "{status:'unsuccess',error:'"+e.toString()+"',msg:''}";

}

Resume a job within Quartz requires the following details.

dsXName : The Data source name
jobName : Job name to be resumed
jobGroup : The job group associated with the job to be resumed

Start scheduler

Function :

public String startQrtzSchedular(String dsXName)

{

try

{

createLog("\n"+new Date()+" startQrtzSchedular called dsXName="+dsXName);

InitialContext ctx = new InitialContext();

Scheduler scheduler = (Scheduler) ctx.lookup(dsXName);

if(!scheduler.isShutdown())

{

createLog("\n"+new Date()+"checking shutdown status {status:'unsuccess',error:'Schedular for source "+dsXName+" already running.',msg:''}");

return "{status:'unsuccess',error:'Schedular for source "+dsXName+" already running.',msg:''}";

}

scheduler.start();

return "{status:'success',error:'',msg:'Scheduler started successfully'}";

}

catch(Exception e)

{

createLog("\n"+new Date()+" {status:'success',error:'"+e.toString()+"',msg:''} ");

return "{status:'unsuccess',error:'"+e.toString()+"',msg:''}";

}

Start Scheduler with Quartz requires the following details.

dsXName : The Data source name

Stop scheduler

Function :

public String stopQrtzSchedular(String dsXName)

{

try

{

createLog("\n"+new Date()+"stopQrtzSchedular called with dsXName="+dsXName);

InitialContext ctx = new InitialContext();

Scheduler scheduler = (Scheduler) ctx.lookup(dsXName);

if(scheduler.isShutdown())

{

createLog("\n"+new Date()+" {status:'unsuccess',error:'Schedular for source "+dsXName+" already shutdown.',msg:''} ");

return "{status:'unsuccess',error:'Schedular for source "+dsXName+" already shutdown.',msg:''}";

}

scheduler.shutdown(true);

return "{status:'success',error:'',msg:'Scheduler shutdown successfully'}";

}

catch(Exception e)

{

createLog("\n"+new Date()+" execption in stopQrtzSchedular {status:'success',error:'"+e.toString()+"',msg:''} ");

return "{status:'unsuccess',error:'"+e.toString()+"',msg:''}";

}

Stop Scheduler with Quartz requires the following details.

1. dsXName : The Data source name

HiDiFiNeD Tech Life - Hitesh Bhupta

WebSphere Deployment Manual

Installing new application

Quartz Integration On Oracle Weblogic

Configuring Web Logic 10.3.5 and log4j for your Java Application

Apache SSL with JBoss

Integrating Quartz with JBoss

Quartz Overview

Features

Integrating Quartz with Jboss

Working with Quartz

Add a new job to Quartz scheduler

Delete a job

Reschedule a job

Pause a job

Resume a job

Start scheduler

Stop scheduler