Installing WebSphere Everyplace Access 4.21 On AIX

Full Install

Version 11060210 of the build

This method presumes you are connected to a network drive which has a WebSphere Everyplace Access (WEA) build available. This process describes the use of Setup Manager, which installs WEA. It includes the installation of components "WebSphere Everyplace Access", "WebSphere Everyplace Access Basic Services", "SecureWay Directory Server", and "DB2 Universal Database Server", Everyplace Synchronization Server, DB2 Everyplace, Intelligent Notification Server, Device Management Server, and the portlets. Note that this was a snapshot for a particular build. There might be changes in defaults in subsequent builds/installs.

When using Setup Manager without the use of the keyboard (for accessibility), choosing a radio button involves using the "Tab" key to go to the appropriate field, and pressing the space bar to select that field.  For selecting check boxes, use the tab and arrow keys to move to the appropriate  position, then press the space bar to "check" the box. Also, in the following sections, when instructed to "select" or "click", use the tab key to go to the appropriate field, then press the "Enter" key.

Before you begin installation of the full complement of services, and you are using the normal "NIM" installation Operating System image, you must increase your file sizes and (supposedly) reboot your machine. This can be done automatically using a utility provided in the "tools" directory.

1)  Logon to your AIX machine (i.e. "(yourmachinename).raleigh.ibm.com") as "root", but before you attempt to install WEA, you must increase your file sizes. (i.e. change directories to "/WEA/tools/shayden", and execute the script "qp.ksh"). See Increasing File Sizes for details of this script. You will then be instructed to reboot the machine to apply settings (this reboot process is probably not necessary). However, if you wish to do so, it can be done by typing "reboot" .

2)  (After reboot), logon to your AIX machine (i.e. "(yourmachinename).raleigh.ibm.com") as "root", and then mount a network drive to your machine that has the appropriate build on it (i.e. execute the command "/tools/gdeen/mknas", shell scripts which mount the network disk with builds on it). See Example Mount Script for details of this script.

3)  Change directories to the newly mounted drive (i.e. "cd  /nasimgs/cd1"), and at the AIX command prompt type "./install.sh". In a few seconds a new window should appear for performing the installation.

During installation, progress will be displayed on the window you started the install on.

Once installation is complete the WEA Information Center is located at "HTTPServer/htdocs/en_US/WEAInfo/en/InfoCenter/index.html"

(common Administrator password for Windows machines is (generic password))
 
 
 

WebSphere Everyplace Access Install

1)  After invoking the install script, the first screen you will see is the "View Information" window in the "View Prerequisites" panel. If you wish, view the prerequisites (this will be done via a web browser), then click "Next"

2)  In the "Reading Software License" panel, select "Accept" in the "Program License Agreement" section and click "Next".

3)  In the "Install Selection" panel, select "Standard Install" and click "Next".

4)  You then have the option to enter a response file of a previously recorded install if desired, do not enter a value (and if one is there by default, delete it from this input field), and click "Next".

5)  In the "Select Components" panel, select only the components "WebSphere Everyplace Access", "WebSphere Everyplace Access Basic Services", "Intelligent Notification Services", "Everyplace Synchronization", "Device Manager", "SecureWay Directory Server", and "DB2 Universal Database Server", and click "Next".

(Note: for installation with Microsoft Active Directory, see Installation with Microsoft Active Directory)
 
 
 

IBM HTTP Server

1)  In the "Collecting Admin Username for IBM HTTP Server" panel, enter "ihsadmin" for the User Name, Password, and Confirm password fields. For the "Group" enter "ihsgrp", then click "Next".
 
 

For installations with other LDAP servers, the following will not be performed:

SecureWay Directory Installation

1)  In the "SecureWay Directory Server" "Collect LDAP Suffix Information" panel, in the Suffix field enter "dc=rushmore" (or "dc=raleigh,dc=ibm,dc=com").  In the Administrative User enter "cn=wpsadmin",  for the Password and Confirm Password fields enter "wpsadmin", then click "Next".  (LDAP port is "389").

(Note: for installation with Microsoft Active Directory, see Installation with Microsoft Active Directory)

WebSphere Application Server

1)  In the "WebSphere Application Server directory" panel, click "Next" to accept the defaults (WebSphere Application Server Directory is "/usr/WebSphere/AppServer").

2)  In the "Choose DB Location" panel "Is this a remote database" field, select "No", and then click "Next".

4)  In the "Collect DB User Info" panel, accept the default for Database Username = "wasinst" and Local Database Group "wasgrp", and enter "wasinst" for the Database Password and Confirm Database Password fields, then click "Next". (Database Username was "wasinst" and Local Database Group was "wasgrp")

5)  In the "Collect Database Settings" panel, click "Next" to accept the defaults (Local Database Name = "wasdbl", Local Database Alias  name = "wasdb", Node Name = "LOOPBACK", and Database Server Port = "55555").
 
 
 

Portal Server

If you are installing an LDAP directory other than SecureWay Directory Server, steps 3 and 4 will be different. See the appropriate LDAP directory instructions for specifics for your LDAP Directory.

1)  In the "LTPA Password" panel, enter "wpsbind" for the LTPA Password and Confirm password, and click "Next".

2)  In the "Server Configuration" panel, click "Next" to accept the defaults. (the Install Directory is "/usr/WebSphere/PortalServer", the Hostname is "(yourmachinename).raleigh.ibm.com", the Base URI i.e. "/wps", and the Home page is. "/portal", and the Customized page is "/myportal". Proxy Host and Proxy port were blank. The Base URI and the Home page will be the URL to access the Portal portlet, i.e.. "http://(yourmachinename).raleigh.ibm.com/wps/portal".).

3)  In the "Selection of LDAP Server" panel, for the "User Password" and "Confirm Password" fields, enter "wpsadmin", then click "Next" to accept the defaults ("SecureWay Directory" was selected). (LDAP Server was "(yourmachinename).raleigh.ibm.com", User DN was "cn=wpsadmin", Suffix was "dc=rushmore", and LDAP Port Number was "389").

4)  In the "LDAP Configuration" panel, accept the defaults and click "Next". (User Object Class was "inetOrgPerson", User DN Prefix was "uid", User DN Suffix was "cn=users,dc=rushmore", Group Object Class was "groupOfUniqueNames", Group Member was "uniqueMember", Group DN Prefix was "cn", Group DN Suffix was ""cn=groups,dc=rushmore", Administrator DN was "uid=wpsadmin,cn=users,dc=rushmore", and Administrative group DN was "cn=wpsadmins,cn=groups,dc=rushmore").

5)  In the "Portal Server Database Selection" panel, select "Create and initialize a new database (DB2 Only)", and click "Next".

6)  In the "Additional Database Configuration" panel , enter "wpsdb", and for the Database User, User Password, and Confirm password fields enter "wasinst, and click "Next". (JDBC Database Driver was "COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource", JDBC URL Prefix was "jdbc:db2", and JDBC Driver Library was "/home/db2inst1/sqllib/java12/db2java.zip").

7)  In the "Database option for Member Services" "Database option for Member Services" panel, select "Create and initialize a new database (DB2 Only)", and click "Next".

8)  In the "Database Configuration for Members" "Database option for Member Services" panel, enter "wmsdb", and  for the Database User, User Password and Confirm password enter "wasinst", then click "Next". (Database Name was "wmsdb", JDBC Database Driver was "COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource", JDBC URL Prefix was "jdbc:db2", and JDBC Driver Library was "/home/db2inst1/sqllib/java12/db2java.zip").
 
 

Portlets

1)  In the "WebSphere EveryPlace Access Portlets" to be installed panel, for the "Portal Administrator Password" enter "wpsadmin", and the "Database Administrator Password" field enter "wasinst", then click "Next" to accept the remaining defaults (all portlets selected, which includes "Portlets for Lotus Domino", "Portlets for Microsoft Exchange", and "Portlets for Productivity Enhancements". (Already filled in were Portal Administrator Username "wpsadmin", Group was "wpsadmins", Portal Server Hostname was "(yourhostname).raleigh.ibm.com".  In the "Offline Browsing Database Configuration" section, "Create and initialize a new database (DB2 Only)" was selected, and the Database Administration Username was "wasinst")
 
 

Everyplace Synchronization Server

1)  In the "Choose Everyplace Synchronization Adapters" panel select "Adapter for Microsoft Exchange", and "Adapter for relational databases using DB2 Everyplace (JDBC compliant)", then click "Next".

2)  In the "Configure Adapter for Microsoft Exchange" panel, for the Hostname enter "abe.raleigh.ibm.com", and your Username and Password (i.e. "shayden").

3)  In the "DB2 Everyplace" panel enter "wasinst" as the Username, Password, and Password Confirm in the associated fields. (Already filled in are the WebSphere Application Path "/usr/WebSphere/AppServer", the DB2 Everyplace Path "/usr/lpp/DB2Everyplace81", and the Username default was "db2inst1", which must be changed to "wasinst")

4)  In the "Configure Database Server" panel, for the "Password" and "Confirm Password" fields enter "wasinst", In the "Database Username" field enter "wasinst", and in the "Database Password" and "Password Confirm" fields enter "wasinst", then click "Next". (Already filled in were Node Name "LOOPESS", Port "55555", Install Directory "/usr/WebSphere/IBMSyncServer", Instance was "db2inst1",  JDBC Driver "COM.ibm.db2.jdbc.app.DB2Driver", JDBC URL Prefix "jdbc:db2:" the JDBC Library "/home/db2inst1/sqllib/java12/db2java.zip", and Server Administrator "essadmin" (changed to "wasinst"))

5)  In the "Configure Portal Server" panel, accept the defaults and click "Next". (Already filled in were Portal Base URI "/wps", and the Portal Server Hostname "(yourhostname).raleigh.ibm.com".)

(Note: to install only Basic and DB2e, select ESS install and only select the "Adapter for relational databases using DB2 Everyplace (JDBC compliant)".)
 
 

Intelligent Notification Services Server 2.0
`
1)  In the "General Installation Information" panel, click "Next" to accept the defaults. (Already filled in were Install Path "/usr/WebSphere/INS", and Hostname "(yourservername).raleigh.ibm.com")

2)  In the "Selected SubComponents configuration" panel, select "Messaging Services" and "Subscription Services", and click "Next".

3)  In the "Subcomponent Configuration" panel, click "Next" to accept the default path (Alrady filled in was Path "/temp/undDelayQueue").

4)  In the "Select Portal LDAP Type" panel, select "SecureWay Directory", and click "Next".

5)  In the "Configure LDAP Server", click "Next" to accept the defaults. (Already filled in were LDAP server hostname "(yourhostname).raleigh.ibm.com", LDAP Server Port "389", Root Username "cn=wpsadmin", Root Password (8 "*"'s), and LDAP Suffix "dc=rushmore".)

6)  In the "Configure Database", use the default database name ("insdb"), and enter "wasinst" for the Database User, Database Password, and Confirm Password fields, and click "Next".

7)  In the "Administration portlets install", accept the defaults and click "Next". (Already filled in were WebSphere Portal Hostname "(yourhostname).raleigh.ibm.com", and Portal Base URI "/wps").
 
 

Device Manager Database

1)  In the "Choose or use an existing database", click "Next" to accept the defaults.(Create and initialize a local database (reommended)).

2)  In the "Database creation mode", for the Database Username, Database Password and Confirm Password fields enter "wasinst", then click "Next". (Already filled in was the "Instance Name", with a value of "db2inst1" which must be changed to "wasinst").
 
 
 

Device Manager

1)  In the "Configure Device Manager", click "Next" to accept the defaults.  (Already filled in were Device Manager Directory "/usr/WebSphere/DMS", Web Service Directory "/usr/HTTPServer", JDBC Driver "/home/db2inst2/sqllib/java12/db2java.zip", Database Username, Database Password and Confirm password was "wasinst")
 

Summary

1)  In the "Display Summary", click "Next" to accept the defaults. (note that Steve renamed the script file "/StevesFullInst1010021124WEA_response.script", and clicked "Save Configuration".). Go have a latte'.
 
 
 

Installation Details

After several minths a popup "Configuring for Admin Role " will appear.  While you are in the process of performing these steps you should also change the WebSphere Portal Ping Initial Timeout value to 1800.  From the WebSphere Administrative Console, scope down to "WebSphere Administrative Domain", "Nodes", (yournodename), "Application Servers", and select "WebSphere Portal".  In the "Advanced" tab for the Portal Server, change "Ping initial timeout" to "1800", click "Apply".

Follow the Configuring for Admin Role instructions before you continue with the installation of the software. When you are through with the configuring for admin role, be sure to click OK in the Configuring for Admin Role popup. The installation will then continue.
 

Wait a month, and eventually an "Installation Complete" popup should be displayed stating the response file has been saved, click "OK".  In the Display Summary window, click "Finish".

Logs resulting from the installation include the "setup*" file, which is the overall install log. Within that file will be references to additional logs "RunCommand* that will be in the directory "/usr/IBMWPO/RunCommand". (note that in the "setup*", and the "RunCommand*", the "*" refers to a "randomly generated" numeric value created during the install process.)

Additional logs can be found in "/usr/WebSphere/INS/install", and "/usr/WebSphere/INS/install/RecentAlert" directories
 
 
 
 

Databases Installed During Full Installation

WebSphere Application Server   wasdbl  (alias: wasdb)
WebSphere Portal     wpsdb  (alias: wpsdb)
WebSphere Member Services   wmsdb
Offline Browsing     oflnbrs
Intelligent Notification Services   insdb  weadb
Everyplace Synchronization Server  cafprsst  (alias: cafalias)  tss1  (alias: tssalias)
DB2 Everyplace     dsyctldb  vnurse  m_vnurse  m_vn2
Device Manager     dms

WPO and WAS DB's

WebSphere Application Server   wasdbl  (alias: wasdb)
WebSphere Portal     wpsdb  (alias: wpsdb)
WebSphere Member Services   wmsdb
 

WebSphere Application Servers Installed
 

Default Server
WebSphere Portal
DMS_AppServer
Everyplace Synchronization Server
IBM DB2 Everyplace Server
Everyplace Recent Alert Server
DMconsole_AppServer
 

WebSphere Resources Installed

Sample DB Driver (installed with WAS)
wps40JDBC
Offline DB Driver
ESS DB Driver
RA DB Driver
INS DB Driver
 

WebSphere Enterprise Applications Available

(yourmachinename)_sampleApp
WebSphere Member Subsystem
WPS Enterprise Application
WCM Publish WebApp
WS Proxy
PortletInstaller_WPS_PA_101
CustomizerPortlets_WPS_PA_103
SelectorPortlet_WPS_PA_105
CredentialAdministration_WPS_PA_107
WebServicesAdministration_WPS_PA_109
Settings_WPS_PA_111
MarkupsManager_WPS_PA_113
UsersManager_WPS_PA_115
PortletManagementPortlets_WPS_PA_117
Tracing_WPS_PA_119
GroupsManager_WPS_PA_121
SearchPortlets_WPS_PA_123
ClientsManager_WPS_PA_127
AccessControl_WPS_PA_129
WelcomePortlet_WPS_PA_131
WebServicesManager_WPS_PA_133
QuickLinks_WPS_PA_135
worldclock_WPS_PA_137
reminder_WPS_PA_139
PortalContentPortlets_WPS_PA_141
ContentOrganizer_WPS_PA_143
obconfig_WPS_PA_145
QuickLinks_ea_WPS_PA_147
reminder_ea_WPS_PA_149
worldclock_ea_WPS_PA_151
wpsmail_ea_WPS_PA_153
imageviewer_ea_WPS_PA_155
ClippingPortlets_ea_WPS_PA_125
WebCache
UserGroupInfoWebService
ESSAdmin_WPS_PA_157
INSPortlet_WPS_PA_159
BannerAd_ea_WPS_PA_161
ldapSearch_WPS_PA_163
XSLT_ea_WPS_PA_165
notesiiopcalendar_WPS_PA_167
notesiiopcontacts_WPS_PA_169
notesiiopjournal_WPS_PA_171
notesiiopmail_WPS_PA_173
notesiioptodo_WPS_PA_175
exchange2000_WPS_PA_177
ESS Enterprise Application
IBM DB2 Everyplace
RecentAlertWebService
(yourmachinename)_DMS_WebApp
(yourmachinename)_DMconsole_WebApp
 
 
 

Post Installation Required Steps

After the installation has completed, manual steps are required which corects a shared memory problem between the Application Server and DB2 on AIX machines and allow users to be added to WEA portal, as well as initializing appropriate environment variables for INS.

1) Logoff and then log back on the AIX session.

2) Stop WAS and all application servers,

3) Change the DB2 instance you installed the Portal Server as (i.e. "wasinst") to support adding users and groups, by performing the following:

          su - wasinst
          export EXTSHM=ON
          db2set DB2ENVLIST=EXTSHM
          db2stop force
          db2start

4) Add the command "export EXTSHM=ON" to the associated DB ".profile" file.

5)  Restart WAS, all application servers, and any associated INS and ESS servers.
 
 

Testing The Installation

At this point WEA and associated software should be installed, and WAS and your applications should have been started. Start the Admin Console (from a command prompt type "./adminclient.sh  &"), and when queried for authentication, use the value "wpsadmin" for the ID and password. (Note: if you had left the Admin Console running after performing the steps in "Configuring for Admin Role", you still have a snapshot of the configuration of WES/WAS at that point. Refreshing the Admin Console will not show you the remaining applications that were installed after the configuration was performed. To see these applications you must exit the Admin Console and restart it. Logon using ID/Password of "wpsadmin").

Steve:  If you provide the "Security Center password" with anything other than "wpsbind", it will be changed. Apparently during the installation process the Security Center password was changed from the value input (i.e. "wpsadmin") to "wpsbind". Dont know why!

To verify the installation and operation of WebSphere Application Server, scope down to "WebSphere Administrative Domain", "Nodes", (yournodename), "Application Servers", select "Default Server", right mouse click and select "Start". Once the Default Server has started you should be able to run the "snoop" servlet by using your favorite browser and browsing the url "http://localhost/servlet/snoop". The userid and password for accessing servlets is "wpsadmin".

To verify the installation of WEA, use the url "http://localhost/wps/portal" (or alternatively your machinename, i.e.. "http://rushtest55.raleigh.ibm.com/wps/portal") to run the "WebSphere Everyplace Access" portlet. If you are queried for an ID/Password, use "wpsadmin" for both.

To login to the WebSphere Everyplace Access using the "portal" portlet, click on the key icon on the upper right corner of the web page. For the User ID and Password, enter the value "wpsadmin", and click the "Log In".

If the snoop servlet and portal portlet both work your installation was (probably) successful.
 
 

Restarting WebSphere Everyplace Access

1)  The "graceful" way to stop WEA is from the WebSphere Admin Console, selecting your node (i.e. "wea2aix1"), right mouse click, and click on "Stop". You will be prompted as to whether you really want to do this, click "OK".  (alternatively you  can (from a command prompt) "kill -9 (yourprocessnumber) on all java processes running on your machine. Note that this is a "disgraceful" way to stop WEA/WAS, and your results might dissappoint you)

2) Start the IBM WS Admin Server by issing the command "./startupServer.sh &" from the command prompt.

3) Wait a few minutes for WAS to start, then start the WebSphere Administrator Console, also from the command line using the command "./adminclient.sh  &".

4) When the Admin Console appears, scope down to "WebSphere Administrative Domain", "Nodes", "(yournodename - i.e. "wea2aix1")", "Application Servers", and one by one select all servers, right mouse click, click on "Start" to start them. This includes "Default Server", "WebSphere Portal", "Everyplace Synchronization Server", "Everyplace Recent Alert Server", "DMS_AppServer", and "DMSconsole_AppServer".

5) At this point you should be able to access all WEA components when you logon at the "(yourmachinename).raleigh.ibm.com/wps/portal" web site.
 
 
 

Starting Intelligent Notification Server:
 
 
 

Installation with Microsoft Active Directory

1) In the "Portal Server " "Selection of LDAP server" panel, select "Microsoft Active Directory", and in the "LDAP Server" field enter "wpspro.raleigh.ibm.com", in the "User DN" field enter "cn=wpsadmin,cn=users,dc=raleigh,dc=raleigh,dc=ibm,dc=com",  in the "User password"  and Confirm password" field enter "wpsadmin", and in the "Suffix" field enter "dc=raleigh,dc=ibm,dc=com", then click "Next".(LDAP Port Number was "389")

2)  In the "LDAP Configuration" panel "User Object Class" field enter "user", in the "User DN Prefix" field enter "cn", in the "User DN Suffix" field enter  "cn=users,dc=raleigh,dc=ibm,dc=com", in the "Group Object Class" field enter "group", in the "Group Member" field enter "member", in the "Group DN Prefix" field enter "cn", in the "Group DN Suffix" field enter "cn=users,dc=raleigh,dc=ibm,dc=com", in the "Administrator DN" field enter "cn=wpsadmin,cn=users,dc=raleigh,dc=ibm,dc=com", and in the "Administrative group DN" field enter "cn=wpsadmins,cn=users,dc=raleigh,dc=ibm,dc=com", then click "Next".
 

3)  At the 13 step portion of the installation, in the "Select Users/Groups - AdminRole" panel, for the "Users", select "CN=wpsadmin,CN=users"   , and for the "Groups", select "CN=wpsadmins,CN=Users, dc=raleigh,dc=ibm,dc=com", and click "OK".

4)  In the "Security Center", click "Apply", and in the "Warning" popup, click "OK".

5)  In the "Security Center" panel, click "OK".  Follow the remaining steps in the "Configuring the Admin Role" section.
 
 
 
 

Installation with iPlanet Directory Server

1) In the "Portal Server " "Selection of LDAP server" panel, select "iPlanet", and in the "LDAP Server" field enter "wpspro.raleigh.ibm.com", in the "User DN" field enter "cn=Directory Manager",  in the "User password"  and Confirm password" field enter "wpstest1", and in the "Suffix" field enter "dc=raleigh,dc=ibm,dc=com", and "LDAP Port Number" was "388", then click "Next".

2)  In the "LDAP Configuration" panel "User Object Class" field enter/accept "inetOrgPerson", in the "User DN Prefix" field enter/accept "uid", in the "User DN Suffix" field enter  "ou=People,dc=raleigh,dc=ibm,dc=com", in the "Group Object Class" field enter "groupOfUniqueNames", in the "Group Member" field enter "uniquemember", in the "Group DN Prefix" field enter "cn", in the "Group DN Suffix" field enter "ou=groups,dc=raleigh,dc=ibm,dc=com", in the "Administrator DN" field enter "uid=wpsadmin,ou=People,dc=raleigh,dc=ibm,dc=com", and in the "Administrative group DN" field enter "cn=wpsadmins,ou=People,dc=raleigh,dc=ibm,dc=com", then click "Next".

3)  In the "Intelligent Notification Services Server" "Select Portal LDAP Type", select "Other LDAP server".

4)  At the 13 step portion of the installation, in the "Select Users/Groups - AdminRole" panel, for the "Users", select "CN=wpsadmin,CN=users"   , and for the "Groups", select "CN=wpsadmins,CN=Users, dc=raleigh,dc=ibm,dc=com", and click "OK".

4)  In the "Security Center", click "Apply", and in the "Warning" popup, click "OK".

5)  In the "Security Center" panel, click "OK".  Follow the remaining steps in the "Configuring the Admin Role" section.

6)  At the "Intelligent Notification Services Server" "Select Portal LDAP Type" panel, select "Other LDAP server" and click "Next".  You will be prompted with a dialog box informing you "If Portal Server is using an LDAP server other than SecureWay Directory, you must import or create Intelligent Notification Services user and group definitions in the directory. Refer to the LDAP documentation for more information and specific instructions", click "OK". Supposedly these have already been added to "wpspro.raleigh.ibm.com" iPlanet directory.
 
 
 
 
 

Uninstalling Everything
 

1) Run the script "/usr/IBMWPO/uninstall/uninstall.sh" giving the build CD1 as the only parameter (i.e. "uninstall.sh   /nasimgs/cd1").

2) In the "Selecting Components", select all that are highlighted, then click "Next".  (Portal Server, WEA Basic Services, WAS, Secureway Server and Client, INS Server, IBMHTTP Server, ESS Servr, DMS Server, DB2 UDS, and the DB2 Fixpack)

3) In the "Previous installatino(s) of component(S)....", all are selected for uninstall, click "Next".

4) In the "Summary" click "Next". Hava a latte'
 
 

Increasing File Sizes

This script contains the commands to increase your file sizes to accomodate the larger build. Note that it only adds to the current size of your file system without knowing or caring what they currently are!

#!/bin/ksh

print "Fixing the /etc/profile -- to resolve stty issue"
cat /etc/profile | sed -e "s/stty erase/#stty erase/g" >/tools/mo.log
mv /tools/mo.log /etc/profile

chfs -a size='+200000' /
chfs -a size='+2400000' /home
chfs -a size='+800000' /tmp
chfs -a size='+1200000' /usr
#usr/sbin/chfs -a size=6553600 /home
usr/sbin/chfs -a size=224000 /home

echo
echo "Filesystem /, /tmp, /usr and /home modified."
echo "Updating /etc/security/limits file"
echo
cp /tools/insv2/shilen/limits /etc/security/limits

echo
echo "Remember to reboot to apply settings"
 
 
 
 
 

Example Mount Script

The following are the contents of a schell script which can be used as is or modified for mounting the build you wish. The important things to consider is the last section, which specifies the machine ("cinta03"), as well as the directory path the build is on ("drive1/421old/install/cd(blahblahbla)").

(by Gary Deen)

#!/usr/bin/ksh
#
# [$1] = Build  I.E. 10220330  - October 22, at 3:30am
# if unspecified, then get the most Current Build
#
REQBUILD="$1"
if [[ "$REQBUILD" = "-?" ]]; then
 print "Format: $0 [OptionalBuildDate]"
 print ""
 print "When OptionalBuildDate is blank, the current build is used."
 print "When an OptionBuildDate is specified, that build is used."
 print "The build is then linked to from \"/nasimgs\"."
 print "Change directories into \"/nasimgs/cd1\" to start a build."
 print
 print "Available builds:"
 ls /tools/WEA_R421
 exit 3
fi
PROGDIR=$(/usr/bin/dirname $0)
#
# run nfsc to connect to cinta03, until the builds no longer
# need the cinta03 images.
#
#$PROGDIR/nfsc1

function rmlinks
{
#
# Clean up any previous nasimgs directory, and set to empty
#
MYDIR="$1"
#print /usr/bin/mkdir -p $MYDIR
/usr/bin/mkdir -p $MYDIR 2> /dev/null
MDIRLIST=$(/usr/bin/ls $MYDIR)
for MDIR in $MDIRLIST ;
do
# print /usr/sbin/unlink $MYDIR/$MDIR
 /usr/sbin/unlink $MYDIR/$MDIR
done
}

function mountnas
{
#
# Mount the Network Attached Share with the builds at /nas
#
if [[ -d "/nas" ]]; then
 :
else
 print "No /nas"
#fi
#cd /nas 2>/dev/null
#CIWD2=`cd /nas 2>/dev/null && /usr/bin/pwd`
#cd - 2> /dev/null
#print $CIWD2

#if [[ "$CIWD2" != "/nas" ]]; then
 print usr/bin/mkdir /nas
 /usr/bin/mkdir /nas 2>/dev/null
fi
ISMOUNT=$(/usr/sbin/mount | /usr/bin/grep "nas" | /usr/bin/awk 'BEGIN{}
/nas300/ {print $3 };
END{}')
if [[ $ISMOUNT = "" ]]; then
 print /usr/sbin/mount -o ro nas300:/staging /nas
 /usr/sbin/mount -o ro nas300:/staging /nas
fi
}

function stripdotdot
{
string1="$1""/"
string2="$2"
#print $string1$string2
while [[ "`print $string2 | /usr/bin/head -c 3`" = "../" ]]; do
        #
        # remove "../" from front of string 2
        #
        WC=`print $string2|/usr/bin/wc -c`
        ((WC2 = WC - 3))
        MYLINK2=`print $string2|/usr/bin/tail -c $WC2`
        string2="$MYLINK2"
        #
        # remove last "/directory" from string1
        #

        junkstring1=`echo $string1 | /usr/bin/awk 'BEGIN { RS="/"; OSTR="";LAST="";LAST2=""}
                {
                OSTR=OSTR LAST2
                LAST2=LAST
                LAST=$1"/"
                }
        END{ print OSTR }'`
        string1=$junkstring1
done
        print $string1$string2
}

#
#
#
function linkdir
{
 #
 # $1 "Directory which contains links"
 # $2 "directory in which to copy these links."
 #
 # This routine will copy all of the links in a directory into another
 # directory. If the original directory contains links that are "../..",
 # then the links will be correctly repaired to not contain them.
 #

 #
 # for all images in NAS, make a link file to them
 #
 BUILDDIR="$1" # usually /nas/WEA_R421/CurrentBuild/cdlinks
 DESTDIR="$2" # usually /nasimgs

 cd $BUILDDIR 1>&2 2>/dev/null
 CWD=`/usr/bin/pwd`
 if [[ "$CWD" != "$BUILDDIR" ]]; then
  print
  print "cd $BUILDDIR has failed. Check mounts."
  exit 3
 fi

 FILES=`/usr/bin/ls .`
 cd - 1>&2 2> /dev/null
 print "Linking Build directories " $FILES

 for MDIR in $FILES ;
 do
  #MDIR == cd1
  MYLINK=`/usr/bin/ls -la $BUILDDIR/$MDIR | /usr/bin/awk 'BEGIN{}
   {print $11}
   END{}'`
  #MYLINK == "../../10230303/cdimg/cd1" or "/nas/WEA_R421/10230202/cdimg/cd1"
  if [[ `echo $MYLINK | /usr/bin/head -c 1` = '/' ]]; then
   /usr/bin/ln -s $MYLINK $DESTDIR/$MDIR
   echo 1 /usr/bin/ln -s $MYLINK $DESTDIR/$MDIR
  else
   MYLINK2=`stripdotdot "$BUILDDIR" "$MYLINK"`
   /usr/bin/ln -s $MYLINK2 $DESTDIR/$MDIR
   echo 2 /usr/bin/ln -s $MYLINK2 $DESTDIR/$MDIR
  fi
 done
}

function getrelease
{
MYDIR="$1"
cd $MYDIR 1>&2 2>/dev/null
if [[ "$(pwd)" != "$MYDIR" ]]; then
        print "MOUNT failed."
        exit 3
fi
RELEASE=`/usr/bin/ls | /usr/bin/grep [0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]`
#cd - 1>&2 2> /dev/null
print $RELEASE
}
 

function fixupmissing
{
 #
 # for all directories in Jims Mounted last good build, get a link
 # this is because not all CDs are rebuilt at each build.
 #

 NEWDIR=$1
 cd /WEA/new 1>&2 2>/dev/null
 MFILES=`/usr/bin/ls .`
 cd - 1>&2 2> /dev/null

 for MDIR in $MFILES ;
 do
  if [[ -h "$NEWDIR/$MDIR" ]]; then
    :
  else
   print "Linking OLD build directories " $MDIR
   /usr/bin/ln -s /WEA/new/$MDIR $NEWDIR/$MDIR
   echo 3 /usr/bin/ln -s /WEA/new/$MDIR $NEWDIR/$MDIR
  fi
 done
}

if [[ "$REQBUILD" = "" ]]; then
 rmlinks /nasimgs
 mountnas
 linkdir "/nas/WEA_R421/CurrentBuild/cdlinks" "/nasimgs"

# fixupmissing "/nasimgs"

 RELEASE=`getrelease /nasimgs/cd1`
 cd - 1>&2 2> /dev/null
 if [[ -d "/tools/WEA_R421/$RELEASE" ]]; then
  :
 else
  rmlinks "/tools/WEA_R421/$RELEASE"
  linkdir "/nas/WEA_R421/CurrentBuild/cdlinks" "/tools/WEA_R421/$RELEASE"
#  fixupmissing "/tools/WEA_R421/$RELEASE"
 fi
else
 #
 # User typed in a build date for an argument.
 # Try and find this build date from a list of valid builds saved in /tools/gdeen/builds/WEA_R421
 #
 if [[ -d "/tools/WEA_R421/$REQBUILD" ]]; then
  rmlinks /nasimgs
  mountnas
  linkdir "/tools/WEA_R421/$REQBUILD" "/nasimgs"
 else
  print "Build Requested is not in /tools/WEA_R421"
  exit 3
 fi
fi
RELEASE=`getrelease /nasimgs/cd1`
print ""
print "CD /nasimgs/cd1 for the latest $RELEASE build"
 

(OR)  $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
 
 

#!/bin/ksh

print  Fixing AIX/Linux Issue....
nfso -o nfs_use_reserved_ports=1
 

function mymount
{
echo Mounting $1 as $2
mkdir -p $2
/usr/sbin/mknfsmnt -f $2 -d $1 -h cinta03.raleigh.ibm.com -n -B -A -t ro -w bg -r 10 -Y -Z -X -H -j -q -g
}
echo  Mounting "cinta03 drive1/421"....

mymount /drive1/421/install/cd1 /WEA/new/cd1
mymount /drive1/421/install/cd2-1 /WEA/new/cd2-1
mymount /drive1/421/install/cd2-2 /WEA/new/cd2-2
mymount /drive1/421/install/cd2-3 /WEA/new/cd2-3
mymount /drive1/421/install/cd2-4 /WEA/new/cd2-4
mymount /drive1/421/install/cd2-5 /WEA/new/cd2-5
mymount /drive1/421/install/cd2-6 /WEA/new/cd2-6
mymount /drive1/421/install/cd2-7 /WEA/new/cd2-7
mymount /drive1/421/install/cd3 /WEA/new/cd3
mymount /drive1/421/install/cd4 /WEA/new/cd4
mymount /drive1/421/install/cd5 /WEA/new/cd5
mymount /drive1/421/install/cd6 /WEA/new/cd6
mymount /drive1/421/install/cd7 /WEA/new/cd7
mymount /drive1/421/install/cd8 /WEA/new/cd8
mymount /drive1/421/install/cd9 /WEA/new/cd9