Labels

.net (1) *nix (1) administration (1) Android (2) Axis2 (2) best practice (5) big-data (1) business-analysis (1) code re-use (1) continuous-integration (1) Cordova-PhoneGap (1) database (2) defect (1) design (3) Eclipse (7) education (1) groovy (2) https (2) Hudson (4) Java (1) JAX-RS (2) Jersey (3) Jetty (1) localization (1) m2eclipse (2) MapForce (1) Maven (12) MySQL (1) Nexus (4) notes (4) OO (1) Oracle (4) performance (1) Perl (1) PL/SQL (1) podcast (1) PostgreSQL (1) requirement (1) scripting (1) serialization (1) shell (1) SoapUI (1) SQL (1) SSH (2) stored procedure (1) STS (2) Subclipse (1) Subversion (3) TOAD (3) Tomcat (4) UML (2) unit-testing (2) WAMP (1) WAS (3) Windows (3) WP8 (2) WTP (2) XML (4) XSLT (1)
Showing posts with label WAS. Show all posts
Showing posts with label WAS. Show all posts

Thursday, January 22, 2015

Why won't changes to web.xml in deployment directory take effect in WebSphere?

Normally when a web application is deployed to WebSphere, the "exploded" .EAR file resides in a directory similar to

C:\Programs\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\<your computer name here>Node01Cell\<EAR file name here>\<WAR file name here>

Most changes to files underneath this directory structure are reflected in the application after the web application is re-started.  However, making changes to web.xml here will not have any effect.  Instead, WebSphere stores a copy of web.xml in

C:\Programs\IBM\WebSphere\AppServer\profiles\AppSrv01\config\cells\<your computer name here>Node01Cell\applications\<EAR file name here>\deployments\<context root here>\<WAR file name here>\WEB-INF\web.xml

that it actually heeds.  Misleading, eh?

Tuesday, December 2, 2014

WebSphere, ADMA5006E, and java.lang.NullPointerException

After compiling some code with the Oracle JDK,

java version "1.8.0_20"
Java(TM) SE Runtime Environment (build 1.8.0_20-b26)
Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode)

I deployed to WebSphere I got the following error:

ADMA5006E: An error occurred configuring [my application name] in WebSphere Application Server repository: java.lang.NullPointerException

After adjusting my JAVA_HOME to point at the WebSphere Java,

 java version "1.6.0"
Java(TM) SE Runtime Environment (build pwa6460_26sr7fp1ifix-20140220_01(SR7 FP1+
IX90136+IX90137))
IBM J9 VM (build 2.6, JRE 1.6.0 Windows 7 amd64-64 Compressed References 2013123
0_180580 (JIT enabled, AOT enabled)

I was able to deploy to WebSphere.  While the javac command did not specify the target Java version, and the version 1.8 byte code may have problems running on a version 1.6 platform, getting a java.lang.NullPointerException doesn't seem like well-written error handling?

Wednesday, June 18, 2014

Where do you find WebSphere Application Server port information?

For WAS 8.5.5.2, to find port information, on the left-side of the admin GUI, Servers > Server Types > WebSphere application servers.

Then, on the main part of the GUI, choose your server, then Configuration tab > Communication sub-section > Ports