How to migrate netscape messaging 4.15 to iplanet messaging 5.2 on solaris

How to migrate netscape messaging 4.15 to iplanet messaging 5.2 on solaris. Any guide is available ?

Hi,
Below given is the Migration guide from iPlanet. Follow the instructions given carefully. Also, you would like to check out the Release notes for any known gotchas.
http://docs.sun.com/source/816-6017-10/single.htm#44598
Regards,
Preethy

Similar Messages

How can i migration netscape messaging 3.6 mailbox to iplanet messaging 5.2 mailbox

how can i migration netscape messaging 3.6 mailbox to iplanet messaging 5.2 mailbox

Once you have created all the users on the directory, you can use mboxutil and deliver, to copy the mails from one box to another. I have done this twice, but I can't send you the scripts for a legal problem.
If a user on the NMS3.6 use pop, there is only a folder called uid/inbox, with something like:
./uid/inbox/__VALIDITY__
./uid/inbox/__lock__
./uid/inbox/__deliver__
./uid/inbox/__GENNAME__
./uid/inbox/__highest__
./uid/inbox/20020106172021.AAA.4ce2af5a
./uid/inbox/20020106215444.AAA.4ce2af5a
./uid/inbox/20020106232803.AAA.4ce2af5a
./uid/inbox/20020106233026.AAA.4ce2af5a
All the files that begin with _ are useless. And the files like 200... are the emails. So you have the uid, and the files that you have to copy.
To deliver an email to a user, that user MUST have a mailbox. So first you have to create the mailbox, through execute "mboxutil -c user/uid/INBOX", after that you can copy the email using, "deliver -m inbox uid < ./uid/inbox/20020106172021.AAA.4ce2af5a".
You can use a script to first create all the mailboxes, after that you can deliver all the emails.
If your users use IMAP, then they can have differents folders, the idea is the same, first create all the folder(always create the INBOX first), in the _MAILBOX.LST file there is a list of the folders of every user.
Best regards
eos no mas

Migrating from Netscape Messaging Server 4.15 Plug-in to iPlanet Messaging Server 5.1 Channel

Hi, there.
I wrote a custom plug-in for Netscape Messaging Server 4.15. The client for
whom I did this is now upgrading to iPlanet Messaging Server 5.1 and has
requested that I update the custom plug-in accordingly. Unfortunately, as
specified in the iPlanet migration documents, you have to re-code the
plug-in as a channel to get it to work under iPlanet Messaging Server...
I've scoured the documentation about how to go about doing this, but I don't
know how to get started as I don't know anything about writing a channel.
The plug-in processes incoming messages to see if they were sent from a
specific domain. It then adds an arbitrary signature to each appropriate
MIME part in the message before letting the messaging server relay it.
1. Can anyone direct me to some explicit directions about how to write a
channel for iPlanet Messaging Server? The documentation for Netscape
Messaging Server was extremely helpful; I haven't found anything equivalent
for iPlanet channels.
2. Channels run as daemons? Do you have to start them when the machine
boots, or are they started for you by the MTA as a result of the channel
configuration file?
3. Do channels listen with sockets on a particular port for communication?
Do I have to parse incoming data and encode outgoing data as if it was an
SMTP communication?
4. Can an SMTP channel co-exist with other SMTP channels on the same
machine? Do the channels have to listen on unique ports? (Sorry, my socket
programming is a little rusty.)
Anxiously awaiting your reply...
Sean Dockery
[email protected]

What is the expected result of the plug-in?
Also, if you set the smtp log level to debug do you see it initializing the plugin at startup time and also entering the plugin during the smtp-accepts?

How to Migrate NMS 4.1 to IMS 5.1

Hi all,
At present I am using Netscape messaging server 4.15 SP6. I want to upgrade to IPlanet Messaging server 5.1.
How can I do to upgrade? Which tool using to migrade from Netscape messaging server 4.15 SP6 to IPlanet Messaging server 5.1?
Thanks.

Hi,
Firstly, can you please clarify that you intend to upgrade to iMS5.1?
I should point out that iMS5.1 went out of support years ago, iMS5.2 is going out of support next year, so if you are going to upgrade I would recommend going to 2005Q4 (or if you can hold off until early next year, 2006Q4 which has a much nicer architecture and other feature).
There are migration guides on docs.sun.com for going from NMS4.15 -> iMS5.2, and then iMS5.2 -> 2005Q4. To be perfectly honest, you would be best building a new system from scratch, and migrate users across one at a time, that way you can have a nice staggered migration.
There are a number of discussions in this forum on migrations which you should look at.
Regards,
Shane.

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

Best Practice to migrate existing Message/Central Instance to new hardware?

I've done some searching for this, but it all seems to be fairly old (I found one decent thread from 2008, but it just seemed outdated). I would like to get some updated info & suggestions on a process to follow for this task.
Here is some info about the current config:
I have an existing SAP ERP 6.0 EHP5 system. SID "XYZ"
Everything is currently running on Windows x64.
ABAP only config.
It is currently setup as a distributed system.
DB server is SQL, which is running on its own hardware as a dedicated DB server. I don't need to touch this.
Uses logon groups to distribute the load between 3 App servers.
One of the App Servers is setup as the Message/CI server. This is what I am wanting to move to VM hardware.
The other two App Servers are setup just as Dialog Instances. VM already. I don't need to touch these.
What I am wanting to do:
I am wanting to migrate the existing Message/CI server to VM hardware to get the current Message/CI system off of very old hardware.
I need to keep the system with the same name & IP.
I do not need/want to mess with the DB server at all.
Need to minimize downtime as much as possible.
I do NOT want to go to an HA environment. That is a different project for the future.
Suggestions? I would like to hear what some of you have done.
Minimize downtime? I have a short maintenance window of a few hours coming up in the next few months, and would like to do this changeover during that downtime.
How do I handle setting this up on the new hardware using the same name & IP, especially with the existing system still running.
What I think I need to do: (Some of these may be out of order, which is why I'm asking for suggestions)
Setup new Windows VM server, named differently than current Message/CI server (Done already).
Run SAPINST to run Global Host Preparation on the new Windows VM server.
Run SAPINST to setup ASCS Instance on the new Windows VM server.
Skip the Database Instance installation, since I already have one running.
Run SAPINST to setup Central Instance on the new Windows VM server.
Copy all of the appropriate profile parameters that were on the old server.
Start SAP and make sure everything is running and working correctly.
Copy all job, spool files, etc. from the old server.
What needs to be done in between those steps for the server rename & IP changes?
Which of these steps can I do in advance of my maintenance downtime window, without it affecting the currently running system?
I have a test environment that I am going to test this with. I'm just trying to get a jump start on my instructions, so that I can hopefully do this quickly and easily. I'm very comfortable doing the installs. Just needing some guidance on how to handle this case.
I'm open to suggestions, and any links you can send my way that show some more recent success at doing this. Everything I keep finding talks about doing the migration for the DB. I am not migrating my DB. It is staying where it is. I'm just wanting to migrate my Message/Central Instance to a VM, without affecting the users, and hopefully them never noticing the changes.
Thanks!

If you're using VMWare, there is a tool provided to virtualize existing systems. Basically it makes a copy of the old system (while it is down) and recreates it as a VM with the same name, IP, etc. I haven't double-checked to see if this process is 'officially' supported by SAP, and I don't know the technical details about how it's done or how long it will take (VMWare is managed by the Network Operations group in my team, so as the SAP sysadmin I'm basically a customer of theirs). However, we have virtualized a few smaller systems that needed to get off failing hardware in a hurry and it worked very well, so I would expect it would for an SAP dialog instance as well. As you're not copying a database, just the app server, it probably would fit within your maintenance window.
If this route works for you, then there is no need to actually install the SAP system on the VM instance... you just copy the old server as-is, then make any adjustments required due to no longer needing old drivers, etc, plus potentially having different memory parameters.

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 migrate address book in outlook express to PAB?

How to migrate address book in outlook express to SUN messages server 's PAB?
Use any LDAP command ?
Thanks!

We provice no supported technique for this.

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 Business Partners?

Hi All,
How to migrate Business Partners from one Solution Manager to another?
Both Solution Managers are 7.0 SPS 17.
We have already move users and roles.
It looks like that we loose messages from projects when we try to migrate them with SOLAR_MIGRATION because of the missing Business Partners.
Thanks & Best Regards,
Leif Pedersen

Hello Leif,
I have the same problem. Did you figure it out?
thanks,
Ingrid

Migrating from messaging direct -- problem with read messages

Folks,
We are migrating from messaging direct's mail server. What I am doing is tar'ing up a user's account,moving it to the new server and untar'ring it. I them use mboxutil to create the folders and then make the '00' directory and number the messages appropriate and move then in. Then I run reconstruct on the mailbox and it works great. The problem is that all the messages are now unread. How do I make them read again???
keith

I had to do a similar migration from a different mail server. I migrated the messages to each user via IMAP, using a Perl script.
The Perl script would determine a few message states and set the IMAP flags appropriately.
I don't recall seeing anything in the docs about setting message states directly. However, in your case, it appears you already have the messages in seperate files. You could try loading via IMAP and setting the flags. I used the NetxAP perl module from CPAN. An alternative, there is an import utility for iMS2. I haven't used it, but you could convert the mail to UNIX mbox format and then load into iMS52.
HTH,
Roger S.

How to migrate Themes, HTML templates, MIME objects to ECC6.0

Hi Friends
How to migrate Themes, HTML templates, MIME objects which are developed in SAP Web@Studio.
or How to use program SIAC_UPLOAD ??
regards
siddharth

Hello Murray,
Your steps sound correct. I would add that you generally need the following:
1. publish the IAC, SYSTEM, and WEBGUI Internet Services (also from SE80)
2. make sure the Integrated ITS is working. Meaning you should activate the ITS in the profile parameter, this can be seen in transaction SITSPMON. Some services in transaction SICF also need to be activated, like the default_host/sap/public/bc/its
From your error message though it looks like the URL you have used is either incorrect or you have used the External Alias feature in SICF? The URL for the ITS is usually http://host:port/sap/bc/gui/sap/its/service. Second, the error is about a language resource file (.htrc), you have not specified if you created one or not. To create one in the language you are logged in with just go to SE80, open your Internet Service and double click on the "Topic xx". Don't forget to publish after creating and saving it.
Edgar

Migrating Support Messages from Maintenance project

We have an implementation project created in 3.2 and we have created messages in project using solar01 txn. we are planning to move to solman 4.0.
Will migrating projects using Solar_migration migrate the messages created under the implementation projects?.
how is Project system landscape migrated ( any impacts using solar_migration) ?.
Can system landscape description ( SMSY) be transported ?.
Please provide any inputs you have...

Hi,
If you want to migrate with data follow this procedure
You have to the data export option Customizing Distribution in the transaction Solution Manager Migration, to migrate all existing distributions from the old Solution Manager system into the new one, (SOLAR_MIGRATION).
Also check this very good link.
http://help.sap.com/saphelp_sm40/helpdata/en/ba/ad93404f673028e10000000a1550b0/content.htm
Feel free to revert back.
--Ragu

Help Pls, How to display feedback messages to the user on 10.1.3

Hi, can anybody explain how to use the <html:messages> tag and the SaveMessages( request , ActionMessage ) on an 10.1.3 ADF application?
There is not such a logic on the ToyStore sample and my requests for help on this thread "Internal Error" on saveMessages(...) has been ignored ....
Omar

Chris,
The following thread should give you some insight on how to migrate your 10.1.2 Struts + ADF application to 10.1.3: reportErrors(PageLifecycleContext ctx) not called
If you are not ready to migrate, you can also develop in JDeveloper 10.1.2 and deploy to 10.1.3. The documentation to do so should be available shortly.I will repost when it becomes available.

How to migrate oracle 9i to oracle 10g

Hi,
Kindly provide how to migrate database from oracle 9i to oracle 10g.

Oracle change their words.
MIGRATE was used to open the database until 9i to upgrade/migrate the database to a higher version/release.
UPGRADE is used to open the database from 10g to upgrade/migrate the database to a higher version/release.
Well, lexical issue. Generally speaking, we migrate the data, but upgrade the database (the core/software).
Nicolas.
PS : upgradation is not the proper word for upgrade.
Message was edited by:
N. Gasparotto

How to migrate netscape messaging 4.15 to iplanet messaging 5.2 on solaris

Similar Messages

Maybe you are looking for