-
Notifications
You must be signed in to change notification settings - Fork 28
Dev: Setting up Windup web
Ondrej Zizka edited this page Feb 27, 2017
·
1 revision
Notes about how to develop and test.
How to setup windup-web video.
- Build windup core (and all it needs before that).
- Build
windup-web
. - Configure WildFly JMS queues. CLI script:
jms-queue add --queue-address=executorQueue --entries=queues/executorQueue
jms-queue add --queue-address=statusUpdateQueue --entries=queues/statusUpdateQueue
jms-queue add --queue-address=packageDiscoveryQueue --entries=queues/packageDiscoveryQueue
- Install and configure Keycloak
- Start WildFly 10 / EAP 7
- Deploy
windup-web/services
. - Create an exploded
windup-web/ui
deployment, point it to the exploded WAR intarget/
In standalone.xml
:
<deployments>
<deployment name="windup-web-services" runtime-name="windup-web-services.war">
<fs-exploded path="/home/ondra/work/Migration/windup-web/services/target/windup-web-services"/>
</deployment>
<deployment name="windup-web" runtime-name="windup-web.war">
<fs-exploded path="/home/ondra/work/Migration/windup-web/ui/target/windup-web"/>
</deployment>
</deployments>
Once this is set up, you can undeploy and deploy using CLI:
undeploy windup-web-services.war
/deployment=windup-web/:deploy
## This wouldn't work because it would not add the .war suffix:
deploy /home/ondra/work/Migration/windup-web/services/target/windup-web-services --unmanaged