mgm

This section lists the Corda CLI A command line tool that supports various Corda-related tasks, including Corda Package Installer (CPI) creation and Corda cluster management. mgm arguments. You can use these commands to execute membership operations for static networks used for testing purposes.

Running the groupPolicy command without any arguments prints a sample GroupPolicy.json file that you can manually tweak.

Bash
PowerShell

corda-cli.sh mgm groupPolicy

corda-cli.cmd mgm groupPolicy

Alternatively, use the following command line arguments to define the static network section of the GroupPolicy:

Argument	Description
--file, -f	The path to a JSON or YAML file that contains static network information; see Generating GroupPolicy Using File Input.
--name	The X.500 A series of international standards defining a global directory service protocol for computer networks. It provides a structured framework for storing, accessing, and managing information about network resources and users in a hierarchical and distributed manner. name of the member Corda identity that has been granted admission to a membership group. Synonym for a virtual node or group member. ; see Generating GroupPolicy Using String Parameters.
--endpoint	The endpoint base URL; see Generating GroupPolicy Using String Parameters.
--endpoint-protocol	The version of end-to-end authentication protocol; see Generating GroupPolicy Using String Parameters.

Generating GroupPolicy Using File Input

To generate GroupPolicy using file input:

Bash
PowerShell

corda-cli.sh mgm groupPolicy --file="app/build/resources/src.yaml"

corda-cli.cmd mgm groupPolicy --file="app/build/resources/src.yaml"

Only memberNames or members blocks may be present.
A single endpoint is assumed for all members when memberNames is used.
Endpoint information specified under members overrides endpoint information set at the root level. An error is thrown if no endpoint information is provided.

Sample Files

JSON with memberNames:

{
  "endpoint": "http://dummy-url",
  "endpointProtocol": 5,
  "memberNames": ["C=GB, L=London, O=Member1", "C=GB, L=London, O=Member2"]
}

JSON with members:

{
  "members": [
      {
      "name": "C=GB, L=London, O=Member1",
      "status": "PENDING",
      "endpoint": "http://dummy-url",
      "endpointProtocol": 5
      },
      {
        "name": "C=GB, L=London, O=Member2",
        "endpoint": "http://dummy-url2",
        "endpointProtocol": 5
      }
    ]
}

YAML with memberNames:

endpoint: "http://dummy-url"
endpointProtocol: 5
memberNames: ["C=GB, L=London, O=Member1", "C=GB, L=London, O=Member2"]

YAML with members which all use a common endpoint, and Member1 overrides the protocol version:

endpoint: "http://dummy-url"
endpointProtocol: 5
members:
  - name: "C=GB, L=London, O=Member1"
    status: "PENDING"
    endpointProtocol: 10
  - name: "C=GB, L=London, O=Member2"

Generating GroupPolicy Using String Parameters

To generate GroupPolicy using parameters:

Bash
PowerShell

corda-cli.sh mgm groupPolicy --name="C=GB, L=London, O=Member1" --name="C=GB, L=London, O=Member2" --endpoint-protocol=5 --endpoint="http://dummy-url"

corda-cli.cmd mgm groupPolicy --name="C=GB, L=London, O=Member1" --name="C=GB, L=London, O=Member2" --endpoint-protocol=5 --endpoint="http://dummy-url"

Passing one or more --name arguments without specifying endpoint information throws an error.
Not passing any --name arguments returns a GroupPolicy with an empty list of static members.
A single endpoint is assumed for all members.

mgm

Generating GroupPolicy Using File Input

Sample Files

Generating GroupPolicy Using String Parameters

Was this page helpful?

Thanks for your feedback!

Chat with us

Propose documentation improvements directly

We're sorry this page wasn't helpful. Let us know how we can make it better!

Chat with us

Create an issue

Propose documentation improvements directly

Our use of cookies