CA Client Automation

  • 1.  As Migrating a Server 12.5 SP1 to a new Server 12.9.

    Posted Sep 25, 2015 01:45 PM

    Dear, someone help me

    I will migrate my old server to a new and do not know how someone could envair me a procedure or document for this activity.

    Need to migrate: Software, Queries, Jobs, permissions configuration, policies, DSM reporting queries, dynamic and static groups. etc ..... all.

     

     

    Current server is a Domain Manager without domain.

    Patch has no manager

    ITCM 12.5 SP1

    OS: Windwos 2008 R2 with SQL 2008 R2 database

     

    I will migrate to the new server

    ITCM 12.9

    SO: 2012 Datacenter with SQL 2012 SP1 database

     

     

    Thank you all



  • 2.  Re: As Migrating a Server 12.5 SP1 to a new Server 12.9.
    Best Answer

    Posted Sep 25, 2015 04:47 PM

    How to Export/Import ITCM Software Packages:

     

    1. Import Software Packages
    2. Copy all ‘*.arc*’ files from old DM in the following location
    3. \\{Server}\c$\Program Files (x86)\CA\DSM\SD\ASM
    4. Create and copy contents to a “Library” folder in TEMP location to New DM.
    5. Select all ‘*.arc’ folders and CTRL+C, right-click All Software, Select Paste à folders to import SW Packages.
    6. Select OK for all the errors.

      

    MDB Admin Console (this tools allows you to migrate the following):

    1. Security profiles

    2. Queries

    3. Asset Groups (Computer Groups)

    4. Query Based Policies

    5. Event Based Policies

    6. Software Computer Groups

    7. Software Procedure Groups

    8. Software Based Policies

    9. Configuration Policies

     

    here's how to use the MDB Admin Console:

    1. Install Java Runtime Environment (Set java_home variable to jre location)

      a. example Java_Home = c:\program files\java\jre7

     

    2. Install by running CA MDB Adminsole.win32.setup_12.0.5.37.exe

    3. download and extract hibernate-3.2.0.ga to c:\program files (x86)\ca\dsm\MDB Admin Console\lib

    4. edit mdbac.properties located in c:\program files (x86)\ca\dsm\mdb admin console\cfg

      a. connection.{sourceDBserver}=jdbc:sqlserver://{sourceDBserver}:1433;DatabaseName=mdb

      b. connection.{targetDBserver}=jdbc:sqlserver://{targetDBserver}:1433;DatabaseName=mdb

    5. test connection in a cmd.exe prompt ran as administrator

      a. c:\progra~2\CA\DSM\MDB Adminconsole>mdbac -testcon -target {targetDBserver} -user ca_itrm -pwd {your itcm password}

    6. Create a temp directory any where on the source server, you'll be using this to export the data you need.

      a. export security profiles (run these commands in a cmd.exe ran as administrator ~HARDCASED~)

        mdbac.bat -export BoSecurityProfile -name "%" -work C:\TEMP\1.SecurityProfiles -source {sourceDBServer} -user ca_itrm -pwd {your itcm password}

      b. export queries

        mdbac.bat -export BoQueryDef -name "%" -work C:\TEMP\3.Queries -source {sourceDBServer} -user ca_itrm -pwd {your itcm password}

      c. export computer groups

        mdbac.bat -export BoGroupDef -name "%" -work C:\TEMP\4.AssetGroups -source {sourceDBServer} -user ca_itrm -pwd {your itcm password}

      d. export query based policies

        mdbac.bat -export BoPolicyQueryBased -name "%" -work C:\TEMP\5.QueryBasedPolicies -source {sourceDBServer} -user ca_itrm -pwd {your itcm password}

      e. export event based policies

        mdbac.bat -export BoPolicyEventBased -name "%" -work C:\TEMP\6.EventBasedPolicies -source {sourceDBServer} -user ca_itrm -pwd {your itcm password}

      f. export software computer groups

        mdbac.bat -export BoSoftwareGroup -name "%" -work C:\TEMP\7.SoftwareGroups -source {sourceDBServer} -user ca_itrm -pwd {your itcm password}

      g. export software procedure groups

        mdbac.bat -export BoProcedureGroup -name "%" -work C:\TEMP\8.ProcedureGroups -source {sourceDBServer} -user ca_itrm -pwd {your itcm password}

      h. export software based policies

        mdbac.bat -export BoPolicySoftware -name "%" -work C:\TEMP\9.SoftwareBasedPolicies -source {sourceDBServer} -user ca_itrm -pwd {your itcm password}

      I. export configuration policies

        mdbac.bat -export BoPolicyComputer -name "%" -work C:\TEMP\11.Configuration -source {sourceDBServer} -user ca_itrm -pwd {your itcm password}

    7. copy the temp file with all the exports to the target server, now you're going to do this in reverse

      a. mdbac.bat -import -file C:\TEMP\1.SecurityProfiles -target {targetDBserver} -user ca_itrm -pwd {your itcm password}

      b. mdbac.bat -import -file C:\TEMP\3.Queries -target {targetDBserver} -user ca_itrm -pwd {your itcm password}

      c. mdbac.bat -import -file C:\TEMP\4.AssetGroups -target {targetDBserver} -user ca_itrm -pwd {your itcm password}

      d. mdbac.bat -import -file C:\TEMP\5.QueryBasedPolicies -target {targetDBserver} -user ca_itrm -pwd {your itcm password}

      e. mdbac.bat -import -file C:\TEMP\6.EventBasedpolicies -target {targetDBserver} -user ca_itrm -pwd {your itcm password}

      f. mdbac.bat -import -file C:\TEMP\7.SoftwareGroups -target {targetDBserver} -user ca_itrm -pwd {your itcm password}

      g. mdbac.bat -import -file C:\TEMP\8.ProcedureGroups -target {targetDBserver} -user ca_itrm -pwd {your itcm password}

      h. mdbac.bat -import -file C:\TEMP\9.SoftwareBasedPolicies -target {targetDBserver} -user ca_itrm -pwd {your itcm password}

      I. mdbac.bat -import -file C:\TEMP\11.Configuration -target {targetDBserver} -user ca_itrm -pwd {your itcm password}

    8. registering SS to new DM (Make sure you enable the computer move policy first!! <~ this policy can save installation records, if unimportant you can skip this)

      a. CA tech doc TEC534779: how to register SS to new DM

      b. cserver unregister

      c. cserver config -h {FQDN of new DM}

      d. cserver register -a

      e. caf register all

      f. caf restart

      g. cserver check -c

     

    If you have many custom software definitions I would contact CA support to walk you through the steps to use the content utility tool to migrate software definitions.

     

    Steven On

    DSM Lead Administrator

    California Franchise Tax Board

    steven.on@ftb.ca.gov



  • 3.  Re: As Migrating a Server 12.5 SP1 to a new Server 12.9.

    Broadcom Employee
    Posted Sep 28, 2015 06:26 AM

    Hi Steven.OnFTB

     

    Thanks for the great update.

     

    regards

    Rich



  • 4.  Re: As Migrating a Server 12.5 SP1 to a new Server 12.9.

    Posted Sep 28, 2015 01:40 PM

    Thank you,

    I will carry out my test environment this final next weekend, come and report the result.



  • 5.  Re: As Migrating a Server 12.5 SP1 to a new Server 12.9.

    Posted Sep 29, 2015 03:38 PM

    Hi,

    I am Mount lab Test.

    Test comunications ok  and export ok

    mdbac -testcon -target msql -user ca_itrm -pwd xxxx 


    more no import all error.


    Command

    mdbac.bat -export BoAreaDef -name "%" -work C:\TEMP\1.BoAreaDef -source msql -user ca_itrm -pwd xxxxxxxx

    result error: [MDBAC-107] verification of target schema failed

     




  • 6.  Re: As Migrating a Server 12.5 SP1 to a new Server 12.9.

    Posted Oct 05, 2015 09:39 AM

    Thank you all, it worked ...



  • 7.  Re: As Migrating a Server 12.5 SP1 to a new Server 12.9.

    Posted Sep 28, 2015 01:48 PM

    Thanks for sharing this Steven.OnFTB