Configure Wildfly as a Web Application Server
Updated: May 15
Teamcenter and Active Workspace require a Web Application Server for communication from the client to the Server Manager. Wildfly is one option of many (Tomcat, Weblogic, JBoss, etc.) that can be used to perform this function.
In the example below, we demonstrate how to configure Wildfly (JBoss) to connect to the Teamcenter and Active Workspace environment to enable communication pass through.
The configuration of the tc.war is a prerequisite for this process. This process provides an interaction with the Web Application Manager (WAM) to build the tc.war file. In addition, if not done already, if you are running Active Workspace 4.3+ you will need to ensure the Microservices are integrated into the Web Application Server.
For information regarding compatible versions of Wildfly and other supported Web Application Servers, see the Teamcenter Certifications and Information section of the Hardware and Software Certifications page on the Siemens Solution Center.
The image (above) shows the various versions of the available Teamcenter Certifications documents on the Siemens Support Center webpage.
Try it out
Learn how to install and configure Wildfly to support a Development or Training Teamcenter and Active Workspace Environment.
Version compatibility
The process is validated in Teamcenter 11 through the latest release (14.*). The process is also validated in Active Workspace 3.4 through the latest release of (6.*). Versions of Wildfly vary depending on the supported version of Teamcenter.
Process to configure Wildfly
Download and extract the supported (compatible) version of Wildfly
Tip. Be sure to reference the Hardware and Software Certifications for the version you are installing to ensure you use the correct and supported version of Wildfly.
Tip. Ensure the directory where Wildfly executes is the directory you intend to run it from prior to proceeding to the configuration.
Example. we placed the wildfly-26.1.1.Final (supported version for Teamcenter 14) in our C:\Apps directory.
Modify the standalone.xml configuration file in the Wildfly installation.
Locate the standalone.xml file in the Wildfly directory. This directory is under the main Wildfly program directory at the following location:
<WILDFLY>\standalone\configuration\standalone.xmlOpen the standalone.xml file in a text editor (we prefer Visual Studio Code).
The image (above) shows an example in Wildfly26 where the standalone.xml file resides.
Tip. In addition to Visual Studio Code, Notepad, Notepad++, and other text editors will do the job just fine.
In the standalone.xml file, perform a search for the following string.
EE:
The image (above) shows the line to look for in the standalone.xml file and the search term.
Caution. The ee:6.0 may reference other numbers, such as 4.0, in different versions of Wildfly. The search ee: will be the key identifier for the line.
Directly beneath the <subsystem xmlns="urn:jboss:domain:ee6.0"> line, add the following element.
<global-modules>
<module name="org.jboss.as.jmx" slot="main"/>
</global-modules>The resulting file will resemble the following screenshot.
The image (above) shows the resulting xml definition in the standalone.xml file.
In the standalone.xml file, perform a search for public.
Locate the interfaces section of the file.
Update the inet-address IP addresses to reflect a range available to your server.
In this example, we used 0.0.0.0 which is wide open. This is only acceptable for our purposes due to other security measures blocking access to the server. Read more information regarding IP addresses and subnets.
Save and close the standalone.xml file.
Add the JMX dependency to Wildfly
Due to adding the org.jboss.as.jmx module to the standalone.xml, you must next add the dependency for the module in order to use it.
In the Wildfly directory, navigate to the following sub-directory.
<WILDFLY>\modules\system\layers\base\org\jboss\as\connector\main
The image (above) shows the module.xml file in the subdirectory in the Wildfly installation. Note that the base folder may vary based on Wildfly version used.
Open the module.xml file in a text editor.
Near the bottom of the file, add the following element.
<module name="org.jboss.as.jmx"/>
The image (above) shows the resulting file with the added element.
Save and close the module.xml file.
Install Wildfly as a service
In order to create an automated service to run Wildfly at startup of the Windows Operating System, you must first copy the service scripts to the <WILDFLY> bin directory and execute the service with a provided script.
In the <WILDFLY> home directory, navigate to:
C:\Apps\wildfly-26.1.1.Final\docs\contrib\scriptsCopy the service folder.
In the <WILDFLY> home directory, navigate to:
C:\Apps\wildfly-26.1.1.Final\binPaste the copied service folder.
The resulting directory will resemble the image (below).
The image (above) shows an example of the location where the service folder is to be pasted.
In an Administrative Command Prompt, type:
cd /d <WILDFLY>\bin\serviceNote. The <WILDFLY> variable in the code (above) represents your installation directory for Wildfly. For example, if using the version in our example the value to type would be:
cd /d C:\Apps\wildfly-26.1.1.Final\bin\servicePress Enter.
Next, type:
service install /name WildflyPress Enter.
The image (above) shows the <WILDFLY> value we used in our example. This path may vary based on your location of the installation and version but the \bin\service will remain the same.
Verify the result states the service is installed.
In a Services window, set the Wildfly service to Started and Automatic.
The image (above) shows the properties dialog for the Wildfly service. Note the Startup type and Service status fields.
In a browser, navigate to:
http://localhost:8080 Tip. The value localhost may be swapped out for the server name (hostname) of the server where Wildfly is configured to run.
Validate the Wildfly instance is running.
The image (above) shows the verification step to validate the Wildfly instance is running.
Deploy the tc.war file to the Wildfly server.
The final step in the process is to locate the tc.war file that is build using the Web Application Manager (WAM) and deploy it to the Wildfly server.
Locate the staging directory in the Web Application Manager (WAM) where the tc.war file was generated.
Copy the tc.war file.
In the <WILDFLY> home directory, navigate to:
<WILDFLY>\standalone\deploymentsPaste the copied tc.war file into the directory.
Validate that the file shows a .deployed status after a few moments.
The image (above) shows an example of where to deploy the tc.war file
Caution. Avoid keeping backups of the tc.war file or other files in this directory as Wildfly will attempt to deploy everything.
For additional reference. Below are additional links that will aid you in understanding, setting up, and learning about open issues and troubleshooting with the tc.war configuration and J2EE Web Application Server setup.
The links (below) direct you to documentation and resources that may be of help on this topic. The links direct to the Teamcenter 14. online help documentation on the Siemens website. However, the information is located in a similar location under each version of Teamcenter 12.3+.
Tip. Some of the following links direct to the Siemens Solution Center and it's content. You will need to have access to a Siemens Account. Login to the Siemens Solution Center, then click the link to redirect to the page.
Help Documentation Links
Support Center Knowledge Base (KB) Articles
It is recommended to visit the Siemens Support Center site and search all open tickets and Knowledge Base articles for useful tips, current issues, and more.
Tip. Be sure to filter by "Knowledge Base" or "Support Cases" to see articles related to this topic.