Cognos Analytics

Cognos Analytics

Connect, learn, and share with thousands of IBM Cognos Analytics users! 

 View Only

  • 1.  Moving from COGNOS 11.1 (on-prem) to COGNOS Analytics 12.0.1 (CP4D and IBM MAS 9.0 on AWS ROSA)

    Posted Mon May 19, 2025 10:26 AM

    Hi All,

    Looking for industry standard to move all custom components present on COGNOS 11.1 (on-prem) to COGNOS Analytics 12.0.1 (CP4D and IBM MAS 9.0 on AWS ROSA).

    We plan to install new COGNOS 12.0.1 on AWS ROSA and want to move all components from current Cognos 11.1(on-prem).

    Need quick and industry standard process.

    Regards,

    Aravind Penugonda



    ------------------------------
    Aravind Penugonda
    ------------------------------


  • 2.  RE: Moving from COGNOS 11.1 (on-prem) to COGNOS Analytics 12.0.1 (CP4D and IBM MAS 9.0 on AWS ROSA)

    Posted Tue May 20, 2025 01:29 PM
    Edited by Daryl Baker Tue May 20, 2025 01:30 PM

    I am not sure there is a "Standard" without looking at an assessment of the environment.  Obviously, there can be a lot to a migration or upgrade.

    But you can start with a simple Export/Import of the Content Store.  

    Do You have multiple Environments? Have you thought about going from CQM to DQM?  If moving to CP4D you will need to do a namespace migration unless you want to start over with security.   Let me know if you want to discuss more.

    Best of luck! ;) 


    ------------------------------
    Daryl Baker
    Director of Software Solutions
    BSP Software - Micro Strategies Inc.
    IL
    8153262562
    ------------------------------

    Original Message


  • 3.  RE: Moving from COGNOS 11.1 (on-prem) to COGNOS Analytics 12.0.1 (CP4D and IBM MAS 9.0 on AWS ROSA)

    Posted Thu May 22, 2025 09:42 AM

    Unlikely, any Cognos upgrade can be standard. Every environment is unique and can have lots customizations.

    I hope you are aware than many Cognos popular components are removed in CA12:

    12.0.0 - June 2023

    Removed Query Studio, Analysis Studio, and Cognos Workspace
    The following components are removed from Cognos Analytics:
    • Query Studio
    • Analysis Studio
    • Cognos Workspace

    I wonder, what are the reasons to use CA@CP4D?

    Configuration of OpenShift clusters and CP4D will complicate things greatly ....



    ------------------------------
    Andrei Istomine
    Open to work - anything Cognos
    https://www.linkedin.com/in/andreii/
    ------------------------------

    Original Message


  • 4.  RE: Moving from COGNOS 11.1 (on-prem) to COGNOS Analytics 12.0.1 (CP4D and IBM MAS 9.0 on AWS ROSA)

    Posted Mon June 09, 2025 10:22 AM

    The simplest way to move your content across is via a deployment archive. Create a full backup in your on-prem version - the deployment zip file will be created in the Deployments folder. Grab a copy of this, ready to transfer it to your new instance.

    The ICP4D Cognos Analytics cartridge has a different architecture from the on-prem version (because it is containerized). Once you have the new instance running, you will need to jump through a couple of hoops to get your deployment archive over to it. I'm assuming you are managing the instance from a bastion server, using oc commands? The first step is to sftp the deployment archive to a folder on that server - probably easiest to use filezilla for that step. Next you'll need to copy it from the bastion to the Artifacts pod in your CA instance - the Artifacts pod has persistent storage for things like deployment archives, jdbc drivers etc. use an oc cp command to copy the file to the Deployments folder of the Artifacts pod (you can identify its exact name using grep). Once the deployment archive is copied over, you should then be able to log in to your new instance and restore the deployment as normal.

    As others have indicated, there are some factors to overcome also - CA in ICP4D only uses Dynamic Query, so if your old instance is Compatible Query you'd need to convert over and test before you deploy. Security will be different too, so you'll either need to migrate over using a tool like MetaManager or set it all up from scratch in the new instance. 

    Good luck!

    MF.



    ------------------------------
    Mark Fry
    Retired Field Solutions Architect
    ------------------------------

    Original Message


Related Content