WebSphere Application Server

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 8.5.50.0 to 8.5.5.21

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 [email protected]

The authenticity of host '192.168.121.153 (192.168.121.153)'
can't be established.
ECDSA key fingerprint is
SHA256:tXFbor73N1qxl0i1TC3zv/8mHzMjwdBYwCCY
bZqfyWs.
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.
[email protected]'s password:
Connected to 192.168.121.153.
sftp> get
/WEBSPHERE/IBM/softwares/IM_Binaries/agent.installer
.linux.gtk.x86_64_1.9.0.20190715_0328.zip
Fetching
/WEBSPHERE/IBM/softwares/IM_Binaries/agent.installer
.linux.gtk.x86_64_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

1.InstallationManager Installation using wasadmin user

By using InstallationManager we will

Install/Update/Rollback/Modify/acceptLicense
1.Create a Folder IM

2.Copy InstallationManager zip file to the IM Folder

3.Unzip the IM Zip file using below Command

unzip
agent.installer.linux.gtk.x86_64_1.9.0.20190715_0328.zip

4.After unzip Successfully Completed we will run below

command

5. [wasadmin@localhost IM]$ ./userinstc -

InstallationDirectory
/WEBSPHERE/IBM/InstallationManager/ -acceptLicense -
showProgress

25% 50% 75% 100%

------------------|------------------|------------------|------------------|
............................................................................
Installed com.ibm.cic.agent_1.9.0.20190715_0328 to
the /WEBSPHERE/IBM/InstallationManager/eclipse
directory.

6.After InstallationManager Successfully Installed or not

verifying in the below location
Go to the IM_Home/tools

cd /WEBSPHERE/IBM/InstallationManager/eclipse/tools

run the below Command

[wasadmin@localhost tools]$ ./imcl listInstalledPackages -

long
/WEBSPHERE/IBM/InstallationManager/eclipse :
com.ibm.cic.agent_1.9.0.20190715_0328 : IBM®
Installation Manager : 1.9.0
[wasadmin@localhost tools]$

Install WAS Product through InstallationManager

1.Create a Folder WAS

2.Copy WASND Binary Files zip into the WAS Folder

3.Unzip the WASND Binary Zip file using below Command

4. [wasadmin@localhost tools]$ cd /WEBSPHERE/WAS
[wasadmin@localhost WAS]$ ls
WAS_ND_V8.5_1_OF_3.zip WAS_ND_V8.5_2_OF_3.zip
WAS_ND_V8.5_3_OF_3.zip
[wasadmin@localhost WAS]$

Unzip WAS_ND_V8.5_1_OF_3.zip ; unzip

WAS_ND_V8.5_2_OF_3.zip ; unzip
WAS_ND_V8.5_3_OF_3.zip

5.After unzip Successfully Findout repository.xml

Run the below command in the SamePath

find . -name “repository.xml”

./disk1/md/repository.xml

vim ./disk1/md/repository.xml
findout offeringId

<repository>
<property name='LayoutPolicy' value='P1'/>
<property name='LayoutPolicyVersion' value='0.0.0.1'/>
<property name='RequireContext'
value='EnclosingVolumeRepository:path=..'/>
<offering id='com.ibm.websphere.ND.v85'
version='8.5.0.20120501_1108'>

Run the below command in the IM_Home/tools

Installed the WAS in the below location

/WEBSPHERE/IBM/WebSphere/AppServer/bin

Check the version

WAS Product Successfully or no verifying

[wasadmin@localhost postinstall]$ pwd

/WEBSPHERE/IBM/WebSphere/AppServer/logs/postinstall
[wasadmin@localhost postinstall]$

[wasadmin@localhost postinstall]$ tail -5f postinstall.log

<method>logReturnCode</method>
<thread>0</thread>
<message>INSTCONFSUCCESS: All config actions ran
successfully with return code 0</message>
</record>
</log>
Creating the profiles

Each profile have its own Template

for Ex:-

DMGR [management/dmgr]
APPLICATION SERVER [default]
CUSTOM PROFILE [managed]
CELL PROFILE [cell]
ADMIN AGENT [management]
JOB MANAGER [manager]

Dmgr Profile

[wasadmin@localhost bin]$ cd ../logs/manageprofiles/

[wasadmin@localhost manageprofiles]$ ls

Dmgr Profile created Successfully

Application Server Profile

Custom Profile

Dmgr Start Command

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

Fderation of the All Application Servers and Custom Servers

Step 1: Dmgr is must and should be running State

Step 2:After Started Dmgr
Step 3:Go to the AppSrv01/bin Path run the Federation
Command
Step 4: ./addNode.sh <DMGR HOSTNAME / IP> DMGR
SOAP Connector Port Number
Ex: ./addNode.sh 192.168.121.140 19026
Step 5:
[wasadmin@localhost bin]$ ./addNode.sh 192.168.121.140
19026
ADMU0116I: Tool information is being logged in file
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/A
ppSrv01/logs/addNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
CWPKI0308I: Adding signer alias "CN=localhost, OU=Root
Certifica" to local
keystore "ClientDefaultTrustStore" with the following
SHA digest:
32:A0:13:6D:62:81:6C:E4:84:AC:04:59:F4:85:88:0E:F
3:FA:43:AA
CWPKI0309I: All signers from remote keystore already exist
in local keystore.
ADMU0001I: Begin federation of node localhostNode02 with
Deployment Manager at
192.168.121.140:19026.
ADMU0009I: Successfully connected to Deployment
Manager Server:
192.168.121.140:19026
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: DOG_SERVER
ADMU2010I: Stopping all server processes for node
localhostNode02
ADMU0512I: Server DOG_SERVER 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:
localhostNode02
ADMU0014I: Adding node localhostNode02 configuration to
cell: localhostCell01
ADMU0016I: Synchronizing configuration between node and
cell.
ADMU0018I: Launching Node Agent process for node:
localhostNode02
ADMU0020I: Reading configuration for Node Agent process:
nodeagent
ADMU0022I: Node Agent launched. Waiting for initialization
status.
[wasadmin@localhost bin]$
AppSrv02

[wasadmin@localhost bin]$ ./addNode.sh 192.168.121.140

19026
ADMU0116I: Tool information is being logged in file
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/A
ppSrv02/logs/addNode.log
ADMU0128I: Starting tool with the AppSrv02 profile
CWPKI0308I: Adding signer alias "CN=localhost, OU=Root
Certifica" to local
keystore "ClientDefaultTrustStore" with the following
SHA digest:
32:A0:13:6D:62:81:6C:E4:84:AC:04:59:F4:85:88:0E:F
3:FA:43:AA
PuTTY X11 proxy: unable to connect to forwarded X server:
Network error: Connection refused
Realm/Cell Name: <default>
Username: wasadmin
Password:
CWPKI0309I: All signers from remote keystore already
exist in local keystore.
ADMU0001I: Begin federation of node localhostNode03 with
Deployment Manager at
192.168.121.140:19026.
ADMU0009I: Successfully connected to Deployment
Manager Server:
192.168.121.140:19026
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: TEST_SERVER
ADMU2010I: Stopping all server processes for node
localhostNode03
ADMU0512I: Server TEST_SERVER 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:
localhostNode03
ADMU0014I: Adding node localhostNode03 configuration to
cell: localhostCell01
ADMU0016I: Synchronizing configuration between node and
cell.
ADMU0018I: Launching Node Agent process for node:
localhostNode03
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:
31827

ADMU0300I: The node localhostNode03 was successfully

added to the
localhostCell01 cell.

ADMU0306I: Note:
ADMU0302I: Any cell-level documents from the standalone
localhostCell01
configuration have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the
localhostCell01 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 localhostCell01
cell using wsadmin
$AdminApp or the Administrative Console.

ADMU0003I: Node localhostNode03 has been successfully

federated.
[wasadmin@localhost bin]$

AppSrv03

[wasadmin@localhost bin]$ ./addNode.sh 192.168.121.140

19026
ADMU0116I: Tool information is being logged in file
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/A
ppSrv03/logs/addNode.log
ADMU0128I: Starting tool with the AppSrv03 profile
CWPKI0308I: Adding signer alias "CN=localhost, OU=Root
Certifica" to local
keystore "ClientDefaultTrustStore" with the following
SHA digest:
32:A0:13:6D:62:81:6C:E4:84:AC:04:59:F4:85:88:0E:F
3:FA:43:AA
PuTTY X11 proxy: unable to connect to forwarded X server:
Network error: Connection refused
Realm/Cell Name: <default>
Username: wasadmin
Password:
CWPKI0309I: All signers from remote keystore already
exist in local keystore.
ADMU0001I: Begin federation of node localhostNode04 with
Deployment Manager at
192.168.121.140:19026.
ADMU0009I: Successfully connected to Deployment
Manager Server:
192.168.121.140:19026
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: GOD_SERVER
ADMU2010I: Stopping all server processes for node
localhostNode04
ADMU0512I: Server GOD_SERVER 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:
localhostNode04
ADMU0014I: Adding node localhostNode04 configuration to
cell: localhostCell01
ADMU0016I: Synchronizing configuration between node and
cell.
ADMU0018I: Launching Node Agent process for node:
localhostNode04
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:
32477

ADMU0300I: The node localhostNode04 was successfully

added to the
localhostCell01 cell.

ADMU0306I: Note:
ADMU0302I: Any cell-level documents from the standalone
localhostCell01
configuration have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the
localhostCell01 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 localhostCell01
cell using wsadmin
$AdminApp or the Administrative Console.

ADMU0003I: Node localhostNode04 has been successfully

federated.
[wasadmin@localhost bin]$

Custom01
[wasadmin@localhost bin]$ ./addNode.sh 192.168.121.140
19026
ADMU0116I: Tool information is being logged in file
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/C
ustom01/logs/addNode.log
ADMU0128I: Starting tool with the Custom01 profile
CWPKI0308I: Adding signer alias "CN=localhost, OU=Root
Certifica" to local
keystore "ClientDefaultTrustStore" with the following
SHA digest:
32:A0:13:6D:62:81:6C:E4:84:AC:04:59:F4:85:88:0E:F
3:FA:43:AA
PuTTY X11 proxy: unable to connect to forwarded X server:
Network error: Connection refused
Realm/Cell Name: <default>
Username: wasadmin
Password:
CWPKI0309I: All signers from remote keystore already
exist in local keystore.
ADMU0001I: Begin federation of node localhostNode05 with
Deployment Manager at
192.168.121.140:19026.
ADMU0009I: Successfully connected to Deployment
Manager Server:
192.168.121.140:19026
ADMU0507I: No servers found in configuration under:
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/C
ustom01/config/cells/localhostCell05/nodes/
localhostNode05/servers
ADMU2010I: Stopping all server processes for node
localhostNode05
ADMU0024I: Deleting the old backup directory.
ADMU0015I: Backing up the original cell repository.
ADMU0012I: Creating Node Agent configuration for node:
localhostNode05
ADMU0014I: Adding node localhostNode05 configuration to
cell: localhostCell01
ADMU0016I: Synchronizing configuration between node and
cell.
ADMU0018I: Launching Node Agent process for node:
localhostNode05
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:
32982

ADMU0300I: The node localhostNode05 was successfully

added to the
localhostCell01 cell.

ADMU0306I: Note:
ADMU0302I: Any cell-level documents from the standalone
localhostCell01
 configuration have not been migrated to the new cell.
ADMU0307I: You might want to:
ADMU0303I: Update the configuration on the
localhostCell01 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 localhostCell01
cell using wsadmin
$AdminApp or the Administrative Console.

ADMU0003I: Node localhostNode05 has been successfully

federated.
[wasadmin@localhost bin]$

FixPack Installation

1.Stop All the Servers

2.Copy FixPack Files into the Appropriate Directory
3.Unzip the Files using unzip Command
4.verify process are not runningusing ps -ef|grep java

[wasadmin@localhost bin]$ ps -ef|grep java

wasadmin 33474 26132 0 11:20 pts/3 00:00:00 grep --
color=auto java
[wasadmin@localhost bin]$

5.Go to InstallationManager/tools run the FixPack Command

6.IHS_FixPack:

[wasadmin@localhost IHS_FixPack]$ unzip 8.5.5-WS-

WASSupplements-FP021-part1.zip ; unzip 8.5.5-WS-
 WASSupplements-FP021-part2.zip ; unzip 8.5.5-WS-
WASSupplements-FP021-part3.zip
Plugins OfferingId

<offering id='com.ibm.websphere.PLG.v85'
version='8.5.5021.20220202_1245'>
‘IHS OfferingId
------------------
<offering id='com.ibm.websphere.IHS.v85'
version='8.5.5021.20220202_1245'>

6.WAS_FixPack:

[wasadmin@localhost WAS_FixPack]$ unzip 8.5.5-WS-

WAS-FP021-part1.zip ; unzip 8.5.5-WS-WAS-FP021-
part2.zip ; unzip 8.5.5-WS-WAS-FP021-part3.zip

Offering Id
<offering id='com.ibm.websphere.ND.v85'
version='8.5.5021.20220202_1245'>
7. Go to InstallationManager/eclipse/tools

Run the below command

8.

9.Install ‘IHS and Plugins wasadmin user

Plugins Installations

10.Install ‘IHS_FixPack

11.
ListInstalledPackages verifying

Starting the all Servers 1 by 1

1.DMGR
2.APPLICATION_SERVER
3.CUSTOM_SERVER

Before federation it will act as a node after federation node

becomes a nodeagent
Nodeagent is a server that creates a automatically when node
is federate into the
cell.

DMGR

Dmgr is managed by all managed Application Servers

It’s a snglepoint of Administartion to manage the all
Application Servers.
AboutThisProfile.txt [DMGR]
[wasadmin@localhost bin]$ cd ../../Dmgr01/logs
[wasadmin@localhost logs]$ cat AboutThisProfile.txt
Application server environment to create: Management
Location:
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr
01
Disk space required: 30 MB
Profile name: Dmgr01
Make this profile the default: True
Node name: localhostNode01
Cell name: localhostCell01
Host name: localhost
Enable administrative security (recommended): True
Administrative console port: 19023
Administrative console secure port: 19024
Management bootstrap port: 19025
Management SOAP connector port: 19026
Run Management as a service: False
[wasadmin@localhost logs]$

Console Url:-

https://192.168.121.140:19024/ibm/console

If Forgot Dmgr Console username and password reset using

wasadmin scripts
[wasadmin@localhost bin]$ ./wsadmin.sh -connType NONE -
lang jython
WASX7357I: By request, this scripting client is not connected
to any server process. Certain configuration and application
operations will be available in local mode.
WASX7031I: For help, enter: "print Help.help()"
wsadmin>AdminTask.changeFileRegistryAccountPassword
('-userId wasadmin -password wasadmin123')
'CWWIM4545I The password is changed for
wasadmin(uid=wasadmin,o=defaultWIMFileBasedRealm)
in the file registry in the temporary workspace. You must
use the "$AdminConfig save" command to save it in the
master repository.'
wsadmin>AdminConfig.save ()
''
wsadmin>

Created the Server using Custom Node

Custom Server created Successfully
-------------------------------------------

Started all Servers no issues reported

Creating the Cluster Environment

Click New
Click Next

Click Finish ; Save and Review

Later start the Cluster

Select the Cluster apply start Function

Started the ‘IHS Server

Application Deployment

Click New Enterprise Application

Click Remote File System

Click Next
Click Next

Mapping the Module

Click Next
Map Contextroots for web modules

Click Next

Click Finish

Go to Application Type
Click WebSphere Enterprise Application
Select the Application and apply start
After starting the Application
We have to access the application via Clustermembers

Error

Verifying the Virtualhost

Restart the Tree_Cl01 and try to access the Application

Now Access the Application

Same process repeats the remining Cluster Members

Tree_Cl02
--------------

http://192.168.121.140:19140/ShoppingCart/
Tree_Cl03
------------
http://192.168.121.140:19160/ShoppingCart/

Tree_Cl05
http://192.168.121.140:19180/ShoppingCart/

Create the Un Managed Node by using un managed node we

have create the WebServer

Click Add Node

Click Apply,Review save changes

Go to Serevers ----Webserver
Click Next

Click Next

Click Finish
Click Review and Sync Changes
Generate and Propagate Plugins

Save and exit the httpd.conf

And restart the httpSerever

Later map the ‘IHS and we have access the Application

Click Ok

Application is Accessing via HTTPServer

http://192.168.121.140:8082/ShoppingCart/
Data Source Creation

DB User Name: Ganesh

Password:71823456

Steps:-
--------
What is a Data Source
--------------------------

Data Source is an object that establish a connection between

APPLICATION SERVER to Database with secure port
number

Types of Data Source 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
(/WEBSPHERE/IBM/WebSphere/AppServer/universalDriver
s/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.Provide

4. Implementation type

5.Name [ Oracle JDBC Driver (XA)]

6.Description [ Oracle JDBC Driver (XA)]

Click Next >

Class Path: ${ORACLE_JDBC_DRIVER_PATH}/ojdbc6.jar

Universal Driver Path Location: $

{ORACLE_JDBC_DRIVER_PATH}
[(/WEBSPHERE/IBM/WebSphere/AppServer/universalDrive
rs/lib/)]
Directory location for "ojdbc6.jar" which is saved as
WebSphere variable ${ORACLE_JDBC_DRIVER_PATH}
------------------------------------------------------------------
(/WEBSPHERE/IBM/WebSphere/AppServer/
universalDrivers/lib/)
------------------------------------------------------------------

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

Creating the Data Source using the JDBC Provider: -

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

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 Reports:-

----------------------------------------------
Ex:-

The test connection operation for data source Ganesh on

server nodeagent at node cropcaptzsfpo_AoppSrvNode01 was
successful.
InformationThe test connection operation for data source
Ganesh on server nodeagent at node
cropcaptzsfpo_AoppSrvNode02 was successful.
InformationThe test connection operation for data source
Ganesh on server nodeagent at node
cropcaptzsfpo_AoppSrvNode03 was successful.

SSL

SSL at WebServer level

SSL at IHS and App.Server Level

------------------------------
SSL at WebServer Level
----------------------

.KDB
.RDB
.STH

KEYSTORES //key.p12// //self signed certificates//

TRUSTSTORES //trust.p12// signers we have to add //third

party certficates// [CA,DIGICERT]

The *.kdb contains the private keys, certificiates, and CA's.

It is encrypted with a password that can be stashed in the *.sth

file.
The *.rdb contains information about outstanding certificate
requests. //CSR ===> CERTIFICATE SIGNING
REQUESTS//

IHS Level there is .kdb , .rdb, .sth

how to create kdb,rdb,sth

keydatabase .kdb

How to create .kdb , .rdb , .sth

Steps:
-----

1.Create the Directory SSL in <IHS_HOME>

/usr/opt/HTTPServer/
2.go to <IHS_HOME>/bin

Execute the below Command for creating the .kdb,.rdb,.sth

./gskcmd -keydb -create -db

/usr/opt/HTTPServer/SSL/IHS.kdb -stash -type <CMS|JKS|
PKCS12> -pw WebAS -expiry 365

Check the certificate Expiry Date

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

[wasadmin@cropcaptzxfo SSL]$ openssl x509 -enddate -

noout -in root_X0F.cer -dates
notBefore=Mar 30 12:29:49 2003 GMT
notAfter=Mar 29 12:29:49 2033 GMT
[wasadmin@cropcaptzxfo SSL]$

X509 ====>Retrive the Certificate related Information like

Domain=[CN,O,OU,POSTALCODE,Country,Signature
Algarithm etc].

OR

[wasadmin@cropcaptzxfo SSL]$ openssl x509 -enddate -

noout -in root_X0F.cer -dates -text
notBefore=Mar 30 12:29:49 2003 GMT
notAfter=Mar 29 12:29:49 2033 GMT
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 15 (0xf)
Signature Algorithm: sha256WithRSAEncryption
Issuer: O=Root CA, OU=http://www.cacert.org, CN=CA
Cert Signing Authority/[email protected]
Validity
Not Before: Mar 30 12:29:49 2003 GMT
Not After : Mar 29 12:29:49 2033 GMT
 Subject: O=Root CA, OU=http://www.cacert.org,
CN=CA Cert Signing
Authority/[email protected]
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (4096 bit)
Modulus:
00:ce:22:c0:e2:46:7d:ec:36:28:07:50:96:f2:a0:
33:40:8c:4b:f1:3b:66:3f:31:e5:6b:02:36:db:d6:
7c:f6:f1:88:8f:4e:77:36:05:41:95:f9:09:f0:12:
cf:46:86:73:60:b7:6e:7e:e8:c0:58:64:ae:cd:b0:
ad:45:17:0c:63:fa:67:0a:e8:d6:d2:bf:3e:e7:98:
c4:f0:4c:fa:e0:03:bb:35:5d:6c:21:de:9e:20:d9:
ba:cd:66:32:37:72:fa:f7:08:f5:c7:cd:58:c9:8e:
e7:0e:5e:ea:3e:fe:1c:a1:14:0a:15:6c:86:84:5b:
64:66:2a:7a:a9:4b:53:79:f5:88:a2:7b:ee:2f:0a:
61:2b:8d:b2:7e:4d:56:a5:13:ec:ea:da:92:9e:ac:
44:41:1e:58:60:65:05:66:f8:c0:44:bd:cb:94:f7:
42:7e:0b:f7:65:68:98:51:05:f0:f3:05:91:04:1d:
1b:17:82:ec:c8:57:bb:c3:6b:7a:88:f1:b0:72:cc:
25:5b:20:91:ec:16:02:12:8f:32:e9:17:18:48:d0:
c7:05:2e:02:30:42:b8:25:9c:05:6b:3f:aa:3a:a7:
eb:53:48:f7:e8:d2:b6:07:98:dc:1b:c6:34:7f:7f:
c9:1c:82:7a:05:58:2b:08:5b:f3:38:a2:ab:17:5d:
66:c9:98:d7:9e:10:8b:a2:d2:dd:74:9a:f7:71:0c:
72:60:df:cd:6f:98:33:9d:96:34:76:3e:24:7a:92:
b0:0e:95:1e:6f:e6:a0:45:38:47:aa:d7:41:ed:4a:
b7:12:f6:d7:1b:83:8a:0f:2e:d8:09:b6:59:d7:aa:
04:ff:d2:93:7d:68:2e:dd:8b:4b:ab:58:ba:2f:8d:
ea:95:a7:a0:c3:54:89:a5:fb:db:8b:51:22:9d:b2:
c3:be:11:be:2c:91:86:8b:96:78:ad:20:d3:8a:2f:
1a:3f:c6:d0:51:65:87:21:b1:19:01:65:7f:45:1c:
87:f5:7c:d0:41:4c:4f:29:98:21:fd:33:1f:75:0c:
04:51:fa:19:77:db:d4:14:1c:ee:81:c3:1d:f5:98:
b7:69:06:91:22:dd:00:50:cc:81:31:ac:12:07:7b:
38:da:68:5b:e6:2b:d4:7e:c9:5f:ad:e8:eb:72:4c:
f3:01:e5:4b:20:bf:9a:a6:57:ca:91:00:01:8b:a1:
75:21:37:b5:63:0d:67:3e:46:4f:70:20:67:ce:c5:
d6:59:db:02:e0:f0:d2:cb:cd:ba:62:b7:90:41:e8:
 dd:20:e4:29:bc:64:29:42:c8:22:dc:78:9a:ff:43:
ec:98:1b:09:51:4b:5a:5a:c2:71:f1:c4:cb:73:a9:
e5:a1:0b
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Subject Key Identifier:
16:B5:32:1B:D4:C7:F3:E0:E6:8E:F3:BD:D2:B0:3A
:EE:B2:39:18:D1
X509v3 Basic Constraints: critical
CA:TRUE
Netscape CA Policy Url:
http://www.cacert.org/index.php?id=10
Netscape Comment:
To get your own certificate for FREE head over to
http://www.cacert.org
X509v3 CRL Distribution Points:

Full Name:
URI:http://crl.cacert.org/revoke.crl

Netscape CA Revocation Url:

URI:http://crl.cacert.org/revoke.crl
Authority Information Access:
OCSP - URI:http://ocsp.cacert.org

X509v3 Authority Key Identifier:

keyid:16:B5:32:1B:D4:C7:F3:E0:E6:8E:F3:BD:D2:
B0:3A:EE:B2:39:18:D1

Signature Algorithm: sha256WithRSAEncryption

47:9c:d7:b3:a2:17:d3:52:53:b7:b4:6a:dd:bf:9b:35:15:21:
6c:ef:6f:18:13:20:81:cc:e8:ed:1d:2a:22:1d:64:76:14:ba:
5b:37:2b:0e:83:ba:3e:4a:6e:46:0d:0b:de:a3:3b:61:00:7a:
a7:0d:95:fa:e6:f3:17:bc:65:e0:2d:07:5a:5b:5f:cc:f4:db:
cc:01:dd:26:d8:da:25:0c:3b:41:a0:65:98:06:29:37:60:8b:
07:a2:5e:83:ca:bf:d5:7a:60:77:0f:fe:20:fd:46:47:07:60:
ef:15:29:45:e5:00:e3:cd:a5:e0:c1:f5:91:fd:16:d1:a7:7d:
e1:2b:88:7c:d5:90:1d:c7:4b:02:99:a7:a3:f4:94:87:56:e9:
67:27:96:ac:c9:e5:86:41:8d:0c:a3:31:08:24:17:43:7e:b4:
 4f:01:47:73:c7:5f:10:06:aa:e6:bc:ba:71:9c:e6:d6:87:ad:
ae:44:af:88:4d:aa:a1:fc:6f:bf:55:45:89:0f:bd:4d:7d:ff:
ce:41:02:0a:c5:01:fc:48:cf:33:49:71:14:19:ae:f5:3e:48:
87:e1:2a:9e:cf:62:be:6a:c4:21:00:ef:f6:d3:72:24:7b:8b:
b0:33:6a:6d:40:5a:97:b3:a8:88:f6:67:5e:4f:4b:1f:ea:9b:
fa:92:df:d6:87:ef:e6:7a:32:e6:f5:f6:6b:93:8a:79:b1:de:
fb:41:31:fc:0e:de:f8:6f:c7:b8:e8:d5:36:a8:59:f6:3e:4d:
8a:ca:5f:ab:dc:cd:c8:e1:c6:58:3f:28:7e:3f:03:1f:00:79:
d0:bd:57:87:91:fe:11:b2:28:81:af:e1:24:24:27:46:dc:56:
90:73:fa:f7:d4:f5:26:92:c5:63:06:a9:82:99:62:bc:5e:13:
16:fe:1f:aa:9d:27:1d:32:82:d7:1f:60:1a:b2:20:be:e6:09:
97:5b:71:20:a9:b1:5d:d7:c9:ce:0b:1c:33:3a:a9:69:b8:6d:
1c:e3:17:3a:2c:10:06:95:b3:c8:99:28:7c:5f:f0:e7:97:b4:
2e:db:59:0c:19:04:b2:29:55:fe:f5:b4:08:9b:0f:b3:77:8d:
69:01:7e:88:c5:ac:70:63:a4:80:b1:65:5a:c0:12:dc:7c:32:
89:82:cd:26:8d:ba:6a:ac:96:3d:a2:1d:73:c1:38:72:4e:d2:
93:4f:16:ac:5a:c7:20:ad:c4:1e:be:27:d4:56:70:98:ba:45:
02:fb:9c:2a:a8:25:d2:1a:fe:da:3c:a9:ca:1e:69:b8:0d:ca:
92:c1:c5:dc:2b:14:ce:33:14:bf:3c:4c:87:29:21:f7:3a:cc:
c5:00:07:2c:15:6b:1b:07
[wasadmin@cropcaptzxfo SSL]$

KDB Creation
-------------

Definitions:
--------------

The *.kdb contains the private keys, certificiates, and CA's.

It is encrypted with a password that can be stashed in the *.sth
file.
The *.rdb contains information about outstanding certificate
requests.

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

db /usr/opt/HTTPServer/SSL/IHS.kdb -pw wasadmin -expire
365 -stash -type cms
[wasadmin@cropcaptzxfo bin]$
[wasadmin@cropcaptzxfo bin]$ cd ../
[wasadmin@cropcaptzxfo HTTPServer]$ cd SSL
[wasadmin@cropcaptzxfo SSL]$ ls -ltrh
total 24K
-rwxrwxrwx. 1 wasadmin wasadmin 2.5K Apr 22 22:31
root_X0F.cer
-rwxrwxrwx. 1 wasadmin wasadmin 2.2K Apr 22 22:32
CAcert_Class3Root_x14E228.cer
-rwxrwxrwx. 1 wasadmin wasadmin 270 Apr 22 22:49
unstash.pl // to view the KDB Password // // ./unstash.pl
IHS.sth //
-rw-rw-r--. 1 wasadmin wasadmin 88 Apr 22 22:51 IHS.kdb
-rw-rw-r--. 1 wasadmin wasadmin 193 Apr 22 22:51 IHS.sth
-rw-rw-r--. 1 wasadmin wasadmin 80 Apr 22 22:51 IHS.rdb
[wasadmin@cropcaptzxfo SSL]$ chmod -R 777 *
[wasadmin@cropcaptzxfo SSL]$

[wasadmin@cropcaptzxfo bin]$ pwd

/usr/opt/HTTPServer/bin
[wasadmin@cropcaptzxfo bin]$

Certificates added into the IHS KeyDatabase

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

[wasadmin@cropcaptzxfo bin]$ ./gskcmd -cert -add -db

/usr/opt/HTTPServer/SSL/IHS.kdb -file
/usr/opt/HTTPServer/SSL/root_X0F.cer -label CAROOT
A password is required to access the source key database.
Please enter a password:
[wasadmin@cropcaptzxfo bin]$ ./gskcmd -cert -add -db
/usr/opt/HTTPServer/SSL/IHS.kdb -file
/usr/opt/HTTPServer/SSL/CAcert_Class3Root_x14E228.cer
-label CAINTERMEDIATE -pw wasadmin
[wasadmin@cropcaptzxfo bin]$ ./gskcmd -cert -list -db
/usr/opt/HTTPServer/SSL/IHS.kdb
A password is required to access the source key database.
Please enter a password:
Certificates in database /usr/opt/HTTPServer/SSL/IHS.kdb:
CAINTERMEDIATE
CAROOT
[wasadmin@cropcaptzxfo bin]$

Certificates added into the Plugins level

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

[wasadmin@cropcaptzxfo ~]$ cd /usr/opt/HTTPServer/bin

[wasadmin@cropcaptzxfo bin]$
[wasadmin@cropcaptzxfo bin]$ ./gskcmd -cert -add -db
/usr/opt/WebSphere/Plugins/SSL/PLG.kdb -file
/usr/opt/WebSphere/Plugins/SSL/root_X0F.cer -label
CAROOT -pw wasadmin
[wasadmin@cropcaptzxfo bin]$ ./gskcmd -cert -add -db
/usr/opt/WebSphere/Plugins/SSL/PLG.kdb -file
/usr/opt/WebSphere/Plugins/SSL/CAcert_Class3Root_x14E2
28.cer -label CAINTERMEDIATE -pw wasadmin
[wasadmin@cropcaptzxfo bin]$ cd ../
[wasadmin@cropcaptzxfo HTTPServer]$ cd ../
[wasadmin@cropcaptzxfo opt]$ cd WebSphere/Plugins/
[wasadmin@cropcaptzxfo Plugins]$ cd SSL/
[wasadmin@cropcaptzxfo SSL]$ ls -ltrh
total 32K
-rwxrwxr-x. 1 wasadmin wasadmin 2.5K Apr 22 22:31
root_X0F.cer
-rwxrwxr-x. 1 wasadmin wasadmin 2.2K Apr 22 22:32
CAcert_Class3Root_x14E228.cer
-rwxrwxrwx. 1 wasadmin wasadmin 193 Apr 22 22:57
PLG.sth
-rwxrwxrwx. 1 wasadmin wasadmin 215 Apr 22 22:59
unstash.py
-rwxrwxrwx. 1 wasadmin wasadmin 9.9K Apr 22 23:07
PLG.kdb
-rwxrwxrwx. 1 wasadmin wasadmin 80 Apr 22 23:07
PLG.rdb
[wasadmin@cropcaptzxfo SSL]$ cd ../../
[wasadmin@cropcaptzxfo WebSphere]$ cd ../
[wasadmin@cropcaptzxfo opt]$ cd HTTPServer/bin
[wasadmin@cropcaptzxfo bin]$

[wasadmin@cropcaptzxfo bin]$ ./gskcmd -cert -list -db

/usr/opt/WebSphere/Plugins/SSL/PLG.kdb
A password is required to access the source key database.
Please enter a password:
Certificates in database
/usr/opt/WebSphere/Plugins/SSL/PLG.kdb:
CAINTERMEDIATE
CAROOT
[wasadmin@cropcaptzxfo bin]$

View the IHS.KDB Password if you have forgot the Password

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

Step 1: Create a Folder SSL in this Path /usr/opt/HTTPServer/

mkdir SSL

Step 2:Change the Ownsership of Folder using chmod -R 777

SSL

Step 3: Go to IHS_Home/bin Execute belowcommand to

create the KDB File

Step 4: ./gskcmd -keydb -create -db

/usr/opt/HTTPServer/SSL/cropcaptzsfpo.kdb -expire 365 -pw
wasadmin -type cms -stash
Step 5: Go to the /usr/opt/HTTPServer/SSL/ verify the
IHS.kdb,IHS,rdb,IHS.sth are there or not

Step 6: Create the file vim unstash.pl

Step 7: paste the below Code

#!/usr/bin/perl
my $file=$ARGV[0];
open F, $file;
my $stash;
read F, $stash, 1024;
my @unstash=map {$_^0xf5} unpack ("C*", $stash);
foreach $c (@unstash) {
last if $c eq 0;
printf "%c", $c;
}
print "\n";

Step 8: Save the file :wq!

Step 9: change the permission of file chmod -R 777 unstash.pl

Step 10: Execute the Below Command :-

./unstash.pl IHS.sth

Step 11: Displays a password below :-

[root@cropcaptzsfpo SSL]# ./unstash.pl IHS.sth

WebAS
[root@cropcaptzsfpo SSL]#

total 28K
-rw-r--r--. 1 root root 80 Mar 31 06:57 IHS.kdb
-rw-r--r--. 1 root root 80 Mar 31 06:57 IHS.rdb
-rw-------. 1 root root 129 Mar 31 07:04 IHS.sth
-rwxrwxrwx. 1 root root 204 Mar 31 07:20 unstash.pl
-rw-r--r--. 1 root root 80 Mar 31 07:37
cropcaptzsfpo.kdb
 -rw-r--r--. 1 root root 129 Mar 31 07:37
cropcaptzsfpo.sth
-rw-r--r--. 1 root root 80 Mar 31 07:37 cropcaptzsfpo.rdb
[root@cropcaptzsfpo SSL]#

Referenced Url:
---------------

https://d1wl9nui6miy8.cloudfront.net/media/965760/wp-a-
guide-to-password-use-in-websphere-application-server.pdf

Raise the CSR at ApplicationServer level

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

SSL certificate and key management > Key stores and

certificates > CellDefaultKeyStore > Personal certificate
requests>

SSL at WebSphereApplication Serer level

Takes backup of Trust.p12 and Key.p12 using below

command :
Ex: 1. cp –pr trust.p12 trust.p12_bkp
2.cp –pr key.p12 key.p12_bkp
Path:
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cell
s/DMGRCell/

trust.p12,key.p12,security.xml files are available under the

above locations.

Step 2:

1.Navigate to Dmgr Console

2.Go to Security tab  click SSL Certificates and
Management  Click Keystores and Certificates  click
CellDefault Keystore  Click Personal Certificate Request
Check the CSR Path

/WEBSPHERE/IBM/WebSphere/AppServer/profiles/
Dmgr01/SSL/

total 12K
-rwxrwxrwx. 1 wasadmin wasadmin 2.5K Aug 8 2022
root_X0F.cer [Root Certificate]
-rwxrwxrwx. 1 wasadmin wasadmin 2.2K Aug 8 2022
CAcert_Class3Root_x14E228.cer [Intermediate
Certificate]
-rwxrwxrwx. 1 wasadmin wasadmin 1.8K Apr 22 23:13
server.cer
[wasadmin@localhost SSL]$

Third Party Certificates we have to add in to trustore and

signers

Go to Security tab  click SSL Certificates and Management

 Click Keystores and Certificates  click CellDefault
Truststore  Signer Certificate == Add

Root, Intermediate, Server Certificate

Press Click Apply review and Save Sync

After that Stop all Servers and Sync the Dmgr and start the
Nodeagent and Servers.

Alias:
FileName:

Click Ok and save sync

Personal Certificates we have to add in the Keystores

Click Chain Certificate and fill Details below
After that asking Advanced option click ok

Sync the All Servers to the DMGR using ./syncNode.sh

<DMGR_HOST> <DMGR_SOAP CONNECTOR PORT
NUMBER>

Troubleshooting

1. 100% Cpu Utilization

2. OOM Issues
3. Automatic Genarated Dumps and Analysis of Dumps
4. Garbage Collection how to enable in Generic JVM
Arguments

1. 100% Cpu Utilization

PID USER PR NI VIRT RES SHR S

%CPU %MEM TIME+ COMMAND
3472 wasadmin 20 0 3451772 285924 47024 R
84.4 7.4 7:05.47 firefox
2207 wasadmin 20 0 2999388 114728 19660 S
5.0 3.0 5:20.49 gnome-shell

For Ex: CPU Utilization is more than 80% taken that process
id and check the server ps -ef|grep 3472
its getting the results later stop the server,Nodeagent

./clearClassCache.sh && ./osgiCfgInit.sh

Later /tmp , /wstemp , config/temp will be removed inside the

content

rm -Rf *

later we will start the Nodeagent and Server later it works

Fine

2. OOM Issues
Verified the SystemOut.log and SystemErr.logs find out error
I related to OOM
Suppose JAVA.LANG.IO EXCEPTION ----- JAVA HEAP
SPACE

Its related to heap memory issue we need to increase the heap

size take help of the OS Team.
Or analyzing Dumps purpose we have some tools we will use
i.e

Heap analyzer and Thread Analyzer tools

How much memory leakage purpose based on the report we

have to move further process is there any hung threads.

Its extenstion of Heap Dumps is .phd Format Portable Heap

Dump

JAVA Core Anayzing purpose use thread Analyzer tool in this

identified any hung threads, any memory issues, JVM Issue
identified its human readable Format.
 1. How many Deadlocks are there identified
2. How many Runnable Threads are there.
3. How many Hung thread are there.
4. Any waiting Conditions and monitor etc.

Thread Analyzer
Heap Analyzer
------------------
Scripts

Generate Plugins in the Command line:-

[aganes2@localhost bin]$ ./GenPluginCfg.sh -cell.name

Dmgr_Cell01 -node.name IHS -webserver.name
HTTPServerv8.5
*** Initiating original genplugincfg call using args of: -
cell.name Dmgr_Cell01 -node.name IHS -webserver.name
HTTPServerv8.5

IBM WebSphere Application Server, Release 8.5

WebSphere Plugin Configuration Generator
Copyright IBM Corp., 1997-2012
PLGC0060E: No applications are mapped to the Web server.
PLGC0005I: Plug-in configuration file =
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01
/config/cells/Dmgr_Cell01/nodes/IHS/servers/
HTTPServerv8.5/plugin-cfg.xml
PLGC0052I: Plug-in configuration file generation is complete
for the Web server. Dmgr_Cell01.IHS.HTTPServerv8.5.
[aganes2@localhost bin]$

Examples:
 To generate a plug-in configuration for all of the clusters in
a cell:
GenPluginCfg -cell.name NetworkDeploymentCell

To generate a plug-in configuration for a single server:

GenPluginCfg -cell.name BaseApplicationServerCell -
node.name appServerNode -server.name appServerName

To generate a plug-in configuration file for a Web server:

GenPluginCfg -cell.name BaseApplicationServerCell -
node.name webserverNode -webserver.name webserverName.

Application Deployment through Scripts

Go to the Dmgr Profile/bin run the below command

[aganes2@localhost profiles]$ cd Dmgr01/

[aganes2@localhost Dmgr01]$ cd bin
[aganes2@localhost bin]$
[aganes2@localhost bin]$ ./wsadmin.sh --conntype NONE
[aganes2@localhost bin]$ ./wsadmin.sh -conntype NONE
WASX7357I: By request, this scripting client is not connected
to any server process. Certain configuration and application
operations will be available in local mode.
WASX7029I: For help, enter: "$Help help"
wsadmin>$AdminApp install
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01
/Deployment/PlantsByWebSphere.ear {-
MapModulesToServers {{.* .*.jar,.*
WebSphere:cell=Dmgr_Cell01,node=AppSrv_Node01,server
=Test_Server} {.* .*.war,.*
WebSphere:cell=Test_Dmgr_Cell01,node=AppSrv_Node02,s
erver=Tree_Server} {.* .*.war,.*
WebSphere:cell=Test_Dmgr_Cell01,node=AppSrv_Node03,s
erver=Test_Server} {.* .*.war,.*
WebSphere:cell=Dmgr_Cell01,node=Custom_Node01,server
=Test_Server}}}
WASX7327I: Contents of was.policy file:
 //
// Plants by WebSphere Security Policy
//

// Required for use of Cloudscape by the EJBs in the

PlantsByWebSphere Application
grant codeBase "file:${application}" {
permission java.io.FilePermission "${app.installed.path}$
{/}Database${/}PLANTSDB${/}-", "read,write";
};

grant codeBase "file:${application}" {

permission java.io.FilePermission "${user.home}$
{/}.mailcap", "read";
permission java.io.FilePermission "${java.home}${/}lib$
{/}mailcap", "read";
};

grant codeBase "file:${application}" {

permission java.io.FilePermission "${app.installed.path}$
{/}PlantsByWebSphereEJB.jar", "read";
};

ADMA5016I: Installation of PlantsByWebSphere started.

ADMA5058I: Application and module versions are validated
with versions of deployment targets.
ADMA5005I: The application PlantsByWebSphere is
configured in the WebSphere Application Server repository.
ADMA5005I: The application PlantsByWebSphere 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 PlantsByWebSphere is
configured in the WebSphere Application Server repository.
ADMA5001I: The application binaries are saved in
/WEBSPHERE/IBM/WebSphere/AppServer/profiles/Dmgr01
/wstemp/Script189a24c32f4/workspace/cells/Dmgr_Cell01/
applications/PlantsByWebSphere.ear/PlantsByWebSphere.ear
ADMA5005I: The application PlantsByWebSphere is
configured in the WebSphere Application Server repository.
SECJ0400I: Successfully updated the application
PlantsByWebSphere with the appContextIDForSecurity
information.
ADMA5005I: The application PlantsByWebSphere is
configured in the WebSphere Application Server repository.
ADMA5005I: The application PlantsByWebSphere is
configured in the WebSphere Application Server repository.
ADMA5113I: Activation plan created successfully.
ADMA5011I: The cleanup of the temp directory for
application PlantsByWebSphere is complete.
ADMA5013I: Application PlantsByWebSphere installed
successfully.

wsadmin>$AdminConfig save

wsadmin>

To Start the Application through the Scripts

[aganes2@localhost bin]$ ./wsadmin.sh -c
"AdminControl.invoke(AdminControl.queryNames('type=Ap
plicationManager,process=Test_Server,*'),'startApplication','P
lantsByWebSphere')" -lang jython
PuTTY X11 proxy: unable to connect to forwarded X server:
Network error: Connection refused
Realm/Cell Name: <default>
Username: wasadmin
Password:
WASX7209I: Connected to process "dmgr" on node
Dmgr_Node01 using SOAP connector; The type of process
is: DeploymentManager
WASX7015E: Exception running command:
"AdminControl.invoke(AdminControl.queryNames('type=Ap
plicationManager,process=Test_Server,*'),'startApplication','P
lantsByWebSphere')"; exception information:
com.ibm.ws.scripting.ScriptingException: WASX7025E:
Error found in String
"WebSphere:name=ApplicationManager,process=Test_Server,
platform=proxy,node=AppSrv_Node01,version=8.5.5.21,type
=ApplicationManager,mbeanIdentifier=ApplicationManager,c
ell=Dmgr_Cell01,spec=1.0
WebSphere:name=ApplicationManager,process=Test_Server,
platform=proxy,node=AppSrv_Node02,version=8.5.5.21,type
=ApplicationManager,mbeanIdentifier=ApplicationManager,c
ell=Dmgr_Cell01,spec=1.0
WebSphere:name=ApplicationManager,process=Test_Server,
platform=proxy,node=AppSrv_Node03,version=8.5.5.21,type
=ApplicationManager,mbeanIdentifier=ApplicationManager,c
ell=Dmgr_Cell01,spec=1.0
WebSphere:name=ApplicationManager,process=Test_Server,
platform=proxy,node=Custom_Node01,version=8.5.5.21,type
=ApplicationManager,mbeanIdentifier=ApplicationManager,c
ell=Dmgr_Cell01,spec=1.0"; cannot create ObjectName.

[aganes2@localhost bin]$
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

Application servers > Test_Server > Process definition > Java Virtual Machine

Run the command

[root@localhost ~]#
/WEBSPHERE/IBM/WebSphere/AppServer/java/8.0/bin/jcon
sole
[root@localhost server1]# netstat -anlp|grep 9000
tcp6 0 0 :::9000 :::* LISTEN 4575/java
[root@localhost server1]#

find / -name jconsole

-------------------------Prepared By AMIRINENI
GANESH---------------------------