Import OMW and OMU policies into OBM

Good day,

I am migrating a customers OMW v8.x and OMU v8.x to the lastest  version of OBM. I have not yet applied the licenses to OBM so am running on the trial license. I exported the OMW and OMU custom policy groups to a folder. After copying the folder to the OBM GWS, I ran ConfigExchange -check and it returns "Successfully Completed". When I then run ConfixExchange -uploadOM it also returns  "Successfully Completed". However, inspection of OBM Policy groups shows no new folder as expected.

1) Is this a restriction on the OBM trial license.

2) Is this a OM version problem.

3) Is there some additional action I need to perform in order to see the policy group in OBM.

I previously performed the OM import to OBM from OM v9 at another customer site.

KInd regards

Graham

  • 0  

    Can you check if the policies exists in OBM but just not in a group? in Policies Templates select the 2nd tab "Policies by type", then try to find your imported policies.

  • 0 in reply to   

    Hello Asaf, thanks for replying. No, I did check there, I also looked in the DB tables (CFG_TEMPLATE*), but no new entries there either. Do you know which log file on the GWS that I can look to for more information. Log opr-clis just seems to show the ConfigExchange commands.

  • 0  

    Hello Graham,

    It's been very long that I've dealt with OMU 8.x (and I all forgot about OMW).

    I'm not even sure OMU 8.x has the command to export policies for OBM.

    Here is the docu about transferring configuration from OM to OBM:

    https://docs.microfocus.com/doc/Operations_Bridge_Manager/24.2/ManageOperationsagentsOBMOverview

    Look for "Scenario 2: Import and reuse custom policies from OM".

    Did you use opcpolicy to export the policies from OMU?

    Best regards,

    Tobias

  • 0 in reply to   

    Hi Tobias, 

    Thanks for the response. For OMU I used opccfgdwn. I tried the OMU import again and now I see the following ...

    \

    My command...

    ConfigExchange -username admin -password <password> -uploadOM -input "C:\Source\OMU Policy Downloads"

    The tail of the output...

    INFO: Skipping because the platform is not supported C:/Source/OMU Policy Downloads/cfgdwn/C/EXECUTABLES/sun/sparc/solaris7/monitor/spi_datapro.xml
    INFO: Skipping because the platform is not supported C:/Source/OMU Policy Downloads/cfgdwn/C/EXECUTABLES/sun/sparc/solaris7/monitor/spi_datapro_input.xml
    INFO: Skipping because the platform is not supported C:/Source/OMU Policy Downloads/cfgdwn/C/EXECUTABLES/sun/sparc/solaris7/monitor/spi_datapro_install.xml
    INFO: Skipping because the platform is not supported C:/Source/OMU Policy Downloads/cfgdwn/C/EXECUTABLES/sun/sparc/solaris7/monitor/spi_datapro_reg.xml
    INFO: Skipping because the platform is not supported C:/Source/OMU Policy Downloads/cfgdwn/C/EXECUTABLES/sun/sparc/solaris7/monitor/spi_datapro_runSHSCollector.sh
    INFO: Skipping because the platform is not supported C:/Source/OMU Policy Downloads/cfgdwn/C/EXECUTABLES/sun/sparc/solaris7/monitor/spi_datapro_task.xml
    ERROR: Operation failed. HTTP Status: 400 (400).
    - Instrumentation with OMU_customer_data already exists

    C:\HPBSM\opr\bin>

    In the documentation it states that I can ignore the last error. 

  • 0 in reply to 

    In some cases, I had to download only policy/policy group  in  cfg download and then I was able to upload to OMi.

    May be similar way could help. 

  • 0   in reply to 

    Hello Graham,

    Does the download directory from OMU have a "POLICIES" and "POLGROUPS" directory?

    Best regards,

    Tobias

  • 0 in reply to   

    This is the directory structure, when I try to import just the specific templates related folders, the command returns that it was successful, but I don't see the monitors in OBM afterwards.

  • 0 in reply to 

    Hi Misaq, Thanks, I did try this but still not able to see policies in OBM.

  • Suggested Answer

    0   in reply to 

    Hello Graham,

    That's what I was afraid of.

    OMU 8.x used templates. The change from templates to policies came with OMU 9.x.
    OBM only understands policies. You cannot import the OMU 8.x templates into OBM directly.

    You may be able to indirectly get those templates manually migrated using the RAW policy editor.

    The OMU 8.x templates are the RAW part of a policy, what's missing is the header.

    Since you know policy type (by directory structure), you can create a new policy with the same name.

    For example for the opcmsg template that starts with: OPCMSG "opcmsg(1|3)"

    You would create a new policy of type Open Message Interface called "opcmsg(1|3)" using the RAW editor,

    then go to the Policy Data part (the RAW part) and paste the whole template in there.

    Best regards,

    Tobias

  • 0 in reply to   

    Thanks for the clarification Tobias. I'll experiment with that approach.