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. Post-Upgrade Tasks
  10. Search Configuration Upgrade
  11. Hierarchies 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. Appendix A: Troubleshooting the Upgrade Process
  16. Appendix B: Frequently Asked Questions
  17. Appendix C: Processing Existing ActiveVOS Tasks
  18. Appendix D: Configuring Metadata Caching

Upgrading from Version 10.1, 10.2, 10.3, 10.4, or 10.5

Upgrading from Version 10.1, 10.2, 10.3, 10.4, or 10.5

Configuring Your Application Server for Java Standard Edition 17 Support in RedHat JBoss EAP 8.x

Configuring Your Application Server for Java Standard Edition 17 Support in RedHat JBoss EAP 8.x

Set the following security configuration changes to enable Java Standard Edition version 17 support in RedHat JBoss EAP version 8.x:
  1. Edit the
    standalone-full.xml
    using a text editor.
  2. Find the
    <security-domain>
    tag.
  3. To update the security domain configuration, add the following configuration directly under the
    <security-domain>
    tag:
    <security-domain name="ActiveVOS" default-realm="ActiveVOSSecurityRealm" permission-mapper="default-permission-mapper"> <realm name="ActiveVOSSecurityRealm" role-decoder="groups-to-roles"/> <realm name="local"/> </security-domain>
  4. To configure the ActiveVOS Security Realm properties, add the following
    ActiveVOSSecurityRealm
    property to the
    <security-realms>
    tag:
    <properties-realm name="ActiveVOSSecurityRealm"> <users-properties path="applicationUsers.properties" relative-to="jboss.server.config.dir"/> <groups-properties path="applicationRoles.properties" relative-to="jboss.server.config.dir"/> </properties-realm>
  5. Add the following HTTP authentication configuration to the
    http-authentication-factory
    tag.
    <http-authentication-factory name="activevos-http-authentication" security-domain="ActiveVOS" http-server-mechanism-factory="global"> <mechanism-configuration> <mechanism mechanism-name="BASIC"> <mechanism-realm realm-name="ActiveVOSSecurityRealm"/> </mechanism> <mechanism mechanism-name="FORM"> <mechanism-realm realm-name="ActiveVOSSecurityRealm"/> </mechanism> <mechanism mechanism-name="CLIENT_CERT"> <mechanism-realm realm-name="ActiveVOSSecurityRealm"/> </mechanism> </mechanism-configuration> </http-authentication-factory>
  6. To modify the Undertow SubSystem, change the
    default-security-domain
    value to
    ActiveVOS
    in the
    urn:jboss:domain:undertow:12.0
    subsystem tag as shown in the following example:
    <subsystem xmlns="urn:jboss:domain:undertow:12.0" default-server="default-server" default-virtual-host="default-host" default-servlet-container="default" default-security-domain="ActiveVOS" statistics-enabled="${wildfly.undertow.statistics-enabled:${wildfly.statistics-enabled:false}}">
  7. To add the user and role properties files, add the
    applicationUsers.properties
    and
    applicationRoles.properties
    files to the
    <jboss-server-path>\standalone\configuration
    directory.

0 COMMENTS

We’d like to hear from you!