powered by ASAP

1. General Error Codes

Error Code Exception Description

-1

UNKNOWN_ERROR

Is used for all errors which are not defined by another error code.
Mostly because the error is not yet known to us.

219

COMMON_CORRUPT_ZIP

Occurs in case of a corrupt ZIP.

404

RESOURCE_NOT_FOUND

Occurs when something is about to be fetched but cannot be found.

666

FATAL_ERROR

Can be used to tell the developer that something really evil happened.

667

FILE_ERROR

Error can be used for File specific IO errors.
Examples:
– PAK specific files which can’t be read
– PAK specific files which can’t be written

2. Common Exceptions (1xxx)

Error Code Exception Description

1000

COMMON_SPECIFIC_ERROR

Used in case no error code matches as the error to describe is too specific.
Enrichment of additional specific exception information by using PakException#specificExceptionData.

1001

CONNECTION_TIMEOUT

Occurs whenever a connection times out.

1002

SSL_CERTIFICATE_ERROR

Occurs whenever ssl certificates are missing, not up-to-date, or generally invalid.

3. Repository Exception (6xx)

Whenever something fails due to repositories (repos), the following exception codes should be used.

Error Code Exception Description

601

REPO_WRONG_CREDENTIALS

Occurs when the given credentials do not grant access to a repository.

602

REPO_MALFORMED_LOCATION

occurs when
– Repo location is empty
– Repo location does not conform to URI
– Repo location does not conform to a defined standard (example WEB-URL)

603

REPO_UNSUPPORTED_LOCATION

Occurs when
– Location is forbidden to be read from/ written to
– Given repo location is not actually a repo
– Server is reachable but does not support repos and thus, refuses to serve

604

REPO_UNKNOWN_LOCATION

Occurs when
– Repo is no repo at all
– Location cannot be found

605

REPO_CANNOT_OVERWRITE

Occurs when someone tried to overwrite files on a repo, but the repo does not allow that.

606

REPO_ONLY_ALLOWS_SNAPSHOT

Occurs when someone tried to write a non snapshot version to a repo, but the repo only allows snapshots.

607

REPO_ONLY_ALLOWS_RELEASE

Occurs when someone tried to write a non release version to a repo, but the repo only allows releases.

608

REPO_UNABLE_TO_SERIALIZE_MODEL

Occurs when serializing from a model to file fails.

609

REPO_CANNOT_DELETE

Occurs when deleting from a repo fails.

610

REPO_CANNOT_CREATE_META_FILE

Occurs when meta file could not be created.

611

REPO_CANNOT_CREATE_DIRECTORY

Occurs when a directory cannot be created.

612

REPO_SERVER_ERROR

Occurs when the repository is server based and a 5xx HTTP Code returns.
This error code is taken when the error couldn’t be specified better.

613

REPO_BAD_REQUEST_ERROR

Occurs when the repository is server based and a 4xx HTTP Code returns.
This error code is taken when the error couldn’t be specified better.

4. Engine Exceptions (7xx)

Whenever something fails due to the engine, the following exception codes should be used.

Error Code Exception Description

701

ENGINE_UNRECOVERABLE_NODE_ERROR

Occurs when the command execution fails and no boundary event is set.
Possible causes:
– Fails for missing inputs/ outputs
– Execution method of command throws exception

702

ENGINE_INITIALIZATION_ERROR

Occurs when
– Commands are missing
– Models are missing
– Credentials are missing
– Dataflow Analysis is enabled and fails

703

ENGINE_UNHANDABLE_EXCEPTION

Occurs for errors based on „plain“ Java, e.g. runtime errors, null-pointer, 3rd party framework problems, threading issues.

704

ENGINE_DFA_FAILED

Occurs when the model got DFA errors, e.g. missing mandatory values, missing mappings
→ Engine will stop

705

ENGINE_DFA_ERROR

Occurs when the DFA could not run due to model errors like
– Missing commands
– Mapping to fields of commands which do not exist
– Other Java based (fatal) errors

706

ENGINE_CREDENTIAL_MANAGER_ERROR

Occurs when credentials are missing and the callback „de.asap.pak.core.credentials.api.ICredentialRequestProvider“ could not fetch them as well

5. Command Pool Exceptions (8xx)

Whenever something fails due to the command pools, the following exception codes should be used.

Error Code Exception Description

801

COMMAND_POOL_CANNOT_FETCH_ALL_COMMANDS

Occurs when fetching all commands fails.
Possible causes:
– Missing/ wrong command version

802

COMMAND_POOL_CANNOT_FIND_COMMAND_IN_REPOS

Occurs when a command could not be found within a repository.

803

COMMAND_POOL_CANNOT_PULL_COMMAND

Occurs when pulling a command fails.

804

COMMAND_POOL_COMMAND_CREATION_FAILED

Occurs when creating a command fails.

805

COMMAND_POOL_LOADING_COMMAND_INTERPRETER_FAILED

Occurs in case it was not possible ot load an interpreter.

806

COMMAND_POOL_LOADING_SERVICE_METAS_FAILED

Occurs when the service could not be loaded.

807

COMMAND_POOL_READING_SERVICE_METAS_FAILED

Occurs when the service meta could not be read.
Possible causes:
– Service meta file/folder not found

808

COMMAND_POOL_CLEANUP_CLASSLOADER_CACHE_FAILED

Occurs when the class loader cache cleanup fails.

809

COMMAND_POOL_UNEXPECTED_DOWNLOAD_LOCATION

Occurs in case of an unexpected download location.
Possible causes:
– Wrong file URL

810

COMMAND_POOL_ARTIFACT_PROVIDES_INVALID_SERVICE_DEFINITION

Occurs in case of an invalid service definition.

811

COMMAND_POOL_NO_SUITABLE_SERVICE_FOUND

Occurs when no suitable service is found.

812

COMMAND_POOL_MULTIPLE_SERVICE_CANDIDATES_FOUND

Occurs when several services are found.

813

COMMAND_POOL_SERVICE_TRANSITIVE_CLASS_MISSING

Occurs when a transitive class is missing by e.g. an artifact, dependency or system class loader.

814

COMMAND_POOL_SERVICE_CLASS_CANNOT_BE_INSTANTIATED

Occurs when a service cannot be instantiated.
Possible causes:
– Not found within an artifact or dependency

815

COMMAND_POOL_SERVICE_CLASS_CANNOT_BE_INITIALIZED

Occurs when a service cannot be initialized.

816

COMMAND_POOL_CANNOT_PULL_SERVICE

Occurs when pulling a service fails.

817

COMMAND_POOL_SERVICE_VERSION_PARSING_ERROR

Occurs when parsing a version fails.

818

COMMAND_POOL_ONLY_ONE_SERVICE_PER_COMMAND_ALLOWED

Occurs when several services are registered for a command.

819

COMMAND_POOL_META_DATA_NOT_FOUND

Occurs when a command meta could not be found due to an e.g. missing or deprecated command version.

6. Command Interpreter Exceptions (9xx)

Whenever something fails due to the command interpreter, the following exception codes should be used.

Error Code Exception Description

901

COMMAND_INTERPRETER_CONSTRUCTION_EXCEPTION

Should be raised by an implementing „de.asap.pak.core.commandpool.spi.ICommandInterpreter“, which is not able to create the desired command.
Possible causes:
– Missing mandatory keys
– Command implementation itself could not be found, e.g. fully-qualified name of a Java class was not found

902

COMMAND_INTERPRETER_FETCHING_COMMAND_ FROM_CLASSLOADER_NOT_POSSIBLE

Occurs when fetching a command from the classloader fails.

903

COMMAND_INTERPRETER_CREATE_EXECUTABLE_ NOT_POSSIBLE

Occurs when no executable could be created.

904

COMMAND_INTERPRETER_EXECUTABLE_FILE_ NOT_FOUND_OR_NULL

Occurs when no executable file could be found.
Possible causes:
– Missing or wrong file path

Sonatype Nexus

PAK features connectors and commands for Sonatype Nexus. This means the software can directly interact with Nexus repositories for storing and managing artifacts. Through these connectors, PAK can automate tasks like uploading binaries or retrieving dependencies, ensuring efficient artifact management within Nexus.

Jenkins

PAK has connectors and commands for Jenkins. This allows the software to directly communicate with Jenkins servers, enabling the automation of CI/CD (Continuous Integration/Continuous Deployment) tasks. Through these connectors, PAK can trigger builds, fetch build statuses, or manage job configurations, streamlining the CI/CD processes within Jenkins.

Git Hub

PAK possesses connectors and commands for GitHub. This means the software can interface directly with GitHub repositories, facilitating actions like code pushes, pull requests, or issue tracking. Through these connectors, PAK can automate various GitHub operations, enhancing code collaboration and repository management.

Atlassian Confluence

PAK is equipped with connectors and commands for Atlassian Confluence. This enables the software to directly interact with Confluence spaces and pages. Through these connectors, PAK can automate actions such as creating, updating, or retrieving documentation, ensuring efficient content management and collaboration within Confluence.

Codebeamer

PAK features connectors and commands for Codebeamer. This allows the software to seamlessly integrate with Codebeamer’s ALM (Application Lifecycle Management) platform. Through these connectors, PAK can automate tasks like issue tracking, test management, or requirements tracing, enhancing the coordination and management of software development processes.

JFrog Artifactory

PAK has connectors and commands for JFrog Artifactory. This means the software can directly interface with Artifactory repositories, enabling actions like artifact storage, retrieval, and management. Through these connectors, PAK can automate tasks such as deploying artifacts or managing repository configurations, streamlining the integration and management of binary artifacts within Artifactory.

Amazon Web Services (AWS)

PAK has connectors and commands for Amazon Web Services (AWS). This means the software possesses specialized interfaces to directly interact with AWS services and execute actions on the AWS platform. Through these connectors, PAK can automate AWS-specific commands, such as launching EC2 instances, managing S3 buckets, or configuring Lambda functions. This allows for efficient integration, management, and automation of AWS resources and services directly from PAK.

Atlassian Jira

PAK features integration tools and capabilities for Atlassian Jira. These tools allow for a direct connection to Jira and the execution of specific actions. Using these integration tools, PAK can automate Jira actions such as adding comments or changing ticket priorities, ensuring seamless handling and coordination of Jira processes.

Git

PAK has connectors and commands for Git. This means it has interfaces to directly communicate with Git and execute actions. Through these connectors, the software can automate Git commands such as retrieving changes or creating branches, enabling efficient integration and management of Git tasks.

Generic Human Tasks

PAK offers you a standard set of commands which require creative input from the user. Enables you to start with automating your workflows, that still need abit of human input.

Generic Commands

PAK offers a standard set of commands giving you the first steps to automate your workflows.

Nexus Maven Command Pool

Nexus is an artifact repository manager for storing binaries, libraries, and artifacts, supporting formats like Maven. Maven, a software project management tool, is based on the Project Object Model (POM) and allows developers to consistently define projects and dependencies. Our Command Pool offers commands for interactions between Maven and Nexus, such as artifact uploads or dependency retrieval.

Artifactory Maven Command Pool

Artifactory allows developers to store, retrieve, and manage binary files and artifacts, providing a
central source for all binaries used in a development process. Apache Maven is a software project
management and comprehension tool that enables developers to consistently describe a project and
its dependencies. Our Command Pool offers a collection of commands used to facilitate interactions
between Maven and Artifactory, such as uploading artifacts or retrieving dependencies.

Open API Command Interpreter

The OpenApi Command Interpreter allows you the automatic parsing of commands from an OpenApi defintion. No additional code needs to be written anymore, just add the address to the definition and our framework does the rest!

Kotlin Command Interpreter

The Kotlin Command Interpreter allows you the parsing and execution of commands within a Kotlin environment to automate various tasks or processes.

Bpmn Interpreter

Workflows come in many shapes and forms. The BPMN (Business Process Model and Notation) Interpreter enables the parsing of worklows defined in the BPMN format into the PAK intern model.

Human Task Interpreter

The Human Task Interpreter allows you the parsing and running of commands within a HTML and Javascript environment. Use this to build commands which need the creative input of a workflow user!

Java Command Interpreter

The Java Command Interpreter allows you the parsing and execution of commands within a Java
environment to automate various tasks or processes.

Core

The heart of the PAK-Framework. Contains the means to run workflows with the PAK engine, but also the possibility to enrich the frameworks interfaces with your own implementations and solutions.

RocksDB Persistence

Data that is generated by a workflow run needs to be saved for short or longer terms. Our solution to the Persistence Interface of the PAK-Framework is to use the high-performance, key-value based RocksDB developed by Facebook.

PAK online

PAK Online is a web based application and provides an Open API based REST API. It enables you to upload workflows and run them periodically or on REST demand.

Command Line App

Run tasks and workflows on the console or as part of a CI/CD Pipeline with our Command Line Interface.

Workflow Editor

With our specially developed editor, a wide variety of workflows can be easily modeled in the wide known BPMN process format.

Workflow Executor

The Workflow Executor is the application to run your workflows. It features a multilingual UI and easy managment of your favorite workflows.

Support

We offer a community website where you can exchange ideas and support each other. For our Pro packages we also offer full support via email.