WS3Converter.jar returns java.lang.NoClassDefFoundError
search cancel

WS3Converter.jar returns java.lang.NoClassDefFoundError


Article ID: 233449


Updated On:


CA Automic Workload Automation - Automation Engine


When migrating websoap object from version 3.2 to 4.6, the following error is returned.:

[automic@server bin]$ java -jar WS3Converter.jar2022-01-17 12:21:31,069 main ERROR Invalid status level specified: WARM. Defaulting to ERROR.*****************************************************  Automic Webservice Object Migration Tool  *****************************************************12:21:31.183 [main] INFO  ws3.converter.Main - Trying to open and parse XML file: ./../conf/uc4config.xml12:21:31.187 [main] INFO  ws3.converter.Main - Trying to open and parse XML file: ./../conf/migrationconfig.xml12:21:31.188 [main] INFO  ws3.converter.Main - Trying to open and parse XML file: ./../conf/login_dat.xmlPlease enter the password for 100/USER/DEPT:12:21:38.458 [main] WARN  ws3.converter.Main - CmdConfigData [migrationConfig=./../conf/migrationconfig.xml, uc4config=./../conf/uc4config.xml, loginData=./../conf/login_dat.xml]12:21:38.458 [main] WARN  ws3.converter.Main - ConfigurationProvider [configfiles=CmdConfigData [migrationConfig=./../conf/migrationconfig.xml, uc4config=./../conf/uc4config.xml, loginData=./../conf/login_dat.xml], host=localhost, port=2217, system=AUTOMIC, client=100, name=USER, department=DEPT, password=*************, language=E, endOfObjName=.WS4, wS3ObjectsPatterns=[*], overwriting=false, ws4Agent=RA_SOAP01]Exception in thread "main" java.lang.NoClassDefFoundError: com/uc4/communication/Connection        at ws3.converter.Main.createConnection(        at ws3.converter.Main.main( by: java.lang.ClassNotFoundException: com.uc4.communication.Connection        at        at java.lang.ClassLoader.loadClass(        at sun.misc.Launcher$AppClassLoader.loadClass(        at java.lang.ClassLoader.loadClass(        ... 2 more

Specifying the job in  <convertWS3Objects> tag in migrationconfig.xml and making sure that the proper connection is used for uc4onfig.xml does not fix this issue. 


Release : 12.3



This seems to be an issue with the soap migration tool on 4.6.1. In the meantime, as a workaround, use the migration tool bundled with the RA.SOAP 4.5.3 or older version.