IBM WebSphere ND Installation & Upgrade

 

How to Install IBM WebSphere and apply Fix Pack?

Procedure to install IBM WebSphere 8.5.5. Network Deployment and apply Fix Pack.

Pre-requisite

In order to install WebSphere ND, you must have product downloaded from IBM or some organization will have a custom package built by their engineering team. In either way – you should have the product package ready to get it installed.

To install WebSphere, you will also need IBM Installation Manager. IBM Installation Manager is needed to install WebSphere. If you are working on WebSphere ND 7 then it’s something new for you, as it was not needed in prior to WebSphere 8 ND. IM is also required to apply fix pack in WebSphere 8.5.5 version.

Component Version Supported Matrix

You will also need to check the supported matrix as listed below for Java SE, Java EE, Servlet, JSP, JSF, EJB, JMS, JDBC. Usually, a developer will confirm this.

  8.5.5 8.5 8.0 7.0 6.1
Java SE 6 & 7 6 & 7 6 6 5
Java EE 6 6 6 5 1.4
Servlet 3.0 3.0 3.0 2.5 2.4
JSP 2.2 2.2 2.2 2.1 2.0
JSF 2.0 2.0 2.0 1.2 1.1
EJB 3.1 3.1 3.1 3.0 3.0
JMS 1.1 1.1 1.1 1.1 1.1
JDBC 4.1 4.0 4.0 4.0 3.0

BONUS (Download in PDF Format): WebSphere ND 8.5.5 Installation & Upgrade Guide

Downloading IBM Installation Manager

IBM IM can be downloaded from IBM website as explained here. Keep in mind you need to have IBM ID in order to download the IBM IM and WebSphere.

If you don’t have one, you can create one by registering yourself at

https://www.ibm.com/account/profile/us?page=reg

I assume you have IBM ID ready. Let’s start downloading IBM IM.

  • Open your favorite Internet browser
  • Download IBM IM 1.8.3 by clicking here
  • Select the one based on your platform. In this demonstration, I will proceed with Linux 64 bit.

  • Click on “Continue” and you will be given an option to either download using Download Director or using a browser (HTTPS).

  • Click on “Continue” to get the download link.

  • Click on the link to start downloading. It may take few minutes based on your Internet speed.
  • Once downloaded, you should have the following file
agent.installer.linux.gtk.x86_64_1.8.3000.20150606_0047.zip

Downloading WebSphere 8.5.5 ND

IBM offers 60 days trial for WebSphere ND Full profile, which I will use in this demonstration.

  • Open your favorite Internet browser
  • Access the following link
https://www-01.ibm.com/marketing/iwm/iwm/web/download.do?source=swerpws-wasnd85&S_PKG=500026211&S_TACT=109J87BW&lang=en_US&dlmethod=http
  • You will see many products listed here, but following three is in our interest.

  • Click on “Download now” for all three parts. It may take few minutes based on your Internet speed.
  • Once downloaded, you should have following three files.
was.repo.8550.ndtrial_part3.zip
was.repo.8550.ndtrial_part2.zip
was.repo.8550.ndtrial_part1.zip

Installing IBM Installation Manager

  • Go to the path where you have downloaded the IBM IM Zip file
agent.installer.linux.gtk.x86_64_1.8.3000.20150606_0047.zip
  • unzip the file by using unzip command
unzip agent.installer.linux.gtk.x86_64_1.8.3000.20150606_0047.zip
  • Once extracted, you should see following

Let’s start the installation by executing install file

./install

It will start installation process in GUI mode, click on Next 

  • Accept the license agreement and click Next

By default, it will install in /opt/IBM however, if you wish to change the directory, you can change it in this screen. 

  • Review the installation summary information and click on Install to begin the installation.
  • If you wish to change anything (like a path), you can click on Back and do so.

It may take few seconds and give you confirmation on the package was installed. 

You can close the window by clicking on a Close button.

Installing WAS 8.5.5 ND

Installation in GUI mode is easy and recommended for new WebSphere learner.

  • Go to the path where you have downloaded the following zip files.
was.repo.8550.ndtrial_part3.zip
was.repo.8550.ndtrial_part2.zip
was.repo.8550.ndtrial_part1.zip
  • Extract them by using unzip command
unzip was.repo.8550.ndtrial_part3.zip
unzip was.repo.8550.ndtrial_part3.zip
unzip was.repo.8550.ndtrial_part3.zip
  • Once extracted, you should have following

Let’s launch IBM Installation Manager to install the WebSphere ND.

Go to the path where you have installed IM. If you haven’t changed the path from default value then; 

cd /opt/IBM/InstallationManager/eclipse/
  • Execute IBMIM to launch it
./IBMIM
  • You will get Installation Manager wizard likes below

  • Click on File >> Preferences
  • Click on Add Repository
  • Click on Browse to select the repository.config file. Repository.config file will be available in a path where you have extracted the downloaded WebSphere zip file.

  • Click Ok and Ok again.

You have successfully configured repository.config, which is necessary to begin the installation. Click on Install icon on the wizard. 

  • Select the checkbox before version and click on Next

  • Accept the license agreement and click Next

  • Select the resource directory and click Next. You may leave it to the default path.

  • Select the path where WebSphere will be installed. If you are happy with installing under /opt/IBM/WebSphere then leave it to default path and click on Next

  • Select the language translation if needed, click on Next

  • You can choose the features to be installed in next screen. Most of the time you want to proceed with “Sample applications” as it helps administrator to deploy and test the environment. Click on Next

 

Finally, you will get review summary information. You can click on Back if anything to be changed else click on Install 

It may take few minutes to install and once completed, you will have following confirmation.

  • Select “None” and click on Finish

Great, so now you are familiar with WebSphere Installation procedure.

Applying WebSphere Fix Pack 

One of the essential tasks for WebSphere administrator is to ensure technology stack in a production environment is up-to-date. There are many including security, feature enhancements & bug fixes are released by IBM.

Downloading fix pack

Fix pack 6 is the latest pack available for WebSphere 8.5.5 which is shown in below demonstration.

  • Open your favorite Internet browser
  • Access the following link
http://www-01.ibm.com/support/docview.wss?uid=swg24040035
  • Select the zip file for your desired platform. I am using Linux, so I will proceed with the download for “Distributed” platform.

Fix pack 6 is available in two parts so you got to download both of them as shown below and click on Continue

  • Log in with your IBM ID to download the fix pack

  • Click on each file (part 1 & part 2) to download

  • Once downloaded, you should have the following file
8.5.5-WS-WAS-FP0000006-part1.zip
8.5.5-WS-WAS-FP0000006-part2.zip

Installing Fix Pack

Go to the path where you have downloaded the fix pack zip file

  • Extract them by using unzip command
unzip 8.5.5-WS-WAS-FP0000006-part1.zip
unzip 8.5.5-WS-WAS-FP0000006-part2.zip

Before you proceed to apply fix pack, you have to ensure WAS is not running. It would be also a good idea to take an entire WebSphere backup if you are doing in a critical environment.

  • Launch IBM Installation Manager
  • Click on File >> Preferences
  • Click on Add Repository
  • Click on Browse and select repository.config, which you got above after extracting fix pack
  • Click on OK

  • You should have something like below, click on OK to continue

  • Click Next

It will give you confirmation that Version 8.5.5.6 is recognized in a repository.config file. Click on Next

  • Accept the terms and click next

  • Here you can customize the features if you wish. Click on Next

  • Review the summary information and click on Update

It will take few minutes and at the end, you will have success message as shown below.

This indicates you have applied Fix Pack 6 on 8.5.5 version and now WAS version is 8.5.5.6.

I hope this helps you to understand the IBM WebSphere installation procedure.

Credits to Chandan Kumar

Anúncios

The Cognitive Scheduling

$2A2BD674772FFE2A

Name: The Cognitive Scheduling

Automation to re-schedule cancelled appointments.

More than 25 millions of doctor appointments are scheduled per year. Because of no-show, the loss in the pillar Psyquiatric is between 11 and 19 millions of dollars per year.

Because of this, the automation solve problem recorrences of Doctors, Therapists, Meetings, Beauty Salon and others.

Know more:

DEMO: https://www.youtube.com/watch?v=I3r-gqG3NYo
SWOT: https://prezi.com/p/35zkia3bxrcx/
GitHub: https://github.com/wagnersouz4/cognitive-scheduling

Share our project: https://ibm.biz/cognitivescheduling

 

 

Administrative Console in the IBM WebSphere Liberty Profile running on Raspberry Pi

Overview

Skill Level: Any Skill Level

Here you will learn step-by-step on how to install and configure the Administrative Console in the IBM WebSphere Liberty Profile.

Ingredients

Download the IBM WebSphere Liberty Profile

Operational System can be IBM AIX, other Unix-like, Windows or z/OS.

Step-by-step

  1. Extract the IBM WebSphere Liberty Profile

    After to download the IBM WebSphere Liberty Profile, so-called WLP, from IBM’s site, just extract to some folder.

    You must not have root’s privilege to run the WLP.

     

    $ unzip wlp-webProfile7-17.0.0.2.zip
  2. Create an encrypted password for keyStore’s certificate

    This password is used by WLP in order to load the certificate over HTTPS instance. It is a must have for Administrative Console.

    The tool securityUtility is going to be used, with the parameter encode and –encoding=aes. At this time, AES cryptography is used.

     

    $ wlp/bin/securityUtility encode --encoding=aes igormonteirovieiraaa
    
    Result: "{aes}ALdLTXUQf7HvUNqRxxFT4yDSMGMUw6Oe5TcawHZAK8LRGNlivTITq3km/Mc82t7EVA=="
  3. Installing the adminCenter-1.0, an Administrative Console for IBMe WebSphere Liberty Profile

    The IBM WebSphere Liberty Profile comes with less features installed as possible, in order to be the most lightweight and secure Application Server in the market and for administrative’s purposes.

    In order to get Administrative Console, the correspondent package is adminCenter and must be installed through the following way:

     

    $ wlp/bin/installUtility install adminCenter-1.0
  4. Creating the server.xml for IBM WebSphere Liberty Profile

    At this time, the previous libraries were added to the filesystem and the WLP’s server.xml is bound to be created. A start is required to get these settings valid.

     

    $ wlp/bin/server start

     

    After this start, the server.xml was created underneath wlp/usr/servers/defaultServer/.

  5. Loading the Administrative Console

    Everytime either a module, library or plugin is installed through installUtility application, it must be pointed into server.xml.

    As best practice, better to stop the WLP before changing these parameters.

     

    $ wlp/bin/server stop

     

    To include the new features in the server.xml:

     

    $ vi wlp/usr/servers/defaultServer/server.xml

     

     

     

    <featureManager>
    <feature>adminCenter-1.0</feature>
     <feature>ssl-1.0</feature>
     </featureManager>
    
    <administrator-role>
     <user>admin</user>
    </administrator-role>
    
    <basicRegistry id="basic">
     <user name="admin" password="admin"/>
     <user name="nonadmin" password="nonadmin"/>
    </basicRegistry>
    
    <keyStore id="defaultKeyStore" password="{aes}ALdLTXUQf7HvUNqRxxFT4yDSMGMUw6Oe5TcawHZAK8LRGNlivTITq3km/Mc82t7EVA==" />
  6. Starting the Administrative Console wlp/bin/server start

    Pre-requisites:

    1. installUtility used to install:
      1. adminCenter-1.0
    2. server.xml configured with:
      1. adminCenter-1.0 as feature
      2. ssl-1.0 as feature
      3. administrative-role
      4. basicRegistry
      5. keyStore

     

    Starting the server:

     

    $ wlp/bin/server start

    The log is placed underneath wlp/usr/servers/defaultServer/logs/. There are two, console.log and messages.log. In case of error, ffdc will be created as well. Expected console.log:

    $ tail -f wlp/usr/servers/defaultServer/logsconsole.log 
    
    Launching defaultServer (WebSphere Application Server 17.0.0.2/wlp-1.0.17.cl170220170523-1818) on Java HotSpot(TM) Client VM, version 1.8.0_65-b17 (en_US)
    [AUDIT ] CWWKE0001I: The server defaultServer has been launched.
    [AUDIT ] CWWKE0100I: This product is licensed for development, and limited production use. The full license terms can be viewed here: https://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/license/base_ilan/ilan/17.0.0.2/lafiles/en.html
    
    [AUDIT ] CWWKZ0058I: Monitoring dropins for applications. 
    [AUDIT ] CWWKF0012I: The server installed the following features: [jsp-2.3, ejbLite-3.2, managedBeans-1.0, servlet-3.1, jsf-2.2, beanValidation-1.1, ssl-1.0, jndi-1.0, appSecurity-2.0, jsonp-1.0, jdbc-4.1, jaxrs-2.0, restConnector-1.0, el-3.0, jaxrsClient-2.0, json-1.0, jpaContainer-2.1, adminCenter-1.0, cdi-1.2, distributedMap-1.0, webProfile-7.0, websocket-1.1, jpa-2.1].
    [AUDIT ] CWWKF0011I: The server defaultServer is ready to run a smarter planet.
    [AUDIT ] CWWKT0016I: Web application available (default_host): http://192.168.1.102:9080/ibm/adminCenter/serverConfig-1.0/
    [AUDIT ] CWWKT0016I: Web application available (default_host): http://192.168.1.102:9080/IBMJMXConnectorREST/
    [AUDIT ] CWWKT0016I: Web application available (default_host): http://192.168.1.102:9080/ibm/api/
    [AUDIT ] CWWKT0016I: Web application available (default_host): http://192.168.1.102:9080/ibm/adminCenter/explore-1.0/
    [AUDIT ] CWWKT0016I: Web application available (default_host): http://192.168.1.102:9080/adminCenter/
    [AUDIT ] CWPKI0803A: SSL certificate created in 31.868 seconds. SSL key file: /home/pi/wlp/usr/servers/defaultServer/resources/security/key.jks
    
    ^C

     

  7. Accessing the Administrative Console of the IBM WebSphere Liberty Profile

    To specific an IP to the URL, the parameter host=”IP” must be inserted in the server.xml at the tag httpEndpoint. The server.xml‘s content must looks like:

     <httpEndpoint id="defaultHttpEndpoint" host="192.168.1.102"
     httpPort="9080"
     httpsPort="9443" />

    A restart may be required in case of changing this IP.

    Use the URL http://localhost:9080/adminCenter/.

    IBM WebSphere Liberty Profile, Administrative Console

Certificate Management

Commands:
# openssl x509 -in cert.crt -text -noout
# openssl req -text -noout -verify -in cert.csr

Listing contents of new certificate:

# openssl x509 -in cert.crt -text -noout
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
19:67:76:8b:79:ad:7f:52:52:01:3d:89:45:6d:9b:cc
Signature Algorithm: sha256WithRSAEncryption
Issuer: C=US, O=Symantec Corporation, OU=Symantec Trust Network, CN=Symantec Class 3 Secure Server CA – G4
Validity
Not Before: May 23 00:00:00 2016 GMT
Not After : Aug 7 23:59:59 2017 GMT
Subject: C=, ST=, L=, O=, OU=, CN=
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Modulus:
00:be:c2:51:07:9a:98:03:a4:b2:1d:71:64:2b:13:
54:15:2c:9b:fc:6a:9b:57:24:fc:b9:c0:ea:26:d0:
7c:35:a6:30:19:31:2a:e0:55:51:35:f5:57:da:7a:
01:ca:36:b4:3a:ee:48:3c:61:0e:a4:77:ac:f8:6e:
fd:00:56:92:ba:ba:11:20:a0:69:97:0d:e8:97:98:
1a:ad:2f:e8:61:f2:c6:25:fe:56:7c:2a:89:a1:57:
11:2d:e1:3e:e9:3a:d9:e9:a7:d0:f6:48:a6:be:5b:
f8:6b:77:b5:22:eb:a0:80:57:de:2f:56:41:23:28:
8e:05:09:b2:5d:ba:36:6d:ef:f7:e3:45:59:7f:ba:
22:94:cc:97:db:56:16:f8:7f:be:29:79:71:d2:bf:
b0:9f:a4:55:37:9a:a5:0d:c0:34:0b:e0:33:ba:3d:
75:a5:39:52:80:51:c2:68:a3:db:77:ae:98:b5:7b:
f1:ac:be:88:fd:61:11:03:de:f0:f6:7a:87:3c:ad:
03:58:30:19:5e:3c:25:d3:e1:fe:d6:99:8e:0f:9b:
e0:84:8c:48:0d:97:f2:40:55:dc:7e:75:8e:97:3f:
71:aa:2b:7f:71:b0:26:85:fb:ac:30:95:5a:8d:db:
9c:36:c0:0f:79:34:cc:12:99:37:79:7a:23:71:c4:
9a:67
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Subject Alternative Name:
DNS:
X509v3 Basic Constraints:
CA:FALSE
X509v3 Key Usage: critical
Digital Signature, Key Encipherment
X509v3 Extended Key Usage:
TLS Web Server Authentication, TLS Web Client Authentication
X509v3 Certificate Policies:
Policy: 2.23.140.1.2.2
CPS: https://d.symcb.com/cps
User Notice:
Explicit Text: https://d.symcb.com/rpa

X509v3 Authority Key Identifier:
keyid:5F:60:CF:61:90:55:DF:84:43:14:8A:60:2A:B2:F5:7A:F4:43:18:EF

X509v3 CRL Distribution Points:

Full Name:
URI:http://ss.symcb.com/ss.crl

Authority Information Access:
OCSP – URI:http://ss.symcd.com
CA Issuers – URI:http://ss.symcb.com/ss.crt

1.3..2.4.2:
.@.}…!….B.G6….VLj..F.>v<.A..i.5.-…w…….X……gp…..4…..
…..T.y^……H0F.!..2L.qQ]g..D.
g..OO…..T.y^……F0D. c.TG…_8M…..L..X..>c.5…+.S.. |C..-..jfIf.S.Z.[EhRC…9LH6..1N
Signature Algorithm: sha256WithRSAEncryption
1c:f5:77:99:c5:d3:08:5f:b9:39:5c:f8:11:28:fa:f1:4d:
92:8a:9b:dd:13:29:49:82:5e:36:eb:7b:86:a0:35:ea:a2:d0:
09:5e:bd:13:d4:c7:c2:13:c8:a0:99:7e:34:82:32:8b:25:e8:
ac:62:54:db:6c:b8:fc:f6:25:a0:24:28:71:fd:a9:7e:63:9a:
bd:a8:73:16:3a:d0:35:61:20:76:6f:7e:21:fc:e6:48:
32:e9:4a:f3:ec:13:35:87:db:9a:7e:8f:6d:b4:7e:09:bc:42:
d1:cf:f4:f8:a9:94:83:1a:25:55:5b:26:98:24:69:a5:5b:d5:
fb:21:82:a9:43:8e:eb:32:54:2c:27:24:70:c3:d3:3e:b8:82:
b2:1a:b4:70:2c:1e:da:de:25:52:fa:f8:82:d3:33:25:cb:20:
55:a8:8e:46

 


Listing contents of CSR:

# openssl req -text -noout -verify -in cert.csr
verify OK
Certificate Request:
Data:
Version: 0 (0x0)
Subject: C=, ST=, L=, O=, OU=, CN=
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Modulus:
00:cc:91:88:d6:95:df:ed:3a:c1:0d:18:5e:a0:22:
9e:95:78:d4:90:76:87:7c:b2:42:20:9a:68:22:42:
31:10:68:08:7f:37:78:b0:6c::ee:26:9c:c9:
1e:6d:42:5a:e6:55:22:76:f4:4e:8e:d9:50:ce:4f:
e6:5c:18:54:f8:f3:08:b4:e9:9e:e2:8b:48:ca:44:
fb:a2:14:a5:50:eb:46:2d:73:2e:8b:71:e7:57:88:
69:14:c2:ae:80:bb:b7:5f:c9:5f:5a:00:31:94:21:
61:a9:44:26:61:30:74:d4:9d:5c:09:ba:20:cc:c5:
c4:22:aa:2b:5d:c6:40:d7:6c:e5:d6:1e:47:90:be:
ce:69
Exponent: 65537 (0x10001)
Attributes:
Requested Extensions:
X509v3 Subject Alternative Name:
DNS:
X509v3 Extended Key Usage: critical
TLS Web Server Authentication
X509v3 Key Usage: critical
Key Encipherment, Key Agreement
Signature Algorithm: sha256WithRSAEncryption
c6:c3:c2:fe:89:6b:4d:2c:df:e8:a6ee:41:6f:a9:25:f1:
87:9f:51:5f:61:96:76:9b:d9:bd:36:da:67:b8:71:c1:c6:3e:
22:df:7e:d3:84:82:91:15:ea:78:4a:d5:e0:ef:f6:e8:32:21:
cf:e6:5d:67:05:53:c6:32:fb:41:92:93:9b:d4:72:c8:d4:27:
82:dc:bc:44:89:cc:13:78:fc:98:3a:7e:4b:c4:13:40:e3:19:
e6:99:71:fa:53:f7:7e:c3:2d:83:28:d9:34:b1:94:b9:bd:18:
0b:73:2e:99:9f:6e:ad:2d:af:86:6f:d3:28:d5:85:77:e0:70:
cd:75:d8:e7:ee:70:e9:d7:d4:a6:24:75:6a:0b:e6:c6:68:b9:
47:be:82:ac:58:f8:2e:65:58:b0:ed:a1:89:b3:85:e5:d3:51:
ee:cd:c1:2b:20:ef:06:9e:56:ca:05:78:2f:5c:db:a0:77:a7:
75:04:1c:b7

Unix

AIX

The %CPU is the percentage of CPU time that has been allocated to that process since the process was started.
#ps aux

# lsvg -o
rootvg
crsrdb_bin
crsprdb_data
crsprdb_index
crsprdb_arch
crsprdb_rman

# lsattr -El sys0 -a realmem

Display CPU usage by process and thread id. The TID column shows the threadID:
#ps -efmo THREAD

#tprof -skex sleep 60

Display processes with the highest CPU utilization:
#ps -eo pid,pcpu,args | sort +1n

To find the threadid (tid) of a known process that is using CPU:
#ps -mp <WLS_PID> -o THREAD

Display processes with the highest memory usage:
#ps -eo pid,vsz,args | sort +1n

To see your server utilization in IBM AIX including top processes, CPU usage, memory, virtual memory, paging space, I/O and load:

# topas
#topas -E
To list the top ten users of paging space in IBM AIX:
#svmon -Pgt 10 (paging)

To list the top ten users of realmem in IBM AIX:
#svmon -Put 10

To find memory usage:
#svmon -u | more
#svmon -P | more


LINUX

Show a breakdown of utilization by an individual processor. The command shows the kernel level, user CPU, system CPU, nice time, idle time, wait time and interrupts per second. Similar data can be obtained with the sar command.
#mpstat

Display five reports of statistics for all processors at two second intervals, enter:
# mpstat -P ALL 2 5

List processes by % CPU usage:
#ps -e -o pcpu,cpu,nice,state,cputime,args

Displays the top ten CPU users on the Linux system:
#ps -eo pcpu,pid,user,args | sort -k 1 -r | head -10
OR
#ps -eo pcpu,pid,user,args | sort -r -k1 | less

List all threads for a particular process:
#ps -C <process> -m -o pid,tid,pcpu,state

List processes by memory usage:
#ps -e -orss=,args= | sort -b -k1,1n | pr -TW$COLUMNS

Show the amount of (remaining) RAM (-m displays in MB):
#free -m

An interactive tool that allows a system administrator to view the process table in order of CPU or memory usage, by user, and at varying refresh rates in real-time.

#top

Solaris:

Show all top threads to determine what could be using the most CPU:
#prstat -Lmc -p <pid>
#prstat -L -p <pid> 1 1

To show the PID, user, state, and thread id:
#ps -Le -o pid,user,s,lwp,pcpu,args | awk ‘$3 != “S” { print }’

Reports paging activity details for applications (executables), data (anonymous) and filesystem activity:
#vmstat -p

Prints out details of memory use by a process:
#pmap -x <pid>

To find how much disk space is used by users in kilobytes in Solaris:
#quot -af

Commands that can be used on most UNIX platforms

Running iostat provides much information, but the values of concern are %user and %sys. If (%user + %sys) > 80 percent over a period of time, then it is likely the bottleneck is CPU. In particular, it is necessary to watch for average CPU being greater than 70 percent with peaks above 90 percent.

#iostat

To report system-wide process use, swapping, memory use, disk I/O and CPU use:
#vmstat

To provides statistics on the average length of the run queue, the percentage of time the run queue is occupied, the average length of the swap queue and the percentage of time the swap queue is occupied.

#sar

Breaks the time into user, system, time waiting for blocked I/O (i.e., NFS, disk, etc.) and idle time.
#sar -u
#sar -q
#sar -k
# sar -d 1 2
One advantage to using sar is that you can write the data to a file and then post-process it when the system is not busy. The file is created using the -a and -o flags. An example of creating a file of 30 snapshots, each two seconds apart, would look like:

#sar a o sardata.out 2 30

This file would then be processed using:
#sar -u -f sardata.out

Mainframe & WebSphere

This is a non-structured content, of which are laboratories for learning purposes.

 

Getting a file from Mainframe:

Commands:
SDSF
ST
PRE JOBNAME
XDC JOBNAME
data set name = 'ID.RESULTS'
disposition = NEW
ISPF
3,4
DSNAME = ID.RESULTS
MENU > ACTIONS > RECEIVE FILES FROM HOST.

xdc

xdc2

xdc4

 
  Software architecture WebSphere mainframe 

Body language as your super power

This is a non-structured content. On other hands, I went through very interesting materials, of which has valuable illustrations and descriptions.

A Essencia da Mente_Steve Andreas (Portuguese version)

Joy:

joy.png

Anger:

anger.png

Disgusting:

pincer-levres.jpg

images.jpgdonald_trump59-620x412.jpg3183973_1363891117018.74res_404_404.jpg

Screen Shot 2016-06-14 at 11.58.54 PM.png

WebSphere Application Server

Commands:
backupConfig.sh
stopServer.sh
stopNode.sh
stopManager.sh
startManager.sh
startNode.sh
startServer.sh

Backing up:

[username@machine bin]$ /opt/IBM/WebSphere/bin/backupConfig.sh
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/profiles/node1/logs/backupConfig.log
ADMU0128I: Starting tool with the node1 profile
ADMU5001I: Backing up config directory
/opt/IBM/WebSphere/profiles/node1/config to file
/opt/IBM/WebSphere/bin/WebSphereConfig_2016-11-03.zip
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: server1
ADMU2010I: Stopping all server processes for node node1
Realm/Cell Name:
Username: wasuser
Password: ADMU0510I: Server server1 is now STOPPED
……………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………..
ADMU5002I: 1,025 files successfully backed up

STOP

/opt/WebSphere/AppServer/profiles/managedNode/bin/stopServer.sh server1 -username UserName -password Password

/opt/WebSphere/AppServer/profiles/managedNode/bin/stopNode.sh -username UserName -password Password

/opt/WebSphere/AppServer/profiles/Dmgr01/bin/stopManager.sh -username UserName -password Password

START

/opt/WebSphere/AppServer/profiles/Dmgr01/bin/startManager.sh

/opt/WebSphere/AppServer/profiles/managedNode/bin/startNode.sh

/opt/WebSphere/AppServer/profiles/managedNode/bin/startServer.sh server1

Install a JAR, a file system’s perspective:

The VENDOR.jar file must be installed in the /opt/IBM/WebSphere/AppServer/lib/. Just copy the VENDOR.jar into that folder and restart the server.

Single Sign On WebSphere App Server:

  1. Ensure that Application Security is enabled.
    1. WebSphere Console
      1. Security
        1. Global Security
          1. Application Security
            1. Enable application security
            2. Ensure that Trust association is enabled.
              1. WebSphere Console
                1. Security
                  1. Global Security
                    1. Authentication
                      1. Web Security
                      2. Trust association
                        1. General Properties
                          1. Enable trust association
            3. Add additional interceptors and attributes
              1. WebSphere Console
                1. Security
                  1. Global Security
                    1. Authentication
                      1. Web Security
                      2. Trust association
                        1. Additional Properties
                          1. Interceptors
                          2. New
            1. Ensure Web Authentication is enabled for URIs requests
              1. WebSphere Console
                1. Security
                  1. Global Security
                    1. Web Security
                      1. General settings
                        1. General Properties
                          1. Web authentication behavior
                            1. Authenticate only when the URI is protected.
            2. Ensure Single Sign-on is enabled
              1. WebSphere Console
                1. Security
                  1. Global Security
                    1. Web Security
                      1. Single Sign-on (SSO)
                        1. Enabled
                        2. Web inbound security attribute propagation
            3. Ensure external authorization providers
              1. WebSphere Console
                1. Security
                  1. Global Security
                    1. External Authorization providers
                      1. General Properties
                        1. Authorization provider:
                        2. External JAAC provider
                        3. Don’t update the provider

IBM LDAP

Commands:
/opt/ibm/ldap/V6.3.1/sbin/ibmslapd -I ldap_name -k
/opt/ibm/ldap/V6.3.1/sbin/ibmslapd -I ldap_name
ps -ef|grep ibmslapd

STOP

[username@machine ~]$ sudo /opt/ibm/ldap/V6.3.1/sbin/ibmslapd -I ldap_name -k
GLPSRV176I Terminated directory server instance ‘ldap_name’ normally.

[username@machine ~]$ ps -ef|grep ibmslapd
username 21678 21578 0 04:16 pts/0 00:00:00 grep ibmslapd

[username@machine ~]$

START

[username@machine ~]$ sudo /opt/ibm/ldap/V6.3.1/sbin/ibmslapd -I ldap_name

GLPSRV041I Server starting.

GLPCTL113I Largest core file size creation limit for the process (in bytes): ‘0’(Soft limit) and ‘-1′(Hard limit).

GLPCTL119I Maximum Data Segment(Kbytes) soft ulimit for the process is -1 and the prescribed minimum is 262144.

GLPCTL119I Maximum File Size(512 bytes block) soft ulimit for the process is -1 and the prescribed minimum is 2097152.

GLPCTL122I Maximum Open Files soft ulimit for the process is 65536 and the prescribed minimum is 500.

GLPCTL122I Maximum Stack Size(Kbytes) soft ulimit for the process is 10240 and the prescribed minimum is 10240.

GLPCTL119I Maximum Virtual Memory(Kbytes) soft ulimit for the process is -1 and the prescribed minimum is 1048576.

GLPCOM024I The extended Operation plugin is successfully loaded from libevent.so.

GLPCOM024I The extended Operation plugin is successfully loaded from libtranext.so.

GLPCOM024I The extended Operation plugin is successfully loaded from libldaprepl.so.

GLPSRV155I The DIGEST-MD5 SASL Bind mechanism is enabled in the configuration file.

GLPCOM021I The preoperation plugin is successfully loaded from libDigest.so.

GLPCOM024I The extended Operation plugin is successfully loaded from libevent.so.

GLPCOM024I The extended Operation plugin is successfully loaded from libtranext.so.

GLPCOM023I The postoperation plugin is successfully loaded from libpsearch.so.

GLPCOM024I The extended Operation plugin is successfully loaded from libpsearch.so.

GLPCOM025I The audit plugin is successfully loaded from libldapaudit.so.

GLPCOM024I The extended Operation plugin is successfully loaded from libevent.so.

GLPCOM023I The postoperation plugin is successfully loaded from libpsearch.so.

GLPCOM024I The extended Operation plugin is successfully loaded from libpsearch.so.

GLPCOM022I The database plugin is successfully loaded from libback-config.so.

GLPCOM024I The extended Operation plugin is successfully loaded from libevent.so.

GLPCOM024I The extended Operation plugin is successfully loaded from libtranext.so.

GLPCOM023I The postoperation plugin is successfully loaded from libpsearch.so.

GLPCOM024I The extended Operation plugin is successfully loaded from libpsearch.so.

GLPCOM022I The database plugin is successfully loaded from libback-rdbm.so.

GLPCOM010I Replication plugin is successfully loaded from libldaprepl.so.

GLPSRV189I Virtual list view support is enabled.

GLPCOM021I The preoperation plugin is successfully loaded from libpta.so.

GLPSRV194I The Record Deleted Entries feature is disabled. Deleted entries are immediately removed from the database.

GLPSRV207I Group conflict resolution during replication is disabled.

GLPSRV221I Replication of security attributes feature is disabled.

GLPSRV200I Initializing primary database and its connections.

GLPCOM031I The attribute column name personIdentification is longer than 16 characters, so the first 16 characters of the specified column name personIdentifica will be used.

GLPRDB126I The directory server will not use DB2 selectivity.

GLPSRV046W No anonymous binds will be allowed.

GLPSRV017I Server configured for secure connections only.

GLPSRV015I Server configured to use 636 as the secure port.

GLPCOM024I The extended Operation plugin is successfully loaded from libloga.so.

GLPCOM024I The extended Operation plugin is successfully loaded from libidsfget.so.

GLPSRV232I Pass-through authentication is disabled.

GLPSRV234I Pass-through support for compare operations is disabled.

GLPSRV003I Server configuration file successfully read.

GLPCOM004I SSL port initialized to 636.

[username@machine ~]$ ps -ef|grep ibmslapd

ldap_name 10398 1 0 07:08 pts/2 00:00:00 /opt/ibm/ldap/V6.3.1/sbin/64/ibmslapd -I ldap_name

username 12676 5437 0 07:09 pts/2 00:00:00 grep ibmslapd

WebSphere MQ / IIB Broker

Commands:
mqsistop BROKER01
mqsilist 
endmqm QueueManager01
dspmq
strmqm
mqsistart BROKER01
mqsilist BROKER01
q -QueueManager_name -MQServer1 > nomeFila_data.out
q -QueueManager_name -MQServer1 -q   

Backup Queue
q -QueueManager_name -MQServer1 > nomeFila_data.out

Clear Queue
q -QueueManager_name -MQServer1 -q

STOP

ps -ef |grep bip
ps -ef |grep DataFlow
# Clean Shared Memory
ipcs -a |grep wbi
m 70254597 0xffffffff D-rw——- wbiadmin mqm wbiadmin mqm 1 393216000 13959340 14811306 12:09:50 18:19:12 12:09:50
m 8388616 0xffffffff D-rw——- wbiadmin mqm wbiadmin mqm 1 268435456 10551476 10551476 18:19:13 no-entry 18:19:13
ipcrm -s 70254597 8388616

[Username@machine ~]$ mqsistop BROKER01
BIP8071I: Successful command completion.

[Username@machine ~]$ mqsilist
BIP1285I: Broker ‘BROKER01’ on queue manager ‘QueueManager01’ is stopped.
BIP8071I: Successful command completion.

Sudo to user mqm ( sudo su – mqm )

Issue stop command on QM QueueManager01 and check if MQ stoped

[mqm@machine ~]$ endmqm QueueManager01
Quiesce request accepted. The queue manager will stop when all outstanding work is complete.

[mqm@machine ~]$ dspmq
QMNAME(QueueManager01) STATUS(Ended normally)

START

Issue start command on QM QueueManager01 and check if MQ started

[mqm@machine ~]$ strmqm QueueManager01
WebSphere MQ queue manager ‘QueueManager01’ starting.
The queue manager is associated with installation ‘Installation1’.

5 log records accessed on queue manager ‘QueueManager01’ during the log replay phase.
Log replay for queue manager ‘QueueManager01’ complete.
Transaction manager state recovered for queue manager ‘QueueManager01’.
WebSphere MQ queue manager ‘QueueManager01’ started using V7.5.0.5.

[mqm@machine ~]$ dspmq
QMNAME(QueueManager01) STATUS(Running)
Issue start command on broker BROKER01 and check if broker all EGs are running
Stop Command: mqsistart BROKER01
Check Command : mqsilist BROKER01

-bash-4.1$ mqsistart BROKER01
BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.

-bash-4.1$ mqsilist BROKER01
———————————–

BIP1286I: Execution group ‘default’ on broker ‘BROKER01’ is running.

———————————–

BIP1286I: Execution group ‘eg2’ on broker ‘BROKER01’ is running.
BIP8071I: Successful command completion.

-bash-4.1$

Start integration servers, applications, and message flows:

$ mqsistartmsgflow BROKER01 -e eg01

Start a named message flow that you have deployed to integration server on the broker BROKER01:

$ mqsistartmsgflow BROKER01 -e eg1 -m simpleflow

Ensure that all message flows are running on the local broker BROKER01:

$ mqsistartmsgflow BROKER01 -g -j

Start the message flow myFlow1 in the application myApplication in the default integration server:

$ mqsistartmsgflow BROKER01 -e default -k myApplication -m myFlow1

Start the message flow myFlow1 in the library myLibrary, which is referenced by the application myApplication, in the default integration server:

$ mqsistartmsgflow BROKER01 -e default -k myApplication -y myLibrary -m myFlow1

Start all message flows and start all applications in the default integration server:

$ mqsistartmsgflow BROKER01 -e default -z -j


TOOLS

IBM MQ

SL#

Tool Name

Description

Link

1

MA01: WebSphere MQ – Q program

This SupportPac contains a simple pipe line program (Q) which takes messages from one source and outputs to a target.

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24000647&loc=en_US&cs=utf-8&lang=en

2

MA0T: WebSphere MQ – Message Test Utility

MsgTest is a command line based program that provides the ability to execute scripts that simulate the flow of messages between applications that use IBM Websphere MQ (WMQ).

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24007048&loc=en_US&cs=utf-8&lang=en

3

MA6O WMQ UNIX Administration Tool

This freeware tool allows the use of extended regular expressions to match not only the name objects but also their attributes. It is very flexible with regard to error logging, is robust and provides a suitable return code at a user defined timeout – regardless of the state of the system resources. It supports remote administration (including z/OS) almost as if the remote queue managers were on the local system.

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24007030&loc=en_US&cs=utf-8&lang=en

4

MA7K – WMQ Trigger monitor service

This SupportPac provides a trigger monitor (TM) which runs as a Windows service and is linked with the WebSphere MQ client library. This program is designed to be run only by the Windows service control manager (SCM) and reports its status to the Windows event log.

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24000149&loc=en_US&cs=utf-8&lang=en

5

MO04 WMQ SSL Wizard

The WebSphere MQ SSL Wizard takes input in series of entry panels and then generates a set of instructions to enable the user to define and start a TLS/SSL channel. The instructions generated include both the platform specific commands for creating the certificates (e.g. using RACF or GSKit) and the MQSC commands used to define and start the WebSphere MQ channel.

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24010367&loc=en_US&cs=utf-8&lang=en

6

MH04-WMQ – Queue Statistics Tool

The tools provided in this SupportPac display several queue statistics as well as information about applications using that one or more queues. All the statistics and information can be displayed on a set interval and optionally recorded to a file.

http://www-01.ibm.com/support/docview.wss?rs=171&q1=Xa02&uid=swg24025857%20&loc=en_US&cs=utf-8&lang=en

7

MH05-WMQ – Events Display Tool

The tool provided in this SupportPac reads, interprets and displays WebSphere MQ events generated on the SYSTEM.ADMIN.*.EVENT event queues. The output can be optionally re-directed to a file and the tool may be triggered by WebSphere MQ if required. All event messages are supported.

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24029241&loc=en_US&cs=utf-8&lang=en

8

MO01 Event and Dead Letter Queue Monitor

This SupportPac contains three utilities; an event queue monitor, a dead letter queue monitor, and a program to remove expired messages.

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24000676&loc=en_US&cs=utf-8&lang=en

9

MO03 – WMQ Queue Load / Unload Utility

The WebSphere MQ Queue Load / Unload Utility allows the user to copy or move the contents of a queue, its messages, to a file. This file can be saved away as required and used at some later point to reload the messages back onto the queue. This file has a specific format understood by the utility, but is human-readable, so that it can be updated in an editor before being reloaded.

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24009368&loc=en_US&cs=utf-8&lang=en

10

MO73 WMQ Linear Log Clean Up Utility

WebSphere MQ Linear Log Clean up utility for Windows platform. This utility is developed in VB Script and hence does not call for any special software (such as Perl or Java).

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24012459&loc=en_US&cs=utf-8&lang=en

11

MO74 -WMQ – Windows Powershell Library

PowerShell is an extensible command line interface shell and scripting language product developed by Microsoft. This SupportPac contains a library which allows for command-line and script-basedadministration of WebSphere MQ queue managers from the PowerShell.

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24017698&loc=en_US&cs=utf-8&lang=en

12

MS0P -WMQ Explorer

This SupportPac provides a set of plug-ins for the WebSphere MQ Explorer, extending its capabilities for configuration of queue managers, and displaying additional information about those queue managers.

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24011617&loc=en_US&cs=utf-8&lang=en

13

MS6B – WMQ Connection Management Utility

This SupportPac provides a korn shell script to list and/or kill all connections to a queue manager by queue, channel, or IP address

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24017810&loc=en_US&cs=utf-8&lang=en

14

MS81-WMQ Internet Pass-Thru

WebSphere MQ Internet Pass-Thru (known as MQIPT) is a WebSphere MQ base product extension that can be used to implement messaging solutions between remote sites across the internet.

It makes the passage of WebSphere MQ channel protocols in to and out of a firewall simpler and more manageable, by tunnelling the protocols inside HTTP or by acting as a proxy.

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24006386&loc=en_US&cs=utf-8&lang=en
15 MQTools MQTools is a package of utilities designed to help WebSphere MQ Administrators carry out their jobs more easily and efficiently across UNIX platforms. The package has three goals: http://wmq.boulder.ibm.com/mqtools/about.html

IBM Integration Bus

SL#

Tool Name

Description

Link

1

IS03 – WMB Message Flow Statistics Visualiser

SupportPac IS03 provides a graphical means of viewing WebSphere Message Broker message flow statistics. The visualisation has the ‘look and feel’ of the WebSphere Message Broker Toolkit and allows the user to rapidly view the all available statistics in an intuitive manner. Both SnapShot and Archive statistics can be viewed using IS03 and it is highly configurable to enable the graphing of exactly the statistics which the user is interested in seeing.

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24030716&loc=en_US&cs=utf-8&lang=en

2

IS02- WMB Explorer Plug-in

This SupportPac plug-in enhances the WebSphere MQ Explorer with the ability to administer a WebSphere Message Broker network.

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24012457&loc=en_US&cs=utf-8&lang=en

3

IE02- IBM Integration Bus – ODBC Database Extender

This SupportPac increases the range of databases supported by IBM Integration Bus and WebSphere Message Broker.

The SupportPac provides binaries for use with WebSphere Message Broker v7.0.0.2, WebSphere Message Broker v8.0 and IBM Integration Bus v9.0.

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24026935&loc=en_US&cs=utf-8&lang=en

4

IH03 – WMB Message display, test & performance utilities

This SupportPac contains a utility that is useful for the development and testing of WebSphere MQ and IBM Integration Bus or WebSphere Message Broker applications. Test messages are stored as files, which are then read by the application and written to a WebSphere MQ queue. The program is GUI based.

http://www-01.ibm.com/support/docview.wss?uid=swg24000637