Difference between revisions of "Create New Job"

From Hornbill
Jump to navigation Jump to search
(9 intermediate revisions by the same user not shown)
Line 16: Line 16:
  
 
==Credentials==
 
==Credentials==
−
Credentials are required for the Jobs to execute within the correct security context for the task completion.  Depending on the Job type, and package used, there will one or more Credentials required to configure.
+
Required to execute jobs with the permissions and rights necessary to complete the task.  Depending on the Job type, and Package used, one or more Credentials may need specifying.
  
 
* Admin Credentials
 
* Admin Credentials
−
*: Used when the package is deployed to the Target Machine and must have administration rights on the Target.
+
*: Used when the Package is deployed to the Target Machine and must have administration rights on the Target.
 
* Run As Credentials
 
* Run As Credentials
 
*: Once deployed, the Package will need to be executed, by default; this will use the security context of that provided by the Admin Credentials.  In some scenarios, this may not suffice as alternative rights may be required.  The Run As Credentials will be used to provide an additional Credential for this purpose.<br>
 
*: Once deployed, the Package will need to be executed, by default; this will use the security context of that provided by the Admin Credentials.  In some scenarios, this may not suffice as alternative rights may be required.  The Run As Credentials will be used to provide an additional Credential for this purpose.<br>
  
−
'''Note:''' The Service Account used for the SIS that facilitates the execution of the Job is employed where no Credentials are specified.  By default the Local System account will not have the correct rights to deploy or execute any package remotely.}}
+
{{infobox|The Service Account used for the SIS that facilitates the execution of the Job is employed where no Credentials are specified.  By default, the Local System account will not have the correct rights to deploy or execute any package remotely.}}
  
 
'''Discovery:'''
 
'''Discovery:'''
Line 29: Line 29:
 
<pre>
 
<pre>
 
Hornbill ITOM <---- Site Integration Server (Local System)
 
Hornbill ITOM <---- Site Integration Server (Local System)
−
|--- Discovery ---- (AD, Browser ...) (Admin Credentials)
+
|--- Discovery ---- (AD, Browser ...) <== [Admin Credentials]
−
         |<---- returning data (http) ----|
+
         |<---- returning data (https) ----|
 
</pre>
 
</pre>
  
Line 38: Line 38:
 
Hornbill ITOM <---- Site Integration Server (Local System)
 
Hornbill ITOM <---- Site Integration Server (Local System)
 
|--- (Deploy And Execute Package) ---> Managed CI
 
|--- (Deploy And Execute Package) ---> Managed CI
−
                            |----> EspSisExec pkg (Admin Credentials)
+
                            |----> EspSisExec pkg <== [Admin Credentials]
−
                        |----> EspSisExecRunAs pkg (Run As Credentials) {Optional}  
+
                        |----> EspSisExecRunAs pkg <== [Run As Credentials {Optional}]
−
        |<-------------------------------------------------------------- returning data (http) ----|
+
                                |<---------------------------------------- returning data (http) ----|
 +
    |<- returning data (https) -|
 
</pre>
 
</pre>
  
−
Credentials are securely stored in Hornbill KeySafe and are always transmitted over secure communications and thus will need creating before configuring any Jobs.  
+
Credentials are securely stored in Hornbill KeySafe and are always transmitted over secure communications and thus will need creating before configuring any Jobs. In some scenarios, depending on the Package, additional Credentials may also be supplied.  Command-line arguments facilitate the passing of Credentials to the packages' at runtime.
−
 
 
−
In some scenarios, depending on the package, additional Credentials may also be supplied.  Command-line arguments facilitate the passing of   Credentials to the packages' runtime.
 
  
 
==Job Types==
 
==Job Types==
Line 51: Line 50:
 
{{Bullet1|[[IT Automation Job]]|Executes a single packaged task, that will execute on one or more computers}}
 
{{Bullet1|[[IT Automation Job]]|Executes a single packaged task, that will execute on one or more computers}}
 
<BR>
 
<BR>
−
=== Creating a Discovery===
 
−
# Select the '''Create New''' button
 
−
# Select '''Discover Job'''
 
−
# Enter Name to identify the Job
 
−
# Select an SIS server:
 
−
#:This can be a single Server or a Group
 
−
# Select the required Protocol
 
−
# Select the required Discovery Mode
 
−
# Enter the relevant Discovery Mode Settings
 
−
# Click Create button
 
−
 
−
[[Category:ITOM]]
 
−
 
−
=== Creating an IT Automation ===
 
−
# Select the '''Create New''' [[File:SelectPackageButton.png|23x22px]] button
 
−
# Select '''IT Automation Job'''
 
−
# Enter Name to identify the Job
 
−
# Select the required Pacakage
 
−
# Select an SIS server:
 
−
#:This can be a single Server or a Group
 
−
# Select the required Protocol
 
−
# Select the required Discovery Mode
 
−
# Enter the relevant Discovery Mode Settings
 
−
# Click Create button
 
−
 
−
[[Category:ITOM]]
 

Revision as of 09:54, 14 August 2021

Home > ITOM > Job Queue > Create New Index

Introduction

From the Job Queue List it is possible to create Ad-Hoc Discovery and IT Automation Jobs. These jobs will be added to the Queue and executed once a registered SIS server downloads the Job from the cloud for processing. Credentials may be required to excute Jobs and will require creation using the Hornbill KeySafe. When creating an IT Automation Job a user must be aware of the Package to use and the relevant configurtaion details. This information can be sourced from the ITOM Package Library.

Related Articles

Credentials

Required to execute jobs with the permissions and rights necessary to complete the task. Depending on the Job type, and Package used, one or more Credentials may need specifying.

  • Admin Credentials
    Used when the Package is deployed to the Target Machine and must have administration rights on the Target.
  • Run As Credentials
    Once deployed, the Package will need to be executed, by default; this will use the security context of that provided by the Admin Credentials. In some scenarios, this may not suffice as alternative rights may be required. The Run As Credentials will be used to provide an additional Credential for this purpose.
Information
The Service Account used for the SIS that facilitates the execution of the Job is employed where no Credentials are specified. By default, the Local System account will not have the correct rights to deploy or execute any package remotely.

Discovery: 

Hornbill ITOM <---- Site Integration Server (Local System)
				|--- Discovery ---- (AD, Browser ...) <== [Admin Credentials]
        |<---- returning data (https) ----|

IT Automation: 

Hornbill ITOM <---- Site Integration Server (Local System)
				|--- (Deploy And Execute Package) ---> Managed CI
						                            |----> EspSisExec pkg <== [Admin Credentials]
								                        |----> EspSisExecRunAs pkg <== [Run As Credentials {Optional}] 
                                |<---------------------------------------- returning data (http) ----|
    |<- returning data (https) -|

Credentials are securely stored in Hornbill KeySafe and are always transmitted over secure communications and thus will need creating before configuring any Jobs. In some scenarios, depending on the Package, additional Credentials may also be supplied. Command-line arguments facilitate the passing of Credentials to the packages' at runtime.

Job Types

Used to discover devices on the network to populate the Inventory
Executes a single packaged task, that will execute on one or more computers


Retrieved from "https://wiki.hornbill.com/index.php?title=Create_New_Job&oldid=27208"