5.10.9.1 CASINSTL LCU
Command File Syntax
5.10.9.1 CASINSTL LCU
Command File Syntax
The following sections describe the process components of Phase One.
If you need to have better resolution or more colors than the default 640x480x16 setup, you should install the appropriate display driver.
The program that installs alternative display drivers is called DSPINSTL.
| DSPINSTL Syntax |
|---|
|
DSPINSTL.EXE /PD:<.DSC_file> /T:<boot_drive> /S:<source_drive> /RES:<resolution> /U |
If you have a system where the video chip set can be
automatically detected, then you can use the auto-detect option. If you do not
know whether your hardware can be auto-detected, we recommend that you try it
out.
If your video adapter is not supported by OS/2 Warp Server for e-business with a display driver shipped with the product, you can try to use the Generic Non-accelerated GRADD driver, or you can use the OS/2 display drivers that came with your adapter. In this case, refer to the CID installation instructions that came with the display drivers for assistance.
For full details of the syntax of DSPINSTL, refer to The OS/2 Warp 4 CID Software Distribution Guide, SG24-2010&CID. or &CID..
In our working example, the invocation of DSPINSTL, as provided in
our LCU client command file, is as follows. It auto-detects the display adapter
chipset and sets a screen resolution of 800x600x256.
x.SVGA = 7
x.7.name = 'SVGA'
x.7.statevar = 'CAS_' || x.7.name
x.7.instprog = 'dspinstl',
' /s:'OS2img,
' /t:'bootdrive,
' /res:800x600x256',
' /auto',
' /u'
x.7.rspdir = ''
x.7.default = ''
|
The variable OS2img has already been explained.
As previously mentioned, some components that belong to the base OS/2 operating system are installed by &Feature.. After the initial installation using SEINST and following a reboot, the Presentation Manager interface is active. With this prerequisite fulfilled, CLIFI.EXE can be used to complete the update.
Since CLIFI and SEINST share the partial response file for keywords of the Component.Selection type, we can still use the same file from Phase One.
The general response file for this invocation of CLIFI is FIBASE.RSP, which can be found in the \OS2\INSTALL directory of the boot drive.
| CLIFI CID Installation Syntax |
|---|
|
CLIFI /A:C /S:<source_path> /B:<boot_drive> /F:<boot_drive>\OS2\INSTALL /R:<generic_response_file> /R2:<partial_response_file> /L1:<error_log_file> /L2:<history_log_file> |
For a description of &Feature., please refer to Section 5.7.6 Introducing &Feature. Installer.. For full details of the syntax of CLIFI, refer to The OS/2 Warp 4 CID Software Distribution Guide, SG24-2010&CID..
| Important Note |
|---|
|
When CLIFI.EXE is invoked during the Phase Two, it installs Systems Management by default. This is required for many other applications, such as Communications Server. Therefore, it is advisable to call CLIFI.EXE at least once, as soon as possible, after installing the OS/2 2.11. |
In our working example, the invocation of CLIFI, as provided in our
LCU client command file, is as follows:
x.FIbase = 4
x.4.name = 'Feature Install 1.2.3 - base components'
x.4.statevar = 'CAS_' || x.4.name
x.4.instprog = 'CLIFI.EXE',
' /s:'OS2img'\FI',
' /a:C',
' /b:'bootdrive,
' /r:'bootdrive'\OS2\INSTALL\FIBASE.RSP',
' /f:'bootdrive'\OS2\INSTALL',
' /l1:'logdir'\'client'.FIerr',
' /l2:'logdir'\'client'.FIlog',
' /r2:'
x.4.rspdir = resdir'\OS2\'
x.4.default = 'server.rsp'
|
Where variable OS2img has already been explained.
The working response file used in our environment is
shown below. We have included only those parts of the response
file that are specific to Feature Installer because the
base OS/2 response file is already illustrated in
Figure 57.
PRINTERUTIL.Selection=0 PUHPJETCLIENT.Selection=0 PUHPJETCLIENT.TarDrv=d: PUHPJETSERVER.Selection=0 PUHPJETSERVER.TarDrv=d: PUMARKNET.Selection=0 PUMARKNET.TarDrv=d: PUMARKVIS.Selection=0 PUMARKVIS.TarDrv=d: HOTPLUG.Selection=0 WARMSWAP.Selection=0 WARMSWAP.ThinkPad=IBM ThinkPad 755CD/CDV WARMSWAP.ThinkPad=IBM ThinkPad 760C/CD WARMSWAP.ThinkPad=IBM ThinkPad 760E WARMSWAP.ThinkPad=IBM ThinkPad 760ED WARMSWAP.ThinkPad=IBM ThinkPad 760EL/ELD WARMSWAP.ThinkPad=IBM ThinkPad 760X/XD WARMSWAP.S506Parm=/A:1 /U:0 WARMDOCK.Selection=0 WARMDOCK.ThinkPad=IBM ThinkPad 755CD/CDV WARMDOCK.ThinkPad=IBM ThinkPad 755CE/CSE/CV/CX WARMDOCK.ThinkPad=IBM ThinkPad 760C/CD WARMDOCK.ThinkPad=IBM ThinkPad 760E WARMDOCK.ThinkPad=IBM ThinkPad 760ED WARMDOCK.ThinkPad=IBM ThinkPad 760EL/ELD WARMDOCK.ThinkPad=IBM ThinkPad 760X/XD |
Java11.RunDrv=d: Java11.Selection=1 runtime.selection=1 runtimeconfig.selection=1 samples.selection=0 samplesconfig.selection=0 samples.smpdrv=d: samples.smppath=\JAVA11 toolkit.selection=0 toolkitconfig.selection=0 toolkit.tktdrv=d: toolkit.tktpath=\JAVA11 tlktdoc.selection=0 tlktdocconfig.selection=0 tlktdoc.tdocdrv=d: tlktdoc.tdocpath=\JAVA11 debugger.selection=0 debuggerconfig.selection=0 debugger.dbgdrv=d: debugger.dbgpath=\JAVA11\ICATJAVA IBMFONTA.Selection=0 IBMFONTG.Selection=0 IBMFONTT.Selection=0 IBMFONTJ.Selection=0 IBMFONTC.Selection=0 IBMFONTS.Selection=0 IBMFONTK.Selection=0 IBMFONTU.Selection=1 XIBMFONT.InstDrive=d: LVMGUI.Selection=1 |
The most important difference between this and the previous versions of OS/2 LAN or Warp Server is that LANINSTR (the File and Print Sharing Services installation program) no longer installs 386 HPFS. However, the parameters of LANINSTR remain unchanged.
| Note |
|---|
|
At the time of writing, following a pristine installation, the MAXCONNECTIONS parameter was not installed, and this prevented the server service from starting. A manual addition was required to overcome this problem. We expect that this will be fixed by the time the final product is available. |
| LANINSTR Syntax |
|---|
LANINSTR /<type> /R:<response_file> /G:<included_rsp_files> /L1:<error_log> /L2:<history_log> |
For full details of the syntax of LANINSTR, refer to &CID.The OS/2 Warp 4 CID Software Distribution Guide, SG24-2010 or &CID..
In our working example, the invocation of LANINSTR, as provided in
our LCU client command file, is as follows:
x.lanserver = 3
x.3.name = 'LAN Server 5.2'
x.3.statevar = 'CAS_' || x.3.name
x.3.instprog = LSRimg'\laninstr',
' /l1:'logdir'\'client'.lsr',
' /srv',
' /r:'
x.3.rspdir = resdir'\LSR\'
x.3.default = 'lansrv.rsp'
|
Where the LSRimg variable is defined as:
LSRimg = imgdir'\LSR\IP08700'
The working response file used in our environment is
shown in Figure 71.
DELETEIBMLAN = Networks< net3 = net4 = netlb = > UPDATEIBMLAN = Networks< net1 = NETBEUI$,*,LM10,*,*,* net2 = TCPBEUI$,*,LM10,*,*,* > DELETEIBMLAN = Requester< wrknets = NETLB,NET3,NET4 > UPDATEIBMLAN = Requester< Computername = SRV163 Domain = D01 useallmem = Yes |
ADDIBMLAN = Requester< wrkservices = MESSENGER wrknets = NET1, NET2 > DELETEIBMLAN = Server< srvservices=ALERTER,DCDBREPL,NETRUN,REMOTEBOOT,REPLICATOR,UPS srvnets = NETLB, NET3, NET4 > UPDATEIBMLAN = Server< autopath = \IBMLAN\PROFILES\SRVAUTO.PRO > ADDIBMLAN = Server< SrvServices = LSSERVER, NETLOGON srvnets = NET1, NET2 > ConfigApplDumpPath = Migrate ConfigApplMaxDumps = Migrate ConfigAutoStartFFST = YES ConfigAutoStartLS = No ConfigCopyDLR = CopyIfRequired ConfigCopyLSP = CopyIfRequired ConfigDisplayMsg = ON ConfigDosNumber = 0 ConfigMsgLogName = Migrate ConfigRouteAlertsTo = NETVIEW ConfigServerType = AdditionalServer ConfigSourceDrive = None ConfigSystemDumpPath = d:\OS2\SYSTEM ConfigSystemMaxDumps = 32 ConfigTargetDrive = D ConfigWsId = DC01 ConfigWsSerial1 = Migrate ConfigWsSerial2 = Migrate ConfigWsType1 = Migrate ConfigWStype2 = Migrate InstallDosLanApi = REMOVE InstallDosRemoteIPL = REMOVE InstallGenericAlerter = INSTALL InstallInstallProgram = REMOVE InstallLoopBackDriver = REMOVE InstallOS2RemoteIPL = REMOVE InstallServer = INSTALL InstallUPM = INSTALL InstallUps = REMOVE InstallMSGPopup = REMOVE InstallGUI = REMOVE InstallClipBoard = REMOVE InstallDesktopIcons = YES |
Please note that the response file shown in Figure 72 contains the line:
ConfigServerType = AdditionalServer
Be sure to change this to the appropriate value if you are migrating a Domain Controller or Backup Domain Controller. You will also change the performance and capacity parameters according to your needs.
| General Tip |
|---|
|
In general, don't install a Primary Domain Controller when introducing a server into an existing domain. Always install it as a Backup Domain Controller and then promote it to Primary Domain Controller as required. |
Because 386 HPFS is now shipped as a separate product, it is no longer installed by LANINSTR.
| Installing |
|---|
|
If you are migrating a server using CID, make sure that you install 386 HPFS directly after File and Print Sharing Services before rebooting the machine. Otherwise, you will have problems rebooting the system. |
If you are currently licensed for 386 HPFS, you do not need to repurchase it, but make sure to request the 386 HPFS Update package, which is licensed as a separate product from OS/2 Warp Server for e-business. During the installation of the base OS/2 operating system, the 386 HPFS file system drivers are detected and removed. However, before rebooting, you will reinstall 386 HPFS.
The 386 HPFS installation, and that of features, such as Fault Tolerance and Local Security, are now performed by &Feature.. For a description of &Feature., please refer to Section 5.7.6 Introducing &Feature. Installer..
The following figure shows the portion of the LCU file where 386 HPFS is
installed.
x.fs386 = 10
x.10.name = 'HPFS386'
x.10.statevar = 'CAS_' || x.10.name
x.10.instprog = 'CLIFI.EXE',
' /s:'FS386img,
' /a:C',
' /b:'bootdrive,
' /r:'FS386img'\fs386.rsp',
' /f:'bootdrive'\OS2\INSTALL',
' /l1:'logdir'\'client'.fs386err',
' /l2:'logdir'\'client'.fs386log',
' /r2:'
x.10.rspdir = resdir'\FS386\'
x.10.default = 'fs386def.rsp'
|
Where the variable FS386img is defined as:
FS386img = imgdir'\KAAJNYH\IP08600'
The working response file used in our environment is shown in Figure 74. It can be used when migrating an existing 386 HPFS installation. In this example, Fault Tolerance and Local Security are configured, thus, the corresponding variables are set to 1.
Please note that &Feature. always requires two response files, one of which is provided by the software manufacturer.
For 386 HPFS, this response file is called FS386.RSP, located in the \<language>\HPFS386 (such as \EN\HPFS386) directory on the 386 HPFS Update CD ROM. It contains the description of all files required to install the product. Do not change this file. The other file (in our example in Figure 74) is provided by the user and contains user-specific settings.
If you do not already have 386 HPFS installed, and since 386 HPFS is available separately from OS/2 Warp Server for e-business, you will need to have a license diskette or some other proof of license (such as a copy of the Warp Server Advanced CD) in order to install it.
In a CID installation, it does not make sense to have to insert a license diskette during the installation process. Therefore, there is a keyword in the response file that replaces the proof of license.
If you have a valid license, please specify the following Keyword=Value pair in your response file:
HPFS386_Top.HAVEADVANCELICENSE=AGREE
Most of the other keywords are used to set the 386 HPFS
tuning parameters that are found in HPFS386.INI after the installation. You can
modify these according to your needs.
Install386HPFS.Selection=0 InstallFaultTolerance.Selection=1 InstallLocalSecurity.Selection=1 WkStaDeterminesCacheSize.Selection=0 WkStaDeterminesHeapSize.Selection=0 ConfigLazyWrite.Selection=1 HPFS386_Top.Config386Cache=512 HPFS386_Top.ConfigHeap=756 HPFS386_Top.ConfigMinBufferIdle=550 HPFS386_Top.ConfigMaxCacheAge=5050 HPFS386_Top.ConfigUseAllMem=Yes HPFS386_Top.HAVEADVANCELICENSE=Agree HPFS386_Top.InstallDrive=D: HPFS386_Top.isIntegratedInstall=NO |
In a CID environment, FFST/2 must be installed in a separate step. The installation program is called FFSTINST.EXE.
| FFSTINST Syntax |
|---|
FFSTINST /L1:<log_file> /S:<source_path> /ROUT:<code> |
In our working example, the invocation of FFSTINST, as provided in
our LCU client command file, is as follows:
x.FFST = 15
x.15.name = 'FFST'
x.15.statevar = 'CAS_' || x.15.name
x.15.instprog = FFSTimg'\ffstinst.exe',
' /s:'FFSTimg,
' /l1:'logdir'\'client'.ffst',
' /rout:1'
x.15.rspdir = ''
x.15.default = ''
|
Where the variable FFSTimg is defined as:
FFSTimg = imgdir'\FFST\WR00530'
| Note |
|---|
|
The /ROUT parameter defines the system where alerts will be sent. A value of 1 means NetView, a value of 2 states that LAN Network Manager should receive the message. A value of 0 means no alerts will be sent. |
The installation of FFST/2 needs no response file.
Previous versions of TCP/IP used INSTALL.EXE for installation. From Version 4 onwards, the installation program changed to Feature Installer. The procedures and response file we have provided represent a working version and use Feature Installer.
We strongly recommend that you use the &Feature. to install these components even though the program INSTALL.EXE still exists. INSTALL.EXE displays dialog boxes on the screen and waits for user interaction to click mouse buttons when it encounters a problem, which is not acceptable in a CID-based installation. In addition, INSTALL.EXE requires Netscape Communicator.
For further detail on the installation of TCP/IP Application Services refer to the README.CID or the \CID\SERVER\TCPAPPS directory on the OS/2 Warp Server for e-business CD-ROM.
Please note that the installation of TCP/IP Services requires Java to be installed.
In our working example, the invocation of the TCP/IP installation, using
Feature Installer, as provided in our LCU client command file, is as follows:
x.TCPIP = 5
x.5.name = 'TCP/IP Application Suite 4.21'
x.5.statevar = 'CAS_' || x.5.name
x.5.instprog = 'CLIFI.EXE',
' /s:'TCPIPimg'\install',
' /a:C',
' /b:'bootdrive,
' /r:'TCPIPimg'\install\tcpinst.rsp',
' /f:'bootdrive'\OS2\INSTALL',
' /l1:'logdir'\'client'.TCPIPerr',
' /l2:'logdir'\'client'.TCPIPlog',
' /r2:'
x.5.rspdir = resdir'\TCPIP\'
x.5.default = client'.rsp'
|
Where the variable TCPIPimg is defined as:
TCPIPimg = imgdir'\TCPIP\UN02100'
The working response file used in our environment
is shown in a series of figures beginning with
Figure 77 through Figure 80.
* TCPIP.InstallDir=D:\TCPIP
TCPIP.InstallDrive=D:
* TARGET_DRIVE=D:
* LOG_PATH1=C:\TCPINST.LOG
* LOG_PATH2=C:\TCPINST2.LOG
* INSTALL_MODE=UNATTENDED
* BOOT_DRIVE=D:
*** needed to install NFS -> to put cfg files in \ETC
TCPIP.MPTS_PATH=D:\MPTN
* MPTS_RSP_FILE=D:\INSTALL\MPTS\MY.RSP
* CONFIG_NO_INSTALL=N
*** needed for DHCP ??? ***
SERVER_YorN=Y
LANG=ENUS
CODEPAGE=850
PACKAGES = (
BASE_APPS = Y
DHCP_DDNS_Server = Y
UINSTAL = Y
VPN = Y
IFOLDER = Y
NFS = Y
)
|
IP_FORWARDING=N
USE_HOSTS_FIRST=Y
INETD=(
AUTOSTART=Y
AUTOSTART_TYPE=START_MIN
)
TELNETD=(
AUTOSTART=Y
AUTOSTART_TYPE=START_MIN
)
FTPD=(
AUTOSTART=Y
AUTOSTART_TYPE=INETD
PARAMETERS=-l
)
TFTPD=(
AUTOSTART=N
AUTOSTART_TYPE=INETD
)
REXECD=(
AUTOSTART=Y
AUTOSTART_TYPE=INETD
)
RSHD=(
AUTOSTART=Y
AUTOSTART_TYPE=INETD
)
LPD=(
AUTOSTART=N
AUTOSTART_TYPE=INETD
)
LPRPORTD=(
AUTOSTART=N
AUTOSTART_TYPE=START_MIN
)
ROUTED=(
AUTOSTART=N
AUTOSTART_TYPE=DET
)
PORTMAP=(
AUTOSTART=N
AUTOSTART_TYPE=DET
)
SENDMAIL=(
AUTOSTART=N
AUTOSTART_TYPE=START_NORM
)
)TALKD=(
AUTOSTART=N
|
)
RSVPD=(
AUTOSTART=N
AUTOSTART_TYPE=DET
)
TCPCFG2D=(
AUTOSTART=N
AUTOSTART_TYPE=DET
)
SYSLOGD=(
AUTOSTART=Y
)
USERNAME=usr146
TZ=CST6CDT
ADMIN_PW=12345
SERVER_USER=(
USERNAME=admin
PASSWORD=12345
UID=0
GID=0
COMMENT=New admin
HOMEDIR=D:\
TELNETD=(
ACTIVE=Y
SHELL=telnetd.cmd
DISCONNECT=Y
)
REXECD=(
ACTIVE=Y
)
FTPD=(
ACTIVE=Y
READ_DIR=D:\
CANREAD=Y
WRITE_DIR=D:\
CANWRITE=Y
IDLETIMEOUT=2000
)
)
SERVER_USER=(
USERNAME=guest
PASSWORD=guest
UID=1
GID=1
HOMEDIR=D:\GUEST
FTPD=(
ACTIVE=Y
READ_DIR=D:\GUEST
CANREAD=Y
CANWRITE=N
LOG=LOGDEL LOGREN LOGPUT
)
)
|
RSH_USER=(
HOSTNAME=rshhost
DOMAIN=raleigh.ibm.com
USERNAME=rshuser
)
TFTP_ACCESS=(
DIRECTORY=D:\TFTP
READ_ONLY=N
HOSTNAME=tftphost
)
ENABLE_SOCKS=Y
SOCKS_USERID=srv146
SOCKS_DOMAIN=(
DOMAIN1=
DOMAIN2=
DOMAIN3=
)
SOCKS_NAMESERVER=(
DOMAIN1=
DOMAIN2=
DOMAIN3=
)
DIRECT_ROUTES=(
DESTINATION=
NETMASK=
)
SOCKD_SERVER=(
SERVER=
DESTINATION=
NETMASK=
)
*REMOTE_PRINT_SERVER=printer1
*REMOTE_PRINTER=lpt1
MAX_LPD_PORTS=12
|
| Note on TCP/IP Installation |
|---|
|
You will note that some of the keywords are commented out. At the time of writing, we were able to install the product successfully using the keyword TCPIP.InstallDrive. This may change by the time the product becomes generally available. We recommend that you check the on-line documentation and the README.CID for the latest advice. |
Depending on your configuration, you may or may not already have Netscape, Version 2.02 installed on your system. If it does not exist on your system, Netscape Communicator is installed. If you already have it, then updating Netscape Navigator 2.02 to Netscape Communicator 4.04 can be a two-step process depending on whether a Plug-In is needed. A Plug-In provides additional functionality when browsing the World Wide Web.
Netscape Communicator is installed using Software Installer. The basic product is installed by the installation program INSTALL.EXE in the \CID\SERVER\NETSCAPE directory on the OS/2 Warp Server for e-business CD-ROM).
| Netscape Install Syntax |
|---|
INSTALL /X /A:I /NMSG /O:DRIVE /R:responsefile /L2:outputfile |
The above syntax is valid for a new installation. If you already have a copy of Netscape installed, you need to substitute the Action (/A) parameter keyword Install (I) for Update (U). Therefore, the new syntax would read:
INSTALL /X /A:U /NMSG /O:DRIVE /R:responsefile /L2:outputfile
For further information on installing Netscape Navigator, refer to the READ.ME file in the \CID\SERVER\NETSCAPE directory of the OS/2 Warp Server for e-business CD-ROM.
| Note on Plug-Ins |
|---|
|
We recommend that multimedia Plug-Ins not be installed on a server. We have included their installation here only for completeness. |
If the Plug-In is needed, it can be copied to the Plug-In directory by simply issuing a COPY command as follows:
COPY X:\SOURCE\NPFI.DLL Y:\TARGET\PROGRAM\PLUGINS
where X:\SOURCE represents the source directory, and Y:\TARGET is the directory in which you installed Netscape Communicator.
| Note on COPY Command |
|---|
|
Since COPY does not return a valid CID return code, we recommend that you create a REXX command file that calls both the installation program and the COPY command and then returns a correct value. |
In our working example, the invocation of the Netscape Navigator
installation as provided in our LCU client command file is as follows:
x.Netscape = 6
x.6.name = 'Netscape Communicator for OS/2 4.04'
x.6.statevar = 'CAS_' || x.6.name
x.6.instprog = NSimg'\install.exe',
' /x',
' /a:i',
' /o:drive',
' /l1:'logdir'\'client'.NSl1',
' /l2:'logdir'\'client'.NSl2',
' /r:'
x.6.rspdir = resdir'\netscape\'
x.6.default = 'netscape.rsp'
|
where the variable NSimg is defined as:
NSimg = imgdir'\NETSCAPE\OS2\XR00404'
The working response file used in our environment
is shown in Figure 82.
COMP = Netscape Communicator 4.04 for OS/2 FILE = D:\netscape AUX1 = D: DELETEBACKUP = Yes SAVEBACKUP = No CFGUPDATE = Auto OVERWRITE = Yes NSCONVERTBROWSER = Yes NSCONVERTQL = Yes NSASSOCIATEHTML = YES |
Like many other products, Personally Safe 'n' Sound is installed by the &Feature.. The use of &Feature. is described in detail in Section 5.7.6 Introducing &Feature. Installer..
| PSNS Install Syntax |
|---|
CLIFI /A:C /R2:PSNSCID.RSP /R:PSNS.RSP /B:C: /S:D:\PSNSTEMP /L1:CIDERR.LOG /L2:CIDHIST.LOG |
For further information on the installation of PSnS, please refer to the on-line documentation or the \CID\SERVER\PSNS directory on the OS/2 Warp Server for e-business CD-ROM.
In our working example, the invocation of the PSnS installation, used by
Feature Installer as provided in our LCU client command file, is as follows:
x.PSnS = 12
x.12.name = 'Warp Server Backup/Restore 6.0'
x.12.statevar = 'CAS_' || x.12.name
x.12.instprog = 'CLIFI.EXE',
' /s:'PSNSimg,
' /a:C',
' /b:'bootdrive,
' /r:'PSNSimg'\PSNS.rsp',
' /f:'bootdrive'\OS2\INSTALL',
' /l1:'logdir'\'client'.PSnSerr',
' /l2:'logdir'\'client'.PSnSlog',
' /r2:'
x.12.rspdir = resdir'\PSNS\'
x.12.default = 'PSNSdef.rsp'
|
where the variable PSNSimg is defined as:
PSNSimg = imgdir'\PSNS\3009103'
The working response file used in our environment is
shown in Figure 84.
PSNS.InstDrive=D: PSNS.InstDir=\PSNS PSNS_GUI.Selection=1 PSNS_CAPI.Selection=1 PSNS_CLI.Selection=1 PSNS_RAPI.Selection=1 PSNS_ADSM.Selection=0 PSNS_DISK.Selection=1 PSNS_LAN.Selection=0 PSNS_OPTICAL.Selection=0 PSNS_PRM.Selection=0 PSNS_REMDRV.Selection=0 PSNS_TAPE.Selection=1 |
Remote Access Services (also known as PPP Server) replaces the LAN Distance product. LAN Distance must be removed with the LDREMOVE command prior to installation of Remote Access Services.
It, therefore, takes three steps to migrate LAN Distance to the new Remote Access PPP server. First, LDREMOVE must be run to remove LAN Distance Connection Server before installing the RAS server.
Since LAN Distance Connection Server is deleted, please make a backup of your configuration files prior to installation. After installing the RAS Server, it can be configured using the previously saved configuration.
For further information on the configuration files to be saved and other preparation steps needed in this area, please refer to Section 3.10 Remove LAN Distance.
In our working example, the invocation of the RAS installation as provided
in our LCU client command file is as follows:
x.PPPsrv = 9
x.9.name = 'PPP server'
x.9.statevar = 'CAS_' || x.9.name
x.9.instprog = PPPimg'\lo510a1\install.exe',
' /r:'
x.9.rspdir = resdir'\PPPsrv\'
x.9.default = 'ld_svr.rsp'
|
where the variable PPPimg is defined as:
PPPimg = imgdir'\PPPSRV\XR09999'
The working response file used in our
environment is shown in Figure 86.
Target = D:\ WorkStationType = SERVER |
PSF/2 allows you to print file formats that your printer typically does not support.
We needed to implement a two-stage installation of PSF/2. This has been implemented in one command file called PSF2PREP.CMD located in the \IBMINST directory of the OS/2 Warp Server for e-business Server Pak CD-ROM. This procedure first copies the source files to a local drive. It then calls the INSTALL program through the LCU batch procedure.
We found that if write access was not provided to the existing \PSF2\INSTALL directory on the server, then the installation would fail.
In our working example, the invocation of the PSF/2 installation as provided
in our LCU client command file is as follows:
x.PSFprep = 13
x.13.name = 'IBM PSF/2 Prep'
x.13.statevar = 'CAS_' || x.13.name
x.13.instprog = cmddir'\PSF2prep.cmd',
' 'imgdir,
' 'psftgtpath
x.13.rspdir = ''
x.13.default = ''
|
where the variable psftgtpath is defined as:
psftgtpath = 'D:'
The variable here is D: in this case only. This variable is
set in the LCU batch procedure and might be different depending on your
environment.
x.PSF2 = 14
x.14.name = 'IBM PSF/2'
x.14.statevar = 'CAS_' || x.14.name
x.14.instprog = psftgtpath'\PSF2\INSTALL\install.exe',
' /a:i',
' /x',
' /s:'PSF2img,
' /o:DRIVE',
' /p:"PSF/2 - Install SERVER"',
' /t:'psftgtpath,
' /L1:'logdir'\'client'.PSFl1',
' /L2:'logdir'\'client'.PSFl2',
' /L3:'logdir'\'client'.PSFl3',
' /r:'
x.14.rspdir = resdir'\psf2\'
x.14.default = 'psf2srv.rsp'
|
where the variable PSF2img is defined as:
PSF2img = imgdir'\PSF2\XR09999'
The working response file used in our
environment is shown in Figure 89.
FILE=D: AUX1=D:\PSF2\INSTAll AUX2=D: COMP=PSF/2 SERVER - BASE FILES COMP=* - RESOURCE LIBRARY COMP=* - PARALLEL ATTACHED DEVICES COMP=* - CODEDFONTS COMP=* - TCP/IP ATTACHED DEVICES COMP=* - TRANSFORMS COMP=* - 300 dpi COMPATABILITY FONTS COMP=* - POSTSCRIPT CFGUPDATE=AUTO OVERWRITE=NO DELETEBACKUP=NO SAVEBACKUP=NO |
Netfinity Manager and Client Services are highly responsive hardware management features that support key systems management tasks.
| Netfinity Services |
|---|
NETFINST.EXE /S:<source_drive> /L1:<error_log_file> /L2:<history_log_file> /R:<response_file> |
For further information on the installation of Netfinity Services, refer to the separate Netfinity Services CD that came with the OS/2 Warp Server for e-business package.
In our working example, the invocation of the Netfinity Services
installation as provided in our LCU client command file is as follows:
x.NetFinity = 23
x.23.name = 'NetFinity 5.20.2 Passive Services'
x.23.statevar = 'CAS_' || x.23.name
x.23.instprog = NETFINimg'\services\netfinst.exe',
' /s:'NETFINimg'\services',
' /l1:'logdir'\'client'.NFl1',
' /l2:'logdir'\'client'.NFl2',
' /r:'
x.23.rspdir = resdir'\NETFIN\'
x.23.default = client'.rsp'
|
where the variable NETFINimg is defined as:
NETFINimg = imgdir'\NETFIN\ver5202\OS2'
The working response file used in our
environment is shown in Figure 91.
Package = Passive Options = RWC, WebManager InstallTo = \NETFIN ChangeConfig = TRUE RouteNMVT = FALSE Driver.TCPIP = 1 Driver.NETBIOS = 0 Driver.NETBIOS2 = 0 Driver.IPX = 0 Driver.SERIPC = 0 Driver.SNA_APPC = 0 ;Parm1.NETBIOS = MACHINE1 ;Parm1.NETBIOS2 = MACHINE2 ;Parm1.SERIPC = MACHINE1 Keyword.1 = Server ;NetTimeout = 15 SystemName = SRV163 ;ForceRemoteLogons = 1 ;ServiceAlerts = 1 ;ShowSupportProgram = 1 ;ReqUserAuthToScreen = 1 ;DisableDNSNameResolution = 1 |
In our working example, the invocation of the LDAP Client Toolkit
installation as provided in our LCU client command file is as follows:
x.LDAP = 11
x.11.name = 'LDAP Client Toolkit API 1.0'
x.11.statevar = 'CAS_' || x.11.name
x.11.instprog = 'CLIFI.EXE',
' /s:'LDAPimg,
' /a:C',
' /b:'bootdrive,
' /r:'LDAPimg'\LDAP.rsp',
' /f:'bootdrive'\OS2\INSTALL',
' /l1:'logdir'\'client'.LDAPerr',
' /l2:'logdir'\'client'.LDAPlog',
' /r2:'
x.11.rspdir = resdir'\LDAP\'
x.11.default = 'LDAPdef.rsp'
|
where the variable LDAPimg is defined as:
LDAPimg = imgdir'\LDAP\IP01000'
The working response file used in our
environment is shown in Figure 93.
LDAP.InstDrive=D: LDAP.InstDir=\LDAPADT LDAP_Tlkt_Feature.Selection=1 LDAP_Toolkit.Selection=1 LDAP_Examples.Selection=0 LDAP_Doc.Selection=0 JAVA_Support.Selection=1 JAVA_Doc.Selection=0 |
TMA is a replacement for the SystemView agent. It is used for managing PC Servers and supports OS/2 using TCP/IP. It is installed using Software Installer.
For further detail on the installation of the Tivoli Management Agent, refer to the on-line documentation and the \CID\SERVER\LCFAGENT directory on the OS/2 Warp Server for e-business CD-ROM.
In our working example, the invocation of the Tivoli Management Agent
installation as provided in our LCU client command file is as follows:
x.LCFagent = 8
x.8.name = 'Tivoli Management Agent 4.0'
x.8.statevar = 'CAS_' || x.8.name
x.8.instprog = LCFimg'\install.exe',
' /x',
' /a:I',
' /o:drive',
' /l1:'logdir'\'client'.LCFl1',
' /l2:'logdir'\'client'.LCFl2',
' /r:'
x.8.rspdir = resdir'\LCF\'
x.8.default = 'lcfagent.rsp'
|
where the variable LCFimg is defined as:
LCFimg = imgdir'\LCFAGENT\XR09999'
The working response file used in
our environment is shown in Figure 95.
FILE = D:\TIVOLI\LCF CFGUPDATE = AUTO OVERWRITE = YES SAVEBACKUP = NO DELETEBACKUP = NO GPORT = 9494 LPORT = 9494 OPTIONS = |
OS/2 Warp Server for e-business includes a fully functional trial version of Lotus Domino Go Webserver. Lotus Domino Go Webserver is installed using Software Installer.
For further information on the installation of Lotus Domino Go Webserver, please refer to the on-line documentation on the separate CD-ROM that was shipped with the OS/2 Warp Server for e-business package.
In our working example, the invocation of the Go Webserver installation as
provided in our LCU client command file is as follows:
x.LotusGO = 21
x.21.name = 'Lotus GO webserver 4.62.5'
x.21.statevar = 'CAS_' || x.21.name
x.21.instprog = GOimg'\install.exe',
' /x',
' /a:I',
' /o:drive',
' /l1:'logdir'\'client'.GOl1',
' /l2:'logdir'\'client'.GOl2',
' /r:'
x.21.rspdir = resdir'\LotusGO\'
x.21.default = 'websrvr.rsp'
|
where the variable GOimg is defined as:
GOimg = imgdir'\LOTUSGO\4_62_05'
The working response file used in our
environment is shown in Figure 98.
*-------------------------------------------------------* * Secure Server Response file * *-------------------------------------------------------* COMP = Lotus Domino Go Webserver COMP = Security Files *COMP = Java Servlets COMP = Search engine for OS/2 Base COMP = Search engine: HTTP support COMP = Search engine: Coding Samples COMP = Installation and Maintenance *-------------------------------------------------------* * Directories installed to... * *-------------------------------------------------------* FILE = D:\WWW\Bin AUX1 = D:\WWW\DLL AUX2 = D:\WWW\Docs AUX3 = D:\WWW\CGI-BIN AUX4 = D:\WWW\HTML AUX5 = D:\WWW\Admin AUX6 = D:\WWW\Icons AUX7 = D:\WWW\Logs AUX8 = D:\WWW\LABELS AUX9 = D:\WWW\Servlets\Public AUX10 = D:\netq AUX11 = D:\netq\toolkit |
*-----------------------------------------------------------------* * Software installer variables... * *-----------------------------------------------------------------* CFGUPDATE = AUTO DELETEBACKUP = NO OVERWRITE = YES SAVEBACKUP = NO *-----------------------------------------------------------------* * Keywords used for installation defaults * *-----------------------------------------------------------------* RESPONSE = YES AUTOSTART = YES KEEP_CNF = NO KEEP_PICS = YES HOST = SRV163 PORT = 80 KEYFILE = keyfile.kyr SSLPORT = 443 ADMIN_ID = adminID ADMIN_PWD = adminPWD KEEP_ADMIN = YES KEEP_SRVCNF = YES |
| Note On Go Webserver Installation |
|---|
|
There are some specific considerations when installing Go Webserver. A hostname must be specified for the installation to complete successfully. Second, an Admin_ID and Admin_PWD must be specified for the unattended CID installation. If you want to install the WebSphere Application Server, you must not install the component Java Servlets. You will notice that our response file conforms to this advice even if the administration user ID and password are not very creative. |
WebSphere Application Server is a plug-in for Lotus Domino Go Webserver that adds Java support.
We found that the installation of WebSphere was not entirely CID-enabled. In order to achieve a successful unattended installation, we created a REXX command file WEBSPHER.CMD. This command file is shipped on the CD-ROM with this redbook.
| WebSphere Installation Syntax |
|---|
WEBSPHER.CMD /R:<script_file> /T:<target_path> /L:<log_file> /S:<source_path> /VERBOSE |
In our working example, the invocation of the WebSphere installation as
provided in our LCU client command file is as follows:
x.WebSpher = 22
x.22.name = 'WebSphere Application Server 1.10'
x.22.statevar = 'CAS_' || x.22.name
x.22.instprog = cmddir'\webspher.cmd',
' /VERBOSE',
' /S:'WEBimg,
' /L:'logdir'\'client'.WSlog',
' /T:'bootdrive'\web\app\',
' /R:'
x.22.rspdir = resdir'\WEBSPHER\'
x.22.default = 'webspher.script'
|
where the variable WEBimg:
WEBimg = imgdir'\WEBSPHER\1_10'
The working response file used in our environment
is shown in Figure 101.
#Java Install script file # # general info programName=WebSphere Application Server programVersion=1.1 componentName= componentVersion= # # components installCorba=true installGo=true installDoc=true installSamples=true installCore=true installSystem=true installCorbaDoc=true installServerPages=true # |
# installation parameters
scriptPlay=true
zipFileName=data.zip
logFileName=Inst
destinationDirectory={root}WebSphere\\AppServer\\
infoString=Install to directory {root}WebSphere\\AppServer\\\nFolder = Application Server V1.0\n
#
# folder options
noFolder=false
folder=Application Server V1.0
#
# log options
log=
logToScreen=true
|
The online books (.INF files) can be installed on the server if required. The OS/2 Warp Server books were available with the previous version of OS/2 Warp Server. They are listed here due to their importance.
Since we assume that the majority of server administration in an Enterprise
environment is conducted from an administrative client station, it is
unnecessary to install this documentation on the server. However, if they must
be installed, this can be accomplished by a REXX script called
INSTBOOK.CMD, located in the \IBMINST
directory on the OS/2 Warp Server for e-business CD-ROM.
In our working example, the invocation of the Warp Server Books installation
as provided in our LCU client command file is as follows:
x.books = 24
x.24.name = 'Warp Server Books'
x.24.statevar = 'CAS_' || x.24.name
x.24.instprog = cmddir'\INSTBOOK.CMD',
' /r:'resdir'\BOOKS\books.src',
' /l1:'logdir'\'client'.books',
' /s:'imgdir'\BOOKS\XR09999',
' /t:'bootdrive
x.24.rspdir = ''
x.24.default = ''
|
where variable imgdir has already been explained.
The following response file installs all books that are shipped with OS/2 Warp Server for e-business. Each line represents one book with entries separated by semicolons.
The first entry in every line names the product the book belongs to. The second entry provides the object ID for the workplace shell. The third is the file name or icon to be used for the workplace shell object. The last entry gives a message number for the title.
Please do not change the lines - if you do not want to install a
particular book, just remove the line from the response file.
LANSERVER;<WSLS_BOOK>;folder;70;icon=lsbooks.ico LANSERVER;<WSLSA3A41>;A3A41M02.INF;71 LANSERVER;<WSLSA3A61>;A3A61M02.INF;72 LANSERVER;<WSLSA3A4G>;A3A4GM02.INF;73 LANSERVER;<WSLSA3A62>;A3A62M02.INF;74 LANSERVER;<WSLAS3A4F>;A3A4FM02.INF;75 LANSERVER;<WSLSA3A4A>;A3A4AM02.INF;76 LANSERVER;<WSLSA3A4I>;A3A4IM02.INF;77 LANSERVER;<WSLSA3A4H>;A3A4HM02.INF;78 LANSERVER;<WSLSA3A53>;A3A53M02.INF;79 LANSERVER;<WSLSA3A83>;A3A83M02.INF;80 LANSERVER;<WSLS40GlOS>;LS40GLOS.HLP;83 MPTS;<WSLSA3V10>;A3V10M02.INF;82 MPTS;<WSDHCPCLT>;DHCPCLNT.INF;81 MPTS;<WSLSA3S12>;A3S12M02.INF;81 LANDISTANCE;<WSLDCSA3T11>;A3T11MST.INF;84 LANDISTANCE;<WSLDCSA3T12>;A3T12MST.INF;85 KARAT;<WSUSVINF>;IKOO0MST.INF;86 KARAT;<WSIFOR1>;I4DU2MST.INF;87 PSF2;<WSJISCII>;JISCII.INF;91 PSF2;<WSAINWNW>;NWMST.INF;88 PSF2;<WSAINVW>;PSF2MST.INF;89 PSNS;<WSPSNS_PSNSINF>;PSNS.INF;90 NETWARE;<NVL_CLIENT>;NWBOOK.INF;61 NETWARE;<NVL_UTILS>;NWUTIL.INF;62 |
IFSDEL removes the files installed by THINIFS.
| IFSDEL Syntax |
|---|
IFSDEL /T:<Target_Path> /TU:<ConfigSys_Path> /SD:<Optional> |
For full details of the syntax for IFSDEL, refer to &CID.The OS/2 Warp 4 CID Software Distribution Guide, SG24-2010 or &CID..
In our working example, the invocation of the IFSDEL command as
provided in our LCU client command file is as follows:
x.ifsdel = 20
x.20.name = 'SRVIFS Delete'
x.20.statevar = ''
x.20.instprog = ciddir'\srvifs\ifsdel',
' /t:'bootdrive'\srvifsrq',
' /tu:'bootdrive
x.20.rspdir = ''
x.20.default = ''
|
There is no need for an IFSDEL response file.
CASDELET removes all traces of LCU from the system. It is executed after all products have been installed.
| CASDELET Syntax |
|---|
CASDELET /TU:<Boot_Drive> /PL:<Path_Values> /L1:<LogFile> |
For full details of the syntax for CASDELET, refer to &CID.The OS/2 Warp 4 CID Software Distribution Guide, SG24-2010 or &CID..
In our working example, the invocation of the CASDELET as provided
in our LCU client command file is as follows:
x.casdelet = 19
x.19.name = 'LAN CID Utility Delete'
x.19.statevar = ''
x.19.instprog = ciddir'\locinstu\casdelet',
' /pl:'dllpath,
' /tu:'bootdrive
x.19.rspdir = ''
x.19.default = ''
|
5.12 NVDM/2 and SWD
Implementation