Coexistence of MOM Notification Workflow and MOM Reporting on SQL 2005
By: Pete Zerger, MCSE(Messaging)
A couple of requests offline told me I’m not the only one who loves the flexibility of Notification Workflow, but still wants the advantages of SQL 2005 Reporting Services. It seems to me this is a pretty straightforward process in a completely distributed install, but it’s a bit tricky for some folks in a single server environment or if the Onepoint and SystemCenterReporting databases are to coexist on the same server. Here’s a quick walkthrough of what it takes to make the two play nice. I'm not speaking to scalability here, so as always, use the sizing tools to make sure your hardware is up to the task.
It's a straightforward process, but order of operations is everything on this one. In short, the legacy components need to be configured first, as SQL 2000 and related services don't know how to facilitate coexistence with the newer SQL 2005 services. If you attempt to install Notification Workflow after the SQL 2005 named instance is in place, you'll have trouble with the Notification Workflow install, as it attempts to make sure both instances of the SQL agent are running, etc.
Base MOM Installation
-
Install SQL 2000 in a DEFAULT INSTANCE.
-
Install MOM database role
-
Install MOM management server role
-
Do NOT install SQL 2000 Reporting Services or MOM Reporting yet!
-
Validate that the MOM installation is healthy. When this is done, you're ready to proceed with the Notification Workflow install.
***MOM Base Installation Complete***
Notification Workflow Installation
Get the Notification Workflow Quickstart Guide HERE and the installation/troubleshooting tips HERE.
-
Install SQL XML
-
Install SQL 2000 Notification Services 2.0 SP1
-
Install Notification Workflow Solution Accelerator
-
Validate your Notification Workflow install is processing and delivering alerts.
***Notification Workflow Installation Complete***
MOM Reporting on SQL 2005 Installation
-
Install SQL 2005 in a NAMED INSTANCE. Since it's for MOM Reporting, I call it SCDW.
-
Choose to install to the named instance and SQL 2005 Reporting Services. Unless you tell it otherwise, the installer will name the reporting directories Reports$SCDW and ReportServer$SCDW. No harm done if you leave it this way...Reporting link still works from the MOM Admin Console.
-
Apply SQL 2005 SP1 now.
***DO NOT install SQL 2005 Notification Services.***
NOTE: As with any MOM Reporting installation on SQL 2005 Reporting Services, supply explicitly the name of the report server directories (Reports$SCDW and ReportServer$SCDW) when prompted. Also, make sure you have the DisableLoopBackCheck registry fix in place as documented in KB918711 (http://support.microsoft.com/Default.aspx?id=918711)
-
That being said, install the MOM 2005 Reporting Server role. When you're prompted for the SQL 2005 Server, you'll enter <server>\SCDW, where <server> is the name of your server.
-
Import management packs are reports.
-
Test your MOM Reporting site and make sure reports render. You’ll need to wait a few hours and wait for the nightly DTS job to transfer some reporting data over to the data warehouse (SystemCenterReporting) so your reports will be populated with data.
I hope you’ll find this information helpful. Your feedback is always welcome at administrator@momresources.org