I'm having difficulty getting wasexport to work on z/OS,either standalone using the scripts or headless via the VCE ant build scripts (automation-example.xml).
It gets a NullPointerException trying to read the WAS 5.1 BASE.product xml file, which is available and readable on the file system. (note: I deleted part of the path from the output below):
Version and example log output below:
VCE Version: Visual Configuration Explorer (Tech Preview) v22.214.171.124811041219
WAS Version: W510224 (z/OS)
JVM: J2RE 1.4.2 IBM z/OS Persistent Reusable VM build cm142ifx-20070813 (SR9a) (JIT enabled: jitc)
Writing script with encoding Cp1047
Temporary files deleted from <path deleted>/vce/wasexporter/temp/2f9405e5
Total elapsed time = 7 seconds
Parsing <path deleted>/WebSphere/nodes/node1/DeploymentManager/properties/version/BASE.product
Terminating abnormally due to severe error.
Total memory: 67303936
Maximum memory: 268435456
Free memory: 60132408
at com.ibm.topology.websphere.provider.WebSphereVersionHelperV5.processProductFile(Unknown Source)
at com.ibm.topology.websphere.provider.WebSphereVersionHelperV5.preInitialization(Unknown Source)
at com.ibm.topology.websphere.provider.WebSphereConfigExporter.initLocalConfigService(Unknown Source)
at com.ibm.topology.websphere.provider.WebSphereConfigExporter.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
<path deleted>/vce/wasexporter/temp/properties deleted.
Re: wasexport on z/OS fails.2009-02-03T21:48:05ZThis is the accepted answer. This is the accepted answer.Neil,
Can you please send me the files in your <path deleted>/WebSphere/nodes/node1/DeploymentManager/properties/version directory? You may email them to firstname.lastname@example.org.
Re: wasexport on z/OS fails.2009-02-10T19:59:19ZThis is the accepted answer. This is the accepted answer.Neil,
Please find attached a new wasexporter.jar file. Replace the like-named file in the vce\wasexporter directory of your target system. This should take care of the NPE, but I'll need you to send me the output if you can. I have to check to make sure that it's picking up the node version metadata correctly.
Re: wasexport on z/OS fails.2009-02-11T13:12:16ZThis is the accepted answer. This is the accepted answer.There's an issue with the second invocation of ConfigService. For some reason, it's not recognizing the properties pointing it to the correct config location. I've attached another wasexporter module to try out. Unfortuneately, we'll have to attack this as trial and error because this issue seems to be unique to the system you are using.
FuBarre 060000P7XJ3 Posts
Re: wasexport on z/OS fails.2009-02-11T17:10:55ZThis is the accepted answer. This is the accepted answer.With Bobs help, the extract is working with the last version of the .jar he posted.
Thank you very much! You've been extremely helpful (and patient!)