Andreas

Hi, thank you for sharing your finding. We added to our change management: JOC-1851: Advanced Search for workflow tags should work when using Oracle A fix will become available from release 2.7.2 and from a patch by end of week. Best regards Andreas

Hi, this is the desired behavior. The "unknown" status is accurate information in this situation. Consider https://kb.sos-berlin.com/display/JS7/JS7+-+System+Architecture#JS7SystemArchitecture-network_connectionsNetworkConnections There is no connection from JOC Cockpit to Agents (unwanted), but from JOC Cockpit to Controller instances that connect to Agents. If the active Controller is gone/inoperable or for the short period (2-3s) of fail-over or switch-over of the Controller, the JOC Cockpit does...

It's great that you made it. You didn't mention the JS7 release that you are using. If you are using JS7 before 2.5.9, 2.6.6, 2.7.0 then you will have had an invalid/expired certificate in the ./trusted_x509-keys directory: JS-2116: Ignore invalid certificates from watched directories Best regards Andreas

It's great that you could resolve the issue. For JOC Cockpit you can simply install a secondary instance (using a different JOC Cockpit ID) - it will automatically become a cluster if both instances are equipped with a license key. The first JOC Cockpit instance started will take the active role. You can switch-over between instances from the Dashboard view. For migrating a Standalone Controller to a cluster see JS7 - How to convert a Standalone Controller to a Controller Cluster

Hi, It is not recommended to access the JS7 database directly as this can result in concurrency issues. The database is not considered an interface. The JOC Cockpit GUI offers the Task History that you can filter for failed jobs and that you can export to an Excel format. The JS7 REST API offers /tasks/history The JS7 - How to create a Task History Report article introduces use of the JS7 PowerShell Module for export of historic data.

I have doubts that the fact that your Controller instances would not couple is related to JOC Cockpit. There is no Base URI in JOC Cockpit. During setup you specify the port of JOC Cockpit which will listen to any network interfaces available on the given host. You can limit use of network interfaces using the jetty.http.host setting in your JETTY_BASE/start.d/http.ini file or jetty.ssl.host setting in ssl.ini if SSL is enabled. However, the hostname in JOC Cockpit's URL is determined by network...

JS7 JobScheduler Maintenance Release 2.7.1 available

Hi, you're lost in curl. It's a Swiss knife and knives can hurt. Sending multipart form-data doesn't mean you can limit yourself to adding the related header. It means that you have to use curl's "form" mode to stream data like this: curl -v -k -L -s -S -X POST -m 15 -F "file=@export.zip" -F "format=ZIP" -F "overwrite=true" -F "targetFolder=/" -H "X-Access-Token: $JS_ACCESS_TOKEN" -H "Accept: */*" http://localhost:4446/joc/api/inventory/import Find attached the related script for import of scheduling...