Develop Reference

Migrate from Jboss EAP 6.4 to WildFly

I need to migrate my application from Jboss EAP 6.4 to WildFly. I am new to Jboss and not a developer. My application is currently deployed on Jboss 6.4 and it's working fine.
Can you please provide me with details on to how to migrate to WildFly server.
Which WildFly version should I use?
Are there any development work to migrate?
How to change configurations (like standalone.xml)?
Any hint or help to do this migration is appreciated. If you need any further information I can provide any details.

Based on the following resources, and my own personal experience, I find that Wildfly 8.2.1 is the closest I can get to EAP 6.4.
What Is The Wildfly Equivalent Of JBoss EAP 6.4
https://access.redhat.com/articles/112673#EAP_6
In terms of standalone.xml changes, I find that most of the changes I make to JBOSS EAP 6.4 and Wildfly 8.2.1 are interchangeable, but anything that includes an XML namespace will need to be updated. For example the loggers, datasources, security-domains use the same XML configuration, but their XML namespace has changed.
Now, as many have mentioned, this will vary tremendously based on your individual app and what subsystem components you're making use of. My own app tends to deploy using very few of the JBOSS capabilities/components, intentionally so that I can shift servers somewhat painlessly. However, other apps can integrate much more tightly and would require a great deal more to migrate.

Overview of camel endpoints?

I have deployed my camel integration projects (WAR) on a JBoss Wildfly application server.
I was wondering if there is a way to see what endpoints are available and what the URL's are?
In a similiar way as i can log into the administration console under Wildfly and select web services to get an overview of what is deployed?
Thanks in advance for your help.

Yes, if you have JMX enabled on your camel context, then you can view a list of endpoints via jconsole, as you can see from:
JMX is on by default according to the camel site but if you've somehow disabled it, adding:
<jmxAgent id="agent" disabled="false"/>
to your <camelContext> element should be enough to re-enable it.

There is also hawtio which is a web console to manage Java stuff, and it has plugins for Apache Camel, JBoss, and others too.
You could then install hawtio in wildfly, and then see your Camel routes / endpoints and whatnot
http://hawt.io/

Tomcat vs Pivotal tc Server

Could anyone advise as to the pros and cons of using Pivotal tc Server as opposed to just vanilla Tomcat for a Spring-MVC Java web application? Could find very little about Pivotal other than on their website and the fact it's packaged as part of the Spring Tool Suite. This lack of info is making me a bit wary about being dependent on it...
Background: Am preparing the development environment for a Spring-MVC project and currently evaluating whether to use the packaged Spring Tool Suite (STS) or just start with the latest Eclipse (possibly combined with the Eclipse STS plugin). Came across Pivotal tc Server as one of the optional components in this plugin.

Pivotal tc Server contains all of vanilla Tomcat, and has a few optional extensions designed to make it easier to deploy and maintain. Broken out into three groups, the diff looks like this:
Configuration extensions (No altered code, just config changes we implement)
Multi-Instance using shared binaries
Trivial to change Tomcat versions while preserving app and configuration
Variable Substitution in config files
Async Logging
Mild Security Tuning (ports, mgmt apps, JMX)
Code Extensions
Patch version releases – fix flaws in current release [e.g. tomcat-7.0.32.B.RELEASE]
Extended JMX interface
Additional Metrics
Application Deployment
Diagnostics Valve - good troubleshooting info when there's a slowdown
Config Templates – including custom-created
Change log level on the fly
Advanced Session replication (Gemfire)
Oracle DB Connection Proxy
Add-Ons
Windows Service Wrapper
RPM / Apt-Get / Debian installers (linux)
Startup scripts (linux)
Chef Recipes
Puppet Scripts
Password Encryption
Spring Insight for performance tuning
FYI on the tag thing, there's still the old "springsource-tc-server" tag. SpringSource is now Pivotal. (Can/should we update the tag or add a new one?)
Hope this helps.

SpringSource tc Server is an enterprise version of Apache Tomcat, the widely used Web application server. SpringSource tc Server is hardened for enterprise use and is coupled with key operational capabilities, advanced diagnostics, and is backed by mission-critical support.
SpringSource tc Server is designed to be a drop in replacement for Apache Tomcat, ensuring a seamless upgrade path for existing custom-built and commercial software applications already certified for Tomcat. Maintaining this level of compatibility enables our customers to add the business-critical functionality they need to more effectively run and manage their applications with the least amount of effort.
find more information at http://static.springsource.com/projects/tc-server/6.0/getstart/cgsdiffs.html

This doesn't answer your question about the pros and cons, but I found this site really helpful in getting tc server up and running in STS. http://sosiouxme.wordpress.com/2012/04/06/the-missing-guide-to-creating-and-modifying-tc-server-instances-for-sts/

To me it seems a high price for just getting a servlet container.
Specifically, it (the tc server) seems to try to mimmic a production quality application server (servlet engine) with the added features.
For development it seems overkill. You could just as well use Tomcat stand-alone or Glassfish or Jetty.
I would choose the tc server if my target was some cloud implementation of Cloud Foundary that was ultimately my target production deployment environment.
Finally, I just noticed that the tc server is a commercial offering. So, the licensing implications should the features become integral to your delivery, might have a cost that your project would not bear:
https://www.cdw.com/shop/products/SpringSource-tc-Server-Spring-Edition-license/2156278.aspx

How do I slim down JBOSS?

We're using Jboss, but we are really only using its JMS stuff. So, is there a way that I can trim down what's loaded when Jboss starts?

You can go for a servlet container (Tomcat) + a JMS provider (ex. ActiveMQ), without using an application server at all.

From 6 years ago, here's a blog entry about configuring JBoss with "just the right stuff."
I haven't used JBoss in a few years, but in v4.0, you could just drop the desired jar files into the deployment directory, and JBoss would load... only those jars.

The correct way to do this, is making a separate profile on your JBoss server that contains only the things needed to use JMS. JBoss v5 comes standard with several profiles: minimal, default, standard, all and web. Each of those starts other services. If you do not specify any profile, you're using the "default" profile.
You can create your own profile starting from a copy of the minimal profile and adding services as needed for JMS support.
The JBoss documentation contains a bit of information on what the files in those profile directories are used for. See Jboss server configurations.
You didn't specify which version of JBoss that you are using. Keep in mind that there are some changes in the configuration between JBoss v4 and JBoss v5/6. The referenced documentation in the answer from Cheeso points to JBoss v4.

Glassfish and Spring setup tutorials/examples?

A simple web search didn't really turn up any examples... so I'm wondering if anyone could point me to any information on configuring Spring on Glassfish? Everything I've been finding is horribly outdated.
Thanks!

Download Netbeans 6.8 it will give you glassfish and spring configured by default.
http://netbeans.org/community/releases/68/

Configuring Spring is not really related to the fact that you are using GlassFish or Tomcat or whatever, you just configure it for an application that you then deploy on a server.
If you have a specific GlassFish related issue, you should probably clarify the question.