WebSphere Application Server drives business agility by providing
developers and IT Architects with an innovative, performance-based foundation to build, reuse, run, integrate and manage Service-Oriented Architecture (SOA) applications and services.
Run applications and services in a reliable, highly available, secure
and scalable environment to ensure business opportunities are not lost
due to application downtime.
Deliver optimized runtime
performance
through provisioning, Web services, and Enterprise JavaBeans™ (EJB)
3.0 enhancements, which can result in fewer energy consuming
processors performing the same workloads of previous versions.
New security capabilities add deeper levels of management, user
governance, and auditing to decrease system vulnerabilities, while
maximizing developer productivity.
From service-enabling legacy assets to inventing new ones, WebSphere
technology makes your business accessible to new users in innovative
ways, giving you immediate insight and interaction with partners,
suppliers, and customers. Subsequently, you increase your return on
investment.
WebSphere Application Server V7 supports the broadest range of
platforms in the industry, helping to provide assurance that your
applications can be built to run on the platform that makes the most
sense for your business.
Increase
developer productivity
using enhanced support for standards, emerging technology and a choice
of development frameworks that simplify programming models.
What is included in the AMI for WebSphere Application Server V7.0?
The operating system of the AMI is SuSE Linux® Enterprise
Server 10. Within this AMI is a secured WebSphere
Application Server
that is registered to a WebSphere Application Server
administrative agent.
To determine the IBM WebSphere Application Server V7.0 level, run
the following command:
/opt/IBM/WebSphere/AppServer/bin/versionInfo.sh.
To determine the SuSE Linux Enterprise Server 10 level, run the
following command: cat
/etc/SuSE-release.
To determine the Linux kernel level, run the following command:
uname -a.
To determine the IBM Update Installer for WebSphere Software
level, run the following command:
/opt/IBM/WebSphere/AppServer/UpdateInstaller/bin/versionInfo.sh.
I noticed that other items are mentioned in the license information,
like IBM Tivoli® Directory Server. However, this offering is not on
the AMI. Am I entitled to use this offering?
The AMI was tailored for usage on AWS. Therefore, a number of items are not
included on the AMI. You are only entitled to use what is provided in the
AMI.
What are typical types of IBM WebSphere Application Server V7.0
solutions that work well on AWS, and what solutions do not?
For optimal results, develop and test applications that are
deployed on a single implementation of WebSphere Application
Server and require minimal interaction outside the AWS environment
for development and testing.
Some systems are less-suited to an Amazon Elastic Compute Cloud
(EC2) based WebSphere Application Server solution. Careful
consideration and testing are required if you want to use Amazon
EC2 to deploy such a solution. Some examples include:
Aggregating applications outside of Amazon
EC2: If your WebSphere Application Server
solution requires a highly available, high-performance
connectivity to backend services located outside the AWS
environment (local services, for example) then the overall
performance and availability might be at risk. In this
situation, consider other solutions where you have more
control over bandwidth, performance and availability.
Integration with external corporate user directories
such as LDAP: This is similar to the need
to aggregate external applications, but user directory
access is a global requirement, raising the importance of
a reliable, secure and fast connection between Amazon EC2
and the external registry. This capability is not provided
by default in the AMI; however, several VPN-based
solutions are documented in the AWS forums.
How does the AMI for IBM WebSphere Application Server V7.0 differ
from the way IBM traditionally sells these offerings?
The offering on AWS differs from the IBM traditional purchasing model in a number of ways:
Pricing. IBM traditionally sells this software on a processor value unit basis. For AWS this software is offered on the standard AWS pricing model.
You are only entitled to use what software is provided on the AMI.
Operating system and underlying infrastructure. If purchased traditionally, you can install WebSphere Application Server V7.0 software on a number of hardware and software platforms and work with multiple database servers. In the AWS environment, the hardware and operating system are static in the AMI and cannot be changed.
Does the AMI for IBM WebSphere Application Server V7.0 have
restrictions?
In general you can use the Development AMI for the development and testing
of commercially available applications. Refer to the Development AMI license agreement for additional details. Refer to the
Development AMI license agreement for additional details.
You can use the Production AMI for any purpose as you would a standard WebSphere Application Server license, such as development, test, production, and deployment. Refer to the Production AMI license agreement for additional details.
When was IBM WebSphere
Application Server V7.0 released to market?
If an IBM WebSphere Application Server V7.0 customer is under current
maintenance, do they get AWS AMIs for free?
No. However, an existing IBM WebSphere Application Server V7.0
customer might decide to deploy their existing products on AWS.
See PVUs required for Amazon Elastic Compute Cloud for
more details.
Which AWS instance types are available with the AMI for IBM WebSphere
Application Server V7.0?
For single user development purposes you can use a Standard Small Instance
or High-CPU Medium instance.
Can I cluster my AMIs for WebSphere Application Server V7.0 for
performance and load balancing?
The WebSphere Application Server V7.0 AMI does not provide clustering or load balancing. Amazon provides AMI load balancing options that can be considered.
Can I have a failover scenario with the AMI for WebSphere Application
Server V7.0 on AWS?
With the AMI for WebSphere Application Server V7.0 available for AWS,
content can only be served from one single server running the AMI for
WebSphere Application Server V7.0 at a time. Review the AWS Customer
Agreement and license information for a full set of requirements and
restrictions that apply to WebSphere Application Server V7.0.
Generally, when you set up these AMI instances on AWS you choose Elastic
Block Storage (EBS) as the storage option. EBS provides a persistent
store. If your live AWS instance fails, you can start a new instance and
reuse the existing EBS storage to restore your server. Your Web site is
not available from the time the AWS instance fails to the time the new AMI
instance starts and you reconfigure the AMI. This process takes several
minutes, depending on the specific configuration of the AWS
instance.
If the restrictions imposed by the AMI for WebSphere Application
Server V7.0 do not suite my needs, are there AMIs with a fully
unrestricted version of WebSphere Application Server V7.0?
There is no unrestricted (full) version of WebSphere Application Server
V7.0 currently available from AWS. You can purchase the full version of
WebSphere Application Server V7.0 from
IBM WebSphere Application Server site.
These full versions can be installed on AWS, using AWS as the hosted
infrastructure.
How do I use the remote deploy functionality in IBM Rational
Application Developer with the AMI for WebSphere Application Server
V7.0?
AMIs hosted on Amazon EC2 use network address translation (NAT) technology.
NAT technology maps an external public IP address to an internal IP
address within the Amazon EC2 network.
To configure the remote deploy functionality in Rational Application
Developer to work with the AMI for WebSphere Application Server V7.0, the
network of the Rational Application Developer machine must be configured
to account for the EC2 NAT technology.
Determine the external public IP address of your AMI.
Determine the fully qualified host name of your AMI. Use the
following command: hostname –fqdn
Determine the internal host name of your AMI. Use the following
command: hostname
On your Rational Application Developer machine, configure the
/etc/hosts files to account for the Amazon EC2 NAT technology; for
example:
How do I access my AMI for WebSphere Application Server V7.0 from my
Web browser?
Access your AMI for WebSphere Application Server V7.0 instance using its
public DNS server name, which can be obtained from the properties of the
instance. See
the ec2-describe-instances command
for more information. By default, the AMI for WebSphere Application Server
V7.0
administrative agent
is listening on port 24000, so that it can be accessed using a URL in the
following format:
http://<ec2-public-server-name>:24000/ibm/console
The <ec2-public-server-name> value is the fully qualified
public DNS server name.
Can I use my corporate LDAP User Directory with the WebSphere
Application Server V7.0?
There are some key options and considerations to take into account.
Because AWS is a cloud-based offering, do not integrate your corporate user
directory in real time. Doing so creates a significant impact to
performance and reliability, especially since the link between AWS and
your remote office relies on the Internet, which cannot guarantee
bandwidth and availability.
Therefore, consider the following two core options:
Use the file-based
Federated Repository
that is included in WebSphere Application Server.
Use a third-party supported LDAP server hosted on Amazon
EC2, thereby reducing the impact of Internet bandwidth and
reliability by linking to a local user directory. For a list of
supported user directories, consult the
supported software document
for IBM WebSphere Application Server V7.0.
What user ID should I use to log into the WebSphere Application
Server V7.0
administration console?
The AMI instance comes with a default user account,virtuser, which
is used to enable WebSphere Application Server global security and to
access the
administrative console.
During the boot sequence of the AMI instance, you are asked to set the
password for this user.
How do I access the UNIX® console of my AMI instance?
The AMI instance is preconfigured to allow you to access the UNIX console
using a secure shell (SSH) and the private key you had to generate and
specify at the time the instance was created. With this configuration, you
can open a secure console without having to know the root password of the
instance. The boot sequence of the instance presents panels for license
agreements and the localization of the image.
If I suspect an error with my AMI for WebSphere Application Server
V7.0, how do I begin to debug the problem?
If you suspect a problem with WebSphere Application Server V7.0, refer to
the troubleshooting section of
the information center.
You can also use
the AWS forums to
see if your problem has already been discussed with others, and to solicit
the help of the AWS user community in correcting your error.
How do I monitor the AMI for WebSphere Application Server V7.0 to
ensure I am not running out of capacity?
Use traditional UNIX tools to determine if the instance has enough
memory and disk capacity. For WebSphere Application Server V7.0, since it
is a Java-based product, you must also employ traditional Java monitoring
mechanisms, such as monitoring garbage collection activity using the
verbosegc JVM option.
Can I apply publically available WebSphere Application Server V7.0
fixes to my AMI?
Embedded in the AMI is the IBM
Update Installer
for WebSphere Software (/opt/IBM/WebSphere/AppServer/UpdateInstaller). Use
the Update Installer to apply WebSphere Application Server V7.0 fix packs
and interim fixes from the
IBM WebSphere Application Server V7.0 Support site.
Where do I find more information on IBM WebSphere Application Server
V7.0?
IBM, the IBM (logo), Tivoli, and WebSphere are trademarks or registered
trademarks of International Business Machines Corporation in the United
States, other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other
countries, or both.
UNIX is a registered trademark of The Open Group in the United States,
other countries, or both
Java is a trademark of Sun Microsystems, Inc in the United States, other
countries, or both.
Amazon Web Services, AWS, Amazon Elastic Compute Cloud, EC2, Amazon Simple
Storage Service, Amazon S3 are trademarks or registered trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries.
Other company, product, or service names may be trademarks or service marks
of others.
References in this publication to IBM products or services do not imply
that IBM intends to make them available in all countries in which IBM
operates. The following paragraph does not apply to the United Kingdom or
any other country where such provisions are inconsistent with local
law:
INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS
IS" WITHOUT WARRANTYOF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING,
BUTNOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR APARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the program(s)
described in this publication at any time without notice.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available
sources. IBM has not tested those products and cannot confirm the accuracy
of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be
addressed to the suppliers of those products.
The information in this publication is provided AS IS without warranty.
Such information was obtained from publicly available sources, is current
as of January 2009, and is subject to change. Any performance data
included in the paper was obtained in the specific operating environment
and is provided as an illustration. Performance in other operating
environments may vary. More specific information about the capabilities of
products described should be obtained from the suppliers of those
products.
