Note
In the previous chapter (i2b2 Server-Common Install) we intentionally did not restart JBoss.
- If you did restart JBoss then you need to proceed with this step.
- If you did not restart JBoss then you can skip this step.
- If you are not sure if JBoss is running then we suggest you proceed with this step in the event that it may be running.
Stop JBoss
In order to deploy the PM cell correctly on your i2b2 server it is important that JBoss is not running.
The process of stopping your WildFly Server depends on your environment and the appropriate steps have been outlined in one of the following sections.
- If your WildFly is running as a Linux Service please proceed to the section on this page titled Stop WildFly Linux Service.
- If your WildFly is running as a Windows Service please proceed to the section on this page titled Stop WildFly Windows Service.
Stop WildFly Linux Service
The following steps will walk you through the process of stopping your WildFly server via a Linux service.
Note
These steps are written as if your WildFly Server is running as a Linux service. If you have not setup your WildFly to run as a Linux service and would like to do so please see Run WildFly as a Linux Service in the Requirements Chapter.
Stop WildFly Windows Service
The following steps will walk you through the process of stopping your WildFly server via a windows service.
Note
These steps are written as if your WildFly Server is running as a Windows service. If you have not setup your WildFly to run as a Windows service and would like to do so please see Run WildFly as a Windows Service in the Requirements Chapter.
Important
The actual name that appears in the list of services depends on what you entered in the service.bat file for the SVCDISP setting.