Frequently Asked Questions (FAQ)
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:
- You imbed ASF Tomcat in your application today. With the integrated Web application server you would not have to imbed ASF Tomcat with your application.
- You have limited system resources which prevent you from optimally running WebSphere Application Server.
-
- The integrated Web application server focused features and functions typically take 40% less memory then WebSphere Application Server. The default for the WebSphere Application Server running on IBM System i 515 Express is 1 gig of memory.
- There is no additional memory needed for startup for the integrated Web application server. It is recommended to have 2 gig of memory to for startup for WebSphere Application Server.
- You want to deploy simple Web applications on your server and do not need the cross platform capabilities, additional security, n-tier deployment environment, JMS & EJB programming model support, SOA features in WebSphere Application Server, WAS ND clustering, or multiple JNDI connections.
- You want to deploy simplified database applications with one data base connection.
- You want to deploy traditional servlet and JSP applications.
How can I obtain integrated Web application server?
The integrated Web application server was announced October 9, 2007 in
IBM United States Announcement, 207-242 and GA was December 21, 2007 for V5R4.
To obtain the integrated Web application server, load the prerequisites and PTFs listed on the
Support page.
What products use the integrated Web application server?
In V6R1, any products that were using ASF Tomcat in prior releases will use the integrated Web application server. The list below is a partial list of products that use the integrated Web services server:
- The i5/OS Web administrative interfaces
- The integrated Web services server
- DB2 Web Query for i
Why use the integrated Web application server vs. ASF Tomcat?
In V6R1, i5/OS will not ship with a version of ASF Tomcat. If you have been using ASF Tomcat, you will need to switch to the Open source Apache Tomcat server, the new integrated Web application server, or WebSphere Application Server. You may download the open-source Apache Tomcat from the following website:
http://tomcat.apache.org/index.html
Why use WebSphere Application Server vs. the integrated Web application server?
Use WebSphere Application server if you want the following:
- You need higher availability or more scalability
- You are supporting cross platform deployment and only want to test with one application server
- You use more then one JNDI (Java Naming and Directory Interface) connection
- You want to use the built-in messaging engine based on WebSphere MQ, or the Java Based Messaging Engine
- You need more of the robust features in WebSphere Application Server such as
-
- Support for full J2EE programming model
-
- servlets, JSP's, JSF's
- EJB's, JMS
- JDBC (integrated app server has limited namespace, only allows one JNDI connection)
- Support for full & extended J2EE packaging model
-
- WAR, EAR, RAR files
- IBM extensions (extended deployment descriptor, annotations, etc.)
- Support for n-tier deployment model
-
- HTTP server, application server, DB on same or different machines
- cross platform, heterogeneous capabilities
-
- Run tiers on different servers, operating systems, etc.
- Support for DB2, Oracle, MySQL, etc. database access
- Support for full range of security options (HTTP server, Web application, Java)
- Support for full range of Web service client and server capabilities
- Support for an integrated test server environment for iterative development
Will WebSphere Application Server Express still be shipped with the i5/OS with V6R1?
WebSphere Application Server Express will continue to be part of Web Enablement for i5/OS, 5722-WE2.
What Java Virtual Machine (JVM) is supported by the integrated Web application server?
The primary JVM is the IBM Technology for Java Virtual Machine. Note: You may have seen IBM Technology for Java Virtual Machine referred to as J2SE 5.0 32-bit JVM in other publications. The IBM Technology for Java Virtual machine is included in licensed program 5722-JV1. Licensed program 5722-JV1 is shipped with the system CDs.
- If using the Web Administration for i5/OS GUI, it will use the 32 bit JVM running under the PASE environment.
- The IBM 64 bit JVM will be supported in V6R1.
- The integrated Web application server can also be configured to run on the i5/OS 64bit classic JVM.
Which application server should be used if porting applications to i5/OS that are now deployed to WebSphere Community Edition (CE)?
WebSphere CE is not supported on i5/OS. Review feature and function comparisons in this FAQ to determine which application server best meet your application requirements.
What are the performance characteristics of the integrated Web application server?
Initial tests have shown that the focused features and functions of the integrated Web application server use ~40% less memory usage then WebSphere Application server and no extra memory is needed for startup. JDBC database intensive applications may not perform as well with integrated Web application server. IBM recommends doing performance proof points with your own application to determine the performance characteristics of it running with each application server. Here are the results of some performance tests:
- Trade 6 (a non EJB application)
Trade6 is a heavy JDBC database application. WebSphere Application Server 6.1 performance was better then integrated Web application server in this situation.
- IBM Web Facing tool application
The integrated Web application server and WebSphere Application Server 6.1 had performance equal (within a percent).
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) and Web application bundle (WAB) 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 i5/OS GUI. The Web Administration for i5/OS uses the default Web administration port of 2001. There are API and command line options available. These will be further described later in 2Q/2008.
Can an API be used to create an instance of the integrated Web application server?
Yes, there are scripts that callable from Qshell. More information regarding using scripts will be made available later in 2Q2008.
Can an API be used to install applications to the integrated Web application server?
Yes, there are scripts callable from Qshell. More information on the scripts will be made available later in 2Q2008.
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 i5/OS V5R4 |
Ships with Web Enablement for i5/OS |
Separate product |
| Fixes |
i5/OS 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 or WAB files) |
full (WAR and EAR files) |
full (WAR and EAR files) |
| Web services |
Yes |
Yes |
Yes |
| Administration & configuration |
Web IBM Web Administration for i5/OS, Qshell |
Web Administration for i5/OS, Qshell, WebSphere Administration console |
Web Administration for i5/OS, 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 |
| Connection pooling - datasources |
Apache commons database connection pooling |
WebSphere connection pooling. |
WebSphere connection pooling. |
| 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 - 1.2,1.3,1.4 |
No |
Yes |
Yes |
| Web Services Framework - UDDI V3 support etc. |
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 Axis2 V1.3 |
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 i5/OS V5R4 |
Ships with Web Enablement for i5/OS |
Separate product |
| Fixes |
i5/OS PTFs |
WebSphere iFix |
WebSphere iFix |
| Administration console |
IBM Web Administration for i5/OS |
IBM Web Administration for i5/OS. Also, WebSphere Administration Console built on Integrated Solution Console which provides consistent user interface across IBM products |
IBM Web Administration for i5/OS. 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 |
| Application assembly |
WAR files are supported, but need Web Administration for i5/OS to create WAB file for deployment - Use other tools like AST or WDSC to assemble applications |
Application Server Toolkit (AST), WDSC |
Application Server Toolkit (AST), WDSC |
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 |
| 
