SLA Unable to Connect to CMS (FWM 01009)

SLA Unable to Connect to CMS (FWM 01009)

Overview

When using 360Suite Semantic Layer Agent (SLA), the task fails with a RemoteException indicating a communication error with the CMS. This issue typically occurs after installing SLA on a Windows host and configuring RMI settings, even when network connectivity appears functional.

Error message observed:
  1. Error at line 1 of sheet 'Relational':
  2. Unable to create the Connection:
  3. java.rmi.RemoteException: Communication error occurred when trying to connect to server SERVERNAME:6400 (FWM 01009)

Symptoms

  1. 360Suite Tasks using the SLA fail with FWM 01009.
  2. Telnet from SLA host to CMS on port 6400 succeeds.
  3. IDT on SLA host can open a session on the same CMS.
  4. There are no firewall issues or restrictions.
  5. SLA logs show RemoteException during CORBA communication.

Cause

By default, the SLA launcher expects SSL mode when the BI environment is configured for CORBA SSL. But in this case:
  1. The CMS was configured with CORBA SSL, but the SLA was launched with -Dbusinessobjects.orb.oci.protocol=mixed.
  2. SLA code does not handle mixed mode; it only enforces SSL when explicitly set to ssl.
As a result, the SLA attempted a non-SSL handshake on a CMS requiring SSL, causing the FWM 01009 error.

Resolution

Force the SLA to use SSL for CORBA communication by setting the correct JVM parameter.
  1. Open the SLA configuration (default path: <360Suite_installation_folder>/360_Semantic_Layer_Agent/360Suite_Semantic_Layer_Agent.exe).
  2. In the Java tab, add the following parameters:
    -Dbusinessobjects.orb.oci.protocol=ssl
    -DcertDir=<path/to/corba/certificate/folder>
    -DtrustedCert=<comma-separated,corba,certificate,names>
    (Adjust paths and filenames to match your environment.)

  3. Restart the SLA service.

    • Related Articles

    • Configure 360Suite to communicate with SSL-enabled environments

      Context Many 360Suite modules need to communication with the BOBJ RESTful API to process specific actions, often "Webi and UNX"-related actions. The features using this RESTful API are the following ones: 360Bind (opening and working with Webi ...

    • Converting Oracle based MSU UNX to SSU fails with "driver could not be loaded error"

      Symptom When you launch a MSU to SSU conversion on a universe based on an Oracle ODBC connection. On WebPatform 2023.1.1 : The task ends in success When you retrieve the - Converted universe, you have an empty Data foundation On WebPlatform 2023.2 ...

    • SLA Installer Fails on 64-Bit Systems When Using BOBJ 4.2 (32-Bit)

      Symptoms Issue When installing the SLA (Semantic Layer Agent) on a 64-bit Windows system that has SAP BusinessObjects 4.2 (32-bit) installed, the SLA service may fail to start. This issue is due to an architecture mismatch: the SLA installer expects ...

    • Unable to create system preferences directory

      Condition The Apache Tomcat server log returns the following error on start-up: Could not create system preferences directory. System preferences are unusable Solution Cause This error occurs if the server is started using a user or service account ...

    • Unable to start 360Suite when tomcat uses slf4j

      Symptom tomcat root page is available /360suite url returns 404 error in tomcat/logs/localhost-{date}.log an error appears on 360Suite startup 03-May-2021 07:51:22.858 SEVERE [localhost-startStop-1] ...