job expectation module

Document: FTE Job Expectation Module Date: 20/01/2014

© 2014 by MQAttach SA and all associated companies. All rights reserved. Version: V1.0.0A

FTE Job Expectation Module

Disclaimer

While every reasonable precaution has been taken in the preparation of this document, neither the author nor the MQAttach

development team assumes responsibility for errors or omissions, or for damages resulting from the use of the information

contained herein. The information contained in this document is believed to be accurate. However, no guarantee is provided. Use

this information at your own risk.

This document is protected by copyright. No part of this document may be reproduced in any form or by any means, electronic,

mechanical, photocopying, recording, or otherwise, without prior written permission of MQAttach SA and all ideas and proposals or

artifacts expressed herein belong to MQAttach and remain the sole intellectually property of MQAttach



Contents 1. Introduction ............................................................................................................. 3

2. Defining a Job Expectation Rule ............................................................................. 4

2.1.1.1 Managing a Job Expectation Rule .................................................................................... 4

2.1.1.2 Job Name/Job Id Match .................................................................................................... 5

2.1.1.3 FTE Agent Selection ......................................................................................................... 5

2.1.1.4 Recurrence Interval .......................................................................................................... 6

2.1.1.5 Expected Count per Agent ............................................................................................... 6

3. Job Expectation Rule Evaluation ............................................................................ 7

3.1.1.1 Summary Job Expectation Evaluation .............................................................................. 8

3.1.1.2 Detail Job Expectation Evaluation .................................................................................... 9

4. Future Developments ........................................................................................... 11



1. Introduction The FTE Job Expectation Module was introduced as part of the MQAttach v1.14.0.0

This module allows users to define “Rules” based on FTE Job Names and other parameters, and for the MQAttach System to check if whether or not MQAttach Audit Information matches these rules at a specific point in time

The advantage of this module is that it allows customers to determine if specific FTE Jobs have been run for a point in time and if not to investigate why not and take corrective action

For example this module will answer the question:

“Have I received all my credit card transaction files for the day across my store agents ?”

The rules engine has a number of configurable parameters allowing the module to be very flexible and configurable. The exact details of rules configuration will be described in Defining a Job Expectation Rule

Once Rules are defined, users can request an analysis at any point in time, and both summary and detailed information can be provided – see Job Expectation Rule Evaluation



2. Defining a Job Expectation Rule

Job Expectation rules are defined using the Menu Option Administration – FTE Job Expectation Rules

2.1.1.1 Managing a Job Expectation Rule

A Name for the Rule

Rules are defined per Company and a Rule Name must be unique

Match Pattern –

This is the regular expression that will matched to determine if an FTE Transaction needs to be matched against this rule – In this case any FTE Job where the name starts with Store000 and is followed by a numeric value not exceeding 9 will be matched ie “Store0001” or “Store0002” but “Credit Card Job” will not be

included

A rule can be matched against FTE Job Id (meta-data tag jobNumber/mqaJobId) or an FTE Job Name (meta-data tag com.ibm.wmqfte.JobName)

Determine if the FTE Transaction Agent must be a source or a destination in order for the transaction to be matched (See FTE Agent Selection)

Defines the Recurrence for the Rule

For example if you expect “Credit Card Files” to be received by the agents specified, once every day you would specify one day

(see Recurrence Interval)

The number of jobs that must be matched per agent per reccurence interval for the rule to be considered fulfilled



A Job Expectation rule is defined by a Unique Name which must be provided and is stored at a company level (Different Companies have different rules)

2.1.1.2 Job Name/Job Id Match

An initial requirement for any Job Expectation rule is that a FTE transaction must match either a Job Name or Job Id in order to be included in the Expectation Evaluation

This value can be specified as a regular expression. Flexibility at this level allows for most use cases that may arise

The Audit Information Job Name or Job id are compared against this value to see if the transaction should be included in the evaluation

Matches are on one of the following:

Type Meta-Data/Transfer Element

Job Name com.ibm.wmqfte.JobName

(Job Name on the transfer template)

Job Id jobNumber or mqaJobId

2.1.1.3 FTE Agent Selection

A secondary requirement for any Job Expectation Rule is to specify the FTE agent or agents where the rule is to apply

For a specific transaction to be considered during evaluation, either the source or destination agent must match the FTE agents in the given group

Type Meta-Data/Transfer Element

Distribution List A list of FTE Agents based on FTE Agent Distribution List (Adminstration – FTE Agent Distribution Lists)

For example a value of “STORE_AGENTS” will attempt to find an FTE Agent Distribution List called “STORE_AGENTS” and validate against the FTE Agents in that list

Any Agent This option nullifies agent selection, and all Active FTE Agents are considered valid for evaluation

Wildcard This option allows only agent names that match a given wildcard string to be considered

For example:

AGENT1* will include any FTE Agent starting with the name “AGENT1” like “AGENT10”, “AGENT11” etc

*STORE* will consider any agent where the agent name contains the keyword “STORE”



2.1.1.4 Recurrence Interval

The final requirement for any Job Expectation Rule is that it must specify a recurrence interval

This information indicates the time period specification for which a given rule must be checked

For example a value of 1 Day indicates that this rule must be satisfied once a day within time period provided, in order for the expectation to have succeeded

A Value of 1 hour would mean that the rule must be satisfied once every hour within the time period provided in order for the expectation to have succeeded

The general rule of thumb here is from a business perspective how often do you expect the files to received within a given time period. This should be reflected in the recurrence interval

We also allow the specification of days to be excluded from the evaluation as non-working days. This is to allow for non-working hours and public holidays

Public Holidays can be defined by navigating to Administration – Public Holidays

Days specified here will be excluded from rule evaluation

2.1.1.5 Expected Count per Agent

This value indicates the actual FTE Transaction Count expectation for the rule and is defined per agent within the time period specified

For example a value of 2 with a recurrence of 1 day indicates that there is a expectation of 2 FTE jobs for every agent within the FTE Agent Selection for every day within the time period selection



3. Job Expectation Rule Evaluation

The Job Expectations will be evaluated for a given time period (Mandatory) and status (optional) and information presented to the user

The color scheme in use is as follows:

Color Explanation

Rules or Periods where the Job have been fully met

Rules or Periods within a Rule where the Expectations have been partially met

Period within a Rule where Jobs are Missing per FTE Agent

Rules or Periods within a Rules were not at ALL Met



3.1.1.1 Summary Job Expectation Evaluation

This will evaluate ALL Available Job Expectation Rules for the given Time Period and Status Filters

Rules will be shown with the appropriate color scheme value based on the outcome of the Rule Evaluation

A drill on a given Job Expectation rule via a double click will present the detail evaluation for the rule selected



3.1.1.2 Detail Job Expectation Evaluation

This function will evaluate a selected Job Expectation rule for the Selected Time Period and Display Detailed results –

Showing per Agent – Period, if:

The Expectation was Fully Met

Partially Met

Not met at all

Detail of the jobs where it was met or there was an error with the ability to further drill



4. Future Developments Some of the future developments for this module include

Integration with an enterprise scheduler so that Job Expectations can be evaluated automatically and notifications can be sent to interested parties with Evaluation Results

The basic concept is that when a Job Expectation Rule is captured, the administrator will be able to define a specific time for evaluation and notification information.

The system will interface with the scheduler and force evaluation of the rule at regular intervals

For example a rule that specifies a 2pm evaluation time, will interface with the system scheduler to run at 2pm and evaluate the rule and send the results to interested parties

This allows rules to evaluated automatically without any user intervention

job expectation module

Documents