Recently active topics

This article provides best practices to avoid any conflict between OpCon processes and antivirus or a log scanner.Security on your serverMore than ever, security is a sensitive and critical element in protecting your company infrastructure and data integrity. You probably already have or plan to add another security layer on your server through an antivirus, scanner or even a log collector. The purpose of this article is to provide the best practices that OpCon and your security applications coexist harmoniously without any conflict.OpCon and antivirusOpCon is a critical application as it's handling your automatization and therefore its processes must remain protected from external interference to avoid dysfunction or outage.By default, an antivirus is scanning the whole system, all the folders and the files searching for viruses or malwares. In a scan operation, it happens that the antivirus is holding a critical files for one of OpCon processes or LSAM such as a log file, a tracking

Set API certificate:This article will show you how to set an auto-signed certificate or your own signed certificate to your OpCon Rest. You'll find three scenarios :1. Generate a new self-signed certificate if no certificate found.2. Generate a new self-signed certificate if the existing certificate is expired.3. Set your own signed certificate. 1. No certificate found:In some cases the OpCon API is not reachable because the certificate is not find by the API, in this case you may only have to apply this procedure to allow the API to use it own auto-generated self-signed certificate : 1. Stop the RestAPI service: SMA OpCon RestAPI 2. Open a command prompt as Administrator 3. Navigate to the SAM folder (for installation on the system drive C:\Program Files\OpConxps\SAM) 4. Run the following command SMAOpConRestApi.Controllers.exe -setcertificate (for older version replaceSMAOpConRestApi.Controllers.exe by SMAOpConRestApi.OwinService) 5. Verify the process completed successfully, the log

This article explains how to use the OpCon API and PowerShell to calculate the average runtime of a job based on historical data and update the Max Runtime field accordingly. This is useful for ensuring that job monitoring thresholds are accurate and reflective of actual performance.OverviewThe Max Runtime field in OpCon can be used to trigger alerts when a job exceeds its expected duration. However, this field is not automatically updated by OpCon. By using the OpCon API, you can automate the process of calculating average runtimes and updating this field.Step-by-Step Process1. Retrieve Historical Job DataUse the OpCon API to retrieve job history for a specific job over a defined date range. Example PowerShell code:$startDate = (Get-Date).AddDays(-7).ToString('yyyy-MM-dd')$endDate = (Get-Date).ToString('yyyy-MM-dd')$url = "$baseUrl/jobhistory?startDate=$startDate&endDate=$endDate&jobName=MyJob"$history = Invoke-RestMethod -Uri $url -Headers $headers -Method Get2. Calculate Ave

This article provides practical PowerShell examples for interacting with the OpCon API. These examples are based on real-world use cases discussed in the OpCon community and training sessions.Getting API VersionUse this script to retrieve the current version of the OpCon API. This endpoint does not require authentication.Invoke-RestMethod -Uri "https://<your-server>/api/version" Authenticating and Storing TokensAuthenticate with the OpCon API and store the token for future use. $body = @{    username = "yourUsername"    password = "yourPassword"}$response = Invoke-RestMethod -Uri "https://<your-server>/api/tokens" -Method Post -Body $body -ContentType "application/json"$token = $response.token  Evaluating ExpressionsEvaluate property expressions using the API to test date formats and dependencies.$headers = @{ Authorization = "Token $token" }$body = @{ expression = "DATEADD(DATE(), -1, 'D')" }Invoke-RestMethod -Uri "https://<your-server>/api/expressions/evaluate" -Met