71 docs tagged with "System Configuration"

Reference for platform-specific jobdata elements in SMA Dynamic Data Input.

OpCon administration encompasses server setup, component configuration, user security, access control, and database management.

Continuous provides scripts and supplemental SQL stored procedures to aid in managing OpCon: - SMA_CHGMACHINE - SMA_CHG_UNIX_GIDUID - SMA_CLEAN_ENS - SMA_CLEARSCHED - SMA_COPYSCHED - SMA_DELETESCHED.

The OpCon server consists of the Schedule Activity Monitor (SAM) and supporting services (SAM-SS).

The Audit Cleanup utility (Audit.exe) archives and purges audit data.

The basic OpCon Server configuration includes a single machine, a single database, and a StandAlone SMAServMan.

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.

BIRTRptgen.exe calls the BIRTPROCESSOR handler to run reports created with Business Intelligence and Reporting Tools (BIRT).

SMACheckTerm.exe compares the termination description of a completed job to a specific value.

SMAChkStat.exe compares schedule and job statuses in OpCon against a logical expression, then returns a pass or fail exit code.

Learn how to chronoman in OpCon.

OpCon includes the following command-line utilities: - Administrative Stored Procedures - Audit History Cleanup - BIRT Report Generator - Check Job Termination - Check Schedule and Job Status -.

After the SMADDI service has been installed with the SAM and the SMADDI stored procedures have been installed with the database, address the following topics before starting the service: -.

Input files containing dynamic transactions for processing by SMADDI must be in a specific format.

Data Input Message Elements define the XML structure used in SMADDI files, covering both data-storage elements and logical grouping elements.

The Continuous SQL scripts for mirroring the OpCon database use scripting variables defined in SMA_SetDBMirroringScriptingVariables.cmd.

OpCon uses Microsoft SQL Server as its database.

The Continuous SQL scripts for replicating the OpCon database use scripting variables defined in SMA_SetDBReplicationScriptingVariables.cmd.

DoBatch.exe automatically builds, checks, deletes, or forecasts OpCon schedules via command files scheduled as Windows jobs.

Failover and recovery with replication lets OpCon switch to a subscribing database server when the primary becomes unavailable, then restore the original configuration once the primary is back. The procedures cover: - Automatic Failover to the Subscribing OpCon Database Server - Manual Failover to the Subscribing OpCon Database Server -.

Failover in OpCon shuts down the primary SMA Service Manager and starts the secondary, transferring control of the application group to the standby server. OpCon supports both automatic and manual failover, and the configuration depends on whether the database uses mirroring, replication, or a standalone setup.

OpCon includes the following graphical utilities: - Legacy Audit Management - Schedule Import/Export (deprecated) - SMA OpCon Configuration Utility All of these utilities, except SMA Data Collector.

The SAM and supporting services (SAM-SS) are the central components of OpCon.

History.exe archives and purges job history.

The Legacy Audit Management program allows administrators to view audit information, as well as maintain the audit table.

Continuous provides a license file during installation and maintenance to enable SAM.

The SAM and supporting services (SAM-SS) have several important logs.

Automation is the preferred method for database maintenance.

Manual setup for Microsoft SQL Replication configures the publisher, distributor, and subscriber roles needed for OpCon transactional replication.

Regular database maintenance helps maintain good performance across OpCon applications.

The Enterprise Manager Administration supports management of Server Options in OpCon.

In addition to displaying the completion percentage and the interim transfer operations (e.g., compressing, decompressing, etc.), the EM displays specific file transfer codes from the agent's.

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

Optional components in OpCon extend the core server with additional capabilities such as LDAP synchronization, notification handling, and data input processing.

Pingman is a utility that constantly pings a machine to determine network stability.

Privileges in OpCon control what actions each role can perform, covering access codes, batch users, departments, functions, machine groups, machines, schedules, and scripts.

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).

OpCon's RBAC model assigns users to roles, and roles hold specific privileges.

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

Roles maintain privileges for multiple User Accounts simultaneously, simplifying administration.

Before OpCon can submit jobs to an agent, the agent must be connected and configured, and the appropriate batch user credentials must be available.

The Schedule Activity Monitor (SAM) determines when jobs in the Daily tables qualify for submission to an agent and processes OpCon events.

The EM is equipped with a command-line interface for Schedule Extract to support the ability for customers to automate the extract of selected schedules.

Learn how to schedule import/export in OpCon.

Database mirroring increases SQL Server database availability and can be configured in two operating modes: high-performance or high-safety.

Setup for Automatic Microsoft SQL Replication lets OpCon automate the configuration and removal of SQL Server transactional replication.

SMA Dynamic Data Input (SMADDI) is an optional OpCon component that dynamically adds data to OpCon using text files.

SMA Evaluate Expression (SMAEvalExp.exe) accesses the OpCon Property Expressions API — the same API used by Job Dependencies and Events Based on Complex Expressions.

The SMANetCom component is responsible for all communication between the SAM and all agents.

The SMA Notify Handler component is responsible for reading the NOTIFY table in the OpCon database and writing the message to the appropriate location.

The SMA OpCon Configuration Utility configures scripts and configuration files on machines running SMA OpCon software.

The SMA Request Router reads the OpCon database to process requests from the SAM and the Enterprise Manager.

The SMA Resource Monitor for Windows monitors files and Windows counters.

The SMA Resource Monitor service reads the Rule files to determine what to monitor.

The SMA Resource Monitor User Interface includes the following tools: - Copy - Delete - Find - Filter.

The SMA Resource Monitor User Interface provides Wizards within the Add and Edit functions for all monitor types and Action Groups.

SMAServMan manages the SAM-SS application group, handling startup, shutdown, and failover.

The SMA Start Time Calculator periodically recalculates estimated start times for all active jobs in the OpCon Daily tables, then updates the database.

Each input file must contain a <msgtype> element describing the type of SMADDI message.

SMADirectory (SMADirectory.exe) manages OpCon directories, keeping log and report directories from consuming excessive disk space.

The SMAGetServiceStatus utility (SMAGetServiceStatus.exe) monitors the status of Windows services.

Learn how to smaholiday in OpCon.

SMALogEvent writes messages to the Windows event log from a command line.

SMASetRMFileName updates the file name monitored by a specified rule in the SMA Resource Monitor Rules file.

The SMA Resource Monitor User Interface creates and manages File Monitors, Counter Monitors, Service Monitors, Process Monitors, and Action Groups.

Learn how to synch sap in OpCon.

System configuration covers all server-level settings — from initial installation and upgrade procedures through runtime server options (logging, SMTP, SSO, notifications) and database management.

User Accounts are required for authentication to OpCon.

OpCon uses role-based access control (RBAC) to manage what each user can see and do.

OpCon utilities are organized into the following sections: - Command-line Utilities - Graphical Utilities - SMA Dynamic Data Input - SMA Resource Monitor.

Error numbers and descriptions for Microsoft Windows Error Codes (0-499).