Best practice for calling OpenDeploy from TeamSite Workflow Java CGI task

TeamSite 6.5 SP1
OpenDeploy 6.1

We have all Java based cgi tasks within a workflow, including calling OpenDeploy and passing some files. Does it make sense to make a web services call via Java to run the deployment instead of making a Java Runtime() call?

I have not really played around with the web services too much, but it was an intriguing thought I had. I think the complexity (especially around authentication) may outweigh the benefits, but am not totally sure.

Any opinions?

Find more posts tagged with

Comments

Migrateduser

So how are you doing this now... sounds like you've written your own procedure to remotely invoke OD? I assume this in not all running on the same box.

Webservices is certainly a viable option. If you look into that, the readme files that ship with the installation, have the bulk of the info.

Mariam

Migrateduser

TeamSite 6.5 SP1
OpenDeploy 6.1

We have all Java based cgi tasks within a workflow, including calling OpenDeploy and passing some files. Does it make sense to make a web services call via Java to run the deployment instead of making a Java Runtime() call?

I have not really played around with the web services too much, but it was an intriguing thought I had. I think the complexity (especially around authentication) may outweigh the benefits, but am not totally sure.

Any opinions?

In my opinion web service call it a overhead, if you want to use the OD API why not use the java native interface insted of the web service call, as the cgi script is running on TeamSite and OpenDeploy server.

Bill Klish

The java code and OD server are all running on the same box as the teamsite server. As far as I know the only way to execute the deployment is by having a java runtime process exec(iwodcmd start mydeploy).

So, it sounds like the deployment java wrapper classes I wrote are the best way to go. Unless I am missing something.