How to migrate the Workbooks from BW3.1 to BI7

Dear Team,
How to Migrate the workbooks from Bw3.1 to BI7. We have recently upgraded to BI7. What are necessary steps and necessary cares needs to take for this.
Best Regards,
SG

Migration is manual. When you open up a 3.x component in a 2004s tool in migrates it. There is no automatic migration available
Rolling out the New SAP NetWeaver 2004s BI Frontend Tools
Migrating Advanced BEx Analyzer Workbooks - What VBA is Supported?
Hope it Helps
Chetan
@CP..

Similar Messages

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 the data from DB to another DB

Hi folks,
             In my project I have one requirement. Let me explain in detail we are maintain two databases one for
             master database called *GIIS* and one is history database HIST. Both DB version is 10g R1.
             (Both DB’s have same no table as well structures)
             1. The GIIS database contains nearly 400 tables (master table as well as temporary table)
                   each Master table having it’s own temporary table.
             2. Whenever we made the entry first it will go to temporary table after authorized that entry it will move to the master table
             3. But the temporary table contains the data after move to master table .
             4.     The temporary table data’s will be move to the HIST database each and every day at the night.
                This migration we done through the procedure. After migration complete the temporary table data’s will de deleted.
My Question:
           1.     Whether it’s good practice to migrate the data from GIIS DB to another HIST DB using oracle stored procedure.
                 (we created the DB link from GIIS to HIST)
           2.     If not can any one suggest me the way to migrate the data from GIIS to HIST.?
           3.     Is there any other possibility to migrate the data from GIIS to HIST with out using procedure?Thanks
Arun

Arun wrote:
Hi Mr.Aman Brother
First of all sorry . I am not saying that don't command my requirement. Just i want know the way of migrate the data from one DB to another DB.
you saying that IMPORT/EXPORT is one of the way to do migration.
But in client side they don't know how to do the IMPORT & EXPORT the database..
Can you suggest me the another way to do that
Arun,
If the client doesn't know how to do exp/imp, I would really doubt and would be immensely concerned before suggesting the client any other way. If they don't know, tell them that there is a concept called test database which is used for learning so they should invest time to learn this technique since the other options suggested by fellow members are far more tougher than this one.
Aman....

How to migrate the data from DEC RDB 5.1 to Oracle 11g

Hi,
As part of my project, we need to migrate the data from DEC RDB 5.1 present on Alpha server with VMS 6.1 OS into Oracle 11g. The size of the data in DEC RDB is around 40 GB.
Could you please suggest various ways of getting this done in easy and simpler way?
Thanks in advance.

Hello,
when Oracle bought Rdb from Digital Equipment Corporation (DEC) in 1994, the name of the product changed from DEC Rdb to Oracle Rdb. Meanwhile the actual version of Rdb is 7.2, so you are on a VERY old version. And that excludes the suggestions from the mentioned note to use a database link from Oracle RDBMS to Rdb, that is simply not possible with that old version of Rdb.
But Rdb 5.1 knew already the Rdb Management Utility (RMU) - I just checked that with Rdb 4.1 which is even older.
There are two commands that are helpful for your task.
RMU/EXTRACT - that writes the metadata into a file. That output helps you to build a script to create all the objects in your target database.
RMU/UNLOAD - that writes the data of each table into a formatted file (one file per table). That output can be used by the SQL*Loader to load your data into the target database.
You can read all details about these commands in the online help on your Alpha. At first, issue the HELP command and look in the output list whether it lists a command RMU or RMU51. Then run that command:
$ help rmu /extract
and
$ help rmu /unload
Replace rmu by rmu51 if the help command shows you that rmu51 exists but not rmu.
There is one caveat. Do you use blobs in your Rdb database? If you don't know that, create an the output with RMU/EXTRACT and search the output file for the string LIST OF BYTE VARYING. If there are none then you have no blobs. If you have some you need to take more care of them, they can't be unloaded into a formatted file, that must happen programmatical. If you have such fields then let me know, then I'll tell you how to get them out of your Rdb database.
Best regards
Wolfgang
P.S.: For Rdb related questions it is better to ask in our Communities at https://communities.oracle.com/portal/server.pt/community/rdb_product_family_on_openvms . That forum is watched by Rdb Support and Development.

How to migrate the portal from server A to Server B

Dear Expert,
I have existing R3 name A and portal connecting. I have setup a new R3 name B on different server. Could you please provide me the steps on how can I migrate the portal connection from Server A to Server B. What are the steps involve .e.g. ITS and etc.
Thank you
KS

Hi,
The communication between portal server and R3 server happens via system only. If you don't want to use R3 system A hereafter, then look for R3 system alias created for 'A' in portal. You can delete that. Now for using new R3 system B in portal, create a new system for B in portal using System Administration. Decide which SSO you are going to use. If user is same in portal and r3, then logon tickets. Else user mapping method.
Check these documents on how these can be done.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/howtoConnecttoSAPR3SystemthroughEnterprisePortal7.0Usingan+iView.
Connecting To R/3 From Portal
Configuring EP for connecting to SAP R/3
Regards,
Harini S
Consider rewarding points for helpful answers

How to migrate the datasource from Bea 8.1 to Bea 10

Hi,
I have to migrate an application from bea 8.1 to 10.
the configuration in 8.1 is as follow : (config.xml)
<JDBCConnectionPool DriverName="oracle.jdbc.driver.OracleDriver"
InitialCapacity="10" KeepXAConnTillTxComplete="true"
MaxCapacity="150" Name="adiosPool" Password="adios47"
Properties="user=adios47"
RemoveInfectedConnectionsEnabled="false"
ShrinkFrequencySeconds="600" StatementCacheSize="100"
SupportsLocalTransaction="false" Targets="server"
TestConnectionsOnCreate="false" TestConnectionsOnReserve="true"
TestFrequencySeconds="60" TestTableName="SQL SELECT 1 FROM DUAL" URL="jdbc:oracle:thin:@AXHE0.application.hvb.de:1521:AXHE0"/>
<JDBCTxDataSource JNDIName="weblogic.jdbc.jts.adiosPool"
Name="adiosPool" PoolName="adiosPool" Targets="server"/>
and that is my new configuration : (config.xml)
<jdbc-system-resource>
<name>adiosPool</name>
<descriptor-file-name>jdbc/adiosPool-0758-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
jdbc/adiosPool-0758-jdbc.xml :
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
<name>adiosPool</name>
<jdbc-driver-params>
<url>jdbc:oracle:thin:@AXHE0.application.hvb.de:1521:AXHE0</url>
<driver-name>oracle.jdbc.OracleDriver</driver-name>
<properties>
<property>
<name>user</name>
<value>adios47</value>
</property>
<property>
<name>portNumber</name>
<value>1521</value>
</property>
<property>
<name>SID</name>
<value>HVAEE0</value>
</property>
<property>
<name>serverName</name>
<value>AXHE0.application.hvb.de</value>
</property>
</properties>
<password-encrypted>{3DES}PMWtUXqoHT8=</password-encrypted>
</jdbc-driver-params>
<jdbc-connection-pool-params>
<test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
</jdbc-connection-pool-params>
<jdbc-data-source-params>
<jndi-name>weblogic.jdbc.jts.adiosPool</jndi-name>
<global-transactions-protocol>TwoPhaseCommit</global-transactions-protocol>
</jdbc-data-source-params>
</jdbc-data-source>
but when I start the server I get the following exception :
START SERVER
javax.naming.NameNotFoundException: While trying to lookup 'weblogic.jdbc.jts.adiosPool' didn't find subcontext 'jdbc'. Resolved 'weblogic'; remaining name
'jdbc/jts/adiosPool'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:246)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:213)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
what's wrong ?
Thanks for your ideas

Hi,
This is realated to Upgrading your domain.You can upgrade your domain from bea weblogic8.1SP4 to Bea weblogic 10.You need to use the upgrade tool from bea weblogic platform10.You can start the Upgrade wizard tool from Windows Start->All Programs->BEA Products->Tools->DomianUpgradeWizard.The tool will take you to upgrade the domain automatically.Once you have upgraded the domian everything(database connection pools,users,groups,any other resources) in 8.1 domian will be changed to 10.
Bea Support Complete upgradation of Application as well as application data from 8.1 to 9.2 or 10.0
Thanks
Bishnu
Regards
Bishnu

How to migrate the computers from SCCM 2007 to SCCM 2012

Hello,
Could anyone tell me how to mirgrate the computers present in SCCM 2007 to SCCM 2012.
Does the "collection migration" job migrate the computers or devices present in the collection? I tried this but computers were not migrated.
Should we again discover the computers in SCCM 2012?
Thanks,
SreehariG

There is no migration job in CM12 that will migrate CM07 clients. You need to install CM12 agent on your CM07 client in order to migrate them. During the installation the existing CM07 client will be uninstalled. You can use any supported
client deployment methods to migrate to your new CM12 environment. More information here:
http://social.technet.microsoft.com/Forums/en-US/configmanagermigration/thread/71175a47-22fe-4284-871c-834c0c999075

How to migrate the data from on version to another version in SAP

Hai,
Now iam working in Upgradation and Data migration Project. Iam new to this Project. My problem is we have the data of one module in 4.7e and we want that module data into upgrade verion say ECC 6.0. But we didnt want to upgrade that module. Pls guide me in this.

hi,
Welcome to SCN.
if you want data of specific module to be transported to different version then you can use BDC,LSMW or BAPI for the transactions of that module according to your requirement.
Also if you search in SCN with migrate data to different version you will get lot of posts.

How to Migrate the database from AIX 4.3 oracle 7 to another Aix 5.3

Hi,
This is the scenario.
Oracle 7 runs in AIX 4.3 now the client wants to upgrade to a new machine with
oracle 10gr2 in AIX 5.3 .
AIX 4.3 in production now.
AIX 5.3 and oracle 10gr2 installed now.
is there any other possibility other than export to migrate to new server.
Regards
Elamaran

Sorry to disappoint you :( It's the same thing as with my car - If it's not without fuel I turn the key and drive ;)
Confined to the development database instance, writing packages is the only thing I'm allowed to do (even forbidden to use some of the Oracle supplied ones).
There are other guys having to do the rest.
Regards
Etbin

How to Transfer the Data from ORACLE APPS to SAP

Hi Gurus,
Here are my couple of quieries regarding Data Migration from Legacy(Oracle Apps) to SAP.
1. How to link between Legacy system(ORACLE APPS) and SAP ?
2. How to migrate the data from Oracle tables to SAP directly, instead of loading the flat files(.txt, .xls) ?
Please respond to my queries ASAP.
Thanks,
SAPSURE.
Edited by: sapsure on Sep 9, 2010 11:39 AM
Edited by: sapsure on Sep 10, 2010 2:32 PM

1. How to link between Legacy system(ORACLE APPS) and SAP ?
        If you have SAP PI in place then you can interact with oracle database tables directly from PI and then data can be posted to SAP transactions through IDocs/BAPIs.
        If you did not have SAP PI still you can do JDBC connection directly from ABAP program. Not sure about the exact steps check in forum.
2. How to migrate the data from Oracle tables to SAP directly, instead of loading the flat files(.txt, .xls) ?
        If you want to directly post the data SAP transactions (I hope not directly to SAP tables) then connection needs to establish through ABAP program or Via. PI.
Regards,

Using i-setup, how to migrate EBS configuration from one Business Group to the other within the instance?

Using i-setup, how to migrate EBS configuration from one Business Group to the other within the instance?

Sandeep,
Yes, I think your command format is not correct.
Try the one that Rod posted.
About the note on metalink. It seems that it is under review.
Here is the basics of the note:
1. Determine the owner of the workbook. Say UserA.
2. Open an sqlplus session to the database.
3. Run the following sql:
SQL> set heading off
SQL> set feedback off
SQL> set echo off
4. Now spool the result of the following sql to a file.
SQL> spool c:\exp.bat
5. Run the sql statement
NOTE: CHANGE DISCOE_HOME
SQL>select '<Disco_Home>\discvr4\dis4adm /connect
EUL_owner_name/passwd@connect_string /export c:\'||rownum||'.eex /workbook "'||
doc_created_by||'.'||doc_name||'"' from
SELECT EUL4_DOCUMENTS.DOC_NAME, doc_created_by, NVL(EUL4_EUL_USERS.EU_USERNAME,
'Document Not Shared') shared_with
FROM EUL4_ACCESS_PRIVS EUL4_ACCESS_PRIVS, EUL4_DOCUMENTS EUL4_DOCUMENTS,
EUL4_EUL_USERS EUL4_EUL_USERS
WHERE ( EUL4_DOCUMENTS.DOC_ID = EUL4_ACCESS_PRIVS.GD_DOC_ID(+) ) AND (
EUL4_EUL_USERS.EU_ID(+) = EUL4_ACCESS_PRIVS.AP_EU_ID )
where doc_created_by='UserA'
where,
Disco_Home is the Location or Discoverer 4 Home.
4. SQL> spool off
5. SQL> set feedback on
6. Now run the batch command file (exp.bat)
Regards
Roelie Viviers

I recently bought a MacBook Air. I migrated the info from my old MacBook to the new Air. None of my contacts migrated. I still have them on my old Macbook, Ipad and iPhone. How do I get them to the new Air?

I recently bought a MacBook Air. I migrated the info from my old MacBook to the new Air. None of my contacts migrated. I still have them on my old Macbook, Ipad and iPhone. How do I get them to the new Air?

You can copy the iWeb application from the desktop machine to your new MBA. But if it's iWeb 2 it won't work with Mavericks or Mt. Lion. Also copy the Domain.sites file from the desktop to your MBA as that's the file with your webstite files in it.
Happy New Year

How to migrate the RPD and catalog file from siebel analitics to obiee

hi all
How to migrate the RPD and catalog file from siebel analitics to obiee and obiee to obiee 11g
Thanks
Sreedhar

hi sreedhar,
you can migrate from siebel to obiee 10g...check this out http://debaatobiee.wordpress.com/tag/migration-siebel-analytics-obiee/
Next install OBIEE 11g and migrate obiee 10g to 11g using this http://prolynxuk.com/blog/?p=424
hope answers your questions.
Cheers,
KK

How to migrate the data flow from DB CONNECT sourse system from 3.5 to BI

Hi
can any one tell me how to migrate the data flow from DB CONNECT sourse system from 3.5 to BI 7.

Hi,
Go to Infoprovider to which your DB connect DS feeds and Right Click on Data source-> Then Migrate-> With Export---> You have to build new 7.0 Transformations and DTP's etc.
~AK

How to migrate the concurrent managers definations from one instance to another

How to migrate the concurrent managers definitions from one instance to another instance by using FNDLOAD in R12.1.3
Greatly appreciate any help on this.
Thanks!

Concurrent managers can't be migrated using FNDLOAD -- Tips and Examples Using FNDLOAD (Doc ID 735338.1)
What are you trying to achieve here? Why migrating CMs from one node to another?
Thanks,
Hussein

How to migrate the Workbooks from BW3.1 to BI7

Similar Messages

Maybe you are looking for