IBM Support

Integrated Web Application Server for IBM i - Frequently asked questions

General Page


This page answers frequently asked questions (FAQs) about the Integrated Web Application Server for i. The FAQ will answer questions regarding the features of the product as well as comparisons to WebSphere Application Server, WebSphere Application Server Network Deployment (ND), and Apache Software Foundation (ASF) Jakarta Tomcat servlet engine (hereafter referred to as ASF Tomcat).


What is Integrated Web Application Server for i?

The integrated Web application server for i is a lightweight Java application server integrated into the operating system. The integrated Web application server contains an Open Services Gateway initiative (OSGi)-based Web servlet container that is readily accessible and provides a flexible foundation for developing jsp and servlet-based Java applications. The integrated Web application server delivers a clear path to the advanced capabilities of the WebSphere middleware portfolio.


Why would I want to use integrated Web application server?

Here are some of the reasons you may want to use integrated Web application server for i:


How can I obtain integrated Web application server?

The following prerequisites are required to be installed on the system in order to use the integrated Web application server for IBM i support:

After loading the products, ensure you load the latest HTTP group PTF.


What products use the integrated Web application server?

The list below is a partial list of products that use the integrated Web application server:


Why use the integrated Web application server vs. ASF Tomcat?

The latest version of the integrated web application server is based on the Liberty profile, a recently-developed dynamic profile for WebSphere Application Server. The profile enables rapid development and deployment of web applications in a simpler and lightweight manner.

Liberty and Tomcat provide a basic servlet engine, but can also be grown to provide additional Java enterprise services and related services. With Liberty, those services have already been integrated with the Liberty kernel, so the services have a common configuration file, log outputs, and more. With Tomcat, the user performs the integration of third-party libraries.

The Liberty profile default configuration is very small and is simpler—unlike Tomcat, which has most of its functionality enabled by default. Liberty features are enabled by the deployed applications as needed and when needed, keeping the server footprint as small as possible.

Tomcat has a slightly faster restart, although both servers start in less than three seconds. Liberty requires fewer restarts due to its dynamic configuration updates. Memory footprints are comparable and will vary in both cases, depending upon the features that are configured (Liberty) or libraries added (Tomcat). The Liberty shared library support has the potential to make significant footprint reductions when applications need different versions of the same library.

Production throughput for the JSP/JDBC workload is about 30 percent higher for Liberty, which could make Liberty a better choice where high-volume performance is important.


Why use WebSphere Application Server vs. the integrated Web application server?

Use WebSphere Application server if you want the following:


What are the differences between how database access is supported by the integrated Web application server vs. ASF Tomcat & WebSphere Application Server?

The integrated Web application server documentation uses the terminology database connections. WebSphere Application server documentation uses the terminology data sources. Both refer to the same thing.

A data source represents a specific database that is used by one or more applications installed in your application server. Data sources provide connection pooling and a JNDI name which can be used by applications to access the data source.

The integrated Web application server supports a single JNDI name source. WebSphere Application Server supports multiple JNDI name sources. You are only allowed one JNDI data base connection with the integrated Web application server. Applications with multiple JNDI names and connections will not be supported on the integrated Web application server.

The integrated Web application server connection pooling support is done by Apache commons database connection pooling. WebSphere Application Server connection pooling is done by WebSphere connection pooling.


What types of Web applications will be supported by the integrated Web application server?

The integrated Web application server supports Web archive (WAR) files.


Is there an option to modify class paths for applications when deploying to the integrated Web application server?

Yes.


Will a servlet that is created run on the integrated Web application server and WebSphere Application Server without modification?

In general, yes, most servlets should run on either application server. However, the integrated Web application server supports only one JNDI connection. Applications with multiple JNDI names and connections will not be supported on the integrated Web application server.


Can IBM WebSphere Portal be run on the integrated Web application server?

No.


Can applications created with IBM WebFacing Tool be run on the integrated Web application server?

Yes. However, applications created with IBM WebFacing Tool have support for high availability and hot failover through the use of WebSphere Application Server Network Deployment (ND). Use WebSphere Application Server ND if high availability and failover is required. In addition, use WebSphere Application Server or WebSphere Application Server ND if J2EE security is required.


Can applications created using WebSphere® Host Access Transformation Services (HATS) Toolkit run in the integrated Web application server?

No.


Can you deploy and run an application created with Rational Business Developer Extension (RBDe) Enterprise Generation Language (EGL) on the integrated Web application server?

No.


Can you target integrated Web application server when creating dynamic web projects when using WebSphere Development Studio Client for System i or Rational Application Developer?

No.


What performance tools can be used to optimize applications running on the integrated Web application server?

You can use Collection Services for heap and garbage collection. You can use tools to analyze applications such as Job Watcher and Performance Explorer (PEX) Analyzer for collecting and Performance Trace Data Visualizer (PTDV) for analyzing performance data.

In V6R1, you will also be able to use Web Performance Advisor, a part of IBM HTTP Server for i, to help tune your application.


What are the options to administer the integrated Web application server?

The preferred way to administer the integrated Web application server is by using the Web Administration for i GUI. The Web Administration for i uses the default Web administration port of 2001.


Can an API be used to create an instance of the integrated Web application server and install applications?

Yes, there are scripts that callable from Qshell found in directory /QIBM/ProdData/OS/ApplicationServer/bin.


What are the general differences between integrated Web application server and WebSphere Application Server?

 
One page summary Integrated Web Application Server WebSphere Application Server Express WebSphere Application Server Network Deployment
Cost Integrated Entitled Fee
Packaging Integrated with IBM i Ships with Web Enablement for IBM i Separate product
Fixes IBM i PTFs WebSphere iFix WebSphere iFix
Access to DB2 for i Yes Yes Yes
Supports JSP and servlets Yes Yes Yes
Multiple instances Yes Yes Yes
JNDI name space connection One Multiple Multiple
Full J2EE support No Yes Yes
Java Based Messaging Engine No Yes Yes
Cross platform No Yes Yes
Advanced workload management, high availability, scalability No No Fully Supported
Memory requirements Focused feature/function ~40% less then WebSphere Application Server - -
J2EE application packaging partial (WAR) full (WAR and EAR files) full (WAR and EAR files)
Web services Yes Yes Yes
Administration & configuration Web IBM Web Administration for IBM i, Qshell Web Administration for IBM i, Qshell, WebSphere Administration console Web Administration for IBM i, Qshell, WebSphere Administration console
Horizontal growth & automatic failover for high availability No No Yes

What are the differences in database features of the integrated Web application server and WebSphere Application Server?

 
DB Integrated Web Application Server WebSphere Application Server Express WebSphere Application Server Network Deployment
Supports access to DB2 for i Yes – (currently slower then WebSphere Application Server) Native JDBC driver, IBM Toolbox for Java and JTOpen data access classes supported Yes, (performance better) ( Native JDBC driver, IBM Toolbox for Java and JTOpen data access classes supported ) Yes, Native JDBC driver, IBM Toolbox for Java and JTOpen data access classes supported
JNDI (Java Naming and Directory Interface) name space connection Only one JNDI name space connection, Multiple JNDI name space connection Multiple JNDI name space connection
Different DBs supported Only DB2 for i Multiple databases including DB2 for i Multiple databases including DB2 for i
 

What are the differences in APIs that are supported by the integrated Web application server and WebSphere Application Server?

 
API support   Integrated Web Application Server WebSphere Application Server Express WebSphere Application Server Network Deployment
Full J2EE support No Yes Yes
Java based messaging engine No Yes Yes
EJB container No Yes Yes
Portlet container No Yes Yes
Session Initiation Protocol (Chat, VoIP Solutions) SIP support No Yes Yes
Supports JSP and servlets Yes Yes Yes
Web Services engine Yes Yes Yes
 

What are the differences in administrative features that are supported by the integrated Web application server and WebSphere Application Server?

 
Administration Integrated Web Application Server WebSphere Application Server Express WebSphere Application Server Network Deployment
Packaging Integrated with IBM i Ships with Web Enablement for IBM i Separate product
Fixes IBM i PTFs WebSphere iFix WebSphere iFix
Administration console IBM Web Administration for IBM i IBM Web Administration for IBM i. Also, WebSphere Administration Console built on Integrated Solution Console which provides consistent user interface across IBM products IBM Web Administration for IBM i. Also, WebSphere Administration Console built on Integrated Solution Console which provides consistent user interface across IBM products
Multiple instances Yes Yes Yes
High availability, clustering and workload management No Yes -
Horizontal growth & automatic failover for high availability No No Yes
 

What products are supported on integrated Web application server Vs. WebSphere Application Server?

 
Product support Integrated Web Application Server WebSphere Application Server Express WebSphere Application Server Network Deployment
IBM Webfacing Tool Yes Yes Yes
HATS No Yes Yes
WDHT Yes for IBM Webfacing Tool but not for HATs Yes Yes
RBDe (EGL) No Yes Yes
WDSC / RAD deploy support No Yes Yes

[{"Product":{"code":"HW1A1","label":"IBM Power Systems"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"--","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]

Document Information

Modified date:
03 May 2021

UID

isg3T1026864