Topics

1

MP Server / OD 10.1 Active Active High Availability implementation

« on: February 27, 2019, 04:08:08 PM »

Hi, I was reading the topic about the subject

http://www.odusergroup.org/forums/index.php?topic=2226.0

Has anyone implemented this solution? I have some doubts that may be someone can help me

Zookeeper
The three ZooKeeper servers should be on different machines than CMOD Servers? or could be run in the same machine?

DB2
We use DB2,  and in the first step, we need to migrate to DB2 pureScale to have shared database accesible from at least two CMOD Servers (we need to define if will have two or more OD servers)

arscache
I guess that if we have a shared file system accesible from CMOD servers, should be OK. Is correct ?

TSM
What's about TSM Server, we can keep only TSM Server?

if we load the information in only one CMOD server, should be accessible from the second CMOD Server?

Thanks in advance
Federico Bucchi

2

Windows Client / Font mapping issue - ICUDT30L to IUCUDT36L

« on: October 24, 2012, 01:51:16 PM »

Hi all!!, we have OnDemand server and thick client version 8.3 (7.1.2.6) and we 're working in migration to OnDemand 8.5. A few years ago, when we need to migrate from version 7.1.2.3 to 7.1.2.6, we followed the instructions of the technote 7007227 and we did tthe following because we had custom code page files.
Basically, the team responsible for designing of AFP forms, created the *.UCM files. In our case the files were

ibm-37_P100-1995.ucm
ibm-284_P100-1995.ucm
ibm-393_p100-2005.ucm
ibm-500_P100-1995.ucm
ibm-2065_p100-2005.ucm
ibm-2100_p100-2005.ucm

and then, with the indications of technote 7007227 that is not longer available, I created the CNV files and put again to icudt30l.dat. After that, all of the mapping fonts all mapping fonts worked successfully. 

On the last week I started with some tests with the thick client to see what happens with the mapping fonts. I read that OnDemand thick client 8.4 is compatible wth Server 8.3; for that reason I installed client 8.4.0.3 and followed the instructions in technote 1290484 (http://www-01.ibm.com/support/docview.wss?rs=129&uid=swg21290484)

a) I made a copy of 6 UCM files used originally

b) I remove the versi?n number and year in each file, for example, ibm-37_P100-1995.ucm was renamed as ibm-37.ucm

c) I edited each file and I changed the name in <code_set_name>. For example <code_set_name> "ibm-37_P100-1999" was changed to <code_set_name>  "ibm-37"

d) I executed makeconv -v command for each UCM file  to create the CNV file

e) I created icudt36l directory under C.\Program Files\IBM\OnDemamd\Locale and I copied *.CNV files indicated in point d)

f) Also, according indicated in PMR 91366,379,000 I did the following:

If you have followed the above technote (7007227) and created custom convertors
for the OnDemand Client version 7.1.2.1 through 7.1.2.9 using ICU 3.0,
you might need to copy the previously created cnvalias.icu file to the
ICU 3.6 data directory created in step 3.

Because the preciously created cnvalias.icu file can reference ICU 3.0
convertors that have been updated in ICU 3.6, you may also need to copy
a few additional *.cnv files extracted using ICU 3.0 to the ICU 3.6 data
directory.  For example, if an old convertor such as
ibm-2065_xxxx-xxxx.cnv is needed and it has been updated from
ibm-2065_p100-2005.cnv to ibm-2065_p100-2006.cnv, you will need to copy
ibm-2065_p100-2005.cnv to the ICU 3.6 data directory.

Someone can tell me what could be worng in my process?

Thanks in advance
Federico

3

MP Server / Upgrade OnDemand 8.3 to 8.5

« on: August 30, 2012, 09:59:57 AM »

Hello, I have to upgrade Ondemand 8.3 (7.1.2.6) to 8.5 and I read some articles in this forum about that and also IBM technical documents. I would make the migration in the following way, but I would like your opinion if you have already been through this experience ..

Current Architecture
AIX: 5.3.11.0 64-bit
OnDemand: 7.1.2.6
DB2: 8.2 FP7 32-bit
TSM Client API: 5.5 32-bit

Architecture after upgrade
AIX: 6.1 64 bit
OnDemand: 8.5.0.4 64-bit
DB2: 9.7 FP5 64-bit
TSM Client API: 6.2 64-bit

Initially we will clone the current server into a new server, in this way, my idea is to make all the migration in the new hardware without users connected working with the application and also have the server available for download/upload services, software installation, etc, etc.

The tasks would be:

1. Backup OnDemand Database, File Systems and configuration files
2. Migrate OnDemand instance from 32 to 64 bits
3. Application test
4. Upgrade OnDemand 7.1.2.6 to 7.1.2.15 (I think may be is not necessary)
5. Application test
6. Install DB2 9.7 64 bits
7. Install latest DB2 9.7 fix pack
8. Backup OnDemand Database, File Systems and configuration files
9. DB2 Upgrade process to convert OnDemand Database from 8.2 to 9.7
10. Uninstall OnDemand 8.3
11. Install OnDemand 8.5.0.0 and 8.5.0.0 ODWEK
12. Run commands to use Database with OnDemand 8.4.1 or higher
   arsdb-I instance_name-uv
   arsdb-I instance_name-mv

13. Run commands to modify System Log table
   arssyscr -I instance_name -l
   arstblsp -I instance_name -a 1 -g "System Log"

14. Run commands to create table System Load
   i. Run the Following SQL query:
   select id from arssys

   ii. If the value returned is less than 5000, run the Following SQL command:
   Update Arssys UPDATE SET id = 5000

   iii. Run the Following Command:
   arssyscr-I instance_name-a

15. Recreate ARSUSRGRP, ARSLOAD, ARSNODE, and tables index ARSAPP
   i. Drop the indexes:
   arsdb-I instance_name-efv arsusrgrp
   arsdb-I instance_name-efv arsload
   arsdb-I instance_name-efv arsnode
   arsdb-I instance_name-efv arsapp

   ii. Create the new indexes:
   arsdb-I instance_name-rfv arsusrgrp
   arsdb-I instance_name-rfv arsload
   arsdb-I instance_name-rfv arsnode
   arsdb-I instance_name-rfv arsapp

   iii. Reorg and update statistics on all the OnDemand system tables:
   arsdb-I instance_name-mv

16. Install IBM Global Security Kit Crypt V8 and IBM Global Security Kit V8 SSL
17. Application test
18. Backup OnDemand Database, File Systems and configuration files
19. Upgrade OnDemand and ODWEK to 8.5.0.4 following instructions of each readme
20. Application test
21. Upgrade TSM API Client from 5.5 32 bits to 6.2 64 bits
22. Application test
23. Install WAS 7.0.0.0
24. Install latest WAS 7.0 fix pack
25. Install 1.0.4.4 WEBi
26. OnDemand testing from WEBi

If everything goes well, I'll plan the migration to OD 9.

I appreciate your comments and suggestions
Thanks and regards
Federico Bucchi