Questions Tagged With migrationhttps://answers.axonivy.com/tags/migration/?type=rssquestions tagged <span class="tag">migration</span>enFri, 21 Aug 2020 03:23:27 -0400The Q&A is dead, long live the communityhttps://answers.axonivy.com/questions/4666/the-q-a-is-dead-long-live-the-community<p>This Q&amp;A served us well for many years and it contains hundreds of threads which have been read thousands of times. Thank you so much for contributing to this space! Here we all shared our knowledge and inspired others by asking questions that really matter. </p> <p>However, the Q&amp;A as a platform has grown old and hit many technical limitations. Therefore, we decided to try something new. We still believe that joint efforts lead to highly effective projects. And we also love to experiment with extended collaboration features.</p> <p>As a result, we moved to a completely new space on <a href="http://community.axonivy.com">http://community.axonivy.com</a> . We hope to see you there soon. Right now is the perfect time to migrate: <a href="https://community.axonivy.com/d/33-share-your-pleasure-with-axonivy-and-win">share your passion</a> with us and, with some luck, you may win a fine local specialty from Zug.</p>Reguel WermelingerFri, 21 Aug 2020 03:23:27 -0400https://answers.axonivy.com/questions/4666/the-q-a-is-dead-long-live-the-communitymigrationUnmigrated request Start from Xpert.ivy 3.9https://answers.axonivy.com/questions/4662/unmigrated-request-start-from-xpert-ivy-3-9<p>Nach einer Migration von Xpert.ivy 3.9 nach Axon.ivy 7.0 steht eine Warnung auf dem "Request Start" Element, den Screenshot wollen Sie aber wegen meines schlechten Karmas nicht sehen :-(( Auf der Warnung steht sinngemäß, dass mit dem "nicht migrierten Start" die Gefahr einer unkontrollierten Übergabe von Prozessparametern besteht. Man solle für die weitere Bearbeitung in die 4.2 Designer Migration Notes schauen. Wahrscheinlich wurden diese aber mit der Version 7 nicht mehr ausgeliefert, deswegen muss ich nun hier nachfragen was konkret getan werden soll. Eigentlich soll alles so bleiben wie es migriert ist, Parameter werden nicht benötigt. Kann man das Element in einen "kontrollierten Start" umwandeln?</p>Thomas Wanka - logwinThu, 30 Jul 2020 07:25:19 -0400https://answers.axonivy.com/questions/4662/unmigrated-request-start-from-xpert-ivy-3-9migration3.9Switching the environment to a new physical hardwarehttps://answers.axonivy.com/questions/4621/switching-the-environment-to-a-new-physical-hardware<p>Hi Ivy team, </p> <p>We are facing the challenge, that our customer will switch the PROD-Enviornment to a new physical hardware within the next few month. </p> <p>We used ivy business data, task data and case data for storing the user data. We also create some folder inside the application folder and keep some pdf, image, doc file.....</p> <p>The question is - How can we switch the database from the old environment to the new one? - Can we export the DB from the old ivy instance and import it to the new one? - Is there any document / guide on how to do that?</p> <p>Thank you!</p>khanh11166Mon, 29 Jun 2020 04:14:40 -0400https://answers.axonivy.com/questions/4621/switching-the-environment-to-a-new-physical-hardwareengineenvironmentswitchmigrationList of things deprecated/no longer supported in version 8https://answers.axonivy.com/questions/4485/list-of-things-deprecated-no-longer-supported-in-version-8<p>Is there any list of things no longer supported in version 8? I'm planning on migrating a project from 7.3.1 to 8 and after the automatic project migration, I am still left with some errors.</p> <p>Moreover, I'm trying to get a feel of how complicated this migration might be.</p> <p>I've tried to read the release notes <a href="https://developer.axonivy.com/doc/8.0/ReleaseNotes.txt">here</a>, but they are a long list of very brief task/story titles which are not extremely helpful if you're not looking for something specific.</p>sorinWed, 01 Apr 2020 11:00:19 -0400https://answers.axonivy.com/questions/4485/list-of-things-deprecated-no-longer-supported-in-version-8migrationDoes HTML Dialogs support Java Class extended CompositeObject in Ivy 8 ?https://answers.axonivy.com/questions/4344/does-html-dialogs-support-java-class-extended-compositeobject-in-ivy-8<p>In Ivy 7, sometimes I use Java Class as a Caller Data for HTML Dialogs like the following picture, and it used to work perfectly <img alt="alt" src="https://i.ibb.co/48QXn7B/Screenshot-2.png"> Then I try to migrate my project to Ivy 8 and I realize that in the components that I am using JavaClass face this error <strong>Process data class 'Class Name' does not exist</strong></p> <p><img alt="alt text" src="https://i.ibb.co/zrVy7Wt/Screenshot-4.png"></p> <p>I also tried to create the new component but Ivy cannot find the JavaClass either </p> <p><img alt="alt text" src="https://i.ibb.co/cx0C9Dc/Screenshot-3.png"></p> <p>So in Ivy 8, does HTML Dialogs still support Java Class extended Composite Object ?. In case not, is there any alternative solution ? Thank you.</p>tdtinThu, 30 Jan 2020 01:47:40 -0500https://answers.axonivy.com/questions/4344/does-html-dialogs-support-java-class-extended-compositeobject-in-ivy-8migrationivyIvy 7.2.1 -> 7.3.1 Migrationhttps://answers.axonivy.com/questions/4017/ivy-7-2-1-7-3-1-migration<p>Hi Ivy Team</p> <p>After migrating sys db and running the application we get the following error :</p> <pre><code> Caused by: ch.ivyteam.ivy.persistence.PersistencyException: Unknown system property 'Database.Id' at ch.ivyteam.ivy.application.internal.ApplicationConfigurationManager.lambda$32(ApplicationConfigurationManager.java:1351) at java.util.Optional.orElseThrow(Optional.java:290) at ch.ivyteam.ivy.application.internal.ApplicationConfigurationManager.getSystemProp(ApplicationConfigurationManager.java:1351) at ch.ivyteam.ivy.application.internal.ApplicationConfigurationManager.getSystemProperty(ApplicationConfigurationManager.java:1336) at ch.xpertline.xent.oauth.ivy.IvySecure.getIvySalt(IvySecure.java:17) </code></pre> <p>Any idea what is missing ?</p> <p>Best regards John</p>John MoserWed, 25 Sep 2019 07:31:38 -0400https://answers.axonivy.com/questions/4017/ivy-7-2-1-7-3-1-migrationivymigrationProblem when opening IvyAdmin after migrationhttps://answers.axonivy.com/questions/3061/problem-when-opening-ivyadmin-after-migration<p>Hi everyone,</p> <p>Currently, I have encountered a problem after migration of the ivy engine (From 6.3 to 7). </p> <p>After successfully converted the database, I cannot open the Ivy Admin anymore. The error message I got is </p> <p><code>There is no process model version released for process model 'Administration' of application 'System'.</code> You can check the log below.</p> <p>Later on, I have to manually change the database of the engine, so that the process model of <code>Administration</code> is released. Could there be something not working correctly during conversion?</p> <p><img alt="alt text" src="https://answers.axonivy.com/upfiles/IMG_09012018_142346_0.png"></p> <pre><code>14:01:55.838 WARN [ch.ivyteam.ivy.webserver.internal.exception] [http-nio-8082-exec-1] [requestId=497, executionContext=SYSTEM, client=0:0:0:0:0:0:0:1] Problem while processing request 'http://localhost:8082/ivy/pro/System/Administration/115D746C75FAF428/start1.ivp' [errorId=160D9B9B9FFDD331, requestId=497, executionContext=SYSTEM, client=0:0:0:0:0:0:0:1] ch.ivyteam.ivy.request.RequestException: There is no process model version released for process model 'Administration' of application 'System'. at ch.ivyteam.ivy.request.RequestException$RequestExceptionBuilder.build(RequestException.java:166) at ch.ivyteam.ivy.webserver.internal.AbstractServlet.findProcessModelVersion(AbstractServlet.java:305) at ch.ivyteam.ivy.webserver.internal.AbstractServlet.analyzePathForProcessModelVersion(AbstractServlet.java:391) at ch.ivyteam.ivy.webserver.internal.process.IvyProcessServlet.doRespondAsSystem(IvyProcessServlet.java:47) at ch.ivyteam.ivy.webserver.internal.AbstractServlet.prepareRespondAsSystem(AbstractServlet.java:230) at ch.ivyteam.ivy.webserver.internal.AbstractServlet.access$3(AbstractServlet.java:212) at ch.ivyteam.ivy.webserver.internal.AbstractServlet$2.call(AbstractServlet.java:190) at ch.ivyteam.ivy.security.internal.SecurityManager.executeAsSystem(SecurityManager.java:1313) at ch.ivyteam.ivy.webserver.internal.AbstractServlet.doService(AbstractServlet.java:184) at ch.ivyteam.ivy.webserver.internal.AbstractServlet.doGet(AbstractServlet.java:168) at javax.servlet.http.HttpServlet.service(HttpServlet.java:635) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at ch.ivyteam.ivy.webserver.internal.exception.IvyExceptionFilter.doFilter(IvyExceptionFilter.java:49) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at ch.ivyteam.ivy.webserver.internal.IvyFilter.doFilterInternal(IvyFilter.java:247) at ch.ivyteam.ivy.webserver.internal.IvyFilter.doFilter(IvyFilter.java:152) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at ch.ivyteam.ivy.webserver.internal.IvyExecuteAsSystemFilter$1.call(IvyExecuteAsSystemFilter.java:45) at ch.ivyteam.ivy.webserver.internal.IvyExecuteAsSystemFilter$1.call(IvyExecuteAsSystemFilter.java:1) at ch.ivyteam.ivy.security.internal.SecurityManager.executeAsSystem(SecurityManager.java:1313) at ch.ivyteam.ivy.webserver.internal.IvyExecuteAsSystemFilter.doFilter(IvyExecuteAsSystemFilter.java:39) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:124) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at ch.ivyteam.ivy.webserver.internal.duplicate.IvyDuplicateRequestFilter.doFilter(IvyDuplicateRequestFilter.java:74) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at ch.ivyteam.ivy.webserver.internal.startup.IvyEngineUnavailableFilter.doFilter(IvyEngineUnavailableFilter.java:46) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:89) at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:120) at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:135) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:478) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:80) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87) at ch.ivyteam.ivy.webserver.internal.PerformanceLogValve.invoke(PerformanceLogValve.java:55) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:799) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1457) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:748) </code></pre>ToanLCTue, 09 Jan 2018 02:37:47 -0500https://answers.axonivy.com/questions/3061/problem-when-opening-ivyadmin-after-migrationivy7xmigrationMigration Ivy Server to another Machinehttps://answers.axonivy.com/questions/2994/migration-ivy-server-to-another-machine<p>Hello, Ivy Team,</p> <p>We are planning to move one existing installation of Axon.Ivy Server to another machine. What are the pitfalls in such scenarios? </p> <ul> <li>We will copy-paste the whole installation folder to the new server (the file system paths will be the same)</li> <li>We will attach the AxonIvySystemDatabse to the new server (p.s. we will also migrating to different db server)</li> <li>We need to change the license file</li> <li>We need to update the configuration to point to the new db server</li> <li>Probably we need to update the server name in the Admin UI </li> </ul> <p>All should be straightforward, right ? Are we missing something ?</p> <p>Best Regards, Yordan</p>Stelt0Tue, 21 Nov 2017 08:29:28 -0500https://answers.axonivy.com/questions/2994/migration-ivy-server-to-another-machineengineaxon.ivyconfigurationmigrationError by Converting IvyAddOnshttps://answers.axonivy.com/questions/2458/error-by-converting-ivyaddons<p>Hello,</p> <p>I use the new Axon Designer Version: 6.5.0 (Jakobshorn). On starting with a new Workspace i want Import the project IvyAddOns. I Imported it from the applications\utilities on the Desinger Installdirectory. After unpacking the Project an Errormessige shows that the Project needs to convert. </p> <p>"Project has wrong version and needs to be converted. Actual version is 51,917, required version is 63,000."</p> <p>I used the option "Convert Project" but it runs in an Error:</p> <p>Converting . Log is stored in 'logs/conversion51917-63000.log'</p> <p>Add REST client configuration to the project.</p> <pre><code>Unexpected error when converting project 'IvyAddOns'. ch.ivyteam.ivy.resource.datamodel.ResourceDataModelException: File restClients.restConfig already exists at ch.ivyteam.ivy.resource.datamodel.framework.AbstractProjectResourceDataModel.createNewDataModelFor(AbstractProjectResourceDataModel.java:121) at ch.ivyteam.ivy.rest.client.config.internal.ProjectRestClientsManager.initialize(ProjectRestClientsManager.java:70) at ch.ivyteam.ivy.designer.project.internal.convert.tasks.v70.CreateRestClientConfigurationFile.doConvertProject(CreateRestClientConfigurationFile.java:41) at ch.ivyteam.ivy.designer.project.restricted.convert.AbstractIvyProjectConverterTask.convertProject(AbstractIvyProjectConverterTask.java:96) at ch.ivyteam.ivy.designer.project.restricted.convert.IvyProjectConverter$1.run(IvyProjectConverter.java:305) at ch.ivyteam.eclipse.util.WorkspaceRunnable$1.run(WorkspaceRunnable.java:70) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2295) at ch.ivyteam.eclipse.util.WorkspaceRunnable.execute(WorkspaceRunnable.java:87) at ch.ivyteam.ivy.designer.project.restricted.convert.IvyProjectConverter.convertProject(IvyProjectConverter.java:328) at ch.ivyteam.ivy.designer.project.restricted.convert.IvyProjectConverter$2.run(IvyProjectConverter.java:498) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) </code></pre> <p>Thank you for HELP Ralf</p>rschreiterSun, 19 Feb 2017 11:47:48 -0500https://answers.axonivy.com/questions/2458/error-by-converting-ivyaddonsmigrationEntity Class Migrationshttps://answers.axonivy.com/questions/1872/entity-class-migrations<p>Hello Guys,</p> <p>I`m new to Hibernate and JPA. I have an Axon.Ivy project that has couple of Entity Classes. I want to move them in a separate project and separate namespace(package) and also to add some additional fields.</p> <p>What are the implications when I`m changing the data model and the namespaces ? How do I migrate the changes to the production server ?</p> <p>In .Net Entity Framework there is a concept of 'migrations' where the changes to the database are applied automatically when the code is deploys.</p> <p>Best Regards, Yordan Yunchov</p>Stelt0Wed, 06 Jul 2016 10:08:37 -0400https://answers.axonivy.com/questions/1872/entity-class-migrationsdataclassmigrationpersistenceMigration of Active Directory Serverhttps://answers.axonivy.com/questions/1859/migration-of-active-directory-server<p>I am migrating an enviroment onto new Servers. The Active Directory Servers are being migrated too. </p> <p>When I Switch to the new AD Server, what will happen to the Users which have all been designated one or more Roles?</p> <p>Will the Users be deleted and reimported, so that one will have to reassign the 200+ Users to their respective roles, or will the Users keep their Roles?</p>RMS71Mon, 04 Jul 2016 14:05:20 -0400https://answers.axonivy.com/questions/1859/migration-of-active-directory-serveractivedirectorymigrationserverLucene versions conflict when migrating from Xpert.ivy v4 to Axon.ivy v5https://answers.axonivy.com/questions/1256/lucene-versions-conflict-when-migrating-from-xpert-ivy-v4-to-axon-ivy-v5<p>Our project have encountered an urgent situation in which we have to migrate all modules into Axon.ivy v5.1.4. The migration have some serious trouble with Lucene.</p> <p>Our project uses Lucene v3.6.0 and we have the <code>lucene-core-v3.6.0.jar</code> in our <code>buildpath</code>. After migrating into Axon.ivy 5.1.4, the project cannot built anymore since we get strange complilation error:</p> <pre><code>Errors occurred during the build. Errors running builder 'Ivy Web Service Process Class Builder' on project 'test'. Bad return type Exception Details: Location: ch/test/lucene/LuceneManager.analyzer()Lorg/apache/lucene/analysis/Analyzer; @10: areturn Reason: Type 'org/apache/lucene/analysis/standard/StandardAnalyzer' (current frame, stack[0]) is not assignable to 'org/apache/lucene/analysis/Analyzer' (from method signature) Current Frame: bci: @10 flags: { } locals: { } stack: { 'org/apache/lucene/analysis/standard/StandardAnalyzer' } Bytecode: 0000000: bb00 f459 b200 28b7 00f6 b0 </code></pre> <p>We found out that the Axon.ivy has upgraded Lucene to v4.5.1 which contains a lots of incompatible changes compared to Lucene v3.6.0. <strong>The problem is we could not find a way to force the Axon.ivy build the project with <code>lucene-core-v3.6.0.jar</code> instead of the built-in <code>lucene-core-v4.5.1.jar</code></strong></p> <h1>UPDATE</h1> <p>We later tried to upgrade our implementation into Lucene 4.5.1 but got several other problems:</p> <p>(1) Axon.ivy issues warnings about we are trying to access Lucene API.</p> <p>(2) Start the project in Axon.ivy Designer will encounter <code>ClassNotFoundException</code>: </p> <pre><code>Caused by: java.lang.NoClassDefFoundError: org/apache/lucene/analysis/Analyzer at ch.soreco.alag.ria.service.taskindex.LucenceHandler.startLuceneInstance(LucenceHandler.java:6) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at ch.ivyteam.ivy.scripting.internal.types.IvyJavaMethod.invokeImpl(IvyJavaMethod.java:73) ... 35 more Caused by: java.lang.ClassNotFoundException: org.apache.lucene.analysis.Analyzer at ch.ivyteam.ivy.java.internal.IvyProjectClassLoader.loadClass(IvyProjectClassLoader.java:243) at java.lang.ClassLoader.loadClass(Unknown Source) ... 41 more </code></pre> <p>.. even if all the jars are shipped with Axon.ivy.</p> <p>(3) If we try to include the jars file into our projects (in the classpath), the build will halt with the <code>Bad Return Type</code> error above.</p> <h1>QUESTIONS</h1> <ul> <li>How could we force the Axon.ivy to build our projects using the <code>lucene-core-v3.6.0</code> instead of the <code>lucene-core-v4.5.1</code> shipped with Axon.ivy?</li> <li>Why do we get strange problems when building the projects with built-in Lucene library of Axon.ivy v5.1.4?</li> </ul> <h1>SAMPLE PROJECTS</h1> <p>I attach in this email the two sample projects which illustrate the problems we are facing. We tested the two with AxonIvyDesigner5.1.4.48243_Windows_x64:</p> <ul> <li><a href="https://app.box.com/s/ggaz5cuiip9g6wb1bdq2l1js7xxi2emx"><code>use_built_in_lucene.iar</code></a>: This project illustrates the problem which we cannot built the project if it uses Lucene's classes.</li> <li><a href="https://app.box.com/s/j8gkpnxnmr9oydyelxy446ej7urqb6d9"><code>use_external_lucene.iar</code></a>: This project illustrates the problem which we purposely include the Lucene's jar files but the project still fails.</li> </ul> <h1>UPDATE 2 (extend the answer)</h1> <p>The solution from Reguel Wermelinger which suggest to repack all the classes in <code>lucene-core-v3.6.0.jar</code> in different package name works.</p> <p>1- Download <a href="https://code.google.com/p/jarjar/downloads/list">JarJar</a> (hosted on Google Code, if you read this after 25.01.2016, please search it on GitHub).</p> <p>2 - Put the file <code>lucene-core-v3.6.0.jar</code> at the same directory at JarJar.</p> <p>3 - Create a text file, namely <code>rules.txt</code>, contains one line</p> <pre><code>rule org.apache.lucene.** org.apache.lucene.v3_6_0.@1 </code></pre> <p>4 - Execute the command</p> <pre><code>$ java -jar jarjar.jar rules.txt lucene-core-v3.6.0.jar lucene-core-v3.6.0-repacked.jar </code></pre> <p>5 - Done!</p> <p>You can download the already-repackged <a href="https://app.box.com/s/9efw6bxhm8gkws25gd34d44qwu30662r"><code>lucene-core-v3.6.0-repacked.jar</code></a></p> <p>Please note that this is only a work-around. The Axon.ivy still has problem if you use the Lucene v4.5.1 shipped with it.</p>Genzer HawkerMon, 13 Apr 2015 08:07:15 -0400https://answers.axonivy.com/questions/1256/lucene-versions-conflict-when-migrating-from-xpert-ivy-v4-to-axon-ivy-v5luceneivy4x-migrationivymigration