Orchestration CLI configured for multiple environments in HCL Workload Automation 10.2. To list available contexts and switch to "test", commands? (Select two)
ocli switch test
ocli config contexts
ocli login test
ocli context list
ocli context use test
Explanation: ocli context list displays configured contexts from config.yaml. ocli context use test activates the test environment for subsequent commands.
HCL HWA 10.2 ephemeral agent installation in OpenShift 4.12 fails pod startup: "Cannot create /opt/hcl/twa/TWS_data_dir because parent directory does not exist". DaemonSet uses emptyDir volume. Correct volumeMount configuration?
configMap: name: tws-config with data directory structure
volumeMounts: - mountPath: /opt/hcl/twa/TWS_data_dir name: tws-data emptyDir: {}
hostPath: path: /var/lib/tws-data type: DirectoryOrCreate
persistentVolumeClaim: claimName: tws-ephemeral-pvc
Explanation: Ephemeral agents require emptyDir for TWS_data_dir volatile storage. DaemonSet spec.volumes: - name: tws-data emptyDir: {} and volumeMounts: - mountPath:
/opt/hcl/twa/TWS_data_dir name: tws-data ensures pod creates data directory on startup. Pod restarts lose plan data intentionally.
A scripting team wants to run automated maintenance jobs through the HCL Workload Automation command line without interactive prompts and with minimal exposure of credentials. They plan to use a dedicated technical user and schedule scripts from a secure operations server. How does the command-line client assemble the full set of connection parameters when some values are provided as command options and others are stored locally?
It first reads parameters supplied to the command and then fills any missing ones from the localopts configuration on the same computer
It requires all parameters, including username and password, to be specified on the command line for non-interactive use
It always prioritizes the values found in localopts over any parameters passed on the command line
It ignores local configuration when a technical user is used and relies only on environment variables
Explanation: The HCL Workload Automation command-line client constructs its connection configuration by first checking for values supplied as explicit parameters to the command. For any required parameters still missing, such as hostname, port, or other connection details, the client consults the localopts file or related local properties on the same computer, allowing a mix of command-line and local configuration. This behavior enables scripts to override specific parameters where necessary while relying on centrally maintained defaults, avoiding the need to repeat full connection details in each script.
Scenario: Large-scale tracing required for broker performance issues. What impacts maximum trace levels in HCL Workload Automation 10.2?
Significant disk usage growth in stdlist/logs
Traces only in memory
Requires broker restart to apply
Performance degradation on broker server
Automatic trace disable after timeout
Explanation: Enabling full traces (e.g., tws_all) substantially increases log volume and CPU/memory usage, impacting performance, and typically requires restarting the application server or broker processes for activation.
Scenario: A fault-tolerant agent in HCL Workload Automation 10.2 linked to an MDM with custom CA-signed certificates fails handshake during linkage after MDM certificate replacement. Which steps reset and re-establish trust without full reinstallation? (Select three)
Update localopts with new verify_cn_string matching SAN
Unlink the agent using conman unlink;force
Manually delete TWSClientTrustFile.jks and restart agent
Run AgentCertificateDownloader utility with updated --tdwbhostname and --tdwbport
Relink using conman link with SSL parameters
Explanation: Unlink the agent using conman unlink;force clears existing linkage state. Run AgentCertificateDownloader utility with updated --tdwbhostname and --tdwbport fetches and installs the new server certificate chain automatically.
To restrict access to sensitive workload definitions in the Dynamic Workload Console (DWC) for HCL Workload Automation 10.2, an administrator wants to implement role- based access control (RBAC) limiting users to view and modify only specific job streams in a particular domain. Which advanced settings in the security file must be configured precisely? (Select two)
Use the FOLDER keyword in conjunction with USEROBJ and DOMAIN specifications
Define object access with CPU=* and ACCESS=DISPLAY,MODIFY for restricted folders
Assign SECURITY role with SUBMIT access limited by JOBSTREAMNAME prefix matching
Restrict PLAN access with TIME windows and FROM/TO date specifications
Implement APPLICATION access restrictions tied to engine connection names
Explanation: The FOLDER keyword in conjunction with USEROBJ and DOMAIN specifications allows granular control over access to objects within specific database folders, enabling restriction to particular job streams or domains. Implementing APPLICATION access restrictions tied to engine connection names limits users to specific distributed engines or domains when multiple connections are defined in the DWC, providing targeted access control beyond global roles.
In a high-availability setup with a backup master domain manager, the primary database password is updated. Which components require updates to the connection parameters to avoid plan switch failures? (Select All that Apply)
Primary master domain manager application server datasource
Dynamic Workload Console engine connections
All dynamic agents in the network
Backup master domain manager Windows services
Explanation: Changing the database password requires updating the datasource file on the primary master domain manager and restarting its application server, updating Windows services on the backup master if applicable, and refreshing engine connection parameters in the Dynamic Workload Console to allow monitoring and management. Dynamic agents do not directly connect to the database, so no changes are needed there.
HCL HWA 10.2 planman create fails mid-production cycle with "Symphony size exceeds 2GB limit" during 18000 job stream finalization across 200 workstations. Current Symphony 1.8GB. DWC shows "Plan creation failed". What production cycle extension enables completion?
A. planman extend 72h /FORCE; planman create /CONTINUE
B. Increase filesystem 10GB; planman create /LARGE
conman "stopsymphony"; rm Symphony; planman create
planman resyncplan all; create 24h increments
Explanation: planman extend 72h /FORCE creates breathing room for 2GB Symphony limit; /CONTINUE resumes 18000 stream finalization across 200 workstations without data loss. Symphony stop destroys running production versus filesystem expansion requiring downtime maintaining cycle continuity.
Scenario: Combining DB2 configuration with templates in HCL Workload Automation 10.2, an administrator needs HADR support. Which file is customized from template?
Variable table for connection strings
JobManager.ini for agents
Security file for user grants
localopts for DB2 port
Datasource configuration XML in overrides
Explanation: Datasource templates include placeholders for HADR client reroute parameters; copying to overrides and adding alternate server details enables high-availability database connections for both master and reporting without full reconfiguration.
Scenario: High volume of messages flooding stdlist on MDM in HCL Workload Automation 10.2. To increase message level temporarily for batchman diagnostics and redirect to file, conman commands? (Select two)
console off
showmsg batchman
console level=10;to /tmp/batchman.log
console level=5
optman msglvl=10
Explanation: console level=10;to /tmp/batchman.log elevates verbosity and redirects detailed messages to a log file for analysis. console off terminates redirection after capturing sufficient data.
Scenario: After a plan extension in HCL Workload Automation 10.2, several event rules remain inactive because they were saved as draft during testing. You need to deploy only the finalized non-draft rules without resetting active sequential rule states. Which planman command and options are required? (Select two)
planman deploy -scratch
planman deploy -noreset
planman deploy
planman deploy -reset
planman deploy -force
Explanation: planman deploy selects and deploys all non-draft event rules from the database to agents. planman deploy -noreset ensures ongoing triggered sequential rules maintain their state, avoiding loss of tracked events.
HCL HWA 10.2 Switch Event Processor high availability configuration fails leader election: conman showswitchep shows LEADER_NONE on backup MDM. What command forces SwitchEP quorum?
conman startswitchep @backup-mdm
conman switchep -elect-leader -quorum 2
SwitchEP HA auto-configures
optman mod _SWITCHEP_HA_QUORUM=2; optman mod _SWITCHEP_LEADER_ELECTION=YES
Explanation: HA SwitchEP requires explicit quorum. optman mod _SWITCHEP_HA_QUORUM=2 configures 2-node majority, optman mod
_SWITCHEP_LEADER_ELECTION=YES enables Raft consensus. Primary SwitchEP elected LEADER, backup FOLLOWER synchronizes event processing.
Scenario: Performance issues occur when connecting the Dynamic Workload Console to an HCL Workload Automation for Z engine due to slow response times. Which advanced setting can be adjusted to increase the timeout value?
zConnectionTimeout in localopts
planQueryTimeout in global options
engineReadWriteTimeout in TdwcGlobalSettings.xml
zOSEngineTimeout in TdwcGlobalSettings.xml
conmanTimeout in optman settings
Explanation: The advanced settings file TdwcGlobalSettings.xml includes parameters to customize timeouts for specific engine types, including the read/write timeout for HCL Workload Automation for Z engines. Increasing this value helps in environments with high latency or large data transfers when querying or modifying plan objects.
For managing dynamic scheduling in HCL Workload Automation 10.2, the dynamic workload broker server is embedded in which components? (Select two)
Fault-tolerant agents
Z-centric endpoints
Standalone dynamic agents
Dynamic Domain Manager
Master Domain Manager Liberty profile
Explanation: Master Domain Manager Liberty profile hosts the central broker for dynamic job dispatch. Dynamic Domain Manager provides hierarchical broker support for large-scale dynamic environments.
Scenario: Uninstalling a backup MDM in 10.2 that shares the database with the primary. What must not be done during uninstall?
Drop database tables
Stop processes on backup
Remove TWA_home directory
Unregister from Liberty repo
Delete local properties files
Explanation: The database is shared, so dropping tables would destroy the primary's data. Uninstall removes local files and instance registration but preserves the remote/shared database.
Scenario: Deploying HCL Workload Automation 10.2 server with Docker. Which registry must be accessed for official container images?
Docker Hub public
HCL Entitled Registry (hclcr.io)
AWS ECR public
Red Hat Quay
GitHub Container Registry
Explanation: Container images for deploying with Docker, including server, console, and agents, are hosted in the HCL Entitled Registry (hclcr.io), requiring login with entitled credentials provided by HCL sales representatives.
To configure LDAP authentication using federated repositories in HCL Workload Automation 10.2 Liberty profile for both MDM and DWC, which XML elements in the server.xml must be precisely defined to integrate Microsoft Active Directory while retaining the local file registry as fallback? (Select two)
<basicRegistry id="basic" realm="basicRealm"/>
<feature>ldapRegistry-3.0</feature> and <feature>federatedRegistry-1.0</feature>
<ldapRegistry id="ldap" realm="myRealm" host="ad.host.com" port="389" baseDN="dc=company,dc=com" bindDN="cn=bind,cn=users,dc=company,dc=com" bindPassword="{xor}encoded"/>
<variable name="admin.group.name" value="TWSAdmins"/>
<federatedRepository id="ldapFed" primaryRealm="myRealm"/>
Explanation: <federatedRepository id="ldapFed" primaryRealm="myRealm"/> establishes the federation combining multiple repositories under a single realm. <ldapRegistry id="ldap" realm="myRealm" host="ad.host.com" port="389" baseDN="dc=company,dc=com" bindDN="cn=bind,cn=users,dc=company,dc=com" bindPassword="
{xor}encoded"/> defines the Active Directory connection details, search base, and secure bind credentials for user/group lookups.
An organization uses HCL Workload Automation 10.2 with DB2, and the support team requests switching from the default type 4 JDBC driver to a type 2 JDBC driver for troubleshooting performance issues. The database server and Dynamic Workload Console remain unchanged. The administrator needs to make this change with minimal impact, ensuring that the engine loads the new driver on the next restart. Which configuration update is required to accomplish this?
Update db.driver.path in the engine properties to point to the type 2 JDBC driver libraries provided for DB2
Update db.user to a special performance user required by the type 2 driver
Update db.databaseName in the engine properties to indicate the driver type and keep db.driver.path unchanged
Update db.sslConnection to true so that the engine automatically switches to the type 2 driver
Explanation: In HCL Workload Automation, the db.driver.path property specifies the filesystem path to the JDBC driver libraries that the engine uses to connect to the database. Support may request switching between type 4 and type 2 JDBC drivers for DB2 or Oracle, and this is done by adjusting the db.driver.path to reference the desired driver implementation while keeping the rest of the database connection parameters consistent. Because driver type is not inferred from the database name, user, or SSL flag, updating only db.driver.path ensures that the engine loads the new driver implementation at the next startup without further structural changes to the configuration.
Troubleshooting HCL HWA 10.2 shows batchman trace+audit correlation: TWS_home/trace/batchman.*.trc "Intercom.msg write blocked" timestamp matches auditbox.msg 4200 "conman STOP batchman" bursts. CP=21h18m stalled. What root cause mitigation prevents recurrence?
planman extend /NOCONMAN
localopts enIntercomThrottling=YES;maxConmanBurst=1800/min;auditbox.msg 75M
conman alias throttle; batchman priority
globalopts CONMAN_THROTTLE=1200/min
Explanation: enIntercomThrottling=YES;maxConmanBurst=1800/min rate-limits 4200 STOP commands preventing Intercom.msg blocking and CP=21h18m stalls; auditbox.msg 75M capacity handles burst metadata vs alias lacking enforcement or globalopts missing workstation granularity maintaining production stability during conman storms.
HCL HWA 10.2 configuring authentication with JWT bearer tokens fails validation: "Signature verification failed". DWC server.xml jwtLoginModule configured but public key mismatch. Required jwtLoginModule configuration?
<jwtLoginModule id="jwtAuth" tokenHeader="Authorization" tokenPrefix="Bearer " signatureAlgorithm="RS256" publicKeyAlias="jwks-key"/>
Liberty extracts public key from token header automatically
Download IdP JWKS endpoint to Liberty truststore
JWT signature validation optional for internal tokens
Explanation: Liberty JWT login module validates token signature against keystore alias. server.xml: <jwtLoginModule id="jwtBearer" tokenHeader="Bearer" signatureAlgorithm="RS256" publicKeyAlias="corp-jwt-key" issuer="https://keycloak.corp.com/realms/hwa"/> imports IdP public key via keytool -importcert -alias corp-jwt- key.
Scenario: To monitor all prompts in the plan and reply to critical ones selectively in batch mode conman in HCL Workload Automation 10.2? (Select two)
tellop reply
showprompts @;global
console prompts
listprompts
reply promptselect=@#CRIT_*;answer=yes;noask
Explanation: showprompts @;global lists all outstanding prompts. reply promptselect=@#CRIT_*;answer=yes;noask replies to matched critical prompts without confirmation.
For server installation in HCL Workload Automation 10.2 without root privileges (introduced in recent updates), which components can now be installed by a regular user? (Select All that Apply)
Dynamic Workload Console
Backup master domain manager
Master domain manager
Z-centric agents
Fault-tolerant agents
Explanation: Recent enhancements allow server installations, including master and backup master domain managers as well as fault-tolerant agents, to be performed using a regular user account without requiring root privileges, simplifying deployment in restricted environments.
Scenario: Dynamic agent jobs are not receiving updated variables from the master in HCL Workload Automation 10.2. Which process and communication path should be examined?
Liberty broker to jobman via HTTPS
Monman to event processor
Mailman to jobman via local queue
Batchman to netman
Writer to Symphony
Explanation: Liberty broker to jobman via HTTPS handles direct job dispatch and parameter streaming for dynamic agents without traditional message files.