Section 1: Windows NT
Install NT 4.0 (Workstation or Server) [Software (S/W) and Server access licenses required]
1) Read the following sections of the Microsoft installation documentation before starting:
a) What You Should Know Before Running Setup
b) System Requirements
c) Starting Setup
2) Obtain the following information from your Network Administrator before starting.
Computer Name
Host Name (typical for Host and Computer names to be the same)
Domain Name
TCP/IP Addressing:
IP Address setup:
Adapter (Network Interface Card): IRQ and Memory Base Address
Host IP address
Subnet Mask address
Default Gateway address
Note: Win95 may use multiple Gateways
Domain Name System (DNS) setup:
Host Name: (Typical entry: ComputerName),
Domain:
(Typical entry: ..com)
up to three DNS IPs
Modem COM Port # , IRQ, and Port Settings (if used)
Note: Your System Administrator may have additional setup information for you, such as
Windows Internet Name Services (WINS) and Dynamic Host Configuration Protocol (DHCP).
3) Proceed with the NT install as per Microsoft instructions using the following information
to assist you with configuring NT for a San Francisco environment.
a) Network Setup: It is not critical that any of the following configuration be accomplished
during the initial NT install. Additional services can be added and or reconfigured after the
initial install. This may be necessary if you need to use third party software to install
drivers, such as for a Network Interface Card (Adapter) install.
Select Start button
Select Settings
Select Control Panel
Select Network
(NetBEUI and TCP/IP required)
Note: Setup networking information per your Administrator and/or local procedures
Identification: (Computer Name, Domain) entries
Services: (Computer Browser, NetBios Interface, RPC Configuration, Server, SNMP Service, Workstation) to install
Note: Add SAP (Sevice Advertising Protocol) Service if IPX/SPX is installed.
Note: Add Microsoft TCP/IP Printing and Simple TCP/IP Services for printing support.
Protocols: (NetBEUI, TCP/IP)
Note: Add DLC if remote networked printer setup support is required
TCP/IP:
IP Address:(Adapter, IP, Subnet Mask, Gateway)
DNS:(Host Name (Use: ComputerName), Domain(Use: localsite.ibm.com), DNS IPs)
Adapters: (Check properties)
Should see non conflicting IRQ (typically 9,10, or 15 depending on your platform)
Should see non conflicting Memory Base address (xD200 or xC200 typically)
Use Start/Programs/Administrator Tools/WinNT Diagnostics to verify no conflicts
Bindings: (Check bindings)
Should see these Bindings: (NetBios Interface, Server, Workstation)
Remote Access Server Service Binding will be there if you installed dial-up networking/modem
Under each Binding in order listed: (Wins Client(TCP/IP), NetBEUI Protocol)
b) If local Internet access is via proxy, configure the proxy address
Select Start button
Select Settings
Select Control Panel
Select Internet
Select Use Proxy Server
enter Proxy Server:
c) If modem communications are required, configure COM2 for dial-up modem services
(assumes your modem port will be COM 2 - check with your System Administrator).
Select Start button
Select Settings
Select Control Panel
Select Ports
Add:
COM Port Number: 2 (Typical settings follow)
Base I/O Port Address: 2f8 or default
IRQ: 3 or default
Select "FIFO Enabled
Check Settings:
Baud Rate: 57600 or higher
Data Bits: 8
Parity: None
Stop Bits: 1
Flow Control: None
ThinkPads Only
- Install ThinkPad Utilities (Set Modem at COM2)
- Install MWave Utilities (Modem & Sound)
NOTE: Downloadable from IBM web page:http://www3.pc.ibm.com/support.
4) If modem communications are required, Setup dial-up modem services
Select My Computer
Select Dial-Up Networking
Select Install button
Note: This will walk you through the modem and Remote Access service setup.
5) If PCMCIA Token Ring setup is required
Note: Ethernet setup is similar.
Select Start button
Select Settings
Select Control Panel
Select PC Card (PCMCIA)
Verify: IBM Token Ring - Socket <0 or 1>
Check Properties (Typical values follow)
Driver Tab: Driver Status - The driver installed, started, and configured this device.
Resources Tab: Interrupt Request (9, 10, or 15 as indicated by selection above)
Memory Range: (D2000-D2FFF or C2000-C2FFF as indicated by selection above)
6) Virtual Memory (VM) Setup
Select Start button
Select Settings
Select Control Panel
Select System
Select Performance Tab
Select Change Button
Set Virtual Memory
Initial Size: (See section: "Total Paging File Size for all Drives - Recommended value")
Maximum Size: (Whatever you can afford within max. possible)
Note: See NT PERFORMANCE HINTS below to determine max. possible.
-----------------------------------------------------------------------------------------------------------------
NT PERFORMANCE HINTS:
1) To determine max. Virtual Memory (VM) NT can use for a given amount of RAM do the following:
a) Right click "empty area" of Start window menu bar below
b) Select Task Manager
c) Select Performance Tab
d) Max. VM = Commit Charge Limit
You can speed NT by allocating VM space on each hard disk (virtual or not doesn't appear to matter). It stops a lot of the thrashing between changing drive accesses (Application executing on drive C/Pagefile.sys on drive D).
Example - dual boot configuration:
one 3 GB Hard Drive:
2 GB FAT32 - C: - Win95 Installed
1 GB NTFS - D: - NT installed
P166/88MB Ram - Max. VM: 333848KB per Task Manager
C: Initial Size: 50, Max. Size: 100 Mostly App Installs Here.
D: Initial Size: 200, Max. Size: 300 Mostly Data stored here.
------------------------------------------------------------------------------------------------------------------
Note: Recommended Install - WinZip32
To handle distribution and porting of projects and packages using long filenames.
Winzip32.exe version 6.3. (Available at: http://www.winzip.com.
Section 2: Netscape Browser
1) Install Netscape (3.0 or higher) Beta or per IBM license agreement
Netscape 3.0 and Communicator Version 4.04 available at: http://www.netscape.com
Netscape 3.0 proxy setup
Start Netscape
Select Options
Select Network Preferences
Select Proxies Tab
Setup for manual or automatic proxy (depends on local site options)
Communicator proxy setup
Select Edit
Select Preferences
Select Advanced +
Select Proxies
Setup for manual or automatic proxy (depends on local site options)
NOTE: Annoyance: Communicator:Netscape 4.0 will output a message that it can't find the html page when double clicking a *.html file or invoking Communicator via an icon that loads an html page. This is a Communicator to Netscape message passing problem and you can ignore the message, the html page will be found and displayed.
Section 3: JDK
1) Install JDK1.1.2 or JDK 1.1.4 and associated API Documentation
(Available at: http://Java.sun.com.)
(JDK 1.1.2 ships with the San Francisco Version 1.1.0 CD). Found in the JDK112 directory.
NOTE: The API Documentation, jdk114doc.zip for JDK114, is a separate install. Assuming a JDK1.1.4 directory JDK install, the default API documentation install is found under \JDK1.1.4\docs\api.
NOTE: If you are using JDK 1.1 or later, it is unnecessary to install BDK1.0 as it has been incorporated into the JDK. BDK 1.0 is also available from Sun.
NOTE: Recommended Installation Directory: C:\JDK1.1.4. Assumes PC install of JDK version 1.1.4. The following NT (PATH and CLASSPATH) environment variable setup assumes this install location.
Unzip the files and follow the built-in JDK installation instructions.
2) Add or Modify PATH and CLASSPATH Environment Variables:
For this step, it will be necessary to either modify or create the PATH and CLASSPATH environment variables as indicated in sub step (a) and (b) below. Sub step (c) provides information on how to do this in a Windows environment.
a) Add the string: "c:\JDK1.1.4\bin" to the PATH variable (Assumes install location is C:\JDK1.1.4.).
b) Add the string: ".;c:\JDK1.1.4\lib\classes.zip" to the CLASSPATH variable (Assumes install location is C:\JDK1.1.4.). The "." at the front-end of the string results in a current directory/folder search.
c) The following steps are to assist with achieving sub steps (a) and (b) above.
Select Start button
Select Settings
Select Control Panel
Select System
Select Environment Tab
Check to see if PATH and/or CLASSPATH exists in either window. The top window contains "System" variables. The bottom window contains "Current User" variables.
To choose which window to use, read the notes in the HELPFUL HINTS section below.
To create a new variable:
a) Select any variable from either the "System" or "User" variable window (see below for information on which window to choose).
b) In the "Variable:" text field, rename the selected variable to "PATH" or "CLASSPATH"
c) In the "Value:" text field, enter the associated string value. For PATH: "c:\JDK1.1.4\bin", without the double quotes. For CLASSPATH: ".;c:\JDK1.1.4\lib\classes.zip" without the double quotes.
d) When the information is correct, press the "set", "apply", and "ok" buttons in the sequence listed here.
To add a string to an existing variable:
a) Select the variable from either the "System" or "User" variable window (see below for information on which window to choose).
b) In the "Value:" text field, append the associated string value. For PATH: "c:\JDK1.1.4\bin", without the double quotes. For CLASSPATH: ".;c:\JDK1.1.4\lib\classes.zip" without the double quotes.
c) When the information is correct, press the "set", "apply", and "ok" buttons in the sequence listed here
3) HELPFUL HINTS:
NOTE: How does NT build environment variable strings? NT will build an environment variable string, such as PATH, by setting PATH = "System PATH" string first, then appending the "User PATH" string 2nd, and finally, if-and-only-if you open a DOS window, appending the "autoexec.bat PATH" string 3rd.
NOTE: Does it matter whether I append information as "System" or "User" variable strings? No, not really, the difference is "System" variables are available for any user Login and "User" variables are available for a specific user Login. The autoexec.bat variable string is not appended until you open a DOS or Command prompt window. The two checks to apply are:
1) Check for duplication of strings - why? Because there's a limit to the string length in DOS.
2) Is this string for all users or a specific user? String is a System or User variable, respectively.
NOTE: How do I verify NT environment variable strings are correct? By opening a DOS or command prompt window and typing "set (environment variable name)", such as "set path", and checking the string for syntax and duplication.
NOTE: When selecting path and file names, keep in mind DOS is more readable if you use the 8.3 DOS convention for naming Folders and Files.
NOTE: You may need to modify the autoexec.bat PATH variable depending on your development environment. For example, to run code in DOS that is dependent on Jbuilder APIs, the Jbuilder bin PATH and class zip file CLASSPATHs will need to be appended.
NOTE: You will append, either manually or automatically, additional strings to these variables during follow-on installs. Jbuilder and the SF Code Generator will add some of their CLASSPATH and PATH string parameters for you during their installs. SF Code Generator adds its parameter/entry to the beginning of the PATH and CLASSPATH variable; I usually move the SF Code Generator entry to the end of the PATH and CLASSPATH variable (later).
Section 4: San Francisco
1) Install San Francisco Version 1.1.0 or the San Francisco Evaluation Software.
NOTE: San Francisco Version 1.1.0 is a complete application.
(San Francisco V1.1.0 CD) available, free of charge, by attending the San Francisco Fundamentals course.
NOTE: The evaluation software is a partial San Francisco application.
(Evaluation Software download or CD request) available through the San Francisco home page: http://www.ibm.com/Java/Sanfrancisco.
Before starting, on the San Francisco CD, read the \Win\Install.txt file. Pay particular attention to information regarding using IBM Anti Virus and Symantec products.
Close all programs and folders.
Select Start button
Select Run
Using the Browse button, navigate to the CD and execute \Win\setup.exe.
Follow the default install procedures found on the CD.
NOTE: the default install uses port 9898 to advertise the San Francisco Global Name Service.
2) Add San Francisco (PATH and CLASSPATH) Environment Variable Strings
Goal 1: Add the string: "c:\sf110\bin" to the PATH variable (Assumes default install location).
Goal 2: Add the string "c:\sf110" to the CLASSPATH variable (Assumes default install location).
See Section 3: JDK for information on selection and setting NT environment variables. If required, the install.txt file provides additional information.
NOTE: Most of the following information can also be found in the online documentation under the section titled: "Installing San Francisco".
3) Test your San Francisco Install (Optional)
Before you start working with San Francisco, it is recommended that you first run the Checkbook sample once to make sure that everything installed successfully.
a) To run a San Francisco application, start the servers: Since this is the first run of a new install, Reinitialize the data and name space.
Select windows Start button
Select Programs
Select IBM San Francisco 1.1.0
Select Reinitialize data and name space
b) Start the application.
Select windows Start button
Select Programs
Select IBM San Francisco 1.1.0
Select Base
Select Base Samples
Select GUI Checkbook Sample (or Simple Checkbook Sample to use the command line version.)
You will be prompted for the data described in the following:
a. Enter a name and an account number.
b. Select whether this is a new account to be created or an existing account.
c. Select the access mode which depends on where the code is being executed.
d. Your sample account is opened and you can now test the transactions by entering a value into the amount field and pressing either Deposit or Withdraw. Press the Apply and then the Ok button.
e. The transaction is started and if a new value for the current balance is calculated, transactions work successfully.
Select Ok and then Exit to leave the sample.
To test whether persistence works:
1. Start the GUI Checkbook Sample again.
2. Enter the same name that you used in the above test.
3. If the value of the current balance is still the same as the one you calculated in the above test, persistence works properly also.
4) Setting up, Backing Up, and/or Restoring GUI and General Ledger (GL) Name Spaces (Optional)
NOTE: Only one name space can be installed at-a-time. Each name space install will delete the previously installed name space. The default install sets up the GUI name space. To run GL sample applications, you must install the GL Extensions name space.
NOTE: Start and Stop San Francisco servers and reinitialize data and name space as prompted. Depending on your processor speed and memory - any of the following operations may take awhile...
a) To Start the Logical San Francisco Network (LSFN):
- Select (Start, Programs, IBM San Francisco 1.1.0, Start LSFN)
b) To Stop the Logical San Francisco Network (LSFN):
- Select (Start, Programs, IBM San Francisco 1.1.0, Stop LSFN)
c) To Reinitialize Data and Name Space:
- Select (Start, Programs, IBM San Francisco 1.1.0, Reinitialize data and name space)
d) To Backup the GUI Name Space:
- Select (Start, Programs, IBM San Francisco 1.1.0, Base, Base Samples,
Backup GUI Sample Name Space)
or, if General Ledger (GL) is installed you can also do this from the GL folder:
- Select (Start, Programs, IBM San Francisco 1.1.0, General Ledger,
General Ledger Samples, Backup GUI Samples Name Space)
e) To Setup the GUI Name Space:
- Select (Start, Programs, IBM San Francisco 1.1.0, Base, Base Samples,
Setup GUI Samples)
or, if General Ledger (GL) is installed you can also do this from the GL folder:
- Select (Start, Programs, IBM San Francisco 1.1.0, General Ledger,
General Ledger Samples, Setup GUI Samples)
f) To Restore the GUI Name Space:
- Select (Start, Programs, IBM San Francisco 1.1.0, Base, Base Samples,
Restore GUI Sample Name Space)
or, if General Ledger (GL) is installed you can also do this from the GL folder:
- Select (Start, Programs, IBM San Francisco 1.1.0, General Ledger,
General Ledger Samples, Restore GUI Samples Name Space)
g) To Backup the GL Name Space:
- Select (Start, Programs, IBM San Francisco 1.1.0, General Ledger,
General Ledger Samples, Backup GL Extension Samples Name Space)
h) To Setup the GL Name Space:
- Select (Start, Programs, IBM San Francisco 1.1.0, General Ledger,
General Ledger Samples, Setup GL Extension Samples)
i) To Restore the GL Name Space:
- Select (Start, Programs, IBM San Francisco 1.1.0, General Ledger,
General Ledger Samples, Restore GL Extension Samples Name Space)
On Windows 95 and NT, the installation procedure also automatically starts the required configuration of your system. During this process, the servers are started. On AIX, the configuration process has to be started manually. When the post-install configuration is completed, San Francisco is up and running.
j) To create the online documentation search applet
- Select (Start, Programs, IBM San Francisco 1.1.0, Create Search Index)
Section 5: San Francisco Fix Pack
NOTE: Fix packs cannot be installed with the San Francisco Evaluation software.
NOTE: Available fix packs are found at http://www.ibm.com/Java/Sanfrancisco.
Fix Pack 1 Associated Fixes:
_____________________
FIX 3089
ABSTRACT:
CheckSecureTaskAccess() does not throw SecureTaskNotFoundException for a secure task that does not exist even though the method signature says it should.
FIX 3117
ABSTRACT:
Logging using OdbcContainer failed with string data right truncation error.
FIX 3216
ABSTRACT:
SecureRandom initialization hangs the GSM in bringup.
FIX 3276
ABSTRACT:
Client communication problems with GSM during transaction recovery.
FIX 3298
ABSTRACT:
Allow Transient Handles to function correctly.
FIX 3318
ABSTRACT:
AccessRights vector not consistently streamed out in UserToken.
FIX 3334
ABSTRACT:
Change in collection internals to work around a database record-size limitation (32k).
FIX 3390
ABSTRACT:
Locking hang in multi-client environment.
FIX 3420
ABSTRACT:
To prevent server configuration problems because of entering data in the wrong case (i.e. upper case versus lower case), the keys used with the server configuration information will all be lower cased before the data is stored.
FIX 3423
ABSTRACT:
Wrong number of elements returned to configuration GUI's.
FIX 3431
ABSTRACT:
Enhacements to Problem classes to increase reliability of problem logging.
FIX 3446
ABSTRACT:
Intermittent hang of a client session during it's bringup.
FIX 3451
ABSTRACT:
DTime creation does not initialize milliseconds value properly.
FIX 3464
ABSTRACT:
An SmServerBringupException is thrown during server process start-up but details on the specific problem are not available.
FIX 3468
ABSTRACT:
Fix regression error resulting from FIX 3117.
FIX 3473
ABSTRACT:
Correction to the algorithm used to generate unique identifiers for objects.
FIX 3474
ABSTRACT:
Append priming support for host, process, serviceobject, & containerid2containerinfo format lines.
FIX 3478
ABSTRACT:
Fix data integrity problem in large collections with dupe hashcode values.
FIX 3488
ABSTRACT:
Failure while running GUI samples Setup with RDB data store.
FIX 3495
ABSTRACT:
Server go away when multiple threads applications run on XA environment.
FIX 3566
ABSTRACT:
The Print utility is not working with persistent data.
FIX 3659
ABSTRACT:
Fix to ensure that collection elements exist properly in NoLock copies of collections.
FIX 3663
ABSTRACT:
UTF (Unicode Transmission Format) processing failure.
FIX 3672
ABSTRACT:
Fix Business Partner Shared Data Factory for ID Generation.
FIX 3708
ABSTRACT:
Improve performance of creating an iterator over an EntityOwningEvent.
FIX 3718
ABSTRACT:
Starting CBOF GUI Samples fails with ClassNotFound error using JDK 1.1.4.
FIX 3726
ABSTRACT:
Allows Document Designer to display text that has been defined as native language to the host operating system.
Section 6: Windows NT Service Pack
1) Install Windows NT Service Pack 3 (Optional)
(downloadable from MS): www.microsoft.com
Warning: Major problems associated with installation of an incorrect Service Pack. Service packs are based on locale (international versions). Obtain the latest "proven" NT Service Pack for your locale. For NT 4.0 the current Service Pack is Service Pack 3 (SP3). SP3 fixes several NT problems including one that only allows JBuilder to add 5 files at-a-time to a project. Now you can add all files to a project, at once, using shift and ctrl keys.
NOTE: An international install attempt reported problems (blue screen death and hard drive format required to recover). THIS IS NOT A REQUIRED INSTALL - IT FIXES SOME MINOR ANNOYANCES ON U.S. PLATFORMS. IMPACT TO INTERNATIONAL INSTALLS IS UNKNOWN - DOWNLOAD THE CORRECT SERVICE PACK FOR YOUR LOCALE FROM MICROSOFT IF YOU NEED THE FIXES.
NOTE: SP3 should be reinstalled after any system configuration changes or application installs. In other words: do it at the end of an application(s) install scenario.
Section 7: Where to Find Additional Information
1) San Francisco online documentation.
If you performed a default San Francisco install, the online documentation can be found at file:///C|/sf110/COM/ibm/sf/doc/ibmsf_sf_DocumentationEntry.html. You can invoke the web page using the "information" icon found in the San Francisco folder.
Select windows Start button
Select Programs
Select IBM San Francisco 1.1.0
Select Information
2) URLS: (NOTE: sections of some sites may require password access)
