Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Action 'was_common_deploy_install_app' does not exist in the specified scope

Friends,

I'm new to Build Forge/RAF, and I'm trying to deploy a sample app using the command line options for raf.  
version 3.0.0.4

Steps used to reproduce my issue
  1. Performance env gen against target system successfully.  Target system is WAS ND configuration with one cluster with one server in it.
  2. added new {scope}/app/properties file  <portlet.properties>
  3. added new app file {scope}/app/media <portlet.ear>
  4. scope={rafw_home}/user/environments/<stuff>/cells/<stuffcell>
  5. {rafw_home}/bin/rafw.sh -env STUFF-TEST-ENV -cell <stuff> -node <stuff> -cluster <stuff> -execute was_common_deploy_install_app -a portlet.ear
After running Step 5 from the RAF server I get the following error:
/core.xml:158: The following error occurred while executing this line:
/product/lib/RAFW_lib_shared.xml:62: Action 'was_common_deploy_install_app' does not exist in the specified scope.

Any suggestions on how to resolve this issue?

0 votes


Accepted answer

Permanent link
 I believe that you need to change the step 5 command to be:
{rafw_home}/bin/rafw.sh -env STUFF-TEST-ENV -cell <stuff> -cluster <stuff> -execute was_common_deploy_install_app -a portlet.ear
Gerald Gordon selected this answer as the correct answer

0 votes

Comments

Thank you very much David!  I also  removed the .ear from the app name after the -a switch.


Kind regards, 

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 12,034

Question asked: Oct 17 '12, 4:23 p.m.

Question was seen: 4,618 times

Last updated: Oct 17 '12, 9:38 p.m.

Confirmation Cancel Confirm