Windows: Upgrade TIM & Wildfly
from TIM Version 7.11.0 upwards
Database
Check required database version (release notes)
Backup database
If needed update database
Java
Check required Java version (release notes)
If needed download required version from Adoptium
Install and set JAVA_HOME for the system
TIM
Check release notes for required wildfly version
Download wildfly.zip, wildfly-delta.zip, dashboard.war & timVERSION
Create backup folders e.g. C:\tim\backup\date\old & C:\tim\backup\date\new
Stop TIM Service
Move existing folder C:\tim\wildflyVERSION-ENVIRONMENT\ to C:\tim\backup\date\old
Extract wildfly.zip to C:\tim\backup\date\new\wf-ver-env
Extract wildfly-delta.zip and copy folder content into C:\tim\backup\date\new\wf-ver-env replace existing files
Copy folder C:\tim\backup\date\new\wf-ver-env\docs\contrib\scripts\service to C:\tim\backup\date\new\wf-ver-env\bin\
Edit C:\tim\backup\date\new\wf-ver-env\bin\service\service.bat & change SHORTNAME and DISPLAYNAME to e.g. TIM39DEV | TIM%WFversion%%Environment%
CONTROLLER=localhost:9990 in service.bat needs to match jboss.management.http.port in standalone-tim.xml
important if multiple app server are installed on one host machine
Replace following files from C:\tim\backup\date\old to C:\tim\backup\date\new
\wf-ver-env\standalone\configuration\jwt.keystore
\wf-ver-env\ssl\keystore.jks
\wf-ver-env\ssl\truststore.jks
\wf-ver-env\standalone\configuration\tim_store_secret.cs
\wf-ver-env\standalone\configuration\tim-ldap.properties
\wf-ver-env\standalone\configuration\dashboard.properties
\wf-ver-env\standalone\configuration\tim.propertiesfor updates after wildfly 37
\wf-ver-env\standalone\configuration\pepper.cs
needs to be moved to the new wildfly
If needed download additional keystore explorer tool
Unzip downloaded timVERSION folder and move timVERSION.ear file to
C:\tim\backup\date\new\wf-ver-env\standalone\deployments
If timVERSION.ear is a directory custom handler may be in use
In this case follow custom handler instruction
Move dashboard.war file to C:\tim\backup\date\new\wf-ver-env\standalone\deployments
Open C:\tim\backup\date\new\wf-ver-env\standalone\configuration\standalone-tim.xml to configure the data source.
Replace env-data only, xml syntax does change
<datasources>
<datasource jta="true" jndi-name="java:/doorisPortalDB" pool-name="doorisPortalDB" enabled="true" use-java-context="true" use-ccm="false">
<connection-url>${env.JDBC_CONNECTION,jboss.JDBC_CONNECTION:jdbc:sqlserver://localhost:1433;databaseName=tim;}</connection-url>
<driver>${env.JDBC_DRIVER,jboss.JDBC_DRIVER:sqlserver}</driver>
<pool>
<min-pool-size>20</min-pool-size>
<max-pool-size>150</max-pool-size>
</pool>
<security>
<user-name>${env.DBUSER,jboss.DBUSER:sa}</user-name>
<password>${env.DBPASSWORD,jboss.DBPASSWORD:t1m}</password>
</security>
<validation>
<check-valid-connection-sql>${env.CHECK_ALIVE_QUERY,jboss.CHECK_ALIVE_QUERY:SELECT 1 FROM TIM_DUAL}</check-valid-connection-sql>
<validate-on-match>true</validate-on-match>
<background-validation>false</background-validation>
<use-fast-fail>false</use-fast-fail>
</validation>
</datasource>
...
</datasources>Set port offset at the end of C:\tim\backup\date\new\wf-ver-env\standalone\configuration\
standalone-tim.xml file
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${env.socket.binding.port-offset,jboss.socket.binding.port-offset:0}">
<socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>
<socket-binding name="http" port="${jboss.http.port:8080}"/>
<socket-binding name="https" port="${jboss.https.port:8443}"/>
<socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
<socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>
<socket-binding name="txn-recovery-environment" port="4712"/>
<socket-binding name="txn-status-manager" port="4713"/>
<outbound-socket-binding name="mail-smtp">
<remote-destination host="${jboss.mail.server.host:localhost}" port="${jboss.mail.server.port:25}"/>
</outbound-socket-binding>
</socket-binding-group>Open C:\tim\backup\date\new\wf-ver-env\bin\standalone.conf.bat & configure following to be disabled:
# TIM Solutions GmbH Configuration part
# Feel free to edit this configuration below!
#JAVA_OPTS="$JAVA_OPTS -Djboss.socket.binding.port-offset=0"
#JAVA_OPTS="$JAVA_OPTS -Djboss.http.port=8080"
#JAVA_OPTS="$JAVA_OPTS -Djboss.JDBC_CONNECTION=jdbc:sqlserver://database.fqdn:1433\;database=tim\;encrypt=true\;loginTimeout=30\;"
#JAVA_OPTS="$JAVA_OPTS -Djboss.JDBC_DRIVER=sqlserver"
#JAVA_OPTS="$JAVA_OPTS -Djboss.CHECK_ALIVE_QUERY='SELECT 1 FROM TIM_DUAL'"
#JAVA_OPTS="$JAVA_OPTS -Djboss.DBUSER=tim"
#JAVA_OPTS="$JAVA_OPTS -Djboss.DBPASSWORD=t1m"Compare C:\tim\backup\date\new\wf-ver-env\bin\standalone.conf.bat with C:\tim\backup\date\old\wf-ver-env\bin\standalone.conf.bat to check JAVA_HOME and Xms & Xmx configuration
Move C:\tim\backup\date\new\wf-ver-env folder to C:\tim\
Open cmd as adminstrator & install the service with following commands:
cd C:\tim\wf-ver-env\bin\service
service.bat install /config standalone-tim.xmlOpen Windows Services & navigate to TIM %WFVERSION% %ENVIRONMENT% e.g. TIM39DEV to set start type to automatic delayed
Start Service e.g. TIM39DEV
Check C:\tim\wf-ver-env\standalone\log\server.log for any issues to resolve.
Issues may be closed ports, connection to the database, missing permissions or antivirus intervention
Open http://hostname:port/loom-portal/license.htm & check validity of TIM license
Database changes require license renewal
Request license according to shown token id (single or multi node)
License can be ordered at License Request
For license activation please use https://hostname:port/loom-portal/license.htm
Open https://hostname:port/tim/client/ to log in
Replace unencrypted passwords with encrypted ones in
C:\tim\wf-ver-env\standalone\configuration\tim.properties &
C:\tim\backup\date\new\wf-ver-env\standalone\configuration\standalone-tim.xml
to decrypt already encrypted files after an update copy wfOLD/standalone/configuration/tim_store_secret.cs to wfNEW/standalone/configuration/
For further configuration check Operational Management Guide e.g SMTP, LDAP Auth & Sync or SSO with SAML
Feel free to contact TIM Servicedesk for assistance
© TIM Solutions GmbH | AGB | Datenschutz | Impressum