How to migrate Stellent 7.5.1 custom layout component to OCS 10gR3

Hi,
I am in the process of upgrading stellent 7.5.1 to OCS 10gR3. There is a custom layout component in 7.5.1 wanted to find out how can I migrate the layout component. As probably there are changes in 10gR3 so want to find out how to migrate the custom layout component and any changes required before migrating to 10gR3.
Thanks.

Hi
am putting out the steps needed for upgrading an existing CS instance from version 7.5.1 to 10gR3. Its basically a 2 step process where we use Configuration Migration Utility to migrate the CS structure and Archiver to migrate the existing contents. The steps are as follows :
1. Install a new CS 10gR3 instance on the server and configure it as per the install guide.
2. Verify that the basic functionalities for the newly installed instance is working fine by doing some simple tests like checkin ,checkout , update etc. Then upgrade the CS to the latest patchset level which can be downloaded from http://updates.oracle.com/download/6907073.html.
3. Install the latest version of Configuration Migration Utility component (which is found in the same uprgade patch set ) on both the 10gR3 CS (target) instance and the 7.5.1 CS (source).Enable them on both the CS instances and restart the same.
4. Run the Configuration Migration Utility on the source CS and download the CMU Bundle created on it.
5. Upload the CMU Bundle created in previous step to the Target CS and import the configurations from that.Verify that the CMU process is completed successfully on the Target CS instance.
6. Create a new archiver instance on the Source CS and export all the contents in that.
7. Open the Archiver Applet for the target CS instance and then Point the collections to the collections.hda of the source CS instance so that we can import the contents. Start the Import process on target server.
8. Once the CMU and Archiver Process are completed then your 10gR3 CS would be an exact replica of the Source 7.5.1 Instance.
You may also go through System Migration Guide to get more understanding on the Migration / Upgrade processes.
Hope this helps
Thanks
Srinath

Similar Messages

How to invoke updateDisplayList method in the custom layout?

I've a group of buttons that get placed in a SkinnableDataContainer with the help of a custom layout class as follows:
<s:SkinnableDataContainer id="buttonsContainer"
    dataProvider="{appModel.myButtons}"
    width="{DIAPLAY_WIDTH}" height="{BUTTON_HEIGHT+4}"
    skinClass="view.skins.ContainerSkin"
    itemRenderer="view.renderer.MyButtonRenderer"
    click="startPointAreaClickHandler(event)"
    mouseMove="areaMouseMoveHandler(event)"
    mouseUp="areaMouseUpHandler(event)"
    rollOut="areaMouseOutHandler(event)"
    >
    <s:layout>
        <layout:ButtonsLayout />
    </s:layout>
</s:SkinnableDataContainer>
myButtons is an ArrayCollection of VOs and VO has x and y coordinates as fields. Values of x and y determine the location of the button. When I add an object to myButtons, the application behaves as expected (adds a button in buttonsContainer at specified x and y coordinate). But when I just change values of x and y of an existing button, the buttons don't get repositioned. I have tried calling invalidateDisplayList on buttonsContainer but that doesn't trigger updateDisplayList method in the custom layout ButtonsLayout.
How do I trigger updateDisplayList method in the custom layout so that the button positions get updated whenever an event changes values of x and y of a button?

Hi Balus,
This is helpful but one problem i faced with this is, when i overided the custom message in the property file,
javax.faces.component.UIInput.REQUIRED =Value is required
but for every UIInput component the same message is coming, but if i am having more than one component on the page forexample: UserName , Email, Password etc...
i need to display messages like
Value is reuired for UserName
Value is reuired for Password
Value is reuired for Email
How this is possible , can u please help me.
Thank You,
Subrahmanyam Baratam.

How to set up fixed height in ADF layout component

I try to create a page by having my main content at the center of page within a box using a fixed height. The idea is when the content is too long, a vertical scrollbar should show up for that box instead of stretching that box. I tried to use trh:tableLayout and set height attribute for trh:cellFormat component. However, instead of showing a vertical scrollbar, it just stretches table cell. Does anyone have a solution to this issue? Thanks.

Thanks for your fast reply. Yes, I already tried layout="vertical" which is not help. I am using JDeveloper 11.1.1.2.0. Actually what I want to do is I will display a block of information in a box area at the center of screen. If the information become too big for that box, I want a scrollbar to show up for that box instead of stretching that box to fit the content.

Search result category with a custom layout set?

Greetings,
I've created a nice little search IVIEW with a custom search options set that will display the document category (taxonomy) in the search result (if the resulting document is categorized, of course.) Works great. However there is one little problem. The categories in the search results are hyperlinked and when you select one, you get a new window with the taxonomy rendered in the default layout set (the ConsumerExplorer I think.) Not good. I need this displayed in a custom layout set.
Any ideas how to make this hyperlink use a custom layout set without changing the default?
Regards,
Paul Federighi

Hi Paul,
As per my knowledge of the basic s of layout sets and iviews.
You want to change the layout set of the iview(window) which opens when u click the hyperlink.
You should do this:
1)Make a new layout set by customizing the default one.
2)If the iview opening is a standard iview then go to its properties and change the Layout set value to ur new layout.
Please revert in case of issues.
I hope it helps.
Regards,
Sumit

How To Migrate My Customized reports & Forms To R12?

Hi...
How To Migrate My Customized reports & Forms To R12?
I want to migrate my customized report&forms to R12 From 11.5.9 Base?
how to find the customized Reports & Forms Location?
How To Register the customized Reports & Forms?
Regards
**SBJ**

Hi,
Please see these documents/links.
Note: 563258.1 - How To Upgrade 11i Custom Forms To R12
Note: 451934.1 - Accessing Custom Forms After Upgrading From To R12
Note: 552010.1 - Can't Open Custom Forms After R12 Upgrade
Note: 130686.1 - How to Generate Form, Library and Menu for Oracle Applications
Forms & Reports in R12?
Forms & Reports in R12?
Thanks,
Hussein

How to migrate my effects custom presets from Premiere Pro CC to Premiere Pro CC 2014?

I have recently created a whole bunch of custom made presets for all the effects I use on a regular daily bases on Premiere Pro CC.
Today I installed the new CC 2014 and all my custom bins and effects presets are gone and to create them all again will literally take me a couple of days and you know all know time is money and I need this migration to happen straight away if possible.
Any ideas on how to migrate these custom made effects presets?
Thanks very much,
Marcelo

Have you tried syncing your preferences and presets to your cloud account? If not, go into the previous version of PP where you have your presets, under the "Premiere Pro" menu on a Mac (not sure where on Windows), the third menu item down (should be your Adobe CC account if you're logged in) allows you to sync all of your settings with the Cloud. Perform this sync, close PP and open PP2014. Sync your settings again and they should all appear in PP CC 2014.

How to migrate rtf Templates in XML Publisher ?

Hi All,
I want the script so that i can download and upload the RTF files directly from my development instance to my production instance.
For this i have come across 3 links
How to migrate rtf Templates in XML Publisher?
http://download.oracle.com/docs/cd/B40089_10/current/acrobat/120xdoig.pdf
unable to migrate physical files using XDO Loader utility
and from here i am running this command from /home/aryan directory
java oracle.apps.xdo.oa.util.XDOLoader DOWNLOAD -DB_USERNAME apps -DB_PASSWORD fnd -JDBC_CONNECTION sharp.apps.com:1522:tst1 -LOB_TYPE TEMPLATE -APPS_SHORT_NAME CUSTOM -LOB_CODE ZEMP -LANGUAGE en -TERRITORY US
but it is giving me error "ksh: java: not found". could anyone can tell me how and from where i have to run the download and upload command
Thanks
Aryan

Hi Hussein,
I tried with applmgr also and still for java -version it is giving me error ksh Java not found
and for which java it is giving me error no java found in different directories path.
Thanks
Aryan

OIM11gR2 - How to migrate an Application Instance Form

Hello,
I'm trying to migrate an Application Instance Form from my Dev env to my QA env.
My target system is SAP
I performed the following steps in Dev:
1. Installed and configured the SAP Connector (no problem here)
2. Created a sandbox
3. Created an Application Instance
4. Created the Application Instance Form
5. Ran a target reconciliation to confirm everything is working properly
6. Exported the sandbox
7. Published the sandbox
8. Via Deployment Manager I exported all objects related to SAP (Resource object, Process Forms, Lookups etc.)
In QA I did:
9. Installed and configured the SAP Connector (no problem here)
10. Via Deployment Manager I imported the objects related to SAP
11. Imported the sandbox
Problem:
To my surprise, the Application Instance does not have a Form in the QA env.
I had to create it manually by performing the following:
12. Create a sandbox
13. Open the Application Instance definition
14. Click on create (to create a form)
15. Entered the same name I used in my Dev environment
16. Received an error message saying that the form already exists
17. Entered a different name for the Form
18. Saved
19. Exported the sandbox (to import in Prd)
20. Published the sandbox
21. Ran a target reconciliation to confirm everything is working properly
I tried to reproduce the problem with another (test) destination environment because I don't want to have the same problem when migrating to Prd.
I repeated the steps 9,10,11 except that I imported the sandbox exported from QA (step 19) instead.
The same problem: Application Instance definition has no Form attached to it in my test destination environment.
If I try to create the form with the same name, it gives an error message saying it is already there.
Is my procedure wrong?
Is there an official procedure explaining how to migrate only Application Instance Form from one env to another?
My env:
OS: Windows 2008 R2 SP1
OIM: 11gR2 BP7
SAP connector: 9.1.2.2.0
Thanks,
Adr

This is a bug: Bug:16027176
Check the [Article ID 1515225.1] which proposes a workaround that might be useful in your case (it was not in mine).
In short the workaround is:
The following order should be observed to export :
- IT Resource & Application instance in one xml
- Request DataSet in another xml
- SysAdmin Sandbox (the one defined while creating the Application Instance and the Form)
- Identity URL Sandbox (defined while customizing the fields on the Form, in the Catalogue page)
Adr

How to migrate mails from Google Apps to MS Exchange Online IMAP (Getting error)

Any tips on How to migrate mails from Google Apps to MSOL? What is required? When I am trying to migrate using IMAP but getting fpollowing error
=======================
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:11
[email protected]
Failed
Error:
Failed to log on successfully for the following reason:
Server rejected Basic login with following message : * CAPABILITY IMAP4rev1 UNSELECT LITERAL+ IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 UIDPLUS COMPRESS=DEFLATE.
Exchange Management Shell command attempted:
'Microsoft.Exchange.Transporter.Provider.PopImap.InternetMailboxMeta' | Move-XsIMAPMailboxToExchangeOnline -AllowUnsecureConnection $false -TargetCredential 'System.Management.Automation.PSCredential' -MaxThreadCount '10' -Quiet
Elapsed Time: 00:00:11
======================
Any help will be much appreciated.
Regards
Sunil DK

I just finished migrating a client from Google Apps to Microsoft Exchange Online using the IMAP option in the Microsoft Online Services Migration Tool.
I added the mailboxes by creating a CSV file [i.e. GoogleApps(Gmail)_Mailboxes.csv] in the following format:
SourceIdentity,SourceServer,SourceLoginID,SourcePassword,TargetIdentity
[email protected],imap.gmail.com,[email protected],P@ssword1,[email protected]
[email protected],imap.gmail.com,[email protected],P@ssword2,[email protected]
[email protected],imap.gmail.com,[email protected],P@ssword3,[email protected]
Then I created a custom folder map XML file [i.e. GoogleApps(Gmail)_FolderMap.xml] to map the Google Apps (Gmail) labels to the appropriate Exchange (Outlook) mailbox folders and create those that didn't exist (i.e. Important, Starred, Follow up,
Misc, Priority) as sub-folders under the Inbox:
<?xml version="1.0" encoding="utf-8"?>
<FolderMappings xmlns="http://tempuri.org/FolderMap.xsd">



<Folder path = "INBOX">
<Property SpecialFolder = "Inbox"/>
</Folder>
<Folder path = "New Mail">
<Property SpecialFolder = "Inbox"/>
</Folder>
<Folder path = "[Root]">
<Property SpecialFolder = "Inbox"/>
</Folder>
<Folder path = "">
<Property SpecialFolder = "Inbox"/>
</Folder>
<Folder path = "Calendar">
<Property SpecialFolder = "Calendar"/>
</Folder>
<Folder path = "Tasks">
<Property Name = "Migration items/Tasks"/>
</Folder>
<Folder path = "Sent Items">
<Property SpecialFolder = "Sent Items"/>
</Folder>
<Folder path = "Sent Mail">
<Property SpecialFolder = "Sent Items"/>
</Folder>
<Folder path = "Sent">
<Property SpecialFolder = "Sent Items"/>
</Folder>
<Folder path = "Deleted Items">
<Property SpecialFolder = "Deleted Items"/>
</Folder>
<Folder path = "Trash">
<Property SpecialFolder = "Deleted Items"/>
</Folder>
<Folder path = "Drafts">
<Property SpecialFolder = "Drafts"/>
</Folder>
<Folder path = "Draft">
<Property SpecialFolder = "Drafts"/>
</Folder>
<Folder path = "Junk E-mail">
<Property SpecialFolder = "Junk E-mail"/>
</Folder>
<Folder path = "Spam">
<Property SpecialFolder = "Junk E-mail"/>
</Folder>
<Folder path = "Contacts">
<Property Name = "Migration Items/Contacts"/>
</Folder>
<Folder path = "Outbox">
<Property SpecialFolder = "Outbox"/>
</Folder>
<Folder path = "Journal">
<Property SpecialFolder = "Journal"/>
</Folder>
<Folder path = "Notes">
<Property SpecialFolder = "Notes"/>
</Folder>
<Folder path = "Public Folders">
<Property ExcludeFolder = "true"/>
</Folder>

<Folder path = "[Gmail]/All Mail">
<Property ExcludeFolder = "true"/>
</Folder>
<Folder path = "All Mail">
<Property ExcludeFolder = "true"/>
</Folder>
<Folder path = "[Gmail]/Drafts">
<Property SpecialFolder = "Drafts"/>
</Folder>
<Folder path = "[Gmail]/Important">
<Property Name = "Inbox/Important"/>
</Folder>
<Folder path = "[Gmail]/Sent Mail">
<Property SpecialFolder = "Sent Items"/>
</Folder>
<Folder path = "[Gmail]/Spam">
<Property SpecialFolder = "Junk E-mail"/>
</Folder>
<Folder path = "[Gmail]/Starred">
<Property Name = "Inbox/Starred"/>
</Folder>
<Folder path = "[Gmail]/Trash">
<Property SpecialFolder = "Deleted Items"/>
</Folder>

<Folder path = "Follow up">
<Property Name = "Inbox/Follow up"/>
</Folder>
<Folder path = "Misc">
<Property Name = "Inbox/Misc"/>
</Folder>
<Folder path = "Priority">
<Property Name = "Inbox/Priority"/>
</Folder>
</FolderMappings>
Additionally, I had to tell the Internet E-mail Mailbox Migration Wizard to use the "Individual Account Credentials" option since I was able to specify each account password in the CSV file when adding the mailboxes to Microsoft Online Services Migration
Tools console.
Just to note, the users had to manually export their contacts to a CSV file and calendars to iCal (ICS) files in order to import those items into Outlook.
I hope this will benefit others since Microsoft doesn't seem to have a custom, specifically defined migration strategy for this scenario. With Google Apps being in direct competition with BPOS/Office365, I assumed that Microsoft would have a simple
strategy using something like ActiveSync to facilitate the migration of email, contacts, calendar entries, etc. Hopefully we'll see something along those lines become available in a future release of the migration tools.
--Jon Payne

How to upgrade Stellent 7.5.1 to Oracle Content Server 10gR3

Hi,
I need to upgrade Stellent 7.5.1 to OCS 10gR3. Can someone provide the steps. Do I need to install OCS 10gR3 and then migrate the folders and content how do I migrate all the folder, content to 10gR3. Is there any documentation, blogs, steps that I can catch up on to get the understanding and get started. Any help is appreciated.
Thanks

Hi
am putting out the steps needed for upgrading an existing CS instance from version 7.5.1 to 10gR3. Its basically a 2 step process where we use Configuration Migration Utility to migrate the CS structure and Archiver to migrate the existing contents. The steps are as follows :
1. Install a new CS 10gR3 instance on the server and configure it as per the install guide.
2. Verify that the basic functionalities for the newly installed instance is working fine by doing some simple tests like checkin ,checkout , update etc. Then upgrade the CS to the latest patchset level which can be downloaded from http://updates.oracle.com/download/6907073.html.
3. Install the latest version of Configuration Migration Utility component (which is found in the same uprgade patch set ) on both the 10gR3 CS (target) instance and the 7.5.1 CS (source).Enable them on both the CS instances and restart the same.
4. Run the Configuration Migration Utility on the source CS and download the CMU Bundle created on it.
5. Upload the CMU Bundle created in previous step to the Target CS and import the configurations from that.Verify that the CMU process is completed successfully on the Target CS instance.
6. Create a new archiver instance on the Source CS and export all the contents in that.
7. Open the Archiver Applet for the target CS instance and then Point the collections to the collections.hda of the source CS instance so that we can import the contents. Start the Import process on target server.
8. Once the CMU and Archiver Process are completed then your 10gR3 CS would be an exact replica of the Source 7.5.1 Instance.
You may also go through System Migration Guide to get more understanding on the Migration / Upgrade processes.
Hope this helps
Thanks
Srinath

How to migrate pricing condition data using lsmw

Hello All,
can any one explain how to migrate pricing condition data using lsmw.
the scenario is we are trying to extend the pricing conditions from one sales area to other sales area on a combination of sales organization, distribution channel and division.

Hi Sreedhar Kodali
Pricing conditions can be extended with the following options:-
1) Customer / material with release status
2) Sales Org / Dist. Channel / Cust group / Material
3) Price List category / Currency / material with release status
4) Material with release status
Assuming that your pricing condition in one sales area is different to another, first you have to create LSMW recording to extend the sales area and then pricing conditions can be uploaded accordingly.
Thanks
G. Lakshmipathi

How to migrate the Objects from 3.1c to BI7

Hi,
We are in Functional Upgradation.
How to Migrate the Objects( Infocubes,DSO,Datasources,Rules...etc...) from 3.1C to BI 7.0
Please help me to doing this....
regards,
anil

BW Upgrade tasks (BW 3.1C to BI 7.0)
Prepare Phase:
Task     How-To     Who
Review BI 7.0 feature lists     Review BI 7.0 feature lists for possible inclusion in developments.     Basis/BW
Obtain the BI 7.0 upgrade guide     Download the upgrade guide from http://service.sap.com/inst-guides -> SAP NetWeaver -> Upgrade
     Basis/BW
Review all upgrade SAP notes     In addition to the upgrade guide, check, download, and review all SAP notes for your upgrade
     BI 7.0 Upgrade notes
     SAP Web Application Server 6.40 upgrade notes
     OS and DB specific upgrade notes
     SAP BW Add-on upgrade notes
(e.g. SAP SEM, ST-PI, etc)
     Plug-In upgrade SAP notes
     Other notes identified in above notes and/or upgrade guides.
     Basis/BW
Check DB and OS requirements for the target SAP BW release     Check DB version/patch level and OS version/patch level required for upgrade
     First check the most current information from the SAP BW homepage http://Service.sap.com/BW -> <SAP BW release> -> Availability
     Additionally, the u201CPlatformsu201D link will take you to the main DB/OS page for BI 7.0 and SAP Web AS 6.40.
     Note: In some cases there are differing requirements for SAP BW 3.0B/SAP BW 3.1 Content and BI 7.0
     Basis
Check SAP BW Add-on upgrade requirements     Do you have SAP BW add-ons installed that require additional handling (e.g. SAP SEM, Enterprise Portal Plug-in, etc)?
     SAP SEM (SAP BW based components) requires SAP SEM 4.0 which is part of the mySAP ERP 2004 suite.
     WP-PI release must be at 6.00 before the upgrade begins. As mentioned before this add-on is merged with PI_Basis after the upgrade.
     Basis
Check SAP BW upgrade requirements          Minimum Support Package and kernel levels for upgrade
     SAP BW Frontend requirements for new SAPGUI, SAP BW BEx Frontend and SAP BW Web applications.
     Source system Plug-In requirements     Basis
Check compatibility requirements with 3rd party software          3rd Party Reporting tools (example: Crystal)
     ETL Tools (example: Ascential, DataStage, etc)
     Scheduling tools (example. Control-M, Maestro, etc)
     Monitoring tools (example: HP OpenView, Patrol, etc)
     Other OS or DB related tools     Basis
Check new component requirements for BI 7.0          If SAP BW web reports were developed in SAP BW 2.x, a windows version of IGS 6.40 (Internet Graphics Service) is required for conversion and future rendering of web graphics (i.e. Charts and GIS Maps).
The IGS chart migration will also be required after the SAP BW web report conversion.
     If you used or activated any SAP BW Web Applications in SAP BW 3.x, or if you have used charts in SAP BW 2.x web reports, you will need a windows version of IGS 6.40 (Internet Graphics Service) to execute the IGS chart migration after the upgrade.
     If ESRI GIS software is in use, a different version of ESRI software maybe required for BI 7.0. (ArcView 8.2?).
     If you plan to use Information Broadcasting, please review the requirement for additional infrastructure components such as EP, KMC, Workbook pre-calculation service, and Web AS connectivity to your mail servers.
Detailed information is available in the SAP NetWeaver u201904 master planning guide (http://service.sap.com/instguides -> SAP NetWeaver).
     Basis
Test and distribute new SAP BW Frontend
          Install and test the new BI 7.0 Frontend (including the new version of SAPGUI for Windows if applicable).
     A detailed FAQ on the new BI 7.0 Frontend is available on the SAP service marketplace alias BWFAQ (http://service.sap.com/BWFAQ).
     After successful testing, the new SAPGUI for Windows and SAP BW Frontend can be distributed to the BW teams and end users.
     Basis
Alpha Conversion:
Ensure that your InfoObject data is consistent from a u201Cconversionu201D perspective (Alpha Converter tool)      Check that you have executed the Alpha Converter tool to check the consistency of your InfoObject definitions and data for InfoObjects that utilize the ALPHA, NUMCV and GJAHR conversion exits.
Note: The Alpha conversion is not part of the SAP BW upgrade itself, but the upgrade simply checks to ensure you have successfully executed the check tool.
Transaction RSMDCNVEXIT
Check the system status:
     u201CAll Characteristics Have Correct Internal Valuesu201D: The Alpha converter has been successful executed. The upgrade preparation can continue.
     u201CNo Check yet/Inconsistent Internal Vales existu201D:
The Alpha converter check has not been executed.
     u201CCharacteristics have Inconsistent Internal Valuesu201D:
The Alpha converter tool check has been executed and data problems have been detected. The InfoObject and data must be processed before the upgrade can be started.
     BW
Upgrade SAP Note updates     Check for newer versions of your SAP notes for the Upgrade.
Tip: The SAP service marketplace offers an option to subscribe to OSS notes so you can be notified of changes when you log on.
     Basis/BW
Confirm SAP BW support package, kernel and DB/OS configuration     Analyze current Support Package and DB/OS/Kernel configurations in your SAP BW landscape in relation to the SAP BW 3.x upgrade requirements.
     Apply necessary support packages, kernel patches, and DB and OS patches to meet upgrade requirements
     Basis
Alignment of SAP BW objects within your SAP BW system landscape     Check and, where required, re-align SAP BW Objects and developments in your SAP BW system landscape (Development, Quality Assurance and Production).
SAP BW Object differences can impact the quality of testing in the Development and Test environment and can lead to change management issues.
     This check is to minimize risk and ensure productive objects are being tested prior to the Production upgrade.
Where alignment issues exist and realignment is not possible, alternative testing plans should be devised.
     Basis/BW
Confirm all developments are deployed.     Ensure that all SAP BW developments are deployed or they are to be re-developed/tested after the upgrade.
     In the DEV system, all SAP BW development transports should be released (i.e. transport created and released) and imported to all downstream systems (i.e. QAS and PRD systems).
For SAP BW developments not already collected in the transport collector, a decision must be made:
Deploy the developments or wait until the upgrade has completed to deploy.
o     Development to be deployed should be collected, released, and imported into the QAS and PRD systems.
o     Developments that should be deployed after the upgrade should be re-tested/re-developed after the upgrade.
     In the QAS or PRD systems, ensure that all SAP BW development transports have been imported prior to the upgrade.
     BW
Implement BI 7.0 Business Explorer Frontend     Install, evaluate, test and distribute the new BI 7.0 Business Explorer Frontend.
     Basis/BW
Pre-upgrade Process:
Download required BI 7.0 support package Stack for inclusion in the upgrade     Determine the equivalent support package level of the source SAP BW release and the target SAP BW release.
     There is a minimum requirement that you upgrade to at least the equivalent support package level on the target SAP BW release so that you do not lose functionality, corrections, and data.
     It is recommended to upgrade to the latest version of all support packages during the upgrade via the upgradeu2019s support package binding functionality.
     BI 7.0 Support Packages are delivered via SAP NetWeaver u201904 Support Package stacks (SP-Stacks). It is not recommended to partially apply some of the SP-Stacksu2019 individual support packages. You should apply all of the SP-Stacks support packages at once.
For more information on the SP-Stacks and SAP NetWeaver SP-Stacks, please see the SAP service marketplace alias SP-Stacks (http://service.sap.com/sp-stacks)
     You should also review, download, and bind in support packages for all add-on components that are installed on SAP BW and will be upgraded during the SAP BW upgrade (e.g. SEM-BW, ST-PI, etc)
     Basis
Apply latest Support Package tool patch     Apply latest SPAM patch before executing PREPARE     Basis
Validate the SAP BW (ABAP) Data Dictionary and the Database Data Dictionary for consistency     Check Database consistency
     Transaction DB02:
o     Execute ABAP SAP_UPDATE_DBDIFF and re-execute DB02 check. This gives a truer view of the SAP BW objects in DB02.
o     Check missing database objects (indices, tables, etc)
o     Missing indices may identify erred data loads or process problems
Tip: Missing indices on InfoCubes can be restored by RSRV or ABAP SAP_INFOCUBE_INDEXES_REPAIR
Note: check for running data loads before executing a repair!
o     Check DDIC/DB consistency
     Verify database objects and consistency
(e.g. SAPDBA check for offline data files)
     BW
Remove unnecessary SAP BW temporary database objects     Delete all SAP BW temporary database objects:
     Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
     This reduces the numbers of database objects that need to be copied during the upgrade.
     Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
     BW
Validate your SAP BW Objects for correctness prior to your upgrade     Using the SAP BW Analysis Tool (transaction RSRV), perform extensive tests on all important SAP BW Objects to ensure their correctness prior to the upgrade.
Note: this test should be repeatable so you can re-validate after the upgrade!
     Ensure that any inconsistencies are identified and corrected
     RSRV has a number of extensive tests and if all checks are executed will consume a large amount of time. Multiple tests can be performed in parallel.
     Tip: Some corrections in development can be deployed to other systems via transport in advance of the next upgrade.
     BW
Ensure DB Statistics are up to date prior to the upgrade          Check DB statistics for all tables.
Tables without statistics, especially system tables, can seriously impact upgrade runtimes.
     Check DB statistics for missing Indexes for InfoCubes and Aggregates
o     User transaction RSRV to check      BW
Check SAP BW Support Package status     Check the status of all support packages (via transaction SPAM)
     Ensure the Support Package queue is empty
     Confirm all applied Support Packages     Basis
Check all u2018Repairsu2019     Check for unreleased repair transports
     Release all unreleased transports
In your QAS and PRD system, check if all repair transports have been imported (i.e. systems are aligned)
     Import missing repair transports into down stream systems. This will avoid differing message and/or errors during the upgrade.
     BW
Check InfoObject status          Check for revised (modified) InfoObjects that have not been activated.
All InfoObjects should be active or saved (not activate):
o     Check all inactive InfoObjects:
Transaction RSD1 (Edit InfoObjects),
click on u201CAll InfoObjectsu201D radio button and click the u201CDisplayu201D button.
Modified InfoObjects are denoted by yellow triangles!
o     Determine if revision should be activated or removed.
     'Reorgu2019 or u2018Repairu2019 all InfoObjects
This checks and repairs any discrepancies in the InfoObject definition and structures. It is common to have obsolete DDIC and table entries for InfoObjects after multiple upgrades and definition changes. These obsolete entries normally do not effect normal SAP BW operations.
     Transaction RSD1 (Edit InfoObjects), Select u201CExecute Repairu201D or u201CExecute Reorgu201D Use expert mode for selective executions.
     BW
All ODS data loads must be activated.          Activate all inactivated ODS Object requests.
All ODS u2018Mu2019 tables must be emptied prior to the upgrade as a new activate process is implemented
o     Inactivated ODS request can be located via the Admin workbench -> u2018Monitoringu201D button -> u2018ODS Status Overviewu201D
     BW
All Transfer and Update rules should be active          Check for inactive Update and Transfer Rules
o     All update rules and transfer rules should be active or deleted.
o     Look into the table RSUPDINFO for update rules and search for the version "not equal" to "A". Likewise use the table RSTS for Transfer rules/structure.     BW
All InfoCubes should be active          Check for inactive InfoCubes and Aggregates (Aggregates are InfoCubes too!)
o     All InfoCubes should be activated or deleted.
o     Execute ABAP RSUPGRCHECK to locate any inactive InfoCubes. See SAP note 449160.
     BW
All Web Report objects should be consistent prior the upgrade.          Check the consistency of your SAP BW web objects (web reports, web templates, URLs, roles, etc). All objects should be consistent prior to web object conversion after the upgrade. It is recommended to ensure consistency before the upgrade.
o     For Original release SAP BW 3.x:
A SAP BW web reporting objects check can be executed via a new check in RSRV. This is provided via a SAP BW support package.
Please see SAP note 484519 for details.
     BW
Backup your system before starting PREPARE     Before execution PREPARE, perform a full database backup (including File system). Ensure you can recover to the point in time before PREPARE was executed.
     Database admin
Address any instructions/errors generated by PREPARE          Address any issues listed in log files Checks. Log generated by PREPARE.
o     Repeat PREPARE until all checks are successful.     Basis
Complete any Logistic V3 data extractions and suspend V3 collection processes          Extract and empty Logistics V3 extractor queues on SAP R/3 source systems.
o     The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss. V3 collector jobs should be suspended for the duration of the upgrade.
They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
     Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
     BW
Complete any data mart data extractions and suspend any data mart extractors          Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
o     The SAP BW Service SAPI, which is used for internal and u2018BW to BWu2019 data mart extraction, is upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the upgrade to avoid any possibility of data loss.
     Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
     BW
Check that your customer defined data class definitions conform to SAP standards          Check all customer created Data classes used by SAP BW Objects (i.e. InfoCubes, ODS Objects, Aggregates, InfoObjects, and PSAs) to ensure they conform to SAP standards.
o     Check your data class definitions as detailed in SAP Notes 46272 and 500252.
o     Incorrect data classes could create activation errors during the upgrade.
     BW
Remove unnecessary SAP BW temporary database objects     Delete all SAP BW temporary database objects:
     Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
For more information see SAP note 308533 (2.x) and 449891 (3.x).
     This reduces the numbers of database objects that need to be copied during the upgrade.
     Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
     Basis/BW
Backups!     Before executing the upgrade, ensure that you have a backup strategy in place so you can return to the point where loading was completed and the upgrade started.
Ensuring you can return to a consistent point in time (without having to handle rollback or repeats of data loads) is key to having a successful fallback plan.
     Database Admin
Before Execution:
All SAP BW administration tasks should have ceased          Cease all SAP BW administration tasks such as Object maintenance, query/web template maintenance, data loads, transports, etc at the beginning of the upgrade.
The Administrators Workbench and the Data Dictionary are locked in the early phases of the upgrade.
     Reminder: Users can execute queries until the time that the upgrade determines that the SAP BW System should be closed*
- timing depends on the type of upgrade selected
     Basis/Admin
Remove unnecessary SAP BW temporary database objects     Repeat the deletion of all SAP BW temporary database objects after you have stopped using the SAP BW Admin workbench*
     Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
For more information see SAP note 308533 (2.x) and 449891 (3.x).
- timing depends on the type of upgrade selected
     BW
Check system parameters     Check OS, DB, and Instance profile parameters.
     Check System Instance parameters for new BI 7.0 specific parameters. See SAP note 192658 for details
     Check for any DB specific parameters for BI 7.0
     Check for any new OS parameters     Basis
Check Database archiving mode     Turn database archive log mode back on if it was disabled during the upgrade!
     Database Admin
After Execution:
Check the systemu2019s installation consistency     Execute Transaction SICK to check installation consistency
     BW
Check the system logs     Perform a technical systems check.
     Example: Check system and all dispatcher logs (inc. ICM logs)
     Basis
Apply latest executable binaries     Apply the latest 6.40 Basis Kernel for all executables
     Tip: use the SAP NetWeaver u201904 SP-Stack selection tool to find all binaries. (http://service.sap.com/swdc)
     Basis
Review BI 7.0 Support Packages for follow-up actions.          Review SAP Notes for all SAP BW Support packages applied during (bound into the upgrade) and applied after the upgrade:
o      Search for Note with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
o     Follow any required instructions identified in the SAP Notes
     Basis
Apply latest patches          Apply the latest SPAM patch
     Apply any required support packages that were not bound into the upgrade.
     Basis
Apply additional BI 7.0 Support Packages
(if required)          SAP recommends that customer remain current on SAP Support Packages.
     Review SAP Notes for all SAP BW Support packages applied in previous task.
o      Search for Notes with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
o     Follow any required instructions identified in the SAP Notes
     Basis
Resolve any modified SAP delivered Role issues      If SAP delivered Roles were modified, then these modifications may incorrectly appear in the upgrade modification adjustment tool (SPAU).
     Review and implement SAP note 569128 as required     Basis
Configuring Information Broadcasting EP/KMC Connections
     If you plan to use the EP integration functionality of Information broadcasting (Broadcast to the EPu2019s PCD, Broadcast to KMC, or Broadcast to Collaboration Rooms):
     Ensure the SAP EP is at the same SP-Stack level as your SAP BW system.
     Follow the online help documentation to configure and connect the SAP BW system and the SAP EP system. (http://help.sap.com).
     For broadcasting to KMC, ensure that KM has the u2018BEx Portfoliou2019 content available.
     Basis
Re-check SAP BW Object and consistency     Execute RSRV to check SAP BW Object consistency
     Repeat tests that we executed prior to the upgrade.
     Validate results      BW
Check InfoCube views for consistency     Check consistency of InfoCube fact table views
     It is possible that fact table view /BIC/V<InfoCube>F is missing if a number of SAP BW upgrades have been performed before. See SAP Note 525988 for instructions for the check and repair program.
     BW
Perform SAP BW Plug-in (SAPI) upgrade follow-up tasks          If required, Re-activate the SAP BW u201CMyselfu201D source system in SAP BW.
     The SAP BW internal plug-in (SAPI), which is used for internal data mart extraction and u2018BW to BWu2019 communication, is upgraded during the SAP BW upgrade. The source system is de-activated to prevent extractions and loading during the upgrade.
     It may be required to replicate export DataSources and reactivate transfer structures/rules for internal data loads (i.e. ODS Object to InfoCube objects).
o     Tip: It is advised to do this step for all export DataSources to avoid possible errors during execution of InfoPackages
     Check that all other Source Systems are active.
o     Activate as required.     Basis/BW
Check SAP BW Personalization is implemented     (SAP BW 2.X upgrades will have performed this in the previous task).
Validate that personalization has been activated in your SAP BW system.
Note: It has been observed that in some cases, BEx Personalization has to be re-activated after an upgrade from SAP BW 3.x to BI 7.0. It is advised to check the status of personalization after the upgrade.
     Enter the IMG (transaction SPRO), select SAP Business Warehouse -> Reporting relevant settings -> General Reporting Settings -> Activate Personalization in BEx
Check the status of the Personalization settings. All entries should be active u2013 highlighted by an unchecked check box.
     To activate highlighted Personalization, click Execute.     BW
For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
Convert ODS secondary indexes to new standard     For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
Convert any customer created ODS Object secondary indexes to the new ODS Object index maintenance process.
     Re-create all indexes in the ODS Object definition screen in transaction RSA1.
     ODS indexes must conform to the new naming convention
     BW
Converting IGS chart settings
     Convert you existing IGS chart settings (converts IGS chart settings from BLOB to new XML storage format)
     Ensure you have the latest SAP Web AS 6.40 IGS (stand alone windows version) installed and working
o      Test via transaction RSRT
     Execute the conversion process as directed the BI 7.0 upgrade guide.
     Note: This step is required for all BI 7.0 upgrades     Basis
Backup your SAP BW system     Perform a full database backup (including the File system)
Remember to adjust your backup scripts to include new components such as the J2EE engine, pre-calculation service, etc.
     Database Admin

How to migrate source code from TFS 2010 to a new TFS 2010

Hi,
Please help me, How to migrate source code from TFS 2010 to a new TFS 2010. we are using SQL 2008 R2 for DB storage and we have Backup of TFS DB. First TFS 2010 is live environment and second TFS 2010 is test environment both OS and SQL version is same.

Hi Pankaj0439,
In general, to move TFS from a hardware to another, you can follow the steps as below:
1. Check your permissions
2. Back up databases and install software
3. Restore TFS databases to the new hardware
4. Update the configuration of the new application-tier server
5. Verify permissions, notify users, and configure backups
And you can also refer to this
article in MSDN for more details.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

How to migrate ESS job from one instance to another Instance ?

Hi Experts,
We have developed some custom ESS jobs in fusion applications. Now we have to migrate newly created ESS jobs to another environment.
Is there any way like we use to extract ldt in EBS R12.
Kindly suggest......!
Thanks,
Praveen

Please refer to:
How to Migrate ESS Job Definitions Using WLST (1941788.1)
Migrating Ess Job Definitions From One Instance To Another Instance (1442541.1)
Jani Rautiainen
Fusion Applications Developer Relations
https://blogs.oracle.com/fadevrel/

How to migrate changed Business Scenarios from Template Project to Solution

SAP Solution Manager - How to migrate changes in Business Scenarios from Template Project to Solution?
Our Global ASAP strategy is based upon a Template Project, Implementation Project, Maintenance Project and Solution with Business Scenarios.
Changes in the Template Project for existing and new Business Sceanarios, etc. are correctly executed. Up till now we have successfully implemented our Template Project and secondly extended our Business Scenarios from 4 to 14. Our 3rd upcoming change will be changes on Business Scenarios as well. These planned changes for the Business Scenarios need to be consistent, possibly without manual intervention.
During a Proof of Concept (PoC) in our Sandbox (SXB) we have identified a possible serious problem when trying to publish these changes in Business Scenarios in the Template Project to the Solution. SAP Solution Manager (SSM) does not seem to support a scenario where Business Scenarios in the Solution can be refreshed or updated with changed Business Scenarios in the Template Project.
We have identified 2 possibillities:
1.     Manual project upgrade
1.1.     Synchronize the changes for the Template Project normally;
1.2.     Delete the changed Business Scenarios from step 1.1 in the Solution;
1.3.     Add the changed Business Scenarios from step 1.1 into the Solution.
For this scenario we foresee a big problem because all Content and Issues connected to the old Solution Business Scenarios loose their coupling with the Solution.
For the Content this may not be a real problem because the Content is also available in the Template Project.
However the Issues are loosely coupled to the Solution Scenarios and therefore need to be coupled manually to these processes.
2.     Manual changes using Maintenance Project
2.1.     Synchronize the changes for the Template Project normally;
2.2.     Publish all changes from step 2.1 in the Template Project
2.3.     Add all new Content from step 2.1 to the structure of the Maintenance Project;
2.4.     Relocate Content and Issues when the Business Scenario has been relocated.
Because SSM does not support this activity we need to delete this Business Scenario first and secondly re-create it again on the correct spot.
Our question: How has SAP done this in other customer projects?
We need to have a working solution by the end of March, 2009.
Best regards,
Peter Hendriksen

Peter,
Did you get an anwer to this question from SAP?
Rgds,
Eamonn.

How to migrate Stellent 7.5.1 custom layout component to OCS 10gR3

Similar Messages

Maybe you are looking for