RAFW partial deployment
![](http://jazz.net/_images/myphoto/884530b676ad33ebbc733822542b8414.jpg)
Hello,
I am facing the automation of partial deployment of an application. For RAFW v7.1.1.4, for was_common_deploy_update_app I have seen that the WAS actions coded in updateApp.py within "actions" folder are:
AdminApp.update 'file'
and
AdminApp.update 'moduelfile'
However, IT department is used of managing this operation by getting a zip file from development in a manner as:
AdminApp.update 'partialapp'
Is there a way of emulating this behavior for current actions? Should we write our own custom action to perform this operation with RAFW?
Thanks in advance for your help.
Regards,
Jorge.
I am facing the automation of partial deployment of an application. For RAFW v7.1.1.4, for was_common_deploy_update_app I have seen that the WAS actions coded in updateApp.py within "actions" folder are:
AdminApp.update 'file'
and
AdminApp.update 'moduelfile'
However, IT department is used of managing this operation by getting a zip file from development in a manner as:
AdminApp.update 'partialapp'
Is there a way of emulating this behavior for current actions? Should we write our own custom action to perform this operation with RAFW?
Thanks in advance for your help.
Regards,
Jorge.
3 answers
![](http://jazz.net/_images/myphoto/884530b676ad33ebbc733822542b8414.jpg)
Hi David,
thanks for posting. This question is pretty old though and I finally developed a custom action for that based on the existing tasks. My custom actions gathers a zip file referenced in the properties (I use a new parameter called "ZIP_FILE"), and calls the addupdate operation for wasadmin AdminApp update.
Jorge.
thanks for posting. This question is pretty old though and I finally developed a custom action for that based on the existing tasks. My custom actions gathers a zip file referenced in the properties (I use a new parameter called "ZIP_FILE"), and calls the addupdate operation for wasadmin AdminApp update.
Jorge.