Symantec IGA

  • 1.  Repoint & Recreate CMS Database

    Posted Jan 08, 2013 05:18 PM
      |   view attached

    [left][left]This publication will take you through the steps necessary to repoint and recreate your cms database for the IdentityMinder Report server or any BOXI 3.1 deployed report server.

    An abbreviated summary of the procedure is as follows:

    Following are the steps to point the CMS database to Oracle.

    (if using Oracle) Use the Native Client:
    [list=1]
    [*]For using the native client of oracle we have to make sure that the TNS ping works fine and we can login via SQL Plus.
    [*]Then in CCM, stop the SIA.
    [*]Go to the properties page of the SIA and navigate to the configuration tab.
    [*]Then select update data source settings.
    [*]Select specify for the CMS system database and select oracle.
    [*]In the server name put in the TNS alias name and user id and password (with which you login to the client).
    [list]

    Note : The DSN method is not listed in the guide and is not recommended.

    To recreate the CMS database you'll complete the following procedure:

    Excerpt from pg. 181 of the Business Objects Administrator's Guide, which is
    attached to this post.


    Select a new or existing CMS database on Windows

    This procedure is not used for clustering CMS services. For information on moving servers between clusters, see Backing up and restoring server configuration settings on page 217. Please consider that BO clustering hasn't yet been certified for use with IdentityMinder Reporting. If this is something your business requires, I suggest you reference this post and open an issue with support.
    Please Note: When you select a new or existing CMS database on Windows, the BusinessObjects installation path, operating system, and machine name cannot change.
    [list=1]
    [*]Use the CCM to stop the Server Intelligence Agent (SIA).
    [*]Select the SIA and click Specify CMS System Database Data Source on the toolbar.
    [*]In the Configuration tab of the "Properties" dialog box, under CMS Data Source, click Specify.
    [*]The remaining steps depend upon the connection type you selected:
    [list]
    [*]If you selected ODBC, the Windows "Select Data Source" dialog box appears. Select the ODBC data source that you want to use as the CMS database; then click OK. (Click New to configure a new DSN.) When prompted, provide your database credentials and click OK.
    [*]If you selected a native driver, you are prompted for your database Server Name, your Login ID, and your Password. Provide this information and then click OK.
    [*]The CCM notifies you when the CMS database setup is complete.
    [list]
    [*]In the "Properties" dialog box, click OK.
    [*]Restart the Server Intelligence Agent.
    [list]

    Excerpt pg. 178 of the BusinessObjects Administrator's Guide, which is attached to this post.

    Deleting and recreating the CMS database
    This procedure shows how to recreate (re-initialize) the current CMS database. By performing this task, you destroy all data that is already present in the database. This procedure is useful, for instance, if you have installed BusinessObjects Enterprise in a development environment for designing and testing your own, custom web applications. You can re-initialize the CMS database in your development environment every time you need to clear the system of all its data. When you recreate the CMS database with the CCM, your existing license keys should be retained in the database. However, if you need to enter license keys again, log on to the CMC with the default Administrator account (which will have been reset to have no password). Go to the Authorization management area and enter your information on the License Keys tab. Note: Remember that all data in your current CMS database will be destroyed if you follow this procedure. Consider backing up your current CMS database before beginning. If necessary, contact your database administrator.

    To recreate the CMS database on Windows (These are procedures strait from SAP support documentation.)

    [list=1]
    [*]Use the CCM to stop the Central Management Server.
    [*]With the CMS selected, click Specify CMS Data Source on the toolbar.
    [*]In the CMS Database Setup dialog box, click Recreate the current Data Source.
    [*]Click OK and, when prompted to confirm, click Yes. The SvcMgr dialog box notifies you when the CMS database setup is complete.
    [*]Click OK. You are returned to the CCM.
    [*]Start the Central Management Server. While it is starting, the CMS writes required system data to the newly emptied data source. You may need to click the Refresh
    [list]
    ***Please note, you will have to reimport IM's biar file after completing this process.

    Please consider the above procedure also resets the BO Enterprise administrator password to blank password. This can be reset within the Enterprise User management link within the CMC homepage. You may also need to reapply the license key within the CMC, so please make note of it before completing this procedure or simply contact support for a new one.

    It's worth noting that there is a good, fairly comprehensive guide published by CA Service Desk here. But the authoritative source for reconfiguration of the cms database can be found within the BOXI admin guide from SAP, which is attached to this post.
    Please post with any questions or concerns.
    Thank you.
    Regards,

    Chris Thomas
    CA Technologies
    Principal Support Engineer
    IdentityMinder Reporting Expert
    Tel: +1-631-342-4360
    Chris.Thomas@ca.com
    LinkedIn

    Attachment(s)

    pdf
    xi3-1_bip_admin_en.pdf   6.94 MB 1 version


  • 2.  RE: Repoint & Recreate CMS Database

     
    Posted Jan 11, 2013 12:51 PM
    Thanks for providing all this great information Chris! :grin:


  • 3.  RE: Repoint & Recreate CMS Database

    Posted Jun 05, 2013 05:34 PM
    If you have a problem with the above procedure, please attempt the following:

    -Checked that the progress bar did not appear while recreating the CMS
    database.
    -Copied the BO_trace.ini file from <install Directory of
    BusinessObjects>\BusinessObjects Enterprise 12.0\win32_x86\scripts and
    placed in <install Directory of BusinessObjects>\BusinessObjects
    Enterprise 12.0\win32_x86.
    -Renamed the BO_trace.ini file to SvcMgr_trace.ini.
    -Checked that the SIA was stopped and a stale CMS.exe was present in
    the task manager.
    -killed the stale CMS.exe and tried to recreate the database, it went
    successfull this time.
    -Able to login to CCM manage servers.
    -Asked to disable the SvcMgr trace, however, you requested to update
    the incident with the steps to disable the same.

    Steps to disable the SvcMgr tarce:
    -Go to <install Directory of BusinessObjects>\BusinessObjects
    Enterprise 12.0\win32_x86 and locate SvcMgr_trace.ini file.
    -Edit SvcMgr_trace.ini in a notepad and make the first parameter
    Active=false;
    -Save the file again.
    Note: To deactivate tracing (Windows and Unix) you will need to set
    the active variable (in .ini file)to false. Deleting the .ini file
    will not stop the tracing.
    Once the ini file with the active variable set to false is read again
    (within a minute) you can remove the file.


  • 4.  RE: Repoint & Recreate CMS Database

     
    Posted Jun 07, 2013 05:22 PM
    Thanks for the additional info Chris!