Issue with Changing tomcat port for Flowable-Modeler

banur · August 22, 2019, 8:58am

Newbie question. I just installed flowable today. I changed the tomcat port from 8080 to 18080 in $CATALINA_HOME/conf/server.xml .
After this, I am able to access the IDM app from http://localhost:18080/flowable-idm/
However, when I try to access the modeler or task apps, I am unable to. when I type http://localhost:18080/flowable-modeler on my browser, I am redirected to
localhost:8080/flowable-idm/#/login?redirectOnAuthSuccess=true&redirectUrl=http://localhost:18080/flowable-modeler/

Manually changing the URL to localhost:18080/flowable-idm/#/login?redirectOnAuthSuccess=true&redirectUrl=http://localhost:18080/flowable-modeler/ also does not help.

Please, can someone suggest if I am doing something wrong?
Flowable version: 6.4.2
Tomcat version: 9.0.24

PascalSchumacher · August 27, 2019, 6:10pm

You have to change the flowable.common.app.idm-url property to http://localhost:18080/flowable-idm see:

https://www.flowable.org/docs/userguide/index.html#_flowable_ui_applications_configurations

For an example check out:

github.com

flowable/flowable-engine/blob/master/modules/flowable-ui-modeler/flowable-ui-modeler-app/src/main/resources/flowable-default.properties

server.port=8888
server.servlet.context-path=/flowable-modeler
management.endpoints.jmx.unique-names=true
# This is needed to force use of JDK proxies instead of using CGLIB
spring.aop.proxy-target-class=false
spring.aop.auto=false
spring.application.name=flowable-ui-modeler
#
# SECURITY
#
spring.security.filter.dispatcher-types=REQUEST,FORWARD,ASYNC
spring.liquibase.enabled=false
spring.banner.location=classpath:/org/flowable/spring/boot/flowable-banner.txt
# The default domain for generating ObjectNames must be specified. Otherwise when multiple Spring Boot applications start in the same servlet container
# all would be created with the same name (com.zaxxer.hikari:name=dataSource,type=HikariDataSource) for example
spring.jmx.default-domain=${spring.application.name}

# Expose all actuator endpoints to the web
# They are exposed, but only authenticated users can see /info and /health abd users with access-admin can see the others
management.endpoints.web.exposure.include=*

This file has been truncated. show original

banur · August 28, 2019, 9:31pm

Many thanks. That is exactly what I had missed.

Topic		Replies	Views
Problem login to flowable-task because wrong redirect Flowable Application	8	2961	April 26, 2017
Login fail being redirect to localhost:8080? Flowable Engine	3	3994	June 4, 2018
Can't access to "Flowable-Modeler", "Flowable-Task", "Flowable-Admin" sites Flowable Engine	9	4041	December 23, 2018
Can’t get access to Flowable-modeler, Flowable-task and other Flowable Engine	2	693	May 24, 2019
Accessing flowable apps other than idm	0	947	September 21, 2018

Issue with Changing tomcat port for Flowable-Modeler

Related topics