WAS: PCT Response file questions

Scenario 1: 4 nodes
Node 1: DeploymentManager + ApplicationServer1
Node 2: ApplicationServer2
Node 3: IHS WebServer1
Node 4: IHS WebServer2
 
Node1 and Node2 clustered.
 
Question 1: which server hostname should be for wasMachineHostName? Deployment manager server hostname? Or ApplicationServer1 hostname? Or ApplicationServer2 hostname?
ANSWER:   It does not matter which hostname.  I would probably use the hostname of the deployment manager myself.  But it really does not matter ether way.  Be sure to choose REMOTE in the PCT, and also you will want to configure the IHS Admin Server  so that you can remotely manage both IHS web servers from the WAS Admin Console.

 
Scenario 2: 2 nodes
Node 1: DeploymentManager + ApplicationServer1 +  IHS WebServer1
Node 2: ApplicationServer2 + IHS WebServer2
 
Question 1: how to decide configType value for WebServer1 and WebServer2
ANSWER:  If the web server is on the same system as the WAS appserver, then it is LOCAL.  In this case, use LOCAL for both of them.

Question 2: what should be the value of profileName for WebServer1?
ANSWER:  for LOCAL scenario, always use the profile name of the WAS node (ie. AppSrv01).  Never use the deployment manager profile name (ie. Dmgr01).

Question 3: What should be the value of wasMachineHostName for WebServer1?
ANSWER:  wasMachineHostName is only used for REMOTE scenario.  So, you do not need that variable at all in this LOCAL case.

Question 4: what should be the value of profileName for WebServer2?
ANSWER:   use the name of the WAS node profile (ie. AppSrv01).

Question 5: what should be the value of wasMachineHostName for WebServer2?
ANSWER:  this is a LOCAL scenario so wasMachineHostName is not needed.

WebSphere: Compile JSP

/opt/IBM/WebSphere/AppServer/profiles/LTSLUATAppNode2/bin/JspBatchCompiler.sh -enterpriseapp.name BPS -webmodule.name BPS.war -cell.name LTSLUATCell -node.name LTSLUATAppNode2 -server.name LTSLUATAppServer2 -filename LTSCAFApi.jsp -keepgenerated true -forceCompilation true -log.level FINEST > jspbatchcompiler.out 2>&1

Set up Samba on Linux

Set Up Steps

The following samba modules are required:

# rpm -qa | grep -i samba

samba-common-3.0.33-3.29.el5_5.1

samba-client-3.0.33-3.29.el5_5.1

samba-3.0.33-3.29.el5_5.1

perl-5.8.8-27.el5.x86_64.rpm

perl-Convert-ASN1-0.20-1.1.noarch.rpm  

mount /net/todnfs03/vol/archive/RedHat/RHEL5-U4-x86_64/rhel-server-5.4-x86_64-dvd.iso /mnt -o loop

cd Server

# rpm -ivh ./perl-5.8.8-27.el5.x86_64.rpm                                                                                          ! Check if already installed. Rpm –qa | grep –i perl

warning: ./perl-5.8.8-27.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186

Preparing...                ########################################### [100%]

        package perl-5.8.8-27.el5.x86_64 is already installed

# rpm -ivh perl-Convert-ASN1-0.20-1.1.noarch.rpm                                                                          ! Check if already installed

warning: perl-Convert-ASN1-0.20-1.1.noarch.rpm: Header V3 DSA signature: NOKEY, key ID 37017186

Preparing...                ########################################### [100%]

   1:perl-Convert-ASN1      ########################################### [100%]

# rpm -ivh ./samba-3.0.33-3.14.el5.x86_64.rpm                                                                                ! Due to yum updates, install this module with --nodeps

warning: ./samba-3.0.33-3.14.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186

Preparing...                ########################################### [100%]

   1:samba                  ########################################### [100%]

Register the server with RHN for updates. Due to a shortage of licenses, currently the server cannot be patched to the latest updated. Check with Ziyan to manually patch Samba to samba-3.0.33-3.29.el5_5.1

rhnreg_ks --activationkey 1-91f9873ace9acf35defa1c52f6348616 --serverUrl https://inf-bcclu1rhn01.goweekend.ca/XMLRPC --sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT

An error has occurred:

Error Message:

    Registration failed: RHN Software Management service entitlements exhausted

Error Class Code: 91

Error Class Info: Registration token unable to entitle system: maximum membership exceeded

Explanation:

    Your organization does not have enough Management entitlements to register this

    system to Red Hat Network. Please notify your organization administrator of this error.

    You should be able to register this system after your organization frees existing

    or purchases additional entitlements. Additional entitlements may be purchased by your

    organization administrator by logging into Red Hat Network and visiting

    the 'Subscription Management' page in the 'Your RHN' section of RHN.

    A common cause of this error code is due to having mistakenly setup an

    Activation Key which is set as the universal default.  If an activation key is set

    on the account as a universal default, you can disable this key and retry to avoid

    requiring a Management entitlement.

See /var/log/up2date for more information

#

scp inf-fcplx1svc03:/etc/samba/smb.conf /etc/samba/                             ! copy sample samba.conf file . Check for “fnettest” for shared samba entry

==========================================smb.conf =====================

[global]
        workgroup = SACMCM
        server string = CRM
        netbios name = crm-bccldvapp01
        guestok = no
      
      
        hosts allow = 10.115. , 10.193.
        # logs split per machine
        log file = /var/log/samba/smbd.log
        # max 50KB per log file, then rotate
        max log size = 50
        security = ADS
        realm = ADROOT.GOWEEKEND.CA
        password server = kdc.goweekend.ca
        encrypt passwords = yes
        smb passwd file = /etc/samba/smbpasswd
  unix password sync = Yes
  passwd program = /usr/bin/passwd %u
  passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
  username map = /etc/samba/smbusers
  socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
        # the login script name depends on the machine name
        # the login script name depends on the unix user used
        # disables profiles support by specifing an empty path
        local master = no
        wins support = yes
        dns proxy =  no
  preserve case = yes
  short preserve case = yes
  case sensitive = yes
        load printers = no
        cups options = raw
        #obtain list of printers automatically on SystemV
        map archive = no
        map hidden = no
        map system = no
   idmap uid = 16777216-33554431
   idmap gid = 16777216-33554431
   template shell = /bin/false
   winbind use default domain = no
[crm]
   comment = MVDR Log
   path = /apps/crm
   valid users = aniu01 mj08

   read list = aniu01
   write list = aniu01 ydong09
   force user = aniu01
   public = no
   writable = yes
   printable = no

====================================End of smb.conf ========================

# net ads join -U adm-userid

adm-userid's password:                                                                     ! Enter domain adm password

Failed to set password for machine account (NT_STATUS_ACCESS_DENIED)

Failed to join domain: Access denied                                                     ! Work with AD admin to enable machine to join domain

#

Modify /etc/hosts to add the following lines

9.115.97.49  samba.goweekend.ca samba

Start Samba

/etc/smb start

Goto workstation

Start>Run>\\samba.goweekend.ca