We are starting refactoring a web method project and the current project is not using any version control system.
I’m looking for a reference document on how to set up the code repository (SVN) fro webMethods using best practices.
We already have the repository hooked up to our dev environment, we are just looking for good practices on the structure of the repo.
We want to have the trunk as a reflection of the current prod and multiple development lines.
The repository should also allow us to set up continuous integration as a next step.
I know this question is quite open but If someone has some recommendations, that would help us a lot!
When you are on one of the recent versions you might want to explore Local Service Development, by which Designer is able to check in the code to Subversion by using Eclipse plugins.
You can choose between Subclipse and Subversive.
Hi Holger, we are currently on 6.5 and we are migrating to 9.9 with 2 steps: 8.5 and 9.2
We are planning to have 4 dev branch, 6.5, 8.5, 9.2, 9.9 and create tag (ex 9.2.1.0 VMVersion/code) on the trunk each time we have a new production ready version.
I think you have mixed up the versions:
Instead of wM 8.5 and 9.2 it should be 8.2 and 9.5.
Migration path sounds reasonable so far.
You might want to check if migrating to 9.10 or 9.12 might be an option instead of migrating to 9.9.
Please make sure to read the Upgrade documentations for each version carefully as there are several pitfalls.
Taking a look at the different Build-In-Services Guides might be helpful as well to check for deprecated services etc.
