StreamWeaver SCOM Gateway Application

Set up the StreamWeaver SCOM Gateway Application on IIS or as an Azure Application Service

To enable communication between the StreamWeaver core services and SCOM, you will need to deploy a small application into an IIS or as an Azure Application Service.  This enables communication to the SCOM SDK process to create new managed objects within SCOM.

Step 1: IIS must be configured to run the StreamWeaver SCOM Gateway application.  The screenshot at the right displays the typical settings for configuring your Windows Server machine's IIS instance.  Note that this should be the same machine as your SCOM Management Server.

Step 2: Deploy the SCOM Gateway Service from the provided zipfile.  The zipfile will need to be unzipped into either the "Default Website" or to one of your choosing.  

Once the files are unzipped, then you will need to add the application and assign to a .NET 4.5 application pool.

Directory structure of an example deployment of the SCOM Gateway Service.

Add Application to the IIS instance...

Step 3: Validate the site is running by hitting the following url:  http://localhost/api/scomrest/ping 

If successful, you will see an Ack returned

Step 4: Add a SCOM user account with the appropriate permissions to allow access to create events, import management packs, and create management objects.  By default this is the SCOM "Administrator" account, but can be mapped to any SCOM group with the appropriate permissions. 

See Microsoft Docs for more information.

In Active Directory create a new group, i.e. "SCOM SDK Access"

Add a user to the group. In this case, we created a new "swp" user.

In SCOM, add the group to the "Administrators" Group.