Deploying Fabric Operations Console


The Fabric Operations Console can be deployed along with the Fabric Network. You can then manually add peers, orderers, CA to the console by importing appropriate JSON files.

The Helm Chart for Fabric Operations Console is available here.

If you want to create the JSON files automatically by using our ansible playbook, the CA server endpoint should be accessible publicly and that endpoint details added in organization.ca_data.url.

NOTE: The Fabric Operations Console has only been tested with operations.tls.enabled = false for Fabric Peers, Orderers and CAs.

Modifying Configuration File

A Sample configuration file for deploying Operations Console is available here. Main change being addition of a new key organization.fabric_console which when enabled will deploy the operations console for the organization.

For generic instructions on the Fabric configuration file, refer this guide.

Run playbook

The deploy-fabric-console.yaml playbook should be used to automatically generate the JSON files and deploy the console. This can be done using the following command

ansible-playbook platforms/hyperledger-fabric/configuration/deploy-fabric-console.yaml --extra-vars "@/path/to/network.yaml"

This will deploy the console which will be available over your proxy at https://<org_name>console.<org_namespace>.<org_external_url_suffix>

The JSON files will be available in <project_dir>/build/assets folder. You can import individual files on respective organization console as well as use bulk import for uploading the zip file <project_dir>/build/

Refer this guide for details on operating the Console.