Show TOC

Outbound Enabler Tab ReferenceLocate this document in the navigation structure

Understand the columns of data displayed in the Outbound Enabler tab for an SAP Mobile Server node.

Column Name Displays
Server Node ID the string that identifies the SAP Mobile Server in the cluster. This property is case-sensitive, and must match the value in the Relay Server configuration.
Mobile Server Port the port on which Outbound Enabler manages requests.
Farm Type the type of request managed by the Relay Server: Replication, Messaging or Webservice protocol. When configuring Relay Server Outbound Enabler properties for a scale-out node, you can select only the Webservice farm type.
Mobile Server Farm the string that identifies the SAP Mobile Server cluster, for which the Relay Server manages requests. This property is case-sensitive, and it must match the value in the Relay Server configuration.
Relay Server Host if the Relay Server farm has a load balancer in front of it, the host name or IP address of the load balancer. Otherwise, the host name or IP address of a single Relay Server.
Status current state of the Outbound Enabler process: stopped, running, or error.
Status Description
additional details on the state of the Outbound Enabler. If you receive one of these messages, follow the documented recommendation:
  • Unknown error state Check the log for additional details.
  • Failed to connect SAP Mobile Server, retrying... Check the SAP Mobile Server port managed by the Outbound Enabler.
  • Unauthorized. Check the security token of Outbound Enabler.
  • Unrecognized farm or server node ID. The string that identifies the SAP Mobile Server cluster or server node in the Outbound Enabler configuration does not match the Relay Server configuration.
  • Please check the relay server host and port or Failed to create I/O stream to the relay server If you use HTTPS port, check to see if the certificate file is valid.
  • Relay server service unavailable. Check if the Relay Server is properly configured, or if any internal errors are logged.
  • Relay server not found. Either the Relay Server is not yet deployed, or the URL suffix is wrong.
  • Bad request. Check the syntax of the URL suffix.
  • Error writing HTTP headers Check if the trusted certificate is valid, and verify the URL suffix syntax. Something may be misformatted.
Note
Sometimes when the Status column shows "Running" the Status Description shows: 
Relay Server outbound enabler is running. Please check the log file to confirm the status.
In these cases, the console may detect that an RSOE is running, even though the RSOE is actually in an error state.
  • The RSOE log level is set too high (4 or 5). SAP Control Center cannot detect the status from scanning the RSOE log.
  • The RSOE enters an unrecognized error condition. For example, when RSOE connects to Relay Server through an Internet proxy server, if the proxy server shuts down, the RSOE is effectively in an error state. The RSOE may continue to retry the connection indefinitely, and produce no log message recognized as an error.
Certificate File the certificate file uploaded to the SAP Mobile Server certificate store.
Log File the name and location of the Outbound Enabler log file. The syntax of this filename is <<nodeName>>.RSOE<<n>>.log. <<n>> is the primary key of the Outbound Enabler database record in the cluster database used by SAP Mobile Platform.