The command below generates .ear with the clean version without the patch and without the customizations.
./customizeACM.sh -i /tmp/aveksa/staging,/tmp/repackaged_ear_dir
There is another command that generates a .ear with patch or customizations.?
In short I need to generate a new .ear with the updated version that is deployed.
I don't really understand your question. The deployed ear file is by definition the ear file that is deployed.
This command (without a path) extracts the contents of the deployed ear file into a temporary directory.
customizeACM.sh -c
Hi Ian
What I need to know is
How do I generate a new .ear from the deployed file so I can do customizations.
Hello Rodrigo
If the question is how to customized currently deployed EAR (add contents in it) and rebuild customized EAR.
Here are steps if that's what you are looking for.
customizeACM.sh script allows you to conveniently extract an aveksa.ear and rebuild customized EAR
- Go to /home/oracle/deploy.
- Run the customizeACM.sh script to extract the .ear file:
customizeACM.sh -c <path to the ear file>
The contents of the .ear are extracted to a directory
location: /tmp/customizeACM/.
[Note: If you do not specify the path to the .ear file, the script prompts you to use the currently deployed
.ear file. If you want to use the currently deployed .ear, enter yes. If you do not want to use the currently
deployed .ear, enter no . But i believe you using currently deployed EAR]
- Go to /tmp/customizeACM/ and modify the extracted files.
- When you finish modifying the files, run the customizeACM.sh script again to rebuild the .ear file.
From /home/oracle/deploy, execute command :
customizeACM.sh -d
That rebuilt and Deploys the new customized .ear file.
Many thanks,
Rakhee
Hi Rakhee Tarar
Thanks for the answer
I apologize for my English
It's not my main language
This is almost what I need ..
The customizeACM.sh -c command will use the .ear defined in the wildfly_deployment.properties file within the /home/oracle/archive/ folder.
The problem:
If I apply a patch patch to IGL (example P02) and use the customizeACM.sh -c command it will use an .ear that does not contain the applied patch.
I have noticed that from time to time IGL creates an updated .ear within /home/oracle/ rchive/, but I want to force this creation.
customizeACM.sh -c without any filename parameter is what you want. By default it prompts you to select the current ear. It even verifies the name of the ear file it will be using.
acm-711:/home/oracle/deploy # ./customizeACM.sh -c
You have not specified an archive ear file to customize.
The current ear file deployed to Wildlfy is stored at: /home/oracle/archive/aveksa_7.1.1_161195_P02-2019-Sep-19-16.18.ear
Do you want to customize that archived ear file [yes/no]?
If this command does not explode the ear file containing the current patch, then my guess is that the current patch was not actually applied successfully?
Hello Rodrigo,
No problem :)
Regarding your below question
"If I apply a patch to IGL (example P02) and use the customizeACM.sh -c command it will use an .ear
that does not contain the applied patch."
- All the EARs will be stored in /home/oracle/archive
now if the latest/current EAR is P02 EAR and you run customzeACM.sh -c it will pick that latest EAR only
Example below :
-Here I have aveksa_7.1.1_161195-2019-Mar-18-13.31.ear (7.1.1 EAR ) and aveksa_7.1.1_161195_P01-2019-Dec-20-14.19.ear (7.1.1 P1 EAR )
acm->:/home/oracle/Aveksa_7.1.1_P01/logs # cd /home/oracle/archive/
acm->:/home/oracle/archive # ls -l
total 1971764
-rw-r--r-- 1 oracle oinstall 552 Mar 18 2019 Archive_README.txt
-rw-r--r-- 1 oracle oinstall 159 Mar 18 2019 DO_NOT_REMOVE_ARCHIVE_FILES.txt
-rw-rw---- 1 oracle oinstall 1012144645 Mar 18 2019 aveksa_7.1.1_161195-2019-Mar-18-13.31.ear
-rw-rw---- 1 oracle oinstall 1006918058 Dec 20 14:22 aveksa_7.1.1_161195_P01-2019-Dec-20-14.19.ear
-rw-rw---- 1 oracle oinstall 131 Dec 20 14:27 wildfly_deployment.properties
- Now run ./customizeACM.sh -c
it shows that current ear file is 7.1.1 P1 EAR and it picked that
acm->:/home/oracle/archive # cd /home/oracle/deploy/
acm->:/home/oracle/deploy # ./customizeACM.sh -c
You have not specified an archive ear file to customize.
The current ear file deployed to Wildlfy is stored at: /home/oracle/archive/aveksa_7.1.1_161195_P01-2019-Dec-20-14.19.ear
Do you want to customize that archived ear file [yes/no]?
- Secondly , I believe customization should’ve been taken care of by running “patch.sh” script
what i mean that , we have customization stuff in existing EAR (Ver) and now we applied patch on top of that ver.
i believe the patch.sh script take care of it as you see when we run patch.sh it does repacking, underplaying/deploying new customized ear. (unless you want to add more contents after)
Many Thanks,
Rakhee
Hello Rodrigo,
No problem :)
Regarding your below question
"If I apply a patch to IGL (example P02) and use the customizeACM.sh -c command it will use an .ear
that does not contain the applied patch."
- All the EARs will be stored in /home/oracle/archive
now if the latest/current EAR is P02 EAR and you run customzeACM.sh -c it will pick that latest EAR only
Example below :
-Here I have aveksa_7.1.1_161195-2019-Mar-18-13.31.ear (7.1.1 EAR ) and aveksa_7.1.1_161195_P01-2019-Dec-20-14.19.ear (7.1.1 P1 EAR )
acm->:/home/oracle/Aveksa_7.1.1_P01/logs # cd /home/oracle/archive/
acm->:/home/oracle/archive # ls -l
total 1971764
-rw-r--r-- 1 oracle oinstall 552 Mar 18 2019 Archive_README.txt
-rw-r--r-- 1 oracle oinstall 159 Mar 18 2019 DO_NOT_REMOVE_ARCHIVE_FILES.txt
-rw-rw---- 1 oracle oinstall 1012144645 Mar 18 2019 aveksa_7.1.1_161195-2019-Mar-18-13.31.ear
-rw-rw---- 1 oracle oinstall 1006918058 Dec 20 14:22 aveksa_7.1.1_161195_P01-2019-Dec-20-14.19.ear
-rw-rw---- 1 oracle oinstall 131 Dec 20 14:27 wildfly_deployment.properties
- Now run ./customizeACM.sh -c
it shows that current ear file is 7.1.1 P1 EAR and it picked that
acm->:/home/oracle/archive # cd /home/oracle/deploy/
acm->:/home/oracle/deploy # ./customizeACM.sh -c
You have not specified an archive ear file to customize.
The current ear file deployed to Wildlfy is stored at: /home/oracle/archive/aveksa_7.1.1_161195_P01-2019-Dec-20-14.19.ear
Do you want to customize that archived ear file [yes/no]?
- Secondly , I believe customization should’ve been taken care of by running “patch.sh” script
what i mean that , we have customization stuff in existing EAR (Ver) and now we applied patch on top of that ver.
i believe the patch.sh script take care of it as you see when we run patch.sh it does repacking, underplaying/deploying new customized ear. (unless you want to add more contents after)
Many Thanks,
Rakhee