{section}
{column}
h1. Introduction

Petals CLI is a command line client to administrate a set of Petals nodes.
Petals CLI has 4 interaction modes:
* *Interactive Mode:* [in this mode|#Interactive console], the user types in commands directly in the shell.
* *Scripting Mode:* [in this mode|#Execution of a Petals script file], Petals CLI executes a script file that contains Petals CLI commands.
* *Executable Mode:* [in this mode|#Execution of a Petals CLI command directly on the command line], Petals CLI is launched with a command as an argument.
* *Redirection Mode:* [in this mode|#Execution of an inlined Petals script], Petals CLI takes the commands to execute from the standard input.

To work, Petals CLI needs to establish a connection with a Petals node.
The connection is a JMX connection (see the credentials defined in the _topology.xml_ file of Petals).

Petals CLI works with Petals 4 and higher, but may also work with Petals 3 versions.
{column}
{column:width=40%}
{panel:title=Table of contents}{toc}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list}{panel}
{column}
{section}

h1. Use Cases

{gliffy:name=Petals_CLI_Use_Cases|align=center|size=L|version=5}

h1. Usage of Petals CLI

{color:red}Needs to be updated{color}

{code}
usage: Petals JMX Command Line Interface

[-d] [-y] [-h <host>] [-n <port>] [-u <user>] [-p <password>] [-H | -V | [--file ] <filename> | -c <command> <command-args> | -C]

-c,--command <command> Execute a command given on the command line.
-C,--console Enable the mode 'console'.
-d,--debug Print stack trace and debugging informations
--file <filename> Enable the script file execution. If filename is '-', commands are read from the stdin.
-H,--help Print this help message and exit.
-h,--host <host> remote petals ESB host name.
-n,--port <port> port number.
-p,--password <password> password.
-u,--user <user> username.
-V,--version Print the version number and exit.

To get help on a command, use the command 'help' on command-line: petals-cli.sh -c help <command>

Available commands:
- deploy: Deploy and start a JBI artifact in petals container.
- start: Start a JBI artifact or the container.
- stop: Stop a JBI artifact or the container.
- undeploy: Stop and uninstall or undeploy JBI artifacts.
- exit: Exit this shell.
- help: Display this help message or help for a specific command.
- list: List JBI artifacts name and current status.
- registry-sync: Force a registry synchronization
- registry-list: List the entries of the registry.
- version: Print version informations about petals container.
- show: Print informations about a JBI artifact.
- load: Load properties from files.
- print: Print a message.
- pwd: Print the working directory.
- set: Assign a value to the system property named key.

Which evolution would you like on Petals? Share it! http://www.petalslink.com/feedback
{code}

h1. Petals CLI: the Basis

h2. Petals CLI capabilities about script and shell usages

h3. Interactive console

Launching Petals CLI with the following command line starts an interactive console with a prompt where the user can enter commands.
{code}
> ./petals-cli.sh -C

Type 'help' for help.
------------------------------------------------------------------------------
petals-cli>
{code}

On Windows, this command is wrapped by another script: *petals-cli-console.bat*.
On Linux, there is no wrapper script but a shell alias can be created.

h3. Execution of a Petals CLI command directly on the command line

Launching Petals CLI with the following command line executes the command specified on the command line.
{code}
> ./petals-cli.sh -c <command> <command-args>
{code}

h3. Execution of a Petals script file

Launching Petals CLI with the following command line executes the commands from the specified Petals script.
{code}
> ./petals-cli.sh <filename>
> ./petals-cli.sh --file <filename>
{code}

{info}A Petals script is text file containing commands supported by Petals CLI.{info}

h3. Execution of an inlined Petals script

Launching Petals CLI with the following command line executes commands provided through the standard input ("stdin").

{code}
> cat <filename> | ./petals-cli.sh -
> cat <filename> | ./petals-cli.sh --file -
> ./petals-cli.sh - << EOF
<command1> <command1-args>
<command2> <command2-args>
EOF
> ./petals-cli.sh --file - << EOF
<command1> <command1-args>
<command2> <command2-args>
EOF
{code}

h2. Getting help

h3. Getting help on command line options and arguments

The help on command line options and arguments is available through the '_\-H_' option. A text containing options, arguments and available commands is displayed according to the usage defined above.
{code}
> ./petals-cli.sh -H
{code}

h3. Getting help on commands from the command line

The help on a command is available by using the command '_help_'. A usage and a description of the command is displayed:
{code}
> ./petals-cli.sh -c help <command>

usage: <command> <command-arguments>

<command description>

>
{code}
where:
* {{<command>}} is the command for which we want to get help.
* {{<command-arguments>}} is the list of arguments for the command.
* {{<command-description}} is a description of the command.

h3. Getting help on available commands and on a command in interactive mode

The list of available commands is available by using the command '_help_' without argument.
Help about a command is available by using the '_help_' command. Command's usage and description are then displayed.
{code}> ./petals-cli.sh -C

Type 'help' for help.
------------------------------------------------------------------------------
petals-cli> help

Available commands:
deploy Deploy and start a JBI artifact in petals container.
exit Exit this shell.
help Display this help message or help for a specific command.
...

For help on a specific command type:
help <command>

petals-cli> help <command>

usage: <command> <command-arguments>

<command description>

petals-cli>
{code}
where:
* {{<command>}} is the command for which we want to get help.
* {{<command-arguments>}} is the list of arguments for the command.
* {{<command-description}} is a description of the command.

h2. Getting the version of Petals CLI

To get the version of Petals CLI, the version of the JVM running Petals CLI, and its operating system, use the '_\-V_' option:
{code}
> ./petals-cli.sh -V
Petals JMX Command Line Interface 1.1.0-SNAPSHOT
Java(TM) SE Runtime Environment 1.6.0_26-b03
Linux 3.0.0-16-generic-pae
{code}

h2. Return codes of Petals CLI

h3. Return code on successful result

When there is no error about options and arguments on the command line, the return code of Petals CLI is 0.

h3. Return code on error about options or arguments on the command line

When there is an error about options or arguments on the command line, the return code of Petals CLI is 1.

h3. Return code on error about options and arguments of a command

When there is an error about options and arguments of a command, the return code of Petals CLI is 1.

h3. Return code when executing a system command in Petals CLI

When a system command is executed in Petals CLI, the return code is the one of the system command.

h2. Error Management

h3. Options and Arguments parsing

When using the script mode or inlined mode, parsing errors (invalid options and/or arguments) result in an interruption of Petals CLI.
The right return code is then pushed back.

h3. Error management of a command set on the command line

If an error occurs during the execution of a command set on the command line:
* The command is interrupted.
* Petals CLI is interrupted with the return code 2.

h3. Error management of a command in interactive mode

If an error occurs during the execution of a command entered in interactive mode:
* The error message is displayed.
* Petals CLI is not interrupted, the user can enter other commands.

h3. Error management of a command read from stdin or a file

If an error occurs during the execution of a flow of commands:
* The command that has thrown the error is interrupted.
* The return code of the command can be checked using the commands _isParsingErrorReturned_, _isExecutionErrorReturned_, _isNoErrorReturned_, the ternary conditional operator, and the _lastErrorCode_ attribute.
{code}
> ./petals-cli.sh - << EOF
deploy <artifact-url>
isNoErrorReturned ? listartefacts : exit lastErrorCode
EOF
{code}

\\
Note:
* The return values of command {{isParsingErrorReturned}}, {{isExecutionErrorReturned}} and {{isNoErrorReturned}} are reset when invoking another command. Only the error of the last command execution can be checked.
* The attribute {{lastErrorCode}} is an argument of the command {{exit}} to return the return code of the last executed command.

h2. Exit from the Console mode

To exit the console mode, use the '_exit_' command.
If a number is set as an argument, it is used as return code. Otherwise, the 0 is returned.
{code}
> ./petals-cli.sh -C

Type 'help' for help.
------------------------------------------------------------------------------
petals-cli> exit
> echo $?
0
> ./petals-cli.sh -C

Type 'help' for help.
------------------------------------------------------------------------------
petals-cli> exit 1
> echo $?
1
{code}

h2. Petals CLI Preferences

It is possible to define preferences in Petals CLI.
The preferences are defined a properties file, as key/value pairs.
By default, this file is located at _$PETALS_CLI_HOME/conf/preferences.properties_.

However, it is possible to move this file somewhere else thanks to an environement variable.
_$PETALS_CLI_PREFS_ is the variable environement that points to the location of the preferences file.

This file contains the following keys:
* *host*: the host of the default Petals node (required). Initial Value: localhost
* *port*: the JMX port of the default Petals node (required). Initial Value: 7700
* *user*: the JMX user name for the default Petals node (optional). Initial Value: petals
* *password*: the JMX password for the default Petals node (optional). Initial Value: petals
* *lang*: the language to use in Petals CLI (FR/EN for the moment). If the value is unknown, then English is picked up.

When optional keys are not defined, Petals CLI will ask for their values manually (or you will have to use the right options with the commands).
If the file does not exist, or that _$PETALS_CLI_PREFS_ points to an invalid location, Petals CLI will use default settings when possible. Otherwise, it will display an error message.

h1. Connection to a Petals node

h2. Connection options from the command line

All the required parameters for a JMX connection must be configurable on the command line as options:
{code}
> ./petals-cli.sh -h <host> -n <port> -u <user> -p <password> -c <command>
> ./petals-cli.sh -h <host> -n <port> -u <user> -p <password> -C
petals-cli@<host1>:<port1>>
{code}

h2. Interacting with several Petals nodes without exiting Petals CLI

In interactive mode or script mode, we should be able to close a connection and open another one without leaving Petals CLI. This is achieved with the '_connect_' and '_disconnect_' commands. If no argument is set on the '_connect_' command, default values are used. These default values are specified in the preferences file.

{code}
> ./petals-cli.sh -C

Type 'help' for help.
------------------------------------------------------------------------------
petals-cli> connect <user1>:<password1>@<host1>:<port1>
Connected on <host1>:<port1> with '<user1>'
petals-cli> disconnect
petals-cli> connect
petals-cli> Would you like to connect to <default-user>:*****@<default-host>:<default-port>? (y/n)
y
petals-cli@<default-host>:<default-port>>
{code}

h2. Default connection

By default (if no argument or option is set).
In console mode, the connection is established with the values given in the preferences file.
{code}
> ./petals-cli.sh -C

Type 'help' for help.
------------------------------------------------------------------------------
petals-cli> connect
petals-cli> Would you like to connect to <default-user>:*****@<default-host>:<default-port>? (y/n)
y
petals-cli@<default-host>:<default-port>>
{code}

The confirmation can be skipped by adding the '_yes_' argument to the command.
{code}
> ./petals-cli.sh -C

Type 'help' for help.
------------------------------------------------------------------------------
petals-cli> connect -y
petals-cli@<default-host>:<default-port>>
{code}

In command line mode, if no argument or option is set, a connection is established with the values defined in the preferences file.

{code}
> ./petals-cli.sh -c stop
{code}

{tip}This is necessary to easily stop a local container{tip}

In script mode, the connection is established with the values defined in the preferences file.
{code}
> ./petals-cli.sh - << EOF
connect
EOF
{code}

If the preferences file does not exist and that _connect_ was invoked without an argument, the command returns the error code 2.

h2. Security

For security reasons, a Petals CLI user may decide that there should be no default connection.
In that case, he may decide to delete the preference file, so that any user will have to type in the right information.
If the preference (properties file) does not exist, Petals CLI displays an error message.

{code}
> ./petals-cli.sh -C

Type 'help' for help.
------------------------------------------------------------------------------
petals-cli> connect
No default connection is available. Use 'help connect' for more information.
{code}

\\
Another possibility is that the user allows to record a default host and port but not the credentials.
In that case, Petals CLI will ask the user to type in the credentials.

{code}
> ./petals-cli.sh -C

Type 'help' for help.
------------------------------------------------------------------------------
petals-cli> connect
petals-cli> Would you like to connect to <default-host>:<-default-port>? (y/n)
y
petals-cli> Username: wrong-username
petals-cli> Password: right-pwd
Invalid credentials.
petals-cli> Retry? (y/n)
y

petals-cli> Username: right-username
petals-cli> Password: wrong-pwd
Invalid credentials.
petals-cli> Retry? (y/n)
y

petals-cli> Username: right-username
petals-cli> Password: right-pwd
petals-cli@<default-host>:<-default-port>>
{code}


h1. Administration Commands

h2. Working with JBI artifacts

h3. Deploying and Starting an Artifact at once

Petals CLI is able to deploy and start a JBI artifact without distinction between shared-library, component and service assembly using the following command:
{code}
deploy <artifact-file> [<configuration-file> | <configuration-properties>]
{code}
where:
* *<artifact-file>* is the local file name or the URL of the artifact to install or deploy and start
* *<configuration-file>* is the local file name or the URL of the properties file used to configure the artifact. This argument is used only if the artifact is a component. It has no sense for other artifacts. This argument is exclusive with {{<configuration-properties>}}.
* *<configuration-properties>* is a list of '_<property-name>=<property-value>_', separated by a space, where _<property-name>_ is the name of the property to configure with _<property-value>_. This argument is used only if the artifact is a component. It has no sense for other artifacts. This argument is exclusive with *<configuration-file>*.

{tip}Auto-completion is available on artifacts IDs and artifact file names.{tip}

h3. Deployment of an Artifact located in a Maven repository

Petals CLI is able to deploy and start a JBI artifact located into a Maven repository by using the following command:
{code}
deploy <maven-artifact> [<configuration-file> | <configuration-properties>]
{code}
where:
* *<maven-artifact>* is the Maven identifiers of the artifact to install: _group-id:artifact-id:version\[:classifier\]_. If required, the Maven repository can be defined in the Maven configuration file ($HOME/.m2/settings.xml)
* *<configuration-file>* is the local file name or the URL of the properties file used to configure the artifact. This argument is used only if the artifact is a component. It has no sense for other artifacts. This argument is exclusive with {{<configuration-properties>}}.
* *<configuration-properties>* is a list of '_<property-name>=<property-value>_', separated by a white character, where _<property-name>_ is the name of the property to configure with _<property-value>_. This argument is used only if the artifact is a component. It has no sense for other artifacts. This argument is exclusive with *<configuration-file>*.

h3. Bulk Deployment and Start

To deploy and start several artifacts in one command, just put them in a local directory and execute the command '_deploy_':
{code}
> ./petals-cli.sh -y - << EOF
deploy /tmp
EOF
> ./petals-cli.sh -C

Type 'help' for help.
------------------------------------------------------------------------------
petals-cli> deploy /tmp
Are you sure you want to deploy all artifacts of directory '/tmp'? (Y/n)
{code}

If the argument _<artifact-file>_ of the '_deploy_' command is a local directory, all artifacts of the directory are deployed. In this case, a confirmation is expected, except if the flag '_yes_' is set on the command line. A confirmation message is displayed in the mode console, except if the flag '_yes_' is set on the command line.

h3. Starting an Artifact

An artifact can be started by using the '_start_' command with the argument '_artifact_':
{code}
> ./petals-cli.sh -c start artifact [ <artifact-file> | [<artifact-type> <artifact-id>] ]
{code}
where:
* *<artifact-file>* is the local file name or the URL of the artifact to start.
* *<artifact-type>* is the nature (SL, component, SA) of the artifact to start.
* *<artifact-id>* is the JBI identifier of the artifact to start.

{tip}Auto-completion is available on artifacts IDs and artifact file names.{tip}

h3. Stopping an artifact

An artifact can be stopped by using the command '_stop_' with the argument '_artifact_':
{code}
> ./petals-cli.sh -c stop artifact [ <artifact-file> | [<artifact-type> <artifact-id>] ]
{code}
where:
* *<artifact-file>* is the local file name or the URL of the artifact to stop.
* *<artifact-type>* is the nature (SL, component, SA) of the artifact to stop.
* *<artifact-id>* is the JBI identifier of the artifact to stop.

{tip}Auto-completion is available on artifacts IDs and artifact file names.{tip}

h3. Undeploying and Stopping an Artifact at once

Petals CLI is able to stop and uninstall/undeploy a JBI artifact without distinction between shared-library, component and service assembly using the following command:
{code}
undeploy [ <artifact-file> | [<artifact-type> <artifact-id>] ]
{code}
where:
* *<artifact-file>* is the local file name or the URL of the artifact to undeploy.
* *<artifact-type>* is the nature (SL, component, SA) of the artifact to undeploy.
* *<artifact-id>* is the JBI identifier of the artifact to undeploy.

{tip}Auto-completion is available on artifacts IDs and artifact file names.{tip}

h3. Bulk Undeployment and Stop

To undeploy several artifacts in one command, just put them in a local directory and execute the '_undeploy_' command:
{code}
> ./petals-cli.sh -y - << EOF
undeploy
EOF
> ./petals-cli.sh -C

Type 'help' for help.
------------------------------------------------------------------------------
petals-cli> undeploy
Are you sure you want to undeploy all artifacts of the Petals node (Y/n) ?
{code}

If no argument is set on command '_undeploy_', all the artifacts are undeployed. In this case a confirmation is expected, except if the '_yes_' flag is set on the command line. A confirmation message is displayed in the console mode, except is the '_yes_' flag is set on the command line.

h3. Showing installed JBI artifacts

All the installed JBI artefacts can be listed using the command '_list \[<artifact-pattern> \[artifact-type\]\]_':
{code}
> ./petals-cli.sh -c list
petals-bc-soap Started BC
petals-se-bpel Started SE
soap-consume-provide Started SA
su-SOAP-EchoService-consume Started SU
su-SOAP-EchoService-provide Started SU
{code}
where:
* *<artifact-pattern>* is an optional RegExp pattern to filter the content of the returned list. All the returned JBI artifacts must have a JBI identifier matching the pattern. If no pattern is defined, all the installed artifacts are returned.
* *<artifact-type>* is one of the following values: SL, BC, SE, SA, SU, used to restrict the returned list.

For each artifact, the command displays (caution to the padding):
* Its JBI identifier.
* Its current status.
* Its type (SL, BC, SE, SA, SU).

h3. Getting information about an Artifact

Information about a JBI artifact can be got with the '_show_' command:
{code}
> ./petals-cli.sh -c show [-e] [ <artifact-file> | [<artifact-type> <artifact-id>] ]
{code}
where:
* *<artifact-file>* is the local file name or the URL of the artifact to show.
* *<artifact-type>* is the nature (SL, component, SA) of the artifact to show.
* *<artifact-id>* is the JBI identifier of the artifact to show.

The '_\-e' option displays extended information.

Displayed information includes:

* For a shared library:
** Its JBI identifier
** Its version, if available
** Extended information:
*** List of embedded libraries

* For a component (BC or SE):
** Its JBI identifier
** Its type: binding component or service engine
** Its version, if available
** Its state (loaded, installed, started, stopped, shutdown)
** Extended information:
*** List of embedded libraries of the boostrap classpath
*** List of embedded libraries of the runtime classpath

* For a service assembly:
** Its JBI identifier
** Its version, if available
** Its state (deployed, started, stopped, shutdown)
** List of embedded service-units (displayed using their JBI identifiers)
** Extended information:
*** For each service unit:
*** Its JBI identifier
*** Its version, if available
*** Its target component ((displayed using its JBI identifier)

{tip}Auto-completion is available on artifacts IDs and artifact file names.{tip}

h3. Interrupting a flow of commands

A flow of commands can be interrupted by using the '_exit_' command. If a number is set as argument, it is used as return code. The argument '_lastErrorCode_' is used as return code value of the last executed command. Otherwise, 0 is returned to the shell.
{code}
> ./petals-cli.sh -y - << EOF
deploy /tmp/my-artifact.zip
exit lastErrorCode
EOF
{code}

h3. Ending a flow of commands

When the end of a flow of commands is reached, if the last command is not '_exit_', the '_exit lastErrorCode_' command is implicitly executed.
{code}
> ./petals-cli.sh -y - << EOF
deploy /tmp/my-artifact.zip
EOF
echo $?
0
{code}

h2. Working with the Container

h3. Getting the versions related to a Petals node

To get the version of a Petals node, the version of the JVM running Petals node, and its operating system, use the '_version_' command:
{code}
> ./petals-cli.sh -c version
Petals JBI Container 3.1.4-SNAPSHOT
Java(TM) SE Runtime Environment 1.6.0_26-b03
Linux 3.0.0-16-generic-pae
{code}

h3. Stopping the container

The container can be stopped by using the '_stop_' command with the argument '_container_':
{code}
> ./petals-cli.sh -c stop container
{code}

h3. Shutdowning the container

The container can be shutdowned by using the command '_stop_' with the argument '_container_' and the parameter '_\--shutdown_'.
{code}
> ./petals-cli.sh -c stop container --shutdown
Are you sure you want to shutdown the container? (y/n)
{code}
A confirmation is expected, except if the '_yes_' flag is set on the command line. A confirmation message is displayed in the console mode, except if the '_yes_' flag is set on the command line.

h3. Getting the topology

When connected to a container, it is possible to get information about the topology this node is part of.

{code}
petals-cli@host:port> topology-list
Domain: Domain 1
Subdomain: SubDomain 1
* Node1
** information

* Node2
** information

Subdomain: SubDomain 2
...
{code}

\\
This command shows a set of Petals nodes, sorted by domain and sub-domains, each node having the following information:
* Container name
* Node type (master or slave)
* Host
* Node ports

h3. Getting the server properties

When connected to a container, it is possible to get all the values defined in its *server.properties* file.

{code}
petals-cli@host:port> properties-list
Key1: value1
Key2: value2
...
{code}
where "keyN" and "valueN" are the keys and values defined in the *server.properties* file of this container.

h3. Changing logger levels

On a container, it is possible to change the level of a logger.
{code}
petals-cli@host:port> logger-set <logger-name> <level>
logger1
logger2
...
{code}

To get all the available loggers, use loggers without any argument.
{code}
petals-cli@host:port> loggers
logger1
logger2
...
{code}

You can also use a regular expression to filter the candidate results.
{code}
petals-cli@host:port> loggers <regular expression>
logger1
logger2
...
{code}

{tip}Auto-completion is available on logger names.{tip}

h2. Working with the Service Registry

{note}Qualified names, like service and interface names, are written as follows:\{namespace-uri\}local-part.{note}

h3. Synchronizing the registry

A synchronization of the registry on a specific node can be done with the '_registry-sync_' command:
{code}
> registry-sync
Synchronization is done
{code}

\\
A synchronization of all the topology nodes can be done with the same command and the '_\--all_' argument.
{code}
> registry-sync --all
<Progress Report (as a percentage)>
Synchronization is done
{code}

\\
{note}Global synchronization is done in two passes:
* Each slave declares its end-points to the master node (n-1 synchronizations, where n is the number of nodes in the topology).
* Each slave gets the master end-points (start from the n-2{html}^th{html} node until we get back to the first slave).
{note}

The response message is displayed in console mode only.

h3. Showing the registry's full content

The full content of the registry can be dumped by using the '_registry-list_' command:
{code}
petals-cli> registry-list
Endpoints:
<endpoint-name-1>: <endpoint-1-characteristics>
<endpoint-name-2>: <endpoint-2-characteristics>
Services:
<service-name-1>:
<endpoints-list>
<service-name-2>:
<endpoints-list>
Interfaces:
<interface-name-1>:
<endpoints-list>
<interface-name-2>:
<endpoints-list>
{code}

where:
* <endpoint-name-x> is an endpoint name.
* <endpoint-x-characteristics> is the attributes of the endpoint, separated by comma: container identifier, component identifier, endpoint type.
* <service-name-x> is a service name.
* <interface-name-x> is an interface name.
* <endpoints-list> is the list of endpoint name implementing the interface or service.

h3. Filtering the registry's full content

The content of the registry can be dumped by using the '_registry-list_' command.
It is however possible to filter the dumped result.
{code}
petals-cli> registry-list endpoint <endpoint-name-regexp> service <service-name-regexp> interface <interface-name-regexp>
Endpoints:
<endpoint-name>: <endpoint-characteristics>
Services:
<service-name-1>:
<endpoint-name>
<service-name-2>:
<endpoint-name>
Interfaces:
<interface-name-1>:
<endpoint-name>
<interface-name-2>:
<endpoint-name>
{code}

where:
* *<endpoint-name-regexp>* is a regular expression used as filter on the full end-point name.
* *<service-name-regexp>* is a regular expression used as filter on the full service name.
* *<interface-name-regexp>* is a regular expression used as filter on the full interface name.

In the result:
* <endpoint-name> is the endpoint name.
* <endpoint-characteristics> is the attributes of the endpoint, separated by comma: container identifier, component identifier, endpoint type.
* <service-name-x> is the services associated to the specified endpoint.
* <interface-name-x> is the interface names associated with the specified endpoint.

The parameter order (endpoint, service, interface) does not matter.
All are optional. If none is specified, the entire regitry content is dumped.

h2. System Commands

Petals CLI can directly execute system commands.
To achieve it, the system command must be prefixed with *system:*.

{code}
petals-cli> system:<system-command>
{code}

As an example,

{code}
petals-cli> system:pwd
{code}