Skip to content

Functions

Jump to bottom
devonfw-core edited this page Aug 20, 2021 · 44 revisions

Functions

The following functions are already implemented:

cobiGenFunctions

i. adaptTemplatesCobiGen

This function is used when you want to adapt CobiGen templates. See CobiGen CLI Documentation

Parameter:

  • You don't need any parameters.

Example:

  • adaptTemplatesCobiGen()
Note:
  1. No background script will run.
  2. The command for execution will be generated by Katacoda runner, so user will have to execute this command manually.
  3. To execute this, devonfw-ide must be installed and also CobiGen must be installed.

ii. cobiGenJava

This function is used for code generation inside Java file i.e. Entity class in Java.

Parameter:

This function consist of two parameters.

  1. First parameter:
    • Required
    • Type- String
    • Description- The path to the Java file you want to generate code for.
  2. Second parameter:
    • Required
    • Type- Array of Integers
    • Description- It is the array of numbers that represent the templates that CobiGen uses to generate code.

Example:

  • cobiGenJava("path/to/java/file/MyEntity.java",[1,3,5,6,8])

Details:

Number Description
1 CRUD logic: Generates the logic layer and implementations for some use cases.
3 CRUD REST services: Generates the service layer with CRUD operations for using in REST services.
5 TO's: Generates the related Transfer Objects.
6 Entity infrastructure: Creates the entity main interface and edits (by a merge) the current entity to extend the newly generated classes.
8 CRUD SpringData Repository: Generates the entity repository (that contains the CRUD operations) in the data access layer.
Note:
  1. User needs to execute this command manually.
  2. You need to add installCobiGen() and adaptTemplatesCobiGen() functions before adding this function for CobiGen installation and adapting the Cobigen Templates respectively.
  3. CobiGen CLI is used for execution of these functions. You can find more information related to CobiGen CLI click here.
  4. To execute this function, devonfw-ide must be installed.

iii. installCobiGen

This function is used to install the CobiGen CLI inside devonfw-ide.

Parameter:

  • No parameters required

Example:

  • installCobiGen()
Note:
  1. The command for execution will be generated by Katacoda runner, so user will have to execute this command manually.
  2. To execute this function, devonfw-ide must be installed.

devonfw-ide Functions

i. installDevonfwIde

This function allows you to install devonfw-ide in your environment.

Parameter:

This function consist of two parameter.

  1. First parameter:
    • Required
    • Type- String[] or Array of String
    • Description-The tools you want to install within the devonfw-ide. You can pass every tool that can be installed with the devonfw-ide. In this parameter, the tools you can pass are: java, mvn, node, npm, gradle, ionic jasypt, jenkins, ng, sonar and yarn. You can pass any tool based on your requirement.

Note: You can also pass the IDEs: eclipse, intellij, and vscode. But are not needed in the Katacoda environment and they might create some errors.

  1. Second parameter:
    • Optional
    • Type- devon-ide version
    • Description-It is the version of the ide to install. If you don't use the second parameter, it will always install the newest devonfw-ide release.

Example:

  • installDevonfwIde(["java","mvn"], "2020.08.001")
Note:
  1. You should not use it when you want to show Katacoda user the installation process of the devonfw-ide.
  2. There are scripts that can run in the Katacoda background before first step.

ii. restoreDevonfwIde

It is similar to installDevonfwIde function but the difference between the two functions is that restoreDevonfwIde installs the ide through a script in the background and the Katacoda user will already have an installed version of devonfw-ide at the start of the tutorial.

Parameter:

This function consist of two parameters.

  1. First parameter:

    • Required
    • Type- Array of String.
    • Description- The tools you want to install within the devonfw-ide. You can pass every tool that can be installed with the devonfw-ide. In this parameter, based on requirement the tools you can pass are: java, mvn, node, npm, gradle, ionic jasypt, jenkins, ng, sonar and yarn.

  2. Second parameter:

    • Optional
    • Type- String
    • Description- Devonfw-ide version that will be installed. If this parameter is omitted, it will install the newest devonfw-ide release.

Example:

  • restoreDevonfwIde(["java","mvn"], "2020.08.001")
Note:

  1. In the Katacoda environment the installation of the devonfw-ide is executed in a startup script. Katacoda user don't have to manually execute it.

  2. It should be used when you don't have to show the Katacoda user how to install the devonfw-ide because some other tutorials are predecessors for this tutorial and the user already knows the process.

devon4j Functions

i. createDevon4jProject

This function is used to create a devon4j project.

Parameter:

This function consist of only one parameter

  1. First parameter:
    • Required
    • Type- String
    • Description- The base package name and it is of type string.

Example:

  • createDevon4jProject("com.mycustomer.myapplication")
Note:
  1. This function generates command the Katacoda user has to execute manually.
  2. To execute this function, devonfw-ide must be installed.
  3. This function will always create the devon4j project with latest devon4j version.

ii. buildJava

This function will build your java project.

Parameter:

This function consist two parameter .

  1. First Parameter:
    • Required
    • Type- String
    • Description- The project directory, relative to workspace.
  2. Second Parameter:
    • Optional
    • Type- Boolean
    • Description- Indicator whether tests should be run. Default is false.

Example:

  • buildJava("cobigenexample", true)
Note:
  1. To execute this function, devonfw-ide must be installed.

iii. runServerJava

This function will run your Java application on server.Parameter and assertion information you need to use properly, which is mentioned below.In Katacoda the command will be executed in a new terminal.

Parameter:

This functions consists of two parameters.

  1. First Parameter:
    • Required
    • Type- String
    • Description- Path to the server directory within the Java project.
  2. Second Parameter:
    • Required
    • Type- JSON object
    • Description- This parameter consist of three attributes which are the assertion information. Only needed for the console runner to check if the server was started properly.
      • First attribute: "startupTime" which is the time in seconds to wait before checking if the server is running
      • Second attribute: "port" which is the port number on which the server is running
      • Third attribute: "path" which is the path to the URL path on which is checked if the server is running

Example:

  • runServerJava("devonfw/workspaces/main/jump-the-queue/java/jtqj/server", { "startupTime": 40, "port": 8081, "path": "jumpthequeue" })
Note:
  1. If the tutorial should be tested on the console environment, you have to specify a port.
  2. For this command the devonfw-ide is not necessarily needed but Maven has to be installed. So if someone installs Maven before (e.g. with a setup script), then the command should also work.The command uses the Spring Boot Maven Plugin to run the Java application. So at the moment only Spring applications are supported.

devon4ng Functions

i. createDevon4ngProject

This function is used to create a devon4ng project in workspace.

Parameter:

This function consist of three parameters.

  1. First parameter:
    • Required
    • Type- String
    • Description- It is the name of the project.
  2. Second parameter:
    • Required
    • Type- String
    • Description- It is the path to where the project should be created (relative to workspace). Folder should exist.
  3. Third parameter:
    • Optional
    • Type- Array of String or String[]
    • Description- It contains String array of parameters, according to https://angular.io/cli/new. You can pass argument that can be used in Angular CLI.

Example:

  • createDevon4ngProject("exampleAngularProject", "") Will create the Angular project to the current workspace with the name exampleAngularProject.

  • createDevon4ngProject("exampleAngularProject", "projects", ["--verbose"]) Will create the Angular project to the directory projects within the current workspace and adds more details to output logging.

Note:
  1. No background script will run.
  2. The command for execution will be generated by Katacoda runner, so user will have to execute this command manually.
  3. This command also works if the devonfw-ide is not installed, but then you have to make sure that the Angular CLI is installed.

ii. buildNg

This function is used to build Angular project.

Parameter:

This function consist of two parameter.

  1. First parameter:
    • Required
    • Type- String
    • Description-It is the path to the Angular project, relative to workspace.
  2. Second parameter:
    • optional
    • Type- String
    • Description- It is the custom output directory.

Example:

  • buildNg("exampleAngularProject") Will build the Angular project to default output directory defined in angular.json outputPath key, normally set to dist/.

  • buildNg("exampleAngularProject", "testOutput") Will build the Angular project to output directory testOutput.

Note:
  1. To use only one parameter, you should have Angular CLI installed and the folder should exist. This can be done by using the devonfw-ide or by installing it manually with the npmInstall function.
  2. The command for execution will be generated by Katacoda runner, so user will have to execute this command manually.
  3. No background script will run.

iii. npmInstall

npmInstall is used for installing packages from node package mangager, for example used in Node.js or Angular projects.

Parameter:

This function consist of two parameters.

  1. First parameter:
    • Required
    • Type- String
    • Description- It is the path to the project where the dependencies from the package.json file are to be installed.
  2. Second parameter:
    • Optional
    • Type- JSON object
    • Description- This parameter consists of three attributes. It is the array of JSON-objects which contains name of a package, global or local installation, or array of npm arguments.
      • First attribute: It is optional and it is the name of a package. Example: {"name": string }
      • Second attribute: It is optional and it is for global or local installation. Default is local, therefore false. Example: {"global" : boolean }
      • Third attribute: It is optional and it is the array of npm arguments. Example: {"args": string[]}

Example:

  • npmInstall("jump-the-queue/angular", {"name": "@angular/cli", "global": true, "args": ["--save-dev"]}) will run 'npm install -g --save-dev @angular/cli' in the directory 'jump-the-queue/angular'.

  • npmInstall("my-thai-star/angular") will run 'npm install' in the directory 'my-thai-star/angular'

Note:
  1. Existing project is required to execute this command.
  2. The command for execution will be generated by Katacoda runner, so user will have to execute this command manually.

iv. runClientNg

This function is used to start the server of Angular project.

Parameters:

This function consist of two parameters.

  1. First parameter:
    • Required
    • Type- String
    • Description-Path to the Angular project from which the frontend server is to be started.
  2. Second parameter:
    • optional
    • Type- String
    • Description- This parameter consist of three attributes which are the required assertion information. Only needed for the console runner to check if the server was started properly.
      • First attribute: "startupTime" which is the time in seconds to wait before checking if the server is running
      • Second attribute: "port" which is the port number on which the server is running
      • Third attribute: "path" which is the path to the URL path on which is checked if the server is running

Example:

  • runClientNg("jump-the-queue/angular", { "startupTime": 200, "port": 4200, "path": "" })
Note:
  1. If the tutorial should be tested on the console environment, you have to specify a port.
  2. To execute this, devonfw-ide must be installed and Angular project should be there.
  3. The command for execution will be generated by Katacoda runner, so user will have to execute this command manually.

Docker Functions

i. dockerCompose

This function is used for running Docker Compose. For more information on Docker Compose click here

Parameter:

This function has consist of two parameters.

  1. First parameter:
    • Required
    • Type- String
    • Description- This is the path to the directory where the docker-compose.yml file is located, relative to workspace.
  2. Second parameter:
    • Required
    • Type- JSON Object
    • Description- This parameter consists of three attributes. In this parameter you need to give assertion information. This parameter is only needed for the console runner to check if the server started properly.
      • First attribute: startupTime which is time in seconds to wait before checking if the server is running.
      • Second attribute: Port on which the server is running.
      • Third attribute: The URL path on which is checked if the server is running.

Example:

  • dockerCompose("my-thai-star", { "startupTime": 600, "port": 8081, "path": "" })
Note:
  1. If the tutorial needs to be tested on the console environment, you have to specify a port.
  2. No background script will run.
  3. The command for execution will be generated by Katacoda runner, so user will have to execute this command manually.
  4. Docker must be installed. In the Katacoda environment, Docker is already preinstalled.

File And Directory Functions

i. changeFile

This function is used to insert, append and replace some text in a file.

Parameter:

This function consist of 2 parameters

  1. First parameter:
    • Required
    • Type- String
    • Description- Path of the file to be changed (relative path to the workspace directory)
  2. Second parameter:
    • Required
    • Type- JSON Object
    • Description-This parameter consist of 3 attributes:
      • First attribute: The content that you want to insert into the file or the filepath of a file from where you want to insert the content.
      • Second attribute: It is Optional. Name of a placeholder
      • Third attribute: It is Optional. Line number where you want to insert your code. (Possible lines are: 1...n+1 for N = number of existing lines. File cant be empty)

Example:

  • changeFile("cobigenexample/core/src/main/java/com/example/application/cobigenexample/customermanagement/dataaccess/api/CustomerEntity.java", { "file": "files/Placeholder.java", "placeholder": "private static final long serialVersionUID = 1L;" })

Details:

Path of the file to get the content from or a string, that should be inserted.

  • If you want to add content from a file then use:

    example: {"file": "[path]"}

  • If you want to add a string to a file then use:

    example: {"content": "[string]"}

  • If you want to add different contents for the katacoda and console runner, then use the properties "fileConsole" and "fileKatacoda" or "contentConsole" and "contentKatacoda":

    example: {"fileConsole": "[pathToConsoleFile]", "fileKatacoda": "[pathToKatacodaFile]"}

  • If you want to insert some content at a specific line, then use "lineNumber" and dont use a placeholder:

    example: {"lineNumber": "[Line]"}

example:{...,"placeholder": "private int age;"}

Before Content or File After

private int age;

public String getFirstname() {
return firstname;
}

private int age;

private String company;
public String getCompany() {
return firstname;
}
public void setCompany(String company) {
this.company = company;
}

private int age;

private String company;
public String getCompany() {
return firstname;
}
public void setCompany(String company) {
this.company = company;

public String getFirstname() {
return firstname;
}
Prerequisite:

The usage of the line number function requires having VSCode installed on your System. Not having VSCode installed will not create any output for Katacoda.

Name of the placeholder:

If you want to insert content into your code between two existing lines, take the previous line as your placeholder or use the option to insert at a line number. Add your placeholder into the new file or string, otherwise it will be replaced entirely.

A placeholder is optional. If you do not define a placeholder, the content in the existing file will be simply replaced by the new content.

Please try not to use custom placeholders. Keep in mind that you might want to build the project before changing them. Custom placeholders with a comment-syntax (e.g. "//PLACEHOLDER") will be removed by the console-environment and others might cause errors.

The option to insert at a linenumber uses a placeholder inserted by a script and just adds it at the step you also insert the content.

Note:
  1. The command for execution will be generated by Katacoda runner, so user will have to execute this command manually.
  2. You should not use linenumber and placeholder in the same function.

ii. createFile

This function creates a new file with a specified content. If no content is specified, an empty file is created.

Parameter:

This functions consists of two parameter.

  1. First Parameter:
    • Required
    • Type- String
    • Description- Path of the file to be created (relative path to the workspace directory).
  2. Second Parameter:
    • Optional
    • Type- String
    • Description- Path of the file to get the content from. Relative to the playbook directory.

Example:

  • createFile("cobigenexample/core/src/main/java/com/example/application/cobigenexample/customermanagement/dataaccess/api/CustomerEntity.java", "files/CustomerEntity.java")
Note:

This function will work without a devonfw-ide installation.

iii. createFolder

This function is used to create a new folder.

Parameter:

This function consist of one parameter.

  1. First parameter:
    • Required
    • Type- String
    • Description- Path of the folder to be created (relative to working directory). Subdirectories are also created.

Example:

  • createFolder("directoryPath/subDirectory")
Note:
  1. The command for execution will be generated by Katacoda runner, so user will have to execute this command manually.
  2. It can be used before any command which needs to be executed in such folder which doesn't exist.

iv. downloadFile

This function is used to download a file from an external URL.

Parameter:

This function consist of 3 parameters.

  1. First parameter:
    • Required
    • Type- String
    • Description- URL of the file to be downloaded.
  2. Second Parameter:
    • Required
    • Type- String
    • Description- Name of file
  3. Third parameter:
    • Optional
    • Type- String
    • Description- The path where the file should be stored. It can be used if you want to load the file into a different folder and not into the current Workspace. If folder does not exists, it will be created.

Example:

Note:

The command for execution will be generated by Katacoda runner, so user will have to execute this command manually.

v. openFile

This function is used to open a particular file.

Parameter:

This function consist of one parameter

  1. First parameter:
    • Required
    • Type- String
    • Description- Path of the file to be opened (relative path to the workspace directory).

Example:

  • openFile("cobigenexample/core/src/main/java/com/example/application/cobigenexample/customermanagement/dataaccess/api/CustomerEntity.java")

Katacoda Environment Functions

i. displayContent

This function is only used when you want to display content such as text, image or any file content in your tutorial.

Parameter:

This function consists of two parameters.

  1. First parameter:
    • Required
    • Type- String
    • Description- The title of the step.

Note: The title should never be empty and it is of type string.

  1. Second parameter:
    • Required
    • Type- Array of JSON objects with files, content, or images to be rendered within the Katacoda step.
    • Description-This function consists of three attributes. The use for this function is to display an image and some descriptive text. No Katacoda syntax is allowed in the files or the content!
      • First attribute: "file": Path to a file whose content is to be displayed in the Katacoda step (e.g. .asciidoc or .txt file). The file should be following the formating of asciidoc files.
      • Second attribute: "content": Plain text to be displayed in the Katacoda step. This Text should be following the formating of asciidoc files.
      • Third attribute: "image": Path to an image to be displayed in the Katacoda step. It should be placed under subfolder of the playbook directory.

Example:

  • displayContent("Step title", [{ "file": "files/description.asciidoc" }, { "content": "This is just plain content." }, { "image": "files/image.png" }])

Formatting rules for content and .asciidoc or .txt files.

  • You can add headers to structure your text. The generated headers are shown in the examples below. The headers should fit into the overall structure of the generated wiki so level 1 header are not allowed, but the other header can be used at your judgement.
  • A list always needs an empty newline between the last row and the list.
  • Use asciidoc style of links

Example for content and .asciidoc or .txt files:

Existing header structure
= Level 1: tutorial title
== Level 2: subtitle
=== Level 3: prerequisites and learning goals
== Level 2: steptitle
=== Level 3: titles from functions 
==== Level 4: subtitles from functions
== Level 2: conclusion

List:
This an unordered List (The empty line is necessary)

* First Item
* Second Item

Link:
The tutorials repository can be found https://github.com/devonfw-tutorials/tutorials/issues[here].
Note:
  1. You should avoid using any command inside any text file for which you want to display content. This will cause problems with the console runner and the tests.

Git Functions

i. cloneRepository

This function is used when you want to clone a repository into a particular directory.

Parameter:

This function consist of two parameter.

  1. First parameter:
    • Required
    • Type- String
    • Description- It is path into which the repository is to be cloned, relative to workspace.
  2. Second parameter:
    • Required
    • Type- String
    • Description-It is the Git repository URL.

Example:

Note:
  1. No scripts will run in the background.
  2. The command for execution will be generated by Katacoda runner, so user will have to execute this command manually.

Workspace Functions

i. changeWorkspace

This function is used to change the workspace of the current tutorial.

Parameter:

This function has only one parameter

  1. First parameter:
    • Required
    • Type- String
    • Description- path to a new workspace (relative to working directory)

Example:

  • changeWorkspace("devonfw/workspaces/project") will set the workspace directory to "[working directory]/devonfw/workspaces/project"

Learn more about the workspace directory and working directory on Structure.

Note:
  1. No background scripts are running and Katacoda user don't have to manually execute them.

ii. restoreWorkspace

This function is used to clone an existing GitHub repository to the working directory of the tutorial. It can be used to continue the tutorial with the state of a previous tutorial located in the repository to be cloned.

Parameter:

This function only consist of one parameter.

  1. First parameter:
    • Optional
    • Type- String.
    • Description- Name of the workspace repository(Default is the playbook-name).

Arguments:

  • User - (Optional) - flag: --user - value: GitHub-username (Default is 'devonfw-tutorials')

Note: You can use a forked workspace-repository, if you add the username as argument. If the runner cannot find the workspace repository in the your repositories, it will use devonfw-tutorials instead.

  • Branch - (Optional) - flag: --branch - value: the working branch (Default is its default-branch)

Note: You can use a different branch, if you add the working branch as argument. If the runner cannot find the branch in the cloned repository, it will use the default branch instead.

  • buildRun.sh --user [username] --branch [branch]

Example:

will run "git clone https://github.com/[GitHub-name]/[playbook-name]" and checkout in branch [branch]

details

workspace The default name of the workspace repository is a concatenation of "workspace-" and the name of your playbook-folder. If you want to use another repository as workspace, you can specify the ending with {"workspace": [name]}. example "workspace-devon4ng" -> {"workspace" : "devon4ng"}

local repository You can use a local repository as workspace in the console environment for your tutorial. Clone the forked repository next to the tutorial-compiler folder. Before cloning the GitHub repository, the console runner will always check, if there is a 'workspace-[name]'-folder next to the tutorial compiler first, and will use it instead.

Keep in mind, that it is a feature only implemented in the console environment. Other runners will clone the environment from GitHub.  

|--tutorial-compiler
|--tutorials 
|--workspace-devon4ng

workspace directory

If you call 'restoreDevonfwIde' or 'installDevonfwIde' before the 'restoreWorkspace'-function the workspace directory remains: 

    `'/root/workspaces/main'`

If you don't call them, the workspace is changed to:

    `'/root/workspaces'`

Learn more about the workspace directory and working directory on Structure

Custom Functions

i. addSetupScript

This function is used to add a script which is executed on startup of the tutorial.

Parameter:

This function consist of two parameters

  1. First parameter:
    • Required
    • Type- String
    • Description- Path of the script (Linux). Relative to the playbook directory.
  2. Second parameter:
    • Required
    • Type- String
    • Description- Path of the script (Windows). Relative to the playbook directory.

Example:

  • addSetupScript("assets/createProjectScript.sh", "assets/createProjectScript.ps1")
Note:
  1. For Katacoda, only first parameter is required.
  2. The script will run in the background while starting the tutorial. Katacoda user will have to wait till the script execution is in process. Once it is done it, Katacoda user will get the message and then command prompt will be available to Katacoda user.

ii. executeCommand

This function is used when you want to use a bash (or powershell/cmd on windows) command.

Parameter:

This function consists of four parameters.

  1. First parameter:

    • Required
    • Type- String
    • Description-It contains the input which is a command. The command that will be executed on Windows.

  2. Second parameter:

    • Required
    • Type- String
    • Description-It contains the input which is a command. The command that will be executed on Linux.

  3. Third parameter:

    • Required
    • Type- JSON object
    • Description- This parameter consist of three attribute. It is a JSON object with optional fields
      • First attribute: (Optional) Directory where the command will be executed, if not in current directory (relative to workspace) Example: {"dir": string}
      • Second attribute: (Optional) Synchronous or asynchronous process. Use asynchronous when starting a server. Default is synchronous. Example: {"asynchronous": boolean}
      • Third attribute: (Optional) Array of arguments Example: {"args": string[]}

  4. Fourth parameter:

    • Required
    • Type- JSON object
    • Description- This parameter consist of three attributes which are the assertion information. Assertion information is needed if you start a server to check server availability. Only required when you start a asynchronous server. This parameter is only needed when the command is an asynchronous command.
      • First attribute: "startupTime" which is the time in seconds to wait before checking if the server is running
      • Second attribute: "port" which is the port number on which the server is running
      • Third attribute: "path" which is the path to the URL path on which is checked if the server is running

Commands:

It is needed to pass a command for Windows and also for Linux-based systems because both systems will always be tested.

Assertion information

startupTime = Time in seconds to wait before checking if the server is running port: Port on which the server is running path: The URL path on which is checked if the server is running interval: The availability of the server is checked in the given interval

  • (Required) port: will throw error if no port is given.
  • (Optional) path: subpath which should be pinged, i.e: if localhost:8081/jumpthequeue should be checked path should be "jumpthequeue". DEFAULT: ""
  • (Optional) interval: interval in seconds in which the server should be pinged until it is available or timeouted. DEFAULT: 5 seconds
  • (Optional) startupTime: seconds until a timeout will occur and an error will be thrown. DEFAULT: 10 minutes

Example:

  • executeCommand("node", "node" ,{"args": ["-v"]}) Will create a command for executing node -v .

  • executeCommand("somePollingScript.ps1","bash somePollingScript.sh", {"dir": "data/setup", "args": ["--params 5"]}) Will create a command to execute the script in the directory with the parameter --params 5 and in the current command prompt. The command prompt will be blocked until you stop the script.

  • executeCommand("someServerScript.ps1","bash someServerScript.sh", {"asynchronous": true, "args":["-port 8080"] },{"port":8080 , "startupTime": 20, "path": "some/path/", "interval": 2}) Starting a server in a new terminal. You have to specify the port for testing, the other parameters are optional. The startupTime can specify how long the runner will wait for a response from the server process and with interval you can set the frequenzy for the server testing. The path is the subpath from your server that should be reached.

Clone this wiki locally