JBoss WildFly Runtime Considerations

To deploy protected J2EE applications under WildFly Application Server, the actions described below are required.

Modify the standalone.xml File

You must add new global modules to handle hasp license calls in the standalone.xml file, as described below. This file is located in the jbossDirectory\standalone\configuration\ directory.

Add the following code to the file:

<subsystem xmlns="urn:jboss:domain:ee:1.0">
  <global-modules>
    <module name="org.jboss.safenet.javaee" slot="main"/>
    <module name="org.jboss.as.server" slot="main"/>
  </global-modules>
</subsystem>

Deploy Global Module

Together with the protected application, you must deploy files for the global module named in the standalone.xml file.

>org.jboss.safenet.javaee is the LDK global module in WildFly Application Server. The file safenet-sentinel-hasp-api-j2ee.jar is generated together with the protected JAR/WAR file when you protect your application with Sentinel LDK Envelope. You must place this file at location jbossDirectory\modules\org\jboss\safenet\javaee\main.

>In the same directory, deploy an xml file called module.xml that contains the following code:

<?xml version="1.0" encoding="UTF-8"?> 
<module xmlns="urn:jboss:module:1.0" name="org.jboss.safenet.javaee">
 <dependencies>
  <module name="javaee.api"/>
 </dependencies>
 <resources>
  <resource-root path="safenet-sentinel-hasp-api-j2ee.jar"/>
    <!-- Insert resources here -->
  </resources>
  </module>