IBM WebSphere Application Server OEM Edition for z/OS Quickstart ...

More documents

Recommendations

Info

4 IBM WebSphere Application Server OEM Edition for z/OS Quickstart Guide
Chapter 2. IBM WebSphere Application Server OEM Editionfor z/OS quickstart proceduresTypical quickstart procedureBefore you begin:This chapter describes two quickstart procedures:v “Typical quickstart procedure”v “Advanced quickstart procedure” on page 7Unless you have a deep understanding of the WebSphere Application Server forz/OS configuration process, you should use the typical quickstart procedure. Formost z/OS systems, the default values provided in thewasOEMDefault.responseFile will be appropriate. However, if you have a deepunderstanding of the WebSphere Application Server for z/OS configuration process,and several of the default values provided in the wasOEMDefault.responseFile donot match the system requirements for your environment, you should use theadvanced quickstart procedure.Reminder: You can run the WASOEM.sh script from an OMVS or telnet/rloginsession. You cannot run this script from under ISHELL.The following procedure can be used to create a IBM WebSphere ApplicationServer OEM Edition for z/OS server instance. This procedure assumes that:vvvYou have already used SMP/E to install IBM WebSphere Application Server OEMEdition for z/OS, according to the instructions provided in the IBM WebSphereApplication Server OEM Edition for z/OS Program Directory.Most of the default values provided in the default response file are appropriatefor your system environment.You do not need to change values in the override response file.v Print a copy of the Appendix A, “z/OS system preparation checklist,” on page 11,and verify that the setup tasks listed in that checklist have been completed forthe target z/OS image. These setup tasks must be completed before you start toconfigure IBM WebSphere Application Server OEM Edition for z/OS.vvvPrint a copy of the Appendix C, “Post-installation tasks check list,” on page 33, sothat you can refer to it when you are ready to complete Step 4.Make sure that you know the VOLSER on which you are going to have theWASOEM.sh script allocate the two data sets into which the WebSphereApplication Server for z/OS configuration technology generates internalconfiguration jobs.You will enter this VOLSER value in response to the following prompt:BBN0133I:Enter the volume name to allocate the DATA and CNTL data sets on,or enter * to select SMS managed :Make sure that you know the VOLSER that can be used by the WASOEM.shscript to allocate a HFS or ZFS data set to contain the IBM WebSphereApplication Server OEM Edition for z/OS configuration file system. This VOLSERmust be able to allow an allocation of a ZFS or HFS data set that has 420primary cylinders and 100 secondary cylinders. SMS managed volumes can bespecified with the * value.You will enter this VOLSER value in response to the following prompt:© Copyright IBM Corp. 2009 5
Page 1 and 2: IBM WebSphere Application Server OE
Page 3 and 4: ContentsTables . . . . . . . . . .
Page 5 and 6: Tables© Copyright IBM Corp. 2009 v
Page 7 and 8: IntroductionThis document is intend
Page 9 and 10: Chapter 1. Building an IBM WebSpher
Page 11: There are other z/OS system tasks t
Page 15 and 16: Following is an example of the comm
Page 17 and 18: WASOEM.shIf you issue this command,
Page 19 and 20: Appendix A. z/OS system preparation
Page 21 and 22: Check whenchange iscompletedz.OS sy
Page 23 and 24: Appendix B. WASOEM.sh shell script
Page 25 and 26: Prompt Description Default value Yo
Page 39 and 40: VariableConfiguration valueszDaemon
Page 41 and 42: Appendix C. Post-installation tasks
Page 43 and 44: Check whentask iscompletedTask Desc

IBM WebSphere Application Server OEM Edition for z/OS Quickstart ...

Create successful ePaper yourself

Delete template?

Save as template?