I have a Java web app (WAR) that requires an older (1.5.11) version of the JRE, but am on Linux and spent a good deal of time setting up my environment for 1.6.34.
The web app needs to be hosted locally on JBoss (4.0.4 GA), which I have no experience with. I'm wondering if it is possible to download the 1.5.11 version of the JDK and configure things so that my JBoss instance is the only thing on my system that is using it. This way I don't need to worry about blowing out any of my other configs for 1.6.34.
If it is possible, what are the general steps and what are the JBoss configs I need to make? Thanks in advance.
Of course this is possible. You can install as many java versions as you like and make sure path/JAVA_HOME is set up correctly for each process you want to launch.
in JBOSS_HOME/bin/run.conf you can specify your 1.5 JAVA_HOME.
But if you are talking about serious business, you should get somebody (like your software supplier) to upgrade. 1.5.11 is superold and unsupported. and JBoss 4.0.4 is equally old and even less supported.
Related
Have multiple versions of Fabric runtimes on local machine (8.1, 8.2, and 9.0 series) which can be listed with:
Get-ServiceFabricRuntimeSupportedVersion
Have combed the Fabric documentation + web for anything about switching (changing) the SDK or Runtime version (effectively rolling back to an earlier installed version not the latest). Nothing. Anybody got an answer. Stopped investigating after trying:
Connect-ServiceFabricCluster
Unregister-ServiceFabricClusterPackage -Code -CodePackageVersion "9.0.1017.9590"
to back out version until I got to the one I want (8.2.1235.9590). But that fail with:
Fabric version has not been registered
Assuming this concerns only the current Powershell context. Start-ServiceFabricClusterRollback flops just like Unregister-ServiceFabricClusterPackage.
This might be very unhelpful, but I think the Supported Runtime Version is just which runtimes does the PS scripts support, not something about the local cluster.
The runtime you have installed is the latest one, so if you want to use an old one you have to uninstall the latest and find the bits for the old runtime and install that.
I am however, not entirely certain! It might be possible to switch runtimes, though it seems unlikely.
From the Control Panel choose Uninstall Programs and removed Fabric (6.0 SDK and Runtime). Restarted Windows (PC). Unclear if a restart is really necessary. Then opened the Web Platform Installer and through Spotlight searched for Fabric to click on Add. That put back 4.2.1235 of the SDK I needed. Done.
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.
We are using JBoss 4.2 GA, and need use a newest version in some new project.
I heard that JBoss 5.0 encounter such bugs... is this correct?
If not, which exact version of 5.0 to use?? and what about 6.0??
Thanks.
JBoss AS 5.1 is perfectly fine. Every app server has bugs, they're big, complex applications in themselves, but 5.1 is solid.
JBoss AS 6 hasn't been released yet, it's still in beta.
Jboss Application Server 7 is released, and up to a beta version of 7.1.0. You can download a copy here, and find the Getting Started Guides here.
As with any major revision of an application server, there are significant changes that might impact upon your business and will need to be considered in the context of your use case. Being an open source project, the early praise and early bugs are in the public arena, so it is easy to research for yourself.
Working on a documentation project involving AS7 I have seen some of the great work that the team has undertaken, and I couldn't imagine going back to a previous version now I've enjoyed the fast boot-up times, the ease of application deployment, custom configuration and the powerful Management CLI.
These kinds of improvements and features, not just constrained to JBoss Application Server or JBoss Enterprize Application Platform, speak volumes about the speed, stability and usability that will be increasing exponentially in this field for all competitors over the coming years. I'd urge you to check out the current generation of application servers if your experience is largely with JBoss AS 4.2.
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/
Hello all,
Can anyone tell me which IDE I can use to do development towards WAS 7.0?
Please help me out with the answer very soon. I have checked Netbeans 6.5 beta and it does not have the support for it. Also on the MyEclipse Blue Edition page it says Compatible with WebSphere 5.x, 6.0, 6.1, 7, but in http://www.myeclipseide.com/index.php?name=PNphpBB2&file=viewtopic&p=98487 I see "WebSphere Application Server V7.0 is not supported by MyEclipse at the moment. Thats the reasons you guys are running into issues."
Anyone please help me out with this issue ASAP.
IBM Rational Application Developer 7.5
If you want proper support for WAS, you should be using the Rational toolset. RAD/RSA and their brethren are optimized for Websphere (as you'd expect given they're both from IBM).
You can do it with baseline Eclipse (I'd use the "real" Eclipse rather than myeclipse) but the easiest set up will be with Rational. You may not want to spend the money however.
It's well worth the cost, since it comes bundled with WAS test environments and can deploy automatically to other WAS instances (for example, system test environments).
RAD 7.5 supports WAS 7 so I'd go for that one. RAD 7 only supports up to WAS 6.1.
See Compare Eclipse Packages for a nice chart