Installation Guide for Oracle Database with Red Hat JBoss

10.4 HotFix 2

Back Next

Configure Server Properties for the Full Profile

Configure the server properties for the full profile of the standalone mode in the

standalone-full.xml

file. The file is in the following directory:

JBoss installation directory

>/standalone/configuration

. To configure the server properties, you can run the commands for the configuration from the JBoss Command Line Interface (CLI).

To use the JBoss CLI, perform the following steps:

Navigate to the following directory:

JBoss installation directory

>/bin

To launch the JBoss CLI, run the following script:

On UNIX.

jboss-cli.sh

On Windows.

jboss-cli.bat

To connect to the server, run the following command:

connect

For more information about configuring server properties, see the JBoss documentation.

Transaction Timeout

The transaction timeout property specifies the time in seconds to wait for the MDM Hub transactions to complete. Set the value based on your environment.

Command:

/subsystem=transactions:write-attribute(name=default-timeout,value=<timeout in seconds>)

Sample configuration:

<subsystem xmlns="urn:jboss:domain:transactions:4.0">
    ...
    <coordinator-environment default-timeout="3600"/>
</subsystem>

Maximum Post Size

The maximum post size property configures the maximum size in bytes of files that you upload. Set the value to the size limit of files that you want to attach in the Data Director application.

Set the value to 20000000 or higher. Default is 10000000.

After installing the MDM Hub, set the same value for the Hub Server property

cmx.file.max_file_size_mb

in the

cmxserver.properties file.

Command:

/subsystem=undertow/server=default-server/<listener type>=<listener name>/:write-attribute(name=max-post-size,value=<maximum file size in bytes>)

Sample configuration:

<subsystem xmlns="urn:jboss:domain:undertow:4.0">
    ...
    <server name="default-server">
        <http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2="true" max-post-size="20000000"/>
        <https-listener name="https" socket-binding="https" security-realm="ApplicationRealm" enable-http2="true" max-post-size="20000000"/>
        ...
        </host>
    </server>
    ...
</subsystem>

Remoting-Connector

The remoting-connector property configures the remoting-connector port and socket binding.

To log in to the Hub Console from a remote machine, set the port to 4447 and the socket binding to remoting.

By default, remoting-connector security is disabled. If you want to configure remoting-connector security for the MDM Hub, ensure that you configure only the Elytron security framework that is supported.

Command:

/socket-binding-group=standard-sockets/socket-binding=remoting:add(port=4447)

/subsystem=remoting/connector=remoting-connector:add(socket-binding=remoting)

Sample configuration for remoting-connector port:

<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
    ...
    <socket-binding name="remoting" port="4447"/>
    ...
</socket-binding-group>

Sample configuration for remoting-connector socket binding:

<subsystem xmlns="urn:jboss:domain:remoting:4.0">
    ...
    <connector name="remoting-connector" socket-binding="remoting"/>
    ...
</subsystem>

Rename Saved Search

Table of Contents

Installation Guide for Oracle Database with Red Hat JBoss

Installation Guide for Oracle Database with Red Hat JBoss

Configure Server Properties for the Full Profile

Configure Server Properties for the Full Profile

Transaction Timeout

Maximum Post Size

Remoting-Connector