nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OpenDeploy upgrade 5.6 to 6.1

marcussteiner

Hi all,

I know we are one year late but still we are running on OD/DD 5.6 and are planning to upgrade to 6.1. Since we are massivly using DAS for both the preview and the live deployment I would like to hear about you experience since it seems we're not able to run both versions OD 5.6/6.1 using DAS on the same server. I've identified three scenarios so far and would like to hear how you got around this problem of upgrading. The following things need to be considered:

Since we're using the eventsubsystem will this be able to cope with both versions at least for the transition period when testing the new release?

We're using the datatype_dd.cfg files generated from DAS for each datatype also for the triggering standalone deployments using iwdd.ipl cfg=/default/... which needs to be in the new default location OpenDeploy/conf.

I've identified the three following scenarios for the upgrade:

1.) Use the upgrade feature of OD:
This will install OD/DD 6.1 in the same location of the old version and will overwrite the old config files. This scenario will not allow a rollback in case of any issues other than a full recovery of the system. So when the upgrade is done we can only pray to hope that everything works fine. Question: Has anybody done this yet and what is the experience with that. Will be able to use the same config files (general and _dd.cfg) after the upgrade or will we need to do a iwsyncdb -initial when done. Also will this have any impacts on the tables being created with regards to table names and column names?

2.) Install OD in seperate location on the same server
This will install both versions on the same server but will not allow us to run them both at the same time. On the other hand we would be able to use the old release when we're not happy with the tests of the new version. This
would allow us to stop DAS on the old version and start DAS on the new version for testing. This would involve a new schema for the database and potential a new target directory. When happy just switch off the old version and use the new verison. The only thing we need to take care of here is to make sure that there are no port conflicts. Any experience of how the eventsubsystem will cope with this scenario?

3.) Install OD in seperate location on different server
Same scenario as the second but not sure if this is possible in the first place to have a OD base server just for the deployments with no TS installation. This would not involve and port conflicts on the sender side.

don't ask!!

Any ideas are highly appreciated

M

TS 6.1 OD/DD 5.6 on Solaris

Find more posts tagged with

Comments

marcussteiner

Yes I know we're late and yes I know it is a lot of text to read. But still your feedback would be appreciated.

many thanks.

Adam Stoller

Yes I know we're late and yes I know it is a lot of text to read. But still your feedback would be appreciated.

many thanks.

I don't use DD too often, so the comments I have are fairly generic:

/OpenDeployNG - and from a customization stand-point you'd probably like to keep that directory the same as it was to minimize the ripple-effect of changing the version of OD/DD on all your other customizations.