using JBoss7 with pacemaker - jboss

Recently I'm trying to implement HA(High Available) on several redHat servers.
Tools:
pacemaker, JBoss
I only found this resource agent(http://linux-ha.org/doc/man-pages/re-ra-jboss.html) which only support JBoss5 and Jboss6. But my JBoss server is JBoss6 EAP which is actually JBoss7 so that I failed to implement HA using JBoss7 and pacemaker.
I have two questions:
1. I googled the resource agent script to find appropriate script to support JBoss7 but I failed. Is there anywhere I can find such a script?
2. If nobody has offered such script, how could I write such a script? Any documents which can offer any help?
thanks a lot.

Related

Jboss AS7 to Wildfly 10 Migration

im trying to migrate JBoss AS7.1 to Wildfly 10, i just followed some threads and i came upon this AS7 to Wildfly 10 guide. Basically it just tells how to migrate server configuration as well as application configuration.
But the problem is, it says to execute ":migrate" function "/subsystem=jacorb:migrate" on jboss cli (Jboss AS7.1 because it says execute on legacy subsystem) but it always throws an error, see below
No handler for migrate at address
Anyone familiar in executing migrate on jboss cli please point me to the right direction
UPDATES
I opted to migrate to wildfly10 from jboss-as7.1 manually (labor intensive, hassle), maybe if i have time to investigate about this i could feedback it there but as of know i time is of the essence and i need to migrate immediately.

How to configure mod_cluster with JBoss EAP 6 while it is running in domain mode?

If application server instances reside on different machines ?
I mainly want to know the configurations guide on the jboss eap server side.
I wrote this how-to a while ago on our project wiki: JBoss AS instances in Domain mode with mod_cluster load balancer. Please, check it out and ask away if it didn't help.

Difference between jboss 6 and jboss 7 standalone server?

I was using Jboss 6 . I am wondering to see jboss 7 which does not have many folders that jboss 6 had. It will be helpful if someone explains the difference between the jboss 7 stand alone server and the previous versions.
AS7 is different in a lot of respects to its predecessors AS6,5. So it wont be possible to list down all the differences here.
to list supported technology related differences, refer to below table.
Some Major Differences: (Thanks for #Jyore for additions)
Modular (on-demand) class-loading
Addition of domain managed nodes (multiple JVM management)
All configuration is done in Standalone.xml for standalone mode and domain.xml for domain mode.
About the new DIRECTORY Structure
configuration : Configuration files for the standalone server that runs off of this installation. All configuration information for the running server is located here and is the single place for configuration modifications for the standalone server.
data :Persistent information written by the server to survive a restart of the server
deployments: End user deployment content can be placed in this directory for automatic detection and deployment of that content into the server's runtime.
NOTE: The server's management API is recommended for installing deployment content. File system based deployment scanning capabilities remain for developer convenience.
lib/ext : Location for installed library jars referenced by applications using the Extension-List mechanism
log : standalone server log files
tmp : location for temporary files written by the server
Apart from that I really dont want to duplicate information on web
There is a migration guide from AS5,AS6 to AS7. This can help you understand what are the config changes that are generally required to switch to AS7. it also points out what has significantly changed, highly recommend going through it.
Also You can read Getting Started with AS7, to know AS7 better

Wix: The service cannot be started during installation

I'm having a problem with Wix Service as the service cannot be started during install progress. It throws the error:
Error 1053: The service did not respond to the start or control request in a timely fashion
I've tried with both [WIX_ACCOUNT_LOCALSYSTEM] and [WIX_ACCOUNT_LOCALSERVICE] but no one of them work.
But there is weird here as I have an installer which using ClickOne, it includes the same service component as the one I have been using in Wix. The ClickOne installs service just fine (using InstallUtil.exe), so it proves the account has right to start a service.
Then, I uninstall the software (installed by ClickOne), and running the Wix installer again, the service starts well now. I don't know the reason why?
I'd like to put some flows for more clearly:
1- On a fresh machine
2- Running Wix software installer --> the service cannot be started and throwing error message --> Cancel install
3- Running ClickOne software installer --> service starts well --> Uninstalling software
4- Running Wix software installer --> service starts well
Also note that, I've tried 2 times on 2 fresh machines but it's the same. Anyone can shed some light on this weird behavior? Or anything I should verify against?
Thanks in advance,
Thank you #Stephen Connolly, #Alexey Ivanov, #Cosmin Pirvu for your comments.
I'd like to add your comments above as the answer.
Using CheckAsm, a great tool to verify the assembly dependencies
Looking at the log information in Event Viewer for anything could stop the service starting (i.e. timeout, services dependency ...)
Verifying all stuffs would be needed for service operations. They should be available once installation completed (i.e. configuration, registry, working folder ...)
If the installer is installing files to the GAC using the Windows Installer tables, the dependencies won't be available when the installer runs the StartServices action

Monitor JBoss through SNMPv3

I am on a development team that is using JBoss EAP 4.3.0.GA_CP06. I need to be able to monitor JBoss using SNMPv3.
I understand I am able to use SNMP to monitor, but is it possible to monitor using v3 out-of-the box? If it is possible, what configurations need to be made to do this? If it is not possible, what external/other options are there for monitoring JBoss with SNMPv3?
Thanks.
Assuming the snmp-agent.sar is in your deploy directory (which depends on which config you picked), then JBoss will be exposing SNMP information on port 1161 (see inside the .sar for additional configuration).
I don't recall if this is SNMPv3, though, or v2.
This is not possible "out-of-the-box". An external SNMP adapter is required (e.g. WebNMS, iReasoning).