Hello. In this article, I would like to introduce the difference between JobUnits and JobNets.
These are two things that you often see when using Hinemos, but if you ask me again, it may be difficult to explain.
The difference between JobUnits and Jobnets is one of the most frequently asked questions on the Customer Portal, which is available to Hinemos subscribers. Let’s take a look at the differences between the two to make your Hinemos experience more pleasant.
Types of Jobs
In Hinemos, jobs can have a hierarchical structure. JobUnits and JobNets are the names of this hierarchy.
A JobUnit is the top-level element of a job hierarchy. All JobNets and command jobs are set as elements of this JobUnit.
When you register a job, you must first create a JobUnit.
A JobNet is an element that can handle all command jobs at once. In addition, JobNets can be handled together with command jobs.
In other words, a JobNet consists of a JobNet and a CommandJob. Multiple Jobnets and Command Jobs can be registered.
The smallest execution unit. It sets the command to be executed on the node.
Difference between JobUnit and JobNet
Now that you understand the difference in hierarchy between JobUnits and JobNets, let’s take a look at the difference between JobUnits and JobNets.
In addition, these two different hierarchies have different “configurable items”. Here is a summary of the items that can be set only in each.
◆Items that can be set only in JobUnit
Job variables are variables that can be set in units of JobUnits, and can be used when specifying commands for jobs in the set JobUnits.
Owner role (configurable in Hinemos 6.2/6.1/6.0/5.0/5.0/4.1)
An owner role can be set for each JobUnit to control who can refer to it.
If a JobUnit is created with the default ALL_USERS role, it will be accessible to all users. By changing the owner role when creating a JobUnit, you can control which users can access it.
Administrative user (configurable in Hinemos 4.0)
An administrative user can be set for each JobUnit to define the users who can be referenced.
When a JobUnit is newly created, all users can refer to it, so to set an administrative user, select one from the users registered in the access management function.
◆Items that can be set only in JobNet
You can specify the waiting conditions (time, end value of the preceding job, end status of the preceding job) for a job.
If the waiting condition is not specified, when a JobUnit or a JobNet including this job is executed, this job will be started regardless of the time, other jobs or JobNets.
Control by the calendar, hold, and skip can be set.
By setting the start delay, you can skip or put on hold the execution status of a job/jobnet when the execution of the job/jobnet is delayed.
The “End Delay” setting allows you to suspend the execution state of a Job or JobNet, or stop the command if the Job or JobNet is running late.
That’s it for the brief introduction to the differences between JobUnits and JobNets.