|
|
|
|
|
|
|
1
|
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
|
9
|
10
|
11
|
12
|
13
|
14
|
15
|
|
16
|
17
|
18
|
19
|
20
|
21
|
22
|
|
23
|
24
|
25
|
26
|
27
|
28
|
29
|
|
30
|
|
|
|
|
|
|
|
|
#9 - 02/15/07 09:54 AM
Best practice recommendations for applying patches
|
Matt_Holt
member
Registered: 01/24/07
Posts: 3
Loc: Minneapolis, MN
|
Hi all -
Does anyone have a recommended process flow for applying patches to AR System and applications? Our system has a number of enhancements - both to code and to the forms.
We're new to the application and are hoping not to learn everything through "trial and error" if we could leverage some experience of others. Thanks for any information and tips you can provide!
Matt
|
|
Top
|
|
|
|
|
#10 - 02/21/07 09:55 AM
Re: Best practice recommendations for applying patches
[Re: Matt_Holt]
|
Matt Reinfeldt
Administrator
Registered: 11/17/06
Posts: 3
|
Matt,
You'll find that all shops tend to do things their own way, but there are some consistencies:
- back up production
- export code
- export data (if necessary)
- import code
- validate clean code (all unnecessary code bits have been removed, ie, if an AL was deleted on Dev, ensure it gets deleted from Prod as well)
- import data
- test
There are tools available (at a cost) to assist with this process: BMC Remedy Migrator & Panacea Workflow Studio.
The actual methodology of exporting/importing tends to vary. I've seen groups that only export code changed since a certain date (the last release), groups that have each developer maintain meticulous lists of all the code that needs to migrate, and groups that move the entire code-base each release. Every method has pros and cons that you will need to weigh before you decide on your methodology.
Take the latter solution, for example.... on the surface, it's cumbersome, right? Move *ALL* the code? scary... but, if you do it correctly, you can ensure an identical copy of your code gets migrated over.
Of course, the above methods don't necessarily cover CMDB changes... that goes through its own procedures and hoops. Maybe someone else will share their procedures for that.
I know I didn't go into a lot of details, but it's one of those items where I have not seen a "standard", per se. If you want, I can cover my personal methodology... 
Enjoy!
|
|
Top
|
|
|
|
|
#11 - 02/21/07 12:52 PM
Re: Best practice recommendations for applying patches
[Re: Matt_Holt]
|
Will Du Chene
member
Registered: 02/09/07
Posts: 2
Loc: Pine City, MN.
|
What are your operating system and database platforms?
_________________________
"Weakness of attitude becomes weakness of character." - Albert Einstein
|
|
Top
|
|
|
|
|
#13 - 03/07/07 10:47 AM
Re: Best practice recommendations for applying patches
[Re: Will Du Chene]
|
Matt_Holt
member
Registered: 01/24/07
Posts: 3
Loc: Minneapolis, MN
|
Sorry for the slow reply.. I thought I had marked my posting to let me know if anyone replied. Thanks for those taking time to check it out.
We're currently using AR System 5.01 and are moving to Remedy v7 (Service Management, Change, SLM, etc.).
|
|
Top
|
|
|
|
Moderator: Colin Miller
|
0 registered
and 0 anonymous users online.
|
|
77 Members
9 Forums
19 Topics
24 Posts
Max Online: 14 @ 02/21/07 09:34 AM
|
|
|
