Hi All,
We did a migration using the upgrade guide from 8.2 to 9.6 for all components - Integration Server, MWS, TN, Centrasite and Mediator.
The migration of all components was successful. However, MWS server instance (default) does not start after the migration utility is run.
Steps followed are as below:

1. Shut Down MWS 8.2.
2. Copy the database to a new Schema.
3. Install MWS 9.6
4. Start MWS 9.6 - it works at this time.
5. Shut Down all components of 9.6.
6. Start MWS 8.2
   7.Upgrade MWS 8.2 to latest fix level.
7. Run the migration scripts.
8. Shut down all components on 8.2
9. Start version 9.6
   The error I receive while starting the MWS states that there is a missing configuration of node on the cluster. However, this environment is not clustered in both the versions. Did anyone face a similar issue/ has experienced with something similar and knows any solution? Please let me know. Thanks.

Before running the migration utility, we should not suppose to start any server. After migration only we can start server otherwise migration utility will not work properly.

Thanks & Regards,
Abhishek

After completing MWS upgrade you need to update the default server instance by using server.sh - update command in mws/bin

Thanks for your replies guys,

To Clarify further,

@Abhishek, The server was started only after the migration utility was completed.
@Sreenivas, the command was run but still got the same error after we try to start the server.

For some reason, MWS tries to believe it is a cluster and tries to find the second node on the cluster after migration.
The logs show that it fails at the moment it cannot find the cluster node. Please find the logs below:

_Full_Log
2014-08-04 10:45:48 CEST (com.softwareag.wsstack.osgi.axis2.setup.internal.TransportListenerRegistryManager:INFO) - updated(null)
2014-08-04 10:45:48 CEST (com.webMethods.portal.system.impl.BuildVersion:INFO) - MWS BuildVersion: 8.2.1.0.144
2014-08-04 10:45:48 CEST (com.webMethods.portal.system.impl.BuildVersion:INFO) - MWS InstalledVersion: 9.6.0.0000-0164
2014-08-04 10:45:49 CEST (Framework:INFO) - Initializing component: com.webMethods.rtl.util.ObjectUtil
2014-08-04 10:45:49 CEST (Framework:INFO) - Initializing component: com.webMethods.rtl.util.ThreadUtil
2014-08-04 10:45:49 CEST (Framework:INFO) - Initializing component: com.webMethods.rtl.util.FileUtil
2014-08-04 10:45:49 CEST (Framework:INFO) - Initializing component: com.webMethods.rtl.util.SystemPaths
2014-08-04 10:45:49 CEST (Framework:INFO) - Initializing component: com.webMethods.rtl.util.Debug
2014-08-04 10:45:49 CEST (webm.caf:INFO) - My webMethods Server 9.6.0.0000-0164
2014-08-04 10:45:49 CEST (com.webMethods.rtl.util.Debug:INFO) - Started sending JDK log messages to Log4J
2014-08-04 10:45:49 CEST (Framework:INFO) - Initializing component: com.webMethods.rtl.io.FileIOManager
2014-08-04 10:45:49 CEST (Framework:INFO) - Initializing component: com.webMethods.rtl.util.xml.XMLUtil
2014-08-04 10:45:49 CEST (Framework:INFO) - Initializing component: com.webMethods.rtl.util.xml.XSLProcessorFactory
2014-08-04 10:45:49 CEST (Framework:INFO) - Loading phase: [phaseID, phaseName] [miePhaseTwo, miePhaseTwo]
2014-08-04 10:45:49 CEST (Framework:INFO) - Initializing components of: miePhaseTwo
2014-08-04 10:45:49 CEST (Framework:INFO) - Initializing component: com.webMethods.portal.system.boot.StartupManager
2014-08-04 10:45:49 CEST (Framework:INFO) - Current DB component level is 40
2014-08-04 10:45:49 CEST (Framework:INFO) - Initializing component: com.webMethods.portal.system.cluster.impl.ClusterProvider
2014-08-04 10:45:49 CEST (Framework:INFO) - Initializing components of: cluster
2014-08-04 10:45:49 CEST (Framework:INFO) - JMS ClientID: SDGEN002.mws.node.mwsdev.6227127950100431872
2014-08-04 10:45:49 CEST (Framework:INFO) - No registered exception delegate
2014-08-04 10:45:49 CEST (Framework:FATAL) - Caught throwable:
com.webMethods.portal.PortalException: [POP.005.0042] Unable to start. The server name mwsdev could not be found in the cluster definition
at com.webMethods.portal.system.cluster.impl.ClusterProvider.registerLocalClusterNode(ClusterProvider.java:545)
at com.webMethods.portal.system.cluster.impl.ClusterProvider.init(ClusterProvider.java:269)
at com.webMethods.portal.system.init.impl.DefaultPhase.initComponent(DefaultPhase.java:117)
at com.webMethods.portal.system.impl.BaseProvider.initComponents(BaseProvider.java:634)
at com.webMethods.portal.system.impl.BaseProvider.init(BaseProvider.java:170)
at com.webMethods.portal.system.init.impl.DefaultPhase.init(DefaultPhase.java:49)
at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.initComponent(DefaultPhaseProvider.java:266)
at com.webMethods.portal.system.impl.BaseProvider.initComponents(BaseProvider.java:634)
at com.webMethods.portal.system.impl.BaseProvider.init(BaseProvider.java:170)
at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.initializePhases(DefaultPhaseProvider.java:91)
at com.webMethods.portal.system.init.impl.ClusterPhaseProvider.initializePhases(ClusterPhaseProvider.java:78)
at com.webMethods.portal.system.init.impl.PartitionPhaseProvider.initializePhases(PartitionPhaseProvider.java:59)
at com.webMethods.portal.system.PortalSystem.init(PortalSystem.java:920)
at com.webMethods.portal.system.PortalSystem.main(PortalSystem.java:856)
at com.webMethods.portal.system.PortalSystemActivator$1.call(PortalSystemActivator.java:56)
at com.webMethods.portal.system.PortalSystemActivator$1.call(PortalSystemActivator.java:53)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
2014-08-04 10:45:49 CEST (com.softwareag.platform.shutdown.internal.ShutdownAction:INFO) - Starting shutdown of OSGi framework with: poll 1000, timeout 120000

Even though you do not have a cluster, there is still a cluster definition that needs to include the node name of the single MWS instance, which appears to be “mwsdev” from your stack trace.

To see the cluster definition, go to /MWS/bin, and run “./mws.sh getconfig cluster.xml”. After that, the cluster.xml file will be located in /MWS/server//config. Open that file and modify it if necessary.

After modification, save it and update the configuration in the MWS database by going back to /MWS/bin and run “./mws.sh putconfig cluster.xml”. Then go back to the config directory and delete the cluster.xml file or rename it to prevent MWS from continuing to use that file instead of configuration in its database at startup.

Hi pavanven,

Please let me know the link for upgrade guide.

Thanks,
Raj

Pavan, I absolutly agree with rwsalisbury. Follow as he suggested.

Raj: Search in this community, you can find necessary info. Also search in empower site to get the required documentation.

Thanks,