Hi Lyn,

Due to the complexity of what makes up System Elements when using native SACM its not possible to create these within SMAX. They are all controlled by UCMDB. To help better explain please see the following doc link:

https://docs.microfocus.com/doc/SMAX/23.4/Native_SACM_overview

Thanks

Dave

Hi, Dave,  Thanks for the response.  I did see that in the docs, but I'm wondering if we couldn't create System Elements in a very limited fashion in SMAX... Specifically for a custom subtype representing Control-M jobs, which are not discoverable, and are all related to one other CI. Hoping that this case is narrow enough that it might be ok. 

Thanks,

Lyn

Hi Lyn,

The issue is that SMAX system elements are generally(*) mapped to UCMDB runningsoftware CIs, which can only exist with a composition relationship to a container CI. Since this is enforced by UCMDB, and you cannot create both the CI and the relationship in SMAX in a single operation, it is not currently possible to let SMAX create system elements.

If I understand this correctly, you are coming from a setup without native SACM, where you created a specific sub-type of system elements in SMAX to represent Control-M jobs.

To transpose that in a native SACM setup, you will have to determine the UCMDB CI type that should be used. That must then fit within the (currently hard-coded) mapping of UCMDB to SMAX ci types. If these CIs are related to a "Device" CI (node in UCMDB), then you can simply use the UCMDB runningsoftware CI.

Otherwise, I would suggest a custom CI type below either "Application Resource" or "Application System". You will then also have to add a Studio rule in SMAX to map that new CI type to the matching SMAX sub-type (similar rules do exist for out-of-the-box CI types).

In any case, you will have to create these CIs in UCMDB, not SMAX. I'm not aware of any way to avoid this.

(*) There are a few other UCMDB ci-types that are also mapped to SMAX system elements - see docs.microfocus.com/.../NativeSACMFunction

We are running native SACM, and we have a custom ci type for the control-M jobs in uCMDB. We currently load them into uCMDB, which federates to SMAX, but we wish to reverse this and load them directly into SMAX for various user- and data- centric reasons. That;'s why I am hoping to be able to create this specific case of a system element into SMAXvia the UI.   (Or, less optimally, via an Integration.) 

What you are asking for will required product changes.

You should probably submit an idea, but that won't give you a solution in the short term.

Thanks for your explanation and advice.

Regards,

Lyn