Guidance Needed: SAM Plugin Installation Order in Domain-Separated Environment + Licensing Clearity

[shubhamkhai]

Hello Community,

I am currently moving forward with installing the SAM (Software Asset Management) plugins on our production instance with a domain-separated environment.

During installation on our DEV instance, we faced several issues such as:

• SaaS Overview not visible in the SAM Workspace

• Integration profiles missing under SaaS License Management

• Plugin dependency failures

• Publisher pack conflicts with domain support

Most of these were resolved with the help of ServiceNow Support, though a few are still in progress.

On DEV, I installed the plugins in the following order:

1. com.snc.samp

2. com.sn_sam_workspace

3. com.sn_sam_saas_int

4. com.snc.samp.microsoft

5. com.sn_samp_adobe

6. com.snc.pa.domain_support

However, in one of our cases, Romana from ServiceNow support advised that the correct approach is to install the publisher packs first (e.g., Microsoft, Adobe, etc.), and then install the SaaS License Management plugin afterwards.

This raises a couple of questions:

• What is the recommended plugin installation order for SAM in a domain-separated setup?

• Does installing them in the wrong order impact functionality (like SaaS overview/integration profiles not being available)?

Additionally, I noticed there is an option to install the com.sn_samp_master_ws plugin, which brings in SAM Workspace along with all publisher packs at once. My concerns here are:

• Does installing this master plugin automatically activate licensing for all publisher packs (e.g., Oracle, IBM, VMware), even if we are not planning to use them?

• Would there be any additional licensing costs just because those packs are installed but unused?

Since we are primarily focusing on SaaS License Management (cloud licenses like Microsoft 365, Adobe, etc.), I want to make sure we avoid unnecessary costs and follow best practices for a domain-separated environment.

Has anyone else implemented SAM in such a setup and can share guidance on installation order and licensing implications of the master plugin?

Any insights would be greatly appreciated!

Thanks in advance,
Shubham

[dreinhardt · Accepted solution]

Hi @shubhamkhai ,

all publisher packs and SaaS direct integrations are included in the SAMP license.

I would recommend to install the „master“ and having all publisher packs installed . Thus will remove any upcoming blockers/dependencies in case the scope of the SAM team changes to one of the publishers with a pack … you are prepared.

Order should be: 1) SAMP master plugin, 2) SaaS plugin.

Best, Dennis