Collecting data warehouse data with the Data Collection Component

Use the Data Collection Component to extract data from the data warehouse. Set up the data collection jobs to extract the data that you need.

1. Start the WebSphere Liberty server server, which hosts the Jazz® Team Server and Data Collection Component.
   For more information, see Deploying and starting the server.
   For the application server, you have the following options:

   WebSphere Liberty server

   You can quickly get started with running data collection jobs by running WebSphere Liberty server application server that is packaged with the Jazz Team Server. The Data Collection Component by default occupies the same ports as the Jazz Team Server: 9080 for HTTP and 9443 for HTTPS. If you need to change the ports, back up your server.xml file that is located in the <JTSInstallDir>\JazzTeamServer\server\liberty\servers\clm directory and edit the appropriate port numbers in the server.xml file. This server.xml file is created only after the first-time you start the Liberty server.

   Note:

   1. To start the WebSphere Liberty server server that is packaged with the Jazz Team Server:
      • In a command prompt, start the server from [JTSInstallDir]\JazzTeamServer\server\server.startup.bat
      The Liberty server successfully starts when the console outputs the message: Server clm started.
      Tip: On the Windows operating system, the Liberty server does not run in a visible console window.
      The following example displays how the console output appears when the Liberty server is first created and started:

      Server clm created.
      4547 File(s) copied
      Starting server clm.
      Server clm started.

   2. If you want to later stop Liberty that is packaged with the Jazz Team Server:
      • In a command prompt, stop the server from [JTSInstallDir]\JazzTeamServer\server\server.shutdown.bat
      The Liberty server successfully stops when the console outputs the message: Server clm stopped.

2. Open a web browser to the dedicated Data Collection Component location.

   The URL is https://<server>:<port>/dcc/web, where <server> is the fully qualified domain name or localhost and the context root is /dcc/web.

   Example:

   In a web browser, type the address: https://localhost:9443/dcc/web

3. When you are prompted, provide your user ID and password to authenticate the Data Collection Component application setup on the Jazz Team Server.

   The user ID must be a member in the JazzAdmins group.

   Example:

   1. Default user ID (case-sensitive): ADMIN
   2. Default password (case-sensitive): ADMIN
   3. Click Log In.

   Tip: If Data Collection Component is not registered with a Jazz Team Server, one of the following error messages is displayed in the web browser:

   Error!
   
   Data Collection Component could not be loaded due to a syntax error or missing dependency.
   Page ID: com.ibm.rational.datacollection.web.ui.internal.pages.DataCollectionManagementPage

   HTTP Status 503 - CRJAZ1173W The com.ibm.rational.datacollection.service.internal.web.IWebRedirector service is not available.

   For details on how to register Data Collection Component with the Jazz Team Server, see Running the setup by using Custom setup in the setup wizard.

   If Data Collection Component is not registered to the same Jazz Team Server as the other Engineering Lifecycle Management applications such as Engineering Test Management (QM) and Change and Configuration Management (CCM), the authentication does not work. In addition, the user must be available in the Administration - Data Collection Component (/dcc)> Active Users page (https://server:port/jts/admin#action=jazz.viewPage&id=com.ibm.team.repository.users). You can click the Administration icon from the product banner of the Administration - Data Collection Component (/dcc) page and select Manage Users to view the Active Users page.

4. If this is the first time you are opening the Data Collection Component application, you might get the following error message:

   Failed to load Licenses Data Collection resource.
   Error 500: CRRCD9002E The Data Collection Component is still initializing. Refresh the page a few minutes later.

   Wait a few minutes as the application is initializing and goes into a loading state. You can determine the initialization is complete when you refresh the web browser and the pages in the Data Collection Component are populated. For example, in the Data Collection Configuration page, wait for the sections under Data Warehouse Properties and Data Collection Properties to populate.
   Learn more about Data Collection Configuration and Administration pages:

   The Data Collection Configuration page displays the essential settings for managing the Data Collection Component.

   Advanced settings that are common settings among the administration pages for the Engineering Lifecycle Management applications are available for the Data Collection Component. To go to the administration page for Data Collection Component, select one of the following options:

   • When the Data Collection Component page (https://localhost:9443/dcc/web) is open in your web browser, you can click the Administration icon from the product banner and select Manage Application. The administration page for Data Collection Component page opens in the web browser with the page title: Administration - Data Collection Component (/dcc)
   • Alternatively, open a web browser to https://<server>:<port>/dcc/admin. For example, https://localhost:9443/dcc/admin
5. Test the data warehouse connection.
   Example:

   1. On the left-pane of the Data Collection Component application, under the Configuration section, click the Data Collection Configuration link.
   2. On the Data Collection Configuration page, click Test Connection.
   3. A successful data warehouse connection displays the message: Connection tested successfully.

      A failed data warehouse connection displays the message: Failed to connect to the data warehouse. For more details, click the show details link.

6. Configure resource groups.
   Important: This step is mandatory if you want to collect data from any of the following sources:

   • Engineering Lifecycle Management applications on a remote Jazz Team Server
   • IBM Engineering Requirements Management DOORS®

   When you run Data Collection Component on a local Jazz Team Server, resource groups are automatically set up for the Engineering Lifecycle Management applications and data warehouse that are registered on this same Jazz Team Server. You can continue to the next step as you are ready to collect data from applications on the local Jazz Team Server.

   Resource Groups are the applications containing the data that you want to collect and register in Data Collection Component to run data collection jobs against.

   Data Collection Component supports collecting data from the following Engineering Lifecycle Management applications:

   • Jazz Team Server
   • Engineering Requirements Management DOORS Next
   • IBM Engineering Workflow Management
   • IBM Engineering Test Management

   And from the following non-Engineering Lifecycle Management applications:

   • Engineering Requirements Management DOORS ,
     Important:

     Before you can collect data from DOORS , you must prepare the data in DOORS . See Configuring DOORS data for external applications.

   In addition, there is a special resource group, which is the data warehouse. This data warehouse is needed as a data source to create the fact and dimension tables for the data-mart. Under the Reporting Data Warehouse Database section, the username, password, and URL to the data warehouse must be specified.

   Before data collection jobs are run, the applications must be registered in Data Collection Component as resource groups. Resource groups are automatically configured for Engineering Lifecycle Management applications and data warehouse that are registered on the same Jazz Team Server as Data Collection Component. For Engineering Lifecycle Management applications, you can discover applications that are registered with a local or external Jazz Team Server or you can manually add the resource groups. For non-Engineering Lifecycle Management applications, you must manually add the resource groups.

   Example:

   1. On the left-pane of the Data Collection Component application, under the Configuration section, select the Resource Group Configuration link.
   2. To automatically detect applications that are registered with your Jazz Team Server, on the Resource Group Configuration page, click Discover. You can discover Engineering Lifecycle Management applications on either a local or remote Jazz Team Server one at a time, however you can repeat this step to register a mixture of local and remote resource groups:
      • To discover Engineering Lifecycle Management applications on a local Jazz Team Server:
        1. In the Add Resource Group window, you can view the list of Engineering Lifecycle Management applications local to your Jazz Team Server where Data Collection Component is also registered. By default, under the Application Instance column, the checkboxes are selected because the local Engineering Lifecycle Management applications have been automatically added as resource groups, and ready for running data collection jobs against them.
      • To discover Engineering Lifecycle Management applications on a remote Jazz Team Server:
        1. On the Add Resource Group window, select the Use an external JTS to discover applications checkbox. This checkbox discovers Engineering Lifecycle Management applications that are registered on a remote machine that is hosted in an external Jazz Team Server.
        2. In the JTS Root Uri field, specify the location of the external JTS: https://<hostname>:<port>/jts. For example: https://my.remote.host.com:9443/jts
        3. Click Discover to display a list of Engineering Lifecycle Management applications registered on the external Jazz Team Server on a remote machine.
        4. For example, under the Application Instance column, select the following list of checkboxes to the Engineering Lifecycle Management applications on the remote machine to add as a resource group for collecting and running data collection jobs:
           • /rm
           • /qm
           • my.remote.host.com:9443/jts
           • /ccm
        5. Click OK.
        6. Back on the Resource Group Configuration page, under each of the product groups you can see the resource groups that are added.
   3. To manually detect applications that are registered with your Jazz Team Server:
      Tip: If you want to add only Engineering Lifecycle Management applications as resource groups, you can skip this step if you already automatically detected and discovered the applications from the previous step. However, you must complete this step if you want to add non-Engineering Lifecycle Management applications as resource groups.
      1. On the Resource Group Configuration page, choose and expand one of the product groups that you want to add as a resource group.
      2. Click Add. A resource group entry is added under the selected product group.
      3. Expand the resource group entry that was added under the product group.
      4. Configure the location of the resource group by specifying the URL to the application registered on your Jazz Team Server. For example:

         Jazz Team Server

         https://<server>:<port>/jts

         Engineering Test Management

         https://<server>:<port>/qm

         Engineering Workflow Management

         https://<server>:<port>/ccm

         DOORS Next

         https:/<server>:<port>/rm

         DOORS

         https:/<server>:<port>/dwa-rrtranslator

   4. For each of these resource groups that was added, specify the additional configuration details, such as the authentication type, version, and unique identifier:
      1. In the Authentication type list, select the authentication setting of the resource group. The valid values are Username and Password, OAuth-JTS, or Jazz Security Architecture SSO:

         Username and Password

         When you select Username and Password as the authentication type, the Username and Password fields are displayed. In the Username field, specify the user name of the resource group. And in the Password field, specify the password of the resource group.

         OAuth-JTS

         When you select OAuth-JTS as the authentication type, the Consumer key and Secret fields are displayed. In the Consumer key field, specify the consumer key that is obtained from the Jazz Team Server.

         To obtain the consumer key from the Jazz Team Server:

         1. Go to the local Jazz Team Server. In Friends(outbound), add a friend list for the remote Engineering Workflow Management server with the following information, and click Next:
            • Root Services URI: https://<remoteccmhostname><:portnumber>/<ccm>/rootservices
            • Name
         2. Set the oAuth Secret as enable trusted, and click Create friend.
         3. Click Finish.
         4. On the remote ccm, consumer inbound page, approve the pending request under provisional keys session, click Save.
         5. On local Jazz Team Server, grab the consumer key and its corresponding secret created for the remote Engineering Workflow Management server created in Step1 under the friends bound. Use this key as the consumer key for Data Collection Component that is the resource group to be added for the remote ccm server.

         And in the Secret field, specify the secret of the consumer key.

         Tip: If the resource group is local to your Jazz Team Serverwhere Data Collection Component is also registered, the Consumer key and Secret fields are automatically complete with the values configured when the application was registered and finalized during the Jazz Team Server setup.

         Jazz Security Architecture SSO

         This option is available if you enabled Jazz Security Architecture single sign-on (SSO) authentication on all Jazz applications.

      2. In the Version field, specify the version-level of the resource group. For example, type 6.0 or 5.0 for the release of, or 9.6.1.6 for the release of DOORS .
      3. In the Unique Identifier field, specify a globally unique identifier that must never be changed in the future. This identifier is used to fill in the SOURCE_ID column of most data warehouse tables. For example "_8_QnwBLoEd2rmrYM7OkLOA". You can use a GUID generator such as www.guidgenerator.com to generate a unique identifier to copy and paste into that field.
      Remember: Under the Reporting Data Warehouse Database section, there is a special resource group which is the data warehouse. This data warehouse is needed as a data source to create the fact and dimension tables for the data-mart. You must configure the warehouse by specifying the username, password, and URL to the data warehouse. For example for a Derby data warehouse, specify the following configuration settings:

      • Relational Database Type: Derby Client
      • URL: //localhost:1527/conf/jts/derby/warehouseDB
      • For the User name and Password, keep the default value to none.
      • For the Version, select the version-level of the resource group from 6.0 or 5.0 release.
   5. Click the Test Connection link for each of the resource group that was added.
      • A successful connection to the resource group displays the following message: Successfully connected to the resource group.
      • A failed connection to the resource group displays the following message: Failed to connect to the resource group. For more details, click the show details link.
   6. Remember to click Save in the Resource Group Configuration page to avoid losing your newly added settings.
7. Specify the load type for the next data collection job.

   Full loads occur during the initial run of the data collection jobs, which builds all the data warehouse tables from scratch. These jobs take longer than typical data collection jobs that run delta builds, which collect only changes from the last time the job ran or a specified date. Any subsequent loads after the initial load or after running a job with a changed load type configuration, automatically defaults back to the Delta load since previous run setting.

   Remember: You must reserve full loads for populating a new or empty data warehouse database, and run delta loads for a data warehouse that is already populated with data.

   A full load can take a long time to complete, such as several days, depending on the amount of data to process. If you are required to do a full load, keep in mind that to generate complete and accurate reports, a full load needs to completely pull in all the data that exists in the configured resource group, for example a specified Engineering Lifecycle Management application. Otherwise, if a full load is interrupted, this interruption can cause your reports to contain incomplete or inaccurate data generated from a not entirely loaded data warehouse. In addition, an interrupted full load can cause the data collection jobs to fail.

   Example:

   You can change the next load configuration settings or keep the default load configuration at Delta load since previous run setting:

   1. On the left pane of the Data Collection Component application, under the Configuration section, select the Delta Load Configuration link.
   2. Under the Enabled column, select the checkbox of the resource group that you want to change the load configuration.
   3. Under the Load Type column, select one of the following load type options from the list:

      Full load

      This load job rebuilds all the data warehouse tables from scratch.

      Delta load since previous run

      This load job only loads the data that has changed or been added since the last successful load. This is the default setting.

      Delta load since date

      This load job requires you to specify a date to load the data that has changed or been added since the selected date.

   4. To apply the changes, click Save.

   Remember: When you change the next load job to a Full load or Delta load since date option, after the job runs with this load type, the load type setting automatically defaults back to the Delta load since previous run setting.
8. Decide which data collection jobs you want to run by loading, selecting, or removing any predefined or custom jobs.

   Custom jobs are jobs that you developed from a new or existing ETL (Extract, Transform, and Load) .ttl file. For details on creating custom jobs, see Wiki page.

   Predefined jobs, also referred to as out-of-box jobs, are jobs that are packaged with the product. You can use these predefined jobs as samples when you develop your own custom jobs. The predefined jobs are located inside the com.ibm.rational.datacollection.service.jar file in the following directory:

   • <installation directory>/server/conf/dcc/sites/dcc-updatesite/plugins/
     
     For example:
     C:\Program Files\ibm\JazzTeamServer\server\conf\dcc\sites\dcc-updatesite\plugins\com.ibm.rational.datacollection.service_<version>.jar

   If you want to view the predefined jobs, copy the com.ibm.rational.datacollection.service.jar to a temporary location outside of the product, and use an extraction tool to decompress the .jar file. You can find the predefined jobs in the /mapping directory inside the .jar file.

   Loading jobs:

   To load all the predefined (out-of-box) jobs and any jobs in the Data Collection Component mapping directory:

   1. If you want to run a job that you developed (custom job), you must add the custom .ttl job files in the Data Collection Component mapping directory. This directory is at <installation directory>/server/conf/dcc/mapping. For example, place your custom .ttl job files into the following directory: C:\Program Files\ibm\JazzTeamServer\server\conf\dcc\mapping.
   2. In the Data Collection Jobs page, click Load Jobs.
   3. Wait a few minutes for the jobs to load. You can refresh the web browser multiple times until all your jobs display in the Data Collection Jobs page.

   Remember: Each time Load Jobs is clicked, by default all the predefined jobs gets loaded with its default settings. In addition, any jobs in the Data Collection Component mapping directory also gets loaded.

   Removing jobs:

   To remove jobs that you do not want to run in the next data collection session:

   1. In the Data Collection Jobs page, locate the job that you want to remove.
   2. Under the Schedule column, hover and click the Delete data collection job icon ().

   Remember: If you click Load Jobs, your job removal selection might not persist. The Load Jobs action causes by default all the predefined jobs to get loaded with its default settings. In addition, any jobs in the Data Collection Component mapping directory are also loaded. The mapping directory is located in the <installation directory>/server/conf/dcc/mapping directory, for example: C:\Program Files\ibm\JazzTeamServer\server\conf\dcc\mapping.

   Selecting jobs:

   To select jobs that you want to run:

   1. In the Data Collection Jobs page, select the checkbox for each data collection job that you want to run.
   2. If you select a checkbox for a data collection job that is by default clear, a window pops up confirming if you are sure that you want to enable the job. The reason for the confirmation is because running this job can impact the performance of the corresponding applications and the overall time to collect data.

   Remember: If you click Load Jobs, your job selection might not persist. The Load Jobs action causes by default all the predefined jobs to get loaded with its default settings. In addition, any jobs in the Data Collection Component mapping directory are also loaded. The mapping directory is located in the <installation directory>/server/conf/dcc/mapping directory, for example: C:\Program Files\ibm\JazzTeamServer\server\conf\dcc\mapping.
9. Run the data collection jobs.

   You can choose to run all the data collection jobs, run a specific data collection, or run a specific data collection job.

   On the Data Collection Jobs page, you can see that Data Collection Component categorizes the jobs into data collections, such as Operational Data Store (ODS), Data-Mart, and Licenses.

   You no longer need to worry about running the jobs in a strict and proper sequence. The Data Collection Component offering is designed to improve performance by using parallel and concurrent processing. Jobs in a data collection, for example in an ODS data collection run in parallel concurrent process. But before the jobs in the Data-Mart data collection can start it needs to wait for the jobs in the ODS data collection to complete. The reason is because the Data-Mart data collection extracts data from the ODS data collection, transforms it using a set of rules, then loads it into the metrics tables as sets of point-in-time information and relationships. This process is cumulative, meaning that a new set of information is added each time the Data-Mart data collection job is run, resulting in a collection of many sets of point-in-time metrics and relationships. This type of data can be used for reports that show metrics, trends, aggregations, and other relationships among the data.

   Select your scope for running data collection jobs:

   Running all the data collection jobs:

   You can trigger the data collection jobs for all the registered applications at once. The jobs within an Operational Data Store data collection run in parallel concurrent process. However, before the jobs in the Data-Mart data collection can start it needs to wait for the jobs in the Operational Data Store data collection to complete.

   1. On the Data Collection Jobs page, click the Run all data warehouse collection jobs link.

   Running a specific data collection:

   You can trigger all the jobs in a data collection. The data collection groups are Operational Data Store (ODS), Data-Mart, and Licenses.

   1. On the Data Collection Jobs page, choose a data collection that you want to run:
      • ODS Data Collection
      • Data-Mart Data Collection
      • Licenses Data Collection
   2. Click the corresponding Run link available in the section heading of the data collection that you chose in the previous step.

   Running a specific data collection job:

   You can trigger a particular data collection job to run.

   1. On the Data Collection Jobs page, locate the job that you want to run.
   2. Under the Schedule column, hover and click the Run data collection job icon ().

   The status of each data collection job can change to one of these states:

   Idle

   The data collection job is inactive.

   Running

   The data collection job is in progress.

   Stopping

   The data collection job is terminating.

10. Monitoring the data collection jobs.

    On the Data Collection Jobs Status page, you can view your collection status. You can check what jobs are complete or currently running, and find the job logs.

    Example:

    1. Open the Data Collection Jobs Status page by going to the left-pane of the Data Collection Component application, under the Data Collection section, and click the Data Collection Jobs Status link.
    2. To refresh and see what jobs are still running or completed, click the Refresh button () next to the Data Collection Jobs Status link. The Data Collection Jobs Status link is available on the left-pane of the Data Collection Component application, under the Data Collection section.
       
    3. You can view the list of jobs that are running under the Currently Running Jobs section, which displays the following details:

       Job Name

       Displays the name of the data collection job that is running.

       Start Time

       Displays a Waiting to start status when a job is issued but not started. Displays the date and 24-hour clock timestamp when a job is started, for example: 2014-04-23 15:53:56

       Running Time

       Displays the length of time the job is running, since you last refreshed the Data Collection Jobs Status page. For example, 0 hours, 0 minutes, 12 seconds.

    4. You can view the list of jobs that are completed under the Job History section, which displays the following details:

       Job Name

       Displays the name of the data collection job that is completed.

       Status

       Displays if the job completed is Success, Failed, or Cancelled.

       Start Time

       Display the date and 24-hour clock timestamp when a job is started, for example: 2014-04-23 16:02:53

       End time

       Display the date and 24-hour clock timestamp when a job is completed, for example: 2014-04-23 16:02:55

       Time Taken

       Displays the total length of time to complete the job, for example 0 hours, 0 minutes, 2 seconds

    5. When you expand a job under the Job History section, you get the following details:

       Resource Group

       Displays the registered application that the job is collecting data from.

       Status

       Displays if the job completed is Success, Failed, or Cancelled.

       Start Time

       Displays the date and 24-hour clock timestamp when a job is started, for example: 2014-04-23 16:02:53

       End Time

       Displays the date and 24-hour clock timestamp when a job is completed, for example: 2014-04-23 16:02:55

       Running Time

       Displays the total length of time to complete the job, for example 0 hours, 0 minutes, 2 seconds

       Processed Resources

       Displays the number of records processed.

       Delivered Rows

       Displays the number of records that were delivered to the data warehouse.

       Failed Resources

       Displays the number of records that failed to deliver to the data warehouse.

       Log

       A Log link that you can click to download and view the log file.

    6. You can limit the number of records display in the job history. Under the Job History section, in the Number of previous jobs to display data for field, type the number of records you want to display in the job history, for example 20 and then click Run.
    7. You can delete the job history. Click the Delete History link for the following drop-down options:

       Delete All

       A Delete Job History window opens. Click OK to delete all job history. Or click Cancel.

       Delete Before

       You can select a date to delete all job history on or before the selected date.

       Delete After

       You can select a date to delete all job history on or after the selected date.

       Delete Between

       You can select two dates to delete all job history inclusively between the two selected dates.

11. Schedule data collection jobs.
    After you are satisfied with the initial run of your data collection job, you have the option to schedule your data collection jobs to run in multiple intervals or times throughout the day. You can trigger to run a data collection job by using either of the two schedule options:

    Interval schedule

    Runs a data collection job at every X number of minutes of the day.

    Daily schedule

    Runs a data collection job at particular times of the day.

    Example:

    1. Open the Data Collection Jobs page by going to the left-pane of the Data Collection Component application, under the Data Collection section, and click the Data Collection Jobs link.
    2. On the Data Collection Jobs page, choose a data collection group that you want to schedule the jobs:
       • ODS Data Collection
       • Data-Mart Data Collection
       • Licenses Data Collection
    3. Click the Schedule link available on the right-side of your selected data collection group.
    4. In the Edit schedule window, use the drop-down menu on the upper right to select one of the following schedule options:

       Interval Schedule

       1. By default the Enabled checkbox is selected to turn on the schedule. However, if you need to temporarily turn off the schedule, clear the Enabled checkbox, such as when performing a server rename. For more information, see Impact of server rename on the Data Collection Component.
       2. Under the Interval group, you can specify to collect data every X number of minutes, by typing a number in the Current time interval field. The minimum number of minutes is 5.
       3. Under the Week Days group, you can specify to collect data on certain days.
          • To select the multiple days of the week, press and hold down the Ctrl key and click the days of the week you want to collect data. For example, Monday, Wednesday, and Friday.
          • To select all the days of the week to collect data, click All.
       4. After you specify the interval schedule, click OK in the Edit schedule window.
          

       Daily Schedule

       1. By default the Enabled checkbox is selected to turn on the schedule. However, if you need to temporarily turn off the schedule, clear the Enabled checkbox, such as when performing a server rename. For more information, see Impact of server rename on the Data Collection Component.
       2. Under the Times group, you can specify more than one particular time of the day that you want to collect data. For example, run a 9:00 AM, noon, and before end of day 4:00 PM data collection job throughout the day.
          1. Click Create Time each time you want to add a time of the day entry.
          2. In the first drop-down menu, specify the hour of the day in a 24-hour clock.
          3. In the second drop-down menu, specify the minutes of the selected hour.
          4. To remove a time, click the Remove time icon that is next to the time entry that you want to remove.
             
       3. Under the Week Days group, you can specify to collect data on certain days at the previously specified times of the day.
          • To select the multiple days of the week, press and hold down the Ctrl key and click the days of the week you want to collect data. For example, Monday, through Friday.
          • To select all the days of the week to collect data, click All.
       4. After you specify the daily schedule, click OK in the Edit schedule window.
          

    5. To apply schedule settings, you must click Save in the Data Collection Jobs page.
    6. To remove a schedule setting:
       1. On the Data Collection Jobs page, choose a data collection group that you want to remove the schedule setting:
          • ODS Data Collection
          • Data-Mart Data Collection
          • Licenses Data Collection
       2. Click the Unschedule link available on the right-side of your selected data collection group.
       3. To apply the removal of the schedule settings, you must click Save available in the Data Collection Jobs page.
    For example, if you have a web client in Coordinated Universal Time (UTC) - X. The server (SaaS) at UTC time (here, X is 6) and when you schedule a job to run on:

    • Friday at 17:30, the actual job runs at Friday 23:30 (17:30 + 6 = 23:30)
    • Friday at 22:00, the actual job runs at Friday 4:00 [(22:00 + 6 = 28:00)-(24, since it crossed 24, 24 is subtracted from 28) = 4:00]
12. Get email notifications when a data collection job fails.
    Remember: Before you can receive email notifications from Data Collection Component, you must verify the Jazz Team Server is enabled to send email notifications by properly configured to integrate with an email server. For more information, see Configuring email settings.
    Example:

    1. On the left-pane of the Data Collection Component application, under the Configuration section, select the Data Collection Configuration link.
    2. In the Data Collection Properties section, click the Edit link.
    3. In the ETL Administrator E-mail List field, type an email address for subscribing to notifications when a data collection job fails. Multiple email addresses can also be specified by using a comma-separated list.
    4. Click Save to update your changes.

    A sample email notification from Data Collection Component:

    Data collection jobs failed for: https://<server>:<port>/dcc/web#action=com.ibm.rational.datacollection.manageResources.dataCollectionJobStatus
    
    [MapGroup]Name:WORKITEM_ODS_DB | Status: Failed | Start Time: Fri Sep 25 15:25:28 EDT 2015 | End Time: Fri Sep 25 15:25:30 EDT 2015 | Duration Time (milliseconds):1326 | Retreived Resources: 0 | Processed Resources:0 | Failed Resources:0 | Inserted Rows:0 | Updated Rows:0  
    [ResourceGroup]Name:RIDW | Status: Failed | Start Time: Fri Sep 25 15:25:28 EDT 2015 | End Time: Fri Sep 25 15:25:30 EDT 2015 | Duration Time (milliseconds):1139 | Retreived Resources: 0 | Processed Resources:0 | Failed Resources:0 | Inserted Rows:0 | Updated Rows:0