abas Software AG

1. Help commands

The help command provides you with an overview of the available commands and their use.

1.1. help

abas-installer help:
Brief overview of the available commands.

1.2. help <command>

abas-installer help <command>:
Information on the use of a certain command.
Example: abas-installer help load-modules

2. Check commands

Using these commands, you can develop your abasfile and check the current status of the system.
They are safe, as they do not cause changes to the system.

2.1. check-configuration

abas-installer check-configuration:
Checking the configuration.

2.2. check-hosts

abas-installer check-hosts:
Checking the requirements and the access to the host.

2.3. check-modules

abas-installer check-modules:
Checking the modules which have already been installed.

2.4. check-module-installations

abas-installer check-module-installations:
Checking the status of the modules which have already been installed.

3. Installation commands

Using these commands, you can perform the installation of the modules.

Always use option -m to refer to your downloaded module codes.
See example in installation guide.

3.1. load-modules

abas-installer load-modules:
Downloading and saving the defined modules.

3.2. generate-access-token

abas-installer generate-access-token:
Generating a temporary access token for registry.abas.sh, which should be used instead of the password.

3.3. prepare-hosts

abas-installer prepare-hosts:
Installing Ruby and Puppet, if they have not yet been installed.
Alternatively, you can install the required versions manually and check if the requirements are met with check-hosts.

3.4. install-modules

abas-installer install-modules:
Installing the defined modules.
Use check-modules to ensure that all modules which are already available are recognized as installed. Otherwise, you may accidentally install undesired software and damage existing installations.

4. Module check commands

abas Installer modules automatically perform checks to check the status of the system and the installation of the modules. However, these commands can also be executed manually.

Always use option -m to refer to your downloaded module codes.
See example in installation guide.

4.1. pre-install

abas-installer run-checks --tag pre-install -i <module-identifier>:
Checking if an installation can be performed successfully.
This command is executed automatically before the installation. If the check fails, the installation is stopped.

4.2. post-install

abas-installer run-checks --tag post-install -i <module-identifier>:
Checking if an installation has been performed successfully.
This command is executed automatically after the installation. If the check fails, the installation of all subsequent modules is stopped.

4.3. runtime

abas-installer run-checks --tag runtime -i <module-identifier>:
Checking if the module is in a functional condition. This means that these checks ensure that the module has been properly installed, configured and started.
This command is not executed automatically.

4.4. run-checks

abas-installer run-checks:
Checking all modules. For every module, you will be prompted to select the test to be performed.soll.

5. Service commands

Modules can define services which allow abas Installer to interact with installed products.

5.1. list-services

abas-installer list-services:
Displaying a list of all services.

5.2. services --status

abas-installer services --status:
Checking the status of all services.

5.3. service <service-name> --status

abas-installer service <service-name> --status:
Checking if a service has been started.

5.4. service <service-name> --start

abas-installer service <service-name> --start:
Starting a service.

5.5. service <service-name> --stop

abas-installer service <service-name> --stop:
Stopping a service.