White Papers

82 Lifecycle Controller Integration Best Practices Guide

8 Event Filter Profile Use Cases

8.1 Discovery of Event Filter Profile Support

Use the following procedure below to confirm the existence of Event Filter profile support. This profile is currently not

supported prior to LC2.

Applies to: LC2+

Prerequisites for script: none

Script: GetEventFilterProfile.win

A) The Lifecycle Controller remote service must be in a “ready” state before running any other WSMAN commands.

GetRemoteServicesAPIStatus():

B) GetLCRegisteredProfiles(): ENUMERATE the DCIM_LCRegisteredProfile class to view all registered profiles. See

section 2.2 for a definition of ENUMERATE.

C) Search for “RegisteredName=Event Filter” and note its instanceID to use in step D)

D) GetLCRegisteredProfile(): GET the DCIM_LCRegisteredProfile instance using the InstanceID from C). See Section

2.3 for a definition of GET.

Results for the InstanceID of DCIM:EventFilter:1.0.0 shown below. If no instance is returned, the profile is not

supported.

DCIM_LCRegisteredProfile

AdvertiseTypeDescriptions = WS-Identify

AdvertiseTypeDescriptions = Interop Namespace

AdvertiseTypes = 1

InstanceID = DCIM:EventFilter:1.0.0

OtherRegisteredOrganization = DCIM

ProfileRequireLicense = Remote Firmware Configuration

ProfileRequireLicenseStatus = LICENSED

RegisteredName = Event Filter

RegisteredOrganization = 1