1. IBM WebSphere Application Server
Gerald Fulleylove – IBM WebSphere Application Server Support Specialist.
UK User Group – May 2017
IBM WebSphere Application Server

2. IBM Software Support Explain call flow.
World Wide
Service Request
Call Agents
Entitlement checks
Routing
Technical Support
Level 1
Technical Specialists
Level 2
Product / Solution
specific in-depth skills
Change Team / Developers
Level 3
Code programming specialists.
Code Owners
Explain call flow.
Emphasise importance of Full & Complete information from outset…benefit to ultimate resolution.
Don’t forget…
Non technical call agents and entitlement verification.
Electronic call logging bypasses the Service Centre
Transfer to other teams, not just up/down…also parallel.
Requests for further information from customer/things to try.
Live Chat
IBM Knowledge Center 2 2 2

3. Request received:
“ Performance and tuning, load balancing and all the other clever tasks that WebSphere can manage “
Q&A 3 3

4. Maximo Best Practices for System Performanc​e 7.6.x.pdf
URL:

5. Maximo Best Practices for System Performanc​e 7.6.x.pdf
Sizing the Java Heap
Tuning the Webcontainer Thread Pool
Tuning the HTTP Server
Choosing the right Load Balancer type

6. Maximo and SCCD Advanced System Configuration|

7. WebSphere Runtime Architecture.|

8. Maximo Best Practices for System Performanc​e 7.6.x.pdf
You can use the following heap size values to start tuning:
Initial: 6144m / Maximum: 6144m (Recommended)
Initial: 4096m / Maximum: 4096m (Minimum)
** Set the initial and maximum heap sizes to the same values for maximum performance.

9. Storage and Allocation – Java Garbage Collection.
The Storage component of the JVM facilitates the creation, management and collection of objects on the java heap.
The JVM maintains two separate memory areas:
native heap and the java heap.
The class data and instance data for Java objects are placed in the Java Heap.
The JVM allocates memory for its underlying objects in the native heap using malloc(). These may include thread stacks, motif objects required by AWT and Swing, buffers for inflaters and deflaters, anything malloc()ed by application JNI code, native data blocks for I/O and Zip operations and JIT compiled code.
With 64bit JVMs , 4Meg Process Address Space Memory limit that applies to 32bit JVM is removed.
For optimum performance set min and maxheap to same value. (with 32bit IBM JVMs min heap should be no more than 25% of maxheap and maxheap no more than 1536 )

10. Quick and Easy way: Using the WebSphere Admin Console to check Java memory usage.
> Monitoring and Tuning
> Performance Viewer
> Current Activity
> Server1. (Default name)
Then select
> Performance Modules,
> tick JVM runtime,
> View Module.
You can see how much memory the JVM is using.

11. Using verbosgc and Heap Dump to check Java memory usage.
- Enabling verbosgc
Manually Generating Java Heap Dump ( xxxx.phd )
Downloading and Installing IBM Support Assistant Workbench ( ISA/Tool )

12. IBM Support Assistant Workbench

13. IBM Support Assistant Workbench

14. IBM Support Assistant Workbench

15. IBM Support Assistant Workbench

16. Maximo Best Practices for System Performanc​e 7.6.x.pdf
Webcontainer thread pool:
 Minimum: 120
 Maximum: 150
To view this administrative console page, click Servers > Server Types > WebSphere application servers > server_name > Thread pools, and select the thread pool that you need to configure.
- Using TPV

17. Deciding where and what to monitor|

18. Maximo Best Practices for System Performanc​e 7.6.x.pdf
IBM HTTP Server and Plugin tuning
TimeOut
Value: 900
The TimeOut directive sets the amount of time the server waits for certain events before failing a request.
KeepAliveTimeOut
High Network Bandwidth: 10
Low Network Bandwidth: 60
The KeepAliveTimeout directive sets the amount of time the server waits for subsequent requests on a persistent connection. Set this value to 60 for those environments that may have high network latency, such as when users are located in areas that are geographically different from the location of the servers.
MaxKeepAliveRequests
Value: 0
The MaxKeepAliveRequests directive sets the number of requests allowed on a persistent connection. Setting this value to zero allows unlimited requests.
MaxRequestsPerChild
The MaxRequestsPerChild directive sets the limit on the number of requests that an individual child server handles during its life. Once this limit is reached, the child process dies. Setting this value to zero ensures that the process never expires.

19. HTTP Session flow.
1. A Web client requests a URL in the browser (input page).
2. The request is routed to the Web server over the Internet.
3. The Web server immediately passes the request to the WebSphere plug-in. All requests go to the WebSphere plug-in first.
4. WebSphere plug-in examines the URL, verifies the list of hostname aliases from which it will accept traffic based on the
virtual host information, and chooses a server to handle the request.
5. A stream is created. A stream is a connection to the Web container. It is possible to maintain a connection (stream) over a
number of requests. The Web container receives the request and based on the URL, dispatches it to the proper servlet.
6. If the servlet class is not loaded, the dynamic class loader loads the servlet. Servlet init(), then doGet() or doPost().
7. JNDI is now used for lookup of either datasources or EJBs required by the servlet.
8. Depending upon whether a datasource is specified or an EJB is requested,the JNDI will direct the servlet:
a) To the corresponding database, and get a connection from its connection pool in the case of a datasource
b) To the corresponding EJB container, which then instantiates the EJB, when an EJB is requested
9. If the EJB requested involves an SQL transaction, it will go back to the JNDI to lookup the datasource.
10. The SQL statement will be executed and the data retrieved will be sent back:
a) To the servlet
b) To the EJB
11. Data beans are created and handed off to JSPs in the case of EJBs.
12. Servlet sends data to JSPs.
13. The JSP generates the HTML that is sent back through the WebSphere plug-in to the Web server.
14. The Web server sends the output page (output html) to the browser. |

20. Understanding the HTTP Plug-in operation

21. Maximo Best Practices for System Performanc​e 7.6.x.pdf
HTTP Server 
- Recommended values for web server plug-in config
- Understanding IBM HTTP Server plug-in Load Balancing in a clustered environment
HTTP plugin :
- MaxConnections
- ServerIOTimeout
- ConnectTimeout
- LoadBalanceWeight

22. Security
JVM Security – controls Java status and permission to run in JVM
Java2 Security * - controls authorisations at the object level
CORBA security – controls access to the ORB
J2EE Security API * - controls access at the EJB and JSP levels
WebSphere Admin Console * - controls access to Admin console and CLI
* Enabled automatically if WebSphere Global Security is enabled.
MS .NET Class Library now or later. |

23. Security OS Cell Admin Console Deployment Manager
-security service (5)
Node Agent
-security service
Application server
-security service (1,2,3,4)
Registry
1.Local OS
2.LDAP
3.Custom |

24.
The SSL Protocol
The previous section provides a high-level description of the SSL handshake, which is the exchange of information between the client and the server prior to sending the encrypted message. This section provides more detail.
The "SSL Messages" figure below shows the sequence of messages that are exchanged in the SSL handshake. Messages that are only sent in certain situations are noted as optional. Each of the SSL messages is described in the following figure:
Within a WebSphere Security trace each of these entries has *** header.
*=info : SSL=all

25. WebSphere MustGather

26. Application Server tracing
WebSphere Community - a free low level implementation, perhaps useful for proof of concepts.
WebSphere Express - 2 CPU license offering
WebSphere Base - the standalone single server offering
WebSphere Application Server Network Deployment - The “standard” business offering - multi server support.
WebSphere Application Server Extended Deployment - WAS ND code plus Workload monitoring and load balancing cells. |

27. Q&A