Standalone.xml file of jboss equivalent in websphere - jboss

I'm trying to migrate a web app from Websphere to JBoss.
I believe the first step is to port the configurations of the server. The main configuration file in Jboss is standalone.xml (or domain.xml for running multiple instances of a server).
Could you tell me what the equivalent of standalone.xml is in websphere ?
Thank you for your time.

There is no direct equivalent. WebSphere is administered via the administration console. If you run WebSphere Express you can connect directly to the app. server's administration port. If you run Network Deployment, you connect to the deployment manager console (DMGR).
The console has all the configuration. They are stored in many XML files, that can be a pain to use directly. Much easier with the console.
The default console port is 9060 (http) or 9043 (https).
URL:
http://yourserver:9060/ibm/console
https://yourserver:9043/ibm/console
See this technote: http://www-01.ibm.com/support/docview.wss?uid=swg21155098
for a bit more information.
You can look at this migration guide for JBoss AS 7.
https://docs.jboss.org/author/display/AS72/How+do+I+migrate+my+application+from+WebSphere+to+AS+7?_sscc=t

Related

JBoss 4.0 HotDeploy

good day.
I am trying to enable hot deploy on my JBoss 4.0.
I have tried to access to localhost:9990, but it doesn't work.
Is there any alternative way to enable it?
Thanks in advance.
JBoss 4.0 contradicts to port 9990.
The port 9990 is the management console access for JBossAS7 and WildFly.
JBoss 4.0 might have a JMX console which is accessible via 8080.
You can simpel use localhost:8080 and navigate from the welcome page.
Note that hot deploy is not recommended for productional JBossAS4/5 instances because of class loading issues, OOM errors.
You might use it for development.
Also JBossAS4 does not have managed deployments, simple drop the file to server/yourProfile/deploy and it will be picked up and deployed.

Configure IBM HTTP server for Jboss Application server

Recently we have moved our application from websphere to jboss application server.
IBM Http server (IHS) has front ended(proxy) the websphere application server.
Now we want to make changes to httpd.conf to make the IHS to front end the jboss. So whats the configuration to be done at IHS server to act like reverse proxy for JBOSS application server?
There's really no reason to do this, because IBM HTTP Server is only ever supported when it's used with IBM software that it was bundled with.
If you do do it, you're nearly alone in doing so and w/o the assistance of IBM.
Technically, you could use mod_proxy_balancer and mod_proxy_http just like any other Apache-based server, but they're not as well maintained because they are only used in one very obscure/withdrawn IBM product that bundles IHS. It's a basic proxy configuration for Apache and not really worth going into detail here.
The best option for JBoss AS/Wildfly application server proxy for you is Apache HTTP Server with mod_cluster.
Community
You can give it a try with Fedora: mod_cluster package
And there is an example on how to compile it from sources and configure it with Apache HTTP Server from scratch: example, recorded terminal session. It also operates on Windows and Solaris.
Why mod_cluster over mod_jk/mod_proxy?
The main benefit of mod_cluster over mod_proxy*balancer / mod_jk solutions is that both JBoss AS and Wildfly contain mod_cluster subsystems that automatically report deployed contexts and life cycle events to the mod_cluster balancer in Apache HTTP Server. JBoss AS/Wildfly workers join Apache HTTP Server balancer automatically, you don't have to reconfigure anything in your httpd.conf nor restart httpd when you add another JBoss AS/Wildfly worker.
Current load report is also a part of these service messages. One may use several different load metrics within JBoss AS/Wildfly, e.g. heap utilization, CPU load, number of currently open sessions, or one could easily implement a custom load metric.
The result is a high-throughput dynamic load balancer that takes into account actual utilization of your JBoss AS/Wildfly workers.
Commercial support
If you need a fully supported solution for mod_cluster balancer, both Red Hat JBoss Web Server, i.e. Apache HTTP Server, mod_cluster, OpenSSL, Tomcat 7, Tomcat 8, mod_jk, ModSecurity, and Red Hat JBoss Enterprise Application Platform (EAP), i.e. application server built on Wildfly 10+ or AS 7+, entitle you to fully supported mod_cluster balancer fronting either Tomcat workers or EAP workers.
Full Disclosure: I am an engineer at Red Hat

Aws backend code debugging

I deployed my backend code(used framework is drop-wizard) in the form of jar file on AWS(Amazon Web service) server. I want to know is it possible to debug that jar file(jar file deployed on the AWS server) using eclipse on my local pc?? If yes than please display the way of how to do it??
Looking for a good response
Thanks
First, you need to start your application with remote debugging
enabled. With dropwizard, you are typically starting the application
on a server with:
java -jar myapp-0.0.1-SNAPSHOT.jar
Change this to:
java -Xdebug -agentlib:jdwp=transport=dt_socket,address=9999,server=y,suspend=n -jar myapp-0.0.1-SNAPSHOT.jar
This sets up Java to listen for remote debugging sessions on port
9999. Make sure you choose a port that's not blocked by firewalls or
your AWS security configuration.
Next, you have to configure Eclipse to connect to the remote
application for debugging. In Eclipse, right click on the project and
select Debug, Debug Configuration. Create a new configuration of
Remote Java Application. Set the host to your AWS server and the port
to 9999, as above.
Now you should be able to set a breakpoint in your code and start a
debug session on the remote server.

Can't Access ActiveMQ Web Console

I am having trouble accessing ActiveMQ's web console.
On their website it says you can access the console through the URL : localhost:8161/admin
But all I get when I try this is "This webpage is not available"
I found another site saying I can access it through port '61616', which gives me a response in the form of the following :
I have done some extensive searching on this issue, and have found others with the same problem, but have not come across a solution.
I am fairly new to using ActiveMQ so please excuse me if I have left out any relevant information.
Any help is greatly appreciated.
The admin console is a web application (WAR-file) deployed in an embedded Jetty server that starts up along with ActiveMQ standalone distribution.
Since you intend to run ActiveMQ inside a web application inside Tomcat, it would not make sense to fire up a jetty server.
Simply deploy the web console WAR to your Tomcat. You need to point out the JMS/OpenWire connection URI as well as JMX connection URI to ActiveMQ Web Console to get it going. Typically in Tomcat setenv.sh (or similar file):
JAVA_OPTS="$JAVA_OPTS -Dwebconsole.type=properties -Dwebconsole.jms.url=tcp://localhost:61616- Dwebconsole.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi -Dwebconsole.jmx.user=admin -Dwebconsole.jmx.password=mypassw0rd"
This requires you to have JMX setup on your Tomcat instance. If not, check this Tomcat doc page out.
This will deploy the console just like any app in your Tomcat (not port 8161).
Off-topic, but a nice feature with decoupling the web console from the actual broker is that you can access a the activem broker of a master/slave pair using failover protocol and comma separated jmx settings.

JBoss AS 7.1.1 Remote Application Monitoring

atm I'm facing some problems when I'm trying to connect to my JBoss AS 7.1.1 (on a Linux-Server) via JMX remotely and monitor my Java-Apps from a Win-7 client. I can only see the standard JVM settings but no app-specific ones.
I learned that I have to include the jars in the Classpath while starting jvisualvm on my Windows 7 client.
that looks like this:
"C:\Program Files (x86)\Java\jdk1.7.0_07\bin\jvisualvm.exe" -cp:a C:\Users\myuser\jboss-as-7.1.1.Final\modules
But still it is not working...when I try to connect via:
service:jmx:remoting-jmx://:9999
Is there any special configuration I have to change in my JBoss server besides enabling jmx-management in standalone.xml?
Thanks in advance!