Best Practice: Upgrade BOXIR2 to BOXIR3.1

Hello,
I have to upgrade from BOXIR2 SP3 to BOXIR3.1
Any experience or best practices with it ..
How long does it need approximately to perform this task ..
Do i have to uninstall all BO Service Packs before beginning in this Rank ? (SP3, SP2, Monthly HotFix 1 then BOE XIR2)
Thanks

there are 2 options
1) upgrade, install XI 3.x on top of XIR2 and choose the upgrade option. This is risky so backup your FRS and CMS db 1st.
2) if a 2nd computer or VM is available then migrate using the import wizard or combination CMS DB copy and FRS copy. (these would be the recommended way to (upgrade/migrate).
Regards,
Tim

Similar Messages

Best practices-upgrade to Universal FC Studio

I have the pre universal installed.
Works fine for the G5 but I can migrate to a universal edition for the same machine (G5).
Question: My personal advice is to ditch all of the old versions but there is no one specific reference on removing an earlier studio application or uninstaller(hint-this is a good idea with Automator I think). I would like NOT to scratch the drive and start anew.
Maybe a manual trash where the applications, their application support files, and preferences are sent to the can. Is there anything else?
Is there a better way?

Before upgrading make sure to back up your current installs (particulalry DVD non-Universal version) Usually just making a copy of the apps themselves in the Application Folder should be okay and you can use them if needed, and if you have any other version of DVD SP you will need it.
Then just install - no real need to delete all the other items because they should update fine. (Though I think there was an issue with some Compressor presets).
You can also ditch all packages, receipts and prefs prior to installing the new software. Usually a good idea to repair permissions both before and after the install also.
As an aside, if you computer is running well, projects are working and being completed, and you have all the apps in the Studio, such as Motion, already running, you may just want to put the Universal Binary on the shelf until you get a MacIntel that needs it.
Final Cut (the Apllication) Universal does run well (and maybe you should install that), the others are a draw, Compressor seems to have thrown a couple of bugs (not sure where, maybe it is Tiger 10.4.8 and Quicktime) although on my MacIntel it does seem alot better than it has been in terms of quality and DVD SP 4.1 has some real issues - such as menu creation - which makes it not great to use.

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

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.

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

Best Practice for config upgrade

Hi
Is there a best practice guide to follow to performing a network upgrade. So I am replacing a stack of 5 3750 switches and replacing with 2 stacks of 2 3750x switches, but then also introducing a 4500x vss pair aswell as the new core. Is there an easy migration process to migrate the config or do I have to understand what the current network is configured as and build a new config for the new topology.
Im new to this process so just wondering if I can find an easier way, Thanks

Is there an easy migration process to migrate the config or do I have to understand what the current network is configured as and build a new config for the new topology.
You really need to understand how the current network is configured before you can do the upgrade otherwise if something doesn't work you will have no idea of where to begin troubleshooting.
That doesn't mean you need to build an entirely new configuration because you may well be able to apply most of the configuration on your existing switches to the new switches although it's not clear what functions the new switches will be doing ie.
currently you have a stack of 3750s doing what ? eg. access for users, routing for vlans etc.
you are replacing them with 3750x's switches and 4500x switches so are you splitting up the functions of the 3750s between them.
If you are then obviously you cannot take the existing configuration and copy it to both the 3750x and the 4500x switches.
When I did upgrades like this I would download the existing configurations to my laptop and make any necessary edits. If I couldn't use the existing configuration I just created new ones. When I came to upgrade I had all the configurations ready to load onto the switches.
Bear in mind that some configuration just won't copy across ie. if you have QOS on your current switches and you try to copy that to the 4500x it probably wont work as they use different commands for a lot of the same functions.
But the key thing is you must understand what you are trying to do ie. simply trying to copy across configurations without the understanding could create a lot of problems.
Jon

Upgrade and migration from Netware to Linux best practice

Hi folks,
We've been running NSM 2.5 for a few years on Netware and have been very satisfied with the product and performance. We are planning to migrating to SLES11 with OES11 very soon to finally move away from Netware and I have some issues I can't seem to find answers to. Of course I want to use NSM to move my home directories from my Netware to my SLES so I want this working well when we migrate.
I've searched but not found a good resource to show how to move the NSM engine from a Netware server to a Linux server with best practices. Anyone have experience with this and any gottchas?
The other question is of course is to upgrade NSM to a new version before or after the move to Linux/OES11? We are at Ver 2.5.0.43 and want to move to the latest version. Upgrade procedure and best practices would be handy.
The last of course is NSM compatible with SLES/OES11? I presume it is and certainly hope so because we want to move all of our users to SLES11 NSS.

On 5/9/2012 11:06 AM, jlauzon wrote:
>
> Hi folks,
> We've been running NSM 2.5 for a few years on Netware and have been
> very satisfied with the product and performance. We are planning to
> migrating to SLES11 with OES11 very soon to finally move away from
> Netware and I have some issues I can't seem to find answers to. Of
> course I want to use NSM to move my home directories from my Netware to
> my SLES so I want this working well when we migrate.
> I've searched but not found a good resource to show how to move the NSM
> engine from a Netware server to a Linux server with best practices.
> Anyone have experience with this and any gottchas?
The NSM 3.0.x Engine setup process actually handles the migration from
NSM 2.5 fairly easily. Our 3.0 Installation Guide (available at
http://www.novell.com/documentation/storagemanager3 ) includes all the
information you should need regarding migration, including the
suggestions I'll list here.
You'll want to leave NSM 2.5 running during the migration so that the
NSM 3.0 setup wizard can connect to that Engine and import its policies
and pending events. You'll also want to have as few pending events as
possible in NSM 2.5 -- deferred deletes are fine, but all pending events
will slow down the migration process, since they'll have to be
transferred over.
> The other question is of course is to upgrade NSM to a new version
> before or after the move to Linux/OES11? We are at Ver 2.5.0.43 and want
> to move to the latest version. Upgrade procedure and best practices
> would be handy.
Again, this information is available in the 3.0 Installation Guide. To
migrate from 2.5 to 3.0.x, you'll have to have at least one OES11 server
in your tree to install it on; but you'll also have to leave the NSM 2.5
Engine running on its Netware host long enough to migrate from it.
> The last of course is NSM compatible with SLES/OES11? I presume it is
> and certainly hope so because we want to move all of our users to SLES11
> NSS.
We are about to release version 3.0.4 of NSM, which provides full
support for OES11 on SLES11. The NFMS Support Team can also provide you
with builds of NSM 3.0.3 which support OES11; if you need those for
early testing, please send an email to storagemanager[at]novell[dot]com.
Hope this helps!
- NFMS Support Team

Best Practice: Upgrade BOXIR2 to BOXIR3.1

Similar Messages

Maybe you are looking for