Websphere Archive

WEBSPHERE 8.5 NETWORK DEPLOYMENT CREATING PROFILES

CREATING PROFILES USING PROFILE MANAGEMENT TOOL

1.

screen1

2. Select Option Typical Profile Creation

screen2

4. Click Next on Profile Creation Summary

screen4

5. Installation Started

screen5

6. Profile  Creation complete click Finish

screen6

 

6. You Will Come To This Screen Which Confirming That AppSrv01 And Dmgr01 Two Profiles Has Been Created.screen7

7. Let’s start the Dmgr – Go to /opt/IBM/Websphere/AppServer/profiles/Dmgr01/bin and run ./startManager.sh script.    When you get a message stating “Server dmgr open for e-business porcees id is 8897 ”  that’s mean dmgr  up

screen8

8. You Can Access Cell Using  http://hostname:9060/ibm/console    you should get below screen.  To login click login since we didn’t define any user during our installation

screen9

9. Once You Login You Will See Following Screen.

screen10

10. Click On Websphere Application Server From Left Hand Panel, Notice  One App Server With The Name of server1  is Created During Our Installation.

screen11

 

 

 

 

 

Websphere 8.5 Network Deployment Installation Part2

  1. Run ./Install.sh  as show in below screen shotCapture
  2. Click Install

screen1

3. Select IBM WebSphere Application Server Network Deployment

screen24. Accept terms and condition here

screen3

5.  take default and click Next

screen4

6. take default and click Next

screen5

7. click Nextscreen5

8.

screen6

9. Click Install

screen8

10.   Installation started

screen9

12.  Installation completedscreen10

 

 

 

 

Websphere 8.5 Network Deployment installation Part1

WEBSPHERE 8.5 INSTALLATION

 

PREREQUISITE

  • ORACLE LINUX 5.8 64 BIT
  • I WILL BE DOING THIS INSTALLATION AS A ROOT USER
  • USING JAVA 6 FOR THIS INSTALLATION
  • USING IBM INSTALLATION MANAGER FOR THIS INSTALLATION
  1. I have my installation file under /software. Go to /software/IIM_Linux_x86_64_1.7.3 folder and run script ./Install.sh  as show in below screen shot

Capture

2. Click Install

screen1

3. click File and then Preferences

screen2

4. You will come to this screen Browse to the location of your WebSphere Installation filesscreen3

5. pick below option as shown

screen4.0

6. On this screen select repository.configscreen5.07. click ok

screen6.0

8. Repository installed.  We just configure Highlighted repositoryscreen7

 

 

 

 

Reset WebSphere admin console password

As a WebSphere admin one of the commonly seen issue is how to reset the WebSphere admin console password.

Well below are the steps to reset our WebSphere Admin Console Password

1) Using Admin Console:

To reset the password using the admin console

a) Go to DMGR profile config cells directory.

b) Edit the file(After taking backup) — security.xml and change the enabled value to false(refer to the below attachments)

1

 

c) Now, log in to the admin console, go to Security tab>Global Security>select Enable Administrative Security>Click on Security   Configuration Wizard>

2
Then click on Next. And Select the user repository as Federated repositories.
After entering the user name and password logout from admin console. Since, the changes are related to configuration restart the dmgr server instance to reflect the changes

2. Using wsadmin utility:

To reset the password using wsadmin tool:-

a) Go to WAS-Home>bin>./wsadmin.sh –lang jython –username wasadm –password wasadm123

b) Execute the below commands.

3

c) Reset the password using steps described above in section:1.c)

 

This will reset your wasadmin password.

Please feel free to get in touch with us if you have any queries.

Cheers,

Wonders Team

Clustering in WebSphere Application Server

Clustering is a very critical aspect of any middleware enterprise application. It provides capabilities of high availability by providing fail over and load balancing mechanism.

This post is a sample demonstration of configuring a cluster in WebSphere Application Server Network Deployment 7.0.

Prerequisites:

Deployment Manager Profile created using profile management tools.

 

Steps:

1. Create Cluster definition.

Log into WAS Admin console — > Servers — > Clusters — > WebSphere application server clusters.

Clustering in WebSphere

Clustering in websphere

Clustering in websphere

 

2. Create cluster members.

Provide the details about the cluster members.

Clustering in WebSphere

 

Define the node on which the cluster member would reside.

Also define whether the server would be generated based on a server template.

You can add additional members to the cluster.

Clustering in WebSphere

Cluster-Complete

Once the cluster is created successfully, it would be in stopped state by default.

3. Make sure the node agent is started.

Go to System administration from left panel — > Node agents — > Check the status.

 

Clustering in WebSphere

Clustering in WebSphere

 

If the Node Agent is not  started, you can execute the below script to start the same.

WAS_HOME/profiles/YOUR_PROFILE_NAME/bin/startNode.cmd

4. Start the cluster.

 

Cluster-Start

 

Further reading:

http://pic.dhe.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=%2Fcom.ibm.websphere.nd.doc%2Finfo%2Fae%2Fae%2Ftrun_wlm_cluster.html

 

Some common issues while configuring a cluster in WebSphere Application Server.

Issues:

1.

Cluster member MyServer1 will not be started because the Node Agent on node Node02 is not active. Cluster members can be started individually from the cluster member collection panel.

Remedy:

Make sure you start the Node Agent.

2.

The node agent on node Node02 must be started to perform the restart operation. Node agents in stopped state cannot be started from the console.

Remedy:

You would need to start the node agent from command line as below.

WAS_HOME/profiles/YOUR_PROFILE_NAME/bin/startNode.cmd

 

3.

 

Caused by: com.ibm.websphere.management.exception.AdminException: ADMU7707E: Failed while trying to determine the Windows Service name for server: nodeagent; probable error executing WASService.exe: com.ibm.websphere.management.exception.AdminException: ADMU7709E: Unexpected exception while processing server: nodeagent; exception = java.io.IOException: Cannot run program “D:\Softwares\bin\WASService.exe”: CreateProcess error=740, The requested operation requires elevation.

 

Remedy:

Check whether the node agent service is present or not. If not create a node agent service as below.

 

WAS_HOME\bin> wasservice -add Dmgr01_NodeAgent

-servername server1 -profilePath “D:\Softwares\profiles\Dmgr01”

-wasHome “D:\Softwares” -logFile “D:\Softwares\profiles\Dmgr01\logs\nodeagent\startNode.log”

-logRoot “D:\Softwares\profiles\Dmgr01logs\nodeagent” -restart true -startType automatic

 

4.

The node LTADKAW7Node01 is not synchronized with the master configuration. This may prevent cluster member MyServer1 from starting correctly.

Remedy: Synchronize the node.

 

Cheers,

Wonders team 🙂