Thursday, 16 July 2009

HTTP 501 Not Implemented when attempting to administrator Sametime 8.0.2

Whilst documenting my mega Connections/Domino/Portal/Sametime/Quickr demo, I noticed that I was unable to access the Sametime Configuration web UI ( http://foobar.com/stconfig.nsf ), but received the exception: -

HTTP 501 Not Implemented

when I tried.

As per usual, I Google'd around, and found reference to this Technote: -

Sametime: Unable to Administer the Server when Web SSO is Disabled


and followed the third circumvention: -

<snip>
Workaround #3

1. Open the servlet.properties file found in the Lotus\Domino\Data directory (using a text editor such as Notepad).
2. Locate the line that begins with: servlet.admin.initArgs=Statistics.Servlet
3. Follow the line to the end where you will find a parameter called:

      "LoginURL=/stconfig.nsf?Login"

4. Delete it.

Example:

Delete what is in bold below, including the comma before the parameter:

servlet.admin.initArgs=Statistics.Servlet.Name=stats,XML.File.Path=admin_web_site.xml,Servlet.Resource.Relative.URL=/servlet/auth/admin,Static.Resource.Relative.URL=/sametime/stadmin,Static.Resource.Relative.Path=/domino/html/sametime/stadmin,Language.Resource.Relative.Path=strings/,Default.Language.Suffix=en,AccessControl.Roles=[SametimeAdmin];[SametimeMonitor];[DatabaseAdmin],ServletURL=admin,LoginURL=/stconfig.nsf?Login

5. Save the changes

6. Type tell http restart on the Domino Server console for the settings to take effect. 
</snip>

Apart from (stupidly) killing the HTTP server WHILST logged in via the Web Administrator client ( I ran tell http quit rather than tell http restart on my Linux-based server ), this worked a treat.

Interesting to see that this Technote was written in 2004, and pertains to ST 3 whereas I'm using ST 8.0.2 :-)

No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...