How to migrate my test work to TFS

Right now, Use Enterprise Tester to run the test cases and submit bugs and use Jira and Wiki to administrate the states of bugs. Now we plan to migrate to TFS, how to do that? We want to use TFS as our test tool and administrate the test cases
and bugs. Does TFS have the similar tools such as Enterprise Tester, Jira and Wiki?
Thanks,

Hi shimly,
If you want to do the migration from Enterprise Tester to TFS, you can use
TFS Integrate Platform. For the migration, you might need to wirte your own plugin to migrate from Enterprise Tester to TFS.
You can use TFS to do the test case and bug administration. And you can use Microsoft Test Manager if you want to use a test tools which is integrate with TFS. Check this
page for more information about TFS artifacts.
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.

Similar Messages

  • How does "Forms Table Test" work?

    Hey guys,
    I want to use a "forms table test" on the order management lines form, but it doesn't show any reaction.
    In which forms do I use table forms test?
    best regards
    dewi

    Very simple. This table existed in Oracle Version 3 and was used prior to PL/SQL for performing computations. The dummy column is just that. I always returns one row, one column if you select from it.
    Now: DON'T DROP THIS TABLE!!!!!! I decided to see what would happen I did drop the table. Ever hear of INSTANCE CRASH? The Oracle Kernel uses this table Internally for consistency purposes. Shame on Oracle for saying in Version 6 that this table is no longer needed. Also, if your application does a select <sequence name>.nextval from DUAL, change your code as you'll see LOTS of excessive IOs from using this table.

  • 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.

  • HT2518 I'm in the process of transferring files fm pc to mac, all connections verified and migration asst is working. HW, my outlook contacts nor email are listed as an option for transfer.  Any1 else have such a plm?  If so, how did you resolve?

    I'm in the process of transferring files fm pc to mac, all connections verified and migration asst is working. HW, my outlook contacts nor email are listed as an option for transfer.  Any1 else have such a plm?  If so, how did you resolve?

    I used O2M from http://www.littlemachines.com to move from Outlook to Apple Mail.
    Richard

  • MSTest not running in TFS build but tests works fine locally in visual studio

    Hi Team,
    I have 18 unit tests in my test project wanted to run in TFS build. But build says no tests to execute. please find the below details and images for more info.
    Even MSTest command is not working. 
    TFS : 2010
    BUild Server has visual studio 2010 ultimate with SP1.
    Thanks in Advance,
    Shree
    $hree

    Hi Shree,
    I am glad to hear you resolved the issue. Thanks for sharing your experience here, it is good to other members who experience the same issue in the community.
    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 Extract Test Cases from TFS 2013 to Excel

    How to extract test cases from 2013 Team Foundation Server to excel.
    Yuvaraj G

    Hi Yuvaraj,
    To export test cases in TFS 2013 to an Excel file, you can follow the steps as below:
    Create a query for the test cases that you want to export in Team Explorer
    Open an empty Excel file, click the tab of "Team"
    Click "New List" and then select the TFS server and the detailed team project
    In query list, select the query you created before, then click OK to export the test cases
    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 siebel BI report to TEST and PROD from DEV without manually?

    Hi,
    i have developed siebel BI reports in DEV environment. Now want to migrate in test and prod. Is there any automated process available or need to manually. Adding reports to views and uploading templates etc.
    Thanks,
    lax

    Hi,
    try this online training: http://www.oracle.com/technology/obe/admin/owb10gr2_gs.htm.
    Regards,
    Detlef

  • 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 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

  • 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 integrate Silverlight tests into a CI (continuous integration) process. MSTest.exe gives unable to load test container error.

    Hi,
    I am getting "unable to load test container error", while loading test dll. This test dll uses silverlights test framework.
    The details of error is as below,
    Unable to load the test container 'SLTest.dll' or one of its dependencies.
    Error details:
    System.IO.FileNotFoundException: Could not load file or assembly 'System.Windows, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e' or one of its dependencies. The system cannot find the file specified
    System.IO.FileNotFoundException: Could not load file or assembly 'System, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e' or one of its dependencies. The system cannot find the file specified.
    Can any one tell why I am getting this error?
    I would like to run tests which uses silverlight test frame work. One of my solution contains tests which uses silverlight test framework and NUnit or MSTest.
    How to run tests which uses silverlight test framework in TFS Build?
    Vivek.

    I'm getting the same issue:
    Error details: System.IO.FileNotFoundException: Could not load file or assembly 'System.Windows,
    Version=5.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e' or one of its dependencies. The system cannot find the file specified
    On running TeamCity with my unit tests.
    On the server I have silverlight v5.0 installed. System.Windows.dll is present there.
    But still I'm getting this error. What I'm doing wrong?
    Viviek, have you solved your issue?

  • How to migrate a local calendar to a WebDAV server?

    Because I do not like to sync using iCloud I installed Maverick Server to have a local server for my calendars. The other devices in my home can then connect to it. I found it easy to set up using this webpage and it works with a test calendar. I add something in iCal with my MacBook and seconds later it appears on my iPad.
    But I am puzzled on how to migrate my local calendars in iCal to the server. I tried to export them to the desktop and then import them into the server calendar I see in iCal. Then iCal gives this warning:
    Should I proceed? I do not want to damage 12 years of iCalendar data. I have backups, but preventing a mess is always easier.

    Surprisingly, this morning all calendars showed up in my iPhone. Apparently there is a delay.
    But now there is another issue with the error:
    "The server responded with an error.
    Access to “event from years ago” in “the second added calendar” in account “local” is not permitted.
    The server responded:
    “403” to operation CalDAVWriteEntityQueueableOperation."
    [Ignore] [Try Again] [Revert to Server]
    Each event starting with the beginning of that calendar (years ago) seems to generate an error. It will take a day to click on Ignore for all those events.
    Will ask this in a new thread. For now the issue this thread is about is solved, thank you. I also updated my profile, except for my iPad. No 'edit' option next to that one. Strange.

  • My Zoom in Gesture Doesn't Work on Safari How can i make it work?

    I just bought a mac book pro 2011 and i know that the zoom in gesture used to work on safari at first but it doesnt anymore how can i make it work again?

    So it does not work at all in Safari?  Do you have any other web browsers installed that you could test it out on to see if it is just acting up with Safari?

  • TFS performance report pack not working on TFS 2013

    Hi
    I have TFS 2013 setup and I found TFS performance report pack from http://blogs.msdn.com/b/granth/archive/2009/02/03/announcing-tfs-performance-report-pack.aspx URL.
    These reports don't work after uploading to my report server. The blog talk about creating a shared data source TfsActivityReportDS
    and using Data Source=localhost;Initial Catalog=TfsActivityLogging
    as connection string.
    I don't have any database by name TfsActivityReportDS in my TFS and as a result I am not able to run any report on my TFS 2013 server.
    Is there any way to get these reports work for TFS 2013? Or is there other TFS performance report pack made for TFS 2013?
    Regards, Premal Acharya

    Hi Charles,
    Thanks a ton for your help. :)
    It worked on TFS 2013. I followed your steps. I also found one easy way to edit the queries mentioned in those rdl files. I opened them in text editor and replaced TfsActivityLogging with my TFS project name (Tfs_DefaultCollection). Saved rdl file and opened
    it in report builder and then my job was only to modify the data source.
    I really appreciate your help for getting the reports worked on TFS 2013.
    However I am only stuck with one little issue pertained to Server Status - Source Control Request Queue.rdl file
    This report file doesn't have any queries and it also uses XML as connection to the data source. When I run this report on my TFS server I am getting error as URL "http://localhost:8080/versioncontrol/v1.0/administration.asmx" not found.
    Detailed information about the report file is given below.
    Report Name
    Server Status - Source Control Request Queue
    Connection type
    XML
    Connection string in data source 
    http://localhost:8080/versioncontrol/v1.0/administration.asmx
    Query Under data set
    <Query>
       <Method Name="QueryServerRequests" 
    Namespace="http://schemas.microsoft.com/TeamFoundation/2005/06/VersionControl/Admin/03">
       </Method>
       <ElementPath IgnoreNamespaces="true">*</ElementPath>
    </Query>
    -------END---------
    I don't know how to get it work. Your help and advice on this will be highly appreciated.
    Thanks again for helping me to get other reports worked with TFS 2013.
    Regards, Premal Acharya

  • How can we get ADFSecurity work when used in OC4J, OID and OAM?

    I am getting error in http server log "mod_oc4j: Response status=499 and reason=Oracle SSO, but failed to get mod_osso global context."
    But I am not using Oracle SSO and my client doesn't want to use it either, I am using OAM SSO(CoreIDSSO) in my configuration. Please read the details below.
    I am using ADFSecurity in an app that is protected by OAM. To migrate ADFSecurity permissions from
    system-jazn-data.xml to OID, I used JAZNMigrationTool to populate OID with Grantees and Permissions. OAM gives login page, and authentication works fine.
    But ADFSecurity is not working. ADFComponent Delete button is enabled even for roles that dont have permissions for the iterator delete.
    - The app works fine when I use without OAM. ADF Security permissions work fine.
    - The app works fine when used with OAM, but with ADFSecurity disabled (enforce=false).
    - When I enforce ADFSecurity alongwith OAM, ADFSecurity is not working.
    In the doc "Oracle Containers for J2EE Security Guide b28957", there is a mention of use of CoreIDPrincipal for permissions. Our OID Permissions entries show
    LDAPRealmRole for attribute orcljaznprincipal. I am not sure if this could be the reason.
    We have configured AccessServerSDK for the SOA instance and have policy for the urls in the policy manager. We have entries in orion-application.xml, orion-web.xml and system-jazn-data.xml as per the documentations.
    How can we get ADFSecurity work when used with OID and OAM?

    Have you been able to successfully integrate OAS with OAM & OID? We have similar requriement and so far we have not been able to get it working.
    We have application specific roles which we map to OID roles using orion-application.xml.
    Any pointers to achieve this would be greatly appreciated.
    thanks,
    Dipal

Maybe you are looking for

  • Got a New MacBook!! (And a few questions)

    Hello everyone... I've finally switched to Mac! Well... I'm halfway in the process. Right now I'm typing this on my PC. I'm completely new to the world of Mac, and if you could help me with some questions I have, I'd really appreciate it! 1. How fast

  • Motion 3 Crashing at specific frame - only in Best Quality setting!

    Hello everyone, I've got several Motion projects that show the same problem: The project behaves and exports fine as long as I don't set the Render Quality to "Best". When I set the Quality to "Best", Motion will always crash at a specific frame (not

  • Publishing website

    hey i have created a website using iweb not that i use a trial version of .mac account i just have 50 mb space for web pages.whereas the size of y website comes out to be 75 mb. i dont have enough funds to buy a mac account at the moment. can you lea

  • Scheduling process chain in 1st and last of the month

    Hello , Can some one help in scheduling the process chain at the starting of the month and the end of the month ? The chain has to start on 1 st and 28th of every month. Help me with the informations please! Points will be assigned! Thanks in Advance

  • Get Support Link in EP

    Hi, Could anyone please explain me, what does the "GET SUPPORT" link in EP does(in logic screen) Thanks, Sathya