Start and Stop JBoss

Starting the Extended Server actually means to start several server processes on a server machine. For a Windows host these can be configured to run as Windows Services, for Unix types of servers and development servers you will start the server processes manually. It should be noted that starting of JBoss Application Server is relevant only if JBoss was selected as the application server.

Contents

Start the Extended Server Windows services

If you, during the installation have selected that you want Windows services, then all you have to do is to start the Windows services.

  1. Start the admin tool for Windows services.
    It's located in the Control Panel and it is called Services.
  2. Start the IFS JBoss Server <Instance> (<ifs_home>) service.
    Select the service and click the start icon in the toolbar.
  3. Start the IFS BatchServer1 <Instance> (<ifs_home>) service.
    Select the service and click the start icon in the toolbar.
  4. Start the IFS ConnectServer1 <Instance> (<ifs_home>) service.
    Select the service and click the start icon in the toolbar.

Start the Extended Server manually on Windows

If you do not want to use Windows services, then you have to start the IFS Servers manually. The program/scripts for JBoss Server, Batch Server and Connect Server are located in the <ifs_home>\instance\<Instance>\bin catalog.

  1. Start the JBoss Server

    The script is located in <ifs_home>\instance\<Instance>\bin
    Run the command start_jboss.cmd
  2. Start the Batch Server.

    The script is located in <ifs_home>\instance\<Instance>\bin
    Run command start_batchserver1.cmd
  3. Start the Connect Server.

    The script is located in <ifs_home>\instance\<Instance>\bin
     Run command start_connectserver1.cmd

Start the Extended Server manually on Unix types of OS

If you are not running on a Windows Machine, you have to start the Extended Server manually. The start scripts for Extended Server, Batch Server and Connect Server are located in the <ifs_home>/instance/<Instance>/bin catalog.

  1. Start the JBoss Server

    The script is located in <ifs_home>/instance/<Instance>/bin
    Run command jboss.sh start as user ifs
  2. Start the Batch Server.

    The script is located in <ifs_home>/instance/<Instance>/bin
    Run command ./batchserver1.sh start as user ifs
  3. Start the Connect Server.

    The script is located in <ifs_home>/instance/<Instance>/bin
     Run command ./connectserver1.sh start as user ifs

Template for boot/shutdown on Unix type of OS

A template for boot/shutdown is included as <ifs_home>/bin/ifsctl.sh.
This script should always be run as root and must be edited for your specific installation, e.g. if more Batch/Connect servers are added.

Unix Script Usage Reference

This section is a reference of the capabilities, location, and names of the Unix version of the server scripts.

Boot/shutdown template script

Command Script Basics
Location <ifs_home>/bin
Name ifsctl.sh
Comment Run as user root
Command Script Parameters
start calls subscripts with start argument
stop calls subscripts with stop argument
status calls subscripts with status argument

JBoss Server Script

Command Script Basics
Location <ifs_home>/instance/<Instance>/bin
Name jboss.sh
Comment Run as user ifs
Command Script Parameters
start starts the server
stop stops the server
status displays the status for the server

Batch Server Script

Command Script Basics
Location <ifs_home>/instance/<Instance>/bin
Name batchserver1.sh
Comment Run as user ifs
Command Script Parameters
start starts the server
stop stops the server
status displays the status for the server

Connect Server Script

Command Script Basics
Location <ifs_home>/instance/<Instance>/bin
Name connectserver1.sh
Comment Run as user ifs
Command Script Parameters
start starts the server
stop stops the server
status displays the status for the server

  

Verify

The different server are running.
 

The IFS Enterprise Explorer is a web deployed application. After running the standard installation the installation technician needs to sign the application. This is a security measure to assure that end users can trust the application.

Read more details about Signing IFS Enterprise Explorer. 

The next step is to test the Extended Server by logging on using IFS Enterprise Explorer.
If you can't find the Windows service in the Windows Services Tool. It's possible that the install program couldn't add the service or that you didn't select the server part to be installed as a Service.
Note: You can also install and uninstall the services at any time using the install_service_*.cmd and uninstall_service_*.cmd scripts.