Someone told me that there are some annotations in JBoss Application Server that can do similar work as Quartz. What are these annotations? Are they better than Quartz?
This blog post lists the options available within JBoss: http://anilsaldhana.blogspot.com/2011/05/scheduler-jobs-in-jboss-as.html
To summarize:
Quartz Scheduler:
http://docs.jboss.org/ejb3/docs/tutorial/1.0.7/html/Quartz_scheduler_integration.html
http://community.jboss.org/wiki/HowtoconfigureaQuartzservice
java.util.Timer:
You will need to create your own instances of timer tasks in your application.
JBoss Scheduler:
http://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/Additional_Services-Scheduling_Tasks.html
Section 10.7 and 10.8 of http://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/index.html
Related
I am very new to jboss app server and using jboss app server 4.1.4 and want to upgrade to any latest version like 6 or 7. What’s the best process to perform i.e. I have seen that “copy the .rar and .war files” and these can’t make right scene to work. What's the best process?
The best way to start is to get an overview over your existing application. In particular:
Which non-standard JBoss features do you use (JBoss Cache, JCA Work Manager, …)?
What "managed resources" (data sources, connection factories, …) do you use?
Which configuration changes did you make (connection pool, transaction timeout, …)?
Which classloading assumptions does your packaging make?
and then individually check how these are handled in the JBoss version you want to migrate to.
there is no one to answer this question..looks shame about it.
I'm trying to find the best way to grammatically determine if my program is running on Jboss 5 or Jboss 7 (eap-6.1). The ways I've been finding so far are jboss 5 or jboss 7 specific, which doesn't work because the code has to work in both. Tried both solutions from here: How do I programmatically obtain the version in JBoss AS 5.1? and they didn't work. One complained about org.jboss.Main not existing in jboss 7, the other complained aobut not finidng "jmx/rmi/RMIAdaptor".
The only way I can see is to do Class.forName to look for "org.jboss.Version" (should be found if jboss 5) and if that fails, do Class.forName "org.jboss.util.xml.catalog.Version" (jboss 7). But that seems like a terrible idea.
The reason I need to know if the war is running on jboss 5 or 7 is because there are some custom files that are located in different places in both. So it's like "if jboss 5, execute this piece of code, if jboss 7 execute the other.
Ok i just saw what the problem is.
I would suggest you to think about design issues/refactoring of your software.
If you want to provide your software within different environments, seperate your logic from
technology dependencies.
Build facedes and interfaces to meet environmental requironments.
In my oppionen thats much better as to think we must support all integration platforms and support all there versions. This is completely impossible.
So decouple your business logic and offer specific interfaces. These interfaces (adapters) are much simplier to implement and to maintain.
Hope it helps.
UPDATE DUE TO COMMENT.
I think a solution is for servers 4 to 6 is to use
the MBean Server of JBoss to lookup the registered web application
which is associated to the deployed WarFile.
I suggest first to lookup the registered MBean of the web application manually using the JBoss jmx-console. The name of the WebApplication should be found under the capital "web" or "web-deployment" within the jmx-console.
If you found that name you can implement an own jmx based lookup mechanism
to check for that name.
Here is an Tutorial: pretty old but i think it gives you an idea how to do.
There must be more tutorials for this problem:
http://www.theserverside.com/news/1364648/Using-JMX-to-Manage-Web-Applications
Within JBoss 7 i just can give you the hint that its architecture is based on OSGI. So to lookup for other services you should have a look to this mechanism.
In any case you don't have direct access to the file system and the deployment directory
from an application which is deployed within a JEE container, except of
using the mechanisms provided by the container. JNDI Lookup, JMX ManagedBean mechanism, Java Connector Archicture (JCA) (makes no sense in your case)
It's not an answer just an suggestions since the implementations are completely different
One way could be to use the "interceptors" which are executed during bootstrap and before any ejb invocation and there you have access to the invocation context in other words ejb container.
I can't give you any example but this would be an access point to start.
Another accesspoint is to check for system wide JMX Beans by looking through the
Adminstratore console of the JBoss Server.
You can inject JMX Bean state into your application through the Context Mechansim.
Take a look from Version 4 to 6 at the JMX Managed Bean mechanism. The JMX Achitecture is the main concept of JBoss 3 to 6, so at this point you can influence and maintain the JBoss behaviour.
Aditionally i think you have differences from 4 to 6.x version and 7.0 because since
7 it's a completely new architecture. Since 7.0 the JMX architecture doens't exists anymore.
I have a bunch of services (EJBs, remotem stateless) running on JB-AS 5.1.0. Now I have a new AS7.1 on which I develop new Services (JEE6, EJB, CDI, ...)
I want to access the AS5.1 Services via remote JNDI.
Has anyone done this before and can help? I need my JEE6-Beans to have access to the AS5.1 client-jars, so I am trying to add them to ear/lib or create a module containing the jars, but so far without luck ...
The best solutions I have seen so far can be found here. You can follow this forum for more information.
Please post your findings here so others can help / benefit.
Good luck!
I want to know if is possible deploy GWT 2.x applications on server with support for the servlet spec 2.4 like JBoss 4.
I have reviewed the official documentation but apparently there is no dependences. So my questions are:
Is possible?
Is needed workarounds?
Any has some previous experience?
Yes It is possible. You can deploy GWT applicaions to any external web server like Tomcat, Jboss etc. Your question is bit wide in context. So, better look at some tutorials.
This tutorial will help you more. I have not gone into details of this but seems good.
Can anyone suggest which monitoring tool is the best for monitoring JBOSS, in particular ESB queue depth etc?
I currently use Hyperic with a custom plugin, does anything support JBOSS ESB out of the box?
JBoss Operations Network is your best bet if you want an out-of-the-box working project.
http://www.jboss.com/products/jbosson/