- Automic Support – general search
Description: Go straight to the specified Automic Support incident.
- Automic Community – discussions search
Description: Search for Automic Community discussion threads containing the specified keyword.
- Automation Engine v12.1 documentation search
Description: Search v12.1 Automic Workload Automation guides for the specified keyword.
- Automation Engine v12.1 messages search
Description: Search v12.1 Automation Engine messages documentation for the specified keyword.
- Automation Engine v12.1 Java API search
Description: Search v12.1 Automation Engine Java API documentation for the specified keyword.
- Automation Engine v11.2 DB schema search
Description: Search v11.2 Automation Engine DB schema documentation for the specified keyword. (The v12.1 DB schema documentation does not appear to be indexed by Google.)
%sis replaced by whatever you type after the keyword.
"character, and is used to ensure that keywords containing spaces or punctuation work more reliably.
- The URLs use Google where native search facilities (hosted on automic.com) do not exist.
If you would like to start using the newly released Rest API for Automic v12.1 or simply test it.. here is what to do:
0- Download Postman
=> It's a Rest API testing tool & is very simple to use
=> you can download it here: https://www.getpostman.com/
=> it is available for Windows, MacOS, Linux and also as a Google Chrome Extension
1- Open Postman and import the 2 files contained in the Postman_Files.zip archive attached to this post
=> One file contains all the Rest call examples for the Automic v12.1 Rest API
=> The other file contains a list of Postman Environment Variables (Port number, URL, etc.)
2- In Postman, click on the "config" wheel and click on "Manage Environments":
3- Adapt the values to your environment (replace aetesthost with the hostname where the engine is installed, replace the client number to your own client, update the Login & Dept, the Password, etc):
4- that's it! now you can go under "_AE_Official" and into either Folders (Search or Executions) and run the actual calls. this will give you working examples to start with. (click on the "Send" button to actually submit a request and see the response from the Automic Engine):
5- Bonus: you can generate code snippets from any of these calls by simply clicking on the "Code" link (right above "Update Request" button). You can pick your scripting or programming language, and Postman will generate a snippet of code for the exact Rest call:
In version 11, some customers may notice that Used(Host) is showing 0 for licenses where they have active agents, when before it used to show the number of licenses used.
This is because in SystemOverview > License, the column Used(Host) will show 0 even though you have active agents for that license IF any of the agent categories has a maximum amount of agents set to 999999.
This is because the Automation Engine will take this as an indication to not count the agents due to performance reasons. This is by design.
Example above, you have 137 licenses (count=137) for EX.OS.WIN.
You have 1 active Windows agent.
If you have any agent in your License that shows 999999, then the Used(host) column will not be computed and will show 0.
Otherwise, Used(Host) will show 1.
Update March 1st 2017
This behavior has been corrected. Starting with the versions below (not yet released), the Used(Host) column will now show the number of licenses used, regardless if there's any agent that's showing 999999.
Below is an example how I connect to two clients (non-verbose & verbose). Then I start a search on client 2000, export the result and import it on client 3000 with a simple Powershell one-liner. The object-path information are kept - missing folder structures are created on destination / existing objects are moved to new location if necessary.
I have several more cmdlets ready that integrate with each other. In example you can do a search on client A and use the search-result to check whether the same objects are deployed on client B. Or pipe it into search-aeStatistic to see when the last run happened.
Also it's a no-brainer to pick the input from a database or file instead of a search-aeObject output.
Did I raise any interest? I'm looking for some serious feedback & people that are interested in testing. I plan to migrate my WorkflowVision (https://marketplace.automic.com/details/workflow-visio) as well as CSV2VARA (https://marketplace.automic.com/details/vara2csv-csv2vara) solutions onto it.
Works with AE10 /11/12 + Powershell v3+.
Btw, sorry for the German text. That's the Windows locale I guess .
- The Windows batch script has been replaced by a PowerShell script.
- There is now one UCDJ binary directory per UCDJ version, instead of one per Automation Engine system.
- The startup script now copies configuration and help stub files to a subdirectory of the user’s home directory, if not already there.
- Log and trace files are now also written to sub-directories of the user’s home directory.
- The JRE version can now be specified as an argument to the startup script.
UC4 User Interface — multiple configurations
InstructionsThis folder contains a set of scripts and files to aid running the Automic ONE Automation Java User Interface (UCDJ) with multiple different configurations. It facilitates running:
- Different versions of UCDJ
- Under different JREs
- With different initial environment variables
- With different XML configuration files (uc4config.xml and login_dat.xml)
- Against different Automation Engine systems (development, test, production)
- With a color-coded environment-specific application icon that matches the color hard-coded in the uc4config.xml file
- Place the contents of this folder in the directory
"C:\UC4\UC4 User Interface".
The shortcuts will not work unless everything is put into this exact location.
- Download and extract the ONE Automation Java User Interface from downloads.automic.com. Place the files in a sub-directory under UCDJ in this directory. The name of the sub-directory should be based on the version of the UI. E.g., if you use version 11.2.2, place the files in UCDJ\v11.2.2\bin.
- Download the Java Runtime Environment (JRE) you wish to use, or more than one if you like. Place the binaries under the Java folder, in a sub-directory named based on the JRE version. E.g, jre1.8.0_102.
- For each Automation Engine system to which you wish to connect, create a copy of the ucdj.jar file, with the system abbreviation in the name. E.g., if have three systems named DEV, TEST, and PROD, create three copies of the ucdj.jar file: ucdj-DEV.jar, ucdj-TEST.jar, and ucdj-PROD.jar.
- Optionally, if you wish to color-code the application icons, replace the application icon uc432.png located in com\UC4\ucdf\images inside each ucdj-XXX.jar file. You can choose one of the icons from the icons sub-directory or use your own icon. It should be a 32x32 pixel PNG file. To replace the icon in the JAR file, rename the .jar file to .zip, open the ZIP file in WinZIP, replace the pertinent icon file, save the ZIP, and then rename it back to .jar.
- For each Automation Enigine system you have created, create a pair of XML configuration files in the config sub-directory. E.g., for the AE system named DEV, create uc4config-DEV.xml and login_dat-DEV.xml. Modify the connection information in each uc4config-XXX.xml file so that it contains only the host name and CP socket details for that particular AE system. If desired, modify the color definitions too.
- Configure the properties of the shortcuts (or create new ones), so that the UC4.vbs script is called with three arguments:
- The name or abbreviation of the AE system
- The version number (folder name under UDCJ where the UI binaries reside)
- The JRE version (folder name under Java where the JRE binaries reside)
- Orange: EXP2
- Yellow: EXP
- Blue: DEV
- Green: ITE (TEST)
- Red: PROD
The UC4.vbs script is simply a wrapper that runs the UC4.ps1 script. The only reason the VBS script is there at all is to prevent a command window from appearing. The UC4.ps1 script copies config and help files to a sub-directory of the user's home directory, and then starts the requested UI in the requested JRE and with the requested configuration. At the top of the PowerShell script, you can set the default JRE version, if desired.
I have attached a ZIP file containing a skeleton of this directory. You must provide the UCDJ & JRE binaries.
- UC4 EXP.lnk
- UC4 EXP2.lnk
- UC4 DEV.lnk
- UC4 ITE.lnk
- UC4 PROD.lnk
- UC4 User Interface instructions.txt
We are very excited to share with you a 50% off registration code* for CA World ‘17!
When you register between now and September 22nd, you can not only take advantage of the Early Bird Rate, but you will also be able to apply this 50% off registration code, bringing your total registration price down to just $647.50.
We look forward to seeing you in Las Vegas!
*Please see full code details below:
· 50% off current registration fee
· Does not include training/certifications
· Is not valid for $195 government rate
· Code is not retro-active
· Code must be entered upon registration to receive discount
· Code valid until November 11, 2017
It works in Java UI and in ECC/AWI with AE11.2 and AE12
Just run SCRI.MASTERMIND
The Automation Engine is not a real time engine. All time based actions are triggered by a so called “Timer” transaction. This transaction is executed every 20 seconds. (In realty it is a little more complex, however knowing this is sufficient to understand the behavior explained below.)
A UNIX job executing the os command “sleep 30” will have a runtime of approximately 30 seconds:
Using maximum runtime – MRT – of 15 seconds, else cancel, should abort the job:
However it may happen, that the job is not canceled:
Let’s think about 2 scenarios:
Timer take place 5 seconds after job start – MRT still ok.
Next Timer will be 25 seconds (= 5 + 20) after jobs start. Job is still active and will be canceled, because MRT is violated.
Timer take place 12 seconds after job start – MRT still ok.
Next Timer will be 32 seconds (= 12 + 20) after jobs start. Job has finished in the meantime (2 seconds before), so it cannot be canceled, even MRT is violated.
Note: In addition the timing mid also be influenced by the current load of the system.
Knowing this it is understandable, that maximum runtime setting below 1 minute do not make sense.