Commands

Generic and supporting

display

Syntax: display [displayType]

Change display type (displayType) to: * standard where data rows and headers are formatted as regular table * csv where date rows and headers are separated with configured separator in the runtime console configuration file. * json where date are formatted in JSON (it's a good option for integration). * xml where date are formatted in XML (it's a good option for integration).

Examples:

Show the current settings:

> display
Display mode: plain_text

Change display to csv and show the list of microservices:

> display csv
Display mode: csv
> microservice list
Zone,Node,Microservice,Type,Version,#Services
default,NODE_1,queueMicroservice,native,1.5.0.0,1
default,NODE_1,exchange-rates,native,1.5.0.0,1
default,NODE_1,channelMicroservice,native,1.5.0.0,1
default,NODE_1,exchange,servlet,1.5.0.0,2
default,NODE_1,currency-converter-gbp,native,1.5.0.0,1
default,NODE_1,http-session-repository,native,1.5.0.0,2
default,NODE_1,currency-converter-chf,native,1.5.0.0,1
default,NODE_1,currency-converter-eur,native,1.5.0.0,1

Change display to json and show the list of microservices:

> display json
Display mode: json
> microservice list
{"commandResult":[{"Zone":"default","Node":"NODE_1","Microservice":"queueMicroservice","Type":"native","Version":"1.5.0.0","#Services":"1"},{"Zone":"default","Node":"NODE_1","Microservice":"exchange-rates","Type":"native","Version":"1.5.0.0","#Services":"1"},{"Zone":"default","Node":"NODE_1","Microservice":"channelMicroservice","Type":"native","Version":"1.5.0.0","#Services":"1"},{"Zone":"default","Node":"NODE_1","Microservice":"exchange","Type":"servlet","Version":"1.5.0.0","#Services":"2"},{"Zone":"default","Node":"NODE_1","Microservice":"currency-converter-gbp","Type":"native","Version":"1.5.0.0","#Services":"1"},{"Zone":"default","Node":"NODE_1","Microservice":"http-session-repository","Type":"native","Version":"1.5.0.0","#Services":"2"},{"Zone":"default","Node":"NODE_1","Microservice":"currency-converter-chf","Type":"native","Version":"1.5.0.0","#Services":"1"},{"Zone":"default","Node":"NODE_1","Microservice":"currency-converter-eur","Type":"native","Version":"1.5.0.0","#Services":"1"}],"exitCode":"0","printStream":[{"stdOut":[]},{"stdErr":[]}]}

Change display to xml and show the list of microservices:

> display xml
Display mode: xml
> microservice list
<groups><commandResult><rows><row><Zone>default</Zone><Node>NODE_1</Node><Microservice>queueMicroservice</Microservice><Type>native</Type><Version>1.5.0.0</Version><Services>1</Services></row><row><Zone>default</Zone><Node>NODE_1</Node><Microservice>exchange-rates</Microservice><Type>native</Type><Version>1.5.0.0</Version><Services>1</Services></row><row><Zone>default</Zone><Node>NODE_1</Node><Microservice>channelMicroservice</Microservice><Type>native</Type><Version>1.5.0.0</Version><Services>1</Services></row><row><Zone>default</Zone><Node>NODE_1</Node><Microservice>exchange</Microservice><Type>servlet</Type><Version>1.5.0.0</Version><Services>2</Services></row><row><Zone>default</Zone><Node>NODE_1</Node><Microservice>currency-converter-gbp</Microservice><Type>native</Type><Version>1.5.0.0</Version><Services>1</Services></row><row><Zone>default</Zone><Node>NODE_1</Node><Microservice>http-session-repository</Microservice><Type>native</Type><Version>1.5.0.0</Version><Services>2</Services></row><row><Zone>default</Zone><Node>NODE_1</Node><Microservice>currency-converter-chf</Microservice><Type>native</Type><Version>1.5.0.0</Version><Services>1</Services></row><row><Zone>default</Zone><Node>NODE_1</Node><Microservice>currency-converter-eur</Microservice><Type>native</Type><Version>1.5.0.0</Version><Services>1</Services></row></rows></commandResult><exitCode><line>0</line></exitCode><printStream><groups><group><groups><stdOut><groups></groups></stdOut></groups></group><group><groups><stdErr><groups></groups></stdErr></groups></group></groups></printStream></groups>

echo

Syntax: echo [on|off]

Change echo mode (on|off) or show current state. When echo mode is on the typed command is displayed just after command execution.

It's useful feature when commands are run as a script through script run, where is aggregated output the command and its results is displayed in proper order.

Examples:

Check the current state of echo mode

> echo
Echo mode: off

Turn echo mode on and show the list of microservices (notice that after turning on the echo mode, each executed command is displayed):

> echo on
Echo mode: on
> microservice list
microservice list
Zone    Node   Microservice            Type    Version #Services
default NODE_1 queueMicroservice       native  1.5.0.0 1
default NODE_1 exchange-rates          native  1.5.0.0 1
default NODE_1 channelMicroservice     native  1.5.0.0 1
default NODE_1 exchange                servlet 1.5.0.0 2
default NODE_1 currency-converter-gbp  native  1.5.0.0 1
default NODE_1 http-session-repository native  1.5.0.0 2
default NODE_1 currency-converter-chf  native  1.5.0.0 1
default NODE_1 currency-converter-eur  native  1.5.0.0 1

env set

Syntax: env set <name> <value>

Set variables inside the console session and use it with other commands or scripts.

Argument	Information
`<name>`	The name of the variable, it can be access by `$name`.
`<value>`	the variable's value.

Examples:

Set $micro1 as queueMicroservice and stop it using newly created variable:

> microservice status queueMicroservice
Zone    Node   Microservice      ProcessID Status  Available Activated
default NODE_1 queueMicroservice 14021     RUNNING yes       yes

> env set micro1 queueMicroservice
Environment variable 'micro' set to 'queueMicroservice'.

> microservice stop $micro1
>> queueMicroservice <<

stopped: yes

> microservice status queueMicroservice
Zone    Node   Microservice      ProcessID Status  Available Activated
default NODE_1 queueMicroservice none      STOPPED no        yes

Unset previously defined variable

> env set micro1 ""
Environment variable 'micro1' unset.

env show

Syntax: env show

Show the list of defined variables inside the console session.

Examples:

Set $micro1 and $micro2 and show all variables

> env show

> env set micro1 queueMicroservice
Environment variable 'micro1' set to 'queueMicroservice'.

> env set micro2 channelMicroservice
Environment variable 'micro2' set to 'channelMicroservice'.

> env show
micro2: channelMicroservice
micro1: queueMicroservice

events list

Syntax: events list

Display the list of events handled by JLupin.

Examples:

Show the events list after the process keeper has performed action

> events list
Zone    Node   EventId           EventTime           EventType                                         EventDesc
default NODE_1 20623576048038034 2018-08-08 08:41:22 START_MICROSERVICES_STOPPED_OUTSIDE_JLUPIN_BEFORE microservices ready to start due to being stopped ...
default NODE_1 20623593453296516 2018-08-08 08:41:39 START_MICROSERVICES_STOPPED_OUTSIDE_JLUPIN_AFTER  microservices:[currency-converter-eur] statuses af...

events details

Syntax: events details <event_id>

Display details of the given event identified by <event_id>.

Examples:

> events details 20623576048038034
Node:      NODE_1
EventId:   20623576048038034
EventTime: 2018-08-08 08:41:22
EventType: START_MICROSERVICES_STOPPED_OUTSIDE_JLUPIN_BEFORE
EventDesc: microservices ready to start due to being stopped outside jlupin:[currency-converter-eur]

exit

Syntax: exit

Quit console.

Examples:

> exit

grep

Syntax: grep <regexp>

Filter results using <regexp> regular expression (applied to each line).

Examples:

Find all microservices including the word exchange in their names:

> microservice list | grep exchange
default NODE_1 exchange-rates          native  1.5.0.0 1
default NODE_1 exchange                servlet 1.5.0.0 2

Syntax: header [on|off]

It determines if headers should be displayed (on) or not (off).

Examples:

Show the current setting and the list of microservices:

> header
Header mode: on

> microservice list
Zone    Node   Microservice            Type    Version #Services
default NODE_1 queueMicroservice       native  1.5.0.0 1
default NODE_1 exchange-rates          native  1.5.0.0 1
default NODE_1 channelMicroservice     native  1.5.0.0 1
default NODE_1 exchange                servlet 1.5.0.0 2
default NODE_1 currency-converter-gbp  native  1.5.0.0 1
default NODE_1 http-session-repository native  1.5.0.0 2
default NODE_1 currency-converter-chf  native  1.5.0.0 1
default NODE_1 currency-converter-eur  native  1.5.0.0 1

Turn off headers and show the list of microservices:

> header off
Header mode: off
> microservice list
default NODE_1 queueMicroservice       native  1.5.0.0 1
default NODE_1 exchange-rates          native  1.5.0.0 1
default NODE_1 channelMicroservice     native  1.5.0.0 1
default NODE_1 exchange                servlet 1.5.0.0 2
default NODE_1 currency-converter-gbp  native  1.5.0.0 1
default NODE_1 http-session-repository native  1.5.0.0 2
default NODE_1 currency-converter-chf  native  1.5.0.0 1
default NODE_1 currency-converter-eur  native  1.5.0.0 1

help

Syntax: help [<command>]

Shows help for all or given (<command>) command.

Examples:

> help
> help microservice

interactive

syntax: interactive [on|off]

Change interactive mode (on/off) or show current state.

If the interactive mode is enabled all commands that assume their scope are preceded by a control question.

If you have three microservices running on the node:

> microservice list
Zone    Node   Microservice            Type    Version #Services
default NODE_1 queueMicroservice       native  1.5.0.0 1
default NODE_1 exchange-rates          native  1.5.0.0 1
default NODE_1 channelMicroservice     native  1.5.0.0 1
default NODE_1 exchange                servlet 1.5.0.0 2
default NODE_1 currency-converter-gbp  native  1.5.0.0 1
default NODE_1 http-session-repository native  1.5.0.0 2
default NODE_1 currency-converter-chf  native  1.5.0.0 1
default NODE_1 currency-converter-eur  native  1.5.0.0 1

The following command:

> microservice restart

is going to restart all your microservices (if the name is not given, the console assumes all).

If the interactive mode is enabled the above command triggers a control question:

Are you sure you want to restart all microservices on the node? (Y/N):

If it is disabled - the console proceed action with no other interactions.

If you provide the exact scope of the command (no assuming is performed), even if the interactive mode is enabled, a control question is not asked.

For example:

> microservice restart exchange-rates

will restart exchange-rates microservice immediately.

> microservice restart *

will restart all microservices running on the node immediately.

Argument	Information
`on\|off`	Enable/disable interactive mode.

Examples:

Turn interactive mode on

> interactive on

Turn interactive mode off

> interactive off

Check interactive mode state

> interactive
Interactive mode: on

lock release

Syntax: lock release

Release all locks handled by the current node.

Examples:

Release all locks

> lock release
all locks was released
Locks released: NODE_2

oscommand

Syntax: oscommand <oscommand>

Execute external command in OS (where CLI console is installed). The exit code of the oscommand is the same as the exit code of OS command.

Examples:

Show os statistics:

> oscommand oscommand vmstat 3 3
procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu-----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa st
 2  0 333216 335440      0 5374476    0    0     7     3    0    0  2  2 97  0  0
 0  0 333216 334136      0 5374484    0    0     0     0  922  867  1  1 98  0  0
 0  0 333216 335004      0 5374500    0    0     0     4 1585 1438  3  3 93  0  0
OS command has been executed successfully.

quit

Syntax: quit

Quit console.

Examples:

> quit

show

Syntax: show [all|brief|<parameter>] [<microservice_name>]

List attributes (all, brief or specified by <parameter>) of the node or the microservice identified by <microservice_name>.

Argument	Information
`all\|brief\|<parameter>`	Show value of all (`all`), selected (`brief`) attributes or specific parameter (`<parameter>`).
`<microservice_name>`	If this parameter is given, then the command applies to specific microservice, otherwise it applies to the node.

Each component in JLupin Platform environment are represented in its console as an object with set of parameters, which are grouped in the following groups:

ATTRIBUTES - the list of object attributes, which describes it in the scope of console.
RUNTIME - set of parameters that show the current state of the object.
CONFIGURATION - set of parameters from microservice's or node's configuration (collected in YAML files).
JAVA_PROPERTIES - the current list of java properties provided by the platform and user (ex. through additional configuration) of the node or the given microservice.

Is case if CONFIGURATION the further sections and associated sets of parameters are provided in tree model, where name of the sections is a key to deeper section or a leaf.

Examples:

The readTimeout parameter of JLRMC logical server from Main Server configuration file:

ZONE:
  name: default
MAIN_SERVER:
  name: NODE_1
SERVERS:
  JLRMC: #JLupin Remote Method Call Fast Protocol
    port: 9090
    readTimeout: 480000
    waitForFinishExecuteAllRequests: true
[...]

is represented as CONFIGURATION:SERVERS:JLRMC:port and its value can be displayed in this way:

> show CONFIGURATION:SERVERS:JLRMC:port

If you want to access microservice configuration provide the proper parameter path and name of a microservice.

> show CONFIGURATION:PROPERTIES:jvmOptions1 myMicro

If you want to display all sections and parameters on specific level of configuration, use *, like in the following example:

> show CONFIGURATION:PROPERTIES:* myMicro
> show RUNTIME:*

set

Syntax: set <parameter> to <value> [<microservice_name>]

Set <parameter> to <value> for the node or the microservice identified by <microservice_name>.

Argument	Information
`<parameter>`	Parameter name.
`<value>`	Value.
`<microservice_name>`	If this parameter is given, then the command applies to specific microservice, otherwise it applies to the node.

Examples:

Increasing number of threads for JLRMC interface of the node to 256:

> set CONFIGURATION:SERVERS:JLRMC:threadPoolSize to 256

Changing JAVA OPTS for myMicro:

> set CONFIGURATION:PROPERTIES:jvmOptions1 to "-Xms64M -Xmx192M" myMicro

All changes have to be activated through node or microservice restart.

script record start

Syntax: script record start <file_path>

Start recording list of successfully executed commands in <file_path> file. The <file_path> is relative to $JLUPIN_HOME/platform/start/control/script (defined by appropriate parameter in the console runtime configuration).

Examples:

Start recording the sample.jlc script (the recorded script will be localed in $JLUPIN_HOME/platform/start/control/script):

> script record start sample.jlc
Script recording started.

script record show

Syntax: script record show

Show the list of recorded commands (the script record start should be previously performed).

Examples:

Start recording the sample.jlc script, enter some commands and display the current list of the recording (notice that when command exit with an error, it is not added to the script):

> script record start sample.jlc
Script recording started.
> microservice status
Zone    Node   Microservice            ProcessID Status  Available Activated
default NODE_1 channelMicroservice     6796      RUNNING yes       yes
default NODE_1 currency-converter-chf  5200      RUNNING yes       yes
default NODE_1 currency-converter-eur  10012     RUNNING yes       yes
default NODE_1 currency-converter-gbp  7888      RUNNING yes       yes
default NODE_1 exchange                516       RUNNING yes       yes
default NODE_1 exchange-rates          7620      RUNNING yes       yes
default NODE_1 http-session-repository 5084      RUNNING yes       yes
default NODE_1 queueMicroservice       6420      RUNNING yes       yes
> node version
Zone    Node   ProductName                       CodeName Version    CommitNo
default NODE_1 JLupin Platform Community Edition CYPRUS   1.5.0.1-ce 47759aa6
> node vvvvv
Command not found.
> script record show
interactive off
echo on
microservice status
node version

NOTICE that on the top of each script the interactive off and echo on is added automatically. The first is necessary to prevent script from being paused, that second one is useful when log analyzing from script execution is needed.

script record stop

Syntax: script record stop

Stop script recording. The <file_path script (defined while script record start executing) is ready to use, no further command will be added to the script.

Examples:

Start recording the sample.jlc script, enter some commands and stop recording:

> script record start sample.jlc
Script recording started.
> microservice status
Zone    Node   Microservice            ProcessID Status  Available Activated
default NODE_1 channelMicroservice     6796      RUNNING yes       yes
default NODE_1 currency-converter-chf  5200      RUNNING yes       yes
default NODE_1 currency-converter-eur  10012     RUNNING yes       yes
default NODE_1 currency-converter-gbp  7888      RUNNING yes       yes
default NODE_1 exchange                516       RUNNING yes       yes
default NODE_1 exchange-rates          7620      RUNNING yes       yes
default NODE_1 http-session-repository 5084      RUNNING yes       yes
default NODE_1 queueMicroservice       6420      RUNNING yes       yes
> node version
Zone    Node   ProductName                       CodeName Version    CommitNo
default NODE_1 JLupin Platform Community Edition CYPRUS   1.5.0.1-ce 47759aa6
> script record stop
Script recording stopped.

script run

Syntax: script run <file_path> [force]

Run a script from file (<file_path>), optionally in force mode.

Argument	Information
`<file_path>`	Path to the script file. The final path is relative to the default path ($ JLUPIN_HOME / server / start).
`[force]`	If the `force` switch is given, execution of the entire set of commands is not stopped, even if one of the commands fails - all commands are executed from the script regardless of the state of each operation.

Examples:

Start recording the sample.jlc script, enter some commands, stop recording and execute previously recorded script:

> script record start sample.jlc
Script recording started.
> microservice status
Zone    Node   Microservice            ProcessID Status  Available Activated
default NODE_1 channelMicroservice     6796      RUNNING yes       yes
default NODE_1 currency-converter-chf  5200      RUNNING yes       yes
default NODE_1 currency-converter-eur  10012     RUNNING yes       yes
default NODE_1 currency-converter-gbp  7888      RUNNING yes       yes
default NODE_1 exchange                516       RUNNING yes       yes
default NODE_1 exchange-rates          7620      RUNNING yes       yes
default NODE_1 http-session-repository 5084      RUNNING yes       yes
default NODE_1 queueMicroservice       6420      RUNNING yes       yes
> node version
Zone    Node   ProductName                       CodeName Version    CommitNo
default NODE_1 JLupin Platform Community Edition CYPRUS   1.5.0.1-ce 47759aa6
> node vvvvv
Command not found.
> script record show
interactive off
echo on
microservice status
node version
> script record stop
Script recording stopped.
> script run sample.jlc
Interactive mode: off
Echo mode: on
microservice status
Zone    Node   Microservice            ProcessID Status  Available Activated
default NODE_1 channelMicroservice     6796      RUNNING yes       yes
default NODE_1 currency-converter-chf  5200      RUNNING yes       yes
default NODE_1 currency-converter-eur  10012     RUNNING yes       yes
default NODE_1 currency-converter-gbp  7888      RUNNING yes       yes
default NODE_1 exchange                516       RUNNING yes       yes
default NODE_1 exchange-rates          7620      RUNNING yes       yes
erdefault NODE_1 http-session-repository 5084      RUNNING yes       yes
default NODE_1 queueMicroservice       6420      RUNNING yes       yes
node version
Zone    Node   ProductName                       CodeName Version    CommitNo
default NODE_1 JLupin Platform Community Edition CYPRUS   1.5.0.1-ce 47759aa6

Run previously and manually prepared script (sample2.jlc), located in /home/jlupin, in force mode (it contains mistakes on purpose):

> script run /home/jlupin/sample2.jls

> script run sample2.jlc
Interactive mode: off
Echo mode: on
microservice list
Zone    Node   Microservice            Type    Version #Services
default NODE_1 queueMicroservice       native  1.5.0.0 1
default NODE_1 exchange-rates          native  1.5.0.0 1
default NODE_1 channelMicroservice     native  1.5.0.0 1
default NODE_1 exchange                servlet 1.5.0.0 2
default NODE_1 currency-converter-gbp  native  1.5.0.0 1
default NODE_1 http-session-repository native  1.5.0.0 2
default NODE_1 currency-converter-chf  native  1.5.0.0 1
default NODE_1 currency-converter-eur  native  1.5.0.0 1
microservice restart non-existent
>> non-existent <<

restarted: no
error:     non-existent@NODE_1: Cannot restart the microservice due to: running microservice:non-existent is not defined (redefined) in current configuration file, no restart process this microservice will be executed. Check console logs for details.
node runtime os
Zone    Node   Status  %OsCpuUsage %OsMemUsage #OsMemFree
default NODE_1 ENABLED 12.7        69.9        2.37 GB

sleep

Syntax: sleep <seconds>

Sleep for the <seconds> number of seconds. It's useful while executing scripts, ex. to wait until service discovery detects previously performed changes in the environment.

Examples:

Sleep for 5 seconds:

> sleep 5
>

verbose

Syntax: verbose [on|off]

Change verbose mode (on|off) or show current state. if the verbose is on, more information is displayed including print stream coming from microservices processes, provided by the platform.

Argument	Information
`on\|off`	Enable/disable verbose mode.

Examples:

Turn verbose mode off:

> verbose off

Turn verbose mode on:

> verbose on

Check the current setting:

> verbose
Verbose mode: off

The output of a microservice being terminated when verbose mode is on:

> microservice terminate exchange-rates
Updating microservices on NODE_1:
lock by type:MAIN_SERVER_TRANSMISSION_COMMAND_INTERPRETER is lock by operation:EXECUTE_COMMAND
removed configuration for process:exchange-rates from process manager load balancer
stop force processes by names...
lock by type:MICROSERVICE_HEALTH_CHECK is lock by operation:STOP_TERMINATE
lock by type:MICROSERVICE_OS_PROCESS_MANIPULATION is lock by operation:STOP_TERMINATE
start destroy process:exchange-rates with process id:6356
process:exchange-rates with process id:6356 was properly destroy by OS destroy command
process:exchange-rates linked with microservice process id:6356 was destroyed
lock by type:MICROSERVICE_OS_PROCESS_MANIPULATION is unlock by operation:STOP_TERMINATE
lock by type:MICROSERVICE_HEALTH_CHECK is unlock by operation:STOP_TERMINATE
lock by type:MAIN_SERVER_TRANSMISSION_COMMAND_INTERPRETER is unlock by operation:EXECUTE_COMMAND
exchange-rates@NODE_1: Microservice terminated correctly.
>> exchange-rates <<

terminated: yes

The output of a microservice being terminated when verbose mode is off:

> microservice terminate exchange-rates
>> exchange-rates <<

terminated: yes

version

Syntax: version

Display console version.

Examples:

ProductName             CodeName Version CommitNo
JLupin Platform Console CYPRUS   1.5.0.0 303533e

Node

node activate

Syntax: node activate

Activate node, which means that its service repository is actively updated by service discovery process and services are available for their consumers in the environment.

Examples:

> node activate
Node activated: NODE_1  
> microservice repo
Zone    Node   Microservice           LoadBalancer       Entry                         CommPorts           ConnTimeout ReadTimeout
default NODE_1 currency-converter-chf LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-chf LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-chf LOAD_BALANCER_NO:1 currency-converter-chf@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 currency-converter-chf@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 currency-converter-chf@NODE_1 9090,9095,9096,9097 2000        300000

node deactivate

Syntax: node deactivate [force]

Deactivate node, which means that its service repository is empty regardless the operational state of microservices and services are not available to potential consumers in the environment. If the force option is used, additionally all logical servers are shutdown and sockets are closed. Use force carefully because it ma cause errors for requests that are processed while node deactivation with force is performed.

Examples:

> microservice repo
Zone    Node   Microservice           LoadBalancer       Entry                         CommPorts           ConnTimeout ReadTimeout
default NODE_1 currency-converter-chf LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-chf LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-chf LOAD_BALANCER_NO:1 currency-converter-chf@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 currency-converter-chf@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 currency-converter-chf@NODE_1 9090,9095,9096,9097 2000        300000
> node deactivate
Node deactivated: NODE_1
> microservice repo
> node deactivate force
Node deactivated: NODE_1
> microservice repo
> node activate
Node activated: NODE_1
> microservice repo
Zone    Node   Microservice           LoadBalancer       Entry                         CommPorts           ConnTimeout ReadTimeout
default NODE_1 currency-converter-chf LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-chf LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-chf LOAD_BALANCER_NO:1 currency-converter-chf@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 currency-converter-chf@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 currency-converter-chf@NODE_1 9090,9095,9096,9097 2000        300000

node peers

Syntax: node peers

Display node peers - other JLupin nodes to which the balancers of the current node and its microservices are directed and service discovery process is performed. The list of node peers is the list of JLupin nodes with which the microservices on the current node can communicate via built-in balancers.

The list of node peers are directly taken from NODE_PEERS section from Main Server configuration file.

Examples:

Entries in main.yml on NODE_2:

NODE_PEERS:
  NODE_2:
    ip: 127.0.0.1
    jlrmcPort: 9190
    queuePort: 9195
    transmissionPort: 9196
    informationPort: 9197
  NODE_1:
    queuePort: 9095
    jlrmcPort: 9090
    informationPort: 9097
    ip: 10.2.2.31
    transmissionPort: 9096

The list available in console (on NODE_2):

> node peers
SrcZone SrcNode SrcIPAddress Zone    Node   IPAddress CommPorts
default NODE_2  127.0.0.1    default NODE_1 10.2.2.31 9090,9095,9096,9097
default NODE_2  127.0.0.1    default NODE_2 127.0.0.1 9190,9195,9196,9197

node peer add

Syntax: node peer add <peer_name> <peer_IP> [<jlrmcPort> <queuePort> <transmissionPort> <informationPort>]

Add a node peer identified in the network by IP address <peer_IP> (or FQDN if resolvable by the current node) with name <peer_name> to the current node's configuration with default ports from configuration file (control.yml) or explicitly provided (<jlrmcPort> <queuePort> <transmissionPort> <informationPort>).

The command modifies NODE_PEERS section in Main Server configuration file.

Argument	Information
`<peer_name>`	Name of a peer node to add
`<peer_IP>`	IP address of a peer node.
`[<jlrmcPort>]`	Optional. JLRMC port of a peer node.
`[<queuePort>]`	Optional. QUEUE port of a peer node.
`[<transmissionPort>]`	Optional. TRANSMISSION port of a peer node.
`[<informationPort>]`	Optional. INFORMATION port of a peer node.

Examples:

Adding peer NODE_1 to NODE_2, using standard ports

> node peers
SrcZone SrcNode SrcIPAddress Zone    Node   IPAddress CommPorts
default NODE_2  127.0.0.1    default NODE_2 127.0.0.1 9190,9195,9196,9197

> node peer add NODE_1 10.2.2.31
Peer added: NODE_1

> node peers
SrcZone SrcNode SrcIPAddress Zone    Node   IPAddress CommPorts
default NODE_2  127.0.0.1    default NODE_1 10.2.2.31 9090,9095,9096,9097
default NODE_2  127.0.0.1    default NODE_2 127.0.0.1 9190,9195,9196,9197

Adding peer NODE_2 to NODE_1, using custom ports

> node peers
SrcZone SrcNode SrcIPAddress Zone    Node   IPAddress CommPorts
default t-app1  127.0.0.1    default t-app1 127.0.0.1 9090,9095,9096,9097

> node peer add NODE_2 10.2.2.32 9190 9195 9196 9197
Peer added: NODE_2

> node peers
SrcZone SrcNode SrcIPAddress Zone    Node   IPAddress CommPorts
default NODE_1  127.0.0.1    default NODE_1 127.0.0.1 9090,9095,9096,9097
default NODE_1  127.0.0.1    default NODE_2 10.2.2.32 9190,9195,9196,9197

node peer remove

Syntax: node peer remove <peer_name>

Remove a peer node (<peer_name>) from the current node's configuration.

The command modifies NODE_PEERS section in Main Server configuration file.

Argument	Information
`<peer_name>`	Name of a peer node to remove.

Examples:

Removing NODE_1 peer from NODE_2:

> node peers
SrcZone SrcNode SrcIPAddress Zone    Node   IPAddress CommPorts
default NODE_2  127.0.0.1    default NODE_1 10.2.2.31 9090,9095,9096,9097
default NODE_2  127.0.0.1    default NODE_2 127.0.0.1 9190,9195,9196,9197

> node peer remove NODE_1
Peer removed: NODE_1

> node peers
SrcZone SrcNode SrcIPAddress Zone    Node   IPAddress CommPorts
default NODE_2  127.0.0.1    default NODE_2 127.0.0.1 9190,9195,9196,9197

node repo

Syntax: node repo

Show entries of service repository in the process manager scope - the list of microservices that this particular node (Main Serve) is able to connect and send a request. The list of remote microservices is available if additional nodes are provided in NODE_PEERS section in Main Server configuration.

Examples:

In this case we have two nodes: NODE_1 and NODE_2, on which the same microservice is running: exchange. We changed NODE_PEERS list on NODE_2 by adding NODE_1, look at the difference between outputs of node peers and node repo commands on each node:

NODE_PEERS @ NODE_1

> node peers
SrcZone SrcNode SrcIPAddress Zone    Node   IPAddress CommPorts
default t-app1  127.0.0.1    default t-app1 127.0.0.1 9090,9095,9096,9097

node repo @ NODE_2

> node repo
Zone    Node   Entry              CommPorts   ConnTimeout ReadTimeout
default t-app1 exchange@localhost 20000,20002 1000        30000

NODE_PEERS @ NODE_2

> node peers
SrcZone SrcNode SrcIPAddress Zone    Node   IPAddress CommPorts
default NODE_2  127.0.0.1    default NODE_1 10.2.2.31 9090,9095,9096,9097
default NODE_2  127.0.0.1    default NODE_2 127.0.0.1 9190,9195,9196,9197

node repo @ NODE_2

> node repo
Zone    Node   Entry              CommPorts           ConnTimeout ReadTimeout
default NODE_2 exchange@localhost 30000,30002         1000        30000
default NODE_2 exchange@NODE_1    9090,9095,9096,9097 1000        90000

NODE_2 "sees" microserices running on NODE_1.

node runtime

Syntax: node runtime [threads|memory|cpu|os]

Show the runtime parameter of the current node. If no arguments are provided the basic information if provided.

Argument	Information
`[threads]`	Detailed information about thread pools associated with logical servers.
`[memory]`	Detailed information about JVM memory statistics of Main Server.
`[cpu]`	Information about CPU usage of Main Server.
`[os]`	Basic information of operating system - overall memory and CPU usage and.

Examples:

Basic information

> node runtime
Zone    Node   Status  %MemUsageMax %CpuUsage
default NODE_1 ENABLED 36.5         1.0

Threads statistics

> node runtime threads
Zone    Node   Status  Server           Type             %ThrUsage #ThrFree
default NODE_1 ENABLED JLRMC            JLRMC            0.0       1024
default NODE_1 ENABLED ELASTIC_HTTP     ELASTIC_HTTP     0.0       128
default NODE_1 ENABLED QUEUE            QUEUE            0.0       256
default NODE_1 ENABLED TRANSMISSION     TRANSMISSION     1.6       63
default NODE_1 ENABLED INFORMATION      INFORMATION      0.0       64
default NODE_1 ENABLED INFORMATION_HTTP INFORMATION_HTTP 0.0       64

Memory statistics

> node runtime memory
Zone    Node   Status  %MemUsageTotal %MemUsageMax #MemFree #MemUsed #MemTotal #MemMax
default NODE_1 ENABLED 57.2           57.2         0.11 GB  0.14 GB  0.25 GB   0.25 GB

OS statistics

> node runtime os
Zone    Node   Status  %OsCpuUsage %OsMemUsage #OsMemFree
default NODE_1 ENABLED 4.7         36.1        4.88 GB

node servers list

Syntax: node servers list

Show the list of logical servers with its basic configuration.

Examples:

> node servers list
Zone    Node   Status  Server           Type             Port #Threads
default NODE_1 ENABLED JLRMC            JLRMC            9090 1024
default NODE_1 ENABLED ELASTIC_HTTP     ELASTIC_HTTP     8082 128
default NODE_1 ENABLED QUEUE            QUEUE            9095 256
default NODE_1 ENABLED TRANSMISSION     TRANSMISSION     9096 64
default NODE_1 ENABLED INFORMATION      INFORMATION      9097 64
default NODE_1 ENABLED INFORMATION_HTTP INFORMATION_HTTP 9098 64

node shutdown

Syntax: node shutdown

Shutdown JLupin Platform and all microservices (including technical ones). The shutdown is performed in graceful mode, it waits until all requests are processed.

Examples:

> node shutdown
Node shutdown: NODE_1

node start

Syntax: node start

Start JLupin PLatform. On Linux it simply executes $JLUPIN_HOME/platform/start/start.sh script, however on windows JLupin Platform should operate as a windows service (see JLupin Platform how to do it).

Examples:

> node start
Node started.

node status

Syntax: node status

Show JLupin PLatform status, the following value are possible:

ENABLED - the node is up and running, all services are configured as available.
DEACTIVATED - the node is deactivated, which means that all services are configured as unavailable (service repository is empty)
DISABLED - the node is disabled, which means that all services are configured as unavailable (service repository is empty) and all logical servers for data processing are shutdown (sockets are unavailable).

Examples:

> node status
Zone    Node   #Micro Status
default NODE_1 8      ENABLED
> node deactivate
Node deactivated: NODE_1
> node status
Zone    Node   #Micro Status
default NODE_1 8      DEACTIVATED
> node deactivate force
Node deactivated: NODE_1
> node status
Zone    Node   #Micro Status
default NODE_1 8      DISABLED
> node activate
Node activated: NODE_1
> node status
Zone    Node   #Micro Status
default NODE_1 8      ENABLED

node terminate

Syntax: node terminate

Terminate the Main Server and all microservices (including technical ones) on the current.

Examples:

> node terminate

node version

Syntax: node version

Show version of the current node.

Examples:

> node version
Zone    Node   ProductName                       CodeName Version    CommitNo
default NODE_1 JLupin Platform Community Edition CYPRUS   1.5.0.0-ce 1dfff125

Microservice

microservice activate

Syntax: microservice activate [<microservice>]

Activate all or the given (<microservice>) microservice, where 'activation' means that all or the given (<microservice>) microservice is configured as available - it's present in the service repository.

Examples:

Check the status:

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 25236     RUNNING yes       yes
default NODE_1 exchange               24938     RUNNING yes       yes
default NODE_1 exchange-rates         24754     RUNNING yes       yes

> microservice repo
Zone    Node   Microservice           LoadBalancer       Entry                         CommPorts           ConnTimeout ReadTimeout
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:2 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:2 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:2 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:2 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:2 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:2 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000

Deactivate exchange-rates and check the status again. Note that exchange-rates has become unavailable for other microservices.

> microservice deactivate exchange-rates
>> exchange-rates <<

deactivated: yes

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 25236     RUNNING yes       yes
default NODE_1 exchange               24938     RUNNING yes       yes
default NODE_1 exchange-rates         24754     RUNNING yes       no
> microservice repo
Zone    Node   Microservice           LoadBalancer       Entry                         CommPorts           ConnTimeout ReadTimeout
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:2 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:2 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:2 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:2 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000

Activate exchange-rates and check the status again:

> microservice activate exchange-rates
>> exchange-rates <<

activated: yes

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 25236     RUNNING yes       yes
default NODE_1 exchange               24938     RUNNING yes       yes
default NODE_1 exchange-rates         24754     RUNNING yes       yes

> microservice repo
Zone    Node   Microservice           LoadBalancer       Entry                         CommPorts           ConnTimeout ReadTimeout
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:2 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:2 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:2 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:2 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:2 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:2 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000

microservice deactivate

Syntax: microservice deactivate [<microservice>]

Deactivate all or the given (<microservice>) microservice, where 'deactivation' means that all or the given (<microservice>) microservice is configured as unavailable - it's absent in the service repository.

Examples:

Check the status:

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 25236     RUNNING yes       yes
default NODE_1 exchange               24938     RUNNING yes       yes
default NODE_1 exchange-rates         24754     RUNNING yes       yes

> microservice repo
Zone    Node   Microservice           LoadBalancer       Entry                         CommPorts           ConnTimeout ReadTimeout
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:2 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:2 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:2 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:2 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:2 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:2 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000

Deactivate exchange-rates and check the status again. Note that exchange-rates has become unavailable for other microservices.

> microservice deactivate exchange-rates
>> exchange-rates <<

deactivated: yes

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 25236     RUNNING yes       yes
default NODE_1 exchange               24938     RUNNING yes       yes
default NODE_1 exchange-rates         24754     RUNNING yes       no
> microservice repo
Zone    Node   Microservice           LoadBalancer       Entry                         CommPorts           ConnTimeout ReadTimeout
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:2 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:2 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:2 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:2 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000

microservice deploy

Syntax: microservice deploy [<repository_name>:]<file_path>

Deploy (upload & start or restart) microservice file identified by <file_path>, located in the default or <repository_name> repository.

Argument	Information
`<repository_name>`	The name of the repository from which the microservice file should be downloaded from. Repositories are defined in the configuration.
`<file_path>`	Path to zipped microservice, including file name with its extension.

Examples:

Deploy from default repository:

> microservice status
Zone    Node   Microservice            ProcessID Status   Available Activated
default NODE_1 currency-converter-chf  22046     RUNNING  yes       yes
default NODE_1 currency-converter-eur  21969     RUNNING  yes       yes
default NODE_1 currency-converter-gbp  22319     RUNNING  yes       yes
default NODE_1 exchange                22223     RUNNING  yes       yes

> microservice deploy exchange-rates.zip
>> exchange-rates.zip <<

deployed: yes

> microservice status
Zone    Node   Microservice            ProcessID Status   Available Activated
default NODE_1 currency-converter-chf  22046     RUNNING  yes       yes
default NODE_1 currency-converter-eur  21969     RUNNING  yes       yes
default NODE_1 currency-converter-gbp  22319     RUNNING  yes       yes
default NODE_1 exchange                22223     RUNNING  yes       yes
default NODE_1 exchange-rates          18774     RUNNING  yes       yes

Deploy from centralArtifactory repository (remote_http type), from release0.5 directory:

> microservice deploy centralArtifactory:release0.5/exchange-rates.zip
>> exchange-rates.zip <<

deployed: yes

microservice destroy

Syntax: microservice destroy [<microservice>]

Destroy all or the given (<microservice>) microservice located on the node. To perform this action the microservice must be stopped or terminated.

Examples:

Destroy all microservices (if interactive mode is enabled a control question is asked)

> microservice status
Zone    Node   Microservice           ProcessID Status     Available Activated
default NODE_1 currency-converter-eur none      TERMINATED no        yes
default NODE_1 exchange               none      TERMINATED no        yes

> microservice destroy
Are you sure you want to destroy selected microservices on the node? (Y/N):
Y
>> currency-converter-eur <<

destroyed: yes

>> exchange <<

destroyed: yes

> microservice status
Zone Node Microservice ProcessID Status Available Activated

Destroy all microservice (no question is asked... be careful)

> microservice status
Zone    Node   Microservice           ProcessID Status   Available Activated
default NODE_1 currency-converter-eur none      STOPPED* no        yes
default NODE_1 exchange               none      STOPPED* no        yes
default NODE_1 exchange-rates         none      STOPPED* no        yes
> microservice destroy *
>> currency-converter-eur <<

destroyed: yes

>> exchange <<

destroyed: yes

>> exchange-rates <<

destroyed: yes
> microservice status
Zone Node Microservice ProcessID Status Available Activated

Destroy specific microservice

> microservice status
Zone    Node   Microservice           ProcessID Status     Available Activated
default NODE_1 currency-converter-eur none      TERMINATED no        yes
default NODE_1 exchange               none      TERMINATED no        yes
default NODE_1 exchange-rates         none      TERMINATED no        yes

> microservice destroy exchange-rates
>> exchange-rates <<

destroyed: yes
> microservice status
Zone    Node   Microservice           ProcessID Status     Available Activated
default NODE_1 currency-converter-eur none      TERMINATED no        yes
default NODE_1 exchange               none      TERMINATED no        yes

microservice details

Syntax: microservice details [<microservice>]

Show details of the given (<microservice>) microservice on the current node. In the current version of JLupin PLatform - the list of provided services are presented.

Examples:

> microservice details
Zone    Node   Microservice           Service
default NODE_1 currency-converter-eur currencyConverterEurService
default NODE_1 exchange               GET|/
default NODE_1 exchange               POST|/convert
default NODE_1 exchange-rates         exchangeRatesService

microservice double restart

Syntax: microservice double restart [<microservice>]

Restart all or the given (<microservice>) microservice twice. It useful when keeping the same set of listening ports for the microservice is important.

Examples:

Check the service port (main port for synchronous requests processing - JLRMC in case of NATIVE, HTTP in case of SERVLET):

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 49064     RUNNING yes       yes
default NODE_1 exchange               49204     RUNNING yes       yes
default NODE_1 exchange-rates         19419     RUNNING yes       yes

> show RUNTIME:servicePort exchange-rates
servicePort: 20009

Double restart:

> microservice double restart exchange-rates
>> exchange-rates <<

restarted: yes

Check service port again:

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 49064     RUNNING yes       yes
default NODE_1 exchange               49204     RUNNING yes       yes
default NODE_1 exchange-rates         19897     RUNNING yes       yes

> show RUNTIME:servicePort exchange-rates
servicePort: 20009

microservice list

Syntax: microservice list

List microservices on the node.

Examples:

> microservice list
Zone    Node   Microservice           Type    Version #Services
default NODE_1 exchange-rates         native  1.5.0.0 1
default NODE_1 exchange               servlet 1.5.0.0 2
default NODE_1 currency-converter-eur native  1.5.0.0 1

microservice repo

Syntax: microservice repo [<microservice>]

Show microservice's load balancer's service repository for the current or given (<microservice>) microservice.

Examples:

Check the list of available microservices from each microservice perspective:

> microservice repo
Zone    Node   Microservice           LoadBalancer       Entry                         CommPorts           ConnTimeout ReadTimeout
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:2 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:2 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 currency-converter-eur LOAD_BALANCER_NO:2 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange               LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:2 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:2 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange-rates         LOAD_BALANCER_NO:2 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000

Check the list of microservices from exchange microservice perspective:

> microservice repo exchange
Zone    Node   Microservice LoadBalancer       Entry                         CommPorts           ConnTimeout ReadTimeout
default NODE_1 exchange     LOAD_BALANCER_NO:1 exchange-rates@NODE_1         9090,9095,9096,9097 2000        300000
default NODE_1 exchange     LOAD_BALANCER_NO:1 exchange@NODE_1               9090,9095,9096,9097 2000        300000
default NODE_1 exchange     LOAD_BALANCER_NO:1 currency-converter-eur@NODE_1 9090,9095,9096,9097 2000        300000

microservice restart

Syntax: microservice restart [<microservice>]

Restart all or given (<microservice>) microservice on the node (restart is fully online)

Examples:

Restart all microservices (if interactive mode is enabled a control question is asked)

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 40180     RUNNING yes       yes
default NODE_1 exchange               37664     RUNNING yes       yes
default NODE_1 exchange-rates         41369     RUNNING yes       yes

> microservice restart
Are you sure you want to restart selected microservices on the node? (Y/N):
y
>> currency-converter-eur <<

restarted: yes

>> exchange <<

restarted: yes

>> exchange-rates <<

restarted: yes

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 48183     RUNNING yes       yes
default NODE_1 exchange               48312     RUNNING yes       yes
default NODE_1 exchange-rates         48574     RUNNING yes       yes

Restart all microservice (no question is asked... be careful... or never mind, the zero downtime deployment mechanism keeps services always online)

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 48183     RUNNING yes       yes
default NODE_1 exchange               48312     RUNNING yes       yes
default NODE_1 exchange-rates         48574     RUNNING yes       yes

> microservice restart *
>> currency-converter-eur <<

restarted: yes

>> exchange <<

restarted: yes

>> exchange-rates <<

restarted: yes

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 49064     RUNNING yes       yes
default NODE_1 exchange               49204     RUNNING yes       yes
default NODE_1 exchange-rates         49473     RUNNING yes       yes

Restart the specific microservice

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 49064     RUNNING yes       yes
default NODE_1 exchange               49204     RUNNING yes       yes
default NODE_1 exchange-rates         49473     RUNNING yes       yes

> microservice restart exchange
exchange         exchange-rates
> microservice restart exchange-rates
>> exchange-rates <<

restarted: yes

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 49064     RUNNING yes       yes
default NODE_1 exchange               49204     RUNNING yes       yes
default NODE_1 exchange-rates         50357     RUNNING yes       yes

microservice runtime

Syntax: microservice runtime [threads|memory|cpu|stats] [<microservice>]

It shows runtime parameters of all or the given microservice (<microservice>).

Argument	Information
`[threads]`	Detailed information about thread pools.
`[memory]`	Detailed information about all of the given `<microservice>`.
`[cpu]`	Information about CPU usage of all of the given `<microservice>`.
`[stats]`	Basic statistics of all or the given `<microservice>`.
`[<microservice>]`	The name of the microservice to which the command is applied

Examples:

Basic information of all microservices

> microservice runtime
Zone    Node   Microservice           Status  %MemUsageMax %CpuUsage
default NODE_2 exchange               RUNNING 52.7         0.1
default NODE_2 currency-converter-chf RUNNING 66.7         0.1

Threads statistics

> microservice runtime threads
Zone    Node   Microservice           Status  Server Type  %ThrUsage #ThrFree
default NODE_2 exchange               RUNNING HTTP   HTTP  0.0       10000
default NODE_2 currency-converter-chf RUNNING JLRMC  JLRMC 0.0       128
default NODE_2 currency-converter-chf RUNNING QUEUE  QUEUE 0.0       128

Memory usage of specific microservice

> microservice runtime memory currency-converter-chf
Zone    Node   Microservice           Status  %MemUsageTotal %MemUsageMax #MemFree #MemUsed #MemTotal #MemMax
default NODE_2 currency-converter-chf RUNNING 71.2           71.2         0.03 GB  0.08 GB  0.12 GB   0.12 GB

microservice start

Syntax: microservice start [<microservice>]

Start all or the given (<microservice>) microservice ('force' flag indicates if also activate microservice regardless its previous state).

Examples:

Start all microservices (if interactive mode is enabled a control question is asked)

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur none      STOPPED no        yes
default NODE_1 exchange               none      STOPPED no        yes
default NODE_1 exchange-rates         none      STOPPED no        yes

> microservice start
Are you sure you want to start selected microservices on the node? (Y/N):
y
>> currency-converter-eur <<

started: yes

>> exchange <<

started: yes

>> exchange-rates <<

started: yes

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 24008     RUNNING yes       yes
default NODE_1 exchange               24109     RUNNING yes       yes
default NODE_1 exchange-rates         24227     RUNNING yes       yes

Start all microservice (with no question asked)

> microservice status
Zone    Node   Microservice           ProcessID Status     Available Activated
default NODE_1 currency-converter-eur none      TERMINATED no        yes
default NODE_1 exchange               none      TERMINATED no        yes
default NODE_1 exchange-rates         none      TERMINATED no        yes

> microservice start *
>> currency-converter-eur <<

started: yes

>> exchange <<

started: yes

>> exchange-rates <<

started: yes

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 24891     RUNNING yes       yes
default NODE_1 exchange               24989     RUNNING yes       yes
default NODE_1 exchange-rates         25097     RUNNING yes       yes

Start specific microservice

> microservice status
Zone    Node   Microservice           ProcessID Status     Available Activated
default NODE_1 currency-converter-eur none      TERMINATED no        yes
default NODE_1 exchange               none      TERMINATED no        yes
default NODE_1 exchange-rates         none      TERMINATED no        yes

> microservice start exchange
exchange         exchange-rates
> microservice start exchange-rates
>> exchange-rates <<

started: yes

> microservice status
Zone    Node   Microservice           ProcessID Status     Available Activated
default NODE_1 currency-converter-eur none      TERMINATED no        yes
default NODE_1 exchange               none      TERMINATED no        yes
default NODE_1 exchange-rates         25719     RUNNING    yes       yes

microservice status

Syntax: microservice status [<microservice>]

Show the status of all or the given (<microservice>) microservice.

'ProcessID' is the PID of microservice's process in OS (if started)
'Status' is the operational status of a microservice
'Available' shows the availability status from Main Server load balancer perspective
'Activated' shows the administrative status of microservice availability.

If 'Status' is 'RUNNING' and 'Available' is 'no' it can mean that: * microservice is overloaded and not responding * microservice process has been killed or suddenly has stopped

If 'Activated' is 'false' it means that microservice deactivate or node deactivate has been executed. Deactivated microservice is not preset in the service repository, so it's not available for other microservices as well as for external clients using HTTP(S) protocol on JLupin Edge Balancer (only microservices with httpStickySession = true is available for previously created sessions, new ones are handled by another microservices in the environment) .

Examples:

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 40180     RUNNING yes       yes
default NODE_1 exchange               37664     RUNNING yes       yes
default NODE_1 exchange-rates         41369     RUNNING yes       yes

microservice stop

Syntax: microservice stop [<microservice>]

Stop all or the given (<microservice>) microservice on the current node. The 'stop' procedure is graceful - JLupin Platform waits until all requests are processed (within the timeout).

Examples:

Stop all microservices (if interactive mode is enabled a control question is asked)

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 18984     RUNNING yes       yes
default NODE_1 exchange               22223     RUNNING yes       yes
default NODE_1 exchange-rates         none      STOPPED no        yes

> microservice stop
Are you sure you want to stop selected microservices on the node? (Y/N):
Y
>> currency-converter-eur <<

stopped: yes

>> exchange <<

stopped: yes

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur none      STOPPED no        yes
default NODE_1 exchange               none      STOPPED no        yes
default NODE_1 exchange-rates         none      STOPPED no        yes

Stop all microservice (no question is asked... be careful... have you configured a cluster ??)

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 25236     RUNNING yes       yes
default NODE_1 exchange               24938     RUNNING yes       yes
default NODE_1 exchange-rates         24754     RUNNING yes       yes
> microservice stop *
>> currency-converter-eur <<

stopped: yes

>> exchange <<

stopped: yes

>> exchange-rates <<

stopped: yes
> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur none      STOPPED no        yes
default NODE_1 exchange               none      STOPPED no        yes
default NODE_1 exchange-rates         none      STOPPED no        yes

Stop specific microservice

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 18984     RUNNING yes       yes
default NODE_1 exchange               22223     RUNNING yes       yes
default NODE_1 exchange-rates         18774     RUNNING yes       yes

> microservice stop exchange-rates
>> exchange-rates <<

stopped: yes

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 18984     RUNNING yes       yes
default NODE_1 exchange               22223     RUNNING yes       yes
default NODE_1 exchange-rates         none      STOPPED no        yes

microservice tech

Syntax: microservice tech <name> <command> [force]

Manage technical microservices. Commands are provided from technical microservice configuration file and are dynamically prompt to user. If force option is provided the command is executed regardless of whether the command is known to JLupin Platform.

Argument	Information
`<name>`	Name of technical microservice.
`<command>`	command for the management of a technical microservice.
`[force]`	The command is executed regardless of whether the command is known to Main Server.

Examples:

Status of nginx microservice:

> microservice tech nginx status
Zone    Node   Type  Name  ProcessID Running
default NODE_2 nginx nginx 29012     yes

Reload of nginx microservice (verbose is on, otherwise no comments are provided)

> microservice tech nginx reload
lock by type:MAIN_SERVER_TRANSMISSION_COMMAND_INTERPRETER is lock by operation:EXECUTE_COMMAND
lock by type:TECHNICAL_PROCESS_HEALTH_CHECK is lock by operation:EXECUTE_COMMAND
lock by type:TECHNICAL_OS_PROCESS_MANIPULATION is lock by operation:EXECUTE_COMMAND
start executing NGINX command:reload for:LINUX
process output after executing NGINX command:reload for:LINUX is null
lock by type:TECHNICAL_OS_PROCESS_MANIPULATION is unlock by operation:EXECUTE_COMMAND
lock by type:TECHNICAL_PROCESS_HEALTH_CHECK is unlock by operation:EXECUTE_COMMAND
lock by type:MAIN_SERVER_TRANSMISSION_COMMAND_INTERPRETER is unlock by operation:EXECUTE_COMMAND
NODE_1: Executed command reload on technical microservice nginx.

microservice terminate

Syntax: microservice terminate [<microservice>]

Stop force all or the given (<microservice>) microservice on the current node.

Examples:

Terminate all microservices (if interactive mode is enabled a control question is asked)

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 24008     RUNNING yes       yes
default NODE_1 exchange               24109     RUNNING yes       yes
default NODE_1 exchange-rates         24227     RUNNING yes       yes

> microservice terminate
Are you sure you want to terminate selected microservices on the node? (Y/N):
y
>> currency-converter-eur <<

terminated: yes

>> exchange <<

terminated: yes

>> exchange-rates <<

terminated: yes

> microservice status
Zone    Node   Microservice           ProcessID Status     Available Activated
default NODE_1 currency-converter-eur none      TERMINATED no        yes
default NODE_1 exchange               none      TERMINATED no        yes
default NODE_1 exchange-rates         none      TERMINATED no        yes

Terminate all microservice (no question is asked... be careful... have you configured a cluster ??)

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 24891     RUNNING yes       yes
default NODE_1 exchange               24989     RUNNING yes       yes
default NODE_1 exchange-rates         25097     RUNNING yes       yes

> microservice terminate *
>> currency-converter-eur <<

terminated: yes

>> exchange <<

terminated: yes

>> exchange-rates <<

terminated: yes

> microservice status
Zone    Node   Microservice           ProcessID Status     Available Activated
default NODE_1 currency-converter-eur none      TERMINATED no        yes
default NODE_1 exchange               none      TERMINATED no        yes
default NODE_1 exchange-rates         none      TERMINATED no        yes

Terminate specific microservice:

> microservice status
Zone    Node   Microservice           ProcessID Status  Available Activated
default NODE_1 currency-converter-eur 37565     RUNNING yes       yes
default NODE_1 exchange               37664     RUNNING yes       yes
default NODE_1 exchange-rates         25719     RUNNING yes       yes

> microservice terminate exchange-rates
>> exchange-rates <<

terminated: yes

> microservice status
Zone    Node   Microservice           ProcessID Status     Available Activated
default NODE_1 currency-converter-eur 37565     RUNNING    yes       yes
default NODE_1 exchange               37664     RUNNING    yes       yes
default NODE_1 exchange-rates         none      TERMINATED no        yes

microservice undeploy

Syntax: microservice undeploy [<microservice>] [force]

Undeploy (stop or terminate and destroy) all or the given () microservice ('force' flag indicates terminate).

Examples:

Undeploy channelMicroservice microservice:

> microservice status
Zone    Node   Microservice            ProcessID Status  Available Activated
default NODE_1 channelMicroservice     21819     RUNNING yes       yes
default NODE_1 currency-converter-chf  22046     RUNNING yes       yes
default NODE_1 currency-converter-eur  21969     RUNNING yes       yes
default NODE_1 currency-converter-gbp  22319     RUNNING yes       yes
default NODE_1 exchange                22223     RUNNING yes       yes
default NODE_1 exchange-rates          29290     RUNNING yes       yes
default NODE_1 http-session-repository 22139     RUNNING yes       yes
default NODE_1 queueMicroservice       21891     RUNNING yes       yes

> microservice undeploy channelMicroservice
>> channelMicroservice <<

undeployed: yes

> microservice status
Zone    Node   Microservice            ProcessID Status  Available Activated
default NODE_1 currency-converter-chf  22046     RUNNING yes       yes
default NODE_1 currency-converter-eur  21969     RUNNING yes       yes
default NODE_1 currency-converter-gbp  22319     RUNNING yes       yes
default NODE_1 exchange                22223     RUNNING yes       yes
default NODE_1 exchange-rates          29290     RUNNING yes       yes
default NODE_1 http-session-repository 22139     RUNNING yes       yes
default NODE_1 queueMicroservice       21891     RUNNING yes       yes

Forcibly undeploy exchange-rates microservice (exchange-rates is terminated before being destroyed):

> microservice status
Zone    Node   Microservice            ProcessID Status  Available Activated
default NODE_1 channelMicroservice     21819     RUNNING yes       yes
default NODE_1 currency-converter-chf  22046     RUNNING yes       yes
default NODE_1 currency-converter-eur  21969     RUNNING yes       yes
default NODE_1 currency-converter-gbp  22319     RUNNING yes       yes
default NODE_1 exchange                22223     RUNNING yes       yes
default NODE_1 http-session-repository 22139     RUNNING yes       yes
default NODE_1 queueMicroservice       21891     RUNNING yes       yes

> microservice undeploy exchange-rates force
>> exchange-rates <<

undeployed: yes

> microservice status
Zone    Node   Microservice            ProcessID Status  Available Activated
default NODE_1 currency-converter-chf  22046     RUNNING yes       yes
default NODE_1 currency-converter-eur  21969     RUNNING yes       yes
default NODE_1 currency-converter-gbp  22319     RUNNING yes       yes
default NODE_1 exchange                22223     RUNNING yes       yes
default NODE_1 http-session-repository 22139     RUNNING yes       yes

microservice upload

Syntax: microservice upload [<repository_name>:]<file_path>

Upload microservice file identified by <file_path>, located in the default or <repository_name> repository.

Argument	Information
`<repository_name>`	The name of the repository from which the microservice file should be downloaded from. Repositories are defined in the configuration.
`<file_path>`	Path to zipped microservice, including file name with its extension.

Examples:

Upload from default repository:

> microservice status
Zone    Node   Microservice            ProcessID Status  Available Activated
default NODE_1 currency-converter-chf  22046     RUNNING yes       yes
default NODE_1 currency-converter-eur  21969     RUNNING yes       yes
default NODE_1 currency-converter-gbp  22319     RUNNING yes       yes
default NODE_1 exchange                22223     RUNNING yes       yes
default NODE_1 http-session-repository 22139     RUNNING yes       yes

> microservice upload exchange-rates.zip
>> exchange-rates.zip <<

uploaded: yes

> microservice status
Zone    Node   Microservice            ProcessID Status   Available Activated
default NODE_1 currency-converter-chf  22046     RUNNING  yes       yes
default NODE_1 currency-converter-eur  21969     RUNNING  yes       yes
default NODE_1 currency-converter-gbp  22319     RUNNING  yes       yes
default NODE_1 exchange                22223     RUNNING  yes       yes
default NODE_1 exchange-rates          none      STOPPED* no        yes
default NODE_1 http-session-repository 22139     RUNNING  yes       yes

Upload from centralArtifactory repository (remote_http type), from release0.5 directory:

> microservice status
Zone    Node   Microservice            ProcessID Status  Available Activated
default NODE_1 currency-converter-chf  22046     RUNNING yes       yes
default NODE_1 currency-converter-eur  21969     RUNNING yes       yes
default NODE_1 currency-converter-gbp  22319     RUNNING yes       yes
default NODE_1 exchange                22223     RUNNING yes       yes
default NODE_1 http-session-repository 22139     RUNNING yes       yes

> microservice upload centralArtifactory:release0.5/exchange-rates.zip
>> exchange-rates.zip <<

uploaded: yes

> microservice status
Zone    Node   Microservice            ProcessID Status   Available Activated
default NODE_1 currency-converter-chf  22046     RUNNING  yes       yes
default NODE_1 currency-converter-eur  21969     RUNNING  yes       yes
default NODE_1 currency-converter-gbp  22319     RUNNING  yes       yes
default NODE_1 exchange                22223     RUNNING  yes       yes
default NODE_1 exchange-rates          none      STOPPED* no        yes
default NODE_1 http-session-repository 22139     RUNNING  yes       yes

Documentation

CONTENTS

Commands

Generic and supporting

display

echo

env set

env show

events list

events details

exit

grep

header

help

interactive

lock release

oscommand

quit

show

set

script record start

script record show

script record stop

script run

sleep

verbose

version

Node

node activate

node deactivate

node peers

node peer add

node peer remove

node repo

node runtime

node servers list

node shutdown

node start

node status

node terminate

node version

Microservice

microservice activate

microservice deactivate

microservice deploy

microservice destroy

microservice details

microservice double restart

microservice list

microservice repo

microservice restart

microservice runtime

microservice start

microservice status

microservice stop

microservice tech

microservice terminate

microservice undeploy

microservice upload