A while back, one of the guys I worked with wrote an external java program that used the client.jar API to install, publish or backup packages.
The code had a props file that contained server data needed for the transaction (host, port, username, password, directories for backup, etc.) It also required a list of packages (to action against).
There is another easier way to accomplish this: You can write a flow service that wraps a call to pub.packages:installPackage. The flow could contain a loop for multiple iterations. It will require that the packages are in replicate/inbound directory.
A word of caution to you: No matter what you decide to do, always back up your server packages prior to installing any packages in case you make a mistake and overwrite existing code with OLDER code. This would occur in cases where you have worked on code, and an earlier package version resides in the replicate/inbound directory.
HTH
Ray
#webMethods-Archive#webMethods#Integration-Server-and-ESB