I haven’t set up the SWD self service portal (SSP) in a long time, so I am setting it up in my lab:
Setup Dashboard complete… The SSP and TSP are both on my bigfix server (no port conflicts with webui nor web reports). Both the TSP and SSP diag pages are all green and test authentication via TSP is good. Application Management Group created with a test package (task and target) created and deployed as portal offer.
Enabled SS Dashboard and generated PIN on test targets.
When I log on to the SSP (from a test target with dashboard enabled), it accepts my credentials. It’s at that point I get the error:
Server configuration error: Relevance error: Singular expression refers to nonexistent object… Relevance: (names of items 0 of it, id of items 0 of it, operating system of items 0 of it) of (applicable computers of it, it) whose (exists values whose (it as lowercase = “|cn=chad,cn=users,dc=bignerdlabs,dc=com” as lowercase) of (results (item 0 of it, property 2 of item 1 of it)) AND not exists values whose (it as lowercase = “|cn=chad,cn=users,dc=bignerdlabs,dc=com” as lowercase) of (results (item 0 of it, property 3 of item 1 of it))) of fixlet 19 of bes site whose (name of it starts with “Software Distribution”)
So, it’s looking at the analysis (fixlet 19) and looking for the DN (distinguished name) of my AD ID. So this tells me the SSP is talking to the TSP and getting that data, then looking for computers I’ve registered. Seems to me that THIS would be the point that the dashboard would present me with the option of registering my local computer and populating the “SSP_GREEN” registry key that the analysis looks for.
Everything is 9.5.2.
I’ve gone through the docs a number of times hoping I missed some step that the SSP would use to get me that initial “Add a computer” dialog from the doc, but no…
Any thoughts?
The console operator used in the SSP configuration (which actually configures the TSP) needs to have access to the “Software Distribution” site… Duh…
So now I’m able to log on to the SSP and register the local computer and my test software package shows up in the SSP to install… However, the local SSP (in the BES Client Available software dashboard) is empty…
Ok… resolved this also… Turns out a software “Offer” is what it needed verses a “Portal Offer”… Since the AMG Dashboard supports regular actions as well as policy actions, I assumed an “Offer” was a regular action offer that would show up in the “offers” part of the client. Very strange terminology overlap IBM decided to go with here. I sometimes wonder who makes these decisions…
Now that I see what it can do, I really don’t see the benefit of setting up all of these moving parts to essentially get the same functionality as creating a regular action and making it an offer… sure you get a prettier dashboard, but the end result is the same… Don’t get it.
I’m glad you figured it out. For those who haven’t, the terminology can be a little confusing.
Offer - Gets sent to the BES Client UI Available Software tab
Portal Offer - Gets sent to the SSP
A normal offer deployed through the BES Console will get sent to the BES Client UI’s Offers tab, whereas a offer from the SWD dashboard’s AMG section goes to the Available Software tab.
The purpose of SSP is for a junior administrator without BES Console access to manage multiple computers. Most people probably will have BES Console access to manage multiple computers or use the BES Client UI to manage offers, but the SSP does serve a purpose for those who needs it.