microsoft / vsts-ibm-websphere-extension

VSTS Extension to integrate with IBM WebSphere Application Server
Other
8 stars 16 forks source link

Not found wsadmin: null #4

Closed perbellinie closed 7 years ago

perbellinie commented 7 years ago

Hi, I'm using the plugin but you get the following error: 2017-05-29T13:57:29.5748039Z ##[debug]check path : null 2017-05-29T13:57:29.5904296Z ##[debug]task result: Failed 2017-05-29T13:57:29.6060553Z ##[error]Error: Failed which: Not found wsadmin: null 2017-05-29T13:57:29.6060553Z ##[debug]Processed: ##vso[task.issue type=error;]Error: Failed which: Not found wsadmin: null 2017-05-29T13:57:29.6060553Z ##[debug]Processed: ##vso[task.complete result=Failed;]Error: Failed which: Not found wsadmin: null

The server where the plugin is running is different from the deployer and therefore did not install the wsadmin command.

yacaovsnc commented 7 years ago

Per the prerequisite section in the readme:

You can run wsadmin.sh(Linux) / wsadmin.bat(Windows) command from the terminal or command line respectively. Make sure IBM WebSphere bin/ directory is in the PATH.

You need to install "wsadmin" on the deployer node as well.

karthikeyanchinnarasu commented 5 years ago

We are facing same issue while deoyment. How to fix? Where need to be install wsadmin. Can you plz provide the steps for that?

yacaovsnc commented 5 years ago

@karthikeyanchinnarasu on the agent node you need to have wsadmin installed. This is a IBM tool and comes with your WebSphere installation. You need to follow IBM's documents to install that.

abhijit-dey5 commented 5 years ago

Hi All, I am also having same issue. My agent is having websphere installed in it and we are trying to deploy an application on the agent itself. So, technically the agent and the target server both have websphere and wsadmin installed. But even after that, I am facing this issue