Overview

This document refers to the installation/upgrade procedure for a client/server installation of OCS where the server components are running on Linux/Unix. The procedure using a MS-Windows server will be documented later and will be similar to what is documented here.

This document has been written based upon OCS release 208.00 running on Build Professional 8.03.00.40. This procedure may require alteration if running on a different version of Build Professional or OCS.

This document assumes the database and data have been loaded. ( either a blank database for a new installation or loaded data for a conversion or existing system )

No account has been taken for customer running customer specific versions/modifications.

Steps not required for a Build Professional upgrade will be marked with an *
 

Procedure

All steps must be followed in the listed order.

1. Download the Build Professional release from the TODAY Systems Web Server. You will need both the main Build Professional server archive (bpXXXXXXX.cpio.gz or bpXXXXXXX.zip where XXXXXXX is the release number) available in the relevant directory for your platform and also the Build Professional client archive (bcXXXXXXX.zip where XXXXXXX is the release number). Other files may be required depending on your platform as described in point 5 below.
    
2. Decompress the server files and move them to your Build Professional server.
    
3. Read the readme.txt file for any additional information that may be required for your installation of BuildProfessional.
    
4. Run the Install script as the root user. The install script will then list prerequisites for the installation. After confirming the prerequisites the installation will proceed . The Install script will prompt you to enter:

• The target installation directory name or CR to install into the current directory. Choose a new directory that is different to the old directory that the previous release of Build Professional was installed in. We recommend choosing a directory where the Build Professional release number forms part of the directory structure. (This will allow your users to continue using the OCS applications while the new Build Professional is being installed) This directory will be referred to as $installdir for the remainder of this document.
   
• Your license numbers and activation keys. Enter your license details as supplied by TODAY Systems.
   
• An optional repository password. We recommend leaving this blank.

5. After the installation has completed additional binaries may have to be copied and branded according to database. Please read the BuildProfessional readme.txt file for information on the binaries required for specific databases and the instructions on how to brand them.
    
6. The shell script $installdir/bin/Today have hard-coded paths in them for the system shared libraries. As the position of these shared libraries is site specific and is determined at operating system install time, the paths specified in the script may need to be modified to reflect the correct path.
    
7. * Several directories are required for 3 BuildProfessional areas , these are:

 <Your Production sfiles area>

This is the application repository and is where the OCS applications are stored. When you install BuildProfessional, a blank sfiles repository is created in $installdir/sfiles

This blank set of sfiles should be copied to this area.

 <Your Production Data Area>

This is where application data is kept that is not stored in the database.

Several files must be created here. These are:

ocspatch.txt

Which should have in it the previous release number ie:

206.01.000

ocsapps.txt

Which should have in it the applications you have (usually all of them):

todayOCS

today_AP

todaySFL

special  (which can be downloaded from our ftp server)

ocsuppth.txt

Must have the server path for where upgrades will be uncompressed into. Ie:

/disk1/ocs/setup

<Your Production Scripts Area>

This is where user defined server side scripts may be created.

Another set of areas is also required for the test area.

These area will be referred to later.

9. Several scripts in the $installdir/bin directory must be modified/created. The following descriptions assume 1 test and 1 production area is used.

 The nimconf file must have the following lines added:

[Session Manager Service: OCS Prod]

Command=$installdir/bin/Today.OCSprod -R

ConfigFile=OCSprod.todayrc

ConfigPath=.:$installdir/bin

Description=OCS Production Environment

LinkActiveFrequency=50

 

[Session Manager Service: OCS Test]

Command=$installdir/bin/Today.OCStest -R

ConfigFile=OCStest.todayrc

ConfigPath=.:$installdir/bin

Description=OCS Test Environment

LinkActiveFrequency=50

 

[Session Manager Service: OCSold Prod]

Command=$installdir/bin/Today.OCSprod -R

ConfigFile=OCSprodold.todayrc

ConfigPath=.:$installdir/bin

Description=OCS Old Production Environment

LinkActiveFrequency=50

 

[Session Manager Service: OCSold Test]

Command=$installdir/bin/Today.OCStest -R

ConfigFile=OCStestold.todayrc

ConfigPath=.:$installdir/bin

Description=OCS Old Test Environment

LinkActiveFrequency=50

Copy the Today script to Today.OCStest and Today.OCSprod

Modify the Today script by deleting the lines

TODAYCONFIG=$installdir/bin/.todayrc

export TODAYCONFIG

Copy the Today script to TodayINT

Modify the Today.OCSprod file by changing the lines  

TODAYCONFIG=$installdir/bin/.todayrc

to

TODAYCONFIG=$installdir/bin/OCSprod.todayrc

Modify the Today.OCStest file by changing the lines

TODAYCONFIG=$installdir/bin/.todayrc

to

TODAYCONFIG=$installdir/bin/OCStest.todayrc

Both files Today.OCSprod and Today.OCStest need to have any database specific environment variables set at the top of the script such as: (The environment variables must be changed to suit the separate production and test areas) 

Informix SE

INFORMIXDIR=<Informix Directory>

export INFORMIXDIR

DBPATH=<Database Path>

export DBPATH

DBDATE=Y4MD0

export DBDATE

 

Oracle

ORACLE_SID=<Oracle SID>

export ORACLE_SID

ORACLE_USER=Oracle Username/Password

export ORACLE_USER

 

Informix Online

INFORMIX_SERVER=<Informix Server>

export INFORMIX_SERVER

INFORMIXDIR=<Informix Directory>

export INFORMIXDIR

DBDATE=Y4MD0

export DBDATE

Also add any other operating specific commands required for the users environment.

Eg umask settings

ulimit settings

Modify the .todayrc file by adding the following lines under the [TODAY Environment] section

* Where <Version> is the Build Professional Version Number, eg. BuildProVersion=8.03.00

BuildProVersion=<Version> *  

DynamicDateFmt=M

DisableNulls=True

DefaultFilter=nothing

        DebugScreenStack=

False

ocsSharePath

=<Data Transfer Directory>

Change the lines

ClientPrinting=True

to

ClientPrinting=False

 

TemplateApplication=Template

To
TemplateApplication=menus

 

EditEditableNoBg=DarkGrey

To

;EditEditableNoBg=DarkGrey

 

EditEditableNoBrush=solid-DarkGrey

To

;EditEditableNoBrush=solid-DarkGrey

If you are running Informix Online change

;       InformixOnline=True

to

InformixOnline=True  

 

If running using the SQL Server database then add the following lines under the [TODAY Environment] section

 

        SQLKeysetCursor=True

 

If running using the Oracle database then add the following lines under the [TODAY Environment] section

        OracleNullsLow=True

Add the following lines into the  [Accelerator] section:

 *UndoKey=Control-Z

*CutKey=Control-X

*CopyKey=Control-C

*DeleteField=Control-D

*InsertField=Control-I

*AppendField=Control-A

*OKKey=F8

*ApplyKey=F9

*PrintKey=Control-P

*CloseKey=Escape

Add the following lines into the  [Class Defaults] section:

DisplayReport.font=ReportFont

PrinterReport.font=ReportFont

Copy the .todayrc file to OCSprod.todayrc, OCStest.todayrc, OCSprodold.todayrc and OCStestold.todayrc

In the files OCSprod.todayrc and OCSprodold.todayrc  change the lines

RepositoryPath=$installdir/sfiles

to

RepositoryPath=<Your Production sfiles area>

 

DataPath=$installdir/data

to

DataPath=<Your Production Data Area>

 

ScriptPath=$installdir/data

to

ScriptPath=<Your Production Scripts Area>

In the files OCStest.todayrc and OCStestold.todayrc  change the lines

RepositoryPath=$installdir/sfiles

to

RepositoryPath=<Your Test sfiles area>

 

DataPath=$installdir/data

to

DataPath=<Your Test Data Area>

 

ScriptPath=$installdir/data

to

ScriptPath=<Your Test Scripts Area>

In the files OCSprod.todayrc, OCStest.todayrc the following lines into the specified section:

[Class Defaults]

Delete the line

Desktop.font=CellFont

 

[Font]

ReportFont=Courier-7

TitleFont=MS Sans Serif-bold-8

TabSelectedFont=MS Sans Serif-bold-underline-8

OCSFixedFont=Courier-10

ocsHighlightFont=MS Sans Serif-bold-8

 

[Brush]

MenuBrush=solid-DarkGrey

ocsDispBrush=solid-WindowsGrey

ocsDispInqBrush=solid-WindowsGrey

 

[Color]

MenuBg=128.128.128

MenuFg=255.255.255

ocsDispBg=XP_COLOR_3DFACE

ocsDispInqFg=XP_COLOR_WINDOWTEXT

ocsDispInqBg=XP_COLOR_3DFACE

ocsHighlightFg=255.0.0

In the files OCSprodold.todayrc, OCStestold.todayrc change the following lines

font=StandardFont

to

font=EditFont

 

Desktop.font=CellFont

To

Desktop.font=EditFont

In the files OCSprodold.todayrc, OCStestold.todayrc the following lines into the specified section:

[TODAY Environment]

OldEditMinWidth=True

OldPanelBehaviour=True

OldPushButtonJustification=True

OldScreenNavigation=True

OldShowCommand=True

OldSingleCellScrollBarDimensions=True

MainScreenLines=22

MainScreenColumns=110

 

[Class Defaults]

Edit.font=EditFont

 

[Font]

EditFont=Courier-9

ReportFont=Courier-7

In the files OCSprodold.todayrc, OCStestold.todayrc comment out the following lines:

CellWidth=6
CellHeight=13

9. Modify unix startup scripts. A unix startup script is required to start the session manager. The session manager is started by running $installdir/bin/Sessmgr. The system must be rebooted.
    
10. Modify other scripts as required. Most systems will want 1 or more user set up for data and Build Professional maintenance. These users will have to have their .profile modified and other associated scripts created to set up the Build Professional and database settings as outline above.

The .profile or new script should contain the following Build Professional Environment Variables:

 TODAYCONFIG=$installdir/bin/OCSprod.todayrc ( or $installdir/bin/OCStest.todayrc for a test script )

Export TODAYCONFIG

And should contain database specific environment variables such as:

Informix SE

INFORMIXDIR=<Informix Directory>

export INFORMIXDIR

DBPATH=<Database Path>

export DBPATH

DBDATE=Y4MD0

export DBDATE

 

Oracle

ORACLE_SID=<Oracle SID>

export ORACLE_SID

ORACLE_USER=Oracle Username/Password

export ORACLE_USER

 

Informix Online

INFORMIX_SERVER=<Informix Server>

export INFORMIX_SERVER

INFORMIXDIR=<Informix Directory>

export INFORMIXDIR

DBDATE=Y4MD0

export DBDATE

Also add any other operating specific commands required for the users environment.

Eg umask settings

ulimit settings

The user account/script should be used for all Build Professional command line utilities such as archive, running specific upgrade processes that may be required from time to time or database utilities

11. * The OCS setup application must be archived in the repository using the command: (Ensure your environment is correctly setup as per step 10 above and that this is repeated for both Test and Production )

archive -xsf setup.tdy

12. Decompress the client files to your client machines. (Or somewhere accessible by the client machines) The following steps 13 to 14 will have to be repeated for each client machine.
     
13. Run the setup.exe file for your client machine following the installation instructions.
     
14. Once the buildpro client is installed the wintoday.ini file in the $windowsinstalldir/bin_net directory must be modified. The following lines should be commented out:

CellWidth=6
CellHeight=13

ClientPrinting=True

UseExternalHelp=yes  

EditEditableNoBg=DarkGrey

EditEditableNoBrush=solid-DarkGrey

font=StandardFont

Desktop.font=CellFont

15. * Before the Build Professional client can be set up the client environment must be set up for the users.

A common shared area must be set up. Eg: S:\ocs\ where S:\ocs\ points to the same physical location no matter which user access it. (NOTE: This may be optionally set up per user, this means any external scripts/programs that need to be setup must be setup for each user)

The directory structure under this directory should be:

Test

Scripts (Location of external scripts / programs you wish users to be able to run from the OCS menus )

Prod

Scripts (Location of external scripts / programs you wish users to be able to run from the OCS menus )

Help (The help files from the ftp server can be uncompressed into here)

16. * Before the client/server component of Build Professional can be run TCP/IP must be running on the clients and server. The clients should be able to ping the server by name and ip number and server should be able to ping the clients by name and ip number.
     
17. The OCS Client must be installed as per the OCS client installation instructions available of the OCS web site.
     
18. Shortcuts should be created for each user on their desktop or StartMenu as per the OCS Client installation instructions. NOTE: This step is set up differently if running through a thin terminal product such a terminal server or metaframe.
     
19. * The administ application must be run. Under “System Definition” the fields “Default File Manager” and “Default Database Manager” must be changed to ORACLE, INFORMIX or MSSQL.
     
20. The OCS setup application can then be run which will install all the OCS applications. The OCS application archive from our Web Server must be decompressed into the server set up area first as specified in the ocsuppth.txt file setup in step 7 above.
     
21. The pulldown menus must be rebuilt. NOTE: This can be avoided if the old applications were archived in prior to running setup.