Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Troubleshooting the Upgrade Process
  16. Frequently Asked Questions
  17. Processing Existing ActiveVOS Tasks
  18. Configuring Metadata Caching

Upgrading from Version 9.5.1

Upgrading from Version 9.5.1

Configure Server Properties for the Full Profile

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
standalone-full.xml
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 run the JBoss CLI, from a command prompt, navigate to the following directory:
<
JBoss installation directory
>/bin
The following table describes the server properties configuration for the full profile:
Configuration
Description
Command
Transaction timeout
Ensures that the MDM Hub transactions have enough time to complete. In the
subsystem
with the name
urn:jboss:domain:transactions:<n.n>
, set
default-timeout=3600
within the
coordinator-environment
element.
/subsystem=transactions:write-attribute(name=default-timeout,value=3600)
HTTPS protocol
Configures the HTTPS protocol for MDM Hub communications and for ActiveVOS communications with the MDM Hub.
Before you configure the HTTPS protocol, use the Java
keytool
command to generate a certificate and store it in a keystore. The certificate must be signed by a trusted certificate authority. Note the key alias and keystore password that you create.
To configure the HTTPS protocol, in the subsystem with the name
urn:jboss:domain:undertow:<n.n>
, add the
https-listener
element to the server configuration.
/subsystem=undertow/server=default-server:write-attribute(name=https,value=https)
Maximum post size
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.
In the
subsystem
with the name
urn:jboss:domain:undertow:<n.n>
, set the
max-post-size
attribute of the
<https-listener name=" <listener type>">
element 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.
/subsystem=undertow/server=default-server/https-listener=<listener type>/:write-attribute(name=max-post-size,value=<maximum file size in bytes>)
Remoting-connector
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.
In the
subsystem
with the name
urn:jboss:domain:remoting:<n.n>
, set the
port
attribute to 4447 for the child element
<socket-binding name="remoting">
of the
socket-binding-group
element.
Set the
socket-binding
attribute 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.
/socket-binding-group=standard-sockets/socket-binding=remoting:add(port=4447)
/subsystem=remoting/connector=remoting-connector:add(socket-binding=remoting)
For more information about configuring server properties, see the JBoss documentation.

0 COMMENTS

We’d like to hear from you!