Versions Compared

Old Version 3

changes.mady.by.user Eric McDonald

Saved on

compared with

New Version Current

changes.mady.by.user Eric McDonald

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This guide focuses on the Wildfly's Elytron subsystem configuration needed to deploy CONNECT.

Please refer to the following CONNECT Implementation Guides to integrate CONNECT with your live web service components and to import genuine certificates issued by an authorized certificate authority before attempting transactions on a live exchange:

Prerequisites

  1. A running instance of MySQL - The CONNECT team uses version 5.7.22
  2. Either a downloaded /wiki/spaces/CONNECTWIKI/pages/117610137 or a /wiki/spaces/CONNECTWIKI/pages/113311928 CONNECT binary zip file or a local CONNECT build
  3. If Direct will be deployed with CONNECT, the Java Cryptography Extension must be installed. Please see the Oracle JCE Documentation.
  4. Set JBOSS_HOME as an environment variable with the path to your JBoss installation root and add the variable to your class path

...

SNI configuration are detailed in section " SNI Configuration in Wildfly 15" on Multiple Certificate, TLS and SAML support .

Address bindings

By default, WildFly services and applications are bound only to localhost.  As needed, change any references of 127.0.0.1 to the desired binding address.  0.0.0.0 can be used to bind to all addresses.

...

  1. Start the WildFly server and open the admin console. Follow the instructions for creating a new user.
  2. After creating a new user, click the Try Again link in the admin console to log in.
  3. In the Admin Console, click Deployments tab
  4. In the left Nav panel, click Add next to Deployment

  5. Choose Upload a new deployment click Next, click Choose File and browse to the <binary-location>/CONNECT-<VERSION>/CONNECT/<VERSION>/CONNECT-JB7-<VERSION>.ear file, click Next and then click Finish

    Info

    If deploying from compiled source code, the CONNECT ear will be located at $CONNECT_ROOT/Product/Production/Deploy/jboss7/target


  6. Click the Enable button corresponding to the CONNECT ear file

  7. Optional: For deploying CONNECT Admin GUI, repeat the steps 1-4 using <binary-location>/CONNECT-<VERSION>/CONNECTAdminGU/<VERSION>/CONNECTAdminGUI-<VERSION>.war

    Info

    If deploying from compiled source code, the AdminGUI war file will be located at $CONNECT_ROOT/Product/Production/Adapters/General/CONNECTAdminGUI/target


Log4J Configuration

Edit  $JBOSS_HOME/standalone/configuration/standalone.xml as following:

  • Add new file handler (ie NHIN) under the existing File handler to logging subsystem:


    Code Block
    titlelogging subsystem
           <subsystem xmlns="urn:jboss:domain:logging:6.0">
            ..
            <periodic-rotating-file-handler name="FILE" autoflush="true">
                <formatter>
                    <named-formatter name="PATTERN"/>
                </formatter>
                <file relative-to="jboss.server.log.dir" path="Nhin.log"/>
                <suffix value=".yyyy-MM-dd"/>
                <append value="true"/>
            </periodic-rotating-file-handler>
            <logger category="gov.hhs">
                <level name="DEBUG"/>
            </logger>
            <root-logger>
                <level name="INFO"/>
                <handlers>
                    <handler name="FILE"/>
                </handlers>
            </root-logger>
            ..
        </subsystem>


FIPS Mode

Wildfly 15 with FIPS-140-2 and SNI

Further Reads