Yes, it's Blaze Advisor 6.8 for Java. Blaze Advisor 6.7 supports JDK 1.6 and will work in WAS 7.0 as well, but there is no dedicated quick deployer for it.
You can still deploy Blaze in a web container using Java quick deployer, or you can adapt files generated by EJB, MDB or Web Services quick deployer for WAS 6.1 to WAS 7.0
Adding to this thread as it is related.
Deployed a Blaze Advisor 6.8 RMA into WAS 7.0, but when try and use the RMA, it runs very slow, and throws up alot of NullPointer exceptions. However run it in tomcat and it works fine, and it is also fine within the IDE (Using Sun JVM 1.6).
However if I use IBM JVM 1.6 with Blaze Advisor IDE then as soon as I open up a rules project I get the same Nullpointer exception. I have subsequently looked at the InstallationAndSetup.pdf that says IBM JDK 1.6 isn't supported, if this is the case does that mean we cannot run the RMA on WAS 7.0?
Aviva UK Health
We are currently using blaze advisor 6.7 and migrating to was 7 from was 6.1. We are also using IBM's RSA 7.5.3. Our rule service is called by accessing the .adv, .jcp and .rb files. We are receiving "Failure initializing an agent for project http://localhost:9080/bzccn/rule_ccn/CCN_Assignment.adv."
Here is an excerpt from our .server file
I double checked that we are using Java 1.6 in Blaze and in the WAS 7 server.
Tried IBM 1.6.0 JVM SR6, Still the same issue. Any updates how we can get around this problem
Our team is running in production with Blaze Advisor 6.8 on WAS 7.0 with SR6 with JDK 6. We have no issues at this time, everything is working perfectly at this time. It is imperative that the EAR/WAR projects and the ADB file (rulebase) be compiled using the same JDK and that the same JDK is running on the Server as was used for compilation. If everything is not the same, you will see compatibility exceptions at run-time if not at build time.
In WAS 6.1, We compiled the rules under SUN JDK and at runtime we used IBM 1.5 JDK that came with the websphere and it worked, has anything changed in WAS 7.0 that requires the same JDK. BTW we use JSR 94 API Deployment which is basically a set of INNOVATOR ATTRIB Files and i donot see any change in those file just by switching JDK but if i deploy the application under JBOSS using SUN JVM 1.6.0 it works.
Retrieving data ...