Using maven style artifacts for deployment with RAF 3.0.0.4
![]()
Friends,
I'm trying to accomplish automated deployments of maven artifacts using RAF.
We have three ways to access maven artifacts for deployment in our environment.
Here is my problem. Most of my developers create maven style application files for deployment such as component>-1-2-3.ear/.war file. I think there should be a better way for me to deploy this application without having to update the 1-2-3 portion /apps/properties/<component>-1-2-3.properties or /apps/media/<component>-1-2-3.ear/.war application file every time I need to deploy a new version of the application file using a RAF job on an imported environment.
How can I create a template with these requests to deploy war files that generally have the same prefix but different suffixes for file names? Using RAF I would like a good way to back up the existing war/ear files before deployment of a new application file.
Process I know today:
1. Generate Env using RAF tool.
2. Use RAF eclipse client to import exiting application file from Portal/WAS environment.
3. Update /apps/media and /apps/properties with the appropriate information for each application file <component>1-2-3.properties and corresponding <component>1-2-3.ear/.war.
4. Run execute from RAF eclipse client once. Then I can run this job from RAF web ui as needed.
I'm trying to avoid creating a script to build a .properties file for every application file that has a different suffix (1-2-3.ear/.war) when I need to deploy an application.
Please let me know if we have a solution to this already. Is there some sort of Pre/Suffix parameters that RAF 3.0.0.4 understands, in order for me to deploy subsequent maven style app files?
Thanks,
|
3 answers
![]()
Hi Gerald, did you find any solution for this problem ??
|
![]()
Hi Ketil,
I built a program on top of the RAF tool that dynamically creates the properties files needed to support maven style artifacts This ended up being a better solution because we have many different cluster and single node configurations that vary based on the application being deployed.
|
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.