It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×7,423
×5,877
×4,303
×2,344
×1,373
×1,252
×487
×144

question asked: Apr 02 '22, 1:20 p.m.
question was seen: 863 times
last updated: Apr 05 '22, 9:28 p.m.

Related questions

Patching new ELM702 installation to iFix11 before WAS deployment

0
Sean F (1.3k●2●49●160) | asked Apr 02 '22, 1:20 p.m.

I have a new ELM702 installation on Linux

ELM has been installed but it has not yet been configured on WAS or connected to the DB2 database

It is currently stock 702

It needs to be patched to iFix11

I was thinking it would be simpler to patch the installation before plugging it in to WAS + DB2

The iFix11 patch instructions assume that ELM702 has already been deployed on WAS and been running before.

A lot of the instructions seem to be around cleaning up the problems created by the old version.

I was thinking there would be a way to patch the installed ELM702 deployment file system prior to deploying the applications on the WAS server for the first time. Like maybe just replacing each WAR file with the patch version prior to deployment.

Are there any short cuts along this avenue for patching a CLM installation prior to deploying on WAS so the cleanup steps can be eliminated?

Comments
Kenny Smith commented Apr 05 '22, 9:28 p.m.

 Why are you installing on WAS and not using Liberty? 

Be the first one to answer this question!

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.