We got farm of Red Hat servers which has Jboss 6.1 in our environments. Now we need to upgrade Jboss AS to 6.4. The easy way is to deploy the new version on the server and copy the config files and modules to the new jboss instance. It requires additional space in the filesystem.
Is there any other way to upgrade to 6.4 without having multiple instances. I am looking something like a patch upgrade on the existing Jboss 6.1 instance in CLI mode.
Please update your valuable thoughts.
Cheers,
Jose
You can use patch in CLI mode, See the guide[1]
[1]https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Installation_Guide/sect-Patching_JBoss_EAP_6.html
Related
I'm a newbie in DevOps. So I want to migrate an application from JBoss fuse in my laptop to Openshift fuse. How do I do that?
I have tried using oc command to build my source code on laptop but it doesn't work.
here is the error pic
thank you in advance
this seems to be the oc bug 1398330, which was merged into ocp and is in OCP v3.5.0.7 or newer.
Please test with the newest version.
I'm trying to migrate my JBoss eap 6.3 to JBoss eap 7.1, using a jboss migration tool, but the jboss-server-migration.sh is giving me illegalargumentexception: failed to retrieve server SOURCE
https://gist.github.com/jj110178/80616755c0335c2090d4256d8c322bb2
I'm tryin to follow this guide
https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.1/html/migration_guide/
https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.1/html-single/using_the_jboss_server_migration_tool
But unfortunately can't even get to run the migration tool
here is my directory structure
/c/Users/Username/dev/migration/jboss-eap-7.1
/c/Users/Username/dev/migration/jboss-eap-6.3
Hopefully someone can guide me on this
THanks in advance
I don't see -s or -t in the instructions. Try one of the versions in the guide. This one is when using a properties file.
EAP_HOME/bin/jboss-server-migration.sh --source EAP_PREVIOUS_HOME --environment path/to/my-server-migration.properties
https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.1/html/using_the_jboss_server_migration_tool/configuring_the_migration_tool
Thanks in advance. I am working on to upgrade JBOSS As7 to Wildfly 10. Manually I am able to do it. But I am looking for scripted solution that works without manual intervention as I need to upgrade 1000s of client. Please suggest some tools or scripts to do this.
Thanks,
Naga
I prefer to use CLI scripts to configure a server.
You are able to use variables and use the sript on different installations.
Also you are able to configure a new instance the same way as before.
If you use a newer version the CLI run check whether all is applicable.
I don't think that there is a general tool to migrate the config.
For minor versions you are able to copy the configuration folder, but you might loose new enhancements or features.
I learn that RHEL and Centos has the exact same source code. So my question here is if one application built for RHEL 6.4, could we just install and make it running on Centos 6.4 without any update?
And another question is RHEL and Centos will always use the same version number for the same source code, right?
Yes, software built on RHEL 6.4 should work as-is on CentOS 6.4 (assuming you don't depend on one of the relatively few RHEL-specific details, mostly to do with branding).
CentOS, except where necessary, uses upstream RHEL sources unmodified. When they need to modify a package they indicate that in the release notes and in the release field of the RPM in question.
JBoss Web 2.1.3 in JBoss 5.1.0 has some fixes that I need on a production server running JBoss Web 2.1.2 in JBoss 5.0.1.
I don't want to upgrade to JBoss 5.1.0 yet on a production cluster. This is too risky.
So how do I upgrade JBoss Web only?
This is a sar. So I'd imagine all that is required is to switch in jbossweb.sar from JBoss 5.0.1.
Has anybody done this? Is this the correct approach? Are there any gotchas?
I can't find any useful documentation in relation to this on the web.
Maybe I should ask this question on serverfault - but there seems to be less activity there.
Swapping out jbossweb.sar might work, but it's pretty risky in itself. If you're averse to the risk in moving to 5.1, I'd be just as averse to the risk of swapping JBossWeb.
That said, if you have a good automated test suite, then you might be able to get enough confidence in the swap to take it to production.
This sort of situation is where I get a lot of value from the RedHat/JBoss EAP subscription - they will backport fixes to the version of JBoss that you're running, plus test and verify it for you.
I managed to reproduce the bug we had and verified that it did not occur with jboss 5.1.0.
I upgraded to jboss 5.1.0 to sort this out.
That plus lots of system testing and everyone was happy.
Based on https://docs.jboss.org/jbossweb/2.1.x/building.html and https://developer.jboss.org/thread/156024:
mkdir -p /tmp/jbossweb && cd /tmp/jbossweb
svn checkout https://anonsvn.jboss.org/repos/jbossweb/branches/2.1.x/
wget https://archive.apache.org/dist/ant/binaries/apache-ant-1.6.5-bin.tar.gz
tar -zxvf apache-ant-1.6.5-bin.tar.gz && cd 2.1.x
../apache-ant-1.6.5-bin/bin/ant download
../apache-ant-1.6.5-bin/bin/ant
cp output/jars/jbossweb.jar $JBOSS_5.1.0.GA_HOME/server/default/deploy/jbossweb.sar/