Previous Topic: General Template Group ManagementNext Topic: Example


create—Create a Template Group / Software Template

This command creates a new software template.

This command has the following format:

templategroup action=create 
name=template_group_name
[supergroup=group_name]
[swTemplate=software_template_name]
[comment=comment]
[{query="query" | queryfile=file_name }]
[engineName=engine_name
[enginePeriod=engine_evalution_frequence]]
[{transaction
[norollback]|
synchronized }
[cascade[={y|n}]}]
[{setup_jobs | setup&activate_jobs }] 
| [regenerate [ = {y/n}]]
| [{adhoc_only | adhoc_always}] 
[evaluationstart ="YYYY-MM-DD hh:mm"]
[evaluationperiod=hours]
[calendarname=calendar_name]
[globaltime] 
[jcPriority={1,...,10}]
[userMessage]
{adhoc_only | adhoc_always}

The coding has the following effects:

adhoc_only

Adhoc evaluation is enabled only when new or reinstalled targets report their inventory.

adhoc_always

Adhoc evaluation is enabled always when targets report their inventory.

If neither adhoc_only, nor adhoc_always are coded, then no adhoc handling is assumed.

calendarName

Specifies the name of the calendar that controls the time when the evaluation can take place.

Note: To activate a calendarname entry you also have to code "evaluationPeriod".

cascade

If "cascade" or "cascade=y" is coded, the job linkage of the container is switched to resolution of dependencies into install cascades.
If "cascade=n" is coded, the job linkage is switched to no resolution.

This parameter should only be coded, if the job linkage of the container is in batch processing or in synchronized mode, or if it switched into this mode by This action (by coding either "transaction" or "synchronized").

comment

Specifies a comment that is stored with the software template.

engineName

Specifies the name of an engine that will process the group evaluation.

If not coded any engine can process the evaluation.

This parameter is only valid if queryName or sdQuery is coded.

enginePeriod

Specifies in minutes the period in which the engine will re-evaluate the group. If not coded 1 min is assumed.If engineName is coded but not enginePeriod, a default of 1 minute is assumed.

This parameter is only valid if engineName is coded.

evaluationStart

Time, when the evaluation should start. The time should be coded in ISO format "YYYY-MM-DD hh:mm". If no EvaluationStart is coded, the actual time is used.

This parameter is to be used for query or template groups only.

evaluationPeriod

Period in which the query is evaluated. The period is specified in hours.

This parameter is usable for query or template groups only.

If it is omitted or if 0 is coded, no reevaluation is performed.

globalTime

If "globalTime" or "globalTime=y" is coded, then the time specifications are based on the enterprise manager time.

If "globalTime=n" is coded, it is based on domain manager time. (default)

jcPriority

Specifies the priority of the job container.

The priority specified has to be numeric and its value has to be greater or equal 1 and less or equal 10.

If not coded priority 5 is assumed.

name

Specifies the template group name.

If the group does not exist, it is created according to the specified group attributes. If it exists, the specified groups attributes are ignored and the specified software template is created and assigned to this group.

norollback

Specifies that no rollback of previous jobs of the same transaction be performed in case of failure.

query

Indicates that the template is also a query group. The query coded has to be a USD 4.0 SP1 legacy query.

queryfile

Specifies the the file in which the query is stored. The size of the query stored is only limited by the capacity of the server. The query has to be a legal SD 4.0 SP1 legacy query.

The query coded has to be a SD 4.0 SP1 legacy query.

regenerate

If "regenerate" or "regenerate=y" is coded the regeneration of jobs that have failed earlier for this template will be done.

If "regenerate=n" is coded it will not be done.

If the parameter is not coded, "regenerate=y" is assumed.

setup_jobs

According to the conformance check, set up jobs but do not activate.

If neither setup_jobs nor setup&activate_jobs is coded, then only a conformance check is assumed.

setup&activate_jobs

Set up and activate jobs according to the conformance check.

If neither setup_jobs nor setup&activate_jobs is coded, then only a conformance check is assumed.

Notes: If the parameter setup&activate_jobs is used from the command prompt or shell level, the parameter should be enclosed in quotes due to the special meaning of "&" to the command prompt or the shell. If you use batch scripts, you do not need quotes for this parameter.

supergroup

Specifies the name of an existing computer group where the group in question will be created as a subgroup. If not coded the group will be created at the system folder "Computers and Users".

swTemplate

Specifies the name of the software template the order will be assigned to.

If not coded the order will be assigned to a software template of default name, that is, “<group name> [$date $time]”.

synchronized

The job linkage option is set to "Synchronized job execution".

transaction

The job linkage option is set to "Batch job execution".

userMessage

Specifies the custom administrator message for a template group.