Technical support knowledge for Application Integration Middleware including WebSphere, CICS, BPM, MQ, Broker, IIB, ODM, DataPower, Mobile, Appliances, and more! Following the IBM Social Computing Guidelines - Steve Webb, Joseph Lam
Many of us are familiar with the traditional IBM Installation Manager (IIM) Eclipse-based rich client, IBMIM , that allows one to drive IIM in an environment where a GUI is available.
However, this approach is not always feasible, especially in an environment where one needs to access IIM on a remote server, perhaps one without a GUI console i.e. operating in so-called "headless" mode.
This is often the case with remote UNIX® servers ( AIX, Linux, Solaris etc. ) where one's only point of access is via... [More]
The Java™ JRE will throw an OOM error for more than just a Java heap with no free space. So the single heapdump you have from an outage might not be useful at all and could lead you down the wrong debugging path. It is very important to get a complete set of documentation from an OutOfMemory (OOM) error. A single heapdump is never enough to figure out the general type of OOM you’re dealing with.
(Note that this information is correct for a WebSphere Java process running with an IBM Java JRE, and... [More]
In late 2014, we published Security Bulletin: Vulnerability in SSLv3 affects IBM WebSphere Application Server (CVE-2014-3566) . As detailed in the bulletin, the IBM WebSphere Application Server could allow a remote attacker to obtain sensitive information, caused by a design error when using the SSLv3 protocol. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) attack to... [More]
The HAManager/HAM (High Availability Manager) Framework is an integral WebSphere Application Server (WAS) part designed to provide an infrastructure for making selected WAS services highly available. It is present in all JVMs including Deployment Manager and Node Agents. HAM can be used by other internal WebSphere components to provide automatic failover support.
Four basic HAManager services:
Bulletin Board - Used by WLM and ODC
HA Groups ... [More]
The two tables below provide the most commonly used Webcontainer attributes and custom properties for WebSphere Application Server. The Webcontainer attributes are configured at the application level in the ibm-web-ext.xmi or ibm-web-ext.xml file. They are only used by specific application.
Allow web applications to serve static file types, such as HTML. If it is set to... [More]
During installing Products and Fixes with IBM Installation Manager, Installation Manager searches open repositories where Packages and Fixes exist. But how can you verify the applicable packages, updates, and features are in a target repository from the command line?
Installation Manager provides the command line tool, imcl, to manage installation. The imcl command can be found in <IM_ROOT>/eclipse/tools subdirectory.
Where <IM_ROOT> is root directory where IM is installed.
We will introduce how to... [More]
If you need to verify the product information of Liberty Profile, you can use the productInfo command to display the current product version, edition, and other details about the product.
Command: "productInfo version" shows the product name, version, and edition. It can be entered from the install root bin directory, for example, "wlp\bin\productInfo version".
This command can be used to validate if Liberty is successfully installed.
* Note: The product edition is displayed... [More]
Java heap is the area of memory that is used by the Java virtual machine (JVM) for storing Java objects. Optimal Java heap size is application and use dependent. Setting the JVM heap size is directly related to the number of server instances that needs to be started on a specific node and the total RAM available on the machine. The maximum heap should be incremented not to exceed 50% of overall physical memory. The Java heap memory is used by the applications that are deployed and the component running in... [More]
During the course of WebSphere Application Server operation, a JVM may produce important diagnostic information in a variety of files and formats. In this blog entry, we will briefly examine each of these files and their purpose.
A wealth of valuable Java™ virtual machine diagnostic data can be gathered by doing the following tasks:
1) JVM process standard error stream
In WebSphere, JVM writes some errors messages on the standard error... [More]
The WebSphere Application Server does not contain code that provides for a secure database connection method other than basic userid/password authentication, which is implemented through an authentication alias. However, this does not mean you cannot configure another authentication method. Most of the WebSphere Application Server datasource configuration, with the exception of pool configuration parameters, are properties that are simply passed to a JDBC driver package.
For example, if I create a new datasource... [More]
Co-authored by: Shawfu Chen and Steve Dittmar
As of IBM WebSphere Application Server V8.5, users on most platforms can choose to run on Java SDK 6.1 or 7.0, with support for 7.1 having been added more recently. Java SDK 6.1 continues to be shipped with, and updated automatically by, the WebSphere Application Server fix packs. However, some users do not realize that Java SDK 7.x fix packs are not included in the WebSphere Application Server fix packs and thus is not automatically installed or kept up-to-date by the... [More]
Sometimes servers do not start. Maybe it is due to a bad build, the configuration has gotten corrupted, or it just stopped working. This blog helps you understand the anatomy of the Application Server start up process. It provides you with troubleshooting and debugging techniques to determine why the server is not starting or why the server is not stopping.
Starting the server
Let's see what happens when a server is started using the startServer.sh /bat server1 command.
Two Java virtual machines... [More]
This 2-part blog is focused on some commonly occurring exceptions for the status cache problem. With this problem, the status display of an application server, node agent, or an application is shown as 'red' or 'unknown' on the WebSphere Administrative Console. However, the actual process is up running.
In part 1, we will look at when this type of issue can occur due to one of the following areas:
Discovery ports with firewall
Operating system level
This blog is part 2 of a 2-part blog that is focused on some commonly occurring exceptions for the status cache problem. To read part 1 first, see Common status cache problems in the WebSphere Administrative Console - Part 1 .
With this problem, the status display of an application server, node agent, or an application is shown as 'red' or 'unknown' on the WebSphere Administrative Console. However, the actual process is up running.
In part 2, we will look at when this type of issue can occur due... [More]
Windows Authentication is not a WebSphere Application Server feature . Instead it is a capability provided by the Windows operating system and the MS JDBC Driver should be supporting it. All that needs to be done in WebSphere Application Server (WAS) is to not define a J2C Authentication alias and configure the data source custom property integratedSecurity=true .
Add the .dll files for the driver to the WebSphere Application Server Installation. The .dll files can be obtained with a SQL Server driver from Microsoft. The... [More]