WebSphere Application ServerV9.0 & v9.0.5.

16

Basic Linux Commands and Course Details

Step1: Install VMWARE17 with KEY

Step2:Install Centos7
Step3: Practise Linux Commands
Step4: WebSphere Course
Step5:InstallationManager Installation Procedure
Step6:WebSphere ND Installation
Step7:Create Profile with Cmd and GUI Mode
Step 8:Creating the Clusters
Step9:Deploy the Application WAR/EAR/JAR File
Step10:IHS and Plugin installation and Integration mapping with Application.
Step11: Creating the DataSource.
Step12: SSL Certificate Installation Self -Signed or 3rd Party CA Certificates
Step13:Verbose Garbage collection
Step14:OOM Issues related Concepts
Step15:TLS version change Concepts
Step16:FixPack Installation 9.0.5.1 to 9.0.5.16

Step3: Practise Linux Commands

Directory Creation using mkdir command

Ex:- mkdir <DIR_NAME>

Creation of a File using touch command

Ex:- touch <File_Name.txt>

Search the file in the Server using Find Command

find / -name "*.txt"

Copy the file from one location to one location/Path

Ex:- cp <File_Path1> <FilePath2>

Rename/Move the file

Ex: mv <Old FileName> <New_FileName>

mv abc 123
mv <old_Path> <New_Path>

Ex:- mv abc /home/wasadmin/ABC //moving the file//

Remove th file from the particular Location

rm -f <File_Name>

rm -Rf <File_Name/Directory>

File System of Linux:-

---------------------

/boot
/root
/opt
/var/
/usr/ etc....

change permissions of a file and ownership of the file

chmod -R 777 File_Name

chown -R wasadmin:wasadmin <File/FolderName>

R:4,W:2,X:1 ====>777

7===>OWNER
7===>USER
7====>OTHERS

Files copying from Server to Server using Two Ways

1.SCP
2.SFTP

SFTP :-

[root@localhost ~]# sftp wasadmin@192.168.121.153

The authenticity of host '192.168.121.153 (192.168.121.153)' can't be
established.
ECDSA key fingerprint is
SHA256:tXFbor73N1qxl0i1TC3zv/8mHzMjwdBYwCCYbZqfyWs.
ECDSA key fingerprint is
MD5:41:26:cf:a1:94:77:a5:35:c4:55:ac:9a:89:51:9c:fa.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.121.153' (ECDSA) to the list of known
hosts.
wasadmin@192.168.121.153's password:
Connected to 192.168.121.153.
sftp> get
/WEBSPHERE/IBM/softwares/IM_Binaries/agent.installer.linux.gtk.x86_6
4_1.9.0.20190715_0328.zip
Fetching
/WEBSPHERE/IBM/softwares/IM_Binaries/agent.installer.linux.gtk.x86_6
4_1.9.0.20190715_0328.zip to
agent.installer.linux.gtk.x86_64_1.9.0.20190715_0328.zip
/WEBSPHERE/IBM/softwares/IM_Binaries/agent.installer 100% 203MB
8.6MB/s 00:23
sftp>

chown user:group <File/Folder_Name>

change the Directory using cd

IBM WebSphere Application Server v9.0 and v9.0.5

InstallationManager Installation

Step 1:Create the folders IM WEBSPHERE HTTPSERVER

Step 2: Copy the files from local to Remote using winscp
Step 3: Change the Permission from root to wasadmin
Step 4: unzip IM.zip file using unzip IM.zip file

Findouting Offering ID:

Open vim.repository.xml we have get in offering ID

<?xml version='1.0' encoding='UTF-8'?>

<?repositoryDigest version='0.0.1'?>
<repositoryDigest>
 <repository>
<property name='LayoutPolicy' value='P1'/>
<property name='LayoutPolicyVersion' value='0.0.0.1'/>
<property
name='PLATFORMS_com.ibm.cic.agent~1.9.2008.20240227_0018'
value='os=linux,arch=x86_64'/>
<property name='RequireContext'
value='InstallKit:im.version=1.9.2.8,im.internal.version=1.9.2008.20240227
_0018,admin=install,user=userinst'/>
<offering id='com.ibm.cic.agent' version='1.9.2008.20240227_0018'>
<information name='%Offering.name' version='1.9.2.8'>
%Offering.description

Step 5: Installation of InstallationManager:

Step 5: run the below Command:

[wasadmin@wasserver tools]$ ./imcl install com.ibm.cic.agent -

InstallationDirectory /IM/IBM/InstallationManager/ -acceptLicense -sP -
repositories /IM/repository.config -dL /IM/IMShared/
25% 50% 75% 100%
------------------|------------------|------------------|------------------|
............................................................................
Installed com.ibm.cic.agent_1.9.2008.20240227_0018 to the
/IM/IBM/InstallationManager/eclipse directory.

WebSphere Installation v9.0

Step 1:
Go to the InstallationManager Path
IM Path: /IM/IBM/InstallationManager/eclipse/tools

Copy the WASv9.0 Binaries from local to Remote using Winscp

For Ex:-

[wasadmin@wasserver WEBSPHERE]$ mv WAS9.tar WAS9

[wasadmin@wasserver WEBSPHERE]$ cd WAS9/
[wasadmin@wasserver WAS9]$ tar -xvf WAS9.tar

Step 2: Findouting OfferingID’s:

Ex:-
[wasadmin@wasserver WAS9]$ cd /IM/IBM/InstallationManager/eclipse/tools/
[wasadmin@wasserver tools]$ ./imcl listAvailablePackages -repositories
/WEBSPHERE/WAS9/WAS9/repository.config
com.ibm.java.jdk.v8_8.0.5041.20190924_1031
com.ibm.websphere.ND.v90_9.0.5001.20190828_0616
Step 3: Installation through offering ID’s
[wasadmin@wasserver tools]$ ./imcl install
com.ibm.websphere.ND.v90_9.0.5001.20190828_0616
com.ibm.java.jdk.v8_8.0.5041.20190924_1031 -InstallationDirectory
/WEBSPHERE/IBM/WebSphere/AppServer/ -acceptLicense -sP -
repositories
/WEBSPHERE/WAS9/WAS9/repository.config,/WEBSPHERE/WAS9/WA
S9/repository.config -dL /WEBSPHERE/IMShared/

[wasadmin@wasserver bin]$ pwd

/WEBSPHERE/IBM/WebSphere/AppServer/bin
[wasadmin@wasserver bin]$ cd /IM/IBM/InstallationManager/eclipse/tools/
[wasadmin@wasserver tools]$ ./imcl install
com.ibm.websphere.ND.v90_9.0.5001.20190828_0616
com.ibm.java.jdk.v8_8.0.5041.20190924_1031 -InstallationDirectory
/WEBSPHERE/IBM/WebSphere/AppServer/ -acceptLicense -sP -
repositories
/WEBSPHERE/WAS9/WAS9/repository.config,/WEBSPHERE/WAS9/WA
S9/repository.config -dL /WEBSPHERE/IMShared/
25% 50% 75% 100%
------------------|------------------|------------------|------------------|
............................................................................
Installed com.ibm.websphere.ND.v90_9.0.5001.20190828_0616 to the
/WEBSPHERE/IBM/WebSphere/AppServer/ directory.
Installed com.ibm.java.jdk.v8_8.0.5041.20190924_1031 to the
/WEBSPHERE/IBM/WebSphere/AppServer/ directory.
[wasadmin@wasserver tools]$

HistroryInfo
Verifying JAVA Version

[wasadmin@wasserver bin]$ ./java -version

java version "1.8.0_221"
Java(TM) SE Runtime Environment (build 8.0.5.41 - pxa6480sr5fp41-
20190919_01(SR5 FP41))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References
20190911_427071 (JIT enabled, AOT enabled)
OpenJ9 - d581d49
OMR - ca4db84
IBM - 5cfdf9c)
JCL - 20190918_01 based on Oracle jdk8u221-b11
[wasadmin@wasserver bin]$ pwd
/WEBSPHERE/IBM/WebSphere/AppServer/java/8.0/jre/bin
[wasadmin@wasserver bin]$

Profiles Creation

[wasadmin@wasserver java]$ cd ../

[wasadmin@wasserver AppServer]$ cd bin
[wasadmin@wasserver bin]$ ./manageprofiles.sh -create -profileName Dmgr01
-profilePath /WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01/ -
templatePath
/WEBSPHERE/IBM/WebSphere/AppServer/profileTemplates/management/
-cellName Dmgr_Cell01 -nodeName Dmgr_Node01 -startingPort 19005 &

Verifying the Profile Success or not

Postinstall.log
cd /WEBSPHERE/IBM/WebSphere/AppServer/logs/mana
geprofiles/

tail -5f Dmgr_create.log

<date>2024-03-27T21:42:22</date>
<millis>1711555942349</millis>
<sequence>4193</sequence>
<logger>com.ibm.wsspi.profile.WSProfileCLI</logger>
<level>INFO</level>
<class>com.ibm.wsspi.profile.WSProfileCLI</class>
<method>invokeWSProfile</method>
<thread>1</thread>
<message>Returning with return code: INSTCONFSUCCESS</message>
</record>
</log>

Application Server Profile AppSrv01

Go to WAS_HOME/bin
Run the below Command : -
---------------------------------
./manageprofiles.sh -create -profileName AppSrv01 -profilePath
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv01/ -
templatePath
/WEBSPHERE/IBM/WebSphere/AppServer/profileTemplates/default/ -
cellName AppSrv_Cell01 -nodeName AppSrv_Node01 -serverName
wasserver -serverType APPLICATION_SERVER

Verify Profile is successfully created or not

------------------------------------------------------
[wasadmin@wasserver manageprofiles]$ pwd
/WEBSPHERE/IBM/WebSphere/AppServer/logs/manageprofiles
[wasadmin@wasserver manageprofiles]$
[wasadmin@wasserver manageprofiles]$ tail -5f AppSrv01_create.log
 <method>invokeWSProfile</method>
<thread>1</thread>
<message>Returning with return code: INSTCONFSUCCESS</message>
</record>
</log>
AppSrv02
[wasadmin@wasserver bin]$ ./manageprofiles.sh -create -profileName
AppSrv02 -profilePath
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv02/ -
templatePath
/WEBSPHERE/IBM/WebSphere/AppServer/profileTemplates/default/ -
cellName AppSrv_Cell02 -nodeName AppSrv_Node02 -serverName
wasserver -serverType APPLICATION_SERVER &
[1] 6163
[wasadmin@wasserver bin]$ INSTCONFSUCCESS: Success: Profile AppSrv02
now exists. Please consult
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv02/logs/About
ThisProfile.txt for more information about this profile.

[1]+ Done ./manageprofiles.sh -create -profileName AppSrv02 -

profilePath /WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv02/
-templatePath
/WEBSPHERE/IBM/WebSphere/AppServer/profileTemplates/default/ -
cellName AppSrv_Cell02 -nodeName AppSrv_Node02 -serverName
wasserver -serverType APPLICATION_SERVER
[wasadmin@wasserver bin]$

AppSrv03
[wasadmin@wasserver bin]$ ./manageprofiles.sh -create -profileName
AppSrv03 -profilePath
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv03/ -
templatePath
/WEBSPHERE/IBM/WebSphere/AppServer/profileTemplates/default/ -
cellName AppSrv_Cell03 -nodeName AppSrv_Node03 -serverName
wasserver -serverType APPLICATION_SERVER &
[1] 6548
[wasadmin@wasserver bin]$

INSTCONFSUCCESS: Success: Profile AppSrv03 now exists. Please consult

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv03/logs/About
ThisProfile.txt for more information about this profile.

Custom Profile

WAS_HOME/bin
Run the below Command:-
---------------------------------
[wasadmin@wasserver bin]$ ./manageprofiles.sh -create -profileName Custom1
-profilePath
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Custom01/ -
templatePath
/WEBSPHERE/IBM/WebSphere/AppServer/profileTemplates/managed/ -
cellName Custom_Cell01 -nodeName Custom_Node01

INSTCONFSUCCESS: Success: Profile Custom1 now exists. Please consult

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Custom01/logs/About
ThisProfile.txt for more information about this profile.

Federation v9.0

To start the Dmgr:-

[wasadmin@wasserver WebSphere]$ cd AppServer/profiles/Dmgr01/bin

[wasadmin@wasserver bin]$ ./startManager.sh

ADMU0116I: Tool information is being logged in file
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/startSe
rver.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3011E: Server launched but failed initialization. Server logs,
startServer.log, and other log files under
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr
should
contain failure information.
Port Conflict Issue
Modify the Port Number

[wasadmin@wasserver Dmgr_Node01]$ cp -pr serverindex.xml

serverindex.xml_bkp
[wasadmin@wasserver Dmgr_Node01]$ vim serverindex.xml
[wasadmin@wasserver Dmgr_Node01]$ pwd
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/Dmg
r_Cell01/nodes/Dmgr_Node01
[wasadmin@wasserver Dmgr_Node01]$

Changed the Port Number

-------------------------------
<specialEndpoints xmi:id="NamedEndPoint_15"
endPointName="STATUS_LISTENER_ADDRESS">
<endPoint xmi:id="EndPoint_15" host="wasserver" port="9454"/>
</specialEndpoints>
</serverEntries>
</serverindex:ServerIndex>

Dmgr Starting Error

Started Dmgr
Solution:
Cpu utilization is full,Increased RAM 2 GB and HostName verify

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNo
de.log
[wasadmin@wasserver bin]$ cat /etc/hosts
127.0.0.1
::1
192.168.88.129 wasserver
[wasadmin@wasserver bin]$

Federation AppSrv01 to Dmgr01

[wasadmin@wasserver bin]$ ./addNode.sh wasserver 19008

ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/addNo
de.log
ADMU0128I: Starting tool with the AppSrv01 profile
CWPKI0308I: Adding signer alias "root_1" to local keystore
"ClientDefaultTrustStore" with the following SHA digest:
D7:BC:D5:8E:B9:0A:E1:2C:BA:63:65:1E:4A:A5:A5:9C:AF:54:0B:48
ADMU0001I: Begin federation of node AppSrv_Node01 with Deployment
Manager at
wasserver:19008.
ADMU0009I: Successfully connected to Deployment Manager Server:
wasserver:19008
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: wasserver
ADMU2010I: Stopping all server processes for node AppSrv_Node01
ADMU0512I: Server wasserver cannot be reached. It appears to be stopped.
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: AppSrv_Node01
ADMU0014I: Adding node AppSrv_Node01 configuration to cell: Dmgr_Cell01
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0018I: Launching Node Agent process for node: AppSrv_Node01
ADMU0020I: Reading configuration for Node Agent process: nodeagent
ADMU0022I: Node Agent launched. Waiting for initialization status.
ADMU0030I: Node Agent initialization completed successfully. Process id is:
4368
ADMU0300I: The node AppSrv_Node01 was successfully added to the
Dmgr_Cell01
cell.

ADMU0306I: Note:
ADMU0302I: Any cell-level documents from the standalone Dmgr_Cell01
configuration have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the Dmgr_Cell01 Deployment
Manager with
values from the old cell-level documents.

ADMU0306I: Note:
ADMU0304I: Because -includeapps was not specified, applications installed on
the standalone node were not installed on the new cell.
ADMU0307I: You might want to:
ADMU0305I: Install applications onto the Dmgr_Cell01 cell using wsadmin
$AdminApp or the Administrative Console.

ADMU0003I: Node AppSrv_Node01 has been successfully federated.

[wasadmin@wasserver bin]$

Federation AppSrv02 to Dmgr01

[wasadmin@wasserver bin]$ ./addNode.sh wasserver 19008
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv02/logs/addNo
de.log
ADMU0128I: Starting tool with the AppSrv02 profile
CWPKI0308I: Adding signer alias "root_1" to local keystore
"ClientDefaultTrustStore" with the following SHA digest:
D7:BC:D5:8E:B9:0A:E1:2C:BA:63:65:1E:4A:A5:A5:9C:AF:54:0B:48
ADMU0001I: Begin federation of node AppSrv_Node02 with Deployment
Manager at
wasserver:19008.
ADMU0009I: Successfully connected to Deployment Manager Server:
wasserver:19008
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: wasserver
ADMU2010I: Stopping all server processes for node AppSrv_Node02
ADMU0512I: Server wasserver cannot be reached. It appears to be stopped.
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: AppSrv_Node02
ADMU0014I: Adding node AppSrv_Node02 configuration to cell: Dmgr_Cell01
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0018I: Launching Node Agent process for node: AppSrv_Node02
ADMU0020I: Reading configuration for Node Agent process: nodeagent
ADMU0022I: Node Agent launched. Waiting for initialization status.
ADMU0030I: Node Agent initialization completed successfully. Process id is:
4639

ADMU0300I: The node AppSrv_Node02 was successfully added to the

Dmgr_Cell01
cell.

ADMU0306I: Note:
ADMU0302I: Any cell-level documents from the standalone Dmgr_Cell01
configuration have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the Dmgr_Cell01 Deployment
Manager with
values from the old cell-level documents.

ADMU0306I: Note:
ADMU0304I: Because -includeapps was not specified, applications installed on
the standalone node were not installed on the new cell.
ADMU0307I: You might want to:
ADMU0305I: Install applications onto the Dmgr_Cell01 cell using wsadmin
$AdminApp or the Administrative Console.

ADMU0003I: Node AppSrv_Node02 has been successfully federated.

[wasadmin@wasserver bin]$

Federation AppSrv03 to Dmgr01

[wasadmin@wasserver bin]$ ./addNode.sh wasserver 19008
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv03/logs/addNo
de.log
ADMU0128I: Starting tool with the AppSrv03 profile
CWPKI0308I: Adding signer alias "root_1" to local keystore
"ClientDefaultTrustStore" with the following SHA digest:
D7:BC:D5:8E:B9:0A:E1:2C:BA:63:65:1E:4A:A5:A5:9C:AF:54:0B:48
ADMU0001I: Begin federation of node AppSrv_Node03 with Deployment
Manager at
wasserver:19008.
ADMU0009I: Successfully connected to Deployment Manager Server:
wasserver:19008
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: wasserver
ADMU2010I: Stopping all server processes for node AppSrv_Node03
ADMU0512I: Server wasserver cannot be reached. It appears to be stopped.
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: AppSrv_Node03
ADMU0014I: Adding node AppSrv_Node03 configuration to cell: Dmgr_Cell01
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0022I: Node Agent launched. Waiting for initialization status.
ADMU0300I: The node AppSrv_Node03 was successfully added to the
Dmgr_Cell01
cell.

ADMU0306I: Note:
ADMU0302I: Any cell-level documents from the standalone Dmgr_Cell01
configuration have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the Dmgr_Cell01 Deployment
Manager with
values from the old cell-level documents.

ADMU0306I: Note:
ADMU0304I: Because -includeapps was not specified, applications installed on
the standalone node were not installed on the new cell.
ADMU0307I: You might want to:
ADMU0305I: Install applications onto the Dmgr_Cell01 cell using wsadmin
$AdminApp or the Administrative Console.

ADMU0003I: Node AppSrv_Node03 has been successfully federated.

Federation Custom01 to Dmgr01
[wasadmin@wasserver bin]$ ./addNode.sh wasserver 19008
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Custom01/logs/addNo
de.log
ADMU0128I: Starting tool with the Custom1 profile
CWPKI0308I: Adding signer alias "root_1" to local keystore
"ClientDefaultTrustStore" with the following SHA digest:
D7:BC:D5:8E:B9:0A:E1:2C:BA:63:65:1E:4A:A5:A5:9C:AF:54:0B:48
ADMU0001I: Begin federation of node Custom_Node01 with Deployment
Manager at
wasserver:19008.
ADMU0009I: Successfully connected to Deployment Manager Server:
wasserver:19008
ADMU0507I: No servers found in configuration under:

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Custom01/config/cells
/Custom_Cell01/nodes/Custom_Node01/servers
ADMU2010I: Stopping all server processes for node Custom_Node01
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node: Custom_Node01
ADMU0014I: Adding node Custom_Node01 configuration to cell: Dmgr_Cell01
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0018I: Launching Node Agent process for node: Custom_Node01
ADMU0020I: Reading configuration for Node Agent process: nodeagent
ADMU0022I: Node Agent launched. Waiting for initialization status.
ADMU0030I: Node Agent initialization completed successfully. Process id is:
5416

ADMU0300I: The node Custom_Node01 was successfully added to the

Dmgr_Cell01
cell.

ADMU0306I: Note:
ADMU0302I: Any cell-level documents from the standalone Dmgr_Cell01
configuration have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the Dmgr_Cell01 Deployment
Manager with
values from the old cell-level documents.

ADMU0306I: Note:
ADMU0304I: Because -includeapps was not specified, applications installed on
the standalone node were not installed on the new cell.
ADMU0307I: You might want to:
ADMU0305I: Install applications onto the Dmgr_Cell01 cell using wsadmin
$AdminApp or the Administrative Console.

ADMU0003I: Node Custom_Node01 has been successfully federated.

[wasadmin@wasserver bin]$
Login Dmgr Console
Starting the Application Servers

Create the Server by using Custom Node

Starting the Custom Profile

Creating the Cluster Mechanism

Click Next
Click Next
Click Next
Click Finish and Save Configuration

Click the Particular Cluster > select Cluster Members in Additional Properties
press select all Cluster Mmebrs and Start the Operation below Screenshot
verify
After created the Cluster my Dmgr Console is very slow then stop the servers
First Start Dmgr increase the heap size 2GB for DMGR later stop Dmgr and
Start the Dmgr working Super Fast
App.Server have 4 are there 2 App.Servers 1 GB and remaining 2 Servers 2 GB
Given and clean Restarted the Servers.

Application Deployment
Go to Application > New Enterprose Application

Click Next

Click Next
Click Next

Select the application and select Cluster and apply

Click Next

Click Finish and Save the Master Configuration

Start the Application

Application Types > click WebSphere Enterprise Applications > select the
Application > start the Application
Application Started Successfully

Applicationis Deploying through Scripts

Go to WAS_HOME/profiles/Dmgr01/bin

WAS_HOME
=/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/

Run the below Command

[wasadmin@wasserver bin]$ ./wsadmin.sh -host wasserver -port 19008 -c

'$AdminApp install /WEBSPHERE/ShoppingCart.war -usedefaultbindings'
WASX7209I: Connected to process "dmgr" on node Dmgr_Node01 using SOAP
connector; The type of process is: DeploymentManager
WASX7327I: Contents of was.policy file:
//
// Template policy file for enterprise application.
// Extra permissions can be added if required by the enterprise application.
//
// NOTE: Syntax errors in the policy files will cause the enterprise application
FAIL to start.
// Extreme care should be taken when editing these policy files. It is advised
to use
// the policytool provided by the JDK for editing the policy files
// (WAS_HOME/java/jre/bin/policytool).
//

grant codeBase "file:${application}" {

};

grant codeBase "file:${jars}" {

};

grant codeBase "file:${connectorComponent}" {

};

grant codeBase "file:${webComponent}" {

};

grant codeBase "file:${ejbComponent}" {

};

ADMA5016I: Installation of ShoppingCart.war18e839fe20e started.

ADMA5058I: Application and module versions are validated with versions of
deployment targets.
ADMA5005I: The application ShoppingCart.war18e839fe20e is configured in
the WebSphere Application Server repository.
ADMA5005I: The application ShoppingCart.war18e839fe20e is configured in
the WebSphere Application Server repository.
ADMA5081I: The bootstrap address for client module is configured in the
WebSphere Application Server repository.
ADMA5053I: The library references for the installed optional package are
created.
ADMA5005I: The application ShoppingCart.war18e839fe20e is configured in
the WebSphere Application Server repository.
ADMA5001I: The application binaries are saved in
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01/wstemp/Scrip
t18e839fa4c8/workspace/cells/Dmgr_Cell01/applications/ShoppingCart.war
18e839fe20e.ear/ShoppingCart.war18e839fe20e.ear
ADMA5005I: The application ShoppingCart.war18e839fe20e is configured in
the WebSphere Application Server repository.
SECJ0400I: Successfully updated the application ShoppingCart.war18e839fe20e
with the appContextIDForSecurity information.
ADMA5005I: The application ShoppingCart.war18e839fe20e is configured in
the WebSphere Application Server repository.
ADMA5005I: The application ShoppingCart.war18e839fe20e is configured in
the WebSphere Application Server repository.
ADMA5113I: Activation plan created successfully.
ADMA5011I: The cleanup of the temp directory for application
ShoppingCart.war18e839fe20e is complete.
ADMA5013I: Application ShoppingCart.war18e839fe20e installed successfully.

[wasadmin@wasserver bin]$

After start the Application we will map the Modules later accessing the
Application
 Started All Applications
Cluster Member01 accessing Application

Cluster Member02 accessing Application

Cluster Member03 accessing Application

Cluster Member04 accessing Application

Shopping Cart Application Accessing Cluster Member01

Cluster Member04 accessing Application

ClusterMember02 accessing Application

Cluster Member03 accessing Application

IBM HTTPSERVER v9.0 Installation
Last login: Thu Mar 28 12:22:33 2024 from 192.168.88.1
[wasadmin@wasserver ~]$ cd /HTTPSERVER/
[wasadmin@wasserver HTTPSERVER]$ ls -ltrh
total 3.5G
-rw-r--r--. 1 wasadmin wasadmin 3.5G Aug 21 2023 IHS9.tar
[wasadmin@wasserver HTTPSERVER]$ mkdir IHS
[wasadmin@wasserver HTTPSERVER]$ mv IHS9.tar IHS
[wasadmin@wasserver HTTPSERVER]$ cd IHS/
[wasadmin@wasserver IHS]$ tar -xvf IHS9.tar

Go to IM_Path:

[wasadmin@wasserver IHS]$ cd /IM/IBM/InstallationManager/eclipse/tools/

Findouting Offering ID as shown Below:
---------------------------------------------------
[wasadmin@wasserver tools]$ ./imcl listAvailablePackages -repositories
/HTTPSERVER/IHS/IHS9/repository.config
com.ibm.java.jdk.v8_8.0.5041.20190924_1031
com.ibm.websphere.IHS.v90_9.0.5001.20190828_0616
[wasadmin@wasserver tools]$
Plugins Installations

Findouting OfferingID:
[wasadmin@wasserver tools]$ ./imcl listAvailablePackages -repositories
/WEBSPHERE/Plugins/Plugin9/repository.config
com.ibm.java.jdk.v8_8.0.5041.20190924_1031
com.ibm.websphere.PLG.v90_9.0.5001.20190828_0616
com.ibm.websphere.WCT.v90_9.0.5001.20190828_0616
[wasadmin@wasserver tools]$

WAS FixPackv9.0.5.16
Stop the All Servers take Environment backup

Findouting Offering ID:

[wasadmin@wasserver tools]$ ./imcl listAvailablePackages -repositories

/WEBSPHERE/FP16/9.0.5-WS-WAS-FP016/repository.config
com.ibm.websphere.BASE.v90_9.0.5016.20230609_0954
com.ibm.websphere.ILAN.v90_9.0.5016.20230609_0954
com.ibm.websphere.ND.v90_9.0.5016.20230609_0954
com.ibm.websphere.NDDMZ.v90_9.0.5016.20230609_0954
[wasadmin@wasserver tools]$

[wasadmin@wasserver tools]$ ./imcl listAvailablePackages -repositories

/WEBSPHERE/JAVA/repository.config
com.ibm.java.jdk.v8_8.0.8006.20230627_0542
[wasadmin@wasserver tools]$

HTTPServer and Plugins FixPackv9.0.5.16

[wasadmin@wasserver tools]$ ./imcl listAvailablePackages -repositories

/HTTPSERVER/IHS/repository.config; ./imcl listAvailablePackages -
repositories /WEBSPHERE/JAVA/repository.config
com.ibm.websphere.IHS.v90_9.0.5016.20230609_0954
com.ibm.websphere.PLG.v90_9.0.5016.20230609_0954
com.ibm.java.jdk.v8_8.0.8006.20230627_0542
[wasadmin@wasserver tools]$

WASv9.0 to 9.0.5.16

HTTPServer and Plugins v9.0 to 9.0.5.16

Memory Management Tool

 Enter following in “Generic JVM arguments” box

-Djavax.management.builder.initial=
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.port=9000

Findout jconsole Path for health check for all Servers

login as: wasadmin

wasadmin@192.168.88.129's password:
Activate the web console with: systemctl enable --now cockpit.socket

Last login: Thu Mar 28 17:05:11 2024 from 192.168.88.1

[wasadmin@wasserver ~]$ find /WEBSPHERE/IBM/WebSphere/AppServer/ -
name "jconsole"
/WEBSPHERE/IBM/WebSphere/AppServer/java/8.0/bin/jconsole
[wasadmin@wasserver ~]$
/WEBSPHERE/IBM/WebSphere/AppServer/java/8.0/bin/jconsole
After click Connect below Screenshot will be displayed
HTTPServer Creation using un managed Node

Click Next
Click Apply and save

Go to the Servers > ServerTypes > click webserver > select Un managed Node
IHS
Click Next

Click Next
Click Next

Click Finish and save changes the Master Configuration

Generate the Plugins and Propagate the Plugins

Genreate the Plugins through Script/backend
Go to DMGR/bin

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/

Run below command it will shows below format

[wasadmin@wasserver bin]$ cd
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/
[wasadmin@wasserver cells]$ ls -ltrh
total 20K
drwxr-xr-x. 20 wasadmin wasadmin 4.0K Mar 28 08:35 Dmgr_Cell01
-rw-r--r--. 1 wasadmin wasadmin 16K Mar 28 18:01 plugin-cfg.xml
[wasadmin@wasserver cells]$ cp -pr plugin-cfg.xml
/WEBSPHERE/IBM/WebSphere/Plugins/config/templates/
[wasadmin@wasserver cells]$

Copy Plugins File in suitable Location

Later enable load module 22 and paste the propagate plugins path

Go to IHS/bin

cd /HTTPSERVER/IBM/HTTPServer/conf/

backup of httpd.conf

[wasadmin@wasserver cells]$ cd /HTTPSERVER/IBM/HTTPServer/conf

[wasadmin@wasserver conf]$ cp -pr httpd.conf httpd.conf_bkp
[wasadmin@wasserver conf]$

After enable load module mapp the application with IHS

Press ok and save changes in Master Configuration
After that restart the all Cluster members

After restart the Cluster Members we will access application using 8082 Port
Number
IHS started Successfully
SSL Certificate Configuration In IBM WebSphere Application Server v9.0.5.16

Take backup of key.p12,trust.p12,security.xml

Below path:

[wasadmin@wasserver bin]$ cd
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/
Dmgr_Cell01/
[wasadmin@wasserver Dmgr_Cell01]$ pwd
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/Dmg
r_Cell01
[wasadmin@wasserver Dmgr_Cell01]$

Run the following Commands

cp -pr key.p12 key.p12_bkp

cp -pr trust.p12 trust.p12_bkp
cp -pr security.xml security.xml_bkp

Self Signed Certificate in IBM WebSphere Level

Extract original Certificate and create New Certificate and replace them with New
Certificate

Click Apply
CLICK Chained Certificate under New Button and Fill All Properties

Click apply and save the Configurations into DMGR

Select old certificate and press replace button and select checkbox Delete old
certificate after replacement

Later click apply and save the configurations as shown in below

But Self Signed Certificate creation as shown below

Click New button under default keystore > personal Certificates and fill all
properties as shown below
Third Party certificates renewal in default Truststore > signer certificates

Take the backup of old certificate and add the new certificates
root,intermediate,server certificate
Root ,Intermediate and server certificates added

Delete old certificates and save changes

Select old certificate and delete them

Verifying the certificates using openssl command
------------------------------------------------------------------

[wasadmin@wasserver SSL]$ openssl x509 -in

DigiCertTLSECCP384RootG5_Root_Certificate.crt -noout -dates
notBefore=Jan 15 00:00:00 2021 GMT
notAfter=Jan 14 23:59:59 2046 GMT
[wasadmin@wasserver SSL]$ openssl x509 -in
DigiCertG5TLSECCSHA3842021CA1-1_Intermediate_Certificate.crt -
noout -dates
notBefore=Apr 14 00:00:00 2021 GMT
notAfter=Apr 13 23:59:59 2031 GMT
[wasadmin@wasserver SSL]$ openssl x509 -in
G1CrossSignedDigiCertTLSRSA4096RootG5_Server_Certificate.crt -noout
-dates
notBefore=Sep 21 00:00:00 2022 GMT
notAfter=Nov 9 23:59:59 2031 GMT
[wasadmin@wasserver SSL]$

CSR Creation
SSL at HTTPServer Level

Created the KDB,RDB,STASH

[wasadmin@wasserver bin]$ ./gskcmd -keydb -create -db

/HTTPSERVER/IBM/HTTPServer/SSL/ihs.kdb -pw WebAS -expire 365 -
stash -type cms
[wasadmin@wasserver bin]$ cd ../
[wasadmin@wasserver HTTPServer]$ cd SSL
[wasadmin@wasserver SSL]$ ls -ltrh
total 12K
-rw-r--r--. 1 wasadmin wasadmin 144 Mar 28 21:29 ihs.kdb
-rw-r--r--. 1 wasadmin wasadmin 193 Mar 28 21:29 ihs.sth
-rw-r--r--. 1 wasadmin wasadmin 80 Mar 28 21:29 ihs.rdb
[wasadmin@wasserver SSL]$ chmod -R 775 *
[wasadmin@wasserver SSL]$ cd ../
[wasadmin@wasserver HTTPServer]$ cd bin
[wasadmin@wasserver bin]$

Create the Self-signed Certificate

export PATH=$PATH:/HTTPSERVER/IBM/HTTPServer/bin
[wasadmin@wasserver bin]$ ./gskcmd -cert -create -label ihscert -db
/HTTPSERVER/IBM/HTTPServer/SSL/ihs.kdb -pw WebAS -dn
"CN=Ihsserver,OU=Ganesh,O=Ganesh,L=Delhi,ST=Delhi,C=IN" -size
2048 -sig_alg SHA256WITHRSA
[wasadmin@wasserver bin]$

Setas default certificate

[wasadmin@wasserver bin]$ ./gskcmd -cert -setdefault -label ihscert -db

/HTTPSERVER/IBM/HTTPServer/SSL/ihs.kdb -pw WebAS
[wasadmin@wasserver bin]$

Verifying the certificates in kdb

[wasadmin@wasserver bin]$ ./gskcmd -cert -list -db
/HTTPSERVER/IBM/HTTPServer/SSL/ihs.kdb
A password is required to access the source key database.
Please enter a password:

Certificates in database /HTTPSERVER/IBM/HTTPServer/SSL/ihs.kdb:

ihscert
[wasadmin@wasserver bin]$

Take backup of httpd.conf and enable ssl load modules as shown below

[wasadmin@wasserver conf]$ cp -pr httpd.conf httpd.conf_bkp_latest

[wasadmin@wasserver conf]$ vim httpd.conf
[wasadmin@wasserver conf]$ vim httpd.conf

LoadModule ibm_ssl_module modules/mod_ibm_ssl.so

Listen 4443
SSLCheckCertificateExpiration 30
<VirtualHost *:4443>
SSLEnable
#Header always set Strict-Transport-Security "max-age=31536000;
includeSubDomains; preload"
</VirtualHost>
KeyFile /HTTPSERVER/IBM/HTTPServer/SSL/ihs.kdb
SSLDisable

Go to Console > Environment > VirtualHost>defaulthost> hostalias > add 4443

port number
Copy webserver keystore Directory

Add WAS Root certificate to Plugin-key.kdb

[wasadmin@wasserver HTTPServer]$ gskcmd -cert -add -label root-cert -file

/tmp/root.cer -db plugin-key.kdb -pw WebAS
[wasadmin@wasserver bin]$ more
/HTTPSERVER/IBM/HTTPServer/conf/httpd.conf|grep plugin
WebSpherePluginConfig
/WEBSPHERE/IBM/WebSphere/Plugins/config/HTTPServer/plugin-
cfg.xml
[wasadmin@wasserver bin]$ cd
/WEBSPHERE/IBM/WebSphere/Plugins/config/HTTPServer/
[wasadmin@wasserver HTTPServer]$ ls -ltr
total 24
-rw-r--r--. 1 wasadmin wasadmin 7500 Mar 29 07:52 plugin-cfg.xml
-rw-r--r--. 1 wasadmin wasadmin 10144 Mar 29 14:42 plugin-key.kdb
-rw-r--r--. 1 wasadmin wasadmin 193 Mar 29 14:42 plugin-key.sth

[wasadmin@wasserver bin]$ cd
/WEBSPHERE/IBM/WebSphere/Plugins/config/HTTPServer/
[wasadmin@wasserver HTTPServer]$ ls -ltr
total 24
-rw-r--r--. 1 wasadmin wasadmin 7500 Mar 29 07:52 plugin-cfg.xml
-rw-r--r--. 1 wasadmin wasadmin 10144 Mar 29 14:42 plugin-key.kdb
-rw-r--r--. 1 wasadmin wasadmin 193 Mar 29 14:42 plugin-key.sth
[wasadmin@wasserver HTTPServer]$ gskcmd -cert -add -label root-cert -filr
/tmp/root.cer -db plugin-key.kdb -pw WebAS

If GUI Mode not generated properly plugin-key.kdb,plugin-key.rdb,plugin-

key.stash use below command line

[wasadmin@localhost HTTPServer]$ pwd

/opt/IBM/WebSphere/Plugins/config/HTTPServer
[wasadmin@localhost HTTPServer]$ gskcmd -cert -add -label root-cert -file
/opt/root.cer -db /opt/IBM/WebSphere/Plugins/config/HTTPServer/plugin-
key.kdb -pw WebAS -type cms
[wasadmin@localhost HTTPServer]$ ls -ltrh
total 24K
-rw-r--r--. 1 wasadmin wasadmin 5.1K Apr 1 00:49 plugin-cfg.xml
-rw-r--r--. 1 wasadmin wasadmin 193 Apr 1 00:54 plugin-key.sth
-rw-r--r--. 1 wasadmin wasadmin 5.0K Apr 1 00:55 plugin-key.kdb
-rw-r--r--. 1 wasadmin wasadmin 80 Apr 1 00:55 plugin-key.rdb
[wasadmin@localhost HTTPServer]$

Clean restarting all Servers

----------------------------

Go to WAS_Home/profiles/Dmgr01/bin

run following Command later remove temp,wstemp,config/temp folders

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01/bin
[wasadmin@wasserver bin]$ ./clearClassCache.sh ; ./osgiCfgInit.sh
OSGi profile cache successfully cleaned for
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01.
OSGi server cache successfully cleaned for
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01/servers/dmgr.
[wasadmin@wasserver bin]$ cd ../
[wasadmin@wasserver Dmgr01]$ cd temp/
[wasadmin@wasserver temp]$ cd ../
[wasadmin@wasserver Dmgr01]$ rm -Rf temp
[wasadmin@wasserver Dmgr01]$ rm -Rf wstemp
[wasadmin@wasserver Dmgr01]$ cd config/
[wasadmin@wasserver config]$ rm -Rf temp
[wasadmin@wasserver config]$ cd ../
[wasadmin@wasserver Dmgr01]$ cd bin

[wasadmin@wasserver bin]$ ./startManager.sh

ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/sta
rtServer.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server dmgr open for e-business; process id is 2182
[wasadmin@wasserver bin]$

AppSrv01 Clean Restart

----------------------

[wasadmin@wasserver profiles]$ cd AppSrv01

[wasadmin@wasserver AppSrv01]$ rm -Rf temp/
[wasadmin@wasserver AppSrv01]$ rm -Rf wstemp
[wasadmin@wasserver AppSrv01]$ cd config/
[wasadmin@wasserver config]$ rm -Rf temp
[wasadmin@wasserver config]$ cd ../
[wasadmin@wasserver AppSrv01]$ cd bin
[wasadmin@wasserver bin]$ ./clearClassCache.sh ; ./osgiCfgInit.sh
OSGi profile cache successfully cleaned for
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv01.
OSGi server cache successfully cleaned for
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv01/servers/nod
eagent.
OSGi server cache successfully cleaned for
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv01/servers/Test
_Cl01.
OSGi server cache successfully cleaned for
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv01/servers/was
server.
[wasadmin@wasserver bin]$ ./syncNode.sh wasserver 19005
ADMU0116I: Tool information is being logged in file
 /WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/syncN
ode.log
ADMU0128I: Starting tool with the AppSrv01 profile
^C[wasadmin@wasserver bin]$ ./syncNode.sh wasserver 19008
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/syncN
ode.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU0401I: Begin syncNode operation for node AppSrv_Node01 with
Deployment
Manager wasserver: 19008
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node AppSrv_Node01 has been
synchronized with
Deployment Manager wasserver: 19008
[wasadmin@wasserver bin]$ ./startNode.sh
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/nodeag
ent/startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server nodeagent open for e-business; process id is 2959
[wasadmin@wasserver bin]$ ./startServer.sh wasserver
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/wasser
ver/startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: wasserver
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server wasserver open for e-business; process id is 3274
[wasadmin@wasserver bin]$ ./serverStatus.sh -all
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server
Status.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU0503I: Retrieving server status for all servers
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: wasserver
ADMU0506I: Server name: nodeagent
ADMU0506I: Server name: Test_Cl01
ADMU0508I: The Application Server "wasserver" is STARTED
ADMU0508I: The Node Agent "nodeagent" is STARTED
ADMU0509I: The Application Server "Test_Cl01" cannot be reached. It appears
to
 be stopped.
[wasadmin@wasserver bin]$ ./startServer.sh Test_Cl01
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/Test_C
l01/startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: Test_Cl01
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server Test_Cl01 open for e-business; process id is 3716
[wasadmin@wasserver bin]$

AppSrv02 Clean Restart

----------------------
[wasadmin@wasserver profiles]$ cd AppSrv02
[wasadmin@wasserver AppSrv02]$ rm -Rf temp wstemp
[wasadmin@wasserver AppSrv02]$ cd config/
[wasadmin@wasserver config]$ rm -Rf temp
[wasadmin@wasserver config]$ cd ../../
[wasadmin@wasserver profiles]$ cd AppSrv02/bin
[wasadmin@wasserver bin]$ ./syncNode.sh 192.168.88.129 19008
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv02/logs/syncN
ode.log
ADMU0128I: Starting tool with the AppSrv02 profile
ADMU0401I: Begin syncNode operation for node AppSrv_Node02 with
Deployment
Manager 192.168.88.129: 19008
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node AppSrv_Node02 has been
synchronized with
Deployment Manager 192.168.88.129: 19008
[wasadmin@wasserver bin]$ ./startNode.sh
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv02/logs/nodeag
ent/startServer.log
ADMU0128I: Starting tool with the AppSrv02 profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server nodeagent open for e-business; process id is 4080
[wasadmin@wasserver bin]$ ./serverStatus.sh -all
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv02/logs/server
Status.log
ADMU0128I: Starting tool with the AppSrv02 profile
ADMU0503I: Retrieving server status for all servers
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: wasserver
ADMU0506I: Server name: nodeagent
ADMU0506I: Server name: Test_Cl02
ADMU0509I: The Application Server "wasserver" cannot be reached. It appears
to
be stopped.
ADMU0508I: The Node Agent "nodeagent" is STARTED
ADMU0509I: The Application Server "Test_Cl02" cannot be reached. It appears
to
be stopped.
[wasadmin@wasserver bin]$ ./startServer.sh wasserver
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv02/logs/wasser
ver/startServer.log
ADMU0128I: Starting tool with the AppSrv02 profile
ADMU3100I: Reading configuration for server: wasserver
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server wasserver open for e-business; process id is 4423
[wasadmin@wasserver bin]$ ./startServer.sh Test_Cl02
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv02/logs/Test_C
l02/startServer.log
ADMU0128I: Starting tool with the AppSrv02 profile
ADMU3100I: Reading configuration for server: Test_Cl02
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server Test_Cl02 open for e-business; process id is 4691
[wasadmin@wasserver bin]$

AppSrv03 Clean Restart

---------------------
[wasadmin@wasserver profiles]$ cd AppSrv03
[wasadmin@wasserver AppSrv03]$ rm -Rf temp
[wasadmin@wasserver AppSrv03]$ rm -Rf wstemp
[wasadmin@wasserver AppSrv03]$ rm -Rf temp
[wasadmin@wasserver AppSrv03]$ cd config/
[wasadmin@wasserver config]$ rm -Rf temp
[wasadmin@wasserver config]$ cd ../../
[wasadmin@wasserver profiles]$ cd AppSrv03
[wasadmin@wasserver AppSrv03]$ cd bin
[wasadmin@wasserver bin]$ ./syncNode.sh 192.168.88.129 19008
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv03/logs/syncN
ode.log
ADMU0128I: Starting tool with the AppSrv03 profile
ADMU0401I: Begin syncNode operation for node AppSrv_Node03 with
Deployment
 Manager 192.168.88.129: 19008
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node AppSrv_Node03 has been
synchronized with
Deployment Manager 192.168.88.129: 19008
[wasadmin@wasserver bin]$ ./startNode.sh
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv03/logs/nodeag
ent/startServer.log
ADMU0128I: Starting tool with the AppSrv03 profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server nodeagent open for e-business; process id is 5099
[wasadmin@wasserver bin]$ ./serverStatus.sh -all
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv03/logs/server
Status.log
ADMU0128I: Starting tool with the AppSrv03 profile
ADMU0503I: Retrieving server status for all servers
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: wasserver
ADMU0506I: Server name: nodeagent
ADMU0506I: Server name: Test_Cl03
ADMU0509I: The Application Server "wasserver" cannot be reached. It appears
to
be stopped.
ADMU0508I: The Node Agent "nodeagent" is STARTED
ADMU0509I: The Application Server "Test_Cl03" cannot be reached. It appears
to
be stopped.
[wasadmin@wasserver bin]$ ./startServer.sh wasserver ; ./startServer.sh
Test_Cl03
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv03/logs/wasser
ver/startServer.log
ADMU0128I: Starting tool with the AppSrv03 profile
ADMU3100I: Reading configuration for server: wasserver
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server wasserver open for e-business; process id is 5478
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/AppSrv03/logs/Test_C
l03/startServer.log
ADMU0128I: Starting tool with the AppSrv03 profile
ADMU3100I: Reading configuration for server: Test_Cl03
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server Test_Cl03 open for e-business; process id is 5753
[wasadmin@wasserver bin]$ cd ../../
[wasadmin@wasserver profiles]$

Custom01 Clean Restart

----------------------
[wasadmin@wasserver profiles]$ cd Custom01
[wasadmin@wasserver Custom01]$ rm -Rf temp wstemp
[wasadmin@wasserver Custom01]$ cd config/
[wasadmin@wasserver config]$ rm -Rf temp
[wasadmin@wasserver config]$ cd ../../
[wasadmin@wasserver profiles]$ cd Custom01/bin
[wasadmin@wasserver bin]$ ./clearClassCache.sh ; ./osgiCfgInit.sh
OSGi profile cache successfully cleaned for
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Custom01.
OSGi server cache successfully cleaned for
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Custom01/servers/nod
eagent.
OSGi server cache successfully cleaned for
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Custom01/servers/Test
_Cl04.
OSGi server cache successfully cleaned for
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Custom01/servers/was
server.
[wasadmin@wasserver bin]$ ./syncNode.sh wasserver 19008
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Custom01/logs/syncN
ode.log
ADMU0128I: Starting tool with the Custom1 profile
ADMU0401I: Begin syncNode operation for node Custom_Node01 with
Deployment
Manager wasserver: 19008
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node Custom_Node01 has been
synchronized with
Deployment Manager wasserver: 19008
[wasadmin@wasserver bin]$ ./startNode.sh
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Custom01/logs/nodeag
ent/startServer.log
ADMU0128I: Starting tool with the Custom1 profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server nodeagent open for e-business; process id is 6432
[wasadmin@wasserver bin]$ cd ../
[wasadmin@wasserver Custom01]$ cd bin
[wasadmin@wasserver bin]$ ./serverStatus.sh -all
ADMU0116I: Tool information is being logged in file
 /WEBSPHERE/IBM/WebSphere/AppServer/profiles/Custom01/logs/server
Status.log
ADMU0128I: Starting tool with the Custom1 profile
ADMU0503I: Retrieving server status for all servers
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: nodeagent
ADMU0506I: Server name: wasserver
ADMU0506I: Server name: Test_Cl04
ADMU0508I: The Node Agent "nodeagent" is STARTED
ADMU0509I: The Application Server "wasserver" cannot be reached. It appears
to
be stopped.
ADMU0509I: The Application Server "Test_Cl04" cannot be reached. It appears
to
be stopped.
[wasadmin@wasserver bin]$ ./startServer.sh wasserver
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Custom01/logs/wasser
ver/startServer.log
ADMU0128I: Starting tool with the Custom1 profile
ADMU3100I: Reading configuration for server: wasserver
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server wasserver open for e-business; process id is 6904
[wasadmin@wasserver bin]$ ./startServer.sh Test_Cl04
ADMU0116I: Tool information is being logged in file

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Custom01/logs/Test_C
l04/startServer.log
ADMU0128I: Starting tool with the Custom1 profile
ADMU3100I: Reading configuration for server: Test_Cl04
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server Test_Cl04 open for e-business; process id is 7256
[wasadmin@wasserver bin]$

HTTPServer Start Command

------------------------

[wasadmin@wasserver bin]$ ./apachectl -k start

[wasadmin@wasserver bin]$ ps -ef|grep httpd
wasadmin 7709 1 3 07:34 ? 00:00:00
/HTTPSERVER/IBM/HTTPServer/bin/httpd -d
/HTTPSERVER/IBM/HTTPServer -k start
wasadmin 7710 7709 0 07:34 ? 00:00:00
/HTTPSERVER/IBM/HTTPServer/bin/httpd -d
/HTTPSERVER/IBM/HTTPServer -k start
wasadmin 7712 7709 0 07:34 ? 00:00:00
/HTTPSERVER/IBM/HTTPServer/bin/httpd -d
/HTTPSERVER/IBM/HTTPServer -k start
wasadmin 7713 7709 1 07:34 ? 00:00:00
/HTTPSERVER/IBM/HTTPServer/bin/httpd -d
/HTTPSERVER/IBM/HTTPServer -k start
wasadmin 7820 1687 0 07:34 pts/0 00:00:00 grep --color=auto httpd
[wasadmin@wasserver bin]$

Port Conflict issues command and Identification

-----------------------------------------------

what is port Conflict

---------------------
[wasadmin@wasserver bin]$ lsof -i:8082
[wasadmin@wasserver bin]$ lsof -i:443
[wasadmin@wasserver bin]$ lsof -i:4443
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
httpd 7709 wasadmin 4u IPv6 57147 0t0 TCP *:pharos (LISTEN)
httpd 7713 wasadmin 4u IPv6 57147 0t0 TCP *:pharos (LISTEN)
[wasadmin@wasserver bin]$ ps -ef|grep 7713
wasadmin 7713 7709 0 07:34 ? 00:00:00
/HTTPSERVER/IBM/HTTPServer/bin/httpd -d
/HTTPSERVER/IBM/HTTPServer -k start
wasadmin 7897 1687 0 07:37 pts/0 00:00:00 grep --color=auto 7713
[wasadmin@wasserver bin]$ ps -ef|grep 7709
wasadmin 7709 1 0 07:34 ? 00:00:00
/HTTPSERVER/IBM/HTTPServer/bin/httpd -d
/HTTPSERVER/IBM/HTTPServer -k start
wasadmin 7710 7709 0 07:34 ? 00:00:00
/HTTPSERVER/IBM/HTTPServer/bin/httpd -d
/HTTPSERVER/IBM/HTTPServer -k start
wasadmin 7711 7709 0 07:34 ? 00:00:00
/HTTPSERVER/IBM/HTTPServer/bin/sidd 0 20
HTTPSERVER/IBM/HTTPServer/logs/siddport 5534 OLOG OLOG
wasadmin 7712 7709 0 07:34 ? 00:00:00
/HTTPSERVER/IBM/HTTPServer/bin/httpd -d
/HTTPSERVER/IBM/HTTPServer -k start
wasadmin 7713 7709 0 07:34 ? 00:00:00
/HTTPSERVER/IBM/HTTPServer/bin/httpd -d
/HTTPSERVER/IBM/HTTPServer -k start
wasadmin 7905 1687 0 07:37 pts/0 00:00:00 grep --color=auto 7709
[wasadmin@wasserver bin]$

LDAP Configuration
Login with Dmgr
Take backup of security.xml by using cp -pr security.xml security.xml_bkp
OR Take backup od Dmgr_Cell
Last login: Fri Mar 29 06:52:46 2024 from 192.168.88.1
[wasadmin@wasserver ~]$ cd
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/
[wasadmin@wasserver cells]$ ls -ltrh
total 20K
-rw-r--r--. 1 wasadmin wasadmin 16K Mar 28 18:01 plugin-cfg.xml
drwxr-xr-x. 20 wasadmin wasadmin 4.0K Mar 29 06:40 Dmgr_Cell01
[wasadmin@wasserver cells]$ cp -pr Dmgr_Cell01 Dmgr_Cell01_bkp
[wasadmin@wasserver cells]$ cd Dmgr_Cell01
[wasadmin@wasserver Dmgr_Cell01]$ cp -pr security.xml security.xml_bkp
[wasadmin@wasserver Dmgr_Cell01]$

Login console using below url

http://192.168.88.129:19005/ibm/console

Dmgr AboutThisProfile.txt
[wasadmin@wasserver logs]$ cat AboutThisProfile.txt
Application server environment to create: Management
Location: /WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01
Disk space required: 30 MB
Profile name: Dmgr01
Make this profile the default: False
Node name: Dmgr_Node01
Cell name: Dmgr_Cell01
Host name: wasserver
Enable administrative security (recommended): False
Administrative console port: 19005 ====================== Console
Port Number without Security
Administrative console secure port: 19006 ======================
Console Port Number with Security

Management bootstrap port: 19007

Management SOAP connector port: 19008 === SOAP CONNECTOR PORT
NUMBER
Run Management as a service: False
[wasadmin@wasserver logs]$
Click Configure tab beside federated Repositories
Verify ping is working or not

Connect LDAP Server through AD EXPLORER

Hostname and Ip Address mapping hosts file :-
C:\Windows\System32\drivers\etc\
Click Add Repositories and Gives Primary administrative User name
Primary administrative User name: Administrator
And save the configuration

Click New Repository

Gives different distinguished Name and save the configurations

Click ok and save configuration

and go to security select federated Repositories and set as current as shown below
Click save the Master Configuration later Restart the Dmgr
Now Press Login Button
Creating user

click create and assign roles to the particular user

Click ok and save configuration login with same user

Login Successfully with the created User

DataSource
UserName:Ganesh
Password:71823456
Alias:ORACLE
Description:password is required
CLICK apply and save the configuration
select scope as a Cluster based on the Requirement we will select Scope and click
New
XA : Multiple Databases connect at single point of time
Connection Pool DataSource: Single Database connect at single point of time.
Connection pool DataSource: Non-XA DataSource

Later click Next

Click Next
Click Finish and Save the Configuration
Click Particular JDBC Provider under Addditional Properties DataSource

Click New
DataSource Name: (DataBase Name): Ganesh
JNDI: jdbc/DataSource Name
Url: jdbc:oracle:thin:@localhost:1521:XE
Click Next

Map the Alias into security

Click Next
Click Finish and Save Master Configuration

Select all Node agnets and press Restart all Servers on Node
Select DataSource Press Test Connection Button if any Errors verify nodeagent
logs i.e

SystemOut.log and SystemErr.log

Notes for DataSource:-

-------------------------------
DataSource
----------

What is the Database?

Ans:-

Database nothing but to store large amount of data to store in the database by
using records format record consists of Id (Primary Key),Name Varchar(30)
Salary VARCHAR(30),Joining Date Date,Reliving Date date;

What is a DataSource
--------------------

DataSource is an object that establish a connection between

APPLICATIONSERVER to Database with secure port number

Types of DataSource and its Def

-------------------------------

1.ORACLE
2.SQL
3.MYSQL
4.DB2
5.DERY BY

i.e. 1521 is ORACLE PORT //ORACLE 11G is the Database Client//

i.e. 1433 is SQL SERVER PORT

i.e 50,000 is DB2 PORT

i.e 1306 is MYSQL PORT

Steps for creating and configure the DATASOURCE

-----------------------------------------------

DRIVERS: THIK and THIN (Directly Establish the Connection)

JDBC,JNDI

JAVA DATABASE CONNECTIVITY

JAVA NAMING DIRECTORY INTERFACE

1. Contact Application Team for JNDI Details

JNDI: JDBC/DATASOURCE [DataSource Name:<DataBase UserName>]

2.Contact DB Team for UserName and Password (username & password of the
DB)

3.After getting the Details we need to configure

4.Download JAR File ojdbc6.jar or ojdbc8.jar and place it UNIVERSAL

DRIVER LOCATION (/opt/IBM/WebSphere/AppServer/universalDrivers/lib/)
5.Global security > JAAS - J2C authentication data >

under these location ADD Database Details (Alias,UserName,Password) click

Apply,Review and sync

6.Go to Resources > JDBC > Select Preferences (Cluster or based on the
Organization)>click NEW >

Properties:-
-----------

1.Scope

2.DataBase Type

3.Provider

4. Implementation type

5.Name [ Oracle JDBC Driver (XA) ] Multiple Database connect at a Time

6.Description [ Oracle JDBC Driver (XA) ]

Click Next >

Class Path: ${ORACLE_JDBC_DRIVER_PATH}/ojdbc6.jar

Universal Driver Path Location: ${ORACLE_JDBC_DRIVER_PATH}

[C:\Program Files (x86)\IBM\WebSphere\AppServer\universalDriver\lib]

Directory location for "ojdbc6.jar" which is saved as WebSphere variable

${ORACLE_JDBC_DRIVER_PATH}
------------------------------------------------------------------
C:\Program Files (x86)\IBM\WebSphere\AppServer\universalDriver\lib
------------------------------------------------------------------

Click Next > Summary > Finish > JDBC providers > Save > JDBC providers >
Synchronize changes with Nodes > OK

Creating the DataSource using the JDBC Povider :-

----------------------------------------------

JDBC providers > Oracle JDBC Driver (XA)

Additional Properties
Data sources
Properties:
----------

1.Scope : cells:cropcaptzsfpo_Cell01:clusters:Cropcaptzsfpo_Cluster

2.JDBC provider name : Oracle JDBC Driver (XA)

3.DataSource Name:Ganesh //Oracle UserName//

4.JNDI Name : JDBC/DATASOURCE NAME // JDBC/Ganesh//

5.Enter database specific properties for the data source

URL:jdbc:oracle:thin:@localhost:1521:XE
jdbc:oracle:thin:@192.168.121.1:1521:XE

6.Setup security aliases

7.Summary > Finish > JDBC providers > Oracle JDBC Driver (XA) > Data
sources > Save > JDBC providers > Oracle JDBC Driver (XA) > Data sources >
Synchronize changes with Nodes > click OK

8.Go to System Administartion > Node agents > select all Node agents > click
restart all Servers on Node

9.Wait till Action will be complete then go to Resources > JDBC

Provider>DataSources> select DataSource >Click Test_Connection

Success No issues > any errors you will see Node agent Logs

i.e. SystemOut.log and SystemErr.log under Nodeagents.

DataSource Test_Connection Results:-

-------------------------------------------------

The test connection operation for data source Ganesh on server nodeagent at
node Custom_Node01 was successful.
The test connection operation for data source Ganesh on server nodeagent at
node AppSrv_Node01 was successful.
The test connection operation for data source Ganesh on server nodeagent at
node AppSrv_Node02 was successful.

*** Prepared by AMIRINENI GANESH ***