Tag Archive | was

Step by Step: High Availability & Fault Tolerance of Deployment Manager using NFS on Linux

The DETAILED STEPS can be downloaded from the below link

http://webspherepundit.com/wp-content/uploads/2016/08/High-Availability-Fault-Tolerance-of-the-Deployment-Manager-using-NFS-on-Linux.pdf

 

Abstract:

  • For this exercise a shared filesystem will be created using NFS 4 on which the dmgr profile will be created.
  • This filesystem would be mounted on both the Primary and secondary dmgr servers.
  • Ip alias and host alias would be used during the creation of dmgrs profiles
  • The Ip alias will be active only on one Dmgr at a time either primary or standby depending on the situation of failover or failback.
  • The dmgr process will be running on the node which hosts the ip alias .

NOTE : I have used NFS4 to simulate this scenario .. but in a productions env you could use SAN storage or any similar Technology . Also for the clustering it can be setup using any other OS based clustering available like POWER HA or RHEL Clustering etc

Env Diagram :

WebSphere Version: 8.5.5.0
OS : RHEL 6.5

dmgrHA1

Highlevel Steps :

Step1 : Install and configure NFS 4 on the Server which will hold the Dmgr profile
Step2 : Create the Shared Filesystem for Dmgr profiles on the NFS Server
Step3: Mount shared filesystem on Primary Dmgr : dmgr1.myorg.com  (10.0.0.1)
Step4: Mount shared filesystem on Standby Dmgr : dmgr2.myorg.com  (10.0.0.2)
Step5: Set Ip Alias on the Primary ie dmgr1.myorg.com (10.0.0.1)
Step6: Install WebSphere Application Server on the Primary Dmgr ie dmgr1.myorg.com (10.0.0.1)
Step7: Create the Dmgr profile on dmgr1.myorg.com
Step8: Install WebSpere Application Server on the Application Server Node ie wasnode.myorg.com (10.0.0.3)
Step9: Create AppServer profile on wasnode.myorg.com (10.0.0.3)
Step10: Federate the Appserver Profile from wasnode.myorg.com (10.0.0.3) to the Dmgr Cell
Step11: Install WebSpere Application Server on the Standby  Dmgr ie dmgr2.myorg.com (10.0.0.2)
Step12: Copy profileRegistry.xml from the dmg1.myorg.com to dmg2.myorg.com
Step13: Failover from Primary ie dmgr1.myorg.com ( 10.0.0.1) to the Standby dmgr2.myorg.com (10.0.0.2)
Step14: Testing the Failover to Standby dmgr2.myorg.com ( 10.0.0.2) from Primary ie dmgr1.myorg.com ( 10.0.0.1)
Step15: Failback to Primary ie dmgr1.myorg.com ( 10.0.0.1) from  Standby dmgr2.myorg.com ( 10.0.0.2)

 

To get automated mail updates of my Posts..
Please subscribe to the site http://webspherepundit.com
And also like the Facebook Page
https://www.facebook.com/webspherepundit

 

Integrate TDS LDAP with Websphere Applicaiton Server

Security is a critical aspect of any distributed application model. Most of the firms have a centralized repository of the users in LDAP servers like Active Directory, TDS, Open DJ etc.

Activity :
To Integrate Tivoli Directory Server LDAP with Websphere Application Server as Federated Repository

Assumptions : 
a) Tivoli Directory server is allready Installed and users are avaliable in it ( Note Any LDAP ie Active Directory , TDS , OpenDj , Sun Directory Server etc can be used )

b) Websphere Application Server is installed and profiles and servers created and running .
c) The TDS Ldap server should be reachable from the DMGR and the Nodes .. so you can test it using telnet command
From Dmgr and Node check telnet to LDAP at Port 389 ( or which ever port its is running)

Eg : telnet <Ldap IP> 389

d) In this example I have a Dmgr , Nodeagent and a server and will be integrating the Dmgr with TDS LDap

 

Steps to Integrate LDAP with WAS

Step 1: Details from the LDAP Team.
Before beginning the Ldap Integrating there are a few information  which are needed from the LDAP team ( If its not managed by you )

Basic Details needed :

Hostname/IP address of TDS Server : 10.0.0.15
Port No : 386  ( non SSL)
Bind DN : cn =root
Bind Password : password
Base Dn: dc=ibm,dc=com

Additional properties may be needed depending on your env like
User Filter:
Group filter:
User ID map:
Group ID map:  etc..

But in my case its not needed as most are default

NOTE : Ensure that the WAS admin user which we logged in the WAS console with ie wasadmin is unique in both the Filebased and in LDAP  ie the user wasadmin should not be avaliable in the LDAP  as its allready there in the FileBased Registry

And If “wasadmin” is also there in LDAP , then there will be conflict and we will be prevented to login to the admin console as “wasadmin” post the Integration with TDS.

As a best practice , keep wasadmin intact but create another user in the LDAP and later add this use to the admin group from the was console .

For eg  I have created “webadmin” as an user in the LDAP which I will add to the was administration group after the WAS integration wth LDAP in this article

This is applicable for all the users in the WAS and LDAP. It should be unique in the repositories

 

Step 2: Validating using LDAP Browsers

a) Downlaod the Ldap Browser and extract it . Then Launch the “lbe.jar”

lbe

lbe1

b) Go File >> New

lbe2

c) Give a name to the connections for recognition . I have entered TDSLDAP

lbe3

d) Go to “Connections” tab

LdapBrowser1
             1) Enter the IP Address(10.0.0.15) Port No (389) and click Fetch DN .
             2) Select dc=ibm,dc=com
            3) Uncheck  “Anonymous bind”
            4) Enter username “cn=root” and password = password
            5) Click Save and then Connect

e) We will see all the users which are there in the Ldap in the Ldap Browser console

LdapBrowser2

Step 3: Once all the information is available and validated, we can proceed with the integration of Ldap with WAS


Step 4: 
Login to the WAS Admin console with wasadmin user

url :https://10.0.0.15:9043/ibm/console 

Just to check the list of users Navigate to Users and Group >> Manage Users
We  see the List of users before the integration . Only “wasadmin” as File Based Realm

FederatedRepos0

Step 5: To Integrate Ldap .. Click  “Global Security “

FederatedRepos

Then Click “Configure” on the Federated Repositories


Step 6:
 Click on “Manage Repositories” as per the screenshot

FederatedRepos1


Step 7:
 Click  “ADD” and  , Select “LDAP repository” from the dropdown

FederatedRepos3


Step 8:
 This page we need to enter the details of the LDAP ( shared by Ldap team )
      a ) Enter the LDAP Name  (  Can be any name which will identify it . I have named it TDSLDAP )
     b )  In the Drop Down Select “IBM Tivoli Directory Server “
     c ) Enter the Bind Distintguised Name : cn=root
    d )   Enter the Bind Password : password
    e )  Here the Federated Repository properties for login is “uid” it might differ based on your              environment it could be “cn” “email id ” etc
    f )  Primary Host Name : connections.ibm.com ( you could provide the ip too )
    g )  Port No : 389
    i )  Click Apply and Save

FederatedRepos4

 

FederatedRepos5


Step 9:
 Click on Global security > Federated repositories

FederatedRepos6

Click on “Add Repositories ( LDAP custom etc )


Step 10:
 From the drop Down Select “TDSLDAP”

FederatedRepos7

Enter the Base DN in our case : dc=ibm,dc=com


Step 11:
 Click Apply and Save

FederatedRepos8


Step 12:
 Check “Allow operations if some of the repositories are down”

FederatedRepos9

This will enable us to login as wasadmin to the admin console even if the LDAP id down .


Step 13: 
Click Apply and Save

FederatedRepos10

Step 14: Do full Synchronise


Step 15:
 Stop the Servers, Nodeagent and the Dmgr

Stop Servers
/opt/IBM/WebSphere/AppServer/profiles/Custom01/bin/stopServer.sh server1

Stop Nodeagent
/opt/IBM/WebSphere/AppServer/profiles/Custom01/bin/stopNode.sh server1

Stop Dmgr
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/stopManager.sh

 

Step 16: Start the Dmgr , Nodeagent and Servers
Start Dmgr :
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/startManager.sh

Start Nodeagent :
/opt/IBM/WebSphere/AppServer/profiles/Custom01/bin/startNode.sh

Start Server :
/opt/IBM/WebSphere/AppServer/profiles/Custom01/bin/startServer.sh server1

Check for any errors for LDAP etc in the SystemOut logs


Step 17:
 Validation : Now login with the file based registry user ie “wasadmin”

We can see the users from the LDAP and also  wasadmin user from file based repository


tds1

 

 

Testing

Test 1: We will add user “santosh”  from the LDAP as a monitor role in WAS  and test it

           a ) Click User and Groups >> Administrative user Roles
Currently only “wasadmin” is available

FederatedRepos32

b )
 Click Add ,

FederatedRepos32

          c ) Select “monitor” Role
Search the users using the Search button , We will be able to see the users from the ldap
Select “santosh” and drag it to the other side

FederatedRepos33
Select OK and Save the configurations

FederatedRepos34
The user “santosh “ is added to the Administrative role as a “monitor” Role

FederatedRepos35Apply and Sync with the nodes

         d )  Now Logout

         e )  Try login with user Santosh and password: password (As mentioned in the LDAP ) 
         f )  We are able to login properly if all the setting are done correctly

FederatedRepos36
           g )  Navigate to other options and you will not see lots of options which were visible in the                            wasadmin login

FederatedRepos37
for eg under Nodes we dont see the options like Full Syncronise , Add etc


Test 2 :
 We will add webadmin this user is from the LDPA we will add it to the admin group

               a)  Click User and Groups >> Administrative user Roles
Currently only “wasadmin” is there
              b )  Click Add ,

              c )  Select “administrator” Role
Search the users using the Search button , We will be able to see the users there
Select “webadmin” and drag it to the other side

FederatedRepos38

Click OK and Save the changes

FederatedRepos39
Apply and Sync with the nodes

          d ) Now Logout

         e )  Try login with user webadmin and password: password (Password from the Ldap) 

FederatedRepos40
         f ) We will see all the options which were available for wasadmin is also available for                     “webadmin“.

 

This is how we integrate TDS LDAP with Websphere Application Server . Similarly we can integrate any LDAP like Active Directory  etc in a federated Repository .

 

 

To get regular mail updates on my Posts..
Please subscribe to the site http://webspherepundit.com
And also like the Facebook Page
https://www.facebook.com/webspherepundit

 

Important IMCL Commands

 1: Check the version of IBM Installation Manager

Command: ./imcl version

[root@wasnode tools]# pwd
/opt/IBM/InstallationManager/eclipse/tools
[root@wasnode tools]#
[root@wasnode tools]# ./imcl version
Installation Manager (installed)
Version: 1.6.2
Internal Version: 1.6.2000.20130301_2248
[root@wasnode tools]#

imclversion

=========================================================================
 2: List Installed Packages
Command: ./imcl listInstalledPackages

[root@wasnode tools]# ./imcl listInstalledPackages
com.ibm.cic.agent_1.6.2000.20130301_2248
com.ibm.websphere.IBMJAVA.v70_7.0.4001.20130510_2103
com.ibm.websphere.ND.v85_8.5.5003.20140730_1249

====> com.ibm.websphere.IBMJAVA.v70_7.0.4001.20130510_2103   JAVA SDK
====> com.ibm.websphere.ND.v85_8.5.5003.20140730_1249              WAS ND 8.5

imclinstalledversion
=========================================================================
 3: List Installed Directory
Command: ./imcl listInstallationDirectories

[root@wasnode tools]# ./imcl listInstallationDirectories
/opt/IBM/WebSphere/AppServer

The Installation of WAS ND and SDK is done at “/opt/IBM/WebSphere/AppServer

imclinstalleddirectory
=========================================================================
 4) Uninstalling packages by using imcl
Command: ./imcl uninstall
Uninstall packages from the tools directory by using Installation Manager command line (imcl) uninstall commands.
Before you begin
•To identify the package_id_version,feature_id, run the listAvailablePackages command.

Procedure
To uninstall a package by using imcl:
1) Navigate to the tool directory
2) Run the uninstall command: using imcl

imcl uninstall package_id_version,feature_id -installationDirectory installation_directory

NOTE : There are many options available with imcl, use that as per your requirement

3) List the Installed packages to verify the packages you want to uninstall
BE VERY CAREFUL BEFORE YOU SELECT THE PACKAGE IDs .. Bcoz there may be many Other Websphere Packages installed on different directories

[root@wasnode tools]# ./imcl listInstalledPackages
com.ibm.cic.agent_1.6.2000.20130301_2248
com.ibm.websphere.IBMJAVA.v70_7.0.4001.20130510_2103
com.ibm.websphere.ND.v85_8.5.5003.20140730_1249

We will be uninstalling “com.ibm.websphere.IBMJAVA.v70_7.0.4001.20130510_2103 com.ibm.websphere.ND.v85_8.5.5003.20140730_1249″

4) List the directories where the Websphere Packages are installed
BE VERY CAREFUL BEFORE YOU SELECT THE PACKAGE IDs .. Bcoz There many be many Other Websphere Packages installed on different directories

[root@wasnode tools]# ./imcl listInstallationDirectories
/opt/IBM/WebSphere/AppServer
[root@wasnode tools]#

Here I have only one location where WAS is installed

5) Launch the uninstall option for imcl command line

[root@wasnode tools]# ./imcl uninstall com.ibm.websphere.ND.v85_8.5.5003.20140730_1249 com.ibm.websphere.IBMJAVA.v70_7.0.4001.20130510_2103 -installationDirectory /opt/IBM/WebSphere/AppServer
[root@wasnode tools]#

6) Validate it using “imcl listInstalledPackages” to ensure the WAS packages are removed

[root@wasnode tools]# ./imcl listInstalledPackages
com.ibm.cic.agent_1.6.2000.20130301_2248
[root@wasnode tools]#

7) Delete the WAS Installed Folders post un-installation
/opt/IBM/WebSphere/AppServer

imcluninstall

Video

This is how we uninstall WAS ND
=========================================================================
 5: List Available Packages in the Repositories

Command: ./imcl listAvailablePackages
You need to use “imcl listAvailablePackages” command . It will display the Offerings and packages within the Repositories.

[root@wasnode tools]# ./imcl listAvailablePackages -repositories /IBMSoftware/was8.5_IHS_8.5/was8.5.5/WASND
com.ibm.websphere.ND.v85_8.5.5000.20130514_1044[root@wasnode tools]#
[root@wasnode tools]# ./imcl listAvailablePackages -repositories /IBMSoftware/was8.5_IHS_8.5/was8.5.5/SDK
com.ibm.websphere.IBMJAVA.v70_7.0.4001.20130510_2103
com.ibm.websphere.liberty.IBMJAVA.v70_7.0.4001.20130510_2103
[root@wasnode tools]#

=========================================================================

 6: Install of Websphere ND 8.5 using imcl command line

Command: ./imcl install
To install the Product using imcl command you need to use “install” Option of imcl
a) Ensure all the prerequisites are satisfied like space , permission etc
b) Extract the WAS binaries in the server which you have downloaded
c) Execute the “imcl listAvailablePackages “ in the repository to validate the packages

[root@wasnode tools]# cd /opt/IBM/InstallationManager/eclipse/tools
[root@wasnode tools]# ./imcl listAvailablePackages -repositories /IBMSoftware/was8.5_IHS_8.5/was8.5.5/WASND

com.ibm.websphere.ND.v85_8.5.5000.20130514_1044
[root@wasnode tools]#

d) Execute “imcl install” to Install the WAS ND Packages “com.ibm.websphere.ND.v85_8.5.5000.20130514_1044″

[root@wasnode tools]#./imcl install com.ibm.websphere.ND.v85_8.5.5000.20130514_1044 -repositories /IBMSoftware/was8.5_IHS_8.5/was8.5.5/WASND -installationDirectory /opt/IBM/WebSphere/AppServer -acceptLicense -sP
25%               50%                     75%                       100%
——————|——————|——————|——————|
……………………………………………………………………………………………
Installed com.ibm.websphere.ND.v85_8.5.5000.20130514_1044 to the /opt/IBM/WebSphere/AppServer directory.
[root@wasnode tools]#

Similarly you can install the SDK 7 Package too

[root@wasnode tools]# ./imcl listAvailablePackages -repositories /IBMSoftware/was8.5_IHS_8.5/was8.5.5/SDK
com.ibm.websphere.IBMJAVA.v70_7.0.4001.20130510_2103
com.ibm.websphere.liberty.IBMJAVA.v70_7.0.4001.20130510_2103
[root@wasnode tools]#
[root@wasnode tools]# ./imcl install com.ibm.websphere.IBMJAVA.v70_7.0.4001.20130510_2103 -repositories /IBMSoftware/was8.5_IHS_8.5/was8.5.5/SDK -installationDirectory /opt/IBM/WebSphere/AppServer -acceptLicense -sP25%                     50%                   75%                100%
——————|——————|——————|——————|
……………………………………………………………………………………………
Installed com.ibm.websphere.IBMJAVA.v70_7.0.4001.20130510_2103 to the /opt/IBM/WebSphere/AppServer directory.

e) List the Installed packages to verify the packages you have installed

[root@wasnode tools]# ./imcl listInstalledPackages
com.ibm.cic.agent_1.6.2000.20130301_2248
com.ibm.websphere.IBMJAVA.v70_7.0.4001.20130510_2103
com.ibm.websphere.ND.v85_8.5.5003.20140730_1249

f) List the directories where the Websphere Packages are installed

[root@wasnode tools]# ./imcl listInstallationDirectories
/opt/IBM/WebSphere/AppServer
[root@wasnode tools]#

This completes the installation of WAS ND and JAVA SDK 7

=========================================================================
 6: Updation of Websphere ND 8.5.5.1 FIXPACK using imcl command line
Command : ./imcl install

Current Version : WAS ND 8.5.5.0
New Version : WAS ND 8.5.5.1

Procedure
a) Stop All the WAS Processes ( dmgr, Nodeagent , Server ) Also Apply the Fixpack to Dmgr First before applying to other nodes

b) Take the tar backup of the WAS directories, Profiles, IIM, IIM Data ( var/ibm ) etc to revert in case of any issues

c) Check the Current version of the WAS Installation using “./imcl listInstalledPackages”

[root@connections tools]# cd /opt/IBM/InstallationManager/eclipse/tools
[root@connections tools]# ./imcl listInstalledPackages
com.ibm.cic.agent_1.8.2001.20150409_1833
com.ibm.websphere.ND.v85_8.5.5000.20130514_1044

The version is WAS ND 8.5.5.0
Imcl

d) Check the Path of the WAS installation using “./imcl listInstallationDirectories”

[root@connections bin]# cd /opt/IBM/InstallationManager/eclipse/tools
[root@connections tools]# ./imcl listInstallationDirectories
/opt/IBM/WebSphere/AppServer

Imcl3

e) Also Check the Version of WAS using “versionInfo.sh”

[root@connections tools]# cd /opt/IBM/WebSphere/AppServer/bin/
[root@connections bin]# ./versionInfo.sh
WVER0010I: Copyright (c) IBM Corporation 2002, 2012; All rights reserved.
WVER0012I: VersionInfo reporter version 1.15.1.48, dated 2/8/12——————————————————————————–
——————————————————————————–
Name IBM WebSphere Application Server Network Deployment
Version 8.5.5.0
ID ND

Imcl2

e) Extract the Fixpack zip 8.5.5-WS-WASND-FP0000001-part1.zip & 8.5.5-WS-WASND-FP0000001-part2.zip in the same Folder .

I have extracted it in /IBMsoftware/Fixpacks/WASND_8.5.5.1FP/

f) List the Available packages in the fixpack Extracted path ie /IBMsoftware/Fixpacks/WASND_8.5.5.1FP/

Command : ./imcl listAvailablePackages -repositories /IBMsoftware/Fixpacks/WASND_8.5.5.1FP/

[root@connections tools]# ./imcl listAvailablePackages -repositories /IBMsoftware/Fixpacks/WASND_8.5.5.1FP/ com.ibm.websphere.BASE.v85_8.5.5001.20131018_2242
…………………..
com.ibm.websphere.ND.v85_8.5.5001.20131018_2242
………………………..
com.ibm.websphere.NDTRIAL.v85_8.5.5001.20131018_2242
[root@connections tools]#
[root@connections tools]#

Here we can see “com.ibm.websphere.ND.v85_8.5.5001.20131018_2242″ Package .. We will upgrade this package as we are using websphere.ND.V8.5.5

Imcl5

g) Update the Fixpack using the imcl command
Command: ./imcl install com.ibm.websphere.ND.v85_8.5.5001.20131018_2242 -repositories /IBMsoftware/Fixpacks/WASND_8.5.5.1FP/ -installationDirectory /opt/IBM/WebSphere/AppServer -acceptLicense -sP

[root@connections tools]# ./imcl install com.ibm.websphere.ND.v85_8.5.5001.20131018_2242 -repositories /IBMsoftware/Fixpacks/WASND_8.5.5.1FP/ -installationDirectory /opt/IBM/WebSphere/AppServer -acceptLicense -sP
25%                  50%                     75%                     100%
——————|——————|——————|——————|
…………………………………………:….

Imcl6

h) After the completion of the above command .  check the updated version of WAS , it should be WAS 8.5.5.1 now .
We can see that the package is now “com.ibm.websphere.ND.v85_8.5.5001.20131018_2242″

[root@connections ]# cd /opt/IBM/InstallationManager/eclipse/tools/
[root@connections tools]# ./imcl listInstalledPackages
com.ibm.cic.agent_1.8.2001.20150409_1833
com.ibm.websphere.ND.v85_8.5.5001.20131018_2242
[root@connections tools]#

Imcl7

i) Check the versionInfo.sh to see if the Version of the WAS has been updated .

[root@connections tools]# cd /opt/IBM/WebSphere/AppServer/bin/
[root@connections bin]# ./versionInfo.sh
WVER0010I: Copyright (c) IBM Corporation 2002, 2012; All rights reserved.
——————————————————————————–Name IBM WebSphere Application Server Network Deployment
Version 8.5.5.1
ID ND ………….

Imcl8

j) Start the Dmgr, NodeAgent, WAS Servers after the fixpack updation and check the SystemOut.log to see if there are any errors

This is how we can easily update the fixpack using imcl

 

 

To get regular mail updates on my Posts..
Please subscribe to the site http://webspherepundit.com
And also like the Facebook Page
https://www.facebook.com/webspherepundit

=========================================================================

Silent Installation of IHS , Plugin and Customization Toolbox 8.5.5 using Response File

Following are the steps for the silent installation

1) Download the necessary packages and the fixpacks from the Passport Advantage
2) Ensure the necessary access is available .. in our case its root ( Though we can install using a non-root user)
3) Create the necessary filesystems ( we will be installing in /opt )
4) Check for sufficient space in the filesystem to extract the zip files and the installation of the Binaries

5) Install the IBM Installation Manager
You can use the Record Function of the Ibm Installation Manager .
Click on the below Link for the Post on Record Function of IIM to create the Response File

Click Here LINK :

6) I have pasted the sample Response File for Installation of IHS , Plugin and Customisation Tool

### SAMPLE RESPONSE FILE FOR IHS, PLUGIN And CUSTOMISATION TOOLBOX ###

<?xml version=”1.0″ encoding=”UTF-8″?>
<!–The “acceptLicense” attribute has been deprecated. Use “-acceptLicense” command line option to accept license agreements.–>
<agent-input acceptLicense=’true’>
<server>
<repository location=’/installers/IBMHTTP8.5.5’/>
<repository location=’/installers/WASSupplements04’/>
<repository location=’/installers/WASSupplements04’/>
</server>
<profile id=’IBM HTTP Server V8.5_MYAPP’ installLocation=’/opt/IBM/HTTPServer‘>
<data key=’eclipseLocation’ value=’/opt/IBM/HTTPServer‘/>
<data key=’user.import.profile’ value=’false’/>
<data key=’cic.selector.os’ value=’linux’/>
<data key=’cic.selector.arch’ value=’x86’/>
<data key=’cic.selector.ws’ value=’gtk’/>
<data key=’user.ihs.allowNonRootSilentInstall’ value=’true’/>
<data key=’user.ihs.http.server.service.name’ value=’none’/>
<data key=’user.ihs.httpPort’ value=’80‘/>
<data key=’user.ihs.installHttpService’ value=’false’/>
<data key=’cic.selector.nl’ value=’en’/>
</profile>
<install modify=’false’>
<offering id=’com.ibm.websphere.IHS.v85′ version=’8.5.5004.20141119_1746′ profile=’IBM HTTP Server V8.5_MYAPP‘ features=’core.feature,arch.64bit’ installFixes=’none’/>
<offering id=’com.ibm.websphere.PLG.v85′ version=’8.5.5004.20141119_1746′ profile=’Web Server Plug-ins for IBM WebSphere Application Server V8.5_MYAPP’ features=’core.feature,com.ibm.jre.6_64bit’ installFixes=’none’/>
<offering id=’com.ibm.websphere.WCT.v85′ version=’8.5.5004.20141119_1746′ profile=’WebSphere Customization Toolbox V8.5_MYAPP’ features=’core.feature,pct’ installFixes=’none’/>
</install>
<profile id=’Web Server Plug-ins for IBM WebSphere Application Server V8.5_MYAPP’ installLocation=’/opt/IBM/Plugins‘>
<data key=’eclipseLocation’ value=’/opt/IBM/Plugins‘/>
<data key=’user.import.profile’ value=’false’/>
<data key=’cic.selector.os’ value=’linux’/>
<data key=’cic.selector.arch’ value=’x86’/>
<data key=’cic.selector.ws’ value=’gtk’/>
<data key=’cic.selector.nl’ value=’en’/>
</profile>
<profile id=’WebSphere Customization Toolbox V8.5_MYAPP’ installLocation=’/opt/IBM/Toolbox‘>
<data key=’eclipseLocation’ value=’/opt/IBM/Toolbox‘/>
<data key=’user.import.profile’ value=’false’/>
<data key=’cic.selector.os’ value=’linux’/>
<data key=’cic.selector.arch’ value=’x86’/>
<data key=’cic.selector.ws’ value=’gtk’/>
<data key=’cic.selector.nl’ value=’en’/>
</profile>
<preference name=’com.ibm.cic.common.core.preferences.eclipseCache’ value=’/opt/IMShared‘/>
<preference name=’com.ibm.cic.common.core.preferences.connectTimeout’ value=’30’/>
<preference name=’com.ibm.cic.common.core.preferences.readTimeout’ value=’45’/>
<preference name=’com.ibm.cic.common.core.preferences.downloadAutoRetryCount’ value=’0’/>
<preference name=’offering.service.repositories.areUsed’ value=’true’/>
<preference name=’com.ibm.cic.common.core.preferences.ssl.nonsecureMode’ value=’false’/>
<preference name=’com.ibm.cic.common.core.preferences.http.disablePreemptiveAuthentication’ value=’false’/>
<preference name=’http.ntlm.auth.kind’ value=’NTLM’/>
<preference name=’http.ntlm.auth.enableIntegrated.win32′ value=’true’/>
<preference name=’com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts’ value=’true’/>
<preference name=’com.ibm.cic.common.core.preferences.keepFetchedFiles’ value=’false’/>
<preference name=’PassportAdvantageIsEnabled’ value=’false’/>
<preference name=’com.ibm.cic.common.core.preferences.searchForUpdates’ value=’false’/>
<preference name=’com.ibm.cic.agent.ui.displayInternalVersion’ value=’false’/>
<preference name=’com.ibm.cic.common.sharedUI.showErrorLog’ value=’true’/>
<preference name=’com.ibm.cic.common.sharedUI.showWarningLog’ value=’true’/>
<preference name=’com.ibm.cic.common.sharedUI.showNoteLog’ value=’true’/>
</agent-input>

### SAMPLE RESPONSE FILE FOR IHS, PLUGIN And CUSTOMISATION TOOLBOX ###

Sample Attachment of the Response File :IHS_Plugins_WCT_8554_Response

7) The Minimal Changes needed to suit your environment

a) Path of the Extracted Binaries and the repository.config files
<repository location=’/installers/IBMHTTP8.5.5‘/>
<repository location=’/installers/WASSupplements04‘/>
<repository location=’/installers/WASSupplements04/WASFP/’/>

b) Installation path of the IHS
<profile id=’IBM HTTP Server V8.5_MYAPP’ installLocation=’/opt/IBM/HTTPServer‘>
<data key=’eclipseLocation’ value=’/opt/IBM/HTTPServer’/>

c) Port changes for IHS
<data key=’user.ihs.httpPort’ value=’80‘/>

d) Plugin Installation Path
<profile id=’Web Server Plug-ins for IBM WebSphere Application Server V8.5_MYAPP’ installLocation=’/opt/IBM/Plugins‘>
<data key=’eclipseLocation’ value=’/opt/IBM/Plugins‘/>

e) Customization Toolbox Installation Path
<profile id=’WebSphere Customization Toolbox V8.5_MYAPP’ installLocation=’/opt/IBM/Toolbox‘>
<data key=’eclipseLocation’ value=’/opt/IBM/Toolbox‘/>

f) IIM Shared location
<preference name=’com.ibm.cic.common.core.preferences.eclipseCache’ value=’/opt/IMShared‘/>

 

8) Once the response file is ready . Save this response file in the Server at location of your choise
I have kept it in /tmp/IHS_Plugins_WCT_85_Install_Response.xml

Ensure necessary permissions are available for this file execute the imcl command

bash-3.2$ #cd /opt/IBM/InstallationManager/eclipese/tools/
#./imcl input /tmp/IHS_Plugins_WCT_85_Install_Response.xml -acceptLicense -sP

9) Once the installation is completed you can navigate to the folder locations to verify the versions and the Installation Directories of IHS , Plugin and Customization toolBox 8.5

 

To get regular mail updates on my Posts..
Please subscribe to the site http://webspherepundit.com
And also like the Facebook Page
https://www.facebook.com/webspherepundit

 

 

 

 

 

Create the DMGR Profile using Profile Management Tool

After installing the core Websphere product files for the product, you must create a profile.
You can refer to  WebSphere App Server 7.0 Installation on Linux Using GUI

Methods to create the profile
a) To create the profile you can use the graphical user interface tool that is provided by the Profile Management Tool.
b) You can also use the manageprofiles command to create profiles

Assumption :
a) The binaries are installed in /opt/IBM/WebSphere/AppServer
b) You have sudo access or root access

1) Profile Creation
Launch the Profile Management Tool
<was_root>/bin/ProfileManagement/pmt.sh

In our case its /opt/IBM/WebSphere/AppServer/bin/pmt.sh

ProfileDmgr1

2) Profile Management Tool
The PMT has loaded, the option to create a profile will be available.Click Create to start the profile creation wizard

ProfileDmgr_2

 

 

3) Environment Selection
Select which type of Profile you want to create
We would be creating the Dmgr profile . It is within the Management option

profiledmgr_4

4) Server Type Selection
Select the Deployment Manager profile and click Next

profiledmgr_5

4) Profile Creation Option
We will select the “Advanced profile creation” as we will be able to customize the path, cell names, ports etc.
Click Next

profiledmgr_6

5) Optional Application Deployment
Select the ” Deploy Administration console” this application is used to manage your application servers
Click Next

profiledmgr_7

6) Profile Name and Path
Enter the Profile Name and the Path of the DMGR profile
Click Next

ProfileDmgr_8

7) Node , Host and Cell
Enter the Node , Host and Cell of the DMGR profile
Click Next

profiledmgr_9

7) Administrative Security
Select the Administration security
Enter the admin username : in our case we would do as “wasadmin”
Enter the password
Click Next

This is user with which we can login to the admin console and the administer the cell

profiledmgr_10

8) Security Certificate
The certificates for the internal communication and access .. we will use the create “Default Personal Certificates”
Click Next

profiledmgr_11

9) Security Certificate 2
The certificate details are mentioned and the expiry duration is mentioned .. you could extent the validation of the certificate
Click Next

profiledmgr_12

10) Port Details
The Port assignment is mentioned . you could change the ports
Ensure that the ports are not in use . Else it would cause the port conflict
Click Next

profiledmgr_13
10)Linux Service Definition
Enabling this selection will create scripts in the /etc/rc.d/ to auto restart the profile when the physical restarts
Click Next

profiledmgr_14

11) Summary
Validate the summary details before creating the profile  . Click Create

profiledmgr_15

12)Profile Creation Progress
During the profile creation the logs would be created in <was_home>/logs/manageprofile/ folder
Monitor the logs for any errors

profiledmgr_16

12)Profile Creation Completed
If the profile creation is sucessful the message will be displayed .
Enable the first steps

ProfileDmgr_17

13)First Steps
Here you could validate the installation
Start the dmgr servers etc

ProfileDmgr_18

profiledmgr_19

14 ) AboutThisProfile
This text is within the <profile_home>logs/AboutThisProfile.txt
This file will contain the details of the profile like
ProfileName,Ports, Path etc

profiledmgr_20

15 ) List the profiles
Navigate to <WAS_HOME>/bin/manageprofile.sh -listProfiles
for eg /opt/IBM/WebSphere/AppServer/bin/manageprofile.sh -listProfiles

ProfileDmgr_21

16 ) Login to the admin console
Open the browser
Enter the url ; https://ipaddressofhost:9043/ibm/console
Check the Administrative Console Port Secure in AboutThisProfile.txt
Enter the
Admin username : wasadmin
Put the password and login

ProfileDmgr_22

WebSphere App Server 7.0 Installation on Linux Using GUI

Installation of Websphere 7 on Linux

a) Before Installation Some planning needs to be done
b) What version of Websphere is required to support your applications?
c) Are there any OS tweaks for the platform required for the chosen version of Websphere?
d) Ensure all the prerequisites are satisfied
e) There are supported browsers on the servers where WAS is going to be installed
f) What version of OS and fix packs are required to support the chosen version   of WebSphere?
g) What topology will you be installing and the profiles created
h) Which filesystem to download the software  does it have enough space
i) You would need the root or sudo access to install it ( though you can use the non-root installation ) It can get   tricky due to permission issues   So within the scope of this training we would install using root
j) Ensure that X11 rpms are installed and the Linux server has a GUI or X11 Forwarding enabled

Installation of Websphere Application Server 7 using GUI
1) Getting the Software Package
a) Login to the Passport Advantage using the Customers Login
b) Download and save the software dump to the server where you want to install
c) Ensure there is sufficient space in the filesystem where you are going to extract the files
d) Identify which filesystem you want to install

2) Extracting the WAS 7 Software  
a) Login as root
I have saved the software for WAS 7 at /IbmSoftware/was
b) They are in the *.tar.gz formart
c) Use gunzip to unzip the each files ie there are 3 files
#cd /IbmSoftware/was
#gunzip C1G34ML.tar.gz
Similarly do it for all the files
Screenshot :

install1
d) Ensure all the 3 files are extracted in the same folder
e) Untar all the 3 files in the same location
for eg  #tar -xvf C1G34ML.tar
Screenshot :

install2

After the Extraction

install_3

f) After the extraction of all the tar files

3) Execute the ./launchpad.sh

4) Installation wizard welcome screen
It will be presented with the installation wizard welcome screen

install_launchpad11

Clicking on Next will take you to the software license agreement screen

5) Software license agreement
Accept the license agreement and click Next

install_7

6) System prerequisites check
The installer will check to ensure that your Linux OS meets the required prerequisites.
Click Next

install_8

7) Optional features
To enable the installation of samples by checking the Install the Sample applications checkbox.

install_14

Click Next

8) Installation directory
Specify the path where you want to install the Websphere Binaries.

install_9

In our case its /opt/IBM/WebSphere/AppServer

9) Profile Management Tool
After the base binaries are installed, we will use another tool called the  Profile Management Tool
to demonstrate how to independently create an application server profile.
We select None .Click Next

Install_15

10) Centralized Installation Manager
We don’t select the Repository and we keep it unselected as we dont want to create this repository. Click Next

install_16

11) Installation Progress
Click Next and the installation process will start and the progress will be shown

install_13

12) Successful Installation

install_12

Click Finish

13) Validate the Files System where the WAS is installed . In our case its /opt/IBM/WebSpere/AppServer

14) To check to see if the base binaries have installed correctly
Run the WebSphere command script installver.sh which is found in the bin folder
<was_root>/bin/installver.sh

install_17

15) This completes the installation of WAS 7 using GUI

 

Change the password for the FileBased Registry users in WAS

Question : Change/Reset the password for the FileBased Registry users in WAS console
Answer : This can be done by the Manager Users option in the admin console .

TTHIS IS ONLY APPLICABLE FOR FILE BASED REGISTRY

  1. Log in to the console of impact, which by default is https://servername:9060/ibm/consoleconsole_login
  2. Login as User ID = wasadmin password= <CURRENT PASSWORD>
  3. Then Click on User and Groups >> Managed Users
  4. Click on Search button, this will display the users you have:

manageusers

5.  Click on  “wasadmin”.  The following window will come up:

manageusers1

6.  Enter the new password in the Password field and Confirm password. Then click OK. Sync the Nodes

7. Log out from this page.

8. Restart the Server

9. Login with the new Password

Change the Password for Wasadmin in Websphere

Questions : Forgot password and cannot access WebSphere Application Server administrative console

Questions : Manually change the wasadmin WebSphere Application Server

Answer : If the wasadmin ID is in the File Based Registry

WARNING: Please use this as the last resort and make sure the server is not in the middle of processing any transactions.

There are 2 possible methods for disabling security:
======================================================================================
By way of wsadmin command:

  1. Login to the Dmgr as the OS user
  2. Navigate to  /<WAS_INSTALL_DIR>/bin/
  3. Execute $./wsadmin -conntype NONE
  4. wsadmin> securityoff
  5. wsadmin> exit
  6. Restart the servers.
  7. Enable the security from administrative console.
  8. Restart the servers.

======================================================================================

By way of manual edit of security.xml file, which is typically located in

<WAS_POFILE_HOME>/config/cells<CELL_NAME> /:

  1. Create a copy for security.xml file, in case you need to roll back.
  2. Disable the security from the security.xml file (change the very first occurrence of… enabled=”true” to enabled=”false”)
  3. Sync the Nodes
  4. Restart the servers.
  5. Enable the security from administrative console.
  6. Restart the servers.

======================================================================================

If WAS is using LDAP for the Authentication and authorization .

Ask the LDAP Administrator to reset the password for wasadmin