diff --git a/docs/Audit Management.md b/docs/Audit Management.md index 9b0b70b..4c3c17a 100644 --- a/docs/Audit Management.md +++ b/docs/Audit Management.md @@ -4,11 +4,23 @@ sidebar_label: 'Audit Management' * Used to view history of User updates to the OpCon database -* Resides under Management in Enterprise Manager +* Resides under **Management** > **Reporting** * The Audit Management (view) screen displays drop list for user, audit category selection, and options for date range to view preferred Audit information * Select **Master Job** in Audit Categories drop-down list * Click View Audit button or export data to .CSV file +![AuditHistory](../static/imgbasic/AuditHistory.png) + +![AuditHistory2](../static/imgbasic/AuditHistory2.png) + +![Columns](../static/imgbasic/Columns.png) + +![Categories](../static/imgbasic/Categories.png) + +## Enterprise Manager + +
+ ![Picture295](../static/imgbasic/295.png) ![Picture296](../static/imgbasic/296.png) @@ -27,4 +39,6 @@ sidebar_label: 'Audit Management' ### Audit Management Table -![Picture300](../static/imgbasic/300.png) \ No newline at end of file +![Picture300](../static/imgbasic/300.png) + +
\ No newline at end of file diff --git a/docs/Embedded Scripts.md b/docs/Embedded Scripts.md index d6ce629..d1ccf40 100644 --- a/docs/Embedded Scripts.md +++ b/docs/Embedded Scripts.md @@ -18,12 +18,13 @@ sidebar_label: 'Embedded Scripts' ### Script Types * Configure type of Scripts which can be stored by OpCon -* There are 5 **predefined** Script types, but more can be added +* There are 6 **predefined** Script types, but more can be added * Command Shell (.cmd) * Perl (.ps) * PowerShell (.ps1) * Python (.py) * VBScript (.vbs) + 8 SQL (.sql) ![](../static/imgbasic/sm-script-types.png) diff --git a/docs/Operation Views.md b/docs/Operation Views.md index b7255d3..c2f3735 100644 --- a/docs/Operation Views.md +++ b/docs/Operation Views.md @@ -79,7 +79,7 @@ When a Job is selected with a right-click several options are made available in * Job Configuration Tool * Job Executions History * Job Summary -* Job Status Update +* Status Update * Job Output * Diagram diff --git a/docs/SM - Job Configuration.md b/docs/SM - Job Configuration.md index a6e0af5..651f2ea 100644 --- a/docs/SM - Job Configuration.md +++ b/docs/SM - Job Configuration.md @@ -48,6 +48,6 @@ Right-Click Jobs and available actions appear ![](../static/imgbasic/Picture78.png) -### Bulk Job Status Update +### Bulk Status Update ![](../static/imgbasic/Picture79.png) diff --git a/docs/SM - Job Status.md b/docs/SM - Job Status.md index adc9d0d..fa5e399 100644 --- a/docs/SM - Job Status.md +++ b/docs/SM - Job Status.md @@ -23,7 +23,7 @@ When a Job is selected with a right-click several options are made available in * Job Configuration Tool * Job Executions History * Job Summary -* Job Status Update +* Status Update * Job Output * Diagram diff --git a/docs/SM - Machine Status And User Accounts.md b/docs/SM - Machine Status And User Accounts.md index 0300834..63c35d5 100644 --- a/docs/SM - Machine Status And User Accounts.md +++ b/docs/SM - Machine Status And User Accounts.md @@ -7,7 +7,7 @@ sidebar_label: 'SM - Machine Status And User Accounts' * Machine Status can be determined by the heart icon in the bottom right hand corner of the screen * Selecting the icon will display all Agents and their status * Machines can be bulk selected for status updates - * As with Schedule and Job status updates, only options available to a machine will be configurable + * As with Schedule and Status Updates, only options available to a machine will be configurable ![](../static/imgbasic/Picture83.png) diff --git a/docs/SMA History.md b/docs/SMA History.md index c66a83e..080db19 100644 --- a/docs/SMA History.md +++ b/docs/SMA History.md @@ -6,8 +6,7 @@ sidebar_label: 'SMA History' * Founded in 1980 * Headquarters in Houston, Texas -* Over 800 Clients -* Offices in USA and France +* Service Over 800 Clients Worldwide * Proven Solution for all Operating Systems * Customer Driven Technology * 24x7x365 Support diff --git a/docs/Schedule Status.md b/docs/Schedule Status.md index 36b4927..921fcc9 100644 --- a/docs/Schedule Status.md +++ b/docs/Schedule Status.md @@ -46,7 +46,7 @@ Right-Click Jobs and available actions appear ![Picture78](../static/imgbasic/Picture78.png) -### Bulk Job Status Update +### Bulk Status Update ![Picture79](../static/imgbasic/Picture79.png) diff --git a/docs/Support Information.md b/docs/Support Information.md index cee15e1..a2ebe97 100644 --- a/docs/Support Information.md +++ b/docs/Support Information.md @@ -36,12 +36,12 @@ sidebar_label: 'Support Information' * OpCon Wizards Group * A Learning Community hosted as a LinkedIn Group that provides communication and feedback with OpCon experts within SMA and with other users -##### OpCon Roundtables +##### OpCon Connections -* SMA Roundtables -* 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. +* SMA Connections +* A new series of sessions designed to develop meaningful connections with and among our valued customers. These sessions will provide a space where you can engage not only with our products but also with each other, fostering a collaborative information network.. -##### Webinars +##### SMA Webinars * SMA Webinars * Webinars are educational presentations updating clients on releases and improvements as well as demonstrations of OpCon use cases. diff --git a/docs/Unit 1 Exercise 8.md b/docs/Unit 1 Exercise 8.md index 94eed7c..4275380 100644 --- a/docs/Unit 1 Exercise 8.md +++ b/docs/Unit 1 Exercise 8.md @@ -50,7 +50,7 @@ We can validate that this is the error by navigating to that location via a Wind 14. Click the **Save**. This should take you back to the Processes screen. #### On the Processes screen -15. The **Job Selection** menu should still be open, click **Job Status Update** and select **Restart**. +15. The **Job Selection** menu should still be open, click **Status Update** and select **Restart**. 16. Close the **Job Selection** menu. 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. diff --git a/docs/Unit 1 Exercise 9-obsolete.md b/docs/Unit 1 Exercise 9-obsolete.md index 98e7976..bc1cd8e 100644 --- a/docs/Unit 1 Exercise 9-obsolete.md +++ b/docs/Unit 1 Exercise 9-obsolete.md @@ -56,11 +56,11 @@ https://SMATraining * You should be able to see all 4 Jobs built for today in the Job List. 9. From the **Job** list, select **Windows Job 1** and **Windows Job 2**. 10. Right-Click one of the Jobs. - * The **Job Status Update** screen will appear on the right. + * The **Status Update** screen will appear on the right. * Notice that not all actions are available. Only the actions that can be performed for both Jobs. 11. Select **Restart on Hold**. * Solution Manager will show a message in the top of the screen confirming the action was processed. -12. Close the **Job Status Update** screen, minimize Google Chrome and go back to **Enterprise Manager**. +12. Close the **Status Update** screen, minimize Google Chrome and go back to **Enterprise Manager**. 13. Open the **List** or **Matrix** view, go to today’s date and check the Jobs under **My First Schedule**. * The status for **Windows Job 1** and **Windows Job 2** should be **On Hold**. 14. Still from **Enterprise Manager**, Right-Click the Jobs and select **Release**. You must perform this action for each Job. diff --git a/docs/Unit 2 Exercise 10.md b/docs/Unit 2 Exercise 10.md index 5514f33..3be06cc 100644 --- a/docs/Unit 2 Exercise 10.md +++ b/docs/Unit 2 Exercise 10.md @@ -59,13 +59,13 @@ The **Forecast** screen should show the **15th and 30th days of each month** as 19. In the **Frequency Manager Wizard**: * 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 **Calendar** drop-down menu, select **Master Holiday**. * In the **A/O/B/N** section, select **On Date**. * Click the **Save** button. 20. In the **Active** column, select the frequency then select **Forecast**. :::tip -The **Forecast** screen should show the **dates selected on the Master Calendar in Exercise 7** as green. +The **Forecast** screen should show the **dates selected on the Master Holiday in Exercise 7** as green. ::: 21. Click the **Back** button to navigate back to the **Studio** workspace. diff --git a/docs/Unit 2 Exercise 4 And 5.md b/docs/Unit 2 Exercise 4 And 5.md index 4e12637..736f3cc 100644 --- a/docs/Unit 2 Exercise 4 And 5.md +++ b/docs/Unit 2 Exercise 4 And 5.md @@ -26,7 +26,8 @@ Start Communication for the ```SUSEVM``` Machine. 2. Select **Enable Full Comm. (Job start Enabled)**. 3. Click **Back**. 4. You should receive a **Not Responding** in the **Status** column. -5. Continue on to **Exercise 5**. +5. Close **Operations** +6. Continue on to **Exercise 5**. :::info Note 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. @@ -42,19 +43,20 @@ View the **Netcom Log** to determine the reason why you are unable to establish #### Viewing the Log -1. Open a **File Explorer** window -2. Navigate to where the logs are stored. In this environment they are stored in the following path: **C:\ProgramData\OpConxps\SAM\Log** -3. Double click on the **SMANetcom.log** file. -4. Scroll to the bottom of the **SMANetcom.log** file and look for this entry in the Log file: +1. In **Library** > **Administration** > **Logs** +2. Click on the **SMANetcom.log** file. +3. Scroll to the bottom of the **SMANetcom.log** file and look for this entry in the Log file: * ```ConnectToMachine() -- Exception happens at machine [SUSEVM]: No connection could be made because the target machine actively refused it. [[:3111]]``` +4. Click **Back** until you get to the main **Library** page. #### Correcting the Communication Error -5. Back in Solution Manager, right click the **SUSEVM** machine -6. Select the **Wrench** icon to edit Machine details. -7. Click the **Change Communication Status** button at the bottom of the screen, select **Disable Communication**. -8. In the **General Settings** tab, change the **Socket Number** to ```3100```. -9. Click the **Save**. +5. In **Library** > **Administration** > **Agents**. +6. Right-click on the **SUSEVM** Unix Agent. +7. Click the **Wrench** icon in the Agent Selection panel to edit the Machine details. +8. Click the **Change Communication Status** button at the bottom of the screen, select **Disable Communication**. +9. In the **General Settings** tab, change the **Socket Number** to ```3100```. +10. Click the **Save**. 11. Click the **Change Communication Status** button, select **Enable Full Comm. (Job Start Enabled)**. 12. Click the **Back** button in the top right-hand corner to return to the **Agents** main screen to verify that the **SUSEVM** machine is now communicating. 13. Close **Operations**. diff --git a/docs/Unit 3 Exercise 1.md b/docs/Unit 3 Exercise 1.md index e774488..cf18cc8 100644 --- a/docs/Unit 3 Exercise 1.md +++ b/docs/Unit 3 Exercise 1.md @@ -36,7 +36,7 @@ You will create a new **Role** and **User Account**, then assign this new user t * In the **Description** field, enter some documentation. * Example: Role to be used during the security exercises. * Click **Save** -8. Click on the **User** section within the **Role Definition** section +8. Click on the **Users** section within the **Role Definition** section 9. Select the check-box for **Student Number1** 10. Click **Save**. 11. Close **Library** @@ -58,7 +58,7 @@ You will create a new **Role** and **User Account**, then assign this new user t :::note * License & Support should show you the version information and links for various SMA and OpCon websites. -* Tags is accessible but if you try to create a new tag you won't be able to do to a lack pf permissions. +* Tags is accessible but if you try to create a new tag you won't be able to do to a lack of permissions. ::: 16. **Logout** of **Student1** and back in as the **SMAUSER** diff --git a/docs/Unit 3 Exercise 11.md b/docs/Unit 3 Exercise 11.md index 858fd1e..32a37ae 100644 --- a/docs/Unit 3 Exercise 11.md +++ b/docs/Unit 3 Exercise 11.md @@ -76,9 +76,10 @@ Validate that all the jobs in **My First Schedule** are in a completed state and 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. +27. Toggle on the **Overwrite Exsisting** switch +28. In the **Schedule List**, select **My First Schedule**. +29. Click the **Build** button. +30. 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 6.md b/docs/Unit 3 Exercise 6.md index 5607e0a..f69cfce 100644 --- a/docs/Unit 3 Exercise 6.md +++ b/docs/Unit 3 Exercise 6.md @@ -2,188 +2,90 @@ sidebar_label: 'Unit 3 Exercise 6' --- -## Exercise 6: Function Privileges +## Exercise 6: Access Codes ### Objective -To grant the Training Role some Function Privileges. +To create an Access Code and assign it to a job. ### Summary -Grant the **Training** role the **Function Privilege** of **Build Daily Schedules**. +Create an **Access Code** called **TrainingAC** and assign the **Access Code** to **WINDOWS JOB 1** in **MY FIRST SCHEDULE**. Log out of Enterprise Manager and log back in as **Student1** and note that the user cannot view **WINDOWS JOB 1** because the **TrainingAC Access Code** has not been assigned to the **Training** role. -Validate that **Student1** should be able to see the jobs in **MY FIRST SCHEDULE** but not all of them. **Student1** should only see the first three Windows jobs in the schedule. This is because the **Training** role only has access to the jobs that the ** TrainingDept** department was assigned to. - -Then attempt to to add a UNIX job to the schedule in Job Master. Finally, attempt to change the job status of existing jobs in the daily schedule. ### Instructions -#### Granting the Function Privilege - -1. In **Library** > **Security** > **Access Management** -2. In the **Role** list, select **Training**. -3. In the **Role Definition** section, select **Activities** -4. Expand **Schedule**. -5. Select the checkbox for **Build Daily Schedules** -6. Click **Save** - -#### Validate Privileges - -7. Click **Logout** -8. In the **Logout** pop-up, click **yes**. -9. From the **Login** screen: +#### Create the Access Code + +1. In **Library** under **Security**, select **Access Codes**. +2. Click **Add**. +3. In the **Access Code** pop-up window: + * In the **Name** field, enter ```TrainingAC```. + * In the **Description** field, enter in some **documentation**. + * Example: This is an Access Code for the Training. + * Click **Save**. +4. Click **Back** in the top right corner. + +#### Assign the Access Code to the Job +5. In **Library** > **Administration**, select **Master Jobs**. +6. Using the filers at the top of the job table, search for and select **Windows Job 1**. +7. Click **Edit**. +8. Click the **Lock** button in the upper right-hand corner. +9. In the **Access Code** drop-down list, select **TrainingAC**. +10. Click the **Save**. +11. Close **Library**. + +#### Validate the Privileges +12. Logout of **Solution Manager**. +13. On the **Login** screen: * In the **Username** field, enter ```Student1```. - * In the **Password** field, enter ```password1```. - * Click **Login**. -10. In **Library** > **Administration**, select **Master Job**. -11. In the **Job** list, what do you see? - -:::note -You should only see 3 Windows Jobs. Why? - -Because the **Training** role associated with the **Student1** user has access only to the jobs assigned to the **TrainingDept**. -::: - -12. Select **Windows Job 1**, what is the User ID associated with this Job? - -:::caution Warning -The field should be empty. This is because in Exercise 3, we granted the **Training** role access to **SMATRAINING\BATCHUSER** and **NOT** to **SMATRAINING\SMAUSER**. - -**DO NOT Change the User ID.** -::: - -#### Attempt to Add a UNIX Job -13. Click **Back** in the upper right corner. -14. Click **Add**. -15. In **Job Type** field, try to select UNIX. + * In the **Password** field, enter ```password1```. +14. Under the **Library** > **Administration** topic, click **Master Jobs**. :::note -* What happens? -* Can you select a UNIX machine? -You can’t add a UNIX Job because the role is not assigned to any UNIX machine. -::: - -16. Close **Library** - -#### Change Job Statuses in Matrix - -17. In the **Operation** section, click **Processes** in the top right corner. -18. In the **Schedule Build** screen: - * In the **Scheduling Dates** section, validate that today is selected for both **From** and **To**. - * In the **Schedule Build** section, select **Released** - * Toggle **Overwrite Existing Schedules** on - * In the **Schedule List** section, select **My First Schedule**. - * Click **Build**. -19. On the **Build*** screen, expand out the date until you can click on the **Schedule Name**. -20. Once in the **Processes** screen, make sure that **My First Schedule** is in the **Schedule** section. -21. In the **Job** section, right click **Windows Job 2** and select **Release**. The job should move to a **Waiting on Dependency** status. -22. Right-Click **Windows Job 2** again and click **Force Start**. - -:::note -* Notice that **Force Start** is not enabled. +* What do you see? * Why? -* Because the **Force-Start Job Departmental Function Privilege** is not granted to this user’s role. +* You should not see **Windows Job 1** because the **Training** role, isn't granted access to the **TrainingAC Access Code**. ::: -23. Right-click **Windows Job 3** and notice that the **Cancel** option is not enabled. - -:::note -* Why? -* Because the **Cancel Jobs Departmental Function Privilege** is not granted to this user’s role. -::: - -24. Right-click **Windows Job 1** and select **Release** to allow the jobs in **My First Schedule** to complete. -25. **Logout** of Solution Manager once **My First Schedule** is complete -26. Log back in by clicking the **Login with Windows** button. +15. Be sure to logout of the **Student1** profile and log back in as **smauser**. ## Enterprise Manager
-:::tip [Walkthrough Video - Unit 3 Exercise 6](../static/videobasic/U3E6.mp4) -::: + -#### Granting the Function Privilege +:::tip [Walkthrough Video - Unit 3 Exercise 7](../static/videobasic/U3E7.mp4) -1. In **Security**, expand **Privileges**, double click on **Function Privileges**. -2. In the **Select Role** drop-down, select **Training**. -3. In the **Revoked** column, select **Build Daily Schedules** and using the green arrow move the privilege to the **Granted** column. -4. Close the **Function Privileges** tab. -5. Open the **Matrix** view and check if **My First Schedule** is completed. If not, cancel any Job that is keeping the Schedule open. -6. Close the **Matrix** view. - -#### Validate Privileges - -7. Click the **Lock** icon in the top left corner to log out of Enterprise Manager. -8. In the **Confirm Logout** window, click **OK**. -9. From the OpCon/xps Login screen: - * In the **Username** field, enter ```Student1```. - * In the **Password** field, enter ```password1```. - * Click **Login**. -10. In **Administration** section, double click **Job Master**. -11. In the **Schedule** drop-down, select **My First Schedule**. -12. In the **Job** Drop-down, what do you see? - -:::note -You should only see 3 Windows Jobs. Why? - -Because the **Training** role associated with the **Student1** user has access only to the jobs assigned to the **TrainingDept**. -::: - -13. Select **Windows Job 1**, what is the User ID associated with this Job? - -:::caution Warning -The field should be empty. This is becuase in Exercise 3, we granted the **Training** role access to **SMATRAINING\BATCHUSER** and **NOT** to **SMATRAINING\SMAUSER**. - -**DO NOT Change the User ID.** -::: - -#### Attempt to Add a UNIX Job -14. Click **Add** in the upper right corner. -15. In **Job Type** field, try to select UNIX. - -:::note -* What happens? -* Can you select a UNIX machine? -You can’t add a UNIX Job because the role is not assigned to any UNIX machine. -::: - -16. Click **Cancel** in the top right corner. -17. Close the **Job Master** tab. - -#### Change Job Statuses in Matrix -** -18. In the **Operation** section, double click **Schedule Build**. -19. In the **Schedule Build** pop-up window: - * In the **Scheudle Selection** section, select **My First Schedule**. - * In the **Scheduling Dates** section, validate that today is selected for both **Start** and **Stop**. - * Check the box for **Overwrite existing schedules**. - * Click **Build**. - * In the **Build Properties** window, select **Released** and ** OK**. - * Close the **Schedule Build** pop-up window -20. In the **Operation** section, double click **Matrix**. -21. In the **Calendar** on the **Matrix** screen, make sure today’s date is selected. -22. In the **Schedule** section, select **My First Schedule**. -23. In the **Job** section, right click **Windows Job 2** and select **Release**. The job should move to a **Waiting on Dependency** status. -24. Right-Click **Windows Job 2** again and click **Force Start**. - -:::note -* Notice that **Force Start** is not enabled. -* Why? -* Because the **Force-Start Job Departmental Function Privilege** is not granted to this user’s role. -::: - -25. Right-click **Windows Job 3** and notice that the **Cancel** option is not enabled. - -:::note -* Why? -* Because the **Cancel Jobs Departmental Function Privilege** is not granted to this user’s role. ::: -26. Right-click **Windows Job 1** and select **Release** to allow the jobs in **My First Schedule** to complete. -28. Click the **Lock** icon to logout of Enterprise Manager. -29. Click **OK** to confirm you are logging out. -30. Leave both the **Username** and the **Password** fields blank. -31. Click **Login**. +1. Under the **Security** topic, Double-Click on **Access Codes**. +2. Click the Add button on the Access Codes toolbar. +3. Type **Training** in the **Name** field. +4. Type **This is an Access code for the Training**. in the Documentation field. +5. Click the Save button on the Access Codes toolbar. +6. Close the Access Codes tab. +7. Be sure you are logged on with your ```SMATRAINING\SMAUSER``` login. +8. Under the **Administration** topic, Double-Click **Job Master**. +9. Select My **First Schedule** from the **Schedule** drop-down list. +10. Select **Windows Job 1** from the **Job** drop-down list. +11. On the **Access Code** drop-down list, select **Training**. +12. **Save** your Job and close the Job Master tab.. +13. Logout from Enterprise Manager. Click the Logout button or select Logout from the Enterprise Manager Menu bar. +14. Click **OK** to confirm you are logging out. +15. From the OpCon/xps Login screen type ```Student1``` in the **Username** field and ```password1``` in the **Password** Field. Click Login. +16. Under the **Administration** topic, Double-Click **Job Master**. +17. Select **My First Schedule** from the **Schedule** drop-down list. +18. Click the Job drop-down list. What do you see? Why? +19. Close the Job Master tab and then logout from Enterprise Manager. Click **OK** to confirm you are logging out. +20. From the OpCon/xps Login screen leave both the **Username** and the **Password** fields blank and click **Login**.
\ No newline at end of file diff --git a/docs/Unit 3 Exercise 7.md b/docs/Unit 3 Exercise 7.md index 8d47c78..c61427d 100644 --- a/docs/Unit 3 Exercise 7.md +++ b/docs/Unit 3 Exercise 7.md @@ -2,90 +2,188 @@ sidebar_label: 'Unit 3 Exercise 7' --- -## Exercise 7: Access Codes +## Exercise 7: Function Privileges ### Objective -To create an Access Code and assign it to a job. +To grant the Training Role some Function Privileges. ### Summary -Create an **Access Code** called **TrainingAC** and assign the **Access Code** to **WINDOWS JOB 1** in **MY FIRST SCHEDULE**. Log out of Enterprise Manager and log back in as **Student1** and note that the user cannot view **WINDOWS JOB 1** because the **TrainingAC Access Code** has not been assigned to the **Training** role. +Grant the **Training** role the **Function Privilege** of **Build Daily Schedules**. +Validate that **Student1** should be able to see the jobs in **MY FIRST SCHEDULE** but not all of them. **Student1** should only see the first three Windows jobs in the schedule. This is because the **Training** role only has access to the jobs that the ** TrainingDept** department was assigned to. + +Then attempt to to add a UNIX job to the schedule in Job Master. Finally, attempt to change the job status of existing jobs in the daily schedule. ### Instructions -#### Create the Access Code - -1. In **Library** under **Security**, select **Access Codes**. -2. Click **Add**. -3. In the **Access Code** pop-up window: - * In the **Name** field, enter ```TrainingAC```. - * In the **Description** field, enter in some **documentation**. - * Example: This is an Access Code for the Training. - * Click **Save**. -4. Click **Back** in the top right corner. - -#### Assign the Access Code to the Job -5. In **Library** > **Administration**, select **Master Jobs**. -6. Using the filers at the top of the job table, search for and select **Windows Job 1**. -7. Click **Edit**. -8. Click the **Lock** button in the upper right-hand corner. -9. In the **Access Code** drop-down list, select **TrainingAC**. -10. Click the **Save**. -11. Close **Library**. - -#### Validate the Privileges -12. Logout of **Solution Manager**. -13. On the **Login** screen: +#### Granting the Function Privilege + +1. In **Library** > **Security** > **Access Management** +2. In the **Role** list, select **Training**. +3. In the **Role Definition** section, select **Activities** +4. Expand **Schedule**. +5. Select the checkbox for **Build Daily Schedules** +6. Click **Save** + +#### Validate Privileges + +7. Click **Logout** +8. In the **Logout** pop-up, click **yes**. +9. From the **Login** screen: * In the **Username** field, enter ```Student1```. - * In the **Password** field, enter ```password1```. -14. Under the **Library** > **Administration** topic, click **Master Jobs**. + * In the **Password** field, enter ```password1```. + * Click **Login**. +10. In **Library** > **Administration**, select **Master Job**. +11. In the **Job** list, what do you see? + +:::note +You should only see 3 Windows Jobs. Why? + +Because the **Training** role associated with the **Student1** user has access only to the jobs assigned to the **TrainingDept**. +::: + +12. Select **Windows Job 1**, what is the User ID associated with this Job? + +:::caution Warning +The field should be empty. This is because in Exercise 3, we granted the **Training** role access to **SMATRAINING\BATCHUSER** and **NOT** to **SMATRAINING\SMAUSER**. + +**DO NOT Change the User ID.** +::: + +#### Attempt to Add a UNIX Job +13. Click **Back** in the upper right corner. +14. Click **Add**. +15. In **Job Type** field, try to select UNIX. :::note -* What do you see? +* What happens? +* Can you select a UNIX machine? +You can’t add a UNIX Job because the role is not assigned to any UNIX machine. +::: + +16. Close **Library** + +#### Change Job Statuses in Matrix + +17. In the **Operation** section, click **Processes** in the top right corner. +18. In the **Schedule Build** screen: + * In the **Scheduling Dates** section, validate that today is selected for both **From** and **To**. + * In the **Schedule Build** section, select **Released** + * Toggle **Overwrite Existing Schedules** on + * In the **Schedule List** section, select **My First Schedule**. + * Click **Build**. +19. On the **Build*** screen, expand out the date until you can click on the **Schedule Name**. +20. Once in the **Processes** screen, make sure that **My First Schedule** is in the **Schedule** section. +21. In the **Job** section, right click **Windows Job 2** and select **Release**. The job should move to a **Waiting on Dependency** status. +22. Right-Click **Windows Job 2** again and click **Force Start**. + +:::note +* Notice that **Force Start** is not enabled. * Why? -* You should not see **Windows Job 1** because the **Training** role, isn't granted access to the **TrainingAC Access Code**. +* Because the **Force-Start Job Departmental Function Privilege** is not granted to this user’s role. ::: -15. Be sure to logout of the **Student1** profile and log back in as **smauser**. +23. Right-click **Windows Job 3** and notice that the **Cancel** option is not enabled. + +:::note +* Why? +* Because the **Cancel Jobs Departmental Function Privilege** is not granted to this user’s role. +::: + +24. Right-click **Windows Job 1** and select **Release** to allow the jobs in **My First Schedule** to complete. +25. **Logout** of Solution Manager once **My First Schedule** is complete +26. Log back in by clicking the **Login with Windows** button. ## Enterprise Manager
- +:::tip [Walkthrough Video - Unit 3 Exercise 6](../static/videobasic/U3E6.mp4) +::: -:::tip [Walkthrough Video - Unit 3 Exercise 7](../static/videobasic/U3E7.mp4) +#### Granting the Function Privilege +1. In **Security**, expand **Privileges**, double click on **Function Privileges**. +2. In the **Select Role** drop-down, select **Training**. +3. In the **Revoked** column, select **Build Daily Schedules** and using the green arrow move the privilege to the **Granted** column. +4. Close the **Function Privileges** tab. +5. Open the **Matrix** view and check if **My First Schedule** is completed. If not, cancel any Job that is keeping the Schedule open. +6. Close the **Matrix** view. + +#### Validate Privileges + +7. Click the **Lock** icon in the top left corner to log out of Enterprise Manager. +8. In the **Confirm Logout** window, click **OK**. +9. From the OpCon/xps Login screen: + * In the **Username** field, enter ```Student1```. + * In the **Password** field, enter ```password1```. + * Click **Login**. +10. In **Administration** section, double click **Job Master**. +11. In the **Schedule** drop-down, select **My First Schedule**. +12. In the **Job** Drop-down, what do you see? + +:::note +You should only see 3 Windows Jobs. Why? + +Because the **Training** role associated with the **Student1** user has access only to the jobs assigned to the **TrainingDept**. +::: + +13. Select **Windows Job 1**, what is the User ID associated with this Job? + +:::caution Warning +The field should be empty. This is becuase in Exercise 3, we granted the **Training** role access to **SMATRAINING\BATCHUSER** and **NOT** to **SMATRAINING\SMAUSER**. + +**DO NOT Change the User ID.** +::: + +#### Attempt to Add a UNIX Job +14. Click **Add** in the upper right corner. +15. In **Job Type** field, try to select UNIX. + +:::note +* What happens? +* Can you select a UNIX machine? +You can’t add a UNIX Job because the role is not assigned to any UNIX machine. +::: + +16. Click **Cancel** in the top right corner. +17. Close the **Job Master** tab. + +#### Change Job Statuses in Matrix +** +18. In the **Operation** section, double click **Schedule Build**. +19. In the **Schedule Build** pop-up window: + * In the **Scheudle Selection** section, select **My First Schedule**. + * In the **Scheduling Dates** section, validate that today is selected for both **Start** and **Stop**. + * Check the box for **Overwrite existing schedules**. + * Click **Build**. + * In the **Build Properties** window, select **Released** and ** OK**. + * Close the **Schedule Build** pop-up window +20. In the **Operation** section, double click **Matrix**. +21. In the **Calendar** on the **Matrix** screen, make sure today’s date is selected. +22. In the **Schedule** section, select **My First Schedule**. +23. In the **Job** section, right click **Windows Job 2** and select **Release**. The job should move to a **Waiting on Dependency** status. +24. Right-Click **Windows Job 2** again and click **Force Start**. + +:::note +* Notice that **Force Start** is not enabled. +* Why? +* Because the **Force-Start Job Departmental Function Privilege** is not granted to this user’s role. +::: + +25. Right-click **Windows Job 3** and notice that the **Cancel** option is not enabled. + +:::note +* Why? +* Because the **Cancel Jobs Departmental Function Privilege** is not granted to this user’s role. ::: -1. Under the **Security** topic, Double-Click on **Access Codes**. -2. Click the Add button on the Access Codes toolbar. -3. Type **Training** in the **Name** field. -4. Type **This is an Access code for the Training**. in the Documentation field. -5. Click the Save button on the Access Codes toolbar. -6. Close the Access Codes tab. -7. Be sure you are logged on with your ```SMATRAINING\SMAUSER``` login. -8. Under the **Administration** topic, Double-Click **Job Master**. -9. Select My **First Schedule** from the **Schedule** drop-down list. -10. Select **Windows Job 1** from the **Job** drop-down list. -11. On the **Access Code** drop-down list, select **Training**. -12. **Save** your Job and close the Job Master tab.. -13. Logout from Enterprise Manager. Click the Logout button or select Logout from the Enterprise Manager Menu bar. -14. Click **OK** to confirm you are logging out. -15. From the OpCon/xps Login screen type ```Student1``` in the **Username** field and ```password1``` in the **Password** Field. Click Login. -16. Under the **Administration** topic, Double-Click **Job Master**. -17. Select **My First Schedule** from the **Schedule** drop-down list. -18. Click the Job drop-down list. What do you see? Why? -19. Close the Job Master tab and then logout from Enterprise Manager. Click **OK** to confirm you are logging out. -20. From the OpCon/xps Login screen leave both the **Username** and the **Password** fields blank and click **Login**. +26. Right-click **Windows Job 1** and select **Release** to allow the jobs in **My First Schedule** to complete. +28. Click the **Lock** icon to logout of Enterprise Manager. +29. Click **OK** to confirm you are logging out. +30. Leave both the **Username** and the **Password** fields blank. +31. Click **Login**.
\ No newline at end of file diff --git a/docs/Unit 4 Exercise 11.md b/docs/Unit 4 Exercise 11.md index 47e8010..fd37f80 100644 --- a/docs/Unit 4 Exercise 11.md +++ b/docs/Unit 4 Exercise 11.md @@ -51,8 +51,8 @@ You are going to create a schedule with two jobs. One job will create the file w * In the **Name** field, enter ```Create File``` * In the **Job Type** drop-down, select **Windows** * In the **Machine Selection** drop-down, select **SMATraining** -* In the **Job Action** drop-down, select **Embedded Script** * In the **User ID** drop-down, select **SMATRAINING\SMAUSER** +* In the **Job Action** drop-down, select **Embedded Script** * In the **Script** drop-down, select **Windows_File_Arrival** * In the **Version** drop-down, select **LATEST (X)** * In the **Runner** drop-down, select **PowerShell** diff --git a/docs/Unit 4 Exercise 2.md b/docs/Unit 4 Exercise 2.md index a7f7e0b..d6622e5 100644 --- a/docs/Unit 4 Exercise 2.md +++ b/docs/Unit 4 Exercise 2.md @@ -67,6 +67,7 @@ Utilizing a **Threshold** called **TrainingThreshold** to prevent a job from run * In the **Job Status** drop down, select **Finish OK**. * In the **Value** field, enter ```0```. * Click **Save**. + * Click **Back**. 19. In **Studio**, select the **Threshold Update Job**. 20. In the side menu, select **Add Threshold Update**. 21. In the **Threshold** pop-up window: diff --git a/docs/Unit 4 Exercise 3.md b/docs/Unit 4 Exercise 3.md index d497a82..b95351c 100644 --- a/docs/Unit 4 Exercise 3.md +++ b/docs/Unit 4 Exercise 3.md @@ -63,7 +63,7 @@ What happened? 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 Definition). -19. In **Processes**, right-Click the Job and select **Restart** in the **Job Status Update**. +19. In **Processes**, right-Click the Job and select **Restart** in the **Status Update**. 20. Wait until the Job finishes **OK**. 21. In **Library** > **Administration**, select **Thresholds**. 22. Select **TrainingThreshold**. diff --git a/docs/Unit 4 Exercise 6.md b/docs/Unit 4 Exercise 6.md index d7806d5..1005530 100644 --- a/docs/Unit 4 Exercise 6.md +++ b/docs/Unit 4 Exercise 6.md @@ -28,7 +28,7 @@ Create a Schedule named **Repeating Schedule**. This schedule will contain 4 con * _Example: This is the Daily Sub-Schedule._ * In the **Schedule Settings** frame, mark the **SubSchedule** checkbox. * Saturday and Sunday are **working days**. -* This sub-schedule doesn't use the **Master Calendar** +* This sub-schedule doesn't use the **Master Holiday Calendar** * Click the **Save** button. 4. Click **Back** @@ -61,7 +61,7 @@ Create a Schedule named **Repeating Schedule**. This schedule will contain 4 con * In the **Documentation** field, enter some documentation * _Example: This is the Primary Schedule for the Repeating SubSchedule example._ * Saturday and Sunday are **NOT working days**. -* This sub-schedule does use the **Master Calendar** +* This sub-schedule does use the **Master Holiday Calendar** * Click the **Save** button. 14. Click **Back**. diff --git a/docs/Unit 4 Exercise 7.md b/docs/Unit 4 Exercise 7.md index 41d0e7e..af4414d 100644 --- a/docs/Unit 4 Exercise 7.md +++ b/docs/Unit 4 Exercise 7.md @@ -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 schedule does use the **Master Calendar** +* This schedule does use the **Master Holiday Calendar** * Click the **Save** button. 8. Close **Studio** diff --git a/docs/Unit 4 Lab B.md b/docs/Unit 4 Lab B.md index b97fbbd..933cc6a 100644 --- a/docs/Unit 4 Lab B.md +++ b/docs/Unit 4 Lab B.md @@ -70,10 +70,10 @@ The **Schedule Instance Property** ```[[SI.FILENAME]]``` will be passed by the * * These are the parameters for the ```$JOB:RESTART``` event: * [[$SCHEDULE DATE]] * [[$SCHEDULE NAME]] - * File Arrival + * FA Incoming * Create a **File Arrival** job called **FA Incoming** * 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"_ + * _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``` * Set **Failure Criteria** so that 0 or 1 will be considered Finish OK diff --git a/i18n/it/docusaurus-plugin-content-docs/current/SM - Job Status.md b/i18n/it/docusaurus-plugin-content-docs/current/SM - Job Status.md index 94bbe36..22d0bc3 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/SM - Job Status.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/SM - Job Status.md @@ -32,7 +32,7 @@ Quando un Job viene selezionato con un clic destro, diverse opzioni sono rese di * Strumenti di configurazione del Job (Job Configuration Tool) * Storia delle esecuzini dei (Job Executions History) * Sintesi del Job (Job Summary) -* Aggiornamento dello stato del Job(Job Status Update) +* Aggiornamento dello stato del Job(Status Update) * Job Output * Diagram diff --git a/i18n/it/docusaurus-plugin-content-docs/current/Unit 1 Exercise 9.md b/i18n/it/docusaurus-plugin-content-docs/current/Unit 1 Exercise 9.md index 3e021d2..7faf68b 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/Unit 1 Exercise 9.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/Unit 1 Exercise 9.md @@ -59,11 +59,11 @@ https://SMATraining * Dovresti essere in grado di vedere tutti e 4 i Job costruiti per oggi nella lista dei Jobs. 9. Dalla lista dei Job selezionare **Windows Job 1** e **Windows Job 2**. 10. Fare clic con il tasto destro del mouse su uno dei Jobs. - * Comparirà sulla destra il riquadro **Job Status Update**. + * Comparirà sulla destra il riquadro **Status Update**. * Notate che non tutte le azioni sono disponibili. Solo le azioni che possono essere eseguite per entrambi i Jobs. 11. Seleziona ```Restart on Hold```. * Solution Manager mostrerà un messaggio nella parte superiore dello schermo che conferma che l'azione è stata elaborata. -12. Chiudere la schermata **Job Status Update** minimizzare Google Chrome e tornare a **Enterprise Manager**. +12. Chiudere la schermata **Status Update** minimizzare Google Chrome e tornare a **Enterprise Manager**. 13. Apreire la vista **List** o **Matrix**, andare alla data di oggi e controllare i Job sotto **My First Schedule**. * Lo stato dei Job **Windows Job 1** and **Windows Job 2** dovrebbero essere ```On Hold```. 14. Sempre dall' **Enterprise Manager**, Fare clic con il tasto destro del mouse sui Job e selezionare ```Release```. È necessario eseguire questa azione per ogni Job. diff --git a/sidebars.js b/sidebars.js index 18de0a3..edef7df 100644 --- a/sidebars.js +++ b/sidebars.js @@ -91,9 +91,9 @@ module.exports = { 'Unit 3 Exercise 4', 'Schedule Privileges', 'Unit 3 Exercise 5', - 'Function Privileges', - 'Unit 3 Exercise 6', 'Access Codes', + 'Unit 3 Exercise 6', + 'Function Privileges', 'Unit 3 Exercise 7', 'Common Role Configurations', 'Unit 3 Lab A', diff --git a/static/imgbasic/AuditHistory.png b/static/imgbasic/AuditHistory.png new file mode 100644 index 0000000..037296c --- /dev/null +++ b/static/imgbasic/AuditHistory.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:241347eb75c43e00173911acdfafc6b37849c79afdb50a097017930544c9386b +size 139115 diff --git a/static/imgbasic/AuditHistory2.png b/static/imgbasic/AuditHistory2.png new file mode 100644 index 0000000..83ce3ad --- /dev/null +++ b/static/imgbasic/AuditHistory2.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39da04f000e0f886349c7f56e0c753573539e3669d43e83e395e5001c1923d01 +size 514942 diff --git a/static/imgbasic/Categories.png b/static/imgbasic/Categories.png new file mode 100644 index 0000000..c447cf9 --- /dev/null +++ b/static/imgbasic/Categories.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e10f16c211feebfde4e49b0cd4f4c2f8ec5a62fdbc07d94baffab1e8545f4789 +size 363837 diff --git a/static/imgbasic/Columns.png b/static/imgbasic/Columns.png new file mode 100644 index 0000000..23adeca --- /dev/null +++ b/static/imgbasic/Columns.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b827b5cc107d9a5439d4d5aa0c6621d3268c6afaeef970f46e994eb7d5545eb +size 199997