24 docs tagged with "Business Analyst"

OpCon bases all date and time automation on the OpCon server's date and time, providing a consistent reference for all graphical interfaces and agent machines.

OpCon best practices are proven patterns for building reliable, maintainable automation — from documenting thresholds and properties to setting up automated maintenance schedules, configuring alerts, and structuring job dependencies effectively.

This section explains the core building blocks of OpCon automation — the objects, rules, and behaviors that define how work is scheduled, run, and tracked.

Custom reports in OpCon are built using the BIRT (Business Intelligence and Reporting Tools) framework. You can edit the Continuous-supplied BIRT reports or create entirely new ones to meet specific reporting requirements.

Master job definitions can include all possible Job Automation Components.

Embedded Scripts in OpCon lets users centrally manage scripts for distribution to Agents.

The SMA File Transfer (SMAFT) system transfers files across multiple platforms via an OpCon job.

Frequencies are calendar rules that determine which days a job or schedule qualifies to build and run.

OpCon supports running the same schedule multiple times simultaneously using named instances or multi-instance definitions.

Frequencies specify the recurring days on which a schedule or a job should run.

OpCon was designed to use two major sets of tables.

Job Tracking lets OpCon monitor external jobs (user-submitted or program-submitted) that were started outside an OpCon schedule or event.

Named Schedule Instances reduce the maintenance burden on repeatable workflows by allowing a single definition rule to be designated for unlimited use or job runs.

The Null job generates OpCon events and/or sets thresholds without running a job.

OpCon includes Predefined Reports for gathering information on OpCon status.

Reference for file transfer status codes and error messages displayed in OpCon for MCP, OS 2200, UNIX, and Windows platforms. The Origination column identifies whether the error occurred at the FTAgent (Destination) or the FTServer (Source).

Each agent returns different status messages while a job is running and when a job completes.

All OpCon report files are stored in the OpConxps/EnterpriseManagerx64/reports/OPCONXPS_Reports/ folder on the SAM application server.

The Property Expressions API gives you advanced control over job dependencies and events by evaluating expressions that read and write OpCon property values at runtime.

The Property Expressions API syntax may contain strings, numbers, operators, functions, and OpCon properties (e.g., Global, Schedule Instance, Job Instance, and Machine Instance properties).

Reference material for OpCon events, notification configuration, reports, command-line and graphical utilities, error message codes, property expression syntax, best practices, and licensing.

The Reporting Service is a Windows Service that extracts data from the OpCon database, transforms it, and loads it into a dedicated Reporting database. This isolates reporting queries from the operational database and makes the data viewable and downloadable through Solution Manager.

There are several scenarios for automation that benefit from using Machine Groups in OpCon.

Reference table of Microsoft Windows System Error Codes (0–499) for interpreting Windows job exit codes in OpCon.