Last week, we had the author of TDD for a Shopping Website LiveProject. Friday at 11am Ranch time, Steven Solomon will be hosting a live TDD session just for us. See for the agenda and registration link
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Frits Walraven
Bartenders:
  • Piet Souris
  • Himai Minh

Problem deploying apps to WebSphere Deployment Manager

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have been trying to deploy an application to the deployment manager. The reasons are complex, and I realize that the WebSphere Admin console does not support this directly. I've managed to get it working using wsadmin scripting interface.
However, now I'm running into a problem. In order to get it working I had to add an HTTP Transport to the dmgr to match the default_host virtual host. This seems to allow my application to function, however, it seems to cause a problem with the "filetransfer" application that comes installed on the deployment manager. The file transfer client seems to be trying to connect to the new HTTP Transport and expects the FileTransfer app to be listening there, which of course it's not.
A number of critical functions (e.g., installing apps and adding new nodes to the cell) require the use of the filetransfer application, so this problem is pretty serious.
Has anyone else tried to do this? Have any of you experienced the same problem?
Thanks,
Geoff
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I can't imagine anyone else would try this. This is (as you've found out) a really, really bad idea. I would like to know some of the reasons why you think you need to do this. What could you be doing that you couldn't accomplish by installing your apps on some other server and then making JMX calls into the deployment manager?
Kyle
 
Geoff Hardy
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Kyle Brown:
I can't imagine anyone else would try this. This is (as you've found out) a really, really bad idea. I would like to know some of the reasons why you think you need to do this. What could you be doing that you couldn't accomplish by installing your apps on some other server and then making JMX calls into the deployment manager?

Kyle



Sorry I waited so long to reply. I'm back to working on this issue, and I'm willing to try making remote calls to the deployment manager. Do you know whether it's possible to forward credentials when using admin APIs. My application consists of a web service, which is authenticated using basic auth. This web service then makes calls to the AdminService (will change to use AdminClient), ConfigService, and AppManagement APIs. If I'm doing this remotely in a secure environment, what's the best way to forward the credentials to the deployment manager via these APIs? It would be unfortunate if I had to pass the user name and password as parameters to the web service. The WebSphere docs claim that when using LPTA, credentials are forwardable. Does this apply to the admin APIs?

Thanks,
Geoff
 
Kyle Brown
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes, so long as the other server is in the same cell, credentials will be automatically forwarded if you set things up correctly. If you use the RMI connector for SOAP for your admin calls from JMX then you shouldn't need any other setup for security -- the credentials should be passed on the RMI/IIOP security context automatically. SOAP would be more complicated to secure -- I'll have to check on that one.

Kyle
 
Pay attention! Tiny ad!
Free, earth friendly heat - from the CodeRanch trailboss
https://www.kickstarter.com/projects/paulwheaton/free-heat
reply
    Bookmark Topic Watch Topic
  • New Topic