Java SDK Demo

Preparations

Creating a BCS Instance

1. Log in to the BCS console.
2. Click Create BCS Instance in the upper right corner of the page.
3. Configure basic information about the BCS instance by referring to Table 1.
   

   To ensure that the demo runs properly, set the parameters as described in the following table.

   Table 1 Basic settings

   Parameter	Setting
   Region	Retain the default value.
   Enterprise Project	Select an existing enterprise project, for example, default. If the enterprise management service is not enabled, this parameter is unavailable.
   Instance Name	Enter java-sdk-demo.
   Edition	Select Professional. If OSCCA-published cryptographic algorithms must be used, select Enterprise.
   Blockchain Type	Select Private.
   Enhanced Hyperledger Fabric Version	v2.2
   Consensus Mechanism	Select Raft (CFT).
   Resource Access Initial Password	Enter a password.
   Confirm Password	-

4. Click Next: Configure Resources. Table 2 describes the resource parameters.

   Table 2 Resource configurations

   Parameter	Example
   Environment Resources	Select Custom.
   Cluster	Select Create a new CCE cluster.
   AZ	Select an AZ.
   Cross-AZ Scheduling	Select No.
   Use EIP of a CCE Node	Select Yes.

5. Click Next: Configure Blockchain. Table 3 describes the blockchain parameters.

   Table 3 Blockchain configurations

   Parameter	Example
   Blockchain Configuration	Select Custom.
   Blockchain Mgmt. Initial Password	If you do not enter a password here, the previously specified resource access initial password will be used.
   Confirm Password	-
   Volume Type	Select SFS Turbo or select another one as prompted.
   Storage Capacity of Peer Organization (GB)	Retain the default value.
   Ledger Storage	Select File database (GoLevelDB).
   Peer Organization	A peer organization named organization has been automatically created. Change the peer quantity to 1.
   Channel Configuration	The organization organization has been added to the channel automatically. Retain this default setting.
   Orderer Quantity	Retain the default value.
   Security Mechanism	Select ECDSA. NOTICE: The OSCCA-published cryptographic algorithms option is available. If you select this option, other modifications are required for the demo deployment. Pay attention to the descriptions of modifications.
   Configure Block Generation	Select No.
   Enable Support for RESTful API	Select No.

6. Click Next: Confirm.
7. Confirm the configurations and finish the creation process.

   Wait for several minutes. After a message is displayed indicating successful installation, check the status of the instance. If it is Normal, the deployment is completed.

Installing and Instantiating a Chaincode

1. Log in to the BCS console.
2. In the navigation pane on the left, click Instance Management.
3. Find the instance you just created and click Manage Blockchain to go to the Blockchain Management console.

4. On the login page, enter the username and password, and click Log In.
   

   The username is admin, and the password is the Blockchain Mgmt. Initial Password set when you created the BCS instance. If you have not set this password, use the resource access initial password.

5. Click in the upper left corner of the page.
   The parameters for chaincode installation are as follows.

   Table 4 Installation parameters

   Parameter	Setting
   Chaincode Name	Enter chaincode.
   Chaincode Version	Select 2.0.
   Ledger Storage	File database (goleveldb)
   Select All Peers	Check the box.
   Organization & Peer	Select peer-0.
   Language	Select Golang.
   Chaincode File	Chaincode_Go_Demo: To obtain it, go to the BCS console and click Use Cases. Download the example Go chaincode in the Java SDK Demo area.
   Chaincode Description	Enter a description of the chaincode.
   Code Security Check	This option is displayed only when the chaincode language is Golang. Enable this option to check chaincode security.

6. Click Install.
7. After installing the chaincode, click Instantiate in the Operation column of the chaincode list.
   The parameters for chaincode instantiation are as follows.

   Table 5 Instantiation parameters

   Parameter	Setting
   Chaincode Name	Enter chaincode.
   Channel	Select channel.
   Chaincode Version	Select 2.0.
   Initialization Function	Enter init.
   Chaincode Parameters	a,200,b,250
   Endorsement Policy	Select Endorsement from any of the following organizations.
   Endorsing Organizations	Select organization.
   Privacy Protection Configuration	Select No.

8. Click Instantiate.

   Wait for 2 to 3 minutes and refresh the page. Click View more in the Instantiation column to check the instantiation status.

Configuring the Application

1. Import the project.

   Obtain the project code and decompress it. To obtain the project code, go to the BCS console and choose Use Cases. Download the example Java chaincode in the Java SDK Demo area.

   Right-click the Eclipse page, and choose Import from the shortcut menu to import the project code file (Maven project) to Eclipse.

   

2. Download SDK configurations and certificates.
   1. On the Instance Management page, click Download Client Configuration on an instance card.
   2. Select SDK Configuration File and set the parameters as described in the following table.

      Table 6 SDK parameters

      Parameter	Description
      Chaincode Name	Enter chaincode. NOTICE: The chaincode name must be the same as the name specified during chaincode installation and instantiation.
      Certificate Root Path	Enter the path to the config folder of the javasdkdemo project. NOTICE: Change the backslashes (\) to slashes (/), for example, D:/javasdkdemo/config.
      Channel	Select channel.
      Organization & Peer	Select all peers in the channel.

      Select Orderer Certificate.

      Select Peer Certificates, select organization for Peer Organization, and select Administrator certificate.

   3. Click Download to download the SDK configuration file and the administrator certificates for the java-sdk-demo-orderer and organization organizations to the config directory in the demo project.

3. Copy and decompress the package.
4. Decompress demo-config.zip and copy the contents in the java-sdk-demo-orderer-admin-cert, organization-admin-cert, and sdk-config folders to the config directory in the demo project.

Deploying the Application

1. In the Maven project, find the Main.java file in the /javasdkdemo/src/main/java/handler/ directory, and change the file path in the following code of the Main class to the absolute path of the java-sdk-demo-sdk-config.yaml file. The path can be found in . Change the backslashes (\) to slashes (/).

   helper.setConfigCtx("E:/yourdir/.yaml");

   For example, change the path to helper.setConfigCtx("D:/javasdkdemo/config/java-sdk-demo-channel-sdk-config.yaml").

   

   Add the dependency upon fabric-sdk-java-1.4.1-jar-with-dependencies.jar in the lib folder of the project to pom.xml because OSCCA-published cryptographic algorithms and other cryptographic algorithms need to refer to the fabric-sdk dependency package. To add the dependency, remove the comments on the dependency as shown in the following figure. Otherwise, the project may not run properly.

   Figure 1 File details
   

2. Run the main function.

   Each time the command is successfully executed, the key-value pair <testuser,100> is saved to the blockchain. If you query key testuser, the value is 100. You can also view the transaction records in Block Browser.

   Figure 2 Transaction records