Groove Web Services Registry Keys

Microsoft Office Groove 2007 and Microsoft Office Server 2007 Groove Data Bridge use registry keys to communicate run-time data to a local Groove Web Services SOAP client. The registry keys are stored in a different registry hive on Office Groove 2007 than they are on Office Server 2007 Groove Data Bridge.

Registry Keys on Office Groove 2007

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Groove\ 
        GrooveHTTPDesiredPort
        GrooveHTTPPort
        GrooveLocalHTTPPort
        GrooveLocalHTTPServerPID

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Groove\WebServices\ 
        LocalRequestKey
        LocalResponseKey

Registry Keys on Office Server 2007 Groove Data Bridge

HKEY_LOCAL_MACHINE\Software\Microsoft\Office Server\12.0\Groove\ 
        GrooveHTTPDesiredPort
        GrooveHTTPPort
        GrooveLocalHTTPPort
        GrooveLocalHTTPServerPID

HKEY_LOCAL_MACHINE\Software\Microsoft\
  Office Server\12.0\Groove\WebServices\ 
        LocalRequestKey
        LocalResponseKey

Port and ProcessID Keys

  • GrooveHTTPDesiredPort—if this key is defined, Groove or Groove Data Bridge reads this key and attempts to use the specified port for HTTP Web service requests. This key has a DWORD value.

  • GrooveHTTPPort and GrooveLocalHTTPPort—Groove or Groove Data Bridge sets these keys to specify the port that it is currently listening on for Web service requests. These keys have DWORD values and always have the same value.

  • GrooveLocalHTTPServerPID—Groove or Groove Data Bridge sets this key to its current Process ID. This key has a DWORD value. Your Web Services application can use the Process ID to check if the Groove or Groove Data Bridge process is running. If your application is running as a SOAP client to Groove, it needs the Process ID in order to give the Groove process permission to set the foreground window when your Web services application is running. This permission is important if your application calls a GrooveLocal operation that causes Groove to display a window to the user.

See Also

Reference

Headers Used in Groove Web Services

Concepts

Security in Groove Web Services
Reading Groove Registry Keys
Reading Groove Data Bridge Registry Keys