Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Apart from starting Adeptia Connect application manually, you can also configure it to be started automatically as a service at the start of your system running on Linux. 

The details below guide you on how to start the application in both manual and automatic ways.

This page contains the following information:

Starting Connect Server

This section guides you on how to start Connect Server manually and automatically.

Prerequisite

Configure the systemd service in your Linux operation system.

Starting Connect Server manually

To start or stop the Connect Server Kernel, WebRunner, and AIMap, follow the steps below:

  1. Open Terminal.
  2. Go to the directory ...<ConnectServerInstallFolder>/AdeptiaServer/ServerKernel.
  3. Type ./startup.sh to start.

To stop the services, type ./stop.sh.

AIMap services start and stop automatically along with Connect Server Kernel and WebRunner when you run the ./startup.sh and ./stop.sh commands respectively. However, if you want to start or stop AIMap services individually, use the following commands:
./startAIMap.sh
./stopAIMap.sh

To ensure that Connect Kernel and Connect WebRunner are started successfully, go to the directory .../<ConnectServerInstallFolder>/AdeptiaServer/ServerKernel/logs/applicationlogs and type the following commands respectively:

  • cat KernelApplication.log
  • cat WebrunnerApplication.log

These commands will display the details of the KernelApplication.log and WebrunnerApplication.log files respectively. Ensure that these files contain the message that "Kernel has started successfully" and "WebRunner has started successfully".

Starting Connect Server automatically as a Linux daemon

Before you start, ensure that you are going to make these changes from within the root user account.

Perform the following steps to start Connect Server as a daemon:

  1. Go to the folder ...<ConnectServerInstallFolder>/AdeptiaServer/ServerKernel.
  2. Open startup.sh file.
  3. Update the path in the file as depicted in the example image given below.


    Ensure that the:

    • Path you enter is as per the installed location of Adeptia Connect in your system.
    • startup.sh file has executable permissions for the root user.
  4. Create a Systemd service file, “adeptiaconnectserver.service”, for the Connect Server at the following location: /etc/systemd/system.

    [Unit]
    Description= Adeptia Connect Server
    Documentation= https://docs.adeptia.com/
    
    [Service]
    Type=simple
    RemainAfterExit=true
    ExecStart=/bin/bash /usr/local/bin/AdeptiaBuild/AdeptiaConnect-3.3/ConnectServer/AdeptiaServer/ServerKernel/startup.sh
    
    [Install]
    WantedBy=multi-user.target
    Ensure that the path you enter is as per the installed location of Adeptia Connect in your system.


  5. Run the following command to reload the systemd daemon.
    systemctl daemon-reload
  6. Run the following command to start the Connect Server
    systemctl start adeptiaconnectserver
  7. Run the following command to enable the newly created service for the Connect Server to get started on system start-up.
    systemctl enable adeptiaconnectserver 

The Connect Server will now start automatically whenever your system starts.

To stop or restart the Connect Server running as a daemon, use the following commands:

  • To stop, run the following command:
    systemctl stop adeptiaconnectserver
  • To restart, run the following command:
    systemctl restart adeptiaconnectserver
After these changes, always make sure to start/stop/restart Connect Server as a daemon only. In case you want to use startup.sh or stop.sh to start or stop the Connect Server manually, make sure that the Connect Server is not running as a daemon. 

Starting Connect Portal

This section guides you on how to start Connect Portal manually and automatically.

Prerequisite

Configure the systemd service in your Linux operation system.

Starting Connect Portal manually

To start or stop the Connect Portal, follow the steps below:

  1. Open Terminal.
  2. Go to the directory ...<ConnectPortaInstallFolder>/bin.
  3. Type ./startup.sh to start.

To stop the services, type ./stop.sh.

To ensure that Connect Kernel and Connect WebRunner are started successfully, go to the directory .../<ConnectPortalInstallFolder>/logs and type the command.
cat catalina-YYYY-MM-DD HH-MM-SS.log

Ensure that these files contain the message stating Starting ProtocolHandler ["http-nio-80"].

Starting Connect Portal automatically as a Linux daemon

Before you start, ensure that you are going to make these changes from within the root user account.

Perform the following steps to start Connect Server as a daemon:

  1. Go to the folder …<ConnectPortaInstallFolder>/bin.
  2. Open startup.sh file.
  3. Update the path in the file as depicted in the image given below.



    Ensure that the:

    • Path you enter is as per the installed location of Adeptia Connect in your system.
    • startup.sh file has executable permissions for the root user.
  4. Create a Systemd service file, “adeptiaconnectportal.service”, for the Connect portal at the following location:
    /etc/systemd/system.       

    [Unit]
    Description= Adeptia Connect Portal
    Documentation= https://docs.adeptia.com/
    
    [Service]
    Type= simple
    
    RemainAfterExit=true
    ExecStart=/bin/bash /usr/local/bin/AdeptiaBuild/AdeptiaConnect-3.3/ConnectPortal/bin/startup.sh
    
    [Install]
    WantedBy= multi-user.target
    Ensure that the path you enter is as per the installed location of Adeptia Connect in your system.
  5. Run the following command to reload the systemd daemon.
    systemctl daemon-reload
  6. Run the following command to start the Connect Portal
    systemctl start adeptiaconnectportal
  7. Run the following command to enable the newly created service for the Connect Portal to get started on system start-up.
    systemctl enable adeptiaconnectportal

The Connect Portal will now start automatically whenever your system starts.

To stop or restart the Connect Portal running as a daemon, use the following commands:

  • To stop, run the following command:
    systemctl stop adeptiaconnectportal
  • To restart, run the following command:
    systemctl restart adeptiaconnectportal
After these changes, always make sure to start/stop/restart Connect Portal as a daemon only. In case you want to use startup.sh or stop.sh to start or stop the Connect Portal manually, make sure that the Connect Portal is not running as a daemon. 

Configuring Adeptia Connect as a Linux service for automatic startup

You can also start the entire application automatically by configuring it as a Linux service on your Linux system. To achieve this, follow the steps given below that set up automatic startup for both the Adeptia Connect Server and Portal.  

Important

You can add Adeptia Connect services – ConnectServer and ConnectPortal – as Linux services only on Red Hat Enterprise Linux Server 7.9 or a higher version of Linux.

Make sure that the chkconfig command is installed on your Linux system.
  1. Download the zip AdeptiaConnect.zip and extract it.
    The zip contains two service files – ConnectServer, and ConnectPortal
  2. Stop Adeptia services.
  3. Place the extracted ConnectServer and ConnectPortal files in the \etc\init.d folder.  
  4. Open ConnectServer file in edit mode.
  5. In the INSTALLATIONPATH field, enter the Adeptia installation directory path up to ServerKernel as shown in the example below. 
  6. Save the file.
  7. Open ConnectPortal file in edit mode.
  8. In the INSTALLATIONPATH field, enter the Connect Portal installation directory path up to the "bin" folder as shown in the example below.
  9. Save the file.
  10. Grant permissions to ConnectServer and ConnectPortal files to be executed by running the following commands. 
    chmod +x ConnectServer
    chmod +x ConnectPortal
  11. Run the following command to add the ConnectServer and ConnectPortal services in run levels. 
    chkconfig --add ConnectServer
    chkconfig --add ConnectPortal
  12. Check the status of the services by runningthe following command.

    chkconfig

    To check the status of a specific service, for example, ConnectServer, use the following command.
    sudo systemctl status ConnectServer.service
  13. Run the following commands to start the Adeptia services (if not started yet), enabling automatic startup of the application. 
    chkconfig ConnectServer on
    chkconfig ConnectPortal on
    You can also use following command to start the services. 
    service ConnectServer start
    service ConnectPortal start

    To stop or restart the services, use the following commands.
    • service <Service Name> stop
    • service <Service Name> restart
  14. Restart the system.
    After the system restarts, the ConnectServer service starts the java instances of Kernel, WebRunner, and AIMap services, and the ConnectPortal service starts the java instance of Portal.

Adding ConnectServer service without AIMap

If you wish to add Adeptia Connect services without AIMap, do the followings.

  1. Download the zip AdeptiaConnectWithoutAIMap.zip and extract it. 
    The zip contains three files – ConnectServer, ConnectPortal, and startup.sh
  2. Stop Adeptia services.
  3. Place the extracted startup.sh file at ../AdeptiaConnect/ConnectServer/AdeptiaServer/ServerKernel location.

    Make sure that you have granted the required set of permissions to startup.sh file for its execution.
  4. Follow the steps from 3 through 14 in the section above.
    After the system restarts, the ConnectServer service starts the java instances of Kernel, and WebRunner.

    To add the AIMap service at any later point in time, you can execute the startupAIMap.sh file located at ../AdeptiaConnect/ConnectServer/AdeptiaServer/ServerKernel. To remove the AIMap service again, you can execute the stopAIMap.sh file placed at the same location.

Next step

Verifying Installation  

  • No labels