From b3a9d22f1cca9c0e945deb6364174023669bab17 Mon Sep 17 00:00:00 2001 From: MoKranda Date: Tue, 16 Jan 2024 09:16:23 -0600 Subject: [PATCH 1/2] corrected spelling and grammer --- docs/Access Codes.md | 3 - docs/Action Buttons.md | 15 +-- docs/Architecture.md | 2 +- docs/Calendars.md | 2 +- docs/Defining A Request.md | 2 +- docs/EM_Walkthroughs.md | 38 +++--- docs/EM_Walkthroughs_Alt.md | 67 ++++++++++ docs/Embedded Scripts.md | 108 +++++++--------- docs/Escalation Manager.md | 30 ++--- docs/Event Triggers.md | 6 +- docs/External Event Thresholds.md | 22 ++-- docs/File Arrival Jobs.md | 23 +++- docs/Frequency Definition Wizard.md | 24 ++-- docs/Job Dependency Types.md | 52 +++++--- docs/Notification Manager.md | 36 ++---- ...On Interval -- Annual Plan -- Odd Even.md} | 37 +++--- docs/On Request -- Periods.md | 46 +++---- docs/Operation Views.md | 4 +- docs/SM - Diagrams And Views.md | 2 +- docs/SM - Job Configuration.md | 2 +- docs/Schedule Builds.md | 4 +- docs/Support Information.md | 2 +- docs/Unit 1 Exercise 1.md | 12 +- docs/Unit 1 Exercise 3.md | 12 +- docs/Unit 1 Exercise 4.md | 7 +- docs/Unit 1 Exercise 6.md | 2 +- docs/Unit 1 Exercise 8.md | 30 +++-- docs/Unit 1 Lab.md | 35 ++--- docs/Unit 2 Exercise 1.md | 6 +- docs/Unit 2 Exercise 10.md | 44 +++---- docs/Unit 2 Exercise 11.md | 99 +++----------- docs/Unit 2 Exercise 12.md | 121 ++++++++++++++++++ docs/Unit 2 Exercise 3.md | 5 +- docs/Unit 2 Exercise 4 And 5.md | 2 +- docs/Unit 2 Exercise 6.md | 2 +- docs/Unit 2 Exercise 7.md | 50 ++++---- docs/Unit 2 Exercise 8.md | 16 ++- docs/Unit 2 Exercise 9.md | 28 ++-- docs/Unit 2 Lab A.md | 52 ++++---- docs/Unit 2 Lab B.md | 21 +-- docs/Unit 3 Exercise 1.md | 10 +- docs/Unit 3 Exercise 10.md | 2 +- docs/Unit 3 Exercise 11.md | 58 ++++----- docs/Unit 3 Exercise 13.md | 14 +- docs/Unit 3 Exercise 14.md | 6 +- docs/Unit 3 Exercise 8.md | 10 +- docs/Unit 3 Exercise 9.md | 6 +- docs/Unit 3 Lab B.md | 28 ++-- docs/Unit 3 Lab C.md | 4 +- docs/Unit 4 Exercise 1.md | 8 +- docs/Unit 4 Exercise 10.md | 6 +- docs/Unit 4 Exercise 11.md | 2 +- docs/Unit 4 Exercise 12.md | 8 +- docs/Unit 4 Exercise 2.md | 9 +- docs/Unit 4 Exercise 3.md | 6 +- docs/Unit 4 Exercise 4.md | 4 +- docs/Unit 4 Exercise 5.md | 2 +- docs/Unit 4 Exercise 6.md | 2 +- docs/Unit 4 Exercise 7.md | 4 +- docs/Unit 4 Exercise 8.md | 6 +- docs/Unit 4 Exercise 9.md | 2 +- docs/Unit 4 Lab A.md | 12 +- docs/Unit 4 Lab B.md | 8 +- docs/Update Master Job.md | 2 +- docs/User Mode.md | 2 +- docs/Viewing Process Indicators.md | 2 +- docs/Windows File Movement Job Sub-Types.md | 2 +- sidebars.js | 8 +- static/imgbasic/Click-n-Drag.png | 3 + 69 files changed, 716 insertions(+), 591 deletions(-) create mode 100644 docs/EM_Walkthroughs_Alt.md rename docs/{On Interval -- Odd Even -- Annual Plan.md => On Interval -- Annual Plan -- Odd Even.md} (91%) create mode 100644 docs/Unit 2 Exercise 12.md create mode 100644 static/imgbasic/Click-n-Drag.png diff --git a/docs/Access Codes.md b/docs/Access Codes.md index 67990da..32c6974 100644 --- a/docs/Access Codes.md +++ b/docs/Access Codes.md @@ -19,13 +19,10 @@ sidebar_label: 'Access Codes' ### Add Access Code - ![Access Codes Main Screen](../static/imgbasic/access-codes-main.png) - ![Access Codes Add](../static/imgbasic/sm-access-codes-add.png) - ## Enterprise Manager
diff --git a/docs/Action Buttons.md b/docs/Action Buttons.md index 7f4275f..802ddc2 100644 --- a/docs/Action Buttons.md +++ b/docs/Action Buttons.md @@ -6,18 +6,17 @@ sidebar_label: 'Action Buttons' The table contains the keyboard shortcuts for Solution Manager. If a shortcut has been implemented for a button, then the shortcut will be specified in the button tooltip. - | Shortcut | Function | | --- | --- | -| Ctrl+Alt+A | Admin Mode | -| Ctrl+Alt+H | Help | -| Ctrl+Alt+R | Refresh | -| Ctrl+Enter | Valid for form without Save button | -| Ctrl+B | Back | -| Ctrl+S | Save | +| CTRL + ALT + A | Admin Mode | +| CTRL + Space | Property Selector | +| CTRL + ALT + H | Help | +| CTRL + ALT + R | Refresh | +| CTRL + Enter | Valid for screens without a Save button | +| CTRL + B | Back | +| CTRL + S | Save | | Esc | Cancel/Undo/Exit/No | - ## Enterprise Manager
diff --git a/docs/Architecture.md b/docs/Architecture.md index 57fa2c8..701fbad 100644 --- a/docs/Architecture.md +++ b/docs/Architecture.md @@ -5,7 +5,7 @@ sidebar_label: 'Architecture' ### What is OpCon? -* A Platform independent Job Scheduling and Automation Solution that SMA provides to manage an entire Datacenter +* A Platform independent Job Scheduling and Automation Solution that SMA provides to manage an entire data center ![Picture3](../static/imgbasic/Picture3.png) diff --git a/docs/Calendars.md b/docs/Calendars.md index 9cbce79..490491d 100644 --- a/docs/Calendars.md +++ b/docs/Calendars.md @@ -46,7 +46,7 @@ sidebar_label: 'Calendars'
-In Enterprise Manager, **Calendars** is found in **Adminstration > Calendars** +In Enterprise Manager, **Calendars** is found in **Administration > Calendars** ### Calendar Screen Descriptions diff --git a/docs/Defining A Request.md b/docs/Defining A Request.md index 175aaf6..4f34483 100644 --- a/docs/Defining A Request.md +++ b/docs/Defining A Request.md @@ -2,7 +2,7 @@ sidebar_label: 'Defining A Request' --- -The Service Definition is composed of serveral fields, many of which are optional: +The Service Definition is composed of several fields, many of which are optional: ![](../static/imgbasic/SelfServiceRequestDetails.png) diff --git a/docs/EM_Walkthroughs.md b/docs/EM_Walkthroughs.md index 11b0d6c..6ee09ec 100644 --- a/docs/EM_Walkthroughs.md +++ b/docs/EM_Walkthroughs.md @@ -8,52 +8,52 @@ hide_title: true ### Enterprise Manager -|Schedules and Jobs || | | -|------------------ | ---------------| ------------- | ------------- | +|Schedules and Jobs | | | | +| --- | --- | --- | --- | | [Create a Schedule](../static/videobasic/U1E1.mp4) | [Create a Windows Job](../static/videobasic/U1E3.mp4) |[Schedule and Job Statuses](../static/videobasic/U1E7.mp4) | [Edit a Daily Job](../static/videobasic/U1E8.mp4) | | [Build a Schedule](../static/videobasic/U1E6.mp4) | [Null Jobs](../static/videobasic/U2E2.mp4) | [Workflow Designer](../static/videobasic/U1E10.mp4) | | Dependencies and Tags | | -| --------------------- | -------------- | +| --- | --- | | [Create Job Dependencies](../static/videobasic/U1E4.mp4) | [Create Tags/Tag Manager](../static/videobasic/U1E5.mp4) | | Using Properties | | | -| ---------------- | ------ | --------- | +| --- | --- | --- | | [Define a Global Property](../static/videobasic/U2E1.mp4) | [Define a System Property](../static/videobasic/U3E10.mp4) | [Define an Instance Property](../static/videobasic/U3E11.mp4) | | Machine Definition and Communication | | | -| ------------------------------------ | ------------------- | ------------------ | +| --- | --- | --- | | [Define a Machine (UNIX)](../static/videobasic/U2E3.mp4) | [Create a UNIX Job](../static/videobasic/U2E6.mp4) | [Correct a Communication Error](../static/videobasic/U2E4and5.mp4) | | Frequencies and Calendars || -| ----------- | -------------| -| [Create a Frequency (All Weeks, On Occurence, On Day) ](../static/videobasic/U2E8.mp4) | [Create a Frequency (OnRequest, Beginning, Middle, End of Period)](../static/videobasic/U2E9.mp4) | -| [Create a Frequency (On Interval, Annual Plan)](../static/videobasic/U2E10.mp4) | [Multiple and Negative Frequencies](../static/videobasic/U2E11.mp4) | +| --- | --- | +| [Create All Weeks, On Occurrence, and On Day Frequencies](../static/videobasic/U2E8.mp4) | [Create OnRequest, Beginning, Middle, and End of Period Frequencies](../static/videobasic/U2E9.mp4) | +| [Create On Interval and Annual Plan Frequencies](../static/videobasic/U2E10.mp4) | [Create Multiple or Negative Frequencies](../static/videobasic/U2E11.mp4) | | [Create and Update Calendars](../static/videobasic/U2E7.mp4) | | -| User and Account Management | | | | -| --------------------------- | --------------- | --------------- | ------------------ | +| User/Account Management | | | | +| --- | --- | --- | --- | | [Create a Role and User Account](../static/videobasic/U3E1.mp4) | [Manage Machine Privileges](../static/videobasic/U3E2.mp4) | [Manage Batch Users](../static/videobasic/U3E3.mp4) | [Manage Departmental Privileges](../static/videobasic/U3E4.mp4) | | [Manage Schedule Privileges](../static/videobasic/U3E5.mp4) | [Manage Function Privileges](../static/videobasic/U3E6.mp4) | [Manage Access Codes](../static/videobasic/U3E7.mp4) | | Notifications and Escalations | | -| ----------------------------- | ------------------- | +| --- | --- | | [Notification Manager](../static/videobasic/U3E8.mp4) | [Email Escalation](../static/videobasic/U3E9.mp4) | -|Events, Resources, Thresholds | | | -|----------|-------| ---------- | +| Events, Resources, Thresholds | | | +| --- | --- | --- | |[Events](../static/videobasic/U3E13.mp4) | [Events (Failure Criteria)](../static/videobasic/U3E14.mp4) | [Resources](../static/videobasic/U4E1.mp4) | | [Thresholds](../static/videobasic/U4E2.mp4) | [Thresholds (External Events)](../static/videobasic/U4E3.mp4)| -|Scripts|| -|------|------| +| Scripts | | +| --- | --- | | [Embedded Scripts](../static/videobasic/U4E4.mp4) | [Importing Scripts](../static/videobasic/U4E5.mp4)| -|SubsSchedules ||| -|------------- |-------|-------| +| SubSchedules | | | +| --- | --- | --- | |[SubSchedules (Mulitiple Runs)](../static/videobasic/U4E6.mp4) | [SubSchedules (Concurrent Processes)](../static/videobasic/U4E7.mp4)| [SubSchedules (Daily and Monthly Processes)](../static/videobasic/U4E8.mp4)| | -|File Transfer || -|------------- |---------| +| File Transfer | | +| --- | --- | |[SMA File Transfer (SMAFT)](../static/videobasic/U4E9.mp4)|[Windows File Movement (Job SubTypes)](../static/videobasic/U4E10.mp4)| |[Windows File Arrival](../static/videobasic/U4E11.mp4)|[Windows File Arrival (Multiple Files)](../static/videobasic/U4E12.mp4)| diff --git a/docs/EM_Walkthroughs_Alt.md b/docs/EM_Walkthroughs_Alt.md new file mode 100644 index 0000000..456f2e8 --- /dev/null +++ b/docs/EM_Walkthroughs_Alt.md @@ -0,0 +1,67 @@ +--- +sidebar_label: 'EM Walkthroughs' +hide_title: true +--- + +## Concept Walkthroughs + +### Unit 1 +| Topic | EM Video Link | +| --- | --- | +| Schedule Master | [Create a Schedule](../static/videobasic/U1E1.mp4) | +| Batch Job | [Unit 1 Exercise 2](../static/videobasic/U1E2.mp4) | +| Master Job| [Unit 1 Exercise 3](../static/videobasic/U1E3.mp4) | +| Dependencies | [Unit 1 Exercise 4](../static/videobasic/U1E4.mp4) | +| Tags and Tag Manager | [Unit 1 Exercise 5](../static/videobasic/U1E5.mp4) | +| Schedule Builds | [Unit 1 Exercise 6](../static/videobasic/U1E6.mp4) | +| Schedule and Job Statuses | [Unit 1 Exercise 7](../static/videobasic/U1E7.mp4) | +| Daily Jobs | [Unit 1 Exercise 8](../static/videobasic/U1E8.mp4) | +| Workflow Designer | [Unit 1 Exercise 10](../static/videobasic/U1E10.mp4) | + +### Unit 2 +| Topic | EM Video Link | +| --- | --- | +| Properties | [Unit 2 Exercise 1](../static/videobasic/U2E1.mp4) | +| Null Jobs | [Unit 2 Exercise 2](../static/videobasic/U2E2.mp4) | +| Define a Machine |[Unit 2 Exercise 3](../static/videobasic/U2E3.mp4) | +| Troubleshoot Communication Error |[Unit 2 Exercises 4 and 5 ](../static/videobasic/U2E4and5.mp4) | +| UNIX Job |[Unit 2 Exercise 6](../static/videobasic/U2E6.mp4) | +| Calendars (create and Update) |[Unit 2 Exercise 7](../static/videobasic/U2E7.mp4) | +| Frequencies:
  • All Weeks
  • On Occurrence
  • On Day
|[Unit 2 Exercise 8](../static/videobasic/U2E8.mp4) | +| Frequencies:
  • On Request
  • Beginning of Period
  • Middle of Period
  • End of Period
|[Unit 2 Exercise 9](../static/videobasic/U2E9.mp4) | +| Frequencies:
  • On Interval
  • Annual Plan
|[Unit 2 Exercise 10](../static/videobasic/U2E10.mp4) | +| Frequencies:
  • Multiple
  • Negative
|[Unit 2 Exercise 11](../static/videobasic/U2E11.mp4) | + +### Unit 3 +| Topic | EM Video Link | +| --- | --- | +| Users and Roles Management | [Unit 3 Exercise 1](../static/videobasic/U3E1.mp4) | +| Machine Privileges | [Unit 3 Exercise 2](../static/videobasic/U3E2.mp4) | +| Batch User Privileges | [Unit 3 Exercise 3](../static/videobasic/U3E3.mp4) | +| Departmental Function Privileges | [Unit 3 Exercise 4](../static/videobasic/U3E4.mp4) | +| Schedule Privileges | [Unit 3 Exercise 5](../static/videobasic/U3E5.mp4) | +| Function Privileges | [Unit 3 Exercise 6](../static/videobasic/U3E6.mp4) | +| Access Codes | [Unit 3 Exercise 7](../static/videobasic/U3E7.mp4) | +| Notification Manager | [Unit 3 Exercise 8](../static/videobasic/U3E8.mp4) | +| Escalation Manager | [Unit 3 Exercise 9](../static/videobasic/U3E9.mp4) | +| System Properties | [Unit 3 Exercise 10](../static/videobasic/U3E10.mp4) | +| Instance Properties | [Unit 3 Exercise 11](../static/videobasic/U3E11.mp4) | +| Events | [Unit 3 Exercise 12](../static/videobasic/U3E12.mp4) | +| Events Triggers | [Unit 3 Exercise 13](../static/videobasic/U3E13.mp4) | +| Events and Advance Failure Criterial | [Unit 3 Exercise 14](../static/videobasic/U3E14.mp4) | + +### Unit 4 +| Topic | EM Video Link | +| --- | --- | +| Resources | [Unit 4 Exercise 1](../static/videobasic/U4E1.mp4) | +| Thresholds | [Unit 4 Exercise 2](../static/videobasic/U4E2.mp4) | +| Thresholds via Events | [Unit 4 Exercise 3](../static/videobasic/U4E3.mp4)| +| Embedded Scripts (Existing) | [Unit 4 Exercise 4](../static/videobasic/U4E4.mp4) | +| Embedded Scripts (Importing New) | [Unit 4 Exercise 5](../static/videobasic/U4E5.mp4) | +| SubSchedule (Multiple Runs) | [Unit 4 Exercise 6](../static/videobasic/U4E6.mp4) | +| SubSchedule (Concurrent Processes) | [Unit 4 Exercise 7](../static/videobasic/U4E7.mp4)| +| SubSchedule (Daily/Monthly Processing) | [Unit 4 Exercise 8](../static/videobasic/U4E8.mp4)| +| SMA File Transfer (SMAFT) | [Unit 4 Exercise 9](../static/videobasic/U4E9.mp4) | +| Job Sub-Types |[Unit 4 Exercise 10](../static/videobasic/U4E10.mp4)| +| File Arrival (Single File) | [Unit 4 Exercise 11](../static/videobasic/U4E11.mp4)| +| File Arrival (Multiple Files) | [Unit 4 Exercise 12](../static/videobasic/U4E12.mp4)| \ No newline at end of file diff --git a/docs/Embedded Scripts.md b/docs/Embedded Scripts.md index d834a14..d6ce629 100644 --- a/docs/Embedded Scripts.md +++ b/docs/Embedded Scripts.md @@ -2,42 +2,51 @@ sidebar_label: 'Embedded Scripts' --- -* OpCon has ability to push Scripts from OpCon database to Windows and UNIX Machines (LSAMs) to run -* Database has centralized Repository that is replicated with database -* Version Control +* OpCon has ability to push Scripts from the OpCon database to Windows and UNIX environments +* The OpCon Database acts as a centralized Repository that is replicated with database +* The Repository allows for Version Control -* Four places used in OpCon to setup and use Embedded Scripts: - * Script Types - * Script Runners - * Script Repository - * Job Master +![](../static/imgbasic/sm-scripts.png) -### Embedded Scripts - Script Types +#### Four part make up Embedded Scripts -* Configure type of Scripts which can be stored by OpCon +* Script Types +* Script Runners +* Script Repository +* Job Master + +### Script Types +* Configure type of Scripts which can be stored by OpCon * There are 5 **predefined** Script types, but more can be added - * Command Shell (.cmd) - * Perl (.ps) - * PowerShell (.ps1) - * Python (.py) - * VBScript (.vbs) + * Command Shell (.cmd) + * Perl (.ps) + * PowerShell (.ps1) + * Python (.py) + * VBScript (.vbs) -### Embedded Scripts - Script Runners +![](../static/imgbasic/sm-script-types.png) -* Script Runners define Command Line created to run Script +### Script Runners -Example: +* Script Runners define Command Line created to run Script +* Allows more than one Script runner per Script Type -* Powershell includes ```“–ExecutionPolicy Bypass and –File”``` before command +![](../static/imgbasic/sm-script-runners.png) -* Allows more than one Script runner per Script Type +:::tip Example +* Powershell would include ```“–ExecutionPolicy Bypass and –File”``` before command, so the Script Runner would look like: ```powershell.exe -ExecutionPolicy Bypass -File $FILE $ARGUMENTS```. +::: ### Script Repository * Where Scripts are created and stored * Previous versions are accessible +![](../static/imgbasic/sm-add-script.png) + +#### Required Fields + * **Name** – Defines Name of Script (No spaces allowed in Name) * **Description** – Documents purpose of Script * **Open File** - Allows loading of Script from network @@ -45,71 +54,52 @@ Example: * **Type** – Specifies Script Type * **Initial Comments** – Documents differences between Script versions -### Assign a Role to a New Script +#### Assign a Role to a New Script * A Role must be assigned when a Script is created or imported to the Script Repository -### Embedded Scripts - Job Master - -* **Job Action** – Change from Run Program to Embedded Scripts -* **Script** – Specifies which script to call -* **Script Type** – Specifies Script Type for Selected Script -* **Runner** – Script Runner for Selected Script -* **Run Command Template** – Contents of Script Runner -* **Version** – Specifies Script Version selected -* **Arguments** – Enter the parameter(s) passed to Script (if needed) -* **Working Dir.** – Working Directory (starting directory) for Script - -## Solution Manager - -* In Solution Manager, **Scripts** is found in **Library > Administration > Scripts** - -### Scripts Menu - -![](../static/imgbasic/sm-scripts.png) - -### Script Types - -![](../static/imgbasic/sm-script-types.png) - -### Script Runners +![](../static/imgbasic/sm-assign-role-script.png) -![](../static/imgbasic/sm-script-runners.png) +#### Edit a Script -### Copy Script to Edit Version +* In the Repository, a **Copy** of the script must be made before you can **Edit** it. ![](../static/imgbasic/sm-copy-script-edit.png) ![](../static/imgbasic/sm-edit-script-version.png) -### Add Script +#### Deploy Script -![](../static/imgbasic/sm-add-script.png) - -### Assign a Role to a New Script - -![](../static/imgbasic/sm-assign-role-script.png) - -### Deploy Script +* Multiple jobs can run differnt versions of the same Embedded script. +* To have all jobs run the same version, one needs to **Deploy** that version to the jobs. ![](../static/imgbasic/sm-deploy-script-button.png) ![](../static/imgbasic/sm-script-deploy.png) -### Script Cross References +#### Script Cross References + +* Cross Reference in the Repository allows one to see all the jobs that are running the same script. ![](../static/imgbasic/sm-script-cross-references.png) :::warning - A Script with Cross References cannot be deleted - ::: -### Script in Job Properties +### Embedded Script Job ![](../static/imgbasic/sm-script-in-job-properties.png) +* **Job Action** – Change from Run Program to Embedded Scripts +* **Script** – Specifies which script to call +* **Script Type** – Specifies Script Type for Selected Script +* **Runner** – Script Runner for Selected Script +* **Run Command Template** – Contents of Script Runner +* **Version** – Specifies Script Version selected +* **Arguments** – Enter the parameter(s) passed to Script (if needed) +* **Working Dir.** – Working Directory (starting directory) for Script + ## Enterprise Manager * In Enterprise Manager, **Scripts** is found in **Scripts** diff --git a/docs/Escalation Manager.md b/docs/Escalation Manager.md index 580bff1..e12297b 100644 --- a/docs/Escalation Manager.md +++ b/docs/Escalation Manager.md @@ -6,17 +6,21 @@ sidebar_label: 'Escalation Manager' * Escalation Rules are tied to Notifications setup in Notification Manager * **Groups** must be created **BEFORE Rules** -### Escalation Manager - Groups +![](../static/imgbasic/sm-escalation-manager-main.png) + +### Groups * Groups specify who will be tied to a Notification * Email address is gathered from the User Account screen * Specifies who can acknowledge an Escalated Notification -### Escalation Manager - Global Property +![](../static/imgbasic/sm-escalation-manager-group.png) + +### Global Property * A Global Property can have OpCon automatically update which users are tied to group -### Escalation Manager - Rules +### Rules * Escalation Rules lists: * Which group will be alerted @@ -24,27 +28,17 @@ sidebar_label: 'Escalation Manager' * Minutes between alerts * Multiple Groups can be listed to elevate alerts after a configured number of Notifications -### Notification Manager - Escalation Rule +![](../static/imgbasic/sm-escalation-rule-add.png) + +![](../static/imgbasic/sm-escalation-rule-sequence.png) + +### Escalation Rule * Tie Escalated Notifications within Notification Manager * Only one Escalation Rule can be set up per Notification * Escalation Rules can only be set to emails at this time -### Primary Screen - -![](../static/imgbasic/sm-escalation-manager-main.png) - -### Add a Group - -![](../static/imgbasic/sm-escalation-manager-group.png) - -### Add a Rule -![](../static/imgbasic/sm-escalation-rule-add.png) - -### Rule Sequence - -![](../static/imgbasic/sm-escalation-rule-sequence.png) ## Enterprise Manager diff --git a/docs/Event Triggers.md b/docs/Event Triggers.md index 6fc5457..a17d3e5 100644 --- a/docs/Event Triggers.md +++ b/docs/Event Triggers.md @@ -8,10 +8,10 @@ sidebar_label: 'Event Triggers' ### Event Definition Wizard -![](../static/imgbasic/sm-event-triggers.png) - * An Event will send once a Job has reached any of the 9 statuses listed below: +![](../static/imgbasic/sm-event-triggers.png) + ### Event Trigger Details ![](../static/imgbasic/sm-event-trigger-details.png) @@ -20,6 +20,8 @@ sidebar_label: 'Event Triggers' ![](../static/imgbasic/sm-event-template-parameters.png) + + ## Enterprise Manager
diff --git a/docs/External Event Thresholds.md b/docs/External Event Thresholds.md index 4f5234d..0516a79 100644 --- a/docs/External Event Thresholds.md +++ b/docs/External Event Thresholds.md @@ -6,25 +6,23 @@ sidebar_label: 'External Event Thresholds' * As with any OpCon Event, ```$THRESHOLD:SET``` can be used as external Event * Benefit: Can use + and – as calculation +* Thresholds can be used to count files + +![](../static/imgbasic/sm-external-threshold-event.png) -Example: +:::tip Example ```$THRESHOLD:SET,,+1``` ```$THRESHOLD:SET,,-1``` +::: -* Thresholds can be used to count files - -Example: +:::tip Example * A Company receives some files every day that need to be counted - - * Use File Watcher process looking for files - * Each time file arrives, process will add ```1``` to Threshold - * Set Notification to relay Threshold value - -### Solution Manager - -![](../static/imgbasic/sm-external-threshold-event.png) + * Use File Watcher process looking for files + * Each time file arrives, process will add ```1``` to Threshold + * Set Notification to relay Threshold value +::: ### Enterprise Manager diff --git a/docs/File Arrival Jobs.md b/docs/File Arrival Jobs.md index 780cae3..11100d2 100644 --- a/docs/File Arrival Jobs.md +++ b/docs/File Arrival Jobs.md @@ -10,7 +10,6 @@ sidebar_label: 'File Arrival Jobs' ![](../static/imgbasic/File_Arrival_Windows_SM.png) - ### UNIX File Arrival Jobs * UNIX standard wildcards allowed in file name @@ -19,14 +18,26 @@ sidebar_label: 'File Arrival Jobs' ![](../static/imgbasic/File_Arrival_UNIX_SM.png) * File Arrival Job finishes OK - * Fails if file does not arrive in Time Stamp Window + * Fails if file does not arrive in Time Stamp Window * LSAMs (Windows and UNIX) set some Properties for that Job - * Work as Job Instance Properties for File Arrival Job: + * Work as Job Instance Properties for File Arrival Job: -![](../static/imgbasic/444.png)| +### File Arrival Properties -###### Example: +:::note +The file being searched in the table below for by the File Arrival job resides in **"D:\NewFiles\File123456789.txt"** +::: +| Property Name | Description | Example | +| --- | --- | --- | +| JI.$ARRIVED BASE FILE NAME | Resolves to the file found by the File Arrival job. | File123456789 | +| JI.$ARRIVED FILE EXTENSION | Resolves to the extension of the file found by the File Arrival job. | .txt | +| JI.$ARRIVED FILE NAME | Resolves to the directory path and file name of the file found by the File Arrival job. | D:\NewFiles\File123456789.txt | +| JI.$ARRIVED FILE PATH | Resolves to the directory path of the file found by the File Arrival job. | D:\NewFiles | +| JI.$ARRIVED SHORT FILE NAME | Resolves to the file name and extension of the found by the File Arrival job. | File123456789.txt | + + +:::tip Example * Receive 5 files and all should be processed the same way * Order of file processing does not matter * Set up: @@ -37,7 +48,7 @@ sidebar_label: 'File Arrival Jobs' * The Event adds a Multi-Instance Container Job that calls the processing SubSchedule * Once the Container Job finishes, it triggers the Event to restart the File Watcher * This will loop through all 5 files - +::: ## Enterprise Manager diff --git a/docs/Frequency Definition Wizard.md b/docs/Frequency Definition Wizard.md index 76e4735..b6c31f0 100644 --- a/docs/Frequency Definition Wizard.md +++ b/docs/Frequency Definition Wizard.md @@ -10,9 +10,9 @@ Click the **Add** button under the **Frequency list** to create a **New Frequenc Select an existing Frequency from the **Inactive** list and move it to the **Active** list -![](../static/imgbasic/SM_Frequency_Master_Job.png)| +![](../static/imgbasic/SM_Frequency_Master_Job.png) -![](../static/imgbasic/SM_Frequency_Manager_Wizard_Main.png)| +![](../static/imgbasic/SM_Frequency_Manager_Wizard_Main.png) :::caution Always start with **“When to Schedule”** @@ -21,16 +21,16 @@ Always start with **“When to Schedule”** * Depending on selection, different fields will be available * Select desired days, interval, occurrence, or period -![](../static/imgbasic/SM_Frequency_WhentoSchedule.png)| +![](../static/imgbasic/SM_Frequency_WhentoSchedule.png) * Frequencies reference two settings from a Schedule to determine what is considered a working day * Workdays per Week * Holiday Calendars * Selections for workdays per week and a Holiday Calendar will determine non-working days for that Schedule -![](../static/imgbasic/Frequency_Calendar.png)| +![](../static/imgbasic/Frequency_Calendar.png) -![](../static/imgbasic/SM_Frequency_Days.png)| +![](../static/imgbasic/SM_Frequency_Days.png) #### Frequency Definition Wizard - A/O/B/N @@ -40,7 +40,7 @@ Always start with **“When to Schedule”** * **Before Date** will run a Job on the first working day prior to a non-working day * **Not Schedule** will simply not run a Job on a non-working day -![](../static/imgbasic/SM_AOBN_Flag.png)| +![](../static/imgbasic/SM_AOBN_Flag.png) ## Enterprise Manager @@ -60,20 +60,20 @@ Always start with **“When to Schedule”** * Depending on selection, different fields will be available * Select desired days, interval, occurrence, or period -![](../static/imgbasic/231.png)| +![](../static/imgbasic/231.png) -![](../static/imgbasic/232.png)| +![](../static/imgbasic/232.png) -![](../static/imgbasic/233.png)| +![](../static/imgbasic/233.png) * Frequencies reference two settings from a Schedule to determine what is considered a working day * Workdays per Week * Holiday Calendars * Selections for workdays per week and a Holiday Calendar will determine non-working days for that Schedule -![](../static/imgbasic/234.png)| +![](../static/imgbasic/234.png) -![](../static/imgbasic/235.png)| +![](../static/imgbasic/235.png) #### Frequency Definition Wizard - A/O/B/N @@ -83,6 +83,6 @@ Always start with **“When to Schedule”** * **Before Date** will run a Job on the first working day prior to a non-working day * **Not Schedule** will simply not run a Job on a non-working day -![](../static/imgbasic/236.png)| +![](../static/imgbasic/236.png)
\ No newline at end of file diff --git a/docs/Job Dependency Types.md b/docs/Job Dependency Types.md index dadb4c3..0112d73 100644 --- a/docs/Job Dependency Types.md +++ b/docs/Job Dependency Types.md @@ -9,64 +9,78 @@ sidebar_label: 'Job Dependency Types' * **Excludes** – The selected Job will be removed from the Schedule on days the dependent Job is scheduled * **Conflict** – Dependent Job will not start if the selected Job is currently running -### Job Dependency Types - **After** +![Job Dependency Types](../static/imgbasic/sm-job-dependency-types.png) +#### Requires + +* Represented with a solid line +* Accounts for Jobs which are always part of the Workflow + +#### After + +* Represented with a dashed line * Accounts for Jobs which are occasionally part of the Workflow * If Job Dependencies must be tied upstream when After Dependencies are used -Example: - +:::tip Example * **Job 1** and **Job 3** have an everyday Frequency, **Job 2** is only built on Fridays * **Job 3** has an After Dependency on **Job 2** because it is only occasionally present * **Job 3** also needs a Dependency on **Job 1** to make sure **Job 1** runs before **Job 3** when **Job 2** does not exist +::: -### Job Dependency Types - **Excludes** +#### Excludes * Allows Monthly Jobs to automatically remove daily Jobs from a Schedule * Alternative to **Negative Frequencies** using **Do Not Schedule** * Excludes Dependencies are not represented in Forecast Screens * To test, build a Schedule for the proper date and include the correct Jobs -### Job Dependency Types - **Conflict** +#### Conflict * Allows Jobs to wait only if a dependent Job is running * Identified with Pink Lines in chart * If neither Job should start when the other is running, a Dependency should be set from **Job 1** to **Job 4** as well as from **Job 4** to **Job 1** -### Job Dependency - **Ignore Exit Code** +### Job Dependency Conditions -* **Ignore Exit Code** option is valid for either a **Requires** or a **After** Dependency Type -* If selected, the option will allow a selected Job to run once the Dependent Job is complete regardless of Exit Code status +![Job Dependency Conditions](../static/imgbasic/sm-job-dependency-conditions.png) -### Job Dependency - **Failed** +#### Finished OK + +* **Finished OK** option is valid for either the **Requires** or **After** Dependency Type +* If selected, the previous Job will need to have finished successfully before other Jobs can run. + +#### Failed * **Failed** option is valid for either the **Requires** or **After** Dependency Type * If selected, will allow the previous Job to fail then process other Jobs that are part of that path -### Job Dependency - **Offset** +#### Ignore Exit Code + +* **Ignore Exit Code** option is valid for either a **Requires** or a **After** Dependency Type +* If selected, the option will allow a selected Job to run once the Dependent Job is complete regardless of Exit Code status + +### Additional Settings + +#### Job Dependency - **Offset** * Allows Cross Day Dependencies * Uses Physical Day instead of Working Day by default * Unless the Job Dependency Offset Type in Server Options is set to **Occurrence** instead of default of **Calendar Days** -### Job Dependency - **Based on Frequency** +#### Job Dependency - **Based on Frequency** * Allows a Dependency to be set only when the Job is built using a specific Frequency * If no Frequency is selected, the Dependency is always true * Used in place of After Dependency -### Conflicts with other days +### Schedule Dependency Setting + +#### Conflicts with other days * Prevents a Schedule from opening until all Daily instances of that Schedule from previous days are complete * Use **Late to Start** notices if this parameter is used -### Dependency Types - -![](../static/imgbasic/sm-job-dependency-types.png) - -### Condition Types - -![](../static/imgbasic/sm-job-dependency-conditions.png) ## Enterprise Manager diff --git a/docs/Notification Manager.md b/docs/Notification Manager.md index 7fcc512..25642cf 100644 --- a/docs/Notification Manager.md +++ b/docs/Notification Manager.md @@ -10,59 +10,41 @@ sidebar_label: 'Notification Manager' ### Notification Triggers Main Screen -|| -|---| -|![](../static/imgbasic/sm-notification-trigger-main.png)| +![](../static/imgbasic/sm-notification-trigger-main.png) ### Add/Edit Trigger Output -|| -|---| -|![](../static/imgbasic/sm-notification-trigger-set-email.png)| +![](../static/imgbasic/sm-notification-trigger-set-email.png) ### Manage Trigger Groups -|| -|---| -|![](../static/imgbasic/sm-notification-triggers-manage-groups.png)| +![](../static/imgbasic/sm-notification-triggers-manage-groups.png) ## Enterprise Manager
-|| -|---| -|![](../static/imgbasic/320.png)| +![](../static/imgbasic/320.png) #### Add Schedule Trigger -|| -|---| -|![](../static/imgbasic/321.png)| +![](../static/imgbasic/321.png) #### Add Job Trigger -|| -|---| -|![](../static/imgbasic/322.png)| +![](../static/imgbasic/322.png) #### Machine Trigger -|| -|---| -|![](../static/imgbasic/323.png)| +![](../static/imgbasic/323.png) #### Schedule Select -|| -|---| -|![](../static/imgbasic/324.png)| +![](../static/imgbasic/324.png) #### Notification Types -|| -|---| -|![](../static/imgbasic/325.png)| +![](../static/imgbasic/325.png)
diff --git a/docs/On Interval -- Odd Even -- Annual Plan.md b/docs/On Interval -- Annual Plan -- Odd Even.md similarity index 91% rename from docs/On Interval -- Odd Even -- Annual Plan.md rename to docs/On Interval -- Annual Plan -- Odd Even.md index 4ffc46e..45139fa 100644 --- a/docs/On Interval -- Odd Even -- Annual Plan.md +++ b/docs/On Interval -- Annual Plan -- Odd Even.md @@ -1,17 +1,17 @@ --- -sidebar_label: 'On Interval -- Odd Even -- Annual Plan' +sidebar_label: 'On Interval -- Annual Plan --- Odd Even' --- -## Frequency Definition Wizard - On Interval, Odd & Even Weeks, Annual Plan +## Frequency Definition Wizard - On Interval, Annual Plan, Odd & Even Weeks ### On Intervals * Essentially the On Day option, but blocked in multiples of 5 (instead of creating 6 different Frequencies) -Or +-OR- - * Every X number of days starting on X date - * Start Date can be the same every year, or could be one time start date and increments keep going forever +* Every X number of days starting on X date +* Start Date can be the same every year, or could be one time start date and increments keep going forever * Other Fields: * **A/O/B/N** flag is applicable * The Calendar selected will block off days listed within a Calendar AFTER **A/O/B/N** days are set @@ -20,6 +20,20 @@ Or ![](../static/imgbasic/SM_OnIntervals_Dates.png) +### Annual Plan Calendars + +* Two Steps in Using Annual Plan Calendar: + * Create/Maintain Calendar + * Apply a Calendar to a frequency +* **A/O/B/N** is _NOT_ configurable +* Offsets use workdays + +![](../static/imgbasic/SM_AnnualPlan_Main.png) + +![](../static/imgbasic/SM_AnnualPlan_Offset.png) + +![](../static/imgbasic/SM_AnnualPlan_Forecast.png) + ### Odd and Even Weeks Odd Weeks @@ -43,19 +57,6 @@ Even Weeks * **A/O/B/N** flag is applicable * The Calendar selected will block off days listed within a Calendar AFTER **A/O/B/N** days are set -### Annual Plan Calendars - -* Two Steps in Using Annual Plan Calendar: - * Create/Maintain Calendar - * Apply a Calendar to a frequency -* **A/O/B/N** is _NOT_ configurable -* Offsets use workdays - -![](../static/imgbasic/SM_AnnualPlan_Main.png) - -![](../static/imgbasic/SM_AnnualPlan_Offset.png) - -![](../static/imgbasic/SM_AnnualPlan_Forecast.png) ## Enterprise Manager diff --git a/docs/On Request -- Periods.md b/docs/On Request -- Periods.md index 33bcf68..ade524c 100644 --- a/docs/On Request -- Periods.md +++ b/docs/On Request -- Periods.md @@ -2,7 +2,7 @@ sidebar_label: 'On Request -- Periods' --- -## Frequency Definition Wizard - On Request & Beginning, Middle, End of Period +## Frequency Definition Wizard -- On Request -- Beginning, Middle, End of Period ### On Request @@ -14,17 +14,6 @@ sidebar_label: 'On Request -- Periods' ![](../static/imgbasic/SM_Frequency_OnRequest.png) -### End of Period - -* Allows a Job to run on the Last day of Week, Month, Quarter, or Year -* Use **A/O/B/N** flag to specify the last working day of that Period -* Offset Days is in Working Days -* Other Fields: - * **A/O/B/N** flag is applicable - * The Calendar selected will block off days listed within a Calendar AFTER **A/O/B/N** days are set - -![](../static/imgbasic/SM_Frequency_EOP.png) - ### Beginning of Period * Allows a Job to run on the First of Week, Month, Quarter, or Year @@ -50,6 +39,17 @@ For 31 day months, 15.5 is rounded up to 16 ![](../static/imgbasic/SM_Frequency_MOP.png) +### End of Period + +* Allows a Job to run on the Last day of Week, Month, Quarter, or Year +* Use **A/O/B/N** flag to specify the last working day of that Period +* Offset Days is in Working Days +* Other Fields: + * **A/O/B/N** flag is applicable + * The Calendar selected will block off days listed within a Calendar AFTER **A/O/B/N** days are set + +![](../static/imgbasic/SM_Frequency_EOP.png) + ## Enterprise Manager
@@ -66,17 +66,6 @@ For 31 day months, 15.5 is rounded up to 16 ![](../static/imgbasic/240.png) -#### End of Period - -* Allows a Job to run on the Last day of Week, Month, Quarter, or Year -* Use **A/O/B/N** flag to specify the last working day of that Period -* Offset Days is in Working Days -* Other Fields: - * **A/O/B/N** flag is applicable - * The Calendar selected will block off days listed within a Calendar AFTER **A/O/B/N** days are set - -![](../static/imgbasic/241.png) - #### Beginning of Period * Allows a Job to run on the First of Week, Month, Quarter, or Year @@ -103,4 +92,15 @@ For 31 day months, 15.5 is rounded up to 16 ![](../static/imgbasic/24301.png) +#### End of Period + +* Allows a Job to run on the Last day of Week, Month, Quarter, or Year +* Use **A/O/B/N** flag to specify the last working day of that Period +* Offset Days is in Working Days +* Other Fields: + * **A/O/B/N** flag is applicable + * The Calendar selected will block off days listed within a Calendar AFTER **A/O/B/N** days are set + +![](../static/imgbasic/241.png) +
\ No newline at end of file diff --git a/docs/Operation Views.md b/docs/Operation Views.md index a0c5eea..b7255d3 100644 --- a/docs/Operation Views.md +++ b/docs/Operation Views.md @@ -32,7 +32,7 @@ sidebar_label: 'Operation Views' ### Diagrams and Views -* In the Diagram option of the Job Selection tab the user can select several options to manipulate PERT view in Solution Mananger: +* In the Diagram option of the Job Selection tab the user can select several options to manipulate PERT view in Solution Manager: * Progressive Discovery * A focused view of Dependency relationships * Isolate Dependency Chain View @@ -152,7 +152,7 @@ Example: * Open List or Matrix View * Open PERT View * Click PERT tab, then drag and drop to left until a rectangle appears -* The **Rectangle** represents new postion of PERT tab +* The **Rectangle** represents new position of PERT tab * Release mouse button ![Picture42](../static/imgbasic/Picture42.png) diff --git a/docs/SM - Diagrams And Views.md b/docs/SM - Diagrams And Views.md index f21a38f..f02b72f 100644 --- a/docs/SM - Diagrams And Views.md +++ b/docs/SM - Diagrams And Views.md @@ -4,7 +4,7 @@ sidebar_label: 'SM - Diagrams and Views' ### Solution Manager: Diagrams and Views -* In the Diagram option of the Job Selection tab the user can select several options to manipulate PERT view in Solution Mananger: +* In the Diagram option of the Job Selection tab the user can select several options to manipulate PERT view in Solution Manager: * Progressive Discovery * A focused view of Dependency relationships * Isolate Dependency Chain View diff --git a/docs/SM - Job Configuration.md b/docs/SM - Job Configuration.md index 982f4c5..a6e0af5 100644 --- a/docs/SM - Job Configuration.md +++ b/docs/SM - Job Configuration.md @@ -26,7 +26,7 @@ sidebar_label: 'SM - Job Configuration' Currently configurable options: * Machines/Machine Groups -* Prerun Command Line +* Pre-run Command Line * Working Directory * Failure Criteria * Run Command Line diff --git a/docs/Schedule Builds.md b/docs/Schedule Builds.md index d501a3f..2202275 100644 --- a/docs/Schedule Builds.md +++ b/docs/Schedule Builds.md @@ -54,11 +54,11 @@ sidebar_label: 'Schedule Builds' #### Autobuild -##### Autobuild Example 1: +##### Auto-build Example 1: ![Picture30](../static/imgbasic/Picture30.png) -##### Autobuild Example 2: +##### Auto-build Example 2: ![Picture31](../static/imgbasic/Picture31.png) diff --git a/docs/Support Information.md b/docs/Support Information.md index 4af1281..cee15e1 100644 --- a/docs/Support Information.md +++ b/docs/Support Information.md @@ -39,7 +39,7 @@ sidebar_label: 'Support Information' ##### OpCon Roundtables * SMA Roundtables -* Roundtables are frequent OpCon-centered technical discussions and Q & A sessions hosted digitally the third Thursday of each month by Product Manangement and Technical Specialists. +* Roundtables are frequent OpCon-centered technical discussions and Q & A sessions hosted digitally the third Thursday of each month by Product Management and Technical Specialists. ##### Webinars diff --git a/docs/Unit 1 Exercise 1.md b/docs/Unit 1 Exercise 1.md index 4d8a3f7..7c9ea87 100644 --- a/docs/Unit 1 Exercise 1.md +++ b/docs/Unit 1 Exercise 1.md @@ -15,15 +15,15 @@ Create a Schedule named **MY FIRST SCHEDULE**. Provide documentation about this ### Instructions 1. In Solution Manager, from the **Home** tab, select **Studio**. -2. Click the **Add** button on the toolbar. -3. In the Schedule Name textbox, enter **My First Schedule**. -4. In the Documentation textbox, enter **This is a training schedule**. -5. In the **Schedule Build and Maintenance** frame, select the **Auto Build** checkbox. +2. Click the **Add** button in the toolbar. +3. In the **Schedule Name** textbox, enter **My First Schedule**. +4. In the **Documentation** textbox, enter **This is a training schedule**. +5. In the **Schedule Build and Maintenance** section, select the **Auto Build** checkbox. 6. Set ```7``` for the number of days in advance for Auto Build. 7. Set ```1``` for the number of days to Auto Build. 8. Select the **Auto Delete** checkbox. 9. Set ```7``` for the number of days to Auto Delete. -10. Click the Save button. +10. Click the **Save**. 11. Close **Studio**. ## Enterprise Manager @@ -35,7 +35,7 @@ Create a Schedule named **MY FIRST SCHEDULE**. Provide documentation about this ::: Steps to Create a Schedule -1. In **Librarby** > **Administration**, double-click on **Schedule Master**. +1. In **Library** > **Administration**, double-click on **Schedule Master**. 2. Click the **Add** button on the toolbar. 3. In the Name textbox, enter **My First Schedule**. 4. In the Documentation textbox, enter **This is a training Schedule**. diff --git a/docs/Unit 1 Exercise 3.md b/docs/Unit 1 Exercise 3.md index 31d36ab..b269e14 100644 --- a/docs/Unit 1 Exercise 3.md +++ b/docs/Unit 1 Exercise 3.md @@ -6,7 +6,7 @@ sidebar_label: 'Unit 1 Exercise 3' ### Objective -To succesfully add 4 Windows jobs to My First Schedule. +To successfully add 4 Windows jobs to My First Schedule. ### Summary @@ -21,12 +21,12 @@ Each of the 4 jobs will use the **Inactive Frequency** called **Example-Mon-Sun- 1. In Solution Manager, select **Studio**. 2. In the **Schedule List**, select **My First Schedule**. 3. Click the **View** button in the toolbar. -4. In the Menu to the right, select **Add Job**. +4. In the **Menu** to the right, select **Add Job**. #### Create Your First Job -5. In the Name textbox, enter **Windows Job 1** -6. In the Job Type drop-down list, select **Windows**. +5. In the **Name** textbox, enter **Windows Job 1** +6. In the **Job Type** drop-down list, select **Windows**. 7. Expand the **Task Details** section to open the Details box. 8. In the **Machine Selection** section, select the **SMATraining** machine from the **Machines or Machine Group** drop down. 9. In the **General** section, select **SMATRAINING\SMAUSER** from the **User Id** drop down. @@ -35,13 +35,13 @@ Each of the 4 jobs will use the **Inactive Frequency** called **Example-Mon-Sun- "C:\Program Files\OpConxps\MSLSAM\genericp.exe" -t10 ``` 11. Click the **Save** button. -12. Click the **Lock** button in the top right-hand corner of the **Master Job Details** screen. +12. Click the **Lock (or CTRL + Alt + A)** button in the top right-hand corner of the **Master Job Details** screen. 13. Scroll down and expand the **Frequency** section. 14. From the **Inactive** column, select the Frequency named **Example-Mon-Sun-O** and click the **<** button to move the Frequency to **Active** column. 15. Click **Save**. 16. Close **Studio** and **Library**. -#### Duplicate Windows Job 1 +#### Create Windows Job 2, 3, and 4 17. Navigate to **Library**. 18. Select **Master Jobs** under the **Administration** column. diff --git a/docs/Unit 1 Exercise 4.md b/docs/Unit 1 Exercise 4.md index 563e8c8..a3e4fe9 100644 --- a/docs/Unit 1 Exercise 4.md +++ b/docs/Unit 1 Exercise 4.md @@ -30,13 +30,14 @@ Utilize a **REQUIRES - Finished OK Dependency** between each of the four 4 jobs #### Set remaining Dependencies 10. Click on **Windows Job 3**. -11. Repeat Steps 5-8 to create a dependency between **Windows Job 2** and **Windows Job 3**. +11. Repeat Steps 5-9 to create a dependency between **Windows Job 2** and **Windows Job 3**. 12. Click on **Windows Job 2**. -13. Repeat Steps 5-8 to create a dependency between **Windows Job 1** and **Windows Job 2**. +13. Repeat Steps 5-9 to create a dependency between **Windows Job 1** and **Windows Job 2**. 14. Close **Studio** :::tip -You can also 'Click and Drag' from dot to dot on each job to pull up the Job Dependency window. +You can also 'Click and Drag' from the bottom dot on a job to the top dot on the next job to pull up the Job Dependency window. +![Click-n-Drag Dependency Creation](../static/imgbasic/Click-n-Drag.png) ::: ## Enterprise Manager diff --git a/docs/Unit 1 Exercise 6.md b/docs/Unit 1 Exercise 6.md index 4a6c980..e9f5140 100644 --- a/docs/Unit 1 Exercise 6.md +++ b/docs/Unit 1 Exercise 6.md @@ -32,7 +32,7 @@ Build the schedule called **MY FIRST SCHEDULE** as **Released** for today only. 10. Select **Tags** from the **Job Filters** menu. 11. Select either ```CRITICAL``` or ```GENERICP``` from the **Tags** list. 12. You should see **Windows Job 1-Windows Job 3**. -13. Close **Operations**. +13. Close **Operations** once all jobs **Finished OK**. ## Enterprise Manager diff --git a/docs/Unit 1 Exercise 8.md b/docs/Unit 1 Exercise 8.md index d363722..94eed7c 100644 --- a/docs/Unit 1 Exercise 8.md +++ b/docs/Unit 1 Exercise 8.md @@ -39,15 +39,20 @@ The job **Wrong Path** will have an **Return Code** of ```31001```. This **Retur #### Correct the Daily Job Definition 10. The **Daily Job Definition** screen will appear. -11. Click the **Lock** icon in the upper right-hand corner. +11. Click the **Lock (or CRTL + ALT + A)** icon in the upper right-hand corner. 12. Expand the **Task Details** section. 13. In the **Run** section, modify the **Command Line** AND **Working Directory** paths from ```MSLSAM2``` to ```MSLSAM```. -14. Click the **Save** button. + +:::info +We can validate that this is the error by navigating to that location via a Windows Explorer Window on this server. You will notice that in the OpConxps directory there is no MSLSAM2 directory. +::: + +14. Click the **Save**. This should take you back to the Processes screen. #### On the Processes screen -15. In the **Job Selection** menu, click **Job Status Update** and select **Restart**. +15. The **Job Selection** menu should still be open, click **Job Status Update** and select **Restart**. 16. Close the **Job Selection** menu. -17. The job should have a **Finished OK** status because you corrected the invalid command in the **Command Line**. +17. The job should have a **Finished OK** status because the invalid command in the **Command Line** has been corrected. 18. In the **Processes** screen, in the **Date** list, select tomorrow’s date. 19. Select the **Murphy’s Law** shedule with tomorrow's date in the **Date** column in the **Schedule** section. 20. Right-click on the **Wrong Path** Job. @@ -56,16 +61,17 @@ The job **Wrong Path** will have an **Return Code** of ```31001```. This **Retur #### On the Daily Job Definition screen 22. Expand the **Task Details** section. 23. Notice that the paths still contains **MSLSAM2** instead of **MSLSAM**. -24. Don’t make any changes. -25. Close **Operations**. :::info -Remember that you need to rebuild all copies of the Daily Tables when the Master Record is changed. +This is because only today's instance of the job has been corrected. All other versions in the Processes screen will have the error. In order to correct the other daily instances, the Master version will need to be corrected and the Schedule will need to be rebuilt. ::: +24. Don’t make any changes. +25. Close **Operations**. + #### Correcting the Master Job 26. Navigate to **Library**, click the **Master Jobs** topic. -27. Use the search field at the top of the **Master Job** list to locate the **Wrong Path** Job in the **Murphys Law** Schedule. +27. Use the search field at the top of the **Master Job** list to locate the **Wrong Path** Job in the **Murphy's Law** Schedule. 28. Select the job and click the **Edit** button. 29. Click the **Lock** icon in the upper right-hand corner. 30. Expand **Task Details** and locate the **Run** section. @@ -73,7 +79,11 @@ Remember that you need to rebuild all copies of the Daily Tables when the Master 32. Click **Save**. 33. Close **Library**. -#### Rebuild the Furture Dates +:::info +Remember that all future instances of the Schedule will need to be rebuild after the Master version has been changed. +::: + +#### Rebuild the Future Dates 34. Select the **Operations** tab, then click on **Schedule Build**. 35. In the **From** field select tomorrow. 36. In the **To** field select 7 days from today. @@ -81,7 +91,7 @@ Remember that you need to rebuild all copies of the Daily Tables when the Master 38. Click the **Overwrite Existing Schedules** toggle to turn on. 39. In the **Schedule Selection** section, select **Murphy's Law**. 40. Click the **Build** button. -41. Click the link for the **Murphys Law** schedule for any date you just built out. +41. Click the link for the **Murphy's Law** schedule for any date you just built out. #### Validate the Change 42. Right-click on the **Wrong Path** job. diff --git a/docs/Unit 1 Lab.md b/docs/Unit 1 Lab.md index 77a2c50..d672fd6 100644 --- a/docs/Unit 1 Lab.md +++ b/docs/Unit 1 Lab.md @@ -31,7 +31,7 @@ Congo Online Retail Inc. needs to run inventory reports every day starting at 8: * Auto-delete the Schedule for ```7``` days ago :::tip -* You can reference [Unit 1 - Exercise 1](/docs/Unit%201%20Exercise%201.md) for steps on how to create a Schedule. +* You can reference [**Unit 1 - Exercise 1**](/docs/Unit%201%20Exercise%201.md) for steps on how to create a Schedule. ::: * Create a **Windows Job** for **each of the products in the introduction** @@ -39,41 +39,46 @@ Congo Online Retail Inc. needs to run inventory reports every day starting at 8: * These jobs need to run on the ```SMATRAINING``` **Machine** * These jobs need to run as the ```SMATRAINING\SMAUSER``` **User ID** * Each of the six jobs will use the following command line: +```cmd +"C:\Program Files\OpConxps\MSLSAM\genericp.exe" -t15 -e0 ``` -“C:\Program Files\OpConxps\MSLSAM\genericp.exe” –t15 –e0 -``` -* The Jobs must run Monday-Friday -* Use the **Inactive Frequency**: ```Mon-FriOnDate``` -* Click the Forecast button to be sure the frequency matches the requirement. * Add **Documentation** for each Job. * Example: This Job is reporting inventory for the number of Legos in Stock :::tip -* You can reference [Unit 1 - Exercise 3](/docs/Unit%201%20Exercise%203.md) for steps on how to create jobs and add a frequency. +You can reference [**Unit 1 - Exercise 3**](/docs/Unit%201%20Exercise%203.md) for steps on how to create Jobs. ::: -* The Jobs must run in the following order with each job **requiring** the job before it to **Finish OK**: - * **Legos** → **Nerf** → **Smartphones** → **XBOX** → **Levis** → **Nike** - * Visual representation at bottom of lab. +* **Tag** each of the jobs according to the appropriate category: **Toys**, **Electronics** or **Clothing**. :::tip -* You can reference [Unit 1 - Exercise 4](/docs/Unit%201%20Exercise%204.md) for steps on how to create dependencies. +You can reference [**Unit 1 - Exercise 5**](/docs/Unit%201%20Exercise%205.md) for steps on how to add Tags. ::: -* **Tag** each of the jobs according to the appropriate category: **Toys**, **Electronics** or **Clothing**. +* The Jobs must run Monday-Friday +* Use the **Inactive Frequency**: ```Mon-FriOnDate``` +* Click the Forecast button to be sure the frequency matches the requirement. + +:::tip +You can reference [**Unit 1 - Exercise 3**](/docs/Unit%201%20Exercise%203.md) for steps on how to add a Frequency. +::: + +* The Jobs must run in the following order with each job **requiring** the job before it to **Finish OK**: + * **Legos** → **Nerf** → **Smartphones** → **XBOX** → **Levis** → **Nike** + * Visual representation at bottom of lab. :::tip -* You can reference [Unit 1 - Exercise 5](/docs/Unit%201%20Exercise%205.md) for steps on how to add Tags. +You can reference [**Unit 1 - Exercise 4**](/docs/Unit%201%20Exercise%204.md) for steps on how to create Dependencies. ::: * **Build the schedule** so that it runs today and the rest of the week prior to class starting. * **Check the status** of the Schedule and Jobs in the **Processes** screen to ensure all the jobs ran successfully. :::tip -* You can reference [Unit 1 - Exercise 6](/docs/Unit%201%20Exercise%206.md) for steps on how to build the Schedule. +You can reference [**Unit 1 - Exercise 6**](/docs/Unit%201%20Exercise%206.md) for steps on how to build the Schedule. ::: -Upon completion, the Jobs will run in this order: +Upon completion, the jobs will run in this order: ![Run Order](../static/imgbasic/unit1lab1dependencyview.png) \ No newline at end of file diff --git a/docs/Unit 2 Exercise 1.md b/docs/Unit 2 Exercise 1.md index fcfbc90..16bda79 100644 --- a/docs/Unit 2 Exercise 1.md +++ b/docs/Unit 2 Exercise 1.md @@ -10,7 +10,7 @@ To replace hardcoded text in the command line with Global Properties so that the ### Summary -Create two Global Properties, ```RUNTIME``` with a value of ```10``` and ```PATH_Windows``` with a value of ```C:\Program Files\OpConxps\MSLSAM```. For four of the jobs in **MY FIRST SCHEDULE**, replace the hardcoded text with the newly created properties. +Create two Global Properties, ```RUNTIME``` with a value of ```10``` and ```PATH_Windows``` with a value of ```C:\Program Files\OpConxps\MSLSAM```. For three of the jobs in **MY FIRST SCHEDULE**, replace the hardcoded text with the newly created properties. Build **MY FIRST SCHEDULE** for today, then view the schedule's performance in Processes screen. Verify that the proper values are attributed to the Properties used. @@ -54,7 +54,7 @@ The command line should change from ```“C:\Program Files\OpConxps\MSLSAM\gener :::info Note Your updated **Command Line** should now look like: -```“[[PATH_Windows]]\genericp.exe” –t[[RUNTIME]]``` +```"[[PATH_Windows]]\genericp.exe" -t[[RUNTIME]]``` ::: 26. Click the **Save** button. @@ -74,7 +74,7 @@ Your updated **Command Line** should now look like: 37. Right-click on one of the four jobs that were modified. 38. In the **Job Selection** panel, select **Job Output**. 39. Click **Refresh**. -40. Click on the link that appears after the **Refresh** is compelete. +40. Click on the link that appears after the **Refresh** is complete. 41. Look at lines four and five and validate that the **Global Properties** resolved to ```C:\Program Files\OpConxps\MSLSAM``` and ```10``` respectively. 42. Close the **Job Output**. 43. Close **Operations**. diff --git a/docs/Unit 2 Exercise 10.md b/docs/Unit 2 Exercise 10.md index fff3fa1..5514f33 100644 --- a/docs/Unit 2 Exercise 10.md +++ b/docs/Unit 2 Exercise 10.md @@ -23,13 +23,11 @@ In the **Annual Plan Freq** job, create a new frequency that will utilize a cust In the **Annual Plan Plus One Freq** job, create a new frequency that will utilize a custom calendar with a day offset of one. ### Instructions - 1. In **Studio**, select the **Frequency Practice** Schedule and click **View**. 2. In the side menu, select **Add Job**. #### Create the On Interval Freq Job - -3. In the **Name** field, enter **All Weeks Freq**. +3. In the **Name** field, enter **On Interval Freq**. 4. Leave the **Job Type** as **Null Job**. 5. Click the **Save** button. 6. Click the **Lock** button to enter **Admin Mode**. @@ -42,15 +40,15 @@ In the **Annual Plan Plus One Freq** job, create a new frequency that will utili * In the **A/O/B/N** section, select **Before Date**. * Make sure the **Day Type** is set to **Working**. * Click the **Save** button. -10. In the **Active** column, select the frequency then select **Forcast**. +10. In the **Active** column, select the frequency then select **Forecast**. :::tip The **Forecast** screen should show the **15th and 30th days of each month** as green. If the 15th or 30th is a holiday the previous working day should be green. ::: -#### Create the Annual Plan Freq Job - 11. Click the **Back** button to navigate back to the **Studio** workspace. + +#### Create the Annual Plan Freq Job 12. In the side menu, select **Add Job**. 13. In the **Name** field, enter **Annual Plan Freq**. 14. Leave the **Job Type** as **Null Job**. @@ -62,35 +60,35 @@ The **Forecast** screen should show the **15th and 30th days of each month** as * In the **Name** field, enter ```Annual```. * In the **When to Scheduled** dop-down menu, select **Annual Plan**. * In the **Calendar** drop-down menu, select **Master Calendar**. - * In the **A/O/B/N** section, select **Before Date**. + * In the **A/O/B/N** section, select **On Date**. * Click the **Save** button. -20. In the **Active** column, select the frequency then select **Forcast**. +20. In the **Active** column, select the frequency then select **Forecast**. :::tip -The **Forecast** screen should show the **date you selected in Exercise 7** as green. +The **Forecast** screen should show the **dates selected on the Master Calendar in Exercise 7** as green. ::: -#### Create the Annual Plan Plus One Freq Job +21. Click the **Back** button to navigate back to the **Studio** workspace. -11. Click the **Back** button to navigate back to the **Studio** workspace. -12. In the side menu, select **Add Job**. -13. In the **Name** field, enter **Annual Plan Plus One Freq**. -14. Leave the **Job Type** as **Null Job**. -15. Click the **Save** button. -16. Click the **Lock** button to enter **Admin Mode**. -17. Expand the **Frequency** section, if not already expanded. -18. Click the **Add** button. -19. In the **Frequency Manager Wizard**: - * In the **Name** field, enter ```Annual+1```. +#### Create the Annual Plan Plus One Freq Job +22. In the side menu, select **Add Job**. +23. In the **Name** field, enter **Annual Plan Plus One Freq**. +24. Leave the **Job Type** as **Null Job**. +25. Click the **Save** button. +26. Click the **Lock** button to enter **Admin Mode**. +27. Expand the **Frequency** section, if not already expanded. +28. Click the **Add** button. +29. In the **Frequency Manager Wizard**: + * In the **Name** field, enter ```Annual+1WD```. * In the **When to Scheduled** dop-down menu, select **Annual Plan**. * In the **Calendar** drop-down menu, select **My First Calendar**. * in the **Offset Days**, enter ```1```. - * In the **A/O/B/N** section, select **Before Date**. + * In the **A/O/B/N** section, select **On Date**. * Click the **Save** button. -20. In the **Active** column, select the frequency then select **Forcast**. +30. In the **Active** column, select the frequency then select **Forecast**. :::tip -The **Forecast** screen should show the **date you selected in Exercise 7** as green. +The **Forecast** screen should show the **date selected on My First Calendar in Exercise 7 with an offset of +1** as green. ::: 31. Close **Library**. diff --git a/docs/Unit 2 Exercise 11.md b/docs/Unit 2 Exercise 11.md index 9e56049..56845c1 100644 --- a/docs/Unit 2 Exercise 11.md +++ b/docs/Unit 2 Exercise 11.md @@ -2,30 +2,24 @@ sidebar_label: 'Unit 2 Exercise 11' --- -## Exercise 11: Multiple Frequencies +## Exercise 11: Looping Jobs ### Objective -To become familiar with using Negative Frequencies, Multiple Frequencies, and Looping Jobs. +To become utilize the Restart setting to create a Looping Job. ### Summary -Create a new Schedule called **Multiple and Negative Frequencies** that runs Monday-Friday. In this schedule, you will have 3 jobs in this scheduled. One will loop when it **Finishes OK**, one will have **multiple frequencies** and each frequency will have its own **Start Offset**, and the last job will have a **Negative frequency**. +Utilizing the schedule, **My First Schedule**, you will add a looping job that will restart multiple times after each run **Finishes OK**. ### Instructions -1. In **Studio**, select the **Add** -2. In the **Name** field, enter ```Multiple and Negative Frequencies```. -3. In the **Schedule Start Time and Work Days**, select **Monday - Friday**. -4. Click **Save**. -5. Close **Studio**. - #### Create a Looping Job - -6. In **Library** > **Administration**, select **Master Job**. -7. Select **Add**. -8. In the **Schedule** field, select **Multiple and Negative Frequencies**. -9. In the **Name** field, enter ```Looping Job```. +1. In **Studio**, select the **My First Schedule** +2. Click the **View** button. +3. In the side menu, select **Add Job**. +4. Validate that **My First Schedule** is in the Schedule field. +4. In the **Name** textbox, enter ```Looping Job```. 10. In the **Job Type** drop-down, select **Windows**. 11. Expand the **Task Details** section to open the Details box. 12. In the **Machine Selection** section, select the **SMATraining** machine from the **Machines or Machine Group** drop down. @@ -46,76 +40,25 @@ Create a new Schedule called **Multiple and Negative Frequencies** that runs Mon * In the **Value** field, enter ```15```. * In the **Number of Runs** field, enter ```4```. 22. Click **Save**. -23. Click **Back** in the top right corner. - -#### Create the Multiple Frequency Job - -24. In **Library** > **Administration**, select **Master Job**. -25. Select **Add**. -26. In the **Schedule** field, select **Multiple and Negative Frequencies**. -27. In the **Name** field, enter ```Multiple Frequencies```. -28. In the **Job Type** drop-down, select **Null Job**. -29. Click the **Save** button. -30. Click the **Lock** button to enter **Admin Mode**. -31. Expand the **Frequency** section, if not already expanded. -32. Click the **Add** button. -33. In the **Frequency Manager Wizard**: - * In the **Name** field, enter ```15th-B```. - * In the **When to Scheduled** dop-down menu, select **On Day**. - * In the **On** *X* **days of week**, enter ```15```. - * In the **Day Type** field, select **On 15th day**. - * In the **A/O/B/N** section, select **Before Date**. - * Click the **Save** button. -34. Click the **Lock** button to enter **Admin Mode**. -35. In the **Active** column, select the frequency you just created. -36. Scroll down to the **Start Offset** field, enter ```20:00```. -37. Click **Save**. -38. Repeat Steps 32-37, to add a **Frequency** for the **last business day of the month** that will have a **Start Offset** of ```18:00```. -39. Click **Back** in the top right corner. - -#### Create the Negative Frequency Job - -40. Select **Add**. -41. In the **Schedule** field, select **Multiple and Negative Frequencies**. -42. In the **Name** field, enter ```Negative Frequencies```. -43. In the **Job Type** drop-down, select **Null Job**. -44. Click the **Save** button. -45. Click the **Lock** button to enter **Admin Mode**. -46. Expand the **Frequency** section, if not already expanded. -47. Click the **Add** button. -48. In the **Frequency Manager Wizard**: - * In the **Name** field, enter ```EOM-O```. - * In the **When to Scheduled** dop-down menu, select **End of Period**. - * In the **Period** field, select **Month**. - * In the **A/O/B/N** section, select **On Date**. - * Click the **Save** button. -49. Click the **Lock** button to enter **Admin Mode**. -50. In the **Active** column, select the frequency you just created. -51. Scroll down to the **Job Build Status** field, select **Do Not Schedule** from the drop-down. -52. Click **Save**. -53. Repeat Steps 47-48, to add a **Frequency** for Monday - Friday and won't run on holidays. You can use an Inactive frequency if you already have one that meets this criteria. -54. Close **Library**. - -#### Build the Schedule for today and the End of the Month - -55. In **Operations**, select **Schedule Build**. -56. In the **From** field select the **15th** or **the working day before if the 15th is a non-working day or holiday**. -57. In the **To** field select select the **15th** or **the working day before if the 15th is a non-working day or holiday**. -58. Select the **Released** radio button in the **Schedule Build** section. -59. In the **Schedule Selection** section, select **Multiple and Negative Frequencies**. -60. Click the **Build** button. -61. Click the link for the **Multiple and Negative Frequencies** schedule for any date you just built out. +23. Close **Studio**. -:::info -You should see that all three jobs built out and that the **Start Time** of the **Multiple Freqency** job is **8:00 PM**. -::: +#### Add the Job to the Daily -62. Repeat **Steps 37-43** to build the schedule for the last working day of the month. +24. In **Operations**, click on **Processes** in the top right corner. +25. In the **Date** section, select today's date. +26. In the **Schedule** section, right-click on **My First Schedule**. +27. In the **Schedule Selection** window, click the **+** sign. +28. In the **Add Job(s) for...** pop-up window, select the **Looping Job** and click **Next**. +29. On the next screen, click the **Release** radial button then click **Next**. +30. On the next screen, click **Submit**. +31. Click **Close**. +32. In the **Job** section, you should see the job and it should run successfully. :::info -You should see only two job on the last working day of the month, the Looping Job and the Multiple Freq job, and the **Multiple Frequency** jobshould have a **Start Time** of **6:00 PM**. +The Looping Job will probably look like it is stuck in the "Wait Start Time" state but if you look at the **Return Code** column, you should see all zeros (0000000000). ::: +33. Close **Operations**. ## Enterprise Manager diff --git a/docs/Unit 2 Exercise 12.md b/docs/Unit 2 Exercise 12.md new file mode 100644 index 0000000..c8ca6d3 --- /dev/null +++ b/docs/Unit 2 Exercise 12.md @@ -0,0 +1,121 @@ +--- +sidebar_label: 'Unit 2 Exercise 12' +--- + +## Exercise 12: Multiple Frequencies + +### Objective + +To become familiar with using Negative Frequencies and Multiple Frequencies. + +### Summary + +Create a new Schedule called **Multiple and Negative Frequencies** that runs Monday-Friday. In this schedule, you will have 2 jobs. One will have **multiple frequencies** where each frequency has its own **Start Offset**, and the other job will have a **Negative frequency**. + +### Instructions + +1. In **Studio**, select the **Add** +2. In the **Name** field, enter ```Multiple and Negative Frequencies```. +3. In the **Schedule Start Time and Work Days**, select **Monday - Friday**. +4. Click **Save**. +5. Close **Studio**. + +#### Create the Multiple Frequency Job + +6. In **Library** > **Administration**, select **Master Job**. +7. Select **Add**. +8. In the **Schedule** field, select **Multiple and Negative Frequencies**. +9. In the **Name** field, enter ```Multiple Frequencies```. +10. In the **Job Type** drop-down, select **Null Job**. +11. Click the **Save** button. +12. Click the **Lock** button to enter **Admin Mode**. +13. Expand the **Frequency** section, if not already expanded. +14. Click the **Add** button. +15. In the **Frequency Manager Wizard**: + * In the **Name** field, enter ```15th-B```. + * In the **When to Scheduled** dop-down menu, select **On Day**. + * In the **On** *X* **days of week**, enter ```15```. + * In the **Day Type** field, select **On 15th day**. + * In the **A/O/B/N** section, select **Before Date**. + * Click the **Save** button. +16. Click the **Lock** button to enter **Admin Mode**. +17. In the **Active** column, select the frequency you just created. +18. Scroll down to the **Start Offset** field, enter ```20:00```. +19. Click **Save**. +20. Repeat Steps 32-37, to add a **Frequency** for the **last business day of the month** that will have a **Start Offset** of ```18:00```. +21. Click **Back** in the top right corner. + +#### Create the Negative Frequency Job + +22. Select **Add**. +23. In the **Schedule** field, select **Multiple and Negative Frequencies**. +24. In the **Name** field, enter ```Negative Frequencies```. +25. In the **Job Type** drop-down, select **Null Job**. +26. Click the **Save** button. +27. Click the **Lock** button to enter **Admin Mode**. +28. Expand the **Frequency** section, if not already expanded. +29. In the **Inactive** column, select the **EOM-B** frequency. +30. Using the **<** button, move it into the **Active** column. +31. In the **Active** column, select the frequency you just created. +32. Scroll down to the **Job Build Status** field, select **Do Not Schedule** from the drop-down. +33. Click **Save**. +34. Click the **Lock** button to enter **Admin Mode**. +35. In the Frequency Manager Wizard: + * In the **Name** field, enter ```Mon-Fri-N```. + * In the **When to Scheduled** dop-down menu, select **All Weeks**. + * In the **Days of the Week**, select **Monday-Friday**. + * In the **A/O/B/N** section, select **Not Schedule**. + * Click the **Save** button. +36. Close **Library**. + +#### Build the Schedule for today and the End of the Month + +37. In **Operations**, select **Schedule Build**. +38. In the **From** field select the **15th** or **the working day before if the 15th is a non-working day or holiday**. +39. In the **To** field select select the same date as you did for **From**. +40. Select the **Released** radio button in the **Schedule Build** section. +41. In the **Schedule Selection** section, select **Multiple and Negative Frequencies**. +42. Click the **Build** button. +43. Click the link for the **Multiple and Negative Frequencies** schedule for any date you just built out. + +:::info +You should see that both jobs get built and that the **Start Time** of the **Multiple Frequency** job is **8:00 PM**. +::: + +44. Repeat **Steps 37-43** to build the schedule for the last working day of the month. + +:::info +You should see only one job on the last working day of the month, the Multiple Freq job, and it should have a **Start Time** of **6:00 PM**. +::: + +## Enterprise Manager + +
+ + + +:::tip [Walkthrough Video - Unit 2 Exercise 11](../static/videobasic/U2E11.mp4) + +::: + +1. **Multiple Frequencies** + * Create a new Schedule. + * Add a Null Job and setup Frequencies allowing a Job to run on the 15th of the month (working day before) and the last business day of the month. + * Schedule - 5 Day Work Week + * The Job runs at ```20:00``` when it is not the last day of the month and ```18:00``` when it is the last business day of the month. + * Use the Forecast All Button to view both Frequencies. + * The first listed will be Green and the second will be Yellow. +2. **Negative Frequencies** + * In a new Null Job (same Schedule), set up Frequencies allowing the Job to run every day of the month, Monday through Friday, unless it is a Holiday or the last Day of the Month. + * Use the Forecast All Button to view both Frequencies. + + :::note + The Negative Frequency will appear purple + ::: + +
\ No newline at end of file diff --git a/docs/Unit 2 Exercise 3.md b/docs/Unit 2 Exercise 3.md index 1dac229..b7ed6ba 100644 --- a/docs/Unit 2 Exercise 3.md +++ b/docs/Unit 2 Exercise 3.md @@ -34,7 +34,7 @@ The **JORS Port Number** for this agent will be ```3110```. This agent will be u #### Define the Communication Settings 10. Expand the **Communication Settings** section. -11. In the **JORS Port Number** field, eneter ```3110```. +11. In the **JORS Port Number** field, enter ```3110```. #### Define the File Transfer Settings @@ -43,7 +43,8 @@ The **JORS Port Number** for this agent will be ```3110```. This agent will be u 14. In the **File Transfer Port Number (Non-TLS)** field, enter ```3110```. 15. In the **Support non-TLS for SMAFT Agent Communications** field, select ```True``` from the drop down menu. 16. In the **Support non-TLS for SMAFT Server Communications** field, select ```True``` from the drop down menu. -17. Continue on to **Exercise 4**. +17. Click **Save**. +18. Continue on to **Exercise 4**. ## Enterprise Manager diff --git a/docs/Unit 2 Exercise 4 And 5.md b/docs/Unit 2 Exercise 4 And 5.md index 920bd22..4e12637 100644 --- a/docs/Unit 2 Exercise 4 And 5.md +++ b/docs/Unit 2 Exercise 4 And 5.md @@ -29,7 +29,7 @@ Start Communication for the ```SUSEVM``` Machine. 5. Continue on to **Exercise 5**. :::info Note -Do not panic! This is an expected behaviour based on the port number we ented when defining the **Socket Number** in Exercise 3. Please continue on to Exercise 5 to correct this issue. +Do not panic! This is an expected behavior based on the port number we entered when defining the **Socket Number** in Exercise 3. Please continue on to Exercise 5 to correct this issue. ::: ### Exercise 5 diff --git a/docs/Unit 2 Exercise 6.md b/docs/Unit 2 Exercise 6.md index fb9c490..89dfbee 100644 --- a/docs/Unit 2 Exercise 6.md +++ b/docs/Unit 2 Exercise 6.md @@ -74,7 +74,7 @@ Create a ```UNIX``` job in **MY FIRST SCHEDULE** called **UNIX Job 1**. This job 1. Under the **Administration** topic, Double-Click on **Job Master**. 2. In the **Schedule** drop-down list, select **My First Schedule**. -3. Click the **Add** button on the **Job Maste**r toolbar. +3. Click the **Add** button on the **Job Master** toolbar. 4. In the **Name** textbox, enter ```UNIX Job 1```. 5. In the **Job Type** drop-down list, select **UNIX**. 6. In the **Primary Machine** drop-down list, select the **SUSEVM** machine for the Job to run on. diff --git a/docs/Unit 2 Exercise 7.md b/docs/Unit 2 Exercise 7.md index 7c484c0..ef16461 100644 --- a/docs/Unit 2 Exercise 7.md +++ b/docs/Unit 2 Exercise 7.md @@ -6,23 +6,23 @@ sidebar_label: 'Unit 2 Exercise 7' ### Objective -To update the Master Holiday Calendar and create a seperate calendar with customized dates. +To update the Master Holiday Calendar and create a separate calendar with customized dates. ### Summary Update the **Master Holiday Calendar** so the following dates are marked as holidays: - * January 1st - New Years Day - * January 16th – Martin Luther King Jr. Day - * February 20th – President’s Day - * May 29th – Memorial Day - * June 19th - Juneteenth National Independence Day (Observed) - * July 4th – Independence Day - * September 4th – Labor Day - * October 9th – Columbus Day - * November 11th – Veterans Day - * November 23rd – Thanksgiving Day - * December 25th - Christmas Day (Observed) + * Monday, January 1st - New Years Day + * Monday, January 15th – Martin Luther King Jr. Day + * Monday, February 19th – President’s Day + * Monday, May 27th – Memorial Day + * Wednesday, June 19th - Juneteenth National Independence Day (Observed) + * Thursday, July 4th – Independence Day + * Monday, September 2nd – Labor Day + * Monday, October 14th – Columbus Day + * Monday, November 11th – Veterans Day + * Thursday, November 28rd – Thanksgiving Day + * Wednesday, December 25th - Christmas Day (Observed) You will also create a new calendar called **My First Calendar** and select several dates of your choosing. @@ -32,7 +32,7 @@ You will also create a new calendar called **My First Calendar** and select seve #### Update the Master Holiday Calendar -2. Select **Master Holiday** from the list of Caledars. +2. Select **Master Holiday** from the list of Calendars. 3. Click **Edit**. 4. In the **Calendar Settings**, select the dates listed in the **Summary** section above. 5. Click **Save**. @@ -52,12 +52,9 @@ You will also create a new calendar called **My First Calendar** and select seve
- :::tip [Walkthrough Video - Unit 2 Exercise 7](../static/videobasic/U2E7.mp4) - ::: - 1. Click on **Calendars** from the **Navigation Panel**. 2. Click the **Add** Button. 3. Type **MyFirstCalendar** in the **Name** field. @@ -72,15 +69,16 @@ The dates are saved dynamically 9. Select **Master Holiday** from the **Calendar List**. 10. Click the following dates in the Calendar to set up the current year Federal Holidays, then close the **Calendars** tab: - * January 16th – Martin Luther King Jr. Day - * February 20th – President’s Day - * May 29th – Memorial Day - * June 19th - Juneteenth National Independence Day (Observed) - * July 4th – Independence Day - * September 4th – Labor Day - * October 9th – Columbus Day - * November 11th – Veterans Day - * November 23rd – Thanksgiving Day - * December 25th - Christmas Day (Observed) + * Monday, January 1st - New Years Day + * Monday, January 15th – Martin Luther King Jr. Day + * Monday, February 19th – President’s Day + * Monday, May 27th – Memorial Day + * Wednesday, June 19th - Juneteenth National Independence Day (Observed) + * Thursday, July 4th – Independence Day + * Monday, September 2nd – Labor Day + * Monday, October 14th – Columbus Day + * Monday, November 11th – Veterans Day + * Thursday, November 28rd – Thanksgiving Day + * Wednesday, December 25th - Christmas Day (Observed)
\ No newline at end of file diff --git a/docs/Unit 2 Exercise 8.md b/docs/Unit 2 Exercise 8.md index 54e2121..33d82ed 100644 --- a/docs/Unit 2 Exercise 8.md +++ b/docs/Unit 2 Exercise 8.md @@ -42,15 +42,16 @@ In the **On Day Freq** job, create a new frequency named that will run on the 1s * In the **A/O/B/N** section, select **Before Date**. * Make sure the **Day Type** is set to **Working**. * Click the **Save** button. -10. In the **Active** column, select the frequency then select **Forcast**. +10. In the **Active** column, select the frequency then select **Forecast**. :::tip The **Forecast** screen should show **all Tuesday and Thursday** dates in green unless they are a holiday. If there is a Tuesday or Thursday holiday the previous day should be green. ::: +11. Click the **Back** button to navigate back to the **Studio** workspace. + #### Create the On Occurrence Freq Job -11. Click the **Back** button to navigate back to the **Studio** workspace. 12. In the side menu, select **Add Job**. 13. In the **Name** field, enter **On Occurrence Freq**. 14. Leave the **Job Type** as **Null Job**. @@ -60,22 +61,23 @@ The **Forecast** screen should show **all Tuesday and Thursday** dates in green 18. Click the **Add** button. 19. In the **Frequency Manager Wizard**: * In the **Name** field, enter ```4th-Thurs-B```. - * In the **When to Scheduled** dop-down menu, select **On Ocurrence**. + * In the **When to Scheduled** dop-down menu, select **On Occurrence**. * In the **On Occurrence** drop-down menu, select **Fourth**. * In the **Period** drop-down, select **Month**. * In the **Days of the Week** section, select **Thursday**. * In the **A/O/B/N** section, select **Before Date**. * Make sure the **Day Type** is set to **Working**. * Click the **Save** button. -20. In the **Active** column, select the frequency then select **Forcast**. +20. In the **Active** column, select the frequency then select **Forecast**. :::tip -The **Forecast** screen should show the **4th Thursday of every month** should be green except for Thanksgiving. The day before Thanksgiving should be green because the 4th Thursday of Novemeber is a holiday. +The **Forecast** screen should show the **4th Thursday of every month** should be green except for Thanksgiving. The day before Thanksgiving should be green because the 4th Thursday of November is a holiday. ::: +21. Click the **Back** button to navigate back to the **Studio** workspace. + #### Create the On Day Freq Job -21. Click the **Back** button to navigate back to the **Studio** workspace. 22. In the side menu, select **Add Job**. 23. In the **Name** field, enter **On Day Freq**. 24. Leave the **Job Type** as **Null Job**. @@ -90,7 +92,7 @@ The **Forecast** screen should show the **4th Thursday of every month** should b * In the **Day Type** field, select **On 1st working day**. * In the **A/O/B/N** section, select **On Date**. * Click the **Save** button. -30. In the **Active** column, select the frequency then select **Forcast**. +30. In the **Active** column, select the frequency then select **Forecast**. :::tip The **Forecast** screen should show the **1st working day of every month** should be green _except for New Year’s Day_. Notice how holidays and weekends affect this Frequency. diff --git a/docs/Unit 2 Exercise 9.md b/docs/Unit 2 Exercise 9.md index 0e3610c..3fc70e6 100644 --- a/docs/Unit 2 Exercise 9.md +++ b/docs/Unit 2 Exercise 9.md @@ -19,19 +19,17 @@ Utilizing the **Frequency Practice Schedule**, you will create four new Null job In the **On Request Freq** job, create a new frequency that will be used to add jobs dynamically to a schedule. -In the **Begining of Period Freq** job, create a new frequency that will run on the 1st Working Day (WD) of the month or the day after in case of a holiday. +In the **Beginning of Period Freq** job, create a new frequency that will run on the 1st Working Day (WD) of the month or the day after in case of a holiday. In the **Middle of Period Freq** job, create a new frequency named that will run on the Wednesday closest to the middle of the month or the day after in case of a holiday. In the **End of Period Freq** job, create a new frequency named that will run on the last Working Day (WD) of the month or the day before in case of a holiday. ### Instructions - 1. In **Studio**, select the **Frequency Practice** Schedule and click **View**. 2. In the side menu, select **Add Job**. #### Create the On Request Freq Job - 3. In the **Name** field, enter **On Request Freq**. 4. Leave the **Job Type** as **Null Job**. 5. Click the **Save** button. @@ -40,17 +38,18 @@ In the **End of Period Freq** job, create a new frequency named that will run on 8. Click the **Add** button. 9. In the **Frequency Manager Wizard**: * In the **Name** field, enter ```OnRequest```. - * In the **Requst Date** field, select a date on the calendar that is in the past. + * In the **When to Scheduled** dop-down menu, select **On Request**. + * In the **Request Date** field, select a date on the calendar that is in the past. * Click the **Save** button. -10. In the **Active** column, select the frequency then select **Forcast**. +10. In the **Active** column, select the frequency then select **Forecast**. :::tip The **Forecast** screen should show only the date that you chose in green. ::: -#### Create the Beginning of Period Freq Job - 11. Click the **Back** button to navigate back to the **Studio** workspace. + +#### Create the Beginning of Period Freq Job 12. In the side menu, select **Add Job**. 13. In the **Name** field, enter **Beginning of Period Freq**. 14. Leave the **Job Type** as **Null Job**. @@ -65,15 +64,15 @@ The **Forecast** screen should show only the date that you chose in green. * In the **A/O/B/N** section, select **After Date**. * Make sure the **Day Type** is set to **Working**. * Click the **Save** button. -20. In the **Active** column, select the frequency then select **Forcast**. +20. In the **Active** column, select the frequency then select **Forecast**. :::tip The **Forecast** screen should show the **first working day of every month** as green. Notice how holidays and weekends affect this Frequency. ::: -#### Create the Middle of Period Freq Job - 21. Click the **Back** button to navigate back to the **Studio** workspace. + +#### Create the Middle of Period Freq Job 22. In the side menu, select **Add Job**. 23. In the **Name** field, enter **Middle of Period Freq**. 24. Leave the **Job Type** as **Null Job**. @@ -89,15 +88,15 @@ The **Forecast** screen should show the **first working day of every month** as * In the **A/O/B/N** section, select **After Date**. * Make sure the **Day Type** is set to **Working**. * Click the **Save** button. -30. In the **Active** column, select the frequency then select **Forcast**. +30. In the **Active** column, select the frequency then select **Forecast**. :::tip The **Forecast** screen should show the **Wednesday closest to the middle of every month** as green. Notice how holidays and weekends affect this Frequency. ::: -#### Create the End of Period Freq Job - 31. Click the **Back** button to navigate back to the **Studio** workspace. + +#### Create the End of Period Freq Job 32. In the side menu, select **Add Job**. 33. In the **Name** field, enter **End of Period Freq**. 34. Leave the **Job Type** as **Null Job**. @@ -112,11 +111,10 @@ The **Forecast** screen should show the **Wednesday closest to the middle of eve * In the **A/O/B/N** section, select **Before Date**. * Make sure the **Day Type** is set to **Working**. * Click the **Save** button. -40. In the **Active** column, select the frequency then select **Forcast**. +40. In the **Active** column, select the frequency then select **Forecast**. :::tip The **Forecast** screen should show the **last working day of every month** as green. Notice how holidays and weekends affect this Frequency. - ::: 41. Close **Library**. diff --git a/docs/Unit 2 Lab A.md b/docs/Unit 2 Lab A.md index 40d2742..1e13c11 100644 --- a/docs/Unit 2 Lab A.md +++ b/docs/Unit 2 Lab A.md @@ -14,24 +14,24 @@ Congo Online Retail Inc’s Payroll Department work week is Monday through Frida #### Toys Department -* Every 14 Days starting on January 7th of this year - * The Working Day before, if date falls on a Non-Working Day +* Every 14 Days starting on January 7th of this year + * The Working Day before, if date falls on a Non-Working Day #### Electronics Department * 15th of the Month - * The Working Day before, if date falls on a Non-Working Day -* Last Working Day of the month - * The Working Day before, if date falls on a Non-Working Day -* End of Year (Negative) - * Payroll that includes both the monthly Payroll and Bonuses is run in place of the End of Month Payroll on the last working day of the year + * The Working Day before, if date falls on a Non-Working Day +* Last Working Day of the month + * The Working Day before, if date falls on a Non-Working Day +* End of Year (Negative) + * Payroll that includes both the monthly Payroll and Bonuses is run in place of the End of Month Payroll on the last working day of the year #### Clothing Department -* Every Friday - * The Working Day after, if date falls on a Non-Working Day +* Every Friday + * The Working Day after, if date falls on a Non-Working Day * OnRequest - * After every major sales milestone is reached + * After every major sales milestone is reached ### Lab Instructions @@ -39,37 +39,37 @@ Congo Online Retail Inc’s Payroll Department work week is Monday through Frida Use the **NULL JOB Job Type** for all jobs in this lab. ::: -* Create a S**chedule** called **Congo Payroll Payments** -* Add **Documentation** for the Schedule +* Create a **Schedule** called **Congo Payroll Payments** +* Add **Documentation** for the Schedule * Saturday and Sundays are non-working days -* The **Master Holiday Calendar** is used -* **Auto-build** the Schedule 7 days in advance for 1 day -* **Auto-delete** the Schedule for 7 days ago +* The **Master Holiday Calendar** is used +* **Auto-build** the Schedule 7 days in advance for 1 day +* **Auto-delete** the Schedule for 7 days ago :::tip -* You can reference [Unit 1 - Exercise 1](/docs/Unit%201%20Exercise%201.md) for steps on how to create a Schedule. +You can reference [**Unit 1 - Exercise 1**](/docs/Unit%201%20Exercise%201.md) for steps on how to create a Schedule. ::: -* Four **Null Jobs** will be created: - * **Toys** will need **one Job** with **one Frequency** - * **Electronics** will need **two Jobs** - * Job 1 - **three Frequencies** - * Job 2 - **one Frequency** - * **Clothing** will need **one Job** with **two Frequencies** +* Four **Null Jobs** will be created: + * **Toys** will need **one Job** with **one Frequency** + * **Electronics** will need **two Jobs** + * Job 1 - **three Frequencies** + * Job 2 - **one Frequency** + * **Clothing** will need **one Job** with **two Frequencies** :::tip -* You can reference [Unit 2 - Exercise 2](/docs/Unit%202%20Exercise%202.md) for steps on how to create Null jobs. +You can reference [**Unit 2 - Exercise 2**](/docs/Unit%202%20Exercise%202.md) for steps on how to create Null jobs. ::: -* Tag all Jobs according to the product (**Toys**, **Electronics** and **Clothing**) +* Tag all Jobs according to the product (**Toys**, **Electronics** and **Clothing**) :::tip -* You can reference [Unit 1 - Exercise 5](/docs/Unit%201%20Exercise%205.md) for steps on how to add Tags. +You can reference [**Unit 1 - Exercise 5**](/docs/Unit%201%20Exercise%205.md) for steps on how to add Tags. ::: * Upon completion, the “**Forecast All**” results will look like the following: -#### Forcasts of Frequencies +#### Forecasts of Frequencies #### Toys ![](../static/imgbasic/SM_Forecast-Interval_Lab.png) diff --git a/docs/Unit 2 Lab B.md b/docs/Unit 2 Lab B.md index 8f94fdd..1398de1 100644 --- a/docs/Unit 2 Lab B.md +++ b/docs/Unit 2 Lab B.md @@ -8,9 +8,9 @@ To use the concepts presented in Units 1 and 2 to create a schedule that will jo ### Objective -Congo Online Retail Inc. needs to run daily inventory checks every day of the week using a schedule called **Conge Inventory Management**. +Congo Online Retail Inc. needs to run daily inventory checks every day of the week using a schedule called **Congo Inventory Management**. -To manange the inventory for each product, a special program must be run for each department: +To manage the inventory for each product, a special program must be run for each department: * **Toys** – ```"C:\scripts\CheckInvToys.EXE"``` * **Electronics** – ```"C:\scripts\CheckInvElectronics.EXE"``` @@ -38,7 +38,7 @@ The programs read the database and generate order requests to purchase new items * Auto-delete the schedule for ```7``` days ago :::tip -* You can reference [Unit 1 - Exercise 1](/docs/Unit%201%20Exercise%201.md) for steps on how to create a Schedule. +You can reference [**Unit 1 - Exercise 1**](/docs/Unit%201%20Exercise%201.md) for steps on how to create a Schedule. ::: * Create a **Windows Job** for each of the products in the introduction. @@ -54,9 +54,11 @@ The programs read the database and generate order requests to purchase new items * Tag these 6 Jobs according to the product type (**Toys**, **Electronics**, or **Clothing**) :::tip -* You can reference [Unit 1 - Exercise 3](/docs/Unit%201%20Exercise%203.md) for steps on how to create a Windows Job. -* You can reference [Unit 2 - Exercise 11](/docs/Unit%202%20Exercise%2011.md) for stepts on how to create a Looping Job. -* You can reference [Unit 1 - Exercise 5](/docs/Unit%201%20Exercise%205.md) for steps on how to add Tags. +You can reference [**Unit 1 - Exercise 3**](/docs/Unit%201%20Exercise%203.md) for steps on how to create a Windows Job. + +You can reference [**Unit 2 - Exercise 11**](/docs/Unit%202%20Exercise%2011.md) for steps on how to create a Looping Job. + +You can reference [**Unit 1 - Exercise 5**](/docs/Unit%201%20Exercise%205.md) for steps on how to add Tags ::: * Create a Unix Job named **Inventory Purchase Report** @@ -68,14 +70,15 @@ The programs read the database and generate order requests to purchase new items * The Inventory Purchase Report requires the 6 Windows Jobs and must run after all runs have completed :::tip -* You can reference [Unit 2 - Exercise 6](/docs/Unit%202%20Exercise%206.md) for steps on how to create a UNIX Job. -* You can reference [Unit 1 - Exercise 4](/docs/Unit%201%20Exercise%204.md) for steps on how to add dependencies. +You can reference [**Unit 2 - Exercise 6**](/docs/Unit%202%20Exercise%206.md) for steps on how to create a UNIX Job. + +You can reference [**Unit 1 - Exercise 4**](/docs/Unit%201%20Exercise%204.md) for steps on how to add Dependencies. ::: * Build the Schedule for today and tomorrow :::tip -* You can reference [Unit 1 - Exercise 6](/docs/Unit%201%20Exercise%206.md) for steps on how to build the Schedule. +You can reference [**Unit 1 - Exercise 6**](/docs/Unit%201%20Exercise%206.md) for steps on how to build the Schedule. ::: :::info diff --git a/docs/Unit 3 Exercise 1.md b/docs/Unit 3 Exercise 1.md index 39ed188..3d43b92 100644 --- a/docs/Unit 3 Exercise 1.md +++ b/docs/Unit 3 Exercise 1.md @@ -10,15 +10,7 @@ To create your first Role and assign your first User Account to it. ### Summary -Utilizing **Enterprise Manager**, you will create a new **Role** and **User Account**. Then utilizing **Solution Manager***, you will assign this new user to the new role. - - called ```Student1```. Then you will assign ```Student 1``` the **Role** of ```Training```. - -By logging out of Enterprise Manager and logging back in as Student1 you will validate that the user has limited access with the UI. The access can be validated by attempting to view the **Machines** that are defined. - - - (Full User Name: ```Student Number 1```). - +Utilizing **Enterprise Manager**, you will create a new **Role** and **User Account**. Then utilizing **Solution Manager***, you will assign this new user to the new role. By logging out of Enterprise Manager and logging back in as Student1 you will validate that the user has limited access with the UI. The access can be validated by attempting to view the **Machines** that are defined. ### Instructions diff --git a/docs/Unit 3 Exercise 10.md b/docs/Unit 3 Exercise 10.md index 362dc5c..764dbd0 100644 --- a/docs/Unit 3 Exercise 10.md +++ b/docs/Unit 3 Exercise 10.md @@ -14,7 +14,7 @@ Create a customized **System Property** using the **$DATE** Property, that has a ### Instructions -1. In **Library** > **Administration**, click on **Global Properties**. +1. In **Library** > **Administration**, select **Global Properties**. 2. In the **Global Properties** list select **$DATE**. 3. Click the **Copy** button. 4. In the **Global Property** pop-up window, diff --git a/docs/Unit 3 Exercise 11.md b/docs/Unit 3 Exercise 11.md index 461fb66..35f6625 100644 --- a/docs/Unit 3 Exercise 11.md +++ b/docs/Unit 3 Exercise 11.md @@ -10,13 +10,13 @@ To use different types of **Instance Properties** in place of hard coded values ### Summary -Modify **Windows Job 4** and **Windows Job 5** to use **Schedule and Job Instance Properties** for the ```Path``` and ```-t``` parameter. Within **MY FIRST SCHEDULE**, you will create a **Schedule Instance Property** called ```Path``` with a value of ```C:\Program Files\OpConxps\MSLSAM```. Within **Windows Job 4** and **Windows Job 5**, you will create a **Job Instance Property** called ```TIME``` with a numerical value of your choosing. +Modify **Windows Job 4** to use **Schedule and Job Instance Properties** for the ```Path``` and ```-t``` parameter. Within **MY FIRST SCHEDULE**, you will create a **Schedule Instance Property** called ```Path``` with a value of ```C:\Program Files\OpConxps\MSLSAM```. Within **Windows Job 4**, you will create a **Job Instance Property** called ```TIME``` with a numerical value of your choosing. ### Instructions #### Create the Schedule Instance Property -1. In **Library** > **Administration**, click on **Master Schedules**. +1. In **Library** > **Administration**, select **Master Schedules**. 2. In the **Schedule** list, select **My First Schedule**. 3. Click the **Edit** button. 4. Click the **Lock** icon in the upper right-hand corner. @@ -32,36 +32,29 @@ Modify **Windows Job 4** and **Windows Job 5** to use **Schedule and Job Instanc 9. Under **Library** > **Administration**, select **Master Jobs**. 10. In the **Master Jobs** list, select **Windows Job 4**. -11. While holding down the **CNTL key**, click the **Edit** button and the job should open in a new tab. +11. While holding down the **CTRL key**, click the **Edit** button and the job should open in a new tab. 12. In the new tab, click the **Lock** button in the upper right-hand corner. 13. Expand **Instance Properties**. - * Click **+ Add New Property Set**. + * Click **+ Add New Property Set** button. * Click the **green + button**. * In the **Name** field, enter ```TIME```. * In the **Value** field, enter a number of your choice between 10 and 60. * Click the **Check Mark** button to verify the the entry. * click **Save**. -14. Close the tab. -15. Repeat Steps 10-14 to add a **Instance Property** to **Windows Job 5**. - -#### Modify the Jobs to use the Instance Properties - -16. Under **Library** > **Administration**, select **Master Jobs**. -17. In the **Master Jobs** list, select **Windows Job 4**. -18. Click the **Lock** button in the upper right-hand corner. -19. Click the **Edit** button. -20. Expand the **Task Details** box. -21. Locate the **Command Line** and highlight ```C:\Program Files\OpConxps\MSLSAM```. -22. Using either, the **Magic Wand** or **CTRL+SPACE**, pull up the **Property Selector** window. -23. In the **Property Selectory** pop-up window: - * In the **Scope** field, uncheck **Global** and **Machine**. +14. Refresh the web page. + +#### Modify the Job to use the Instance Properties + +15. While still on the **Master Job Definition** screen for **Windows Job 4, click the **Lock** button in the upper right-hand corner. +16. Expand the **Task Details** box. +17. Locate the **Command Line** and highlight ```C:\Program Files\OpConxps\MSLSAM```. +18. Using either, the **Magic Wand** or **CTRL+SPACE**, pull up the **Property Selector** window. +19. In the **Property Selector** pop-up window: + * In the **Scope** field, uncheck **Global**, **Job**, and **Machine**. * In the **Search** field, enter ```Path```. * Select the Property named, **SI.Path**. * Click **OK** -24. Using the search filter, locate and select the property called ```Path```. -25. Click **OK**. -26. Repeat **Steps 21-25** to replace the ```10``` with the Job Instance Property called **JI.TIME**. -27. Repeat **Steps 17-26** for **Windows Job 5**. +20. Repeat **Steps 21-25** to replace the ```10``` with the Job Instance Property called **JI.TIME**. :::tip The new command line should look similar to the following: @@ -70,23 +63,22 @@ The new command line should look similar to the following: ``` ::: -28. Click the **Save** button. -29. Close **Library**. +21. Click **Save**. +22. Close **Library**. #### Build the Schedule :::tip -Validate that all the jobs in **My First Schedule** are in a completed state and that the **Schedule Status** shows as **Completed**. As you may need to overwrite the exsiting schedule during the build process. +Validate that all the jobs in **My First Schedule** are in a completed state and that the **Schedule Status** shows as **Completed**. As you may need to overwrite the existing schedule during the build process. ::: -30. In **Operations**, click on **Schedule Build**. -31. In the **From** field, select today's date. -32. In the **To** field, select today's date. -33. Select the **Released** radio button. -34. In the **Schedule List**, select **My First Schedule**. -35. Click the **Build** button. -36. Expand and click on the schedule link for **My First Schedule** to return to the **Processes** screen. - +23. In **Operations**, click on **Schedule Build**. +24. In the **From** field, select today's date. +25. In the **To** field, select today's date. +26. Select the **Released** radio button. +27. In the **Schedule List**, select **My First Schedule**. +28. Click the **Build** button. +29. Expand and click on the schedule link for **My First Schedule** to return to the **Processes** screen. ## Enterprise Manager diff --git a/docs/Unit 3 Exercise 13.md b/docs/Unit 3 Exercise 13.md index 8708fad..1d0f226 100644 --- a/docs/Unit 3 Exercise 13.md +++ b/docs/Unit 3 Exercise 13.md @@ -6,7 +6,7 @@ sidebar_label: 'Unit 3 Exercise 13' ### Objective -To use Events to cancel a job in a workflow when a preceeding job finishes okay. +To use Events to cancel a job in a workflow when a preceding job finishes okay. ### Summary @@ -31,7 +31,7 @@ These jobs should run in a particular order so that the event will cancel the th 9. Click the **Save** button. 10. Click the **Lock** button in the upper right-hand corner. 11. Expand the **Frequency** box. -12. **Add** a frequncy for a **Mon-Sun-O** pattern. +12. **Add** a frequency for a **Mon-Sun-O** pattern. * In the **Frequency Name** box, type **Mon-Sun-O**. * Set **When to Schedule** as **All Weeks**. * Select all days of the week by marking their check boxes. @@ -50,9 +50,9 @@ These jobs should run in a particular order so that the event will cancel the th 20. In the **Create new Event** screen: * In the **Send Event On** dropdown, select **Job Status**. * In the **Job Status** dropdown, select **Finished OK**. - * In the **Event Templete** dropdown, select the **$JOB:CANCEL** event. - * In the **Schedule Date** field, use the **Magic Wand** or **CNTL+SPACE** to enter in **$SCHEDULE DATE**. - * In the **Schedule Name** field, use the **Magic Wand** or **CNTL+SPACE** to enter in **$SCHEDULE NAME**. + * In the **Event Template** dropdown, select the **$JOB:CANCEL** event. + * In the **Schedule Date** field, use the **Magic Wand** or **CTRL+SPACE** to enter in **$SCHEDULE DATE**. + * In the **Schedule Name** field, use the **Magic Wand** or **CTRL+SPACE** to enter in **$SCHEDULE NAME**. * In the **Job Name** field, enter in the job name for **Test Event 3**. * Click **Save**. 21. Click **Save**. @@ -61,7 +61,7 @@ These jobs should run in a particular order so that the event will cancel the th :::info For all events, you can use **System Properties** for fields like the **Schedule Date** and **Schedule Name**. -* For example: To use a ```$JOB:CANCEL,,,``` event, you can substatute the following for the appropriate fields: +* For example: To use a ```$JOB:CANCEL,,,``` event, you can substitute the following for the appropriate fields: * `````` can be replaced with either ```CURRENT```, ```[[$DATE]]```, or ```[[$SCHEDULE DATE]]``` * `````` needs to be replaced with either the **full name of the Schedule the Job is in** or ```[[$SCHEDULE NAME]]``` * `````` needs to be replaced with **the name of the Job this Event is going to cancel** @@ -77,7 +77,7 @@ For all events, you can use **System Properties** for fields like the **Schedule 28. In the **Job Dependency** pop-up, select **Test Event 2** in the **Job** drop down list. 29. Verify that the **Dependency Type** is **Requires** and the **Condition** is **Finished OK**. 30. Click the **Save** button. -31. Repeat **Steps 26-30** to add a dependnecy between **Test Event 1** and **Test Event 2**. +31. Repeat **Steps 26-30** to add a dependency between **Test Event 1** and **Test Event 2**. 32. Close **Studio**. #### Rebuild the Schedule diff --git a/docs/Unit 3 Exercise 14.md b/docs/Unit 3 Exercise 14.md index e35216d..dca4e9e 100644 --- a/docs/Unit 3 Exercise 14.md +++ b/docs/Unit 3 Exercise 14.md @@ -38,9 +38,9 @@ You will also add a new Event triggered on **Exit Description** of 100 and will * In the **Send Event On** drop down, select **Exit Description**. * In the **Comparison Operator** dropdown, select **Equal To**. * In the **Value** field, enter ```100```. - * In the **Event Templete** drop down, select the **$JOB:SKIP** event. - * In the **Schedule date** field, use the **Magic Wand** or **CNTL+SPACE** to select **$SCHEDULE DATE** property. - * In the **Schedule name** field, use the **Magic Wand** or **CNTL+SPACE** to select **$SCHEDULE NAME** property. + * In the **Event Template** drop down, select the **$JOB:SKIP** event. + * In the **Schedule date** field, use the **Magic Wand** or **CTRL+SPACE** to select **$SCHEDULE DATE** property. + * In the **Schedule name** field, use the **Magic Wand** or **CTRL+SPACE** to select **$SCHEDULE NAME** property. * In the **Job name** field, enter ```Job 2```. * Click the **Save** button. 13. Click the **Save** button in the **Master Job Definition**. diff --git a/docs/Unit 3 Exercise 8.md b/docs/Unit 3 Exercise 8.md index 9868579..f2e1108 100644 --- a/docs/Unit 3 Exercise 8.md +++ b/docs/Unit 3 Exercise 8.md @@ -10,18 +10,18 @@ To set up notifications via Notification Manager. ### Summary -Using **Notification Manager** you will create an email notification to alert **smauser@congo.local** when a machine is marked up. You will use the Thunderbird Mail Client to manage the notificaitons. +Using **Notification Manager** you will create an email notification to alert **smauser@congo.local** when a machine is marked up. You will use the Thunderbird Mail Client to manage the notifications. ### Instructions -1. In **Library**, under the **Management** topic, click on **Notification Triggers**. +1. In **Library** > **Management**, select **Notification Triggers**. 2. Click **Manage Groups** in the upper right corner. #### Create a Notification Group 3. On the **Manage Groups** screen, click **Add**. 4. In the **Name** field, type ```All Machines```. -5. In the **Type** drop-down, seleect **Machine**. +5. In the **Type** drop-down, select **Machine**. 6. Under the **Name** field, select **Included** so that future machines are included in this trigger. 7. Validate that the **Selected** check boxes for both machines is checked. 8. Click **Save**. @@ -30,7 +30,7 @@ Using **Notification Manager** you will create an email notification to alert ** Notice that the new group has been added to the top section of the Manage Groups screen. ::: -#### Create the Nofitication Trigger +#### Create the Notification Trigger 9. Click on **Notification Triggers** in the upper right corner. 10. On the **Notification Trigger** screen, click **Add**. @@ -47,7 +47,7 @@ Notice that the new group has been added to the top section of the Manage Groups #### Test the Notification 17. Select the **All Machines** trigger from the **Main List** in the top half of the screen. -18. Click **Test All** to test your notifcation. +18. Click **Test All** to test your notification. 19. Open the Thunderbird email client and check the inbox. 20. Close **Library**. diff --git a/docs/Unit 3 Exercise 9.md b/docs/Unit 3 Exercise 9.md index 393ea39..75e8bb6 100644 --- a/docs/Unit 3 Exercise 9.md +++ b/docs/Unit 3 Exercise 9.md @@ -23,7 +23,7 @@ Once that the **Escalation Rule** is defined, you will assign that rule to a **N 2. In the **Groups** section on the right side, click **Add**. 3. In the **Add New Escalation Group** pop-up window: * In the **Name** field, enter ```Level 1```. - * In the **Users** section, select ```Student1``` and ```SMATRAINING\SMAUSER``` in the **Available Users** column by holding down the **CNTL Key**. + * In the **Users** section, select ```Student1``` and ```SMATRAINING\SMAUSER``` in the **Available Users** column by holding down the **CTRL Key**. * Click the **>** button to move the users to the **Assigned Users** column. * Click the **Save** Button. @@ -48,9 +48,9 @@ If you needed to add multiple escalation levels, you would click add again on th #### Applying the Escalation -7. Under the **Library** > **Management**, click on **Notification Triggers**. +7. Under the **Library** > **Management**, select **Notification Triggers**. 8. In the **Notification Triggers** section, click on **Escalation Example**. -9. In the **Trigger** drop-down in the bottom half of the screen, validate that **Job Failed** is selected. +9. In the **Trigger Name** drop-down in the bottom half of the screen, validate that **Job Failed** is selected. 10. In the **Escalation Rule** drop-down, select **Escalation Job Failure**. 11. Click the **Save** Button. 12. Close **Library**. diff --git a/docs/Unit 3 Lab B.md b/docs/Unit 3 Lab B.md index 15bc8da..32067d0 100644 --- a/docs/Unit 3 Lab B.md +++ b/docs/Unit 3 Lab B.md @@ -10,7 +10,7 @@ To use the skills learned so far to alert you when jobs are **Late to Start**, * ### Summary -Congo Online Retail needs to make sure all shipping orders are processed and ready to go before 5 am (Monday - Sunday) utilizing a Schedule called **Conge Retail Order Processing**. +Congo Online Retail needs to make sure all shipping orders are processed and ready to go before 5 am (Monday - Sunday) utilizing a Schedule called **Congo Retail Order Processing**. **_If any of these processes have not completed by 5 am or if any are taking longer than 5 minutes, you need to be notified._** @@ -25,7 +25,7 @@ Congo Online Retail needs to make sure all shipping orders are processed and rea * **Auto Delete** for ```7``` days ago :::tip -* You can reference [Unit 1 - Exercise 1](/docs/Unit%201%20Exercise%201.md) for steps on how to create a Schedule. +You can reference [**Unit 1 - Exercise 1**](/docs/Unit%201%20Exercise%201.md) for steps on how to create a Schedule. ::: #### Create the Jobs @@ -34,56 +34,58 @@ Congo Online Retail needs to make sure all shipping orders are processed and rea * **Legos** * Command Line: ```"C:\scripts\ShipmentProcessorToys.EXE" –t90``` * Add documentation + * Tag the Job under ```Toys``` * Add a frequency that will allow the job to run everyday. * Start Offset: ```03:00``` * Late to Start Offset: ```01:55 (4:55 am)``` * Max Run Time: ```5``` - * Tag the Job under ```Toys``` * **Nerf** * Command Line: ```"C:\scripts\ShipmentProcessorToys.EXE" –t120``` * Add documentation + * Tag the Job under ```Toys``` * Add a frequency that will allow the job to run everyday. * Start Offset: ```04:00``` * Late to Finish Offset: ```01:00 (5:00 am)``` * Max Run Time: ```5``` - * Tag the Job under ```Toys``` * **Smartphones** * Command Line: ```"C:\scripts\ShipmentProcessorElectronics.EXE" –t15``` * Add documentation + * Tag the Job under ```Electronics``` * Add a frequency that will allow the job to run everyday. * Start Offset: ``04:30`` * Late to Finish Offset: ```00:30 (5:00 am)``` * Max Run Time: ```5``` - * Tag the Job under ```Electronics``` * **XBOX** * Command Line: ```"C:\scripts\ShipmentProcessorElectronics.EXE" –t350``` * Add documentation + * Tag the Job under ```Electronics``` * Add a frequency that will allow the job to run everyday. * Start Offset: ```02:30``` * Late to Finish Offset: ```02:30 (5:00 am)``` * Max Run Time: ```5``` - * Tag the Job under ```Electronics``` * **Levis** * Command Line: ```"C:\scripts\ShipmentProcessorClothing.EXE" –t45``` * Add documentation + * Tag the Job under ```Clothing``` * Add a frequency that will allow the job to run everyday. * Start Offset: ```03:10``` * Late to Start Offset: ```01:45 (4:55 am)``` * Max Run Time: ```5``` - * Tag the Job under ```Clothing``` * **Nike** * Command Line: ```"C:\scripts\ShipmentProcessorClothing.EXE" –t75``` * Add documentation + * Tag the Job under ```Clothing``` * Add a frequency that will allow the job to run everyday. * Start Offset: ```03:45``` * Late to Finish Offset: ```01:15 (5:00 am)``` * Max Run Time: ```5``` - * Tag the Job under ```Clothing``` :::tip -* You can reference [Unit 1 - Exercise 3](/docs/Unit%201%20Exercise%203.md) for steps on how to create a Windows Job. -* You can reference [Unit 1 - Exercise 5](/docs/Unit%201%20Exercise%205.md) for steps on how to add Tags. -* You can reference [Unit 2 - Exercise 11](/docs/Unit%202%20Exercise%2011.md) and Other Frequency Details for steps on how to set up Start Offsets, Late to Start, and Late to Finish settings. +You can reference [**Unit 1 - Exercise 3**](/docs/Unit%201%20Exercise%203.md) for steps on how to create a Windows Job. + +You can reference [**Unit 1 - Exercise 5**](/docs/Unit%201%20Exercise%205.md) for steps on how to add Tags. + +You can reference [**Unit 2 - Exercise 11**](/docs/Unit%202%20Exercise%2011.md) and Other Frequency Details for steps on how to set up Start Offsets, Late to Start, and Late to Finish settings. ::: #### Create the Notifications @@ -100,7 +102,7 @@ It is best practice to setup email notifications using **System Properties** to ::: :::tip -* You can reference [Unit 3 - Exercise 8](/docs/Unit%203%20Exercise%208.md) for steps on how to create Notifications. +You can reference [**Unit 3 - Exercise 8**](/docs/Unit%203%20Exercise%208.md) for steps on how to create Notifications. ::: #### Create the Schedule @@ -114,7 +116,7 @@ You should receive 7 emails: 2 Late to Start, 4 Late to Finish, and 1 Exceeded M ::: :::tip -* You can reference [Unit 1 - Exercise 6](/docs/Unit%201%20Exercise%206.md) for steps on how to build a schedule. +You can reference [**Unit 1 - Exercise 6**](/docs/Unit%201%20Exercise%206.md) for steps on how to build a schedule. ::: diff --git a/docs/Unit 3 Lab C.md b/docs/Unit 3 Lab C.md index 6c2abcb..53e4889 100644 --- a/docs/Unit 3 Lab C.md +++ b/docs/Unit 3 Lab C.md @@ -13,7 +13,7 @@ To use the property types we have learned about to design a schedule of jobs tha The Accounting Department needs a folder for each product labeled with the product's name and prior day's date. You will utilize a script called **Create_Folder** that resides in ```C:\Scripts``` to create a directory for each product that Congo ships: **Legos**, **Nerf**, **Smartphones**, **XBOX**, **Levis**, and **Nike**. These new directories will reside in a path specific to the Accounting Department, ```C:\Accounting``` and will have a ```yyyy-mm-dd(-1d)_``` for the folder name. :::tip -Best practice is to create a property for any value that will be typed more than once or may change every few years. Some examples of properties that may be used in thes lab are: +Best practice is to create a property for any value that will be typed more than once or may change every few years. Some examples of properties that may be used in the lab are: * **PATH_Scripts** property with a value of ```C:\scripts``` * **PATH_Accounting** property with a value of ```C:\Accounting``` * **$SCHEDULE DATE** property with a value of ```yyyy-mm-dd``` @@ -35,7 +35,7 @@ Best practice is to create a property for any value that will be typed more than * Name each **Job** the same as its **product name** * This Job needs to run on the **SMATRAINING** machine * This Job needs to run as the **SMATRAINING\SMAUSER** User ID -* Utilizing the **Magic Wand** or **CNTL+SPACE** create a command line using properties in the appropriate places to run the following statement: +* Utilizing the **Magic Wand** or **CTRL + SPACE** create a command line using properties in the appropriate places to run the following statement: * ```"C:\scripts\Create_Folder.cmd" "C:\Accounting\yyyy-mm-dd(-1d)_Legos"``` :::tip Hint Remember that each Job is assigned to a product and the folder name must match the product. You can use a System Property in place of the product name in the command line. diff --git a/docs/Unit 4 Exercise 1.md b/docs/Unit 4 Exercise 1.md index 54c0b06..4e5a8b4 100644 --- a/docs/Unit 4 Exercise 1.md +++ b/docs/Unit 4 Exercise 1.md @@ -31,7 +31,7 @@ You will then have each job trigger a notification, so that you know how many re 5. In **Library** > **Administration**, select **Master Schedules**. 6. Click the **Add** button. -7. On the **Master Scheudle Definition** screen: +7. On the **Master Schedule Definition** screen: * In the **Schedule Name** field, enter ```My Resource Schedule```. * Add **Documentation** to your Schedule. * Monday through Sunday are working days @@ -49,9 +49,9 @@ You will then have each job trigger a notification, so that you know how many re 12. On the **Master Job Definition** screen, * In the **Name** field, enter ```Use 2 Job A```. * In the **Job Type** drop down, select **Windows**. - * In the **Machine** drop downd, select **SMATraining** - * In the **User ID** drop down, selet **SMATRAINING\SMAUSER** - * In the **Command Line** field, enter ```"C:\Program Files\OpConxps\MSLSAM\genericp.exe" -t20```. _Remeber to user properties where acceptable._ + * In the **Machine** drop down, select **SMATraining** + * In the **User ID** drop down, select **SMATRAINING\SMAUSER** + * In the **Command Line** field, enter ```"C:\Program Files\OpConxps\MSLSAM\genericp.exe" -t20```. _Remember to user properties where acceptable._ * Click **Save**. 13. Click the **Lock** icon to enter **Admin Mode**. 14. In the **Documentation** section, add some **documentation**. diff --git a/docs/Unit 4 Exercise 10.md b/docs/Unit 4 Exercise 10.md index ffe6471..623bd3a 100644 --- a/docs/Unit 4 Exercise 10.md +++ b/docs/Unit 4 Exercise 10.md @@ -16,7 +16,7 @@ Then you will manually release each of the jobs and monitor the movement of the ### Instructions -#### Create Driectories and a File +#### Create Directories and the File 1. In a **Windows Explorer** create two directories, ```C:\Finish``` and ```C:\Start```. 2. Open **Notepad** and create a new file. @@ -31,14 +31,14 @@ Then you will manually release each of the jobs and monitor the movement of the * In the **Name** field, enter ```Windows Sub-Types Exercise```. * In the **Documentation** field, enter in some documentation. * _Example: This is a training Schedule for Windows Sub-Type Jobs._ -* Saturday and Sunday are 88non-working days**. +* Saturday and Sunday are **non-working days**. * Do **NOT** configure **Auto Build**. * Click the **Save**. 8. Click **Back**. #### Add the Copy Job to the Schedule -9. Utilizing the filters in the **Scheudle List**, locate and select **Windows Sub-Types Exercise**. +9. Utilizing the filters in the **Schedule List**, locate and select **Windows Sub-Types Exercise**. 10. Select **Add Job** in the side menu. 11. On **Master Job Definition** screen: * In the **Name** field, enter ```File Copy```. diff --git a/docs/Unit 4 Exercise 11.md b/docs/Unit 4 Exercise 11.md index 92f4da0..f068cd4 100644 --- a/docs/Unit 4 Exercise 11.md +++ b/docs/Unit 4 Exercise 11.md @@ -59,7 +59,7 @@ You are going to create a schedule with two jobs. One job will create the file w * Click **Save** 12. Add **Documentation** to the Job. 13. Give the Job a **Frequency** of **Mon-Fri-N** -14. Select the **Frequecny** in the **Active** column, in the **Job Build Status** drop-down, select **On Hold** +14. Select the **Frequency** in the **Active** column, in the **Job Build Status** drop-down, select **On Hold** 15. Click **Save** 16. click **Back** diff --git a/docs/Unit 4 Exercise 12.md b/docs/Unit 4 Exercise 12.md index c4b0d4e..b47fad0 100644 --- a/docs/Unit 4 Exercise 12.md +++ b/docs/Unit 4 Exercise 12.md @@ -14,7 +14,7 @@ You are going to create a schedule with three jobs. One job will create the file ### Instructions -#### Create the Sub-Schedule to Processs the Files +#### Create the Sub-Schedule to Process the Files 1. In **Library** > **Administration**, select on **Master Schedule**. 2. Click the **Add** button. @@ -38,7 +38,7 @@ You are going to create a schedule with three jobs. One job will create the file * In the **Machine Selection** drop-down, select **SMATraining** * In the **User ID** drop-down, select **SMATRAINING\SMAUSER** * In the **Command Line** field, enter ```"C:\Program Files\OpConxps\MSLSAM\genericp.exe" -t10``` - * _Remeber to use properties where acceptable._ + * _Remember to use properties where acceptable._ * Click **Save** * Add **Documentation** to the Job. * Give the Job a **Frequency** of ```Mon-Sun-O```. @@ -71,7 +71,7 @@ You are going to create a schedule with three jobs. One job will create the file #### Create the Parent Schedule 12. Click the **Add** button. -13. On the **Master Schedule Definistion screen: +13. On the **Master Schedule Definition** screen: * In the **Name** field, enter ```File Arrival - Multiple Files``` * Add **Documentation** * Pick your working days @@ -81,7 +81,7 @@ You are going to create a schedule with three jobs. One job will create the file #### Add the FA MultiFile -15. In the **Schedule List**, search for and select the **File Arrival - Multiple Filess** schedule. +15. In the **Schedule List**, search for and select the **File Arrival - Multiple Files** schedule. 16. Click **View** 17. Click **Add Job** 18. On the **Master Schedule Definition** screen: diff --git a/docs/Unit 4 Exercise 2.md b/docs/Unit 4 Exercise 2.md index 4bc9f1c..1b252ea 100644 --- a/docs/Unit 4 Exercise 2.md +++ b/docs/Unit 4 Exercise 2.md @@ -79,13 +79,14 @@ Utilizing a **Threshold** called **TrainingThreshold** to prevent a job from run 22. In the side menu in **Studio**, select **Add Job** 23. On the **Master Job Definition** screen: - * In the **Name** field, eneter ```Initial Value Notification```. + * In the **Name** field, enter ```Initial Value Notification```. * In the **Job Type** field, leave it as **Null Job**. * Add **Documentation**. * In the **Frequency** section, move the **Mon-Sun-O** frequency into the **Active** column. + * Click **Save**. 24. Click **Back** to get back to the **Studio**. 25. Utilizing the **Copy** function, copy the **Initial Value Notification** job to create 2 more jobs. One called, **After Update Job** and the other called **Final Value Job**. -26. Select the **Initial Value Notificaiton**, click the **Wrench** icon and enter **Admin Mode**. +26. Select the **Initial Value Notification**, click the **Wrench** icon and enter **Admin Mode**. * In the **Event** section, click **+** * In the **Event** pop-up window: * In the **Send Event On** dropdown, select **Job Status**. @@ -97,7 +98,7 @@ Utilizing a **Threshold** called **TrainingThreshold** to prevent a job from run * Click the **Save** button. * Click the **Save** button in **Master Job Definition**. * Click **Back** -27. Select the **After Value Notificaiton**, click the **Wrench** icon and enter **Admin Mode**. +27. Select the **After Value Notification**, click the **Wrench** icon and enter **Admin Mode**. * In the **Event** section, click **+** * In the **Event** pop-up window: * In the **Send Event On** dropdown, select **Job Status**. @@ -109,7 +110,7 @@ Utilizing a **Threshold** called **TrainingThreshold** to prevent a job from run * Click the **Save** button. * Click the **Save** button in **Master Job Definition**. * Click **Back** -28. Select the **Final Value Notificaiton**, click the **Wrench** icon and enter **Admin Mode**. +28. Select the **Final Value Notification**, click the **Wrench** icon and enter **Admin Mode**. * In the **Event** section, click **+** * In the **Event** pop-up window: * In the **Send Event On** dropdown, select **Job Status**. diff --git a/docs/Unit 4 Exercise 3.md b/docs/Unit 4 Exercise 3.md index b465d02..c7e97f0 100644 --- a/docs/Unit 4 Exercise 3.md +++ b/docs/Unit 4 Exercise 3.md @@ -24,7 +24,7 @@ Utilizing the **My Threshold Schedule** created in the previous exercise, you wi * In the **Job Type** drop down, select **Windows**. * In the **Machine** drop down, select **SMATraining**. * In the **User ID** drop down, select **SMATRAINING\SMAUSER**. -* In the **Command Line** field, enter ```"C:\scripts\ExerciseThreshold.cmd" +1```. _Remeber to use properties where acceptable._ +* In the **Command Line** field, enter ```"C:\scripts\ExerciseThreshold.cmd" +1```. _Remember to use properties where acceptable._ * Do not forget to add **Documentation**. * In the **frequency** section, move the ```Mon-Sun-O``` frequency into the **Active** column. @@ -37,7 +37,7 @@ Utilizing the **My Threshold Schedule** created in the previous exercise, you wi #### Add the Job to Operations -8. Open **Processses** to verify that **My Threshold Schedule** is completed. +8. Open **Processes** to verify that **My Threshold Schedule** is completed. 9. Return to **My Threshold Schedule** and add the Job just created to the Daily Schedule list. * Select **My Threshold Schedule** and click the **(+)** button in the **Schedule Selection** side menu. * Select **Threshold External Event Job** and click the **Next** button. @@ -62,7 +62,7 @@ What happened? 15. Click the **Wrench** icon to open the **Daily Job Definition**. 16. Click the **Lock** icon to edit Daily details. 17. In **Task Details**, change the **Command Line** to this: ```“C:\scripts\ExerciseThreshold.cmd” -1``` -18. Click the **Save** button (This will only save the Job in the Daily Definiton). +18. Click the **Save** button (This will only save the Job in the Daily Definition). 19. In **Processes**, right-Click the Job and select **Restart** in the **Job Status Update**. 20. Wait until the Job finishes **OK**. 21. In **Library** > **Administration**, select **Thresholds**. diff --git a/docs/Unit 4 Exercise 4.md b/docs/Unit 4 Exercise 4.md index 08eede7..06ef0fc 100644 --- a/docs/Unit 4 Exercise 4.md +++ b/docs/Unit 4 Exercise 4.md @@ -23,8 +23,8 @@ Using the existing schedule called, **Embedded Scripts Training**, create a Wind 4. In the **Name** textbox, enter ```Create Daily Folder```. 5. In the **Job Type** drop-down list, select **Windows**. 6. In the **Machine Selection** drop-down list, select **SMATraining**. -7. In the **Job Action** drop-down list, select **Embedded Script**. 8. In the **User ID** drop-down menu, select **SMATRAINING\SMAUSER**. +7. In the **Job Action** drop-down list, select **Embedded Script**. 9. In the **Script** drop-down list, select the **Create_Folder**. 10. Leave the Version as **LATEST (X)**. 11. In the **Runner** drop-down menu, select **Command Shell**. @@ -35,7 +35,7 @@ Using the existing schedule called, **Embedded Scripts Training**, create a Wind 15. Scroll to the **Frequency** sections and **ADD** a Frequency called ```Mon-Fri-N```. 16. Add **Documentation** and then click the **Save** button. -#### Verify Directory Does NOT Exsist +#### Verify Directory Does NOT Exist 17. Outside of OpCon (Using **Windows File Explorer**) verify that the following folder does not exist in the following path, ```“C:\IT\Backups\[[$SCHEDULE DATEYYYYMM]]”```, (where ```$SCHEDULE DATEYYYYMM``` refers to the current month of the current year) diff --git a/docs/Unit 4 Exercise 5.md b/docs/Unit 4 Exercise 5.md index f5ca2aa..a2b2762 100644 --- a/docs/Unit 4 Exercise 5.md +++ b/docs/Unit 4 Exercise 5.md @@ -62,7 +62,7 @@ In the **Script Repository**, import a script called **ExerciseThreshold.cmd**. * Close the **Add Jobs** results screen. * Wait until the Job finishes **OK**. 15. After the Job is finished, open the **Thresholds** tab and check the value. It must be ```2```. -16. For practice, **edit the Daily Job** and change the value in the **Arguements** field to ```0```, restart the Job and check the **Threshold** again. +16. For practice, **edit the Daily Job** and change the value in the **Arguments** field to ```0```, restart the Job and check the **Threshold** again. :::note The TrainingThreshold should have a value of 0 when this exercise is complete. diff --git a/docs/Unit 4 Exercise 6.md b/docs/Unit 4 Exercise 6.md index eb89689..d7806d5 100644 --- a/docs/Unit 4 Exercise 6.md +++ b/docs/Unit 4 Exercise 6.md @@ -49,7 +49,7 @@ Create a Schedule named **Repeating Schedule**. This schedule will contain 4 con * Within the **Frequency** box, select **Example-Mon-Sun-O** in the **Inactive** list and move it to the **Active** list. * Click the **Save** button. 9. Click **Back**. -10. Utilizing the **Copy** function, copy Job 1 unitl you have 5 jobs total. +10. Utilizing the **Copy** function, copy Job 1 until you have 5 jobs total. 11. Create **Dependencies** between the 5 jobs so they run in a sequential chain. * Job 1 → Job 2 → Job 3 → Job 4 → Job 5 diff --git a/docs/Unit 4 Exercise 7.md b/docs/Unit 4 Exercise 7.md index cc98f3e..41d0e7e 100644 --- a/docs/Unit 4 Exercise 7.md +++ b/docs/Unit 4 Exercise 7.md @@ -10,7 +10,7 @@ To use a Resource to prevent multiple Container jobs from kicking off at the sam ### Summary -Create a Schedule called **Process Files**. Create 5 new container jobs named **File 1**, **File 2**, etc. within this Schedule and assign the **SS_Repeating** sub-schedule that was created in Exercise 6. These contaner jobs will also have a **Resource Dependency** to prevent them from all kicking off at the same time. +Create a Schedule called **Process Files**. Create 5 new container jobs named **File 1**, **File 2**, etc. within this Schedule and assign the **SS_Repeating** sub-schedule that was created in Exercise 6. These container jobs will also have a **Resource Dependency** to prevent them from all kicking off at the same time. ### Instructions @@ -35,7 +35,7 @@ Create a Schedule called **Process Files**. Create 5 new container jobs named ** * In the **Documentation** field, enter some documentation * _Example: This is the Parent Schedule._ * Saturday and Sunday are **NOT working days**. -* This sub-schedule does use the **Master Calendar** +* This schedule does use the **Master Calendar** * Click the **Save** button. 8. Close **Studio** diff --git a/docs/Unit 4 Exercise 8.md b/docs/Unit 4 Exercise 8.md index ecd59ca..61abdef 100644 --- a/docs/Unit 4 Exercise 8.md +++ b/docs/Unit 4 Exercise 8.md @@ -10,7 +10,7 @@ To use Negative Frequency to prevent 2 container jobs from being built on the sa ### Summary -In a single schedule called, **NightlyProcessing**, you will have 2 container jobs each calling a unique sub-schedule, **SS_Daily** and **SS-Monthly**. One container called, **Daily**, will run evey day except for the end of the month. The other called, **Monthly**, will run only at end of month. +In a single schedule called, **NightlyProcessing**, you will have 2 container jobs each calling a unique sub-schedule, **SS_Daily** and **SS-Monthly**. One container called, **Daily**, will run every day except for the end of the month. The other called, **Monthly**, will run only at end of month. ### Instructions @@ -32,7 +32,7 @@ In a single schedule called, **NightlyProcessing**, you will have 2 container jo 6. Using the filters, locate and select **SS-Monthly**. 7. Click the **View**. 8. Utilizing the **Copy** function, copy **Job 1** two times to create **Job 6** and **Job 7**. -9. **Add Dependencies** to have the new jobs run after **Job 5** in sequencial order. +9. **Add Dependencies** to have the new jobs run after **Job 5** in sequential order. * _Job 1 → Job 2 → Job 3 → Job 4 → Job 5 → Job 6 → Job 7_ 10. Click **Back** until you return the **Schedule List** @@ -44,7 +44,7 @@ In a single schedule called, **NightlyProcessing**, you will have 2 container jo * In the **Name** field, enter ```NightlyProcessing```. * In the **Documentation** field, enter **This is the Main Schedule**. * In the **Start Offset Hours** box, enter ```19``` (19:00 or 07:00 PM). -* In the **Work Days** section, select Sautrday and Sunday. +* In the **Work Days** section, select Saturday and Sunday. * In the **Holiday Calendar Settings**, select **Use Master Holiday**. * Select **Auto Build** and set it as ```7``` days in advance for ```1```. * Select **Auto Delete** and set it as ```7```. diff --git a/docs/Unit 4 Exercise 9.md b/docs/Unit 4 Exercise 9.md index 937b3a3..cb64cfe 100644 --- a/docs/Unit 4 Exercise 9.md +++ b/docs/Unit 4 Exercise 9.md @@ -19,7 +19,7 @@ To add a **File Transfer** job to **My First Schedule**. This job will move a fi 1. In **Library** > **Administration**, select **Master Jobs**. 2. Click **ADD**. 3. On the **Master Job Definition** screen: -* In the **Schedule** drop-down, select **My First Scheudle**. +* In the **Schedule** drop-down, select **My First Schedule**. * In the **Name** field, enter ```SMAFT Job 1```. * In the **Job Type** dropdown list, select **File Transfer**. * In the **Source** section: diff --git a/docs/Unit 4 Lab A.md b/docs/Unit 4 Lab A.md index 73b5849..3654f6d 100644 --- a/docs/Unit 4 Lab A.md +++ b/docs/Unit 4 Lab A.md @@ -16,18 +16,18 @@ A unique script is run for each product: **Toys** -* Legos: ```C:\scripts\UpdInvLegos.CMD``` -* Nerf: ```C:\scripts\UpdInvNerf.CMD``` +* Legos: ```C:\scripts\UpdInvLegos.CMD``` +* Nerf: ```C:\scripts\UpdInvNerf.CMD``` **Clothing** -* Nike: ```C:\scripts\UpdInvNike.CMD``` -* Levis: ```C:\scripts\UpdInvLevis.CMD``` +* Nike: ```C:\scripts\UpdInvNike.CMD``` +* Levis: ```C:\scripts\UpdInvLevis.CMD``` **Electronics** -* Smartphones: ```C:\scripts\UpdInvSmartphones.CMD``` -* XBOX: ```C:\scripts\UpdInvXBOX.CMD``` +* Smartphones: ```C:\scripts\UpdInvSmartphones.CMD``` +* XBOX: ```C:\scripts\UpdInvXBOX.CMD``` These jobs can run in the order they are listed above with two exceptions: diff --git a/docs/Unit 4 Lab B.md b/docs/Unit 4 Lab B.md index cceb765..bd89eef 100644 --- a/docs/Unit 4 Lab B.md +++ b/docs/Unit 4 Lab B.md @@ -10,7 +10,7 @@ To use File Arrival to detect the arrival of a multiple files and add a containe ### Summary -Congo Online Retail Inc. has a file for every office that made a staffing change during the month. There is no way to predict the number of files that will be present every day of the month but will always show up between **00:00 (midnight)** and **7:00 PM**. We will not know the name of the files, but we know the directory where they will be placed and the extention, **.txt**. Since these files come in randomly and multiple files can show up at once, only one file can be processed at a given time. +Congo Online Retail Inc. has a file for every office that made a staffing change during the month. There is no way to predict the number of files that will be present every day of the month but will always show up between **00:00 (midnight)** and **7:00 PM**. We will not know the name of the files, but we know the directory where they will be placed and the extension, **.txt**. Since these files come in randomly and multiple files can show up at once, only one file can be processed at a given time. The steps taken to process each file are: * **Decrypt** @@ -72,7 +72,7 @@ The **Schedule Instance Property** ```[[SI.FILENAME]]``` will be passed by the * * [[$SCHEDULE NAME]] * File Arrival * Create a **File Arrival** job called **FA Incoming** - * Monitor the **C:\Human Resources\Incoming Files** for any files that have a ***.txt** extention. + * Monitor the **C:\Human Resources\Incoming Files** for any files that have a ***.txt** extension. * _Example: "[[HR-Incoming]]\*.txt" or "C:\Human Resources\Incoming Files\*.txt"_ * **Start Time** for file creation should be ```00:00``` (midnight) * **End Time** for the file creation should be ```07:00 PM``` @@ -97,7 +97,7 @@ The **Schedule Instance Property** ```[[SI.FILENAME]]``` will be passed by the * #### Build the Schedule * Build the schedule for today's date -* Monitor the scheudle to ensure that each of the 5 files is processed. +* Monitor the schedule to ensure that each of the 5 files is processed. * You should process a file for each of the following cities but not necessarily in this order: * Chicago * Houston @@ -158,7 +158,7 @@ The **Schedule Instance Property** ```[[SI.FILENAME]]``` will be passed by the * * **Auto-build** the Schedule ```7``` days in advance for ```1``` day * **Auto-delete** the Schedule for ```7``` days ago * Add **Documentation** for the Schedule -* Create a **Container Job** in the **HR Import Schedul**e named **HR Import Processing** +* Create a **Container Job** in the **HR Import Schedule** named **HR Import Processing** * The **Container Job** should run the **SS-HR Import Processing SubSchedule** * The container Job should **Allow Multi-Instance** * Add **Documentation** diff --git a/docs/Update Master Job.md b/docs/Update Master Job.md index c69a462..94e2a9e 100644 --- a/docs/Update Master Job.md +++ b/docs/Update Master Job.md @@ -30,7 +30,7 @@ When a Job is edited in Daily List, changes are applied **only** to a specific c Currently configurable options: * Machines/Machine Groups -* Prerun Command Line +* Pre-run Command Line * Working Directory * Failure Criteria * Run Command Line diff --git a/docs/User Mode.md b/docs/User Mode.md index 1f1bcb6..37208ad 100644 --- a/docs/User Mode.md +++ b/docs/User Mode.md @@ -16,7 +16,7 @@ Users not in the ```ocadm``` Role or in a Role without the ```Maintain Service - If user inputs are configured, the Service Request will allow the User to configure the User Input field(s) for the Service Request * The page will enforce any validation rules - If the validation fails, a message in red text will indicate an invalid entry - - Form vailidation takes place each time the ```Submit``` button is clicked + - Form validation takes place each time the ```Submit``` button is clicked || |---| diff --git a/docs/Viewing Process Indicators.md b/docs/Viewing Process Indicators.md index ef6fbf3..6e2081e 100644 --- a/docs/Viewing Process Indicators.md +++ b/docs/Viewing Process Indicators.md @@ -2,7 +2,7 @@ sidebar_label: 'Viewing Process Indicators' --- -* When a Service Request is submitted, a page will dispay to indicate the execution of the Request with a progress bar +* When a Service Request is submitted, a page will display to indicate the execution of the Request with a progress bar * This page can be exited by clicking **OK** ![](../static/imgbasic/SelfServiceRequestProgressBar.png) diff --git a/docs/Windows File Movement Job Sub-Types.md b/docs/Windows File Movement Job Sub-Types.md index 03d9747..a34319a 100644 --- a/docs/Windows File Movement Job Sub-Types.md +++ b/docs/Windows File Movement Job Sub-Types.md @@ -13,7 +13,7 @@ sidebar_label: 'Windows File Movement Job Sub-Types' * **File Rename** - Renames a file * **File Delete** - Delete files * **Corelation** - Special integration with Corelation - * **WSFTP Pro** - Special integration with WSFTP Pro + * **WS-FTP Pro** - Special integration with WS-FTP Pro ![](../static/imgbasic/Job_Subtypes_SM.png) diff --git a/sidebars.js b/sidebars.js index d77226a..f347109 100644 --- a/sidebars.js +++ b/sidebars.js @@ -32,8 +32,6 @@ module.exports = { 'Unit 1 Exercise 7', 'Update Master Job', 'Unit 1 Exercise 8', - 'Workflow Designer', - 'Unit 1 Exercise 9', 'OpCon Logs', 'Unit 1 Lab', ], @@ -61,12 +59,13 @@ module.exports = { 'Unit 2 Exercise 8', 'On Request -- Periods', 'Unit 2 Exercise 9', - 'On Interval -- Odd Even -- Annual Plan', + 'On Interval -- Annual Plan -- Odd Even', 'Unit 2 Exercise 10', 'Other Frequency Details', 'Looping Jobs', - 'Multiple Frequencies', 'Unit 2 Exercise 11', + 'Multiple Frequencies', + 'Unit 2 Exercise 12', 'Unit 2 Lab A', 'OpCon User Help', 'Troubleshooting Schedules And Jobs', @@ -179,6 +178,7 @@ module.exports = { collapsed: true, items: [ 'EM_Walkthroughs', + 'EM_Walkthroughs_Alt', ], }, //{ diff --git a/static/imgbasic/Click-n-Drag.png b/static/imgbasic/Click-n-Drag.png new file mode 100644 index 0000000..afd3064 --- /dev/null +++ b/static/imgbasic/Click-n-Drag.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62e5ff3d249c6ba810fcb630bdac1cadfdae99fecb5006eeffde66ece05c5ae0 +size 111452 From 1a699b0ba1bbe54bfe1c58fcda8971e1b50ea510 Mon Sep 17 00:00:00 2001 From: MoKranda <60985608+MoKranda@users.noreply.github.com> Date: Tue, 16 Jan 2024 09:42:49 -0600 Subject: [PATCH 2/2] Update Unit 2 Exercise 11.md removed 'To become' and correct grammar after change. --- docs/Unit 2 Exercise 11.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/Unit 2 Exercise 11.md b/docs/Unit 2 Exercise 11.md index 56845c1..5c436df 100644 --- a/docs/Unit 2 Exercise 11.md +++ b/docs/Unit 2 Exercise 11.md @@ -6,7 +6,7 @@ sidebar_label: 'Unit 2 Exercise 11' ### Objective -To become utilize the Restart setting to create a Looping Job. +Utilize the Restart settings to create a Looping Job. ### Summary @@ -90,4 +90,4 @@ Your browser does not support the video tag. The Negative Frequency will appear purple ::: -
\ No newline at end of file +