Is it possible to know when this plugin will be available? We want to use Hudson to make some WAS deployment (WAS 6.1) and it will be useful for us.

Antony

I have this plugin installed on the latest hudson release on linux.

I have Websphere 6.1.0.21 installed locally as well.

I would like to deploy to a remote websphere instance also running Websphere 6.1.0.21.

I setup a WAS installation and WAS server, but I don't see where I configure the step in my Hudson Job. It is a Maven 2 job, can I only add the step in a freestyle project?

Now, the tough question, I need to auto deploy to a remote server, any details on what should be in the Websphere step in my job to do that? I guess I need to Update the application, save everything, and restart the application server.

Any help is greatly appreciated.

Regards,
Paul

Is there any way to run the wsadmin.sh script using sudo on unix?

Hi ,

My requirement is to deploy the application in Websphere Cluster environment , so following are the steps i followed in ant build file which i call in Hudson job 

1. checkout code from CVS

2. run a CMD file for building the application ear file , using wesphere python script .

3. finally , restarting the manager and nodes

 which seems to be a hectic job

how can i configure the WEBSPHERE - Cluster setup into Hudson using WAS-Plugin ,  and add pre-setup and post-setup  steps which will run

my python script  and publish the deployment details.

Thanks & Regards ,

Kirthish Kulkarni.

Romain,

Thanks for building the plug-in. It works great but I'm having a small issue. When a deployment fails, it still says the build is successful. Is there something I can do to pass the value back to Hudson? When I run wsadmin outside of the plugin see that the %ERRORLEVEL% parameter is > 0 (105 to exact) when it exits on error. But the plugin must be preventing Hudson from recognizing the error code of the wsadmin.bat program. I could use the windows batch command build option but the plugin makes everything much easier to setup and read and also the plugin hides the password to the server. That is a huge plus.

Thanks in advance for the help.

I wrote short post about my experience setting up CI infrastructure based on Jenkins, using this plugin to deploy remotely between different WAS8 environments. The post can be found here. 

Hi,

We have a doubt as WAS Think Client integration with WAS Server. Our system have a machine with jenkins (with WAS builder plugin) and a lot of remote WAS. The WAS Think client versión is 7.0.0.12 (instaled in Jenkins machine) and we want deploy aplications in WAS servers with other versions like 7.0.0.13, 7.0.0.14. ¿Is this a problem? ¿Have one experience about it?

And the second, in all the WAS we have a security enabled, ¿Could be a problem?

Thanks a lot,

AtEnfe

I have a situation where I need the username and password defined at the server level available to use inside of a wsadmin script.  This will be used to configure LDAP security.  Is there a way that these can be externalized so they are available inside of a admin script and hopefully keep them secure?

Is it possible to pass a variable as "Was Server" instead of selecting it from a combo at the build step level? This is useful in case of parametrized builds.

If it is not possible, could I ask for that feature?

Is it possible to use a WebSphere installation that has spaces in the path? Mine is installed under C:\Program Files and I want to invoke a python script via wsadmin.bat.

Here is the Jenkins console output:

Using user admin defined at the server level
$ C:\Program Files\IBM\WebSphere\AppServer\bin\wsadmin.bat -conntype SOAP -host {IP address here} -port 9044 -user admin -password ******** -lang jython -f "{path to the script}\install_to_websphere.py"
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
Build step 'IBM WebSphere Application Server 6.x/7.x' marked build as failure

I tried putting quotation marks, either single or double, around the path in the main Jenkins configuration. Doesn't work, the configuration complains it's not a folder and the build step won't even start. Is there any other way to make it work despite the spaces?

Is there a timeline of when version 2.0 will be released?  I am really interested in the Message Broker support.

How do you get this to work??

My WAS is located on my remote windows server and Jenkins is on Linux.  I don't understand the part were it says the "Installation directory"  the wsadmin file would be located on my remote WAS under the /bin directory... so what exactly would i put in "Installation directory" field ??   I just want to run a jacl script that needs to execute the "wsadmin" command that is located on the windows server that will replace my .ear file after my build deployment is complete. Thank you for your help.

Hello.

Can you put in some lines about how to make it work with administration thin client?

We are trying to achieve the following:

We need to automatically deploy one ear from jenkins to a remote WAS installation but we cannot afford ( well, people won`t let us) install a full instance of WAS.

After we have installed the plugin, we need to create a WAS instance on jenkins in order to use WAS builder plugin, but we do not have one.

I can see that you have support for administration thin clients but I am not sure how the path should look like so it can be recognised as a WAS instance.

Can you help me with that?

Also, the user name and password which needs to be provided on the plugin configuration panel should it have a deployer role on the remote WAS instance? Or should it be an user that connects locally to the administration thin client?

Very much appreciated.

Thanks,

Ioana.

Hello. 

I can see that you attached the thin client bat file. It`s very much appreciated. I did manage to setup the plugin and query some stuff remotely on the WAS instance. What I wasn`t able to do though was to actually deploy an ear, which was in fact my target.The thin client is on a Windows machine while WAS is installed on Aix and I get this error while using AdminApp.install: 

ADMA0043E:
C:\Temp\app23320.ear does not exist for installation.

I assume that it tries to transfer the ear file to the remote machine and it is looking for the ear in a temporary folder on a windows machine, but the remote machine is  an AIX. I`ve googled around, the only information I could find is that this might happen if I have WAS 5.1, that does not support the transfer,which is not the case or the 2 machines,the one with the thin client and the remote one run on different OS, which is my case but seems ridiculous to have that constraint. 

Do you happen to know anything about it? I would really appreciate it. I know there are other ways of doing it, but some other methods require wasadmin password or having a root user on the remote machine, which we`re not allowed to have. 

Thanks a lot for answering to my comment. 

Cheers, 

Ioana C.