microsoft / vsts-ibm-websphere-extension

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

Unable to install on WebSphere Cluster #11

Closed bayernmunich closed 6 years ago

bayernmunich commented 6 years ago

I am getting "javax.management.MalformedObjectNameException: Invalid character ':' in value part of property"

task capture ibm

yacaovsnc commented 6 years ago

Can you please set "System.Debug" to true, rerun the job and attach the log here?

Also have you tried to manually deploy with wsadmin command and does it fail the same way? This task is only a wrapper around the tool. It would be easiest if we can get the manual command working and then try to mimic that from the task.

bayernmunich commented 6 years ago

thanks for the replay. As you said to set "System.Debug" to true . Attached logs for the same. ReleaseLogs.zip

yacaovsnc commented 6 years ago

The value set in Target Cluster is fishy. Shouldn't it be "FrameWorkCluster"? I don't know your cluster name, so I hope I guessed it right.

bayernmunich commented 6 years ago

thanks for the replay. As per your suggestion we have updated cluster details at attached in screenshot. updated cluster details We have got different error as attached in the logs tasklog_3.log updated cluster details

. websphere

Please find our websphere server details attached.

Kindly help. Let us know for any details.

yacaovsnc commented 6 years ago

Please try setting the "Target Cluster" field to FrameWorkCluster and rerun. The log still shows there is an error in arguments and it failed to parse it.

bayernmunich commented 6 years ago

thanks for the replay. Tried setting "Target Cluster" field to FrameWorkCluster as updated in Scrrenshot. build and release Updated logs for the same. release_update.log

yacaovsnc commented 6 years ago

Great, we made progress! Now the syntax issue is gone and the error message is actually meaningful:

_com.ibm.ws.scripting.ScriptingException: WASX7111E: Cannot find a match for supplied option: "[WEB-INF/web.xml, validationservice_vsts.war,WEB-INF/web.xml, default_host]" for task "MapWebModToVH". The supplied option must match with the existing task data in the application and the existing task data are: "[validationservice_vsts.war validationservice_vsts.war,WEB-INF/web.xml]"_

You can actually leave "Context Root for Web Modules" and "Web Module" empty. This way wsadmin will attempt to automatically find the correct value. So please remove those two fields and try again?

bayernmunich commented 6 years ago

thanks for the replay! As you mentioned I left blank "Context Root for Web Modules" and "Web Module" still facing issue. Updated Screenshot and log for the same. release_sc Websphere.log

yacaovsnc commented 6 years ago

It seems the web module we extracted has a "/r" at the end and it doesn't match the existing configuration. Probably due to line ending difference on different OSes.

What was auto-configured: _[["validationservice_vsts.war\r" "validationservice_vsts.war,WEB-INF/web.xml" "default_host"]] -contextroot /validationservice_vstswar ]')

What was expected: "MapWebModToVH". The supplied option must match with the existing task data in the application and the existing task data are: _"[validationservice_vsts.war validationservicevsts.war,WEB-INF/web.xml] "

The format of this arg is: [["${webModule}" "${uri}" "${virtualHost}"]]

So please try set the webModule field to validationservice_vsts.war, and try again?

bayernmunich commented 6 years ago

Thank you so much for your continuous support. Issue is resolved and deployment is successful. Cheers!!!!!!!!!!! :hand: :beers: :beers: :guitar: