IBM WebSphere Portal and LotusWeb Content Management

Amazon Machine Image (AMI) GetStarted Guide

Last updated December 8, 2009

Marshall Lamb (mlamb@us.ibm.com)Xinyi Xu (xinyi@us.ibm.com)

WebSphere Portal Development, Software GroupIBM Research Triangle Park

Lotus AMI Usage Guide

1.

Table of Contents1. 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........................................................................................ 52.1.2 SECURITY GROUPS..................................................................................... 5

2.2 Managing AMI instances ......................................................................... 5 2.3 Accessing the AMI instance ..................................................................... 5

2.3.1 CONSOLE ACCESS..................................................................................... 52.3.2 REMOTE DESKTOP ACCESS........................................................................... 6

2.4 Booting the AMI Instance ......................................................................... 7 2.4.1 CONFIGURATION MODULES SEQUENCE........................................................... 72.4.2 PRE-INSTALLED OS/SOFTWARE LICENSE AGREEMENT SCREENS.............................72.4.3 USER PASSWORD CONFIGURATION SCREENS..................................................... 72.4.4 AMAZON WEB 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 WEBSPHERE APPLICATION SERVER AND WEBSPHERE PORTAL CONFIGURATION

PROGRESS SCREENS........................................................................................... 213. WORKING WITH AN AMI INSTANCE ..................................................... 23

3.1 File system locations ............................................................................. 23 3.2 Starting and stopping WebSphere Portal .............................................. 24 3.3 Starting and stopping the HTTP Server ................................................. 24 3.4 Using WebSphere Portlet Factory (Development AMI Only) ................. 25 3.5 Accessing the site from a browser ......................................................... 26 3.6 User accounts ........................................................................................ 26

4. SERVICING INSTANCES ........................................................................ 27

5. REPACKAGING THE AMI ....................................................................... 28

2

Lotus AMI Usage Guide

1. Introduction

1.1 PurposeThis document details the deployment instructions for WebSphere Portal® Server andLotus 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 includescustomized modules to guide you through the AMI instance configuration steps. Theremainder of this document will guide you through these steps, as well as how to buildnew AMIs based on instances created based on the original. You may wish to build newAMIs to contain your own custom WebSphere Portal Server and Lotus Web ContentManagement Standard Edition solutions.

1.2 Topics coveredThis document focuses on the process of setting up an instance of the AMI. It will coverthe following topics in detail:

► Initializing a new instance based on the AMI, including setting up persistentstorage for the instance via the use of Elastic Block Storage (EBS)

► Accessing and managing WebSphere Portal Server and Lotus Web ContentManagement Standard Edition

► Creating a WebSphere Portlet Factory Project in Eclipse (Development AMIonly)

► Building a new AMI based on an instance you customize

1.3 AssumptionsThis documentation is intended for users who have a general knowledge of Linux andhow Linux works. The user should also possess a good understanding of Linuxcommands 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 beprovided with links to product documentation for more detailed information and guidanceon how to use the product to build a Web site.

1.4 AMI contents and configurationThe WebSphere Portal and Lotus Web Content Management AMIs are preinstalled andpreconfigured instances of the product. Instances created based on these AMIs areready to use and have been preconfigured with certain features to make it easier to getstarted. The product configuration includes:• Security enabled: WebSphere Application Server security is enabled, with the

virtuser user ID serving as both the portal administrator and WebSphereApplication Server administrator id. During the initialization of the AMI, you will berequired to set the password for the virtuser user id.

• HTTP Server enabled: The IBM HTTP Server is configured to provide port 80access to WebSphere Portal. See section 3.3 on how to use the HTTP Server.

• External DB2 database: An instance IBM DB2 Enterprise Edition is installed andconfigured as WebSphere Portal and Lotus Web Content Management's externaldatabase and user repository. This provides an enterprise class and highlyperforming database environment.

• New Site Wizard: WebSphere Portal is preconfigured with the New Site Wizard,available from the Portal Catalog, which aids in the creation of micro sites withinthe portal. For more information, refer to the Portal Catalog entry .

• Default content sites: WebSphere Portal is preconfigured with two sample virtualportals: a sample intranet content site, and a sample Internet content site. Bothsites are accessible through the virtual portal URIs /wps/portal/intranet and /wps/portal/internet, respectively.

• Developer mode enabled: Developer mode speeds up the start time forWebSphere Portal by deferring the start of individual web applications and portletsuntil they are first requested by the end user. For more information on developermode, refer to the WebSphere Portal Information Center.

• WebSphere Portlet Factory: Eclipse and WebSphere Portlet Factory areinstalled. (Development AMI only)

2. Initializing a new instance of the AMI

The following sections outline prerequisite information and steps for creating a newinstance of an AMI. Details of how to use the Amazon Web Services (AWS) tools toaccess AWS, set up an account, and create AMI instances are not provided here. TheGetting Started Guide on the AWS Web site should be used first to become familiar withthis process: http://docs.amazonwebservices.com/AWSEC2/latest/GettingStartedGuide/

4

Lotus AMI Usage Guide

2.1 Amazon Instance Information

2.1.1 Instance sizesAmazon EC2 provides the flexibility to choose from a number of different instance typesto meet your computing needs. Each instance provides a predictable amount ofdedicated compute capacity and is charged per instance-hour consumed.

Typical deployments of WebSphere Portal Server and Lotus Web Content ManagementStandard Edition require at least a Large image size, to have access to enough physicalmemory 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 DevelopmentAMIs are running with a 32-bit version of SuSE SLES Linux operating system, so only32-bit instance types can be used. Production AMIs are 64-bit, so 64-bit enabled imagesizes should be used for production use.

For more information on instance types and pricing of Amazon EC2, please visit http:// aws.amazon.com/ec2/

2.1.2 Security groupsThe security group you define and use when creating new instances needs to haveadditional ports authorized for WebSphere Portal. Ensure you have the following portsauthorized:

• 10040: Default HTTP port for the WebSphere Portal instance• 10027: Application server administration console port• 80: Web server port

See the AWS documentation for more information.

2.2 Managing AMI instancesAWS provides a simple Web console for managing AMI instance and EBS storagevolumes: https://console.aws.amazon.com/.

2.3 Accessing the AMI instance

2.3.1 Console accessThe AMI is configured to allow secure shell (SSH) access with automatic root userauthentication using a secure RSA private key based on the keypair specified atinstance creation. The user will need the RSA private keypair saved to a local file thatcan be used as input to SSH.

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:

ssh –i <location of rsa keypair file> <instance public address>

For Putty users, Amazon has documentation on how to configure Putty with the publickey 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 forSSH access.

Note: Only SSH access using the secure keypair is allowed. Instances created basedon these AMIs have password-based authentication disabled for higher security.

2.3.2 Remote desktop accessThe SuSE installation has vncserver automatically included, so you can use a free VNCclient to remotely connect to the instance's graphical desktop. The boot sequence of thenew instance, described below, also sets up desktop icons to help with starting andstopping the WebSphere Portal server as well as access the portal home page andadministrative console.

To enable vncserver, do the following:1. Switch users to “virtuser”, since the desktop icons belong to virtuser's desktop.Alternatively, the desktop icons can be copied from /home/virtuser/Desktop to /root/Desktop if running the desktop for root user is preferred.

> su virtuser

2. Start the VNC server in the background:> vncserver

You can now access the instance remotely using its public DNS host name. Forexample:

vncviewer ec2-174-129-160-99.compute-1.amazonaws.com:1

2.4 Booting the AMI Instance

When an AMI instance is first booted and accessed over SSH, the user will be promptedto accept the license agreements of software components pre-installed on the AMI.Next, a sequence of AWS and product-specific instance configuration modules allow theuser to configure the AMI according to their specific needs. This section provides anoutline and description of each step of the initial configuration process.

6

Lotus AMI Usage Guide

2.4.1 Configuration Modules SequenceWhen an AMI instance is started for the very first time, a user will go through thefollowing interactive configuration steps in sequence before the system is ready to use:

1. Pre-installed OS/software license agreement screens (production AMIs only)

2. Password configuration screens

3. Amazon Web Services access configuration screens

4. Elastic Block Storage (EBS) configuration screens

5. WebSphere Application Server and WebSphere Portal configuration progressscreen

A description of each interactive step is listed in the next several sub-sections.

2.4.2 Pre-installed OS/software license agreementscreens

When a production AMI instance boots for the very first time, the first step is to gothrough the license agreement screens. (License agreements for Development AMIsare covered by a different process and so are not shown during the boot-up sequence.)This is to ensure that the user has accepted all required operating system and thelicense agreements of pre-installed software components before starting to use theinstance.

The user must agree to all the licenses shown, otherwise the instance will terminate.

2.4.3 User password configuration screensThe next set of screens require the user to reset the passwords for the root andvirtuser users. Virtuser is the WebSphere Application Server and WebSphere Portaladministrative user. Use virtuser to login to either WebSphere Portal or the WebSphereApplication Server administration console.

7

Lotus AMI Usage Guide

Figure 1 Password configuration for the root user

Figure 2 Password configuration for the virtuser user

8

Lotus AMI Usage Guide

Figure 3 Password configuration results

2.4.4 Amazon Web Services configuration screensAfter the operating system/software license agreement screens, the Amazon WebServices configuration screens will show.

These screens allow the user to setup the AWS credentials required for the usage ofElastic Block Storage, which will be discussed in the next sub-section.

9

Lotus AMI Usage Guide

Figure 4 AWS credentials setup choices

For this module, there are two methods of transferring over the credential files that yougenerated 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 andcertificate files to a local directory in the image, such as /mnt, which will bereferred to in the next section.

The second method is to manually input the credential files as described in section2.2.3.1. This method is not recommended when working in a command lineenvironment.

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

Figure 5 Local private key and certificate selection

Enter in the location of the private key and the certificate files in the corresponding inputboxes, and select [Next]:

Figure 6 Local private key and certificate file location selection

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.

Figure 7 AWS credential configuration results

2.4.4.1 Manually input credential files

To manually input the credential files, select the option Manually enter contents forcertificate and private key on the first screen of the AWS Credentials Configurationpage. Select [Next] to continue.

12

Lotus AMI Usage Guide

Figure 8 Manually enter certificate and private key selection

The next page contains fields that have input boxes for the X.509 certificate and privatekey files. Copy and paste the corresponding files’ contents into the dialog boxes. Topaste in a PuTTY window, simply click the right mouse button.

Figure 9 Manual entry of the certificate and private key

13

Lotus AMI Usage Guide

When you are done pasting the content of the files, select [Next]. An EC2 APIcommand will be run against the credentials to see if they are valid. If the credentialsare valid, the result dialog will appear. Select [End] to complete the module.

Figure 10 AWS credential configuration results

If you selected to skip AWS credential configuration on the first screen of the AWSCredentials Configuration page, then setting up an EBS storage volume will be skippedand WebSphere Portal Server and Web Content Management Standard Edition willoperate from a configuration stored locally in the EC2 instance, which is notrecommended. If the instance prematurely terminates, then all previous work will be lost.See the next section for details.

2.4.5 EBS Configuration ModuleAmazon EBS is a persistent storage option for EC2. Since instance storage is volatile,data that is required to be available beyond the lifetime of an AMI instance must bestored on an EBS volume. The EBS Configuration module can either create a newEBS volume, mount a pre-existing EBS volume, or use the instance’s own internalvolatile storage. The AWS credentials must be set up successfully in the previous AWSConfiguration Module in order for this module to run.

Note that if an AMI instance prematurely terminates, because of an operating systemerror, for example, then the AMI instance is lost and a new instance must be created.That is why it is important to consider leveraging EBS to persist vital configuration data.

14

Lotus AMI Usage Guide

2.4.5.1 Creating a New EBS volume

To create a new EBS volume, select the first option, and select [Next]:

Figure 11 New EBS volume selection

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

Figure 12 EBS volume size

A status bar and conditions will be presented while the volume is being created andmounted. The below result dialog will appear upon completion. Select [End] to exit themodule.

Figure 13 EBS configuration results

16

Lotus AMI Usage Guide

2.4.5.2 Attaching an Existing EBS volume

To mount an existing volume associated with your AWS account, choose the secondoption, and select [Next]:

Figure 14 Existing EBS volume selection

The next screen will show details regarding the EBS volumes that you may haveassociated with your account. If this is your first time using Amazon EC2, there may notbe any volumes available. As such, creating a new volume will be the only option to usepersistent storage with an AMI instance. Please refer to the previous section in thiscase.

Note that only EBS volumes located in the same zone as your instance and are notalready attached to any instance will be shown. If there are available volumes, select avolume by highlighting it in the selection box. You will also be presented with an optionto format the volume. To format the volume, please select the Format Volumecheckbox. Select [Next] to continue.

17

Lotus AMI Usage Guide

Figure 15 Existing EBS volume selection, part 2

A status bar and conditions will be presented while the volume chosen is being attachedand mounted. The result dialog will appear when the aforementioned steps arecompleted, as shown. Select [End] to complete the module.

18

Lotus AMI Usage Guide

Figure 16 EBS configuration results

2.4.5.3 Use Internal Volatile Storage Only

If you decide to store your data only within the volatile storage provided inside an AMIinstance, choose Use internal storage (volatile) option and select [Next] to continue.

19

Lotus AMI Usage Guide

Figure 17 Use internal storage selection

An alert dialog will be shown. Select [Yes] to continue with using volatile storage, orselect [No] to go back to the menu.

Figure 18 Use internal storage warning

20

Lotus AMI Usage Guide

2.4.6 WebSphere Application Server and WebSpherePortal configuration progress screens

After the password EBS configuration screens are completed, the software configurationmodule will run. This module will present a progress dialog as it updates theWebSphere Application Server, WebSphere Portal, DB2 and Web ContentManagement components with the information provided so far. Specifically:

1. The software configuration will be updated with the new instance's hostname andvirtuser password

2. The volatile file system directories (WebSphere Application Server configurationprofile and DB2 database instance) will be backed up and relocated to the EBSvolume newly attached and mounted.

Note: If volatile storage was selected in the previous configuration screens (no EBSvolume usage), then these volatile file system directories are still copied to the /mntdirectory as that volume has significantly more storage than the root (/) file system.

Figure19 Application server configuration progress

In Figure 19, the application server configuration progress is tracked. During thisprocess, the application server and WebSphere Portal's configuration profile is updatedwith the new instance's host name and the new virtuser password. The datasourceconfigurations are also updated to point to the local database instance using the newinternal host name of the instance. Note that this process can take several minutesto complete.

21

Lotus AMI Usage Guide

Once system configuration is completed, the following screen will appear showing thatthe configuration is successful. Select [End] to continue.

Figure 19 Application server configuration results

Initial configuration is now complete and the system is ready to use. The next sectiondescribes how to get started working with the new instance.

3. Working with an AMI instance

Congratulations on completing the instantiation of a WebSphere Portal Server and WebContent Management Standard Edition AMI. We will now orient you on how to getstarted with the system. For more information on how to administer, customize, anddevelop applications for the portal and web content management platform, refer to theonline product documentation: http://www.ibm.com/developerworks/websphere/zones/portal/proddoc.html

3.1 File system locationsItem Location

WebSphere Portal installationdirectory

/opt/IBM/WebSphere/PortalServer

22

Lotus AMI Usage Guide

WebSphere Application Serverinstallation directory

/opt/IBM/WebSphere/AppServer

Application server configurationprofile

/opt/IBM/WebSphere/wp_profile

DB2 install directory /opt/ibm/db2

DB2 instance directory /home/db2inst1/db2inst1

WebSphere Portal log directory /opt/IBM/WebSphere/wp_profile/logs/WebSphere_Portal

IBM HTTP Server installationdirectory (production AMI only)

/opt/IBM/WebSphere/HTTPServer

Eclipse installation directory(development AMI only)

/opt/eclipse

WebSphere Portlet Factoryinstallation directory (developmentAMI only)

/opt/IBM/WPFactory

3.2 Starting and stopping WebSphere Portal

Starting and stopping WebSphere Portal is accomplished by using the WebSphereApplication Server startServer.sh and stopServer.sh shell scripts, respectively.

Open a secure shell session with your new instance, then change to the /opt/IBM/WebSphere/wp_profile/bin directory. To start WebSphere Portal, run the followingcommand from within this directory:./startServer.sh WebSphere_PortalLikewise, stop WebSphere Portal using the following command within the samedirectory:./stopServer.sh WebSphere_Portal -user virtuser -password <password>Note that with the stopServer.sh script, it is required to specify the administrative user(virtuser) and password, which was provided in the password configuration panelsduring initial setup of this instance.If you are accessing the graphical desktop remotely, there are icons on the desktop forstarting and stopping WebSphere Portal.

3.3 Starting and stopping the HTTP ServerThe AMI comes preconfigured with the IBM HTTP Server to allow port 80 access toWebSphere Portal. By default, the HTTP Server is stopped. To start the HTTP Server,change to the /opt/IBM/HTTPServer/bin directory and run the following command:

23

Lotus AMI Usage Guide

./apachectl start

Likewise, to stop the HTTP Server, run the following command:

./apachectl stopThe HTTP Server reads its application server plugin configuration from /opt/IBM/HTTPServer/Plugins/config/webserver1/plugin_cfg.xml, which gets automaticallyrefreshed during AMI instance creation.

3.4 Using WebSphere Portlet Factory(Development AMI Only)

The AMI comes preinstalled with the IBM WebSphere Portlet Factory and Eclipse fordeveloping portlet applications. To utilize WebSphere Portlet Factory, connect to theAMI instance by VNC Viewer as virtuser, After logging in, you may either change tothe /opt/eclipse directory and run the following command:

./eclipseOr

click WebSphere Portlet Factory desktop icon.

After Eclipse started, you may be prompted with:

Enter your desired location, We would recommend /mnt/portalfs/workspace. Then clickOK.

You may change the workspace perspective by clicking Window > Open Perspective >Other, and selecting WebSphere Portlet Factory, and clicking OK.

You may create a WebSphere Portlet Factory Project by clicking File > New >WebSphere Portlet Factory Project, and following its wizard.

24

Lotus AMI Usage Guide

For more information on using WebSphere Portlet Factory, see the productdocumentation center: http://www.ibm.com/software/genservers/portletfactory.

3.5 Accessing the site from a browser

After WebSphere Portal has started, you can access it using the following URLs:

WebSphere Portal home page (if HTTP Server is stopped):

http://<public host name>:10040/wps/portal

WebSphere Portal home page (if HTTP Server is active):

http://<public host name>/wps/portal

WebSphere Application Server admin console:

http://<public host name>:10027/ibm/console

If you are accessing the graphical desktop remotely, there are icons on the desktop foraccessing the portal home page and administration console.

4. Servicing instances

WebSphere Portal Server and Lotus Web Content Management Standard Edition canbe 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 aparticular product issue) or fixpacks (regular, cumulative roll-ups of iFixes into a singleinstallable unit), are available to be downloaded from the IBM support site:

WebSphere Portal: http://www-01.ibm.com/software/genservers/portal/support/

Lotus Web Content Management: http://www-01.ibm.com/software/lotus/products/webcontentmanagement/support/

From these sites, you can search on problem symptoms and receive information ontechnotes, redbooks, and fixes that may address that problem.

iFixes and fixpack installation requires the use of the Portal Update Installer, which canbe 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 createdfrom an AMI that has been updated to a more recent service level. To do this, you willneed to have extracted all custom artifacts from the instance so that they can be appliedagain, 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 newinstance using the appropriate administration utilities.

Refer to the WebSphere Portal InfoCenter for topics on administering WebSpherePortal, and the use of the xmlaccess utility specifically: http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/index.jsp

Refer to the Lotus Web Content Management InfoCenter for topics on exporting andimporting content libraries: http://publib.boulder.ibm.com/infocenter/wcmdoc/v6r0/index.jsp

5. Repackaging the AMI

After customizing an instance of a WebSphere Portal Server and Web ContentManagement Standard Edition AMI with custom applications, site designs, and contentlibraries, you may want to build a new AMI based on this instance from which newinstances can be created. The EC2 tools are already installed and configured on yourinstance, so follow the instructions below to prepare and upload a new AMI.

1. Stop WebSphere Portal using either the desktop icon or the stopServer.sh script, asdescribed in section 3.2.

2. First switch to the db2inst1 user then stop DB2, as follows:> su db2inst1> db2stop> <ctrl-d>

The last command exits the db2inst1 user shell and returns back to root user.

3. Change to the /var/adm/ibmvmcoc-postinstall directory and run the resetvm.shshell script to prepare the software and operating system for reinitialization. If thesystem is rebooted after running this script, then the user will be presented with theinitialization screens documented in section 2.2.

> cd /var/adm/ibmvmcoc-postinstall> ./resetvm.sh

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 youto reboot the system. Ignore any of these messages and proceed to the next stepbelow.

4. Since you have customized portal and web content, you will need to replace thedefault wp_profile configuration profile and db2inst1 instance archives with thecustomized 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 ofthe default configuration. If any other volatile data is stored on an EBS volume, thiswill 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 StorageService (S3). The ec2-bundle-vol command requires the private key and certificatefiles associated with your Amazon account, and probably already uploaded as part ofthe 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> -pami_v1 -d /mnt/ec2

Specify the location of your private key and certificate files if different than above, forthe -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 spaceto hold the new image. The example places it under /mnt/ec2, which is a directoryyou 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 helpsyou organize all of your AMIs by “buckets”. If the bucket you specify doesn't exist, itwill 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 manifestfile and location instead of “/mnt/ec2/ami_v1.manifest.xml”. You will need to provideyour AWS access and secret access keys for the -a and -s parameters, which can beobtained from under Your Account -> Access Identifiers after logging into AmazonWeb Services (http://aws.amazon.com/). Lastly, the –retry option ensures the uploadcontinues 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 forthis operation.

> cd /root/ec2/bin> ./ec2-register -K /mnt/pk.pem -C /mnt/cert.pem ami_bucket/ami_v1.manifest.xml

Instead of “ami_bucket/ami_v1.manifest.xml”, you will need to specify the bucket andmanifest name that you used during upload. After registration, you are now ready tocreate instances based on your new AMI!

28

© Copyright IBM Corporation 2009All Rights Reserved.

IBM Canada8200 Warden AvenueMarkham, ONL6G 1C7Canada

Printed in Canada01/2009

IBM, IBM (logo), DB2 are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States,other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, othercountries, or both.

UNIX is a registered trademark of The Open Group in the UnitedStates, other countries, or both

Windows is a trademark of Microsoft Corporation in the UnitedStates, 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 trademarksof Amazon.com, Inc. or its affiliates in the United States and/or othercountries

Other company, product, or service names may be trademarks orservice marks of others.

References in this publication to IBM products or services do notimply that IBM intends to make them available in all countries inwhich IBM operates. The following paragraph does not apply to theUnited Kingdom or any other country where such provisions areinconsistent 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 warrantiesin certain transactions, therefore, this statement may not apply toyou.

This information could include technical inaccuracies ortypographical errors. Changes are periodically made to theinformation herein; these changes will be incorporated in neweditions of the publication. IBM may make improvements and/orchanges in the product(s) and/or the program(s) described in thispublication at any time without notice.

Information concerning non-IBM products was obtained from thesuppliers of those products, their published announcements or otherpublicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or anyother claims related to non-IBM products. Questions on thecapabilities of non-IBM products should be addressed to thesuppliers of those products.

The information in this publication is provided AS IS withoutwarranty. Such information was obtained from publicly availablesources, is current as of January 2009, and is subject to change.Any performance data included in the paper was obtained in thespecific operating environment and is provided as an illustration.Performance in other operating environments may vary. Morespecific information about the capabilities of products describedshould be obtained from the suppliers of those products.