Configuration WebInterface for the Internal Webservice

The AE Internal Webservice was the previous method to communicate with an AE system and is supported only for partners that have legacy installations and integrations to maintain. For new installations and integrations, the REST API is the newer and preferred communication technology. For more information, see REST API

As of version 21.0, the Automation Engine and the Java components communicate using TLS/SSL. These components establish a connection with the Java communication process (JCP), which uses trusted certificates to prove its identity to other communication partners.

You can use the trustedCertFolder= parameter in the respective configuration file to define the path to the folder where the trusted certificates are stored. Otherwise, the certificates should be installed in the Java trust store. For more information, see Securing Connections to the AE (TLS/SSL).

You can use the pushbutton Save Settings to store the settings to the file ucws.ini.

Connect Information and Default User

  • Java Communication Process (host:port)

    Connection to the Automation Engine using the format Server name:Port

    • Server name: Name of the computer on which the communication process is available

    • Port: Port of the Java communication process

      Example

      Server1:8443

  • Client

  • User

  • Department (optional)

  • Password

    Note: The number of stars does not refer to the password length

  • Language

    Allowed values: E (English, default), D (German) or F (French)

    The login fails if a value other than the values allowed is set.

Session Handling

  • Connection Timeout

    Timeout for connections (in minutes).

    The Internal Webservice closes connections to web clients automatically if the last request they sent dates back longer than the number of minutes defined here.

  • Waiting Connections

    Number of open connections to web clients (display field only).

    The pushbutton Close all can be used to close all open Web client connections.

  • Open Sessions

    Number of open web client sessions (display field only).

    Sessions will only be created if the web client logs on with the operation logon. Using the default user has the effect that a connection is established but no session is created.

Operation

  • Name of the operation

    Select the operations which can be processed with the default user.

    The operations logon and logoff are always available.