How to setup node and angular platform using

1. Download node js tar file. For instance to download node 22 version, navigate to https://nodejs.org/en/blog/release/v22.11.0 Click on the belo0w https://nodejs.org/dist/v22.11.0/node-v22.11.0-linux-x64.tar.xz 2. Copy the file to the linux instance, and from that folder untar the file. tar -xf node-v22.11.0-linux-x64.tar.xz 3. You will see a folder like node-v22.11.0-linux-x64. Setup the Export path of the node. 4. export PATH=/root/node/node-v22.11.0-linux-x64/bin:$PATH

Consumer related softwares

Paid versions Gravity write - AI driven for story generation 11Eleven labs - AI driven voice genereation for stories Adobe Express - for animation capcut, Clickchamp - for final vedio clips merge

Splunk and Sterling Integrator Integration

 Splunk Installation

rpm -i --prefix=/mnt/splunk2 splunk-8.2.2-87344edfcdb4-linux-2.6-x86_64.rpm

./splunk start --accept-license

Create the admin user - splunkadmin

Splunk DB Connect Manual Configuration

 

You can also install DB Connect by copying its directory into your Splunk Enterprise apps directory:

Download Splunk DB Connect and save it to a temporary location that you can access from your Splunk Enterprise instance.

Un-tar the download.

Move the splunk_app_db_connect directory into $SPLUNK_HOME/etc/apps.

Restart Splunk Enterprise (./mnt/splunk2/splunk/bin/splunk stop and then ./mnt/splunk2/splunk/bin/splunk start)

After you navigate to the Splunk DB Connect app, You may get "Cannot communicate with task server, please check your settings"

Setup the JRE Installation Path(JAVA_HOME) in the UI - 

Check If java is install by issuing java -version command. If not installed, download the latest tar.gz (jdk-8u202-linux-i586.tar.gz) package from Oracle java.

tar zxvf jdk-8u202-linux-i586.tar.gz

Change the permissions if required - chown -R root:root jdk1.8.0_202

Navigate to the JRE, notedown the path and enter it in the UI - /mnt/jdk1.8.0_202/jre

Download the corresponding driver. Here it is DB2.

Untar the file to see the folder - jdbc_sqlj

Copy or move the db2jcc4.jar file to the $SPLUNK_HOME/etc/apps/splunk_app_db_connect/drivers directory

Uninstall Splunk

rpm -qa | grep -i splunk

Then put the command rpm -e above_command_result

Example : rpm -e splunkforwarder-6.3.2-aaff59bb082c.x86_64

Splunk Data Retreival from database

Create a read only user on the database and record the identity credentials.

Navigate to Splunk UI->apps->splunk_app_db_connect->Configuration->Identities. Create the identity using the identity credentails of the read only user

Create the Connection

On the Data Lab -> Retrieve the data. Use cron expressions for Execution Frequency like for every 2 minutes polling  - */2 * * * *

Splunk Reports and Dashboards

To get the users created

index="edi" source="YFS_PERSON_INFO" sourcetype="database"  | transaction LAST_NAME, CREATETS, MODIFYTS  |  table FIRSTNAME, LAST_NAME, EMAILID, DEPARTMENT, CREATETS, MODIFYTS |   sort by CREATETS desc

MQ Installation

1. Create a group before the installation: 

For example to create a group named mqm with GID of 1010 you would type: groupadd -g 1010 mqm 

2. Create the mqm user and add the user to mqm group

useradd -u 1001 -g mqm -G mqm, root mqm 

3. sudo passwd mqm 

4. Add the below line to get sudo access.

vi /etc/sudoers

mqm     ALL=(ALL)       ALL

4. Check the maximum open files - sysctl fs.file-max 

If value is lesser than the below add the line in /etc/sysctl.conf fs.file-max = 524288 

5. Increase the file descriptors (from root user) 

vi /etc/security/limits.conf #add the below line

mqm hard nofile 10240 

mqm soft nofile 10240 

6. gunzip the tar file and then run. sudo tar -xvf IBM_MQ_9.1.5_LINUX_X86-64.tar.gz 

7.  You must be a root to accept the lincese. Please switch to root.

8. Change directory to MQServer and then Accept the license sudo ./mqlicense.sh 

9. sudo rpm -ivh MQ*.rpm

How to keep the IP address on linux on VMware

Good file looking like this /etc/sysconfig/network-scripts/ifcfg-eth0 TYPE="Ethernet" PROXY_METHOD="none" BROWSER_ONLY="no" BOOTPROTO="dhcp" DEFROUTE="yes" IPV4_FAILURE_FATAL="no" IPV6INIT="yes" IPV6_AUTOCONF="yes" IPV6_DEFROUTE="yes" IPV6_FAILURE_FATAL="no" IPV6_ADDR_GEN_MODE="stable-privacy" NAME="enp0s3" UUID="43558b3d-8a5d-4555-b105-c61eb883b0b1" DEVICE="enp0s3" ONBOOT="yes" ********************************************************* One more possibility /etc/sysconfig/network-scripts/ifcfg-(interface-name) To find your network interface name, you can use the following # nmcli con # vim /etc/sysconfig/network-scripts/ifcfg-enp0s3 TYPE="Ethernet" BOOTPROTO="none" NAME="enp0s3" IPADDR="192.168.20.150" NETMASK="255.255.255.0" GATEWAY="192.168.20.1" DEVICE="enp0s3" ONBOOT="yes" Then restart the NetworkManager with: # systemctl restart NetworkManager

Step by step process for installing Aspera Fasp.io gateway

Step by step process for installing Aspera Fasp.io gateway Follow the IBM page. I got all these steps from there - https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.con.doc/aspera_def_unixlinux.htm Download ASP_FASP.IO_GW_V1.0.1_LNX_EN.zip from IBM site and keep it available in the server Example: /opt/softwares/Aspera/ Unzip the file. Example: sudo unzip ASP_FASP.IO_GW_V1.0.1_LNX_EN.zip Use rpm file with yum install. Example: sudo yum install ./ibm-fasp.io-gateway-1.0.1-1.x86_64.rpm ........ ....... Installed size: 8.8 M Is this ok [y/d/N]: y Then it looks like the below. Running transaction test Transaction test succeeded Running transaction Installing : ibm-fasp.io-gateway-1.0.1-1.x86_64 1/1 Verifying : ibm-fasp.io-gateway-1.0.1-1.x86_64 1/1 Installed: ibm-fasp.io-gateway.x86_64 0:1.0.1-1 Complete! _________________________________________________________________________________________ Location of installed files: Executable: /usr/bin Default configuration files: /etc/fasp.io Documentation: /usr/share/fasp.io-gateway SystemD startup file: /etc/systemd/system/fasp.io-gateway.service ************************************************************************************************** Copied the below example from IBM Site only Example This example defines an Aspera gateway connection on two machines running Linux. The configuration is as follows: The IP address of the local gateway machine is 9.20.193.107. The IP address of the remote gateway machine is 9.20.192.115. The local queue manager is running on a machine with IP address 9.20.121.5. The remote queue manager is running on a machine with IP address 9.20.121.25. Both queue managers are listening on port 1414. The queue manager channel on the local queue manager is changed to connect to the local Aspera gateway using conname 9.20.193.107(1500). The queue manager channel on the remote queue manager is changed to connect to the remote Aspera gateway using conname 9.20.192.115(1500). Define an Aspera gateway connection on the local gateway machine: Install the Aspera gateway: rpm -ivh ibm-fasp.io-gateway-1.0.0_qa_48-1.x86_64.rpm Modify the gateway.toml file in the /etc/fasp.io directory that was created by the install. Edit it to set the local gateway definitions. [[bridge]] name = "Outbound" [bridge.local] protocol = "tcp" host = "9.20.193.107" port = 1500 [bridge.forward] protocol = "fasp" host = "9.20.192.115" port = 1600 [[bridge]] name = "Inbound" [bridge.local] protocol = "fasp" host = "9.20.193.107" port = 1600 [bridge.forward] protocol = "tcp" host = "9.20.121.5" port = 1414 Repeat the previous step to define an Aspera gateway connection on the remote gateway machine. Modify the gateway.toml file in the /etc/fasp.io directory that was created by the install. Edit it to set the remote gateway definitions: [[bridge]] name = "Outbound" [bridge.local] protocol = "tcp" host = "9.20.192.115" port = 1500 [bridge.forward] protocol = "fasp" host = "9.20.193.107" port = 1600 [[bridge]] name = "Inbound" [bridge.local] protocol = "fasp" host = "9.20.192.115" port = 1600 [bridge.forward] protocol = "tcp" host = "9.20.121.25" port = 1414 At each end of the connection, change the channel definition to connect to the port that the local gateway is listening on. Change the queue manager channel on the local queue manager to connect to the local Aspera gateway using conname 9.20.193.107(1500). Change the queue manager channel on the remote queue manager to connect to the remote Aspera gateway using conname 9.20.192.115(1500). Start the local gateway by running the following command on the local gateway machine: systemctl start fasp.io-gatewayCopy code Start the remote gateway by running the following command on the remote gateway machine: systemctl start fasp.io-gatewayCopy code Restart the channels. ************************************************************************************************************* In case if Queue manager and FASP gateway are on the same server. The configuration may look like below. Here local queue manager and FASP are on the same machine - 192.168.1.107. Similarly the remote FASP gateway is 192.168.1.108. [[bridge]] name = "Outbound" #connection from the local queue manager to the local fasp gateway [bridge.local] protocol = "tcp" host = "192.168.1.107" port = 1500 #from the local fasp gateway to the remote fasp gateway [bridge.forward] protocol = "fasp" host = "192.168.1.108" port = 1600 [[bridge]] name = "Inbound" #the connection from the remote fasp gateway to the local fasp gateway [bridge.local] protocol = "fasp" host = "192.168.1.107" port = 1600 #from the local gateway to the local queue manager. [bridge.forward] protocol = "tcp" host = "192.168.1.107" port = 1414 [[bridge]] name = "Outbound" [bridge.local] protocol = "tcp" host = "192.168.1.108" port = 1500 [bridge.forward] protocol = "fasp" host = "192.168.1.107" port = 1600 [[bridge]] name = "Inbound" [bridge.local] protocol = "fasp" host = "192.168.1.108" port = 1600 [bridge.forward] protocol = "tcp" host = "192.168.1.108" port = 1414

Linux setup on VMware

Setup Bridged Network adapter Select both boot and dvd iso files. rhel-server-7.7-x86_64-boot.iso rhel-server-7.7-x86_64-dvd.iso Select "Software Selection" select "Server with GUI" and other options

Select "Network & Hostname" Apply the changes

Stop firewall rules systemctl disable firewalld 

If not selected during installation then follow below

Type the following command 

to edit /etc/hostname using vi text 

editor: sudo vi /etc/hostname Delete the old name and setup new name. 

Example: cat /etc/hostname statebank 

Next Edit the /etc/hosts file: sudo nano /etc/hosts 

Replace any occurrence of the existing computer name with your new one 

 Example: cat /etc/hosts 127.0.0.1 statebank localhost.localdomain localhost4 localhost4.localdomain4 ::1 statebank localhost.localdomain localhost6 localhost6.localdomain6 

 Reboot the system to changes take effect: sudo 

reboot Good file looking like this 

/etc/sysconfig/network-scripts/ifcfg-eth0 TYPE="Ethernet" PROXY_METHOD="none" BROWSER_ONLY="no" BOOTPROTO="dhcp" DEFROUTE="yes" IPV4_FAILURE_FATAL="no" IPV6INIT="yes" IPV6_AUTOCONF="yes" IPV6_DEFROUTE="yes" IPV6_FAILURE_FATAL="no" IPV6_ADDR_GEN_MODE="stable-privacy" NAME="enp0s3" UUID="43558b3d-8a5d-4555-b105-c61eb883b0b1" DEVICE="enp0s3" ONBOOT="yes"