IBM. IBM WebSphere Application Server v8.0. & IBM WebSphere MQ 7. Workshop. Day 1. Lab Exercises. ISV & Developer Relations

Size: px

Start display at page:

Download "IBM. IBM WebSphere Application Server v8.0. & IBM WebSphere MQ 7. Workshop. Day 1. Lab Exercises. ISV & Developer Relations"

Alvin Page
5 years ago
Views:

1 IBM IBM WebSphere Application Server v8.0 & IBM WebSphere MQ 7 Workshop Alger, du 13 au 14 décembre 2011 Day 1 Lab Exercises

2 Contents LABS INTRODUCTION... 3 LAB 1 WEBSPHERE APPLICATION SERVER BASIC INSTALLATION PREPARE THE ENVIRONMENT INSTALL WEBSPHERE APPLICATION SERVER CREATE A WEBSPHERE APPLICATION SERVER PROFILE INSTALL IBM HTTP SERVER AND WEBSPHERE HTTP SERVER PLUGINS FIRST START LAB 2 CONFIGURE WEBSPHERE APPLICATION SERVER CONFIGURE THE SERVER TO USE DB2 WITHOUT SECURITY CONFIGURE SSL TO DATABASE VIA JDBC FOR USE WITH WAS CONFIGURE IBM HTTP SERVER FOR USE WITH WAS CONFIGURE WEBSPHERE APPLICATION SERVER TO USE AN LDAP USE SSL AND LDAP ON YOUR APPLICATION LAB 3 CREATE A CELL AND FEDERATE THE UNMANAGED NODE CREATE THE DEPLOYMENT MANAGER TRANSFORM THE APPLICATION SERVER INTO A COMPLEX TOPOLOGY NEXT STEPS COMMON TASKS... 75

3 Labs Introduction The objective of this lab is to provide you with an understanding of the basic WebSphere Application Server and WebSphere Application Server Network Deployment infrastructure. Within the constraints of the machine image available for the exercise you ll configure a typical WAS environment comprised of an HTTP server, WebSphere Application Server, DB2 database server and LDAP server for application use. You ll then add a WAS-ND Deployment Manager and federate the application server environment into WAS-ND to adding scalability, failover, and centralized management to your environment. This lab is provided AS-IS, with no formal IBM support. Some instructions in this lab may be Linux operating-system specific. If you plan on running the lab on an operating-system other than Linux, you will need to execute the appropriate commands, and use appropriate files (.sh vs..bat) for your operating system. The directory locations are specified in the lab instructions using symbolic references, as follows: Reference variable Windows location Linux or UNIX locations <WAS_HOME> C:\IBM\WebSphere\AppServer /usr/websphere/appserver /opt/websphere/appserver <PROFILE_HOME > C:\IBM\WebSphere\AppServer\profiles\AppSrv01 /usr/websphere/appserver/profiles/appsr v01 /opt/websphere/appserver/profiles/appsr v01 <RAD_HOME> C:\Program Files\IBM\SDP /opt/ibm/sdp <LAB_FILES> C:\Labfiles80 /tmp/labfiles80 <TEMP> C:\temp /tmp Note for Windows users: When directory locations are passed as parameters to a Java program such as EJBdeploy or wsadmin, it is necessary to replace the backslashes with forward slashes to follow the Java convention. For example, C:\Labfiles80\ would be replaced by C:/Labfiles80/ WebSphere Application Server v8.0 Page 3

4 At the end of this lab you should be able to Install WebSphere Application Server using IBM Installation Manager and configure WebSphere Application Server for a departmental deployment on a single server Configure a WebSphere Application Server Network Deployment cluster for a departmental deployment on a single server Configure WAS and WAS ND to use DB2 for application data Configure a Federated Repository for WAS and WAS-ND to use an LDAP server for user authentication. Page 4 WebSphere Application Server v8.0

5 WebSphere Application Server v8.0 Page 5

Lab 1 WebSphere Application Server basic installation 1.1 Prepare the environment 1. Start the Virtual Machine image a. Log in using root with the password password 2.

6 Lab 1 WebSphere Application Server basic installation 1.1 Prepare the environment 1. Start the Virtual Machine image a. Log in using root with the password password 2. Open a terminal window and type mount /dev/sdb /repository 3. IBM Installation Manager (IIM) is already installed on the image used for this exercise, which meets the minimum IIM version requirement for WAS V8 of IIM Note If are running an version prior to IIM the instructions for updating IM to a later release are available from a. Launch IBM Installation Manager as shown below Page 6 WebSphere Application Server v8.0

7 b. Click File -> Preferences for the IBM Installation Manager Preferences as shown below c. Click Add Repository WebSphere Application Server v8.0 Page 7

d. Enter /repository/was8nd/ as shown below and click OK

installation and updates as shown below (since the Red

want to attempt to connect to the on-line IBM service

8 d. Enter /repository/was8nd/ as shown below and click OK e. Unselect Search service repositories during installation and updates as shown below (since the Red Hat guest doesn t have an internet connection we don t want to attempt to connect to the on-line IBM service repositories), then click Apply. Page 8 WebSphere Application Server v8.0

9 f. Click OK as shown below. 4. Check the version of WebSphere Application Server available a. Click Install from the Installation Manager b. Notice Version WebSphere Application Server v8.0 Page 9

10 c. Click Cancel d. Click File -> Preferences for the IBM Installation Manager Preferences as shown below e. Click Add Repository Page 10 WebSphere Application Server v8.0

11 f. Enter /repository/wasfp/ as shown below and click OK g. Click OK as shown below. WebSphere Application Server v8.0 Page 11

12 1.2 Install WebSphere Application Server 1. Install WebSphere Application Server binaries a. Click Install from the Installation Manager Page 12 WebSphere Application Server v8.0

b. Click Show All versions. You ll notice that the ifix is now listed for install in addition to WAS V8.0.0.0 c.

13 b. Click Show All versions. You ll notice that the ifix is now listed for install in addition to WAS V c. Select Version d. Click Next e. Select Accept the License and Click Next WebSphere Application Server v8.0 Page 13

14 f. Install WebSphere Application Server to /opt/ibm/websphere/appserver as shown and click Next g. Select English as the language and click Next Page 14 WebSphere Application Server v8.0

Once the install has completed you should see the dialog below.

15 h. Unselect Stand-alone thin clients.. as show below and click Next i. Review the install package list j. Once the install has completed you should see the dialog below. Select None (Do Not Start the Profile Management Tool) and Click Finish - Exit the Installation Manager at this point WebSphere Application Server v8.0 Page 15

16 k. Exit the Installation Manager Note: You installed both WAS and an ifix, demonstrating a one pass install. 1.3 Create a WebSphere Application Server profile 1. Launch the Profile Management Tool a. In a terminal window change directories to /opt/ibm/websphere/appserver/bin/profilemanagement using the command Page 16 WebSphere Application Server v8.0

17 cd /opt/ibm/websphere/appserver/bin/profilemanagement as shown below b. Launch the WebSphere Customization Toolkit (formerly the Profile Management Tool ) using the command./pmt.sh as shown below 2. Create a WebSphere Application Server Profile, installing the adminconsole and sample application, configuring administrative security with the user wasadmin and password wasadmin. a. Select Create to start the profile creation process WebSphere Application Server v8.0 Page 17

18 Note: Even though you launched the Profile Management Tool with the command pmt.sh you ll notice that the WebSphere Customization Toollbox launched. A subset of this new toolbox is installed with WAS which includes the Profile Management Tool and the Configuration Migration Tool b. Highlight Application Server and click Next as shown below. c. Select Advanced Profile Creation as shown below. Page 18 WebSphere Application Server v8.0

d. Continue through the panels accepting all the defaults by clicking on Next until you reach the Administrative Security panel, then specify wasadmin for the user and wasadmin for the password as

19 d. Continue through the panels accepting all the defaults by clicking on Next until you reach the Administrative Security panel, then specify wasadmin for the user and wasadmin for the password as shown below. e. Again continue though all the panels accepting all the defaults by clicking Next until you reach the panel shown below. Create the profile by clicking Create WebSphere Application Server v8.0 Page 19

20 f. Unselect the First Steps dialog, click Finish as shown below Page 20 WebSphere Application Server v8.0

Launch the Installation Manager and again select Preferences Install as you did previously b.

21 g. Exit the WCT (WebSphere Customization Toolbox) by clicking Exit as shown below 1.4 Install IBM HTTP Server and WebSphere HTTP Server plugins 1. Install IBM HTTP Server (IHS) a. Launch the Installation Manager and again select Preferences Install as you did previously b. Add "/repository/was WCT/" as a new repository. Click on OK and then on Install c. Choose IBM HTTP Server, Web Server Plug-ins and WebSphere Customization Toolbox as shown below and click Next WebSphere Application Server v8.0 Page 21

22 d. Accept the license agreements and click Next e. Accept the default install location port assignment and click Next f. Click install g. Once the install completes as shown below, select None as indicated and click Finish h. Exit the Installation Manager. 2. Configure the HTTP Server Plugin a. As shown below change directories to /opt/ibm/websphere/toolbox/wct/ the enter./wct.sh Page 22 WebSphere Application Server v8.0

23 b. Specify Web Server Plug-ins Configuration Tool and Click Launch Selected Tool as shown below c. Click on Add... d. Enter webserver1 and /opt/ibm/websphere/plugins as shown below and click Finish WebSphere Application Server v8.0 Page 23

Create an userid ihsadmin with a password of ihsadmin as shown and click Next i.

24 e. Click Create as shown below f. Select IBM HTTP Server V8 and click Next g. Enter /opt/ibm/httpserver/conf/httpd.conf and click Next h. Create an userid ihsadmin with a password of ihsadmin as shown and click Next i. Enter ihsrun and ihsgrp as shown and select Create a new system user ID., as shown below then click Next Page 24 WebSphere Application Server v8.0

25 j. Specify webserver1 for the web server name and click Next k. Check local and enter /opt/ibm/websphere/appserver then click Next l. Select the AppSrv01 profile and click Next WebSphere Application Server v8.0 Page 25

26 m. Click Configure n. Exit the WCT when completed 1.5 First start 1. Start the server. a. Open a terminal window and change to the directory /opt/ibm/websphere/appserver/profiles/appsrv01/bin b. Start the server with the command./startserver.sh server1 as shown below c. Wait until you see the message Page 26 WebSphere Application Server v8.0

27 ADMU3000I: Server server1 open for e-business; process id is xxx 2. Access the configuration console a. Open a browser on your host machine b. enter the URL Note: If you receive a warning about the SSL certificate being presented click Continue to the website to accept the certificate. This occurs because you are using a self-signed certificate from WAS for which a certificate does not already exist in the browser The warning below is from Internet Explorer WebSphere Application Server v8.0 Page 27

28 The warning from Firefox is shown below c. Since WAS administrative security is enabled this will redirect to Enter wasadmin for user ID and wasadmin for the password as shown below Page 28 WebSphere Application Server v8.0

29 Note: When you open the browser you will receive one or two security alerts. If prompted to remember passwords, DISABLE this function. Password remembering functions can compromise security, so this function should not be used. WebSphere Application Server v8.0 Page 29

30 Page 30 WebSphere Application Server v8.0

31 Lab 2 Configure WebSphere Application Server 2.1 Configure the server to use DB2 without security 1. Create a JDBC driver a. DB2 is not running as a service, so you will need to start DB2 by opening a terminal window and entering su db2inst1 which will change you from the user root to db2inst1 then enter the command db2start as and wait for the message SQL1063N DB2START processing was successful as shown below. b. Once inside the Websphere Application Server console Navigate to Resources -> JDBC Providers,Change the scope to Node=thinkNode01 then select New WebSphere Application Server v8.0 Page 31

thinknode01 ) d. Configure the classpath to /opt/ibm/db2/v9.

32 c. Click on JDBC Providers to start the dialog to create a DB2 JDBC Provider with the settings shown below (note the resource scope of thinknode01 ) d. Configure the classpath to /opt/ibm/db2/v9.7/java and a native library path of /opt/ibm/db2/v9.7/bin as shown Page 32 WebSphere Application Server v8.0

e. Click Next, Review the Summary Panel, then click Finish, then Save your changes. 2. Create a data source a. Click on the DB2 Universal JDBC Driver Provider (XA) as shown below.

33 e. Click Next, Review the Summary Panel, then click Finish, then Save your changes. 2. Create a data source a. Click on the DB2 Universal JDBC Driver Provider (XA) as shown below. b. Click on Data sources as shown below c. Configure a Data source with following settings 1) DataSource Name WAS V8 Datasource for DB2 WebSphere Application Server v8.0 Page 33

2) JNDI Name jdbc/was97db_ds 3) Database Name WAS97DB 4) Server name think 5) Port 50000 6) the settings shown below, and Save d.

34 2) JNDI Name jdbc/was97db_ds 3) Database Name WAS97DB 4) Server name think 5) Port ) the settings shown below, and Save d. After configuring the Data source you will need to create a JAAS J2C Authentication Alias. Select the data source you just configured, then the JAAS-J2C authentication data by clicking as shown below. Page 34 WebSphere Application Server v8.0

e. Select New and create an alias with the name db2alias, the user ID of db2inst1 and password of password as shown below, then click OK. Then Save the changes. f.

35 e. Select New and create an alias with the name db2alias, the user ID of db2inst1 and password of password as shown below, then click OK. Then Save the changes. f. Navigate to the data source, and change the security settings to use a container-managed authentication alias, using the alias you just created. Select db2alias from the drop-down list as shown in the following screenshot WebSphere Application Server v8.0 Page 35

36 g. Select OK. Save your configuration by clicking Save h. Ensure that you "Test connection" after the data source configuration. This can be done by selecting the configured data source and clicking on "Test connection". A Successful test connection will ensure that the application using the data source is able to securely connect to Database. 3. Change the data source mapping for the DefaultApplication a. Navigate to Applications -> Application Types -> WebSphere Enterprise Applications b. Stop the Default Application Page 36 WebSphere Application Server v8.0

37 c. Click on the application DefaultApplication to drill down into the application settings d. Then click on Map data sources for all 2.x CMP beans as shown below to drill down into the current application settings WebSphere Application Server v8.0 Page 37

Authorization Type 3) Click OK 4) Select the Increment EJB and click Modify Resource Authentication Method 5) Select

38 e. Change the Data Source settings as described below 1) Browse to jdbc/was97db_ds as the target resource JNDI name, and select Apply 2) Select the Increment EJB and click Set Authorization Type, specify Container for the Authorization Type 3) Click OK 4) Select the Increment EJB and click Modify Resource Authentication Method 5) Select Use default method and browse to db2alias as the Authentication data entry 6) Click Apply Page 38 WebSphere Application Server v8.0

Open Firefox with the url http://localhost:9080/hitcount and select Enterprise

39 f. Verify the settings indicated below and click OK g. Save your changes. 4. Check your configuration a. Start the DefaultApplication b. Open Firefox with the url and select Enterprise Bean as the execution method and click on Increment as shown below WebSphere Application Server v8.0 Page 39

40 c. If you have successfully configured the datasource to use DB2 you ll see the value increment as shown below on each reload of the page 2.2 Configure SSL to database via JDBC for use with WAS Whenever there is sensitive data going over a network connection, it is important to secure the communications. In the past, the connections to databases were typically protected by either using isolated network segments or by implementing VPNs. Recent databases now support SSL for their JDBC connections. This means that it has become relatively easy to ensure that this segment of the topology is secured 1. Stop the application server. a. From the terminal window you started the server, execute the following command./stopserver.sh server1 username wasadmin password wasadmin b. Wait until you see the message ADMU4000I: Server server1 stop completed. 2. Create the certificate Page 40 WebSphere Application Server v8.0

Installed with IBM HTTP Server, you can use IBM Key Manager.

41 a. Create folders to store keys. In a terminal, type mkdir /opt/ibm/ssl/ && mkdir /opt/ibm/ssl/db2/ b. Installed with IBM HTTP Server, you can use IBM Key Manager.Open a terminal an type /opt/ibm/httpserver/bin/ikeyman c. From the Key Database File menu, click New d. Enter db2.kdb as File Name and /opt/ibm/ssl/db2/ as Location WebSphere Application Server v8.0 Page 41

Under Create menu, select New Self-SignedCertificate g.

42 e. Enter WebAS for the password fields, tick Stash password to a file and click OK. Note the password WebAS is the default WebSphere password keyrings. f. Under Create menu, select New Self-SignedCertificate g. Enter DB2 in the Key Label field and ISV_IBM in the Common name. Notice this certificate will be valid for one year. Click OK Page 42 WebSphere Application Server v8.0

43 h. Close the IBM Key Management when the requested action has successfully been completed. 3. Prepare DB2 to use the certificate a. In the terminal type cd /opt/ibm/ssl/db2/ and then ls Check files: db2.kdb, db2.rdb, and db2.sth are all present. b. Configure DB2 in order to use SSL instead of unencrypted conversation. We assume DB2 is correctly configured in order to use SSL (the global security kit is installed and paths configured) 1) In a terminal, type su - db2inst1 2) type db2 update dbm cfg using SSL_SVR_KEYDB /opt/ibm/ssl/db2/db2.kdb 3) type db2 update dbm cfg using SSL_SVR_STASH /opt/ibm/ssl/db2/db2.sth 4) type db2 update dbm cfg using SSL_SVCENAME ) type db2set -i db2inst1 DB2COMM=SSL (if you want to restore the usual protocal, switch SSL with TCPIP) 6) type db2stop && db2start 7) You should get If DB2 fails to start, the configuration may not be done correctly. WebSphere Application Server v8.0 Page 43

Check your error, you should now set the communication protocol and import the certificate. c. Click on the data source and modify the port number to 5543 d.

44 4. Prepare Websphere Application Server to use the certificate a. Start WAS cd /opt/ibm/websphere/appserver/profiles/appsrv01/bin./startserver.sh server1 b. In the configuration console, check now the datasource doesn't work anymore by testing it. You get. Check your error, you should now set the communication protocol and import the certificate. c. Click on the data source and modify the port number to 5543 d. Click Apply e. Under Additional Properties, click Custom properties. Page 44 WebSphere Application Server v8.0

45 f. Click New to create a new custom property. g. Enter sslconnection for Name and true for value. Click OK h. Verify the property now exists. i. Now we need to import the certificate. Navigate to Security -> SSL certificate and key management, click on Key stores and certificates on the right. j. Click on NodeDefaultTrustStore and then on Signer certificates on the right k. Click on Retrieve from port WebSphere Application Server v8.0 Page 45

l. Enter localhost as Host and 50443 as Port. Click then Retrieve signer information. WebSphere Application Server will contact the port/host to request the signer.

46 l. Enter localhost as Host and as Port. Click then Retrieve signer information. WebSphere Application Server will contact the port/host to request the signer. Signer information is displayed in the panel. Enter DB2Certificate as Alias. Click on OK m. Saves changes and restart the application server. In a federated topology, you would have to restart the node agent as well. cd /opt/ibm/websphere/appserver/profiles/appsrv01/bin./stopserver.sh server1 username wasadmin password wasadmin./startserver.sh server1 5. Check the configuration a. Test the connection using the administrative console and then using the hitcount application. Page 46 WebSphere Application Server v8.0

b. tcpcump is installed, look on port 50001 and on port 50443 if you see activity using following

47 b. tcpcump is installed, look on port and on port if you see activity using following commands tcpdump -i lo port tcpdump -i lo port WebSphere Application Server v8.0 Page 47

48 2.3 Configure IBM HTTP Server for use with WAS 1. Start IHS a. Start IBM HTTP Server as shown below b. Test that IHS is running by entering as shown below Page 48 WebSphere Application Server v8.0

Now that the webserver is created generate and propagate the plugin configuration file as shown below 1) Select the web server (1), and then click

49 2. Configure WAS a. In the adminconsole navigate to Server Types -> Web Servers b. Note that webserver1 was created using the WebSphere Customization Toolkit earlier. Now that the webserver is created generate and propagate the plugin configuration file as shown below 1) Select the web server (1), and then click Generate Plug-in (2), 2) Select the web server (1), and then click Propagate Plug-in (3). c. Go to Firefox and enter Exercise the application as before selecting Enterprise Java Bean and clicking Increment WebSphere Application Server v8.0 Page 49

50 d. You may also want to invoke and examine the results. You can see that the HTTP server is being used as well as the port (9080) in use in the WebSphere web container among other runtime configuration details. Page 50 WebSphere Application Server v8.0

51 2.4 Configure WebSphere Application Server to use an LDAP Configure WebSphere Application Server to use an LDAP as a user registry. OpenLDAP has been installed and configured with a small user user population on the lab image 1. Create a new repository a. Navigate to Security in the adminconsole and click Global Security as shown below. b. On the Global Security dialog, click Configure as shown below WebSphere Application Server v8.0 Page 51

52 c. Click Add Base Entry to Realm as shown below d. Click Add Repository as shown below, and choose LDAP repository Page 52 WebSphere Application Server v8.0

53 e. Enter LDAP for the Repository Identifier, Custom for the Directory Type and think for the Primary Host Name, and 389 for the port as shown below and click Apply then click on Group Attribute Definition as shown below. Note: Until you click Apply the Group Attribute Definition is not accessible. If you accidentally click OK instead of Apply, you end up on the Manage Repositories panel. To return panel shown below simply drill down into LDAP repository from the Manage Repositories panel f. Enter guid for the Name of the group membership attribute as shown below and click OK, then Save your changes WebSphere Application Server v8.0 Page 53

54 g. Enter o=ldap for Distinguished name of the base entry for the realm and dc=ibm,dc=com for the Distinguished name of the base entry for this repository and click OK as shown below, then Save your changes h. As shown below on the Global Security Panel 1) Click Set as current, 2) Click Apply 3) Select Enable Application Security 4) Click Apply 5) Then Save your changes Page 54 WebSphere Application Server v8.0

55 2. Check your changes a. In order for the changes to be reflected you will need to stop and start the server. 1) Logout from the adminconsole 2) Stop the server from the terminal window you started it in with the command cd /opt/ibm/websphere/appserver/profiles/appsrv01/bin./stopserver.sh server1 username wasadmin password wasadmin 3) Wait until you see the message ADMU4000I: Server server1 stop completed. 4) Start the server from the LINUX shell with the command./startserver.sh server1 WebSphere Application Server v8.0 Page 55

In the Seach for Users dialog click Search as shown below.

56 b. Once the server has started, log back into the adminconsole and navigate to Users and Groups and click Manage Users as shown below c. In the Seach for Users dialog click Search as shown below. You should see the user entries from LDAP as well as for wasadmin in the file based registry. Page 56 WebSphere Application Server v8.0

d. Open Konqueror and enter the URL http://localhost/snoop you should be prompted for a User name and password as shown below, enter jdoe1 for the User

result Firefox has a valid LTPA token (cookie).

57 d. Open Konqueror and enter the URL you should be prompted for a User name and password as shown below, enter jdoe1 for the User name and jdoe1 for the password Note: You need to use Konqueror for the snoop application because Firefox is already open for the adminconsole and as a result Firefox has a valid LTPA token (cookie). Thus if you simply open another explorer instance you will not be prompted to login since the LTPA cookie used to authenticate wasadmin to the adminconsole will be present in the browser, so no authentication prompt will occur WebSphere Application Server v8.0 Page 57

2.5 Use SSL and LDAP on your application 1. Understand why HTTPS is so important. a. Close Konqueror and open a terminal. Type tcpdump -i lo -XX -vvv -a -s 0 port 80 b.

58 2.5 Use SSL and LDAP on your application 1. Understand why HTTPS is so important. a. Close Konqueror and open a terminal. Type tcpdump -i lo -XX -vvv -a -s 0 port 80 b. Open Konqueror and go to c. Enter jdoe1 as username and password and click OK. d. Check the console: you can see the webpage source code! You need to encrypt your communication. 2. Enable Signe sign-on to use SSL a. In the WebSphere Application Console, go to Security -> Global security. Click on Single sign-on b. Tick Require SSL, then click OK and save the change. Page 58 WebSphere Application Server v8.0

3. Map users and role a. From the Webpshere Entreprise applications, click on DefaultApplication. b. Click on Security role to user/group mapping c.

59 3. Map users and role a. From the Webpshere Entreprise applications, click on DefaultApplication. b. Click on Security role to user/group mapping c. In order to ensure everyone has access to the application, select All Role and select None from the Map Special Subjects menu. WebSphere Application Server v8.0 Page 59

60 d. Click OK and save. Click again on Security role to user/group mapping of DefaultApplication. e. Select All Role and click on the Map Users... button f. Search users and add jdoe1 g. Click on OK. Page 60 WebSphere Application Server v8.0

h. Check your get as below result, Click OK and save modifications. i.

Observe the result of the configuration a. Go to https://localhost:9443/snoop.

forever. b. Try to login with jdoe2 as username and password. The authorization failed. c.

61 h. Check your get as below result, Click OK and save modifications. i. Restart the application server and restart konqueror. 4. Observe the result of the configuration a. Go to You will get a warning about the certificate Click on continue and accept the certificate forever. b. Try to login with jdoe2 as username and password. The authorization failed. c. Open a terminal and type tcpdump -i lo -XX -vvv -a -s 0 port 9443 d. Login using jdoe1 username and password. WebSphere Application Server v8.0 Page 61

62 e. Check the network dump, is the web page readable? Congratulations, your application infrastructure is now ready to serve applications through the HTTP server -> HTTP server plug-in -> WebSphere Application Server -> DB2. Before starting the next part of the lab (below) first 1) Log out of the adminconsole 2) Stop WebSphere Application Server by entering./stopserver server1 username wasadmin password wasadmin from the LINUX command window where you started the application server. Once you see the message ADMU4000I: Server server1 stop completed. Page 62 WebSphere Application Server v8.0

63 WebSphere Application Server v8.0 Page 63

64 Lab 3 Create a cell and federate the unmanaged node This lab will assume that an departmental application infrastructure; consisting of an HTTP Server and WebSphere Application Server instance, needs to be deployed and configured to use LDAP, and a DB2 database, needs to be deployed in an environment as depicted below. Since the enterprise is providing a proxy server in the DMZ in order to provide for security we will be configuring the HTTP server to run on the same server as the application server and will thus be able to safely and securely leverage the WebSphere Application Server capability to manage IBM HTTP Server. As is often the case in many enterprises, much of the infrastructure is outside the domain of the application server administration team. While most often the LDAP server and Database server are located on external servers, for the purposes of this lab both will be located on the same server as the application server, though the actual administration of LDAP and DB2 performed by others, while the WAS configuration to use these services will be part of this exercise. Page 64 WebSphere Application Server v8.0

65 3.1 Create the deployment Manager 1. Create the Deployment Manager profile a. Start the graphical Profile Management Tool (PMT) with the command./pmt.sh from a terminal shell in the directory /opt/ibm/websphere/appserver/bin/profilemanagement b. Click Create c. Highlight Management as the Environment Selection as shown below, then click Next d. Select Deployment Manager as shown below, then click Next WebSphere Application Server v8.0 Page 65

66 e. As you did in lab part 1, select Advanced Profile Creation on the next panel, then click Next f. Accept the defaults, clicking Next, until you get to the Administrative Security Panel, then once again enter wasadmin for the user ID and wasadmin for the password. g. Continue to accept the PMT provide defaults until you reach the Port Value Assignment panel shown below, select Default Port Values as shown below (we ll take steps to insure no conflicts exist) Page 66 WebSphere Application Server v8.0

67 h. As before in Lab 1 when configuring the application server do NOT select Run the deployment manager process as a Linux service, and click Next i. Click Create to create the profile, j. Unselect First Steps then click Finish. k. Exit the PMT by selecting File -> Exit in the upper left corner of the PMT 2. Start the Deployment Manager WebSphere Application Server v8.0 Page 67

68 a. Open a LINUX command shell and navigate to /opt/ibm/websphere/appserver/profiles/dmgr01/bin b. Enter the command./startmanager.sh and wait until you see the message ADMU3000I: Server dmgr open for e-business; process id is xxxx 3.2 Transform the application server into a complex topology 1. Federate the Application Server a. Return to the LINUX command shell that you used to start and stop the Application Server (if you closed the shell the directory is /opt/ibm/websphere/appserver/profiles/appsrv01/bin) b. Enter the command./addnode.sh localhost includeapps username wasadmin password wasadmin This tells WAS to add a node by connecting to the deployment manager running on the localhost, to include the existing applications that are deployed on the application server and to use wasadmin as the administrative userid and password. c. Wait for the message ADMU0003I: Node thinknode01 has been successfully federated 2. Configure a WAS-ND Cluster a. Log into the adminconsole using Firefox with the URL Since WAS administrative security is enabled this will redirect to Enter wasadmin for user ID and password as you did before. b. Navigate to Servers -> Clusters and click WebSphere Application Server clusters in the console as shown below. Page 68 WebSphere Application Server v8.0

In order to use our existing server configuration and application we are going to

69 c. Click New to create a new cluster d. Enter MyCluster for a Cluster name as shown below, then click Next e. In order to use our existing server configuration and application we are going to select create the cluster member by converting an existing application server as shown below, then click Next WebSphere Application Server v8.0 Page 69

70 f. Enter server2 as the server name for the next cluster member as shown below and click Add Member. Then enter server3 as a server name and click Add Member. At this point you should have 3 servers in the cluster; server1, server2 and server3. Once you do so, click Next Page 70 WebSphere Application Server v8.0

71 g. Review the settings, then click Finish to create the cluster members h. Now navigate to Servers -> Server Types -> WebSphere Application Servers, select server1 and click delete Note: Server1 is being deleted to remove the port conflicts were mentioned previously during profile creation. Alternatively one could have changed the port number settings for server1, but simply removing the server from our configuration is the quickest means remove the conflicts. i. Save changes 3. Check network alias and test the cluster WebSphere Application Server v8.0 Page 71

a. You can choose to save your changes at this time if you wish, but we have one more

Navigate to Environment -> Virtual Hosts in the console b. Click default_host c.

Check to insure that numbers 9081 and 9444 (for server 2) as shown below exist as well as

72 a. You can choose to save your changes at this time if you wish, but we have one more configuration change to make, this to the virtual host definition. Navigate to Environment -> Virtual Hosts in the console b. Click default_host c. Click Host Aliases. Check to insure that numbers 9081 and 9444 (for server 2) as shown below exist as well as ports 9082 and 9445 (for server3) exist for the host alias list for the default host. Add them if needed (they should already be listed) Click Save if you need to add them Page 72 WebSphere Application Server v8.0

Once the synchronization is complete, you will need to regenerate and propagate the HTTP server plug-in as you did before by navigating to Servers > Web Servers,

73 d. Save your changes if you ve not already done. e. Just to make sure all our changes have been pushed out to the node agent, we re going to save and synchronize as shown below. f. Once the synchronization is complete, you will need to regenerate and propagate the HTTP server plug-in as you did before by navigating to Servers > Web Servers, selecting webserver1 and clicking Generate Plug-in and then once again selecting webserver1 and clicking Propogate Plugin g. You can now start your application server cluster by navigating to: Servers -> Clusters -> WebSphere Application Server Clusters, selecting MyCluster and clicking start. WebSphere Application Server v8.0 Page 73

h. Once the cluster is completed starting as shown below, you can enter http://localhost/snoop in a Firefox browser instance and if you examine it s

You may need to close and to reopen firefox to clear its web cache data.

74 h. Once the cluster is completed starting as shown below, you can enter in a Firefox browser instance and if you examine it s output you ll see that some requests are served from port 9081 (server2) and some from port 9082 (server3). You may need to close and to reopen firefox to clear its web cache data. Note: You may have noticed that you were not prompted to login when you accessed the application, this is because the Global Security settings a standalone WAS instance is not migrated during federation into a WAS- ND cell. Page 74 WebSphere Application Server v8.0

75 Next steps 1- During this lab you regularly used command line containing the WebSphere Application Server username and password. It is a huge lack of security. If you are not convince, type history grep password in a terminal. You may forbid this way of command, so open files soap.client.props and change the default value of com.ibm.soap.loginsource to stdin. 2- Sign in or Register on DeveloperWorks and join the community Main links: cli_installation_appclient_silent.html Common Tasks Below are some common tasks that you may need to perform several times during this lab 4. Starting a WAS (standalone) application server./startserver <servername> e.g from the /opt/ibm/websphere/appserver/profiles/appsrv01/bin directory./startserver.sh server1 5. Stopping a WAS (standalone) application server./stopserver <servername> e.g from the /opt/ibm/websphere/appserver/profiles/appsrv01/bin directory./stopserver.sh server1 6. Starting a WAS-ND Node Agent startnode e.g from the /opt/ibm/websphere/appserver/profiles/appsrv01/bin directory WebSphere Application Server v8.0 Page 75

76 startnode 7. Stopping WAS-ND Node Agent stopnode e.g from the /opt/ibm/websphere/appserver/profiles/appsrv01/bin directory stopnode 8. Starting a WAS-ND Deployment Manager startmanager e.g from the /opt/ibm/websphere/appserver/profiles/dmgr01/bin directory startmanager 9. Starting a WAS-ND Deployment Manager stopmanager e.g from the /opt/ibm/websphere/appserver/profiles/dmgr01/bin directory stopmanager Page 76 WebSphere Application Server v8.0

EVALUATION ONLY. WA2097 WebSphere Application Server 8.5 Administration on Linux. Student Labs. Web Age Solutions Inc.

EVALUATION ONLY. WA2097 WebSphere Application Server 8.5 Administration on Linux. Student Labs. Web Age Solutions Inc. WA2097 WebSphere Application Server 8.5 Administration on Linux Student Labs Web Age Solutions Inc. Copyright 2013 Web Age Solutions Inc. 1 Table of Contents Directory Paths Used in Labs...3 Lab Notes...4