IBM WebSphere Application Server v8.

0:
Installation Guideline
In this document, we provide a technical overview of the system installation of WebSphere Application
Server (WAS), IBM HTTP server (IHS) and Plugins for WebSphere, based on AIA Thailand Intranet
application (Stand-alone server environment: A single server that is not managed as part of a cell, all IBM
product will be install to same server).

For Intranet application, a Stand-alone server system management is designed as diagram below.

We cover the following topics:

I. IBM Installation Manager (IM) Installation

II. IBM HTTP Server (IHS) Installation
III. Web Server Configuration (httpd.conf)
IV. WebSphere Application Server (WAS) Installation
V. WebSphere Profile Creation
VI. Web Server Plug-ins Installation
VII. WebSphere Application Server Fix Pack Installation
VIII. (Appendix A) Enable WebSphere Administrative Console Security
IX. (Appendix B) Creating Users and Groups
X. (Appendix C) Assigning Groups to Roles

1 Part I: IBM Installation Manager (IM) Installation

Part I: IBM Installation Manager (IM) Installation
Installation Manager comes in the form of an installation kit, which contains a set of Installation
Manager binary and a flat-file repository for the Installation Manager product. The installation kit is only
used for setup and maintenance of the Installation Manager.

You need to run Installation Manager only on those systems on which you install or update product
code. You normally need only one Installation Manager on a computer because one Installation
Manager can track any number of product installations.

To begin an installation, you need to install software prerequisite – Microsoft Visual C++ 2008 Service
Pack 1 before install the IM. And follow instruction step below.

1. Edit VM setting and mount .ISO file to WAS8DISC0-IM.iso

2. Open the software package in ISO file (or download from http://www.microsoft.com/en-
us/download/details.aspx?id=5582) and run vcredist_sp1_x86.exe
3. Click Next, and accept the EULA to continue.

4. Close the Windows after installation was done.

2 Part I: IBM Installation Manager (IM) Installation

5. Click install.exe to launch setup wizard for IBM Installation Manager package, and click Next to
continue.

6. Accept the license agreement and click Next to continue.

7. Change directory for Installation Manager to F:\IBM\Installation Manager\eclipse, click Next to
continue, and follows on screen instruction to install the package.

3 Part I: IBM Installation Manager (IM) Installation

8. Click Restart Installation Manager after installation was completed.

4 Part I: IBM Installation Manager (IM) Installation

Part II: IBM HTTP Server (IHS) Installation
To complete this part, follows instruction step below.

1. Edit VM setting and mount .ISO file to WAS8DISC2-Supplement.iso

2. Browse CD/DVD drive and open launchpad.exe
3. Click IBM HTTP Server on the left navigation, and then click Launch Installation Manager to
install IBM HTTP Server on the right and follows on screen instruction.

4. Verify product package – IBM HTTP Server for WebSphere Application Server version 8.0.0.0 is
selected and status is will be installed, then click Next to continue.

5 Part II: IBM HTTP Server (IHS) Installation

5. Change Shared Resources Directory to F:\IBM\IMShared, and then click Next to continue.

6. Accept default to create a new package group, but change Installation Directory to F:\IBM\IHS,
then click Next to continue.

7. Leave default for features to install, and then click Next to continue.

6 Part II: IBM HTTP Server (IHS) Installation

8. Change a specified user account to Run IBM HTTP Server as a Windows Service, and then click
Next to continue.

9. Review the software package to be installed and click Install to continue.

7 Part II: IBM HTTP Server (IHS) Installation

10. Click Finish once the product was installed complete successfully.

8 Part II: IBM HTTP Server (IHS) Installation

Part III: Web Server Configuration (httpd.conf)
Please refer to table below.

System Name / HTTP Server Configuration File (httpd.conf)

Web Site
iPoS

httpd-asap.conf

DDR

httpdddrth.conf

9 Part III: Web Server Configuration (httpd.conf)

Part IV: WebSphere Application Server (WAS) Installation
To install product using the GUI, complete the following steps to install WebSphere Application Server in
admin mode:

1. Edit VM setting and mount .ISO file to WAS8DISC1-BASE.iso

2. Browse CD/DVD drive and open launchpad.exe
3. Click WebSphere Application Server on the left navigation, and then click Launch Installation
Manager to install WebSphere Application Server on the right and follows on screen
instruction.

4. Verify product package – IBM WebSphere Application Server version 8.0.0.0 is selected and
status is will be installed, then click Next to continue.

10 Part IV: WebSphere Application Server (WAS) Installation

5. Accept default to create a new package group, but change Installation Directory to
F:\IBM\WebSphere\AppServer, then click Next to continue.

11 Part IV: WebSphere Application Server (WAS) Installation

6. Accept default Translations and then click Next to continue.

7. Accept default features to install, but change IBM SDK for Java to 32-bit version (as screenshot).
Then click Next to continue.

12 Part IV: WebSphere Application Server (WAS) Installation

8. Review the software package to be installed and click Install to continue.

9. Click Finish once the product was installed complete successfully.

13 Part IV: WebSphere Application Server (WAS) Installation

Part V: WebSphere Profiles Creation
This part will show you to create an application server profile so that you can make applications
available to the Internet or to an intranet. We will create an application server profile using the Profile
Creation wizard. The Profile Creation wizard is the graphical user interface to the pmt.bat command.

1. Use the Start menu to access the Profile Creation wizard. Click Start  All Programs  IBM
WebSphere  IBM WebSphere Application Server V8.0  Tools  Profile Management Tool.

2. On the Environment Selection page, select Application server and then click Next.

14 Part V: WebSphere Profiles Creation

3. On the Profile Creation Options page, select Advanced profile creation and then click Next.

4. On the Optional Application Deployment page, select Deploy the administrative console only
and then click Next.

5. On the Profile Name and Location Page:

a. Type a Profile name (We will use the profile name that reflect to the project name, and
easy for everyone can understand. Example: The profile name for application server of
iPoS project is iPOSAppSrv or DDRInt project is DDRAppSrv) and change Profile directory
to F:\IBM\WebSphere\AppServer\profiles\<Profile name>.
b. Depend on design for each application server; you can select option for Server runtime
performance tuning setting – Standard, Peak and Development.
c. Click Next.

15 Part V: WebSphere Profiles Creation

6. On the Node and Host names page, follow the instructions to enter Node name, Server name
and Host name
a. Use default for Node name.
b. Type Server name (We still adhere to the original concept same as profile naming, which
reflect to the project name and easy to understand. Example: The server name for
application server of iPoS project is iPOSAppSrv or DDRInt project is DDRAppSrv)
c. Use default for Host name.
d. Click Next.

16 Part V: WebSphere Profiles Creation

7. To enable security, select Enable administrative security on the profile. Enter the user ID and
password in the corresponding field and then click Next. (See Appendix A, if security not enable)

8. On the Security Certificate (Part 1) page, select Create a new default personal certificate and
select Create a new root signing certificate and then click Next.
9. On the Security Certificate (Part 2) page, modify the certificate values (if any) or accept the
default values.

17 Part V: WebSphere Profiles Creation

10. On the Port Values Assignment page, click Recommended port values. The tool returns values
for the ports that it does not detect are in use, or change it (if any). Click Next.

11. On the Windows Service Definition page, specified user account to Run the application server
process as a Windows service, and then click Next.

12. Leave default, no change. Click Next on the Web Server Definition page.

18 Part V: WebSphere Profiles Creation

13. Review the information about the Profile Creation Summary page and then click Create.
14. When the profile creation process ends, click Finish.
15. After process was done, use the First steps console to run and installation verification test.

19 Part V: WebSphere Profiles Creation

16. Have a look on the First steps output to see which one have an error, warning or something like
that and see message said that Server <ApplicationServer> open for e-business; process id is xxxx

20 Part V: WebSphere Profiles Creation

Part VI: Web Server Plug-ins Installation
To complete this part, follows instruction step below.

1. Edit VM setting and mount .ISO file to WAS8DISC2-Supplement.iso

2. Browse CD/DVD drive and open launchpad.exe
3. Click Web Server Plug-ins on the left navigation, and then click Launch Installation Manager to
install Web Server Plug-ins on the right and follows on screen instruction.

4. Verify product package – Web Server Plug-ins for IBM WebSphere Application Server version
8.0.0.0 is selected and status is will be installed, then click Next to continue.

21 Part VI: Web Server Plug-ins Installation

5. Accept default to create a new package group, but change Installation Directory to
F:\IBM\WebSphere\Plugins, then click Next to continue.

6. Accept default features to install, but change Runtime Environment for Java to 32-bit version (as
screenshot). Then click Next to continue.

7. Review the software package to be installed and click Install to continue.

22 Part VI: Web Server Plug-ins Installation

8. Click Finish once the product was installed complete successfully.

23 Part VI: Web Server Plug-ins Installation

Part VII: WebSphere Application Server Fix Pack Installation
To complete this part, follows instruction step below.

1. Edit VM setting and mount .ISO file to WAS8DISC3-FP5.iso

2. Run IBM Installation Manager with GUI. Click Start  All Programs  IBM Installation Manager
 IBM Installation Manager
3. From menu File, click Preferences…

4. Click Add Repository… and browse CD/DVD drive to open repository.config for WAS, IHS and
Plug-Ins (as screenshot).

5. Select Update all and click Next to continue.

24 Part VII: WebSphere Application Server Fix Pack Installation

6. Accept the license agreement and then click Next to continue.
7. Verify features to be installed the fix pack, and then click Update to continue.

8. Click Finish once the products were installed complete successfully.

25 Part VII: WebSphere Application Server Fix Pack Installation

9. Verify product components that installed on the server.
a. IBM HTTP Server, run command apache.exe -version at the IHS binary installed
directory.

b. WebSphere Application Server, run command versionInfo.bat from the Application

Server binary installed directory.

c. Web Server Plug-ins for WebSphere Application Server, run command versionInfo.bat
from the Plug-ins binary installed directory.

26 Part VII: WebSphere Application Server Fix Pack Installation

 d. Installation Manager, open C:\ProgramData\IBM\Installation Manager\installed.xml

27 Part VII: WebSphere Application Server Fix Pack Installation

Appendix A: Enable WebSphere Administrative Console Security
By enabling security, you protect your server from unauthorized users and are then able to provide
application isolation and requirements for authenticating application users. Follows step below to
enable security on the WebSphere Administrative Console.

1. Start the WebSphere Application Server administrative console. If security is currently disabled,
you are prompt to input the User ID.

2. Navigate to the Security section, click Global security.

28 Appendix A: Enable WebSphere Administrative Console Security

3. Use the Security Configuration Wizard to enable administrative security.
a. Click Security Configuration Wizard.
b. Step 1: Specify extent of protection; leave the screen options set to their default –
Enable application security and Use Java 2 security to restrict access to local resources.

c. Step 2: Select user repository – Federated repositories.

29 Appendix A: Enable WebSphere Administrative Console Security

 d. Step 3: Configure federated repository, enter the Primary administrative user name
and password of a user with administrator privileges.

e. Step 4: Summary, verify list of value that are selected during wizard.

f. Click Finish and Save configuration.

4. Restart WebSphere service.

30 Appendix A: Enable WebSphere Administrative Console Security

Appendix B: Creating Users and Groups
If administrative security is enabled, each time you log in to the administrative console, you must
authenticate with the user ID that was identified as having an administrative role. You can add
additional administrative users and assign authorization levels from the administrative console by
follows steps below.

1. Login to the WebSphere Application Server administrative console with a valid administrator
user ID and password or user which created in the Appendix A.

2. Navigate to Users and Groups  Manage Groups. To create a new group, click Create…

31 Appendix B: Creating Users and Groups

3. Type group name and description (if any) in the require field (*). Example: Enter _atdc_deployer
for group name and ATDC Role-based group: Deployer for description.

4. Navigate to Users and Groups  Manage Users. To create a new user, click Create…

32 Appendix B: Creating Users and Groups

5. Fill in user information (as table below) in the require field (*), and then specify Group
Membership (that create completed in step 2-4).

UAT User

User ID First Name Last Name Role-based

MLBR001 Noppadol Prathumthong Deployer
MLBR002 Manoch Romlee Deployer

Production User:

User ID First Name Last Name Role-based

BPCSA10 Tanayos Ngamcharatsiwichai Deployer
BPCSA13 Thongchai Sujaritviriyakhun Deployer
BPCSA41 Komsan Kupptithumkul Deployer
BPCSA49 Pattarachai Vanichtanachai Deployer
BPCSA51 Apichat Boonserth Deployer
BPCSA53 Chatchai Rattanaviboon Deployer
BPCSA54 Phaiwan Mala Deployer

33 Appendix B: Creating Users and Groups

6. Click Search to find available group, select a group, and then click Add to mapped user with
group, and then click Close to continue.

7. Click Create button to finish.

8. To verify user and group.
a. Navigate to Users and Groups  Manage Groups.
b. Click at group to view group properties.
c. Click tab Members.
d. Verify the appropriate user has been added into group.

34 Appendix B: Creating Users and Groups

Appendix C: Assigning Groups to Roles
Administrative roles are defined to provide degrees of authority that are needed to perform certain
administrative functions from either the Web-based administrative console or the system management
scripting interface. The authorization policy is only enforced when administrative security is enabled.
More information describes the administrative roles. Follows step below to assign group with a role.

1. Login to the WebSphere Application Server administrative console with a valid administrator
user ID and password or user which created in the Appendix A.

2. Navigate to Users and Groups  Administrative group roles. Click Add…

3. Use this page to add administrative roles to groups. Assigning administrative roles to groups
enables them to administer application servers through the administrative console. Follows
instruction below.
a. Get the appropriate Role(s) as Deployer.

35 Appendix C: Assigning Groups to Roles

 b. Select an appropriate group by use Search to find all available groups.
c. Click Add to mapped group to role.
d. Click OK.
e. Click Save local configuration to the master configuration.

4. Verify appropriate group is mapped to proper role.

# # #

36 Appendix C: Assigning Groups to Roles