Novell GroupWise Coexistence Solution for Exchange
When you check a GroupWise recipient availability from Outlook client site, you are able to specify a day range beyond 30 days. When doing similar from other site, i.e. checking Exchange recipient from a GroupWise site, there is no busy information returned when scheduling an appointment beyond 30 days limit.
There are two sites of a problem:
Exchange systems have various ranges of date range a FB Search can be done. Exchange 2007 has a limit of 42 days, Exchange 2010 has 62 days ... so we cannot go anyhow further behind this Exchange site limit.
Our FB Service tool has few parts:
The "Redirector" installs into EWS. It listens to free/busy requests from outlook and injects the data for GroupWise users into the response sent back by Exchange. This explains what you see when scheduling GroupWise users from Outlook - can be done for more than 30 days. The Redirector simply uses the requested date rage when it calls the POA via SOAP. So ... whatever Outlook asks for ... it gets.
The "Handler" is a web service that installs in IIS. It handles any URL with "https://%3cwindows/ domain>/ngwfbs" at the start.
Within the code for the Handler, the date range is hard coded at 30 days.
There has been an Enhancement request created for our engineering.