Hi Karl,
thanks for the detailed input. That helped me to sort out our options.
I looked into our job configurations and it came out that we don't use
forced metadata or solr field mappings any more. They were already
migrated to the transformation pipeline. So i think it is possible to
recreate the configuration with the export/import commands.
But i will need to customize the import routine a little bit to step
over the version check and ignore the import of the forced metadata
settings.
We will take no further actions to avoid (2) and (3) and live with that.
(too many uncertainties, cost/benefit decision)
Regards,
Markus
Am 25.02.2016 um 13:34 schrieb Karl Wright:
Hi Markus,
Here's the first draft of the page I promised.
https://cwiki.apache.org/confluence/display/CONNECTORS/Migrating+ManifoldCF+installations+across+major+versions
Karl
On Thu, Feb 25, 2016 at 3:09 AM, Karl Wright <[email protected]
<mailto:[email protected]>> wrote:
Hi Markus,
>>>>>>
we plan to migrate from ManifoldCF 1.7.1 to ManifoldCF 2.3.
Is there a migration guide available?
>>>>>>
There's no automatic upgrade here not simply because of schema
changes but because in many cases duplicate functionality was
removed from various connectors. That means that your jobs and
connections would, in most cases, need to be recreated anyway.
Even export and import could not be made automatic for this reason.
There was an extended period, however, when MCF 1.x and 2.x
releases occurred together, and had functional equivalence. The
most recent pair was 1.10 + 2.2. There is an *automatic* upgrade
for 1.7->1.10. I would therefore suggest that you attempt upgrade
to 1.10 before looking at the issues of going from 1.x to 2.x.
>>>>>>
We want to run ManifoldCF 2.3 on Java 8 in a Servlet-API 3.0
container (Tomcat 7), which is - for now - predefined by our OPs.
Is this possible? Or is Servlet now API 3.1 required? (we notices
that the shipped standalone deployment now works with Jetty 9)
<<<<<<
The only reason for the servlet API upgrade was for Jetty 9 to
work. Java 8 should work fine. I also expect Tomcat 7 to work
fine, but the simple way to test this would be to deploy the
standalone combined war in a test environment and see how it
does. That way you will know of any issues before you take the
plunge.
As for documentation -- it is a good point that we could use a
migration guide. I'll create a ticket to write one.
Hope this helps.
Thanks,
Karl
On Thu, Feb 25, 2016 at 2:42 AM, Markus Schuch
<[email protected] <mailto:[email protected]>> wrote:
Hi,
we plan to migrate from ManifoldCF 1.7.1 to ManifoldCF 2.3.
Is there a migration guide available?
We want to run ManifoldCF 2.3 on Java 8 in a Servlet-API 3.0
container (Tomcat 7), which is - for now - predefined by our OPs.
Is this possible? Or is Servlet now API 3.1 required? (we
notices that the shipped standalone deployment now works with
Jetty 9)
I think it would be helpful if the ManifoldCF website would
give some hints on required platform and API versions besides
the connectors.
We saw the chema changes in the changelog and we expect that
we will have to start 2.x on an empty database and manually
recreating all our configuration.
This has some downsides:
(1) manual configuration effort
(2) loss of the job queue -> full reindex necessary
(3) loss of the history
For (1) we want look into the configuration export/import
commands or the REST API.
Is the configuration export/import compatible between 1.x and 2.x?
Did anybode use those commands for a migration or is the REST
API the only reasonable way?
Has anybody ideas about (2) and (3)?
Many thanks in advance
Markus
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
