So you have a solid understanding of Service Manager 2010 Beta 2, installed the necessary components into your virtual lab, and have also installed the Service Manager DW to get the full breadth of the product.
In this posting we’ll cover the final component: Register with Service Manager DW.
It is important to go through registering the Service Manager Data Warehouse in order for reporting to function.
When the steps below are completed, Service Manager will perform seven data warehouse jobs that run at various times in order to maintain the data warehouse databases.
Job Schedule and Frequency:
Each of the defined jobs can be modified to run as needed, except for the Entity (or Grooming), this function is handled as a workflow.
If you need to change the job schedule and frequency for the Service Manager Data Warehouse jobs — you can do this via the Service Manager Console or PowerShell (see below for examples).
The Service Manager snap-in for Windows PowerShell contains cmdlets that are used to manage Data Warehouse functions on the server that hosts the Data Warehouse.
Type the get-help command followed by the name of the cmdlet for which you want help.
For example, get-help Set-SCDWJobSchedule
When you run Windows PowerShell cmdlets for the first time, you must set the execution policy to RemoteSigned. Then, each time you run a Windows PowerShell cmdlet, you must run the Add-PSSnapin command to add the Service Manager snap-in.
Service Manager: Register with Service Manager Data Warehouse Wizard
This wizard based process registers the Service Manager management group you created on your first virtual machine (VM1) with the Service Manager Data Warehouse management group you created on your second virtual machine (VM2).
Once you have gone through the Service Manager Data Warehouse Wizard, I recommend validating the Data Warehouse Registration process.
This can be done by launching PowerShell and typing the following command:
“A table with two rows of data will display. The first column, DataSourceName will list the Service Manager management group name and the data warehouse management group name.” – Microsoft
Now that the registration process has been validated, let’s get a better understanding of what is occuring between the Service Manager Management Group and the Service Manager Data Warehouse Management Group.
Unbeknownst to you, there is a process called MPSyncJob already running in the background.
During this process (MPSyncJob) the installed management packs from the Service Manager Management group (VM1) actually get deployed to the Data Warehouse management group (VM2).
The MPSyncJob process actually takes a couple of hours to complete.
You can view the job status in the Data Warehouse Jobs pane in the Service Manager console.
- Start the Service Manager console.
- In the Service Manager console, select Data Warehouse.
- In the Data Warehouse pane, expand Data Warehouse, and then click DW Jobs.
- In the Data Warehouse Jobs pane, click MPSyncJob.
- In the Tasks pane, under Synchronization, click Details.
- In the MP Sync Job dialog box, scroll to the right and examine the Status column.
- Scroll through the Status list. The management pack deployment process is complete when Associated or Imported is listed in the status column for all of the MPs.
Make sure that there is no status of either Pending Association or Failed in the status list. In the Data Warehouse Jobs pane, the status of the MPSyncJob will have changed from Running to Not Started.
There is another column not being shown: Datasource
“It is a best practice to not turn off any Service Manager computers or stop any Service Manager services during this time.” – Microsoft
Let’s walk through the Register with Service Manager Data Warehouse Wizard:
General info screen…
You can either use the drop down menu or enter the DW Mgmt Srv name.
The server name is masked out, but you will be required to Test Connection before continuing.
It is recommended to either create or select the Run As Account for the install.
Masked out my entries, but your previous entries will appear here.
Upon selecting Create, the wizard completes…
Data Warehouse Registration successful.
This is expected and the following walks you through the next steps.
Once the wizard is complete, you must enable the schedule for the Extract, Transform, and Load jobs (ETL) via PS.
Enable Data Warehouse job schedules:
Launch PowerShell and type the following commands:
Enable-SCDWJobSchedule –JobName Extract_<data warehouse management group name>
Enable-SCDWJobSchedule –JobName Extract_<Service Manager management group name>
Enable-SCDWJobSchedule –JobName Transform
Enable-SCDWJobSchedule –JobName Load
After completing the forementioned steps, you can use the console to perform the necessary Service Manager functions, or you can use PowerShell.
Service Center Windows PowerShell Cmdlets:
Get-SCDWJobSchedule – Displays the schedule for a data warehouse job
Get-SCDWJob – Retrieves current data warehouse jobs
Get-SCDWMgmtGroup – Shows details for a management group that is registered with the data warehouse
Remove-SCDWMgmtGroup – Removes a management group from the data warehouse
Set-SCDWJobSchedule – Sets the schedule for data warehouse jobs
Enable-SCDWJobSchedule – Enables a data warehouse job schedule
Disable-SCDWJobSchedule – Disables a data warehouse job schedule. Job schedules are disabled by default
Adjust Job Schedule and Frequency via PS:
Use the Set-SCDWJobSchedule Windows PowerShell cmdlet to schedule when data warehouse jobs run.
The Set-SCDWJobSchedule –ScheduleType Weekly cmdlet and parameter combination allows jobs to run only on the days specified.
For example, the following commands could be used to define a daily or weekly schedule:
Set-SCDWJobSchedule -JobName Transform –ScheduleType Daily -DailyFrequency 01:00:00 -DailyStart 06:00
Set-SCDWJobSchedule -JobName Transform -ScheduleType Weekly -WeeklyFrequency Tuesday, Thursday -WeeklyStart 06:00
Troubleshooting Data Warehouse Jobs:
If you need to troubleshoot one of the Data Warehouse Jobs, do the following:
Type Get-SCDWJob and look for any status that indicates the command failed.
Review the output, and locate any job with a status of “Failed.”
Type Get-SCDWJobModule -JobName Transform.Common. Specify the data warehouse job that failed as the value of the JobName parameter.
In the output, locate a status of “Failed,” and then review the Error Message column for more information about why the data warehouse job failed.
When you are ready to retry the failed job, type Resume-SCDWJob -JobName Transform.Common
Wow! That was a lot of work just to Register with Service Manager Data Warehouse.
I’ll share more shortly on what steps to take next…