Issue with the Patch execution where new patch is not supperseeding old one.

Amogh_Bongirwar

I have an case where I have created one custom patch is 2015 using the custom module code and which was moved to processed to the production.

 

Now in 　2017 I have created another patch using the Same custom module code which I used in 2015 (Note 2015 patch was not present in my dev box while developing the 2017 patch)

 

Now in production we have both 2015 and 2017 patch is present.

 

The case which I observed that in few random case environment is 　using 2015 patch to execute the code(so the 2017 code changes is not working).

 

Where as per my knowledge Livelink will always use the latest patch code if there are multiple patch for same function based on patch created date.

 

Testing already: Patch 2017 and 2015 is present on the server and code for patch is same in all the case.

 

Does any one have idea on this point how\ in which sequence livelink will load the patch.

 

Appu Nair

If you are familiar with Oscript may I suggest you look at the Patch Ospace?I see many tell tale signs of how it is done

ApplyOldPatch, ApplyNewPatch etc etc. A cursory look tells me the new style actually takes precedence,alterable

in a ini setting 

In any case you can safely put a echo statement in a patch

For e.g echo(" I am the Old patch") in the old and echo("I am the new") in the new and this will rule out if

LL is loading one or both your patches in the thread log.

Towards the end of the startup you will see some counts like

         .PatchLog( "===[ PATCH SUMMARY ]====================" )

.PatchLog( Str.Format( "Total patches skipped: %1", .GetPatchesSkipped() ) )

.PatchLog( Str.Format( "Total features overwritten: %1", .GetFeaturesOverwritten() ) )

.PatchLog( Str.Format( "Total features overwritten more than once: %1", .GetFeaturesOverwrittenAgain() ) )

.PatchLog( Str.Format( "Total features overwritten with the same value: %1", .GetFeaturesOverwrittenSameValue() ) )

.PatchLog( "========================================" )

A more interested person might even look at PostPatchActions.

​

If yours is a new "style" i think it will do some date /time based treatment...

Appu Nair
Principal Architect | Alitek
Website: alitek.com

---

From: eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com>
Sent: Thursday, July 6, 2017 9:52 AM
To: eLink Recipient
Subject: Issue with the Patch execution where new patch is not supperseeding old one.

 

Issue with the Patch execution where new patch is not supperseeding old one.

Posted by Bongirwar, Amogh On 07/06/2017 10:44 AM

I have an case where I have created one custom patch is 2015 using the custom module code and which was moved to processed to the production. Now in 　2017 I have created another patch using theSame custom module code which I used in 2015 (Note 2015 patch was not present in my dev box while developing the 2017 patch) Now in production we have both 2015 and 2017 patch is present. The case which I observed that in few random case environment is 　using 2015 patch to execute the code(so the 2017 code changes is not working). Where as per my knowledge Livelink will always use the latest patch code if there are multiple patch for same function based on patch created date. Testing already: Patch 2017 and 2015 is present on the server and code for patch is same in all the case. Does any one have idea on this point how\ in which sequence livelink will load the patch.

---

[To post a comment, use the normal reply function]
Forum:	Content Server Development Forum
Content Server:	Knowledge Center CS16

 
Confidentiality Note: This message contains information, which may be privileged or confidential, or exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee responsible for delivering the message to the intended recipient, you are hereby NOTIFIED that any dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you receive this message in error, please notify sender immediately.