IBM Middleware Design Solutions.

Install IBM Blockchain Platform: Develop for the dev environment on your local machine. you would be able to develop and test with a complete local dev environment, including Hyperledger Composer, Hyperledger Fabric, CLI tools, IDE extension, a REST server, and app generator.

You need to install these tools before you attempt to install IBM Blockchain Platform: Develop

Instructions for Mac OS:

Install nvm and Apple Xcode

Install Node
On macOS, you've got two options for a C++ compiler: the full XCode application or the stand-alone Command Line Tools portion of Xcode.

Open your terminal of choice

Very first step is install the VM on your machine, so that you could be able to run your target operating system as per your choice.



After starting the VM go to your port forwarding setting as below and set the port forwarding on NAT for the ports used if you want access the datapower developer interface on your local browser.



Next step is to pull down the DataPower docker image from Github/DockerHub
Login to your docker container and run the below command to pull the latest docker image

docker pull ibmcom/datapower:latest

Check the installed imaged on your docker by running the below command (you can download the MQ image as well in the same way)



Next step is to start the docker container:

docker run -it \

   -v $PWD/config:/drouter/config \

   -v $PWD/local:/drouter/local \

   -e DATAPOWER_ACCEPT_LICENSE=true \

   -e DATAPOWER_INTERACTIVE=true \

   -p 9090:9090 \

   -p 9022:22 \

   -p 5554:5554 \

   -p 8000-8010:8000-8010 \

   --name idg \

   ibmcom/datapower

1. Now enable the Datapower Web GUI development interface that has to be accessed on browser.

2.  configure; web-mgmt 0 9090 9090;

Now if you need to start it again then you need to start and attach the image that you created idg

docket start idg

docker attach idg

Now open the browser and type the url https://localhost:9090 and login to the Datapower Web GUI. 

default username : admin 
default password : admin

You are done Cheers 👍



Copy a remote file (using - Concatenation operator)
     ssh abc@sysloggerserver1.linuxnix.com: /var/ftp/pub/webadmin/debian/read    abc@sysloggerserver2.persistent.co.in:/opt/oradba/debadmin/logic/abc/
 
'&&' –Logical AND operator
execute second command, if the first command runs successfully
    ping -c1 abc.com && ssh abc@abc.com
    example: Check if a folder exists or not. If it's not present, create it
    [ ! -d /var/temp ] && mkdir /var/temp
    Example: Create folder, if the folder creation is successful, then only change the directory.
    mkdir abc && cd abc
 
|| –Logical OR operator
    Example: Create a folder if the folder does not exits.
    [ -d /var/temp ] || mkdir /var/temp
    Example: Ping to a machine and let users know if it's not reachable in a meaning full way.
    ping -c1 google.com &> /dev/null || echo “There is some problem with network, please connect your network admin"
 
&& and || operator use case
    Example: Check if a file exists or not. If it exists inform user it exists otherwise create it.
    [-f /var/temp.txt] && echo "file exist" || touch /var/temp.txt
    Example:Check if my previous command executed successfully or not pwd /home/surendra  
    [ $? -eq 0 ] && echo "Yes, $? command successfully executed" || echo “pwd command failed"

| — PIPE operator
output of first command as an input to second command
    Example: Count no of files/folder located in a folder
    ls -l | wc -l
    Example: Display all the partition names in the system.
    df -m | awk '{print $1}'     //  -m is to check space in MB
    Example: to count no of partitions:
    df |wc -l
 
! -NOT operator (Negation operator)
    Example:Remove all the files, which are not a .doc file.
      ls | grep -v doc | xargs rm -rf or rm -rf *.{xls, txt, pdf}
      better way to achieve this: rm !(*.doc)
      Example: Move all the files expect .doc files to /opt
      mv !(*.doc) /opt/
   
{ } –Command combination operator
combine two or more commands to be executed depending on the previous command
    Example:  Check if /opt/temp.txt exists or not?
    [-f /opt/temp.txt] && echo "file exits" || {"The file does not exist"; touch /opt/temp.txt}
 
() –Precedence operator
execute command in precedence order
( caommand1 && command2 ) || ( command3 && command4 )

Service is running or not in Linux
    Method 1: Using service command
    $service servicename status
    Method 2: Using init.d scripts which are located in /etc/init.d folder
    /etc/init.d/cron status

List file with soft link
 ls -lrt | grep ^l    // ^ character is a special regular expression which means start of line
 find . -type l
 find . -maxdepth 1 -type l

 Count occurrence of a word
    $ grep -c "Error" logfile.txt
 
Printing lines before and after of matching word
    $ grep --context=6 error logfile.txt or grep -C 6 "Error" logfile.txt
 
Pattern using egrep and regular expression
    $ egrep 'Error|Exception' logfile.txt

Search patterns in gzip files using zgrep
    $ zgrep -i Error *.gz
 
Search whole word in a file using grep
    $grep -W Error logfile.txt
 
More control, use `\<' and `\>' to match the start and end of words
    $ grep 'ERROR>' *

Display files names which contains given word 
    $ grep -l ERROR *.log

Option to display lines numbers
    $ grep -n ERROR logfile.txt

includes a recipe with a statement
include_recipe anothercookbook::somerecipe

must include the following line
depends "anothercookbook"

AWS OpsWorks stores custom JSON in the following locations: You can declare custom JSON at the deployment, layer, and stack levels.

On Linux instances:

    /var/chef/runs/run-ID/attribs.json

    /var/chef/runs/run-ID/nodes/hostname.json
   
    run-ID is a unique ID that AWS OpsWorks assigns to each Chef run on an instance, and hostname is the instance's hostname.
   
   
To access custom JSON from Chef recipes, use standard Chef node syntax.
    {
  "state": "visible"
  }
  syntax:  node[:attribute][:child_attribute][...]
Ex: Chef::Log.info("********** The app's initial state is '#{node['state']}' **********")
stack name: node[:opsworks][:stack][:name].
Note

Custom JSON is limited to 80 KB.


To run custom recipe on opsworks stack layer.
Change to the Recipes tab, enter each custom recipe in the appropriate event field and click + to add it to the list.
Specify a recipe as follows: cookbook::somerecipe (omit the .rb extension)

To run a custom recipe manually, it must be in one of your custom cookbooks but does not have to be assigned to a lifecycle event.
When you run a recipe manually, AWS OpsWorks installs the same deploy attributes that it does for a Deploy event.
To manually run recipes on stack instances:
    On the Stack page, click Run command. For Command, select Execute Recipes.
    Enter the recipes to be run in the Recipes to execute box by using the standard cookbookname::recipename format
    add a custom JSON object that defines custom attributes that will be merged into the stack configuration and deployment attributes that are installed on the instances
    nder Instances, select the instances on which AWS OpsWorks should run the recipes.
   
   

Issue:
Issue with setting up a new repos on local workstation, while trying to push the code to remote git repository.
Stack trace looks like:
        Permission denied (publickey). fatal: Could not read from remote repository.



How it could be resolved:  



Now I check the keys under ~/.ssh

What logs should I look into for troubleshooting?

The agent installation log is at /var/log/awslogs-agent-setup.log
The agent log is at /var/log/awslogs.log


Make sure AWS configuration is configured on the running instance. It is not configured If you see the below error:

Recipe : Recipes are nothing but the simple ruby code to manage the system (Nodes). Each recipe is mapped to a provider and Provider completes the action with required steps. And then resources get processed. This phase is called execution phase.


Resources: Each system has multiple components and each component is handle by resource, so resource is component configuration policy
It could be a file, cronjob, service, package
 A resource comes with four component :   A type, A name, Attributes, Actions
  So structure would be :
   type "name" do
    attribute "value"
    action :action_type
 end
 Note: Every action has its default value, example: package resource default action is :install
            package "httpd"  equivalent to =>   package "httpd" do
            action :install
           end
Here, package is a type and httpd is a name.

Lets look at some actions
Action
:install               Does the installation of the resource
:nothing  It defines a resource that does nothing. 
Resource example with attribute:
service "httpd" do
action :start
                                                        retries 3
  ignore_failure true
end
Resource of type service and name is httpd will get started as per the defined action. If service is not getting started then still your chef run will not fail as per the defined attribute ignore_failure.


Cookbook: bundle all the recipes and store on chef server

Provider: To make sure that resources are handled in right manner, so there are different providers for different resources

When we right a code to install a package then provider is chosen according to the target platform. And platform is chosen by Ohai. Ohai is a ruby gem installed with chef itself.

Running the Ohai command on my machine for reference:



chef-client: it handled the process of recipes (cookbbok) in two phases.
                    First Phase: All the recipes are added in run_list  would be added in container
                    Second Phase: All the libraries are loaded with all dependencies. this is called        
                    compilation phase




Guard Attributes: Guard attributes are basically defined to check weather the desired state is present or not for the Chef resource. If the desire state is already presents then chef resource does nothing for the same resource.
it would be a string or a block of ruby code as a value
Block of ruby code may return true or false
String as a value may return 0 (means exit status) 

   
     Attribute
not_if if true, dont execute the resource
only_if if true, then execute the resource

And we can use the argument with these attributes as below:


 _____________________________________________________________________

Next part is coming soon .....