Custom Solutions
General
b4A Custom Solutions are based on an internal best4Automic interface that enables extensions to be written for best4Automic using the Groovy scripting language. Such solutions are also technically referred to as b4A Groovy Distributions. They can therefore be used to carry out special implementations tailored directly to the customer or to support migration and analysis projects with automated steps in order to save time and resources.
The b4A Custom Solutions are delivered in the form of a ZIP archive, which must be unpacked in the scripts subdirectory (must be created if necessary). Alternatively, the archive can be unpacked in any directory and a symbolic link can be created in the scripts subdirectory.
The ZIP archive contains the following folder structure:
- scripts
- contains the Groovy source code of the extension
- conf
- contains the configuration files of the extension
- doc
- contains the documentation for the extension
To call the function of the b4A Custom Solution, the name of the directory or the symbolic link below the subdirectory scripts is required. The name is then specified in the following command:
./b4A --custom-solution <name> [<options> ...]
Installation
- Unpack the ZIP archive b4a-
<solution>
-<version>
.zip into any directory. - Change to the base directory of the b4A installation and from there to the scripts subdirectory.
- Create a symbolic link to the path where the b4A Custom Solution was unpacked
Solutions
Public Solutions
Public Solutions can be requested and used by customers of the best4Automic Solution. Depending on the function of the solution, a specific bundle may be required. These solutions are not included in the standard support for the product.
- Migrate b4A Actions
- Migration of b4A actions and b4A data stream variables from PCK.BEST4AUTOMIC_BASE to B4A.BASE
- Migrate Schedule Variables
- Migration of the static variables for schedule definitions to the new format in XML variables
Customer Solutions
Here is a list of examples of b4A Custom Solutions that have already been implemented for customers.
- Activate
- Mass activation of an object with different parameterization via PromptSet parameters based on a CSV file
- AD Sync
- A separate implementation for the synchronization of user accounts and groups, which follows different rules than the Automic Automation component
- Agent Installation
- Authorizes new agents, authorizes them for defined clients, creates an associated login object and executes an automated test.
- Agent Decommission
- Shuts down agents and deletes the associated object. A report on the process is then sent by e-mail
- Create SAP Job
- Mass creation of SAP jobs based on a CSV input file
- Include Analysis
- Creates a dependency tree for include objects and saves them in DOT language format
- Move
- Mass moving of objects based on a CSV input file
- Replace Login Queue
- Replace LOGIN and QUEUE objects in attributes and scripts of many object types based on mapping definitions
- Edit SAP Connections
- Creates or edits SAP Connection objects
- Report Package Modifications
- Checks in the development client which changes have been made to a package since the last release build. The version management of the Automation Engine is required for this.
- Create FTP Connection
- Creates an FTP connection object and sets the attributes. A report on the process is then sent by e-mail
- Workflow Task Delete
- Deletes tasks from workflows in a folder whose name corresponds to a regular expression. All workflow types are supported for this operation.
- Advanced Rename
- Renames objects and also includes uses in scripts and static variables.
- Find Inactive Objects And Tasks
- Searches for inactive objects and, in the case of workflows, also looks at the tasks. The active flag on the object definitions is considered here.
- Advanced Object Content Search
- Searches for a character string in significantly more object attributes than the search in the AWI
- TWS Migration
- Is able to create Automic objects from flat file exports from TWS. Resource and schedule files are supported
- Duplicate Workflow
- Duplicates a workflow including all jobs contained as tasks and the sub-workflows. The objects are renamed according to a defined rule