Migrate software models created from SSO Integration Profile

[Matt Velthoen]

Hi all,

I'm working with SAM Pro and SaaS License Management.  I've set up a PoC in our Dev instance and this includes setting up a SSO integration profile to pull apps from Azure AD.

Once the apps are loaded, several software models get created automatically.  These have to be published to the catalog via a related link on the model.  Then entitlements are created, etc.

When migrating from Dev > Test, I noticed the software model and catalog item did not get created (yes, they were in the update sets).  I'm wondering if this is expected or if I'm not doing this correctly.

Do I need to...

• Connect > set up models > publish cat item separately in each instance?  My issue with that is the Sys IDs are not going to match, so any work done to a catalog item (add/edit variables, etc.) is going to be a pain.
• Same as above but set it all up in Prod then copy down?
• Export/import these records via XML?
• ???

Any help is appreciated.  I haven't had luck searching for this since all the results are too generic.  I will also need to do something similar for apps set up with Direct Integration Profile, but I don't even have that working yet.  I'm assuming the process will be roughly the same.

[Matt Velthoen]

Also wondering if there is a best practice for migrating the integration profile (SSO or Direct) between instances.  My assumption is that this needs to be set up separately for each, but I can't find anything that states one or the other.

[Ken Neikirk1 · Accepted solution]

The profile need to be configured in each instance.  It is not captured in an update set.

I would copy down from Prod for the catalog items.  The software models should get created in each instance when you set up the integration profile and run the jobs.

[Community Alums]

Thanks for the response.  So, would you copy down the catalog items and then update them in each instance to point to the local software model?  Otherwise, the item/model linking would be broken since the models aren't the same record (this would affect testing and updates later).

The issue I'd have with this is any changes to the catalog item later on would require updates in each instance.

[Matt Velthoen]

Lacking any other info, I have created the integration profile in Prod and published the necessary models to the catalog.  Both models and catalog items have been copied down to sub-Prod instances via XML so I can work on the correct records there and migrate changes back up via update set.

A bit clunky, but works.