Hi Ray,
I wouldn’t mind even using the manual interface with VSS that you’re describing. I don’t need fancy integration with the tool. (I’d almost prefer NOT to have it, because it tends to mask essential details.)
My problem is more fundamental than that: what are the artifacts that I’d check into VSS? Where do they live? How are they generated?
I’m missing this point because our wM TN/Developer run on a Unix server in our data center. I only access that machine via the TN/Developer clients, so I don’t ever see the server directory structure.
Obviously I have a C:\Program Files\webMethods6\ directory on my desktop for the client. Under that I have the usual suspects: Developer, TNConsole, Modeler, and jvm.
If I bring up Developer, I can go to File->Export and put out a WinZip file for a package on my client. Is that what you’re checking into VSS? I guess it allows me versioning and labeling, which is good. Better than not having a safety net at all!
And now if I made a total mess of a package and wanted to start fresh with my last archived version, I’d check the ZIP file out of VSS, delete the package in Developer, and then use File->Reload Package?
First I tried idea with a new folder that I added to my current project package. I put a service in it, exported the ZIP file, and then tried to delete the folder. Developer wouldn’t let me until I deleted the service I’d put under it. Once I had deleted the folder I went back to the File menu to try and reload the ZIP file, but the Reload Package option was grayed out. Is this only pertinent at the package level?
Next I tried it with a new package. I added a folder and a simple service, exported to a ZIP file, then deleted the package. Reload Package is not asking me for the location of the ZIP file. It’s doing something else that I’m ignorant of.
I don’t see how to get the contents of the ZIP file back into Developer. What am I missing?
I agree with your comments about archiving Java services. It’s not just about having a backup copy, IMO. It’s the usual development cycle where you’d like to maintain a labeled history of your code.
Thank you, as always, for sharing your experience. Sincerely, MOD