Technical Note 205
This page was last modified 06:02, 10 April 2007.From Documentation
(Difference between revisions)
| Revision as of 05:47, 10 April 2007 Moff (Talk | contribs) ← Previous diff |
Current revision Moff (Talk | contribs) |
||
| Line 12: | Line 12: | ||
| The upgrade is performed as follows: | The upgrade is performed as follows: | ||
| - | #Download COSmanager 4.2.5 distribution for your Operating System from [http://downloads.fs.com.au/main.php Functional Software Downloads]. Save the distribution to /tmp on the target host | + | #Download COSmanager 4.2.5 distribution for your Operating System from [http://downloads.fs.com.au/main.php Functional Software Downloads]. Save the distribution to <tt>/tmp</tt> on the target host |
| - | #As a COSmanager Manager run: cos | + | #As a COSmanager Manager user run: |
| + | #:<pre> | ||
| + | #:cos</pre> | ||
| #Config > COSMOS configuration > COSMOS applications, then Application > Install | #Config > COSMOS configuration > COSMOS applications, then Application > Install | ||
| - | #Select file, enter filename as downloaded, eg /tmp/cosmos-4.2.5 | + | #Select file, enter filename as downloaded, eg <tt>/tmp/cosmos-4.2.5</tt> |
| #When requested whether to share or copy the database, select copy | #When requested whether to share or copy the database, select copy | ||
| #Exit COSmanager | #Exit COSmanager | ||
| - | #As a COSmanager Manager, ignoring missing audit trail messages, run: cos -u cosmos -v 4.2.5 | + | #As a COSmanager Manager user, ignoring missing audit trail messages, run: |
| + | #:<pre> | ||
| + | #:cos -u cosmos -v 4.2.5</pre> | ||
| #Config > COSmanager configuration > Applications | #Config > COSmanager configuration > Applications | ||
| #Select COSmanager 4.2, then Application > Default version | #Select COSmanager 4.2, then Application > Default version | ||
| Line 31: | Line 35: | ||
| #Then Remote > Get applications | #Then Remote > Get applications | ||
| #Exit COSmanager | #Exit COSmanager | ||
| - | #Edit /etc/passwd and change the home directory of cosmos to the new installed directory of COSmanager Framework 4.2.5, for example, from /usr/cosmos/COS_3.2 to /usr/cosmos/COS_4.2 | + | #Edit /etc/passwd and change the home directory of cosmos to the new installed directory of COSmanager Framework 4.2.5, for example, from <tt>/usr/cosmos/COS_3.2</tt> to <tt>/usr/cosmos/COS_4.2</tt> |
| #Create new symbolic link to the cos and FSsh program, for example: | #Create new symbolic link to the cos and FSsh program, for example: | ||
| #:<pre> | #:<pre> | ||
| Line 42: | Line 46: | ||
| #:cd ~cosmos/Install | #:cd ~cosmos/Install | ||
| #:./upg_sched</pre> | #:./upg_sched</pre> | ||
| - | #Some tables should be compared with new default values. These tables are appl_cap, comm_meth, hostclass, hostype, role and table. Run: | + | #Some tables should be compared with new default values. These tables are <tt>appl_cap</tt>, <tt>comm_meth</tt>, <tt>hostclass</tt>, <tt>hostype</tt>, <tt>role</tt> and <tt>table</tt>. Run: |
| #:<pre> | #:<pre> | ||
| #:cd ~cosmos/db | #:cd ~cosmos/db | ||
| #:diff <table> ../distrib.db</pre> | #:diff <table> ../distrib.db</pre> | ||
| - | #:If entries in <table> are superseded or no longer needed, the remove the file <table> from the current directory. | + | #:If entries in <table> are superseded or no longer needed, then remove the file < table> from the current directory. |
Current revision
[edit]
Technical Note
This article recreates Technical Note 205.2, originally posted January 21, 2005.
[edit]
How do I upgrade from COSMOS 3.2.1 to COSmanager 4.2.5
All products, Backup 3.2.x, Duty 3.0, Sentinel 4.2.x and Task 4.1, will run with COSmanager Framework 4.2.5. They will be able to take advantage of context sensitive menus and new look and feel without the need for any modifications.
[edit]
Upgrade process
The upgrade is performed as follows:
- Download COSmanager 4.2.5 distribution for your Operating System from Functional Software Downloads. Save the distribution to /tmp on the target host
- As a COSmanager Manager user run:
- cos
- Config > COSMOS configuration > COSMOS applications, then Application > Install
- Select file, enter filename as downloaded, eg /tmp/cosmos-4.2.5
- When requested whether to share or copy the database, select copy
- Exit COSmanager
- As a COSmanager Manager user, ignoring missing audit trail messages, run:
- cos -u cosmos -v 4.2.5
- Config > COSmanager configuration > Applications
- Select COSmanager 4.2, then Application > Default version
- Config > COSmanager configuration > Other tables
- Select audlist, then Table > Maintain
- Select the audit trail COSMOS, then Maintain > Change
- Change all occurances of COSMOS to COSmanager (in Name, Description, File and Archive directory)
- Save the changes
- Config > COSmanager configuration > Hosts
- Select all entries that are not COSmanager hosts, then Maintain > Remove (you can avoid having to confirm each entry being removed by first File > Confirm actions)
- Then Remote > Allow access
- Then Remote > Get applications
- Exit COSmanager
- Edit /etc/passwd and change the home directory of cosmos to the new installed directory of COSmanager Framework 4.2.5, for example, from /usr/cosmos/COS_3.2 to /usr/cosmos/COS_4.2
- Create new symbolic link to the cos and FSsh program, for example:
- ln -s /usr/cosmos/COS_4.2/bin/cos /bin/cos
- ln -s /usr/cosmos/COS_4.2/bin/FSsh /bin/FSsh
- ln -s /usr/cosmos/COS_4.2/bin/FStcl /bin/FStcl
- From a root shell run:
- cos -u cosmos cosmos -c ksh
- cd ~cosmos/Install
- ./upg_sched
- Some tables should be compared with new default values. These tables are appl_cap, comm_meth, hostclass, hostype, role and table. Run:
- cd ~cosmos/db
- diff <table> ../distrib.db
- If entries in
are superseded or no longer needed, then remove the file < table> from the current directory.