It's all about the answers!

Ask a question

RAFW issue when deploying ear with more than one .war files


Antonio Bonanni (1111717) | asked Sep 03 '10, 8:02 a.m.
Hi all,

i'm having a strange issue with RAFW (7.1.1.4) deploy on Websphere 7.0: i deploy correctly an ear application file with a single module with no problems. When i try to deploy the last one ( that contains multiple modules ) i receive the following error ( from buildforge logs ):

call_wsadmin:
09/03/10 05:51AM EXEC WASX7209I: Connected to process "dmgr" on node DmgrTest01 using SOAP connector; The type of process is: DeploymentManager
09/03/10 05:51AM EXEC WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: ""
09/03/10 05:51AM EXEC OPTIONS is defined in /opt/RAFW/user/environments/Test01_07/cells/Test01_07/apps/properties/XXXXX.properties
09/03/10 05:51AM EXEC Updating XXXXX ...
09/03/10 05:51AM EXEC WASX7017E: Exception received while running file "/opt/RAFW/product/actions/deploy/was/common/scripts/installApp.py"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7111E: Cannot find a match for supplied option: "" for task "MapModulesToServers"
09/03/10 05:51AM EXEC
09/03/10 05:51AM EXEC
09/03/10 05:51AM EXEC prepare_shell:
09/03/10 05:51AM EXEC
09/03/10 05:51AM EXEC change_directory_ownership:
09/03/10 05:51AM EXEC Current user is the OS_USER: /opt/RAFW/logs/Test01_07/cells/Test01_07/clusters/C_XXX ownership will not be modified.
09/03/10 05:51AM EXEC
09/03/10 05:51AM EXEC prepare_shell:
09/03/10 05:51AM EXEC
09/03/10 05:51AM EXEC change_directory_ownership:
09/03/10 05:51AM EXEC Current user is the OS_USER: /opt/RAFW/work/Test01_07/cells/Test01_07/clusters/C_XXX ownership will not be modified.
09/03/10 05:51AM EXEC Computing list of files to transfer back to the framework server
09/03/10 05:51AM EXEC
09/03/10 05:51AM EXEC BUILD FAILED
09/03/10 05:51AM EXEC /opt/RAFW/product/lib/RAFW_lib.xml:167: The following error occurred while executing this line:
09/03/10 05:51AM EXEC /opt/RAFW/product/actions/deploy/was/common/deploy_was_applications.xml:125: The following error occurred while executing this line:
09/03/10 05:51AM EXEC /opt/RAFW/product/lib/jython/ant_jythonLib.xml:190: exec returned: 105
09/03/10 05:51AM EXEC
09/03/10 05:51AM EXEC Total time: 1 minute 1 second
09/03/10 05:51AM EXEC Relative Path: logs/Test01_07/cells/Test01_07/clusters/C_XXX
09/03/10 05:51AM EXEC get: was_common_deploy_install_app.log
09/03/10 05:51AM EXEC end
09/03/10 05:51AM RESULT 1 (1)

We tried to work on deploy options for rafw ( we get this options when we've deployed the application first time ) checking for trailing or special characters or syntax errors with no success.

Has anyone experienced this issue ?

Solutions or workaround ?

Thanks

2 answers



permanent link
Ronald Signorino (3154) | answered Oct 27 '10, 8:10 p.m.
WASX7111E: Cannot find a match for supplied option: "" for task "MapModulesToServers"


When I get this error, I use the Admin Console to install the .ear with the associated module and vhost mappings for each .war. Then on the Summary Page (before actually installing), I use the link in the right hand pane to show the equivalent scripting commands. I compare that result with the options I specified in the .properties file that I supplied to RAFW for that same .ear.

I have used RAFW to deploy as many as 5 .war files within one .ear. Using the Admin Console to get the correct config of the options is very useful, especially with .ears supplied with third party products.

Hope this helps

permanent link
Timothy Robertson (216143) | answered Oct 28 '10, 4:10 p.m.
The suggestion above is a very good one. Sure seems like you don't have the -MapModulesToServers option defined. Depending on the format of the file you are using to deploy the application with RAFW this will be another option added to the big OPTIONS= property or if you're using the split options format
options.multi.MapModulesToServers=,]

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.