Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Step - by - step guide on how to Install Insights Enterprise - Business logic

 Prerequisite
  • Environment variable INSIGHTS_HOME and server-config.json. 
    • Windows: Server 2 - SetEnvVariables.bat
    • Linux: insights_first.sh
  • Java
  • Apache-Tomcat

Refer here for installation steps if required.

Assumption:

FABRIC_HOME will be used to refer to the directory where all the network related files are extracted

 Step1: Configuration

Create the file  blockchainConfig.json in $INSIGHTS_HOME/.InSights/ and make the necessary changes.

SampleblockchainConfig.json

  • The CA, peer, and user should be from the same org
  • The Eventhub is not available as a separate container but obtained by using the peer instance and so it can use the peer url
  • The user private key (ends with "_sk") can be found in FABRIC_HOME/ledger/ca/msp/keystore
  • The public key (pem) can be found in FABRIC_HOME/ledger/ca/msp/signcerts
  • Copy the user private key (ends with "_sk") and public key (pem) into any suitable directory (when moving between different machines/servers ensure these files are not corrupted) and provide their path
  • The USER_SER_PATH is a path for storing the serialized format of the user context which is generated from the user private key (ends with "_sk") and public key (pem)
  • Place the datamodel.json and Process.json files in any directory suitable and provide the path in blockchainConfig.json
 Step2: Run PlatformAuditEngine
  • Download the PlatformAuditEngine jar from (Nexus link here)
  • Run the downloaded jar using the command:
java -jar PlatformAuditEngine-<version>.jar

Example: java -jar PlatformAuditEngine-0.1.jar

  • If you want to run the jar as a background service instead, use the below command:
nohup java -jar PlatformAuditEngine-<version>.jar &

Example: nohup java -jar PlatformAuditEngine-0.1.jar &

  • The logs will be available at $INSIGHTS_HOME/logs/PlatformAuditEngine

Note

The server running PlatformAuditEngine must have the blockchainConfig.json file with the dependency files (datamodel.json, Process.json, private and public keys) in appropriate locations

 Step3: Run PlatformAuditService
  • git clone for below?
  • Copy the folders keystore, sign and static available under PlatformAuditService/src/main/resources/ into $INSIGHTS_HOME/.InSights/ 
  • Download the PlatformService war from (Nexus link here)
  • Move the war into webapps directory of apache-tomcat and restart tomcat
    • Use the following commands inside the apache-tomcat directory to restart
    • ./bin/shutdown.sh
    • ./bin/startup.sh

Note

The server running Apache Tomcat must have the blockchainConfig.json file with the dependency files (datamodel.json, Process.json, private and public keys) in appropriate locations

  • No labels