IBM Blockchain Platform

https://www.ibm.com/docs/en/blockchain-platform
Admin
IBM Blockchain Platform is an enterprise-grade blockchain solution that enables organizations to...
Tokens:682,652
Snippets:2,471
Trust Score:10
Update:10 months ago
Show doc for...
Tokens:
Raw
### Example Operator Deployment Output

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=options-deploy-blockchain-platform-253-prem-manually

This is an example of the expected output when verifying the operator deployment status using `kubectl get deployment`. It confirms that the `ibp-operator` deployment is ready, up-to-date, and available with a running instance.

```text
NAME           READY     UP-TO-DATE   AVAILABLE   AGE
ibp-operator   1/1       1            1           46s
```

--------------------------------

### Docker Run Output Example

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=reference-cloud-hsm-pkcs-11-proxy

This is an example output from running the Docker container locally. It shows the execution of client-specific commands like adding a server, creating a certificate, copying certificate files, verifying the Luna partitions, and starting the PKCS11 daemon.

```bash
$ docker run -it -e HSM_ADDRESS=<HSM_ADDRESS> -e CLIENT_ADDRESS=<CLIENT_ADDRESS> -v ${PWD}/configs/:/configs test
+ vtl addServer -n 10.208.66.177 -c /configs/server.pem

New server 10.208.66.177 successfully added to server list.

+ vtl createcert -n 10.220.203.73
Private Key created and written to: /usr/safenet/lunaclient/cert/client/10.220.203.73Key.pem
Certificate created and written to: /usr/safenet/lunaclient/cert/client/10.220.203.73.pem
+ cp /configs/cert.pem /usr/safenet/lunaclient/cert/client/10.220.203.73.pem
+ cp /configs/key.pem /usr/safenet/lunaclient/cert/client/10.220.203.73Key.pem
+ vtl verify

The following Luna SA Slots/Partitions were found:

Slot    Serial #            Label
====    ================    =====
    0           500752010     partition1

+ pkcs11-daemon /usr/safenet/lunaclient/lib/libCryptoki2_64.so -
pkcs11-proxy[12]: Listening on: tcp://0.0.0.0:2345
```

--------------------------------

### Console URL Example

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=kubernetes-deploying-blockchain-platform-252-behind-firewall

An example of the IBM Blockchain Platform console URL, where placeholders for namespace and domain need to be replaced with actual deployment-specific values.

```text
https://<NAMESPACE>-ibpconsole-console.<DOMAIN>:443
```

--------------------------------

### Example Deployment Status Output

Source: https://www.ibm.com/docs/en/blockchain-platform/2.1_topic=platform-deploy-blockchain-213-manually

Example output from `kubectl get deployment` command showing the status of the `ibp-operator` deployment. It indicates that one replica is expected, ready, and available, with a deployment age of 46 seconds.

```text
NAME           READY     UP-TO-DATE   AVAILABLE   AGE
ibp-operator   1/1       1            1           46s

```

--------------------------------

### Download Fabric CA Client Binaries

Source: https://www.ibm.com/docs/en/blockchain-platform/2.1_topic=how-using-blockchain-platform-apis

Fetches and installs the Fabric tool binaries, including the Fabric CA client, using a curl command. It installs the binaries into a 'bin/' directory. Assumes you have curl installed.

```bash
curl -sSL http://bit.ly/2ysbOFE | bash -s 1.4.3 1.4.3 -d -s
```

--------------------------------

### Verify DNS Configuration with nslookup

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=kubernetes-deploying-blockchain-platform-252

A command-line example using `nslookup` to verify that a specific hostname, like 'console.test.example.com', is correctly resolving to its associated IP address, confirming DNS setup.

```bash
$ nslookup console.test.example.com

```

--------------------------------

### Console URL and Login Example

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=kubernetes-deploying-blockchain-platform-253

Provides an example of the IBM Blockchain Platform console URL and demonstrates how to access the login screen. It also explains how to use the email and password fields from the ibp-console.yaml file for authentication.

```text
https://<NAMESPACE>-ibpconsole-console.<DOMAIN>:443

console.example.com
console.test.example.com
peer.test.example.com
```

--------------------------------

### Example IBM Blockchain Platform Console URL

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=kubernetes-deploying-blockchain-platform-254

An example of a fully formed IBM Blockchain Platform console URL, demonstrating the structure after replacing the namespace and domain placeholders.

```plaintext
https://blockchain-project-ibpconsole-console.xyz.abc.com:443
```

--------------------------------

### Example: Get Logs from Console UI Container

Source: https://www.ibm.com/docs/en/blockchain-platform/2.1_topic=kubernetes-deploying-blockchain-platform-213

This is a concrete example of the `kubectl logs` command, specifically fetching logs from the 'optools' container (the console UI) of the 'ibpconsole' pod within the 'blockchain-project' namespace. This helps in debugging issues related to the console's user interface.

```bash
kubectl logs -f ibpconsole-55cf9db6cc-856nz optools -n blockchain-project
```

--------------------------------

### Start Local Docker Registry (Shell)

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=options-deploy-from-red-hat-marketplace-airgap-installation

Starts a local Docker registry using `cloudctl case launch`. This command requires the case file, inventory item, and arguments specifying the registry host, user, password, and directory.

```shell
cloudctl case launch \
--case ${OFFLINECASE} \
--inventory ${ITEM} \
--action start-registry \
--args "--registry $PORTABLE_REGISTRY --user $PORTABLE_REGISTRY_USER --pass $PORTABLE_REGISTRY_PASSWORD --dir $PORTABLE_REGISTRY_PATH"
```

--------------------------------

### Example IBM Blockchain Platform Console URL

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=kubernetes-deploying-blockchain-platform-252

An example of a fully formed IBM Blockchain Platform console URL. This illustrates the expected format after replacing the namespace and domain placeholders.

```plaintext
https://blockchain-project-ibpconsole-console.xyz.abc.com:443

```

--------------------------------

### Install Node.js Application Dependencies

Source: https://www.ibm.com/docs/en/blockchain-platform/2.1_topic=tutorials-creating-applications

Installs the necessary Node.js dependencies for the commercial paper application. This command is run after navigating to the application directory.

```bash
npm install
```

--------------------------------

### Start Local Docker Registry for IBM Blockchain Platform

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=options-deploy-from-red-hat-marketplace-airgap-installation

This command uses the `cloudctl` CLI to start the local Docker registry. It requires the case file, inventory item, and arguments specifying the registry host and port, user, password, and the directory for image storage.

```shell
cloudctl case launch \
--case ${OFFLINECASE} \
--inventory ${ITEM} \
--action start-registry \
--args "--registry $PORTABLE_REGISTRY --user $PORTABLE_REGISTRY_USER --pass $PORTABLE_REGISTRY_PASSWORD --dir $PORTABLE_REGISTRY_PATH"


```

--------------------------------

### Example Output of Local Docker Run

Source: https://www.ibm.com/docs/en/blockchain-platform/2.1_topic=tutorials-hardware-security-module-hsm

This is an example of the expected output when running the Docker image locally. It demonstrates successful server addition, certificate creation, file copying, and the PKCS11 proxy listening on the specified port.

```shell
$ docker run -it -e HSM_ADDRESS=<HSM_ADDRESS> -e CLIENT_ADDRESS=<CLIENT_ADDRESS> -v ${PWD}/configs/:/configs test
+ vtl addServer -n 10.208.66.177 -c /configs/server.pem

New server 10.208.66.177 successfully added to server list.

+ vtl createcert -n 10.220.203.73
Private Key created and written to: /usr/safenet/lunaclient/cert/client/10.220.203.73Key.pem
Certificate created and written to: /usr/safenet/lunaclient/cert/client/10.220.203.73.pem
+ cp /configs/cert.pem /usr/safenet/lunaclient/cert/client/10.220.203.73.pem
+ cp /configs/key.pem /usr/safenet/lunaclient/cert/client/10.220.203.73Key.pem
+ vtl verify

The following Luna SA Slots/Partitions were found:

Slot    Serial #            Label
====    ================    =====
    0           500752010     partition1

+ pkcs11-daemon /usr/safenet/lunaclient/lib/libCryptoki2_64.so -
pkcs11-proxy[12]: Listening on: tcp://0.0.0.0:2345

```

--------------------------------

### Example Successful ClusterRoleBinding Application Output

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=options-deploy-blockchain-251-manually

This is an example of the output you might see after successfully applying the ClusterRoleBinding and adding the cluster role to the user using `oc` commands. It confirms the creation of the ClusterRoleBinding and the addition of the role to the service account.

```text
clusterrolebinding.rbac.authorization.k8s.io/blockchain-project created
clusterrole.rbac.authorization.k8s.io/blockchain-project added: "system:serviceaccounts:blockchain-project"

```

--------------------------------

### Start PKCS11 Daemon

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=reference-cloud-hsm-pkcs-11-proxy

This command starts the PKCS11 daemon using a specified library location. It's a simple execution command.

```bash
pkcs11-daemon $LIBRARY_LOCATION -
```

--------------------------------

### DNS Wildcard Entry Example

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=kubernetes-deploying-blockchain-platform-252

This DNS entry example demonstrates how to configure a wildcard host entry for a load balancer. This is crucial for enabling console and peer services to resolve correctly within your Kubernetes environment.

```dns
*.test.example.com

```

--------------------------------

### Get Kubernetes Namespaces using kubectl

Source: https://www.ibm.com/docs/en/blockchain-platform/2.1_topic=ha-about-high-availability

This command lists all available namespaces in a Kubernetes cluster. It is used to determine the correct namespace, often one starting with 'n', which is required for other kubectl commands like 'get deployment'.

```bash
kubectl get namespace
```

--------------------------------

### Complete Configuration File Example for IBM EN Blockchain Platform

Source: https://www.ibm.com/docs/en/blockchain-platform/2.1_topic=how-using-blockchain-platform-apis

An example of a completed configuration file for the IBM EN Blockchain Platform. It includes enrollment details for the component and TLS CA, along with their respective certificates and credentials. This file can be used with the 'Create an ordering service' or 'Create a peer' API.

```json
{
   "enrollment": {
      "component": {
         "cahost": "9.30.20.70",
         "caport": "32129",
         "caname": "ca",
         "catls": {
            "cacert": "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUNGakNDQWIyZ0F3SUJBZ0lVTmlUbkdTandSdU1JVXhpWGcwMGZZWXhPSndJd0NnWUlLb1pJemowRUF3SXcKYURFTE1Ba0dBMVVFQmhNQ1ZWTXhGekFWQmdOVkJBZ1REazV2Y25Sb0lFTmhjbTlzYVc1aE1SUXdFZ1lEVlFRSwpFd3RJZVhCbGNteGxaR2RsY2pFUE1BMEdBMVVFQ3hNR1JtRmljbWxqTVJ0Z3WURWUVFERXhCbVlXSnlhV010ClkyRXRjMlZ5ZG1WeU1CNFhEVEU0TVRFeE5qRTJNVEF3TUZvWERUTXpNVEV4TWpFMk1UQXdNRm93YURFTE1Ba0cKQTFVRUJoTUNWVk14RnpBVkJnTlZCQWdURGs1dmNuUm9JRU5oY205c2FXNWhNUlF3RWdZRFZRUUtFd3RJZVhCbApjbXhsWkdkbGNqRVBNQTBHQTFVRUN4TUdSbUZpY21sak1Sa3dGd1lEVlFRREV4Qm1ZV0p5YVdNdFkyRXRjMlZ5CmRtVnlNRmt3RXdZSEtvWkl6ajBDQVFZSUtvWkl6ajBEQVFjRFFnQUU1dlBucDJUNTdkY2hTOGRLNExsMFJRZEEKd284RmJsMzBPcnBGdWFHUld5TFl4eGcxcVFTemhUY3hTcGtHZjh3a1FzVDVFb01lSWcrRytldjBOU01FUTZORgpNRU13RGdZRFZSMFBBUUgvQkFRREFnRUdNQklHQTFVZEV3RUIvd1FJTUFZQkFmOENBUUV3SFFZRFZSME9CQllFCkZMd2d1N0J3Uk9lQ2hzV2hWQWptMTdmalh1eVBNQW9HQ0NxR1NNNDlCQU1DQTBjQU1FUUNJR0FCRmNSdXhtSkIKY3c4OTJJOXhPS3YxVmYyT0JHZUh5N2pFQzRBRm5najFBaUJqdHFvdjBXMXdxZjhwcGttYkxIQkJoWW1vS3ZqRwo4bDQyeVQ5bWYxWVQrZz09Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K",
            "enrollid": "peer1",
            "enrollsecret": "peer1pw",
            "admincerts": [
               "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUMzRENDQW9PZ0F3SUJBZ0lVS2Vib0drZEJqenM5bllRbkVQTWp0VG56YTVrd0NnWUlLb1pJemowRUF3SXcKYURFTE1Ba0dBMVVFQmhNQ1ZWTXhGekFWQmdOVkJBZ1REazV2Y25Sb0lFTmhjbTlzYVc1aE1SUXdFZ1lEVlFRSwpFd3RJZVhCbGNteGxaR2RsY2pFUE1BMEdBMVVFQ3hNR1JtRmljbWxqTVJrd0Z3WURWUVFERXhCbVlXSnlhV010ClkyRXRjMlZ5ZG1WeU1CNFhEVEU0TVRFeE9URTNNRE13TUZvWERURTVNVEV4T1RFM01EZ3dNRm93ZmpFTE1BaKQTFVRUJoTUNWVk14RnpBVkJnTlZCQWdURGs1dmNuUm9JRU5oY205c2FXNWhNUlF3RWdZRFZRUUtFd3RJZVhCbApjbXhsWkdkbGNqRXVNQXNHQTFVRUN4TUVkWE5sY2pBTEJnTlZCQXNUQkc5eVp6RXdFZ1lEVlFRTEV3dGtaWEJoCmNuUnRaVzUwTVRFUU1BNEdBMVVFQXhNSFlXUnRhVzR4Y0RCWk1CTUdCeXFHU000OUFnRUdDQ3FHU000OUF3RUgKQTBJQUJLbjUwdEU5TmpZb0RFNDBqalh6RUJ2T2c3Y3RtOElRd0laMnRkS29iNEwwVVhKdSs1Tkt5S2dyUk9vbApWcjBmQmg5cWZWMjl4Nms0T2dmMFNiVklBZWlqZ2ZRd2dmRXdEZ1lEVlIwUEFRSC9CQVFEQWdlQU1Bd0dBMVVkCkV3RUIvd1FDTUFBd0hRWURWUjBPQkJZRUZOYWFkV0VzcGp2Smk1akpiVktiS2M3ZU1wUmhNQjhHQTFVZEl3UVkKTUJhQUZMd2d1N0J3Uk9lQ2hzV2hWQWptMTdmalh1eVBNQ2NHQTFVZEVRUWdNQjZDSEdOb1lXNWtjbUZ6TFcxaQpjQzV5WVd4bGFXZG9MbWxpYlM1amIyMHdhQVlJS2dNRUJRWUhDQUVFWEhzaVlYUjBjbk1pT25zaWFHWXVRV1ptCmFXeHBZWFJwYjI0aU9pSnZjbWN4TG1SbGNHRnlkRzFsYm5ReElpd2lhR1l1Ulc1eWIyeHNiV1Z1ZEVsRUlqb2kKWVdSdGFXNHhjQ0lzSW1obUxsUjVjR1VpT2lKMWMyVnlJbjE5TUFvR0NDcUdTTTQ5QkFNQ0EwY0FNRVFDSURGeApDYzE1bDZUZ1dqYnhSZzlmNjczOGV0K0NZZ1I3VVpGR200VHdoQk5jQWlBNmtUMFFwbDV6WnBUN3BzM0dySXlVCmEydDRHSTQ5ZTdjUm5PMmdrSzl6Zz09Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K"
            ]
         },
         "enrollid": "peertls",
         "enrollsecret": "peertlspw",
         "csr": {
            "hosts": [
            ]
         }
      }
   }
}
```

--------------------------------

### Example: Get Logs from Console UI Container

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=kubernetes-deploying-blockchain-platform-25-behind-firewall

This is an example of how to retrieve logs specifically from the 'optools' container (console UI) of the IBM Blockchain Platform console pod. This command is useful for debugging issues related to the console's user interface or its communication with other components.

```bash
kubectl logs -f ibpconsole-55cf9db6cc-856nz console -n blockchain-project
```

--------------------------------

### Get Components Information using cURL

Source: https://www.ibm.com/docs/en/blockchain-platform/2.1_topic=how-using-blockchain-platform-apis

This snippet shows how to retrieve information about all components managed by your IBM Blockchain Platform console using a cURL GET request. It includes examples for different authentication methods (API key/secret and Bearer token) and console versions. The `-k` flag is used for insecure connections, and the `Content-Type` header should be set to `application/json`.

```curl
curl -X GET \
   https://d456fcd8ee0e4ddfb1ad9bf45986e546-optools.bp01.blockchain.cloud.ibm.com/ak/api/v2/components \
   -H 'Content-Type: application/json' \
   -H 'Authorization: Bearer eyJraWQ.....zJPsw
```

```curl
curl -X GET \
https://openshiftcluster.us-south.containers.appdomain.cloud:443/ak/api/v2/components \
   -H 'Content-Type: application/json' \
   -u kO25ME32Nu8TikR_:buYImbg0co8SxneoBWzHueYwrf9Xhg5f \
   -k
```

--------------------------------

### Get Console URL using OpenShift CLI

Source: https://www.ibm.com/docs/en/blockchain-platform/2.1_topic=platform-deploy-blockchain-213-prem-manually

This command retrieves the console URL from an OpenShift cluster. It requires the OpenShift CLI to be installed and configured. The output provides the necessary URL to access the IBM Blockchain Platform console.

```bash
oc get routes -n <PROJECT_NAME>
```

--------------------------------

### Initialize Local Docker Registry (Shell)

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=options-deploy-from-red-hat-marketplace-airgap-installation

Initializes the prerequisites for running a local Docker registry using `cloudctl case launch`. This action configures the registry settings, including host, user, password, and storage directory.

```shell
cloudctl case launch \
--case ${OFFLINECASE} \
--inventory ${ITEM} \
--action init-registry \
--args "--registry $PORTABLE_REGISTRY_HOST --user $PORTABLE_REGISTRY_USER --pass $PORTABLE_REGISTRY_PASSWORD --dir $PORTABLE_REGISTRY_PATH"
```

--------------------------------

### Ansible Playbook Console URL Output Example

Source: https://www.ibm.com/docs/en/blockchain-platform/2.1_topic=playbooks-deploy-service-from-ansible-playbook

This snippet shows the expected output from an Ansible playbook task that prints the IBM Blockchain Platform console URL upon successful installation. It indicates the task name, status, and the generated console URL.

```text
TASK [console : Print console URL] *************************************************************************************************************************************
ok: [localhost] => {
   "msg": "IBM Blockchain Platform console available at https://xm0507-ibp-console-console.ibp20openshifttestcluster-0defdaa0c51bd4a2dcb024eab4bf04a1-0001.us-south.containers.appdomain.cloud"
}

```

--------------------------------

### Configure Source Registry Credentials (Shell)

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=options-deploy-from-red-hat-marketplace-airgap-installation

This `cloudctl case launch` command configures the credentials for the source registry, which is typically the entitled registry. It uses the provided registry host, user, and password to establish the connection.

```shell
cloudctl case launch \
--case ${OFFLINECASE} \
--inventory ${ITEM} \
--action configure-creds-airgap \
--args "--registry ${SOURCE_REGISTRY} --user ${SOURCE_REGISTRY_USER} --pass ${SOURCE_REGISTRY_PASS}"
```

--------------------------------

### Generate Smart Contract Tests in Java

Source: https://www.ibm.com/docs/en/blockchain-platform/2.1_topic=applications-developing-smart-contracts-blockchain-developer-tools

This example outlines the process of generating test files for an instantiated smart contract. The generated tests can be in Java, suitable for Java projects. The IBM Blockchain Platform extension handles the installation of dependencies and building the test file.

```text
1. Ensure the smart contract is instantiated.
2. Right-click the smart contract in the Fabric Gateways pane.
3. Select "Generate Smart Contract Tests".
4. Choose Java.
```

--------------------------------

### Deploy and Verify PKCS11 Proxy Pod

Source: https://www.ibm.com/docs/en/blockchain-platform/2.1_topic=console-advanced-deployment-options

These commands deploy the PKCS11 proxy pod defined in `pod.yaml` to the `hsm` namespace and then describe the pod's status. The `describe` command helps verify if the pod has been scheduled, pulled the image, and started successfully, including checking probe results.

```bash
kubectl create -f pod.yaml -n hsm

```

```bash
kubectl describe pod pkcs11-proxy -n hsm

```

--------------------------------

### Generate Smart Contract Tests in JavaScript/TypeScript

Source: https://www.ibm.com/docs/en/blockchain-platform/2.1_topic=applications-developing-smart-contracts-blockchain-developer-tools

This example outlines the process of generating test files for an instantiated smart contract. The generated tests can be in JavaScript or TypeScript, suitable for Node.js projects. The IBM Blockchain Platform extension handles the installation of dependencies and building the test file.

```text
1. Ensure the smart contract is instantiated.
2. Right-click the smart contract in the Fabric Gateways pane.
3. Select "Generate Smart Contract Tests".
4. Choose JavaScript or TypeScript.
```

--------------------------------

### Build PKCS #11 Proxy Docker Image with SoftHSM

Source: https://www.ibm.com/docs/en/blockchain-platform/2.1_topic=console-advanced-deployment-options

This Dockerfile defines the steps to build a PKCS #11 proxy image. It first creates a builder stage to compile the proxy from source and install dependencies like git, make, and cmake. It then sets up the final image, copies the compiled proxy binaries, configures environment variables for the proxy socket and HSM library location, and includes an example configuration for SoftHSM, including its installation and initialization. This snippet is intended for Docker environments.

```docker
########## Build the pkcs11 proxy ##########
FROM registry.access.redhat.com/ubi8/ubi-minimal as builder
ARG ARCH=amd64

ARG VERSION=2032875

RUN microdnf install -y \
   git \
   make \
   cmake \
   openssl-devel \
   gcc;

RUN if [ "${ARCH}" == "amd64" ]; then ARCH="x86_64"; fi && \
   rpm -ivh https://kojipkgs.fedoraproject.org/packages/libseccomp/2.4.2/2.fc30/${ARCH}/libseccomp-2.4.2-2.fc30.${ARCH}.rpm && \
   rpm -ivh https://kojipkgs.fedoraproject.org/packages/libseccomp/2.4.2/2.fc30/${ARCH}/libseccomp-devel-2.4.2-2.fc30.${ARCH}.rpm


RUN git clone https://github.com/SUNET/pkcs11-proxy && \
   cd pkcs11-proxy && \
   git checkout ${VERSION} && \
   cmake . && \
   make && \
   make install

########## FINAL image - Build softhsm client ##########

FROM registry.access.redhat.com/ubi8/ubi-minimal
ARG ARCH=amd64

RUN microdnf install -y \
   shadow-utils \
   && microdnf clean all \
   && groupadd -g 7051 ibp-user \
   && useradd -u 7051 -g ibp-user -s /bin/bash ibp-user \
   && mkdir /licenses \
   && if [ "${ARCH}" == "amd64" ]; then ARCH="x86_64"; fi \
   && rpm -ivh https://kojipkgs.fedoraproject.org/packages/libseccomp/2.4.2/2.fc30/${ARCH}/libseccomp-2.4.2-2.fc30.${ARCH}.rpm \
   && microdnf remove shadow-utils \
   && microdnf clean all;

COPY --from=builder /usr/local/bin/pkcs11-daemon /usr/local/bin/pkcs11-daemon
COPY --from=builder /usr/local/lib/libpkcs11-proxy.so.0.1 /usr/local/lib/libpkcs11-proxy.so.0.1
COPY --from=builder /usr/local/lib/libpkcs11-proxy.so.0 /usr/local/lib/libpkcs11-proxy.so.0
COPY --from=builder /usr/local/lib/libpkcs11-proxy.so /usr/local/lib/libpkcs11-proxy.so

ENV PKCS11_DAEMON_SOCKET="tcp://0.0.0.0:2345"
#ENV PKCS11_PROXY_TLS_PSK_FILE="/tls.psk"
EXPOSE 2345

### YOUR HSM LIBRARY BUILD GOES HERE ###

ENV LIBRARY_LOCATION="/usr/lib64/softhsm/libsofthsm.so"

### YOUR HSM LIBRARY BUILD ENDS HERE ###

### EXAMPLE CONFIGURATION FOR SOFTHSM ###

ENV SLOT 0
ENV LABEL test
ENV PIN 5678
ENV SO_PIN 5678
ENV ARCH x86_64
ENV DEBUG_OUTPUT 1

RUN microdnf update && \
   microdnf install -y shadow-utils && \
   rpm -ivh https://kojipkgs.fedoraproject.org/packages/softhsm/2.5.0/4.fc30/${ARCH}/softhsm-2.5.0-4.fc30.${ARCH}.rpm
RUN mkdir -p /var/lib/softhsm/tokens/
RUN softhsm2-util --slot ${SLOT} --init-token --label ${LABEL} --pin ${PIN} --so-pin ${SO_PIN}

### EXAMPLE CONFIGURATION FOR SOFTHSM ENDS HERE###

### ###

CMD ["sh", "-c", "pkcs11-proxy $LIBRARY_LOCATION -^{*}"]

```

--------------------------------

### Complete Blockchain Platform Configuration File Example

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=how-using-blockchain-platform-apis

This JSON object represents a completed configuration file for the IBM EN Blockchain Platform. It includes enrollment details for both a component and its TLS, specifying hostnames, ports, names, certificates, and enrollment credentials. This file can be used with the 'Create an ordering service' or 'Create a peer' API.

```json
{
   "enrollment": {
      "component": {
         "cahost": "9.30.20.70",
         "caport": "32129",
         "caname": "ca",
         "catls": {
            "cacert": "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUNGakNDQWIyZ0F3SUJBZ0lVTmlUbkdTandSdU1JVXhpWGcwMGZZWXhPSndJd0NnWUlLb1pJemowRUF3SXcKYURFTE1Ba0dBMVVFQmhNQ1ZWTXhGekFWQmdOVkJBZ1REazV2Y25Sb0lFTmhjbTlzYVc1aE1SUXdFZ1lEVlFRSwpFd3RJZVhCbGNteGxaR2RsY2pFUE1BMEdBMVVFQ3hNR1JtRmljbWxqTVJ0Z3WURWUVFERXhCbVlXSnlhV010ClkyRXRjMlZ5ZG1WeU1CNFhEVEU0TVRFeE5qRTJNVEF3TUZvWERUTXpNVEV4TWpFMk1UQXdNRm93YURFTE1Ba0cKQTFVRUJoTUNWVk14RnpBVkJnTlZCQWdURGs1dmNuUm9JRU5oY205c2FXNWhNUlF3RWdZRFZRUUtFd3RJZVhCbApjbXhsWkdkbGNqRVBNQTBHQTFVRUN4TUdSbUZpY21sak1Sa3dGd1lEVlFRREV4Qm1ZV0p5YVdNdFkyRXRjMlZ5CmRtVnlNRmt3RXdZSEtvWkl6ajBDQVFZSUtvWkl6ajBEQVFjRFFnQUU1dlBucDJUNTdkY2hTOGRLNExsMFJRZEEKd284RmJsMzBPcnBGdWFHUld5TFl4eGcxcVFTemhUY3hTcGtHZjh3a1FzVDVFb01lSWcrRytldjBOU01FUTZORgpNRU13RGdZRFZSMFBBUUgvQkFRREFnRUdNQklHQTFVZEV3RUIvd1FJTUFZQkFmOENBUUV3SFFZRFZSME9CQllFCkZMd2d1N0J3Uk9lQ2hzV2hWQWptMTdmalh1eVBNQW9HQ0NxR1NNNDlCQU1DQTBjQU1FUUNJR0FCRmNSdXhtSkIKY3c4OTJJOXhPS3YxVmYyT0JHZUh5N2pFQzRBRm5najFBaUJqdHFvdjBXMXdxZjhwcGttYkxIQkJoWW1vS3ZqRwo4bDQyeVQ5bWYxWVQrZz09Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K
         },
         "enrollid": "peer1",
         "enrollsecret": "peer1pw",
         "admincerts": [
            "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUMz RENDQW9PZ0F3SUJBZ0lVS2Vib0drZEJqenM5bllRbkVQTWp0VG56YTVrd0NnWUlLb1pJemowRUF3SXcKYURFTE1Ba0dBMVVFQmhNQ1ZWTXhGekFWQmdOVkJBZ1REazV2Y25Sb0lFTmhjbTlzYVc1aE1SUXdFZ1lEVlFRSwpFd3RJZVhCbGNteGxaR2RsY2pFUE1BMEdBMVVFQ3hNR1JtRmljbWxqTVJrd0Z3WURWUVFERXhCbVlXSnlhV010ClkyRXRjMlZ5ZG1WeU1CNFhEVEU0TVRFeE9URTNNRE13TUZvWERURTVNVEV4T1RFM01EZ3dNRm93ZmpFTE1BaKQTFVRUJoTUNWVk14RnpBVkJnTlZCQWdURGs1dmNuUm9JRU5oY205c2FXNWhNUlF3RWdZRFZRUUtFd3RJZVhCbApjbXhsWkdkbGNqRXVNQXNHQTFVRUN4TUVkWE5sY2pBTEJnTlZCQXNUQkc5eVp6RXdFZ1lEVlFRTEV3dGtaWEJoCmNuUnRaVzUwTVRFUU1BNEdBMVVFQXhNSFlXUnRhV040Y0RCWk1CTUdCeXFHU000OUFnRUdDQ3FHU000OUF3RUgKQTBJQUJLbjUwdEU5TmpZb0RFNDBqalh6RUJ2T2c3Y3RtOElRd0laMnRkS29iNEwwVVhKdSs1Tkt5S2dyUk9vbApWcjBmQmg5cWZWMjl4Nms0T2dmMFNiVklBZWlqZ2ZRd2dmRXdEZ1lEVlIwUEFRSC9CQVFEQWdlQU1Bd0dBMVVkCkV3RUIvd1FDTUFBd0hRWURWUjBPQkJZRUZOYWFkV0VzcGp2Smk1akpiVktiS2M3ZU1wUmhNQjhHQTFVZEl3UVkKTUJhQUZMd2d1N0J3Uk9lQ2hzV2hWQWptMTdmalh1eVBNQ2NHQTFVZEVRUWdNQjZDSEdOb1lXNWtjbUZ6TFcxaQpjQzV5WVd4bGFXZG9MbWxpYlM1amIyMHdhQVlJS2dNRUJRWUhDQUVFWEhzaVlYUjBjbk1pT25zaWFHWXVRV1ptCmFXeHBZWFJwYjI0aU9pSnZjbWN4TG1SbGNHRnlkRzFsYm5ReElpd2lhR1l1Ulc1eWIyeHNiV1Z1ZEVsRUlqb2kKWVdSdGFXNHeD229zSW1obUxsUjVjR1VpT2lKMWMyVnlJbjE5TUFvR0NDcUdTTTQ5QkFNQ0EwY0FNRVFDSURG
         Q2MxNWw2VGd3SmJ4Umc5ZjY3MzhlK0NZZ1I3VVpGR200VHdoQk5jQWlBNmtUMFFwbDV6WnBUN3BzM0dySXlVCmEydDRHSTQ5ZTdjUm5PMmdrSzl6Z3c9PQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg==
         ]
      },
      "tls": {
         "cahost": "9.30.20.70",
         "caport": "32129",
         "caname": "tlsca",
         "catls": {
            "cacert": "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUNGakNDQWIyZ0F3SUJBZ0lVTmlUbkdTandSdU1JVXhpWGcwMGZZWXhPSndJd0NnWUlLb1pJemowRUF3SXcKYURFTE1Ba0dBMVVFQmhNQ1ZWTXhGekFWQmdOVkJBZ1REazV2Y25Sb0lFTmhjbTlzYVc1aE1SUXdFZ1lEVlFRSwpFd3RJZVhCbGNteGxaR2RsY2pFUE1BMEdBMVVFQ3hNR1JtRmljbWxqTVJrd0Z3WURWUVFERXhCbVlXSnlhV010ClkyRXRjMlZ5ZG1WeU1CNFhEVEU0TVRFeE5qRTJNVEF3TUZvWERUTXpNVEV4TWpFMk1UQXdNRm93YURFTE1Ba0cKQTFVRUJoTUNWVk14RnpBVkJnTlZCQWdURGs1dmNuUm9JRU5oY205c2FXNWhNUlF3RWdZRFZRUUtFd3RJZVhCbApXhsWkdkbGNqRVBNQTBHQTFVRUN4TUdSbUZpY21sak1Sa3dGd1lEVlFRREV4Qm1ZV0p5YVdNdFkyRXRjMlZ5CmRtVnlNRmt3RXdZSEtvWkl6ajBDQVFZSUtvWkl6ajBEQVFjRFFnQUU1dlBucDJUNTdkY2hTOGRLNExsMFJRZEEKd284RmJsMzBPcnBGdWFHUld5TFl4eGcxcVFTemhUY3hTcGtHZjh3a1FzVDVFb01lSWcrRytldjBOU01FUTZORgpNRU13RGdZRFZSMFBBUUgvQkFRREFnRUdNQklHQTFVZEV3RUIvd1FJTUFZQkFmOENBUUV3SFFZRFZSME9CQllFCkZMd2d1N0J3Uk9lQ2hzV2hWQWptMTdmalh1eVBNQW9HQ0NxR1NNNDlCQU1DQTBjQU1FUUNJR0FCRmNSdXhtSkIKY3c4OTJJOXhPS3YxVmYyT0JHZUh5N2pFQzRBRm5najFBaUJqdHFvdjBXMXdxZjhwcGttYkxIQkJoWW1vS3ZqRwo4bDQyeVQ5bWYxWVQrZz09Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K
         },
         "enrollid": "peertls",
         "enrollsecret": "peertlspw",
         "csr": {
            "hosts": [
            ]
         }
      }
   }
}
```

--------------------------------

### Check Docker Installation Command

Source: https://www.ibm.com/docs/en/blockchain-platform/2.1_topic=playbooks-getting-started-ansible-blockchain-platform

This command verifies if Docker is installed on the machine. The output will display the Docker version if it's installed, otherwise, it indicates that Docker needs to be installed.

```bash
docker --version
```

--------------------------------

### Build Docker Image for PKCS #11 Proxy with SoftHSM

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=reference-hsm-pkcs-11-proxy

This Dockerfile builds a PKCS #11 proxy image, incorporating SoftHSM drivers for testing. It installs build dependencies, clones and builds the pkcs11-proxy project, and then sets up the final image with necessary libraries and environment variables. The example configuration for SoftHSM is included but can be removed for other HSMs.

```docker
########## Build the pkcs11 proxy ##########
FROM registry.access.redhat.com/ubi8/ubi-minimal as builder
ARG ARCH=amd64

ARG VERSION=2032875

RUN microdnf install -y \
   git \
   make \
   cmake \
   openssl-devel \
   gcc;

RUN if [ "${ARCH}" == "amd64" ]; then ARCH="x86_64"; fi && \
   rpm -ivh https://kojipkgs.fedoraproject.org/packages/libseccomp/2.4.2/2.fc30/${ARCH}/libseccomp-2.4.2-2.fc30.${ARCH}.rpm && \
   rpm -ivh https://kojipkgs.fedoraproject.org/packages/libseccomp/2.4.2/2.fc30/${ARCH}/libseccomp-devel-2.4.2-2.fc30.${ARCH}.rpm


RUN git clone https://github.com/SUNET/pkcs11-proxy && \
   cd pkcs11-proxy && \
   git checkout ${VERSION} && \
   cmake . && \
   make && \
   make install

########## FINAL image - Build softhsm client ##########

FROM registry.access.redhat.com/ubi8/ubi-minimal
ARG ARCH=amd64

RUN microdnf install -y \
   shadow-utils \
   && microdnf clean all \
   && groupadd -g 7051 ibp-user \
   && useradd -u 7051 -g ibp-user -s /bin/bash ibp-user \
   && mkdir /licenses \
   && if [ "${ARCH}" == "amd64" ]; then ARCH="x86_64"; fi \
   && rpm -ivh https://kojipkgs.fedoraproject.org/packages/libseccomp/2.4.2/2.fc30/${ARCH}/libseccomp-2.4.2-2.fc30.${ARCH}.rpm \
   && microdnf remove shadow-utils \
   && microdnf clean all;

COPY --from=builder /usr/local/bin/pkcs11-daemon /usr/local/bin/pkcs11-daemon
COPY --from=builder /usr/local/lib/libpkcs11-proxy.so.0.1 /usr/local/lib/libpkcs11-proxy.so.0.1
COPY --from=builder /usr/local/lib/libpkcs11-proxy.so.0 /usr/local/lib/libpkcs11-proxy.so.0
COPY --from=builder /usr/local/lib/libpkcs11-proxy.so /usr/local/lib/libpkcs11-proxy.so

ENV PKCS11_DAEMON_SOCKET="tcp://0.0.0.0:2345"
# ENV PKCS11_PROXY_TLS_PSK_FILE="/tls.psk"
EXPOSE 2345

### YOUR HSM LIBRARY BUILD GOES HERE ###

ENV LIBRARY_LOCATION="/usr/lib64/softhsm/libsofthsm.so"

### YOUR HSM LIBRARY BUILD ENDS HERE ###

### EXAMPLE CONFIGURATION FOR SOFTHSM ###

ENV SLOT 0
ENV LABEL test
ENV PIN 5678
ENV SO_PIN 5678
ENV ARCH x86_64
ENV DEBUG_OUTPUT 1

RUN microdnf update && \
   microdnf install -y shadow-utils && \
   rpm -ivh https://kojipkgs.fedoraproject.org/packages/softhsm/2.5.0/4.fc30/${ARCH}/softhsm-2.5.0-4.fc30.${ARCH}.rpm
RUN mkdir -p /var/lib/softhsm/tokens/
RUN softhsm2-util --slot ${SLOT} --init-token --label ${LABEL} --pin ${PIN} --so-pin ${SO_PIN}

### EXAMPLE CONFIGURATION FOR SOFTHSM ENDS HERE###

### ###

CMD ["sh", "-c", "pkcs11-proxy $LIBRARY_LOCATION - "]

```

--------------------------------

### Initialize Local Docker Registry for IBM Blockchain Platform

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=options-deploy-from-red-hat-marketplace-airgap-installation

This command uses the `cloudctl` CLI to initialize the prerequisites for running a Docker registry. It requires the case file, inventory item, and arguments specifying the registry host, user, password, and directory for storing images.

```shell
cloudctl case launch \
--case ${OFFLINECASE} \
--inventory ${ITEM} \
--action init-registry \
--args "--registry $PORTABLE_REGISTRY_HOST --user $PORTABLE_REGISTRY_USER --pass $PORTABLE_REGISTRY_PASSWORD --dir $PORTABLE_REGISTRY_PATH"


```

--------------------------------

### Fetch and Vendor Go Smart Contract Dependencies

Source: https://www.ibm.com/docs/en/blockchain-platform/2.5_topic=started-deploy-smart-contract-network

Fetches the necessary dependencies and prepares them for installation on a Fabric v2.x peer. This command ensures that all required modules are downloaded and vendored, enabling the smart contract to run correctly.

```bash
go mod tidy
go mod vendor

```

--------------------------------

### Navigate to Magnetocorp Application Directory

Source: https://www.ibm.com/docs/en/blockchain-platform/2.1_topic=tutorials-creating-applications

Changes the directory to the application code folder for the 'magnetocorp' organization. This is where you will prepare the application dependencies.

```bash
cd organization/magnetocorp/application
```
Tokens:
Raw