WIXLIB

IBM Softwareb.Configure Tomcat to serve applications on HTTP and HTPPS default ports:We're doing this because.We have decided that our public URI for CLMdeployment is going to be clm.admin.ws. We want it tobe served with no reference to ports on the server tomake user access easier. This will also allow ourinstallation to scale in the future and leverge middlewarelike Web Server or DNS virtual names.You will see how this is done in upcoming labs of thisworkshop.i.Open the server configuration nf\server.xml for editing.ii.Look for the string '9443'a.iii.Change the occurrences in non-commented nodes of that port andredirectPort attributes value to 443Perform another search looking for the string '9080'a.Change the occurrences in non-commented nodes of that port attributevalue to 80InformationJust the Connector nodes for HTTP and HTTPS are required tobe changed for CLM. However, you don't want redirections to aport you don't want to use in your deployment and which maybe in use by other services.The resulting nodes for HTTP and HTTPS will look like the following:. Connector port "80" protocol "HTTP/1.1"connectionTimeout "20000"redirectPort "443" / .CLM 2012 Administration WorkshopPage 10

IBM Software Connector port "443"connectionTimeout "20000"maxHttpHeaderSize "8192"maxThreads "150"minSpareThreads "25"enableLookups "false"disableUploadTimeout "true"acceptCount "100"scheme "https"secure "true"clientAuth "false"keystoreFile "ibm-team-ssl.keystore"keystorePass "ibm-team"protocol "HTTP/1.1"SSLEnabled "true"sslProtocol " {jazz.connector.sslProtocol}"algorithm " {jazz.connector.algorithm}"URIEncoding "UTF-8" / iv.Save your changes and exit.6.Start the CLM applications by double-clicking tup.7.Set up the CLM applications.a.Open a browser and run setup by navigating to https://clm.admin.ws/jts/setup. Ignoreany security warnings and add a security exception if asked.b.Login to JTS with the login/password ADMIN/ADMIN.c.Select Express Setup, then Next.Errors During SetupIf you receive errors during setup and need to continue,you can restart setup at any time. However, you willprobably be forced to run Custom Setup.If you run Custom Setup, just accept all the defaults andselect Next on each screen. Some screens will requireyou to select an obvious button, such as RegisterApplications or Finalize Application Setup. In any case,each screen has a green status message that willappear indicating that the screen is complete. When yousee this message you can select Next.d.In Configure Public URI, make sure the Public URI Root is https://clm.admin.ws/jts.CLM 2012 Administration WorkshopPage 11

IBM SoftwareFully Qualified Domain NameAlways use fully qualified domain names when setting upCLM applications. This can save you significant timewhen moving or expanding applications later. In yourcase, you simply added an FQDN to your etc/hosts filethat you'll use during setup. The utility of this will becomeclearer in later labs.e.Select I understand that once the Public URI is set, it cannot be modified, thenselect Next.f.On the Create User page, create the admin user, and then select Next:i.User ID: adminwsii.Name: adminwsiii.Password: adminwsiv.Email: admin@clmadmin.wsg.Select Next when Express Setup is complete.h.Assign Licenses:No Licenses AvailableIf the proper licenses are not available, you will need toinstall them. You can download CLM licenses for theproper version of the product from the RTC downloadpages.i.8.i.Under Rational Team Concert, next to Rational Team Concert – Developer, selectActivate Trial.ii.Under Rational Requirements Composer, next to Rational RequirementsComposer – Analyst, select Activate Trial.iii.Under Rational Quality Manager, next to Rational Quality Manager – QualityProfessional, select Activate Trial.Select Finish. The Server Administration screen will appear.Create the MTM project.a.On the Server Administration screen, scroll down to the section Manage LifecycleProjects.b.Select Try out the Money That Matters sample.CLM 2012 Administration WorkshopPage 12

IBM Softwarec.Select Create.d.Confirm that you understand the warning about deploying the sample product applicationto a production environment, then select Create.e.Add CALs to usersf.9.i.Select the Members link near the top of the window.ii.Make sure that Money that Matters Sample is the selected project. You'll see thelist of users assigned to the project.iii.Select the Build user and give that user a Build System license. Select Save.Navigate back to the previous window.iv.Assign Analyst, Developer, and Quality Professional licenses to Al, Bob, Deb, andTanuj. Select Save after selecting the license for each user.v.You may assign license to other users as well, but the users listed above are theones we'll use as examples in this workshop.Quality Check: Assure that the MTM sample has been created successfully.i.After the creation phase ends, select arrow next to the Home button, and selectJKE Banking (Change Management). Assure you can see the work items.ii.Select the Home button, and select JKE Banking (Quality Management). Assureyou can see the testing tasks and event log.iii.Select the Home button, and select JKE Banking (Requirements). Assure you cansee the requirements and tracing.Shut down the server by .shutdown.bat.CLM 2012 Administration WorkshopPage 13

IBM Software1.4Install WebSphere Application Server Network DeploymentInstalling WAS ND instead of standard WASThe main features of WAS ND over other WAS optionsare:–Clustering–High Availability–Edge Components–Dynamic Scalability–Advanced centralized management features fordistributed configurationsWAS ND is necessary in this workshop for the clusteringyou'll do in later labs. In addition, we take advantage ofthe centralized management features of the deploymentmanager to emulate some distributed scenarios also inlater labs.If you don't use clustering in your environment you wouldnormally install the version of WAS that is available toyou through purchasing CLM and take advantage ofsimpler configuration and management.Profile setup in standard WAS is similar, but simpler,than the process described in this lab. But the processyou follow in the lab allows you to skip migrating CLMinto WAS, then moving it into WAS ND. In this workshop,we will migrate directly to WAS ND to save time.1.Navigate to C:/AdminWS/Downloads and execute the file you downloaded for installing WASND. For Windows platform it will be typically called IBMIM win32.exe.2.If prompted, enter the ibm.com developerWorks username and password you used to downloadthe software.3.In the first screen, Make sure Installation Manager version 1.5.2 (or higher) and IBM WAS NDTrial 8.0.0.3 are both selected. Select Next.Upgrading Installation Manager (IM)If you have IM 1.5.2 or higher already installed, you willonly see the option for the WAS ND trial.4.Select all the recommended packages and fixes, and select Next.CLM 2012 Administration WorkshopPage 14

IBM SoftwareValidation error?You may get an error telling you that a fix cannot beinstalled in your system. This will happen if the defaultpackages selected by Installation Manager includedpackages for other platforms (like i5OSPPC).You just have to select Back, uncheck those packagesand continue with the installation.5.If you accept the terms of the license agreement, select Next.6.Answer the survey questions and select Next.7.Change the WAS ND installation directory to C:\AdminWS\IBM\WebSphere\AppServer. SelectNext.8.Select any additional languages you want, then select Next.9.Make sure all the features are selected EXCEPT:a.Sample applicationsb.IBM 32-bit SDK for Java, Version 610.Select Next.11.Review the summary information, and if everything is correct, select Install.12.In the final window displayed after installation, select None, then Finish. You will create a profilelater in this lab.CLM 2012 Administration WorkshopPage 15

IBM Software1.5Install IBM HTTP Server (IHS)1.Start IBM Installation Manager from the Start menu.2.Configure the repository for installing IBM HTTP Server:a.Select File Preferencesb.Select Repositories and then Add Repository.c.Write SIHSILAN as the repositoryand click OK. You may be prompted to enter your ibm.com developerWorks credentials.d.Select OK to exit the Preferences wizard.3.Select Install.4.Enter user name and password for developerWorks if asked.5.Select IBM HTTP Server for WAS and Web Server Plug-ins for WAS. Select Next.Validation IssuesIf you receive a Validation Issues error messageindicating your installation requires Microsoft Visual C 2008 Redistributable Package, you can download thepackages aspx?id x?displaylang en&id 15336And restart Installation Manager6.If you accept the license terms, select Next.7.Answer the questions to the survey and select Next.8.Change the directories for the install packages as indicated below, then select Next.9.a.IBM HTTP Server Installation Directory: C:\AdminWS\IBM\HTTPServerb.Web Server Plug-ins installation directory: C:\AdminWS\IBM\WebSphere\PluginsMake sure all packages are selected EXCEPT those listed below, then select Next:a.IBM 32-bit Runtime Environment for Java, Version 6CLM 2012 Administration WorkshopPage 16

IBM Software10.Set the following options for Web Server Configuration, then select Next:a.HTTP Port: 80 (default)b.Do NOT run IBM HTTP Server as a Windows service11.Verify the packages, then select Install.12.Select Finish when the installation is complete.13.Close the Installation Manager.14.Verify the IBM HTTP Server is installed correctly.a.Execute httpd in C:\AdminWS\IBM\HTTPServer\binb.In a browser, navigate to http://clm.admin.ws/. You should see the IBM HTTP ServerVersion 8.0 splash screen.c.Close the browser and the httpd command window.CLM 2012 Administration WorkshopPage 17

IBM Software1.6Setup WAS NDMigrating from Tomcat to WASIn a later lab, you will migrate your CLM applicationsfrom Tomcat to the WAS profile that you are creatinghere.1.Start the Profile Management Tool from the Start menu.2.Select Create in the WebSphere Customization Toolbox.3.Select Cell, then select Next.About the Cell ProfileA profile in WebSphere Application Server tailors theexecution of the product binaries to certain runtimedefinition.Because we are working with WAS ND, we are creatingtwo profiles:–The deployment manager profile defines adeployment manager in a distributed serverenvironment. The deployment manager is thecentral administration point of a cell andprovides, among other things, an administrativeconsole to administer the servers it managesand the concept of a master configurationrepository for them.–The application server profile (“CLMAppSrv01”)defines an application server under control of theDeployment Manager.This combination of a deployment manager profile andan application server profile is known as a Cell profile inWAS.4.Select Advanced profile creation, then select Next.5.Make sure both options are selected, then select Next.6.a.Deploy the administrative console: checkb.Deploy the default application: checkSet the profile names and locations, then select Next.a.Deployment manager profile name: CLMDMgr01b.Application server profile name: CLMAppSrv01CLM 2012 Administration WorkshopPage 18

IBM Softwarec.7.Leave the Profile directory set to the default.Set the Node, Host, and Cell Names, then select Next.a.Deployment manager node name: CLMCellMgr01b.Application server node name: CLMNode01c.Host name: clm.admin.wsd.Cell name: CLMCell01Some more WAS conceptsThe configuration we are performing with WAS NDcreates the following elements for us:––8.9.10.A cell (“CLMCellMgr01”): a cell is a grouping ofnodes into a single administrative domain. Thiscell can consist of multiple nodes, which are alladministered from a single point, the deploymentmanager.A node for each profile: a node is anadministrative grouping of application servers forconfiguration and operational management.Make sure Enable administrative security is selected and the user name and password areset. Then Next.a.Username: wasadminb.Password: wasadminOn Secuirty Certificate (Part 1), accept the defaults and select Next:a.Create a new default personal certificateb.Create a new root signing certificatesOn Security Certificate (Part 2), keep all the defaults and select NextKeystore PasswordNote that the default keystore password is WasAS.11.Accept all the default port values in Port Values Assignment Part 1, and then Part 2. Note thatsince this is the first node you

the download. If you agree to the license statement, select I Confirm. _c. Select the Installation Manager version for your platform and click Download Now. _6. Download DB2 Express-C (this lab was tested with version 10.1). _a. Navigate to the DB2 Express-C download page Prompted with a newer version of DB2?