WebSphere Application Server (WAS)

Overview

WAS is a software product that performs the role of a web application server. More specifically, it is a software framework and middleware that hosts Java based web applications. This document is a shortened version of some of the administration tasks found in WAS 8.5 Configuration and Administration Guide.

Installation

Install/Setup IBM Installation Manager

IBM products are installed using IBM Installation Manager either through a GUI, command line, console or silently. Download and install IBM Installation Manager first before installing other software. There are many options for installing IBM Installation Manager but here we will install it on the server we want t WAS on. Commands listed here are for the console mode. You will also need a valid IBM login.

Install

cd /usr/local/src/

mkdir ibmim

cd ibmim

# Place installation manager here.

unzip agent.installer.linux.gtk.x86_64_1.8.6001.20170428_1156.zip

./installc -c

N -> A -> N -> N -> I -> R

Setup

After installing IBMIM you will be presented with the IBMIM menu. If you exit, you can start IBMIM using the command ./imcl -c. Note: You cannot install WebSphere Application Server V8.5 with Console Mode.

/opt/IBM/InstallationManager/eclipse/tools

./imcl -c

Add a repository and credentials

P. Preferences -> 1. Repositories -> D. Add Repository -> P. Provide credentials and connect -> 1. [X] Save password if valid -> O. OK -> A. Apply Changes and Return to Preferences Menu -> R. Return to Main Menu

You can now install the required software except for WAS v8.5.

1. Install - Install software packages -> Enter the master password to unlock credentials storage: -> 11. [ ] IBM WebSphere SDK Java Technology Edition (Optional) 7.0.9.60 -> 1. Choose version 7.0.9.60 for installation -> N -> N -> N

Now, as you cannot install WAS v8.5 using the console, you will need to use the command line as below. It does not appear to read the repository information entered through the console.

./imcl install com.ibm.websphere.NDTRIAL.v85_8.5.5011.20161206_1434  -repositories  http://www.ibm.com/software/repositorymanager/V85WASNDTrial -prompt -acceptLicense -properties user.wasjava=java8

Enter the master password to unlock credentials storage:

Installed com.ibm.websphere.NDTRIAL.v85_8.5.5011.20161206_1434 to the /opt/IBM/WebSphere/AppServer directory.

Profiles

There are a number of Profiles which provide for a function run time environment. They are briefly listed here but a full overview can be found in the WAS documentation.

Application server profile - The application server profile defines a single stand-alone application server. Using this profile gives you an application server that can be run in unmanaged (stand-alone) mode or managed mode (by federating it with the administrative agent profile).
Deployment manager profile - The deployment manager profile defines a deployment manager in a distributed server environment.
Custom profile - A custom profile is an empty node without any server instance that is intended for federation to a deployment manager. After federation, the deployment manager uses it as a target on which it can create, for example, application server profile instances.
Cell profile - A cell profile combines two profiles: a deployment manager profile and an application server profile.
Administrative agent profile - The administrative agent profile provides enhanced management capabilities for stand-alone application servers.
Job manager profile - A job manager is defined by a job manager profile. The job manager’s primary purpose is to support flexible management of WebSphere Application Server profiles and to queue jobs to registered servers.

Building Systems with Profiles

The following profile management tools are available.

The manageprofiles command: A command-line interface for profile management functions.
Profile Management Tool (PMT): A GUI interface delivered by the WebSphere Customization Toolbox. This tool gathers user input and invokes the manageprofiles command-line tool to manage the profiles for you. Can be started with /opt/IBM/WebSphere/AppServer/bin/ProfileManagement/wct.sh.
Administrative console of the deployment manager or the job manager profile, which can create profiles on remote machines. You will require either manageprofiles or PMT to create this profile before being able to use it.

Note: Each profile you create is registered in a profile registry, which is under: install_root/properties/profileRegistry.xml

Profiles have very similar setup and so we will cover the Application and Cell profiles here. When you create a Cell profile, you essentially create a Deployment Manager and Application profile that get federated to the Cell profile.

Creating an application server profile (GUI)

Run WebSphere Customization Toolbox.

/opt/IBM/WebSphere/AppServer/bin/ProfileManagement/wct.sh

Start creating the profile

Click Create ->

Select Application Server ->

Next ->

Advanced profile creation ->

Next ->

Select all 3 applications ->

Next ->

Specify a profile name and directory path. Change the end of the directory path to be the same as the Profile name. Select the Server runtime performance tuning setting appropriate for the install ->

Next ->

Specify the Node, Server and Host names ->

Next ->

Enable administrative security with a username and password ->

Next ->

Create a new default certificate ->

Next ->

Next ->

Change recommended ports if required ->

Next ->

Check Run the application server process as a Linux service and provide the username to run as (Must be valid) ->

Next ->

Uncheck Create a Web server definition ->

Next ->

Create

Creating an cell profile (GUI)

Run WebSphere Customization Toolbox.

/opt/IBM/WebSphere/AppServer/bin/ProfileManagement/wct.sh

Start creating the profile

Click Create ->

Select Cell (deployment manager and a federated application server) ->

Next ->

Advanced profile creation ->

Next ->

Select both applications ->

Next ->

Specify a Deployment manager profile name, an Application server profile name and a directory path. Change the end of the directory path to be the same as the Deployment manager profile name. Select the Server runtime performance tuning setting appropriate for the install ->

Next ->

Specify the Deployment manager node name, Application server node name, Host name and Cell name ->

Next ->

Enable administrative security with a username and password ->

Next ->

Create a new default certificate ->

Next ->

Next ->

Change the deployment manager recommended ports if required ->

Next ->

Change the application server recommended ports if required ->

Next ->

Check Run the application server process as a Linux service and provide the username to run as (Must be valid) ->

Next ->

Uncheck Create a Web server definition ->

Next ->

Create

Creating an cell profile (cmd)

There are 2 ways to do this from the command line. Using the command managerprofiles.sh which has a lot of arguments to present. Or by downloading the manageprofiles interactive utility which uses managerprofiles.sh under the hood. If you have multiple profiles to create, you can create a response file and amend the response file as per each profile.

Things to note. The tool has some nifty bugs. It tries to find the various port files in the directory where the profiles are created, before they are actually created. It complains that it cannot find ./PropFilePasswordEncoder.sh in the current directory even though you were in the directory when you started the tool. For the port file issue, you can tell the utility to look in /opt/IBM/WebSphere/AppServer/profileTemplates/cell/default/actions/portsUpdate/ for portdef.props and nodeportdef.props. You can also copy these files and amend the ports for you next profile so that the ports do not conflict.

Example of the utility below. The menu has been dropped after the first for brevity.

Create response files

/opt/IBM/WebSphere/AppServer/bin/run_manageprofilesInteractive.sh

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

Change the node agent recommended ports if required ->

Next ->

MANAGEPROFILES - Command Menu

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

1  create

2  augment

3  delete

4  unaugment

5  unaugmentAll

6  deleteAll

7  listProfiles

8  listAugments

9  backupProfile

10 restoreProfile

11 getName

12 getPath

13 validateRegistry

14 validateAndUpdateRegistry

15 getDefaultName

16 setDefaultName

17 response

18 help

Select number [press "q" to quit]: 1

create

nifregisty.property file was not found at "../properties/NIFRegistry.properties

.nifregisty file was not found at ""

 /bin/setupCmdLine.sh

  1  Cell profiles (cell/dmgr & cell/default)

  2  Custom profile (managed)

  3  Deployment Manager profile (dmgr)

  4  Management profile for a Deployment Manager, Administrative Agent or Job Manager server (management)

  5  Application server profile (default)

  6  Secure proxy profile (secureproxy)

  7  Other...

  8  Cancel (do nothing)

Select templatePath: 1

Default: (Dmgr01)

Enter the ProfileName

[Press "enter" to take default]:

Default: (AppSrv01)

Enter the AppServer's profileName

[Press "enter" to take default]:

Default: (server4)

Enter the Hostname

[Press "enter" to take default]:

Default: (server4CellManager01)

Enter the Nodename

[Press "enter" to take default]:

Default: (server4Cell01)

Enter the CellName

[Press "enter" to take default]:

Default: (/opt/IBM/WebSphere/AppServer/profiles/Dmgr01)

Enter the profilePath

[Press "enter" to take default]:

 /bin/setupCmdLine.sh

Default: (server4Node01)

Enter the AppServerNodeName

[Press "enter" to take default]:

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

 Required parameters summary

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

 * profileName=Dmgr01

 * profilePath=/opt/IBM/WebSphere/AppServer/profiles/Dmgr01

 * templatePath=/opt/IBM/WebSphere/AppServer/profileTemplates/cell/dmgr

 * nodeName=server4CellManager01

 * cellName=server4Cell01

 * hostName=server4

 * appServerNodeName=server4Node01

 * AppServerProfileName=AppSrv01

Press "enter" to continue ["r" to reset, "q" to quit]:

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

Optional: (following parameters are NOT required)

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

1  enableAdminSecurity              19 personalCertDN

2  adminUserName                    20 personalCertValidityPeriod

3  adminPassword                    21 signingCertDN

4  samplesPassword                  22 signingCertValidityPeriod

5  omitAction                       23 startingPort

6  debug                            24 portsFile

7  importPersonalCertKS             25 defaultPorts

8  importPersonalCertKSType         26 validatePorts

9  importPersonalCertKSPassword     27 webServerCheck

10 importPersonalCertKSAlias        28 webServerHostname

11 importSigningCertKS              29 webServerInstallPath

12 importSigningCertKSType          30 webServerName

13 importSigningCertKSPassword      31 webServerOS

14 importSigningCertKSAlias         32 webServerPluginPath

15 isDefault                        33 webServerPort

16 keyStorePassword                 34 webServerType

17 nodeDefaultPorts                 35 enableService

18 nodePortsFile                    36 serviceUserName

Enter number to select or change[press "q" to quit,"c" to continue]: 1

AdminSecurity = disabled

Enable AdminSecurity?[y/n, "c" to clear]: y

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

Optional: (following parameters are NOT required)

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

Enter number to select or change[press "q" to quit,"c" to continue]: 2

Admin username: wasadmin

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

Optional: (following parameters are NOT required)

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

Enter number to select or change[press "q" to quit,"c" to continue]: 3

Admin Password: 11july2004

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

Optional: (following parameters are NOT required)

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

Enter number to select or change[press "q" to quit,"c" to continue]: 4

Samples Password: 11july2004

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

Optional: (following parameters are NOT required)

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

Enter number to select or change[press "q" to quit,"c" to continue]: 17

Nodedefaultports = disabled

Enable Nodedefaultports?[y/n]: n

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

Optional: (following parameters are NOT required)

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

Enter number to select or change[press "q" to quit,"c" to continue]: 18

Syntax: <Full_path_to_portsfile>/<portsfile.ext>

e.g. /opt/IBM/WebSphere/AppServer//my_custom_properties/nodeportdef.props

Node ports file: /opt/IBM/WebSphere/AppServer/profileTemplates/cell/default/actions/portsUpdate/nodeportdef.props

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

Optional: (following parameters are NOT required)

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

Enter number to select or change[press "q" to quit,"c" to continue]: 24

Syntax: <WAS_Install_Root>/profiles/<dmgr_prof_name>/properties/portdef.props

e.g. /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/properties/portdef.props

Ports file: /opt/IBM/WebSphere/AppServer/profileTemplates/cell/default/actions/portsUpdate/portdef.props

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

Optional: (following parameters are NOT required)

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

Enter number to select or change[press "q" to quit,"c" to continue]: 26

validatePorts = disabled

Enable validatePorts?[y/n]: y

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

Optional: (following parameters are NOT required)

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

Enter number to select or change[press "q" to quit,"c" to continue]: 35

enableService = disabled

Enable enableService?[y/n, "c" to clear]: y

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

Optional: (following parameters are NOT required)

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

Enter number to select or change[press "q" to quit,"c" to continue]: 36

The serviceUserName MUST be a root user.

Service username: root

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

Optional: (following parameters are NOT required)

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

Enter number to select or change[press "q" to quit,"c" to continue]: c

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

CREATE command summary:

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

 * profileName=Dmgr01

 * profilePath=/opt/IBM/WebSphere/AppServer/profiles/Dmgr01

 * templatePath=/opt/IBM/WebSphere/AppServer/profileTemplates/cell/dmgr

 * nodeName=server4CellManager01

 * cellName=server4Cell01

 * hostName=server4

 * adminUserName=wasadmin

 * adminPassword=11july2004

 * appServerNodeName=server4Node01

 * enableAdminSecurity=true

 * nodePortsFile=/opt/IBM/WebSphere/AppServer/profileTemplates/cell/default/actions/portsUpdate/nodeportdef.props

 * samplesPassword=11july2004

 * portsFile=/opt/IBM/WebSphere/AppServer/profileTemplates/cell/default/actions/portsUpdate/portdef.props

 * validatePorts=enabled

 * enableService=true

 * serviceUserName=root

Press "b" to go back and make changes or "c" to continue: c

Press "q" to quit, "r" add to response file, or "c" to run the command: r

Created Command Log in ../logs/response_create_cell_dmgr_25447.txt

Notice: ./PropFilePasswordEncoder.sh was not found in current dir.

Any passwords in ../logs/response_create_cell_dmgr_25447.txt will NOT be encoded!

Created Command Log in ../logs/response_create_cell_default_25447.txt

Notice: ./PropFilePasswordEncoder.sh was not found in current dir.

Any passwords in ../logs/response_create_cell_default_25447.txt will NOT be encoded!

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

Use the created response files

/opt/IBM/WebSphere/AppServer/bin/run_manageprofilesInteractive.sh

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

MANAGEPROFILES - Command Menu

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

1 create

2 augment

3 delete

4 unaugment

5 unaugmentAll

6 deleteAll

7 listProfiles

8 listAugments

9 backupProfile

10 restoreProfile

11 getName

12 getPath

13 validateRegistry

14 validateAndUpdateRegistry

15 getDefaultName

16 setDefaultName

17 response

18 help

Select number [press "q" to quit]: 17

response

Example: /opt/IBM/WebSphere/AppServer/logs/dmgr_response.txt

Full path including response file name: /opt/IBM/WebSphere/AppServer/logs/response_create_cell_dmgr_25447.txt

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

command summary:

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

* response=/opt/IBM/WebSphere/AppServer/logs/response_create_cell_dmgr_25447.txt

Press "b" to go back and make changes or "c" to continue: c

Press "q" to quit, or "c" to continue and run the response: c

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

./manageprofiles.sh -response /opt/IBM/WebSphere/AppServer/logs/response_create_cell_dmgr_25447.txt

Created Command Log in /opt/IBM/WebSphere/AppServer/logs/manageprofilesInteractive.log

You may check /opt/IBM/WebSphere/AppServer/logs/manageprofiles/<command>.log for command status.

INSTCONFSUCCESS: Success: Profile Dmgr01 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/AboutThisProfile.txt for more information about this profile.

Elapse time: 2.1803334 minutes

Done!

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

MANAGEPROFILES - Command Menu

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

Select number [press "q" to quit]: 17

response

Example: /opt/IBM/WebSphere/AppServer/logs/dmgr_response.txt

Full path including response file name: /opt/IBM/WebSphere/AppServer/logs/response_create_cell_default_25447.txt

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

command summary:

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

* response=/opt/IBM/WebSphere/AppServer/logs/response_create_cell_default_25447.txt

Press "b" to go back and make changes or "c" to continue: c

Press "q" to quit, or "c" to continue and run the response: c

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

./manageprofiles.sh -response /opt/IBM/WebSphere/AppServer/logs/response_create_cell_default_25447.txt

Added command to /opt/IBM/WebSphere/AppServer/logs/manageprofilesInteractive.log

You may check /opt/IBM/WebSphere/AppServer/logs/manageprofiles/<command>.log for command status.

INSTCONFSUCCESS: Success: Profile AppSrv01 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/AboutThisProfile.txt for more information about this profile.

Elapse time: 22.719 seconds

Done!

As per the output, the commands run during the process can be found in /opt/IBM/WebSphere/AppServer/logs/manageprofilesInteractive.log

Test your installation.

Start WAS and browse to the following URL

chkconfig --list

server4CellManager01_was.init 0:off 1:off 2:on 3:on 4:on 5:on 6:off

service server4CellManager01_was.init start

https://server4.grow4.co.uk:9043/ibm/console/

Login

System Administration -> Cell -> Local Topology -> Expand to Nodes and Applications

Federating nodes to a cell

This can be done from the command line with the addNode command or with Deployment manager of the Cell.

From the GUI

1. Ensure that both the target application server and the deployment manager are running.

2. Open the deployment manager administrative console, and log in with administrative privileges.

3. Click System Administration -> Nodes -> Add Node.

4. Select Managed node, and click Next.

5. Enter the information about your environment and click OK.

Administration Consoles and Commands

The Administrative console can be hosted in different places dependent on your setup. Below are some of the places you can find an Administrative console.

In a stand-alone server environment it is in the application server and can only manage those resources
In a non-stand-alone server environment it is in the application server or deployment manager in case of a Network Deployment environment and can manage all resources in the cell
An administrative agent can host a console and manage application server nodes that are registered to it
Job manager console is used to manage job queues

Starting and accessing the consoles

The console is accessible through a URL like this.

http://<hostname>:<WC_adminhost>/ibm/console

https://<hostname>:<WC_adminhost_secure>/ibm/console

If you have multiple servers running, the administrative port must be different for each. To find out which port is used for each profile, run the following command.

# grep -r WC_adminhost= /opt/IBM/WebSphere/AppServer/profiles/

/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/properties/portdef.props:WC_adminhost=9060

/opt/IBM/WebSphere/AppServer/profiles/Dmgr02/properties/portdef.props:WC_adminhost=9062

]# grep -r WC_adminhost_secure= /opt/IBM/WebSphere/AppServer/profiles/

/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/properties/portdef.props:WC_adminhost_secure=9043

/opt/IBM/WebSphere/AppServer/profiles/Dmgr02/properties/portdef.props:WC_adminhost_secure=9045

To check if the service is running, run the serverstatus.sh

Google Sites

Report abuse