Skip to main content Skip to complementary content

Starting or stopping a Talend SAP RFC Server

You can manually start or stop a Talend SAP RFC Server by running the scripts or batch files in the bin directory.

Procedure

  1. Confirm that the process is running by running the ps command.
  2. Set up the Talend SAP RFC Server as a Linux service.

    On Red Hat and Ubuntu, the systemd service is used to start and stop services. You can find the files that control the systemd service in /etc/systemd/system.

    From the example, the sap-rfc file is added and not installed by default. If you want to add your Talend SAP RFC Server, use the following sample service file and ensure to change the paths that suit your installation:

    
    # SystemD descriptor file for Talend SAP RFC Server
    
    [Unit]
    
    Description=Talend SAP RFC Server service
    
    Before=runlevel3.target runlevel5.target
    
    After=local-fs.target remote-fs.target network-online.target time-sync.target systemd-journald-dev-log.socket
    
    Wants=network-online.target
    
    Conflicts=shutdown.target
    
    
    [Service]
    
    Type=simple
    
    Environment=JAVA_HOME=/usr/java/jre1.8.0_171-amd64
    
    ExecStart=/opt/talend/7.0.1/sap-rfc-server/bin/start-tsaps.sh
    
    ExecStop=/opt/talend/7.0.1/sap-rfc-server/bin/stop-tsaps.sh
    
    User=talenduser
    
    Group=talendgroup
    
    WorkingDirectory=/opt/talend/7.0.1/sap-rfc-server
     
    
    [Install]
    
    WantedBy=multi-user.target
  3. Open a terminal instance.
  4. Open the command prompt.
  5. Enter and execute the following commands (where $TSAPS_HOME corresponds to the directory where the Talend SAP RFC Server has been installed or extracted).
    • Run the following commands to start a Talend SAP RFC Server.

      cd $TSAPS_HOME/bin
      ./start-tsaps.sh
    • Run the following commands to stop a Talend SAP RFC Server.

      cd $TSAPS_HOME/bin
      ./stop-tsaps.sh

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!