Knowledge Base > Automation Engine and Target Systems > NSK > Configuration of NSK-specific Parameters

Configuration of NSK-Specific Parameters

The NSK agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host can be used to specify NSK-specific parameters in jobs (e.g. the TACL to be used or the userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. under which the jobAn Automation Engine object type for a process that runs on a target system. reportA report provides more detailed information about a task's execution or a component. should be created).

Specify the parameters in the following format:

== Parameter=Value

The agent searches the scriptA particular Automation Engine object type. for these lines and sets the parameters to the values you specified. TACL handles these lines as comments.

The following parameters are supported:

Parameter

Description

UC4_TACL_PROGRAM

Alternative TACL (Shell)

You can specify a different TACL if the standard TACL loads an environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications. which should not be used for AE jobs. This parameter is also helpful if several clients access a nonstop machine and require different TACL environments.

The agent uses the standard TACL if the specified TACL cannot be used and logs an error message.

UC4_TACL_PROCESSNAME

TACL process name

UC4_REPORT_USERNAME

User under which the job report should be created.

The value "DEFAULT_USER" can also be specified. In this case, the job report is created for the user under which the job runs.

UC4_REPORT_SECURITY

NonStop security string for the job report

Use this parameter carefully. An incorrect security string can have the effect that the agent cannot read or delete the job report.

Examples:

== UC4_TACL_PROGRAM=$SYSTEM.SYS03.TACL
== UC4_TACL_PROCESSNAME=$CAT2
== UC4_REPORT_USERNAME=SQLCMP.SMITH
== UC4_REPORT_SECURITY=NNNN

This is an optional functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,…. The agent uses the particular default values for parameters which have not been set in the script.

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH