Deployment of SAS Web Applications under IBM Web ... - Ftp Sas

Page | 4Please Note: IBM Webspshere(WAS) is third-party software. If you are downloading and using these third-partysoftware binaries for NON R&D Use, before starting it is very important to contact John Roth’s team : *Dept: JDT(Java Development Technologies) or JDT@wnt.sas.com, and discuss the license limitations on these internal versionsof third-party softwares.5. Windows is a fairly straight forward install without too many prerequisite steps andgotchas but that’s not always the case for the UNIX platforms.Remember to check out those resources outlined in step 3 above. I have done both AIXand Solaris WAS installs and my system administrator had to update our machinesbefore I could perform my WAS install.6. For UNIX, you need to be root when you perform gzip, untar, and the WAS install.7. Unzip the windows archive files or untar the UNIX archives (using gzip -d followed bytar –xvf) for the version you want to use into a temporary directory.On UNIX it will look something like below:8. To install WAS, you can run launchpad.bat / launchpad.sh in the main directory (butyou must have a configured browser to do so) or you can run the ‘install’ thatresides in the “WAS” directory that you unzipped or untarred into. Below are thesteps I followed:• Invoke launchpad.bat on Windows or launchpad.sh on UNIX. For UNIX platforms, ifyou do not have the current directory (“.”) in your PATH, then you will need toenter “./launchpad.sh”.• You will see “IBM WebSphere Application Server Network Deployment” window (Asmentioned you will see below window coming up automatically only if you have aconfigured browser to do so). This window shows you the different products thatyou can install. For now, we are only interested in WAS.Note: Launchpad will not work (especially on UNIX) if your browser is notconfigured correctly. If this is the case, you can configure the browser to runand invoke launchpad again. Or you can invoke the WAS installation wizarddirectly (which does not require a browser) by going down to the “WAS” subdirectoryand executing “install”. But in both the cases you must have yourDISPLAY variable set in your unix client for e.g. SSH with and XServer(like Exceedor X Ming) running.

Page | 6• If problems were found, stop wizard, correct the problems, start wizard again.The most common prerequisite values are, back-level OS, not enough space, UNIXkernel settings, but the results displayed are helpful as to the problemencountered.• If no were problems found, click Next.• If it finds another WAS, it will tell you about it (unique ports can be setlater). Click Next.• Enter directory to install WAS to (or take the default “C:\ProgramFiles\IBM\WebSphere\AppServer” or for UNIX “/usr/IBM/WebSphere/AppServer”) andclick Next.• You will see the “Features Requested” window, and all 3 features are checked.Leave the Core product files checked but uncheck application server samples andJavadocs unless you really want them. The samples add a lot of overhead and youmost likely will not use the Javadocs. Click Next.

Page | 7• You will see the Installation Features Summary for you to review. Click Next.• The installation starts running, be patient, it will take awhile but you will seea progress bar. Go grab a beverage now. The last major component installed is“webui”, you may think you are stuck at about 92%, your not, it’s just a largecomponent.• After the install is complete, you will see the Installation Complete window witha checkbox to launch the profile creation wizard (leave this checked). ClickNext.• The Installation Wizard will end but now you will see the “Welcome to ProfileCreation Wizard” window. Click Next.

Page | 8• The default is to create an Application Server profile, leave this selected asmost people are using and installing a single base application server. If youdecide you want to run in a WAS ND environment, you will run the profile wizard ata later time and choose to create a Deployment Manager profile. Our goal is firstto get a single running application server. Click Next.• It will prompt you for the profile name, the default is AppSrv01. Click Next.• It will prompt you for the profile directory, the default is your installdirectory followed by “\profiles\AppSrv01”, so for Windows it was “C:\ProgramFiles\IBM\WebSphere\AppServer\profiles\AppSrv01”. Click Next.

Page | 9• You will see the node and host name window where the default host is your machineDNS name (D1234.na.sas.com) and the node is machine plus “Node01” (D1234Node01).Click Next.• You will see the Port Value Assignment window. If you do not have another WASinstalled on that machine, you won’t need to be concerned about any conflicts.WAS normally sorts these ports out for you if it is aware of other profiles (in mycase on AIX, it did). If you are going to either run one or the other, youcan also use the same ports. Click Next.• For Windows, you will see the “Windows Service Definition” window. This gives youthe opportunity to start and stop WAS as a service. If so you will need to entera userid, password, and service startup type. Click Next.• You will see the Profile Summary window with your selections. click Next.

Page | 10• Now the Profile Creation wizard creates the actual profile. This will also takeawhile so if are ready for another coffee, feel free to go grab another cup.• You will see the Profile Creation complete window with the Launch First StepsConsole check box. Leave this checked as we want to verify our WAS install andclick Finish. So now a standalone web application server is created under profileAppSrv01.• The Profile Creation wizard window will go away and now you will see the FirstSteps window. Click on “Installation Verification”.

Page | 11• You will see the Installation Verification window with messages showing theprogress of the test. The test will start the server, run some tests, and thengive you the result of the test. All these messages are on this window but youwill have to scroll down to see the ending messages, the scrolling did not happenautomatically for me. In other words, check the scroll bar on the right and whenit shows more, scroll, otherwise you might be waiting for the end of test messagesa long time. The last message you should see is “Installation Verification iscomplete”.• So now the application server is running. Above screen also contains some usefulcommands and information if you want to start the application server from thecommand line tools (putty etc.).• Back on the First Steps window, click on admin console. If your browser isconfigured correctly on that machine, you will see the admin console display inyour browser. I say “if” because on my Windows box this worked fine but on myUNIX boxes, it did not display, nothing happens since the browser was notconfigured. If you do not see the admin console, go to a machine with a workingbrowser and invoke the admin console (http://D1234.na.sas.com:9060/ibm/console/).

Page | 13profile using the “Profile Creation Wizard” and then add your node(s). Then once youadd a node, you can then add other servers into this node. More on this in a latersection.Upgrading the WAS Server to 6.0.2.19The IBM web-site has been referred to update this section accordingly. As of02/01/07, the most current WAS 6 level is 6.0.2.23 BUT we plan on using 6.0.2.19.You can determine the latest WAS level by looking at the recommended updates page athttp://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27004980. This page will alsolist the latest WAS Java SDK cumulative fix for WAS 6.0.2 of which we are going touse the WAS JDK SR6 level.The process below describes the manual service update process for WAS. It takesawhile so please be patient.10. A note about some IBM terminology on what 6.0.2.19 reflects. It means you will haveto first apply the V6.0 refresh pack 2 to bring you to the 6.0.2 level. Then youwill apply V6.0.2 fix pack 19 to bring you to the 6.0.2.19 level. Then you willapply the WAS JDK Cumulative Fix to update the WAS JDK/JRE to the 1.4.2 SR6 level.11. See page http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24009813 for 6.0.2refresh pack details. You will have to click on the tab for the platform you areinterested in. The readme for this refresh pack is at http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27006336. We have this refresh packlocally at \\sashq\root\dept\jdt\IBM_WAS60\refreshpack2.12. See page http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg24014975 for6.0.2.19 fix pack details. You will have to click on the tab for the platform youare interested in. The link to the readme for this fix pack and other details are onthis page. You can download the applicable 6.0.2.19 fix pack for your platform or Ihave these fix packs locally at \\sashq\root\dept\jdt\IBM_WAS60\fixpack19 . Pickthe correct one for your platform; name is 6.0.2-WS-WAS-xxx-FP00000019, where xxx isthe specific platform name.13. See page http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24014326 for the WAS6.0.2 Java SDK 1.4.2 SR6 cumulative fix details. The link to the readme for this fixpack and other details are on this page. You can download the applicable Java SDK1.4.2 SR6 Cumulative Fix for your platform from this page or I have these fix packslocally at \\sashq\root\dept\jdt\IBM_WAS60\WASJDKSR6. Pick the correct one for yourplatform; name is 6.0.2-WS-WASJavaSDK-xxx-FP00000017, where xxx is the specificplatform name.14. Verify that you will have enough space. For a Refresh pack, you will needapproximately 400 MB of free space in the system temporary directory (typically /tmp)and another 400 MB in the file system that hosts the WebSphere Application Serverimage (typically /usr or /opt) on a UNIX-based platform, or approximately 800 MB offree space on the disk drive where you are installing on a Windows platform.15. So go ahead and download both the refresh pack and fix pack for your platform, theyare just archive files you will have to unzip or untar.16. On your machine where WAS is installed, extract the file into your WAS_HOME. Thisstep is very important that you extract it into your WAS_HOME because unlike WAS 5,WAS 6 requires this updateinstaller directory structure be in WAS_HOME. For example,on Windows, you would extract this into "C:\Program Files\IBM\WebSphere\AppServer"(for UNIX “/usr/IBM/WebSphere/AppServer”) which would create the directory structure"C:\Program Files\IBM\WebSphere\AppServer\updateinstaller". If you already have

Page | 14another updateinstaller directory there, delete it, rename it, or move it some placeelse. If you don’t extract to the correct location, you will find out shortly whenyou execute the update command, it will tell you. So to untar the refresh pack fileaixrp602.tar present at /tmp/WAS/refreshpack602 do following:# cd /usr/IBM/WebSphere/AppServer //change to WAS_HOME# mv updateinstaller updateinstallerOLD //rename existing updateinstaller# tar -xvf /tmp/WAS/refreshpack602/aixrp602.tarx License.txt, 34565 bytes, 68 media blocks.x Notices.txt, 47426 bytes, 93 media blocks.x updateinstallerx updateinstaller/libx updateinstaller/maintenancex updateinstaller/maintenance/6.0-WS-WAS-AixPPC32-RP0000002.pak, 344081113 bytes,672034 media blocks....x updateinstaller/frameworkx updateinstaller/docs/readme_updateinstaller.txt, 103676 bytes, 203 media blocks.x updateinstaller/update, 363434 bytes, 710 media blocks.x updateinstaller/version.txt, 175 bytes, 1 media blocks.x updateinstaller/update.jar, 13500636 bytes, 26369 media blocks.# pwd/usr/IBM/WebSphere/AppServer# cd updateinstaller# ls -ltotal 27112drwxr-xr-x 3 root system 4096 Jul 01 2005 docsdrwxr-xr-x 3 root system 4096 Jul 01 2005 frameworkdrwxr-xr-x 2 root system 256 Jul 01 2005 libdrwxr-xr-x 2 root system 256 Jul 01 2005 maintenancedrwxr-xr-x 2 root system 256 Jul 01 2005 responsefiles-rwxr-xr-x 1 root system 363434 Jun 25 2005 update-rw-r--r-- 1 root system 13500636 Jun 25 2005 update.jar-rw-r--r-- 1 root system 175 Jun 25 2005 version.txt# cd maintenance# ls -ltotal 672040-rw-r--r-- 1 root system 344081113 Jul 01 2005 6.0-WS-WAS-AixPPC32-RP0000002.pakSo the above listed file 6.0-WS-WAS-AixPPC32-RP0000002.pak confirms you have theright refresh pack file at right location to apply to raise WAS Base installationfrom 6.0 to 6.0.2.17. You can actually extract into the same “updateinstaller” directory but it adds a fewmore complications. You will have to overwrite existing files because you will wantthe most current update tools. As a matter of fact, fix pack 6.0.2.19 will NOTinstall with the update installer that came with refresh pack 2. You will now havemultiple refresh/fix pack files and will have to indicate which one during the updateprocess. You will also have to delete the existing .../updateinstaller/javadirectory because that gets created from your existing WAS level during the updateprocess (for refesh packs).18. Stop all application server processes, the nodeagent process, the deployment managerprocess, and all server processes, that belong to serviceable features. Features withserver processes include the IBM HTTP Server. Stop all WAS processes. The productmight not continue to run successfully, or without error if you install a Refresh/Fixpack while a WebSphere Application Server-related Java process is running.19. It is recommended and very good practice to run the backupConfig command to back upyour WAS configuration files.

Page | 1520. Go to WAS_HOME/updateinstaller directory, and invoke the update installer graphicalinterface via the "update" executable.oYou will see Welcome window, click Next.oEnter WAS Home directory for UNIX “/usr/IBM/WebSphere/AppServer” (C:\ProgramFiles\IBM\WebSphere\AppServer), click Next.

Page | 16oChoose "Install Maintenance Package", click Next.oIt should then display the refresh pack directory and name to install, clickNext. FYI, this is where if you have multiple refresh/fix packs in thisdirectory, it will want to know which one.oFor refresh packs, you will see a window indicating it will copy your WAS JDK,click Next. This is because refresh packs may update the WAS JDK/JRE. If so,they will copy the current WAS JRE to use into the updateinstaller directorybecause it is going to overwrite the WAS version. A fix pack will not(normally) update the WAS JDK/JRE so it can use the WAS version and not have tocreate a copy.

Page | 17oIt copies the JDK and then asks you to relaunch the wizard, make sure youclick Relaunch, otherwise the refresh pack will not get installed.oOnce again, it will display the refresh pack directory and name to install,click Next.

Page | 18oYou will see a window indicating you will be upgraded with RP6020 and to where,click Next.oThe upgrade will start; it will take awhile, just settle back. Component"webui" is the last one and takes quite awhile itself, it's really not stuck.You will see the process first backup all the WAS components and then update thecomponents so be patient.oThen hopefully you will see " the final window indicating Success: The followingproduct was successfully upgraded", click Finish.

Page | 1921. So after applying refresh pack 2, go to WAS_HOME/bin and enter versionInfo commandand see info, the important part being:NameIBM WebSphere Application Server - NDVersion 6.0.2.0IDND22. You will then follow a similar process as we just did but to apply fix pack 6.0.2.19.In this case, you should not see the JDK/JRE get copied and when the process is done,you should once again run versionInfo again and see the 6.0.2.19 version.o So first thing now is to get the fixpack file in the WAS_HOME\updateinstallerdirectory# cd /usr/IBM/WebSphere/AppServer/# mv updateinstaller updateinstallerRP# tar -xvf /tmp/WAS/fixpack19/AIX-32bit/6.0.2-WS-WAS-AixPPC32-FP00000019.tarx License.txt, 34565 bytes, 68 media blocks.x Notices.txt, 47426 bytes, 93 media blocks.x updateinstallerx updateinstaller/framework/version.xml, 562 bytes, 2 media blocks.x updateinstaller/maintenancex updateinstaller/maintenance/6.0.2-WS-WAS-AixPPC32-FP00000019.pak, 260166234bytes, 508138 media blocks.x updateinstaller/libx updateinstaller/lib/xdplugins.jar, 17775 bytes, 35 media blocks.x updateinstaller/lib/updiplugins.jar, 1567 bytes, 4 media blocks.x updateinstaller/lib/wbiplugins.jar, 3723 bytes, 8 media blocks....x updateinstaller/docs/readme_updateinstaller.txt, 103676 bytes, 203 media blocks.x updateinstaller/docs/readme_updateinstaller.pdf, 396992 bytes, 776 media blocks.x updateinstaller/docs/readme_updateinstaller.html, 94604 bytes, 185 media blocks.# pwd/usr/IBM/WebSphere/AppServer# cd updateinstaller

Page | 20# ls -ltotal 27016drwxr-xr-x 3 root system 4096 Oct 06 2006 docsdrwxr-xr-x 3 root system 4096 Oct 06 2006 frameworkdrwxr-xr-x 2 root system 256 Oct 06 2006 libdrwxr-xr-x 2 root system 256 Apr 25 2007 maintenancedrwxr-xr-x 2 root system 256 Oct 06 2006 responsefiles-rwxr-xr-x 1 root system 363512 Oct 06 2006 update-rw-r--r-- 1 root system 13451593 Oct 06 2006 update.jar-rw-r--r-- 1 root system 175 Oct 06 2006 version.txt# cd maintenance# ls -ltotal 508152-rw-r--r-- 1 root system 260166234 Apr 25 2007 6.0.2-WS-WAS-AixPPC32-FP00000019.pakooSo the above listed file 6.0.2-WS-WAS-AixPPC32-FP00000019.pak confirms you havethe right Fix pack file at right location to apply to raise your WAS Baseinstallation which is now 6.0.2 to 6.0.2.19.Stop all application server processes, the nodeagent process, the deploymentmanager process, and all server processes, that belong to serviceable features.Features with server processes include the IBM HTTP Server. Stop all WASprocesses. The product might not continue to run successfully, or without errorif you install a Refresh/Fix pack while a WebSphere Application Server-relatedJava process is running.Go to WAS_HOME/updateinstaller directory, and invoke the update installergraphical interface via the "update" executable. You will see Welcome window,click Next.oEnter WAS Home directory for UNIX “/usr/IBM/WebSphere/AppServer” (C:\ProgramFiles\IBM\WebSphere\AppServer), click Next.

Page | 21oChoose "Install Maintenance Package", click Next.oIt should then display the fix pack directory and name to install, click Next.FYI, this is where if you have multiple refresh/fix packs in this directory (notin this case), it will want to know which one.oYou will see a window indicating you will be upgraded with FP60219 and to where,click Next.oThe upgrade will start; it will take awhile, just settle back.

Page | 22oThen you will see " the final window indicating Success: The following productwas successfully upgraded", click Finish.23. So after applying refresh pack 2, go to WAS_HOME/bin and enter versionInfo commandand see info, the important part being:NameIBM WebSphere Application Server - NDVersion 6.0.2.19IDND24. You will then follow a similar process as we just did in the steps above for point 14but to apply the WAS Java SDK cumulative fix. In this case, ONLY the WAS JDK/JREwill get updated.

Page | 23Welcome Screen. Click Next.Enter WAS_HOME.Select Install maintenance package. Click Next.As there is only one package under WAS_HOME/updateinstaller you get it by defaulthere. Click Next.

Page | 24You will see a message about update to an installed JDK. Click Next.Copying of JDK in progress.Click relaunch.Select Install maintenance package. Click Next.

Page | 25Click Next.Click Next.Click Finish25. You should be all set to start up WAS again at the new WAS 6.0.2.19 version with theWAS Java SDK at the SR6 level. To verify the Java version, go to WAS_HOME/java/binand enter the “Java -version” command. These versions are:1. AIX ca142ifx-200604212. Windows cn142ifx-20061121

Page | 263. Sun 1.4.2_12-b0326. Now you can start your application server which is created with the AppSrv01 profileand this profile AppSrv01 can be found under WAS_HOME\profiles with a folder namedAppSrv01. To start the server (created)associated with this profile:27.#cd /usr/IBM/WebSphere/AppServer/profiles //change to WAS_HOME/profiles#cd AppSrv01//change to profile directory#cd bin//change to bin under profile#./startServer.sh server1//command to start serverADMU0116I: Tool information is being logged in file/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServADMU0128I: Starting tool with the AppSrv01 profileADMU3100I: Reading configuration for server: server1ADMU3200I: Server launched. Waiting for initialization status.ADMU3000I: Server server1 open for e-business; process id is 610528To check if the server is runnig:#ps –ef | grep IBMroot 6105281 0 07:01:12 pts/0 1:15 /usr/IBM/WebSphere/AppServer/java/bin/java -Xbootclasspath/p:/usr/IBM/WebSphere/AppServer/java/jre/lib/ext/ibmorb.jar:/usr/IBM/WebSphere/AppServer/java/jre/lib/ext/ibmext.jar -Dwas.status.socket=45740 -classpath/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/properties:/usr/IBM/WebSphere/AppServer/properties:/usr/IBM/WebSphere/AppServer/lib/bootstrap.jar:/usr/IBM/WebSphere/AppServer/lib/j2ee.jar:/usr/IBM/WebSphere/AppServer/lib/lmproxy.jar:/usr/IBM/WebSphere/AppServer/lib/urlprotocols.jar -Dws.ext.dirs=/usr/IBM/WebSphere/AppServer/java/lib:/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/classes:/usr/IBM/WebSphere/AppServer/classes:/usr/IBM/WebSphere/AppServer/lib:/usr/IBM/WebSphere/AppServer/installedChannels:/usr/IBM/WebSphere/AppServer/lib/ext:/usr/IBM/WebSphere/AppServer/web/help:/usr/IBM/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime -Dderby.system.home=/usr/IBM/WebSphere/AppServer/derby -Dcom.ibm.itp.location=/usr/IBM/WebSphere/AppServer/bin -Djava.util.logging.configureByServer=true -Dibm.websphere.preload.classes=true -Duser.install.root=/usr/IBM/WebSphere/AppServer/profiles/AppSrv01 -Dwas.install.root=/usr/IBM/WebSphere/AppServer -Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager -Ddb2j.system.home=/usr/IBM/WebSphere/AppServer/cloudscape -Dserver.root=/usr/IBM/WebSphere/AppServer/profiles/AppSrv01 -Xms640m -Xmx1840m -Xss256k -Xoss256k -Xpartialcompactgc -Xgcpolicy:optthruput -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.awt.headless=true -Xk15000 -Xloratio0.2 -Xlp -Dsun.rmi.dgc.ackTimeout=1 -Dcom.ibm.websphere.threadpool.clearThreadLocal=TRUE -Djava.security.auth.login.config=/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/properties/wsjaas.conf -Djava.security.policy=/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/properties/server.policy com.ibm.ws.bootstrap.WSLauncher com.ibm.ws.runtime.WsServer/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/config blues07Node01Cell blues07Node01 server1OR#cd /usr/IBM/WebSphere/AppServer/profiles //change to WAS_HOME/profiles#cd firststeps#./firststeps.sh //before this command do set DISPLAY and start XserverThis command will display the following first steps window which you havealready seen in one of steps above:Click on Start the server link. It will open another window where you can seethe status of the starting server:

Page | 27You can close this window.Once the server is started successfully the link ‘Start the Server’ in thefirst steps window above will be changed to ‘Stop the Server’Click Stop the server link whenever you want to stop the server.This window can be closed.

Page | 28Recommended settings to the server28. Setting JVM Arguments• Open the WebSphere Console for your profile using url as below:http://MachineNameOnWhichServerIsRunning:WC_adminhost_Port/ibm/consoleE.g. for me it is http://blues07.unx.sas.com:9060/ibm/console/You should have noted the port Number for Administrative Console (WC_adminhost)from one of the screens that you get during profile creation. If not you can findit in the following file:WAS_HOME/profiles//config/cells//nodes//serverindex.xmlFor me /usr/IBM/WebSphere/AppServer/profiles/AppSrv02/config/cells/blues07Node02Cell/nodes/blues07Node02• Just click on Login as by default the admin Console is not secured.Once you are logged in. Expand the ‘Servers’ on the left-hand side. Click‘Application Servers’ to see your server on the right hand side.• Click on the ‘server1’ link and go to ‘Configuration’ tab.• On the ‘Configuration’ tab, Under ‘Server Infrastructure’, Click on ‘Process Definition’.• On the next page, under ‘Additional Properties’ Click on ‘Java Virtual Machine’

Page | 29• On the next page we have Change Initial Heap Size=256, Maximum Heap Size=256 andGeneric JVM Arguments=… Value to put for Generic JVM Arguments can be found inSAS® 9.1.3 Intelligence Platform Web Application Administration Guide Third Edition available at:http://support.sas.com/documentation/configuration/biwaag.pdfIn this book, Go to ‘Best Practices for Configuring your Middle Tier’and then go to ‘Tuning WebSphere 6.0.2 or 6.1’ on page 66 and under‘Configure the JVM Arguments’ you can find the value for ‘Generic JVMArguments’ for your platform.• After putting the values as indicated Click on Apply• You get the same page refreshed and with a ‘save’ link on top. Click save.

Page | 30• Click Save• You will be back to the page where you made JVM changesApplication servers > server1 > Process Definition > Java Virtual MachineAnd you can see your changes; this indicates your changes are successfully saved.29. Enforce Java 2 SecurityGo to Security – Global Security. Check the check-box for ‘Enforce Java 2Security’. Click Apply. Click Save link on the next page and then ‘Save’ on thenext screen.30. Setting Web Container Properties• Go to Servers – Application Servers – Server1 – Configuration tab – and under‘Container Settings’ expand ‘Web Container Settings’ click ‘Web Container’.

Page | 31• Under’ Additional Properties’ Click on ‘Custom Properties’• Click new button• In the Name field type prependSlashToResource and in the Value field type trueand click Apply.• You get the same page with ‘save’ link on top. Click ‘save’ link.• Click ‘Save’ button.

Page | 32• You can see your Custom property prependSlashToResource is set to true.• Follow the same steps as above to add one more custom propertycom.ibm.ws.webcontainer.channelwritetype with Value as sync as below:31. Setting Thread-Pool Properties• Go to Servers – Application Servers – Server1 – Configuration tab – and under‘Additional Properties’ Click ‘Thread Pools’• Click on ‘Web Container’ link

Page | 33• Change the minimum size value from 10 to 35.Change the maximum size value from 50 to 35.Click Apply.• You will see the same page with save link. Click Save link. Then Click on savebutton on the next page.• You can see your changes.32. Apply IBMs PK31745 fix (This could be optional as in my case things were working fineeven though I did not follow this step).• Internally at SAS this fixpack is available at file://///sashq/root/dept/jdt/IBM_WAS60/ibmfix.Copy the jar file present at this location PK31745.jar and put it underWAS_HOME\classes

Page | 3433. Apply the SAS Hotfix 14JPS01 also known as ‘SAS fix from Tom Caulkins’ to SAS WebApplications. May be you cannot perform this step now as it is SAS Specific and needto be followed later when you are ready to do (Re-)Configuration of SASMidtier(webtier). Further down in this guide we remind you of this step again, whenwe show the installation and configuration of SAS Midtier (webtier) components.34. If your WebSphere is running on AIX Operating system, you might consider to followsome OS specific tuning that must be done (given sufficient RAM):http://sww.sas.com/saspedia/WebSphere_Version_6.0#WAS_6.0.2.15_and_SAS_9.1.3_SP4_PlusYou can also find the same information in SAS® 9.1.3 Intelligence Platform Web ApplicationAdministration Guide Third Edition available at:http://support.sas.com/documentation/configuration/biwaag.pdfIn this book, go to ‘Best Practices for Configuring your Middle Tier’ and then goto ‘Tuning WebSphere 6.0.2 or 6.1’ and on page 69 you can find ‘Set Tuning Values forthe AIX Operating System’.Things to be done on SAS side to be able to deploy on WebSphere35. You need to create a custom plan file which has WebSphere Application Server (for Web download).36. Moreover, for all my new installations I follow a best-practice especially for SASWeb(tier) Components:-First only install (without configuration wizard),-Then apply all the Hot fixes (Do not forget to apply Hotfix 14JPS01) and-Then Run only the SAS Configuration WizardReason to do so is that when SAS Configuration Wizard runs and creates “.war” filesfor deployment, it includes all the changes from Hotfixes.37. During configuration Wizard steps, when you are asked for JDK location you mustsupply the JDK bundled with WebSphere which usually is (or can be found at)WAS_HOME\javaAlso you must specify this location in the configuration.properties file that you canedit during the Configuration itself:

Page | 35If your SAS WebTier is on a separatemachine. You may not get this screen.To view it clearly, you may zoom it.To view it clearly, you may zoom itBut if I am configuring Xythos and I get the following screen, I always specify thepath for JDK 1.4.2_05/1.4.2_15:38. Few other things that might you have to specify when configuring SAS WebTier in theconfiguration.properties are:WEBSRVHOST=was12 //put the hostname of the machine where WebSphere runsWEBSRVPORT=9080 //WC_defaulthost. Can found from admin console atServers > Application Servers > server1(yourAppSrvrName)Under ‘Communications’ expand ‘Ports’ to see list of all theports used by your server. ORYou can find all the ports in serverindex.xml atWAS_HOME/profiles//config/cells//nodes//WEBSRVTYPE=websphere //it will be set to this value if your plan file has WebSphereNote: You might see TOMCAT_HOME=/usr/local/Tomcat4.1. Ignore it.APP_SERVER_WEBSPHERE_NODE= blues07Node01 //You can find these values fromAPP_SERVER_WEBSPHERE_CELL= blues07Node01Cell //websphere Console. From the RunTimeAPP_SERVER_WEBSPHERE_SERVER=server1//of the serverAPP_SERVER_WEBSPHERE_HOME=/usr/IBM/WebSphere/AppServer //WAS_HOMEWEBSPHERE_DEBUG_LOGIN=false

Page | 3639. You save your configuration.properties file and complete the configuration wizard.40. After configuration wizard is completed successfully, check in SAS_Configuration_dir/Lev1/web/webapps if all the SAS Web Apps are created.41. In the instructions.html file that gets created at the end of configuration wizardcontains some steps about SAS mid(web) tier deployments.i. Deploying your Web Applications (Modifying Policy Files): which states instructionsabout modifying policy files. Policy files control the permissions granted to the Webapplications. In WebSphere the policy file(s) we are interested in is ‘was.policy’.Mainly this policy file can be found at two places. One underWAS_HOME/profiles//properties and there will be one ‘was.policy’file with each web-application that is deployed under this profile’s server for e.g.in my case when I will deploy Portal application, Portal will have its own‘was.policy’ file under/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/blues07Node01Cell/Portal_war.ear/META-INF.But the ‘was.policy’ file which is under WAS_HOME/profiles//properties is sortof global policy file. All the changes (settings) made to this ‘was.ploicy’ file willbe applied to each application as it is deployed.Two policy file fragments were created in SAS_Conf_Dir/Lev1/web/Deployments:-sas.allpermissions.websphere.policy allows the Web applications to run without securityrestrictions. This file should be used during the initial install.-sas.websphere.policy defines more restrictive security settings. This file should beused in a production environment.So far we have always appended the contents of sas.allpermissions.websphere.policy to the‘was.policy’ file under WAS_HOME/profiles//properties before starting thedeployment of any SAS Web-applications.ii. Configure WebSphere Security and Authentication Information: You can safely ignorethese instructions as they are not enough for 6.0 and 6.1. Actually, these changesalong with some more are already covered under points 28 to 31 of thisdocument.Note: Unlike Tomcat, for WebSphere one has to manually deploy the SAS Webapplications.Now we can start the deployment process of SAS WebApplications42. First lets deploy SAS Web Infrastructure Kit applications:1. SASTheme_default2. SASPreferences3. SASDoc

Page | 374. Portal5. SASStoredProcessI follow step 10: Prepare the servlet container environment and Step 11: Deploy Webapplication files into the servlet container from ‘wik_readme.html’ which you can findin the installation of SAS Web-Tier components and is atSAS_Install_Dir/Web/Portal2.0.1.Although the section for WebSphere in these steps mentions WebSphere5.1, these stepscan be followed for WebSphere 6.0 and 6.1 as well, but they are not enough.• In Step 10 under section Installation Tips for IBM WebSphere 5.1 on Unix Systems, there are two points a)and b). Changes mentioned in point a) are not sufficient for 6.0 and 6.1. If youhave followed this document completely from the beginning you can ignore thispoint as these changes along with some more are already covered under point 28 to31.Point b) is something that must be followed now which says: Update WebSphere'sJAAS configuration file to include the authentication information that is used bySAS Web Infrastructure Kit Web applications. To do so, concatenate the contents ofthe login.config file located in the SASServicesConfig folder of the setup (installation)directory to your server's JAAS configuration file located in the‘WAS_HOME/profiles//properties’ directory. As a default, theserver's JAAS configuration file is called wsjaas.conf.• In Step 11 under section Installation Tips for IBM WebSphere 5.1 on Unix Systems you can safely ignorepoint a, b and c, if you have used SAS Configuration Wizard to configure your SASWeb Tier components (web applications) and you have .war files created underSAS_Configuration_dir/Lev1/web/webapps as mentioned in step 39 of this documentabove.Now as mentioned in point d you can start deploying (install) the SAS Webapplications.I have taken those steps here with screenshots:Using the WebSphere Administrative Console, deploy the Web applications created bySAS Configuration Wizard and kept in SAS_Configuration_dir/Lev1/web/webapps, asfollows:i. If needed, start the WebSphere application server.ii. Point your browser to the WebSphere Administrative Console Webapplication (for example, http://localhost:9060/ibm/console). ForUnix systems you have to start the browser on the unix machinewhere your .war files are located.iii. Log on to the WebSphere Administrative Console. By default, you donot need to enter an account and password.iv.Use the ‘Preparing for application installation wizard’, asdescribed in Steps v through xiv below, to deploy each of thefollowing Web applications. The Web applications should bedeployed in the order that they are listed here:1. SASTheme_default2. SASPreferences

Page | 383. SASDoc4. Portal5. SASStoredProcessv. After you have logged on, use the tree on the left side of theconsole to navigate to the ‘Preparing for application installationwizard’ (for example, Applications -> Install New Application).vi. On the first screen, set the Local path (or Server path for anetwork deployment) by using the browse button to navigate to the/usr/wrdi/sas/config/Lev1/web/webapps directory and selecting theappropriate Web application.vii.Set the Context Root to the name of the Web application (thefilename without the .war extension), and then select the Nextbutton.viii.On the next screen, select the Generate Default Bindings checkbox, and then select the Next button.ix.On the next screen, select the Continue button. The Java policiesthat are used by the Web applications will be set in upcomingsteps.

Page | 39x. You should now be on Step 1 on the ‘Install a New Applicationwizard’. Select the Next button to accept the defaults.xi.On Step 2 of the wizard, select the Next button to accept thedefaults. At this step, typically at customer sites under‘Clusters and Servers’ (shown in red rectangle) you will see alist with more than one server (clusters) listed. You (WebAdministrator at Customer site) must know your server name (orcluster) to select from the list. Then check the checkbox (shownin green circle) for the application and click the apply button(shown in blue rounded rectangle).Typical example of the same step at customer site:

Page | 40xii.On Step 3 of the wizard, select the Next button to accept thedefaults.xiii.On Step 4 of the wizard, select the Finish button to deploy theWeb application.xiv.On the Installing... screen, select the Save to MasterConfiguration link.

Page | 41On the Save screen, select the Save button to save the changes tothe master configuration.xv.Repeat Steps v, vi, vii, viii, ix, x, xi, xii, xii, and xiv foreach SAS Web Infrastructure Kit web-application.Now as mentioned in point e, after all of the SAS Web Infrastructure Kit webapplicationshave been deployed, adjust the settings for the SASTheme_default,SASPreferences, and Portal Web applications as followsi. Use the tree on the left side of the console to navigate to theEnterprise Applications wizard (for example, Applications ->Enterprise Applications).ii.Select the SASTheme_default Web application link.iii.Change the Starting Weight to a value that is less than theStarting Weight of the other Web applications (for example, 0).Then select the OK button. You will see ‘save’ link appearing tosave this change. But you can choose not to click it now, insteadsave everything once you are done with the changes forSASPreferences and Portal as well.

Page | 42iv.Select the SASPreferences Web application link. Change theStarting Weight to a value that is greater than the StartingWeight of the SASTheme_default Web application (for example, 10).Then select the OK button.v. Select the Portal Web application link. Change the Starting Weightto a value that is greater than the Starting Weight of theSASTheme_default Web application (for example, 10). Change theClassloader Mode to PARENT_LAST. Change the WAR ClassloaderPolicy to Application, and then select the OK button.

Page | 43vi.On the Enterprise Applications screen, select the Save link in theMessage(s) area. On the Save screen, select the Save button tosave the changes to the master configuration. This completes thedeployment of SAS Web Infrastructure Kit web-applications.Now if have followed step i. from point 40 in this document, you can safelyignore the remaining steps (f to j) in the ‘wik_readme.html’.43. If you have been asked to include SASBIDashboard in your deployment, then followsteps below to deploy it.i. Follow the steps v, vi, vii, viii, ix, x, xi, xii, xii, and xiv from pointno. 41 in this document above to deploy the SASBIDashboard.war file.ii. After the application is deployed, select the application, go toConfiguration tab and insure that the starting weight value is greater thanthe SAS Portal that you set during step v. under point 42 in this document.

Page | 4444. Now you might want to restart (stop and start) your WebSphere Application server andtest the SAS Web-applications deployed so far or you can continue with the remainingsteps and first complete the deployment of all the SAS Web Applications.You might want to refer point no. 48 about ‘Starting and Stopping your WebSphereApplication server’ at the end of this document.45. Now let’s deploy SAS Web Report Studio:i. The document that I follow is ‘deployment.html’ located under SAS WebReport Studio installation directory. For me it is at‘/usr/wrdi/sas/SASWebReportStudio/3.1’. In this document you can directlygo to section ‘Deploying SAS Web Report Studio for UNIX and WebSphere 5.1’.Although this section for WebSphere mentions WebSphere5.1, these steps canbe followed for WebSphere 6.0 and 6.1 as well.The instructions mentioned in subsection ‘Updating wsjaas.conf’ about copyingthe contents of login.config can be skipped if you have followed point no.41 in this document. Reason is the login.config file present in foldernamed ‘live’ under installation directory of SAS Web Report Studio isexactly the same as the login.config file present in folder named‘SASServicesConfig’ under installation directory of SAS Portal components(Web Infrastructure Kit).The deployment process steps mentioned there under ‘Deploying SAS WebReport Studio’ are similar to the steps v, vi, vii, viii, ix, x, xi, xii,xii, and xiv from point no. 41 in this document.Follow these steps to deploy SASWebReportStudio.war file.ii. After the application is deployed, return to the left side of the page and,under the Applications heading, click on Enterprise Applications. Then, onthe right side of the page, click on the SASWebReportStudio_war link. Inthe Configuration tab, set Classloader mode to PARENT_LAST and set WARClassloader Policy to Module. Then, click on the OK button.

Page | 45On the Enterprise Applications screen, select the Save link in theMessage(s) area. On the Save screen, select the Save button to save thechanges to the master configuration. This completes the deployment of SASWeb Report Studio web-applications.46. Now let’s deploy SAS Web Report Viewer:i. The document that I follow is ‘deployment.html’ located under SAS WebReport Viewer installation directory. For me it is at‘/usr/wrdi/sas/SASWebReportViewer /3.1’. In this document you can directlygo to section ‘Deploying SAS Web Report Viewer for UNIX and WebSphere 5.1’.Although this section for WebSphere mentions WebSphere5.1, these steps canbe followed for WebSphere 6.0 and 6.1 as well.The instructions mentioned in subsection ‘Updating wsjaas.conf’ about copying thecontents of login.config can be skipped if you have followed point no. 41in this document. Reason is the login.config file present in folder named‘live’ under installation directory of SAS Web Report Viewer is exactly thesame as the login.config file present in folder named ‘SASServicesConfig’under installation directory of SAS Portal components (Web InfrastructureKit).The deployment process steps mentioned there under ‘Deploying SAS WebReport Viewer’ are similar to the steps v, vi, vii, viii, ix, x, xi, xii,xii, and xiv from point no. 41 in this document.Follow these steps to deploy SASWebReportViewer.war file.ii. After the application is deployed, return to the left side of the page and,under the Applications heading, click on Enterprise Applications. Then, onthe right side of the page, click on the SASWebReportViewer_war link. Inthe Configuration tab, set Classloader mode to PARENT_LAST and set WARClassloader Policy to Module. Then, click on the OK button.

Page | 46On the Enterprise Applications screen, select the Save link in theMessage(s) area. On the Save screen, select the Save button to save thechanges to the master configuration. This completes the deployment of SASWeb Report Viewer web-applications.47. Now let’s deploy SAS Web OLAP Viewer:i. The document that I follow is ‘config.pdf’ (config.doc) located under SASWeb OLAP Viewer installation directory. For me it is at ‘/usr/wrdi/sas/SASWebOlapViewerforJava/3.1’. In this document you can directly go tosection ‘Deployment’ on page 22 in Chapter8: SAS Web OLAP Viewer for UNIXand WebSphere 5.1. Although this chapter for WebSphere mentionsWebSphere5.1, these steps can be followed for WebSphere 6.0 and 6.1 aswell.The instructions mentioned in subsection ‘Updating wsjaas.conf’ about copying thecontents of login.config can be skipped if you have followed point no. 41in this document. Reason is the login.config file present in folder named‘SASServicesConfig’ under installation directory of SAS Web OLAP Viewer isexactly the same as the login.config file present in folder named‘SASServicesConfig’ under installation directory of SAS Portal components(Web Infrastructure Kit).The deployment process steps mentioned there under ‘Deploying SAS Web OLAPViewer’ are similar to the steps v, vi, vii, viii, ix, x, xi, xii, xii, andxiv from point no. 41 in this document.Follow these steps to deploy SASWebOLAPViewer.war file.ii. After the application is deployed, return to the left side of the page and,under the Applications heading, click on Enterprise Applications. Then, onthe right side of the page, click on the SASWebOLAPViewer_war link. In theConfiguration tab, set Classloader mode to PARENT_LAST and set WARClassloader Policy to Application. Then, click on the OK button.On the Enterprise Applications screen, select the Save link in theMessage(s) area. On the Save screen, select the Save button to save thechanges to the master configuration. This completes the deployment of SASWeb Report Viewer web-applications.48. Now you can restart (stop and start) your WebSphere Application server and test theSAS Web-applications deployed.You might want to refer point no. 48 about ‘Starting and Stopping your WebSphereApplication server’ at the end of this document.

Page | 47PortalStored-Process ApplicationSASPreferences from PortalStored-Process from PortalBIDashboard from PortalWeb Report Viewer from PortalWeb Report StudioWebOLAPViewer49. Starting and Stopping your WebSphere Application serveri. One way to start and stop server is to do it from the binary files of theprofile to which your application server belongs to:In this document our application server is ‘server1’ and it belongs toprofile ‘AppSrv01’.Note: You need to log-in with the user who owns the WebSphere installationor user which has permission to execute start/stop scripts and has porperaccess to required locations and files. In my case ‘root’ is the owner.#/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/bin>./startServer.shserver1ADMU0116I: Tool information is being logged in file/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.logADMU0128I: Starting tool with the AppSrv01 profileADMU3100I: Reading configuration for server: server1ADMU3200I: Server launched. Waiting for initialization status.ADMU3000I: Server server1 open for e-business; process id is 700562#/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/bin>

Page | 48#/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/bin>./stopServer.sh server1ADMU0116I: Tool information is being logged in file/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/stopServer.logADMU0128I: Starting tool with the AppSrv01 profileADMU3100I: Reading configuration for server: server1ADMU3201I: Server stop request issued. Waiting for stop status.ADMU4000I: Server server1 stop completed.ii.Another way to start and stop your server is from the firststeps window#cd /usr/IBM/WebSphere/AppServer/profiles //change to WAS_HOME/profiles#cd firststeps#./firststeps.sh//before this command do set DISPLAY and start XserverThis command will display the following first steps window.Click on Start the server link. It will open another window where you cansee the status of the starting server:You can close this window.Once the server is started successfully the link ‘Start the Server’ in thefirst steps window above will be changed to ‘Stop the Server’. Click Stopthe server link whenever you want to stop the server.This window can be closed.