CTP Application

The best way we have found to handle CTP's is to only install for an issue you are experiencing. You can get the weekly notifiication sent to you off mylawson of CTP's released this week. While helpful to see if anything looks promising, we don't use that to determine when we install CTP's. You would be in a constant cycle of reviewing and installing CTP's.

We install what is needed to correct issues, from there we plan time to install MSP/ESP's. Since these are groups of the CTP's/JT's we include our super users in testing and plan it out like a mini upgrade with scheduled testing cycles. That keeps us current. The MSP/ESP cycles are around May & November. You want to stay current or one back with MSP/ESP becuase that is the standard Lawson policy for patching issues.

When we get a CTP to install (usually from a lawson case) we install in preview mode. That will tell us what programs are updated, we will also do a diff on the code to see what actually changed. Once we know what programs changed, that becomes our list for testing and validation since CTP's can be bundled with others to bring you to a certain code base.

Thanks!

How often do you apply CTPs? Is it as soon as Lawson says which one is needed or on a monthly or quarterly basis or during a normal maintenance window?

We are very similar to Mark, we only install CTPs when an issue comes up. I review the weekly notifications so I am aware of the issues out there but do not typically recommend CTPs to users. The only times we install CTPs when they are released is when they are required for a BSI upgrade or an issue addressed in a critical notification.

We have been in an upgrade cycle where we have not had to worry about MSPs much.

We also rely on the preview log heavily to decide what needs to be tested in the CTP.

Hi Erika,
I also agree with Mike and Roger. We also only apply a CTP if its linked to an ongoing issue.

Due to the amount of testing and thereby resources required for that, we do not have a regular patch applying policy. However if you are able to arrange for resources from within the business to test then should look to apply them at least twice a year (to keep you upto date).

We also rely on the preview mode for the testing to get an understanding of areas(programs) effected and threby testing needs. Some CTP's are just specific to one object but sometimes if a common object library is effected you can have pages of programs which get effected and need testing

Saurabh

Erika,

Ditto for us as well...we only apply CTP's when advised by Lawson that they may correct a specifically reported issue. There are too many to apply them all. Plus, there have been instances where, when applying a CTP to adderess one issue, it may cause or uncover another. So, to keep it simple, we only apply them as needed.

Erika,

We have a normal maitenance window scheduled monthly. So what we do is ID the impact to the organization of the CTP to determine is it needed today or can it wait for our monthly downtime. If for example there is a PR related CTP that is needed before the next PR cycle we would put it in right away but if we get a CTP for a report issue GM465 is one we had recently that had little impact we waited for our monthly downtime.

We have been using the monthly downtime approach for about a year now and the users seem more comfortable. They know when we will take the system, most of them are scheduled, there is no surprises. If a CTP is critical and we need it ASAP, we communicate the downtime as early as possible with impacts (programs effected) and what issue is being addressed.

This approach seems to have given our users a sense of stability. Right after upgrading to LSF 9 we had two months where it seemed almost weekly we were in the CTP install mode. This removed confidence in the system and the code Lawson produces. You have the right approach to get this set up front from the ideas listed in this string. It will make your life so much easier when new to Lawson to set the expectations.

Erika,
Our users are VERY leery of applying a CTP. A CTP is subject to do just about anything. With little or no documenation. We have had a CTP apply that forces a business practice change due to a change on a form that we didn't need or want. Just be very careful on applying them. I agree with all the posts here, have a set time, do not apply a CTP except for a known issue, test every thing.

Thanks everyone for your responses. This is great feedback!

Erika:

Here is my "best practices" -
- Use a standard directory to store all CTP's in, like "ctps/"
- Create a new directory for each CTP. I use this system: For ctp 12345, the directory is "ctps/ctp12345"
- Put the .tar file in the directory for the CTP, untar it in there
- Run CTP in preview mode first. Then copy the preview file from the $LAWDIR/[prodline]/Admin directory.
- If more than one product line is patched, copy preview file using this system:
cp $LAWDIR/[prodline]/Admin/preview.log preview_[prodline].log
(don't use the brackets, I'm just using them for clarity)
- Then proceed as normal