Upgrade weblogic 8.1 sp3 to 8.1 sp6; Need assistance!

Question

On a test / dev platform we used platform816_upgrade_solaris32.bin as provided by BEA to perform an upgrade from weblogic 8.1 sp3 to 8.1 sp6. The upgrade was successful. On an identical server (production)we attempted to follow the same steps with the same upgrade executable and it failed. Very early in the upgrade the tool requested that we identify BEA_Home which we did. It then replied that weblogic 8.1 was not running on our production server. Therefore we were unable to complete the upgrade. We do, however, run weblogic 8.1 on that server ... without question. We have a valid license file and we can view weblogic version info in our weblogic console. We noticed that the registry.xml file on the test server is different from the registry.xml file on production. Can anyone provide any assistance or advice? Thanks! ([email protected])

Answer 1

Hi
here is the Roadmap for Upgrading to WebLogic Platform 8.1 SP6
plz take a look at this link's
http://e-docs.bea.com/platform/docs81/upgrade/roadmap.html#1072938
http://e-docs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#1105995
-- check the JNDI lookup for both the managed server
-- JMS Connection Factory Tasks
Connection factories are objects that enable JMS clients to create JMS connections. A connection factory supports concurrent use, enabling multiple threads to access the object simultaneously. WebLogic JMS provides preconfigured "default connection factories" that can be enabled or disabled on a per-server basis, as described in Using a Default Connection Factory <jms_config.html>. Otherwise, you can configure one or more connection factories to create connections with predefined attributes that better suit your application ? as long as each connection factory is uniquely named. WebLogic Server adds them to the JNDI space during startup, and the application then retrieves a connection factory using WebLogic JNDI.
You can establish cluster-wide, transparent access to JMS destinations from any server in the cluster, either by using the default connection factories for each server instance, or by configuring one or more connection factories and targeting them to one or more server instances in the cluster. This way, each connection factory can be deployed on multiple WebLogic Servers. For more information on configuring JMS clustering, see "Managing JMS <../jms/config.html>" in Programming WebLogic JMS.
let me know the result,
Thanks,
Sathiya