Skip to main content

Run Actimize Job

NICE Actimize Job Execution: Complete Step-by-Step Guide

Where Jobs Are Executed

Jobs in NICE Actimize are executed in the AIS (Actimize Intelligence Server) layer, NOT in the business applications like IFM. Here's the architecture:

Business Layer (IFM/AML/Trade Surveillance)

AIS (Actimize Intelligence Server) ← JOBS RUN HERE

Database Layer (UDM)

Operating System/Hardware

Method 1: Manual Job Execution via AIS Admin Console

Step-by-Step Process:

Step 1: Access AIS Admin Console

Location: AIS Admin Console (separate from IFM interface)
URL: http://[server]:7001/ais-admin (typical port)
Login: System administrator credentials

Navigation:

  1. Open web browser
  2. Navigate to AIS Admin Console URL
  3. Login with administrative credentials
  4. You'll see the main AIS dashboard

Step 2: Navigate to Job Management

AIS Admin Console → Job Management → Job Control

Menu Path:

  • Main Dashboard → Administration
  • Administration → Job Management
  • Job Management → Job Control or Job Monitor

Step 3: Locate the Job

Job Control → Job List → Filter/Search

Finding Your Job:

  1. Job List View: Shows all available jobs

  2. Filter Options:

    • Job Name (e.g., "Daily_Fraud_Processing")
    • Job Status (Scheduled, Running, Completed, Failed)
    • Job Type (Batch, Real-time, Scenario)
    • Owner/Group
  3. Search: Use search box to find specific job

Step 4: Execute the Job

Select Job → Actions → Run Now

Detailed Steps:

  1. Select the job from the list (checkbox or click)
  2. Right-click or use Actions button
  3. Choose "Run Now" or "Execute Immediately"
  4. Confirm execution in popup dialog
  5. Monitor progress in Job Monitor

Step 5: Monitor Job Execution

Job Monitor → Real-time Status → Logs

Monitoring Features:

  • Status: Running, Completed, Failed, Queued
  • Progress: Percentage complete (if available)
  • Start Time: When job began
  • Estimated Completion: Based on historical data
  • Resource Usage: CPU, Memory utilization
  • Log Output: Real-time log viewing

Real-Life Example: Running Daily Fraud Processing Job

Scenario: Manually run the daily fraud detection job outside of schedule

Step 1: Login to AIS Admin

URL: https://fraud-ais-prod.bank.com:7001/ais-admin
Username: ais_admin
Password: [secure_password]

Step 2: Navigate to Job Control

Dashboard → Administration → Job Management → Job Control

Step 3: Find the Job

Job Filter: Name contains "Daily_Fraud"
Result: "Daily_Fraud_Processing_Job_v2.1"
Status: Scheduled (Next run: 02:00 AM tomorrow)

Step 4: Execute Job

1. Select: ☑ Daily_Fraud_Processing_Job_v2.1
2. Actions → Run Now
3. Confirmation Dialog:
"Are you sure you want to execute this job immediately?
This may impact system performance."
→ Click "Yes, Execute Now"

Step 5: Monitor Execution

Job Monitor shows:
- Status: Running
- Started: 14:23:15
- Progress: Step 2 of 8 (Data Extraction)
- Estimated Completion: 17:45:00
- Current Task: Processing transaction files

Method 2: Command Line Execution

Direct Server Access Method:

Step 1: Connect to AIS Server

# SSH to AIS server
ssh ais_admin@fraud-ais-prod.bank.com

# Navigate to AIS installation directory
cd /opt/actimize/ais

Step 2: Use AIS Command Line Tools

# List available jobs
./ais-cli list-jobs

# Execute specific job
./ais-cli execute-job --job-name "Daily_Fraud_Processing" --wait

# Execute with parameters
./ais-cli execute-job --job-name "Daily_Fraud_Processing" \
--param "PROCESS_DATE=2025-07-16" \
--param "MODE=FULL_PROCESSING"

Step 3: Monitor via Command Line

# Check job status
./ais-cli job-status --job-id 12345

# View job logs
./ais-cli job-logs --job-name "Daily_Fraud_Processing" --tail

# Real-time monitoring
./ais-cli monitor-job --job-id 12345

Example Command Line Session:

[ais_admin@fraud-ais-prod ~]$ cd /opt/actimize/ais
[ais_admin@fraud-ais-prod ais]$ ./ais-cli list-jobs
Available Jobs:
1. Daily_Fraud_Processing
2. Weekly_Model_Refresh
3. Monthly_Customer_Profiling
4. Hourly_Alert_Processing

[ais_admin@fraud-ais-prod ais]$ ./ais-cli execute-job --job-name "Daily_Fraud_Processing"
Job submitted successfully.
Job ID: 98765
Status: Queued

[ais_admin@fraud-ais-prod ais]$ ./ais-cli monitor-job --job-id 98765
Job Status: Running
Current Step: Data Transformation (Step 3 of 8)
Progress: 37%
Start Time: 2025-07-17 14:25:32
Estimated Completion: 2025-07-17 17:42:15

Method 3: Database Direct Execution

For Advanced Users (SQL-based execution):

Step 1: Connect to AIS Database

-- Connect to AIS database
sqlplus ais_user/password@ais_database

Step 2: Insert Job Execution Request

-- Check available jobs
SELECT job_id, job_name, status FROM ais_job_definitions;

-- Queue job for immediate execution
INSERT INTO ais_job_queue (
job_id,
execution_time,
priority,
parameters,
requested_by
) VALUES (
101, -- Daily_Fraud_Processing job_id
SYSDATE, -- Execute now
'HIGH',
'PROCESS_DATE=2025-07-17|MODE=MANUAL',
'manual_execution'
);

COMMIT;

Step 3: Monitor via Database

-- Check execution status
SELECT execution_id, status, start_time, progress_pct, current_step
FROM ais_job_executions
WHERE job_id = 101
ORDER BY start_time DESC;

-- View job logs
SELECT log_timestamp, log_level, message
FROM ais_job_logs
WHERE execution_id = 12345
ORDER BY log_timestamp DESC;

Method 4: Enterprise Scheduler Integration

Control-M Integration (Common in Production):

Step 1: Access Control-M Workbench

Control-M/Enterprise Manager → Workbench → Job Scheduling

Step 2: Find Actimize Jobs

Folder: ACTIMIZE_JOBS
Subfolder: FRAUD_DETECTION
Job: Daily_Fraud_Processing_CTLM

Step 3: Execute Job

Right-click job → Force Job → Confirm

Other Enterprise Schedulers:

Autosys:

# Command line execution
sendevent -E FORCE_STARTJOB -J ACTIMIZE_DAILY_FRAUD

Tivoli Workload Scheduler:

# Submit job for immediate execution
conman "submit sched(ACTIMIZE_DAILY_FRAUD);exec"

Job Execution Troubleshooting

Common Issues and Solutions:

Issue 1: Job Won't Start

Symptoms:

  • Job stays in "Queued" status
  • No error messages visible

Diagnosis Steps:

  1. Check AIS Service Status:

    systemctl status ais-server
  2. Check Resource Availability:

    SELECT * FROM ais_system_resources WHERE resource_type = 'PROCESSING_SLOTS';
  3. Check Dependencies:

    SELECT * FROM ais_job_dependencies WHERE job_id = 101;

Solutions:

  • Restart AIS service if stopped
  • Wait for processing slots to become available
  • Manually complete blocking dependencies

Issue 2: Job Fails Immediately

Symptoms:

  • Job status changes to "Failed" within seconds
  • Minimal processing occurs

Diagnosis Steps:

  1. Check Job Logs:

    AIS Admin → Job Monitor → Select Job → View Logs
  2. Check System Logs:

    tail -f /opt/actimize/ais/logs/ais-server.log
  3. Validate Job Configuration:

    SELECT * FROM ais_job_definitions WHERE job_id = 101;

Common Causes:

  • Missing input files
  • Database connectivity issues
  • Insufficient disk space
  • Configuration errors

Issue 3: Job Runs But Produces No Results

Symptoms:

  • Job completes successfully
  • No alerts or outputs generated

Diagnosis Steps:

  1. Check Data Volume:

    SELECT COUNT(*) FROM staging_transactions WHERE process_date = '2025-07-17';
  2. Verify Scenario Configuration:

    IFM Admin → Scenarios → Active Scenarios
  3. Check Processing Logs:

    AIS Admin → Job Logs → Detail View

Best Practices for Job Execution

1. Pre-Execution Checklist

  • Verify all dependencies are met
  • Check system resource availability
  • Confirm input data is available
  • Review recent execution history
  • Notify stakeholders of manual execution

2. During Execution

  • Monitor progress regularly
  • Watch for error messages
  • Check system performance impact
  • Be prepared to stop if issues arise

3. Post-Execution

  • Verify job completed successfully
  • Check output data quality
  • Review performance metrics
  • Document any issues encountered
  • Notify stakeholders of completion

4. Emergency Procedures

  • Stop Running Job: Use "Kill Job" option in AIS Admin
  • Emergency Contact: Have system admin contact info ready
  • Rollback Plan: Know how to revert changes if needed

Job Execution Permissions

Who Can Execute Jobs:

RolePermissionsInterface Access
AIS AdministratorFull job controlAIS Admin Console, CLI, Database
System OperatorExecute pre-defined jobsAIS Admin Console
Business UserView job status onlyIFM/Application dashboards
Read-Only UserMonitor onlyLimited AIS Admin access

Permission Configuration:

-- Grant job execution permission
INSERT INTO ais_user_permissions (user_id, permission_type, resource_id)
VALUES ('fraud_analyst', 'EXECUTE_JOB', 101);

-- Revoke permission
DELETE FROM ais_user_permissions
WHERE user_id = 'fraud_analyst' AND permission_type = 'EXECUTE_JOB';

Remember: Jobs are executed in AIS, not in the business applications. The business applications (IFM, AML, etc.) consume the results of job execution but don't directly control the execution process.