Professional Documents
Culture Documents
Get Started WebSphere Portal and IBM Web Content Management AMI
Get Started WebSphere Portal and IBM Web Content Management AMI
1.
Table of Contents
1. INTRODUCTION........................................................................................ 3
1.1 Purpose................................................................................................... 3
1.2 Topics covered........................................................................................ 3
1.3 Assumptions............................................................................................ 3
1.4 AMI contents and configuration ............................................................... 4
2. INITIALIZING A NEW INSTANCE OF THE AMI........................................ 4
2.1 Amazon Instance Information .................................................................. 5
2.1.1 INSTANCE SIZES........................................................................................ 5
2.1.2 SECURITY GROUPS..................................................................................... 5
2.2 Managing AMI instances......................................................................... 5
2.3 Accessing the AMI instance ..................................................................... 5
2.3.1 CONSOLE ACCESS..................................................................................... 5
2.3.2 REMOTE DESKTOP ACCESS........................................................................... 6
2.4 Booting the AMI Instance ......................................................................... 7
2.4.1 CONFIGURATION MODULES SEQUENCE........................................................... 7
2.4.2 PRE-INSTALLED OS/SOFTWARE LICENSE AGREEMENT SCREENS.............................7
2.4.3 USER PASSWORD CONFIGURATION SCREENS..................................................... 7
2.4.4 AMAZON W EB SERVICES CONFIGURATION SCREENS........................................... 9
2.4.4.1 Manually input credential files.................................................................. 12
2.4.5 EBS CONFIGURATION MODULE.................................................................. 14
2.4.5.1 Creating a New EBS volume..................................................................... 15
2.4.5.2 Attaching an Existing EBS volume........................................................... 17
2.4.5.3 Use Internal Volatile Storage Only............................................................ 19
2.4.6 W EBSPHERE APPLICATION SERVER AND W EBSPHERE PORTAL CONFIGURATION
PROGRESS SCREENS........................................................................................... 21
2
Lotus AMI Usage Guide
1. Introduction
1.1 Purpose
This document details the deployment instructions for WebSphere Portal® Server and
Lotus Web Content Management® Standard Edition 6.1.5 Amazon Machine Images
(here after referred to simply as “the AMI”) under the Amazon Elastic Compute Cloud™
(EC2™) infrastructure.
This AMI will allow you to experience the fully functional WebSphere Portal Server and
Web Content Management instance on Linux® on Amazon EC2. The AMI also includes
customized modules to guide you through the AMI instance configuration steps. The
remainder of this document will guide you through these steps, as well as how to build
new AMIs based on instances created based on the original. You may wish to build new
AMIs to contain your own custom WebSphere Portal Server and Lotus Web Content
Management Standard Edition solutions.
1.3 Assumptions
This documentation is intended for users who have a general knowledge of Linux and
how Linux works. The user should also possess a good understanding of Linux
commands and how to manipulate input and output.
3
Lotus AMI Usage Guide
A basic overview of how to manage WebSphere Portal will be provided. The user will be
provided with links to product documentation for more detailed information and guidance
on how to use the product to build a Web site.
4
Lotus AMI Usage Guide
Typical deployments of WebSphere Portal Server and Lotus Web Content Management
Standard Edition require at least a Large image size, to have access to enough physical
memory and computing power. A small instance type is fine for development, single-
user purposes only.
Note that the WebSphere Portal and Lotus Web Content Management Development
AMIs are running with a 32-bit version of SuSE SLES Linux operating system, so only
32-bit instance types can be used. Production AMIs are 64-bit, so 64-bit enabled image
sizes should be used for production use.
For more information on instance types and pricing of Amazon EC2, please visit http://
aws.amazon.com/ec2/
5
Lotus AMI Usage Guide
For Linux SSH users, the keypair file is simply provided on the command line using the -
i parameter. For example:
For Putty users, Amazon has documentation on how to configure Putty with the public
key for automatic authentication: http://docs.amazonwebservices.com/
AWSEC2/2007-03-01/GettingStartedGuide/putty.html
Amazon also has a video that demonstrates how to set up Putty: http://
developer.amazonwebservices.com/connect/entry.jspa?externalID=583.
File transfer is allowed using secure FTP (SFTP) along with the secure keypair used for
SSH access.
Note: Only SSH access using the secure keypair is allowed. Instances created based
on these AMIs have password-based authentication disabled for higher security.
You can now access the instance remotely using its public DNS host name. For
example:
vncviewer ec2-174-129-160-99.compute-1.amazonaws.com:1
When an AMI instance is first booted and accessed over SSH, the user will be prompted
to accept the license agreements of software components pre-installed on the AMI.
Next, a sequence of AWS and product-specific instance configuration modules allow the
user to configure the AMI according to their specific needs. This section provides an
outline and description of each step of the initial configuration process.
6
Lotus AMI Usage Guide
7
Lotus AMI Usage Guide
8
Lotus AMI Usage Guide
9
Lotus AMI Usage Guide
For this module, there are two methods of transferring over the credential files that you
generated as part of your AWS account creation: a key file and certificate file.
The first method is to copy over the files directly to your instance using secure FTP
(SFTP) or secure copy (SCP). Now would be a good time to transfer the key and
certificate files to a local directory in the image, such as /mnt, which will be
referred to in the next section.
The second method is to manually input the credential files as described in section
2.2.3.1. This method is not recommended when working in a command line
environment.
Following the first method, choose the option Certificate and Private Key exist locally.
Select [Next] and press Enter to continue.
10
Lotus AMI Usage Guide
Enter in the location of the private key and the certificate files in the corresponding input
boxes, and select [Next]:
11
Lotus AMI Usage Guide
The module will run an API command to validate the AWS credentials. If successful,
you will be prompted with the following result dialog. Select [End] to continue.
12
Lotus AMI Usage Guide
The next page contains fields that have input boxes for the X.509 certificate and private
key files. Copy and paste the corresponding files’ contents into the dialog boxes. To
paste in a PuTTY window, simply click the right mouse button.
13
Lotus AMI Usage Guide
When you are done pasting the content of the files, select [Next]. An EC2 API
command will be run against the credentials to see if they are valid. If the credentials
are valid, the result dialog will appear. Select [End] to complete the module.
If you selected to skip AWS credential configuration on the first screen of the AWS
Credentials Configuration page, then setting up an EBS storage volume will be skipped
and WebSphere Portal Server and Web Content Management Standard Edition will
operate from a configuration stored locally in the EC2 instance, which is not
recommended. If the instance prematurely terminates, then all previous work will be lost.
See the next section for details.
14
Lotus AMI Usage Guide
Choose the size of the EBS volume by entering an integer between 1 and 1000
(gigabytes), and select [Next]. We recommend at least 5 GB:
15
Lotus AMI Usage Guide
A status bar and conditions will be presented while the volume is being created and
mounted. The below result dialog will appear upon completion. Select [End] to exit the
module.
16
Lotus AMI Usage Guide
The next screen will show details regarding the EBS volumes that you may have
associated with your account. If this is your first time using Amazon EC2, there may not
be any volumes available. As such, creating a new volume will be the only option to use
persistent storage with an AMI instance. Please refer to the previous section in this
case.
Note that only EBS volumes located in the same zone as your instance and are not
already attached to any instance will be shown. If there are available volumes, select a
volume by highlighting it in the selection box. You will also be presented with an option
to format the volume. To format the volume, please select the Format Volume
checkbox. Select [Next] to continue.
17
Lotus AMI Usage Guide
A status bar and conditions will be presented while the volume chosen is being attached
and mounted. The result dialog will appear when the aforementioned steps are
completed, as shown. Select [End] to complete the module.
18
Lotus AMI Usage Guide
19
Lotus AMI Usage Guide
An alert dialog will be shown. Select [Yes] to continue with using volatile storage, or
select [No] to go back to the menu.
20
Lotus AMI Usage Guide
In Figure 19, the application server configuration progress is tracked. During this
process, the application server and WebSphere Portal's configuration profile is updated
with the new instance's host name and the new virtuser password. The datasource
configurations are also updated to point to the local database instance using the new
internal host name of the instance. Note that this process can take several minutes
to complete.
21
Lotus AMI Usage Guide
Once system configuration is completed, the following screen will appear showing that
the configuration is successful. Select [End] to continue.
Initial configuration is now complete and the system is ready to use. The next section
describes how to get started working with the new instance.
22
Lotus AMI Usage Guide
23
Lotus AMI Usage Guide
./apachectl start
Likewise, to stop the HTTP Server, run the following command:
./apachectl stop
The HTTP Server reads its application server plugin configuration from /opt/IBM/
HTTPServer/Plugins/config/webserver1/plugin_cfg.xml, which gets automatically
refreshed during AMI instance creation.
24
Lotus AMI Usage Guide
For more information on using WebSphere Portlet Factory, see the product
documentation center: http://www.ibm.com/software/genservers/portletfactory.
If you are accessing the graphical desktop remotely, there are icons on the desktop for
accessing the portal home page and administration console.
4. Servicing instances
WebSphere Portal Server and Lotus Web Content Management Standard Edition can
be serviced on the AMI instance just like any other native installation of this software.
Corrective service packages, in the form of iFixes (or “interim fixes”, which address a
particular product issue) or fixpacks (regular, cumulative roll-ups of iFixes into a single
installable unit), are available to be downloaded from the IBM support site:
From these sites, you can search on problem symptoms and receive information on
technotes, redbooks, and fixes that may address that problem.
iFixes and fixpack installation requires the use of the Portal Update Installer, which can
be downloaded from here: http://www.ibm.com/support/docview.wss?uid=swg24006942
25
Lotus AMI Usage Guide
Alternatively, you may wish to re-apply your customizations to a new instance created
from an AMI that has been updated to a more recent service level. To do this, you will
need to have extracted all custom artifacts from the instance so that they can be applied
again, such as:
• Exported content libraries, using the ConfigEngine's export-wcm-data task
• Exported portal configuration using the xmlaccess utility
• All portlet WAR files and other J2EE resources
Then, after creating a new instance, these artifacts can be imported into the new
instance using the appropriate administration utilities.
Refer to the Lotus Web Content Management InfoCenter for topics on exporting and
importing content libraries: http://publib.boulder.ibm.com/infocenter/wcmdoc/v6r0/
index.jsp
1. Stop WebSphere Portal using either the desktop icon or the stopServer.sh script, as
described in section 3.2.
The last command exits the db2inst1 user shell and returns back to root user.
This also removed the automatic mounting of an EBS volume from the /etc/fstab file,
so when the system is rebooted, there will be no EBS volume mounted.
26
Lotus AMI Usage Guide
Note: The resetvm.sh may display errors about files not being found or instruct you
to reboot the system. Ignore any of these messages and proceed to the next step
below.
4. Since you have customized portal and web content, you will need to replace the
default wp_profile configuration profile and db2inst1 instance archives with the
customized versions:
> cd /
> rm /opt/IBM/WebSphere/wp_profile
> zip -r /opt/IBM/WebSphere/wp_profile.zip /mnt/portalfs/
wp_profile
> cd /
> rm /home/db2inst1/db2inst1
> zip -r /home/db2inst1/db2inst1.zip /mnt/portalfs/db2inst1
Now, when a new instance is created, your customized data will be used instead of
the default configuration. If any other volatile data is stored on an EBS volume, this
will need to also be copied back into the local filesystem to be stored with the AMI.
5. Bundle the new AMI, to get it ready for uploading to Amazon's Simple Storage
Service (S3). The ec2-bundle-vol command requires the private key and certificate
files associated with your Amazon account, and probably already uploaded as part of
the original AWS configuration for this instance (see section 2.3.4).
> ec2-bundle-vol -k /mnt/pk.pem -c /mnt/cert.pem -u <AWS_ID> -p
ami_v1 -d /mnt/ec2
Specify the location of your private key and certificate files if different than above, for
the -k and -c parameters. Also provide your 12-digit AWS ID in place of <AWS_ID>.
Specify a meaningful package name for the new AMI instead of “ami_v1”. And lastly,
be sure to place the new bundle under the /mnt directory, which has plenty of space
to hold the new image. The example places it under /mnt/ec2, which is a directory
you will have to created.
For more information on this command, refer to the Amazon documentation: http://
docs.amazonwebservices.com/AWSEC2/latest/DeveloperGuide/CLTRG-ami-bundle-
vol.html
6. Upload the bundle to S3. This requires a bucket to store the image in, which helps
you organize all of your AMIs by “buckets”. If the bucket you specify doesn't exist, it
will be created:
> ec2-upload-bundle -b ami_bucket -m /mnt/ec2/ami_v1.manifest.xml
-a <AWS_access_key> -s <AWS_secret_access_key> --retry
Specify the bucket to use instead of “ami_bucket”. Also specify the bundle's manifest
file and location instead of “/mnt/ec2/ami_v1.manifest.xml”. You will need to provide
your AWS access and secret access keys for the -a and -s parameters, which can be
obtained from under Your Account -> Access Identifiers after logging into Amazon
Web Services (http://aws.amazon.com/). Lastly, the –retry option ensures the upload
continues where it left off if there was a network error.
27
Lotus AMI Usage Guide
7. Register your new AMI. Again, you will need your private key and certificate files for
this operation.
> cd /root/ec2/bin
> ./ec2-register -K /mnt/pk.pem -C /mnt/cert.pem ami_bucket/
ami_v1.manifest.xml
28
© Copyright IBM Corporation 2009
All Rights Reserved.
IBM Canada
8200 Warden Avenue
Markham, ON
L6G 1C7
Canada
Printed in Canada
01/2009
IBM, IBM (logo), DB2 are trademarks or registered trademarks of The information in this publication is provided AS IS without
International Business Machines Corporation in the United States, warranty. Such information was obtained from publicly available
other countries, or both. sources, is current as of January 2009, and is subject to change.
Any performance data included in the paper was obtained in the
Linux is a trademark of Linus Torvalds in the United States, other specific operating environment and is provided as an illustration.
countries, or both. Performance in other operating environments may vary. More
specific information about the capabilities of products described
UNIX is a registered trademark of The Open Group in the United should be obtained from the suppliers of those products.
States, other countries, or both