1. Platform LSF or 9.1.x must be installed, configured, and running prior to deploying Platform Web Services.

Transcription

1 README SAS Platfrm Web Services General Requirements IMPORTANT: Please read and understand the fllwing requirements befre prceeding with deplyment f Platfrm LSF and Platfrm Web Services. Failure t meet these requirements will result in deplyment failures and/r an unsupprted cnfiguratin. Please be sure t als read the pre-deplyment steps fr additinal details. Deplyment Steps 1. Platfrm LSF r 9.1.x must be installed, cnfigured, and running prir t deplying Platfrm Web Services. 2. Platfrm Web Services must be deplyed int a dedicated SAS Web Applicatin Server. The nly ther web applicatin allwed t run in the same SAS Web Applicatin Server as Platfrm Web Services is the SAS-prvided frnt-end applicatin knwn as the SAS Grid Manager Mdule fr SAS Envirnment Manager. If yu fllw the Express r Typical path in the SAS Deplyment Wizard, this will happen autmatically and Platfrm Web Services will be deplyed t SASServer14. Changes made via the SAS Deplyment Wizard Custm path that affect the SAS Web Applicatin Server t which Platfrm Web Services is deplyed can result in an unsupprted cnfiguratin. 3. Platfrm Web Services must be installed and run as an LSF Administratr. This means that the SAS Web Applicatin Server t which Platfrm Web Services is deplyed must als be installed and run as an LSF administratr. In rder t meet this requirement, the SAS Deplyment Wizard must be run as an LSF administratr t deply SAS. Platfrm Web Services must be installed, cnfigured, and run as the Primary LSF Administratr unless a patch (108149), prvided by Platfrm Cmputing and available thrugh SAS Technical Supprt is applied. See the sectin titled Installing SAS as the Primary LSF Administratr, if yu want t run Platfrm Web Services as an LSF Primary Administratr. See the sectin titled Installing SAS as a Nn-Primary LSF Administratr, if yu want t run Platfrm Web Services as an LSF Nn-Primary Administratr. 4. Bth hrizntal and vertical middle tier clustering are supprted fr Platfrm Web Services. 1

2 SAS Platfrm Web Services README 5. Platfrm Web Services must be deplyed n either an LSF server hst r an LSF client hst with access t the LSF cnfiguratin and cnnectivity t the cluster. The SAS Middle Tier hst where Platfrm Web Services is running must have Platfrm LSF installed (as stated in requirement #1). This allws Platfrm Web Services t use LSF executables such as lsrun t perfrm actins. The SAS Middle Tier hst where Platfrm Web Services is running must be allwed t talk t the cluster. If deplyed t a SAS Middle Tier hst that is an LSF server machine, the machine shuld already be in the LSF cluster file and cnnected t the cluster. If deplyed t a SAS Middle Tier hst that is an LSF client machine, yu can insert the SAS Middle Tier hst name(s) in the LSF cluster file. Yu can als enable flating clients n the SAS Grid. The SAS Middle Tier hst where Platfrm Web Services is running must have access t the Platfrm LSF cnfiguratin directry. There are tw ways this can be accmplished: 1) direct access (via a shared file system) t the LSF cnfiguratin directry, and, 2) pseud access t the lsf.cnf file (e.g. a lcal cpy f the actual lsf.cnf file). The "pseud" cpy f the lsf.cnf file must have the LSF_MASTER_LIST and LSF_GET_CONF=lim envirnment variables defined. Additinally, the LSF_INCLUDEDIR envirnment variable must be defined in rder fr the SDW prerequisite check t wrk. 6. Platfrm Web Services users must be valid users registered in the SAS Metadata repsitry. Since Platfrm Web Services will use SAS single sign-n thrugh the Central Authenticatin Service, the users must be valid users registered in the SAS metadata repsitry. The users that are LSF administratrs will have full privileges, whereas the users that are nt LSF administratrs will have limited privileges. 7. Platfrm Web Services requires a PstgreSQL database. The SAS Web Infrastructure Platfrm Data Server is a PstgreSQL database and meets this requirement. If the deplyment steps utlined in this dcument are fllwed crrectly, the SAS Web Infrastructure Platfrm Data Server will autmatically be deplyed and Platfrm Web Services will be cnfigured t use it. Pre-deplyment Steps Prir t deplying Platfrm Web Services via the SAS Deplyment Wizard, the fllwing steps shuld be cmpleted. These steps are described in general terms as the specifics f hw t perfrm each f these steps is beynd the scpe f this dcument. Installing SAS as the Primary LSF Administratr 1. Create an perating system accunt that will serve as bth the Primary LSF Administratr and the SAS install accunt. 2. Install Platfrm LSF r 9.1.x. 2

3 SAS Platfrm Web Services README 3. Surce the Platfrm LSF cnfiguratin file. This ensures that the LSF_ENVDIR envirnment variable is set prir t running the SAS Deplyment Wizard. 4. Dwnlad (r therwise acquire access t) a SAS Sftware Dept. Installing SAS as a Nn-Primary LSF Administratr 1. Create an perating system accunt that will serve as bth the LSF administratr and the SAS install accunt. 2. Cnfigure passwrdless SSH such that the SAS install accunt, under which Platfrm Web Services is running, has the ability t lg in (via SSH) t any LSF master candidate hst as the Primary LSF Administratr. 3. Install Platfrm LSF r 9.1.x. 4. Windws ONLY: Grant the SAS install accunt read/write access t the LSF cnfiguratin files. 5. Surce the Platfrm LSF cnfiguratin file. This ensures that the LSF_ENVDIR envirnment variable is set prir t running the SDW. 6. Dwnlad (r therwise acquire access t) a SAS Sftware Dept. Cnfiguring Passwrdless SSH This sectin prvides a brief verview f hw t minimally cnfigure passwrdless SSH as required by Platfrm Web Services. All f the details surrunding passwrdless SSH cnfiguratin are beynd the scpe f this dcument. It is highly recmmended that yu read the dcumentatin included with the versin f SSH yu are running as the details can vary acrss different versins f SSH. Passwrdless SSH is required if yu have applied the patch with build ID (this is the patch that yu wuld apply if yu need t run Platfrm Web Services as a Nn-Primary LSF Administratr). By cnfiguring passwrdless SSH, the Nn-Primary LSF Administratr accunt used t run Platfrm Web Services will be able t lg in (via SSH) t any LSF master candidate hst as the Primary LSF Administratr withut a passwrd. T cnfigure passwrdless SSH, take the fllwing steps: 1. Lg nt every Platfrm Web Services hst as the LSF Nn-Primary Administratr and ensure that an SSH public/private key pair exists. It is highly recmmended that the same SSH public/private key pair be used n all machines. The SSH public/private key pair is typically fund in the ~/.ssh/ directry. If an SSH public/private key pair des NOT exist, create ne. This is typically dne with the ssh-keygen cmmand. Again, it is highly recmmended that the same SSH public/private key pair be used n all machines. 2. Lg nt every LSF master candidate hst as the LSF Primary Administratr and add the SSH public key f the LSF Nn-Primary Administratr t the authrized_keys file. The authrized_keys file is typically fund in the ~/.ssh/ directry. 3

4 SAS Platfrm Web Services README If the authrized_keys file des nt exist, create ne with yur favrite text editr. 3. Lg nt every LSF master candidate hst (as the LSF Primary Administratr) frm every Platfrm Web Services hst (as the LSF Nn-Primary Administratr). D this t ensure that each LSF master candidate hst is added t the SSH knwn_hsts file n every Platfrm Web Services hst. The SSH knwn_hsts file is typically fund in the ~/.ssh/ directry. See the sectin belw titled SSH hst authenticity fr mre infrmatin abut why this step is necessary. SSH Hst Authenticity The first time an SSH lgin attempt is made frm ne hst (the lcal hst) t anther hst (the remte hst), SSH will display a message, fllwed by a prmpt, similar t the fllwing: The authenticity f hst 'smehst.sas.cm ( )' can't be established. RSA key fingerprint is 76:36:38:cd:95:f3:b1:57:b3:ce:f2:be:65:4a:d1:72. Are yu sure yu want t cntinue cnnecting (yes/n)? Once the abve prmpt is answered with yes, SSH will add the remte hst (smehst.sas.cm in the abve example) t the SSH knwn_hsts belnging t the currently lgged in user accunt. Once the remte hst is added t the knwn_hsts file, SSH will nt display this message and prmpt n subsequent lgin attempts frm the current lcal hst as the currently lgged in user t the remte hst. When Platfrm Web Services attempts t lg int a remte system via SSH, it will fail if SSH respnds with the abve message and prmpt since Platfrm Web Services expects fr passwrdless SSH t already be cnfigured such that interactin is nt necessary. Pst-deplyment Steps Platfrm Web Services requires pst-deplyment steps n Windws. These steps have nt been autmated due t limitatins in the SAS Deplyment Wizard. As mentined in the general requirements sectin f this dcument, Platfrm Web Services must be run as an LSF administratr. This happens autmatically n a UNIX-based deplyment when the SAS Deplyment Wizard is run as the LSF Administratr t install SAS. On a Windws-based deplyment, hwever, the SAS Web Applicatin Servers and the applicatins cntained within them are cnfigured t run as Windws Services. The SAS Deplyment Wizard creates and cnfigures these services t run under a lcal system accunt. The fllwing steps must be taken pst-deplyment in rder t prperly cnfigure the Windws Service assciated with the SAS Web Applicatin Server that hsts Platfrm Web Services. 1. Open an MS-DOS prmpt. 2. Enter services.msc at the prmpt and press Enter. 3. Lcate the service assciated with SASServer14 frm yur deplyment. 4

5 SAS Platfrm Web Services README 4. Stp the service. 5. Mdify the service t run as an LSF administratr. 6. Start the service. SAS and all ther SAS Institute Inc. prduct r service names are registered trademarks r trademarks f SAS Institute Inc. in the USA and ther cuntries. indicates USA registratin. Other brand and prduct names are trademarks f their respective cmpanies. Cpyright 2016 SAS Institute Inc. Cary, NC, USA. All rights reserved July 2016