CA Service Management

  • 1.  Advice On Moving CABI To Application New Server

    Posted Mar 06, 2014 10:53 PM

    Hello,

    I intend to upgrade SDM from 12.6 to 12.9 for our organisation. Our CABI 3.3 SP1 installation is currently on the same application 2008 R2 server as SDM 12.6.

    I want SDM 12.9 moved to a 2012 application server, but I found out CABI 3.3 SP1 is not compatible with 2012. So I need to move CABI 3.3 SP1 to another 2008 R2 application server, as I need a new host name, and would prefer a fresh clean enivorment. The CABI 3.3 SP1 BO_CMS database will remain on the same server.

    Can I just install the CABI 3.3 SP1 application on the new server and point it to the existing BO_CMS database, and what about the post CABI 3.3 SP1 hotfix, do I just run the vbs script again?

    Any advice out there?

    Cheers

    Stuart



  • 2.  RE: Advice On Moving CABI To Application New Server
    Best Answer

    Posted Mar 06, 2014 11:55 PM

    Hi Stuart,

    You may install CABI 3.3 SP1 on new server and point existing BO_CMS database during the installation. Once completed, perform the post installation /configuration steps followed by copying CABI content from old to new environment(TEC578370).



    Thanks,
    Naveen



  • 3.  RE: Advice On Moving CABI To Application New Server

    Posted Mar 09, 2014 07:01 PM

    Thanks for the reply, what installation files do I use to install CABI 3.3. SP1 on a new server?

    On the existing application server, I installed CABI 3.2 then CABI 3.2 SP5, followed by CABI 3.3 SP1.

     

     

     



  • 4.  RE: Advice On Moving CABI To Application New Server

    Posted Mar 09, 2014 08:38 PM

    Stuart,

    CABI 3.3 SP1 is SAP BOXI 3.1 SP6. You may perform steps from TEC592444 which contains information about the files to download.

    Thanks,
    Naveen



  • 5.  RE: Advice On Moving CABI To Application New Server

    Posted Mar 09, 2014 09:06 PM
    naveen_desham:

    Stuart,

    CABI 3.3 SP1 is SAP BOXI 3.1 SP6. You may perform steps from TEC592444 which contains information about the files to download.

    Thanks,
    Naveen


    So I should install the same order CABI 3.2, then 3.2 SP5 and 3.3 SP1. As that document is based on SP5 already being installed.

     



  • 6.  RE: Advice On Moving CABI To Application New Server

    Posted Mar 12, 2014 10:56 PM

    *Information from CA Support*

    **********************************

    ORIGINAL/SOURCE CABI Server:
     1) Backup CABI machine.
     2) Backup CABI CMS database.
     3) Backup CABI FileStore on ORIGINAL/SOURCE CABI Server. This directory structure will be manually copied to the SWINGBOX at a later time.
      a) If your SOURCE CABI Server is CABI 2.x then
       1) back up a copy of the FileStore folder located at:
        c:\Program Files(x86)\CA\SC\CommonReporting\BusinessObjects Enterprise 11\FileStore
       2) Open the Central Configuration Manager (CCM),  select the Central Management Server
       3) Right click on Central Management Server and open its properties
       4) Click on configuration tab and notedown the DSN Name under CMS Data Source option
       5) Open Windows 32bit Datasource Administrator and identify the same DSN Name above
       6) Note down the information about this datasource. You'll have to create the same datasource on your SWINGBOX later
       
      b) If your SOURCE CABI Server is CABI 3.x then
       1) back up a copy of the FileStore folder located at:
        c:\Program Files(x86)\CA\SC\CommonReporting3\BusinessObjects Enterprise 12.0\FileStore
       2) Open the Central Configuration Manager (CCM), select the Server Intelligence Agent (SIA).
       3) Right click on SIA and open its properties
       4) Click on configuration tab and notedown the DSN Name under CMS Data Source option
       5) Open Windows 32bit Datasource Administrator and identify the same DSN Name above
       6) Note down the information about this datasource. You'll have to create the same datasource on your SWINGBOX later

     

    SWINGBOX CABI Server:
     INSTALL FRESH:
      1) Obtain a new Windows server (which will be our SWINGBOX CABI Server) that supports CABI 3.2 SP3 and SP5.
      2) Install CABI 3.2 SP3 first using SDM 12.6 DVD2 or 12.7 DVD2.
       a) Follow the SDM Implementation Guide to complete the whole install.
       b) Run the SDM CABI Configuration option on the DVD2 as well, which installs the CA SDM ODBC driver.
       c) Point this ODBC driver to your SDM Dev/Test/Swing box and not production SDM Server.
      3) Install CABI 3.2 SP5 following TEC566603.

     RESTORE FILESTORE:
      4) Restore the Original/Source FileStore folder from Original/Source CABI Server  TO SWINGBOX Server's location:
       c:\Program Files(x86)\CA\SC\CommonReporting3\BusinessObjects Enterprise 12.0\FileStore
      5) Open Windows 32bit Datasource Administrator and create a NEW DSN Name which has similar settings as you noted down on ORIGINAL/SOURCE CABI Server earlier. This will be referred to as the SOURCE Datasource later on.
       Note: This will be used only for Reading data and not to write to it. Try to name this appropriately for you to identify it easily that its Production.
      6) Open the Central Configuration Manager (CCM),  select the Server Intelligence Agent (SIA) and stop it.

     RESTORE ORIGINAL/SOURCE CABI DATA:
      7) Right click on SIA and open its properties. Click on configuration tab and notedown the DSN Name under CMS Data Source option. Dont click on anything yet.
      8) Open Windows 32bit Datasource Administrator and identify the same DSN Name above. This will be referred to as your DESTINATION Datasource later on.
      9) Back on the Configuration tab the SIA properites window, Click on "Specify" under CMS System Database Configuration.
      10) Select option 'Copy data source' option and click OK.
      11) Leave the AutoDetect option on the first drop down.
      12) For the Get data from option, click Specify and then select appropriate SOURCE DSN that you created above.
      13) For the Copy to the following data source option, click Specify and then select appropriate DESTINATION DSN that you created above.
      14) Click OK.
      15) You'll get a warning that this operation will delete all BOXI tables in the DESTINATION DSN. Click YES as its just fresh/empty d/b for us that we created on the SWINGBOX above
      16) Continue with rest of the process which will migrate the CABI Source Database information to Destination Database
      17) Once the process is complete, Start the SIA via Central Configuration Manager (CCM)
      18) Now in the CCM, select the button "update objects" (its the second button on the right hand side of delete button). Provide your SOURCE CABI Administrator username/password when prompted for authentication.
      19) This process will now detect all objects that need to be updated and updates them (Note: this is all happening on the SWINGBOX. Nothing here now should touch your SOURCE. If you want to be safe, rename/delete the SOURCE DSN so that its not used anymore)
      20) This process might take a while. Once completed, you'll get a notification. You could review the log file that it prompts for, to ensure that if there are any errors you can review them later.
      21) Restart SIA and Tomcat from CCN

     STOP SCHEDULED REPORTS:
      22) Login to Central Management Console (CMC) as an administrator on CABI SWINGBOX:
       a) Select the Instance Manager drop down in CMC
        1) There is a Check box next to Status button on the bottom half of your screen. Ensure you select a specific Status and then click Find button.
        2) Select all reports that are in Running/Pending/Recurring Status  and hit the PAUSE button.
        3) Repeat the above steps until you see 0 reports that are in Status = Recurring/Pending/Running.
        4) This is to ensure you are not sending duplicate reports to your users because your SWINGBOX CABI data is exactly now a replica of SOURCE CABI data.
       b) With in CMC:
       c) Verify if your Universes exist in the Universes drop down.
       d) Verify if your folders/reports exist in the Folders drop down and navigate through sub folders.
       e) Verify if your Users exist in the Users drop down.
      
     CORRECT UNIVERSE'S CONNECTION:
      23) Adjust the CA Service Desk universe to use the correct Service Desk server now by launching BOXI Designer, login as administrator to CABI SWINGBOX at the logon prompt
       a) Click FILE -> IMPORT
       b) On the Import Universe window, click the top BROWSE button and navigate to the CA UNIVERSES folder and click on OK.
       c) The CA SERVICE DESK Universe will appear in the Universe section. select it and click on OK.
       d) Once the import is complete, click on FILE- > PARAMETERS
       e) click on the EDIT button.
       f) On the resulting window, click the BACK button and wait for about 10 seconds before the Define a new connection screen shows up.
       g) Select GENERIC -> GENERIC ODBC3 DATASOURCE -> ODBC DRIVERS  and click Next.
       h) Select appropriate option that you want to use (i.e., Use Business Objects credentials option or provide a hardcoded Service Desk Manager username/password).
       i) In the DATASOURCE NAME field select the drop down and select appropriate CA ServiceDesk Manager datasource that your CA SDM SWINGBOX is going to use.
       j) Click on the TEST CONNECTION button. A message stating 'Connection Successful' should be displayed.
       k) Click on OK and Next.
       l) Select the CONNECTION POOL MODE setting to "Disconnect after each transaction".
       m) Click on NEXT and then click on FINISH on the next screen.
       n) Click on the TEST button. A message stating 'Connection Successful' should be displayed.
       o) Click OK
       p) Click on FILE -> SAVE
       q) Once the save is complete, select FILE -> EXPORT. Select all the groups in the GROUPS section and click on OK
       r) Once the export is complete, click on the OK button and close the Designer program.

     TEST REPORTS:
      24) Test the out of box Service Desk CABI reports from Infoview to ensure that they work correctly.
      25) Test your custom CABI reports from Infoview to ensure they work correctly.
      26) Schedule some reports to ensure they work as expected.

     BACKUP CABI SWINGBOX  and CABI CMS database now.



  • 7.  RE: [CABI for CA Service Desk] RE: Advice On Moving CABI To Application New

    Broadcom Employee
    Posted Mar 13, 2014 02:24 AM
    Hi Stuart,

    Whilst this was developed primarily for 2.x to 3.x migration we have had trouble around step#18 in this list.

    Instead we ended up creating a new sia+ default servers (after stopping sia and recreating them via add new option in the central configuration manager). And then follow the step in 18 and forward.

    So while the approach works in general, there maybe tweaks needed.

    This doc did not finish any detailed testing too. Just something that we've been putting together on one location.

    -R


  • 8.  RE: [CABI for CA Service Desk] RE: Advice On Moving CABI To Application New

    Posted Mar 19, 2014 07:50 PM

    What exactly would I lose by creating a new BO_CMS database and following TEC578370?

    Also is there any problems if the CABI BO_CMS database is running in a SQL 2008 compatibility level and the SDM mdb database is running a SQL 2012 compatibility level ?