NW Upgrade best practice

Hi
We will be upgrading our WAS 6.40 (and EP6) patch level from 17 to 21 and I want some advice as to which stage in the process would be ideal to upgrade NWDS from 17 to 21.
By which stage, I would mean, at the end of the production upgrade, or when developemnt and test have been upgraded or at what ever time that is best. There will be code freeze in terms of enhancements but we may need to work on some emergency break-fixes, if any.
Also, will there be any issue if we were to develop Java webdynpro using an older SP (17) and migrate them through newer development and test env (21) to go to production (17)?
Appreciate if anybody can share from experience or provide some links to useful materials.
Many thanks!
Sanchai

Your NWDS must be on the same patch level as your target system you are developing in. If you freeze development for the upgrade in a sane way then you need to be able to perform maintenance to production so will need the same patch level as production. However you also need to perform and fixes to modification in the patched systems.
What I am saying is you likely need both versions to be safe and can in fact run both versions on the same PC.
Don't forget to import the latest BUILT/JEE/JTECHS SCA's into the tracks that have been patched and move them along the track with the patching you perform.
SAP strongly recommends the NWDS be on the same SP level as the target system and also your tracks have the same SCA Archive versions. Otherwise your CBS can happily build without error but your deploy could at worst cause a system restore and being shouted at by basis. Basically developing 21 - 21 - 17 is not safe but rolling changes through 21 -21 - 21 as you are patching is fine
Course ADM225 teaches some of this and some is spread in notes and online help. Its a bit of an all round question and not all stuck in one place I'm afraid.
Edited by: Graham Newport on Mar 31, 2008 11:53 PM

Similar Messages

11g Upgrade Best Practices

Hi,
We have a SAP ERP 6.0 EHP5 SPS6 with Oracle Database 10.2.0.2 running on AIX 5.3.
There is a DR Standby Database available for the Production setup.
We need to upgrade the DB to 11g R2.
Please let me know if the DB can be upgraded with minimal or no downtime.
Please share the best practices for upgrading the DB with minimal or no downtime.
Regards,
Narayan

There would be a minimal downtime. From 11202 onwards, the upgrades would be out-of-place so the downtime would be lesser compared to the previous releases. Please see the following link and download the slides for the upgrade and migration from the Upgrade group of Oracle Corp.
http://apex.oracle.com/pls/apex/f?p=202202:2:::::P2_SUCHWORT:migrate112
Aman....

Upgrade Best Practices

Hi,
Do anyone have or know about the best practices of upgrade from 4.6c to ECC 6.0

Hi Satya,
There is a small ppt from SAP at following link.
http://help.sap.com/bp_bblibrary/500/General/SAP_BP_Upgrade.ppt
May be you would like to have look at it.
Thanks
Umesh

BO XI R2 to BO XI 3.1 upgrade - Best Practice

Hi Experts,
    We are using BO Xi R2 version now. We would like to upgrade BO XI R2 to BO XI R3.1 version. Could you please suggest me
How to do that. Could you please provide me step by step how to go about this task?
    Could you please tell me what are all the advantages and disadvantages of this activity? Is there any problem if I migrate the reports and instance from my BO Xi R2 version to BO XI 3.1 version After Installation of BO XI 3.1.
     Suggest some best methods to do this activity.
Regards,
Sridharan Krishnan

There is no step by step upgrade because every customer system is different. XIR2 can be upgraded or migrated. Typically migrated is the safest option (because it doesn't require both versions to be installed on the same server) .
Migration would require that you have your XIR2 server and XI 3.1 on a different server then you could use the [import wizard |http://help.sap.com/businessobject/product_guides/boexir31SP3/en/xi31_sp3_bip_importwiz_en.pdf]on 3.1 to bring everything over.
Typically customers would hire a consultant for complex migrations.
Regards,
Tim

Upgrade from XI 3.0 (SP17) to PI 7.0 (SP12): Best Practices

Hi mates,
I've a few questions regarding the upgrade to PI 7.0.
If the upgrade process is done in phased manner i.e. DEV, QA, PRD in that order over a period of 3 weeks,
How do we handle the transports from DEV->QA->PRD when DEV is 7.0 and QA & PRD on 3.0 using CMS?
Will there be inconsistencies when transports are moved, because a few features could be different or internal representation of IR/ID content could be different in 3.0 & 7.0?
What are the upgrade best practices, phased manner or all at a time?
Please throw more light on this. I appreciate the inputs from people who've helped clients upgrade from 3.0 to 7.0. Any SAP documentation related to this?
I looked at the thread Transports from XI 3.0 to PI 7.0 but the answert is very generic, w/o any supporting documentation and real time experience.
thx in adv
praveen

> Hi mates,
>
> I've a few questions regarding the upgrade to PI
> 7.0.
>
> If the upgrade process is done in phased manner i.e.
> DEV, QA, PRD in that order over a period of 3 weeks,
> How do we handle the transports from DEV->QA->PRD
> when DEV is 7.0 and QA & PRD on 3.0 using CMS?
Im my experience you should implement a change freeze for this period, with the exception of emergency transports - and these have to be justified.
> Will there be inconsistencies when transports are
> moved, because a few features could be different or
> internal representation of IR/ID content could be
> different in 3.0 & 7.0?
Full regression testing will be needed on each interface. If you implement a change freeze this process becomes easier
>
> What are the upgrade best practices, phased manner or
> all at a time?
Allow plenty of resources to fully test every interface, as you would with any upgrade.
You could also take the time to implement the new <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/80bbbd55-5004-2a10-f181-8bb096923cb6">CTS+</a> for this new version to avoid any further transport issues (PI7.0 SP12 +). A new method for a new system!
Also, how is your SLD set up for XI? This can have an impact.

Best practice for upgrading task definition without deleting task instances

best practice for upgrading task definition in production system without deleting or terminating task instances
If I try and update a task definition with task instances running I get the following error:
Task definition 'My Task - Add User' may not be modified while there are active task instances
Is there a best practice to handle this. I tried to force an update through the console but that didn't work. I tried editing the task from the debug page and got the same error.

1) Rename the original task definition.
2) Upload the new task definition with the original name.
3) Later, after all the running tasks have timed out, delete the old definition.
E.g., if your task definition is "myWorkflow":
1) Rename "myWorkflow" to "myWorkflow-old-2009-07-28"
2) Upload the new task definition as "myWorkflow".
Existing tasks will stay linked to the original (renamed) workflow definition.
New tasks will use the new definition.
As the previous poster notes, depending on the changes you are making, letting the old task definitions stay active could have bad side-effects and might be better avoided.

Upgraded to CS5, CS4 apps still in place. OK to remove? Best practice?

No problem to report just a minor dilema.
Upgrade to CS5 is completed and all the previous CS4 application folders are still in place and functional.
What is the best practice regarding the previous version?
Leave them be.
Move to trash.
Uninstall (when provided).
Thanks for your help.
Pete
iMac • Intel Core i7 • 2.8 GHz • 8 GB RAM • OS X 10.6.7

Bob,
One follow-up question. What about the earlier Acrobat component? Backward compatibility isn't problematic in the case of Acrobat correct?
Thanks for your time.
Pete
iMac • 2.8 GHz Intel Core i7 • 8 GB RAM • OS X 10.6.7
Adobe CS5.x Design Premium

Best Practice for upgrading to 11.1.1.3

Hi,
Can anyone tell me what is the best practice to upgrade FMW to 11.1.1.3...
I followed the following steps to set up FMW 11.1.1.3.
1. Oracle Enterprise edition Database 10.2.0.1 and applied 10.2.0.4 patch
2. Installed RCU 11.1.1.3
3. Installed Weblogic server 10.3.3 (11gR1)
4. Installed Soa Suite 11.1.1.2 and applied patch for 11.1.1.3
Is this the right way of installation or do i have to install 11.1.1.2 first f and then install 11.1.1.3..
Regards,
Sundar

Yes, that seems to be fine.
regards

EP Upgrade - SP14 - Best Practice for Modification File Comparison

SDN Experts -
We are upgrading our EP from SP14 - SP16. SAP offers a file "diff" tool that is only useful for Java application files to assist in re-applying our mods on top of the new code stack.
We are looking for best practices in Portal upgrades to do the following:
- Identify all files that we have modified on existing SP
- Diff all source code files (java, XML, GUI, other) between Current SP14 and SP16
We are also looking for documentation that identifies the local directory structure for NWDS. This would aid us in creating a batch process to "diff" our source code libraries.
Any recommendations are appreciated.
Thanks

I'm not realy getting your question because you already state what to do:
We are looking for best practices in Portal upgrades to do the following:
Identify all files that we have modified on existing SP
Diff all source code files (java, XML, GUI, other) between Current SP14 and SP16
You should know by documentation what is changed I guess? Then start diff-ing the code and recompile or repackage. NWDS also has diff functionalities.
Good luck,
Benjamin

Best practice for upgrading task definition in production system

If I try and update a task definition with task instances running I get the following error:
Task definition 'My Task - Add User' may not be modified while there are active task instances
Is there a best practice to handle this. I tried to force an update through the console but that didn't work. I tried editing the task from the debug page and got the same error.

The best way for upgrade purposes is to use the rename function of the TaskDefinition from the lh command line utility.
Basically renames all current task instances with the TaskDefinition name. You can then alter the existing TaskDefinition and upload into identity manager.

Best Practice in Upgrade from ECC 5.0 to ECC 6.0

Dear All,
Can someone help in looking for Best practice in Upgrade from ECC 5.0 To ECC 6.0 Project from Functional FI and CO Side.
Thanks

Moved to a different forum.

Best Practice for Installation of Both Leopard and Aperture 2 upgrade.

I've finally bought the bullet and purchased both Leopard and Aperture 2.0 upgrade. I've tried searching for a best practice to install both, but haven't been able to find one--only trouble shooting type stuff. Any suggestions, things to avoid, etc would be greatly appreciated. Even a gentle shove to a prior thread would be helpful. . . .
Thanks for pointing me in the right direction.
Steve

steve hutchcraft wrote:
I've tried searching for a best practice to install...
• First be really sure that all your apps work well with 10.5.3 before you leave 10.4.11, which is extraordinarily stable.
• Immediately prior to and immediately after every installation of any kind (OS, apps, drivers, etc.) got to Utilities/Disk Utility/First Aid, and Repair Permissions. Repairing Permissions is not a problem fixer per se, but anecdotally many folks with heavy graphics installations (including me) who follow that protocol seem to maintain better operating environments under the challenge of heavy graphics than folks who do not diligently do so.
• When you upgrade the OS do a "clean install."
• RAM is relatively inexpensive and 2 GB RAM is limiting. I recommend adding 4x2 GB RAM. One good source is OWC: http://www.owcomputing.com/.
• After you do your installations check for updates to the OS and/or Aperture, and perform any upgrades. Remember to Repair Permissions immediately prior to and immediately after the upgrade installations.
• If you are looking for further Aperture performance improvement, consider the Radeon HD 3870. Reviews at http://www.barefeats.com/harper16.html and at http://www.barefeats.com/harper17.html.
Good luck!
-Allen Wicks

What's the best practice to upgrade 3GS from 3.1.2 to 4.2.1

I was reading the thread which was very helpful:
http://discussions.apple.com/thread.jspa?threadID=2665989
But there is a slight difference here with my situation:
-- I'm planning to upgrade from 3.1.2 to 4.2.1, yet in that thread the guy was trying to upgrade from 4.1
And recently a friend told me he had an error 1013 during upgrade. Google also mentioned another error code, 1015, related to upgrading to 4.2.1
1. Does anyone know what exactly caused Error 1013 and 1015?
2. what is the best practice to upgrade from 3.1.2? Upgrading to 4.1 first and then upgrade from 4.1 to 4.2.1? Will that eliminate the occurring of these itunes errors?
*(Yes, I know apple has officially terminated supporting upgrading an iphone firmware to anything below 4.3. But can we just discuss my questions hypothetically?)*
Thanks people.

paulcb wrote:
Errors 1013 and 1015...
http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=iphoneError+1013+and1015
http://support.apple.com/kb/ts1275
Thanks a lot, paulcb.

Best practices of Upgrade - 10.1.2 to 10.1.3

One of our customer is planning to upgrade BPM (BPEL Process manager server) to latest version…(10.1.2 to 10.1.3)
Please let me know if someone has any best practice document on this upgrade and provide some guidance to modify the old components to new components.
This will help the customer to work with the latest oracle fusion suite of components.

Cbeckett,
I haven't checked yet, but my guess is that the upgrade side isn't
ready yet - at this early stage it's more to show you what features
ares there...
Shaun Pond

SAP Upgrade from 4.7 to ECC 6.0 connected to BW 7.0 Best Practices

We are upgrading SAP R/3 4.7 to ECC 6.0. We have been running live in a BW 7.0 environment. We have done some enhancements for 2LIS_11_VAITM - Sales Document Item Data and 2LIS_13_VDITM - Billing Document Item Data datasources. We currently have a test instance that has been upgraded to ECC6.0.
What are the best business practices for testing BW to insure data transfer and enhancements are working correctly?
Eg. Should we connect the ECC6 instance to BWD and test there OR upgrade R/3 TST that is connected BWD and test there OR Upgrade QAS and test in BWQ.
Thanks in advance . . .
Edited by: RWC on May 4, 2011 6:26 PM

Hi RWC,
the plug-in will change slightly, you may notice differences in the screens of RSA2 and others after the upgrade.
Regarding best practices: In a recent upgrade our project team decided to create a parallel landscape with a new, additional Dev and QA on the R/3 side.
We connected these new systems to a BW Sandbox and the BW QA.
We identified all datasources, transfer rules and infopackages in use in production and recorded them with related objects onto transports in BW Dev. Before the import into BW Sandbox and BW QA we adjusted the system name conversion table to convert from old R/3 Dev to new R/3 Dev in order set up all the required connections for testing with the upgraded R/3 systems.
After the go LIVE of the upgrade we renamed the old R/3 Dev system in BW Dev and ran BDLS to convert everything (speak to your Basis team). That way we made sure not to lose any Development and we got rid of the old R/3 Dev system.
Take a look at this post for issues we encountered during this project and test everything you load in production.
Re: Impact on BI 7.0 due to ECC 5.0 to ECC 6.0 Upgrade
Best,
Ralf

NW Upgrade best practice

Similar Messages

Maybe you are looking for