IDM 14.2 CP5 fails to start after migrating JBoss EAP 6.4 to EAP 7.2

book

Article ID: 141311

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal CA Identity Suite

Issue/Introduction

When there is No http listener configured in jboss 6.4,  after migration to jboss 7.2, the "ejb" subsystem with service "remote" throws an error during the EAP 7.2 App server startup.
Something like this below

                                  ("subsystem" => "ejb3"),
                                  ("service" => "remote")
                                 ]) - failure description: {
                                         "WFLYCTL0412: Required services that are not installed:" => ["jboss.remoting.remotingConnectorInfoService.http-remoting-connector"],
                                         "WFLYCTL0180: Services with missing/unavailable dependencies" => [
                                         "org.wildfly.clustering.cache.registry-entry.ejb.client-mappings is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]",
                                        "org.wildfly.ejb.remote is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"

Environment

Release : 14.2

Component : IdentityMinder(Identity Manager)

Resolution

1) For the "remote" subsystem 

    remove the remoting-connector   (i.e.)   change below subsystem 
    
       <subsystem xmlns="urn:jboss:domain:remoting:4.0">
            <connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/>
            <http-connector name="http-remoting-connector" connector-ref="http" security-realm="ApplicationRealm"/>
        </subsystem>


   To
            
            <subsystem xmlns="urn:jboss:domain:remoting:4.0">
                        <http-connector name="http-remoting-connector" connector-ref="http" security-realm="ApplicationRealm"/>
             </subsystem>

2) Change the connector-ref that is present in  http-remoting-connector to use https instead of http
       
        <subsystem xmlns="urn:jboss:domain:remoting:4.0">
                        <http-connector name="http-remoting-connector" connector-ref="http" security-realm="ApplicationRealm"/>
             </subsystem>

      To

             <subsystem xmlns="urn:jboss:domain:remoting:4.0">
                        <http-connector name="http-remoting-connector" connector-ref="https" security-realm="ApplicationRealm"/>
             </subsystem>

3) There is a known issue with EAP 7.x (https://access.redhat.com/solutions/3464611)
    so we need to follow the resolution as recommended and add in the missing  lines in standalone configuration file 
        

 <subsystem xmlns="urn:jboss:domain:webservices:2.0">
        <modify-wsdl-address>true</modify-wsdl-address>
        <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>
        <wsdl-port>8080</wsdl-port>
        <wsdl-secure-port>8443</wsdl-secure-port>
        <wsdl-uri-scheme>https</wsdl-uri-scheme>
        ...
    </subsystem>


  Mostly the missing line are 
        <wsdl-port>8080</wsdl-port>
        <wsdl-secure-port>8443</wsdl-secure-port>
        <wsdl-uri-scheme>https</wsdl-uri-scheme>