Create Windows service Identity Portal
search cancel

Create Windows service Identity Portal

book

Article ID: 257731

calendar_today

Updated On:

Products

CA Identity Portal

Issue/Introduction

A customer was following the below document to run Wildfly as a Windows Service.
https://community.i2b2.org/wiki/display/getstarted/2.4.2.4+Run+Wildfly+as+a+Windows+Service

It is working when the customer tried to launch Identity Portal User Console with localhost in the URL in the browser.
But when the customer tried the same using the IP of the server it doesn't work.

Whereas when the customer started the service using manually using the below command:
"standalone.bat -b=0.0.0.0 -bmanagement=0.0.0.0"

Both the localhost and IP address of the server is working fine.

Environment

Release : 14.4

Resolution

Go to standalone.xml configuration file that is saved into C:\CA\wildfly-15.0.1.Final\standalone\configuration PATH and open with Notepad++ or Visual Studio Code

Change the value under <interface name="public">
From:
<inet-address value="${jboss.bind.address:127.0.0.1}"/>
To:
<inet-address value="${jboss.bind.address:0.0.0.0}"/>

And then enter the following command to install the service:
$ service install

Now start the Wildfly service under services in the Windows machine, Both the localhost and IP address of the server should be working fine.

Additional Information

https://dev.to/orestispantazos/wildfly-as-windows-service-456c