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
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]
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]
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]
WebSphere Application Server uses multiple temporary locations for many reasons. This blog explains the most commonly used temporary files, why they are used and when they can be removed. This blog will also explain the files and directories that can be removed under the profile direction with caution.
Be careful in deleting any temporary, cache and log files in WebSphere Application Server!
Before making any changes to the environment , take a backup of the... [More]
A wealth of valuable JVM diagnostic data can be gathered by doing the following tasks:
Generate a Java™ thread dump.
Enable logging of verbose garbage collection data for Server.
Generate a Java heap dump.
Generate a system core dump & snap trc file.
In the overall process of problem determination, diagnostic data must be collected or generated, and the data must be analyzed. Various tools are available to help you analyze diagnostic data for solving problems. Below... [More]
Here are the most commonly asked questions about running IBM WebSphere Application Server as a non-root user. Its applicable for a WebSphere Application Server V6.0 profile and later.
It is a common practice to run the application server as a non-root user. Most of the WebSphere Application Server users install and run the application server as a non-root user only. There are no restrictions on how you protect your resource. You can set the permission of the file as you like, but there are some key and... [More]
This blog contains some common questions and answers that are related to the use of JMS connection pools and session pools. Hopefully this information will help you in your environment tuning efforts.
Q: WebSphere MQ Queue Connection Factories in WebSphere Application Server releases contain both a connection pool and a session pool for configuration. When configuring the session pool, is this configuration for each connection? For example, if my connection pool has a maximum size of 10, and my session pool also has a... [More]
Configuration migration is the process of upgrading a WebSphere Application Server installation to a newer major release. Migration leverages the existing configuration and applications and migrates them to the newest version environment. This blog provides important tips when you are running Migration Utilities ( Configuration Migration Tool (CMT) or command line (WASPreupgrade/WASPostupgrade)) to migrate WebSphere Application Server from one version to another.
Make sure that the ulimit for open files is not set to the... [More]
With an increasing amount of stack products being available and used with WebSphere Application Server on z/OS, we're starting to see EC3 timeouts of different varieties that are caused by Mbean long waits or deadlocks. An initial review of the dump and reason code may produce what looks like a common timeout, like HTTP or EJB. But closer inspection of an SVC dump or javacore could reveal that the thread that took the timeout was actually waiting on an internal Mbean request.
In general, Mbean requests flow... [More]
The WebSphere L2 Support team handles its fair share of WebSphere Application Server performance analysis. Often it appears as though the Monitoring Agent (that thing that reports whether the system is behaving - or not) is the problem itself. The truth is, the more problems that the agent has to report, the more noise the agent is going to interject into the diagnostic data. It's a vicious cycle.
One of the common agents that are encountered is Wily. Like any performance monitoring tool, Wily can introduce a... [More]
Are you planning to upgrade your level of z/OS or WebSphere Application Server, or maybe even both, and are wondering how one might affect the other?
The Software Product Compatibility Report will help you figure this out:
The first page you will see is this:
You can select 'High-level' or 'In-depth' reports. The High-level report is sufficient if all you want to see is what... [More]
Sometimes, during the course of testing or troubleshooting, we need to really understand what is going on in the depths of the WebSphere code when our enterprise application executes it's logic. When the basic log output from the server does not provide enough data to surmise what the root cause of the problem is we must then collect verbose tracing data from the server in hopes to capture the sequence of events that are occurring (or not occurring) while the application is running. This is where reference traces can become... [More]