Help Center > > Getting Started> Quick Purchase of a BCS Service and Resources

Quick Purchase of a BCS Service and Resources

Updated at: Jun 19, 2019 GMT+08:00

HUAWEI CLOUD BCS provides a quick purchase method. Configurations of a BCS service and the resources it requires are integrated on the same page for purchase. You do not need to subscribe to the resources (such as clusters and cloud hosts) required by the service in advance to deploy a blockchain network. This method reduces the need of jumping between pages, helping you quickly subscribe to services.

Next, an example consortium blockchain will be deployed to describe BCS service deployment using the quick purchase method.

Account Registration

  1. Log in to the HUAWEI CLOUD website at
  2. Click Register in the upper right corner of the page.

    Complete the registration as prompted.

  3. Move the pointer to the user name in the upper right corner, and select My Account from the drop-down list.
  4. On the Account Info page, click Authenticate to the right of Authentication Status.

    Complete real-name authentication as prompted.

Service Authorization

BCS services must be deployed on Cloud Container Engine (CCE) clusters. CCE is a highly scalable, high-performance managed Kubernetes service, supporting Docker containers. With CCE, you can easily deploy, manage, and scale out containerized applications on HUAWEI CLOUD. If you are a newly registered tenant, go to the CCE console for service authorization (as shown in the following figure). If you do not perform the authorization, cluster creation will fail during BCS service deployment.

Service Deployment

  1. Log in to the BCS console, and click Buy BCS Service and Resources in the upper right corner.

  2. Set the parameters on the displayed page.

    • Billing Mode: Two options are available, yearly/monthly and pay per use. For example, select Pay per use.
    • Region: Select the region where the blockchain infrastructure is located. You are advised to select the same region as the service application system. For example, you can select CN North-Beijing1.
    • BCS Service Name: The value can contain a maximum of 4-24 characters, including letters, digits, and hyphens (-). It must not start with a hyphen (-). For example, enter bcs-ysq.
    • Edition: The BCS provides the basic, professional, and premium editions. For details about the differences between the editions, see Edition Specifications. For example, select Professional.
    • Blockchain Type: A private blockchain is used only by the tenant that deploys the BCS service. A consortium blockchain can be used by the initiator and the tenants that the initiator invites. For example, select Consortium.
      Figure 1 Parameter configuration (1)
    • Consensus Mechanism: The supported mechanisms for blockchain nodes reaching consensus include Solo (for testing), fast Byzantine fault tolerance (FBFT), and Kafka (crash fault tolerant). They differ in feature and application scenarios. For details, see Functions. For example, select FBFT.
    • Enable Data Aging on Orderers: When the amount of data on an orderer reaches a threshold, the system automatically deletes the earliest data to prevent exceptions caused by insufficient storage space. This function is available if Consensus Mechanism is set to Kafka (CFT). For example, select No.
    • Security Mechanism: Select the encryption algorithm used to ensure data security. The Elliptic Curve Digital Signature Algorithm (ECDSA) and Chinese cryptographic algorithms are supported. For example, select ECDSA.
    • Version: Specify the BCS service version. (Usually only one version is available, which is the latest version.)
    • Blockchain Mgmt. Initial Password: Set the password for the user admin to log in to the blockchain management page.
      Figure 2 Parameter configuration (2)
    • Peer Organization: Create three peer organizations xxx1, xxx2, and xxx3 each with two peers.
    • Number of Orderers: If the FBFT ordering service is used, four orderers are configured.
    • Disk Capacity of Peer Organization: The disks are used to store ledger data on peers. For example, set it to 40 GB.
    • Ledger Storage: Multiple types of databases can be used for ledger storage. For details about the differences, see the tips on the BCS service purchase page. For example, select File database (goleveldb).
      Figure 3 Parameter configuration (3)
    • Channel Configuration: Channels isolate business in a consortium blockchain. Business participants (some or all of the organizations in a consortium) are channel members. Each channel can be regarded as a sub-chain and corresponds to one ledger. For example, create a channel named testchannel, and add the peer organizations xxx1, xxx2, and xxx3 to the channel.
      Figure 4 Parameter configuration (4)
    • Cluster: BCS services are deployed in clusters. You can use an existing cluster or create a new one. For example, select Enable automatic creation to create a new cluster.
    • AZ: Select an availability zone (AZ) where the cloud server resides, for example, AZ1.
    • Cloud Server Specifications: Select the specifications of the cloud server in the cluster, for example, 2 vCPUs | 4 GB.
    • Cloud Server Quantity: For example, set it to 1.
    • High Availability: If you have high requirements on system reliability, purchase a high-availability cloud server. For example, select No.
    • Cloud Server Login Method: Passwords and key pairs are supported for login to the cloud server. For example, select Password.
    • Password of Root User: Set the password of the root user for login to the cloud server.
      Figure 5 Parameter configuration (5)

  3. Click Next, confirm the configuration, and click Submit.

    Wait for several minutes. After a message indicating successful installation is displayed, check the status of the service and organizations. If they are Normal, the BCS service deployment is completed.

    Figure 6 Successful deployment

Follow-up Operations

After deploying a BCS service, you need to perform the following operations:

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?

Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel