I have been searching for RAD 7 and WAS 7 from IBM but could not find the relevant installers. I have an application that requires this version and I still have not been able to open it. I clarify that I need the specific version and not a different one (Neither previous nor superior).
I am grateful if you can tell me where I can download the versions of the indicated applications, no matter if they are the test versions or they are housed in unofficial repositories.
What operating system does your application run? For Linux use these PARTNUMBERS CZ0KHML.zip
Download 2 of 9:
WebSphere Application Server V7.0 for Linux on PowerPC, 32-bit, Multilingual
C1G03ML.tar.gz. C1G03ML
Related
I'm using ATG 9.1. how can I know which version of JDK must be used for different versions of ATG?
With JDK 6 I am able to work normally, whereas ACC is not working as it Requires a small version of JRE.
Why is that only ACC requires a small version of JRE and not other modules?
ATG/Oracle Commerce's required versions can be found on https://support.oracle.com -- you will need to log-in, and you may need access to be granted by an Oracle representative.
ATG 9.1 compatibility is covered in document "Oracle Art Technology Group (ATG) Commerce Supported Environments - Release 9.x (Doc ID 1342327.1)", which will link you to https://support.oracle.com/epmos/main/downloadattachmentprocessor?parent=DOCUMENT&sourceId=1342327.1&attachid=1342327.1:ATG9404&clickstream=yes
The 'compatibility matrix' shows the required JDK is "Sun 32-bit or 64-bit JDK 1.6.0_41" on all supported platforms (Windows, Solaris, RedHat) for JBoss and Weblogic application servers, but different for WebSphere.
The ACC can be run from within the app server, or in separate JVM. I don't know a reason why it would require a different JDK version.
Oracle usually suggest that this as a base version, so if a minor update to your application server requires a minor update to the JVM, you should probably follow your appserver's requirements.
Our agency requires that all Windows software be packaged by a central group. We've been using STS on Windows 7 for quite a while. I can't find any kind of official statement to indicate that it will run on Windows 10. Is STS working for folks running Windows 10 64 bit (HP hardware, if that makes a difference).
Several of us have tried finding information on the STS official site and I have submitted an issue to the STS issue tracker but it is unassigned. It would be helpful if we could point to some practical experience or success with this.
Thanks in advance,
Leila
I received a very helpful comment from Martin Lippert on the STS issue tracker site. He said "The latest version of STS (3.8.3) as well as the upcoming version (3.8.4) are based on Eclipse Neon, which has Windows 10 as a supported target environment defined (https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_6.xml). Therefore you can run STS on Windows 10."
We also tested it on a test computer and it seems to be working fine.
My Clearcase Version: 7.1.0 .
My os is windows 7, after I installed Clearcase. I couldn't create a dynamic view by using Create View.And I found that when i start clearcase service from control panel, there is only two service.
Is there any ways to correct this problem except to download a higher version.
ClearCase 7.1.2 is deployed on our Windows 7 at work.
However, when I see that there is only two services, that means MVFS (which is a device, not a driver) has failed to install properly.
The usual fix is to uninstall and reinstall ClearCase.
But there is no guarantee for 7.1.0.
The OP adds:
I have reinstall it three times, but the problem still exists
That confirms 7.1.0 is not supported (at least for the dynamic views part) on Windows 7.
As "System Requirements for ClearCase 7.1.x" confirms, Windows7 SP1 actually needs 7.1.2.3 at minimum.
And even then, you can have some issue: " PM54437: Windows 7 64bit MVFS clients flood albd_server of the View Server host with ALBD_FIND_SERVER RPCs" (which needs 7.1.2.6)
So getting the latest 7.1.x is recommended.
In your case though, since it isn't possible to get a version above 7.1.0, you can try and install a Virtual PC Windows Xp on your Windows 7.
Microsoft Virtual PC for Windows (formerly Connectix Virtual PC) is a client based software virtualization application that allows simultaneous operating systems to run on a single PC.
Each virtual machine emulates a complete hardware system—from processor to network card—in a self-contained, isolated software environment, enabling the simultaneous operation of otherwise incompatible systems.
ClearCase does support Virtual PC.
What's missing in dbgeng.dll in windows 7 Vs the dbgeng.dll distributed with debugging tools for windows ?
Very late to the party on this one but I've run into one very significant difference recently:
The dbgeng.dll built into windows installations will not support remote debugging where as the one installed with debugging tools does!
There appear to be other differences also that I didn't dig deeper into - all I knew was a working program using the built in dll started crashing when using the debugging tools one... which was a pain considering I would have liked to use the remote debugging facility out of the box.
This post shows the difference between Windows 7 and Windows 8 preview, I believe Windows 8 version is similar or possibly same as latest one that ships that is in debugging tools because when I do use dependencyWalker I notice that the one in Debugging Tools also has this new exported method DebugCreateEx which is also in the latest version
Windows 7 System 32 version:
Dependency walker:
Debugging tools version:
Dependency walker:
Hope this helps in some way to explain the differences, especially the post at the top.
I am required to create a simple application. Since I am good at WPF and I don't know win forms that good I implemented my application by creating a .Net Framework 4.0 WPF project in Visual Studio. Everything works great the application runs like it is supposed to.
Since the application is required to run in multiple platforms (Windows XP and above) I am including the prerequisites when publishing my applications. The prerequisites happen to be:
1) WIC (Windows Imaging Component) old computers need that to run the .net framework 4.0
2) Windows installer 3.1 (needed in order to install the next prerequisite)
3) Windows .NET Framework 4.0 Client Profile
If I install those prerequisites then the application runs like it is supposed to.
Now the problem is:
My boss did not approve my application because he tried installing it in a Windows XP machine with SP2 and this are the things that happened:
Step 1)
// first prerequisite (WIC) took less than 1 minute to install everything
// is working great so far.
Step 2)
// second prerequisite (Windows Installer 3.1) takes about 2 minutes to install
// which is great. After the installation is done the computer needs to be
// restarted in order to continue with the installation. Things are not going
// that good now but we are still ok...
Step 3)
// After the computer is done rebooting it continues with the last prerequisite
// (Windows .NET Framework 4.0 Client Profile). That takes 10 minutes to install!!!!
Step 4)
// My application has all the prerequisites needed to be installed so it installs in
// about 1 minute
We recorded the time, and the application took about 25 minutes to install from start to finish. The computer where we tested the installation was a virtual computer using 2 cores and 1 GB of memory with 3.1 GHZ.
What do you guys recommend in order to speed up this installation? Should I use a different technology such as windows forms using .net 2.0? It will be nice if I can deploy the application that I have already created. If you guys could help me make this application portable I will really appreciate it. In order to do so I tried building my application with all the required references copied to the output directory. That did not work... Or any ideas of how to make the installation be faster will be of great help as well.
If you're using .NET Framework 4.0 (which is not going to come out-of-the-box with any versions of Windows, especially Windows XP) there's no way to get around the install of .NET 4.0 on the target machine. Your major bottleneck is going to be the download of .NET 4.0 files from Microsoft to the machine.
I've run into similar problems where the initial install of an application takes forever because of the .NET 4.0 download and install. We even encountered an issue where the application couldn't be install because there was insufficient disk space for the download.
One option would be to pre-push the prereqs out to all the machines you'll be install this on before deploying your application.
Otherwise, you might be forced to use an older version of the .NET framework. Here's a list of the framework versions which shipped with various versions of windows.
http://blogs.msdn.com/b/astebner/archive/2007/03/14/mailbag-what-version-of-the-net-framework-is-included-in-what-version-of-the-os.aspx
Unfortunately, if your organization is committed to using a 10 year old operating system then they either need to accept that modern tools will require a lengthy install process while all prereqs are loaded... or else force you to use a 10 year old software technolgy.