5. Особенности установки ARTA Synergy 4.1 minsky¶
5.1. Процесс обновления¶
Перед установкой:
обязательно прописать hostname сервера (см. раздел «Переход к использованию Wildfly»):
# echo "127.0.0.1 $(hostname)" >> /etc/hosts
при необходимости создать резервные копии конфигурационных файлов:
/etc/default/arta-synergy-jboss
/opt/synergy/jboss/bin/standalone.conf
/opt/synergy/jboss/standalone/configuration/standalone.xml
/opt/synergy/jboss/standalone/configuration/standalone-full.xml
/opt/synergy/jboss/standalone/deployments/Synergy.ear/META-INF/jboss-deployment-structure.xml
/opt/synergy/utils/configs/nginx/synergy-base
/opt/synergy/jboss/standalone/configuration/arta/esb/docIndex.xml
/opt/synergy/jboss/standalone/configuration/arta/esb/fileIndex.xml
/opt/synergy/jboss/standalone/configuration/arta/esb/formIndex.xml
/opt/synergy/jboss/standalone/configuration/standalone-onesynergy.xml
/opt/synergy/jboss/standalone/deployments/Synergy.ear/META-INF/application.xml
/opt/synergy/jboss/standalone/configuration/arta/api-observation-configuration.xml
сделать резервные копии баз данных и Хранилища
Во время установки: необходимо принять рекомендованные изменения конфигурационных файлов и решения по изменению/удалению пакетов Synergy:
The following NEW packages will be installed:
arta-synergy-webdav{a}
The following packages will be upgraded:
arta-synergy-deps-jackrabbit arta-synergy-esb{b} arta-synergy-jboss{b} arta-synergy-synergy{b} arta-synergy-utils
5 packages upgraded, 1 newly installed, 0 to remove and 154 not upgraded.
Need to get 847 MB of archives. After unpacking 282 MB will be used.
The following packages have unmet dependencies:
arta-synergy-jboss : Conflicts: arta-synergy-deps-mysqldriver (<= 5.1.42) but 5.1.42 is installed.
arta-synergy-synergy : Conflicts: arta-synergy-jbpm but 3.11-r2 is installed.
arta-synergy-esb : Conflicts: arta-synergy-indexator (<= 4.1-r1~181119.114741) but 4.0-r1~181030.182506 is installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) arta-synergy-deps-mysqldriver
2) arta-synergy-indexator
3) arta-synergy-jbpm
Accept this solution? [Y/n/q/?] y
Configuration file `/etc/default/arta-synergy-jboss'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** arta-synergy-jboss (Y/I/N/O/D/Z) [default=N] ? y
Installing new version of config file /etc/default/arta-synergy-jboss ...
Configuration file `/opt/synergy/jboss/bin/standalone.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** standalone.conf (Y/I/N/O/D/Z) [default=N] ? y
Installing new version of config file /opt/synergy/jboss/bin/standalone.conf ...
Configuration file `/opt/synergy/jboss/standalone/configuration/standalone.xml'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** standalone.xml (Y/I/N/O/D/Z) [default=N] ? y
Installing new version of config file /opt/synergy/jboss/standalone/configuration/standalone.xml ...
Configuration file `/opt/synergy/jboss/standalone/configuration/standalone-full.xml'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** standalone-full.xml (Y/I/N/O/D/Z) [default=N] ? y
Configuration file `/opt/synergy/jboss/standalone/deployments/Synergy.ear/META-INF/jboss-deployment-structure.xml'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** jboss-deployment-structure.xml (Y/I/N/O/D/Z) [default=N] ? y
5.2. После обновления¶
Если используется хранилище Cassandra, проверить конфигурационный файл
/opt/synergy/jboss/standalone/deployments/Synergy.ear/META-INF/application.xml
, он должен содержать следующий блок:<module> <ejb>ArtaJCR.war</ejb> </module>
а файл
/opt/synergy/jboss/standalone/deployments/Synergy.ear/META-INF/jboss-deployment-structure.xml
- блок<sub-deployment name="AiBean.jar"> <dependencies> <module name="deployment.Synergy.ear.ArtaJCR.war"/> </dependencies> </sub-deployment>
Если используется индексатор Elasticsearch, включить его в нужных конфигурационных файлах в папке
/opt/synergy/jboss/standalone/configuration/arta/esb/
Выполнить обновление БД в Административном приложении Synergy
Остановить
jboss
и выполнить утилиту для обновления индексов Lucene (см. раздел «Обновление Lucene»):# /opt/synergy/utils/lucene/upgrade-to-lucene-7.sh
В случае успешного апгрейда индексов вывод команды будет таким:
Reading paths from /opt/synergy/jboss/standalone/configuration/arta/luceneConfiguration.xml: /var/lib/synergy/documentIndex /var/lib/synergy/formIndex /var/lib/synergy/index ======================== Upgrade /var/lib/synergy/documentIndex to: Lucene version 4.10.4... done. Lucene version 5.5.0... done. Lucene version 6.3.0... done. Lucene version 7.3.1... done. ======================== Upgrade /var/lib/synergy/formIndex to: Lucene version 4.10.4... done. Lucene version 5.5.0... done. Lucene version 6.3.0... done. Lucene version 7.3.1... done. ======================== Upgrade /var/lib/synergy/index to: Lucene version 4.10.4...done. Lucene version 5.5.0... done. Lucene version 6.3.0... done. Lucene version 7.3.1... done. ======================== Upgrade to Lucene 7 went OK!
При возникновении ошибок при обновлении индексов нужно их удалить и выполнить переиндексацию. Подробное описание приведено в разделе «Обновление Lucene».
В конфигурационном файле nginx прописать строки вида:
location /asforms { proxy_pass http://127.0.0.1:8080/asforms; }
После повторного старта
arta-synergy-jboss
в Административном приложении переиндексировать формы, файлы и документы.Проверить, что все дочерние
war
успешно задеплоены. Из-за перехода к использованию Wildfly возможно, что некоторые приложения не будут запущены:22:46:14,491 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 105) MSC000001: Failed to start service jboss.deployment.unit."itsm.war".component.java:global/ItsmStartupBean.START: org.jboss.msc.service.StartException in service jboss.deployment.unit."itsm.war".component.java:global/ItsmStartupBean.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) [wildfly-ee-14.0.0.Final.jar:14.0.0.Final] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_131] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_131] at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131] at org.jboss.threads.JBossThread.run(JBossThread.java:485) Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) [wildfly-ee-14.0.0.Final.jar:14.0.0.Final] at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134) [wildfly-ee-14.0.0.Final.jar:14.0.0.Final] at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) [wildfly-ee-14.0.0.Final.jar:14.0.0.Final] at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:127) at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [wildfly-ee-14.0.0.Final.jar:14.0.0.Final] ... 8 more Caused by: javax.ejb.EJBException: WFLYEJB0442: Unexpected Error at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:250) at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:388) at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:68) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) [jboss-invocation-1.5.1.Final.jar:1.5.1.Final] at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) [jboss-invocation-1.5.1.Final.jar:1.5.1.Final] at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-14.0.0.Final.jar:14.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) [jboss-invocation-1.5.1.Final.jar:1.5.1.Final] at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) [jboss-invocation-1.5.1.Final.jar:1.5.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) [jboss-invocation-1.5.1.Final.jar:1.5.1.Final] at org.jboss.as.ejb3.component.singleton.StartupCountDownInterceptor.processInvocation(StartupCountDownInterceptor.java:25) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) [jboss-invocation-1.5.1.Final.jar:1.5.1.Final] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) [jboss-invocation-1.5.1.Final.jar:1.5.1.Final] at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [wildfly-ee-14.0.0.Final.jar:14.0.0.Final] ... 13 more Caused by: java.lang.NoSuchMethodError: kz.arta.itsm.rest.SettingsApi.readJsonResult(Ljava/net/HttpURLConnection;)Lorg/codehaus/jackson/JsonNode; at kz.arta.itsm.rest.SettingsApi.loadCalendar(SettingsApi.java:49) at kz.arta.itsm.bean.StartupBean.loadSettings(StartupBean.java:51) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_131] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_131] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_131] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_131] at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:96) [wildfly-ee-14.0.0.Final.jar:14.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) [jboss-invocation-1.5.1.Final.jar:1.5.1.Final] at org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28) [wildfly-ee-14.0.0.Final.jar:14.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) [jboss-invocation-1.5.1.Final.jar:1.5.1.Final] at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [wildfly-ee-14.0.0.Final.jar:14.0.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) [jboss-invocation-1.5.1.Final.jar:1.5.1.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:237) ... 26 more
В случае возникновения такой проблемы обратитесь к рекомендациям по восстановлению работы внешних модулей (см. раздел «Переход к использованию WildFly»).